Database Develop

[Q] Why is Wifi Always Turned Off When Nook Boots?

I am on CM7 nightly 31, but have been having a problem for weeks now. Every time my NC starts up, Wifi is disabled. I can manually start it, but I can't figure out what is causing this behavior. This problem has continued through multiple ROM updates. Any ideas?

This was happening to me until i did a clean install... never found the root cause.

drx69 said:
This was happening to me until i did a clean install... never found the root cause.
Click to expand...
Click to collapse
By clean install do you mean restore to stock then cm7?

thats what i did when i had that problem. using froyo. just reflashed everything and it was back to normal.

I'm having the same issue with CM7. Did you manage to resolve the issue?
Sent from my NookColor using Tapatalk

Also having the same issue. Not sure when it started, been flashing the nightlies since the first build most nights and I didn't always have the issue, but its been going on for awhile. Haven't really cared enough to do a full wipe and reinstall since its just a nuisance (sp?) just wanted to throw my hat in the ring as another person with the issue.

THere are other topics about this exact issue, from what i've read though it has to do with airplane mode defaulting to "on" when you start your nook. It's not set to on in the settings, but in the actual system files. There is a fix for it out there, but I don't have a link. I personally like it defaulting to off because I don't always turn my nook on to go online right away and it saves battery.

ZapBranagann said:
I'm having the same issue with CM7. Did you manage to resolve the issue?
Click to expand...
Click to collapse
Yes. a clean install fixed this issues. I also am no longer having the issue with the wifi turning off during sleep mode.

Great thanks for the confirmation I guess I'll bite the bullet and do a clean install.
Sent from my NookColor using Tapatalk

So I found a solution posted on the dev forums that does not require a full wipe. If you use a sqlite editor you can disable airplane mode in settings.db.
Hope that helps someone!
Sent from my NookColor using Tapatalk

[Q] Bluetooth Problems on CM7

I can't seem to get bluetooth to enable on my Nook. I've tried using CyanogenMod 7 nightly and the CynogenMod-7.0.0-encore as well. No luck. I've tried turning off wireless hard rebooting, fixed permissions ect... When I click the bluetooth icon it blinks and within a quarter of a second it turns off. It doesn't even have an icon that says it's trying to turn it on. Anybody have any ideas on what I can do to fix it?

tons of threads about that - just go to ROM Manager, click Fix Permissions then after that is done and you see a popup asking you to reboot, don't select this, rather press the power switch down until the nook powers off, then turn it back on again

animatechnica said:
tons of threads about that - just go to ROM Manager, click Fix Permissions then after that is done and you see a popup asking you to reboot, don't select this, rather press the power switch down until the nook powers off, then turn it back on again
Click to expand...
Click to collapse
If you would of read, I have already tried it. It didn't work.

I have the same exact issue as the OP.
Tried all the recommended fixes including fixing permissions.
Tried one additional step I found mentioned somewhere.
Go into spare parts uncheck compatibility mode and reboot.
Apparently this worked for some but not me.
Hoping someone with same problem can ping in with what might have worked for them.

Please guys try this.
Firstly, you switch off you wifi.
Secondly, you reboot.
Thirdly, you switch on your bluetooth and get it running. (it seems the bluetooth would not start after Wifi)

Sadly It still isn't working. I've already tried the hard boot with wireless off and quickly starting up the bluetooth as soon as my nook is started. Any other suggestions?
Edit: Do you guys think it just might not work/ dead?

Azamatka said:
Please guys try this.
Firstly, you switch off you wifi.
Secondly, you reboot.
Thirdly, you switch on your bluetooth and get it running. (it seems the bluetooth would not start after Wifi)
Click to expand...
Click to collapse
This. Always works for me. As he said, turn off wifi entirely, POWER DOWN. Boot back up, turn on Bluetooth. Once it's up, turn on Wifi.

khaytsus said:
This. Always works for me. As he said, turn off wifi entirely, POWER DOWN. Boot back up, turn on Bluetooth. Once it's up, turn on Wifi.
Click to expand...
Click to collapse
Nope didn't work if you read my posts... When I find my camera I'll try to post a video of what it does to "try" to enable bluetooth.

Azamatka said:
Please guys try this.
Firstly, you switch off you wifi.
Secondly, you reboot.
Thirdly, you switch on your bluetooth and get it running. (it seems the bluetooth would not start after Wifi)
Click to expand...
Click to collapse
Thanks got it working. I was wondering why it would shut down after clicking turn on. But now if it says paired but not connected does that mean my holux GPS isn't going to work with the nook?

had the same behaviour until tried this:
1 turn off wireless
2 fixed permisions with rom manager
3 turned off nook, by pressing power button
4 restarted nook
5 turned on bluetooth
after this, i could freely turn on/off wifi and bluetooth without complaining
btw, i'm on CM7 stable running on verygreen SD card with 04/04 dal's kernel

@brento1
You have to use an app such as GPS Provider to connect your GPS to android. Otherwise you will get that error.
___________________
- Derek

I have tried all suggestions but bluetooth will not turn on.

don_ernesto said:
had the same behaviour until tried this:
1 turn off wireless
2 fixed permisions with rom manager
3 turned off nook, by pressing power button
4 restarted nook
5 turned on bluetooth
after this, i could freely turn on/off wifi and bluetooth
Click to expand...
Click to collapse
This worked for me.

sanvara said:
This worked for me.
Click to expand...
Click to collapse
Yes above steps works for me too.

don_ernesto said:
had the same behaviour until tried this:
1 turn off wireless
2 fixed permisions with rom manager
3 turned off nook, by pressing power button
4 restarted nook
5 turned on bluetooth
after this, i could freely turn on/off wifi and bluetooth without complaining
btw, i'm on CM7 stable running on verygreen SD card with 04/04 dal's kernel
Click to expand...
Click to collapse
That didn't work... But I figured it out! I was running on Dal's OC kernel and for some reason it was clashing BT! Thanks everyone for trying!

So I've tried everything suggested multiple time with and does not work.
Thanks for discoverying the OC kernel connection. I am also running it. I will try to install a fresh nightly without OC tonight.
Are any of you with working BT also using the OC kernel?

As of this moment, I'm not going to install an OC kernel because I'm afraid I won't be able to get BT to work. Can anyone recommend one?

I have phiremod 6, with the OC kernal and it works, but initially, I had the problem.
Shut down the nook and start it up again. NOTE, Do not do a reboot, do a shut down!
Hope it works for you.

i think i have the same problem that I'm using the OC kernel, do anyone have a suggested kernel to intro?
thanks in advance..

NC, CM7, Dalingrin OC kernel.. Sleep of Death

CWM 3.2.0.1
CM7 Nightly 131
update-CM7-dalingrin-OC-emmc-063011
Sleep of Death-
Sometimes the screen will remain black when trying to wake the device. I haven't been able to find a pattern to the problem, though I think it has something to do with the kernel. It seems completely random.
This has happened on every nightly I've used, which is why I think it's related to the kernel.
Has anyone found a fix?

omnibyte said:
CWM 3.2.0.1
CM7 Nightly 131
update-CM7-dalingrin-OC-emmc-063011
Sleep of Death-
Sometimes the screen will remain black when trying to wake the device. I haven't been able to find a pattern to the problem, though I think it has something to do with the kernel. It seems completely random.
This has happened on every nightly I've used, which is why I think it's related to the kernel.
Has anyone found a fix?
Click to expand...
Click to collapse
Not sure to what the cause is. However, for me I noticed that every time I left wifi on and put my nook to sleep I would get sod anytime after an hr. So now I manually disconnect wifi every time I put my nook to sleep, and I have not once experienced another sod. There are some people that say the latest nightlies have fixed sod but other report there still there so I guess it varies.
I'm currently on n125 with dal's 6/30 oc kernel.

The problem still occurs with the recent nightlies.
It's weird, last night I left it in sleep mode with wifi turned on, and it powered up fine this morning.
A few hours later, I put it in sleep mode, set it down for a minute, then tried to use it again. It wouldn't wake up. From what I can tell, it doesn't matter what amount of time passes.
I'll keep trying the wifi trick you mentioned. If disabling wifi does the trick, then that will narrow down the problem quite a bit.
Thanks for the tip!

dabiddabird said:
Not sure to what the cause is. However, for me I noticed that every time I left wifi on and put my nook to sleep I would get sod anytime after an hr. So now I manually disconnect wifi every time I put my nook to sleep, and I have not once experienced another sod. There are some people that say the latest nightlies have fixed sod but other report there still there so I guess it varies.
I'm currently on n125 with dal's 6/30 oc kernel.
Click to expand...
Click to collapse
I am on n120 with dals 6/30...I always got SOD when I left wifi set to always on...when I switched wifi to shut off with the screen, the problem has not returned!

Yup, it looks like turning wifi off before it sleeps does the trick. 48 hours later and no SOD.
Thanks for the tip!

cmdauria said:
I am on n120 with dals 6/30...I always got SOD when I left wifi set to always on...when I switched wifi to shut off with the screen, the problem has not returned!
Click to expand...
Click to collapse
How do you set wifi to shut off with the screen? I can't find a setting for it.

omnibyte said:
How do you set wifi to shut off with the screen? I can't find a setting for it.
Click to expand...
Click to collapse
Try an app like juice defender.
Sent from my phone using Tapatalk

omnibyte said:
Yup, it looks like turning wifi off before it sleeps does the trick. 48 hours later and no SOD.
Thanks for the tip!
Click to expand...
Click to collapse
No problem glad it worked for you.

koopakid08 said:
Try an app like juice defender.
Sent from my phone using Tapatalk
Click to expand...
Click to collapse
Great, thanks for the recommendation.

If you are looking for a free solution to do this, the application Setting Profiles Lite allows you to set exactly one rule.
Create a profile with wifi off. Create a rule to set the wifi off profile when the screen is off.
Frank

frankusb said:
If you are looking for a free solution to do this, the application Setting Profiles Lite allows you to set exactly one rule.
Create a profile with wifi off. Create a rule to set the wifi off profile when the screen is off.
Frank
Click to expand...
Click to collapse
http://nookdevs.com/NookColor_Issues#Workaround_One
Details there if anyone wants to try it, works great. I used it on stock ROM, now that I have Tasker on my tablet I use it instead, but all the same.

I'm experiencing the SOD on CM 7.1 RC1... so it's not limited to the nightly's.
Has anyone escalated to the CM devs yet?

I think I have found a temp fix for the SOD, doubled my battery life, and increased my bandwidth when tethered. I am no expert at any of this, but after I installed DroidWall from the market and used the "white list" mode enabling only the apps I wanted to use the network I no longer get SOD. For example I am using wifi tether on my galaxy s in infrastructure mode with droidwall on my NC only allowing XDA app access to the internet.
I also have it installed on my galaxy and only have Linux kernel and applications with root accessesing data. I have gotten more than 8 hours on the galaxy without having to charge. Now I am able to have it tethered to my NC all day and neither device needs charging.
Heck maybe its a placibo effect maybe not.
Running CM7.1 RC1
Now if I can figure out why I lost the ability to mount my NC mass storage on the PC after using the new USB host mode and playing with the wiimote. Go figure
Sent from my NookColor using XDA Premium App

skylar.sutton said:
I'm experiencing the SOD on CM 7.1 RC1... so it's not limited to the nightly's.
Has anyone escalated to the CM devs yet?
Click to expand...
Click to collapse
I've also been seeing SOD almost every time I put the NC to sleep for an extended period of time (longer than an hour). Also running 7.1 RC1. Weird thing is that it's been within the last 2 weeks that it's been happening. I've tried the Setting Profiles workaround listed above but I'm not sure if I set up the rules correctly so we'll see what happens

The setting profiles workaround didn't seem to work. I tried switching out my almost full 8gb sd card for a 16 gb sd card and after putting it to sleep overnight, it came back on immediately. Would sd card memory have anything to do with it?

I have also found AutomateIt (free market app) to work well for setting triggers and actions... i.e.
Power Plugged In -> Set Screen Off Timeout 30 min
Power UnPlugged ->Set Screen Off Timeout 2 min
Screen Off -> Set WiFi State Off (delay 5 min)
Screen On -> Set WiFi State On (no delay)

Just my $0.02... but a profile/setting switcher is not a "fix" for the SOD... it's a work around (and an ineffective one at that). The underlying problem still exists, so nothing has been fixed, we're just maneuvering around it.
I'm going to work on something that logs to a remote file and let it run for a few days. I'm hoping I can catch some data around what is going on immediately prior to the lock up.
Also, sorry for the bump.

[Q] Reboot using Airplane mode

Sometimes I'm in areas where I don't get the best reception (i.e. some lecture halls during school hours) and I choose to put my phone in airplane mode so as to conserve battery when the class is over. However I find after trying to come out of Airplane Mode my Revo always reboots. As far as I can remember this issue has also happened in Decrapped 1.0. The same thing happens when I turn on GPS and choose to go to Google Navigation I get rebooted. After the reboot occurs I can turn on the gps/airplane mode etc without any problems. But does this issue happen to anyone else or is it perhaps just my phone? Thanks!!

I find that my revo does the same thing with google nav beta, it will sometimes hang and reboot too. I am running stock rom with a root. When I rotate phone the landscape view is sometimes corrupted with tiny blocks instead of the maps drawn correctly. I have to exit nav app and reload

I've had the same thing happen with airplane mode. I don't really use it often so I figure I can live with it.

Same here. The Revo doesn't seem to like hardware mode changes at times. I get reboots when switching into Bluetooth occasionally.
[I'm Revolting -- are you? Beamed directly into your brain by Revolt 1.3]

I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!

Cryofalcon said:
I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm only adding this due to the fact that I was constantly having issues when tethering with the Verizon 4g Hot Spot app. When running it, I found myself needing to reboot because the data connection would get lost and sometimes go into 3g, causing all sorts of headaches with doing things on my computer, such as redesigning websites, including my own.
What I found, though, related to this post, is using the airplane mode to kill the data connection and restart it, was getting me 4g and a few minutes to a few hours of Internet again until the next glitch.
Overall, modded, ota updated, downgraded, whatever, using that method never rebooted my phone. My thoughts are that it's possible some app might be causing that. I don't use Nav anymore, except as a last resort because it is so buggy, it would cause my phone to crash over and over, and rebooting. So, as for LG or Verizon coming up with a fix for this issue, I don't know if they would see it as one because it's not something everyone is experiencing and with as much as I use(d) that method, it never once happened to me. Please don't take that wrongly, just wanted to point out that it might be a certain app and allow those having this issue to seek another solution, maybe comparing apps installed to see a common denominator.
And, because I see a lot of posts relating to tethering issues with Internet freezing or dropping out, I found, on my LINUX machine (so far), that setting the MTU to 1300 seems to have solved that issue. I know this last part isn't directly related to the original post, but is the reason I kept using the airplane mode method and thought this added information might help someone doing what I was...
-Cybie

Sorry for the bump, but as of flashing Revolt 1.5, the issue in my original post seems to have been corrected as I was able to go from airplane mode to google nav multiple times and didn't reboot at all. so whatever the issue was seems to have been corrected. Thanks MT!!

nexus 7 not killing wifi during sleep after updating to 4.2.1

I have selected to never keep WiFi on during sleep yet now the tablet continues to run the WiFi as you can see in the pictures. This has forced me to use airplane mode when I am on the go because otherwise the tablet just keeps WiFi on and burns the battery extremely quick. This has been a problem since I updated to 4.2.1. I am not rooted completely stock. A solution would be great because this sucks right now. I have tried clearing the cache in recovery but that didn't solve the problem.

I'm running the latest Paranoidandroid ROM and thought that was the problem. I can't yet post to that developer forum so I was just waiting for the next beta.
I guess it's a problem with 4.2.1 then.
-PMS

jetguy35 said:
I have selected to never keep WiFi on during sleep yet now the tablet continues to run the WiFi as you can see in the pictures. This has forced me to use airplane mode when I am on the go because otherwise the tablet just keeps WiFi on and burns the battery extremely quick. This has been a problem since I updated to 4.2.1. I am not rooted completely stock. A solution would be great because this sucks right now. I have tried clearing the cache in recovery but that didn't solve the problem.
Click to expand...
Click to collapse
If you don't find a solution you may want to try DataEasyPro from the market. It kills both 3g and wifi as soon as the screen is off and then runs a user defined schedule to turn on 3g or wifi every now and the for a few seconds to keep you upto date with your social world. Works great. There is even a widget so you can turn off the schedule when you are downloading or updating from the play store.
https://play.google.com/store/apps/details?id=cb56.dataeasypro

PsychoMcSatan said:
I'm running the latest Paranoidandroid ROM and thought that was the problem. I can't yet post to that developer forum so I was just waiting for the next beta.
I guess it's a problem with 4.2.1 then.
-PMS
Click to expand...
Click to collapse
I think it is a 4.2.1 problem. Its hard to say how wide spread it is though because I have only seen a handful of posts about this issue though. To me, this issue is unacceptable. I should not have to enable/disable airplane mode to conserve battery. Especially when the previous version of android prior to the 4.2.1 update handled WiFi sleep settings without a problem. Hopefully a fix will be here soon. My tablet used to have superb battery life without me constantly monitoring it. Now I feel like I have to keep double checking that I remember to use airplane mode so that I don't go to use the tablet and find a nearly depleted battery.

Dmwitz said:
If you don't find a solution you may want to try DataEasyPro from the market. It kills both 3g and wifi as soon as the screen is off and then runs a user defined schedule to turn on 3g or wifi every now and the for a few seconds to keep you upto date with your social world. Works great. There is even a widget so you can turn off the schedule when you are downloading or updating from the play store.
https://play.google.com/store/apps/details?id=cb56.dataeasypro
Click to expand...
Click to collapse
This app shows as not compatible for me when I used the link.

jetguy35 said:
This app shows as not compatible for me when I used the link.
Click to expand...
Click to collapse
I recommend automate it, I have a couple of rules set to turn WiFi of with the screen (with a 5min delay), then turn Wi-Fi back on when the screen turns on. There's plenty of other settings and rules to play with as well.
https://play.google.com/store/apps/details?id=AutomateIt.mainPackage
Sent from my Nexus 7 using xda app-developers app

In had the same issue. I found Google maps to be the culprit.
It defaulted back to location reporting.
Check Google now sync, maps and currents.
Sent from my Nexus 7 using xda app-developers app

It's not google maps itself, it's the android location service. It's always collecting data even if your phone or tabscreen isn't on. This is pretty anoying since google only let you choose between agreeing to run the service in the background or not using it at all. Stupid! How about collecting data only when the device is in use?

Same here. There is a bug report on Google about it.
Sent from my Nexus 7 using xda app-developers app

Ah this is interesting; as last night my battery was on 53% and I am sure I charged it fully previously...... Am on stock too but have rooted.
Might just switch the tablet off all the time for the time being.

I'm on stock rooted 4.2.1 and mine is fine. Strange.
Sent from my Nexus 7 using xda app-developers app

RKight said:
I'm on stock rooted 4.2.1 and mine is fine. Strange.
View attachment 1552034
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
WiFi turns off here also, which means its working as intended, what is strange is is it not working for some people, I'm also on stock rooted 4.2.1.
what is the OP using? Are there any apps installed/running on the OPs device that can keep the WiFi alive?
Sent from my Nexus 7

jersonf said:
what is the OP using? Are there any apps installed/running on the OPs device that can keep the WiFi alive?
Click to expand...
Click to collapse
I highly recommend using an app called Better Battery Stats. You can find the free version here on XDA. It'll tell you if there is an app causing a wakelock. I used it to troubleshoot my Rezound and I'm getting a solid 4-5 hours of screen on time with the extended battery on that because it helped me lock down the apps that were killing my battery.
Sent from my Nexus 7 using xda app-developers app

I'm stock rooted and mines don't turn off neither.
Sent from my Nexus 7 using xda app-developers app

Hmmm. Just checked PA beta 7 and it's doing it too. Wifi on always.
A custom kernel would probably fix that.
Sent from my Nexus 7 using XDA Premium HD app

RKight said:
I highly recommend using an app called Better Battery Stats. You can find the free version here on XDA. It'll tell you if there is an app causing a wakelock. I used it to troubleshoot my Rezound and I'm getting a solid 4-5 hours of screen on time with the extended battery on that because it helped me lock down the apps that were killing my battery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Although my wifi is turning off I give thanks for pointing me in the direction of this app.
http://forum.xda-developers.com/showthread.php?t=1179809
Sent from my Nexus 7

I was having the wifi on issue as well. Just bought my N7, stock 4.2.1 and not rooted. I followed the tip in point four of this post, which details a simple set up using Tasker, where the unit turns the wifi on and off after the screen turns on or off respectively. The reason for the 10 second delay as is detailed in the link, is to allow for the turning on of your N7 to check the time or other reasons, and then quickly turn it off without the wifi on task being activated.
the screenshot below shows my wifi being stuck on while in sleep mode, even with it set to be never on during sleep in the settings, and the change in behavior once the 2 Tasker profiles we set up.
Cheers

Those of you having issues, have you tried the "only when plugged in" setting? Not sure if it would really matter but that's what I use and mine turns on and off just fine.
Sent from my ADR6425LVW using xda app-developers app

RKight said:
...have you tried the "only when plugged in" setting?
Click to expand...
Click to collapse
Testing that now. Turned off Tasker, and set wifi to the "only when plugged in" setting. It's only been about 30 minutes, but so far it looks like it's behaving the same as before, as in keeping wifi on while in sleep. I'll Let it sleep for a few hours and see what the chart shows.
Cheers
EDIT: So I let my N7 sit for about an hour after switching the above mentioned settings, and you can see in the screenshot below that the wifi is staying on while the unit is not awake. I've set my Tasker profiles to control the wifi once again.
I know it may be fixed by a factory reset, but frankly I'm more than happy with the way Tasker handles the issue.
Cheers

so 6 months later, I am still getting this problem. However it seems only to be with the last update. The tasker method seems to be working well though.