Related
I just noticed this morning that when I hit the power button the screen only dims now. I swear it used to shut off the display completely before today, and I know for certain that is how it worked on 1.6. This really is annoying, because now when I put it in my pocket the 3 buttons are constantly being depresses and they vibrate, which lights the display again. That coupled with this stupid lock screen that I have to try to open 3-4 times is really making me angry. Maybe it's just me thugh.....
I'm assuming you upgraded to 2.1?
I remember reading somewhere that someone had a similar issue after upgrading to 2.1 but then they re flashed 2.1 a different way and problem went away.
Same issue here, it really eats up my battery life, and I do end up pushing those soft keys all-too often... I am on 2.1 and that is definitely when the problem started, I'm going to try reflashing to see if I can eliminate the issue.
try the steps found here on streaksmart.com. She reports that she has no issues when its done that way. I don't have my streak yet but will follow these steps when i get it.
I had a similar problem before, only the screen would go off and on again and stay on!
Turns out it was an APP that done this.
It is possible an app is causing the problem.
Don't leave wifi on when not using and the problem disappears.
vatk said:
Don't leave wifi on when not using and the problem disappears.
Click to expand...
Click to collapse
+1
I've been experimenting with what's been causing this on mine, and I noticed that sometimes wifi will not shut all the way off. It hangs at "Turning off..."
So I tried not letting it sleep with wifi on, I turn it on if I need it, then turn it off (really a big pain in the butt) but went two days with no "no sleep" problems.
Today I tried leaving wifi on all the time, not two hours later it happened.
Since it's not happening to everybody, I wonder if it has something to do with our wifi setups. Maybe the router brand, or the encryption type, or something?
Last night I powered off the phone before better. I have wifi on all the time and I never shut it off. Today though, I have had no issues with the sleep function. It's still mid afternoon so we'll see if it continues this way. If so I will explore the wifi solution as well.
I was having this problem and somehow this setting was wrong:
SETTINGS>>APPLICATIONS>>DEVELOPMENT>>STAY AWAKE
mine was checked and we all know what that mean. Check yours to be sure if your not up for flashing again. Just a thought in case you overlooked this...
bhyde said:
I was having this problem and somehow this setting was wrong:
SETTINGS>>APPLICATIONS>>DEVELOPMENT>>STAY AWAKE
mine was checked and we all know what that mean. Check yours to be sure if your not up for flashing again. Just a thought in case you overlooked this...
Click to expand...
Click to collapse
Yes, it means the screen will not time out and go off when it's being charged, but you can still turn it off, and mine wasn't plugged in when I couldn't turn it off.
I don't think this is related to what I've been seeing, but thanks.
It seems that Bluetooth did it today. I was fine all day going black on sleep with power button, but once I switched on wireless to connect to my car stereo it never went off again. Even if I turn off the wireless I have to shut down and reboot.
jnovello said:
It seems that Bluetooth did it today. I was fine all day going black on sleep with power button, but once I switched on wireless to connect to my car stereo it never went off again. Even if I turn off the wireless I have to shut down and reboot.
Click to expand...
Click to collapse
Same here. Started car and it showed zero signal strength for the phone on the dashboard display. Pressed the power button on the Dell Streak and the car display then displayed the signal strength. From then on, the screen would dim but not shut off.
Pete
petesbodyparts said:
Same here. Started car and it showed zero signal strength for the phone on the dashboard display. Pressed the power button on the Dell Streak and the car display then displayed the signal strength. From then on, the screen would dim but not shut off.
Pete
Click to expand...
Click to collapse
Was your wifi also enabled (even if not connected to any AP's) when this happened?
a042349 said:
Was your wifi also enabled (even if not connected to any AP's) when this happened?
Click to expand...
Click to collapse
Yes, and I couldn't turn it off once the "screen dim bug" took hold. Today I've rebooted and left Bluetooth OFF and Wireless ON and have not had an issue all day long, and that's making calls, using 3G, wireless and running a pile of apps. I think I can live with no Bluetooth until the next release.
Pete
I don't think it's BT. I think it's wifi not recovering properly from sleep mode.
a042349 said:
I don't think it's BT. I think it's wifi not recovering properly from sleep mode.
Click to expand...
Click to collapse
Fair call. However, I've now had BT off for 6 hours and I'm using 3G, wireless and USB transfers and it hasn't hiccuped yet. This is the longest I've had with no screen dim bug.
I did notice that when I walked out to the car, the Streak could still "see" my home wireless network, then starting the car and the BT pairing and connecting is when the screen dim bug came back.
Maybe it's when both are run at the same time and both are connected/paired?
petesbodyparts said:
Fair call. However, I've now had BT off for 6 hours and I'm using 3G, wireless and USB transfers and it hasn't hiccuped yet. This is the longest I've had with no screen dim bug.
I did notice that when I walked out to the car, the Streak could still "see" my home wireless network, then starting the car and the BT pairing and connecting is when the screen dim bug came back.
Maybe it's when both are run at the same time and both are connected/paired?
Click to expand...
Click to collapse
I agree its looks like its a wifi issue. I always keep my bluetooth off and it still did it.
I got mine fixed... but the problem is i did a bunch of steps and now cant figure out which one actually fixed it. its been running great for 12hrs now.
What I did, since I noticed that wifi sometimes didn't sleep or wake itself up properly all the time (which i think is what's affecting our Streak sleeping), was turn off the wifi sleep. In other words when my device shuts off wifi stays active.
However, I then used "Tasker" from the Market and setup two profiles. When the screen goes off it shuts off 3G, wifi and autosync. Then when the screen comes on it turns on 3g/wifi, waits 20 secs and enables autosync (which then initiates a mail/calendar/contacts sync).
This has worked perfectly, and I get mad good battery life to boot. Now this means I don't get mail/updates (facebook, weather, etc - still get calls and txts obviously) but for me it's not a big deal especially for the battery life.
I may eventually setup more Tasker events to duplicate "Juice Defender" and poll every half hour (3G only, when screen is off only) to get my updates, but for now it's been working great.
I also setup profiles so if I'm not where I have wifi pairings it shuts down wifi. Also if it detects I'm connected via wifi (at home for instance) it disables my lock screen. I also have it set to only start GPS for apps that need it (Maps, Navigation, Places, etc) and that helps save battery too.
Tasker is an awesome app for $3.99. It has a steep learning curve, but there are enough walk-throughs available to teach you how to do the basics.
rebel146 said:
I agree its looks like its a wifi issue. I always keep my bluetooth off and it still did it.
I got mine fixed... but the problem is i did a bunch of steps and now cant figure out which one actually fixed it. its been running great for 12hrs now.
Click to expand...
Click to collapse
Found the fix on Modaco. Have a look at the last page of the thread called "2.1 Bugs ....., Add what you find please....."
I never knew there was an "Advanced" menu for WiFi!
yeah that is not it. I also have mine set to never time out so does that mean it will never shut off either? Anyway, it keeps happening through the day. Wifi and bluetooth do seem to have something to do with it, but I need them both on all the time so the only thing I can do is reboot. Then it is good for a couple hours. Are the any apps that have a reboot? That's one thing I miss on the iPhone.
Can you recommend an app or a mod which control wifi connection when the screen is off? I notice that if I enable wifi, I got 20% battery drop per a day, but I got 2% drop if I disabled wifi. Still, I like to have wifi on when I am using it, and clicking several time to enable wifi is quite irritating (relatively). So I thought there might be a good resolution to handle this my lazy problem.
I searched it on android market, and can find several. Can you recommend any one which will work well with NookTouch? I appreciate your inputs.
Same problem pal. But I also can't fix wifi not reconnecting when nook is up from sleep state issue. Suggestions?
I use the power widget that comes with ADW. I can turn WiFi on and off from my home screen with one tap.
Is it possible for it to be done automatically? Like on my smartphone? When wifi is turned on and my nook goes to sleep mode then when it wakes up wifi is off, in "disconnected" state.
I use the program Llama. It lets you set up all sorts of conditional changes for phones (similar to Tasker).
On my nook, I have one event trigger. When wifi turns on, Llama delays for 5 minutes, then turns wifi off.
It isn't exactly the same as turning off wifi when the screen turns off, but it helps me save battery. I currently have it send a notification to let me know it is turning off wifi, so I have the option to keep wifi on if I so choose.
Edit: Llama does have an event trigger for Screen Off, but I couldn't get it to work. Maybe the Nook doesn't turn off the screen in the way standard android phones do, so the trigger doesn't run.
Edit 2: I just realized you wanted one that turns wifi off when turning the screen of, then reconnects when turning the screen on. If Llama correctly detects the screen off/on triggers, you could set up two events, one to turn wifi off and one to turn it back on. I haven't gotten it to work, so maybe Llama isn't going to work for your particular needs.
sayno2quat said:
Edit 2: I just realized you wanted one that turns wifi off when turning the screen of, then reconnects when turning the screen on. If Llama correctly detects the screen off/on triggers, you could set up two events, one to turn wifi off and one to turn it back on. I haven't gotten it to work, so maybe Llama isn't going to work for your particular needs.
Click to expand...
Click to collapse
The NST is so heavily customized by B&N that you cannot rely on the "usual" events being triggered.
They only did what was necessary to save enough power and get the device to work and I don't blame them for that.
I'm pretty sure there's an event triggered that can be used for this particular task tho, if I get some spare time I might dig into it.
Well, I'm the impression, that my nook does that. I mean, when in sleeping mode - the WIFI is OFF. But when I awake the NOOK, wifi turns ON by it self and connect to internet. What I suspect, you might have the problem that other users experienced (including me) ... that you will have to change one file. Read more about it here.
I hope, this will help you.
Thx for all help !
Sent from my GT-I9100 using XDA App
In TorimuNooter I fixed the battery drain, pop on over to the TorimuNooter thread. The latest version (Ver 0.3) was just uploaded today!
Sent from my NOOK using XDA App
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.
My screen randomly turns on and sits at the lock screen for a few seconds for no apparent reason. There are no pending notifications, etc. I assume there might be a rogue app causing this, but I don't have that many installed and even less apps doing any background tasks. Any idea on how to find the culprit?
I found this bug report where some apps are mentioned, but I'm not running any of them.
https://code.google.com/p/android/issues/detail?id=39625
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
I noticed that the phone wakes up whenever it reconnects to Wi-Fi. I was changing some router settings last night and I constantly saw the phone waking up shortly after the router rebooted. However, this is not the only scenario where it does it.
Mine has done the same, no idea why, only seen it the once, but it certainly happened, sitting three feet away from me, and suddenly Bingo! its on.
Mine wakes every few minutes. Certain apps (tasker, facebook etc) and syncing seem to cause it to happen more often but even if I disable most apps it still happens. I've been unable to identify the source with better battery stats. It happens bone stock and on CM10.1. I'm still getting better battery life than my GNexus but it's maddening.
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
ludovicien said:
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
Click to expand...
Click to collapse
So my Nexus 4 doesn't want to go to sleep.
- I have sleep set to 15 seconds
- Dream is off (just in case)
It just stays on. It doesn't matter if it's on the the lock screen or at the home screen. I'm guessing some app is keeping it awake. It just started last night, but I don't think I have installed any new apps. Maybe it from an update.
solved
My phone's screen also used to wake up randomly. it was very annoying, especially at midnight
finally, I found out the reason by using "Wakelock detector" app which is freely available in market.
here is XDA thread about WLD: WLD at XDA Thread
the cause of problem was ad Notification, it was holding "full wakelock" (you can see it in screenshot)
good Luck!
Refer Wakelock Detector at XDA
Ramdom screen wake up issue solved
Dear all,
I was experiencing random screen wake issue in my XOLO PLAY smartphone.
The problem was with the AppLock software. After upate is this issue appreard. Earlier AppLock was there and no issue was experienced.
I am writing to AppLock team to fix the bug.
:angel:
All the best
Regards
nitin5062
hcedillo said:
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
Click to expand...
Click to collapse
U made an account to post THIS only?
Been using NC with CM7 for over a year plus. Never any problems - until today. I haven't messed with any base settings for at least three months. The Nuance Swype and Dragon Trial app ran out today - the only thing that I messed with.
Was using it this afternoon on Google+ just cruising around. I put the NC down for about 20 minutes for an errand. Came back and I can't wake it up through the usual press of the "N". Long Press the N - no luck. Tap the Power button - no help. The only thing I could think to do was press and hold the Power button - nothing happened. Long press Power for about 15 seconds and I saw the screen flicker and the Cyanogen Mod green icon appear - like a normal start up. So the desktop arrives and I note that the Wi-Fi is turned off. Usually I have it set to autoconnect to my house router which it has faithfully done since forever. But Wi-Fi is turned off. I clicked it on and after a brief moment I see "Connecting..." up at the top of Wi-Fi Settings but every Access Point including the house router is "Not in Range". Eventually "Connecting..." turns into "Disconnected". Turn Wi-Fi off and then back on. No difference. I think that whatever caused the blowout earlier this afternoon has left the NC wi-fi system in some sort of in-between state.
Later on as I was working with this, I got up to answer the phone, came back and it's shut off again. I was able to re-engage it twice more after pressing this n' that trying to wake the Wi-Fi up. Once engaged it's fine. But as soon as you power down (or it blows up like earlier), Wi-Fi is disonnected, turned off and very hard to re-establish. Incidentally, all other Android devices, tablet, phones in the house off that router work just fine so I don't think it's a matter of a router issue.
Question: Is there a way to "reset" the Wi-Fi functions in the NC? I'm thinking some sort of hard reset is needed but I'm not sure.
Question: What would be my next step to figure out what is causing the unwanted shut down?
Thanks folks. If you need more info, I'm going to be around and will stay on top of this thread.
Hoibb
First that 'unwanted shutdown' is called SOD, Screen of Death. Very common with some devices and combination of apps. Do a little searching on that and you will get overwhelmed with info. Since you were not having it before, it must have something to do with that app or apps that you had to adjust recently. It is tied in with deep sleep and wifi.
Have you tried just forgetting the routers in your wifi list?
Edit: I just reread your post. How long have you had Google + installed? Did you recently just update that?
Edit2: Fortunately, for CM7 there is a patch that fixes SOD. If you want it, I can post a link.
Edit3: Here. Flash this with CWM. It will replace your wifi driver with a patched one that resists SOD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Thank you and...
Lots of good information here. Google+ has been installed for at leat 6-9 months that I can recall. I could uninstall and reinstall, I guess. But...
It's seemed to have righted itself two days ago, so I haven't had a problem - until...
Last evening. I was doing some eMail using K-9 plus floating through Google+. And I put it down to go do something. Came back and it's still working (pulled up the desktop by clicking the "N") but the Wi-Fi is shut off again. Went to Wireless and Network Settings and what I see is "Wi-Fi" sitting on the words "Turning off...". Everything beneath it is greyed out. Decided to just leave it and see. Half hour or so later, it's still in a state of "Turning off...". I backed all the way out and did a restart. On restart, Wi-Fi is turned off so I hit the box to turn it on, it obeyed and went directly to my home router, signed in and I'm back on again.
As the evening progressed, what I got in the habit of doing is short-pressing the Power button to turn off the screen. I found I could reliably come back, wake it up and the Wi-Fi would start back up again on its own without intervention.
So until I get a chance to sort out all the stuff you gave me to do/patch, I'll try to just manually "sleep" the system. I have to study up more on what you said because the terminology and procedures, while probably very clear to most, are not exactly clear to me.
Thanks again for the info.
Hoib
leapinlar said:
First that 'unwanted shutdown' is called SOD, Screen of Death. Very common with some devices and combination of apps. Do a little searching on that and you will get overwhelmed with info. Since you were not having it before, it must have something to do with that app or apps that you had to adjust recently. It is tied in with deep sleep and wifi.
Have you tried just forgetting the routers in your wifi list?
Edit: I just reread your post. How long have you had Google + installed? Did you recently just update that?
Edit2: Fortunately, for CM7 there is a patch that fixes SOD. If you want it, I can post a link.
Edit3: Here. Flash this with CWM. It will replace your wifi driver with a patched one that resists SOD.
Sent from my Nook HD+ running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
@leapin. I should have come back to post add info. My apologies. I believe I was able to resolve this a bit later. I looked at Juice Defender (free) and what it does. I uninstalled it. As soon as I did that, I suffered no more of these SOD problems. Been running great since June.
So was this the real SOD? Or was it Juice Defender setting the power profile in such a way that the Wi-Fi never got the signal to reawaken? What do you think?
Hoibb
Hoibb said:
@leapin. I should have come back to post add info. My apologies. I believe I was able to resolve this a bit later. I looked at Juice Defender (free) and what it does. I uninstalled it. As soon as I did that, I suffered no more of these SOD problems. Been running great since June.
So was this the real SOD? Or was it Juice Defender setting the power profile in such a way that the Wi-Fi never got the signal to reawaken? What do you think?
Hoibb
Click to expand...
Click to collapse
It could have been the real SOD being triggered by Juice Defender. Usually it is some app that triggers it (trying to use wifi while the device is in deep sleep), but the underlying problem is SOD. Some folks never experience an SOD.
Sent from my Nook HD+ running CM10.1 on emmc.