FORUMS
Remove All Ads from XDA

[ISSUE] TouchPad Android Wifi Issue Thread

257 posts
Thanks Meter: 107
 
By bobtidey, Senior Member on 13th February 2012, 12:55 AM
Post Reply Email Thread
19th November 2013, 01:47 AM |#271  
Member
Thanks Meter: 0
 
More
Unhappy ath6kl driver crashes on boot
I've carefully read all 27 pages of this thread and apart from seliger I haven't come across anyone who has a problem similar to mine.
The TP used to work fine. I switched to airplane mode several months back and that's when the problems started. I now have a Touchpad that will not connect. The driver actually crashes during bootup and the wifi button is greyed out (you can slide the button to "on" but then it flicks back to "off" after a couple of minutes.)

I've tried:
Deleting the wifi profile
Browsing in WebOS and then switching back to cyanogenmod
Changing my router channel
Recycling the router
Deleting the android partition and starting again from scratch
Updated the ath6kl driver with the one jsullins uploaded in July

Backups that I have on the sd partition that used to work, now don't.
I've tried lots of cyanogenmod roms, CM7, CM9, CM10, alphas and nightlies (ones that I know used to work).

dmsg:
ath6kl: temporary war to avoid sdio crc error
ath6kl: firmware crashed
ath6kl: crash dump:

logcat:
E/WifiHW (239): Supplicant not running, cannot connect
E/WifiStateMachine(239): Failed to setup control channel, restart supplicant
E/WifiStateMachine(239): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
W/CommandListener(155): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener(155): Setting iface cfg
D/NetworkManagementService(239): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService(239): flags <[down]>
E/WifiStateMachine(239): 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)}
I/wpa_supplicant(2313): rfkill: Cannot open RFKILL control device
E/wpa_supplicant(2313): Could not read interface wlan0 flags: No such device
E/wpa_supplicant(2313): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant(2313): wlan0: Failed to initialize driver interface

dmsg and logcat detailed in the posts below
http://forum.xda-developers.com/show....php?t=2458470
https://code.google.com/p/cmtouchpad...ort=-id%20type

Wifi still works fine in WebOS (never had a problem).
 
 
20th November 2013, 02:33 PM |#272  
daedric's Avatar
Senior Member
Flag Porto
Thanks Meter: 417
 
More
Does Wifi work on WebOS?
20th November 2013, 05:46 PM |#273  
Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by daedric

Does Wifi work on WebOS?

Quote:

Wifi still works fine in WebOS (never had a problem).

2chars
20th November 2013, 05:51 PM |#274  
daedric's Avatar
Senior Member
Flag Porto
Thanks Meter: 417
 
More
How about starting over? ACMEunistall, and ACMEinstall4 or 5 ?
21st November 2013, 06:40 AM |#275  
Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by daedric

How about starting over? ACMEunistall, and ACMEinstall4 or 5 ?

As stated, I've already deleted the partition and started again from scratch.
22nd November 2013, 07:08 PM |#276  
Member
Thanks Meter: 13
 
More
My wifi turns itself off during sleep and even though it says its connect I am able to access the web or connect to the play store. I have made sure that the option to stay connect while sleeping is on. I just did a completed wipe and loaded Invisiblek's 11/21/2013 nightly 10.2 build. It works find in WebOS and has worked find under other ROMs. Just curious if anyone has a workaround/fix for this issue. From what I have read wifi should be working fine with this ROM.


EDIT: I loaded the Evervolv AOSP 4.3.1 ROM and experience the same issues.
8th December 2013, 10:51 AM |#277  
Senior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by Joltrast

I've carefully read all 27 pages of this thread and apart from seliger I haven't come across anyone who has a problem similar to mine.
The TP used to work fine. I switched to airplane mode several months back and that's when the problems started. I now have a Touchpad that will not connect. The driver actually crashes during bootup and the wifi button is greyed out (you can slide the button to "on" but then it flicks back to "off" after a couple of minutes.)

I've tried:
Deleting the wifi profile
Browsing in WebOS and then switching back to cyanogenmod
Changing my router channel
Recycling the router
Deleting the android partition and starting again from scratch
Updated the ath6kl driver with the one jsullins uploaded in July

Backups that I have on the sd partition that used to work, now don't.
I've tried lots of cyanogenmod roms, CM7, CM9, CM10, alphas and nightlies (ones that I know used to work).

dmsg:
ath6kl: temporary war to avoid sdio crc error
ath6kl: firmware crashed
ath6kl: crash dump:

logcat:
E/WifiHW (239): Supplicant not running, cannot connect
E/WifiStateMachine(239): Failed to setup control channel, restart supplicant
E/WifiStateMachine(239): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
W/CommandListener(155): Failed to retrieve HW addr for wlan0 (No such device)
D/CommandListener(155): Setting iface cfg
D/NetworkManagementService(239): rsp <213 00:00:00:00:00:00 0.0.0.0 0 [down]>
D/NetworkManagementService(239): flags <[down]>
E/WifiStateMachine(239): 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)}
I/wpa_supplicant(2313): rfkill: Cannot open RFKILL control device
E/wpa_supplicant(2313): Could not read interface wlan0 flags: No such device
E/wpa_supplicant(2313): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant(2313): wlan0: Failed to initialize driver interface

dmsg and logcat detailed in the posts below
http://forum.xda-developers.com/show....php?t=2458470
https://code.google.com/p/cmtouchpad...ort=-id%20type

Wifi still works fine in WebOS (never had a problem).

I have the exact same issue, wifi still works fine in webos but the drivers acting up on any android build.

In the debug log connected to the PC i get-

12-08 10:48:09.719 400-1530/system_process E/WifiStateMachine´╣Ľ Failed to load driver!
12-08 10:48:09.769 400-455/system_process E/WifiStateMachine´╣Ľ DriverFailedState
27th December 2013, 06:26 PM |#278  
Member
Thanks Meter: 1
 
More
I have the final CWM in my hp touchpad

My wifi is terrible.

it works about 10% of the time.

any drivers or something i can do to improve?

thanks
7th September 2016, 02:40 AM |#279  
Member
Thanks Meter: 2
 
Donate to Me
More
Quote:
Originally Posted by daedric

How about starting over? ACMEunistall, and ACMEinstall4 or 5 ?

Hi I'm not sure how do the ACME unistall and reinstall.. Can you walk me through it.?
12th September 2016, 10:45 PM |#280  
Member
Thanks Meter: 0
 
More
I just recently started having a problem on CM9 (don't have any other information anymore as I tried updating with jc's latest CM11) and thought updating to CM11 would fix things. Well, same problem, unfortunately. Any fixes on this? Any time I try to connect to a wireless network it looks as though it might and ends up saying "disabled" under the network name.
7th October 2016, 02:52 PM |#281  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by adriankeith

I just recently started having a problem on CM9 (don't have any other information anymore as I tried updating with jc's latest CM11) and thought updating to CM11 would fix things. Well, same problem, unfortunately. Any fixes on this? Any time I try to connect to a wireless network it looks as though it might and ends up saying "disabled" under the network name.

So, it has been awhile since I've been to this site and I thought I'd check in to see if there was progress on a Nougat install and, more importantly, a solution to the Wi-Fi card being disabled that many of us are seeing. To give a bit of history, I have a 32 GB Touchpad that I bought on firesale in 2011. The Wi-Fi card works great in webOS, but obviously with no future for webOS, I decided to load Android on my Touchpad in a dual load with webOS. Originally, I loaded one of the CM loads of Android 4. Wi-Fi initially worked great. One day, out of the blue, it just stopped working. I thought maybe the card had died, so I booted into webOS and sure enough, Wi-Fi had no issues. I've been searching for a solution to this issue for years - I've tried loading 4.3, 4.4, 5.x, and I believe even 6.x and nothing has ever solved the problem. I've since blown webOS away but I'm confident that if I reload it, Wi-Fi would work great.

My symptoms are the same as yours - if I go into settings and enable Wi-Fi, it spins for awhile and then disables it. I really have no idea what's going on. It isn't like I want to use this tablet as a daily driver or anything, but I'd like to use it as a home automation controller/dashboard mounted on a wall and for that to happen, I need Wi-Fi to work in Android. It doesn't appear that the issue has ever really been resolved. At this stage, I'm even willing to send my Touchpad into a developer for testing/troubleshooting so the problem would hopefully be resolved once and for all. I suspect that some of us have a slightly different revision of the Wi-Fi card in our Touchpads, but I can't be sure and who knows - maybe a developer already knows that exact issue but can't fix it.
Post Reply Subscribe to Thread

Tags
touchpad, wifi

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes