Hi Guillaume, there is really not enough information here to help you. The onNewIntent() and onRestoreInstanceState() methods do generally work, they are used in many places. You'll need to be more specific about what you are doing to be able to get help. It also can be useful to include the output of these commands with indications of where you are seeing the problem:
adb logcat adb logcat -b events In addition, you can use "adb dumpsys activity" to see the current state of the activity stack to try to diagnose what is going on in your application. On Aug 28, 6:42 am, Guillaume Perrot <[EMAIL PROTECTED]> wrote: > Another lifecycle problem: onRestoreInstanteState is never called when > I relaunch my activity after pressing HOME (and the onCreate is not > called so the activity hasn't been recreated). > > On Aug 28, 1:38 pm, Guillaume Perrot <[EMAIL PROTECTED]> wrote: > > > In M5 I used notifications with intents (with extra arguments) to > > handle special commands. > > If my activity was already started (the main activity of my > > application), onNewIntent was called. > > My activity has the singleTop launch mode manifest attribute. > > In v0.9, onNewIntent is not called anymore, how can I restore this > > behavior ? Is this a bug or am I doing something wrong in the new SDK > > version ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Announcing the new Android 0.9 SDK beta! http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
