It seems when ever i set it down and look back at it its restarting. I cannot figure out why this is happening.
Any suggestions?
Sent from my Nook Color.
Your nook may be trying to do the 1.0.1 software update? Did you turn off the ota update?
It has something to do with the way the BN software shuts off the Wifi when the screen turns off. The work-around for this is to install Settings Profile Life and set a profile to turn off Wifi when the screen turns off.
Sent from my Nook Color.
I have this happen when I use Pulse. Not sure why. I can read a book for hours and have no issues. I bring up Pulse for a while and it reboots after about 5 minutes.
Related
My rooted nook screen keeps turning off while charging, and I can't find the setting to disable it. I have it configured so wi-fi turns on and off with the screen, and sometimes I'd like wifi on in the background to download or do other things. The only way I can do that now is to remember to keep touching the screen every few minutes.
Any help?
I use a widget from the market called Screen ON widget. Just have to tap it to keep screen on. Works great.
Sent from my hacked nook color.
There's an app called 'Setting Profiles' which works well for this situation. The free version allows just one rule which should be fine if this is all you need it for.
Thanks for the response guys. I actually do use Setting profiles, which is what I use to turn the wifi on and off with the screen. I just haven't figured out how to configure it to keep the screen on.
I searched for 'Screen on widget', but I got 3000 hits, and couldn't find it.
Since Sprint is going to try and screw me big time if I get a new phone, I've decided to see what new life I could put into my old Touch Diamond (DIA500). I installed XDAndroid FRX05, and it seems to be working really well, with a few exceptions. One of the first things I tried was to enable Bluetooth. What happens is that it enables, but about 4 seconds after being enabled, it says it's shutting down, then it starts back up, and shuts down. It keeps doing this forever, until I turn it off. Now that I tried Wifi, it does the exact same thing. I've rebooted a few times, and took the battery out once, but still nothing. I've since installed a battery-saving program, but this happened on a fresh install.
The next issue is with the backlight. If I try and change the brightness, it changes for a second, then goes back to the brightness it was. It does this whether I turn the brightness up or down. It's not set to auto.
The third issue is the GPS. It works, but seems to take a long time to get a lock. Under WM, I'd have some kind of location within seconds, even inside. I'm guessing it was using the phone network to speed things up. Under android, it takes a few minutes sometimes, and it's worse inside.
I also had a nightmare calibrating the screen. It's still a little off, but it works. Does anyone know a screen calibration program that would work?
Any ideas?
Thanks!
To solve the brightness problem. Boot WinMo and turn off auto brightness there. That will solve that problem.
Thanks for share you knowledge here DA01
I noticed people are using power management apps to "fix" the SOD in CM7.1. I use green power myself, and it works great. Stopped my SOD's completely.
I ran across this thread to fix a wifi off at screen off issue. http://forum.xda-developers.com/showthread.php?t=774507
It seems the default wifi off at screen off is timed at 15 minutes after the screen turns off. If we could have an option under cyanogen settings, or advaced wifi settings, to change this timer to just a few seconds, I think it could temporarilly fix many of the SOD problems, until the real culprit is found. I know Dalingrin said he would get to the SOD problem after a couple of other projects, but maybe this could be a temporary fix until he really gets into it.
I would have put this under the developers thread, but I read a lot, and post a little.
What do you think?
jameshmiller said:
I noticed people are using power management apps to "fix" the SOD in CM7.1. I use green power myself, and it works great. Stopped my SOD's completely.
I ran across this thread to fix a wifi off at screen off issue. http://forum.xda-developers.com/showthread.php?t=774507
It seems the default wifi off at screen off is timed at 15 minutes after the screen turns off. If we could have an option under cyanogen settings, or advaced wifi settings, to change this timer to just a few seconds, I think it could temporarilly fix many of the SOD problems, until the real culprit is found. I know Dalingrin said he would get to the SOD problem after a couple of other projects, but maybe this could be a temporary fix until he really gets into it.
I would have put this under the developers thread, but I read a lot, and post a little.
What do you think?
Click to expand...
Click to collapse
Just use Setting Profile Lite or Tasker or whatever to turn off wifi at screen off and back on when it's back on. Doesn't seem like adding a setting in CM7 to set the length of time is worth it.
This is the part I'm not quite following...the behavior you're describing (wifi off with screen and on with screen) is actually the CM7 default, so why the need for a special app?
Rodney
I haven't looked at these 3rd party apps yet but I don't believe shortening the wifi sleep timeout would help. I believe the reason these apps prevent SODs is because they forcibly turn off the wifi after some time. There seems to be some condition that the wifi driver or wpa supplicant gets locked and the sleep timeout has no effect.
What is the default time period before wifi turns off when the screen turns off?
I am noticing people in the various SOD threads having success stopping their SOD's with third party software that does what the advanced wifi setting "should" do, cuts the wifi off when the screen turns off. I am using "green power" and set it to turn off wifi 5 seconds after the screen turns off, unless there is traffic. I have not had an SOD since. The thread I linked to says the default android time period for wifi off is 15 minutes.
Maybe, just maybe, SOD's are occurring in this 15 minute time period. That's why people are having success with these 3rd party apps.
This was a reply to rhester72. I should have quoted.
Dalingrin, Did you happen to read the thread I linked to? It may be of some use to you. It may not. It may not pertain to your kernel.
I'm no Dev, just someone that appreciates the work you do, and am trying to help.
Well, I guess I learned something. WiFi off when screen turns off, in the advanced wireless setting, does not actually turn the WiFi off. It only puts it to sleep.
The third party apps that turn WiFi off when screen turns off, actually turn the WiFi off. That's why they "fix" SOD.
I'm still curious as to the default WiFi off/sleep when screen turns off timer is. Just for knowledge sake.
Thanks again, to all of the Devs, for all of your hard work.
Well, interestingly enough, I updated from n150 to n157 last night and this morning after disconnecting from power (with wifi set to never sleep when plugged in), about 5 minutes later I had my first SOD in a *long* time. Not running any special power-management apps.
Rodney
rhester72 said:
This is the part I'm not quite following...the behavior you're describing (wifi off with screen and on with screen) is actually the CM7 default, so why the need for a special app?
Click to expand...
Click to collapse
My NC hasn't had a single SOD since selecting the option to turn wifi off when screen is off. Surely, unless you need notifications while the NC is in sleep, this is the simple solution to SOD?
CM7 #150
Having a problem with the lock screen in CM10.1 that is happening more frequently.
It seems it happens after I open the case lid and the Nook HD+ wakes up. I use pattern lock (but it's happened in the swipe lock also), and for a moment, it looks like it's unlocked. The desktop or app that was up when it went to sleep is there, but only for about 1 second. It goes right back to the lock screen. It repeats over and over. At first, I thought only a reboot would fix it and allow me to unlock it, but I found if I hit the power button to put it to sleep and wake it up, it typically unlocks. Sometimes it might need me trying that a couple of times, but it usually works.
Ideas? Anyone else having a problem unlocking after sleep? So far, I'm not sure if it's just lid-induced sleep or if it would happen after I use the power button to sleep it.
Again, it doesn't happen all the time, but i'm finding it happen more frequently.
Thanks!
lancorp said:
Having a problem with the lock screen in CM10.1 that is happening more frequently.
It seems it happens after I open the case lid and the Nook HD+ wakes up. I use pattern lock (but it's happened in the swipe lock also), and for a moment, it looks like it's unlocked. The desktop or app that was up when it went to sleep is there, but only for about 1 second. It goes right back to the lock screen. It repeats over and over. At first, I thought only a reboot would fix it and allow me to unlock it, but I found if I hit the power button to put it to sleep and wake it up, it typically unlocks. Sometimes it might need me trying that a couple of times, but it usually works.
Ideas? Anyone else having a problem unlocking after sleep? So far, I'm not sure if it's just lid-induced sleep or if it would happen after I use the power button to sleep it.
Again, it doesn't happen all the time, but i'm finding it happen more frequently.
Thanks!
Click to expand...
Click to collapse
I have heard about this problem from several people, but usually it is on an HD+ with the cover that wakes up the tablet. However, I just experienced this a few minutes ago and my Nook has never had a case on it, let alone one that wakes it.
It happened when waking it with the n button but after turning off the screen with the power button and back on with the power button, it worked. (not turning off the Nook, just screen off and back on)
So it appears that it is not only the magnetic wake up that causes the issue.
Sent from my nook HD+ running cm10.1 on emmc from Tapatalk HD
Mine does that too. I thought it was a hardware defect, but I tried another one and it does exactly the same thing.
So far it's only happened with a case-induced wake for me. It happens regardless of whether I sleep it using the case or the power switch.
The lockscreen loop stops if I sleep/wake it using the cover consistently, but it doesn't go away if I sleep/wake it using the power switch, oddly.
same problem with no known solution
lancorp said:
Having a problem with the lock screen in CM10.1 that is happening more frequently.
It seems it happens after I open the case lid and the Nook HD+ wakes up. I use pattern lock (but it's happened in the swipe lock also), and for a moment, it looks like it's unlocked. The desktop or app that was up when it went to sleep is there, but only for about 1 second. It goes right back to the lock screen. It repeats over and over. At first, I thought only a reboot would fix it and allow me to unlock it, but I found if I hit the power button to put it to sleep and wake it up, it typically unlocks. Sometimes it might need me trying that a couple of times, but it usually works.
Ideas? Anyone else having a problem unlocking after sleep? So far, I'm not sure if it's just lid-induced sleep or if it would happen after I use the power button to sleep it.
Again, it doesn't happen all the time, but i'm finding it happen more frequently.
Thanks!
Click to expand...
Click to collapse
I have the same problem and no solution. I wonder if a newer release of CM would help.
Also, in regards to temporary coping, when this problem appears is there a method (besides reset) to deal with the problem. I noticed that sometimes I can eventually get past the lockscreen without restarting, but I'm not sure what causes that. The best solution I have for my wife at this point is I delayed locking-after-sleep to 30 minutes.
Two-user set-up (my wife and me). I am fairly new to the scene--first time I ever loaded CM on any device. I recently bought the HD+ from Best Buy for $150. I tried to follow the verbatim instructions from e.mote titled "[NOOK HD/HD+] Installing CyanogenMod 10.1 for Dummies." I haven't used custom ROMs much since my heady days with my Palm Pre.
I'm in the same boat. Hd+ running CM 10.1.3. I wonder if this still happens on the 10.2 builds...
While on 10.1 this happened to me every time after charging (well, maybe not every time, but that's when it happened...), but if I just turned off screen and then back on I was fine until next charging.
I put on 10.2 earlier today (from Iamafanof site, so not from here). Will be interesting to see if the problem is till there, but I won't know tat for a while yet.
Nook HD problems waking up
asawi said:
While on 10.1 this happened to me every time after charging (well, maybe not every time, but that's when it happened...), but if I just turned off screen and then back on I was fine until next charging.
I put on 10.2 earlier today (from Iamafanof site, so not from here). Will be interesting to see if the problem is till there, but I won't know tat for a while yet.
Click to expand...
Click to collapse
Im seeing this on both 10.1 and 10.2 on my nook HD no cover.
I'm seeing this even without a lock screen. The screen turns on for a second, after that turns off. After many tries it works or after a restart. With lock screen it is the same as above.
Happend on CM 10.1 and CM 10.2 with a cover
So there's no solution to this problem and you just have to reboot it?
You just close and open the cover again
Sent from my rooted GS3 running CM11
oboefiend said:
You just close and open the cover again
Sent from my rooted GS3 running CM11
Click to expand...
Click to collapse
I'll try that again but I don't think it worked.
I have been having the same issue as well with mine. Just curious if really has been a solution to this?
No it is a hardware issue. There are two options close and reopen cover or cut magnets out and turn on manually. I don't think anyone has tried more powerful magnets if you want to test that it would be helpful.
Sent from my SPH-L900 using XDA Free mobile app
I kinow its an old thread, but I Fixed it by closing and opening the magnetic cover, rather than using the power/off/on screen button and it worked.
Only fix is to do one of three things. Remove the magnet from the cover, remove the cover is self, disable the lock screen. It's because the cover and lock screen confuse each other and it has the cover wake it, then the lock screen sleep it, then it sticks. It's very well known, and nothing to panic over, just really freaking annoying.
I have the same problem as others that sometimes after sleeping with the magnetic cover, even with the correct password I could not log in. I have delayed the screen automatic lock to 30 min and usually have to fix it with a restart if it happens.
I have another problem that if I have the nook covered with the magnetic cover for a time period longer than 2 hours. It seems to have been turned off. I have to try holding the power button to turn it back on and it will go through the nook splash screen and then the cyanogenmod start animations. Is this something expected with cyanogenmod? Has anyone else experienced this?
If it's a bug, I am wondering whether updating to CM 10.2.1 will fix it. I have read the first problem cannot be fixed and it might be hardware related. Is the second problem hardware related too? Thanks,
loveleo said:
I have the same problem as others that sometimes after sleeping with the magnetic cover, even with the correct password I could not log in. I have delayed the screen automatic lock to 30 min and usually have to fix it with a restart if it happens.
I have another problem that if I have the nook covered with the magnetic cover for a time period longer than 2 hours. It seems to have been turned off. I have to try holding the power button to turn it back on and it will go through the nook splash screen and then the cyanogenmod start animations. Is this something expected with cyanogenmod? Has anyone else experienced this?
If it's a bug, I am wondering whether updating to CM 10.2.1 will fix it. I have read the first problem cannot be fixed and it might be hardware related. Is the second problem hardware related too? Thanks,
Click to expand...
Click to collapse
You need to open and close the cover twice. It is a known bug on all CM versions.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You need to open and close the cover twice. It is a known bug on all CM versions.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Hum, I can't seem to reproduce my second problem for the last two days. The symptom was that when I tried to press the nook button or the power button to wake it up, nothing happens, it stayed at the black screen. I guess basically what I did was holding the power button to shut it off and then turn back on. I guess it might have needed a second time of opening the cover. I will keep watching and see whether this is the case.