[G1 Android Development] sennister:
There have been a lot of questions posted about getting the update from RC29 to a newer approved build but for some reason people seem to dance around the answers. The original directions stated that you can either wait a while (up to 3 days from reading) or go to *Settings>About phone>System Updates* and manually to tell it to check for an update. I can tell you this much. If you are on RC29 don't bother going to *Settings>About phone>System Updates* because it isn't there until a later build. There is no way to do this from the Settings.

Then there is some mention of using Any Cut to maually create a shotcut to check for updates. It was a good start but really not all that helpful as there is no mention of how to get the program to crate said shortcut. So I dug into this so I could figure it out. Here is what you need to do to create the Any Cut shortcut to manually initiate the process for checking for an available OTA update.

Download the Any Cut app from the Market

Open the program

Select "New Shortcut"

Select "Activity"

Select "Device Info"

Now you can give it a custom name if you really would like to or just click "OK"

The new shortcut will be dropped on your home screen.

Don't bother trying this if you are not on RC29 as the menus are different. I tried to go back and do this while on 1.6 and I no longer see "Device Info". Not a big deal because you can go into the Settings as mentioned by the OP to do this anyhow.

So getting back to the Any Cut shortcut. From your Home screen locate the new shortcut created by Any Cut and open it. Scroll to the bottom of this new window. You will see a text box where you can enter something and a "Check for Updates" button. From my testing it didn't do any good to try and enter in anything in the Text box. I would click the "Check for Updates" button and in the lines above this button I could see the phone doing something but in the end it wouldn't trigger the phone to download anything. The behavoir was the same with something in the check box such as "RC33" or nothing in the box. It would come back with something stating that it successfuly checked though, so I knew it did something. It was late at night so I decided to call it a night and look at it again in the morning. The next morning I picked up the phone and there were no signs that the phone attempted to do an update yet. So I went into the shortcut that I made the night before. This time when I clicked on the "Check for Updates" button (nothing in the text box) it did something different and I could see in the information in this window that it found an update and it began to download it. I watched the progress and once it was complete I closed the screen and sat there waiting for it to do something.... Nothing.... I even rebooted the phone and still nothing. Eventually about 30 minutes passed from when I could see that the update was successfully downloaded and the phone poped up with a message stating that there was an update available to be applied. FINALLY!!! I told it to apply now and I was upgraded from version 1.0 to 1.6 which is the current build as of today for all unrooted phones.

So moral of the story is as follows:

1. Ignore what you have seen about being able to force an update from the settings in the phone. Sure it is there in 1.6 and probably 1.5 for that matter but right after you install RC29 (v1.0) it isn't going to be there so don't bother looking.

2. You can try to do the Any Cut but odds are you may be still stuck and have to wait a while. If nothing else it makes you feel like you are doing something because it gives you a button to push to start the process and can see if the phone is successfully checking for a OTA update on the update servers. Also the phone is setup to check periodically for updates from the OTA servers. This is a way to force that check to take place. I guess it is possible that when I was trying to manually check for the updates that the update system was down for maintenance. If others experience that they can get the update right away then great. Please post that information. For me I still had to wait several hours, about 8 from when I created the Any Cut shortcut and began forcing the check. Eventually my manual check did initiate the download.

3. In the end you may be stuck waiting a while to get the update. For me it was about 20 hours that I waited in all. Much of this time was spent hashing over all the posts in this thread and others trying to find a way to kickstart the process. Of course I have no way of knowing if doing Any cut sped up the process but it made me feel like I was actively doing something about it.

As for why I would want to do something crazy like go back to a unrooted phone. I was having some issues that I wanted to check and see if they were hardware related. I had Bluetooth issues with my car integration but not when paired with my laptop or my headset. My wife's phone (motorola and not a smart phone) had no issues pairing with the car. Since the car was new and I had only attempted to pair with the rooted version of my phone I had no way of knowing if the rooting was causing the problem. I spoke to some people that have the same car that I have and a G1 (unrooted) and they had no issues with the Bluetooth so it wasn't like it couldn't be done. Then my Home button stopped working. Oddly enough it works to wake my phone and when I needed it in the unrooting process. It just will not work when the phone is up and running. To make things even more strange with the home button thing, I unrooted to RC29 and the home button started working fine. When the phone got the OTA update to 1.6 the home button again died. Same functionality as when it was rooted. I spoke to T-Mobile Cust Service and they are sending me a replacement phone. I will be rooting the replacement once it gets here. I can understand that they cannot deny a warranty claim for a manufacture defect even if the phone is rooted. However this all began with the Bluetooth issues and in the rooting process I did fiddle with the radios. So it is possible that was causing the issue.

Hope this helps someone out there.