As I've said, it would be reasonable to have a facility for power manager kind of stuff to get involved in this. This setting is not the way. And it NEVER was. Do you realize what we are seeing here? People complaining that their app can no longer turn on the setting whenever it wants, and people complaining that their power manager or whatever app can longer change the setting. Do you see that, put these together under one boolean setting, and it DOES NOT WORK. Even ignoring that this setting is -really- for the USER to override anything the applications on their device do.
If you care enough about this, contribute a patch to the platform to add a facility for power manager kinds of apps to do what they want. I expect I will implement such a thing at some point, but it is currently a much lower priority than many other things so I don't know when that would be. So if you want to help out, we can talk on android-framework about the API and UI for such a thing. If you just want to complain and not help anyone, feel free to continue here. On Sun, May 3, 2009 at 5:08 AM, Disconnect <[email protected]> wrote: > My argument is that, plain and simply, the default settings apps were > inadequate for many users. Having been forced back to using them, those > users are objecting, and I agree completely. > > It is not just a case of "I disabled GPS and now CrazyAlsFriendFinder > turned it on and drained my battery." Nobody is arguing that that is a good > thing. (Well.. maybe Crazy Al is. But he's crazy.) There is also the case of > "At 3:15, if Locale cannot find MyWorkWifi, I want it to turn on GPS and see > where I am. If I'm home, turn off 3g." Or the much simpler "I want to use > ToggleSettings to control all my toggles in one place, from a dropdown." > > This could be at least mitigated by an additional, simpler intent for each > disabled permission: "Turn On?" (Similar to the mount/unmount prompt.) That > saves some use cases such as manual settings change apps (and judging by the > number of them in the market, users do NOT like the default menus.) And it > gets closer to the "all apps are created equal" basis of Android. > > A later addition to that prompt could allow for "always permit this > application to control this setting". (And maybe add a notification entry > every time it is changed without prompting..?) Again - you block > underhanded/unexpected apps, but you still let the user use the apps THEY > want to use to control THEIR phone. And if you are worried about it, wipe > out the always-allow perms when an app is upgraded. > > > On Sun, May 3, 2009 at 7:02 AM, Mike Hearn <[email protected]>wrote: > >> >> > Clearly. Let me rephrase - while changing settings (Airplane mode), >> > user navigates through Settings and disables GPS as well. >> >> So your argument is that if the user has explicitly disabled the GPS >> function, your app should be able to turn it on without asking them? >> This is exactly why the change was made! >> >> > > > > -- Dianne Hackborn Android framework engineer [email protected] 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 [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 -~----------~----~----~----~------~----~------~--~---
