Obsolete
Status Update
Comments
ja...@gmail.com <ja...@gmail.com> #2
I have the same issue. If I come back home with WiFi on the pgonencan detect my network but won't connect.disabling and re enabling WiFi fixes the issue.
to...@gmail.com <to...@gmail.com> #3
This is reported in many fora as the biggest nexus 5 problem. I suggest raising the priority
s....@gmail.com <s....@gmail.com> #4
I have the same problem
It seems that a connection to wifi is only possible when there is no LTE/3G connection. either after reboot before entering pin or in flight mode
successful connect after reboot:
I/wpa_supplicant( 856): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxx' freq=2447 MHz)
I/wpa_supplicant( 856): wlan0: Associated with xx:xx:xx:xx:xx:xx
I/wpa_supplicant( 856): wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP]
I/wpa_supplicant( 856): wlan0: CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed (auth) [id=12 id_str=]
unsuccessful attempt:
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-SSID-REENABLED id=12 ssid="xxx"
I/wpa_supplicant( 847): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxx' freq=2447 MHz)
D/CommandListener( 177): Clearing all IP addresses on wlan0
I/wpa_supplicant( 847): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=12 ssid="xxx" auth_failures=1 duration=10
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
E/wpa_supplicant( 847): current_ssid == NULL
It seems that a connection to wifi is only possible when there is no LTE/3G connection. either after reboot before entering pin or in flight mode
successful connect after reboot:
I/wpa_supplicant( 856): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxx' freq=2447 MHz)
I/wpa_supplicant( 856): wlan0: Associated with xx:xx:xx:xx:xx:xx
I/wpa_supplicant( 856): wlan0: WPA: Key negotiation completed with xx:xx:xx:xx:xx:xx [PTK=CCMP GTK=TKIP]
I/wpa_supplicant( 856): wlan0: CTRL-EVENT-CONNECTED - Connection to xx:xx:xx:xx:xx:xx completed (auth) [id=12 id_str=]
unsuccessful attempt:
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-SSID-REENABLED id=12 ssid="xxx"
I/wpa_supplicant( 847): wlan0: Trying to associate with xx:xx:xx:xx:xx:xx (SSID='xxx' freq=2447 MHz)
D/CommandListener( 177): Clearing all IP addresses on wlan0
I/wpa_supplicant( 847): wlan0: Authentication with xx:xx:xx:xx:xx:xx timed out.
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-DISCONNECTED bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=12 ssid="xxx" auth_failures=1 duration=10
I/wpa_supplicant( 847): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
E/wpa_supplicant( 847): current_ssid == NULL
ai...@gmail.com <ai...@gmail.com> #5
Sale issue here.
When i go home from a 3g connection, i cant access WiFi automatically. I put Nexus 5 plane mode, i quit plane mode, and i entre Ok in my WiFi network.
When i go home from a 3g connection, i cant access WiFi automatically. I put Nexus 5 plane mode, i quit plane mode, and i entre Ok in my WiFi network.
ja...@gmail.com <ja...@gmail.com> #6
I am also having this issue
dg...@gmail.com <dg...@gmail.com> #7
Same issue here. With LTE on I cannot connect to WiFi.
ri...@gmail.com <ri...@gmail.com> #8
[Comment deleted]
ri...@gmail.com <ri...@gmail.com> #9
Note that comments are for discussing the bug. A "me too" can be signified by starring the bug.
ry...@gmail.com <ry...@gmail.com> #10
Thanks for opening a specific thread on this issue for Nexus 5/4.4 and posting logcat data, etc.
When experiencing this problem the phone will seemingly still have detected that the network is in range. Then, when trying to manually re-connect, the UI reports it's attempting to connect, the signal indicator drops to 1 bar, and after a few seconds it gives up, and the network continues to be listed as in-range. As stated, resetting WiFi connection fixes the problem immediately.
I started seeing this problem upon setting-up a new Nexus 5 (no root, noting fancy). I tired a number of things discussed in other forums regarding this issue under v4.3 (remove and re-add Google account, toggle various wifi settings, etc.) to no avail. I tried a factory rest a couple times as well without luck.
However, on one of my factory resets I chose NOT to let setup automatically restore my apps/settings, thinking I'd just do that manually to rule-out any issues with a specific app. Since then I've re-installed all my apps one-by-one, and have yet to see this problem re-surface. I'm wondering if it might be related to the auto-restore process grabbing some wifi settings data (specific to the NIC or to individual saved networks) from my old phone that are somehow incompatible/conflicting with the Nexus 5/4.4.
When experiencing this problem the phone will seemingly still have detected that the network is in range. Then, when trying to manually re-connect, the UI reports it's attempting to connect, the signal indicator drops to 1 bar, and after a few seconds it gives up, and the network continues to be listed as in-range. As stated, resetting WiFi connection fixes the problem immediately.
I started seeing this problem upon setting-up a new Nexus 5 (no root, noting fancy). I tired a number of things discussed in other forums regarding this issue under v4.3 (remove and re-add Google account, toggle various wifi settings, etc.) to no avail. I tried a factory rest a couple times as well without luck.
However, on one of my factory resets I chose NOT to let setup automatically restore my apps/settings, thinking I'd just do that manually to rule-out any issues with a specific app. Since then I've re-installed all my apps one-by-one, and have yet to see this problem re-surface. I'm wondering if it might be related to the auto-restore process grabbing some wifi settings data (specific to the NIC or to individual saved networks) from my old phone that are somehow incompatible/conflicting with the Nexus 5/4.4.
pi...@gmail.com <pi...@gmail.com> #11
#9 ryan
I did pretty much what you did, and it seemed to have solved my issue. My WiFi is automatically reconnecting, and the signal reception seems to be better overall. Granted I've only tested this out a couple times as of writing this, but it feels promising! Thanks!
Here's exactly what I did:
1. Went to Backup & reset and UNCHECKED the Back up my data option as well as the Automatic restore box.
2. Did a factory reset
3. Entered my WiFi credentials
4. SKIPPED signing into my existing Google account until I was on the Android homescreen. I then manually added my Google account from the Settings menu, and again unchecked the "backup data" box when it asked me to do so.
5. Took the phone out for a spin. It's been reconnecting automatically so far.
It would be great if some other folks tried this and gave their results. Again, thank you Ryan!!
I did pretty much what you did, and it seemed to have solved my issue. My WiFi is automatically reconnecting, and the signal reception seems to be better overall. Granted I've only tested this out a couple times as of writing this, but it feels promising! Thanks!
Here's exactly what I did:
1. Went to Backup & reset and UNCHECKED the Back up my data option as well as the Automatic restore box.
2. Did a factory reset
3. Entered my WiFi credentials
4. SKIPPED signing into my existing Google account until I was on the Android homescreen. I then manually added my Google account from the Settings menu, and again unchecked the "backup data" box when it asked me to do so.
5. Took the phone out for a spin. It's been reconnecting automatically so far.
It would be great if some other folks tried this and gave their results. Again, thank you Ryan!!
fd...@gmail.com <fd...@gmail.com> #13
I'm getting EXACTLY the same issues described above, checked with logcat. When I first switched on the Nexus 5, without a SIM card, I couldn't pass the activation phase because the phone wouldn't connect to my WiFi network at all, whereas all my other devices where connected with no problems (a Nexus 4 among them). I could finally get it to connect though my iPhone's 4S Personal Hotspot.
I tried on several different WiFi networks with the same problems: the phone would only connect after I manually hit the connect button several times (around 5 or 6), and it wouldn't reconnect to known networks by itself at all.
So I finally got it randomly working, but Google, this is definitely not ready for primetime.
I tried on several different WiFi networks with the same problems: the phone would only connect after I manually hit the connect button several times (around 5 or 6), and it wouldn't reconnect to known networks by itself at all.
So I finally got it randomly working, but Google, this is definitely not ready for primetime.
mr...@gmail.com <mr...@gmail.com> #14
Found a possible solution. The problem should be caused by the wifi sync from previous device. If you delete all of the wifi data and reboot. Thing will work fine.
adb shell
$ su
# rm -r /data/misc/wifi/
# reboot
adb shell
$ su
# rm -r /data/misc/wifi/
# reboot
mr...@gmail.com <mr...@gmail.com> #15
Also Google should fix the problem ASAP. It is a very frustration experience for old users. A config error in user space should never trigger a kernel crash. It might be fixed by changed by fixing the wifi sync. But I think fixing in the wifi driver is the way to go.
fd...@gmail.com <fd...@gmail.com> #16
I had this problem in the initial set up, even before connecting to Google servers so no settings from previous devices could have been downloaded to the Nexus 5. Afterwards, I also chose the option not to restore a previous backup from Google servers.
I will try the adb commands you suggest and will post the results here.
I will try the adb commands you suggest and will post the results here.
fd...@gmail.com <fd...@gmail.com> #17
I tried running the commands but I guess I need to root the phone and install "su" in order to get administrator permissions...
wa...@gmail.com <wa...@gmail.com> #18
Agree with #13 and #14. I ran the commands as su on terminal emulator and then reboot, I had to rebuilt my WiFi profile but the problem is now fixed - WiFi now reconnects automatically again.
Thanks!
Thanks!
vi...@google.com <vi...@google.com> #19
Can someone please provide a bug report?
For those who suspect wifi sync from previous device is causing issue to them - take a bug report few seconds after you sign-in on a factory reset device; it would have restored your data by then.
For those who suspect wifi sync from previous device is causing issue to them - take a bug report few seconds after you sign-in on a factory reset device; it would have restored your data by then.
do...@gmail.com <do...@gmail.com> #20
We need a fix as soon as possible... This bug is annoying...
al...@gmail.com <al...@gmail.com> #21
What seems to be a solution(at least in my case) is to erase all remembered
wifi networks, reset to factory settings and begin everything from scratch.
From then on, your device will be connected automatically on any newly
added and remembered wifi network.
wifi networks, reset to factory settings and begin everything from scratch.
From then on, your device will be connected automatically on any newly
added and remembered wifi network.
nn...@google.com <nn...@google.com> #22
Hi all,
As mentioned in comment #18 , we really need a bug report to help debug this problem. Creating a bug report is easy. Just go to Settings->Developer Options->Take Bug report and it will offer you the option of e-mailing the report. You can e-mail it to vinitd@google.com or nnk@google.com.
If "Developer Options" doesn't show up on your settings page, you can enable it by tapping on the Settings->About Phone->Build Number box 7 times. Seehttp://www.androidcentral.com/how-enable-developer-settings-android-42
If "Take bug report" is grayed out, you need to enable USB Debugging from the developer settings page.
Alternatively, if you have adb access, you can run "adb bugreport > bugreport.txt" and e-mail it to us.
Bug reports contain private information, and I wouldn't recommend attaching it to the bug without thoroughly reviewing the contents.
Thank you all for helping us get the information necessary to fix this bug.
As mentioned in
If "Developer Options" doesn't show up on your settings page, you can enable it by tapping on the Settings->About Phone->Build Number box 7 times. See
If "Take bug report" is grayed out, you need to enable USB Debugging from the developer settings page.
Alternatively, if you have adb access, you can run "adb bugreport > bugreport.txt" and e-mail it to us.
Bug reports contain private information, and I wouldn't recommend attaching it to the bug without thoroughly reviewing the contents.
Thank you all for helping us get the information necessary to fix this bug.
nn...@google.com <nn...@google.com> #23
And, like comment #18 said, the bug report needs to be generated a few seconds after you sign in on a factory reset device, after the data was restored. A bug report significantly after that will lose valuable information.
mr...@gmail.com <mr...@gmail.com> #24
I can't reproduce the bug again since google now back up the clean wifi data and won't have the driver crash after reset. I hope someone can take a bug report and send to google before using any workaround.
ni...@gmail.com <ni...@gmail.com> #25
for me the problem is not connecting to wifi, I stay connected but seem to loose the connection to the channel it self. doing the reset all connection stuff did not work.
I use a program "appy geek" and once in a while I get error "java.lang.NullPointerException" and after that it looks like the problem is "fixed" at least for a long time. I don't know if that error comes from app or from the phone's wifi.
Should I create a bug report before and after I get the error?
I use a program "appy geek" and once in a while I get error "java.lang.NullPointerException" and after that it looks like the problem is "fixed" at least for a long time. I don't know if that error comes from app or from the phone's wifi.
Should I create a bug report before and after I get the error?
vl...@gmail.com <vl...@gmail.com> #26
Same issue. I can't connect at all at my WiFi network. I can't even download my app installed on previous phone as there are more 1GB... and I do not want to consume all my mobile traffic for app download. Fix this NOW!
ba...@gmail.com <ba...@gmail.com> #27
I have the same issue.
11-27 09:00:03.932: I/wpa_supplicant(1910): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
11-27 09:00:12.222: I/wpa_supplicant(1910): wlan0: Authentication with 9c:21:6a:29:b1:d2 timed out.
11-27 09:00:14.532: I/wpa_supplicant(1910): wlan0: Trying to associate with 9c:21:6a:29:b1:d2 (SSID='Weizhong_Software1' freq=2437 MHz)
11-27 09:00:03.932: I/wpa_supplicant(1910): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
11-27 09:00:12.222: I/wpa_supplicant(1910): wlan0: Authentication with 9c:21:6a:29:b1:d2 timed out.
11-27 09:00:14.532: I/wpa_supplicant(1910): wlan0: Trying to associate with 9c:21:6a:29:b1:d2 (SSID='Weizhong_Software1' freq=2437 MHz)
nn...@google.com <nn...@google.com> #28
Per comments #18, #21, and #22, we still need someone to send us a bugreport. Please do not post "me too"s unless you have something to add. I'll be deleting future posts which don't provide any new information necessary to debug this problem.
fd...@gmail.com <fd...@gmail.com> #29
#27, I already submitted a bug report to android-team (at) google with the subject line "[5-0250000002149] Nexus 5 WiFi connectivity issue". I didn't get any response from the team, so I guessed you were looking into it.
If you need the bug report to be sent again, please let me know.
If you need the bug report to be sent again, please let me know.
nn...@google.com <nn...@google.com> #30
el...@gmail.com <el...@gmail.com> #31
Hello! Following steps in #11 helped. Installed FXR WiFi app and switched off the automatic syncing to Google servers. Did not need to do factory reset.
Thanks for the to tip!
Thanks for the to tip!
ni...@gmail.com <ni...@gmail.com> #32
Is there any news on the wifi issue with 4.4.1 update?
ni...@gmail.com <ni...@gmail.com> #33
Instead of connecting wifi with password I connected using WPS function and is extremely better. Still a bit off sometimes. All other "fix" does noting for me.
ja...@gmail.com <ja...@gmail.com> #34
Hi all
For Those wondering, 4.4.2 did not fix the issue for me. I went ahead and used the wifi fixr app and it did fix it however, by deleting all the old wifi networks in the settings. My nexus 5 now automatically connects to the wifi network at each tube stop like my nexus 4 did before. Interestingly not every single one of them disappeared though : the networks I've actually connected to with my nexus 5 remained... As if there were saved somewhere else!
For Those wondering, 4.4.2 did not fix the issue for me. I went ahead and used the wifi fixr app and it did fix it however, by deleting all the old wifi networks in the settings. My nexus 5 now automatically connects to the wifi network at each tube stop like my nexus 4 did before. Interestingly not every single one of them disappeared though : the networks I've actually connected to with my nexus 5 remained... As if there were saved somewhere else!
lc...@gmail.com <lc...@gmail.com> #35
I can't get connected to my WiFi..just got the nexus 5 but this is a huge dissapointment...can some one help me
This is the error I'm getting
"Saved, secure with WPA/wpa2",
This is the error I'm getting
"Saved, secure with WPA/wpa2",
co...@gmail.com <co...@gmail.com> #36
This was happening on my HTC One (AT&T).
Bug was reproducible (on a 2.4GHz network) by setting the Wi-Fi frequency band to "5GHz only". Presumably this emulates the phone going out of range of the network which was another way to reproduce the bug.
Setting the Wi-Fi frequency band back to "auto" would result in the network showing in the list of networks (password saved) but would not automatically connect. logcat shows the same errors as posted above.
For me, disabling then enabling Wifi didn't work, but disabling then enabling airplane mode would result in the phone connecting to the network.
Removing the /data/misc/wifi/ directory as suggested above appears to have fixed the issue, although it would be nice to have my wifi passwords back.
Bug was reproducible (on a 2.4GHz network) by setting the Wi-Fi frequency band to "5GHz only". Presumably this emulates the phone going out of range of the network which was another way to reproduce the bug.
Setting the Wi-Fi frequency band back to "auto" would result in the network showing in the list of networks (password saved) but would not automatically connect. logcat shows the same errors as posted above.
For me, disabling then enabling Wifi didn't work, but disabling then enabling airplane mode would result in the phone connecting to the network.
Removing the /data/misc/wifi/ directory as suggested above appears to have fixed the issue, although it would be nice to have my wifi passwords back.
wr...@gmail.com <wr...@gmail.com> #37
So 4.4.3 didn't address this. Awesome.
ne...@gmail.com <ne...@gmail.com> #38
As above following the steps in post #13 the work around works for me. Thank you ;)
The Airplane Mode enable reactivate my Wifi as well.
My issue is not being able to use the Wifi App on my Nexus 4 to tether my Nexus 7 to it.
Would be great if Google would address this bug
Cheers
The Airplane Mode enable reactivate my Wifi as well.
My issue is not being able to use the Wifi App on my Nexus 4 to tether my Nexus 7 to it.
Would be great if Google would address this bug
Cheers
ju...@gmail.com <ju...@gmail.com> #39
[Comment deleted]
km...@gmail.com <km...@gmail.com> #40
After reading all the above solutions, it seemed that my Huawei HW302 Android 4.4.2 device only allows with a limited number of connections. As I had just come home from a long multi-country tour and had connected my new phone to several dozen wi-fi spots, I figured I had exceeded the device's wi-fi connections threshold. There were just too many left in the system. Rather than erase them all, as some people had suggested, I simply erased those I didn't recognize or knew I wouldn't be using again. I then erased my home network and re-input my code. Problem is now fixed.
sa...@google.com <sa...@google.com> #41
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
Description
Logcat:
I/wpa_supplicant(14758): wlan0: Authentication with 6c:f3:7f:68:10:80 timed out.
I/wpa_supplicant(14758): wlan0: CTRL-EVENT-DISCONNECTED bssid=6c:f3:7f:68:10:80 reason=3 locally_generated=1
I/wpa_supplicant(14758): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=38 ssid="A-MSFTWLAN" auth_failures=1 duration=10
I/wpa_supplicant(14758): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
E/wpa_supplicant(14758): current_ssid == NULL
I/wpa_supplicant(14758): wlan0: Trying to associate with SSID 'Free Public WiFi'
I/wpa_supplicant(14758): wlan0: Association request to the driver failed
I/wpa_supplicant(14758): wlan0: CTRL-EVENT-SSID-REENABLED id=38 ssid="A-MSFTWLAN"
I/wpa_supplicant(14758): wlan0: Trying to associate with 6c:f3:7f:68:10:90 (SSID='A-MSFTWLAN' freq=5785 MHz)
I/wpa_supplicant(14758): wlan0: Authentication with 6c:f3:7f:68:10:90 timed out.
I/wpa_supplicant(14758): wlan0: CTRL-EVENT-DISCONNECTED bssid=6c:f3:7f:68:10:90 reason=3 locally_generated=1
I/wpa_supplicant(14758): wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=38 ssid="A-MSFTWLAN" auth_failures=2 duration=20
I/wpa_supplicant(14758): wlan0: CTRL-EVENT-ASSOC-REJECT status_code=1
E/wpa_supplicant(14758): current_ssid == NULL
I/wpa_supplicant(14758): wlan0: Trying to associate with SSID 'Free Public WiFi'
I/wpa_supplicant(14758): wlan0: Association request to the driver failed
dmesg:
<6>[ 3493.899316] bq24192_set_input_i_limit: input current limit = 500 setting 0x02
<3>[ 3518.094595] WLDEV-ERROR) wldev_set_country : wldev_set_country: set country for US as Q2 rev 57
<4>[ 3519.297185] ------------[ cut here ]------------
<4>[ 3519.297285] WARNING: at net/wireless/ibss.c:24 __cfg80211_ibss_joined+0x154/0x18c()
<4>[ 3519.297450] [<c010de1c>] (unwind_backtrace+0x0/0x144) from [<c09fd44c>] (dump_stack+0x20/0x24)
<4>[ 3519.297602] [<c09fd44c>] (dump_stack+0x20/0x24) from [<c0192adc>] (warn_slowpath_common+0x58/0x70)
<4>[ 3519.297751] [<c0192adc>] (warn_slowpath_common+0x58/0x70) from [<c0192bec>] (warn_slowpath_null+0x2c/0x34)
<4>[ 3519.297896] [<c0192bec>] (warn_slowpath_null+0x2c/0x34) from [<c09c46f4>] (__cfg80211_ibss_joined+0x154/0x18c)
<4>[ 3519.297985] [<c09c46f4>] (__cfg80211_ibss_joined+0x154/0x18c) from [<c09af058>] (cfg80211_process_rdev_events+0xe0/0x21c)
<4>[ 3519.298133] [<c09af058>] (cfg80211_process_rdev_events+0xe0/0x21c) from [<c09ac11c>] (cfg80211_event_work+0x34/0x58)
<4>[ 3519.298285] [<c09ac11c>] (cfg80211_event_work+0x34/0x58) from [<c01acd58>] (process_one_work+0x144/0x49c)
<4>[ 3519.298432] [<c01acd58>] (process_one_work+0x144/0x49c) from [<c01ad434>] (worker_thread+0x174/0x378)
<4>[ 3519.298579] [<c01ad434>] (worker_thread+0x174/0x378) from [<c01b3690>] (kthread+0x98/0xa4)
<4>[ 3519.298727] [<c01b3690>] (kthread+0x98/0xa4) from [<c0107f60>] (kernel_thread_exit+0x0/0x8)
<4>[ 3519.298805] ---[ end trace 2798f0a5ca958678 ]---
<6>[ 3528.911937] CFG80211-ERROR) wl_cfg80211_disconnect : Reason 3
<4>[ 3542.412631] ------------[ cut here ]------------
<4>[ 3542.412832] WARNING: at net/wireless/ibss.c:24 __cfg80211_ibss_joined+0x154/0x18c()
<4>[ 3542.412955] [<c010de1c>] (unwind_backtrace+0x0/0x144) from [<c09fd44c>] (dump_stack+0x20/0x24)
<4>[ 3542.413143] [<c09fd44c>] (dump_stack+0x20/0x24) from [<c0192adc>] (warn_slowpath_common+0x58/0x70)
<4>[ 3542.413595] [<c0192adc>] (warn_slowpath_common+0x58/0x70) from [<c0192bec>] (warn_slowpath_null+0x2c/0x34)
<4>[ 3542.413773] [<c0192bec>] (warn_slowpath_null+0x2c/0x34) from [<c09c46f4>] (__cfg80211_ibss_joined+0x154/0x18c)
<4>[ 3542.413951] [<c09c46f4>] (__cfg80211_ibss_joined+0x154/0x18c) from [<c09af058>] (cfg80211_process_rdev_events+0xe0/0x21c)
<4>[ 3542.414126] [<c09af058>] (cfg80211_process_rdev_events+0xe0/0x21c) from [<c09ac11c>] (cfg80211_event_work+0x34/0x58)
<4>[ 3542.414321] [<c09ac11c>] (cfg80211_event_work+0x34/0x58) from [<c01acd58>] (process_one_work+0x144/0x49c)
<4>[ 3542.414539] [<c01acd58>] (process_one_work+0x144/0x49c) from [<c01ad434>] (worker_thread+0x174/0x378)
<4>[ 3542.414649] [<c01ad434>] (worker_thread+0x174/0x378) from [<c01b3690>] (kthread+0x98/0xa4)
<4>[ 3542.414835] [<c01b3690>] (kthread+0x98/0xa4) from [<c0107f60>] (kernel_thread_exit+0x0/0x8)
<4>[ 3542.415028] ---[ end trace 2798f0a5ca958679 ]---
<4>[ 3576.276410] ---[ end trace 2798f0a5ca95867a ]---
<6>[ 3583.680638] max17048_set_rcomp: new RCOMP = 0x46
<6>[ 3583.685822] max17048_work: raw soc = 0xA624 raw vcell = 0x0D03
<6>[ 3583.686240] max17048_work: SOC = 85 vbatt_mv = 4163
<6>[ 3583.686467] max17048_work: ibatt_ua = -252311 batt_temp = 305
<6>[ 3583.722149] healthd: battery l=85 v=4163 t=30.4 h=2 st=2 c=-290 chg=u
<6>[ 3585.889862] CFG80211-ERROR) wl_cfg80211_disconnect : Reason 3
<4>[ 3610.141393] ------------[ cut here ]------------
<4>[ 3610.141689] WARNING: at net/wireless/ibss.c:24 __cfg80211_ibss_joined+0x154/0x18c()
<4>[ 3610.142173] [<c010de1c>] (unwind_backtrace+0x0/0x144) from [<c09fd44c>] (dump_stack+0x20/0x24)
<4>[ 3610.142464] [<c09fd44c>] (dump_stack+0x20/0x24) from [<c0192adc>] (warn_slowpath_common+0x58/0x70)
<4>[ 3610.142928] [<c0192adc>] (warn_slowpath_common+0x58/0x70) from [<c0192bec>] (warn_slowpath_null+0x2c/0x34)
<4>[ 3610.143392] [<c0192bec>] (warn_slowpath_null+0x2c/0x34) from [<c09c46f4>] (__cfg80211_ibss_joined+0x154/0x18c)
<4>[ 3610.143857] [<c09c46f4>] (__cfg80211_ibss_joined+0x154/0x18c) from [<c09af058>] (cfg80211_process_rdev_events+0xe0/0x21c)
<4>[ 3610.144317] [<c09af058>] (cfg80211_process_rdev_events+0xe0/0x21c) from [<c09ac11c>] (cfg80211_event_work+0x34/0x58)
<4>[ 3610.144790] [<c09ac11c>] (cfg80211_event_work+0x34/0x58) from [<c01acd58>] (process_one_work+0x144/0x49c)
<4>[ 3610.145255] [<c01acd58>] (process_one_work+0x144/0x49c) from [<c01ad434>] (worker_thread+0x174/0x378)
<4>[ 3610.145713] [<c01ad434>] (worker_thread+0x174/0x378) from [<c01b3690>] (kthread+0x98/0xa4)
<4>[ 3610.145996] [<c01b3690>] (kthread+0x98/0xa4) from [<c0107f60>] (kernel_thread_exit+0x0/0x8)
<4>[ 3610.146430] ---[ end trace 2798f0a5ca95867b ]---
<5>[ 3614.677674] type=1400 audit(1383858867.187:343): avc: denied { read write } for pid=21980 comm="app_process" path="/dev/pts/2" dev="devpts" ino=5 scontext=u:r:zygote:s0 tcontext=u:object_r:devpts:s0 tclass=chr_file
<5>[ 3614.678909] type=1400 audit(1383858867.187:344): avc: denied { write } for pid=21980 comm="app_process" path="pipe:[85261]" dev="pipefs" ino=85261 scontext=u:r:zygote:s0 tcontext=u:r:init:s0 tclass=fifo_file
<5>[ 3614.679031] type=1400 audit(1383858867.187:345): avc: denied { write } for pid=21980 comm="app_process" path="pipe:[85262]" dev="pipefs" ino=85262 scontext=u:r:zygote:s0 tcontext=u:r:init:s0 tclass=fifo_file
<5>[ 3614.679403] type=1400 audit(1383858867.197:346): avc: denied { read write } for pid=21980 comm="app_process" path="socket:[84123]" dev="sockfs" ino=84123 scontext=u:r:zygote:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket
<5>[ 3614.679496] type=1400 audit(1383858867.197:347): avc: denied { read write } for pid=21980 comm="app_process" path="socket:[9184]" dev="sockfs" ino=9184 scontext=u:r:zygote:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket
<5>[ 3614.679616] type=1400 audit(1383858867.197:348): avc: denied { read write } for pid=21980 comm="app_process" path="socket:[46043]" dev="sockfs" ino=46043 scontext=u:r:zygote:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket
<5>[ 3614.679745] type=1400 audit(1383858867.197:349): avc: denied { read write } for pid=21980 comm="app_process" path="socket:[56838]" dev="sockfs" ino=56838 scontext=u:r:zygote:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket
<5>[ 3614.679865] type=1400 audit(1383858867.197:350): avc: denied { read write } for pid=21980 comm="app_process" path="socket:[66440]" dev="sockfs" ino=66440 scontext=u:r:zygote:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket
<5>[ 3614.679955] type=1400 audit(1383858867.197:351): avc: denied { read write } for pid=21980 comm="app_process" path="socket:[86276]" dev="sockfs" ino=86276 scontext=u:r:zygote:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket
<5>[ 3614.680073] type=1400 audit(1383858867.197:352): avc: denied { read write } for pid=21980 comm="app_process" path="socket:[86281]" dev="sockfs" ino=86281 scontext=u:r:zygote:s0 tcontext=u:r:init:s0 tclass=unix_stream_socket