On Mar 2, 5:22 am, Neha nehas...@gmail.com wrote:
I have tried launching OtherActivity from SingleTaskActivity in both
these ways:
Intent explicitIntent = new Intent(this, OtherActivity.class);
explicitIntent.setComponent(new ComponentName(this,
OtherActivity.class));
Thanks a lot for your reply!
I'm seeing the same behavior when I launch my second Activity (say B)
by providing the component name or by using an intent-filter (custom
category). In both cases, Activity B is popped from the stack after
returning from HOME.
My AndroidManifest.xml looks like this:
Hi,
Does anyone have any updates on this issue? I'm facing the same
problem with my activity when launchMode=singleTask.
- Launcher - Activity A (singleTask) - Activity B (standard)
- Press HOME
- Long-press HOME or go to Launcher
- Activity A (B's onDestroy called)
adb shell dumpsys
There was another thread about this recently. This message summarizes
the behavior with singleTask
http://groups.google.com/group/android-developers/msg/471bef9e235f6c65
In short, with launchMode=singleTask the behavior after re-visiting
Home is different depending on whether the activity at
When you say launch do you mean launching from Eclipse? If so, there is a
bug in older SDKs where this would use the wrong intent so when you later
launch it from the launcher you would get a new task.
You can use adb shell dumpsys activity to see the current state of the
activity stack at
I'm facing same issue. Did you got any fix or work around for this ?
On Mar 26, 6:55 pm, jseghers jsegh...@cequint.com wrote:
The code that starts the .About activity is:
protected void startAbout()
{
Intent aIntent = new Intent(this, About.class);
The code that starts the .About activity is:
protected void startAbout()
{
Intent aIntent = new Intent(this, About.class);
startActivity(aIntent);
}
The Manifest entries for .UserLaunch and .About are in my original
post.
The intent that returns the task to the front
You can do adb logcat -b events to see the event log which will include a
line the activity manager prints when finishing an activity, with the reason
why it is doing it.
On Tue, Mar 24, 2009 at 7:24 PM, jseghers jsegh...@cequint.com wrote:
I am just starting on an Android app and I am puzzled
Thank you for your reply!
I am seeing am_task_to_front followed by am_finish_activity.
I found the event-log-tags file and apparently the reason is clear.
What is not clear to me though is why the activity manager thinks it
should clear the the task.
The relevant lines of the log are:
That means you are using some CLEAR_TOP or finish flag in an intent or in
the manifest. Or possibly it has been 30 minutes since the app was last
launched, in which case the system will restart it automatically.
On Wed, Mar 25, 2009 at 11:12 AM, jseghers jsegh...@cequint.com wrote:
Thank you
10 matches
Mail list logo
