• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Google Play Music App

Well, that was what I thought it needed as a reason to keep running. Maybe it's designed that way? I came across this thread recently. Though it's not exactly your situation, it's in the neighborhood. The consensus of those posting (that don't want it to run in the background) was to go w/ a third party player, like Mort Player, and just disable Google's provided one. Like I said before, I'm beginning to suspect that Google's music player is designed to run all the time.
 
Yes I think you're right. I did disable it once before but after enabling it and using it again I find it better than the default player.
 
Changed my mind and have disabled it once again but not because of it remaining in memory but because there doesn't appear to be a stop or exit function on the player itself, which is probably related in some way to the original issue.
 
RyanB said:
Pressing the home key doesn't necessarily shut it down. Using back key will typically tell the IS that it's OK to close out the background functionality, but if there's open RAM than there's a chance the OS will keep it open. Also, if it's just sitting in RAM doesn't mean that it's running. Open apps don't use resources until they're running
Click to expand...

Why would there have been open ram in the first place?
 
Well, if it's running, it will require some of the available RAM
 
RyanB said:
(shrug) that depends on what you are running on your device
Click to expand...

I thought you meant open ram just for that particular app?

I only used the app for playing mp3's on my phone, I never used it for anything else, so would it still be required to run and have open ram when not in use is what I mean?
 
If your RAM is full, the OS will close things out when it needs to free up space . If you have open RAM, it will tend to keep things open and just sitting there. Is that what you're getting at?
 
RyanB said:
If your RAM is full, the OS will close things out when it needs to free up space . If you have open RAM, it will tend to keep things open and just sitting there. Is that what you're getting at?
Click to expand...

I think so.

So open ram is the same as the term free ram?
 
Or thinking about it the used ram is open ram and free ram is unused ram memory, is that correct?
 
Open, free, unused... they are all meaning the same thing.
 
It's either open, free, unused, available, etc, or it's used, occupied, full, etc.
 
My current RAM status since disabling the Google Play Music App is

RAM status 538MB/624MB
 
Look at mind. The first number is the occupied/full portion, the second is how much is free/unoccupied.
syde5evy.jpg
 
So in your case I would suppose the first number to be RAM being used, and the second number to be what's left. I'd have to see it to be sure though.
 
Yep. 489 is used/full/occupied, and 135 is how much you have available before stuff starts getting closed out to make more room.
 
I'm no expert and have my own questions about CPU usage regarding system apps when removed, but here's my opinion based on what I've read and learned.

You'll notice if you play a game that is heavy or do some multitasking using some apps, that your free/available RAM will generally be greater after backing out of all those apps. The Android System manages it's RAM effectively by kicking/closing apps out of RAM/memory your not using, to allow others to run. Stop worrying about Google Music using a little RAM when your not using it, although if don't wish to have it you can disable it to save a little battery. Having it open doesn't mean the system is using much processor cycles to hold it in memory.
I think I'm right... :)
 
I think that the OP is worried about it being listed among the running services at this point (where it would use cycles), as opposed to just being in RAM.
 
RyanB said:
I think that the OP is worried about it being listed among the running services at this point (where it would use cycles), as opposed to just being in RAM.
Click to expand...

Am I right in saying that as long as it shows a mb figure in ram but 0:00 in CPU then this means it's not using cycles at that moment in time? which should be fine.
 
Yes if its 0.00 or 0.00.00 either way nothing is being used or any task being performed . if u hit the force stop the android may laugh at you and clear the section from you viewing it .
 
pm5544 said:
Am I right in saying that as long as it shows a mb figure in ram but 0:00 in CPU then this means it's not using cycles at that moment in time? which should be fine.
Click to expand...

Yes, that's the idea. The 0:00 is how long the app has been running (not open, but using cycles), so that means it's not currently using any cycles. Now depending on how a given app is written, it may start itself. Facebook's app is notorious for this (or at least it used to be, I got rid of it long ago for just this reason). So if you're concerned that it'll be running again soon, keep an eye on it. If you see it running and you haven't opened it, it's not a glitch so much as doing what is intended.
 
You must log in or register to reply here.
Back
Top Bottom