Killing a process doesn't get rid of its current state. The next time you go to it, it will be launched with whatever the last activity was.
On Wed, Aug 19, 2009 at 9:40 AM, bkbonner <[email protected]> wrote: > > Our application is defined to launch a SplashScreenActivity from > Intent { action=android.intent.action.MAIN categories= > {android.intent.category.LAUNCHER} . After the SplashScreenActivity > does its work, it launches another intent to launch MainMenuActivity > and finish() is called on SplashScreenActivity. > > When we run our app for the first time on our phone, the > SplashScreenActivity launches OK, and correctly launches the > MainMenuActivity. > > However, if we kill the app using TaskKiller, LOGCAT indicates that > the application has been killed. I can't debug the app, because > launching it from eclipse with the debugger makes it work OK, because > it reinstalls the app. Perhaps there is a way to launch the app > without reinstalling it? > > Here is the Log of us killing our app. > > 08-18 22:58:59.003: INFO/ActivityManager(56): Displayed activity > com.tni.TasKiller/.TasKiller?: 1737 ms > 08-18 22:59:00.723: DEBUG/ActivityManager(56): Uninstalling process > com.qbir.android > 08-18 22:59:00.723: DEBUG/ActivityManager(56): Force removing > process ProcessRecord?{43588718 15204:com.qbir.android/10061} > (com.qbir.android/10061) > 08-18 22:59:00.723: INFO/Process(56): Sending signal. PID: 15204 > SIG: 9 > 08-18 22:59:00.733: DEBUG/ActivityManager(56): Force finishing > activity com.qbir.android/.activity.MainMenuActivity? > 08-18 22:59:00.743: WARN/ActivityManager(56): Activity HistoryRecord? > {43596f98 {com.qbir.android/ > com.qbir.android.activity.MainMenuActivity?}} being finished, but not > in LRU list > 08-18 22:59:00.763: WARN/ResourceType(56): No package identifier > when getting value for resource number 0x7f060001 > 08-18 22:59:00.793: INFO/WindowManager(56): WIN DEATH: Window > {43650590 com.qbir.android/ > com.qbir.android.activity.MainMenuActivity? paused=true} > 08-18 22:59:00.793: DEBUG/ActivityManager(56): Received spurious > death notification for thread android.os.binderpr...@43?3d8798 > > > When we launch the application again, the LOG messages for > SplashScreenActivity are not logged and it looks from LOGCAT that > Android is launching the MainMenuActivity instead. Here is the log: > > 08-18 22:59:02.233: INFO/ActivityManager(56): Starting activity: > Intent { action=android.intent.action.MAIN categories= > {android.intent.category.HOME} flags=0x10200000 comp= > {com.android.launcher/com.android.launcher.Launcher} } > 08-18 22:59:02.373: WARN/InputManagerService(56): Starting input on > non-focused client com.android.internal.view.IInputMethodClient$Stub > $pr...@4365dd48 (uid=10121 pid=15255) > 08-18 22:59:08.493: INFO/ActivityManager(56): Starting activity: > Intent { action=android.intent.action.MAIN categories= > {android.intent.category.LAUNCHER} flags=0x10200000 comp= > {com.qbir.android/com.qbir.android.activity.MainMenuActivity?} } > 08-18 22:59:08.593: INFO/ActivityManager(56): Start proc > com.qbir.android for activity > com.qbir.android/.activity.MainMenuActivity?: pid=15262 uid=10061 gids= > {1006, 3003} > 08-18 22:59:08.653: INFO/jdwp(15262): received file descriptor 13 > from ADB > > Can someone Romaine, Diane help us understand what is happening? We > saw this happening because some variables are initialized in > SplashScreenActivity that aren't available with MainMenuActivity and > we were getting NPEs. > > > -- 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, and so won't reply to such e-mails. 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 -~----------~----~----~----~------~----~------~--~---
