I have an auto-nooted NC which has been pre-rooted with 1.1 through the Decad3nce method. Started noticing after rebooting a day later that the Wifi sleep mode issues from before are persisting.
Essentially, it doesn't recover from sleep and I'd have to manually go to the Wifi settings page to trigger the connection to the SSID--which is something I took care of before 1.1 with a Tasker script. Also noticed in the Nook Color Settings panel that there are 3 entries for Wireless referencing com.android.settings (actually, after looking just now, noticed other duplicate entries as well such as Settings and Time Zone).
The other problem that's more annoying to me is that after a few minutes of using, Button Savior essentially stops working until rebooted. The only button that works is the home key.
So are any of these repairable without resorting to going back to factory and performing the root and installations again?
Any insight is, of course, appreciated!
I had the same problem with WiFi after updating to 1.1 via Decadence. I ended up going back to 1.0.1 to avoid some glaring issues I was having.
But, check this thread for some solutions others had. Maybe it will help you.
Thanks, will look it over.
Regarding my Wifi, i actually found an app after several tries looking for ones that toggle wifi on/off. None really worked except REGPON which prevents the wifi radio to go into sleep mode.
Related
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.
My rooted NC 1.1 has stopped reconnecting automatically to my wifi network after sleep. It had been working fine for a while so I am not sure what changed. To get it to reconnect I either need to toggle the wifi on/off or select the network using wifi settings. After that it is fine. If I just put it to sleep and turn it back on after a minute or so it connects fine. The problem occurs after several minutes (say 10) of sleep.
I have deleted all my network connections, rebooted and then connected to my network with no change. Again this had been working fine in its current state.
I then reimaged it to a known working 1.1 image using CWR but the wifi issue remains.
This is more nuisance then anything else but it sure is annoying.
Look forward to any suggestions since I dont know what else to try.
Bob Silver
NC 1.1 rooted 1.1ghz
Ipad 3g 4.2.1
Iphone 4 IOS 4.1 jailbroken
same problem here, sometimes it works but after waiting too long it doesn't reconnect. I think after being asleep so long it just fails to refresh/rescan. Kind of silly they dont have a rescan/refresh button in the wifi settings...
You can try going into Settings/Wireless/Wifi Settings/hit the menu again and go to Advanced, set the sleep option to Never. This helps but it still shuts off the wifi after being locked for a few minutes.
The fix I use is called "SoftLocker Free" in the market. This basically prevents it from sleeping, but still allows the screen to turn off. It draws more power from the battery since the wifi stays on, but I've had good luck with it.
Strange question, but do you have AT&T? I've seen a ton of folks with non-rooted nooks have this issue on the official Barnes and Noble forum, all with Uverse.
No i am not using att.
Thanks for the tips so far.
Bob
ZTE blade has a similar issue, there's a couple of workarounds.
1. Keep the device awake when screen is off (holds wifi connection but uses battery power)
2. Automatically toggle wifi when you turn the screen back on.
I've made an app that does (1.) when you leave wifi on and turn the screen off. (similar to softlocker, but it automatically grabs the lock when wifi is left on and has other features). Search for "Advanced wifi lock"
If you want (2.) grab "Blade wifi fix".
This seems to be common among Android devices judging by the sheer volume of WiFi fix and Wifi lock applications in the market. Now, we just have to figure out which one works better with NookColor. Free would be better of course
Mine does it as well - WiFi on after waking up. Can stay awake for 10 minutes not connecting, bus as soon as I'll go to wireless settings, I can see it obtaining IP immediately. I also noticed it goes away from time to time and comes back by itself.
I started having so many wifi issues with Nookie Froyo 0.6.8 that I decided to just blow it away and reinstall the ROM.
However this time I'm having a totally new problem. Everytime I reboot or power on the Nook Color, the wifi defaults to turned off. Before it would always default on.
Is there a way to make the wifi default to turned on without me having to go into settings and turning it on all the time?
I installed Spare Parts and change the policy to never sleep, however that isn't helping with reboots.
I also faced wifi issue on Nookie Froyo 0.6.8. NC kept on turn on/off the wifi. Need to wait for a certain period of time to have the wifi work. Which ROM are you using to improve the wifi issue?
running cm7... i had this problem before... could not find the root cause. I was able to fix it by doing a clean install.
I heard it's an issue with airplane mode being turned on one time. Once you turn it on, it stays on (until you enable BT or WiFi) and is defaulted to on when you turn on your system, even if it doesn't say so in the settings. Somewhere on these forums is a fix, although I don't mind it being off when the nook boots up bcuz it saves power if I'm not going online.
I have so far only used NookieFroyo on SD (no airplane mode, no apps, no eMMC boots), and while I don't think I have this exact problem, I would like a fix for the WiFi issues. From boot it takes so long to enable the WiFi that I just go in and do it manually anyway.
More troubling to me is the wake up time -- still the WiFi takes forever and/or never comes back. This is no problem for me as I'll just go to Settings and toggle it, but others in the household aren't as technical and I'd really rather the thing reassociate on its own. Is that "Spare Parts" app the correct solution?
xdabr said:
I have so far only used NookieFroyo on SD (no airplane mode, no apps, no eMMC boots), and while I don't think I have this exact problem, I would like a fix for the WiFi issues. From boot it takes so long to enable the WiFi that I just go in and do it manually anyway.
More troubling to me is the wake up time -- still the WiFi takes forever and/or never comes back. This is no problem for me as I'll just go to Settings and toggle it, but others in the household aren't as technical and I'd really rather the thing reassociate on its own. Is that "Spare Parts" app the correct solution?
Click to expand...
Click to collapse
Although it's not a fix, you should have a Wifi widget on the home screen so that you can easily toggle it from there (and teach others how to). That's what I do.
I had a similar problem in that the WiFi would be off upon boot and/or when I try to manually control the WiFi it began looping on/off/on/off (you get the idea). I had a "Beautiful Toggle Widget" for this very reason (to give WiFi a kick in the pants). When the WiFi cycles, the widget did also. Could not correlate this with anything in particular.
This was so annoying that I bailed on Nookie Froyo 0.6.8 for the time being (playing with CM7 on a dual boot setup).
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!!
I have a serious problem with my Galaxy Note. All of a sudden Wifi is not working anymore (cannot be turned on anymore at all). Any ideas as how to get it fixed?
Background: I was playing a online game, put the device on the table (waiting for a timed task to finish). About 5 Minutes later I was picking it up again and noticed that the phone was shut off. Turned it on again and noticed that WIFI was greyed out. Other bugs noticed: The game data was wiped and all device administrators have been unselected (I use a tool that needs device administrator privileges to turn on the phone by swiping over the motion sensor). I don't know if WIFI was turned on or off at the time of crash. Anyhow - seems like some files that were in use (or recently in use) were deleted/corrupted. Probably including some WIFI components.
Stuff tried already: Turning Flight mode on/off. Rebooting Phone. Removing Battery. Various service codes found on the net like *#232339#, *#526# and *#528# all which do noting (do not open anything; seem to be invalid).
Phone is running on Stock Android 4.1.2, it is NOT rooted.
Any advices how to fix the problem (I'd really really really like to keep my app data, so factory reset is something I'd like to avoid). Found a tool called "fxr wifi fix and rescue" but dunno if it would be aplicable in this case or if it could make things even worse. Anything else? Any log files that can be checked? Anything to determine if this is hardware or software related?
Thanks for any help....