Database Info

[Solved]Wifi problem with all Motorola Android 2.3.6 rom

How can help with this problem?
Code:
Sending a DHCP renewal
D/WifiStateTracker( 2717): Disable Bluetooth co-ex mode
V/WifiStateTracker( 2717): AutoIP is disabled
D/WifiStateTracker( 2717): DhcpHandler: DHCP request started
E/wpa_supplicant(11431): ERROR - wpa_driver_tista_private_send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8000305, drv->errors = 1, errno = 95 - Operation not supported on transport endpoint)
E/wpa_supplicant(11431): ERROR - Failed to handle rx data filter command!
D/WifiStateTracker( 2717): DHCP renewal started
- wifi disconnect on some router every 5-8 min.
- no problem with the same router on Android 2.3.4
- kernel problem?
Solution for this problem
- it is a problem with android >2.3.6
- there is no fix from google
- Change lease time for IP adress at your router from unlimited to 2 weeks or 2 year or 2 month ....

Code:
--------- beginning of /dev/log/main
D/alogcat (12049): stopped
D/alogcat (12049): starting ...
--------- beginning of /dev/log/system
W/InputManagerService( 2717): Window already focused, ignoring focus gain of: [email protected]
D/RadioSignalLevel( 3382): Gsm Radio Signal level: 4
D/RadioSignalLevel( 3382): Gsm Radio Signal level: 4
W/InputManagerService( 2717): Window already focused, ignoring focus gain of: [email protected]
D/WifiStateTracker( 2717): Sending a DHCP renewal
D/WifiStateTracker( 2717): Disable Bluetooth co-ex mode
V/WifiStateTracker( 2717): AutoIP is disabled
D/WifiStateTracker( 2717): DhcpHandler: DHCP request started
E/wpa_supplicant(11431): ERROR - wpa_driver_tista_private_send - error sending Wext private IOCTL to STA driver (ioctl_cmd = 8000305, drv->errors = 1, errno = 95 - Operation not supported on transport endpoint)
E/wpa_supplicant(11431): ERROR - Failed to handle rx data filter command!
D/WifiStateTracker( 2717): DHCP renewal started
I/ActivityManager( 2717): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.motorola.blur.home/.HomeActivity } from pid 2717
V/alogcat (12049): save instance
V/alogcat (12049): paused
I/ActivityManager( 2717): No longer want com.android.settings (pid 10969): hidden #21
D/battery_widget_monitor(10800): onReceive:Intent { act=android.appwidget.action.APPWIDGET_UPDATE cmp=ccc71.bmw/.lib.bmw_widget (has extras) }
W/battery_widget_monitor(10800): total active Widgets:4
I/ActivityManager( 2717): Resumed Activity: org.jtb.alogcat/.LogActivity totalTime: 182 ms
D/alogcat (12049): stopping ...
W/InputManagerService( 2717): Starting input on non-focused client [email protected] (uid=10099 pid=12049)
D/alogcat (12049): stopped
I/EventLogService( 3514): Aggregate from 1329512002062 (log), 1329512002062 (data)
I/ActivityManager( 2717): Starting: Intent { act=com.motorola.blur.apps.ACTION_APPS flg=0x10200000 cmp=com.motorola.blur.home/com.motorola.blur.apps.AppsActivity (has extras) } from pid 3414
I/ActivityManager( 2717): Displayed com.motorola.blur.home/com.motorola.blur.apps.AppsActivity: +621ms
D/dalvikvm(12049): GC_EXPLICIT freed 902K, 64% free 3238K/8967K, external 2939K/3671K, paused 70ms
I/ActivityManager( 2717): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=org.jtb.alogcat/.LogActivity } from pid 3414
V/alogcat (12049): started
I/alogcat (12049): new intent: android.intent.action.MAIN
D/alogcat (12049): stopping ...
D/alogcat (12049): canceling periodic saves
V/alogcat (12049): resumed
D/alogcat (12049): starting ...
I/ActivityManager( 2717): Resumed Activity: org.jtb.alogcat/.LogActivity totalTime: 217 ms
W/InputManagerService( 2717): Starting input on non-focused client [email protected] (uid=10141 pid=3414)
W/KeyCharacterMap(12049): Can't open keycharmap file
W/KeyCharacterMap(12049): Error loading keycharmap file '/data/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65537.devname='qtouch-touchscreen'
W/KeyCharacterMap(12049): Can't open keycharmap file
W/KeyCharacterMap(12049): Error loading keycharmap file '/system/usr/keychars/qtouch-touchscreen.kcm.bin'. hw.keyboards.65537.devname='qtouch-touchscreen'
W/KeyCharacterMap(12049): Can't open keycharmap file
W/KeyCharacterMap(12049): Using default keymap: /system/usr/keychars/qwerty.kcm.bin

Hi,
I found this with TPLINK routers (firewalls, etc.). I think the problem is about TPLINK's DHCP server implementation. I have a TPLINK firewall since 6 month ago, and I have this bug too.
TPLINK's DHCP server deamon (and sometimes their client) has some known incompatbility with ISP's DHCP solutions.
Of course, something is changed in 2.3.6 compared to 2.3.4, because same router is perfectly work with older version.
My workaround about this is disabling DHCP: I use manual IP, or use a "wifi profiler", which turns on/off predefined Fix IP on specified WIFI SSID.
I know it is not a perfect solution in foreign places.
I tried to replace dhcp deamon, wifi drivers, wifi configuration files from 2.3.4, but no success. (I am not a linux expert, so maybe I didn't change every dependent modules, etc.)
DHCP bug is allways present, whenever I'am using open, wep and wpa/wpa2 wireless link - if same DHCP server used.
(OFF: However I have another Wifi bug on CM7/MIUI ROMs with WPA2: after some minutes or transferring a few megabytes, the connection will "stuck" - no more dataflow, I have to reconnect.)

walter79 said:
How can help with this problem?
- wifi disconnect on some router every 5-8 min.
- no problem with the same router on Android 2.3.4
- kernel problem?
Click to expand...
Click to collapse
As a Defy+ user, I'd like to report this bug to official Motorola forum. I've already reported the search bug FC in app drawer. Please tell me how to report.

LeopardSurd said:
As a Defy+ user, I'd like to report this bug to official Motorola forum. I've already reported the search bug FC in app drawer. Please tell me how to report.
Click to expand...
Click to collapse
Copy the Logfile. For me the problem can find on router from Vodafon. (Vodafon Easybox 803 and 903) This router can only buy with a DSL-contract from Vodafon in germany. Maybe it is a kernel problem. I can`t test v3 kernel from motorola. I use a Android 2.3.4 kernel. I tried all v2 gingerbread kernels.

walter79 said:
Copy the Logfile. For me the problem can find on router from Vodafon. (Vodafon Easybox 803 and 903) This router can only buy with a DSL-contract from Vodafon in germany. Maybe it is a kernel problem. I can`t test v3 kernel from motorola. I use a Android 2.3.4 kernel. I tried all v2 gingerbread kernels.
Click to expand...
Click to collapse
ok, thanks!

There is a bug report on Motorola forum:
https://forums.motorola.com/posts/6c79bca040

Any way of using CM's WiFi driver on stock ROM?
Cm7 wifi is way faster than stock!

Can someone test to change ip adress lease time from unlimited to 2 weeks. You have to change this in your router

I found this in the Motorola forums, might help.
https://forums.motorola.com/posts/6808fc89ae

cdlq456 said:
I found this in the Motorola forums, might help.
https://forums.motorola.com/posts/6808fc89ae
Click to expand...
Click to collapse
This a different problem. I think only changing router DHCP settings will work.

I have no problems w Netgear WNR1000 ( this is my router model I think) , my rom is GGL ROM - Defy Green Lens [Android 2.3.6] . WIFI is working as a charm ,it is fast (faster than on CM72 roms) and energy efficient . I used to have problems with roms 2.1 , 2.2 - never with gingerbread roms . But those problems was connected with security settings .

This wifi bug is present in all Android 2.3.6 or 3.2 builds. Samsung has this bug too.
http://code.google.com/p/android/issues/detail?id=20461
There is no fix. You can only change the ip lease time of your router from unlimited to anything else.

I will check that in my router setup .

Solution for this problem
- it is a problem with android >2.3.6
- there is no fix from google
- Change lease time for IP adress at your router from unlimited to 2 weeks or 2 year or 2 month ....

http://review.cyanogenmod.com/#change,6098
Wifi problem is a framework problem. It is fixable by edit framework.jar on each >= android 2.3.6 rom.
I will test the fix on my MS2Ginger rom.
Thanks to quarx he found the fix on cm7 review page.

I know this is an oold thread, but I think that it's importannt that there's a fix that doesn't include changing settings in any rooter:
http://chromloop.com/2011/09/how-to...roblem-wifi-connected-but-no-internet-access/
My friend just bought the Defy+ from a store, new and quite expensive and was REALLY dissapointed to find out that it crashes most(all?) wireless N routers, cause he travels a lot and connects from a lot of random rooters. Applied this easy mod(after Framaroot-ing) and all seems ok after being connected for about 30 minutes now . Hurray!!:victory:

[Q] Wireless-N not work

Have faced a problem that my HTC One S don't connect to wi-fi N access point. It stucks at authentication. If I disable N-mode at AP - the phone connects normally. Does anybody have such problem? In both cases WPA2 is used.

bump.... so no one have such problems? or no one is using wifi-n?

have you try the advanced option of wi-fi?
option ---> wi-fi ----> advanced ----> better wi-fi performance?

igooor87 said:
have you try the advanced option of wi-fi?
option ---> wi-fi ----> advanced ----> better wi-fi performance?
Click to expand...
Click to collapse
Yes, I have tried but no luck. Here is logcat:
I/wpa_supplicant( 4356): wlan0: Trying to associate with yy:yy:yy:yy:yy:yy (SSID='MY-WLAN' freq=2472 MHz)
I/wpa_supplicant( 4356): Cancelling scan request -
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): WEXT: Custom wireless event: 'BEACONIEs='
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): wlan0: Associated with yy:yy:yy:yy:yy:yy
I/wpa_supplicant( 4356): Cancelling scan request -
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
I/wpa_supplicant( 4356): [SeamLess] We are roaming state is drv->flag_roam_state is 0drv->flag_roaming is 0
I/wpa_supplicant( 4356): [SeamLess] We are roaming state is drv->flag_roam_state is 0drv->flag_disconnect_state is 0
I/wpa_supplicant( 4356): [SeamLess] Flag roam state is mlme_event_disconnect:1514
I/wpa_supplicant( 4356): [SeamLess] We are in roaming_scan_handler to register to timeout handlers
I/wpa_supplicant( 4356): [SeamLess] We requested scan to connect
I/wpa_supplicant( 4356): Setting scan request: 0 sec 0 usec
I/wpa_supplicant( 4356): wpa_supplicant_trigger_scan +
W/wpa_supplicant( 4356): [EAP-MSG] EAP [email protected]: eap_methods not available
I/wpa_supplicant( 4356): [SeamLess] This is already connected so rejected to yy:yy:yy:yy:yy:yy
I/wpa_supplicant( 4356): [SeamLess] flag_disconnect is set i.e., Seamless is give it up
I/wpa_supplicant( 4356): [SeamLess] Event DISASSOC is Generated seamless_roaming_disconnect:438
I/wpa_supplicant( 4356): wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
I/wpa_supplicant( 4356): WPA: Auto connect enabled: try to reconnect (wps=0)
I/wpa_supplicant( 4356): Setting scan request: 0 sec 500000 usec
I/wpa_supplicant( 4356): Setting scan request: 0 sec 100000 usec
I/wpa_supplicant( 4356): wlan0: CTRL-EVENT-DISCONNECTED bssid=yy:yy:yy:yy:yy:yy reason=0
I/wpa_supplicant( 4356): wpa_supplicant_set_state -
BUT, the passphase is correct. If I just turn off N-mode in access point it connects normally.

Does your router have the option for WPA+WPA2 not just one or the other? If so try enabling the setting to use both.
Sent from my HTC One S using xda premium

doktortaru said:
Does your router have the option for WPA+WPA2 not just one or the other? If so try enabling the setting to use both.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Currently I configure it to use only WPA2 (CCMP/AES cipher) but also tryed with WPA (TKIP cipher) and already tryed to use both WPA+WPA2 - no luck.
P.S.
I'm also have HTC Incredible S and it connects to AP normally in all possible modes while One S won't.

WLAN
Working fine on my Phone.. Problems with your Rom?

Andy2502 said:
Working fine on my Phone.. Problems with your Rom?
Click to expand...
Click to collapse
Have checked with 3 different roms including official. What AP do you have and which speed it suppors (150/300mbps)?

i had a similar issue but my phone would reboot after failed attempts to connect.
what is your baseband? i was on 0.15 and the phone finally connected when i used the TMOUS RUU to update to 0.16.

suhailtheboss said:
i had a similar issue but my phone would reboot after failed attempts to connect.
what is your baseband? i was on 0.15 and the phone finally connected when i used the TMOUS RUU to update to 0.16.
Click to expand...
Click to collapse
radio is 0.16.31501S.17_2_10.23.31501S.10L and the rom is 1.78.401.2, previously was on official T-Mobile DE rom, but currently on LeeDroid. With both roms wifi won't auth with AP in N-mode

Solved by compiling latest compat-wireless for AP.

darkside_ua said:
Solved by compiling latest compat-wireless for AP.
Click to expand...
Click to collapse
Hi, i have the same issue with the original ROM 1.78.401.2.
Could you please explain me how to solve this? My HTC is already rooted...
Thanks

[Q] Cyanogenmod 10 Nightly build(s) wifi issues

Hi all,
I recently purchased a SGS3 and ran the stock ROM for approx 30mins before flashing a CM10 nightly build (i9300 intl). Because of this I am unable to verify if the wifi was working on my home router prior to flashing a custom ROM.
At work I am able to connect to our wifi connection without problemson 2.4ghz or 5ghz. At home I've got a D-Link DSL-G604T wireless router which I am unable to connect to. I've tried changing the wifi channel, password, removing protection, factory reset and installed a seperate CM10 nightly build without any help.
When trying to connect to the WIFI connection I get the following output in adb logcat.
Anyone have any ideas what may be stopping me from connecting ot my wifi?
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
W/wpa_supplicant( 5841): wlan0: Failed to initiate AP scan
I/wpa_supplicant( 5841): wlan0: Trying to associate with 00:1e:58:80:a2:e2 (SSID
='HOMEWIFI' freq=2452 MHz)
D/CommandListener( 1913): Clearing all IP addresses on wlan0
I/wpa_supplicant( 5841): wlan0: Associated with 00:1e:58:80:a2:e2
I/wpa_supplicant( 5841): wlan0: Authentication with 00:1e:58:80:a2:e2 timed out.
I/wpa_supplicant( 5841): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00
reason=0
More info of my phone (kernel, build etc): i.imgur.com/PRaEx.png
Cheers

You checked "Yes this is a question"
Guess where it belongs?
Moved to Q&A
Friendly Neighborhood Moderator

[Q] Wifi won't enable?

Hello everyone,
Can somebody give me an advice related to the following issue ?
A friend of mine bought two months ago a Huawei G510 smartphone. I never ever recommend somebody to buy a Huawei, but he told me: "It's okay, you know the phones doesn't last a lot in my hands".
And again...he proved this was true. After one month he dropped the phone in a sink full of water.
He sent it to me into a bowl with rice, I opened it, cleaned it and the phone is working fine right now. But there is an issue: Wifi won't start. I factory reset the phone, I opened again to check if there is any cable disconnected...but everything is fine.
I extracted the phone catlog and this is what I get related to the wifi:
Code:
E/WifiStateMachine( 432): Failed to start supplicant!
W/CommandListener( 147): Failed to retrieve HW addr for eth0 (No such device)
E/WifiStateMachine( 432): Unable to change interface settings: java.lang.IllegalStateException: command '28 interface setcfg eth0 0.0.0.0 0 down' failed with '400 28 Failed to set address (No such device)'
W/WifiHW ( 432): wifi_start_supplicant: ath_supplicant:-ieth0 -c/data/misc/wifi/wpa_supplicant.conf start
E/wpa_supplicant( 1890): Line 3: unknown global field 'p2p_disabled=1'.
E/wpa_supplicant( 1890): Line 3: Invalid configuration line 'p2p_disabled=1'.
I/wpa_supplicant( 1890): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 1890): nl80211: Could not configure driver to use managed mode
E/wpa_supplicant( 1890): Could not read interface eth0 flags: No such device
E/wpa_supplicant( 1890): eth0: Failed to initialize driver interface
Can somebody tell me what it can be ? Is the modem roasted ? Any solution or idea ?
Thank you.

How to debug Wifi Calling?

Hi there,
I have a very strange behavior with one of my mobile phones.
Let me start by describing my setup a little bit.
I have 2 locations with 2 separate Wifis.
The first Wifi (Wifi1) is a WPA2-PEAP/MSCHAPv2 one. Here a Cisco 240AC is used as access point, a Linux firewall and a Cisco router for Dial-Up. ISP is Deutsche Telekom.
The firewall does not block any traffic to or from the mobile devices.
The second Wifi (Wifi2) is WPA2-PSK with a Fritzbox as access point and router and also Deutsche Telekom as ISP. So the ISP is the same for both locations.
I have 3 mobile phones available. Two times OnePlus and one Blackview BV9900 Pro.
All of them have a T-Mobile SIM.
The One Plus devices do Wifi Calling without any problems on Wifi1 (and probably Wifi2, but not tested).
For the Blackview device Wifi Calling is working on Wifi2.
Unfortunately the Blackview is not able to do any Wifi Calls on Wifi1.
I can see UDP-packets flowing from the Blackview phone to the T-Mobile-VoWifi-Server (109.237.187.131) with destination ports 500 and 4500 on tcpdump/wireshark.
The T-Mobile-Server is also responding with some packets. But the phone does not establish a Wifi call.
If it would be a problem with the Blackview mobile phone, I'd expect it won't work with any WIFI.
If it would be a problem with the Wifi itself, I'd expect it won't work with any device there.
Has anybody a hint how to debug that?
Thanks a lot.

Try
Code:
adb devices
adb shell "logcat -b radio | tee logcat.txt"
To stop logcat-ing press Ctrl-C

Thanks a lot @jwoegerbauer
Sorry for late reply, but I've spent the last days with comparing the logcats recorded in Wifi1 and Wifi2.
Unfortunately there are so many messages, that I get totally lost. And I could not find any error message.
Only these suspicious message appearing in Wifi1 only:
Code:
07-27 12:11:38.539 2399 2801 D RILJ : LCE capacity information received:{downlinkCapacityKbps=0, uplinkCapacityKbps=0, confidence=-1, status=-1 [SUB0]
07-27 12:11:38.539 2399 2801 D RILJ : [UNSL]< UNSOL_LCE_INFO_RECV {downlinkCapacityKbps=0, uplinkCapacityKbps=0, confidence=-1, status=-1 [SUB0]
07-27 12:12:12.377 2399 2801 D RILJ : LCE capacity information received:{downlinkCapacityKbps=25812, uplinkCapacityKbps=0, confidence=-1, status=-1 [SUB0]
07-27 12:12:12.377 2399 2801 D RILJ : [UNSL]< UNSOL_LCE_INFO_RECV {downlinkCapacityKbps=25812, uplinkCapacityKbps=0, confidence=-1, status=-1 [SUB0]
Those messages are missing in Wifi2 logcat completely.
So, I decided to change almost everything in Wifi1. I had a different Cisco access point model on spare and connected it directly to the router (with the help of a Cisco switch instead of Netgear switch).
Setup is now: (Blackview Mobile) -> (Cisco AP) -> (Cisco SW) -> (Cisco Router).
I changed also the encryption to WPA2-PSK (like in Wifi2, because I want to be sure there is no bug in Android) and also the Network mode from 802.11ac to 802.11n (also like in Wifi2).
I gave a static IP to the mobile phone via Android settings and set the DNS server to my ISP's manually.
You can say, I removed the firewall and changed everything except the router itself.
But still, Wifi Calling is not working.

After several month of investigation I found the issue.
I could not find the problem on logcat, but I used tcpdump and Wireshark to capture the traffic on my firewall.
The packets had a size of up to 1378 bytes and the "Don't fragment" bit set.
The link between firewall and router had an MTU of 1280 Bytes.
Therefore many packets got dropped at the firewall.
Increasing the MTU to 1500 Bytes solved the problem and Wifi Calling is working now.