Related
I used the update.zip from the Samsung site to update to EB13, everything went off just fine except my Epic now takes an average of 2 seconds to wake from sleep after pressing the power button, sometimes going up to 4 or 5. Not the worst thing in the world, but pretty annoying.
I narrowed it down to my non-usage of the lock screen. I typically run without using a lock screen at all (disabled via SwitchPro Widget). If I turn the lock screen back ON, my Epic wakes from sleep either instantly or within 1/2 a second. With the lock screen disabled (no pattern lock either), it's super slow to wake.
Anyone have any ideas on what I could try?
Mine works just fine, but I'm using the lock screen, try uninstalling that widget and see if it corrects the problem when you use the lock screen.
Small update to this. I had an idea to move all the apps that I had moved to the SD card back to the phone to see if that helped. It does. With the lock screen on, my Epic comes back from sleep instantly every time. With lock screen off it varies between 1/2 and 1 second.
The apps I moved to SD were ones I hardly used.. I don't know why that would have an effect on the wake time?
Mine seems a bit slow too. But it's not the 4 or 5 seconds you described. It seems like it's about one second, when it used to be anywhere between instantly and half a second.
It's kind of annoying because the delay is just barely too long to where I start second guessing myself on whether or not I pushed the button in all the way or not.
Go to your display setting and reset your horizantal calibration accelerometer... that fixed my phone waking up issue...
Sent from my SPH-D700 using XDA App
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
toxicsociety said:
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
Click to expand...
Click to collapse
I use the same program as you do and I have the exact same problem So your not alone.
Mine is slow to wake also, about a second. When its plugged into the charger its instant, weird.
I'm glad we aren't alone though. Hopefully if this is a big enough issue, people will look into it. And also, they've pulled the EB13 update from Sprint and Samsung's website.
It's causing problems with reading media from the SD card and also has data issues. So hopefully in the new one, they will fix this problem too?
Looks like it's No Lock, from what I can tell. If you disable it, it comes on instantly. If it's enabled, it takes it a moment to wake up.
So I get these wakelocks for some reason, about 2-10 minutes of Audioout_2 and Audioout_3 per hour when idle, with screen off.
And they seem to show up as wakelocks, even if I have my phone active. So I get like 47minutes of this wakelock, but awake time is 56:27minutes and screen on 54 minutes. And this is not the problem until you see how much of this wakelock has kept your phone awake after 24 hours, I had like 3-5 hours. Should I be worried?
APP - Wakelock Detector, BetterBatteryStats.
What I have tried - Uninstalling Viber, no difference. Disabling all lock sounds, touch sounds, dial pad tones, not much difference either.
I didn't have this before, what could it be?
Android 4.3 Stock, not rooted
I seem to be having the same issue. I'm running on stock 4.3, no rooting, I do not have Viber, and while I do have Skype installed, I almost never use it. I have haptic feedback disabled as well as touch sounds.
Rebooting the phone seems to fix the issue, but that's obviously a bit of a pain to do every time.
Other than maybe blaming Poweramp for keeping the wakelock going, I can't think of any other apps that could be causing the issue.
apu95 said:
I seem to be having the same issue. I'm running on stock 4.3, no rooting, I do not have Viber, and while I do have Skype installed, I almost never use it. I have haptic feedback disabled as well as touch sounds.
Rebooting the phone seems to fix the issue, but that's obviously a bit of a pain to do every time.
Other than maybe blaming Poweramp for keeping the wakelock going, I can't think of any other apps that could be causing the issue.
Click to expand...
Click to collapse
After you reboot when does the issue seem to come back? What apps are you usually using?
Do you have any of these apps - Light Manager, DashClock Widget, Smart Wifi toggler.*
*These apps have no deal with audio wakelocks whatsoever, but still, maybe 4.3 has caused one of those apps to use the audio wakelocks somehow.
Yukicore said:
After you reboot when does the issue seem to come back? What apps are you usually using?
Do you have any of these apps - Light Manager, DashClock Widget, Smart Wifi toggler.*
*These apps have no deal with audio wakelocks whatsoever, but still, maybe 4.3 has caused one of those apps to use the audio wakelocks somehow.
Click to expand...
Click to collapse
My main apps are Gmail, Chrome, Facebook, Twitter, BaconReader and Poweramp. After rebooting the length of the wakelock time definitely isn't as long. And yes, I do have DashClock Widget. I didn't consider that one to be a potential culprit.
Yukicore said:
So I get these wakelocks for some reason, about 2-10 minutes of Audioout_2 and Audioout_3 per hour when idle, with screen off.
And they seem to show up as wakelocks, even if I have my phone active. So I get like 47minutes of this wakelock, but awake time is 56:27minutes and screen on 54 minutes. And this is not the problem until you see how much of this wakelock has kept your phone awake after 24 hours, I had like 3-5 hours. Should I be worried?
APP - Wakelock Detector, BetterBatteryStats.
What I have tried - Uninstalling Viber, no difference. Disabling all lock sounds, touch sounds, dial pad tones, not much difference either.
I didn't have this before, what could it be?
Android 4.3 Stock, not rooted
Click to expand...
Click to collapse
I have the same problem.
I noticed that audioout_2 only runs when my screen is on.(most of the time)
The audioout_2 run time and SOT are always close.
The audioout_2 and audioout_3 will not run (very minimum) when your cell goes into deep sleep.
I have mostly Google apps installed.
Edit: After searching on internet,Many users told these wakelocks can be caused if there is a corrupted mediafile (picture,music,video)..
Need a solution for this.
l33ttroll said:
I have the same problem.
I noticed that audioout_2 only runs when my screen is on.(most of the time)
The audioout_2 run time and SOT are always close.
The audioout_2 and audioout_3 will not run (very minimum) when your cell goes into deep sleep.
I have mostly Google apps installed.
Edit: After searching on internet,Many users told these wakelocks can be caused if there is a corrupted mediafile (picture,music,video)..
Need a solution for this.
Click to expand...
Click to collapse
What do you mean corrupted mediafile, like unsupported MP3 file? Could that be a problem? God dammit, this is too complicated.
I have only a few pictures that I have taken with the phone, no videos. Only music could be related.
So I yesterday turned on location services, the results I got were pretty bad. I am not 100% sure that the issue is location services, but I did not have this bad screen_on - awake ratio before. Here are some screens.
I didn't do anything unusual, I might report back tomorrow about results w/o location services.
I left only GPS setting active in location settings. Here are the results.
6hours phone on, Battery left 87%.
55:31min awake, 38min screen on.
1013 wakelock usage 32:12min.
I played a few games, made some calls for the time when screen was awake.
I would call this a success, because usually I could barely make through a day, almost 3hours screen on in 12hour period. And the battery is dead.
Yukicore said:
I left only GPS setting active in location settings. Here are the results.
6hours phone on, Battery left 87%.
55:31min awake, 38min screen on.
1013 wakelock usage 32:12min.
I played a few games, made some calls for the time when screen was awake.
I would call this a success, because usually I could barely make through a day, almost 3hours screen on in 12hour period. And the battery is dead.
Click to expand...
Click to collapse
What was your solution? So far my current one is to reboot when I wake up in the morning.
apu95 said:
What was your solution? So far my current one is to reboot when I wake up in the morning.
Click to expand...
Click to collapse
I disabled Wi-Fi & mobile network location in Location access settings. But I am not entirely sure that this is a solution.
I am very confused with all this Android and Nexus 4 problem amount and uncertainty, I am not even sure what to believe anymore. I am starting to wish I had bought an iPhone. Maybe it was because I was at just at home and in a city mainly, and the cellphone just didn't have to look for different cell towers, I am not sure what should I even think anymore.
But currently this has helped me, I guess. Disadvantages of this might be that the phone will not be able to select the best server available when indoors... I'm just so tired of Android.
I can't shake off this stupid wakelock, it keeps my phone awake, Android is soo annoying, I would probably never notice this if it weren't for the battery usage apps, but I would notice the horrible battery life on Nexus 4.
Has anyone had this problem and made it go away? Or is still having, and just got through with it and ignores it? Please help me!
I think I had 0 amount of this wakelock in the first few days I got these battery status apps, I had only a few Media, Caldendar, Gmail etc. wakelocks
The wakelocks are caused by the touch sounds that are enabled by default.
Everytime you touch a button on your phone it will make a sound, which will initiate the wakelock. Turn off these sounds in:
Settings -> Sound -> Touch Sound
You can also 'hear' the wakelock, because when you hold the back speaker of the phone to your ear when a sound was just played, you will hear some static noise for ~2-3 seconds after the sound finished playing.
When you listen to music or watching a video you will also get these wakelocks, but that's completely normal.
Sent from my Nexus 4 using xda app-developers app
mumaster20 said:
The wakelocks are caused by the touch sounds that are enabled by default.
Everytime you touch a button on your phone it will make a sound, which will initiate the wakelock. Turn off these sounds in:
Settings -> Sound -> Touch Sound
You can also 'hear' the wakelock, because when you hold the back speaker of the phone to your ear when a sound was just played, you will hear some static noise for ~2-3 seconds after the sound finished playing.
When you listen to music or watching a video you will also get these wakelocks, but that's completely normal.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
+1 to that
Even if u have ur dialpad to sound off. Go ahead and type numbers in like crazy then check the wakelocks!
Even if u have turned that option to OFF.
Sent from my Nexus 4 using XDA Premium 4 mobile app
WasifSal said:
+1 to that
Even if u have ur dialpad to sound off. Go ahead and type numbers in like crazy then check the wakelocks!
Even if u have turned that option to OFF.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Right, did You have that before? Or it just turned up recently, I don't remember having this much wakelocks, and why are ''wakelocks'' wakelocks when you are using your phone and the screen is on?
I noticed that if I don't have internet access, the wakelock doesn't come up as much. It's some kind of app, maybe, it very much could be one of Google's, It ain't Viber (for me), I have tried disabling, turning it off, no change in wakelock amount.
Yukicore said:
Right, did You have that before? Or it just turned up recently, I don't remember having this much wakelocks, and why are ''wakelocks'' wakelocks when you are using your phone and the screen is on?
I noticed that if I don't have internet access, the wakelock doesn't come up as much. It's some kind of app, maybe, it very much could be one of Google's, It ain't Viber (for me), I have tried disabling, turning it off, no change in wakelock amount.
Click to expand...
Click to collapse
I just checked that now
To be honest i'm in the same condition u are in. I don't know whats causing these. Try greenifying Google+, Google Now etc. They have helped me a bit in saving some... Google+ updates/syncs, and that makes a wakelock as well.
Sent from my Nexus 4 using XDA Premium 4 mobile app
WasifSal said:
I just checked that now
To be honest i'm in the same condition u are in. I don't know whats causing these. Try greenifying Google+, Google Now etc. They have helped me a bit in saving some... Google+ updates/syncs, and that makes a wakelock as well.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have set syncing and updating google apps to the minimum already. Google Now is not active.
Does other android phones like Galaxy S3, S4, HTC One also have this bad battery life, or is it Nexus 4 specific?
apu95 said:
What was your solution? So far my current one is to reboot when I wake up in the morning.
Click to expand...
Click to collapse
Do You have Flash Player installed on Your Android device?
This is really weird, I restart the phone, use gmail, and some other apps, turn off screen, check for wake locks, no Audio wake lock at all, I open Chrome, use it a little and then check for wake locks and it has appeared and is at at the top, also other wakelocks have increased count.
Also another matter, I notice a little pop in the speakers sometimes, even though I have set to vibrate only mode.
EVERY TIME I TOUCH THE SCREEN THE SPEAKER TURNS ON, it is just quietly hissing, you need to be in complete silence to hear this. This is definitely causing a big battery drain, I need to fix this ASAP. Anyone has a clue?
Turned off touch sounds, hissing has disappeared. But it literally started hissing after I press anywhere on the screen, even though only a few buttons make a touch sound.
Got to stop typing now, my hands are burning when I'm using Google chrome on my nexus 4...
I disabled Google+ Notifications through Google+(app) > Settings > google account > notifications
And I turned off all Sounds, from Dial pad touch tones to screen lock sound and vibrate on touch. Now I had tried this before the Google+, but I still had the issue with the wakelock.
I get little to none of this wakelock, also turned off google+ backup feature. Disabled some sync options in google account.
But basically I get a lot less of this wakelock now, I am not entirely sure it was Google+, but I have been using the phone casually, as usual for 30+ Hours, charged once, and I get better battery life and much less of this wake lock, phone is mostly in sleep mode when screen is off, about 1-4 Minutes awake.
Now I don't guarantee anything, maybe it's some service that didn't start up this time, but I'm pretty sure that I had opened every app that I was using when I had the problem, this seems to have fixed the problem, see if it helps, if you are experiencing the same issue, and please let me know, thanks!
Oh and I have been using the phone's speaker indeed, for games, Youtube app, Chrome etc. and Received calls, messages, notifications.
Any solution? I'm still having this 1013 wakelock without apparent cause..
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Well what case have you got?
I have no such problem on my Portenzo hardback case.
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Click to expand...
Click to collapse
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
sfhub said:
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
Click to expand...
Click to collapse
Same. WiFi on or off seems to work okay... WiFi on and searching is always touch and go for me. Hopefully it can be fixed pretty easily in software down the road... before it starts to actually bother me.
Noticed this on mine as well. Different than my 2012 model but not a real problem
Sent from my Nexus 7 using Tapatalk 4
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
WilliamG said:
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
Click to expand...
Click to collapse
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
negroplasty said:
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
Click to expand...
Click to collapse
Yeah. All I know is I have the wifi set to not run during sleep, and all seems fine, - just that it takes the Nexus a good number of seconds to come alive after it's been asleep a while.
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
RKight said:
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Same for me.
I noticed if WIFI is ON, or device is connecting to power/USB. The wake will works perfectly and instantly.
But if WIFI is OFF or not USB connection, the wake is not function after closed the cover for few seconds.
WilliamG said:
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Click to expand...
Click to collapse
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
hyperxguy said:
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
Click to expand...
Click to collapse
That's impressive! I'm sure it's a bug that affects all Nexus 7 2013 devices, but it's still lame.
For anyone having this issue, I found a thread on the Google product forums about this. That's apparently how they became aware of the other issues that have been reported. If you could, please post your problem in this thread: http://productforums.google.com/forum/m/#!category-topic/mobile/android-devices/8MTpqfFmw8Q
Sent from my Nexus 7 using xda app-developers app
Are we sure this is actually an issue? Based on the threads I'm reading about this, the cover only seems to wake the screen when you open it while things are running that would normally keep the N7 out of deep sleep. Isn't the tablet being able to enter deep sleep mode successfully a good thing?
The reason I say this is because a lot of you, including myself are reporting that when Wifi is off, and the tablet is unplugged, opening the cover won't wake the screen if it's been closed for a long time but it will after just short periods. This indicates deep sleep being entered successfully. If the cover is able to wake the screen in that mode, I'd be more worried that deep sleep mode isn't being entered successfully.
I guess the main question is: Is 4.3 along with the Nexus 7 hardware actually designed to only be able to be powered on by the power button itself during deep sleep? Do not services have to be running in the background constantly in order to allow something else to wake the screen? For example, in order for one of those 3rd party screen apps that use either proximity sensors, or light sensors or position sensors (shake) in order to wake your screen to work, all of the better ones I've seen not only require administrator permission, but also running background services.
In other words, they use the hardware sensors inside the Nexus 7 to wake the screen but also require some kind of additional resources running in the background. Which means resources being consumed. Smart covers also use hardware inside the N7 to wake the screen but without an app consuming resources in the background to so do. Which means NO resources consuming battery or memory, which is a good thing.
I'm not so sure I even WANT this fixed if it's going to mean my tablet has to have stuff running in the background in order for it to work. If Google can make it so that's not the case, then I have no problem with it. I could be completely wrong as well, I'm just speculating so if Google says it is actually a software bug then I guess I am.
omnius1 said:
Do not services have to be running in the background constantly in order to allow something else to wake the screen?
Click to expand...
Click to collapse
I guess that depends on the magnetometer chip they are using. If it can generate an async interrupt on a change in magnetic field, then that is one thing, if it has to be polled, that's something else. I don't find it too great a hardship to occasionally have to press the button, so if it is doing this to save more power, that suits me.
I think this thread is about all the "odd" things happening, specifically to the some 2013 Nexus 7 (some people don't have this problem).
I also have the 2012 N7 and the Nook HD+ with smart covers, both are running JB4.3.
Both can go into deep sleep and whatever (wifi on/off, things running or not) and will wake up in an instant as normal.
This is not normal !!
By the way, I received the replacement and similar results. I didn't expect it to fix the issue anyway as I think this is similar
to the tough issue with some N7s (I don't have this issue) which is a google problem.
A little off-topic about deep sleep... my Nook HD+ can sleep for a whole day and only take 1% of the battery.. best I've seen.
Edit: just in case somebody thinking about a ROM problem, I've tried multiple ROMs including stock.. all have same issue.
Moko smart cover is the best
It should wake up within a second, at worst, period. Ideally it'll wake up "almost instantaneously". There's something wrong.
I wish the mods would merge these two threads so the nonsense is at least in one place.
Mine sometimes will wake after a delay and will sometimes just sit and do nothing at all until I press the power button. It has turned on after a 30 second delay, after being idle all night, but has also completely failed to turn on after being idle for just five minutes. This thread is definitely aimed toward the odd inconsistences and what I indeed perceive to be a problem.
Sent from my Nexus 7 using xda app-developers app
Has anyone else had this happen? Happens quite often for me. I'll be playing a game at work, get up to do some work while leaving game open. Come back and unlock the phone and it's on home screen. Does the same thing while listening to Pandora.
I've never noticed that happening to me, I just tried to reproduce it with not luck. How are you unlocking the phone?
Either fingerprint or iris. It does it with both. I don't see it happening when turning phone off and on right away. Phone usually sits a few min before it does it.
jeb192004 said:
Either fingerprint or iris. It does it with both. I don't see it happening when turning phone off and on right away. Phone usually sits a few min before it does it.
Click to expand...
Click to collapse
Battery optimization setting probably. Try disabling optimization for an app that currently does it and see what happens
That didn't help
Couldn't replicate issue either. Let Rayman running and screen went off for about 5 mins. Unlocked with fingerprint and went directly to the game. I had power saving off and performance mode set to optimized.
OP do you also lose your place when it directs you to the home page? Or does it resume when you reopen the app?
It resumes when reopened.
Power saving off and performance mode set to optimized as well.
The one app where it does it almost every time is Star Wars: Galaxy of Hero's. Only other app I notice it once and while is Pandora.
Are you sure you aren't iris unlocking it without knowing you are? Sometimes mine unlocks almost instantly when i press the unlock button. Or when I turn my screen on to check the time.
Is "iris unlock when screen turns on" enabled?
Lock screen & security > iris scanner
I'm sure. Most of the time my phone is face down and I grab it by the side and put finger on scanner. Turned iris scanner off just to be sure and it's still doing it.
Also does it with line messanger...
I have this exact problem as well. Seems to happen rather randomly.
I sometimes see the app actually minimizing to the home screen when I unlock the phone, so it's probably not some background task killing it.
The app is only minimized, not killed.
I have this issue as well.
I think I found the problem. Uninstalled bxActions and as of the past 2 hours the problem is gone.
i have this issue but i don't have bxActions so i don't think that is the problem
Are any of you happening to use the long press home option, the one that bypasses the lock screen? Even though you may not be using the home button maybe the option is still affecting the apps that are open and thinks for some reason you're pushing on the home button.
It might be an app causing it. I still haven't had any issues since I uninstalled bxActions. If you don't have that installed it could be a different app causing it.
I was also having this issue. Stopped bxactions and the issue is gone. Started bxActions back up and issue came back.
Same problem here. On Verizon s8 and no bxaction installed. Very irritating!
Unrelated but another problem is when I change to aggressive wifi/cell handover in developer options it allways defaults back off after a reboot? Any ideas??
After about 20 minutes, Pandora keeps closing. Battery management for the app is off. I've tried uninstalling, restarting the phone, but nothing has helped.
Is anyone else experiencing this?
Yep. Already tried turning off battery optimizing for pandora and giving it the proper permissions.... I suspect it is due to oos aggressive battery mgmt
This is a sign from the Universe to switch to Spotify. You have bright futures ahead.
Experiencing the same. Very annoying.
you guys figure this out?
I've had the same issue with Google Play Music. The only solution I have found so far is to lock the app in memory. After that, I've never had issues with it just closing randomly.
No issues at all with Pandora. I'm on 9.0.11. I have the app set to optimize, but I've got adaptive battery turned off because reasons.
I experience this all the time with the direct from Oneplus 6T. However, my wife's T-mobile 6T doesn't do this. What the heck?
I'm on 9.0.11, still does this with Pandora despite turning off battery optimisation and adaptive battery...has anyone else figured this out yet?
No issues here. May be Pandora's problem. Maybe they need to fix the app.
Pandora stops after 20 minutes ~
Was experiencing the same thing. I turned my background restriction off under battery usage, seems to be fixed on mine now. Nope shut down again
Apps stop working fix on armor phone. Mine is armor 6E
Press app main button near your home button. Then you can either swipe away running apps or press one of the two buttons which are clear all, or go into running apps settings (same screen, not main settings). This allows you to either have all apps stop after a certain time or individually have apps turn off automatically once screen times out after a certain amount of time. I hope this helps! Took me forever to find.
woflx said:
No issues here. May be Pandora's problem. Maybe they need to fix the app.
Click to expand...
Click to collapse
I agree with this post. I also noticed that when using pandora while using the waze navigation app that you can skip or pause but, are not able to replay a song. I have contacted both pandora and, waze about this issue and, they just blame each other. In the end no fix. I have pandora plus btw
I understand this may only help a few people, but what fixed it for me was going to settings > battery > adaptive battery > restricted apps... And then removing Pandora (from the list I forgot I added it to, upon the phone's prior suggestion)