Database Users

sleep of death

I'm now on my third nexus 7 and in general absolutely love the device but I'm getting fed up with the issues.
My first device suffered from sever flickering, the second had the backlight bleed and now the third refuses to wake after the screen is turned off about fifty percent of the time.
This is not the same issue as people are reporting in other posts as the charger is never connected when I have a problem. It doesn't matter if the screen times out or if I press the power button to after I finish using the device.
I'm using the stock ROM (with the 4.1.1 update), no root and have only installed the kindel app so its about as vanilla as can be.
The second nexus I had did this once but I had already organised the return and didn't think much of it.
Anyone else having similar issues or able to recommended a fix as this nexus is perfect in every other way?

Factory reset, leave it that way for a while, does it happen? If no, then you probably have an app doing something wonky.

Turn off automatic backlight, manually set it to around 40% and see if the flicker and the "SOD" goes away.

As the poster above said, turn off automatic brightness and see if that fixes it.

Nospin said:
As the poster above said, turn off automatic brightness and see if that fixes it.
Click to expand...
Click to collapse
Automatic brightness is on my N7 (and other devices) 100% of the time... No SOD problems here.

lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.

THANKS!
Just got my first nexus 7 yesterday and after pretty much falling in love, was dismayed about the unexplained black outs for no apparent reason. Could not wake up the device afterward without holding down the power key for 10 sec then leaving it alone for a while.
After reading your post, I realized that the incidents occurred after switching from manual to automatic brightness in a dimly lit room, followed by mysterious recoveries when moving to brighter room. I will monitor, but hope for the best. (Will probably just use manual settings as I found the automatic mode to be too dim in all settings anyway - old eyes!)
I am already pretty raw on this point as I just spent the last 10 years or so with a laptop that would not wake up from sleep, and just learned to live with it after wasting SO much time trying to get to the bottom of it. If you have saved me from that, or from having to exchange the n7, I owe you big time. Thanks again!
Compusmurf said:
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
Click to expand...
Click to collapse

did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying

seven2099 said:
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
Click to expand...
Click to collapse
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back

seven2099 said:
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
Click to expand...
Click to collapse
i have similar issue with forced sleep, it cannot waken sometimes. TnT
anyone can help?

Further investigation shows this has nothing to do with brightness and that all tablets with this issue should be returned/exchanged immediately.
Quick google search will allow you to find that comes directly from Asus support.
Total fail, asus ftl

new tab rendered more quality issues. opened it at the shop, returned it immediately and went samsung.
Asus will always be asus.. too bad cuz my tf300 was pretty decent in terms of quality, just had wierd screen lift and squeecky issues.
Galaxy Tab 2.0 7inch is a much better choice now.

I have exactly the same problem with my current device. About 30% of the time, the power button would just stop working so I couldn't turn the unit on or off, unless I plugged it in to the charger. It didn't turn on for a full day once so I did a full factory reset which included re-flashing the stock rom and the problem persisted, the button would still not work! So I packaged it up for return and left it sitting for a couple of days. Just before I went to post it, I checked that the issue remained and to my surprise it turned itself back on again! I kept it and since then, it has only happened once.
I do intend to return it though, but only when I hear Asus are shipping units which are built properly. Clearly a hardware issue but pretty weird since it seems random and is not reproducible by any means I know of.

I am experiencing a similar issue. Does setting a manual brightness fix the issue?

It is my 3rd Nexus now with exactly the same problem.
I found out that the Nexus is in APX-mode (NVFlash) when it's in this state (SoD). Windows tries to install a APX driver when it is connected via USB.
The problem occured always with 16GB Nexus. A friends 8GB works fine.
Nexus 7 (C9) - Stock Rom 4.1.2. - locked - not rooted

Turning off the auto-brightness fixed the issue for me. Minor workaround to a major problem.

Always on display no longer moves around

From the box, the always on display (AOD) shifted around every minute or so to prevent burn in.
Two days ago I installed the T-Mobile update for my s7 edge. Last night, I was trying out my new wireless charger when I noticed the AOD no longer moves around. I tried charging directly, rebooting, powering off, changing themes/styles to see if it would start shifting around.
Did the update cause this change? Is anybody experiencing the same thing? Is this a bug or intentional (didn't see anything in patch notes). Thank for any input.
I love the AOD but now super paranoid about burn in.

Have you tried turning AOD off, waiting a bit, and turning it back on? Maybe reboot while it's off, then turn it back on.

Yeah, reports circulating that the T-Mobile update is causing the AOD to remain stationary. If you're on T-Mobile, definitely turn off AOD until they release a fix.

Yea I've tried disabling AOD and rebooting but it's still stationary. I went ahead and disabled it entirely and hoping a fix will be released soon. Thanks all.

Damn, disabled mine until it's fixed. Didn't even notice, thanks.
Sent Via My Samsung S7 Edge

Is it dimmed more like the night clock mode? I was thinking maybe they did that and figured it's not a problem any more, but just guessing. I have Verizon version and I jist use the night clock mode all time as the regular clock seems too bright.

hp79 said:
Is it dimmed more like the night clock mode? I was thinking maybe they did that and figured it's not a problem any more, but just guessing. I have Verizon version and I jist use the night clock mode all time as the regular clock seems too bright.
Click to expand...
Click to collapse
The brightness of the AOD is still determined by ambient lighting. The only time the AOD moves to a different position now is when I power up the screen then lock it. If I don't power up the screen, it will stay in that same position with auto brightness in effect.

DNx714 said:
The brightness of the AOD is still determined by ambient lighting. The only time the AOD moves to a different position now is when I power up the screen then lock it. If I don't power up the screen, it will stay in that same position with auto brightness in effect.
Click to expand...
Click to collapse
Yeah, definitely must be a bug then.
I'm annoyed of the Night Clock where it shows the time of an alarm that's set out few days out. I now disabled all alarms so I don't see that. lol.
Also, the stupid + sign on the icon groups in TouchWiz is really awkward and wastes so much space. They didn't have this in Galaxy S6.

Had this issue on a Fresh install (Not present on the Same Version previously (I rolled back after a upgrade)
My default was stuck in the middle and did not move, I went in and change the clock style to the round clock and hands, and mine is moving around the screen as normal

Note 4 Power Saving automatically turns off

Hi guys,
Having an issue with my Note 4 (SM-N910F) international version since the MM 6.0.1 update. I received a further update after the MM 6.0.1 recently and thought the issue would've been fixed but alas, no!
Current version of Software: N910FXXS1DPE7.
Issue is, I have power saving mode turned on and set to: Start power saving "Immediately". However it keeps getting turned off and the screen becomes bright and I could not recognise a pattern how this occurs.
Things tried so far:
-Unticked automatic brightness and dragged all the way to low.
-Smart stay was/is never ticked.
-Auto adjust screen tone is ticked, but unticking that and also leaving automatic brightness turned off still causing power saving to automatically turn off.
-I have tried to check for this issue in Safe mode and it still happens.
Any ideas of what could be causing this? I do not want to do a factor reset for this issue and if it can be avoided after all. Safe mode is somewhat similar isn't it?
I have noticed the issue occur when I start using Gmail app (not the Inbox one), but that is just one scenario.
It seems like the light sensor gets triggered when it faces bright light and turns off power saving mode and screen becomes bright, but just could be a red herring.
Thanks a million!
Bharath

corpuscallosum said:
Hi guys,
Having an issue with my Note 4 (SM-N910F) international version since the MM 6.0.1 update. I received a further update after the MM 6.0.1 recently and thought the issue would've been fixed but alas, no!
Current version of Software: N910FXXS1DPE7.
Issue is, I have power saving mode turned on and set to: Start power saving "Immediately". However it keeps getting turned off and the screen becomes bright and I could not recognise a pattern how this occurs.
Things tried so far:
-Unticked automatic brightness and dragged all the way to low.
-Smart stay was/is never ticked.
-Auto adjust screen tone is ticked, but unticking that and also leaving automatic brightness turned off still causing power saving to automatically turn off.
-I have tried to check for this issue in Safe mode and it still happens.
Any ideas of what could be causing this? I do not want to do a factor reset for this issue and if it can be avoided after all. Safe mode is somewhat similar isn't it?
I have noticed the issue occur when I start using Gmail app (not the Inbox one), but that is just one scenario.
It seems like the light sensor gets triggered when it faces bright light and turns off power saving mode and screen becomes bright, but just could be a red herring.
Thanks a million!
Bharath
Click to expand...
Click to collapse
I have just one problem like yours. When i receive Marshmallow i just update. But Power Saving turns off every reboot. Just back to factory settings and make your wipes. I solve this with wipes and factory.

Tavok said:
I have just one problem like yours. When i receive Marshmallow i just update. But Power Saving turns off every reboot. Just back to factory settings and make your wipes. I solve this with wipes and factory.
Click to expand...
Click to collapse
Thanks. Yeah I am trying to avoid factory reset because can't go thorugh the process of installing apps, setting up all the various accounts etc especially since there is no built in fully restorable backup feature. Family man with kids and have enough IT stuff to do at work.
I'm on stock/non-rooted device also. And this will be my last Samung device, if not the last Android!

I understand you very well. You can use HELIUM apk to make your nandroid backups without root and make easier this tedious work. I don't have rooted my phone but helium makes all faster that, and i use also wondershare mobile go for android and PC.
I hope this helps you and you can resolve your problem. Good luck and regards from Switzerland - (Mexico)

Tavok said:
I understand you very well. You can use HELIUM apk to make your nandroid backups without root and make easier this tedious work. I don't have rooted my phone but helium makes all faster that, and i use also wondershare mobile go for android and PC.
I hope this helps you and you can resolve your problem. Good luck and regards from Switzerland - (Mexico)
Click to expand...
Click to collapse
Thanks Tavok. I did download Helium and wanted to test it out, however my phone is now staying in Power Saving mode since a few days! I have done nothing new, didn't uninstall any app or change any settings as such for it to work. This is bugging me because I want to know what fixed it so that I can re-apply the fix again if need be.
I've also read that some people are complaining about Note 4 getting stuck in Power Saving mode and I hope this is not the case with mine, now that it seems to work as expected.
I will update this thread once I check it out further.

I found out how this power saving mode gets turned off. It is the Location settings. If location is off, the power saving mode stays on (this is what it was set to hence I didn't see the issue happening). But when I changed it back to High accuracy, I started to notice the power saving getting turned off from time to time when using certain applications that require Location accuracy.
This is a bug since the MM update!!
Any ideas how to use Location accuracy and still retain Power saving mode?

I did a factory reset and the issue persisted! I tried various location settings(of the 3 choices) asks none of them helped. When set to any one of them power saving automatically turns off after a while I.e. when location needs to be detected. The only workaround us to turnoff location altogether but that messes with the auto sync of accounts! Grrrrrrrr

I verified with Samsung Tech Support that Location and Power Saving are incompatible on the Galaxy Note 4, even with the latest Android version available for the device (6.0.1) . In other words, Turning on Location while Power Saving is active will disable Power Saving after a short period. Fortunately, the problem is fixed on later devices.

S8 auto brightness issue

Hi, two days ago I did an update to AQG5, since that, I have issue with auto dimming screen. When I get into light conditions, my screen gets quickly very bright, but then when I get into dark room, it's stays bright, or dimm very slowly and takes about 1 min to be at right settings. Is anyone facing the same issue? Before update everything was fine and quick.
Sent from my SM-G950F using Tapatalk

Its a know issue in the last update.

I seem to have the same problem. Where can I read that its a known issue of this firmware? thanks.

I tested my US Unlocked Model G950U1 with the firmware update that came out yesterday, and it does not have the Auto brightness dimming bug. So it must be only on certain S8 models with their particular firmware.https://forum.xda-developers.com/galaxy-s8/help/software-updateaqg2-unlocked-s8-t3648073

Auto Brightness issues

I have the Galaxy S8+ on Sprint as well as my gf. We are on the latest update on Sprint and the auto brightness on both phones doesn't work anymore. Does anyone else have this issue?

yes its a bug...last update not fix it completely

Always found that auto brightness was a battery suck. I've never had problems with setting it to 50% and being able to see it while indoors or out. Checking your phone at 3am with 50%, however, might blind you though.

I was having trouble since the update a couple of days ago. I just found a link that walked me through calibrating the sensors again, which seems to have done the trick. I'll keep an eye on it and update if there are any changes, but hopefully that takes care of it for you too! PM me if you'd like the link, as I am unable to post it because I have not been active enough on XDA.

This could help
https://recomhub.com/blog/galaxy-s8-and-galaxy-s8-plus-how-to-calibrate-auto-brightness/

Sorta.... Not really.... No
This partially..... No, with this, it's all or nothing. I've tried this in a pitch black room to set the low light. When I flip the might on, set it to maximum and switch auto brightness on, everything appears fine. When I flip the might off again thing into complete darkness, the auto brightness does not return to the lowest setting. It stops at approximately 15-20%.
Thanks for the resource, but a different calibration method must be used to restore true accuracy. There was absolutely nothing wrong with it before, but leave it to Samsung to mess with something in good working order and which no one asked to be "fixed."