Related
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 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..
Have anyone other than me experienced that the phone suddenly is turned of? It's not the BSOD or reboot, but just turned off and can be turned on right away..
I've saw it yesterday when it was in my pocket, and this morning when i woke up.
I'm using the CM7 RC1 ROM straight from the box.
Yes. I get this to... (With every build of CM that is)
Same happens to me also with the latest CM7.
Me and my brother also get this, started with cm7 57 I think
Sent from my Optimus 2X using Tapatalk
Does anyone know how to use ADB to log? Then we could maybe capture some logs when this happens and post to aremcee to see if he can help us..
The same thing has happend to me 2 times in the week a have had this replacement device. It's worse than the one I traded this one for
But I'm on stock havn't rooted or anything.
Just had a BSOD aswell.. Gotta hate this phone. It's works on stock so I can't send it to my dealer and get my money back
Install a Froyo Rom
Profit.
My findings on the CM7 sod (sleep of death) issue (I post this here, as I don't have enough posts to post it to dev area):
I've been using CM7 occasionally since the first nightly. About 2 months ago I suddenly had 3 sods in 2 days. This was after I bought JuiceDefender Ultimate. In JD I had sync enabled once per hour, and JD set to first try to connect to wifi and then mobile data. In Android wifi settings I had wifi sleep policy set to "when screen turns off".
After I set JD to use only mobile data on sync events, and turned wifi sleep policy to "never", I haven't had a single sod since. If I remember correctly, I once managed to induce a sod by turning wifi on or off (can't remember which) through the power control widget, and immediately after that I turned the screen off normally by pressing the power button (while wifi was "dimmed" in the power control widget meaning it was changing it's state).
So I strongly believe that my sods were caused by the combination of turning wifi on or off (either through widget or JD doing it) and turning the screen off at the same time. I didn't experiment any more, since I found my solution above.
I wrote this here, because people try hard to hunt down what's causing the sods, and I wanted to share my thoughts. If it is of no help, then sorry.
it happens sometime... don't trust your phone's alarm to wake up. you could have bad surprise (just had the experience 2 days ago) :'(
i am running cm7 no. 165. and vork kernel clocked to 1504 no reboots or black out issues. i also have green power managing my network data only... good luck all... just remember that cm7 is still nightly and is not considered stable.
Hi, I'm about to get one LG, but I've had the same issue with an Orange Boston mobile with a 2.3.5 CM7. I disabled Wi-Fi sleep too and it seems to help.
Before the scren weirdly shut down and the phone rebooted.
Hmm might try this out and see if it works.
I can't seem to get this issues myself. I will try and test this later on my other phone.
That is the reason why I don`t use CM7 anymore ...
Moderator Message
Extensive discussion going on here >
http://forum.xda-developers.com/showthread.php?t=997705
THREAD CLOSED
I have a Nexus 6, flashed with the 6.0 factory image.
I have my wifi set to always on (for tmobile calling). After then screen locks it shuts wifi off. This is great for my battery but bad for my staying connected. At work cell coverage is spotty and without wifi always on I can get 30min + delay in getting text/calls. This has caused a few problems with my boss thinking im off screwing around and ignoring him.
Anyone else notice this? or have a way to keep wifi always on.
My wifi randomly drops since I updated to 6.0. It is annoying. I am not sure if it is tied to the screen shutting off or not.
Yeah it's getting supper annoying. I'm at wits end with it. Might flash back to 5
Probably it is related to this bug: https://code.google.com/p/android/issues/detail?id=188909
When I turned off my WiFi, it was still running, showed in the battery history detail. It was OFF, so I expect it's also OFF there. But it's not OFF. Although today, I don't have that problem.
So please STAR that bug to get more attention.
Have you all tried HellsCore kernel with the "old" WiFi drivers that he built? Apparently it resolved issues for people.
Happen to have a link? Had hoped to stay stock for awhile but ATM its killing me.
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
So weird, but same thing has been happening to me the past few days. But I have a justified cause. It started immediately after installing Franco Kernel.
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
My N6 is running Android 7.0, have not had problems until a couple of days ago.
The right half of my display started scrolling while, the left side of the display was normal. I powered it off and back on a couple of times and, the issue was still there; I panicked and did a factory reset from the "Settings" menu hoping that would solve the problem, it did not; I still had a jacked up display.
Is this a failure mode that anyone else has seen?
I powered the phone off and, turned it back on with the volume control button pressed and, it booted into safe mode(?) then, I toggled the mode to "Restart" and, upon restart, my display was normal. This was not the end as, it will occasionally be split screen when I unlock it. I have discovered that sometimes if I receive or make a call the display will return to normal, if not, I just power cycle it into the safe-recovery mode (but not do anything else) then toggle to restart and, it's all good until next time.
Is it possible that another device (blue-tooth) in close proximity could cause my phone display to act up?
Click to expand...
Click to collapse
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Pkt_Lnt said:
It is a known hardware issue in some N6 phones, some have it and it only shows up on certain rom / kernel combos, even stock. One thing that helps is to use the interactive kernel governor and/or the down sampling factor. Of course you will need a kernel manager app for that.
https://forum.xda-developers.com/showpost.php?p=63249802&postcount=4602
Click to expand...
Click to collapse
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
I've since flashed stock pn, and now elementalx. It's not acted up yet. Seemes to be a better performance kernel. We'll see how battery is. Sorry to hijack your thread!
Sent from my Nexus 6 using Tapatalk
queensgate555 said:
That's good to know.
I inserted the Bluetooth question because, coincidentally or not this issue presented when I acquired a wristwatch ($19.00 from China) that connected to my phone via Bluetooth, It had it's own fitness app which I installed (which did not work). To me, there seems to be more "connection" than expected as, the fault thing only seems to happen when the watch was powered on (but not even connected via Bluetooth). If there was a bug caused by the companion app, that should have been taken care of by the factory reset.
I'm going to do some "scientific testing" by, not powering on the watch for a week and see if the issue reoccurs. Meanwhile, I will read up on kernel manager apps.
Click to expand...
Click to collapse
Well, so much for "scientific testing" and wishful thinking.....didn't take long to eliminate the wristwatch, now to fix the problem.
.