On Monday 21 October 2013 17:46:06 Jamie Strandboge wrote: > Recently someone asked me about adding an apparmor policy group for qtpowerd > so that apps could stop application lifecycle from suspending the app. I > said to file a bug and I'd look at it because I was thinking this seemed > reasonable for a number of reasons (which I'll list below). We were told > that apps should not generally have this permission. This particular case > was a 3rd party music player and in this case it was easy enough to punt > and say that 3rd party music players should use the upcoming media service. > However... > > I think we may be too strict on this. Consider the following apps: > * a metronome app for musicians to practice to (2 are in the app store now) > * a white noise app to help people sleep (1 in the store) > * a navigation app that speaks the directions to you as you drive (none in > the app store AFAIK, but this would be a wonderful addition) > * internet radio apps (there are at least 2 in the store) > * a 3rd party alarm clock (perhaps the API that the core app clock uses is > sufficient-- I haven't checked)
* I'm going to release Xbmcremote (http://notyetthere.org/?page_id=17) later this week. It is affected too by this. The feature to pause the running movie or lower the music's volume on incoming phone calls is disabled for Ubuntu. -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
