Hey guys I tried searching but came up empty handed here.
Whenever I put my nook in standby (push power button or it automatically does it with inactivity) the wifi connection turns off. I've got it set to do that in spare parts so that it only stays "awake" while charging and not while idle.
The problem is it doesn't do that. Regardless of if it's charging or not, whenever I wake it up, even though wifi is enabled in the settings, it doesn't search on connect to my network. I have to go into Setting -> Wireless and as soon as I go into that menu, it finally connects automatically. It won't do it unless I go to that menu.
I'm rooted with the 1.0.1 Autonoonter btw.
Mine was doing something similiar. For me, it kept hanging up on obtaining an IP. I used an app called Wifi Static (free in the market) to set up a static IP and haven't had any problems since. Wifi seems to shut itself off way less often and when it does, it only takes 1-2 seconds to auto reconnect. Don't know if it will help you or not, but it's worth a try.
Have you done any modification of the wifi settings at all? Like the ad-hoc supplicant mod?
Quilombo said:
Have you done any modification of the wifi settings at all? Like the ad-hoc supplicant mod?
Click to expand...
Click to collapse
I have not.
I have the problem but it only happens with certain routers others work just fine . . . weird!
I have exactly the same problem. It started with the upgrade to 1.1. Affects stock or adhoc supplicant.Very annoying. Yet to find a fix
When I reboot my Captivate, my Rosewill RNX-EasyN4 router reboots also. When the Captivate tries to connect to Wifi that is when the router reboots. This only happens after I reboot the phone. When I just turn off Wifi and then turn it back on, the router is fine. Even if I turn off the Wifi for a while and turn it back later, the router has no problems. Has anyone experienced this problem before? I am running Serendipity 6.3. I think it was happening when I was running stock also, but I am not 100% sure.
Sounds like your router is flakey. Rebooting the Captivate should not cause a reboot of your router. Check the Rosewill website and see if they have updated firmware for your router. That may solve the problem.
I have the latest firmware on the router dated 2010.07.15. I do not think it is a problem with the router because I have multiple notebooks, a PS3, and a wireless printer connected to it. Only the Captivate causes it to reboot.
Turn off wifi before you reboot.
Sent from a place my wife doesn't know about (yet)
Tried that already. Once I turn Wi-Fi back on, the router reboots.
Ok, try power cycling the router. 2) try the fxr wifi fix from the market.
Sent from a place my wife doesn't know about (yet)
Tried power cycling already. Installed and ran the FXR Wifi Fix, but that did not help. I went back to try your original suggestion, turn Wi-fi before reboot. Normally I have Flight mode turned on and Wi-fi enabled. When I reboot Wi-fi is disabled. So I assumed that rebooting with Flight mode on was the same as turning Wi-fi off. But I just tried it and they are not the same. When I manually turn off Wi-fi and reboot, it does not cause the router to reboot. The problem seems to be that when I reboot with Wi-fi on the phone is still in the router's WLAN Client Table. And when the phone tries to reconnect while the router thinks the phone is still connected, it causes it to reboot. At least now I can work around it. Thanks for your help.
Shouko said:
Tried power cycling already. Installed and ran the FXR Wifi Fix, but that did not help. I went back to try your original suggestion, turn Wi-fi before reboot. Normally I have Flight mode turned on and Wi-fi enabled. When I reboot Wi-fi is disabled. So I assumed that rebooting with Flight mode on was the same as turning Wi-fi off. But I just tried it and they are not the same. When I manually turn off Wi-fi and reboot, it does not cause the router to reboot. The problem seems to be that when I reboot with Wi-fi on the phone is still in the router's WLAN Client Table. And when the phone tries to reconnect while the router thinks the phone is still connected, it causes it to reboot. At least now I can work around it. Thanks for your help.
Click to expand...
Click to collapse
Are you by any chance using a wireless N router? I've found that my Bionic will reboot my router every time I try to connect, not just on reboots. But if I turn off the wireless N and just use B+G on my router the phone works fine.
I'm on university wi-fi. I think it's 802.1x, requiring username/domain and password. Which kinda sucks cause Chromecast doesn't work. But anyway, just about every time I turn the screen on, the wi-fi appears connected, but YouTube and facebook just give loading spinners and I think eventually time out. I have to switch the wi-fi off and on again to get the wi-fi to actually work properly. I don't have the same problem with my laptop, so I'm thinking it's a problem with my Note 3. I'm using rooted NB4 if that makes a difference. Any ideas?
Anyone having problems with WiFi on stock ROM lately? Every so often the WiFi shuts off completely and can't be enabled again until restarting the watch. I have tried manually switching it back on in Settings but it remains stuck in Off mode. Factory reset it, cleared the Android Wear app and everything but it still gets this problem. It was perfectly fine for about a month or two after the WiFi update was pushed.
sierratango88 said:
Anyone having problems with WiFi on stock ROM lately? Every so often the WiFi shuts off completely and can't be enabled again until restarting the watch. I have tried manually switching it back on in Settings but it remains stuck in Off mode. Factory reset it, cleared the Android Wear app and everything but it still gets this problem. It was perfectly fine for about a month or two after the WiFi update was pushed.
Click to expand...
Click to collapse
Happens on occasion to me too, but no idea why.
Sent from my Nexus 9 using Tapatalk
Same issue here.
I have a similar problem with trying to keep WIFI on. I have to turn off Bluetooth using the Advanced Settings app (root not required) to make WIFI connect. If you don't want to use the app, try turning off bluetooth on your phone to see if WIFI will connect. I think the watch prioritizes bluetooth connection.
https://play.google.com/store/apps/details?id=com.sssemil.advancedsettings&hl=en
Edit: I turned off bluetooth on my phone and the watch's WIFI connection stays on.
Hi everyone
I have a profile that that kicks in every 30 mins from 8 am to 9pm, to sync my account. I have set it up to use wifi first, but if there is no wifi connection it will go to my mobile data instead.
Now here is the problem if my phone is on standby it always connects via mobile data regardless of a wifi connection is available. But if I am using my device at the time when the task runs then it will connect to wifi. I have checked my, keep wif on in sleep option and it is set to always.
Could anyone explain as to what this is happening?
Thanks in advance
What is your Android version?
I am currently using a custom rom called exodus which is currently based on marshmallow.
Check if Tasker is excludied from Battery Optimization and whether Wi-Fi is not deactivated while the phone is in sleep mode in Settings/Wi-Fi/Advanced/Keep Wi-Fi on during sleep.
yep tasker is excluded from battery optimisation and the allow wifi during sleep policy is always.
If you're turning wifi on with tasker action wifi turn on, try instead of that shell script "svc wifi enable".
Ok thanks, I will let you know the out come of this. I was using secure settings to enable Wifi as the command built in tasker, is not compatible from kitkat and onwards if I remember correctly.
I found out "svc wifi enable" command does exactly the same thing
Discovered I'm having the very same problem on cm13 and the batch jobs have been done by initialized mobile data. Finally found out a solution to initialize wifi instead of mobile data. I've no limited data plan, but wifi is more battery friendly.
taisto said:
Discovered I'm having the very same problem on cm13 and the batch jobs have been done by initialized mobile data. Finally found out a solution to initialize wifi instead of mobile data. I've no limited data plan, but wifi is more battery friendly.
Click to expand...
Click to collapse
Care to share the solution?
After all this is a community that people use to, find solutions to problems and to get the most out of their device. Which also help others who experience the issue for future reference.
Does anyone else know a solution to this?
HatchetEgg said:
Does anyone else know a solution to this?
Click to expand...
Click to collapse
Do you actually wait for wifi to connect?
Does your phone do the low power screen off wifi thingy?
rignfool said:
Do you actually wait for wifi to connect?
Does your phone do the low power screen off wifi thingy?
Click to expand...
Click to collapse
Yes under normal circumstances it takes about 20 seconds to connect.
No because for some reason my wifi will only switch on if the screen is on.
I also have uninstaled my custom kernel, but this issue still appears from time to time.
There's a setting in wifi connection settings that you can set to that says "keep Wi-Fi on during sleep"
This same setting is often repeated in battery apps like powernap, naptime, better battery saver etc.
Even though the wording is the same, I don't believe they are all touching the same setting so go find those apps if you have them installed.
Also, disable all native battery savers (including Samsung 2 or 3 different ones,, doze, battery optimization etc etc just to see if your problem goes away.... Which it will. At least you'll know though
I have the same problem with Wi-Fi connection.
I have a profile to turn Wi-Fi on and try to connect when certain conditions meet and the screen is off in that case.
It seems that the phone has difficulties turning Wi-Fi on and connecting to it when screen is off. Tasker does manage to turn Wi-Fi on but the phone somehow does not connect *reliably* in all cases.
Tasker is excluded from battery optimization, Wi-Fi on during sleep. I tried turning cpu on for a short time hoping that it will connect, but still no result.
The only possible solution might be turning the screen on briefly at that moment.
If anybody has a better idea, you are more than welcome to share!
alienyd said:
I have the same problem with Wi-Fi connection.
I have a profile to turn Wi-Fi on and try to connect when certain conditions meet and the screen is off in that case.
It seems that the phone has difficulties turning Wi-Fi on and connecting to it when screen is off. Tasker does manage to turn Wi-Fi on but the phone somehow does not connect *reliably* in all cases.
Tasker is excluded from battery optimization, Wi-Fi on during sleep. I tried turning cpu on for a short time hoping that it will connect, but still no result.
The only possible solution might be turning the screen on briefly at that moment.
If anybody has a better idea, you are more than welcome to share!
Click to expand...
Click to collapse
I can certainly say that turning the screen on will enable wifi, as I have resulted to this as well. But unfortunately I do not know any other solutions to try.
loogielv said:
There's a setting in wifi connection settings that you can set to that says "keep Wi-Fi on during sleep"
This same setting is often repeated in battery apps like powernap, naptime, better battery saver etc.
Even though the wording is the same, I don't believe they are all touching the same setting so go find those apps if you have them installed.
Also, disable all native battery savers (including Samsung 2 or 3 different ones,, doze, battery optimization etc etc just to see if your problem goes away.... Which it will. At least you'll know though
Click to expand...
Click to collapse
My Wifi is set to always "keep wifi on during sleep"
I'm going to resort to flashing stock rom again and see if that helps. As I am only using doze and amplify to save battery, all settings for that has been adjusted to the guide I found.
HatchetEgg said:
My Wifi is set to always "keep wifi on during sleep"
I'm going to resort to flashing stock rom again and see if that helps. As I am only using doze and amplify to save battery, all settings for that has been adjusted to the guide I found.
Click to expand...
Click to collapse
Before reflash, just disable xposed and see what you get... I will bet half of this soft taco I'm eating your problem disappears with greenify and or amplify. I'm not saying don't use them at all... Just make sure it works without them. I used to have some serious battery apps, but found after disabling, my battery was IMMENSELY better. And I had no config to deal with. But first things first... IT'S without a doubt, no question, a battery app setting or a system app that's being put to sleep that should be white listed