@Sauray ... I did not think of that. I guess my question would be... since after the player is launched they are now actually outside of my app, do I even have control over the back button at that point?
@Chris Stratton ... It's looking like I will have to build my own... which is fine. Part of me wanted to do so anyway since it seems to be the more accepted way to do things. I was more trying to use the default player b/c I thought it would be the simpler way to do things so I could get the app into the hands of those that are going to be beta testing it. For my second issue... Accessing an AsyncTask from a Notification's PendingIntent ... Could I put a BroadcastReceiver in the AsyncTask then send a broadcast on user interaction with the dialog? That was the next option I was going to try... I just haven't had time to implement it yet. On Wednesday, June 20, 2012 10:44:49 AM UTC-4, Chris Stratton wrote: > > On Jun 20, 10:32 am, Saurav <to.saurav.mukher...@gmail.com> wrote: > > Have you tried starting the media player in an activity, and overriding > the > > on Back Button pressed function? Handling all the functions in the > Activity > > Life Cycle? > > > > I am sure there is a way to keep it running programming it in this > manner! > > Certainly there is if you are free to modify the code of the activity > and/or service it uses. > > The challenge of the question seems to be to get a default application > already on the device (which, incidentally, is often customized by > vendors) to do this. > > An alternative might be to build a mini-player service and activity > into the app based on parts of the AOSP version of the default music > player. -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
