Related
Touchpad just trying to turn wifi on without any success. I have no idea what happened. touchpad worked well for months and just lost wifi. when I boot to WebOs - wifi is working well. I tried to clean up cm9 and flash cm10 - same result.
output from catlog:
02-18 11:35:07.449 E/WifiStateMachine(350): Failed to reload STA firmware java.lang.IllegalStateException: command '40 softap fwreload wlan0 STA' failed with '400 40 Softap operation failed (No such device)'
02-18 11:35:07.459 E/WifiStateMachine(350): Unable to change interface settings: java.lang.IllegalStateException: command '42 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 42 Failed to set address (No such device)'
02-18 11:35:18.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:19.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:20.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:21.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:22.479 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:22.479 E/WifiStateMachine(350): Failed to setup control channel, restart supplicant
02-18 11:35:27.499 E/WifiStateMachine(350): Failed to reload STA firmware java.lang.IllegalStateException: command '43 softap fwreload wlan0 STA' failed with '400 43 Softap operation failed (No such device)'
02-18 11:35:27.509 E/WifiStateMachine(350): Unable to change interface settings: java.lang.IllegalStateException: command '45 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 45 Failed to set address (No such device)'
02-18 11:35:27.509 E/WifiHW (350): Unable to open connection to supplicant on "wlan0": No such file or directory
02-18 11:35:28.509 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:29.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:30.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:31.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:32.519 E/WifiHW (350): Supplicant not running, cannot connect
02-18 11:35:32.519 E/WifiStateMachine(350): Failed to setup control channel, restart supplicant
netcfg shows all interfaces down except lo.
wifi country is eu (never checked it before) and I can't change it.
You could try this; maybe it's something similar?
bananagranola said:
You could try this; maybe it's something similar?
Click to expand...
Click to collapse
no link?
Well, that's my first brain fart today. Won't be the last. http://forum.xda-developers.com/showthread.php?t=1813200
Thanks, but not. my wifi just stopped working without any updates etc.
My goodness - wrong device, wrong thread. Like I said, not the last. http://forum.xda-developers.com/showthread.php?t=1937109
No, didn't helped. wifi in webos works without any problems too.
I'm looking at dmesg and found:
board sdio wifi disable
mmc1: card 0001 removed
is it wifi card?
Sorry, then that was the limit of what I can help with. Other than a full wipe and reflash I don't know what else to try. Hopefully someone with more knowledge will show up.
More info from dmesg:
<6>[ 443.108696] CMTP-ATH6KL v4.4
<3>[ 443.108715] board_sdio_wifi_enable
<6>[ 443.114565] wifi_power(1) 1.8V sdio: set load
<6>[ 443.119068] tenderloin_wifi_power: New regulator mode for 8058_s3: 1
<6>[ 443.126264] wifi_power(1) 3.3V
<6>[ 443.126583] wifi_power(1) 8901_l1 3.3V
<6>[ 443.134761] wifi_power(1) 8058_l19 1.8V
<4>[ 443.135074] wifi_power(1) CHIP_PWD
<4>[ 443.498377] mmc1: queuing unknown CIS tuple 0x01 (3 bytes)
<4>[ 443.507770] mmc1: queuing unknown CIS tuple 0x1a (5 bytes)
<4>[ 443.511869] mmc1: queuing unknown CIS tuple 0x1b (8 bytes)
<4>[ 443.518944] mmc1: queuing unknown CIS tuple 0x14 (0 bytes)
<4>[ 443.529203] mmc1: queuing unknown CIS tuple 0x80 (1 bytes)
<4>[ 443.529474] mmc1: queuing unknown CIS tuple 0x81 (1 bytes)
<4>[ 443.541910] mmc1: queuing unknown CIS tuple 0x82 (1 bytes)
<6>[ 443.541961] mmc1: new high speed SDIO card at address 0001
<3>[ 443.598711] ath6kl: bef2fd6c
<3>[ 446.099490] ath6kl: bef2fcfc
<4>[ 446.099507] ath6kl: bef2fcdc
<6>[ 446.114969] ath6kl: bef2fbc4
<6>[ 446.114985] ath6kl: bef2fbc4
<6>[ 446.116982] ath6kl: bef2fbc4
<6>[ 446.119846] ath6kl: bef2fbc4
<6>[ 446.122747] ath6kl: bef2fbc4
<6>[ 446.125644] ath6kl: bef2fbc4
<6>[ 446.128447] ath6kl: bef2fbc4
<6>[ 446.131304] ath6kl: bef2fbc4
<6>[ 446.134207] ath6kl: bef2fbc4
<6>[ 446.137091] ath6kl: bef2fbc4
<6>[ 446.139949] ath6kl: bef2fbc4
<6>[ 446.142802] ath6kl: bef2fbc4
<6>[ 446.145628] ath6kl: bef2fbc4
<6>[ 446.148491] ath6kl: bef2fbc4
<6>[ 446.151356] ath6kl: bef2fbc4
<6>[ 446.154317] ath6kl: bef2fbc4
<6>[ 446.157094] ath6kl: bef2fbc4
<4>[ 446.160235] ath6kl: bef2fc94
<3>[ 446.163154] ath6kl: bef2fe14
<3>[ 446.166015] ath6kl: bef2fe44
<4>[ 446.168669] ath6kl_sdio: probe of mmc1:0001:1 failed with error -5
<6>[ 462.282740] adm_close port_id=0 index 0
<6>[ 478.764935] adm_close port_id=0 index 0
<3>[ 498.557702] board_sdio_wifi_disable
<6>[ 498.564551] tenderloin_wifi_power: New regulator mode for 8058_s3: 1
<6>[ 498.685586] mmc1: card 0001 removed
i dont know what cleanup cm9 + 10 means.. delete things?
uninstall?
nandroid restore and still no-go?
maybe rootzwixi knows..
goodluck
amkaos said:
i dont know what cleanup cm9 + 10 means.. delete things?
uninstall?
nandroid restore and still no-go?
maybe rootzwixi knows..
goodluck
Click to expand...
Click to collapse
format cache, sdcard, config and data from clockworkmod and then acmeuninstall. tried 3 times. Now trying to flash cm9.
this sounds impossible maybe ::
sometimes my router will not broadcast wifi but all things connected thru ethernet work fine.. or one wireless device cannot connect but others do or other connex issues..etc..
if i restart modem + router, everything connex just fine..
you didnt really give any detes about if hptp only fails on your network etc..
if you do uninstall then acme3 correctly, there is no way that HPTP wont connect to your network... unless you share some obscure hardware fubar that i never heard of..
GL
i hope you post what the outcome is and how you resolved prob.
your experience will help out someone in future time
btw, i dont wanna rub it in but when you get things going, make a nandroid backup .. make more as you tweak out your tab and safely delete prior backups... saved me many headaches..
GL
EDIT:: i see that you do connect w/ webos.. still its easy to restart router + modem..
So, new wifi driver in the new cm10 build - still no success. It's only internet browser with webos ;(
Epic 4g same thing
crea7or said:
So, new wifi driver in the new cm10 build - still no success. It's only internet browser with webos ;(
Click to expand...
Click to collapse
CM10 for 4 months no wifi issues. Suddenly the other morning wifi won't turn on. Boot to a stock image it is fine. Did you ever find a solution?
RichMichPA said:
CM10 for 4 months no wifi issues. Suddenly the other morning wifi won't turn on. Boot to a stock image it is fine. Did you ever find a solution?
Click to expand...
Click to collapse
stock image?
Multiboot utility
crea7or said:
stock image?
Click to expand...
Click to collapse
I use multi boot which lets you reboot into fc09 to add MSL etc. I just tried 9.1 ics and wifi is working.
Exactly the same problem
As yet, no fix in sight.
Wifi in WebOS is solid. I have managed to spontaneously connect a couple of times after several hours, sometimes days. I've tried reflashing several roms/updates, reformating, clearing cache and dalvik, resetting permissions. Nothing.
As long as I do not reboot, once connected the wifi is solid. My catlog shows exactly the same problems as OPs.
It may be a coincidence, but my problems seemed to begin after switching to airplane mode on a recent trip. Since then I've only managed to get the wifi up 3 times.
In settings under wifi it just says "connecting to wifi" regardless of whether the wifi button is set to "ON" or "OFF"
What bothers me, is the "not found" errors in logcat.
I'm out of ideas. If anyone can suggest a way to nail down the issue, I'm all ears. Thanks in advance!
Code:
07-24 11:37:27.209 E/WifiStateMachine(242): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
07-24 11:37:27.209 W/CommandListener(156): Failed to retrieve HW addr for wlan0 (No such device)
07-24 11:37:27.209 D/CommandListener(156): Setting iface cfg
07-24 11:37:27.209 D/NetworkManagementService(242): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
07-24 11:37:27.209 D/NetworkManagementService(242): flags <[down]>
07-24 11:37:27.219 E/WifiStateMachine(242): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg wlan0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
07-24 11:37:27.389 I/wpa_supplicant(6737): rfkill: Cannot open RFKILL control device
07-24 11:37:27.389 E/wpa_supplicant(6737): Could not read interface wlan0 flags: No such device
I'm having the same issue. WiFi works solid on webOs just when I boot into android and try to turn WiFi on, it stays stuck saying “turning on wifi" on cm9 any build and cm10 any build. I uninstalled everything at least 20 times wiped my TP clean on android and webOs(basically factory reset) wiped the cache wiped the delvik cache turned off turn on reinstall android also downloaded WiFi fixer apk and that doesn't help at all either. Everything on webOs works WiFi internet works great. Just when I go into android it stays stuck at turning on WiFi and when I reinstall cm9 or cm10 open up settings this is the only time I can switch the setting to turning on WiFi but everything is in gray with no luck just stuck saying turning on WiFi. Any help would be much appreciated! I hate webOs android is way better!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
I'm having the same issue. WiFi works solid on webOs just when I boot into android and try to turn WiFi on, it stays stuck saying “turning on wifi" on cm9 any build and cm10 any build. I uninstalled everything at least 20 times wiped my TP clean on android and webOs(basically factory reset) wiped the cache wiped the delvik cache turned off turn on reinstall android also downloaded WiFi fixer apk and that doesn't help at all either. Everything on webOs works WiFi internet works great. Just when I go into android it stays stuck at turning on WiFi and when I reinstall cm9 or cm10 open up settings this is the only time I can switch the setting to turning on WiFi but everything is in gray with no luck just stuck saying turning on WiFi. Any help would be much appreciated! I hate webOs android is way better!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
did u try doctore your TP?
After a week of being a happy Sony Xperia ZR (4.1.2, C5502) owner, my wifi stopped connecting to networks. I can't connect to any network I have tried, but the list of networks is ok. It stopped working suddenly. My previously used networks are all marked as "Saved", but when I try to connect the following happens:
1) Saved (doesn't even change when tapped)
2) Connecting -> Saved
3) Connecting -> Authentication problem -> Saved
After half day without wifi, this is what I have tried to fix it:
1) Restart phone
2) Restart phone, take out battery, SD card and SIM card
3) Restart wi-fi router
4) Connect to another network
5) Forget network -> Type password again
6) Connect another Android device to the same network
7) Connect another non-android device to the same network
8) Sony Companion -> Repair
Nothing fixed the issue, still the same problem.
Build number:
10.1.1.A.1.310
Kernel:
3.4.0-g6df7905-02327-g1aa3092
[email protected]) )
#1 SMP PREEMPT Thu Apr 11 11:17:13 2013
logcat from the time of wifi on to first failure (then it repeats the last few lines)
Code:
09-18 09:10:08.116: I/WifiManager(2391): Process ndroid.settings enabled Wifi
09-18 09:10:08.186: E/WifiHW(571): File "/data/misc/wifi/WCNSS_qcom_cfg.ini" exists, not copying
09-18 09:10:08.497: I/wpa_supplicant(3838): nl80211: Don't connect to APs with RSSI < 0
09-18 09:10:08.497: I/wpa_supplicant(3838): rfkill: Cannot open RFKILL control device
09-18 09:10:08.497: I/ActivityManager(571): No longer want com.google.android.onetimeinitializer (pid 1747): hidden #51
09-18 09:10:08.637: I/wpa_supplicant(3838): wapi_supplicant_init: Init WAI packet p2p0
09-18 09:10:08.637: I/wpa_supplicant(3838): Own MAC address: (Here's phone MAC address)
09-18 09:10:08.637: E/wpa_supplicant(3838): Initialization: WAPI:set Staues=1
09-18 09:10:08.657: E/Diag_Lib(3838): Diag_LSM_Init: Failed to open handle to diag driver, error = 13
09-18 09:10:08.757: E/wpa_supplicant(3838): QMI_UIM_EVENT_REG_REQ_V01, qmi_err_code: 0x0
09-18 09:10:08.777: E/wpa_supplicant(3838): QMI_UIM_GET_CARD_STATUS_REQ_V01, qmi_err_code: 0x0
09-18 09:10:08.777: E/wpa_supplicant(3838): card_info[i].card_state: 0x1
09-18 09:10:08.777: E/wpa_supplicant(3838): card_info[i].error_code: 0x0
09-18 09:10:08.777: E/wpa_supplicant(3838): card READY
09-18 09:10:08.777: E/wpa_supplicant(3838): card_info[i].app_type : 0x2
09-18 09:10:08.777: E/wpa_supplicant(3838): card_info[i].app_state : 0x7
09-18 09:10:08.777: E/wpa_supplicant(3838): card found
09-18 09:10:08.797: I/wpa_supplicant(3838): Reading GSM home network domain configuration file '/system/etc/wifi/gsm_domains.conf'
09-18 09:10:08.877: I/wpa_supplicant(3838): nl80211: Don't connect to APs with RSSI < -83
09-18 09:10:08.877: I/wpa_supplicant(3838): rfkill: Cannot open RFKILL control device
09-18 09:10:08.917: I/wpa_supplicant(3838): wapi_supplicant_init: Init WAI packet wlan0
09-18 09:10:08.917: I/wpa_supplicant(3838): Own MAC address: (Here's phone MAC address)
09-18 09:10:08.917: E/wpa_supplicant(3838): Initialization: WAPI:set Staues=1
09-18 09:10:08.957: E/wpa_supplicant(3838): QMI_UIM_EVENT_REG_REQ_V01, qmi_err_code: 0x0
09-18 09:10:08.977: E/wpa_supplicant(3838): QMI_UIM_GET_CARD_STATUS_REQ_V01, qmi_err_code: 0x0
09-18 09:10:08.977: E/wpa_supplicant(3838): card_info[i].card_state: 0x1
09-18 09:10:08.977: E/wpa_supplicant(3838): card_info[i].error_code: 0x0
09-18 09:10:08.977: E/wpa_supplicant(3838): card READY
09-18 09:10:08.977: E/wpa_supplicant(3838): card_info[i].app_type : 0x2
09-18 09:10:08.977: E/wpa_supplicant(3838): card_info[i].app_state : 0x7
09-18 09:10:08.977: E/wpa_supplicant(3838): card found
09-18 09:10:09.037: E/WifiConfigStore(571): Failed to look-up a string: W
09-18 09:10:09.037: E/WifiConfigStore(571): Failed to look-up a string: SMS4
09-18 09:10:09.037: E/WifiConfigStore(571): Failed to look-up a string: SMS4
09-18 09:10:09.077: I/WifiManager(2391): Process ndroid.settings requested an active scan
09-18 09:10:09.087: E/Parcel(334): Reading a NULL string not supported here.
09-18 09:10:09.087: E/Parcel(334): Reading a NULL string not supported here.
09-18 09:10:09.097: E/Parcel(334): Reading a NULL string not supported here.
09-18 09:10:09.097: I/SuperStamina-WifiAnalyzer(571): WiFi is ON.
09-18 09:10:09.117: E/wifidirect(3726): onStartCommand 1
09-18 09:10:09.117: E/wifidirect(3726): Exitting file transfer service.
09-18 09:10:09.117: W/wpa_supplicant(3838): wlan0: Failed to initiate AP scan
09-18 09:10:09.117: W/wpa_supplicant(3838): p2p0: Failed to initiate AP scan
09-18 09:10:09.127: E/wifidirect(3726): onStartCommand 1
09-18 09:10:09.127: E/wifidirect(3726): Exitting file transfer service.
09-18 09:10:10.128: W/wpa_supplicant(3838): wlan0: Failed to initiate AP scan
09-18 09:10:11.119: W/wpa_supplicant(3838): wlan0: Failed to initiate AP scan
09-18 09:10:12.130: W/wpa_supplicant(3838): wlan0: Failed to initiate AP scan
09-18 09:10:12.811: I/wpa_supplicant(3838): wlan0: Trying to associate with (here is my router MAC) (SSID='[email protected]' freq=2427 MHz)
09-18 09:10:14.023: I/wpa_supplicant(3838): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=(here is my router MAC) status_code=1
09-18 09:10:19.088: I/WifiManager(2391): Process ndroid.settings requested an active scan
09-18 09:10:22.812: I/wpa_supplicant(3838): wlan0: Authentication with (here is router MAC) timed out.
Repeat:
09-18 09:10:12.811: I/wpa_supplicant(3838): wlan0: Trying to associate with (here is my router MAC) (SSID='[email protected]' freq=2427 MHz)
09-18 09:10:14.023: I/wpa_supplicant(3838): wlan0: CTRL-EVENT-ASSOC-REJECT bssid=(here is my router MAC) status_code=1
09-18 09:10:22.812: I/wpa_supplicant(3838): wlan0: Authentication with (here is router MAC) timed out.
Any ideas? How to diagnose more, is it HW or SW? I am going to call to support but I know they are just going to guide me through: "Have you tried turning it on and off again?" questions and then recommend sending the phone back to them...
Reset your router settings.. flash your phone using SEUS. If not working after that too.. reinstall once more patiently.. It worked for me
vasantv said:
Reset your router settings.. flash your phone using SEUS. If not working after that too.. reinstall once more patiently.. It worked for me
Click to expand...
Click to collapse
I did factory reset of everything. Still not working. I think the key is why is wpa_supplicant getting: "CTRL-EVENT-ASSOC-REJECT" from the router and why it was working last week (with no changes at all).
kulisgames said:
I did factory reset of everything. Still not working. I think the key is why is wpa_supplicant getting: "CTRL-EVENT-ASSOC-REJECT" from the router and why it was working last week (with no changes at all).
Click to expand...
Click to collapse
I have tried this in another office where there are three wi-fi routers. All three have the same problem: CTRL-EVENT-ASSOC-REJECT. But one of them works sometimes...
Can you try to disable all power saving plans and reboot your phone. See if it fixed. I've fix the wifi keep droping by disable power saving plans
Sent from my SO-04E using XDA Premium 4 mobile app
GavinLiu said:
Can you try to disable all power saving plans and reboot your phone. See if it fixed. I've fix the wifi keep droping by disable power saving plans
Sent from my SO-04E using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I went to the service centre and it is HW problem. Now waiting for them to replace it. :good:
That is good news.
Sent from my SO-04E using XDA Premium 4 mobile app
Hi there. Just got my Gear Live today from Google Play(ordered on 14 July), firmware build is KKV81. When I try to update the firmware from the settings it just says "Something went wrong". Has anyone encountered the same problem? Any ideas how to fix this? I suppose my other option is to update the firmware via adb as described here: http://forum.xda-developers.com/showthread.php?t=2797501, but some steps are not detailed enough so I would like to try something less dangerous first.
Thanks in advance.
apan1982 said:
Hi there. Just got my Gear Live today from Google Play(ordered on 14 July), firmware build is KKV81. When I try to update the firmware from the settings it just says "Something went wrong". Has anyone encountered the same problem? Any ideas how to fix this? I suppose my other option is to update the firmware via adb as described here: http://forum.xda-developers.com/showthread.php?t=2797501, but some steps are not detailed enough so I would like to try something less dangerous first.
Thanks in advance.
Click to expand...
Click to collapse
The same situation!
My firmware build is KKV81, same as yours, and also can't update with OTA to the latest version
And this is in logcat output, while trying to update:
Code:
08-07 20:06:40.620 606-606/? I/SystemUpdateService﹕ onCreate
08-07 20:06:41.660 454-569/? I/ActivityManager﹕ START u0 {act=android.settings.SYSTEM_UPDATE_SETTINGS cmp=com.google.android.gms/.update.SystemUpdateWearableActivity} from pid 619 on display 0
08-07 20:06:41.720 606-606/? D/SystemUpdateActivity﹕ status=6 mobile=false batteryState=0 roaming=false lastCheckinTime=1407349343493 mSetupWizard=false
08-07 20:06:41.780 454-474/? I/ActivityManager﹕ Displayed com.google.android.gms/.update.SystemUpdateWearableActivity: +105ms
08-07 20:06:42.000 662-682/? W/bt-btif﹕ dm_pm_timer expires
08-07 20:06:42.000 662-682/? W/bt-btif﹕ dm_pm_timer expires 0
08-07 20:06:42.000 662-682/? W/bt-btif﹕ proc dm_pm_timer expires
08-07 20:06:43.620 606-606/? I/SystemUpdateService﹕ onCreate
08-07 20:06:43.650 606-1692/? I/SystemUpdateService﹕ network: NetworkInfo: type: PROXY[], state: CONNECTED/CONNECTED, reason: enabled, extra: (none), roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false; metered: false; mobile allowed: true
08-07 20:06:43.650 606-1692/? I/DownloadAttempt﹕ current file is null
08-07 20:06:43.650 606-1692/? I/DownloadAttempt﹕ mSize -1 mDownloaded -1
08-07 20:06:43.650 606-1692/? I/SystemUpdateService﹕ status is 1 (ready)
08-07 20:06:43.650 606-1692/? I/SystemUpdateService﹕ starting download of http://android.clients.google.com/packages/ota/global_samsung_sprat/9463bb9866a01116311155b89e4aae4c436db98c.signed-sprat-KMV78Y-from-KKV81.9463bb98.zip
08-07 20:06:43.660 606-606/? D/SystemUpdateActivity﹕ status=2 mobile=false batteryState=0 roaming=false lastCheckinTime=1407349343493 mSetupWizard=false
08-07 20:06:43.660 606-1692/? I/SystemUpdateService﹕ now status is 2 (in_progress)
08-07 20:06:43.670 606-1693/? I/DownloadAttempt﹕ querying downloadmanager
08-07 20:06:43.690 606-1693/? I/DownloadAttempt﹕ mUrl is http://android.clients.google.com/packages/ota/global_samsung_sprat/9463bb9866a01116311155b89e4aae4c436db98c.signed-sprat-KMV78Y-from-KKV81.9463bb98.zip
08-07 20:06:43.700 606-1693/? I/DownloadAttempt﹕ including auth header <AUTH_HEADER_HEAR>...
08-07 20:06:43.710 606-1694/? I/SystemUpdateService﹕ network: NetworkInfo: type: PROXY[], state: CONNECTED/CONNECTED, reason: enabled, extra: (none), roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false; metered: false; mobile allowed: true
08-07 20:06:43.710 606-1694/? I/SystemUpdateService﹕ now status is 2 (in_progress)
08-07 20:06:44.690 168-169/? E/clockwork_proxy_native﹕ Cannot find uid for tcp connection from 192.168.167.239:44849 to 212.0.195.142:80
08-07 20:06:44.690 1378-1453/? D/ClockworkProxy﹕ TCP connection requested by uid=-1
08-07 20:06:44.690 1378-1453/? D/ClockworkProxy﹕ TCP connection is not from a google app, closing it...
08-07 20:06:44.700 606-1693/? I/DownloadAttempt﹕ caught ioexception
java.io.EOFException
at com.android.okhttp.internal.Util.readAsciiLine(Util.java:342)
at com.android.okhttp.internal.http.RawHeaders.fromBytes(RawHeaders.java:311)
at com.android.okhttp.internal.http.HttpTransport.readResponseHeaders(HttpTransport.java:135)
at com.android.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:644)
at com.android.okhttp.internal.http.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:353)
at com.android.okhttp.internal.http.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:297)
at com.android.okhttp.internal.http.HttpURLConnectionImpl.getResponseCode(HttpURLConnectionImpl.java:509)
at apc.b(SourceFile:328)
at apc.doInBackground(SourceFile:44)
at android.os.AsyncTask$2.call(AsyncTask.java:288)
at java.util.concurrent.FutureTask.run(FutureTask.java:237)
at java.lang.Thread.run(Thread.java:841)
08-07 20:06:44.710 606-1697/? I/SystemUpdateService﹕ network: NetworkInfo: type: PROXY[], state: CONNECTED/CONNECTED, reason: enabled, extra: (none), roaming: false, failover: false, isAvailable: true, isConnectedToProvisioningNetwork: false; metered: false; mobile allowed: true
08-07 20:06:44.710 606-1697/? I/SystemUpdateService﹕ now status is 5 (failed)
08-07 20:06:44.730 606-606/? D/SystemUpdateActivity﹕ status=6 mobile=false batteryState=0 roaming=false lastCheckinTime=1407349343493 mSetupWizard=false
08-07 20:06:44.730 606-1697/? I/SystemUpdateService﹕ download failed; clearing attempt
08-07 20:06:44.750 606-610/? D/dalvikvm﹕ GC_CONCURRENT freed 298K, 9% free 6140K/6724K, paused 3ms+11ms, total 41ms
08-07 20:06:44.760 606-1697/? V/SystemUpdateService﹕ retry (wakeup: true) in 19969 ms
08-07 20:06:49.230 454-483/? I/PowerManagerService﹕ Going to sleep by user request...
And the most interested part of this log is that:
Code:
08-07 20:06:44.690 168-169/? E/clockwork_proxy_native﹕ Cannot find uid for tcp connection from 192.168.167.239:44849 to 212.0.195.142:80
08-07 20:06:44.690 1378-1453/? D/ClockworkProxy﹕ TCP connection requested by uid=-1
08-07 20:06:44.690 1378-1453/? D/ClockworkProxy﹕ TCP connection is not from a google app, closing it...
I can say only that I do not like this very much... not sure if it can be fixed... Anyone has ideas how to proceed with OTA?
I wonder if this is the same issue people are having over on the G watch forums..theres something wrong with the size of the OTA and the watch not having enough storage
Finally, I was able to update the watch. This error persisted while I was staying in 3g-zone of local operator - Unite (Moldova). (I tried both - sharing 3g connection from the Android phone and sharing 3g connection from router, in both cases update was failed with stacktrace above). As soon as I moved home to the fixed ethernet network I was able to proceed with update. In the same time, it was quite hard to proceed with installing update after it was actually downloaded. The "yes" button in the prompt "Do I want to install update" was clickable, but there happened nothing on click. Finally, after restarting and unknown action from me I was able to make update. I am happy now.
So, try to move to other provider and try to update there.
Also got the update by resetting my gear live...
Sent from my SM-G900W8 using Tapatalk
I have been running the unofficial CM 12.1 release from April on my Tab S2 T-810 since that date.
The tablet has been fine - outside the limitations by that release - this morning, however, I found that I had lost WiFi access and have not been able to restore it. I have not downloaded any program updates, nor updated the system, and this seems to have happened overnight. The tablet had not turned off and showed 71% battery this morning. Rebooting the tablet has no effect. I am loath to reinstall CM since I will lose some of the information related to my setup.
Can this be a software bug? Is there another way of turning WiFi on besides through the CM settings such as using the command line in a terminal window? Any attempt to turn WiFi on in settings only results in "turning WiFi on..." displayed with no further activity. My tablet is rooted. By the way, Bluetooth seems to work.
@T_I
Hmm, how do I interpret your reply?
hga89 said:
Hmm, how do I interpret your reply?
Click to expand...
Click to collapse
Well this would have been a better question to ask in the CM thread.
Try CM13?
Lightn1ng said:
Well this would have been a better question to ask in the CM thread.
Try CM13?
Click to expand...
Click to collapse
I eventually first installed MM 6.0 and then CM 13.0 but WiFi cannot be turned on, then reverting to MM 6.0 to see if WiFi worked there but no luck.
Looks like a hardware problem but has anyone else encountered WiFi suddenly dying completely?
The warranty period is one year and I had had the tablet for almost exactly six months when this happened. Since I have both rooted the tablet and installed another ROM, initially CM 12, it seems it will not be covered?
Does anyone have experience getting warranty repairs on a rooted tablet?
hga89 said:
I eventually first installed MM 6.0 and then CM 13.0 but WiFi cannot be turned on, then reverting to MM 6.0 to see if WiFi worked there but no luck.
Looks like a hardware problem but has anyone else encountered WiFi suddenly dying completely?
The warranty period is one year and I had had the tablet for almost exactly six months when this happened. Since I have both rooted the tablet and installed another ROM, initially CM 12, it seems it will not be covered?
Does anyone have experience getting warranty repairs on a rooted tablet?
Click to expand...
Click to collapse
You might want to check with the dev of the cm13 ROM for the T810. He recently had a warrantee repair on his S2 with knox tripped. You can PM him here.
lewmur said:
You might want to check with the dev of the cm13 ROM for the T810. He recently had a warrantee repair on his S2 with knox tripped. You can PM him here.
Click to expand...
Click to collapse
Thank you, just did that. Samsung quoted me 9-11 days turnaround time for the repair of the WiFi...
I have the same problem, WIFI cannot be turned on
xyandxl said:
I have the same problem, WIFI cannot be turned on
Click to expand...
Click to collapse
Interesting. I have the T810, how about you? Are you on CM?
I spent almost one hour with a Samsung technician yesterday doing the following: force-stopping the two WiFi applications; booting into the recovery partition and wiping the cache; booting into safe mode and finally rebooting my own router on the technician's request. The latter, of course, had no bearing on the problem. The technician had not heard of this problem before.
None of the above worked and just to make sure this was not a CM problem I had - prior to contacting Samsung support - reinstalled stock 6.0 on the unit but it behaved no different.
A command-line tool to run on the unit to find the exact error code would be very helpful.
hga89 said:
Interesting. I have the T810, how about you? Are you on CM?
I spent almost one hour with a Samsung technician yesterday doing the following: force-stopping the two WiFi applications; booting into the recovery partition and wiping the cache; booting into safe mode and finally rebooting my own router on the technician's request. The latter, of course, had no bearing on the problem. The technician had not heard of this problem before.
None of the above worked and just to make sure this was not a CM problem I had - prior to contacting Samsung support - reinstalled stock 6.0 on the unit but it behaved no different.
A command-line tool to run on the unit to find the exact error code would be very helpful.
Click to expand...
Click to collapse
In response to another post I made, Ashyx suggested downloading syslog to check the logs. I will do so. Would be interesting if you could do the same.
Here are the mentions I could find of wifi in the logs using syslog. wifi could be found in last_kmsg.log, logcat.log and eventl.log. I am not used to reading android logs but in last_kmsg.log between lines 399 and 416 a Broadcom Dongle Host Driver is being initialized.
Ideas anyone? I should add that the below is when booting CM 13.
last_kmsg.log:397: [ 2.682373] ## wifi_probe
last_kmsg.log:398: [ 2.682586] wifi_set_power = 1
last_kmsg.log:399: [ 3.202178] wifi_set_carddetect = 1
last_kmsg.log:416: [ 3.378906] wifi_set_power = 0
logcat.log:2080: 08-10 12:57:53.610 I/acvpnagent(16328): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
logcat.log:4854: 08-10 13:00:08.532 I/acvpnagent(17178): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
event.log:360: 08-10 12:53:44.899 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848024710]
event.log:752: 08-10 12:55:47.258 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848147075]
event.log:1379: 08-10 12:58:13.172 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848293002]
Found 9 matches for "wifi".
hga89 said:
Here are the mentions I could find of wifi in the logs using syslog. wifi could be found in last_kmsg.log, logcat.log and eventl.log. I am not used to reading android logs but in last_kmsg.log between lines 399 and 416 a Broadcom Dongle Host Driver is being initialized.
Ideas anyone? I should add that the below is when booting CM 13.
last_kmsg.log:397: [ 2.682373] ## wifi_probe
last_kmsg.log:398: [ 2.682586] wifi_set_power = 1
last_kmsg.log:399: [ 3.202178] wifi_set_carddetect = 1
last_kmsg.log:416: [ 3.378906] wifi_set_power = 0
logcat.log:2080: 08-10 12:57:53.610 I/acvpnagent(16328): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
logcat.log:4854: 08-10 13:00:08.532 I/acvpnagent(17178): Function: OnNetworkChange File: AndroidSNAKSystem.cpp Line: 262 Network Change Message: No Connectivity: 0 Is Failover: 0 NetworkInfo: NetworkInfo: Type: Mobile Coarse State: Connected Detailed State: Connected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Wifi Coarse State: Disconnected Detailed State: Disconnected Is Available: 1 Is FailOver: 0 Is FailOver: 0 NetworkInfo: NetworkInfo: Type: Ethernet Coarse State: Unknown Detailed State: Idle Is Available: 0 Is FailOver: 1 Is FailOver: 1
event.log:360: 08-10 12:53:44.899 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848024710]
event.log:752: 08-10 12:55:47.258 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848147075]
event.log:1379: 08-10 12:58:13.172 I/netstats_wifi_sample( 414): [849210724,1868292,2286635822,2470712,844926737,1814474,2248078123,2475581,844926737,1814474,2247907129,2474148,1470848293002]
Found 9 matches for "wifi".
Click to expand...
Click to collapse
Did a further analysis of the various logs. I cannot find any messages tagged error or warning but it seems the Broadcom Dongle Host Driver is able to retrieve a MAC address for the WiFi card immediately followed by:
last_kmsg.log:416: [ 3.378906] wifi_set_power = 0
Any suggestions?
Please don't paste logs in posts.
Use Pastebin.com or upload the logs to Tinyupload.com.
If you upload them I can take a look.
Also you should be running complete stock.
Is your IMEI intact?
ashyx said:
Please don't paste logs in posts.
Use Pastebin.com or upload the logs to Tinyupload.com.
If you upload them I can take a look.
Also you should be running complete stock.
Is your IMEI intact?
Click to expand...
Click to collapse
Than you ashyx. I have now downloaded the zipped logs to http://s000.tinyupload.com/index.php?file_id=38641397716294966079. This is with CM 13 since I need root access to access the logs.
I cannot find an IMEI listing - or any in the About tablet and Status section where it is on my phone. Note that this is a Wifi-only tablet, T-810. On my phone I do have several fields with IMEI, IMEISV, and (cellular) network info, not so on the tablet, only the IP address (unavailable) and MAC address (all zeroes).
Note that I lost Wifi overnight without having installed any system update or any new software at all, it was just not connecting one morning...
hga89 said:
Than you ashyx. I have now downloaded the zipped logs to http://s000.tinyupload.com/index.php?file_id=38641397716294966079. This is with CM 13 since I need root access to access the logs.
I cannot find an IMEI listing - or any in the About tablet and Status section where it is on my phone. Note that this is a Wifi-only tablet, T-810. On my phone I do have several fields with IMEI, IMEISV, and (cellular) network info, not so on the tablet, only the IP address (unavailable) and MAC address (all zeroes).
Note that I lost Wifi overnight without having installed any system update or any new software at all, it was just not connecting one morning...
Click to expand...
Click to collapse
You should really go back to full stock firmware and then pull the logs.
No point trying to track down an issue that is caused by a custom OS.
ashyx said:
You should really go back to full stock firmware and then pull the logs.
No point trying to track down an issue that is caused by a custom OS.
Click to expand...
Click to collapse
OK, will do that and get the logs after rooting.
Before doing so today, I am, however, restoring the latest of the two nandroid backups I have to see if I can get the service back.
hga89 said:
OK, will do that and get the logs after rooting.
Before doing so today, I am, however, restoring the latest of the two nandroid backups I have to see if I can get the service back.
Click to expand...
Click to collapse
Just restored the latest of the two nandroid backups, which included restoring EFS and RADIO partitions. This backup was done /after/ I encountered the Wifi-issue. Restore went fine but no Wifi, I also see that I now have an IMEI field in Phone Settings/Status but that the field is blank.
I believe I have another nandroid from a long time ago when everything was working fine and I will figure out how to get that to the tablet and try a restore.
hga89 said:
Just restored the latest of the two nandroid backups, which included restoring EFS and RADIO partitions. This backup was done /after/ I encountered the Wifi-issue. Restore went fine but no Wifi, I also see that I now have an IMEI field in Phone Settings/Status but that the field is blank.
I believe I have another nandroid from a long time ago when everything was working fine and I will figure out how to get that to the tablet and try a restore.
Click to expand...
Click to collapse
The 2 are tied together. No IMEI usually means an EFS issue and therefore wifi and radio issues.
You really need that backup of the EFS.
ashyx said:
The 2 are tied together. No IMEI usually means an EFS issue and therefore wifi and radio issues.
You really need that backup of the EFS.
Click to expand...
Click to collapse
Just restored a nandroid backup I had made immediately after buying the tablet (Android 5) but restoring it, including the EFS and RADIO partitions did not restore Wifi-connectivity. I also tried "factory reset" from the OS but that also did not help.
I have now uploaded a syslog archive to http://s000.tinyupload.com/index.php?file_id=25506746479682944901.
Ashyx, thank you for looking at them.
Yesterday I used Odin to restore the nandroid backup I made before I rooted and installing a ROM. However, the Wifi problem persists, it cannot be turned on. Not sure the settings in Odin were correct: I used AP to restore and left the Auto-reboot and F. Reset Time checked which was the default. Was this correct?
I am using Odin 3.10.7 since I have to do this from a netbook running Vista Home and have no other Windows computer available. Does this make a difference?
Thank you.
Hi All,
Need some help in getting my wifi and bluetooth back to normal. It's over a month now and all my attempts have failed! I would really appreciate some ideas here. Thank you, and sorry for long thread.
Phone info:
Samsung galaxy S6 SM-G920T (T-Mobile), firmware version: NRD90M.G920TUVS6FRC1, stock OS with root and TWRP recovery
Situation:
Bluetooth does not turn ON at all
Wifi takes a long time to turn ON, and only way to turn it ON is from settings (quick access tile does not work)
Wifi does not remember any password
All other functions work correctly, and the phone is now lightning fast after factory reset
Details and Steps Taken:
Rooted my phone a month ago, and started changing config. Took OS and app backup only, but no EFS/other partition backup.
Turned OFF "Allow OEM Unlock" - don't ask why
This (I believe) resulted in WIFI not remembering passwords, so after reviewing potential solutions, I changed "Secure.Storage" value in build.prop to "0"
Took backup of WPA_supplicant.conf and deleted the file
Problem was not resolved, and I had to restart the phone
Restart resulted in FRP lock - to resolve this I re-installed the OS from stock firmware from Sammobile; Yet - no luck on wifi and bluetooth, error still persisted
I reviewed the system log and found tons of errors (listed below). Based on errors, I tried:
Copying libbluetooth_jni.so library file to '/system/lib' and '/system/vendor/lib' folders
Changing 'semGetAllowBluetoothMode' value to "True" - this reduced some errors (refer below)
Validating file / folder permissions for the /efs partition - they seem to be appropriate, but I cannot confirm since there is no reference
I have also tried using SmartSwitch - but it doesn't recognize phone in download mode. It backups the apps, etc. though
Also wiped the system partition once using TWRP, and re-imaged. Yet no luck.
My hunch currently for these errors is:
The /efs permissions became incorrect or partition became corrupt due to some configuration I performed
The system lost its encryption key when the "OEM unlock" was disabled, and thus cannot read any files from the /system and /efs partition (the device was NOT encrypted, but I am thinking /efs is always encrypted by system - correct me if I am wrong)
System log snippets:
Bluetooth Related Log:
Bluetooth GATT service:
Code:
BtGatt.GattService: [GSIM LOG]: gsimLogHandler: null, msg: MESSAGE_LOAD_PREF
Bluetooth Adapter Service:
Code:
BluetoothAdapterService: onProfileServiceStateChanged() serviceName=com.android.bluetooth.gatt.GattService, state=12, Message sending
semGetAllowBluetoothMode:
Resolved this error by updating the value to "True" in build.prop. Was this the right fix, or is it supposed to get value = 2.
Code:
DevicePolicyManagerService: semGetAllowBluetoothMode - value retunrs : 2
Wifi error log:
Code:
WifiHW : ##################### set firmware type 0 #####################
WifiHW : ==========[WIFI] SEMCO MODULE ===========
WifiHW : TEMP_FAILURE_RETRY complete
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 208 Softap operation succeeded
WifiMonitor: killSupplicant p2ptrue init.svc.wpa_supplicant=unknown init.svc.p2p_supplicant=unknown
WifiHW : supplicant_name : p2p_supplicant
WifiHW : Unable to open connection to supplicant on "@android:wpa_wlan0": No such file or directory
WifiWatchdogStateMachine: Unhandled message { when=0 what=135173 arg1=2 target=com.android.internal.util.StateMachine$SmHandler } in state NotConnectedState
WifiMonitor: startMonitoring(wlan0) failed!
WifiStateMachine: Failed to setup control channel, restart supplicant
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 0
WifiHAL : wifi_cleanup: Read after POLL returned 4, error no = 2
WifiHAL : Event processing terminated
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 219 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 229 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 240 Softap operation succeeded
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 248 Softap operation succeeded
WifiHAL : wifi_event_loop: Read after POLL returned 4, error no = 11
NetworkManagement: wifiFirmwareReload Error reloading wlan0 fw in STA mode: event = 200 256 Softap operation succeeded
WifiStateMachine: Failed 6 times to start supplicant, unload driver
WifiStateMachine: sendErrorBroadcast code:10
WifiController: WifiControllerWifi turn on failed