Nexus S won't go to sleep - Nexus S General

Looks like I've just solved my own issue in the midst of creating a post. For those that are curious anyway, this is what happened..
My phone would not go into sleep mode. Clicking the sleep button would put it into sleep for less than a second before it popped back to the lock screen and stayed there.
The solution was to clean the USB port. Apparently some debris found its way into the USB port (I wonder how, certainly not from leaving it in my pocket, where it normally would be) and wreaked a small havoc on my phone. All is well now and the phone is almost one month old. After rooting and fixing a ringtone issue, my only issue is the crappy Gallery app. The phone is great otherwise! Killer battery life too
Here's a video of what I'm talking about. Enjoy

Same issue here. How exactly did you clean the port?
My issue started immediately after using Shazam. I tried to Shazam a song, then after that the phone would not sleep. I switched batteries, factory reset, nothing fixes it.
In fact, the phone will sleep until the battery gets to about 50% then it just stays awake until it gets into like 20%.

Related

Random Shutdown

When my phone is sitting idle (screen off) it will randomly decide to power itself off. Has anyone else noticed this? Any ideas on what could be causing it?
The Balvenie said:
When my phone is sitting idle (screen off) it will randomly decide to power itself off. Has anyone else noticed this? Any ideas on what could be causing it?
Click to expand...
Click to collapse
you mean randomly power itself ON, right?
if that is the case, it's normal, it just mean it woke up to connect to the internet, to get updates of news, emails, or whatever it was scheduled to pick up
nope. i mean it randomly turns itself off. this topic is being discussed over on the att captivate galaxy forum section.
interesting, so it's going from stanby mode, to complete OFF... nope never seen that happen to my i9000 model
yep totally powered off... completely sucks... looks like there are a bunch of ppl that have this issue with the captivate on att. $10 says its some lame piece of software that att puts on your phone that's causing the problem.
it's possible, i've read here a few users having crazy power issues (battery draining very fast) with their SGS i9000, but after wiping it out clean, to start anew, then the power problem is gone away.
so yes, a software could cause something weird like that.
Factory reset and so far so good
Hey guys,
I use a Galaxy S here in Hong Kong and I had the same random shut down issue constantly happen when my screen went off...
I tried everything, check temperature of cpu, etc. etc. and nothing worked, it just got worse and worse.
I even changed the battery to use the spare one that came with this. Still problematic.
Used SET CPU to limit the cpu to 400mhz, still problems.
Finally I did a factory reset and so far so good.
I only have the original system installed with the Remember the Milk app installed.
24 hours, no problems.
Installed AppBrain app.
Then I installed 3G WatchDog
12 hours, no problem.
Then I installed Paperdroid
12 hours, so far no problems at all.
If I run into an issue I'll post it here. But I think it definitely was a software issue.
Update - it randomly shut down on me
Alright guys, it shut down on my randomly today in the afternoon......
I dont know if it's the re-charging that screwed it up?
Because after my factory reset, last night was the first time i charged it....
Hmmm
This happened to me too - two days in a row until noon it would shut down two or three times - i uninstalled SetCpu and for now (24 hours) it hasn't happened again. I am not sure if it was the one responsible but it started happening after i installed two programs and i uninstalled them after it started happening. I uninstalled Visual Task Switcher first but on the next day it turned off again, then i unsinstalled SetCpu and it hasn't happened again - maybe some wrong profile settings but i didn't feel like experimenting
I had this issue once too in about 40 days.
I was reading an sms and then i turned into standby and put it in my pocket. Later, maybe 40 minutes i came home and my phone was completely off. I do not remember if i had to take out the battery before to get it on again.
I was wondering why it happened. Maybe it was caused by an app i had opened. Battery still was at 40%.
But since it only occured once in 40 days i doesn´t bother me.
Interesting you mention this as it just happened to me today for the first time. I took it out of my pocket and wtf? The phone was off. Very strange... Using the i9000 on the stock Eclair rom.
Should send back for warranty
Sent from my GT-I9000 using XDA App
software clash?
Well the phone suddenly switched off for me, but this time I turned off APPBRAIN and so far so good.
In fact, I came across an app called NoLED and since it kind of keeps ht phone on, while I have it on my desk, I'm able to be notified of stuff and so far with that, the phone hasnt' shut off.
I'm still experimenting with what works, but try turning off AppBrain and see if you still have the random shut off issue....
i use app brain all the time to keep my apps in sync
not the cause of the problem, that's for sure
my phone can last a whole day even with app brain running
OP, do you have MSN Talk installed on your phone? I have this same problem, seems to happen more when I am running MSN talk in a low signal area.
«try a new sim card. «Could be faulty. «i am on my 3rd phone and all of them had this same problem. «i bought a new sim card 4 days ago, and hasnt happened since. «but then again, this problem usually happens to me once every 3rd-5th day anyways, so i dont know if i am in the clear yet.
Me too, shutdown everyday
Hi guys
After upgrade OS to I9000ZSJG4, Phone random shutdown everyday.
Yep still shuts down
Tried keeping AppBrain off, still shuts down.
Used NoLED so the screen kind of stays on, still shuts off..
So far shut off on me after 40 hrs... this is really stupid.
I am this close to taking it back, but I genuinely think it's a software issue than a hardware issue...sigh
Anyone have any luck figuring this out?
Same problem no solution yet
Hi
I too have the same problem, haven't found any solution yet.
The temperature etc is all good, there is no pattern in shutdown issues.
I have tried factory reset and no new application, it still shut down while using in built browser.
I had the same thing happen to me while skiing in Whistler last weekend. It died twice. I attributed it to the cold. I normally use a 3000mah battery up there, but left it back the house that day. Afterwards while charging in the car and even charging it at home it died prematurely again. It was the eBay aftermarket variety 1500mah knock off. I have since changed back to the Samsung OEM battery. I haven't had an issue with it since. My assumption is that the knock offs in my case cannot handle the heat cycles of charging and then the cold as well as the original. Or they have a limited lifespan, well below OEM specs. I am now only using the 3000mah battery on the weekends to hedge my bet on the quality of manufacture, as it seems to be from the same factory as the 1500.

Overheating and battery life.

I don't know what all your experiences are, but I noticed the past few days that my epic is getting hot on the back.
I also noticed that my battery is draining more so than usual. When I got the update last week my battery life sucked, but now since this overheat thing it's gotten worse. It drops a lot even when in standby.
I do not have gps, wifi, anything else on. I am not rooted. Didn't do any battery tweaks. This is completely stock di18.
This is normal use with 3g. It's getting annoying and I'm hoping someone has an answer. Thanks!
Do you have any email accounts configured in the mail application?
This happened once or twice - I rebooted the phone and all was peachy.
Sounds like you have a rogue process wearin it out.
Yeah my phone overheated yesterday while charging....this phone has a few more steps to go before it really beats my hero...
Sent from my SPH-D700 using XDA App
I partly found out what the problem was, but it seems you guys are ahead of me. I had some process keeping my CPU running at 95-100% nonstop. I still haven't figured out what the process was, as now it is back to the normal 5-15%, but I'll have to keep an eye on it now.
the task manager widget turns red and it shows you what process was causing it...for me it was the xda app...a few times.
I think my problem was not backing out of WordFeud. I didn't notice anything on the task manager though. Hasn't happened since that one time.
this happens to me when i'm plugged in and using gmail. screen flickers and then shuts off. the screen-off battery indicator shows the batt. gauge and a little thermometer sign next to it indicating it's too hot.
wtf?!?! this has to be a defect. anyway, is there any official word on this? any pr from sammy/sprint?
i have read elsewhere about some epics resetting themselves a few times a day which could indicate an issue with heating (at least on a pc). so if you think it might be hardware its possible. otherwise keep doing what your doing, monitor your processes for anything thats eating it up, go to about phone > battery use > cell standby to see your time without signal. the higher this is the more battery use. also, might want to consider a startup manager to prevent the 2 DRM files (search forums) from running as this can affect batt life too
you can also use setcpu even (free on here, search it) to throttle your cpu down when it hits a certain temp.
This is very interesting... My wife and I both have this phone, she has had this happen several times after the last update (I though she was just crazy). Me on the other hand... No problem!
I need to look into this a little deeper.
The only time my epic's battery gets hot is during heavy use or gps. Gps/Nav makes it heat up like a mofo. But other than that... *knocks on wood* Its all good, no problems. As far at battery life, I am rooted and using SetCPU to turn down the processor while the screen is off, helps a ton. Not using anything other than that... was using juicedefender but then I started not getting calls or text...
Sent from my SPH-D700 using XDA App
One thing, I learned, that didn't help my battery was putting my phone in the locker at work. That thing must have killed my TWS and ate my battery alive.
i feel like this thread will start to die but i had a weird somewhat related issue last night. i too have had maybe 3-4 times where i woke up to my charging phone with the red LED and a screen that would not turn on, battery pull, worked fine.
however, THIS morning my phone would freeze like 30 seconds after boot EVERY time. tried a few things to no avail until I wiped, reinstalled my ROM (aosp 0.4.1) and the data from a previous backup (which was the way i got that ROM to first boot successfully according to tips in that thread).
so this worked, but i couldnt figure out why my other steps wouldnt. had to be something in the data partition of my system at the time, since changing that worked. the only thing i could think of is that app watchdog which someone mentioned to track processor usage by apps. anyone else ever experience this?
I have experienced this once when I was playing Robodefense while the phone was charging. My phone tends to get a little warm when it charges, and hot if I run something intensive while its charging. Wondering if this will be an issue when I use this phone for GPS nav while plugged into my car.
Sent from my SPH-D700 using XDA App
"I'm having this problem too...I didn't get any warranty for this either. Any reasons onto why this is happening...I woke up this morning and picked up my burning phone lol the temp was at 50C so I took out the battery and let it sit for 15 mins...it went down to 30C, then after not touching it for another 15..it was at 17C...very odd...what should I do, this crap is going to die within the next hour I'm worried it will fry the hard drive or something. Need help! " - I wrote this on a diff. forum a couple days ago
I dont have anything on, no wifi, gps, or any 4g (lol only if I could find it)...I even got rid of my facebook/twitter/weather updater widgets. The only thing that updates is email, and that's only if I click on it. The battery has been dying a lot faster and I charge my phone next to the window now because its like 20 degrees outside here in Chicago, so that brings down my phones temp lol....and today, my phone's battery life went from 100 to 5 percent in about three hours of barely using it...wtf?!
Also, another problem...sometimes when I lock my phone and unlock it after taking it out my pocket or something, the screen doesn't seem to respond...I keep swiping my finger over it to put in my password and it wont do anything and it only works when I slide up my phone for the horizontal view. This happens like 4 out of every 10 times I open phone.
Very embarrassing especially if your trying to get someones number down, I stopped showing off the phone now ...lol

Nexus 4 switching off at night while charging

I know this has been discussed plenty of times but I just have some more questions of my own I'd like to ask.
So my N4 just switches off over night after being charged to like 95-100%.
It is usually fully charged (green LED) but won't turn on if I want to wake the screen.
I have to hold the power button for like 5 seconds for it to switch off. Then I am able to boot it again.
If i just unplug the charger, wait like 30s to a minute, the screen will wake, it works as usual. But the phone restarted (!!!) without any boot animation or anything. Just like nothing happened. If I then go into settings -> battery you can see the phone switched on just a minute ago.
This is happening like everynight for me now, so I had to use my old phone as an alarm clock as I slept in quite a few times actually
I searched like all forums and tried everything but I cannot dissolve this issue.
I even turned off deep sleep in dev options and stuff alike, monitored temperatures and stuff. Nothing conclusive though.
So I just have no idea why this keeps happening.
It happened with different roms and different kernels. Root or not rooted.
A friend of mine has a N4 as well and he does not have this problem at all. He does not have a custom rom flashed or anything.
But I read on other forums that even users with stock rom had this problems.
I think this is a quite common problem with the Nexus 4 device, isn't it?
Anyone solved it yet? Or does at least know the CAUSE for this?
I mean srsly there is like nothing on the forums..
Is it software related? Hardware related? Did I **** something up?
Is this a valid reason to send my phone back to google and get a new (working) one?
Everything else just works flawlessly. I mean the N4 with PA on it works so smooth like a charm.
I DO NOT WANT TO GIVE IT BACK!
noone? really?
I don't remember this being a common problem, though maybe I missed something.
If I was you I would wipe everything and re-flash stock. Then if it still happens return the phone, it shouldn't be doing that and I wouldn't put up with that if it was my phone. But it's your choice.
Sent from my Nexus 4
I have the same problem and I believe that this and similar issues are becoming increasingly mentioned on various sites on the net. XDA tread - http://forum.xda-developers.com/showthread.php?t=2077148 which gives some idea as to what people are doing to get to the bottom of the problem.
There is further info here - https://code.google.com/p/android/issues/detail?id=35139 which starts with Sleep of Death issues on JB4.1.1 (on the Galaxy Nexus but has more recently focused on the Nexus 4).
Initially the problem occurred maybe 3 times a week. I'm running a Stock N4 and whether stock or custom does not seem to make any difference.
I re-flashed a stock image and thought I had solved the problem. The phone ran okay for a few weeks and then reverted to random SOD's normally at night whilst charging. If I use airplane mode at night I have no problems. It has also become unresponsive/deep sleep on three occasions during the day. More recently I have stopped leaving wifi enabled unless I need it I no longer use airplane mode and have not had any further problems --- so far ---
For me at least, the problem might be wifi related.
This happened to me this morning. I have my phone on charge every night and it probably hits 100% about 3am every morning. I have the alarm set at 7am to wake me, and has done every morning since I got it last month. However I have now slept in twice (this morning was catastrophic) due to waking up to find my phone was switched off and my alarm subsequently didnt sound!! I have wifi left on, but all my apps are closed down, and only the alarm app running.
To switch it back on I have to hold the down the power button for in between 5-10 seconds for it to reboot.
Does anyone know why this is happening? The Nexus 4 is perfect in every other way, I'm gutted to find a fault after raving so much about it!
Same thing is happening to me every night !
I have the same problem, but it happens sporadically, so I never know when I'm going to end up sleeping in. It's infuriating.
It just happened again this morning. I had Wi-Fi disabled, so I know it has nothing to do with that.
Tronno1 said:
I have the same problem, but it happens sporadically, so I never know when I'm going to end up sleeping in. It's infuriating.
It just happened again this morning. I had Wi-Fi disabled, so I know it has nothing to do with that.
Click to expand...
Click to collapse
Sounds like a rogue app is triggering the phone to crash or something?
Have you tried a factory reset?
This bs caused me to be late to a final exam... I was so mad when I woke up and saw that it was 2 hours later than the time my alarm was set to sound.. Only started happening with 4.4+ updates.
Sent from my Nexus 4 using xda app-developers app
Factory reset?
Sent from my Nexus 4, while driving in my Evo9.
Hey man,
My girlfriends nexus 4 did this as well and she got it RMA'd with no questions asked and a brand new one sent out, they told her to do a factory reset; this worked for a few days then went back to normal again.
- Sent from my Nexus 7
Charging cable
I have had this problem eventually with every android phone I've ever owned but it seems by replacing the charging cable with a new one the problem goes away. It seems that there is a weird thing with android where if the cable doesn't sit completely snug or straight the battery can charge but the phone won't realize this and go to sleep. Also seen the opposite happen where the phone thinks that the battery is charging and in fact it hasn't. When you unplug it suddenly goes from full charge to nothing. Haven't seen that last one on my Nexus 4 yet though. So I would try replacing the cable (not necessarily the charger) usually worked for me on other phones. Also I would suggest not to leave the phone and cable hanging off the end of a table. Make sure it's in enough that it sits flat. I think this is how I slightly bent mine.

Deep Sleep issues?

My phone has not been able to get into deep sleep. For the last few days that I've checked GSam, it's always been at 0s of deep sleep. Just checked right now and after 21 hours, my phone has gotten 10s of deep sleep. I've done a search and looked through many pages of posts on some of the various battery discussion threads but I haven't been able to find anything. Does anyone have a possible remedy for this or explanation of why it's happening? Is anyone else having trouble going into deep sleep?
Mines is the same, I assume it's because I charge my phone every night, which is really the only time my phone would sit still inactive long enough to actually enter doze.
I might of fixed my draining battery issue so maybe you guys can try it out too. My issue was my phone would not go to deep sleep and would stay awake even when the phones display was off so something was keeping it up. I tried all the different methods out there including the package disabler and doing the hard reset with the cache reset. I was browsing the developer options in the settings screen and looked at my running services. I noticed that my contacts and a. Program called com.qualcomm.location had a message next to them saying restarting while all the other programs just had a countdown of how long they were running. So I clicked on each and pressed stop and I also re-downloaded the package disabler and disabled the com.qualcomm.location. after all that I synced my contacts again and just did a simple reboot and after that my phone was able to deep sleep. Now my battery is not draining like it did. So in my case those 2 apps had an issue and kept trying to reset itself so the phone was never able to sleep. I would recommend looking at your running services in the developer options. go into the running services and see if anything is trying to restart itself over and over again
So I did finally achieve deep sleep. I tried a few things from the temporary battery fix thread and I wasn't able to pin point one thing which worked, THEN, I restarted my phone and it wouldn't go into deep sleep again. I tried wiping the cache and restarted and suddenly it's going into deep sleep again....
I'll keep an eye on it and will update if anything interesting happens.
I finally charged my phone prior to going to sleep and it finally did dose last night, the phone has to be stationary to enter deep sleep
Shuthefrontdoor said:
I finally charged my phone prior to going to sleep and it finally did dose last night, the phone has to be stationary to enter deep sleep
Click to expand...
Click to collapse
Doze and deep sleep seem to be too different things. My phone will sometimes doze without going into deep sleep. What's really weird is that sometimes my phone will randomly stop going into deep sleep and a clearing of the system cache immediately fixes this. There have been at least two times I can confirm I *only* did a cache wipe and the issue was remedied.
Does anyone have any idea why this is happening and why clearing the cache helps?
Anyone figure this out? Also is everyone on stock? Im rooted and on superman rom, this is happening to me every day now after i charge it over night. I have to restart my phone to fix.
yellowsn0w said:
Anyone figure this out? Also is everyone on stock? Im rooted and on superman rom, this is happening to me every day now after i charge it over night. I have to restart my phone to fix.
Click to expand...
Click to collapse
same for me on Galaxy s7 flat exynos sm-930f, no root, stock rom
very annoying
if you find a solution suitable for me (without root) please let me know
same here to me stock exynos s7 when plug off the charger in the morning have to restart the phone otherwise battery dies half day
I figured out that for my phone it defenitly is somehow connected to the fast-charging function.
When using the fast-charger the phone doesn't go into deepsleep anymore.
It happens as soon as the phone touches the fast-charger, it doesn't even need to fully charge for this to occur.
When charging with everything else, incl. Qi nothing happens, but as I said, after the fast-charger was connected - no deepsleep.
At least that's what I observed, no guarantee that this affects everybody.
Komaandy
It is the same issue that has been discussed for a while in "high android system battery drain" thread. Read up last few pages.
SM-G935W8 ?

Doze mode problems a OnePlus 5 issue or Nougat?

I'm not sure if my problem is with OxygenOS or Nougat, but I've scoured the internet for months and haven't found an answer
I have two problems that I think are linked to doze mode on my device, and they both occur under the same conditions. First is my alarm clock (Alarm Clock Xtreme) doesn't work in the morning, and second is my Samsung Gear Fit 2 needs manually reconnected each morning. And through troubleshooting I've determined the problem occurs under rather unique conditions. The problem ONLY occurs when my phone is plugged in and sits overnight (so fully charged sometime during the night). Which is most nights, because I want a full battery in the morning.
But if I happen to go to bed and leave the phone unplugged, the alarm clock WORKS in the morning and the smart watch stays connected all night. So unplugged overnight, no problems. Plugged in, alarm clock won't work and Bluetooth connection to smart watch is dropped.
I haven't been able to find an answer in the 3 months I've had my OnePlus 5. Any thoughts?
Specs: OnePlus 5, Oxygen OS 4.5.10, Nougat 7.1.1.
I can also move this post elsewhere if there is a more appropriate area of the forum for this question. But I don't have this problem with my old device.
You can try disabling battery optimization for selected apps.
doggie13_ said:
You can try disabling battery optimization for selected apps.
Click to expand...
Click to collapse
Thanks, but I already tried that. It doesn't work.
It's probably the apps man if you think about it. Try using a different application and report back.
Dchoi229 said:
It's probably the apps man if you think about it. Try using a different application and report back.
Click to expand...
Click to collapse
I actually had another alarm clock app before, that was doing the same thing. And I don't really have an alternate application for the watch.
I've researched this fairly extensively and have only been able to grasp small nuggets of insight. I did find one source on xda (but I can't remember where I saw it) that talked about doze mode acting funny when the phone is plugged in to charge. Basically an inability to wake from doze under certain circumstances.
Liam1694u said:
I actually had another alarm clock app before, that was doing the same thing. And I don't really have an alternate application for the watch.
I've researched this fairly extensively and have only been able to grasp small nuggets of insight. I did find one source on xda (but I can't remember where I saw it) that talked about doze mode acting funny when the phone is plugged in to charge. Basically an inability to wake from doze under certain circumstances.
Click to expand...
Click to collapse
You can always enable Developer Options and choose the option for the screen to stay awake while charging which should also keep your phone awake. You can also disable Doze completely in Developer Options.
jhs39 said:
You can always enable Developer Options and choose the option for the screen to stay awake while charging which should also keep your phone awake. You can also disable Doze completely in Developer Options.
Click to expand...
Click to collapse
Thanks! I don't want to disable doze, but I might try that other one. My other quick fix I juts thought of is to use a timer switch or smart switch to have the charger shut off after an hour. That's enough to give me a boost, but not fully charge. I tried it last night and everything worked this morning. Though my battery was only at 60%, it was better than nothing.
Liam1694u said:
Thanks! I don't want to disable doze, but I might try that other one. My other quick fix I juts thought of is to use a timer switch or smart switch to have the charger shut off after an hour. That's enough to give me a boost, but not fully charge. I tried it last night and everything worked this morning. Though my battery was only at 60%, it was better than nothing.
Click to expand...
Click to collapse
It's recommended these days to keep your battery charged between 40%—80% to prolong its life and not keep the phone plugged in overnight like in the old days. I charge mine to 80% before going to bed.
If it's actually a Doze issue I don't understand why it wouldn't happen when the phone isn't plugged in. Do you have a screen saver enabled?
Fellow OP5 user here, I have the EXACT same problem.
If I leave the phone charging for long time and doze kicks in, the phone basically shuts down for all purposes until I unlock it with my pattern. Meaning, only the built in alarm (that works even with the phone turned off) will work. Any other (Timely, radio...) won't.
Now here's the kicker: sometimes the deep sleep will cause a weird bootloop, upon which the screen will indefinitely hang on the spinning logo, with the screen turned on, requiring a reboot. And of course this makes the alarm not sound.
This last bit happens at random. If I disable the screen sleeping in Dev options, the alarm will work but when I wake up the pattern input screen would be there, after all night on, which isn't really healthy for the screen.
Turning doze off makes this problem apparently disappear, but I need to investigate some more to draw conclusions. For the time being I sleep without charging, quick charge and the phone's great battery makes it unnecessary to keep it connected all night.
Another fun tidbit of this deep sleep mode: it stops USB tethering. I would have imagined a wakelock in there, but apparently there isn't.
For information : I use vanilla kernel and OOS. I have Magisk on and Gravitybox via Xposed Magisk, but other than that I have nothing particular going on.
I've been hearing that from other sources as well, about not letting it sit overnight on the charger at 100%. Which is why I think I'm gonna keep using the smart switch of my nightstand charger. The OnePlus Dash charging system works great for a quick charge anyways, so having 100% fully charged to last all day long is no longer necessary. I have a normal USB cable at my night stand, so it's a slow charge. If I set the timer to stop after an hour it at least gives me a small charge overnight, without overdoing it. And I have dash charger at work to give me the full quick 20 minute charge that puts me at 60-70%.
No I don't have a screensaver running. It is weird that the phone locks in the doze mode for the alarm and boots me off my watch's BT connection, but only when plugged in and sitting at a full charge for an extended time (haven't stayed awake all night to test just how long it has to sit). But that IS what it IS. Those have been confirmed as the only conditions in which this problem arises. I've been using the smart switch for 3 days now to keep my phone from going to and staying at 100%, and the alarm clock is working again and the watch is staying connected.
It's not that it's a big of a deal for me to have to use a work around like this. I don't mind. But I hate finding a glitch in something and not being able to truly "fix" it. Work-arounds work. But they don't actually solve the problem. This is just a gripe I have in general whenever something like this happens. It's in my nature to want things to work properly. Which is why I haven't had a non-rooted device in at least 5 years. I NEED to have the ability to fix the [email protected]$$ sh1t the software developers and phone manufacturers screw up. Of course, that's probably the number one reason xda exist. This open up the full potential of these devices, because the manufacturers are either too dumb or are financially motivated to not fix things (ahem...Samsung). Thank you everyone who chimed in with advice. I appreciate it.
It has been my experience with this phone so far that doze mode doesn't work. At all. I regularly have widgets that won't update even though I have doze turned off...
Just one of the many annoyances that has me thinking about finally rooting and getting rid of this garbage os...

Categories

Resources