Hi, I'm trying to understand what happens under the covers when *end- users* upgrade their device firmware from Android ver. X to X+1 (regardless of whether they initiate the action, or their carrier sends the update OTA).
I'm working on an Android based device, and I need to understand how this is supposed to work. A new build of Android contains system.img and userdata.img (among other files). The system.img file is read- only, so replacing the user's existing copy shouldn't result in any data loss. Not so with userdata.img; overwriting this file with a newer version would destroy all of an end-users application data (wouldn't it?). Could it be that userdata.img never contains any data that needs to be updated during a FW upgrade, and so isn't overwritten? Or is there some process that merges changes into /data? Surely there is a procedure envisioned for upgrading FW for Android- based devices without nuking users' address books, and other private data. Unfortunately, Googling for this information yields only pages containing specific hacker-level instructions (e.g. adb commands); I can't find any mention of this topic online, or in the documentation. Does anyone know how this is supposed to work, or where this is documented? Thanks very much in advance. -Mr INTJ --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
