[SOLVED]Wifi module dead? (Nope.) - G2 and Desire Z Q&A, Help & Troubleshooting

This morning my wife handed me her phone and said "fixit". It was frozen, no touchscreen, no power button, nothing. I pulled the battery and upon restarting the wifi wouldn't connect. We both have the same phone (Tmo G2), but the only differnce between mine and hers is mine has the DZ HBOOT (I flashed Sense 3.0 ROM a while back) which is CM7.1 with pershoot's kernel and V6 Supercharger U9R4. Mine has been connected to wifi the whole time so I don't think it's the router. I tried to "Forget" the network and rescan but it doesn't show up now. I tried to manally add the SSID and password and it's still a no go. I've fixed permissions and wiped caches. My next step is to check logcat to see if I can find anything. My question is could the wifi module be dead but the phone still operate? Ther are no force closes and the mobile data is fine.
Sent from my HTC Vision using xda premium

heybobitsme said:
This morning my wife handed me her phone and said "fixit". It was frozen, no touchscreen, no power button, nothing. I pulled the battery and upon restarting the wifi wouldn't connect. We both have the same phone (Tmo G2), but the only differnce between mine and hers is mine has the DZ HBOOT (I flashed Sense 3.0 ROM a while back) which is CM7.1 with pershoot's kernel and V6 Supercharger U9R4. Mine has been connected to wifi the whole time so I don't think it's the router. I tried to "Forget" the network and rescan but it doesn't show up now. I tried to manally add the SSID and password and it's still a no go. I've fixed permissions and wiped caches. My next step is to check logcat to see if I can find anything. My question is could the wifi module be dead but the phone still operate? Ther are no force closes and the mobile data is fine.
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
Toasting a module while leaving the rest of the board fine would be a bit hard to do; check /proc/last_kmesg (it might still show what caused the device to freeze up like that.
You could also try watching the logs while toggling the Wi-Fi on/off to see what's being said.
Sent from my HTC Vision using XDA App

This is what I got from the logcat so far
Code:
D/alogcat ( 4359): stopped
D/alogcat ( 4359): starting ...
I/craigsnotifica( 4395): NetworkChangeReceiver -> arrived android.net.wifi.WIFI_STATE_CHANGED
D/dalvikvm( 1477): GC_CONCURRENT freed 1731K, 36% free 8231K/12743K, external 2124K/2616K, paused 4ms+14ms
D/Tethering( 1477): eth0 is not a tetherable iface, ignoring
I/craigsnotifica( 4395): NetworkChangeReceiver -> arrived android.net.wifi.WIFI_STATE_CHANGED
V/WifiStateTracker( 1477): Connection to supplicant established, state=DISCONNECTED
I/wpa_supplicant( 4758): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 4758): Trying to associate with SSID 'linksys'
V/WifiMonitor( 1477): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
V/WifiMonitor( 1477): Event [Trying to associate with SSID 'linksys']
V/WifiStateTracker( 1477): Changing supplicant state: DISCONNECTED ==> SCANNING
I/wpa_supplicant( 4758): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
V/WifiMonitor( 1477): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 1477): Changing supplicant state: SCANNING ==> ASSOCIATING
Note that "linksys" is not the router I'm trying to connect to.

heybobitsme said:
This is what I got from the logcat so far
Code:
D/alogcat ( 4359): stopped
D/alogcat ( 4359): starting ...
I/craigsnotifica( 4395): NetworkChangeReceiver -> arrived android.net.wifi.WIFI_STATE_CHANGED
D/dalvikvm( 1477): GC_CONCURRENT freed 1731K, 36% free 8231K/12743K, external 2124K/2616K, paused 4ms+14ms
D/Tethering( 1477): eth0 is not a tetherable iface, ignoring
I/craigsnotifica( 4395): NetworkChangeReceiver -> arrived android.net.wifi.WIFI_STATE_CHANGED
V/WifiStateTracker( 1477): Connection to supplicant established, state=DISCONNECTED
I/wpa_supplicant( 4758): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 4758): Trying to associate with SSID 'linksys'
V/WifiMonitor( 1477): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
V/WifiMonitor( 1477): Event [Trying to associate with SSID 'linksys']
V/WifiStateTracker( 1477): Changing supplicant state: DISCONNECTED ==> SCANNING
I/wpa_supplicant( 4758): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00
V/WifiMonitor( 1477): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 1477): Changing supplicant state: SCANNING ==> ASSOCIATING
Note that "linksys" is not the router I'm trying to connect to.
Click to expand...
Click to collapse
Well, the module isn't dead. Has there been any changes since when it last worked (updates to apps, apps installed, etc.).
Sent from my HTC Vision using XDA App

Ok, I found the problem. The linksys router shown in the previous post was taking precedence and for some reason the phone was only trying to connect to it. As soon as I removed it my router showed up. Is there a limit as to how many remembered networks you can have? My wife has 5 including our home network.

No limit exists that I am aware of, except memory. I have at least 30+ remembered wifi networks.

That's what I thought. It's weird that it was trying connect to a network and not allowing any other to work.
Sent from my HTC Vision using xda premium

Related

New radio and wimax and now....

After updating the radios my wifi is half broken. I can only connect to open networks. Anything with a password will not connect.
Anybody got some advice
Sent from my PC36100 using XDA App
nobody
10 chars
Dude, relax... These guys have jobs and lives. They can't always pop up an answer within an hour. Give it a little while, someone will come along with some advice. In the mean time, please give them a little more information to work with in helping you. What ROM are you running? Which Radio version did you flash? Are you running a custom kernel? If so, which one?
The more detailed your information is, the easier it will be for someone to help.
Here's a logcat of what happens when I turn on my wifi when on a secure wireless spot
I flashest the lastest radios and wimax files from fresh for the his senese 2.2 rom
currently back on cm6 with snap kernel. Still no go but only on wifi networks that require a password
I/wpa_supplicant( 1424): Authentication with 00:18:01:ec:77:55 timed out.
V/WifiMonitor( 114): Event [Authentication with 00:18:01:ec:77:55 timed out.]
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55]
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiStateTracker( 114): Changing supplicant state: ASSOCIATING ==> DISCONNECTED
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 114): Changing supplicant state: DISCONNECTED ==> SCANNING
E/Tethering( 114): attempting to remove unknown iface (usb0), ignoring
W/Process ( 114): Unable to open /proc/1086/status
W/Process ( 114): Unable to open /proc/1149/status
W/Process ( 114): Unable to open /proc/1222/status
I/wpa_supplicant( 1424): Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55
V/WifiMonitor( 114): Event [Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)]
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55]
V/WifiStateTracker( 114): Changing supplicant state: SCANNING ==> ASSOCIATING
D/dalvikvm( 1389): GC_FOR_MALLOC freed 5561 objects / 526224 bytes in 54ms
D/WifiStateTracker( 114): Reset connections and stopping DHCP
D/WifiStateTracker( 114): Disabling interface
D/NetworkStateTracker( 114): setDetailed state, old =DISCONNECTED and new state=DISCONNECTED
I//system/bin/wpa_supplicant( 1422): l2_packet_receive - recvfrom: Network is down
I/wpa_supplicant( 1424): Authentication with 00:18:01:ec:77:55 timed out.
V/WifiMonitor( 114): Event [Authentication with 00:18:01:ec:77:55 timed out.]
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55]
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiStateTracker( 114): Changing supplicant state: ASSOCIATING ==> DISCONNECTED
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 114): Changing supplicant state: DISCONNECTED ==> SCANNING
D/dalvikvm( 1135): GC_EXPLICIT freed 1616 objects / 128264 bytes in 52ms
I/wpa_supplicant( 1424): Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55
V/WifiMonitor( 114): Event [Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)]
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55]
V/WifiStateTracker( 114): Changing supplicant state: SCANNING ==> ASSOCIATING
D/dalvikvm( 1389): GC_FOR_MALLOC freed 5261 objects / 491704 bytes in 39ms
D/WifiStateTracker( 114): Reset connections and stopping DHCP
D/WifiStateTracker( 114): Disabling interface
D/NetworkStateTracker( 114): setDetailed state, old =DISCONNECTED and new state=DISCONNECTED
I//system/bin/wpa_supplicant( 1422): l2_packet_receive - recvfrom: Network is down
I/wpa_supplicant( 1424): Authentication with 00:18:01:ec:77:55 timed out.
V/WifiMonitor( 114): Event [Authentication with 00:18:01:ec:77:55 timed out.]
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55]
V/WifiStateTracker( 114): Changing supplicant state: ASSOCIATING ==> DISCONNECTED
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 114): Changing supplicant state: DISCONNECTED ==> SCANNING
D/dalvikvm( 479): GC_EXPLICIT freed 220 objects / 12792 bytes in 72ms
I/wpa_supplicant( 1424): Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55
V/WifiMonitor( 114): Event [Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)]
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55]
V/WifiStateTracker( 114): Changing supplicant state: SCANNING ==> ASSOCIATING
D/WifiStateTracker( 114): Reset connections and stopping DHCP
D/WifiStateTracker( 114): Disabling interface
D/NetworkStateTracker( 114): setDetailed state, old =DISCONNECTED and new state=DISCONNECTED
I//system/bin/wpa_supplicant( 1422): l2_packet_receive - recvfrom: Network is down
E/Tethering( 114): attempting to remove unknown iface (usb0), ignoring
I/wpa_supplicant( 1424): Authentication with 00:18:01:ec:77:55 timed out.
V/WifiMonitor( 114): Event [Authentication with 00:18:01:ec:77:55 timed out.]
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55]
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiStateTracker( 114): Changing supplicant state: ASSOCIATING ==> DISCONNECTED
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 114): Changing supplicant state: DISCONNECTED ==> SCANNING
I/wpa_supplicant( 1424): Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55
V/WifiMonitor( 114): Event [Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)]
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55]
V/WifiStateTracker( 114): Changing supplicant state: SCANNING ==> ASSOCIATING
D/WifiStateTracker( 114): Reset connections and stopping DHCP
D/WifiStateTracker( 114): Disabling interface
D/NetworkStateTracker( 114): setDetailed state, old =DISCONNECTED and new state=DISCONNECTED
I//system/bin/wpa_supplicant( 1422): l2_packet_receive - recvfrom: Network is down
I/power ( 114): *** set_screen_state 0
D/SurfaceFlinger( 114): About to give-up screen, flinger = 0xa29a8
D/alogcat ( 1389): stopping ...
D/alogcat ( 1389): paused
D/AK8973 ( 86): Compass CLOSE
I/power ( 114): *** set_screen_state 1
D/alogcat ( 1389): stopping ...
D/alogcat ( 1389): resumed
D/AK8973 ( 86): Compass Start
D/dalvikvm( 1389): GC_FOR_MALLOC freed 12339 objects / 1513392 bytes in 94ms
D/SurfaceFlinger( 114): Screen about to return, flinger = 0xa29a8
D/dalvikvm( 1389): GC_FOR_MALLOC freed 5000 objects / 383928 bytes in 40ms
D/dalvikvm( 1389): GC_FOR_MALLOC freed 2373 objects / 260848 bytes in 37ms
D/dalvikvm( 1389): GC_FOR_MALLOC freed 2378 objects / 333856 bytes in 38ms
I/wpa_supplicant( 1424): Authentication with 00:18:01:ec:77:55 timed out.
V/WifiMonitor( 114): Event [Authentication with 00:18:01:ec:77:55 timed out.]
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:18:01:ec:77:55]
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 114): Changing supplicant state: ASSOCIATING ==> DISCONNECTED
V/WifiStateTracker( 114): Changing supplicant state: DISCONNECTED ==> SCANNING
D/dalvikvm( 1389): GC_FOR_MALLOC freed 3648 objects / 391384 bytes in 50ms
I/wpa_supplicant( 1424): Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)
I/wpa_supplicant( 1424): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55
V/WifiMonitor( 114): Event [Trying to associate with 00:18:01:ec:77:55 (SSID='FJ982' freq=2437 MHz)]
V/WifiMonitor( 114): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:18:01:ec:77:55]
V/WifiStateTracker( 114): Changing supplicant state: SCANNING ==> ASSOCIATING
D/WifiStateTracker( 114): Reset connections and stopping DHCP
D/dalvikvm( 1389): GC_FOR_MALLOC freed 4384 objects / 470416 bytes in 40ms
W/KeyCharacterMap( 1389): No keyboard for id 65540
W/KeyCharacterMap( 1389): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/WifiStateTracker( 114): Disabling interface
D/NetworkStateTracker( 114): setDetailed state, old =DISCONNECTED and new state=DISCONNECTED
I//system/bin/wpa_supplicant( 1422): l2_packet_receive - recvfrom: Network is down
D/dalvikvm( 1389): GC_FOR_MALLOC freed 1105 objects / 134688 bytes in 52ms
I/dalvikvm-heap( 1389): Grow heap (frag case) to 3.778MB for 39862-byte allocation
Ok if u have flash the latest radio and you are sure you're running version ending in .07.28 then I would recommend you flash the Rom over again. Do a titanium back up , then boot in to recovery. Do the regular wipe data etc and then flash the Rom. Once done test your WiFi again.
Sent from my Evo using XDA App
ill try that, first i'll cross my fingers and flash a new nightly
jahnile said:
Ok if u have flash the latest radio and you are sure you're running version ending in .07.28 then I would recommend you flash the Rom over again. Do a titanium back up , then boot in to recovery. Do the regular wipe data etc and then flash the Rom. Once done test your WiFi again.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
that did not help
Try flashing a different rom, see if you have the same issue. That way you'll def.ly know if this is an issue with the rom or some other issue.
Yeah this happens with the lastest fresh and cm6. I went ahead and used the PCM file used during the root process since it pits the everything including radios back at stock. Still no go
Its just odd cause its only on secure wireless networks
Yea it def.ly is wired. I believe it's def.ly the roms though, not sure what's the cause or what's the root of the issue but my guess is that it will be fix in the next update if it's a known issue...
problem solved, for whatever reason a reset on my router sovled this issue.
No clue why, it happened after a new radio and wimax flash but it was my pooply actiontec router from verizon
Lol, glad to hear cause it def.ly had me thinking 4 a min. BTW u should also have ur own router along with that big red 1 or remove it altogether. I know some fios set includes a built in router with the modem but u can get around that, just a thought.
Am a tech guy so just don't like 2 be restricted, lol.
Sent from my EVO using XDA App

[AOSP Wifi Issue] Wifi drops signal and won't reconnect

Hi everyone,
I recently moved to AOSP Roms since I'm sick of Sense and since that I'm experiencing this very weird Wifi-glitch. First of all, here's a logcat of what I get:
Code:
12-07 14:24:20.896 174 732 V WifiMonitor: Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
12-07 14:24:20.906 174 272 V WifiStateTracker: New network state is DISCONNECTED
12-07 14:24:20.906 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00]
12-07 14:24:20.906 174 272 V WifiStateTracker: Changing supplicant state: COMPLETED ==> DISCONNECTED
12-07 14:24:21.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:21.006 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:21.926 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:21.926 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:21.936 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:25.686 174 732 V WifiMonitor: Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
12-07 14:24:25.686 174 272 V WifiStateTracker: New network state is DISCONNECTED
12-07 14:24:25.716 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:25.716 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:24:25.906 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:24:26.916 174 272 D WifiStateTracker: Disabling interface
12-07 14:24:31.936 174 732 V WifiMonitor: Event [Authentication with 00:00:00:00:00:00 timed out.]
12-07 14:24:31.936 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00]
12-07 14:24:31.936 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:31.936 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> DISCONNECTED
12-07 14:24:31.936 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:32.866 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:32.866 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:32.876 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:42.846 174 732 V WifiMonitor: Event [Authentication with 00:11:6b:15:9a:4a timed out.]
12-07 14:24:42.856 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:42.876 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:24:42.876 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:42.876 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:43.716 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:43.716 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:43.736 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:47.886 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:24:48.886 174 272 D WifiStateTracker: Disabling interface
So, from what I understand, the Wifi all of a sudden disconnects and then loops in a DHCP reset process not calling for a new ip adress. I tried using a static ip - no luck either. Anyway, when I set my wifi policy to sleep on screen off this changes the wifi state to DORMANT and when I then wake it up, it starts the DHCPhandler and grabs a new ip. Completely turning wifi off in the settings and then switching it back on has the same effect. logcat:
Code:
12-07 14:28:59.966 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:28:59.966 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:29:00.966 174 272 D WifiStateTracker: Disabling interface
12-07 14:29:00.976 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> DORMANT
12-07 14:29:00.976 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:29:01.976 174 272 D WifiStateTracker: Disabling interface
12-07 14:29:02.296 174 732 V WifiMonitor: Event [CTRL-EVENT-DRIVER-STATE STOPPED]
12-07 14:29:02.306 174 272 V WifiStateTracker: Changing supplicant state: DORMANT ==> DORMANT
12-07 14:31:58.526 174 273 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:31:59.536 174 273 D WifiStateTracker: Disabling interface
12-07 14:32:00.306 174 732 V WifiMonitor: Event [CTRL-EVENT-DRIVER-STATE STARTED]
12-07 14:32:00.306 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:32:00.306 174 272 V WifiStateTracker: Changing supplicant state: DORMANT ==> SCANNING
12-07 14:32:00.976 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:32:00.976 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:32:00.976 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:32:00.986 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=4 BSSID=00:11:6b:15:9a:4a]
12-07 14:32:00.996 174 732 V WifiMonitor: Event [Associated with 00:11:6b:15:9a:4a]
12-07 14:32:00.996 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00]
12-07 14:32:00.996 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> ASSOCIATED
12-07 14:32:00.996 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [WPA: Key negotiation completed with 00:11:6b:15:9a:4a [PTK=CCMP GTK=CCMP]]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-CONNECTED - Connection to 00:11:6b:15:9a:4a completed (reauth) [id=0 id_str=]]
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATED ==> FOUR_WAY_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: FOUR_WAY_HANDSHAKE ==> FOUR_WAY_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: FOUR_WAY_HANDSHAKE ==> GROUP_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: GROUP_HANDSHAKE ==> COMPLETED
12-07 14:32:01.006 174 272 V WifiStateTracker: New network state is CONNECTED
12-07 14:32:01.026 174 734 D WifiStateTracker: DhcpHandler: DHCP request started
12-07 14:32:06.026 174 734 V WifiStateTracker: DhcpHandler: DHCP request succeeded
12-07 14:32:06.036 174 272 V WifiStateTracker: IP configuration: ipaddr 192.168.178.42 gateway 192.168.178.1 netmask 255.255.255.0 dns1 192.168.178.1 dns2 0.0.0.0 DHCP server 192.168.178.1 lease 864000 seconds
12-07 14:32:06.036 174 272 V NetworkStateTracker: Setting TCP values: [4095,87380,110208,4096,16384,110208] which comes from [net.tcp.buffersize.wifi]
I searched the interwebs myself for quite a while and came across pretty similar posts, but none of the threads contained a solution to the problem.
So, as I'm not even close to being a linux/android dev myself I kindly ask you geniuses to lent me a hand on this one, because I really started to love the clean look and amazing speed of AOSP ROMs.
Thanks in advance!
d0msen
Different behaviors on different ROMs:
CM 6, DeFrost: Connection dropping after a couple of seconds/minutes, regardless of the screen being on or off
CM 6 nightly with Vorkkernel: same as Oxygen, looks like it might be kernel related
CM 6 nightly 216 with 2.6.35.9-cyanogenmod [email protected] #10 kernel, no drops so far!
Oxygen: Connection drops after some minutes, regardless of the screen being on or off, comes back to life when DORMANT state is reached in between connection attempts, though
MUIU, Ultimate Droid: Connection stays on pretty long, can even take more than in hour till it drops, DORMANT gets it back on, WIFI is never dropping whilst the screen is on.
Sense ROMs: no reported issue till date
d0msen said:
First of all, if this isn't the right subforum to post this please move the thread to the right one, in my opinion it rather is a dev thing, as it seems to be somehow related to the core of the AOSP.
Hi everyone,
I recently moved to AOSP Roms since I'm sick of Sense and since that I'm experiencing this very weird Wifi-glitch. First of all, here's a logcat of what I get:
Code:
12-07 14:24:20.896 174 732 V WifiMonitor: Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
12-07 14:24:20.906 174 272 V WifiStateTracker: New network state is DISCONNECTED
12-07 14:24:20.906 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00]
12-07 14:24:20.906 174 272 V WifiStateTracker: Changing supplicant state: COMPLETED ==> DISCONNECTED
12-07 14:24:21.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:21.006 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:21.926 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:21.926 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:21.936 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:25.686 174 732 V WifiMonitor: Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
12-07 14:24:25.686 174 272 V WifiStateTracker: New network state is DISCONNECTED
12-07 14:24:25.716 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:25.716 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:24:25.906 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:24:26.916 174 272 D WifiStateTracker: Disabling interface
12-07 14:24:31.936 174 732 V WifiMonitor: Event [Authentication with 00:00:00:00:00:00 timed out.]
12-07 14:24:31.936 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:00:00:00:00:00]
12-07 14:24:31.936 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:31.936 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> DISCONNECTED
12-07 14:24:31.936 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:32.866 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:32.866 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:32.876 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:42.846 174 732 V WifiMonitor: Event [Authentication with 00:11:6b:15:9a:4a timed out.]
12-07 14:24:42.856 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=0 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:42.876 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:24:42.876 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:24:42.876 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> SCANNING
12-07 14:24:43.716 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:24:43.716 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:24:43.736 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:24:47.886 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:24:48.886 174 272 D WifiStateTracker: Disabling interface
So, from what I understand, the Wifi all of a sudden disconnects and then loops in a DHCP reset process not calling for a new ip adress. I tried using a static ip - no luck either. Anyway, when I set my wifi policy to sleep on screen off this changes the wifi state to DORMANT and when I then wake it up, it starts the DHCPhandler and grabs a new ip. Completely turning wifi off in the settings and then switching it back on has the same effect. logcat:
Code:
12-07 14:28:59.966 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> DISCONNECTED
12-07 14:28:59.966 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:29:00.966 174 272 D WifiStateTracker: Disabling interface
12-07 14:29:00.976 174 272 V WifiStateTracker: Changing supplicant state: DISCONNECTED ==> DORMANT
12-07 14:29:00.976 174 272 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:29:01.976 174 272 D WifiStateTracker: Disabling interface
12-07 14:29:02.296 174 732 V WifiMonitor: Event [CTRL-EVENT-DRIVER-STATE STOPPED]
12-07 14:29:02.306 174 272 V WifiStateTracker: Changing supplicant state: DORMANT ==> DORMANT
12-07 14:31:58.526 174 273 D WifiStateTracker: Reset connections and stopping DHCP
12-07 14:31:59.536 174 273 D WifiStateTracker: Disabling interface
12-07 14:32:00.306 174 732 V WifiMonitor: Event [CTRL-EVENT-DRIVER-STATE STARTED]
12-07 14:32:00.306 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
12-07 14:32:00.306 174 272 V WifiStateTracker: Changing supplicant state: DORMANT ==> SCANNING
12-07 14:32:00.976 174 732 V WifiMonitor: Event [Trying to associate with 00:11:6b:15:9a:4a (SSID='default' freq=2457 MHz)]
12-07 14:32:00.976 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:11:6b:15:9a:4a]
12-07 14:32:00.976 174 272 V WifiStateTracker: Changing supplicant state: SCANNING ==> ASSOCIATING
12-07 14:32:00.986 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=4 BSSID=00:11:6b:15:9a:4a]
12-07 14:32:00.996 174 732 V WifiMonitor: Event [Associated with 00:11:6b:15:9a:4a]
12-07 14:32:00.996 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00]
12-07 14:32:00.996 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATING ==> ASSOCIATED
12-07 14:32:00.996 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=5 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=6 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [WPA: Key negotiation completed with 00:11:6b:15:9a:4a [PTK=CCMP GTK=CCMP]]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-STATE-CHANGE id=0 state=7 BSSID=00:00:00:00:00:00]
12-07 14:32:01.006 174 732 V WifiMonitor: Event [CTRL-EVENT-CONNECTED - Connection to 00:11:6b:15:9a:4a completed (reauth) [id=0 id_str=]]
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: ASSOCIATED ==> FOUR_WAY_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: FOUR_WAY_HANDSHAKE ==> FOUR_WAY_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: FOUR_WAY_HANDSHAKE ==> GROUP_HANDSHAKE
12-07 14:32:01.006 174 272 V WifiStateTracker: Changing supplicant state: GROUP_HANDSHAKE ==> COMPLETED
12-07 14:32:01.006 174 272 V WifiStateTracker: New network state is CONNECTED
12-07 14:32:01.026 174 734 D WifiStateTracker: DhcpHandler: DHCP request started
12-07 14:32:06.026 174 734 V WifiStateTracker: DhcpHandler: DHCP request succeeded
12-07 14:32:06.036 174 272 V WifiStateTracker: IP configuration: ipaddr 192.168.178.42 gateway 192.168.178.1 netmask 255.255.255.0 dns1 192.168.178.1 dns2 0.0.0.0 DHCP server 192.168.178.1 lease 864000 seconds
12-07 14:32:06.036 174 272 V NetworkStateTracker: Setting TCP values: [4095,87380,110208,4096,16384,110208] which comes from [net.tcp.buffersize.wifi]
I searched the interwebs myself for quite a while and came across pretty similar posts, but none of the threads contained a solution to the problem.
So, as I'm not even close to being a linux/android dev myself I kindly ask you geniuses to lent me a hand on this one, because I really started to love the clean look and amazing speed of AOSP ROMs.
Thanks in advance!
d0msen
Click to expand...
Click to collapse
+1, getting this issue on Oxygen and CM ROM but not with Ultimate Droid.
getting the same since i changed to supervillain hd rom. before that, everything was ok.
Alright so I tried some other ROMs this afternoon and can confirm that Ultimate Droid does not have these wifi glitches.
Apart from that, MIUI has the problem, but somehow manages to stay connected longer than Oxygen or CM and it never occurred to me, that MIUI would drop the connection, while the screen is on.
Tested both ROMs with Wifi policy set to sleep on screen off and dynamic ip. Hope this helps
EDIT: Ultimate Droid just dropped the connection as well, looks like it's pretty similar to MIUI network-wise.
I have had this happen constantly since the earliest CM6 builds on my university (eduroam; wpa2 enterprise) network. If data's not being used constantly, wifi will die in 2-20 minutes and then needs to be toggled off and on before it reconnects again. Massive pain in the bum. My home wifi is fine.
The stock 2.1 ROM did not seem to have this problem. I've seen these issues brought up several times in here and on IRC - they appear to occur on non-standard network setups. I vaguely recall someone saying it had to do with Android trying to re-establish an idling connection after the security token had expired but, rather than re-authenticating properly, the system just keeps making requests with the invalid token. Someone also suggested it's something to do with migrating between access points on a multi-AP network. Not sure if this is at all accurate, but it would be nice to see this issue fixed.
Kinda not diggin my thread being moved without even giving a reason for that.
because maybe it doesn't belong in android development.. you're not developing anything?
Anyone else feel like this started some time around 2.2.1?
I'm having a similar glitch on Eduroam (PEAP + MSCHAPv2) networks...
since only few people have this problem, i suggest checking if its connected to your wlan access points. if you got a linux box with wlan card (or boot from a live cd), enter
Code:
iwlist [wlan device] scanning
to get a list of wlan devices, type
Code:
iwconfig
here is the output for my wlan, which does NOT drop (policy wifi never off - the battery killer)
Code:
Cell 03 - Address: ***DELETED***
Channel:10
Frequency:2.457 GHz (Channel 10)
Quality=67/70 Signal level=-43 dBm
Encryption key:on
ESSID:"wtf"
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 6 Mb/s; 9 Mb/s
11 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=00000000061f3181
Extra: Last beacon: 348ms ago
IE: Unknown: 0003777466
IE: Unknown: 010882848B0C12961824
IE: Unknown: 03010A
IE: Unknown: 2A0100
IE: Unknown: 32043048606C
IE: Unknown: DD180050F20201010A0002A3400027A4000042435E0062322F00
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK
IE: Unknown: DD0900037F01010024FF7F
breakdown: WPA2 with CCMP, max 54MBit on channel 10
reported a similir bug by me to cyanogen at october 29
http://code.google.com/p/cyanogenmod/issues/detail?id=2431
but no solution yet
I no longer have this issue with CM-216 but I did have it with about CM-200 and earlier (didn't use in between).
My iwlist output is:
Code:
Cell 01 - Address: ---------
Protocol:802.11b/g/n
ESSID:"Epa"
Mode:Managed
Channel:8
Quality:86/100 Signal level:-56 dBm Noise level:-81 dBm
Encryption key:on
Bit Rates:18 Mb/s
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PS
My radio is 32.49.00.32U_5.11.05.27
After two days of testing I can confirm that Wifi works flawlessly with the CM nightly 216! Something must have been changed in between 215 and 216 =)

[Q] Locked keystore

Hey,
I'm having a problem connecting to my wireless network from time to time.
This time, I managed to get a logcat of the output - does anyone have any ideas of what keystore locked means, and how to fix it?
Here is the log output:
V/WifiMonitor( 1257): Event [WPS-AP-AVAILABLE ]
V/WifiMonitor( 1257): Event [Trying to associate with 00:a0:c5:b2:1a:77 (SSID='GurliNETAtHome' freq=2452 MHz)]
V/WifiMonitor( 1257): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=00:a0:c5:b2:1a:77]
V/WifiStateTracker( 1257): Changing supplicant state: SCANNING ==> ASSOCIATING
I/keystore( 1195): uid: 1000 action: t -> 2 state: 2 -> 2 retry: 4
V/WifiStateTracker( 1257): KeyStore.LOCKED
I/wpa_supplicant( 1452): DISABLE_80211X
I/wpa_supplicant( 1452): CTRL_IFACE: wpa_supplicant_ctrl_iface_disable_80211X
D/dalvikvm( 1523): GC_EXPLICIT freed 3080 objects / 136592 bytes in 103ms
I/wpa_supplicant( 1452): CTRL-EVENT-STATE-CHANGE id=1 state=4 BSSID=00:a0:c5:b2:1a:77
V/WifiMonitor( 1257): Event [CTRL-EVENT-STATE-CHANGE id=1 state=4 BSSID=00:a0:c5:b2:1a:77]
V/WifiStateTracker( 1257): Changing supplicant state: ASSOCIATING ==> ASSOCIATED
I/wpa_supplicant( 1452): Associated with 00:a0:c5:b2:1a:77
I/wpa_supplicant( 1452): RX EAPOL from 00:a0:c5:b2:1a:77
I/wpa_supplicant( 1452): RX EAPOL:return ,due to keystore locked
V/WifiMonitor( 1257): Event [Associated with 00:a0:c5:b2:1a:77]
I/wpa_supplicant( 1452): l2_packet_send: ret = '4'
I/wpa_supplicant( 1452): RX EAPOL from 00:a0:c5:b2:1a:77
I/wpa_supplicant( 1452): RX EAPOL:return ,due to keystore locked
D/WifiStateTracker( 1257): Reset connections and stopping DHCP
I/wpa_supplicant( 1452): Rx Data Filter Remove [5] command
I/wpa_supplicant( 1452): auto ip disabled
I/wpa_supplicant( 1452): Rx Data Filter: do not support, ignore
D/NetUtils( 1257): ifc_get_info addr=0 !
D/dalvikvm( 1381): GC_EXPLICIT freed 5286 objects / 208296 bytes in 49ms
I/wpa_supplicant( 1452): RX EAPOL from 00:a0:c5:b2:1a:77
I/wpa_supplicant( 1452): RX EAPOL:return ,due to keystore locked
D/WifiStateTracker( 1257): Disabling interface
I//system/bin/wpa_supplicant( 1450): l2_packet_receive - recvfrom: Network is down
D/dalvikvm( 1564): GC_EXPLICIT freed 3389 objects / 156824 bytes in 70ms
I/wpa_supplicant( 1452): Authentication with 00:a0:c5:b2:1a:77 timed out.
V/WifiMonitor( 1257): Event [Authentication with 00:a0:c5:b2:1a:77 timed out.]
I/wpa_supplicant( 1452): CTRL-EVENT-STATE-CHANGE id=1 state=0 BSSID=00:00:00:00:00:00
V/WifiMonitor( 1257): Event [CTRL-EVENT-STATE-CHANGE id=1 state=0 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 1257): Changing supplicant state: ASSOCIATED ==> DISCONNECTED
I/wpa_supplicant( 1452): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
V/WifiMonitor( 1257): Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
V/WifiStateTracker( 1257): New network state is DISCONNECTED
Click to expand...
Click to collapse
Not sure, but you may be experiencing this bug: code.google.com /p/android/issues/detail?id=16460 (sprry can't post links yet)
I'm having the same issue on Droid Incredible, Stock + Root ROM 2.3.4. It's really annoying, hope the community knows a fix.

[N2E][1.1][solved] wifi/dhcp lease issues

SOLUTION:
If any of you are having dhcp-related issues (e.g. if WiFi status, after displaying "Connecting to YOUR-AP", says 'Unsuccessful') with some routers, the solution - or at least, the one that worked for me after much trial and error - is to replace /system/lib/libnetutils.so with the 1.0 version (attached). Before, you had to either (a) set up a static dhcp lease for your nook in your router (b) use an app like WiFi Static to have your Nook not use dhcp at all.
If you're having this issue, please try this out to confirm the fix works. Please make sure to remove any static dhcp lease assignments that you've set up for your Nook before chiming in.
(Just realized that I hit the wrong button and nothing attached. Old libnetutils is now attached to this post and can also be found here!)
Code:
## backup the 1.1 file somewhere, change name to keep track
adb pull /system/lib/libnetutils.so libnetutils_1.1.so
## remount /system as writable
adb shell mount -o rw,remount /dev/block/mmcblk0p5 /system
## push the 1.0 file attached (assuming you're in same directory)
adb push libnetutils.so /system/lib/
## fix permissions (ownership is already correct, root.root)
adb shell chmod 644 /system/lib/libnetutils.so
## reboot
adb reboot
If it doesn't work - I have no answers for you. I do NOT recommend you try patching the framework, or pushing over wpa_supplicant from 1.0. The former did not change anything and the latter prevents the Nook from associating with your AP after waking up from standby entirely. Replacing /system/etc/wifi/tiwlan_drv.ko or /system/bin/dhcpcd also did not change anything.
My initial half-solutions, speculations, and meanderings, in which I figured out everything that, uh, didn't work, make up the rest of this post and thread
NOTE:
I did have one instance of WiFi reporting it was 'Unsuccessful' (which has been about dhcp) when coming out of standby (as opposed to 'Disconnected' - which is a wpa_supplicant problem). When I checked the logs, wpa_supplicant was complaining that it could not find a suitable AP though, so maybe it is about wpa_supplicant. If the problem persists or happens again, I will try replacing libwpa_client.so with the 1.0 one to see if that changes anything, even though 'Unsuccessful' has referred to dhcp.
Ugh. It looks like downloading and compiling the Android source code/decompiling some .so drivers might be on the horizon. If that's the case, then I'm out, at least for a while. In any case, turning wifi on and off isn't that much of a hassle.
-----------------------------------------------------------------------------
Hey all,
It hasn't been discussed here very much, but over at B&N's official forums, a good amount of people have been complaining that their Nook hasn't been able to connect to their WiFi, both at home and out and about, after the 1.1.0 update. Particularly, Verizon FiOS customers with the stock ActionTec MI424-WR router have been affected - myself included.
Looking at my logs, it looked like DHCP was timing out for some reason. So at first, I went into my FiOS router and had it assign a 'static' IP to my Nook explicitly; this worked fine. Then, realizing that this would only work on this single router and wouldn't cure what ails me if it turns out the same issue comes up on the road. So I poked around in the market and found an app that'll allow me to do what I can already do with my stock Android phone, and have the nook assign itself a Static IP when detecting certain APs. Now that's not going to work if you have no other way to connect to the AP than your Nook AND you do not know the ip address of the AP, but it's still helpful.
Investigation:
As the rest of the thread suggests, I've been poking around the N2E internals in an effort to figure out just what it is got changed in the wifi/dhcp stack between 1.0 and 1.1, and after some testing, I've come closer to isolating the issue!
Replacing /system/lib/libnetutils.so with its 1.0 versions gets dhcp to 'work' again! In other words, without any additional configuration whatsoever!
Unfortunately, I think that something might still be awry. Every once in a while, the WiFi state will change to 'disconnected'. I'm not sure if this is normal behavior or what, but I don't think it is, because it's been happening with 20-30 mins of a successful connection to the router, and did not occur when I was just having the router assign a static ip via dhcp or when I wasn't using dhcp at all. But, perhaps that's the way it worked with 1.0...I really don't know, because I've never really used 1.0 on a regular basis. In fact, I haven't used the nook with dhcp on a regular basis, and am basically flying blind here.
The WiFi handling stack inside /system/framework/framework.jar has also changed. But taking the wifi folder from the 1.0 framework.jar and rebuilding the 1.1 jar based on that has had no effect on any issue - it did not help dhcp work, and nor did it prevent the WiFi from changing to 'disconnected'.
While diff indicates that /system/etc/wifi/tiwlan_drv.ko has also changed, replacing it with the 1.0 version has no effect on any of the above issues.
I did some more digging around and it seems like wpa_supplicant and dhcpcd in /system/bin/ also have slightly different binaries in 1.1.0. But when I replaced them with the binaries from 1.0.0 (but using the 1.1.0 tiwlan_drv.ko), it didn't work, and DHCP still doesn't complete successfully. I have no reason to believe that using the older driver would magically fix anything - doesn't this sound like some configuration issue somewhere?
The thing is, I'm not quite sure where these configuration files or dbs would be. I dug around a bit more and found that wpa_supplicant refers to the wpa_supplicant.conf in /data/misc/wifi (the one in /system/etc/wifi doesn't seem to ever get updated). But this has no bearing on what goes on with dhcpcd, and I haven't been able to find out what, if anything, controls it
Any takers?
Also, the reason I thought that it still worked was that the static configuration that WiFi Static makes for you is not deleted by default when WiFi Static is uninstalled. To shut off static ip, the settings table at
/data/data/com.android.providers.system/databases/settings.db ​has to be modified so that the entry with name "wifi_use_static_ip" should have a it's value="0", not "1".
Probably it will not help, but in my experience Nook couldn't connect when my router (Siemens SLI 5300) has secured with WPA-AES key. Then i've made some experiments and i found out that using WPA2-AES key it works without any problems. 1.1 firmware of course.
domi.nos said:
Probably it will not help, but in my experience Nook couldn't connect when my router (Siemens SLI 5300) has secured with WPA-AES key. Then i've made some experiments and i found out that using WPA2-AES key it works without any problems. 1.1 firmware of course.
Click to expand...
Click to collapse
"Connect" and "obtaining IP address" is two different things.
I did some digging trough the sources today but couldn't find anything obvious in regards to the dhcp issue.
As this seem to be quite a common issue I'm a little surprised that B&N hasn't released some sort of fix yet.
With that said, I've only experienced this once, and that was with 1.0.1
ros87 said:
"Connect" and "obtaining IP address" is two different things.
I did some digging trough the sources today but couldn't find anything obvious in regards to the dhcp issue.
As this seem to be quite a common issue I'm a little surprised that B&N hasn't released some sort of fix yet.
With that said, I've only experienced this once, and that was with 1.0.1
Click to expand...
Click to collapse
Roger-
So did I miss anything? It looks like everything related to wlan/dhcpcd can be found in:
/system/bin (binaries for loading wifi driver, wpa_supplicant, and dhcpcd)
/system/etc/wifi (wifi driver, minor configuration)
/system/etc/dhcpcd (minor configuration)
/data/misc/wifi (wpa_supplicant.conf that actually gets used)
/data/data/com.android.providers.system/databases/settings.db ​
I'm not quite sure what to look for in the settings.db. That database corresponds to this part of the android api though:
http://developer.android.com/reference/android/provider/Settings.System.html
I'm also not sure how to actually configure what calls wpa_supplicant and dhcpcd. Looking at my logs, it looks like a few different services are on the scene, mostly reporting what did what, I guess? But I don't know how to configure them or which of them spawns wpa_supplicant or dhcpcd. Here's the log I posted a few weeks ago, again, for convenience (don't have to click the link from above):
Code:
I/wpa_supplicant( 2539): CTRL-EVENT-SCAN-RESULTS Ready
I/wpa_supplicant( 2539): Trying to associate with FIOS_ROUTER_MAC_ADDRESS (SSID='MYSSID' freq=2462 MHz)
I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=-1 state=3
V/WifiMonitor( 805): Event [Trying to associate with FIOS_ROUTER_MAC_ADDRESS (SSID='MYSSID' freq=2462 MHz)]
V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3]
V/WifiStateTracker( 805): Changing supplicant state: DISCONNECTED ==> ASSOCIATING
D/NetworkStateTracker( 805): setDetailed state, old =DISCONNECTED and new state=CONNECTING
D/ConnectivityService( 805): ConnectivityChange for WIFI: CONNECTING/CONNECTING
I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=4
I/wpa_supplicant( 2539): Associated with FIOS_ROUTER_MAC_ADDRESS
I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=5
V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4]
V/WifiStateTracker( 805): Changing supplicant state: ASSOCIATING ==> ASSOCIATED
D/NetworkStateTracker( 805): setDetailed state, old =CONNECTING and new state=CONNECTING
V/WifiMonitor( 805): Event [Associated with FIOS_ROUTER_MAC_ADDRESS]
V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=5]
I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=5
I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=6
I/wpa_supplicant( 2539): WPA: Key negotiation completed with FIOS_ROUTER_MAC_ADDRESS [PTK=CCMP GTK=CCMP]
I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=7
I/wpa_supplicant( 2539): CTRL-EVENT-CONNECTED - Connection to FIOS_ROUTER_MAC_ADDRESS completed (auth) [id=2 id_str=]
V/WifiStateTracker( 805): Changing supplicant state: ASSOCIATED ==> FOUR_WAY_HANDSHAKE
D/NetworkStateTracker( 805): setDetailed state, old =CONNECTING and new state=AUTHENTICATING
D/ConnectivityService( 805): ConnectivityChange for WIFI: CONNECTING/AUTHENTICATING
V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=5]
V/WifiStateTracker( 805): Changing supplicant state: FOUR_WAY_HANDSHAKE ==> FOUR_WAY_HANDSHAKE
V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=6]
V/WifiStateTracker( 805): Changing supplicant state: FOUR_WAY_HANDSHAKE ==> GROUP_HANDSHAKE
D/NetworkStateTracker( 805): setDetailed state, old =AUTHENTICATING and new state=AUTHENTICATING
V/WifiMonitor( 805): Event [WPA: Key negotiation completed with FIOS_ROUTER_MAC_ADDRESS [PTK=CCMP GTK=CCMP]]
V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7]
V/WifiStateTracker( 805): Changing supplicant state: GROUP_HANDSHAKE ==> COMPLETED
V/WifiMonitor( 805): Event [CTRL-EVENT-CONNECTED - Connection to FIOS_ROUTER_MAC_ADDRESS completed (auth) [id=2 id_str=]]
V/WifiStateTracker( 805): New network state is CONNECTED
W/BluetoothHeadset( 805): Proxy not attached to service
D/WifiStateTracker( 805): DhcpHandler: DHCP request started
D/NetworkStateTracker( 805): setDetailed state, old =AUTHENTICATING and new state=OBTAINING_IPADDR
D/dhcpcd ( 2546): dhcpcd 4.0.15 starting
D/dhcpcd ( 2546): hardware address = NOOK_MAC_ADDRESS
D/dhcpcd ( 2546): executing `/system/etc/dhcpcd/dhcpcd-run-hooks', reason PREINIT
D/WsprService( 862): Received android.net.wifi.STATE_CHANGE action.
D/SettingsWifiEnabler( 862): Received network state changed to NetworkInfo: type: WIFI[], state: CONNECTING/OBTAINING_IPADDR, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
D/dhcpcd ( 2546): host does not support a monotonic clock - timing can skew
D/dhcpcd ( 2546): broadcasting for a lease
D/dhcpcd ( 2546): sending DHCP_DISCOVER with xid 0x834efe68, next in 2.52 seconds
D/ConnectivityService( 805): ConnectivityChange for WIFI: CONNECTING/OBTAINING_IPADDR
D/SurfaceFlinger( 805): Frame buffer posted; elapsed time = 15 msecs
D/SurfaceFlinger( 805): Frame buffer posted; elapsed time = 18 msecs
D/dhcpcd ( 2546): sending DHCP_DISCOVER with xid 0x834efe68, next in 3.12 seconds
I/WifiStateTracker( 805): DhcpHandler: DHCP request failed: Timed out waiting for DHCP to finish
I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=2 state=8
V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=2 state=8]
V/WifiStateTracker( 805): Changing supplicant state: COMPLETED ==> DORMANT
D/WifiStateTracker( 805): Deconfiguring interface and stopping DHCP
D/dhcpcd ( 2546): received SIGTERM, stopping
I/wpa_supplicant( 2539): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
I/wpa_supplicant( 2539): CTRL-EVENT-STATE-CHANGE id=-1 state=8
V/WifiMonitor( 805): Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
V/WifiMonitor( 805): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=8]
D/NetworkStateTracker( 805): setDetailed state, old =OBTAINING_IPADDR and new state=FAILED
I/wpa_supplicant( 2539): succeeded in stopping the last periodical scan
E/wpa_supplicant( 2539): Start periodical(connection) scan.
D/NookWifiManager( 1045): Cannot connect to pre-configured networks
D/DeviceManagerBroadcastReceiver( 1097): action (com.nook.intent.action.OOBE_WIFI_ENABLE_RESPONSE)
D/NookWifiManager( 1097): Cannot connect to pre-configured networks
D/NookWifiManager( 1116): Cannot connect to pre-configured networks
V/WfDownloader( 1116): +WifiManagerObserver: Wifi status: FAILURE__FAILED_TO_ASSOCIATE
V/WfDownloader( 1116): -WifiManagerObserver
V/WifiStateTracker( 805): New network state is DISCONNECTED
V/WifiStateTracker( 805): Changing supplicant state: DORMANT ==> DORMANT
D/ConnectivityService( 805): ConnectivityChange for WIFI: DISCONNECTED/FAILED
V/ConnectivityService( 805): Attempt to connect to WIFI failed.
D/WsprService( 862): Received android.net.wifi.STATE_CHANGE action.
D/SettingsWifiEnabler( 862): Received network state changed to NetworkInfo: type: WIFI[], state: DISCONNECTED/FAILED, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
There is also the following in /init.rc. But shouldn't that only get run once?
service wlan_loader /system/bin/tiwlan_loader \
-f /system/etc/wifi/firmware.bin \
-i /system/etc/wifi/tiwlan.ini \
-e /rom/devconf/WiFiBackupCalibration
disabled
oneshot
service ifcfg_ti /system/bin/ifconfig tiwlan0 up
disabled
oneshot
service wpa_supplicant /system/bin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/data/misc/wifi/wpa_supplicant.conf -dd
socket wpa_tiwlan0 dgram 660 wifi wifi
disabled
oneshot
service dhcpcd /system/bin/dhcpcd -ABKL -d tiwlan0
disabled
oneshot
# TI WLAN Soft AP related services and configuration
service wlan_ap_loader /system/bin/tiap_loader \
-f /system/etc/wifi/softap/firmware_ap.bin \
-i /system/etc/wifi/softap/tiwlan_ap.ini
disabled
oneshot
service udhcpd /system/bin/udhcpd /system/etc/udhcpd/udhcpdWlan.conf
disabled
oneshot
service hostapd /system/bin/hostapd -dd /data/misc/wifi/hostapd.conf
disabled
oneshot
service keystore /system/bin/keystore /data/misc/keystore
user keystore
group keystore
socket keystore stream 666​I haven't got an earlier version of init.rc to compare this to.
Is there any way to specify that dhcpcd let DHCP_DISCOVER actions take longer? I thought it was supposed to take 60 seconds by default, so it is being configured otherwise elsewhere. But where??? Right now it sort of gives up right away.
-e
LastSilmaril said:
Roger-
So did I miss anything? It looks like everything related to wlan/dhcpcd can be found in:
Click to expand...
Click to collapse
Well, we don't have the sources for the kernel module, nor the binaries, so I was just looking at the kernel stuff.
My guess is that it is some miniscule thing somewhere, but not in kernel nor the configs as far as I can see.
Well if it's not in the kernel that's good right? And by kernel, do you mean the kernel itself or the driver?
I found a manpage for dhcpcd; the following switches are being passed to dhcpcd in init.rc:
http://roy.marples.name/cgi-bin/man-cgi?dhcpcd
-A, --noarp
Don't request or claim the address by ARP. This also disables
IPv4LL.
-B, --nobackground
Don't run in the background when we acquire a lease. This is
mainly useful for running under the control of another process,
such as a debugger or a network manager.
-K, --nolink
Don't receive link messages for carrier status. You should only
have to use this with buggy device drivers or running dhcpcd
through a network manager.
-L, --noipv4ll
Don't use IPv4LL (aka APIPA, aka Bonjour, aka ZeroConf).
So as the lack of much standalone configuration files for dhcpcd has already hinted, uh, this doesn't seem to be a dhcpcd config issue.
I'm not sure how to be able to write to init.rc (so I can add "-t 30" to see if that'll do anything). I don't know what partition it's on but cannot just write it back to root (read-only filesystem). Setting system to writable makes no difference, so we can assume it's not hiding on there somewhere. There is a copy of it at /data/local/tmp/init.rc but just modifying that does nothing; /init.rc is not a symlink to /data/local/tmp/init.rc.
This thing might be helpful, but is a bit over my head.
http://blog.linuxconsulting.ro/2010/04/porting-wifi-drivers-to-android.html
LOL, I've been pushing and pulling things without giving a second thought to proper permissions. Can somebody please run ls -l on the following files and post what the proper permissions are supposed to be? I haven't run into issues yet, but I don't want to muck things up.
Code:
/system/etc/wifi/tiwlan0-drv.ko
/system/bin/wpa_supplicant
/system/bin/dhcpcd
/system/etc/dhcpcd/dhcpcd-run-hooks
really? I'm surprised more people here aren't completely up in arms about this issue, which is a matter of basic usability. I've even come across someone with an e2000 with dd-wrt with issues, so it's not just old routers/crippled ISP routers that this is happening to. BN is completely unresponsive, so it's up to us!
LastSilmaril said:
LOL, I've been pushing and pulling things without giving a second thought to proper permissions. Can somebody please run ls -l on the following files and post what the proper permissions are supposed to be? I haven't run into issues yet, but I don't want to muck things up.
Code:
/system/etc/wifi/tiwlan0-drv.ko
/system/bin/wpa_supplicant
/system/bin/dhcpcd
/system/etc/dhcpcd/dhcpcd-run-hooks
Click to expand...
Click to collapse
Correct permissions (per my backup) are:
1. /system/bin/dhcpcd
755, root.shell
2. /system/bin/wpa_supplicant
755, root.shell
3. /system/etc/wifi/tiwlan_drv.ko
644, root.root
4. /system/etc/dhcpcd/dhcpcd-run-hooks
550, dhcp.shell
Also, the diffing I did that led me to think that wpa_supplicant and dhcpcd had changed may not have been accurate, since it may be that the Linux Reader extracting program I was using mucks with the files. When I compare the file sizes of wpa_supplicant and dhcpcd between my 1.0.0 and 1.1.0 backups, I found no difference. The difference is there between the WiFi drivers though - that's something that's definitely changed. But simply dropping it in *still* does not work. It's maddening...
LastSilmaril said:
The difference is there between the WiFi drivers though - that's something that's definitely changed. But simply dropping it in *still* does not work. It's maddening...
Click to expand...
Click to collapse
I don't think this is a problem for that many users of the NST, you might find 20 - 30 reports on the net, maybe a hundred if you really go at it, but that still is just a fraction of the NST owners. So don't expect to see much interest in this topic I'm afraid.
Now, the tiwlan drivers are not unique to the NST, they are part of the omap3 platform and maintained by TI and you might want to look for similar problems there and even updated sources (if the tiwlan module is at fault at all).
ros87 said:
I don't think this is a problem for that many users of the NST, you might find 20 - 30 reports on the net, maybe a hundred if you really go at it, but that still is just a fraction of the NST owners. So don't expect to see much interest in this topic I'm afraid.
Now, the tiwlan drivers are not unique to the NST, they are part of the omap3 platform and maintained by TI and you might want to look for similar problems there and even updated sources (if the tiwlan module is at fault at all).
Click to expand...
Click to collapse
That's exactly the problem Roger - I'm not sure how it is they are at fault if dumping in the old 1.0.0 driver does not help matters...but I can't seem to find anything else that's changed! In the meantime I mucked things up poking around, and decided to go back to stock 1.1.0 and am now re-rooting.
In the meantime though, I'm not sure where exactly to poke around; do you know what version of OMAP3 is in the nook?
(BTW- does anybody know a way around the 'sideloaded books on sdcard do not persist in shelves' problem? Happens in all firmwares, stock or rooted...)
-e
...how do we 'decompile' (meh...) stuff in android?
I have discovered apktool.
Poking around framework.jar under smali/android/net/wifi, there are several changes in there in comparison to the framework from 1.0.
1) BnIpConfig.smali and friends are not in 1.0 (at least not in android/net/wifi)
2) WifiStateTracker$DhcpHandler.smali is 3KB bigger in 1.1.
and many more...
Could this finally be it? I'm tempted to simply dump the android/net/wifi folder in from 1.0 and see what happens (love being fully backed up).
Also, /system/lib/libnetutils.so has changed.
I'm a little bit uneasy messing with this, but I've got backup upon backup now, including several CWM backups, so I'm gonna press on!
I think I may have finally figured it out, after some further testing. Nothing to do with patching framework.jar. But, last time I thought it worked, status would change to 'Disconnected' for no apparent reason after a few minutes. If I'm still connected to WiFi in two hours, I'll post a solution and instructions.
LastSilmaril said:
I think I may have finally figured it out, after some further testing. Nothing to do with patching framework.jar. But, last time I thought it worked, status would change to 'Disconnected' for no apparent reason after a few minutes. If I'm still connected to WiFi in two hours, I'll post a solution and instructions.
Click to expand...
Click to collapse
EDIT: ...Yup, it's definitely disconnecting at some point. I'm not sure if this is normal behavior or what, but somehow I doubt it.
OK, quick update...
1) First, it seems that the only file with any relevance (and this makes sense) is libnetutils.so. The older binaries of dhcpcd and wpa_supplicant are not necessary to get the dhcp to complete.
2)WiFi intermittently switching to 'disconnected' is because of a failure to associate with the AP - not anything to do with dhcp. Why it has to associate again - what causes the 'Disconnect event' - I do not know. But as my wpa_supplicant when this was happening was from 1.0 (and the failure to associate was unambiguously reported by wpa_supplicant), I decided to push back the stock 1.1 wpa_supplicant. Let's see if anything changes as a result. If so, then this whole masturbatory thread will have turned out to be about one measly file

Wildfire can't connect to ad-hoc wifi network

Hi. I setup on my Ubuntu box ad-hoc wifi network with wep access key. Wifi ad-hoc network have static ip and Wildfire have is configured to this static ip. Android see this ad-hoc network, connect to it and disconnect quickly and so a further in a loop. Below logcat:
Code:
V/WifiStateTracker( 200): Changing supplicant state: DORMANT ==> DORMANT
V/WifiStateTracker( 200): Changing supplicant state: DORMANT ==> DORMANT
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
E/ConnectivityService( 200): Attempt to connect to WIFI failed.
E/ConnectivityService( 200): not failing over to mobile type 0 because Mobile Data Disabled
D/Tethering( 200): MasterInitialState.processMessage what=3
V/WifiStateTracker( 200): Changing supplicant state: DORMANT ==> SCANNING
D/PicasaSyncManager( 1051): background data: true
D/dalvikvm( 2862): GC_CONCURRENT freed 380K, 53% free 3402K/7111K, external 0K/0K, paused 23ms+6ms
D/GTalkService( 353): ##### Network broadcast (connected=false) type=WIFI, state=DISCONNECTED
D/GTalkService( 353): [GTalkConnection.1] setInternalNetworkState: type=1, state=DISCONNECTED
D/Beautiful Widgets(4105)( 981): CONNECTIVITY_CHANGE
I/CheckinService( 353): Preparing to send checkin request
I/EventLogService( 353): Accumulating logs since 1340186208334
D/PicasaSyncManager( 1051): reject MetadataSyncTask (****************) because downsync is disabled
D/CMStats ( 1017): CONNECTIVITY_ACTION: noConnectivity = false
D/CMStats ( 1017): CONNECTIVITY_ACTION: starting service
I/wpa_supplicant( 714): Trying to associate with fe:b9:1c:bd:82:08 (SSID='digital-n0123' freq=2412 MHz)
D/CMStats ( 1017): User has opted in -- reporting.
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=fe:b9:1c:bd:82:08
D/CMStats ( 1017): SERVICE: Device ID=1831971E0D06BD1183F51FFA963A31C5
D/CMStats ( 1017): SERVICE: Device Name=buzz
D/CMStats ( 1017): SERVICE: Device Version=CyanogenMod-7.2.0-RC3-buzz
D/CMStats ( 1017): SERVICE: Country=pl
D/CMStats ( 1017): SERVICE: Carrier=Plus
D/CMStats ( 1017): SERVICE: Carrier ID=26001
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=fe:b9:1c:bd:82:08
I/wpa_supplicant( 714): Associated with 00:00:00:00:00:00
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=fe:b9:1c:bd:82:08
I/wpa_supplicant( 714): CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (reauth) [id=2 id_str=]
V/WifiMonitor( 200): Event [Trying to associate with fe:b9:1c:bd:82:08 (SSID='digital-n0123' freq=2412 MHz)]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=fe:b9:1c:bd:82:08]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=fe:b9:1c:bd:82:08]
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=fe:b9:1c:bd:82:08
V/WifiMonitor( 200): Event [Associated with 00:00:00:00:00:00]
I/wpa_supplicant( 714): Associated with ee:45:6a:2b:a2:b9
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 714): CTRL-EVENT-CONNECTED - Connection to ee:45:6a:2b:a2:b9 completed (reauth) [id=2 id_str=]
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=fe:b9:1c:bd:82:08]
V/WifiStateTracker( 200): Changing supplicant state: SCANNING ==> ASSOCIATING
V/WifiMonitor( 200): Event [CTRL-EVENT-CONNECTED - Connection to 00:00:00:00:00:00 completed (reauth) [id=2 id_str=]]
V/WifiStateTracker( 200): Changing supplicant state: ASSOCIATING ==> ASSOCIATED
V/WifiStateTracker( 200): Changing supplicant state: ASSOCIATED ==> COMPLETED
D/CMStats ( 1017): SERVICE: setting checkedin=false
I/wpa_supplicant( 714): Associated with ee:45:6a:2b:a2:b9
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 714): CTRL-EVENT-CONNECTED - Connection to ee:45:6a:2b:a2:b9 completed (reauth) [id=2 id_str=]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=fe:b9:1c:bd:82:08]
V/WifiStateTracker( 200): New network state is CONNECTED
V/WifiMonitor( 200): Event [Associated with ee:45:6a:2b:a2:b9]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00]
V/WifiMonitor( 200): Event [CTRL-EVENT-CONNECTED - Connection to ee:45:6a:2b:a2:b9 completed (reauth) [id=2 id_str=]]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=00:00:00:00:00:00]
V/WifiMonitor( 200): Event [Associated with ee:45:6a:2b:a2:b9]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00]
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 714): Associated with fe:b9:1c:bd:82:08
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 714): CTRL-EVENT-CONNECTED - Connection to fe:b9:1c:bd:82:08 completed (reauth) [id=2 id_str=]
V/WifiMonitor( 200): Event [CTRL-EVENT-CONNECTED - Connection to ee:45:6a:2b:a2:b9 completed (reauth) [id=2 id_str=]]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 200): Static IP configuration succeeded
V/WifiMonitor( 200): Event [Associated with fe:b9:1c:bd:82:08]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00]
V/WifiMonitor( 200): Event [CTRL-EVENT-CONNECTED - Connection to fe:b9:1c:bd:82:08 completed (reauth) [id=2 id_str=]]
I/MediaUploader( 1025): No need to wake up
V/WifiStateTracker( 200): Changing supplicant state: COMPLETED ==> ASSOCIATED
V/WifiStateTracker( 200): Changing supplicant state: ASSOCIATED ==> COMPLETED
V/WifiStateTracker( 200): New network state is CONNECTED
D/WifiWatchdogService( 200): (android.server.ServerThread) digital-n0123 (fe:b9:1c:bd:82:08) does not require the watchdog
D/DHCP ( 200): failed to set default route 192.168.1.1: File exists
V/WifiStateTracker( 200): Static IP configuration failed
V/WifiStateTracker( 200): Changing supplicant state: COMPLETED ==> ASSOCIATED
V/WifiStateTracker( 200): Changing supplicant state: ASSOCIATED ==> COMPLETED
V/WifiStateTracker( 200): New network state is CONNECTED
D/DHCP ( 200): failed to set default route 192.168.1.1: File exists
V/WifiStateTracker( 200): Static IP configuration failed
V/WifiStateTracker( 200): Changing supplicant state: COMPLETED ==> ASSOCIATED
V/WifiStateTracker( 200): IP configuration: ipaddr 192.168.1.3 gateway 192.168.1.1 netmask 255.255.255.0 dns1 8.8.8.8 dns2 0.0.0.0 DHCP server 0.0.0.0 lease 0 seconds
D/WifiWatchdogService( 200): (android.server.ServerThread) digital-n0123 (fe:b9:1c:bd:82:08) does not require the watchdog
D/Tethering( 200): MasterInitialState.processMessage what=3
V/WifiStateTracker( 200): Changing supplicant state: ASSOCIATED ==> COMPLETED
D/GTalkService( 353): ##### Network broadcast (connected=true) type=WIFI, state=CONNECTED
D/GTalkService( 353): [GTalkConnection.1] setInternalNetworkState: type=1, state=CONNECTED
V/WifiStateTracker( 200): New network state is CONNECTED
D/DHCP ( 200): failed to set default route 192.168.1.1: File exists
V/WifiStateTracker( 200): Static IP configuration failed
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=8 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=8 BSSID=00:00:00:00:00:00]
I/wpa_supplicant( 714): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
V/WifiMonitor( 200): Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00]
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00]
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 200): Changing supplicant state: COMPLETED ==> DORMANT
D/WifiStateTracker( 200): Reset connections and stopping DHCP
E/CMStats ( 1017): Got Exception
E/CMStats ( 1017): java.net.UnknownHostException: stats.cyanogenmod.com
E/CMStats ( 1017): at java.net.InetAddress.lookupHostByName(InetAddress.java:497)
E/CMStats ( 1017): at java.net.InetAddress.getAllByNameImpl(InetAddress.java:294)
E/CMStats ( 1017): at java.net.InetAddress.getAllByName(InetAddress.java:256)
E/CMStats ( 1017): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:136)
E/CMStats ( 1017): at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
E/CMStats ( 1017): at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
E/CMStats ( 1017): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:359)
E/CMStats ( 1017): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
E/CMStats ( 1017): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
E/CMStats ( 1017): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:465)
E/CMStats ( 1017): at com.cyanogenmod.stats.ReportingService.report(ReportingService.java:109)
E/CMStats ( 1017): at com.cyanogenmod.stats.ReportingService.access$000(ReportingService.java:23)
E/CMStats ( 1017): at com.cyanogenmod.stats.ReportingService$1.run(ReportingService.java:42)
D/dalvikvm( 1017): GC_CONCURRENT freed 444K, 53% free 2710K/5703K, external 0K/0K, paused 6ms+5ms
D/PicasaSyncManager( 1051): active network: NetworkInfo: type: WIFI[], state: CONNECTING/OBTAINING_IPADDR, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
I/c ( 2862): helper has already been closed and is being re-opened.
D/PicasaSyncManager( 1051): background data: true
D/Beautiful Widgets(4105)( 981): CONNECTIVITY_CHANGE
D/wifi ( 200): wifi doCommand: ret=-1
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
D/WifiStateTracker( 200): Disabling interface
I/wpa_supplicant( 712): l2_packet_receive - recvfrom: Network is down
V/WifiStateTracker( 200): New network state is DISCONNECTED
V/WifiStateTracker( 200): Changing supplicant state: DORMANT ==> DORMANT
V/WifiStateTracker( 200): Changing supplicant state: DORMANT ==> DORMANT
V/WifiStateTracker( 200): Changing supplicant state: DORMANT ==> DORMANT
W/WifiStateTracker( 200): Skip RssiApprox, not connected...
V/WifiStateTracker( 200): Changing supplicant state: DORMANT ==> SCANNING
E/ConnectivityService( 200): not failing over to mobile type 0 because Mobile Data Disabled
D/Tethering( 200): MasterInitialState.processMessage what=3
D/GTalkService( 353): ##### Network broadcast (connected=false) type=WIFI, state=DISCONNECTED
D/GTalkService( 353): [GTalkConnection.1] setInternalNetworkState: type=1, state=DISCONNECTED
D/CMStats ( 1017): CONNECTIVITY_ACTION: noConnectivity = true
I/MediaUploader( 1025): No need to wake up
D/ResourceType( 353): calling getConfigurations
D/ResourceType( 353): called getConfigurations size=265
I/wpa_supplicant( 714): Trying to associate with fe:b9:1c:bd:82:08 (SSID='digital-n0123' freq=2412 MHz)
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=fe:b9:1c:bd:82:08
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=fe:b9:1c:bd:82:08
I/wpa_supplicant( 714): Associated with 2a:cd:5e:6e:e6:e5
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 714): CTRL-EVENT-CONNECTED - Connection to 2a:cd:5e:6e:e6:e5 completed (reauth) [id=2 id_str=]
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 714): Associated with 2a:cd:5e:6e:e6:e5
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 714): CTRL-EVENT-CONNECTED - Connection to 2a:cd:5e:6e:e6:e5 completed (reauth) [id=2 id_str=]
V/WifiMonitor( 200): Event [Trying to associate with fe:b9:1c:bd:82:08 (SSID='digital-n0123' freq=2412 MHz)]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3 BSSID=fe:b9:1c:bd:82:08]
V/WifiStateTracker( 200): Changing supplicant state: SCANNING ==> ASSOCIATING
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=fe:b9:1c:bd:82:08]
V/WifiStateTracker( 200): Changing supplicant state: ASSOCIATING ==> ASSOCIATED
V/WifiMonitor( 200): Event [Associated with 2a:cd:5e:6e:e6:e5]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 200): Changing supplicant state: ASSOCIATED ==> COMPLETED
V/WifiMonitor( 200): Event [CTRL-EVENT-CONNECTED - Connection to 2a:cd:5e:6e:e6:e5 completed (reauth) [id=2 id_str=]]
V/WifiStateTracker( 200): New network state is CONNECTED
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=00:00:00:00:00:00]
V/WifiMonitor( 200): Event [Associated with 2a:cd:5e:6e:e6:e5]
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 714): Associated with fe:b9:1c:bd:82:08
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00
I/wpa_supplicant( 714): CTRL-EVENT-CONNECTED - Connection to fe:b9:1c:bd:82:08 completed (reauth) [id=2 id_str=]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00]
V/WifiMonitor( 200): Event [CTRL-EVENT-CONNECTED - Connection to 2a:cd:5e:6e:e6:e5 completed (reauth) [id=2 id_str=]]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=4 BSSID=00:00:00:00:00:00]
V/WifiMonitor( 200): Event [Associated with fe:b9:1c:bd:82:08]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=7 BSSID=00:00:00:00:00:00]
V/WifiMonitor( 200): Event [CTRL-EVENT-CONNECTED - Connection to fe:b9:1c:bd:82:08 completed (reauth) [id=2 id_str=]]
V/WifiStateTracker( 200): Static IP configuration succeeded
V/WifiStateTracker( 200): Changing supplicant state: COMPLETED ==> ASSOCIATED
V/WifiStateTracker( 200): Changing supplicant state: ASSOCIATED ==> COMPLETED
V/WifiStateTracker( 200): New network state is CONNECTED
D/WifiWatchdogService( 200): (android.server.ServerThread) digital-n0123 (fe:b9:1c:bd:82:08) does not require the watchdog
D/DHCP ( 200): failed to set default route 192.168.1.1: File exists
V/WifiStateTracker( 200): Static IP configuration failed
V/WifiStateTracker( 200): Changing supplicant state: COMPLETED ==> ASSOCIATED
V/WifiStateTracker( 200): Changing supplicant state: ASSOCIATED ==> COMPLETED
V/WifiStateTracker( 200): IP configuration: ipaddr 192.168.1.3 gateway 192.168.1.1 netmask 255.255.255.0 dns1 8.8.8.8 dns2 0.0.0.0 DHCP server 0.0.0.0 lease 0 seconds
D/WifiWatchdogService( 200): (android.server.ServerThread) digital-n0123 (fe:b9:1c:bd:82:08) does not require the watchdog
D/Tethering( 200): MasterInitialState.processMessage what=3
V/WifiStateTracker( 200): New network state is CONNECTED
D/DHCP ( 200): failed to set default route 192.168.1.1: File exists
V/WifiStateTracker( 200): Static IP configuration failed
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=2 state=8 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=2 state=8 BSSID=00:00:00:00:00:00]
I/wpa_supplicant( 714): CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys]
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00]
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00
V/WifiStateTracker( 200): Changing supplicant state: COMPLETED ==> DORMANT
D/WifiStateTracker( 200): Reset connections and stopping DHCP
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00]
I/c ( 2862): helper has already been closed and is being re-opened.
D/GTalkService( 353): ##### Network broadcast (connected=true) type=WIFI, state=CONNECTED
D/GTalkService( 353): [GTalkConnection.1] setInternalNetworkState: type=1, state=CONNECTING
D/PicasaSyncManager( 1051): active network: null
D/dalvikvm( 2862): GC_CONCURRENT freed 505K, 53% free 3409K/7111K, external 0K/0K, paused 7ms+6ms
D/PicasaSyncManager( 1051): background data: true
D/Beautiful Widgets(4105)( 981): CONNECTIVITY_CHANGE
D/CMStats ( 1017): CONNECTIVITY_ACTION: noConnectivity = false
D/CMStats ( 1017): CONNECTIVITY_ACTION: starting service
D/CMStats ( 1017): User has opted in -- reporting.
D/CMStats ( 1017): SERVICE: Device ID=1831971E0D06BD1183F51FFA963A31C5
D/CMStats ( 1017): SERVICE: Device Name=buzz
D/CMStats ( 1017): SERVICE: Device Version=CyanogenMod-7.2.0-RC3-buzz
D/CMStats ( 1017): SERVICE: Country=pl
D/CMStats ( 1017): SERVICE: Carrier=Plus
D/CMStats ( 1017): SERVICE: Carrier ID=26001
D/CMStats ( 1017): SERVICE: setting checkedin=false
I/MediaUploader( 1025): No need to wake up
E/CMStats ( 1017): Got Exception
E/CMStats ( 1017): java.net.UnknownHostException: stats.cyanogenmod.com
E/CMStats ( 1017): at java.net.InetAddress.lookupHostByName(InetAddress.java:497)
E/CMStats ( 1017): at java.net.InetAddress.getAllByNameImpl(InetAddress.java:294)
E/CMStats ( 1017): at java.net.InetAddress.getAllByName(InetAddress.java:256)
E/CMStats ( 1017): at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:136)
E/CMStats ( 1017): at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:164)
E/CMStats ( 1017): at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:119)
E/CMStats ( 1017): at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:359)
E/CMStats ( 1017): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:555)
E/CMStats ( 1017): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:487)
E/CMStats ( 1017): at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:465)
E/CMStats ( 1017): at com.cyanogenmod.stats.ReportingService.report(ReportingService.java:109)
E/CMStats ( 1017): at com.cyanogenmod.stats.ReportingService.access$000(ReportingService.java:23)
E/CMStats ( 1017): at com.cyanogenmod.stats.ReportingService$1.run(ReportingService.java:42)
I/c ( 2862): helper has already been closed and is being re-opened.
D/WifiStateTracker( 200): Disabling interface
I/wpa_supplicant( 712): l2_packet_receive - recvfrom: Network is down
V/WifiStateTracker( 200): New network state is DISCONNECTED
V/WifiStateTracker( 200): Changing supplicant state: DORMANT ==> DORMANT
V/WifiStateTracker( 200): Changing supplicant state: DORMANT ==> DORMANT
I/wpa_supplicant( 714): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiMonitor( 200): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00]
E/ConnectivityService( 200): Attempt to connect to WIFI failed.
D/DHCP ( 200): failed to set default route 192.168.1.1: File exists
V/WifiStateTracker( 200): Static IP configuration failed
Click to expand...
Click to collapse
Well, it seems like its your static IP configuration that's causing the problem. Try changing it or set it to automatic. Also, make sure your ad-hoc network is set up correctly.
Another computer don't have a problem with connecting to my ad-hoc network.
Try mhotspot or connectify.
http://mhotspot.com/index.html
http://www.connectify.me/
HTH
Only for windows i'm using Ubuntu
QkiZMR said:
Only for windows i'm using Ubuntu
Click to expand...
Click to collapse
Ooops sorry
Okay,let's try these apps
https://play.google.com/store/apps/details?id=org.wahtod.wififixer&hl=en
https://play.google.com/store/apps/details?id=org.kman.WifiManager&feature=related_apps
https://play.google.com/store/apps/details?id=com.symsoft.wififixerfree&feature=also_installed
thanks, i will test this apps

Categories

Resources