On Jan 5, 10:19 pm, Dianne Hackborn <[email protected]> wrote: > On Wed, Jan 5, 2011 at 7:07 PM, DulcetTone <[email protected]> wrote: > > Is there no means by which you can tell whether a package installed on > > the phone is burned in with the firmware (and hence immutable) versus > > one that can be updated? > > ApplicationInfo.FLAG_SYSTEM. > > This doesn't really mean it is immutable; you can install an update to it if > it is signed with the same cert (though the update is placed on the data > partition like other third party apps, since /system is read only).
Ok... is this update then read and used instead of the original / system copy? I assume so. > > > On a similar line, why does Google ever put apps on the Market with > > the same signature by which they are burned into some phones? It > > stunts updating terribly. Indeed, why burn any apps on the phone as > > opposed to make them super-easy to find in a dynamic manner? > > Huh? You can update built-in apps, as per above. This is how maps updates > have been delivered for a long time, as well as Market updates (which you > aren't generally aware of), more recently Gmail updates, etc. > This is not the case with my phones. I suppose this must be a consequence of the fact that their firmware was written to from a burn station in Google's own offices here in Cambridge. I cannot, for instance, update Google Maps -- it downloads the update and fails to install every time. I assumed the issue extended to other users' phones. tone -- 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
