Prevent new activity instance after clicking on notification

Question

Hello,

application (non-wanted) behavior -

1. application is started, some text is put into text-box and notification is created through button action.
2. user "clicks" the home button, application is "minimized", notification is available in bar
3. user selects the notification and the application is "maximized"

BUT - instead of the original instance, new instance is started (e.g. in the newest instance is missing the original text; when the latest instance is closed there is still the original instance with original text ) .

the code of the notification method

Context context = getApplicationContext();
    CharSequence contentTitle = "someText1";
    CharSequence contentText = "someText2";
    Intent notifyIntent = new Intent(Intent.ACTION_MAIN);
    notifyIntent.setClass(getApplicationContext(), RadioStream.class);
    PendingIntent intent = 
       PendingIntent.getActivity(RadioStream.this, 0, notifyIntent, 0);

    notifyDetails.setLatestEventInfo(context, contentTitle, contentText, intent);
    mNotificationManager.notify(SIMPLE_NOTFICATION_ID, notifyDetails);

i have also in the manifest xml file following tag

android:launchMode="singleTask"

but it is still the same... The main problem is double/triple initialization of the application, i know that there are other means to preserve the values in resumed applications. Also it is needed that the applications stays running in background as the main functionality is the streaming of internet radio.

What is missing in the code ? What kind of information from my side is missing for to troubleshoot the issue ?

Thanks!

Dav

Answer 1

Hi,

What you refer as "application" is most probably an Activity. To avoid re-crating it when bringing up to front, use

android:launchMode="singleTop"

To have some code running background, you need to realize it as Service

Answer 2

Another option is to use setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP | Intent.FLAG_ACTIVITY_SINGLE_TOP) on your Intent.

Answer 3

reimplemented as service - everything works as expected