[Q] Streaming music app closes in background - G4 Q&A, Help & Troubleshooting

I have the LG G4 with T-mobile and I frequently stream music with Slacker. I have noticed quite a few times that is the music app is streaming in the background (and the screen is off), the application will close completely and stop playing. This does not appear to happen when the app is in the foreground. I do not have any task killing applications installed and I was wondering if others had seen behavior like this? Any thoughts on how to prevent this from happening?
Thanks!

Same to me but with endomondo

What is probably happening, well has to be getting killed by the garbage collector, but why could be a few things.. if it's doing it when your screen is off its the device going into deep sleep and slacker is not pushing a persistent enough service to give it a higher priority to keep the device awake when the screen is off which there wouldn't really be much you can do besides using an app like Tasker or a robot To 4 + device awake while the screen is off and there's probably some other apps that will do it too. That's one way to test and at least find out if that's what's going on. And another likely reason would be simply the phone is being pushed into out of memory situation and Android is killing off everything which would only happen if you had a **** pile of apps running and I still don't see slacker having a low enough priority to be killed so quickly. I would have to know a little more about what all you have running on your device at the time it is being closed
Through my ancient eyes comes the certainty of decay... LG G4 & L 70

Related

[Q] Is ICS on HOX killing apps for no reason?

I have found that my One X often kills apps I have running when I press the power button and put it away for more than a few minutes. I know Android will try to reclaim resources starting with background apps but this is killing the app I am currently looking at.
I have almost nothing else running and my system normally has 200-300 mb of available memory so it is a very unexpected behaviour. A typical example is I have something like firefox displaying a page. I read a bit then press off. I come back 10 minutes later and it needs to restart and reload the page. With previous phones the app would still be in the foreground the next time I turn it on and unless I navigate away it would stay that way.
I have a nexus s running ICS and that does not happen.
I have a desire running GB and is doesn't hapen.
I have a desire running Froyo and it does not happen.
Is there any way to force a less aggressive memory management on HOX?
There is an option for this, in settings > developer options, furthest down under apps section, first one; "Don't keep activities" check if it is enabled.
Sent from my HTC One X using xda premium
.. also beneath it, there is a restriction "Background process limit", it may also cause immediate kills if "no background process" is set
Sent from my HTC One X using xda premium
Thanks for the suggestions but those were set normally.
Tried using the built in browser instead of firefox and the problem was significantly reduced. It seems the system has a bias against non google apps. Even so - this HOX is behaving different in this respect to my other phones. It is my expectation as a user that if I am doing one thing, that thing should still be there the next time I look at my phone.
Something on the device may be leaking and the result is this need to stop stuff. My money is on sense ( mainly because of the observed ripple/flicker on the home screen ).
I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone
Seeing the same issue on my One S.
This happens with Dark Meadow. If the screen times out, or you hit the lock button, the game kind of "crashes". Not sure if this is the One X killing it or whether it's how the app is coded.
It's irritating anyway ><
Applications with a notification icon have not this behavior. Is there a possibility to set a higher priority to applications without root?
I'm having the same problem.
With cm9 @ Desire Z, I could, say, restore my 3000 sms within GoSMS (which takes a while) and meanwhile do whatever I wanted with the phone, eg. browsing, texting and so on.
With the H1X, after a certain time, the apps gets killed/suspended and therefore anything that happened within the app - which is pretty annoying. Any solution in sight?
H1X @ ARHD
I get this too. Annoying.
ViaraiX said:
I've noticed same with my new one x it seems over eager killing all apps even sense launcher.
settings are correct but using chrome I don't dear open anything else for fear of it closing chrome and having to log back into everything, sometimes its as bad as just answering call or replying to a text message and its been killed
just as annoying it even kills launcher if I press home after using an app for more than a few minutes I get the please wait spinner while it has to load launcher
had ICS on desire HD and on zoom tab... this is not how it should work can't believe a phone with more memory and designed to run ICS is having to kill everything when DHD runs perfect
annoying little thing that is so far ruining what is otherwise an amazing phone
Click to expand...
Click to collapse
Sense launcher closing is not cos of the over-aggressive app killing. It's cos the system needs more RAM, so closes Sense since it's not directly in use right now. I do notice that some apps are getting closed after a period of inactivity, probably a default ICS setting that we can tweak when kernels and ROMs get more mature releases
I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously
harryshepard said:
I'm suffering from this defect as well. It's frankly astonishing that this phone behaves in this way. Really makes you wonder if anyone actually uses the phones before releasing such junk. What use is such fantastic hardware if it performs so badly in real use conditions. Every time I press home, loading. Try to run some javascript Web pages then go send a text, then back to browser and all tabs have to refresh. Mine is going back if it doesn't get fixed pretty quickly as it's practically unusable in this state. Battery is unsatisfactory as well. 2 hours on battery, screen on for an hour, 57% left?! What are they thinking seriously
Click to expand...
Click to collapse
If your battery is that bad you have a bad app running rampant or your battery is faulty.
For everyone else, even in settings if "Don't keep activities" is unchecked, try checking it and unchecking it. I read that sometimes it is still set to "Don't keep activities" even if it is unchecked and checking and unchecking it could solve the problem if this is the case. Doesn't hurt to try.
Hopefully one of the devs will make a Rom/kernel with better oom adjustments... I'm hoping.
the multitask implementation on this phone is terrible. I was using runkeeper, stopped to check something in my settings during the ride, phone closed the runkeeper application deleting my ride. It is getting annoying ...

[Q] High CPU usage by Media (Downloads and Media Storage processes)

I've seen the CPU usage by "Media" (android.process.media?) to be always extremely high (as seen by "Battery Usage" and "GSam Battery Monitor") - and seemed to be the culprit of my very fast battery drainage.
So using Titanium Backup, I Froze "Downloads 4.x.x" and "Media Storage 4.x.x" which seemed to have helped a LOT - I get much better battery life, and the CPU usage by "Media" is 0-1% as opposed to 80-98%.
Just wondering - anyone know why this is - and what side-effects I could have by freezing these two processes?
I have been dealing with this issue for the last couple of days too. I ended up having to clear the data in Google Music and start fresh.
I froze pretty much everything possible. Those two processes will make your music stop playing and prevent you from using system sounds. It might also keep the market from functioning.
I think the latest google music update messed something up though. My problem seems to have cleared up, but I also have not played music in a while to see if it comes back.
Gersonian said:
I have been dealing with this issue for the last couple of days too. I ended up having to clear the data in Google Music and start fresh.
I froze pretty much everything possible. Those two processes will make your music stop playing and prevent you from using system sounds. It might also keep the market from functioning.
I think the latest google music update messed something up though. My problem seems to have cleared up, but I also have not played music in a while to see if it comes back.
Click to expand...
Click to collapse
I've had this for quite a while - I don't play music - and I have not had any problems with notifications or sounds, or even downloads.
I read that it does affect Gallery - which I did just try - and yes it seems to force close. But I have always used QuickPic instead which does not seem to have a problem with me freezing these two processes.
I assume they scan the internal and external data locations for media/files... I've read that it's possible that the scanning process gets stuck in a loop if there is a corrupt file or if there is something wrong with the SD card... *shrug*
I'm just wondering if I should be worried.
I'm on CM10 by the way... amazing how much faster my GS3 is over stock...
I miss CM10 from when I was on my Epic. Eventually the day will come that I will flash something. For now I am still just tooling with the way I like things.
I read about the corrupt file issue too. I am keeping an eye on this. Every time I froze media the media-related processes, something inevitably got screwed up. Hopefully I have fixed the issue on my end.
Do you have Google Music on your phone? Just because you do not listen to music does not mean the application isn't draining your battery. It could be starting up and keeping your phone awake if there is something corrupt going on there. Probably better to seek out a solution that allows the core processes to run than to keep them frozen. More than likely you will lose some additional functionality than just the gallery FC'ing.
Gersonian said:
I miss CM10 from when I was on my Epic. Eventually the day will come that I will flash something. For now I am still just tooling with the way I like things.
I read about the corrupt file issue too. I am keeping an eye on this. Every time I froze media the media-related processes, something inevitably got screwed up. Hopefully I have fixed the issue on my end.
Do you have Google Music on your phone? Just because you do not listen to music does not mean the application isn't draining your battery. It could be starting up and keeping your phone awake if there is something corrupt going on there. Probably better to seek out a solution that allows the core processes to run than to keep them frozen. More than likely you will lose some additional functionality than just the gallery FC'ing.
Click to expand...
Click to collapse
Nope - I don't use Google Music - and I use a separate MP3 player for playing music (I'm one of those weird people who doesn't believe in wasting my phone battery on playing music.. haha)
I don't see anything else eating away at my battery life according to Gsam (well, ok, except the evil Amazon App Store - which I can't freeze since some apps I bought from Amazon require it - UGH).
Please read forum rules before posting
Questions go in Q&A
Thread moved
Instead of freezing these processes, when you reboot after a couple of minutes go to settings>battery and then to MEDIA and force stop. It will turn itself back on later if need be but that stops the ruanaway service with no apps force closing when used.
kennyglass123 said:
Instead of freezing these processes, when you reboot after a couple of minutes go to settings>battery and then to MEDIA and force stop. It will turn itself back on later if need be but that stops the ruanaway service with no apps force closing when used.
Click to expand...
Click to collapse
My phone is set to reboot every morning after Ti Backup does a backup of apps/data and I'd hate to have to go through that every morning.
(the SmartPhoneMate app also requires 1-2 reboots a day so that's why I also do that)
Yeah I'm just lazy
One day I'll take the time to figure out if it's something on my SD card...
I just wanted to make sure if there was something else I should be worried about... so far nothing major as far as I can tell.
P.S> Sorry about posting in the wrong place - as you can see, I'm total n00b here (been lurking for a while though)
Here is a good set of solutions and workarounds: http://geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain/
In addition, a further one may be helpful/needed: disable (freeze) the Downloads app (com.android.providers.downloads)
What was most helpful in my case is to use the Rescan Media Root app to disable the buggy image scanner altogether.
ddvo said:
Here is a good set of solutions and workarounds: http://geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain/
In addition, a further one may be helpful/needed: disable (freeze) the Downloads app (com.android.providers.downloads)
What was most helpful in my case is to use the Rescan Media Root app to disable the buggy image scanner altogether.
Click to expand...
Click to collapse
Good stuff... thanks!

[Q] Phone gets unreasonably slow when song changes

It bewilders me everytime it happens. I'll be just doing general things on the phone, listening to music in the background, RAM usually on the 800mb+ spectrum, and then when the song changes, at one point my phone was near frozen for almost 40 seconds, while nothing else is going on. I disabled most bloatware, and very obsessively monitor my RAM usage and currently running apps, but when a song changes, whether natively stored on my SD card, or Pandora, the phone gets crazy slow. The weird part to me is, for example, I'll be playing a PS1 game and have my framerate counter in the top, and it'll usually be at 60(Full speed), but when the song changes in the background that I'm listening to, the game will seem like it's running at like 5 fps for like 15 seconds, and yet my framerate counter still displays the normal 60, as if my phone isn't actually slowing down, but it really is. Any way to remedy this?
Anyone?
Dang, no one else in my boat huh. Here's to hoping lollipop miraculously fixes my issue.
For anyone reading, found the issue. It was the Media Utilities app I downloaded to give me Pandora controls on the notification screen.

[Q] "This app is using a lot of battery" notifications for Spotify on G3 Lollipop

[Q] "This app is using a lot of battery" notifications for Spotify on G3 Lollipop
I am using Spotify on LG G3 with Lollipop update installed (Build number: LRX21R.A1421650137, Software version: V20h-EUR-XX) and I keep getting a notification from "Android System" that "This app is using a lot of battery", asking me whether I want to close it (see attachment).
I don't get this notification for any other apps (even the ones that use a lot of battery), and while Spotify does seem to use too much battery, it is not significantly more than other apps (at least as far as I can see).
I am all in on Spotify, so even if it's true, I would like to disable this notification, but because it is a system notification, I can't turn it off, but it pops up ALL THE TIME, and is driving me mad.
Has anyone experienced similar issues, or know how I make the notification go away permanently?
There also seems to be a G3-specific Reddit thread about this issue (I can't post the link, because I am a new user.)
Same stuff is happening to me. I think it's just the amount of batt Spotify consumes. I noticed is draining far more batt than PowerAmp for example. Hope they improve the app.
antares_requiem said:
Same stuff is happening to me. I think it's just the amount of batt Spotify consumes. I noticed is draining far more batt than PowerAmp for example. Hope they improve the app.
Click to expand...
Click to collapse
There is nothing to improve, Spotify accesses the network to load your music. This uses more energy than Poweramp could use, no wonder! Still the power consumption is nothing compared to the screen or whatever.
Everything is fine with that and the problem is just this useless notification. I also did not find a solution by now. Interesting thing is that I have a LG G3 too, but I can't imagine this to be device specific. Isn't that a lollipop "feature"?
philler79 said:
There is nothing to improve, Spotify accesses the network to load your music. This uses more energy than Poweramp could use, no wonder! Still the power consumption is nothing compared to the screen or whatever.
Everything is fine with that and the problem is just this useless notification. I also did not find a solution by now. Interesting thing is that I have a LG G3 too, but I can't imagine this to be device specific. Isn't that a lollipop "feature"?
Click to expand...
Click to collapse
I don't think this is a fair assessment of the problem. Other music player apps which conceivably have the same type of usage, e.g. Google Play streaming which I also tried out, certainly didn't cause this warning. In fact, no other app of any type on my phone causes this problem, some of which use more battery than Spotify.
The warning that appears from the Android OS seems to based on real battery statistics gathered by the OS. If I click on the nofitication, it takes me to the battery up that is built in to Lollipop, which shows battery usage percentages for each running app. Spotify is indeed very high up on the list, and based on these statistics seem to cause the battery to detoriorate faster than normal.
The way I see that there is one of three possibilities:
Spotify, for some unknown reason, uses much more battery than it should, e.g. there is a long thread on Spotify community about Android and massive battery drain. This seems to be anecdotally related to "keep awake" and/or SD card. On pre-Lollipop versions of Android, there was no system-level battery usage statistics so people could not point a definite finger to the problem, but with Lollipop the system can for the first time record and notify this higher-than-normal battery usage.
Spotify battery usage is within normal limits and there is a bug in Android battery usage notification/statistics that is causing this notification to show up incorrectly.
Sptofiy battery usage is within normal limits, there is no bug in Adroid battery usage notifications, but in LG G3 Lollipop ROM, LG messed something up in Android which means the notification shows up incorrectly.
It has to be one of these three issues, anything else is not a possibility. Regardless of which one it is (hopefully whoever caused the problem will acknowledge and fix it eventually), it drives me mad that this notification keeps popping up every time I use Spotify and there is no way for me to disable it, because it is a system level notification.
I believe it is ultimately a flaw in Android OS or LG ROM that there is no way to take note of and turn off this notification, even if it is valid.
What is strange is that I have not seen this issue reported for other Lollipop devices, e.g. Nexus 5/6. It seems to be G3-specific at the moment. As I mentioned before, there is a G3-specific Reddit thread about it as well, which I can't paste the link to at the moment (nor can I post the link to Spotify Android battery drain thread...)
rikoe said:
I don't think this is a fair assessment of the problem. Other music player apps which conceivably have the same type of usage, e.g. Google Play streaming which I also tried out, certainly didn't cause this warning. In fact, no other app of any type on my phone causes this problem, some of which use more battery than Spotify.
The warning that appears from the Android OS seems to based on real battery statistics gathered by the OS. If I click on the nofitication, it takes me to the battery up that is built in to Lollipop, which shows battery usage percentages for each running app. Spotify is indeed very high up on the list, and based on these statistics seem to cause the battery to detoriorate faster than normal.
The way I see that there is one of three possibilities:
Spotify, for some unknown reason, uses much more battery than it should, e.g. there is a long thread on Spotify community about Android and massive battery drain. This seems to be anecdotally related to "keep awake" and/or SD card. On pre-Lollipop versions of Android, there was no system-level battery usage statistics so people could not point a definite finger to the problem, but with Lollipop the system can for the first time record and notify this higher-than-normal battery usage.
Spotify battery usage is within normal limits and there is a bug in Android battery usage notification/statistics that is causing this notification to show up incorrectly.
Sptofiy battery usage is within normal limits, there is no bug in Adroid battery usage notifications, but in LG G3 Lollipop ROM, LG messed something up in Android which means the notification shows up incorrectly.
It has to be one of these three issues, anything else is not a possibility. Regardless of which one it is (hopefully whoever caused the problem will acknowledge and fix it eventually), it drives me mad that this notification keeps popping up every time I use Spotify and there is no way for me to disable it, because it is a system level notification.
I believe it is ultimately a flaw in Android OS or LG ROM that there is no way to take note of and turn off this notification, even if it is valid.
What is strange is that I have not seen this issue reported for other Lollipop devices, e.g. Nexus 5/6. It seems to be G3-specific at the moment. As I mentioned before, there is a G3-specific Reddit thread about it as well, which I can't paste the link to at the moment (nor can I post the link to Spotify Android battery drain thread...)
Click to expand...
Click to collapse
==============
...it's still the memory bug, I quote; "It seems one of the bugs that plagued Android 5.0 Lollipop is still haunting some users who recently updated to Android 5.1 Lollipop, the first major update to Android Lollipop.
Some users have reported a memory leak issue in the Android 5.1 update that causes apps to crash and even fills device's memory." (gadgetsndtv.com)
Sorry but I agree with rikoe on this one. if this is an Android 5.0 issue, I would have seen the same alert on other applications (I use like 40) none of them are showing up this alert, only Spotify.
Then I tested it about batt consumption. While POWERAMP uses 5%-6% for 1.2 hour of music playing, Spotify uses 10%11% (playing only saved songs and not using 3g or 4g at ALL, only 2G with streaming disabled)
Spotify needs to improve the app.
I see this notification when using TuneIn Radio Pro, which suggests its not a Spotify specific issue.
Naturally TuneIn Radio does use a lot of battery whilst streaming over 3G / 4G, especially if I'm also playing that stream at high volume through the phones speakers. The same I assume is true with Spotify.
I find this notification to be very irritating. Whilst this function might have limited uses in identifying rogue apps which are have significant battery drain, I am fully aware that in this instance my chosen use of my phone will result in faster than normal battery usage. I don't need a notification constantly alerting me to this, especially a notification in the style of Lollipop notifications, which even after seeing this issue for several weeks I still automatically assume to be a genuine notification (FB, Whatsapp etc) rather than an annoying system warning which I can't disable.
My best guess (based on this not being reported for any other device, LG or not) would be that this is an option built in to Lollipop which LG have either chosen to enable and/or set the threshold for activation too low. If LG insist on having this sort of option it needs to either be tucked away in the Battery Settings section, to be viewed at will, or it needs further functionality to allow me to 'approve' TuneIn Radio, Spotify or any other high battery usage app.
LG do seem to like to baby their users, whether that be through this particular issue, constant volume warnings or telling me to unplug my fully charged phone to save power. I don't like it and it isn't improving their chances of my next phone being another LG.
Let's hope they fix this quietly with the next update.
I believe, it is in the LG Rom. Because I have been using AOSP for 4 months and I've never had this problem until I updated to LG lollipop rom. Vs985
Another LG G3 user here.
I had this issue on LG stock lollipop, it dissapeared when I installed Cloudy 2.1. Yesterday I upgraded to Cloudy 2.2 and the problem reappeared.
I am now trying another lock screen (echo) to see if it dissapears.
Also happens with Spotify on the LG G Flex 2. Slightly ironic considering it came with Spotify (or at least the Sprint variant does).
I'm getting this popup for different programs, all are listed as using 0% since last full charge (which I do once per day)
I was just searching this issue for my LG style 2 plus... I have android 6.0.1. Like martenw I get 0 battery usage since last charge, however the app causing me issues is jet audio. So I was really hoping someone has made an xposed module to turn this nuisance alert/warning off...

Ram overload causing lock-ups/crashes/reloads/bluetooth drops?

I've been having some issues with some apps crashing, freezing, or reloading abnormally on the watch whenever I'm playing music (from the watch directly) and tracking a run with Google Fit. It's usually either the launcher (Bubble Widgets), the watchface (Watchmaker premium) or the music (Wear Media) that starts to conk out at some point while I'm out for a run, which can get pretty annoying as I have to restart the music app or reconnect my bluetooth earphones, and check to make sure the Fit app is still tracking my progress. Could this possibly be due to memory issues - having too many things going in parallel that is causing these apps to fail?
Funny, I experience similar. My tracks , play music. Fit and life log run on background too. After 10 to 12 minutes the watch freezes and reboots... After that no problem, so memory leaks or whatever are possible good explanations
Apb said:
Funny, I experience similar. My tracks , play music. Fit and life log run on background too. After 10 to 12 minutes the watch freezes and reboots... After that no problem, so memory leaks or whatever are possible good explanations
Click to expand...
Click to collapse
Ouch..i've never had reboots yet thankfully. I just hate how this thing's selling points for me (offline Music, offline fitness tracking and gps) don't work the way they should. I've noticed though that using one of the stock watch faces reduces the lag and app crashes a good amount, so i'll be adding "switch to the simplest stock watch face" to my pre-run checklist.
Yep, soms watch faces do cause instabilities, especially the more interactive ones on watchmaker do have that effect. Will check some more combinations in exercise to find better stability

Categories

Resources