I’ve been using an android phone for tha past couple of years. I started with a G1 just over 3 years ago, then about 2 years and 8 months ago I upgraded my phone to a Nexus One.
There are some things that I have to admit that I like very much about the Android platform. In fact I’m using it both on my phone and on my Nook Color. It is included in a few other things, like the base of the Nook Color, however that’s a fairly restricted edition, and from what I’m seeing the Nook Tablet is in much the same boat.
I’ve considered replacing the ROM on the Nook Color (NC) more than once, but I keep coming back to the question of do I need to? And frankly it looks now like I don’t have to.
About a year ago one of the developers on XDA Net found a way to get the developer edition of the Honecomb edition of Android to run from a uSD card on the NC. I’m pretty sure that the main reason that the NC does boot from the uSD slot is that it allows the support team to boot the platform to a known state so that they can do diagnostics of the hardware, check the internal memory, and if needed restore the e-reader to a known good OS if perhaps a corrupted OS was received over the net some how.
That said, a side effect is that you can run a full OS from the slot, and while some people use that feature to root the e-reader, running Honeycomb, and various cyanogen mod on the tablet does work.
Unfortunately there are issues with the Honeycomb developer edition. Google decided that they were not going to release the source code as they had for earlier versions, so development ultimately stalled, and some stability issues were left in place. Additionally because the source code was not available, developers could not do things like comment out features of the OS that were related to hardware that the NC didn’t have, such as a camera, or a cell phone radio. And it’s neigh onto impossible to add drivers for hardware that is included in the NC, but which isn’t part of the base hardware load for the target platform of Honeycomb, such as bluetooth.
Given all of that, the Honeycomb release did work well enough that well over 90% of the time I used my Nook Color this last year I was booted up into it.
I did consider trying to move to an SD release of CM7, however I did run into some of the various issues with different uSD cards. In short if you want to run an OS on a NC from the uSD slot, it’s a good idea to use a SanDisk Class 2 or Class 4 card. There are good reasons to use a Class 10 card in some devices. They are great for moving large files around. (Think RAW images on a dslr.) However they are really bad for small block transfers, say getting or updating configuration files.
So about 6 months ago the follow on to Honeycomb was released, and there was some question as to whether the source code for it would be made available. After all, if one release wasn’t viable, would the next one be? Google has historically released the source code for each edition of Android 30-90 days after they release the binary code.
The follow up to Honeycomb is ‘Ice Cream Sandwich’ or ICS. One of the limitations with ICS is that it HTC and Google are not going to push ICS to the Nexus One. Installing it would tie up too much of the internal memory, and make it almost impossible to run any applications on top of it. That’s not a usable setup, and hardly a place where Google wants to showcase the system to new customers.
About 4 months ago, Google did release the source code for ICS. “Great!” you say. “Now compile it and push it pretty much everywhere!” I’d say you don’t understand, but it’s not really quite that ieasy. Actually one could do that. And I’m sure that there are people who did, but there’s a problem with doing that. The code from Google is expecting to run on hardware that Google knows about. If you want to run it on other hardware, you need to figure out where in the code what you want to run it on can be supported. And if there is hardware that is missing that you want to get around, you need to allow for that as well.
And at this point you have to go back to the various people who have been working on various alternative distributions of Android that they’ve been customizing from earlier releases of source code. The thing is that these people do understand the difficulty of building supportable code. They really do want to know what’s working, what isn’t, and if possible why what isn’t working, well, isn’t. One of the things that they realized early on when looking at the ICS code is that a lot of it was stuff that was minor revisions from what they had been working on before, That part they already understood, and didn’t want to start making major changes to. The were also seeing that some of the stuff they had been fighting with for the past several years was being addressed in the new code from ICS. So they started working their way through that, and applying what they were learning to the code base they already had.
One of these teams was the group of developers working on Cyanogen Mod. They had gotten to the point where they had released their version 7 of the platform, and this is the code base they were building on. At a raw comparability level between what’s running on my Nexus One, the CM7 code package is very close to the same base. However what was released as CM7 will run on hardware that the code Google distributed as part of 2.3 (the current version on Nexus One) won’t run on. And arguably even on the Nexus One the CM7 code very possibly will run cleaner. They have been developing the base for a longer period of time, and they really do have a pretty good idea of what they are doing.
What the Cyanogen Mod team are doing is starting with a raw CM7 code base they are patching it with fixes from the ICS code base and incrementally work through that to develop CM9. (CM8 would have been the Honeycomb equivalent, but since Google didn’t release that code, it was skipped.)
In the past month there has been some movement in the CM9 release process. In short CM9 has essentially gotten to the ‘Alpha’ stage. There are still a lot of things that need to be worked out, and it’s hardly a stable release from the perspective of a commercial perspective, but it is working, and most of the varieties of bugs that would cause customer hardship have been worked out. And it looks like the release version of ICS.
Now I’m not going to advise anyone who’s really concerned about their Nook Color to go out and install ICS. Could you? Sure. But like I say the developers are not recommending it, and I certainly won’t either. They do however want other developers to start working with the code they have gotten through and start trying it in more ‘real world’ conditions to start shaking out more of the bugs. That way they can identify what is still at issue, and what can be worked around. It also gives the developers the chance to try different installation mechanisms.
I like the fact that I really do have a pretty much stock Nook Color. It’s running the Barns and Nobel release of Android, I can read books, watch videos, and do a bunch of other stuff with it with the stock OS. That said I don’t want to make major changes to it.
On the other hand I want to see what else I can do with it. It’s possible to do a lot more than the stock OS provides. But if I go and load up the Nook Reader software and it stops working, having the option of shutting down, restarting and loading the B&N software on the B&N os means that I can eliminate B&N as the cause of the problem that I’m seeing. When I upgrade to a Nook Tablet, I would like that same option. I don’t know that I’ll get it, but I would like to do that there as well.
So we’re back to the uSD based OS. In the past month there have been a couple of releases of CM9 for SD boot. and one enterprising developer realized that some of the apps he used ran better under CM7 than under CM9 and decided that he would rather set up a uSD card to support booting both CM7 and CM9. He then released his code.
I’ve instaled it on a 32gig uSD class 4 card from SanDisk and it is working well for me. And that brings me back to where I was earlier. Phones.
I’m looking at my options and I’m not liking a lot of what I’m seeing in the cell phone industry. I’m paying over $130 a month for two android phones on the T-Mobile service plan, and last month we used all of about 100 minutes of talk time. Most of what I use my phone for I can start doing on my NC with CM9, and I’m expecting that will improve in the next few weeks as CM9 gets closer and closer to a final release. Google Voice indicates that it will install on my NC with CM9, so if I can get my bluetooth headset to pair up I can use it to place calls, and when I don’t have wifi service I can still use the contacts list to pull up phone numbers and such. So I’m left wondering what do I need an android phone for?
Well there’s the camera. And you know what they say, any camera is better than no camera when you need to take a picture. But I can get a camera on a feature phone. And there really isn’t a need for me to pay $65 a month for that feature. What about the wifi hotspot? Well, I can get a wifi hotspot from Virgin and pay $20 a month to get service away from home. In fact I do have one of those, so there isn’t much of an incentive to stick with a $50 plan. And I’m not sure that the 500 MB plan is all that bad either. After all most of the time I’ll be using the home connection, and nothing works for me at work. Most of the time where I would need non-home wifi I’m doing a quick search for something, or perhaps getting directions, which means I really don’t need unlimited access.
So I’m down to well, you need a phone. Ok. I sent or received 2 text messages last month, and the pair of us used less than 100 min of cell phone service last month. Both fall well within a $20 / 3 month plan.
So really for me I don’t see a good reason to stay with T-Mobile at this point. Time to look at something else.
Not saying you should. Though if you decide that this is a good time to re-evaluate what services you need, that works too.
-Rusty