Question on wpa_supplicant running on Android 4.4.2

[Ben Greear]

Hello!

I am trying to debug a strange issue with Samsung tablets, model SMT23NU,
running Android 4.4.2.

When the tablet is idle (no pinging or downloading video or similar), it often
disconnects from and ath10k AP running my modified CT firmware.  The difference
is that when my firmware uses 'htt-mgt', which puts all frames over the HTT
interface, things break, but in normal wmi-mgt case, things work fine.  But, when
I sniff on air, I see no reason for this to cause problems.  Could be this is
timing related issue in the tablet.

I rooted the tablet so I could run 'adb shell' and then 'su'.

Looking at 'cat /proc/kmsg', I captured an instance of this issue (see below).

First thing is that the tablet scans about every 10 seconds.

I guess this is because of how supplicant is configured:

root at degaswifiue:/ # cat /system/etc/wifi/wpa_supplicant_overlay.conf
p2p_disabled=1
autoscan=samsung_exponential:8:128
update_config=1


Anyone know a way I can tweak supplicant and/or android to give me more details?
I cannot install completely new software on this tablet.

Anyone know what that link lost (reason 0x0) means?


<6>[  479.518859]  [1:    kworker/1:2: 4992] [c1] [SENSOR] bma255_work_func - x = 78, y = -46, z = 1022 (ra:0)
<4>[  482.280792]  [0: ksdioirqd/mmc2: 5119] [c0] wlan: SCAN COMPLETED: scanned AP count=42
<6>[  483.967803]  [1:        healthd:  136] [c1] healthd: battery l=99 v=4219 t=29.0 h=2 st=3 c=0 o=4 ca=0 ct=1 ps=0 chg=u
<6>[  485.593292]  [0:    kworker/0:0: 5388] [c0] sec-battery sec-battery: sec_bat_time_management: Charging Time : 481 secs
<6>[  485.594421]  [0:    kworker/0:0: 5388] [c0] sec_bat_swelling_check: status(1), swell_mode(0:0), cv(0x0a), temp(290)
<6>[  485.594512]  [0:    kworker/0:0: 5388] [c0] sec-battery sec-battery: sec_bat_fullcharged_check: Charging Mode : Normal
<6>[  485.600952]  [1:        healthd:  136] [c1] healthd: battery l=99 v=4219 t=29.0 h=2 st=3 c=0 o=4 ca=0 ct=1 ps=0 chg=u
<1>[  488.841430]  [0: wpa_supplicant: 5127] [c0] wlan: wlan0 START SCAN
<4>[  490.183685]  [0: ksdioirqd/mmc2: 5119] [c0] wlan: EVENT: Link lost (reason 0x0)
<1>[  490.183837]  [0: ksdioirqd/mmc2: 5119] [c0] wlan: Disconnected from 04:XX:XX:XX:bd:e0: Reason code 3
<4>[  492.332305]  [0: ksdioirqd/mmc2: 5119] [c0] wlan: SCAN COMPLETED: scanned AP count=43
<6>[  495.549438]  [1:    kworker/1:2: 4992] [c1] [SENSOR] bma255_work_func - x = 78, y = -48, z = 1021 (ra:0)
<6>[  495.601928]  [1:        healthd:  136] [c1] healthd: battery l=99 v=4216 t=29.0 h=2 st=3 c=0 o=4 ca=0 ct=1 ps=0 chg=u
<1>[  498.848358]  [0: wpa_supplicant: 5127] [c0] wlan: wlan0 START SCAN
<6>[  501.973999]  [1:       watchdog:  858] [c1] !@Sync 16
<4>[  502.924743]  [0: ksdioirqd/mmc2: 5119] [c0] wlan: SCAN COMPLETED: scanned AP count=45
<1>[  502.955230]  [0: wpa_supplicant: 5127] [c0] wlan: Connected to bssid 04:XX:XX:XX:bd:e0 successfully
<6>[  502.955444]  [0:    kworker/0:0: 5388] [c0] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
<1>[  503.824829]  [0: wpa_supplicant: 5127] [c0] wlan: wlan0 START SCAN


Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com