After upgrading to JK4 via Kies I've noticed some strange Wi-Fi behaviour. It seems to manifest at different times and for no apparent reason, so I'm starting a thread to see if a) anyone else has this issue and b) if so, how does it manifest for them.
First manifestation: after turning on Wi-Fi through Notifications the text switched to "On" but the Wi-Fi symbol did not turn green. Going into the Wireless and Network settings on the phone caused a temporary lockup, when it did let me in Wi-Fi was showing "Error". A reboot of the phone fixed it, temporarily.
Second manifestation: after turning on Wi-Fi through Notifications the text switched to "On" and the Wi-Fi symbol turned green, but it did not connect to my wireless network automatically like it should. Going into the Wireless and Network settings on the phone caused a temporary lockup, when it did let me in Wi-Fi was rapidly switching from a "Turning on" state to "Turning off". It did this about 10-15 times in a few seconds then went to "Error". Turning on and off the Wi-Fi again solved this issue.
Every time I solve this it seems to come back within a 24 hour period. I didn't have this problem (from what I can see) on JK3. I factory reset before and after flashing to JK4, and I flashed JH2 back just to be on the safe side beforehand.
Let the discussion begin!
got_milk said:
After upgrading to JK4 via Kies I've noticed some strange Wi-Fi behaviour. It seems to manifest at different times and for no apparent reason, so I'm starting a thread to see if a) anyone else has this issue and b) if so, how does it manifest for them.
First manifestation: after turning on Wi-Fi through Notifications the text switched to "On" but the Wi-Fi symbol did not turn green. Going into the Wireless and Network settings on the phone caused a temporary lockup, when it did let me in Wi-Fi was showing "Error". A reboot of the phone fixed it, temporarily.
Second manifestation: after turning on Wi-Fi through Notifications the text switched to "On" and the Wi-Fi symbol turned green, but it did not connect to my wireless network automatically like it should. Going into the Wireless and Network settings on the phone caused a temporary lockup, when it did let me in Wi-Fi was rapidly switching from a "Turning on" state to "Turning off". It did this about 10-15 times in a few seconds then went to "Error". Turning on and off the Wi-Fi again solved this issue.
Every time I solve this it seems to come back within a 24 hour period. I didn't have this problem (from what I can see) on JK3. I factory reset before and after flashing to JK4, and I flashed JH2 back just to be on the safe side beforehand.
Let the discussion begin!
Click to expand...
Click to collapse
I quickly tried out after reading your post, and I did confirm your first issue happening, but only when I turn my Wi-Fi on and off really quickly. Also my phone didn't lock up as you described either. Basically, I could only make that issue to surface once I turn off the Wi-Fi, and then turn it back on as soon as my phone reports it is disconnected. When I go into Wi-Fi settings, it does say "Error" there, but if I check the "Wi-Fi" there again, it connects automatically.
I almost never use Wi-Fi because I get 6GB of data, but I can see this becoming a very annoying issue if you have to use Wi-Fi frequently.
Edit: Actually, I ran into a different issue just now. I kept on playing around with my Wi-Fi, and confirmed this happening: Wi-Fi text turns to "ON" but the icon doesn't turn green. When I go into settings, it says "Turning Wi-Fi On.." or something similar and is stuck there. I wasn't able to turn on nor off the Wi-Fi. Reboot fixed issue...for now I guess.
I have also had this issue but I believe it has to do with trying to turn on wireless when your preferred network has a very weak signal. When I'm next to my router, I can turn wi-fi on and off rapidly with no issues. I have only had the issue in my room which has a much weaker signal.
Sent from my GT-I9000M using XDA App
i was having problems with my wifi today...i wasnt able to pickup any wifi signals and i couldnt manually turn the wifi on either...i got a few force closes on some apps and decided to reboot the phone, hopefully sovling the problem...instead i got stuck in the boot loop at the i9000m logo and now my internal sd card is done....hopefully i can return this pos at bell(im on rogers) and do a hup through rogers for the iphone4...at least thats a stable device.
dpvu said:
I have also had this issue but I believe it has to do with trying to turn on wireless when your preferred network has a very weak signal. When I'm next to my router, I can turn wi-fi on and off rapidly with no issues. I have only had the issue in my room which has a much weaker signal.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
I've never tested right beside the router, but my room is next to the room which has the router so I would think I'd have a fairly strong signal.
Interesting, though...
dpvu said:
I have also had this issue but I believe it has to do with trying to turn on wireless when your preferred network has a very weak signal. When I'm next to my router, I can turn wi-fi on and off rapidly with no issues. I have only had the issue in my room which has a much weaker signal.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
I tested my Wi-Fi pretty much right beside my router as well...like less than 3 feet away. My phone was reporting it was seeing an "excellent" signal.
Sent from my GT-I9000M using XDA App
I find my wifi on my phone to be pretty solid.
I have an occasional issue where it does not see my wifi router at work, but all I do is turn it off / on and off she does. Just happens with the work router. Never had an issue with my linksys at home.
I've experience this issue with JH2 and it was caused by a change to fast in the settings. Just give your phone some time to connect and get identified on the network before you turn it off ans don't torn it on right after you disconnect it and you should be fine.
Been having the same issues since upgrading to JK4. Wifi gets stuck in "enabling" state occasionally when it try to turn it on. Sometimes I have to go as far as restarting the phone to get it to work again. Not a huge deal but still a nuisance.
I have seen both of these situations occur once after applying JK3 from Odin. It was shortly after booting it up for the first time including the "ERROR" text. I attributed it to a one-time glitch and it has not come back since. When I am home I force WiFi on and leave it in that state until I leave the house for work the following day so I am not constantly messing with the settings.
I get a similar issue butt only when activating my mobile AP.
Sent from my GT-I9000M using XDA App
I've been having a similar issue with my wifi since upgrading to JK4. I've gotten the "error" message on enabling wifi, but as others have mentioned it may be because I'm re-enabling it too quickly after turning it off. However, in one instance yesterday I tried re-enabling it several times after turning it off via the control widget and was ultimately forced to reboot before it worked again. Also, this morning I found that after leaving home and coming to work, I was still only seeing the wifi hotspots near my apartment rather than the ones in my new location (one of which I have saved and automatically connect to). I had to reset the wifi to find the local hotspots. Other than these wifi issues, I'm really loving JK4 so I just hope they get sorted out.
I recently started Bluetooth to transfer some files to another phone and could not get the file to transfer. Since doing this I have not been able to turn off Bluetooth on my Aria (the sending phone). I am running stock 2.1, rooted.
Could Bluetooth be still trying to send the file and therefore not shutting off? Is there any way of fixing this or has anyone ever heard of this problem before? Would clearing the dalvik cache fix this w/o loosing all of my data and settings? What would clearing the cache partition do anyway?
I have tried rebooting several time with no luck. Any suggestions are welcome.
-Gary
BatteriesIncluded said:
I recently started Bluetooth to transfer some files to another phone and could not get the file to transfer. Since doing this I have not been able to turn off Bluetooth on my Aria (the sending phone). I am running stock 2.1, rooted.
Could Bluetooth be still trying to send the file and therefore not shutting off? Is there any way of fixing this or has anyone ever heard of this problem before? Would clearing the dalvik cache fix this w/o loosing all of my data and settings? What would clearing the cache partition do anyway?
I have tried rebooting several time with no luck. Any suggestions are welcome.
-Gary
Click to expand...
Click to collapse
You can try clearing the cache and dalvik cache, you won't lose any settings or data or anything like that. It also may be worth your while to look at what services are running (settings > applications > services (<- that was off the top of my head, could be a little different)) and see if you can stop the bluetooth service.
That's what I would do if i were in your situation.
Well, still no solution. I've tried clearing the dalvik and cache partitions, tried killing all of the processes related to bluetooth. When I try to uncheck the Bluetooth setting in wireless and networks it says "turning off..." removes the icon from the notification bar and then stops but never updates the menu item to "Turn on...". It is stuck at "turning off...". I'll have to scan for it with another phone to see if it is indeed off. Very odd. It may be time for 2.2 liberated.
BatteriesIncluded said:
Well, still no solution. I've tried clearing the dalvik and cache partitions, tried killing all of the processes related to bluetooth. When I try to uncheck the Bluetooth setting in wireless and networks it says "turning off..." removes the icon from the notification bar and then stops but never updates the menu item to "Turn on...". It is stuck at "turning off...". I'll have to scan for it with another phone to see if it is indeed off. Very odd. It may be time for 2.2 liberated.
Click to expand...
Click to collapse
I didn't say process, i said service
bump
I'm having the same issue here on my HTC Desire running froyo. Any solutions?
Here is what worked for me. I am rooted. I have bloat freezer installed. Had bluetooth share frozen. This morning I accidentally hit bluetooth widget instead of wifi. Bluetooth would not turn off just as OP described. I defrosted bluetooth share, powered off and back on, turned off bluetooth thru settings instead of trhu widget. And it worked. Off now. My theory is freezing bluetooth share had something to do with it but I'm no expert.
So i wake up this morning and decide to check my email. So i turn on my wifi. When i came back to check it the wifi wasn't turn on. I tried again to turn in on but it says "Unable to scan for network"
It was working perfectly fine last night.
I already tried to restarted by holding the power button and pressing restart and by taking the battery out, but it still keeps saying "unable to scan for network"
oh and I'm running a completely stocked phone.
Could my wifi chip just crapped out on me ?
Restart your phone again and restart your modem/WiFi router. See if works after that. Do the modem and router first before you restart your phone. Disable WiFi on your phone before rebooting.
I tried that also but no luck.
When i try turning the wifi on and after it gives me the message the wifi turns its-self back off.
Same thing happens when trying to make a hotspot.
Anybody ??????
try restore factory settings
So i did a factory reset on the phone and still no luck.
My wifi still doesn't turn on at all.
HI, i had no problem with Wifi. Since last time I got to the hostel and have a weak access point I have a bug with Wifi : when I activate it, it says "connecting... ". But nothing happens, it doesn't list access point around me too.
I found a way to make it work: I uncheck Wifi, check airplane mode then check wifi again. It works but I have to do it every each boot or wifi deactivation..
Is there a parameters or cache file stocking the weak ap I was trying to connect when the bug appears at first?
Thank you
Problem not solved but changer: now it work but wifi is never activated at startup.. can't force it to auto activate. Strange...
Anyone else have this problem? I just started having it, first on Phiremod 6 and now just updated to 6.3 hoping for a fix, but no dice.
I have sent back 2 nooks to BN for exchange because of this issue. I didn't know doing the airplane mode thing would temporarily fix the issue. I even did the 8 hard reset and restore and the nook would get stuck on finding wifi window - turning on wifi but nothing would happen. My nook was manualnooted 1.2. Strange?
I'm on nightly-87, Dal's 1.2GHz OC Kernel 5/23, and I'm experiencing something very similar. I went from 7.0.2 to N87 without a hitch, but I immediately started to see the WiFi icon go gray and lose it's connection. I was forced to restart WiFi as a remedy. As of today I'm getting something closer to what you're talking about; when WiFi turns on, the nook will infinity cycle through: disconnected->connecting->disconnecting->scanning. I've wiped Cache, Delvik-cache many times to no avail. Also tried re-flashing N87 and the OC Kernel, which did not work. I'm still not able to connect to my home network(netgear, WPA). But, after enabling/disabling airplane mode, I was able to connect to my LG vortex and obtain the interbuttz.
The last time I did a fresh install was around N20 something. As far as possible causes to this erratic and ethereal bug, my money is on certain update paths for both the OS and Kernel having different remnants. Example: with 87 different experimental OS installs and, to a lesser degree, the three different stable OS installs. There are technically !90 different upgrade paths. Compounded by being paralleled by kernel installs, but I believe when a kernel is updated the former is completely replaced instead of merged. I'm not calling out the Dev's, it would be nearly impossible to foresee and head-off all of the permutations of merging 87+ releases.
I'm no expert, just my two-cents. I'm not really concerned about this as a long term bug. There are fine people hard at work, and unfortunately have far more pressing issues to contend with. It's a sad reality that community driven projects, notably the nook Color, rarely reach maturity or complete/efficient hardware-software integration before the allure and newness of a product wares off.
As a consumer of .rockbox, a Linux based OS for G5.5 ipods and below, Of which I've been using for years and years. And, I would say it's just now becoming 'perfect', even with it's lack of support for many peripheral devices. I'm long term with my gadgets.
I'm rambling now.
Hope this helps to narrow down symptoms and possible causes.
It seems that my problem is a known issue of cm7 (when you click airplane it stay on forever but the checkbox remains unchecked). Try a tool from market that shown me the airplane mode and unchecked it from here. Since I didn't reboot from that test I don't know if it's solved for now.
my NC on CM7 just stopped connecting too
I turned on my NC this morning and my WiFi no longer works either.
All of my hotspots say 'not in range'.
I tried all of the tools I have to turn off 'airplane' mode (just in case it was on)
but, nothing seems to get me 'out of the mode.
What can I try next?
Wifi miraculously auto-fixed itself, and then broke itself again
fulko said:
I turned on my NC this morning and my WiFi no longer works either.
All of my hotspots say 'not in range'.
I tried all of the tools I have to turn off 'airplane' mode (just in case it was on)
but, nothing seems to get me 'out of the mode.
What can I try next?
Click to expand...
Click to collapse
While researching potential solutions... CM7 auto-fixed itself after about 15 minutes.
I didn't touch it.
All of a sudden I heard the Gmail tool beep at me with new messages and the market with a few apps updates that were available.
Now it seems to be working fine.
I spoke too soon, I just powered off and on again to see if the problem was fixed
permanently, and its not... its back to the 'not working' state.
(I hate when that happens, because I don't know what caused it, and I don't know what fixed it!)
This happened (WiFi not hearing any APs) to me a few times with nightly 87, but hasn't happened since I upgraded to n94.
fulko said:
While researching potential solutions... CM7 auto-fixed itself after about 15 minutes.
I didn't touch it.
All of a sudden I heard the Gmail tool beep at me with new messages and the market with a few apps updates that were available.
Now it seems to be working fine.
I spoke too soon, I just powered off and on again to see if the problem was fixed
permanently, and its not... its back to the 'not working' state.
(I hate when that happens, because I don't know what caused it, and I don't know what fixed it!)
Click to expand...
Click to collapse
SAME! Bump.
Same issue.....latest nightly on VG SDcard solution. Never had a problem until recently. Was runnning 7.03(flawlessly) then suddenly started experiencing the issue, flashed the latest nightly (113)...worked for a bit, rebooted and now nada..... just sits at connecting..... then goes to disconnected. Cycles every couple of minutes.....
Any suggestions on what to look at?
**** Note ; WIFI works fine when I boot to EMMC (Nook 1.2) . So I do not believe this to be a hardware problem.
I was just looking for this issue also.
I was doing great with nightlies and the OC 6/18 kernal, this morning I updated to the Nightly 114, and I received no wifi connection on booting up.
So I did all the normal things (1. turn on/off the airplane mode - No change, 2. fixed permissions - no change, 3. restarted multiple time (aft all the prior changes) - no change) Ok I thought, I will go back to my previous nights backup (Nightly 113). But I still get no wifi. The widget says trying to connect, but none of my networks are showing up within range. I run wifi analyzer and I see NO networks (normally I would see about 5 to 7 of them).
So I begin stepping back, I reinstall the Nightly 113, with No OC, and while the wifi is off on bootup, once I 'turn it on' now I see my networks.
I'm cooking with gas now, so I install the OC 6/18 - No Wifi
So I install the OC 6/13 - Still no Wifi
Both times, the Nook boots up with the wifi 'off' so I turn it on, but no connection or sensitivity.
I again reflash the Nightly 113 only and while it again boots up with wifi 'off', I am able to turn it on and it actually sees my networks.
So strange, I am stuck without my OC kernal, but as least the nook works again.
Does anyone have an idea why this is happening to people?
Thanks
onclebob said:
It seems that my problem is a known issue of cm7 (when you click airplane it stay on forever but the checkbox remains unchecked). Try a tool from market that shown me the airplane mode and unchecked it from here. Since I didn't reboot from that test I don't know if it's solved for now.
Click to expand...
Click to collapse
The issue in the OP isn't related to the one you're talking about. Try deleting one or more of your remembered wifi access points with wifi on. Let it rescan and, if it's not some other issue, it should find your access points and connect.
Suffering this same issue as well on my Nook Color. I believe the problem lies under /data, and here's why. First, I made a backup of /data, and then wiped everything:
* I restored my device to factory 1.2: Wifi works
* I flashed CM7 nightly 113: Wifi works
* I flashed dalingrin's OC'd 6/18 kernel: Wifi works
* I restored /data from my backup: Wifi is stuck at "Connecting..."
I thought it might have something to do with the settings.db file under /data/data/com.android.providers.settings/databases/, but when I deleted that file and rebooted, it made no difference with the Wifi problem.
Something under /data might have a problem with the latest CM7 builds, but I couldn't say what exactly. I'm not an expert at this stuff, so I can only share what I've observed and tried for myself.
Hi. I have the same problems with Wifi since this morning. Is there any other solution then turning on and off airplane mode? thx
Formatted /system and /cache, and wiped the Dalvick cache, then flashed only CM7 nightly 143.
The problem still exists. Wifi is stuck at "Connecting..." Has anyone found a solution to this? It's obviously something to do with a setting/file under /data, because if I format /data, Wifi works like normal. But when I restore my backed up /data, Wifi is stuck at "Connecting..."
I think I found a solution. This worked for me, so I hope it works for others.
Shortly after writing my previous post above, I decided to play around with my NookColor, to see if I could get the Wifi to work normally again. Here's what I did, which fixed the "stuck at connecting" problem for me:
1) Go to Settings > Wireless & networks > Wi-Fi settings
2) Check to enable Wi-Fi, if it's not already enabled
3) Click every wireless network in your list and choose "Forget"
4) Make sure every wireless network is forgotten
5) Check to disable Wi-Fi
6) Check to re-enable Wi-Fi
Instead of "Connecting..." I now see "Scanning" and it picks up the routers around me! I selected my router, and it connected! I am now able to browse the web, update my apps, and all seems to be working normally now!
You can also watch if airplane mode is really off using Android assistant:
https://market.android.com/details?id=com.advancedprocessmanager&feature=search_result
it helped me with this problem
flansuse said:
I think I found a solution. This worked for me, so I hope it works for others.
Shortly after writing my previous post above, I decided to play around with my NookColor, to see if I could get the Wifi to work normally again. Here's what I did, which fixed the "stuck at connecting" problem for me:
1) Go to Settings > Wireless & networks > Wi-Fi settings
2) Check to enable Wi-Fi, if it's not already enabled
3) Click every wireless network in your list and choose "Forget"
4) Make sure every wireless network is forgotten
5) Check to disable Wi-Fi
6) Check to re-enable Wi-Fi
Instead of "Connecting..." I now see "Scanning" and it picks up the routers around me! I selected my router, and it connected! I am now able to browse the web, update my apps, and all seems to be working normally now!
Click to expand...
Click to collapse
That worked for me, thanks a ton!
flansuse said:
I think I found a solution. This worked for me, so I hope it works for others.
Shortly after writing my previous post above, I decided to play around with my NookColor, to see if I could get the Wifi to work normally again. Here's what I did, which fixed the "stuck at connecting" problem for me:
1) Go to Settings > Wireless & networks > Wi-Fi settings
2) Check to enable Wi-Fi, if it's not already enabled
3) Click every wireless network in your list and choose "Forget"
4) Make sure every wireless network is forgotten
5) Check to disable Wi-Fi
6) Check to re-enable Wi-Fi
Instead of "Connecting..." I now see "Scanning" and it picks up the routers around me! I selected my router, and it connected! I am now able to browse the web, update my apps, and all seems to be working normally now!
Click to expand...
Click to collapse
Man, you really had my hopes up with this one. You're the first person I've seen say every remembered network needs to be forgotten. But I followed your steps exactly, and my NC still will not connect. It sees all wireless networks available. It knows which ones are open and which ones are secured. I can go so far as to enter the password and click Connect. It says "Obtaining IP address from...", then quickly flashes "Unsuccessful", then "Scanning...", then loops indefinitely. I even took your steps one step further and rebooted before turning WiFi back on. Still doesn't work.
This is the fourth time this has happened to me. And every time, the only way I've been able to fix it is to completely reinstall CM7. That's not a fix, that's a wrecking ball. I'm pretty desperate to find a fix because my NookColor has become a joke, almost unusable. Right when I get it to the point of enjoying it and getting it set up just the way I want it, this happens. And the damn thing is useless without WiFi.
I also installed the latest nightly build, which was from last night. Nothing.
Hi, yesterday I had my nexus 7 charging, when I checked after a couple of hours, I noticed it was fully charged, but the wifi icon was white and "empty" instead of blue and "full", so I went to disable the wifi and enable it again, but it got stucked at "turning on wifi".
Mine is on 4.2.1 and it's rooted, but with the google factory rom, and clockwork recovery. I reset the nexus, same issue, so I reset the nexus again and went to the bootloader and wiped the cache, got the same, so I did a factory reset and got to the setup screen, chose the language and it goes to select wifi and it's still stuck at turning wifi on, and I can pass that screen, is there a way to fix it? is my wifi radio toasted? I need help and I searched on the forums for something like this and I could not find anything, any help will be appreciated.
anyone? I need help with this.
Sounds more like a hardware problem than a software problem, although on a different device (android phone) I could get similar symptoms to appear after fooling around with certain WiFi tether apps. At least one difference between that case and this one though, was that I was able to always clear the problem up with a reboot.
You might be able to get more insight by looking at "dmesg" output or possibly a dumpstate report.
Turn WiFi off, reboot, capture dmesg output, turn WiFi on (fails), capture dmesg output again. (Point of the first capture is only to get approximate starting time of the WiFi fail time - the dmesg timestamps are in seconds since boot, not UTC or local TZ)
good luck