Postby XilasZ » 16 May 2013 11:50
About the service, it's not that simple.
The service and the app share the same process, and the same ram usage. so the 60Mb of RAM that you see, it's for both the service and the app.
When nothing is playing or is paused, the service is there, but flagged as killable if necessary. That means that the service & app in background can be killed at any moment by android. stopping the service wouldn't change the ram usage if the app is still alive.
And forcefully closing the app on back won't matter either, since android can decide to start it again in the background if there's enough RAM, and there's nothing we can do about that, that the way android works.
The real issue is the fact that the internal library used by the app & the service is loaded on startup, but is NEVER unloaded. That's what consume the RAM.