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.
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
I noticed this about a week ago. When I unlock my phone, after a second or two the screen dims then brightens back up. Adaptive brightness is off. I'd been messing with screen calibration around the same time, and I was a little afraid it was caused by something I had tweaked.
It followed me across multiple ROMs, very thorough wipes, and even a full fastboot restore. I was beginning to worry it was some kind of hardware problem.
Eventually I figured out the brightness ducking was caused by a new option in the Naptime app. The current version of Naptime has a disable motion detection option that older versions didn't have. When I have that option enabled my screen brightness ducks on every unlock.
I thought I'd post it here in case it affects anyone else. Would have saved me a lot of aggravation and needless messing with my phone.
I face this sometimes in the YouTube app.
I tried looking everywhere but was unable to find a solution so maybe someone here knows what's going on. I have the blue light filter set to turn on and off via sunset/sunrise. However, when I leave it like this the filter turns on at 6:20pm everyday without fail. I don't know when it turns off but I assume it is in the early hours of the morning when I am asleep. I can set it to a manual time and that works fine, but I don't want to keep changing it every week for the rest of my life...
I have location setting turned on - I never turn location off. I'm not sure why it is stuck at 6:20pm, so any help would be appreciated!
Hi guys, I'm having this problem for about 4 months, every time I turn on the auto brightness it goes to max, even when is super dark in my room, it started after I first unlocked the bootloader, only after I done that, the problem appeard.
I tried to lock the bootloader to see if doing that would revert de situation, but no success!
I've tried multiple costum rom's, I even went back to miui 10, but nothing would revert the situation!
Any ideas that could solve this problem?
if on miui then use code to get to service menu and test sensors
yaro666 said:
if on miui then use code to get to service menu and test sensors
Click to expand...
Click to collapse
I've done that, the sensor seems to work fine, with no light it stays on 0 and when I turn on the light it goes to the max, but on the miui it's always on the max brightness, even if I put it on minimum manually with auto brightness on, it still shoots to maximum brightness