I got the same behavior with the Tabs2 APIDemo source, which doesn't use Intents, but rather a TabContentFactory.
Until the app gets an onDestroy, it seems to add new instances into the call stack, instead of reactivating the current one. After it gets an onDestroy, future launches work fine. So: 1. Launch app, hit home, launch app, hit home, launch app, hit home, launch app. 2. Now start hitting the back button. For as many times as you launched the app, hitting the back button will display an old app instead of exiting. 3. Continue hitting back button until the app gets an onDestroy() (should 4 times in the example above) 3. Repeat from 1. Notice the change of behavior. At 2, a single back button will exit the app Is there some bit that needs to be flipped after a launch? Is this just an emulator thing? Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
