Is there any way to install an application with access to "signature" protection level permissions without it being embedded? The question really comes down to the "signature" permission, from the documentation: "A permission that the system grants only if the requesting application is signed with the same certificate as the application that declared the permission."
The mentioned certificate comes from a OEM? If this is the case, then signing an application with that certificate and installing it (via download, market, etc..) will allow it to have access to "signature" permissions ? Regards, Rúben On Jan 21, 6:37 pm, Ryan Baker <gtrm...@gmail.com> wrote: > Hi Dianne, > > I am also developing on an OEM ROM and am trying to test the updating > functionality. Given that you have said updating a pre-loaded app is > possible, I want to test this on my app and verify it for my > colleagues. To this end, I have installed an app using ADB and > uploaded the same app with a higher version number (not the string > value, but the integer field) to market. > > I get no pushed notification saying there is anupdateavailable for > my app. Under Downloads tab in Market, the app does not show as > installed. When browsing the Market, the app shows as installed but > does not say "updateavailable". When I browse to the application and > touch install, however, I do receive an "overwrite previous version" > warning. > > My question is, will apps installed with ADP receive updates similar > to those added to the pre-built ROM? If not, under what conditions > will apps be considered preloaded by the market and thus capable of > receiving pushedupdatenotices? I am hopeful that preloaded apps will > receive pushed notifications when updates become available, just as > every other app does. > > Or perhaps I misunderstand and pushedupdatenotification is not > possible with preloaded applications. > > Thanks, > -Ryan > > On Dec 17 2009, 9:21 pm, Dianne Hackborn <hack...@android.com> wrote: > > > > > As of 1.6 (and possibly 1.5) you can definitelyupdatethrough the market. > > As long as your updated app is signed with the same cert, when it is > > installed thesystemwill put the new one in /data and ignore the old one in > > /system. > > > Be sure you set your version code (versionName is ignored) so that the newer > > one in market has a higher number; thesystemalso takes care of things like > > checking if the one in /systemhas a version code >= the one in /data and > > deleting the one in /data during boot if that is the case. This allows an > > OTAupdateto deliver a newer version of the app and correctly handle things > > if a marketupdatehad been installed. > > > On Thu, Dec 17, 2009 at 5:01 PM, John Seghers <jsegh...@cequint.com> wrote: > > > I had assumed that if an application was preloaded it could not be > > > updated via the marketplace. My reasoning being: > > > 1) A preloaded application is part of the OEM's ROM image. > > > 2) The APK for the app would therefore be on the /systempartition and > > > thus be read-only > > > 3) Therefore the only way toupdatesuch an application would be via a > > > fullupdate--which would only happen on maintenance releases or OS > > > upgrades. > > > > We are building an app that will be preloaded. In our initial > > > discussions with the OEM, they have also indicated that it would not > > > be upgradable outside of #3 above. > > > > However, I just had Google Maps present anupdatethrough the Android > > > Market. This seems to violate the above assumptions in one or more > > > ways. > > > > How does one preload an application and yet still allow it to be > > > upgraded via the Android Market? > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Android Developers" group. > > > To post to this group, send email to android-developers@googlegroups.com > > > To unsubscribe from this group, send email to > > > android-developers+unsubscr...@googlegroups.com<android-developers%2Bunsubs > > > cr...@googlegroups.com> > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > Note: please don't send private questions to me, as I don't have time to > > provide private support, and so won't reply to such e-mails. All such > > questions should be posted on public forums, where I and others can see and > > answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
