I can't answer your question specifically, but my approach to it would be to learn how full system builds are done, and what is put into an OTA (Over the Air) package. I've brushed up against this as I've been doing full system builds within a CyanogenMod sandbox, but the same information should make itself apparent in a full vanilla build of Android. The part I'm blank on is how the build package is staged so that the phone knows it needs to go pick it up. Some googling should solve that. I imagine it's a side-feature of one of the required apps your mobile service provider pre-installs on your phone. One the package is downloaded, it's a simple job of unpacking and rebooting. Existing app-data can be preserved, so the unpacking process is an additive overlay.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
