On Tue, Nov 17, 2009 at 11:36 AM, jotobjects <[email protected]> wrote:
> On Oct 15, 3:07 pm, Dianne Hackborn <[email protected]> wrote: > > What these programs are doing is using the API that is tended to force > stop > > -everything- about the application: stop all services, cancel all alarms, > > remove all notifications, etc. This is all working as intended, the apps > > are just abusing this API to cause things to happen that you probably > don't > > want to have done. > > Does that mean Jason's solution will not work when this happens? > Sorry I don't know what Jason's solution is. > Is there a planned fix for this so it can't happen or at least > requires an explicit dangerous permission? > I will probably make this API a no-op, since it violates the principle of one app not being able to break another app, and has quickly become confused. It wouldn't make sense to require a dangerous permission, because nobody would understand what that permission means and we'd still have these apps breaking other apps. -- 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
