Quick Solution: Rooting your phone is actually much, much easier than I thought it would be. The two excellent guides that I used are Android and Me’s G1 rooting article and xda-developer’s G1 rooting article. Once you have rooted your phone, you can manually update to Cupcake (Android 1.5) without waiting for the OTA update.

The Whole Story
From what I have read and experienced, an out-of-the box T-Mobile Android G1 is completely reliant on T-Mobile for updates to the Android Operating System. The dilemma here for T-Mobile is probably that customers want timely updates, but they want those updates to be high-quality and bug-free. These two demands are opposing forces in the software development world: a high-quality and bug-free update takes time to build, and then takes lots more time testing for compatibility with millions of users running thousands of different applications in millions of different ways. A buggy update could be released quickly, but who really wants a buggy application?

An additional speculation of mine is that T-Moblie also has to maintain a reputation as well as remain competitive against the iPhone. If T-Mobile acts too quickly and releases a buggy update, then news headlines might read something like, “T-Mobile’s Cupcake turns out to be a dry Muffin” (or something more witty). Apple has a solid reputation of releasing stable updates, so T-Mobile has a high bar.

So, for the OTA updates, I can understand why T-Mobile seems to have shifted the release of Cupcake to the right 6 months.

Accept More Risk, Root your G1

I finally couldn’t wait any more for T-Mobile. Personally, I would prefer a 95% bug-less update now than a 99% bug-less update a month from now. But that’s me. Obviously, the potential risks in updating to a less-stable release of Android include data loss, wasted time, a dead G1, and missing important calls, SMSes, etc. I have waited long enough that I am betting that the process for rooting a G1 has been thoroughly tested and improved since it was first developed, so I gauge that risk at very low.

Using the above links, I found that rooting the G1 is very easy. I was prepared for some fancy commands and quick button pressing.

So I rooted my G1 and updated to the JesusFreke build of Android 1.5 (Cupcake). As you can see in the linked article, this includes the benefits of the Cupcake branch, plus multi-touch for the browser, an update app so you can always have the latest JF build, and (it seems) support for saving apps to your SD card and tethering.

So that’s that. It worked for me. Let me know if it has worked for you, and if so, what are your favorite builds?

Background

I have the T-Mobile G1, which runs the Android operating system.  My current firmware version is 1.1.  My current build number is:

kila-user 1.1 PLAT-RC33 126986 ota-rel-keys,release-keys

The firmware and version of software. Note that this screenshot is from the emulator on my Mac, not my actual G1.

Tasking Priority

The Good

1. Incoming calls “pause” whatever else I am doing, and I don’t have to unlock the phone.
2. Apps can’t “pull” you out of what you are currently doing… so if they have an update I can get to them when I want to.

The Wanted

Like the iPhone, the G1 (running Android) is not only a phone, but a small computer with internet access and the ability to run applications.  Here are a few wantings I have with regard to this multi-functionality:

1. Phone operations should have the highest priority (for my user experience).  I want the option to tell my G1 to maintain a dedicated allotment of resources (memory, proccessor capacity, etc) that are strictly for the phone functionality.
   • These features include incoming calls and outgoing calls at a minimum. I sometimes notice that it takes a few seconds for the incoming number/contact/or picture to show up on the screen.  Also, it takes a few seconds for my custom ring to kick in.  My first indication that there is an incoming call is that the phone begins to vibrate.  I want all functionality related to an incoming call to be as responsive as this vibration.
   • The contacts list is another core-mobile phone feature that can be slow at times.  Lower priority than the above.
2. Perhaps this could be expanded to allow the user to specify if any resources should be dedicated, and to what app or functionality this dedication should apply.
3. The Home screen should have a higher priority… even when my memory is near capacity.  I consider this to be a core phone function, since it is the main way of accessing all apps and functions.

User Interface

The Good

I like most things about the user interface.  Here are a few key likings:

1. Scroll speed is proportional to the speed at which I “flick” my finger.
   
2. The “long press” (press on something and hold your finger there as a sort of “right click”) works well and is timed well (not t0o short, not too long).
3. Notifications concept
4. The dialer buttons are well sized and spaced
   

   A screenshot of the main Android Dialer

The Wanted

1. To switch between apps, you can “long press” the home button.  This “long press” is too long!  by the time I hold that button, I can generally have gone to the Home screen and clicked on a shortcut.  I want a quicker way to navigate between apps!  Must only use buttons available when the keyboard is closed.
   

   Android's application switch screen, after you long press the Home button.

2. Trackball is jerky fast at some times, and slow as anything at others.  On web pages, it is hard to trackball to a link without overshooting or going in a slightly different direction (getting to the exact link you want).  On the other hand, in text fields it is extremely slow if you want to get the cursor at the correct spot.  I have to resort to touching the general area of the text field, and then slowly get there with trackball.  In short, improve the usability of the trackball!
3. Also with trackball, when you press the trackball it can act as a “click”, but sometimes when I click I inadvertently slightly move the ball – I guess -  and end up “clicking” on something below the link I intended to “click”.  Not sure how to solve that problem because it could be just my ability to use the trackball, and the distance from the “ball” to the clicking surface.
4. I want an option to use the “back” hardware button in a different way.  Currently, you can use this button to move back through windows (I think they are “views” in the software definition) of a single app.  Going back from the main screen of an App takes you to the home screen.  As is, this is a logical way to use this button.  But, I would like to have it be like the back button in a browser – and act like every single view on the phone is a page of my browser.  Actually, this is the case if you switch (using a long press on the Home button) from the Messaging app to, say, wpToGo; but not the case if you switch from the Messaging app to, say, a sub-menu of Settings or a sub-menu of Market.  I see the conflict here… but maybe there could be a “long press” of the back button that switches to the last app or view, and a short press of the back button does the default.
5. Sometimes I try to “flick” down the notifications bar, but I miss.
6. On screen keyboard.  There are a few experiments out there, such as a12keys, that have an on-screen keyboard, but its integration with the rest of Android is limited.
7. Visual Voice mail.

The App, Music

The Good

1. Music continues to play when changing focus to another app

The Wanted

1. There is no sorting between music and podcasts
2. I want to view music videos, too (the ones I have bought from iTunes)

Other Aspects

The Good

1. Multiple recipients for text messages.
2. Display of text messages as a conversation (like in Gmail)

The Wanted

1. When using Spanning Sync, my Apple Address Book addresses won’t be found.  That is, I have addresses in Address Book, and when they get synced to my G1, those addresses can be read but when you click on the address from the Contact information screen, you get the message’ “Your search for ‘blah blah’ did not match any locations.”  I think the problem is in the way Google and Apple store address information – Apple uses different fields for City, State, etc, while Google seems to just use one big field called Address.
2. Sometimes it seems like the Menu button doesn’t work the first time.  I don’t know why.

Other Comments?

Please let me know what you think about Android by leaving a comment.  Is there anything you really like? Is there anything you wish would be changed?

Better yet, post your wants to the Android development site.  I should do that, too.

Background

I use a Mac because it is much more stable than Windows.  Also, the open source community is well plugged into working with Macintosh, from what I can tell.

I usually don’t buy software, because in most cases a group of people have come up with a better, free and open source, solution.

I decided to shell out the $79 (which is a bargin) for Apple’s iWork ’08 because I hate using Microsoft Word for Mac, and I am not too fond of NeoOffice (I like the native feel of the iWork’s GUI, which is also found in software like OmniGraffle and Navicat).  As many others have pointed out, Keynote is great, and Pages is pretty good.

Why am I frustrated

I am frustrated because Numbers is slow and lacking in functionality.  I understand that it is only at Version 1.0.2 (at the time of this writing), but I still want more.

I am not trying to do anything fancy, just paste a few hundred cells of data and get some graphs.  Every time I try to do something with a graph, my CPU usage skyrockets and it takes me about 5 minutes to do something as simple as add another column of data to a chart.

I can live without some of the functionality found in Excel, because I don’t need most of the fancy statistical analysis every day.  What I do need is for Numbers to do what it can, well.

My recommendation to the developers (I know that they read this site nearly every day… [sarcasm]) is to tone down the CPU heavy graphical data selection, and just give me a text or simple menu way of manipulating graphs and charts.  Some added flexability with chart making would also greatly enhance the Numbers experience. For example, why is it so hard to get x-axis labels?  And why, if I do it wrong the first time, must I re-create the chart from scratch to get it to work properly?

At this stage in its life, Numbers seems to be working against the current Mac mantra: “Easy and intuitive”.

Begging the Developers

Please, if you can hear me, fix Numbers so that I can use it without pulling out my hair.  Until then, I will be running Software Update every hour…. hoping…

How about you? If you have this problem, please let me know about it so that I can feel better.