Activity stack ordering problem when launching application from Android app installer and from Home screen?

Added the answer that antonyt provided: Override protected void onCreate(Bundle savedInstanceState) { super. OnCreate(savedInstanceState); if ((getIntent().getFlags() & Intent. FLAG_ACTIVITY_BROUGHT_TO_FRONT)!

= 0) { // Activity was brought to front and not created, // Thus finishing this will get us to the last viewed activity finish(); return; } // Regular activity creation code... }.

Added the answer that antonyt provided: @Override protected void onCreate(Bundle savedInstanceState) { super. OnCreate(savedInstanceState); if ((getIntent().getFlags() & Intent. FLAG_ACTIVITY_BROUGHT_TO_FRONT)!

= 0) { // Activity was brought to front and not created, // Thus finishing this will get us to the last viewed activity finish(); return; } // Regular activity creation code... }.

The underlying issue I believe is that the Intents used are different between the launcher and the installer. In so far as you are getting different Intent flags you are going to get different launch behavior. You can muck with the launch modes and you may be able to get a consistent result but fundamentally those different Intents will produce different results.

Your fix (or something like this) is probably your best bet.

This seems like a fundamental problem that many apps would find undesirable - indeed, I have seen the Android Facebook app exhibit this behaviour - and so it is quite disappointing that the above workaround (or similar) is all we can do. – antonyt Jun 18 at 17:31 It could be considered a behavior defect: on the other hand, it does allow you to differentiate between Installer launches and App icon launches, which you could use to launch a Welcome screen that only shows up when someone clicks on the Installer run button. Now that I think about it I might actually use that :) – Femi Jun 18 at 17:53 @Femi However, keep in mind that not everybody will start the app for the first time via the Install & Run option, and they may still appreciate a greeting when they get around to it.

:) – Glendon Trullinger Jun 18 at 18:47 Very true: I already have logic in my apps to check the first run, this is just one more hook. – Femi Jun 18 at 18:56 I have tried to detect whether or not the category is set in the intent used to start the activity (it usually isn't set by the installer, only the launcher) - if it is missing I add the category and the flag and then restart (startActivity()/finish()) with this modified intent. The bad behaviour still occurs even though the intents now seem to match.Do you have any thoughts on this?

– antonyt Jun 18 at 19:34.

Your problem is likely rooted in the fact that App installer doesn't use the LAUNCHER category, as does the launcher. This bug has been documented elsewhere: App always starts fresh from root activity instead of resuming background state (Known Bug).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.