LunarLander.java, the Activity in Lunar Lander sample, doesn't
override onResume(). I don't know how this causes the system starts a
new instance, but that is the method that should wake up the first
instance after going to Home, so I think it should be related.
I'm testing similar scenarios when
FYI ... this problem occurs with the LunarLander example as well.
When I am not so crazed I will post some code that does a pretty good
job illustrating a (simpler || better || hopefully || somewhat)
optimized demo of running a SurfaceView. LL is OK, but it spawned a
few red herrings for me.
St
I figured it out (thanks to your request for the Manifest file, I started
digging).
Adding this to the Activity tag ...
android:launchMode="singleTask"
fixed the problem.
Thanks Mark!
i++
On Sun, Apr 5, 2009 at 12:17 PM, Mark Murphy wrote:
>
> Well, that manifest didn't seem out of the ordi
Well, that manifest didn't seem out of the ordinary. What I was looking
to see were any instructions to force a new copy of the activity to be
started.
FYI, you don't need android:enabled="true" in the element --
that's the default.
> What is also perplexing is that when onCreate is called (aft
Sure ...
http://schemas.android.com/apk/res/android";
package="us.quadrant2.surfacelooptest"
android:versionCode="1"
android:versionName="1.0.0">
What is also perplexing is that when
robotissues wrote:
> I am perplexed. I created an app using LunarLander example as its
> basis. It pauses and resumes in its correct state when the phone
> rings/hangs up or when leaving/returning via notification. However,
> when I click the "Home" button and then click the app's icon, it
> st
6 matches
Mail list logo