Develop Bugs

Wifi not working after rooting

Help My wifi won't even try to connect. It will turn on and i can see my router but when i click connect nothing happens. It worked when i got the phone, i used toast's root then flashed to OMJ EVO 2.1 Eclair v1.3. Didn't work tried flashing with Supersonic_1.32.651.1 and still nothing. then i tried wiping the data and delvic cache and restore with the original backup i made and i still got nothin any ideas

did you flash the most up to date radio?

I was having this problem too, it may be different. My power control would show with the green bar like it was waiting for IP but would not go the bright green indicating it was connedted. If I did it from wireless and Networks it would show "unable to connect" you can find my solution here: http://forum.xda-developers.com/showthread.php?t=699752
I recommend trying this first:
In connect bot on phone, navigate to with
# cd /data/misc/wifi/
then do
# chmod 777 wpa_suplicant.conf
now try to connect from the Wireless and networks in the settings menu. If you can you probably need to do what I did to set it.
Just one question first though, Did you try rebooting the phone? Simple things some times.

Thank you for the input. i've updated radio to 1.39.00.05.31 still does not work. Then i tried changing permissions on the file you recommended...still no luck.
When i go into wireless & networks Wi-Fi will have a disconnected below it. when i go into wi-fi settings i see my home network with "not in range,remembered" under it. After about 3 secs. it changes to "remembered,secured with wep". i'll select it and push connect and nothing happens, it doesn't even appear to be trying to connect.

i noticed something today. Previously when i tried changing those file permissions i simply did exactly what you had said. Did some looking around and the /data/ folder is empty. I did finf the file in /etc/wifi/ directory.

[SOLVED] CM7 | Wifi needs a minute to connect | started with nightlys about Jan.

Hi all,
having troubles with my Wifi. It needs a minute to connect and doesn't connect when screen is off eventhough settings are to always on.
I started asking in CM7 nightly thread about my problem but it's better to have a new thread for that.
So far I didn't find a solution.
I tried:
- replace tiwlan_drv.ko with new one by deleting old one
- compared wpa_supplicant, tiwlan.ini and other data in that folder without significant outcome
- tried old 2011.11.16-nightly where it still worked
Anyone got an idea what I have to copy from my old nightly where it still worked?
This is what happened:
measel said:
sorry, for bringing this up again, since I'm the only one having this issue but I just collected a few logs. maybe someone has a clue what is going on there:
Code:
2012-02-13-19-35-37_wifion.txt > when turning wifi on it needs more than a minute to connect
2012-02-13-19-37-37_wifiscan.txt > wifi instantly connects after starting 'wifi analyzer' app or open the wifi settings window
2012-02-13-19-45-25_wifiscreenoff.txt > when screen is of, wifi doesn't connect eventhough settings are to "always on"
/edit: ok i just tried to read the logs myself and I think you can't really see any reason for that behaviour... am i right that the possible settings I have to look for are in the 'tiwlan.ini'?
Maybe someone provide me a backup of his/her tiwlan.ini for comparison... (I don't have any idea what I'm doing but that doesn't mean I couldn't try. )
I added my tiwlan.ini as well
/edit: compared to tiwlan.ini: no differences. Must be something else.
Click to expand...
Click to collapse
measel said:
Could you please check your logs if it needs exactly a minute to connect? could be a proof that there is some setting involved.
Click to expand...
Click to collapse
measel said:
I just went back to an older version: 2011-11-16 and the problem was gone.
Thank you.
/edit: Ok might have bin the wrong folder... did it have to be /data/misc/wifi/? Argh it's hard when one knows nothing. :|
/edit2: I'm so sorry: I compared wrong files and folders (system and data). I come back here, when I really found something. *shame on me*
Click to expand...
Click to collapse
[] AL [] said:
I'd just copy the module tiwlan_drv.ko [in /system/lib/module] from that older nightly and replace it on the newer build first.
Don't forget to set its permissions afterwards..
You can do this with RootExplorer or with Terminal (from the app tray) by entering these 5 lines:
Code:
su
cd /system/lib/module
mount -o remount,rw /system/
chmod 644 tiwlan_drv.ko
chown 0.0 tiwlan_drv.ko
and reboot.
Click to expand...
Click to collapse

none of these solutions worked right?
I have wifi problems too. Wifi in CM7 is crap

No wifi problems here... I'm using my personal home wifi network most of the time, but other networks works well too.
Red lense German Vodafone Froyo based
CM7.2 Nightly 02102012

I have this issue if I configure my Router security to WPA. With open I can connect immediately

crakeron said:
none of these solutions worked right?
I have wifi problems too. Wifi in CM7 is crap
Click to expand...
Click to collapse
can't really say that. It's great in 111116-nightly so I just wanna figure out what I have to change to get the speed back!
Motorola Defy CM72120121, german Froyo base

I have this problem, too.
Nobody else?
Would be great if some devs could please look this up.

SOLUTION
Hello all,
first off: delete wpa_supplicant and everything is fine!
I gave up and did a factory reset/wipe data. After that it worked w/o problems.
> Now I will restore all my apps and check if it's still working afterwards. > still working
> restore wifi access points > NOT WORKING ANYMORE!
> with shame I delete wpa_supplicant > WORKS AGAIN!
I'm so ashamed. :/ Should have done that like months ago.
I go back to my backup and try it there. > deleting the wpa_supplicant worked!!!!

My Wifi has a problem with WRT54G Wireless Router, with Froyo Stock ROM and CM7.1 RC1.5-jordan.
WIFI connect, signal is good but connection is very slow.
On notebooks, the connection is faster with this same router.
In another Wireless routers connection is normal from Defy. The problem is only between Defy x Linksys WRT54G.
I have set Defy and Router to work only in G mode, but the problem persist.
With the same configurations the problem don´t occour with another routers from D-link, Cisco or other.
Anyone know how can I solve it?
Tnks.

WiFi Connection Issues

Has anyone else noticed this problem:
After upgrading to an ICS leak (currently stock rooted FE22, although noticed so far on all leaks), my WiFi in the presence of a weak signal will stay connected, but not have an active data connection. For example, at work I get 1 bar of WiFi signal shown, and when I first connect I can use data over the WiFi network (market, browser, email, etc.) but after I let my phone sit at my desk for a while and go to use it again, it still shows it's connected to the WiFi network with 1 bar, but there is no data connection (can't communicate to market, browser, etc.). If I disconnect and reconnect to the WiFi network it will once again get active data for a period of time. I have the WiFi setting to always stay connected. If I set it to 'Only When Plugged In' it works fine because it reconnects when I wake it up, but I have a weak cellular signal at work, so this kills the battery faster during background data. It worked fine on the current OTA release of GB with the 'Always On' setting. Any insight/confirmation about this issue would be appreciated. Thanks!

Are you running a customized wpa_supplicant.conf? If so can you please send a copy by PM or copy/paste here after removing any info that you need to (SSID, pw, etc)? Might help understand what's going on - my PEAP/MSCHAPV2 does a "nod-off" but then comes right back up at times. Thought maybe it's a power saving feature as it only seems to happen at times of low demand for data.

I haven't modified anything at all and am running the unmodified FE22 leak, except for root. Here's what my wpa_supplicant.conf file says in its entirety:
from /system/etc/wifi:
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=1
fast_reauth=1
p2p_listen_reg_class=81
p2p_listen_channel=1
p2p_oper_reg_class=81
p2p_oper_channel=11
from /data/misc/wifi:
ctrl_interface=wlan0
driver_param=use_p2p_group_interface=1
update_config=1
device_type=0-00000000-0
p2p_listen_reg_class=81
p2p_listen_channel=1
p2p_oper_reg_class=81
p2p_oper_channel=11
network={
ssid="HOME AP"
psk=<removed>
key_mgmt=WPA-PSK
priority=1
}
network={
ssid="WORK AP"
psk=<removed>
key_mgmt=WPA-PSK
priority=2
}
network={
ssid="attwifi"
key_mgmt=NONE
priority=3
}

CHeil402 said:
I haven't modified anything at all and am running the unmodified FE22 leak, except for root. Here's what my wpa_supplicant.conf file says in its entirety:
<snip>
Click to expand...
Click to collapse
Pretty straight forward... no surprises there. Do you keep the sleep setting normally as "Always On"? As I mentioned before I've seen mine nod off (go down to zero bars) and then reconnect - usually when the phone is idling.
*Edit* Noticed 3 lines missing from the default:
Code:
eapol_version=1
ap_scan=1
fast_reauth=1
If you're familiar with editing wpa_supplicant.conf you could try to add these lines in and see if it helps. Just don't forget to reset the permissions and ownership or it may give an error when starting the wi-fi.

garwynn said:
Pretty straight forward... no surprises there. Do you keep the sleep setting normally as "Always On"? As I mentioned before I've seen mine nod off (go down to zero bars) and then reconnect - usually when the phone is idling.
*Edit* Noticed 3 lines missing from the default:
Code:
eapol_version=1
ap_scan=1
fast_reauth=1
If you're familiar with editing wpa_supplicant.conf you could try to add these lines in and see if it helps. Just don't forget to reset the permissions and ownership or it may give an error when starting the wi-fi.
Click to expand...
Click to collapse
I tried adding these lines in /data/misc/wifiwpa_supplicant.conf, but then wifi wouldn't turn on. So I reverted back to the old one and now it still won't turn on! I used ES File Explorer to edit the text of the file, and set the permissions to rw-rw---- as it was before then restarted my phone. Any ideas?

CHeil402 said:
I tried adding these lines in /data/misc/wifiwpa_supplicant.conf, but then wifi wouldn't turn on. So I reverted back to the old one and now it still won't turn on! I used ES File Explorer to edit the text of the file, and set the permissions to rw-rw---- as it was before then restarted my phone. Any ideas?
Click to expand...
Click to collapse
Well, in a worst case, deleting it will force it to be copied and restore the service... but let's try something else first.
1) Turn off wi-fi (always needs to be off before modifying that file.)
2) inside adb shell please enter the following commands:
Code:
su
cd /data/misc/wifi
chmod 660 wpa_supplicant.conf
chown system.wifi wpa_supplicant.conf
3) Exit and turn back on wi-fi.
If it was the permissions this will fix it.

garwynn said:
Well, in a worst case, deleting it will force it to be copied and restore the service... but let's try something else first.
1) Turn off wi-fi (always needs to be off before modifying that file.)
2) inside adb shell please enter the following commands:
Code:
su
cd /data/misc/wifi
chmod 660 wpa_supplicant.conf
chown system.wifi wpa_supplicant.conf
3) Exit and turn back on wi-fi.
If it was the permissions this will fix it.[/QUOTE]
THANK YOU! Apparently, I forgot to set the ownership. I only changed the permissions. I also re-added the lines you mentioned. I'll have to see if that works... I'll let you know.
Click to expand...
Click to collapse

**UPDATE- Still no improvement. It will connect initially, and have active data. But then it will still show as connected with 1/3 WiFi bars, but no active data unless I disconnect and reconnect to the AP and then the same problem repeats itself.

OK, I'm having the same but in all fairness could be because I did 2 nodata updates. Will suggest if you can to backup your stuff and flash the full rooted version of FE22 and see if that fixes it - or hold tight and wait for OTA to drop if it's just nagging you and you don't want to do it now.

[Q] Another 4.3 Wifi Tether TrevE problem thread

I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.

Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.

Aronmorg said:
I typed this in a previous thread, but I don't know how often previous threads are read. Sorry for the repeat if that is a faux paus in this forum.
Similarily to a previous poster, when I updated to 4.3, my wifi tether trevE no longer works. Whatever is keeping it from working is preventing my wife's s4, both are rooted (obviously), they both have the same message. When I try to start tethering the reply message is " tether started with problems, please Check logs"
when I go to the logs, it tells me the file doesn't exist. I think this is my main problem.
When looking up the proper settings, enable mss Clamping was # 10 on the list, but there wasn't a setting for mss clamping.
I have attached a picture that has four pics with each individual problem that appears. My experience amounts to being able to root and that is pretty much it. I don't know what else would cause these problems in both a note 2 and S4.
Does anyone know what the problem is and what I can do to fix trevE? Are there new settings or do I have to download an older version...? Thanks in advanced.
Click to expand...
Click to collapse
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.

atombombzero said:
load up connectbot and ssh to your localhost.
$ su -
permit root access through whatever app you use
# cd /data/data/com.googlecode.android.wifi.tether/var
# chmod 766 tether.log
That is as far as I have gotten. That lets you view the errors in the app (which are many).
Loading WiFi driver (cmd) - failed
Stopping AP - failed
Stopping WiFi interface - failed
Reloading firmware - failed
Starting AP interface - failed
Configuring AP - failed
Starting AP - failed
Configuring Ip-address - failed
Enabling Routing Fix - failed
Enabling NAT rules - failed
Enabling MSS clamping - failed
Enabling IP forwarding - done
Tethering now running - done
I will play more with it tomorrow to try to figure out why things are failing. I am leaning toward permissions issues as it seems that permissions were at the center of the log problem.
Click to expand...
Click to collapse
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.

bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
I am running a rooted stock with a stock recovery. In installing the hotspot hack zip, does this require TWRP or CWM recovery??

Aronmorg said:
Thanks for the response, truthfully I've never done connectbot and ssh. But it'd be fun to learn, I'll try to learn over the holidays, but I wouldn't understand what's wrong with the app. I'm not a developer. Is there a webinar that explains the basics of understanding apps so that I could learn?
I'm wondering if the developer knows of these issues.
Click to expand...
Click to collapse
I am just a UNIX admin so I know enough to be dangerous. I am no dev.
bhint15 said:
Are you running a fully stock rooted rom? Are you running one built by Platt or Lorjay?
If stock I would go to recovery and flash one of the hotspot hack zips around the forums.
If you are on Platt or Lorjay then it is built-in and you can just use the native hotspot.
Click to expand...
Click to collapse
Also, I can't find the hack of which you speak. I scoured the forums today and found nothing.

I'm running synergy 4.3 rom and native hotspot works no problem. .

I just got my wife's s4 to use the native hotspot by downloading the service.odex and .jar with stock rom. I don't know if something like that is available with the note 2. I see that someone using the synergy 4.3 rom got native hotspot to work, but is that possible with stock rom.

Wi-Fi won't connect -Wi-Fi Connection Failure

I'm having a huge issue. My Wi-Fi won't work on my 2013 Nexus. I select it. It sees it with a full signal and I put in the password, It just says saved. I tried with a connection without a password, it says the same thing. I tried flashing back to factory multiple times but it does nothing. It was working and just all of a sudden went out on me. Is there a way to flash a driver or something?

lowridincrew said:
I'm having a huge issue. My Wi-Fi won't work on my 2013 Nexus. I select it. It sees it with a full signal and I put in the password, It just says saved. I tried with a connection without a password, it says the same thing. I tried flashing back to factory multiple times but it does nothing. It was working and just all of a sudden went out on me. Is there a way to flash a driver or something?
Click to expand...
Click to collapse
Firstly, just reboot the WiFi access point and try to connect to it again.
Did you change firmware or any settings on the WiFi access point? Do other devices connect to it properly?
Can your Nexus connect to other WiFi access points? Try it with your mobile's WiFi hot spot.
Finally, we need some logs:
turn off N7 wifi
start logcat (I prefer 'time' format: adb logcat -v time > log.txt )
turn on N7 wifi
try to connect
stop logcat
compress and post the log here