Hopefully someone can help me figure out, if not a solution, at least an explanation for a behaviour.
The Problem:
On some devices, pressing the launcher icon results in the current task being resumed, on others it results in the initial launch intent being fired (effectively restarting the app). Why does this happen?
The Detail:
When you press the “Launcher Icon” the app starts normally – That is, I assume, an Intent is launched with the name of your first Activity with the action android.intent.action.MAIN and the category android.intent.category.LAUNCHER. This can’t always be the case however:
On the majority of devices, if you press the launcher icon after the app is already running, the currently running Activity in that process is resumed (NOT the initial Activity). It resumes in the same way as if you had selected it from the “Recent Tasks” in the OS menu. This is the behaviour I want on all devices.
However, on selected other devices different behaviour occurs:
-
On the Motorola Xoom, when you press the launcher icon, the App will always start the initial launch
Activityregardless of what is currently running. I assume that the launcher icons always start the “LAUNCHER” intent. -
On the Samsung Tab 2, when you press the launcher icon, if you have just installed the app, it will always launch the initial
Activity(Same as the Xoom) – however, after you restart the device after the install, the launcher icon will instead resume the app. I assume that these devices add “installed apps” into a lookup table on device startup which allow the launcher icons to correctly resume running tasks?
I’ve read many answer that sound similar to my problem but simply adding android:alwaysRetainTaskState="true" or using launchMode="singleTop" to the Activity are not the answer.
Edit:
After the most recent launch of this app, we find that this behaviour has begun to occur on all devices after the first restart. Which seems crazy to me but looking through the restart process, I can’t actually find what’s going wrong.