On Thu, Jan 8, 2009 at 3:45 AM, Steff <[email protected]> wrote: > > > For our solution, you will also need to use > > "android.permission.READ_PHONE_STATE" to be able to handle forward > locking. > > We require this permission on SAM as well. > > Ohhh, I was hoping that it would be enough to give SAM the permission. > Why should the installed app (my app for instance) need the permission > as well?
SAM itself sits pretty high up the stack, and external to the core platform. so could never be a DRM agent. SAM just passes the application to the Android installer, after that it has no control of the application. Since the app directory is wide open, you will need to have something embedded in the app itself to prevent forwarding. The mistake I made was in assuming that this app directory was actually protected, with all the security Google talks about, this seemed like a no-brainer. Shane --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
