I'm trying to get a handle on the onXXX() flow, but am not sure if what I'm seeing is by-design, or is an artifact of repeated debugging sessions on the emulator.
android:launchMode="singleInstance" The app extends TabActivity, has a few tabs whose content is set via new Intent, but no heavy application work is being done yet. The question is about relaunching after pressing the home button: Launch from icon: onCreate, onStart, onResume Home button: onPause, onStop Relaunch: <sometimes> onStart, onResume <othertimes> onCreate, onStart, onResume In the cases where the relaunch starts with onCreate, pressing the "back arrow" on the emulator appears to bring a different instance of my application to the front. The only thing that I can figure out on why I'd get the different relaunch flows, is that I'm initially launching the app from Eclipse, making a little change, launching from Eclipse again, repeat, and this is actually creating new instance of my app. But I'm just guessing this matters, I have no idea, as just doing 'launch from eclipse, home key, relaunch from android icon' also has shown the 'onCreate, onStart, onResume' path. Any ideas on why the different relaunch flows? 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 -~----------~----~----~----~------~----~------~--~---
