Database Develop

Keep wifi from sleeping

Any way to keep wifi on when NC screen times out from inactivity?
I have tried Keep wifi alive with no success. There is no option in the NC settings like there is on my HTC Inc.
Any help would be appreciated.
JDP

jdposhkus said:
Any way to keep wifi on when NC screen times out from inactivity?
I have tried Keep wifi alive with no success. There is no option in the NC settings like there is on my HTC Inc.
Any help would be appreciated.
JDP
Click to expand...
Click to collapse
Spare Parts app has a setting to set wifi sleep policy to never. I've heard mixed reactions as to whether it works, but I'm pretty sure it's working fine for me.

wvcachi said:
Spare Parts app has a setting to set wifi sleep policy to never. I've heard mixed reactions as to whether it works, but I'm pretty sure it's working fine for me.
Click to expand...
Click to collapse
Verified that it's working for me as well.

Thanks.
Ill give it a shot.

SpareParts is definitely not working for me. I think it modifies the settings.db/system table. Went to look at the table, nothing there related to wifi sleep policy. Should be wifi_sleep_policy with a field of 2, and that didn't work either. Any ideas?

Not working for me either.

Yeah, spare parts isn't keeping my wifi alive either. Every time i turn my NC on after sleeping for a few minutes I have to turn wifi off and back on again.

I got mine working. Spare Parts UI did not work. In fact i ran into issues restarting WiFi when I used the UI to set Sleep to never.
I had to manually create an entry in the secure table for wifi_sleep_policy and i use a widget to turn off wifi when i dont need it.
insert into secure values(152, 'wifi_sleep_policy', 2);
I used WiFi OnOff widget (free from market) to turn wiFi off when not needed.

^ Is there a guide somewhere?

duh.. this worked yesterday and now i am back to where i was before. This seems really flaky. I lose wifi even after having the setting. setting in DB or in spare parts does not fix it. its very random but fails more often than it works.
Possibly a faulty device? I cannot imagine that the Nook has such a basic problem. The only time it consistently reconnects is when i power on/off.
Any thoughts?

Is there a reason you wouldn't hit the power button to turn the screen off instead of waiting for it to time out? I do this when listening to tune-in radio, for example, and wifi remains on just fine. It also saves battery
Sent from my rockin' rooted Nook Color using XDA App

mikerocks said:
Yeah, spare parts isn't keeping my wifi alive either. Every time i turn my NC on after sleeping for a few minutes I have to turn wifi off and back on again.
Click to expand...
Click to collapse
I've never had to turn wifi off and back on to make it work again, you sure you aren't having problems with your wireless access point?

I found a quick solution that mostly works. If you download WakeTimer from the market, and create a wakelock (cpu on, screen off) that will keep Android from going into sleep mode and keep your wifi running. I tested it out by continuously pinging my Nook. I said "mostly" works because when you hit a button to turn the screen back on (either power button or nook button) I'd get a single ping timeout before it would resume.
*Edit*
Even though a single ping times out, there doesn't seem to be an interruption in streaming data. Don't know if I have to say it, but I will just in case...keeping your Nook from going into sleep mode will be a drain on the battery.

give it a try.

is there a fix for wifi going to sleep

I have tried all current fix's i have found on this site and none of them work is there some thing i am missing thanks .

The spare parts setting works well for me, not 100% of the time, but enough that it doesnt bother me.

I'm looking too....
Spare parts fix did't help me either

Grab Settings Profile Lite from the market. Set WiFi off when Screen off in the rules. Now Wifi will turn on and off with the screen. Fixed all my WiFi issues.
I also have Spare Parts set to Never.

ThrowingKs said:
Grab Settings Profile Lite from the market. Set WiFi off when Screen off in the rules. Now Wifi will turn on and off with the screen. Fixed all my WiFi issues.
I also have Spare Parts set to Never.
Click to expand...
Click to collapse
Correct me if I'm wrong, but I think that is exactly what the OP doesn't want.
I think he wants the wifi to stay on when he powers the screen back on, instead of having it disconnect when the screen turns back on.
The Nook I believe loses the connection when you turn on the screen.

ThrowingKs said:
Grab Settings Profile Lite from the market. Set WiFi off when Screen off in the rules. Now Wifi will turn on and off with the screen. Fixed all my WiFi issues.
I also have Spare Parts set to Never.
Click to expand...
Click to collapse
Thats how the NC works by default.
Spare parts did not work for me at all. I set it to always on and it still shuts off.

eggman618 said:
Correct me if I'm wrong, but I think that is exactly what the OP doesn't want.
I think he wants the wifi to stay on when he powers the screen back on, instead of having it disconnect when the screen turns back on.
The Nook I believe loses the connection when you turn on the screen.
Click to expand...
Click to collapse
That is what this does. When the screen is on, the WiFi is on. When the screen is off, the WiFi is off. It got rid of all my intermittent issues.

ThrowingKs said:
That is what this does. When the screen is on, the WiFi is on. When the screen is off, the WiFi is off. It got rid of all my intermittent issues.
Click to expand...
Click to collapse
How long have you been running this fix? I ran it for 10 days or so and started having issues, basically it quit working.(would turn off but not back on). Are you using it with spare parts? I am still looking for a permanent solution.

^ I have had it for probably a week and a half. I do also use Spare Parts with WiFi Sleep set to Never.
I also have my Nook set to DHCP, and my DD-WRT router set to give a "Static DHCP" to my Nook.
http://www.dd-wrt.com/wiki/index.php/Static_DHCP

ThrowingKs said:
^ I have had it for probably a week and a half. I do also use Spare Parts with WiFi Sleep set to Never.
I also have my Nook set to DHCP, and my DD-WRT router set to give a "Static DHCP" to my Nook.
http://www.dd-wrt.com/wiki/index.php/Static_DHCP
Click to expand...
Click to collapse
Thanks, will look at this when I have time.

Wifi Lock works for me...
Ok.. I read all the posts I could find and installed Wifi Lock, this is the only one I tested and works great for me. (Tested using Pandora radio)
This is what I did:
1- Install Wifi Lock (Android Market)
2- Reboot Nook Color
3- Go to your Extras and run the app. (It doesn't have a user interface, it only displays a message every time you click on it: Default / Never)
4- If you are using Advanced Task Killer (or any other) make sure you deselect Wifi Lock and add it to your Ignore List (I did it right away, I guess that's a VERY important step)
I just tested it several times for about an hour using Pandora radio, I have no idea how much it will drain the battery... If something goes wrong I'll let you know...

Wifi always off on startup in CM7

Hello everyone, pardon me if I duplicate a thread here, I tried searching but didn't see a similar issue. I am running a dual boot setup with Rooted stock and CM7 on eMMC. My Wifi works great on the rooted stock, however on the CM7 I need to start up Wifi every time I boot into it. Is there a way to make the system "remember" to turn on Wifi? For reference, I am using the CM7 final from this post: http://forum.xda-developers.com/showpost.php?p=12830947&postcount=581

EsotericPunk said:
Hello everyone, pardon me if I duplicate a thread here, I tried searching but didn't see a similar issue. I am running a dual boot setup with Rooted stock and CM7 on eMMC. My Wifi works great on the rooted stock, however on the CM7 I need to start up Wifi every time I boot into it. Is there a way to make the system "remember" to turn on Wifi? For reference, I am using the CM7 final from this post: http://forum.xda-developers.com/showpost.php?p=12830947&postcount=581
Click to expand...
Click to collapse
I'm running CM7 on the SD card and my WiFi starts up fine

You probably accidentally turned airplane mode on at some point. There is a bug in cm7 which causes it to stay enabled permanently after. You can use a sqlite editor from the market to turn it off.
Search for airplane mode in the forums for the details.
Sent from my NookColor using Tapatalk

ZapBranagann said:
You probably accidentally turned airplane mode on at some point. There is a bug in cm7 which causes it to stay enabled permanently after. You can use a sqlite editor from the market to turn it off.
Search for airplane mode in the forums for the details.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
I don't recall turning on Airplane mode but may have when looking at all the menus. I did do an over night battery test with only the released CM7 on the SD card and it was draining about 0.8% per hour using the built in battery meter. I don't know how accurate a test this is but the result was better than the 2% drain that I saw posted else where. Wouldn't the drain be higher if the WiFi never turned off?
Thanks,
jmak

Fix wifi isn't on on boot
If it's not on (and you enabled airplane mode ever) this will fix it:
adb shell
sqlite3 /data/data/com.android.providers.settings/databases/settings.db
delete from system where name = 'airplane_mode_on';
.exit
Click to expand...
Click to collapse

I was having the same issue, and I was able to fix it by downloading a free app called 'Android Assistant'. Start the app and go to the 'Tools' tab. At the bottom of the screen you will see several icons. When I first ran it, the 'Airplane Mode' icon was on (showed blue instead of grey). I tapped that icon (turning Airplane Mode off). It fixed the problem without having to issue the SQL commands. Let me know if this works for you.

Sweet, thanks everyone. I don't recall ever activating airplane mode, but sure enough, it was on!
Woody, I used Android Assistant and it worked perfectly! Actually, this app was a little bit of a bummer, I haven't had to ADB into the nook in forever... since the original autonooter hit for 1.0. Was a little excited that this was my big chance to get my ADB on again. Oh well, there will be other opportunities. Who knows what the coming Froyo update will have in store?

OMG.
Thank you.
Perfect.
Deirdre

EsotericPunk said:
Sweet, thanks everyone. I don't recall ever activating airplane mode, but sure enough, it was on!
Woody, I used Android Assistant and it worked perfectly! Actually, this app was a little bit of a bummer, I haven't had to ADB into the nook in forever... since the original autonooter hit for 1.0. Was a little excited that this was my big chance to get my ADB on again. Oh well, there will be other opportunities. Who knows what the coming Froyo update will have in store?
Click to expand...
Click to collapse
Sorry to burst your bubble

Thanks woody. I think that may have fixed it for me too! I accidently turned on airplane mode fairly soon after I flashed CM7 and have had problems ever since...

Thanks Woody. That was just what I needed.

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.

[discovery] Solution for GPS fix on stock based ROMs GB&Froyo

first of all, I'm not sure if this should post on this development forum
but I guess it is a helpful information for the Chiefs here to fix their ROM.
after tones of trials..
I found that, the only way you can ensure the GPS is working on the first time is..
make sure you have select using GPS function before next boot !!
try now and you'll see. nothing to do with gps.conf
nor hidden menu.
If you find your GPS function in current boot is not working..
keep the GPS selected via notification toggle or system setting.
and then reboot.
The key is, make sure GPS function is selected before next boot.
then, your GPS would working correctly !!
hopefully, some chief here could fix this LG induced "bug".
## the same bug is there even for Froyo V10f stock ROM!

please feed back if it works for you also ~
and i hope you guys find it useful..

Of course it has to do with hidden menu. If there are things f*cked up, then a reboot won't help.
Android decides itself when to use GPS, so turns it off, when there is no app running. For that reason, GPS should be always ticked 'on' in settings. This will not drain battery.

koboltzz said:
Of course it has to do with hidden menu. If there are things f*cked up, then a reboot won't help.
Android decides itself when to use GPS, so turns it off, when there is no app running. For that reason, GPS should be always ticked 'on' in settings. This will not drain battery.
Click to expand...
Click to collapse
Tested it works for fresh install without modifying anything via hidden menu.
just leave your GPS toggle ON before shut down or reboot.
It will working on next boot.

i have found that the gps will work untill u turn wifi on. after that you have
to reboot to get it back.

squide said:
Tested it works for fresh install without modifying anything via hidden menu.
just leave your GPS toggle ON before shut down or reboot.
Click to expand...
Click to collapse
This is just what I said?!
I meant that if the ROM-baker do something strange to the settings in hiddenmenu, reboot won't help.
-> First, settings must be correct, second, leave GPS always on
For me, reboots are not necessary to get GPS to work.

koboltzz said:
This is just what I said?!
I meant that if the ROM-baker do something strange to the settings in hiddenmenu, reboot won't help.
-> First, settings must be correct, second, leave GPS always on
For me, reboots are not necessary to get GPS to work.
Click to expand...
Click to collapse
ok, try turn it off and reboot.
then you'll see it won't work until you leave it ON and reboot again.
I'm not asking if you would leave it ON all the time or not.
I just mean you need to make sure it is ON before any shut down or reboot
in order to ensure it works on next boot up.

woodback said:
i have found that the gps will work untill u turn wifi on. after that you have
to reboot to get it back.
Click to expand...
Click to collapse
if using wifi which mean you can not access the AGPS service via your APN
which mean it would take longer time to fix.
try disable wifi and use your mobile internet again and see..

I am using bulgarian leak v20e and my gps is always off. And whenever i need it i turn it on and it work in 5 seconds.
I never used any Mod or hidden menu and i think this problem is device dependent because i never faced it. I maybe lucky lolzzz
Sent from my LG-P990 using XDA App

for me it is like squide said.

tested with my friend's very stock out of the box V10f Froyo.
The same trick is needed!
He has never even root his 2x
he don't even know there's a hidden menu.
I tried to enable GPS and try to fix on his phone, takes forever..
then I keep the GPS enabled, reboot.. and try to fix
it takes around 15sec to fix even with no data plan on his phone!
outdoor, open sky and fairly cloudy here..

Cannot confirm, at least with my patched services.jar and my 1.6 rom. Rebooted with GPS off, turned it on and got a fix in 10 seconds indoor.

Topogigi said:
Cannot confirm, at least with my patched services.jar and my 1.6 rom. Rebooted with GPS off, turned it on and got a fix in 10 seconds indoor.
Click to expand...
Click to collapse
I'm using your 1.6 at the moment..
GPS OFF then reboot, turn it ON again, take forever to fix.
GPS ON, then reboot, fix in 4 sec. with AGPS.
fix in around 15 sec without data connection.
possibly kernel related?

squide said:
I'm using your 1.6 at the moment..
GPS OFF then reboot, turn it ON again, take forever to fix.
GPS ON, then reboot, fix in 4 sec. with AGPS.
fix in around 15 sec without data connection.
possibly kernel related?
Click to expand...
Click to collapse
Same here. Unless using hiddenmenu.

Topogigi said:
Cannot confirm, at least with my patched services.jar and my 1.6 rom. Rebooted with GPS off, turned it on and got a fix in 10 seconds indoor.
Click to expand...
Click to collapse
Try to do the same test with GPS OFF-> power off and battery pull.
As previous fix would affect the actual time to fix with new setting!
let's forget hidden menu first..
because the out of the box GPS setting in hidden menu is working correctly.
no need to modify anything, found actually no need to add nokia server to make it work.
just ensure GPS is ON before every shut down or reboot.
then the GPS would work on next boot! never been so quick too.

squide said:
I'm using your 1.6 at the moment..
GPS OFF then reboot, turn it ON again, take forever to fix.
GPS ON, then reboot, fix in 4 sec. with AGPS.
fix in around 15 sec without data connection.
possibly kernel related?
Click to expand...
Click to collapse
Reported my experience above. Same kernel, same version, fix in 10 secs near the window.

Topogigi said:
Reported my experience above. Same kernel, same version, fix in 10 secs near the window.
Click to expand...
Click to collapse
if you have fix before, later fix will not show you the actual time needed.
as above I said, try power off with GPS off and a battery pull before restart.
it would clear all hot state from your GPS chip and also clear AGPS state.
from there you'll see the actual time needed.

squide said:
if you have fix before, later fix will not show you the actual time needed.
as above I said, try power off with GPS off and a battery pull before restart.
it would clear all hot state from your GPS chip and also clear AGPS state.
from there you'll see the actual time needed.
Click to expand...
Click to collapse
Yes, a cold fix takes more time than a warm one, but this is normal GPS behaviour. It does not mean that something is wrong there. But I am missing something for sure.

In stock I get a fix in 30 sec. In cm I get a fix in 5 minutes