On Wed, Aug 1, 2012 at 2:57 AM, Dan <dan.schm...@gmail.com> wrote: > > > On Tuesday, July 31, 2012 11:59:45 AM UTC-7, Kristopher Micinski wrote: >> >> This goes in the category of "apps modifying the system." >> >> Your app shouldn't be able to modify the system. >> ................................... > > > > Why? If I want an app that turns off the data connection on a timer > function or reading location manager information or I just don't like > digging through a settings menu, why should I be at the mercy of an > OEM's implementation? > > And if turning off the APN is "not good" why are there APIs that let > you catch the NEW_OUTGOING_CALL intent and consume it so > the call isn't dialed, or the incoming SMS messages, or holding a > wake lock.
Because Android doesn't work like that.. Theoretically, one app shouldn't be able to affect the usability of other apps. In this case, it might not be so bad, but there is also a specific permission that goes with this (turn on / off gps), not for all system related things. So in the general case of modifying the system, your app shouldn't be able to modify system wide things unless it's part of the firmware, and the ways around doing so are slowly being removed. kris -- 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
