Hi,
Just wanted to find out how many people are having the WiFi disconnection/reconnection issue?
I'm thinking of delving deep into the frameworks to fix it, but I'm not sure if it is just a few devices (including mine) or more of a systematic problem.
Thanks
i had the same problem over the last few days. If factory reset didn't work it was a reflash. It works for me now but you never know when it's gonna crash out again.
currently running your 3.1 rooted rom and i'm in Sydney if that makes any difference.
had this issue with the leaked 3.1, Acer_A500_3.019.01_COM_GEN1. i'm using the new stock OTA Acer_A500_4.010.07_COM_GEN1 and haven't had that problem since i upgraded. i'm connecting my Iconia to a home router and a mobile hotspot and both work without problems.
A. if you're rooted, you can just delete dhcpcd-wlan0.lease located in /data/misc/dhcp and try reconnecting.
B. if not, you can try this:
1. Forget the connection
2. Reconnect to the hotspot, this time using Static IP instead of DHCP.
3. Assign a valid IP Address and connect.
i always do option B when i was having the issue.
hope this helps.
Just delete this file in term or root explorer whenever the issue occurs.
/data/misc/dhcp/dhcpcd-wlan0.lease
Sent from my A500 using Tapatalk
Related
For those of you, who like me ,flashed JK6 or newer 2.2 rom , and ended up with WiFi issues , here's a fix posted by another user..... with wifi off ,
First using rootExplorer or adb , delete ....data/wifi/bcm_supp.conf
Restart then ...
With rootExplorer or adb, again, delete.... data/misc/wifi/dhcp/dhcp_list ..
then turn on wifi and BAM!!!! .... Just sharing some info i found ... hope this helps...
Gadgeteer81 said:
I had the same issue on my Tab and my Bell Vibrant (after upgrading to Froyo). The devices would get stuck in "Obtaining IP Address".
This is what worked for me:
To Fix Android going into “Obtaining IP Address” loop:
rm /data/misc/dhcp/dhcp_list
It seems to come from the fact that the phone requests its previous IP address to the access point, without any discover message, whereas the lease has expired from the AP point of view...
The previous leases are stored in /data/misc/dhcp/dhcpcd-eth0.lease and /data/misc/dhcp/dhcp_list. You just have to remove the second file (dhcp_list) to force the phone to start a new dhcp negotiation.
Click to expand...
Click to collapse
cant find it...on my 2.21 is only config and and another thingy...
I had wifi issues ounce and nothing worked to fix it but resetting my router and modem
AustinKnight45 said:
I had wifi issues ounce and nothing worked to fix it but resetting my router and modem
Click to expand...
Click to collapse
Though it makes no sense to me, I found the same to be true. Resetting DHCP did not fix it. But restarting the router finally did.
On the off-chance it matters...
Linksys E4200
1.0.03 build 14
Hi, Today I unrooted Nook, updated to 1.0.1, and rooted it again, all perfect.
Then I installed Root Explorer, and pushed the wpa_supplicant on the sdcard.
Then I copied it from my sdcard to /data/misc/wifi, and overwritted the default one, I did this before and all OK, I need to do this because my university has TTLS PAP and I can't configure it from the B&N Wifi manager, but I forgot I had Wifi connected, and now, it says Unable to start Wi-fi, I tried putting again the default one, but the same happens.
I powered off the Nook 2 times but the problem still.
What should I do? Try a factory reset? I'm scared :S
PD: I rooted with TouchNooter so I don't have a backup image
Sorry for my english too xD
EDIT: I solved it deleting the supplicant and turning on wifi, it created a new one and solved it. Sorry for the post :\
EDIT2: I finally solved it, I had to add a new network from the manager, saved it, and then open Root Explorer, and edit the supplicant manually changing the WPA-EAP to TTLS and the authentication phase to PAP. I don't know why it happened, on the 1.0.0 I did the same and nothing happened :S.
Sorry for the inconvenience ^^u
Just a note, if you root with TouchNooter you can unroot with nookRestore (by ros87, available at http://forum.xda-developers.com/showthread.php?t=1289233 ) without any difficulty at all. If you ever mess anything up, it's a good way to fix things. A factory reset doesn't typically wipe everything so it's not something you really need to worry about.
another note. You can't see and connect to adhoc p2p (non access point) networks like a computer or joikuspot for tethering. Dont know why. Might be easy to enable...
Yeah I had to use nookRestore 2 days ago, I had some problems and needed a reset.
I love there's an app for tunneling by SSH your nook, so I can connect to IRC in my university
By the way, I just found out the NookTouch can only see accesspoints - no adhoc networks. So you can't connect to your computer direct. But of a bummer if on the move - you'd have to carry round a WiFi access point.
Hopefully this can be enabled.
Just thought I better let people know because I was going crazy trying to figure out why my Nook wasn't seeing some networks!
Thread to discuss how to solve wifi problems on cm7 kangs with the new kernel & wifi driver, like my kang here: http://kan.gd/1h7f
updated: wifi problem fixed, fix here: http://kan.gd/1h8g flash with clockworkmod.
problem with phone not waking up after long calls still exists, that will be fixed tomorrow.
Wbaw, I installed your latest KANG (cm-7.2.0-blade-KANG-wbaw-120225), and also have the same wifi problem, like here. (Can not post there, because I haven't got the 10 posts)
Wiped and format everything before install. It says "scanning...connecting...disconnected". I've tried everything from changing the encryption, to changing the SSID, nothing helped. I have a Linksys WAG54GS router, "G" network, channel 10 - 2.457GHZ, encryption is WPA2-PSK. Attached a logcat log from boot, if it helps recognizing what's the problem.
With other KANG and with older kernel & wifi driver, my phone connects to my home wireless network.
Thank you for your help!
PoTT3R said:
Wbaw, I installed your latest KANG (cm-7.2.0-blade-KANG-wbaw-120225), and also have the same wifi problem, like here. (Can not post there, because I haven't got the 10 posts)
Wiped and format everything before install. It says "scanning...connecting...disconnected". I've tried everything from changing the encryption, to changing the SSID, nothing helped. I have a Linksys WAG54GS router, "G" network, channel 10 - 2.457GHZ, encryption is WPA2-PSK. Attached a logcat log from boot, if it helps recognizing what's the problem.
With other KANG and with older kernel & wifi driver, my phone connects to my home wireless network.
Thank you for your help!
Click to expand...
Click to collapse
I'll probably have to make a couple of test kernels for you, it looks like the new wifi driver is failing. It's either the new driver & kernel source or wifi undervolting, but I don't think it's due to undervolting.
You can also try this kernel: http://forum.xda-developers.com/showpost.php?p=22887053&postcount=92 it's the same except I removed some useless looking files from the wifi driver for the kang, they're in that package.
I'll make a couple of packages tomorrow for testing.
If you have any problems with my kernel, please use the issue tracker, open an issue there & I can respond: https://github.com/John-Kenney/zte-turies-35/issues
I will open an issue in the issue tracker tomorrow.
Right now i have to get data back from my SD card, because i accidentally formatted it...
You probably know that by now, that the new wifi driver works only with 802.11b network, so if your router was set to "G-only", the phone could not connect. Of course mine was set to that. I set to "mixed", and it connects without problem.
Can't wait to test your kernel for the GPU overclock Thanks!
Seems strange, it seems to connect at 'g' speeds for me, but my router is set to 11b/g/n auto.
It looks like the new wifi driver causing the problem rather than the kernel, unfortunately I think it's the only wifi driver that works with the new kernel source.
fixed: http://kan.gd/1h8g
A brief history of what I've been through before this issue:
My Pro came with 2.2 Froyo from verizon, then flashed Vanilla's CM7 v8 (which is the absolute best ROM I've tested for this phone); no wifi mac address problem here. Then I messed up by installing another recovery, semi-bricked, and forced to SBF to stock Verizon 2.3.3 gingerbread. Then rooted with Pete's Motorola Root Tools, flashed recovery, kernel, wiped, and once again to Vanilla's CM7 v8.
After all this mess, my Wi-Fi MAC address is changing every time wifi goes off/on or reboot, and this is pretty inconvinient for me since both my workplace and home networks have MAC address filter, and changing the router configuration every time I'm forced to reboot my phone is not an option.
YES, I've flashed the Kernel that the developer provides with the ROM.
YES, I've tried reflashing both the rom and the kernel the way the diveloper suggests, doing system/data/cache wipes in between.
NO, this was not happening the first time I've flashed this ROM.
Any suggestions?
Please help!!
SOLVED READ BELOW!
Fix found
Here's the MAC address fix for your Pros running CM7. If you have had an issue connecting to wifi, it's probably because each time the device's wifi is restarted, a new MAC address is generated which will clog up your router as you can easily run out of IP addresses to lease to each and every new MAC address that's generated each time your device's wifi is restarted. The link can be downloaded here. The instructions are simple:
1. Flash CM7MAC.zip (attached) in clockwork no need to wipe anything
2. "Activate it" by going into the terminal emulator app, typing "su" (without the quotes) then typing "mac-address-fix.sh" (without the quotes). A bunch of weird symbols should come up, but that's normal.
What this does is it auto-generates and writes your permanent MAC address to a file called called nvs_map.bin under /data/misc/wifi/nvs_map.bin. It will remain there and your MAC address will remain the same unless you wipe your /data whereas you will simply have to redo it
Note: if you get an error message in the terminal after doing the fix, make sure your Wi-Fi is turned on and you're connected to a network
For CM7, download -->
hi!
my phone does the same, each time WIFI is turned on it generates a temporary MAC address, but the file you mentioned (nvs_map.bin) can't be found in /data/misc/wifi...
could you help me please how the map_gen file is generated? i don't have CWM so i can't flash the zip file, but i have a terminal and two hands
thx
Do we have anything for Android 4.2?
negro_acdc said:
Here's the MAC address fix for your Pros running CM7. If you have had an issue connecting to wifi, it's probably because each time the device's wifi is restarted, a new MAC address is generated which will clog up your router as you can easily run out of IP addresses to lease to each and every new MAC address that's generated each time your device's wifi is restarted. The link can be downloaded here. The instructions are simple:
1. Flash CM7MAC.zip (attached) in clockwork no need to wipe anything
2. "Activate it" by going into the terminal emulator app, typing "su" (without the quotes) then typing "mac-address-fix.sh" (without the quotes). A bunch of weird symbols should come up, but that's normal.
What this does is it auto-generates and writes your permanent MAC address to a file called called nvs_map.bin under /data/misc/wifi/nvs_map.bin. It will remain there and your MAC address will remain the same unless you wipe your /data whereas you will simply have to redo it
Note: if you get an error message in the terminal after doing the fix, make sure your Wi-Fi is turned on and you're connected to a network
For CM7, download -->
Click to expand...
Click to collapse
Note: if you get an error message in the terminal after doing the fix, make sure your Wi-Fi is turned on and you're connected to a network
** How can I turn on Wi-Fi when there's no mac-address? No mac-address, no network! **
Hi,
I tried running this shell script but seems like its not executed successfully ... reason i believe so is ...
1. i dont see any wierd symbols coming up ... just a pause for a couple of seconds.
2. i dont see the "/data/misc/wifi/nvs_map.bin' file in the said location.
Please help.
thnx
Mac addrs and imei problm
Hi, in my gionee ctrl v4s the problem is two types, i have seen after i was updated lollipop , one problem is tht, whn i reboot my phn thn my mac address automatically changed everytime.. And 2nt problem is tht my imei also erased whn i updated lollipop so plz help me...
this is the best solution
https://www.youtube.com/watch?v=8ejnFB5i5o8
Is there a solution for this in Marshmallow?
yes this is the best solution
Thanks. This process worked well on my lenovo s650 cyanogenmod 13 custom rom. But could someone explain what is really happening through this solution?
my oppo f1s 64gb, it was dead, recovered working fine, but each restart it changes mac id, and remove all wifi stored connections
is there any solutions?
Seems its pretty common for MediaTek chipsets.
Thanks for the video link!
Hi all. I have the following problem, which happened sometime on 4.2.2 and there is still present in 4.3. Note here that I flashed the whole image of 4.3 using adb but without wiping (that is I deleted the –w in the bat file of the image)
So, my nexus 4 does not keep the passwords of some routers wifi and I have to manually login to them every time to connect. This happens in different modems/routers, including my house’s.
Strange thing is that sometimes, even if it is connected, wifi’s name is shown in the list without saying connected underneath. And if I choose it, it prompts me to enter the password to connect.
I opened the wifi list using root explorer (/data/misc/wpa_supplicant.conf) and I deleted the several references of those specific routers but problem still occurs.
Now, is there something I can do to avoid the whole system format? I guess that something is causing a cobflict, but I really can’t think of what that is.
Any ideas?
Thanks a lot.