Hi folks,
Since last thursday I've got a problem with my WiFi on my wildfire. Every time I turn on the WiFi (via not. bar or settings) the little box is ticked but it does not scan or anything. A couple of seconds later I get the message that the WiFi process in the settings app is not responding together with the option to kill the process. Is my WiFi broken now? Or is there a fix?
Thanks in advance
P.S. I'm using CM7 7.1.0
Try flashing the latest nightly or the 7.1.0.1 update.
http://forum.xda-developers.com/showthread.php?t=1143125
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
Try flashing the latest nightly or the 7.1.0.1 update.
http://forum.xda-developers.com/showthread.php?t=1143125
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
It doesn't work. When I boot after applying the update after the bootanimation there's just a black screen. It hangs. I pulled the bat and tried it again but the same...
Usually this can be solved by wiping the dalvik cache, have you tried that?
henkdv said:
Usually this can be solved by wiping the dalvik cache, have you tried that?
Click to expand...
Click to collapse
I managed to update CM7 to 7.1.0.1, but Wi-Fi is still not working! It just hangs after switch-on. And the weirdest thing of all is that it just happened, I dind't change anything or install any new apps...
Try reflashing the radio?
3xeno said:
Try reflashing the radio?
Click to expand...
Click to collapse
Reflashed the radio, still no progress It just wont find any wifi networks and after leaving the settings app the WiFi is turned off automatically (or the app hangs and the same happens) Any other suggestions?
By the way, WiFi-Tethering does work. Still confused about this weird problem :S
Try this in a root shell (enter "su" at the prompt) with wifi enabled:
ip link set up eth0
Though the name might be different on your rom, it's commonly named "wlan0" (eth0 is usually a physical ethernet device). You can find out by running
ip link show
With wifi disabled and enabled, see what new device comes up or disappears. It doesn't hurt to test a name, as long as it isn't "lo" (the loopback device).
After setting the link state, re-scan for APs.
henkdv said:
Try this in a root shell (enter "su" at the prompt) with wifi enabled:
ip link set up eth0
Though the name might be different on your rom, it's commonly named "wlan0" (eth0 is usually a physical ethernet device). You can find out by running
ip link show
With wifi disabled and enabled, see what new device comes up or disappears. It doesn't hurt to test a name, as long as it isn't "lo" (the loopback device).
After setting the link state, re-scan for APs.
Click to expand...
Click to collapse
Could you explain these steps? I'm not so familiar with terminal inputs and especially IP adresses. Whats more strange is that my Wi-Fi disconnects automatically when leaving the Wi-Fi menu and that it doesn't show my saved accesspoints (once connected but not now). Isn't this a software problem?
tobitronics said:
Could you explain these steps?
Click to expand...
Click to collapse
Sure, here's the html formatted manual page. A relevant excerpt:
ip link set - change device attributes
dev DEVICE
DEVICE specifies network device to operate on. When configuring
SR-IOV Virtual Fuction (VF) devices, this keyword should specify
the associated Physical Function (PF) device.
up and down
change the state of the device to UP or DOWN.
Click to expand...
Click to collapse
When the device is down, it won't scan. Some ROMs have a different tool installed as /system/bin/ip though, just typing "ip" will tell you.
tobitronics said:
Whats more strange is that my Wi-Fi disconnects automatically when leaving the Wi-Fi menu and that it doesn't show my saved accesspoints (once connected but not now).
Click to expand...
Click to collapse
The saved networks aren't shown when wifi is turned off. It likely fails to enable the device and does this before attempting to read the saved networks, as this should never happen it might be related to the radio firmware on your phone. See this thread for the list of radio firmware versions. As for disconnecting when you leave the WifiSettings activity, wait a bit longer to see if it stays connected. There's definitely no intentional disconnect in the onPause handler.
tobitronics said:
Isn't this a software problem?
Click to expand...
Click to collapse
I see no reason to believe the contrary.
henkdv said:
Sure, here's the html formatted manual page. A relevant excerpt:When the device is down, it won't scan. Some ROMs have a different tool installed as /system/bin/ip though, just typing "ip" will tell you.The saved networks aren't shown when wifi is turned off. It likely fails to enable the device and does this before attempting to read the saved networks, as this should never happen it might be related to the radio firmware on your phone. See this thread for the list of radio firmware versions. As for disconnecting when you leave the WifiSettings activity, wait a bit longer to see if it stays connected. There's definitely no intentional disconnect in the onPause handler. I see no reason to believe the contrary.
Click to expand...
Click to collapse
I've tried your steps. When setting the IP link to up after switching on WiFi and then enter 'show' i get a whole page of numbers and complicated text, but in each line the State is specified as 'DOWN' or 'UNKNOWN'. It also says something about a loop? When I leave the terminal then to check if WiFi is still on, I find it turned off. When I turn it back on and then let the terminal show, sometimes I get 'DORMANT' and sometimes I get 'DOWN'. I also tried your suggestion about leaving the client on, it stays on for about a minute before it automatically disconnects or gives me the message that the system app is not responding. My radio is already up to date (I even reflashed it twice). And what was that link 'WiFiSettings activity'. I came to a website with lots of code and got immediately confused . I hope this problem can be solved....
tobitronics said:
When setting the IP link to up after switching on WiFi and then enter 'show' i get a whole page of numbers and complicated text, but in each line the State is specified as 'DOWN' or 'UNKNOWN'.
Click to expand...
Click to collapse
This is the RFC2863 state of the interface which is seldom relevant, the actual link state is between < and >.
tobitronics said:
It also says something about a loop?
Click to expand...
Click to collapse
That would be the loopback device. It is always present and its parameters are the same across nearly all Linux kernels, one might be funny and try to change the mtu, queueing discipline or address but it's pointless to do so.
tobitronics said:
When I leave the terminal then to check if WiFi is still on, I find it turned off. When I turn it back on and then let the terminal show, sometimes I get 'DORMANT' and sometimes I get 'DOWN'.
Click to expand...
Click to collapse
According to the documentation, DORMANT means
Interface is L1 up, but waiting for an external event, f.e. for a protocol to establish. (802.1X)
Click to expand...
Click to collapse
This could indicate a problem with wpa_supplicant rather then the radio firmware. Try to connect to an open AP such as the ones at the local Bakker Bart, NS station, McDonalds or T-Mobile shop.
tobitronics said:
I also tried your suggestion about leaving the client on, it stays on for about a minute before it automatically disconnects or gives me the message that the system app is not responding. My radio is already up to date (I even reflashed it twice). And what was that link 'WiFiSettings activity'. I came to a website with lots of code and got immediately confused .
Click to expand...
Click to collapse
It is the actual source code to "Wi-Fi settings" where you normally see the list of networks.
Thanks for your explanation. So what should I do/try now? I was thinking about reinstalling the settings.apk and settingsprovider.apk ....
Sent from my HTC Wildfire using XDA App
Like I said, try an open 802.11a/b/g access point.
henkdv said:
Like I said, try an open 802.11a/b/g access point.
Click to expand...
Click to collapse
I tried that at the McDonald's and it didn't want to search for available networks, so I couldn't connect
Go to settings > Wireless & Networks. Disable this option
Mobile network
Use phone for data connection when Wi-Fi is unavailable
It should change to
Mobile network
Connect to the Internet
Try going to /data/misc/wifi and rename the wpa_supplicant.conf to wpa_supplicant.conf.bak and try again, the system will recreate the file.
Sent from my HTC Wildfire using XDA App
Takudenatsu said:
Try going to /data/misc/wifi and rename the wpa_supplicant.conf to wpa_supplicant.conf.bak and try again, the system will recreate the file.
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
IT WORKSSS!!!! Thank you all for your help. That such a small little text file could cause such a large annoying problem. I hope it won't happen again...
Sent from my HTC Wildfire using XDA App
could you write how?
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.
Hey, I've got CM10 on my GS3. When I go under Settings, the Wifi toggle is set to Off and grayed out so I can't toggle it. When I go to Wifi, it just says "Turning on Wifi" indefinitely. I also have issues with wifi tethering sometimes.
Any solutions to this? I haven't been able to find any posts on it. I'd prefer not to reset to another ROM, but if there's no other ways to fix this, oh well.
Thanks!
Flash to a TW rom and see if it works.
If it doesnt work, try the following:
Diablo67 said:
So as to fix this problem,some people suggest to do a Factory reset.But, it is completely unnecessary.Instead you can try the following methods, which where tested by me successfully.
1. Dial *#*#526#*#* to reload the wifi driver.If it doesn’t work, restart your phone and dial it once gain.It will work for sure.
2.There is an app “Wifi-Fixer” from android market,which claims to be fix this problem.But seriously,it hadn’t worked for my mobile phone(Samsung Galaxy Ace).But,
if you are interested, can download and try it here.
For HTC users, I have a pretty good trick which works very well.
When you have obtaining IP address problem,
1.Turn off wifi.
2.Open “Allshare”, then you will be asked to connect to a wifi network.
3.Then select the wifi network that you need to connect from the list opened.
Magically, you will be connected without any extra effort.This works 100% sure without fail.
If that doesnt work try this:
1.Dial *#*#526#*#*.Then a message will be shown “Driver loading Successful”.
2.Now Start the WiFi, it should work.
If the message “Driver Loading Unsuccessful” is shown, follow these steps:
1. Dial *#*#526#*#* again and click options button on your phone.
2. Select Rx test.
3. Select Channel >9 .
4. Click Start and exit.
5 . After some time, turn on the wifi.It should work.
Click to expand...
Click to collapse
Sent from my PG06100
My phone won't even let me dial that, the code disappears the second I hit star the last time, not sure if it's supposed to do that. I'm gonna just try updating CM and see if that fixes it.
First off I want to say that the rom (SensuAOSP 2.55) is the bomb... But I am having a few problems and not sure where to turn to. My first problem is the tethering, I can't get it to work. I can turn it on, and my IPAD finds it, the password works and it says it is connected. But no data is passed. It shows it has the IP address etc but nothing.
The phone vibrated at one time, but now it is not. I have gone through all the settings (but 1 I guess since I can't find it) with no luck.
Lastly, I have clicked on the A2SDgui icon and it comes up and states It could not start for one of these reasons 1. Your device is not rooted 2. A2SDGUI scripts could not be found 3.No ext partition found. I know I formated the partition, It says that superuser has permission, just not sure what else to check...
Thank you to any of you for your assistance
Sargmaster said:
. My first problem is the tethering, I can't get it to work. I can turn it on, and my IPAD finds it, the password works and it says it is connected. But no data is passed. It shows it has the IP address etc but nothing.
Click to expand...
Click to collapse
Lets talk about the Tethering first... I did the upgrade on this ROM and still did not work (Really didn't think it would). Was wondering if anyone would think I should just update the radio?
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