Dianne,
Any update on this? As of ICS, any app opened via installer suffers from
this.
See http://code.google.com/p/android/issues/detail?id=26658 for instance.
-Jonas
On Saturday, December 5, 2009 4:09:56 AM UTC+1, Mark Wyszomierski wrote:
Hi Dianne,
To follow up on this, the package
Hi Dianne,
To follow up on this, the package installer seems to launch apps in a
similar way Eclipse does, so, the same thing happens here as launching
from Eclipse:
// From eclipse:
Starting activity: Intent { flags=0x1000 comp={com.test.testapp/
com.test.testapp.ActivityMain} }
// From
I don't know if it's monkey or not - it looks like it's just this
install (I'm sure it's the most recent SDK) - I can reproduce this odd
behavior on there. On my other machine, and my test phone, looks like
the default behavior is correct (with the same test apps and same SDK
updates). Thanks for
I may just be misinterpreting what I'm seeing through DDMS actually.
When I run my app, I have three activities, A, B, C. In the DDMS app
list, I see my app listed like:
com.test.myapp
if I select it, and hit the Stop button, it will be killed, but then
replaced by a new instance
I would have mentioned this issue, but you seemed to be very clear that you
were launching from an icon in home both times. :}
Anyway, I am pretty sure this has been fixed in the tool, though I don't
know if that fix is in the current release.
On Wed, Dec 2, 2009 at 8:02 PM, Mark Wyszomierski
Oh I definitely wasn't precise about the launch method, sorry about
that! I definitely didn't think the launch method could have anything
to do with it, I was trying all sorts of launch modes, thinking maybe
that's what the problem was,
Thanks
On Dec 2, 11:57 pm, Dianne Hackborn
I'm seeing the same behavior. Going back to the home screen, then
returning to the process clears everything back to the root.
On Nov 16, 12:42 am, pink 444 pnk...@gmail.com wrote:
Hi all,
I have a task,which is created when an activity with
singleTask launch mode is activated.
Try looking at the event log to see if/why activities are being finished --
adb logcat -b events
Try looking at the activity manager state to see what is going on with your
activities -- adb shell dumpsys activity
Oh and also -- first off don't use singleTask. Do you really know what it
is
Hi Dianne,
I guess I'm not understanding the default process creation method.
Using a new project, with two activities, A and B (both have no custom
flags set in the manifest, and Activity A is set as MAIN and
LAUNCHER):
1) Launch the app from the app drawer
2) Have activity A start activity B.
On Tue, Dec 1, 2009 at 1:46 PM, Mark Wyszomierski mar...@gmail.com wrote:
I guess I'm not understanding the default process creation method.
Fwiw, what we are talking about has absolutely nothing to do with processes.
Please make sure you read this starting at Activities and Tasks:
Hi Dianne,
The default behavior is what I'm going for - but I'm just not seeing
that - I made this small test app - it just has two activities. I
start the app from the app tray. Then have the first activity launch
the second activity. I hit the home button to put the app in the
background. When
I don't know what you are doing. If you try one of the sample apps like
ApiDemos you will see this works fine.
On Tue, Dec 1, 2009 at 4:18 PM, Mark Wyszomierski mar...@gmail.com wrote:
Hi Dianne,
The default behavior is what I'm going for - but I'm just not seeing
that - I made this small
Ok so the sample app code above should be producing the default
behavior though, right? This is happening on a mac running 1.5. I did
a fresh install of the SDK and the test app on a windows machine here,
and it works as you described on that machine (always resumes instance
if running in
Monkey may be doing odd things. Tasks are matched by intent, so if you
build different intents you will be launching different tasks.
On Tue, Dec 1, 2009 at 5:33 PM, Mark Wyszomierski mar...@gmail.com wrote:
Ok so the sample app code above should be producing the default
behavior though,
14 matches
Mail list logo
