s/chrooted/rooted/g On Jul 17, 2012 3:12 PM, "Francisco M. Marzoa Alonso" <[email protected]> wrote:
> You simply cannot do that without a chrooted device. > > Each app runs within its own sandbox and one application cannot do nothing > on other app. > On Jul 14, 2012 8:32 PM, "Jordi Sayeras" <[email protected]> wrote: > >> Hi, >> >> >> I've been searching about this topic but I haven't found a clear solution >> yet. As far as I know, you can specify different *protectionLevel* in >> your *AndroidManifest.xml*, those permissions allow other applications >> to interact with the one you are developing. As an example, imagine that I >> want to kill a processes, that is not mine (from another package) or that I >> want to install a driver I've developed. In both cases the problem is the >> same, those things need to be run as a system / root. How can I develop >> programs that require system / root permissions, do I need an special >> license? >> >> >> >> *Note:* Please, note that granting the permission: >> >> >> >> * <uses-permission >> android:name="android.permission.KILL_BACKGROUND_PROCESSES"/>* >> >> >> >> Using *android:sharedUserId="android.uid.system"* does not work either. >> >> >> >> Also, consider that I cannot ask the users to have their mobiles "rooted". >> >> >> >> Thanks in advance. >> >> >> >> Jordi. >> >> -- >> 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 > > -- 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
