I am currently using the stock Music Player for my phone. Whenever I pause a song, leave the app, and go back to the app, it sometimes goes back to my "All" songs view, not remembering what I was currently playing. It appears that this behavior depends on whether or not the App was closed. For instance, if the app closes by my actions via the Task Manager, or it closes on its own based on memory/CPU management, it loses track of what it is doing.

Is there a setting, or another music app, that allows me to play songs and have that song and playlist remembered even if the app is closed?

I'm running FroYo (2.2) on a Samsung Captivate (Galaxy S series).

  • Please let us know which device you have - since different phones may have different music players. – Daniel Apr 8 '11 at 3:04
  • Try holding the Home key, switching to another app from the list of apps that pops up and doing whatever, and then going back. Does it keep its state in that case? – Matthew Read Apr 8 '11 at 3:05
  • @Matthew, I'll add an additional detail I found out. – Chance Apr 8 '11 at 3:08
  • @Matthew, but to answer your question, yes, it does keep its state. – Chance Apr 8 '11 at 3:11

The Android version of Winamp seems to do a fairly decent job of this. I barely use it (this particular aspect isn't that important to me), but I've just fired it up after about a week, and it picked up exactly where it left off.

  • I downloaded this a few days ago. It brings flashbacks of 1998. – Chance Apr 11 '11 at 20:10

One thing you can try is to increase how long apps stay in memory. It's pretty simple to do this on a Galaxy S -- install One Click Lag Fix from the Market, open it, go to Alter minfree and change it to Moderate (check Set On Boot too). I use this setting and apps usually only get killed if I play Angry Birds for a while and the phone needs to kill them to free up memory.

  • Matthew, I'm interested in this app, but the link seems to be expired and a search didn't bring it up in the market. Does it have a new name? – Chance Sep 11 '11 at 1:33
  • @Chance Looks like they changed the package name from com.rc.QuickFixLagFixR2 to com.rc.QuickFixLagFixR2D, I've updated the link. – Matthew Read Sep 12 '11 at 14:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.