Fwiw, cupcake will add a new field to PACKAGE_ADDED to tell you if this was due to an update, and allow this broadcast to be received by the app to restart itself.
On Tue, Mar 17, 2009 at 3:44 PM, daniel.benedykt <[email protected]>wrote: > > Hi > > I have the same problem. > As far as I know the only way is to set a Service to start after the > installation is done. Maybe you can put a service that runs once (not > really a service hehe) that it will be initiated after the > installation is complete, set up the alarms and end the service. > > Other thing you can do is to react to the > "android.permission.RECEIVE_BOOT_COMPLETED" so next time the user > reboots the phone you can re-register the alarms. > > Hope it helps. > > Daniel > > > On Mar 17, 7:27 pm, Michael Bollmann <[email protected]> > wrote: > > I read that the AlarmManager looses all registered intents if case the > > application > > that registered those intents is upgraded. > > > > What is the correct approach to re-register those intents considering > > the user > > does NOT start the application after upgrading it? > > > -- 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 -~----------~----~----~----~------~----~------~--~---
