Clarification on the Android Froyo Update
*update* A few members of the Android team @ Google posted on Twitter that Android 2.2 has been opened up to a very limited test group and that an OTA update should be available very soon.
Saturday I posted a link online to the Android 2.2 froyo update found on Google’s servers where all OTA update files live. The filename was tipped off by a user that received this update over the air on his Nexus One device. Having the filename for the update, manually downloading the file from the originating server was very simple. At no point during this process did Google actually confirm that Android 2.2 was being sent to consumer devices. A number of theories have been presented as to what has happened, so I’ll present information I collected with a conversation I had with someone at Google. At the time of my conversation it seemed no one was actually sure what happened or how the OTA was received by someone outside of Google. This wasn’t an attempt to push the press the update early, it seems it is more likely that in trying to push the update internally to Google employees there were a few imei numbers in the push that were not supposed to be there. It also could have been leaked by someone who was supposed to get update as well. The answer to the question as far as I know has not been answered.
The FRF50 update could possibly be the final build release to the public but it also may not be.I am trying to find out if a zip file will be provided to update from FRF50 to the actual 2.2 release if that is indeed the case. At this point in time that is something that really cannot be answered because it may in fact not be an issue.
The link to the OTA update was removed because it is not supposed to be circulating in the public. Google has not made a formal announcement relating to the removal of the OTA update from their servers either.
Another important note noticed by a few users last night, the Android 2.2 FRF50 update is currently not able to see copy-protected applications in the Android Market. This has actually been an issue with the Market previously with officially released phones so a solution to this probably won’t require an update, but this hasn’t been confirmed.
So to summarize, if you still wish to install the Android 2.2 update it is absolutely at your own risk. No one other than yourself will assume responsibility for any issues as a result of you updating your phone. Questions or comments, feel free to discuss them here.