Wednesday, April 24, 2013

Re: [android-developers] Notifications and killed app

Change the notification intent to point to the first activity and add a flag to indicate you want to open the other activities (propagate through the activities).


On Wednesday, April 24, 2013 1:16:12 PM UTC+3, Larry Meadors wrote:
On Wed, Apr 24, 2013 at 1:01 AM, Piren <gpi...@gmail.com> wrote:
> The "swipe" thing has a funny way of working when you have a foreground
> service... everything in the app gets closed (all activities are gone)
> except for that service... that means that if you re-launch the app you need
> to figure out the "state" the app was before.
>
> in you case, display which files are being played and go back to showing the
> ui in "playing" mode.

Yeah, I expected the swipe to really kill everything - so I was
surprised that the service survived so persistently (a good thing).

The UI worked as expected now - the only thing I can think of that
would make it better is if it could somehow set up the activity stack
when launched from the notification. Right now it goes directly to my
MusicPlayerActivity and back exits. If I could get it to go to
MusicPlayerActivity with the back stack looking like MainActivity >
TitleDetailActivity > MusicPlayerActivity, it would be perfect.

This'll do for 1.0, however...so close... :)

Thanks for your help, guys.

Larry

--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

No comments:

Post a Comment