Hi, I have this problem while switched between ROMs. But the problem hasn't been solved even if i switch back to the older ROM. The last active process of my WiFi was when i switched back to NEAT ROM. That too worked for a few seconds on the start of boots (even reboots). Then no sign of my WiFi turning on.
I had tried many fixes such as changing the kernel as the drivers are in kernel, using some WiFi fixing apps. But nothing helped.
It is clear from the logcat that i got during turning on my WiFi, that it says WiFi drivers not loaded.
Please suggest any ideas!
1. How to properly load WiFi drivers?
2. Where is the location of the WiFi drivers?
3. How are they installed?
Kernels devs could help me out possibly..
Error log:
" --------- beginning of /dev/log/system
--------- beginning of /dev/log/main
E/WifiStateMachine( 2235): Failed to load driver"
Related
WIFI was working fine. but randomly it has stopped working. Saying "Error" where it should be "connected" is there any settings i can mess with? or default reset?
Are you on a custom rom / kernel? I had this error shortly after flashing one of the senseless roms a few days ago. As soon as i turned on WIFI it said ERROR. Think i was rectified in a later update since then....
Wifi error
Same problem I'm on custom rom and wifi brings up error.... I didn't change kernel
lilken254 said:
Same problem I'm on custom rom and wifi brings up error.... I didn't change kernel
Click to expand...
Click to collapse
Logcat usually shows a bit more detail than the WiFi screen in Settings. If you're able to grab the logcat details around when you turn on WiFi, it might show more helpful output which can make troubleshooting easier.
The majority of WiFi error issues posted on this forum relate to the mismatch between kernel and modules. Wouldn't hurt to reload the kernel and its associated module to eliminate that as a possibility.
Hope that helps!
wifi
its the kernal you will have to change it and your wifi will work again
Hello everyone, I am using JP_MIUI from here.
First I tried to run DoomKernel for MIUI but it didn't work. Then I tried to switch back to the given kernel but no more wifi.
More than that, I have reflashed the rom again with full wipe but wifi doesn't work
The logcat gives the following error :
E/WifiService( 1234): Failed to load Wi-Fi driver.
If someone can help me to run this rom using doomkernel or just tell me how to solve this driver issue.
Thanks
Hi I have problem with wifi connection on this phone the wifi worked on stock rom and then on cyanogen for a while and now it stopped completely (its just trying to connect but It won't get IP. I have tried to switch off security on my router and use different wifi connections nothing has worked
I'm trying to update my dad's phone and I'm having the same issue. It fails to connect after saying "Authenticating". I've double checked everything, still no dice.
I'm on CM7.1 too and my Wi-Fi is not working, but the story is slightly different, check my thread for more info
http://forum.xda-developers.com/showthread.php?t=1390680
It seems linked to the fact that you may use multiple AP / have multiple AP profiles.
For instance, I have 2 wifi AP at home (private / public), and if I forget the public one (using it rarely), I don't have the stucked following message : "Authenticating" / "Obtaining IP address" / "Connecting"
Several users reported this, don't know if it will work for you.
Fr33L4nc3r said:
It seems linked to the fact that you may use multiple AP / have multiple AP profiles.
For instance, I have 2 wifi AP at home (private / public), and if I forget the public one (using it rarely), I don't have the stucked following message : "Authenticating" / "Obtaining IP address" / "Connecting"
Several users reported this, don't know if it will work for you.
Click to expand...
Click to collapse
My story is a little different, i can't even turn on my Wifi, everytime and i attempt to turn it on, the message "Sorry! Application Settings (in process com.android.setings) is not responding. Force close/wait" shows up, and when i choose either one of them, nothing happen, except force close, closed the entire page and back to homescreen =/ tried everything i can think of, re-flash rom, re download rom and re-flash it again, flash stock rom, flash modem, reset router non-worked
rayz93 said:
My story is a little different, i can't even turn on my Wifi, everytime and i attempt to turn it on, the message "Sorry! Application Settings (in process com.android.setings) is not responding. Force close/wait" shows up, and when i choose either one of them, nothing happen, except force close, closed the entire page and back to homescreen =/ tried everything i can think of, re-flash rom, re download rom and re-flash it again, flash stock rom, flash modem, reset router non-worked
Click to expand...
Click to collapse
Yeah, I was answering to the OP because I had a similar issue.
Yours seems more complex, I'm afraid I can't help much.
Hello there and please excuse me for my bad english! As the title says, I can't connect to wifi network. Well, I can but it just work sometimes and works weird. Here's the scenario:
MIUI 3.6.7 rom on a Motorola Atrix 4G.
Android 4.1.2 JZO54K
Baseband N_01.77_38P
Kernel 2.6.32.60-MB860-CM10-ged7b511
On last sunday I tried to connect to a open wifi network, all week I was connecting to my home network. The status of wifi kept on "Turning on wifi..." for a while, but nothing happened. I restarted the phone and happened the same thing. At home, the connection worked but suddenly it closed for no reason. I tried to connect it again but kept again on the "Turning on wifi..." thing and suddenly the phone restarted! Not enough, it got stucked on the very first screen (the one with the "unlocked" text and Motorola logo), so I had to do a battery pull.
I've wiped Dalvik cache, cache partition, did some full wipes, installed again the rom (I was on 3.5.31 for then, updated yesterday to 3.6.7 and still the same), changed the Baseband, installed another kernel and I'm in the same situation. It's driving me crazy.
Got a logcat with Catlog, and found some (maybe interesting) lines (you can find the whole file in ge.tt/36KSn9j/v/0 -- sorry for be unable to post a link or uploading a file here):
06-11 15:21:54.508 W/CommandListener(1415): Failed to retrieve HW addr for eth0 (No such device)
06-11 15:21:54.508 D/CommandListener(1415): Setting iface cfg
06-11 15:21:54.508 E/WifiHW (1714): Unable to open connection to supplicant on "eth0": No such file or directory
06-11 15:21:54.508 I/wpa_supplicant(11001): rfkill: Cannot open RFKILL control device
06-11 15:21:54.508 E/wpa_supplicant(11001): Could not read interface eth0 flags: No such device
06-11 15:21:54.508 E/wpa_supplicant(11001): WEXT: Could not set interface 'eth0' UP
06-11 15:21:54.508 E/wpa_supplicant(11001): eth0: Failed to initialize driver interface
06-11 15:21:55.508 E/WifiHW (1714): Supplicant not running, cannot connect
06-11 15:21:59.508 E/WifiStateMachine(1714): Failed to setup control channel, restart supplicant
Googling about this got me to this thread (drakaz.com/forum/viewtopic.php?id=120... again sorry for the links thing) and got me thinking why the net interface is listened as 'eth0' and not 'wifi0' or something. I'm pretty noob to Android but I'm sort of an average GNU/Linux user, so I checked for what is going on in the dhcpcd.conf file and founded there the hostname was writed as 'wifi0' so I changed to 'eth0'... but this thing is still the same. Can you give me a clue about what the hell is going on? Thank you so much!
Make a nandroid backup and try a different ROM (preferrably a GB/CM7 based one).
ravilov said:
try a different ROM (preferrably a GB/CM7 based one).
Click to expand...
Click to collapse
Thank you so much for your answer! I tried CM7 (both stable and nightly, I heard the last one was a bit more stable than the first one) doing full wipe, of course. But when restarting, on both cases they only reached the very first screen (the one with the Motorola logo) and after like 5 seconds the phone rebooted automatically.
The thing is I really don't want to change MIUI. I've been using it since august, 2012 and I'm in love with it. This is the first time I got an issue so serious. Is there anything else I can do? Thank you so much!
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
ravilov said:
No idea really. I'd tell you to do a full wipe before flashing but you've done that already. The only thing I can think of is flashing MROM (since its kernel has early USB enumeration) and then trying to pull out some more logcats very early on. This is quite a weird error and working out a solution will definitely involve a lot of creative thinking.
Click to expand...
Click to collapse
After the millionth full wipe I just got to install CM7 nightly and a clean reboot. But the wifi thing is still there... Well, a fc popup dialog appears after like 10 seconds: "Sorry! Application Settings (in process com.android.settings) is not responding.". I'm going to install MROM and catch a logcat, will be back then with a logcat. Thank you so much!
So I finally could get MROM working (I guess the thing about all GB roms rebooting when are just installed is about CWM). There's still the same thing I got with CM7. I have a logcat under MROM, and another I catched before I flased MROM (using MIUI v5): As I couldn't got MROM working just after wiping all when I was with CM7, I tried flashing MIUI. It flashed normally and at startup wifi was working, but after a while the connection closed suddenly. I got a logcat from that.
So the logcat with MIUI v5 (2013-06-14-02-26-28.txt) is here: ge.tt/6AQdiSj/v/0
And the logcat with MROM (2013-06-14-15-32-55.txt) is in ge.tt/7slxiSj/v/0
Hope this can help, I will keep pending so if you want to know something just let me know. Thank you so much for your help!
Seems that this is a problem about planned obsolescence. I'm such a noob, I hadn't seen this thread before (http://forum.xda-developers.com/showthread.php?t=1656760) where they explain many people had this issue. I can't post to that thread, but seems that they never got their wifi working again as I do sometimes. This is the weirdest s**t I've ever had with an electronic device.
from time to time my wifi stops working. i try to enable and disable it, but it does not work. i must reboot the phone to get wifi working again.
just now it happened again. so i open an adb shell, switch to root and kill the wpa_supplicant. and now wifi is working again without reboot.
@Lloir & @Thömy attached is a logcat. at 10:30:41.072 i killed the wpa_supplicant
white- said:
from time to time my wifi stops working. i try to enable and disable it, but it does not work. i must reboot the phone to get wifi working again.
just now it happened again. so i open an adb shell, switch to root and kill the wpa_supplicant. and now wifi is working again without reboot.
@Lloir & @Thömy attached is a logcat. at 10:30:41.072 i killed the wpa_supplicant
Click to expand...
Click to collapse
Not sure what the problem is. Can't find anything obvious.
Is that timeline correct?
Code:
09:38:36: disconnection from WiFi
10:18:38 - 10:29:04: you try to enable/disable WiFi a couple of times
10:39:18: connected to WiFi
10:30:41: you kill the wpa_supplicant
10:36:12: wpa_supplicant complains about being forcefully killed
wpa_supplicant restarts 5 times
10:39:17: you're connected to WiFi again
The next time that happens try to get the output of "dumpsys wifi" and "dumpsys connectivity" before you kill something.
Probably needs either a clean install or a fresh kernel flash
Sent from my Nexus 5 using Tapatalk
Thömy said:
Not sure what the problem is. Can't find anything obvious.
Is that timeline correct?
Code:
09:38:36: disconnection from WiFi
10:18:38 - 10:29:04: you try to enable/disable WiFi a couple of times
10:39:18: connected to WiFi
10:30:41: you kill the wpa_supplicant
10:36:12: wpa_supplicant complains about being forcefully killed
wpa_supplicant restarts 5 times
10:39:17: you're connected to WiFi again
The next time that happens try to get the output of "dumpsys wifi" and "dumpsys connectivity" before you kill something.
Click to expand...
Click to collapse
the "10:39:18: connected to WiFi" is imo wrong. because i killed wpa_supplicant because i was not connected to wifi.
i will do the dumpsys thing next time and post the result
Probably needs either a clean install or a fresh kernel flash
Click to expand...
Click to collapse
why? this ist a dirty flash of cm-11-20140304 with its kernel. what is wrong with it?
the problem has occurred again, but a little bit different.
1) connected to b.nuhq.nunet (at work)
2) 12:32:18.973 make a smoking break -> wifi got disconnected because of poor signal
3) back at work place: can not switch on the phone. only the hardware buttons begin to light up, but the displays stays off.
4) attached the phone to usb and adb
5) 12:43:44.938 get a logcat (logcat.txt) and dmesg (dmesg.txt)
try to get the dumpsys wifi on a adb shell as ROOT. this command hangs forever without any output. but after 30 seconds the phone vibrates and the adb logcat on the other terminal spits out many log lines (logcat-crazy.txt). after that, i can switch the display on again. but the phone was not rebooted!
after that i try to get the dumpsys as user. and this works fine (dumpsys-wifi.txt, dumpsys-connectivity.txt)
wifi is still at VERIFYING_POOR_LINK but this is wrong. the access point is 3 meter away from me
dmesg2.txt is after the screen works again. but after 10 minutes the screen is off again and i can not switch the phone on. im still connected via adb
logcat-time.txt is a is a complete log with timestamps.
traces.txt is from /data/anr/traces.txt
13:42 killed wpa_supplicant with "kill 939"
13:44 manually connect b.nuhq.nunet (failed)
13:45 switch wifi off
13:45 switch wifi on (works fine)
after that i can use the screen again.
the problem that the screen can not switched on exists for since the begin. but in the most cases it happens in connection with a poor wifi signal.