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.
EDIT 2: Repushed the updated settings.db file and all seemed to be working now. I had reflashed the CM rom first (but I didn't wipe data), I'm not sure if that fixed a conflict somewhere?
Either way, it's working with data now. If anyone knows what might have been going on, I'm all ears and would love to find out, but I'll keep looking around and see what might have been up
##########
Hi all,
I smashed my screen (and digitiser), and had just turned off mobile data before I dropped my phone. I know with a combo of DeskSMS, Pebble and Airdroid etc I will be able to use most of my phone until I can get it fixed. I've had lots of issues getting the sqlite3 binary on my phone, so I decided to pull my settings.db and edit it.
adb pull /data/data/com.android.providers.settings/databases/settings.db
I then used a sqlite3 editor to edit the global table and changed the mobile_data value from "0" to "1". I pushed it back on, rebooted and mobile data was on, but all my other settings appeared to have reset to default. Bluetooth state, brightness, volume etc. This was fine for using DeskSMS, but it killed my Pebble. It's also not the behaviour I would have expected.
What did I do wrong, and/or why was the rest of the DB values ignored, or changed when I pushed them back to the phone? I'm using CM 10.2, 16GB N4 and was using adb from twrp recovery (I hadn't authorised my laptop for adb before I broke the digitser).
Thanks
EDIT: On second thoughts, I think the fact the mobile data is working is due to it actually being on as a default. This would lead me to believe that by changing mobile data to "1" I am actually corrupting the settings.db and it's loading defaults and recreating it on boot. Is there any CM documentation on the possible states that mobile_data or "preferred_network_mode" can be? I can't seem to find that field in the aosp docs.
Hello,
First of all, I have never rooted my cell phone, so I guess I am still using the original ROM? I have no idea how to change a ROM, how to root a cellphone, or how to even see what mine is, just so you know. This is why I created a new thread, the other ones solutions always reffered to "change your Rom" etc.
I currently possess a HTC/T-Mobile MyTouch 4G. The issue that I'm having is the following: Everytime I try to turn my Wi-Fi on, it takes a little while, turns on for a couple seconds and then turns itself off, without any command. And it keeps going on this cycle: turning on and off (it is so fast that it cannot even recognize any saved networks, and the wifi icon does not even show up in the upper bar), until I rapidly and manually click, when it is "on", to turn off. Then it stops the cycle, with the WiFi turned off. This means that I cannot use my wireless connection, and it has been lasting for more than 2 months by now. I can access 3G normally. I have tried to "soft format" the cellphone, but it has changed nothing. (By soft format, I mean the format option included on the phone. It formatted everything, deleted my contacts, apps, themes, configurations and etc, but it was made from within the phone). Also, when it is "on", and when I click in the "Wi-Fi settings" bar, it shows nothing and it freezes the phone for a while, some seconds. Then it turns to the "off" state and returns me to the previous page automatically.
The problem aparently appeared from nowhere, I have not made a single change in anything other than installing applications. I have had an issue regarding its battery, though, which made me substitute the battery. The problem also seemed to appear with the battery issue, but it is still occuring, even though I have substituted the battery.
I thank you very much in advance, and look forward for help and a solution.
Best regards.
TZephyrus said:
Hello,
First of all, I have never rooted my cell phone, so I guess I am still using the original ROM? I have no idea how to change a ROM, how to root a cellphone, or how to even see what mine is, just so you know. This is why I created a new thread, the other ones solutions always reffered to "change your Rom" etc.
I currently possess a HTC/T-Mobile MyTouch 4G. The issue that I'm having is the following: Everytime I try to turn my Wi-Fi on, it takes a little while, turns on for a couple seconds and then turns itself off, without any command. And it keeps going on this cycle: turning on and off (it is so fast that it cannot even recognize any saved networks, and the wifi icon does not even show up in the upper bar), until I rapidly and manually click, when it is "on", to turn off. Then it stops the cycle, with the WiFi turned off. This means that I cannot use my wireless connection, and it has been lasting for more than 2 months by now. I can access 3G normally. I have tried to "soft format" the cellphone, but it has changed nothing. (By soft format, I mean the format option included on the phone. It formatted everything, deleted my contacts, apps, themes, configurations and etc, but it was made from within the phone). Also, when it is "on", and when I click in the "Wi-Fi settings" bar, it shows nothing and it freezes the phone for a while, some seconds. Then it turns to the "off" state and returns me to the previous page automatically.
The problem aparently appeared from nowhere, I have not made a single change in anything other than installing applications. I have had an issue regarding its battery, though, which made me substitute the battery. The problem also seemed to appear with the battery issue, but it is still occuring, even though I have substituted the battery.
I thank you very much in advance, and look forward for help and a solution.
Best regards.
Click to expand...
Click to collapse
My First android phone was a Motorola MB200. The WiFi never worked. Tried soft reset, flashing the stock Firmware via Pc and using wifi fixing appsbut it never worked.
Until i rooted and flashed cyanogenmod.
The Wifi miraclously started working.
Until now, i dont know why the stock rom couldnt fix that issue.
To cut things short, you could give rooting a try and it might fix your issue.
I'm at a loss here and i hope somebody can help me out here.
I've had my Note 4 for a while now, working great, but after a week or two after flashing Simpl-rom (latest)(Android 5.0.1) it started to drain battery while the screen was off.
I tried to debug this issue and found that WLAN_WAKE is preventing the device from sleeping.
Of course i did search for solutions but none of that worked, disabled all the background scanning and stuff in advanced wifi settings.
I tried to freeze all my regularly used apps planning to unfreeze them one by one to see when the issue started to show up, odd thing is, the issue persists even if i freeze all my daily-use apps.
I also noticed no networks in range show up in my Wi-Fi list, only the ones that i saved in the past (of course most showing out of range).
Using a 3rd party Wi-Fi manager works fine, it detects all the networks in range.
Disabling Wi-Fi allows the phone to go back to sleep again. However, when enabled again after that no more sleeping occurs.
The only "solution" to this is a full reboot. This solves the wakelock/batterydrain issue temporarily but not the Wi-Fi networks not showing up.
It can take 30 minutes before the issue shows up again or it can take half a day.
I also tried to detect if any apps were using background data, none that i could detect.
Even stranger, i have the exact same issue with my Galaxy S5 running Omega-rom (latest). (Android 5.0.1)
The drain on the battery isn't huge (10-15% per night), but it's there and unnecessary (i know it can do with 2-3% per night if the bug doesn't occur), obviously something is going wrong and i wish to find out what and resolve it.
Anyone experienced similar problems or knows how i can proceed to debug this issue?
I say issue because i feel these problems are related, they could be separate problems though..
So, I have been having some extremely frustrating issues with the WiFi on my 6P. I got my phone in January and I have been super happy with it except for this one issue. Since I got it, I was using the stock OS up until the April security patches came out. Before the patches, I had some issues, but the phone was still mostly usable. Especially after that update, however, I have been faced with two very irritating WiFi issues.
When my phone goes to sleep, the WiFi connection inevitably drops out. Sometimes, the WiFi will still be active but not associated, but it will frequently have also switched itself off completely.
I can only stay connected to a network for about 30 seconds tops. The connection will just stall out and then reconnect after several seconds.
In an effort to get better performance, I decided to switch from the stock OS to PureNexus (which I used and loved on my old Nexus 5) and I also flashed the ElementalX kernel. For the first few days, the WiFi performance was rock solid, but slowly it got worse than it was on stock to the point of being unusable now. Now, here's what I have already tried/checked:
The "Keep WiFi awake during sleep" option in the Settings app is DEFINITELY set to Always.
This issue is not specific to any one network. It had occurred on every network that I've used and on 2.4G and 5G networks (although it seems to be worse on 5Ghz)
I tried turning the band selection off Automatic and choosing both 2.4 and 5 only options, both just seemed to make it worse.
I've removed all apps that I installed and checked logcat for any app info that might be related to the issue. All I see is just normal stuff and then BAM! The wifi driver states that it disassociated from the AP.
I tried installing WakeLock to hold WIFI_MODE_FULL at all times. This hasn't made much of a difference with it disassociating while the screen is off.
Has anyone else experienced issues like this? I am to the point now where I might have to send in my phone under the warranty because I don't know if it's just detective hardware or what at this point. The fact that it worked well after a clean install would seem to suggest that it isn't, but the fact that it persisted across two different ROMs suggests that maybe it is.
Either way, I am at a loss and I've exhausted all the diagnostic skill that I have trying to fix this because it's so damn frustrating when you're in the middle of doing something and you can't stay connected for 30 seconds. Any help or ideas would be appreciated immensely!
My issue is the wifi connects but no internet message
Sent from my Nexus 6P using XDA-Developers mobile app
Is this with different Access Points or just at a particular wifi spot? I would factory reset the device, reboot your router, make sure you don't have any odd settings on your router like modified channel bandwidth, etc. If the 6p doesn't stay locked on, it's a hardware issue and I would do a warranty claim. My 6p wifi has been money since January with every ROM.