HOME/LAUNCHER activity messes up activity stack

Question

We are developing a home screen replacement app (a kind of launcher), so our home activity is defined as follows:

<activity android:name="Home"
        ...
        android:launchMode="singleInstance"
        android:stateNotNeeded="true">
    <intent-filter>
        <action android:name="android.intent.action.MAIN" />
        <category android:name="android.intent.category.HOME"/>
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.LAUNCHER" />
    </intent-filter>
</activity>

(see Use my own Android app/apk as launcher/Home Screen Replacement)

This works great, except for the following scenario:

User is in Home activity
User presses a button to go to activity A
User presses the home button (hardware device button), so Home activity is shown again
User presses a button to go to activity B
User presses the back button

At this point, activity A is shown again.

However, I expect the application to show the home activity. After all, the user went from the home activity to activity B.

What are we doing wrong?

How to do that? The home button is standard Android functionality.. — Jonas Sourlier, Aug 06 '14 at 08:41
what do you mean with home button ? hardware device button or a button in UI that redirects the user to home activity of your application ? — elmorabea, Aug 06 '14 at 08:45
I mean the hardware device button. It leads the user back to our Home activity, since it is the one registered as the device home screen (launcher) — Jonas Sourlier, Aug 06 '14 at 08:47

score 1 · Accepted Answer · answered Aug 22 '14 at 12:20

1

Switching to android:launchMode="singleTask" solved the problem.

answered Aug 22 '14 at 12:20

Jonas Sourlier

13,684
16
77
148

HOME/LAUNCHER activity messes up activity stack

1 Answers1