All nice and well - if the API for AlarmManager supported persistent alarms.
Currently, if you update an application your alarms will go bye bye until the phone reboots - no? Requiring a reboot just to reset a few silly alarms seems quite excessive to me - and definitely prevents us from "taking full advantage of the platform". On 25 Feb, 04:58, Dianne Hackborn <[email protected]> wrote: > On Tue, Feb 24, 2009 at 3:38 PM, Peter Jeffe <[email protected]> wrote: > > There are many apps that aren't just simple foreground processes, and > > by limiting what developers can do in this way you're not allowing us > > to take full advantage of the platform. > > That seems quite an exaggeration to me. It's the difference between > automatically starting things up as soon as the .apk is downloaded, before > the user even has a chance to be told of those and launch it, vs. letting > the user go and start the app, that first time, when they want. How is this > not being able to take full advantage of the platform? > > -- > 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. 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 -~----------~----~----~----~------~----~------~--~---
