My app is getting killed while I launch an external intent

by Timothy DeWees » Sat, 22 Aug 2009 10:10:46 GMT

Sponsored Links

I'm hoping for some help on ways to solve a problem.  From my
application, I launch an intent that returns a result I need to read
(Zebra Crossing).  But if the user takes a while to scan the barcode
(low light, wobbly hands, etc), my main intent is getting killed.
When the app re-launches, I'm not hitting the event for the intent

Is there some start parameter to tell me the app is being re-launched
and returning from a child intent?

Any suggestions on this would be helpful!

My app is getting killed while I launch an external intent

by Timothy DeWees » Tue, 22 Sep 2009 04:44:30 GMT

 It's not just what I need to remember, the other action is sending me
data which I get in onActionComplete.  Any thoughts?


Sponsored Links

Other Threads

1. AVD for Motorola Cliq?

Anything around?
In particular, exactly what do those buttons do and are we to assume
to use the DPAD in portrait mode the phone is turned 180 from what
you'd expect "normal" portrait mode to be (see the pic, you'll see
what I mean: I'm just guessing here but as a
developer would like to know how to handle this.
Do we need to code for a new orientation: keyboard closed portrait,
keyboard open portrait and landscape?

Android Academy:

2. Sometimes the running emulator is not found from within Eclipse?!


  when launching my app from within Eclipse, sometimes the running emulator
is found and displayed in the launch dialog, sometimes it isn't?! Killing
adb, the emulator and Eclipse usually helps ... until it happens again.

  Any idea why this is? I see this behavior since the launch of Android.

  I am running on Mac OS X. And it happened on Leopard as well as Snow




4. Autogrow ListView is not working

5. Akhirnya datang juga!

6. Point Sprite support

7. Default display unit px or dp?