[ISSUE] TouchPad Android Wifi Issue Thread

Search This thread

seliger

Member
Jan 26, 2012
12
1
West Lafayette
The ath6kl driver has been merged today into the official CM9 build. So it should be at latest in tomorrows nightlies :)
http://review.cyanogenmod.com/#/c/12341/

I don't know which version of the driver it's though :(


The ath6kl mods made it into the May 22 nightly build. I reflashed this morning with it because of that. Unfortunately it didn't help with the enterprise WPA2 setup we have where I work. I was really hoping it would. The firmware crashes.

I'll try to get a dump posted somewhere for further review.

---------- Post added at 11:07 AM ---------- Previous post was at 10:35 AM ----------

After the new nightly, I'm seeing the following when I connect to my employer's enterprise Wifi. (WPA2 Enterprise, PEAP Authentication, MSCHAPv2)

We have other devices which work great on the WiFi, so I can't necessarily fault it... But it works great on my other WPA2 PSK Wifi networks (so far).



Code:
<6>[ 1649.984123] msm_device_put:device speaker_stereo_rx set 1
<3>[ 1649.993521] msm_device_put:device freq =48000
<6>[ 1650.030912] aif1 codec rates are already configured, just return
<4>[ 1651.866340] ------------[ cut here ]------------
<4>[ 1651.866379] WARNING: at /mnt/ssd1/eyeballer/android/system/kernel/hp/tenderloin/arch/arm/kernel/smp.c:555 resched_cpu+0x5c/0x74()
<4>[ 1651.881376] Modules linked in: ath6kl cfg80211 compat tun ntfs cifs nls_utf8
<4>[ 1651.888605] [<8004bab0>] (unwind_backtrace+0x0/0x164) from [<800b41f0>] (warn_slowpath_common+0x4c/0x64)
<4>[ 1651.897877] [<800b41f0>] (warn_slowpath_common+0x4c/0x64) from [<800b4220>] (warn_slowpath_null+0x18/0x1c)
<4>[ 1651.907685] [<800b4220>] (warn_slowpath_null+0x18/0x1c) from [<800aab90>] (resched_cpu+0x5c/0x74)
<4>[ 1651.916279] [<800aab90>] (resched_cpu+0x5c/0x74) from [<800b1374>] (scheduler_tick+0x1f4/0x2ec)
<4>[ 1651.925136] [<800b1374>] (scheduler_tick+0x1f4/0x2ec) from [<800bf7b0>] (update_process_times+0x44/0x50)
<4>[ 1651.934509] [<800bf7b0>] (update_process_times+0x44/0x50) from [<800d7e40>] (tick_sched_timer+0x98/0xd8)
<4>[ 1651.943970] [<800d7e40>] (tick_sched_timer+0x98/0xd8) from [<800cdb5c>] (__run_hrtimer+0x90/0x118)
<4>[ 1651.953083] [<800cdb5c>] (__run_hrtimer+0x90/0x118) from [<800cdec8>] (hrtimer_interrupt+0x180/0x358)
<4>[ 1651.962032] [<800cdec8>] (hrtimer_interrupt+0x180/0x358) from [<80054b14>] (msm_timer_interrupt+0x34/0x40)
<4>[ 1651.971927] [<80054b14>] (msm_timer_interrupt+0x34/0x40) from [<800ebb80>] (handle_IRQ_event+0x24/0xc4)
<4>[ 1651.981212] [<800ebb80>] (handle_IRQ_event+0x24/0xc4) from [<800ed780>] (handle_percpu_irq+0x4c/0x8c)
<4>[ 1651.990246] [<800ed780>] (handle_percpu_irq+0x4c/0x8c) from [<8004408c>] (asm_do_IRQ+0x8c/0xcc)
<4>[ 1651.999092] [<8004408c>] (asm_do_IRQ+0x8c/0xcc) from [<80044c4c>] (__irq_svc+0x4c/0xe4)
<4>[ 1652.007072] Exception stack(0xbe017ed8 to 0xbe017f20)
<4>[ 1652.011934] 7ec0:                                                       be57e784 00030013
<4>[ 1652.020098] 7ee0: 00000000 00000000 00030013 00000010 be59be04 be59be00 7ec33538 be016000
<4>[ 1652.028256] 7f00: 00000000 00000001 8be08c3c be017f20 80551174 80551188 60030013 ffffffff
<4>[ 1652.036428] [<80044c4c>] (__irq_svc+0x4c/0xe4) from [<80551188>] (_raw_spin_unlock_irqrestore+0x20/0x4c)
<4>[ 1652.045974] [<80551188>] (_raw_spin_unlock_irqrestore+0x20/0x4c) from [<8035ee50>] (uinput_write+0x6c/0x280)
<4>[ 1652.055779] [<8035ee50>] (uinput_write+0x6c/0x280) from [<80127d94>] (vfs_write+0xac/0x154)
<4>[ 1652.064194] [<80127d94>] (vfs_write+0xac/0x154) from [<80127ee8>] (sys_write+0x3c/0x68)
<4>[ 1652.072180] [<80127ee8>] (sys_write+0x3c/0x68) from [<80045140>] (ret_fast_syscall+0x0/0x30)
<4>[ 1652.080510] ---[ end trace 5dae469770479c12 ]-

...and...

Code:
<3>[ 1794.420677] board_sdio_wifi_enable
<6>[ 1794.436534] wifi_power(1) 1.8V sdio: set load
<6>[ 1794.436861] tenderloin_wifi_power: New regulator mode for 8058_s3: 1
<6>[ 1794.445927] wifi_power(1) 3.3V
<6>[ 1794.466436] wifi_power(1) 8901_l1 3.3V
<6>[ 1794.466776] wifi_power(1) 8058_l19 1.8V
<4>[ 1794.476498] wifi_power(1) CHIP_PWD
<4>[ 1794.823077] mmc1: queuing unknown CIS tuple 0x01 (3 bytes)
<4>[ 1794.832939] mmc1: queuing unknown CIS tuple 0x1a (5 bytes)
<4>[ 1794.837012] mmc1: queuing unknown CIS tuple 0x1b (8 bytes)
<4>[ 1794.843932] mmc1: queuing unknown CIS tuple 0x14 (0 bytes)
<4>[ 1794.854659] mmc1: queuing unknown CIS tuple 0x80 (1 bytes)
<4>[ 1794.854970] mmc1: queuing unknown CIS tuple 0x81 (1 bytes)
<4>[ 1794.866914] mmc1: queuing unknown CIS tuple 0x82 (1 bytes)
<6>[ 1794.867113] mmc1: new high speed SDIO card at address 0001
<3>[ 1794.933752] ath6kl: temporary war to avoid sdio crc error
<6>[ 1795.407845] ath6kl: ar6003 hw 2.1.1 sdio fw 3.2.0.144 api 3
<6>[ 1795.438680] ADDRCONF(NETDEV_UP): wlan0: link is not ready
<6>[ 1795.755950] ADDRCONF(NETDEV_UP): wlan0: link is not ready
<6>[ 1795.935445] ADDRCONF(NETDEV_UP): wlan0: link is not ready
<6>[ 1809.019257] msm_device_put:device speaker_stereo_rx set 0
<6>[ 1809.019319] msm_device_put:device speaker_stereo_rx set 1
<3>[ 1809.028698] msm_device_put:device freq =48000
<6>[ 1809.052902] aif1 codec rates are already configured, just return
<6>[ 1812.921866] ADDRCONF(NETDEV_UP): wlan0: link is not ready
<6>[ 1813.327657] msm_device_put:device speaker_stereo_rx set 0
<6>[ 1813.635058] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<7>[ 1823.896412] wlan0: no IPv6 routers present
<6>[ 1838.236427] gpio-keys: volume down button pressed
<6>[ 1838.416449] gpio-keys: volume down button released
<5>[ 1869.849764] msm_timer_set_next_event(12) clock dg_timer, alarm already expired, now c3e5c04e, alarm c3e5c056, late -8
<4>[ 1874.700760] ath6kl: firmware crashed
<6>[ 1874.747758] ath6kl: crash dump:
<6>[ 1874.747838] ath6kl: hw 0x30000582 fw 3.2.0.144
<6>[ 1874.754439] ath6kl: 0: 0x30000582 0x00000000 0x0095f9a1 0xdeadc160
<6>[ 1874.760687] ath6kl: 4: 0x0095f9a1 0x00060530 0x00000020 0x00000000
<6>[ 1874.766823] ath6kl: 8: 0x005614f0 0x0057e83c 0x0057e7cc 0xdeadc0de
<6>[ 1874.772926] ath6kl: 12: 0x00000003 0x00000000 0x00917c3c 0x00917c4b
<6>[ 1874.779149] ath6kl: 16: 0x00000032 0x005614f0 0x005614f0 0x0057e830
<6>[ 1874.785338] ath6kl: 20: 0x00568ffc 0x00561d40 0x0057a490 0x00000000
<6>[ 1874.791648] ath6kl: 24: 0x8095f601 0x00544208 0x005614f0 0x0057e7e8
<6>[ 1874.797896] ath6kl: 28: 0x0057a490 0x00544204 0x0057e7cc 0x00000001
<6>[ 1874.804089] ath6kl: 32: 0x0057a4a0 0x0057a3c4 0x00568ffc 0x00561d40
<6>[ 1874.810396] ath6kl: 36: 0x8095398c 0x00544248 0x0057e7ec 0x005614f0
<6>[ 1874.816645] ath6kl: 40: 0xc08e0e64 0x00544238 0x00000008 0x00544258
<6>[ 1874.822836] ath6kl: 44: 0x00000000 0x00000000 0x0057e8cc 0x00000000
<6>[ 1874.829147] ath6kl: 48: 0x0057e83c 0x00000000 0x00000000 0x00000000
<6>[ 1874.835339] ath6kl: 52: 0x808e24eb 0x00544268 0x0057e7ec 0x00000000
<6>[ 1874.841650] ath6kl: 56: 0x0027e82e 0x00540d14 0x00541e28 0x00000020
<6>[ 1877.198510] binder: 2204:2259 refcount change on invalid ref 16
<6>[ 1877.198789] binder: 2204:2259 refcount change on invalid re

I wish I could help more in deciphering what it means, but it is what I am seeing. If you need me to get more logs, or could direct me how to enable further logging, I am more than happy to help.

Thanks!
Corey
 
  • Like
Reactions: dashbarranger

jetguy35

Senior Member
Mar 29, 2011
102
11
How is the new driver? Does it fix any of the sleep issues? Also, I noticed that my wifi on cm9 gets less range than when I boot into webos. I can go far enough away where cm9 will not find my network and then I'll boot into webos and it generally pulls up the network with a near full signal. Do the new drivers fix this issue?
 

BIGSimon

Senior Member
Jan 19, 2012
556
807
Barnsley
How is the new driver? Does it fix any of the sleep issues? Also, I noticed that my wifi on cm9 gets less range than when I boot into webos. I can go far enough away where cm9 will not find my network and then I'll boot into webos and it generally pulls up the network with a near full signal. Do the new drivers fix this issue?

My battery life has definitely improved, wifi signal is a lot stronger but still not quite as good as webos but that's to be expected
 

KrzychuG

Senior Member
Mar 23, 2006
79
17
My battery life has definitely improved, wifi signal is a lot stronger but still not quite as good as webos but that's to be expected

As for me it solved the wifi sleep issues, that's for sure. Signal seems to be stronger as well, even tho it sometimes just stop loading pages. If it comes to battery life there are still some issues. I often leave my touchpad unused for long time. With build from 30 may and wifi driver around that date device dies after 48-50h when not being used. There's almost no activity on battery stat page so can't say what's using so much. On alpha 2.1/3 it used to survive 6 days when left unsed, so there's still a lot of work to do.
 

nevertells2

Senior Member
Dec 22, 2011
2,307
1,138
Sunny Central Florida!!!
I have two 32gb TP's, one with the 0527 official nightly and the other has 0517. The 0527 nightly has one of the older wifi drivers that JC Sullins provided and I can set sleep policy to turn off wifi when the TP is put to sleep. I have been using Battery Monitor Widget to watch current usage and have noticed that I get reading similar to my other TP that has sleep policy set to never. I can definitely tell on the 0527 TP that current usage is much improved when asleep. The 0517 TP I turn off wifi from settings and use around 30mA, do not get alerts, email or anything that requires wifi. When I wake it up and turn on wifi, it takes around 25 seconds for wifi to reconnect to my AP. The 0527 TP uses around the same mA's as the other, but I get alerts, email and the like while it is asleep. I see occasional spikes in mA's used which I figure is when the wifi wakes up to receive email, then it goes back to around 30mA. Also when I wake the TP up, wifi is up and running after a couple of seconds.
 

etibon

Senior Member
Oct 28, 2007
126
7
\Does anybody else get problems with Youtube using the latest wifi drivers? At a certain point Youtube videos just stop buffering and I have to toggle the "HQ" setting for it to continue.
Actually the problem is not just with Youtube - its with any operation that needs to maintain a network connection for a certain length of time. I also get web pages that don't load all the pictures, Facebook app doesn't load all the pictures, dowloads stopping etc.
With the drivers prior to 0522 I never used to get these kinds of problems. :-(
BTW, my wifi router is set to channel one, 2.4Ghz etc. I have two wifi access points and I get the same symptoms with both. I also get the same thing when I connect to my phone using wifi tethering.
 

RavenSEAL

Senior Member
Apr 13, 2011
251
18
Tampa
My Touchpad just continues to refuse to connect to any of the Wi-Fi networks at my university when using an Android ROM :(

Works fine at home though...

Oh well, looks like I'll have to stick to using WebOS when I'm at school.
 

nevertells2

Senior Member
Dec 22, 2011
2,307
1,138
Sunny Central Florida!!!
\Does anybody else get problems with Youtube using the latest wifi drivers? At a certain point Youtube videos just stop buffering and I have to toggle the "HQ" setting for it to continue.
Actually the problem is not just with Youtube - its with any operation that needs to maintain a network connection for a certain length of time. I also get web pages that don't load all the pictures, Facebook app doesn't load all the pictures, dowloads stopping etc.
With the drivers prior to 0522 I never used to get these kinds of problems. :-(
BTW, my wifi router is set to channel one, 2.4Ghz etc. I have two wifi access points and I get the same symptoms with both. I also get the same thing when I connect to my phone using wifi tethering.

You say the latest wifi drivers. What version of the drivers are you using? It most likely depends on the date of the nightly you are using.

---------- Post added at 05:56 PM ---------- Previous post was at 05:53 PM ----------

My Touchpad just continues to refuse to connect to any of the Wi-Fi networks at my university when using an Android ROM :(

Works fine at home though...

Oh well, looks like I'll have to stick to using WebOS when I'm at school.

You need to explain more. What Android rom? Are you using CM7, CM9, ClassicNerd, AOKP, etc. If you are using CM9, what is the date of the nightly you are using?
 

RavenSEAL

Senior Member
Apr 13, 2011
251
18
Tampa
You need to explain more. What Android rom? Are you using CM7, CM9, ClassicNerd, AOKP, etc. If you are using CM9, what is the date of the nightly you are using?

Sorry about that.

Tried AOKP TL4 and the latest CM9 Nightly + CN

Anytime I tap on the wireless networks at my university, the connection configuration window does not appear after the first time. IP won't configure. Restart doesn't change any factors.

At home, it works normally like it would on any other android device.
 
Last edited:

sdc177

Senior Member
Jan 15, 2010
519
26
Austin, TX
Thought I read a few months back that HP would be releasing something that would fix wifi for good in July. Am I wrong or will that happen? When should I set my calendar to come back and check?

Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
 

hollywood084

Senior Member
Mar 21, 2009
132
23
I have never had a wifi issue that I know of. I used to run scott's MIUI, then I switched to CM 9 alpha 2 when it was released. Is there anything I can do to contribute?
 

nevertells2

Senior Member
Dec 22, 2011
2,307
1,138
Sunny Central Florida!!!
Thought I read a few months back that HP would be releasing something that would fix wifi for good in July. Am I wrong or will that happen? When should I set my calendar to come back and check?

Sent from my SAMSUNG-SGH-I717 using Tapatalk 2

If you install the July 7th nightly, you will have the latest wifi drivers and they work quite well.
 
  • Like
Reactions: sdc177

nitrobg

Senior Member
Sep 3, 2011
527
213
HP has already released the WiFi driver ... you can see it over here... http://rootzwiki.com/topic/25067-wifi-driver-from-android-dump/page__st__10 ...for a guy like me who had no luck getting WiFi to work since day one.. I flashed this and for the first time I was able to get WiFi to work with the latest cm9 nighty ...

Sent from my Galaxy Nexus using xda app-developers app

You should stick with the latest ath6kl:
http://www.mediafire.com/?ffvfuu4s3etq1zc
There are no issues since it has been merged into the nightlies almost 2 months ago.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    This thread is intended to be a gathering point for all wifi issues on Android Touchpad ROMs.

    Having a separate specific issue thread for this will serve several purposes.

    • Avoid wifi issues getting lost in the more general Touchpad ROM threads.
    • Allow issues common to wifi operation on all the different ROMs to be concentrated in one thread.
    • Reduce annoyance to those who are currently enjoying good wifi operation and who see repetition in the issues being aired.
    • Make it easier to report tests and experience on different set ups and as new drivers / ROM integrations appear.
    • Make it easier for users with questions to see if it has been asked before.

    Background
    Wifi operation on Android Touchpads currently is a hit and miss affair. Some users report flawless operation regardless of access point. Others can get stable operation with careful set up and / or choice of access point but problematic operation on access points over which they have no control. Others still fail to get conditions right for any form of stable operation.
    This is in comparison with WebOS based operation where the problems seem to be much fewer. Probably most of the explanation for this difference is the current lack of suitable drivers integrated into the ROM environment. Hopefully this will be fixed at some point and there are some encouraging signs already that improvements are possible.

    Factors affecting operation
    There are several factors which could potentially affect the wifi performance with Android Touchpads including the type of Access point, the set up of the Access point, the local signal strength and interference conditions, variations in Touchpad hardware build, and how the ROM software has been installed and set up. A key factor on top of all these is the wifi drivers used and how they are integrated.

    General advice
    Until the fundamental performance is improved the end user of the Touchpad can do some things to help get better performance particularly if they have control over the Access point. Typically this will be in the home situation. Possibilities for adjusting setting for work or public access points tend to be small or non-existent.

    Note that not all suggestions work for everybody affected so you have to be prepared to experiment a little to see what may work for you.

    The primary suggestions I offer that worked for me in my home situation is to lower the channel setting on the router to Channel 1 even though for me that was worse from a local interference point of view. Other suggestions include avoiding dual band operation and experimenting with security settings (like using WPA instead of WPA2).

    Posting
    Please post to this thread if
    • You want to ask Android Touchpad wifi specific questions including problems you are encountering
    • You can answer Android Touchpad wifi specific questions posted here
    • You have reports on specific problems that may help resolve wifi issues
    • You have suggestions on how to improve operation in the short term with existing drivers
    • You have reports on new driver operation either better or worse.

    Please also include the ROM and version used in any specific reports. Although wifi issues have been present on 2.3( e.g CM7) and 4.0 (ICS) the focus for development is now firmly on ICS and that is where improvements are likely to be made.

    It is unhelpful at this stage just to post here that you do not have any wifi problems unless you have some specific advice on how that can be generally applied. We already know there are many who enjoy good wifi performance.

    Currently I am using CherryKANG 0.2a which does have some experimental new drivers in and for me gives much better performance.
    5
    That was only a preparation for a new driver which yet still has to come. New driver ath6kl, old driver (and still in use) ar6000.
    So no fix yet for wifi :(

    these are the drivers that fixed wifi for me on nightlie version from yesterday:
    http://dl.dropbox.com/u/37682542/update-ath6kl-v3.0-for-20120509-signed.zip
    3
    Until today I could not connect to my home network without forgetting it and reconnecting, and my uni's network has been almost completely unusuable (on CM9, whereas webOS has been great).

    Attempts to manually change locale/region in various ways have all failed.

    adding "ap_scan=2" to data/misc/wifi/wpa_supplicant.conf fixed the problem with my home router. Hoping it will work at uni as well.

    If you have wifi trouble, if nothing else can help, and if you're bored, maybe you can set ap_scan mode to 2. This mode seems to be appreciated by some of the more frustrating/crappy drivers out there. If it works, let us know! Maybe try ap_scan=1! Good luck :)
    2
    Clearing /data/misc/wifi and rebooting makes my touchpad connect to the router without any hesitation, I guess it is similar to forgetting and rebooting(but haven't tried that)

    ROM: 0.2a Kang