I'm having an interesting issue with my AT&T Galaxy Nexus.
At some point, most likely after an update, Wifi tethering stopped working. Because this is a feature I use irregularly, I cannot say for certain when it stopped working. I'm currently using 4.2, but the error persisted into 4.2.1. I know that tethering was working in the past, perhaps in 4.1 or 4.1.2.
The symptom is that when I activate the tethering hotstop, the phone does not turn on the wifi radio (specifically in AP mode). There is no indication of problems on the handset, all of the icons are correct for being in hotspot more, no error message are given. However no other device such as my laptop, Nexus 7, daughters iPod, etc, etc, shows an available wifi network. Tethering and IP forwarding are working because I can correct to the Galaxy Nexus's bluetooth for internet sharing. The problem seems confined to just the Wifi radio.
I did some digging into the logs and discovered the following:
E/hostapd ( 6484): Configuration file: /data/misc/wifi/hostapd.conf
E/hostapd ( 6484): HT (IEEE 802.11n) in 11b mode is not allowed, disabling HT capabilites
I/hostapd ( 6484): rfkill: Cannot open RFKILL control device
E/hostapd ( 6484): nl80211: Failed to set interface wlan0 into AP mode
as well as:
E/hostapd ( 6484): nl80211 driver initialization failed.
All of the log entries for Tethering and TetherController seem correct when I turn off and on the hotspot service.
My /data/misc/wifi/hostapd.conf is pretty basic and has not been hand modified:
interface=wlan0
driver=nl80211
ctrl_interface=/data/misc/wifi/hostapd
ssid=tcgmobile
channel=6
ieee80211n=1
(i have the network open for now during my testing)
The WIFI works fine in normal client mode.
Can anyone shed any light on this? Perhaps there is a driver bug in 4.2?
My next move will be to start wiping and flashing various older ROM versions to try and diagnose this further if no one has any suggestions.
Thanks
mckinleytabor said:
I'm having an interesting issue with my AT&T Galaxy Nexus.
At some point, most likely after an update, Wifi tethering stopped working. Because this is a feature I use irregularly, I cannot say for certain when it stopped working. I'm currently using 4.2, but the error persisted into 4.2.1. I know that tethering was working in the past, perhaps in 4.1 or 4.1.2.
Click to expand...
Click to collapse
I can confirm the issue, seeing the very same behaviour my Nexus S with 4.2.1. It worked with 4.1.1, not sure with 4.1.2
DMESG shows this when trying to enable thetering:
<4>[ 4001.586766] wl_android_wifi_off in
<6>[ 4001.587047] wake disabled for irq 164
<4>[ 4001.587205] wifi_set_power = 0
<4>[ 4001.587275] =========== WLAN placed in RESET ========
<4>[ 4001.601863] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 4001.601970] CFG80211-ERROR) wl_cfg80211_change_virtual_iface : WLC_SET_INFRA error (-1)
<4>[ 4001.602190] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 4001.602345] CFG80211-ERROR) wl_cfg80211_change_virtual_iface : WLC_SET_INFRA error (-1)
<4>[ 4001.602515]
<4>[ 4001.602518] Dongle Host Driver, version 5.90.195.75
<4>[ 4001.602522] Compiled in drivers/net/wireless/bcmdhd on Sep 10 2012 at 14:10:03
<4>[ 4001.602758] wl_android_wifi_on in
<4>[ 4001.602889] wifi_set_power = 1
<4>[ 4001.808894] =========== WLAN going back to live ========
<4>[ 4001.809548] sdio_reset_comm():
<4>[ 4001.827717] F1 signature read @0x18000000=0x9934329
<4>[ 4001.829946] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 4001.874294] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
<6>[ 4001.927125] wake enabled for irq 164
<4>[ 4001.928275] wifi_get_mac_addr
<4>[ 4001.931207] Firmware up: op_mode=2, Broadcom Dongle Host Driver mac=02:1a:11:f6:58:92
<3>[ 4001.937722] CFGP2P-ERROR) wl_cfgp2p_supported : wl p2p error -23
the default wireless tether is working fine here, but third party tether apps do not work until updated for 4.2.X. are you using the default wireless tether with security? try leaving the network open.
Fixed... In a mannor of speaking.
Being somewhat inpatient I went ahead and started experimenting with reflashing ROMs on my device. I didn't actually get very far because it worked on my first attempt.
I did a complete factory reset and reflashed the ROM I had on the device to start with. The ROM is located here: http://forum.xda-developers.com/showthread.php?t=1737849
It would seem that the factory reset did the trick. I went back and confirmed the log files and config files on the new flashing and they are essentially identical to the old flashing. Ergo whatever was preventing the driver from loading was not related to my previous post.
I did have to spend a fun 90 minutes reinstalling all of my software and restoring a manual backup of the SD card data but that needs to be done periodically anyways to clear all the stuff I don't use. So all's well that ends well.
simms22 said:
the default wireless tether is working fine here, but third party tether apps do not work until updated for 4.2.X. are you using the default wireless tether with security? try leaving the network open.
Click to expand...
Click to collapse
I tried the default wireless tethering with various options including secure, open, and different permutations of the network SSID.
Related
Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
Setting a static IP fixed it temporarily but now it doesn't work again.
I have the same problem, wait for a solution.
I also have the same problem
Can you post what rom and radio versions you are using?
Usually this happens because the driver cannot be loaded.
I use :
for radio : 32.43.00.32u_5.09.00.20
for kernel: 2.6.32.15-gf9c0527 [email protected] #1
build: 2.09.405.8 CL218634
soft: LeeDroid_v1.8
I also try: Pays Desire Froyo Sense v1.9
Had the same problem. Wi-Fi starts fine, but if switched off, was unable to start again with the "Unable to start Wi-Fi" error.
Tried flashing different stock roms/radios, updating to Froyo, all sorts, in the end, I sent it back to HTC, they repaired it and I had it back within 4 days.
I just installed
RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed.exe and the wifi problem seems to be solved
dunno, if it really helps. but I had the same problem with all custom roms which used to have wifi-n support. at first, I tried anything starting with wiping, reinstalling and using roms without wifi-n. none of it really helped. but then I changed one single setting on my wifi access point and everthing worked fine with ANY rom and ANY kind of wifi-bandwith.
just a guess, but at least you could try setting your wireless-channel from fixed (mine was fixed to 5) to automatic. there should be an option within your wireless-config on your router called "enable auto channel scan" or something like that...
unless your router is not a really old or crappy one, this could be a solution
edit: PS. I used tested almost every custom rom out of this forum. ALL roms with wifi-n support had the same issues. even newest radio didnt help much. maybe there is something about wifi-n which causes these issues
After two days using "RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00. 32U_5.09.00.20_release_140022_signed" rom, my wifi continue to work like a charm.
It's fairly evident by the number of "wifi problem" threads posted all over xda that there seems to be a huge wifi problem with Android 4.0+. I've seen multiple reports of problems and several reports of methods for fixing user-specific scenarios. In my attempts to better understand what is going on at a system level and in hopes of finding a better solution, I've tried just about all methods I've come across to solve this issue. The only "fix" that works for me is turning off WIFI Power Save Mode via *#0011#. The problem with that fix is it does not work on AOSP ROMs! Hence, I'm trying to find another solution or another method of disabling WiFi Power Save Mode within AOSP ROMs.
Background Information/Description of problem: Turn on wifi and list of available networks will appear. Regardless of being able to connect to a network or not, after 8-10 seconds, the device will scan again, it will time out and the list of available networks will disappear and any connection will be lost. Available networks cannot be seen again until wifi is successfully toggled off and back on again (note - the device seems very picky about actually turning wifi off; it wants to keep it on for some reason - this could be an issue with the multiple reporting of the wifi state in various settings).
Known "Fixes": Some people seem to have luck with certain "fix methods" where others do not.
For most people having this issue or a similar issue, disabling WiFi Power Save Mode in the Service Menu seems to allow the phone to stay connected to networks. This is also true given that the user's wireless router is configured correctly. I've seen reports of several different router models being notorious for issues with Samsung phones, most notably the D-Link DIR-655. I have the DIR-655 and I've configured it to talk nice with my phone when WiFi Power Save Mode is turned off. (I have a new router being shipped to me this week to eliminate this factor altogether)
Some have performed a factory reset with successful wifi connectivity afterwards.
Some have re/flashed a radio and had success. I would like to try reflashing a radio via recovery but we currently do no have one posted on the forum - can someone help me out here?
Some have luck by manually setting the IP address on the router and/or phone.
For the sake of being able to flash an AOSP ROM and have working wifi, I'd like to try and find what's causing this issue and try to find a solution/workaround. I've been troubleshooting and trial-and-erroring most of the weekend.
My research so far:
While looking for the specific setting being toggled via the Service Menu (*#0011#), I found that the WIFI Power Save Mode setting is referenced in /system/app/serviceModeApp_RIL/res/values/strings.xml as
Code:
<string name="powersavemode">WIFI Power Save Mode</string>
which is referenced in /system/app/serviceModeApp_RIL/res/values/public.xml as
Code:
<public type="string" name="powersavemode" id="0x7f06006b" />
That's as far as I've gotten on that road - I haven't found the "0x7f06006b" constant referenced anywhere else yet - maybe someone else knows a quicker way to search for it?
I've attempted to modify settings in wpa_supplicant.conf found in /system/etc/wifi/ and /data/misc/wifi/ with no luck.
I've attempted to use bcm4335 drivers found on other variants of the S4 but I didn't get very far - some implementations are different!
I've gathered several Logcat files for reference:
WiFi Toggle On & Connect
WiFi Connects & Disconnects
CM10.1 WiFi Toggle On Only
Various lines that stand out to me:
Code:
E/wpa_supplicant( 3911): wpa_driver_nl80211_driver_cmd: failed to issue privatecommands
E/wpa_supplicant( 3934): Line 6: unknown global field 'okc=1'.
E/wpa_supplicant( 3934): Line 6: Invalid configuration line 'okc=1'.
I/wpa_supplicant( 3934): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 3934): Could not set interface wlan0 flags (UP): Operation not permitted
E/wpa_supplicant( 3934): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 3934): wlan0: Failed to initialize driver interface
E/wpa_supplicant( 6961): Can't open default ap file
E/wpa_supplicant( 6961): Failed to open config file '/mnt/shell/emulated/0/cred.conf', error: No such file or directory
E/WifiHW ( 721): can't find ctrl_interface=
E/WifiHW ( 721): ctrl_interface != /data/misc/wifi/sockets
E/WifiHW ( 721): wifi_wpa_ctrl_cleanup is skiped.
E/WifiHW ( 721): Unable to open connection to supplicant on "/data/misc/wifi/sockets/p2p0": Connection refused
I'm no expert, but those lines seem to indicate some sort of underlying permissions and/or read/write issues? Some of the files those logs reference to as not existing actually do exist on the device. I saw in one thread where someone mentioned bad partitions? In that same thread someone mentioned flashing the radio/modem to correct their issue and it worked; this is why I want to try reflashing the radio on my phone.
Another thing I want to try is using Odin to reset the entire phone back to official stock, overwriting everything including the modem but we don't have an official tar for this yet.
What I would like to see from other T-Mobile S4 users:
Logcats of someone on stock who does not have wifi issues turning WiFi on from an off state and leaving it for at least 15 seconds. I'd like one where the device does not connect to a network and one where it does connect to a network.
Logcats of someone on CM10.1 doing the same mentioned above.
Someone who knows more about Android than I do to interpret these logcats and provide guidance
I can confirm that the service menu option to disable wifi Does work. Since I did the procedure wifi has been flawless.
im using a verizon dsl modem w router built in, jusy fyi.
Same here with the service code. Tmo s4 btw
Sent from my SGH-M919 using xda app-developers app
Hi,
I have a 2013 Nexus 7 that has the random reboot problem.
Out of curiosity, I ran dmesg and it is flooded with the following log entries
Notify: smsm init
SMS: Modem SMS state changed to SMSM_RESET
Notify: start reset
GSS SMSM state changed to SMSM_RESET
Probable err_fatal on the GSS. Calling subsystem restart...
GSS subsystem failure reason: (unknown, smem_get_entry failed).
subsys-restart: subsystem_restart_dev(): Restart sequence requested for gss, restart_level = 3.
subsys-restart: subsystem_shutdown(): [e3979c00]: Shutting down gss
subsys-restart: subsystem_powerup(): [e3979c00] Powering up gss
pil pil4: gss: Brought out of reset
subsys-restart: subsystem_restart_wq_func(): [e3979c00]: Restart sequence for gss complited.
Notify: start init
...
The message keeps repeating and never stops. Looks like the tablet is stuck in a loop to restart gss and failing.
Does anyone else see the same thing on their dmesg? I'm just wondering if it's normal.
It's rooted stock rom and kernel BTW.
Interesting.
Have you sent that to Google?
I experienced this while building my own custom CM ROM and traced it to these commits:
e459bba398e8a9eee0958d418e9b16dfabdb1515 - mmap: Reinstate passing MADV_MERGEABLE on private anonymous maps
107cdd406b8e404af4d552498076cfe2dfe5efbf - Prevent the madvise(MADV_MERGEABLE) mmap hack from affecting errno.
in bionic. Reverting them from my build enabled the GSS subsystem to load correctly. I'm not sure though if AOSP has fixes for these already or they already have a workaround in the latest builds but reverting these fixed it.
intersectRaven said:
I experienced this while building my own custom CM ROM and traced it to these commits:
e459bba398e8a9eee0958d418e9b16dfabdb1515 - mmap: Reinstate passing MADV_MERGEABLE on private anonymous maps
107cdd406b8e404af4d552498076cfe2dfe5efbf - Prevent the madvise(MADV_MERGEABLE) mmap hack from affecting errno.
in bionic. Reverting them from my build enabled the GSS subsystem to load correctly. I'm not sure though if AOSP has fixes for these already or they already have a workaround in the latest builds but reverting these fixed it.
Click to expand...
Click to collapse
Could you please provide a link to the commit?
@wweeii did you get it fixed?
Sent from my Nexus 4
Hi,
This is my first post, on this great forum, so I'm posting as a "noob"...
So my problem :
- I installed the LegacyXperia 20130908 CM10.1 release. It was working almost OK
- But because of the high wifi drain, I gave the lated DarkKernel a try (http://forum.xda-developers.com/showthread.php?t=2451839)
It seems to perform very good BUT I just noticed something really weird : I have access to the internet through my wifi LAN, I can ping my gateway BUT nothing else works on the local LAN :
ping fails :
[email protected]:/ $ ping -c 1 192.168.1.13
PING 192.168.1.13 (192.168.1.13) 56(84) bytes of data.
From 192.168.1.10 icmp_seq=1 Destination Host Unreachable
The arp table seems incomplete :
1|[email protected]:/ $ arp -a
d810.home (192.168.1.13) at <incomplete> on wlan0
livebox.home (192.168.1.1) at 00:1f:95:26:25:4d [ether] on wlan0
The routes seem ok, the ip neighbours are not :
[email protected]:/ $ ip route show
default via 192.168.1.1 dev wlan0
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.10
192.168.1.1 dev wlan0 scope link
[email protected]:/ $ ip neighbor show
192.168.1.13 dev wlan0 FAILED
192.168.1.1 dev wlan0 lladdr 00:1f:95:26:25:4d STALE
AH, on more weird thing, the kernel arp table has lots of zeroes for the unreachable devices MAC adresses (yes, I have 192.168.1.13 and 1.15 are up and running) :
[email protected]:/ $ cat /proc/net/arp
IP address HW type Flags HW address Mask Device
192.168.1.1 0x1 0x2 00:1f:95:26:25:4d * wlan0
192.168.1.15 0x1 0x0 00:00:00:00:00:00 * wlan0
And I can't seem to be able to communicate with the local LAN only with the android phone...
I have static IPs in my DSL router, I can't set the arp tables manually.
I *think* this was all working with the default ROM kernel, but before I attempt to revert back to that kernel to check (I backed up the modules, but yet another noob thing, I'm not sure putting back the tar into /lib/modules will be enough...) :
==> this is my noob question : anybody knows how I can report that to the dev, and how I can get help ?
Since it's my first post (only 9 remaining now !), I can't post in dev section...
Thanks && regards
Did you flash the DarkModules?
Hi,
Yes i did flash them in cwm...
fschaer said:
==> this is my noob question : anybody knows how I can report that to the dev, and how I can get help ?
Click to expand...
Click to collapse
ROM developer has said:
http://forum.xda-developers.com/showpost.php?p=45704866&postcount=1488
http://forum.xda-developers.com/showpost.php?p=45757921&postcount=155
Someguyfromhell said:
ROM developer has said:
http://forum.xda-developers.com/showpost.php?p=45704866&postcount=1488
http://forum.xda-developers.com/showpost.php?p=45757921&postcount=155
Click to expand...
Click to collapse
Hi,
Thanks for the reminder.
But actually, by dev, i meant the kernel dev : the issue i see is not a force close or things like that,
and it appeared after i flashed this new kernel which seems better for the battery.
I think this is a kernel/wifi modules issue, not a rom one.
Or a noob error, but then i hope some of you can help me understand my error
As i said, wifi is somehow working since i'm replying just now using it...
It's just that apart from the dhcp/gateway, my device seems unable to learn any mac address with this kernel.
I haven't tried a tcpdump for now, and i wanted to test ipv6 but my 'great' dsl/wifi box does not support v6 - yes, that still exists...
Regards
fschaer said:
But actually, by dev, i meant the kernel dev : the issue i see is not a force close or things like that,
Click to expand...
Click to collapse
He is also developing the kernel together with his team, which is given within the .zip file.
Ahh... txs.
OK, now I don't understand anymore anything...
I did :
- remount rw /system/
- cleanup and then restore the /system/lib/modules backup I had done - using tar
- reflash the ROM kernel (200130908)
And... still no ping on the wLAN, but I can ping google and the GW. ??
The arp table still shows me incomplete records.
Still I'm 100% sure I could connect before : I did use connectbot to ssh onto my computer and setup new ssh keys.
I don't know what else I can try exept reboot the dsl box (which is the wifi router)... or delete the recorded stuff in that dsl box and that reference my arc s.
Or reflash all, but I always manage loosing stuff when I reflash (which I avoïd doing then), even with titanium backup
That's all really weird...
Side question : is there *always* a captcha verification on every post ?
Cheers
fschaer said:
Ahh... txs.
OK, now I don't understand anymore anything...
I did :
- remount rw /system/
- cleanup and then restore the /system/lib/modules backup I had done - using tar
- reflash the ROM kernel (200130908)
And... still no ping on the wLAN, but I can ping google and the GW. ??
The arp table still shows me incomplete records.
Still I'm 100% sure I could connect before : I did use connectbot to ssh onto my computer and setup new ssh keys.
I don't know what else I can try exept reboot the dsl box (which is the wifi router)... or delete the recorded stuff in that dsl box and that reference my arc s.
Or reflash all, but I always manage loosing stuff when I reflash (which I avoïd doing then), even with titanium backup
That's all really weird...
Side question : is there *always* a captcha verification on every post ?
Cheers
Click to expand...
Click to collapse
Which DNS server are you using? Did you change anything else by WiFi?
The captcha is only for limited amount of posts, then it will disappear.
I did not change any dns setting, but i saw local names in the terminal, so i must be using my dhcp/box dns.
You remind me i unchecked the wifi optomizations with the new kernel: i read this was causing arp issues on nexus devices...
Lets try to re-enable that... appart from this, i changed nothing after i flashed this kernel.
Except I tried 1.8ghz (it worked well), but this disappeared sincei restored the official rom krtnel
Thats really all i changed since i tried the new kernel yesterday evening
Can you believe this...
- Restoring the wifi optimisations did not help
- rebooting the DSL box helped. For 5 minutes.
I was able to ping a computer on the network, but not to go to the dsl box webserver. and I lost internet.
- subsequent dsl box reboots did not solve anything : no internet, no webserver, no connexion even on the wired PCs , powerd them on or off, nothing.
- *unplugging* everything + dsl box reboot => did restore internet+wifi on the arc
- replugging the PCs did not break
- and I can now see/ping the LAN with the arc s
Only remains, now, the dlink switch I have downtstairs that is the only stuff that remained plugged all time (theres a device on it, but it's off)..... It must have switched to a "netkill" state somehow. Funny, isn't it ?
let's now start wireshark, reinstall the new kernel, and see if there is any difference... and lastly reboot/replug the dlink switch
the come back for the (arp) ping of death ?
Regards
Last experiments:
- fired wireshark, to capture any network suspicious paquets
- reflashed the new kernel+modules
- retried ping / local LAN
Still working.
I rebooted my last network device (dlink switch), repluggued it : everything is still working.
conclusion : I don't understand :laugh:
Cheers
My nexus 7 2013 stopped connecting to wifi a week ago. Then realized bluetooth doesn't work. Wifi won't show any networks; it just fails to turn on and shows no mac address. I thought this must be a weird software issue that some config got mucked up. This happened with running stock 5.1.1 but then tried cm 12.1 to see if it will fix it. Before trying cm I did a factory reset (was stuck at the wifi signin screen) and I cleared the cache and data and cleared dalvik cache. So then I tried CM but unfortunately, this also happens. This has me pretty much convinced that it is a hardware issue and something is wrong with the wifi/bluetooth chip.
Just wanted to see what others thought. After the above, I can't see how this isn't a hardware issue. I was looking and motherboards aren't too expensive and it doesn't look too hard so I might try that.
Oh a weird thing, in this state it is causing an excessive battery drain even when off. It's been off for 8 hours at 100% charge and now is at 74%. So I'm keeping an eye on it to keep it charged until I get a motherboard replacement.
Nothing? Wouldn't others think that this sounds like a hardware problem as the issue persisted across ROMs?
Should I be concerned during disassembly that the battery continues to have an excessive drain even when off?
Do you have root? If you do, install Terminal Emulator, and type the following commands:
su
cat /proc/kmsg >> /sdcard/kmsg.log
Hold down 'Volume Down' key and press C to exit the cat program
Click to expand...
Click to collapse
Then copy the /sdcard/kmsg.log file to your computer, open it up and search for WCNSS and WLAN and see what errors you get.
EDIT:Well this is dumb, you don't have internet so...you can't download Terminal Emulator. If you can, try to get the Terminal Emulator APK downloaded from your PC and transfer it to your phone.
Thanks. I got TE transferred over. I left it for a bit and came back and cat /proc/dmsg was still running. I read that it has something to do with syslogd. I went through the logs but not much of interest. The only time WCNSS is mentioned is here:
Code:
request_suspend_state: sleep (0->3) at 9764978636663 (2015-08-18 23:22:18.939577499 UTC)
<6>[ 9764.990417] early_suspend: call handlers
<4>[ 9764.990600] [ektf3k]:[elan] elan_ktf3k_ts_suspend: enter
<6>[ 9764.991394] active wake lock PowerManagerService.Broadcasts
<6>[ 9764.991577] active wake lock PowerManagerService.WakeLocks
<6>[ 9764.991699] active wake lock PowerManagerService.Display
<6>[ 9764.991790] active wake lock pil-wcnss
<6>[ 9764.992034] PM: Syncing filesystems...
<6>[ 9765.030700] sync done.
WLAN is never mentioned, but ELAN is
Code:
<5>[18419.063201] hall_sensor: [lid_interrupt_handler] LID interrupt handler...gpio: 1..
<5>[18419.129028] hall_sensor: [lid_report_function] SW_LID report value = 1
<6>[18419.207550] request_suspend_state: wakeup (3->0) at 18419196013287 (2015-08-19 01:46:33.156923606 UTC)
<6>[18419.207855] late_resume: call handlers
<4>[18419.208129] [ektf3k]:[elan] elan_ktf3k_ts_resume: enter
<4>[18419.209289] mipi_dsi_panel_power+, on=1
<4>[18419.209930] [ektf3k]:[elan] dump repsponse: 58
<6>[18419.209930] late_resume: done
And also here:
Code:
hall_sensor: [lid_report_function] SW_LID report value = 1
<6>[18419.207550] request_suspend_state: wakeup (3->0) at 18419196013287 (2015-08-19 01:46:33.156923606 UTC)
<6>[18419.207855] late_resume: call handlers
<4>[18419.208129] [ektf3k]:[elan] elan_ktf3k_ts_resume: enter
<4>[18419.209289] mipi_dsi_panel_power+, on=1
<4>[18419.209930] [ektf3k]:[elan] dump repsponse: 58
<6>[18419.209930] late_resume: done
<4>[18419.291656] mipi_dsi_panel_power-
<6>[18419.297668] mipi_JDI_lcd_on+
<6>[18419.297668] mipi_JDI_lcd_on, JDI display on command+, command bl
<6>[18419.441711] mipi_JDI_lcd_on, JDI display on command-
<6>[18419.441711] mipi_JDI_lcd_on-
<7>[18419.457427] EXT_COMMON: hdmi_common_wta_hpd: '1' (unchanged)
I don't see anything that stands out. I was looking for a line confirming (or failing) to activate the wifi/bluetooth.
I attached dmesg but didn't see anything more that stood out, but I might be missing something.
Is there any other way to troubleshoot wifi/bluetooth?
EDIT: I found out adb logcat -d > log.txt seems to give the same as cat /proc/kmsg. I'm looking through it now, but I thought I'd attach that too.