Develop Bugs

Galaxy Nexus Wi-Fi dropping / reconnecting

Been having this issue lately with my Galaxy Nexus. Not sure if its the phone, or my router.
When I'm connected to my home wifi network, the connection on my Galaxy Nexus is constantly in and out. It will stay connected for a few minutes, and then drop for a few seconds, reconnect, and keeps repeating the same cycle. I can watch it do this in the wifi connections menu under settings. This is super frustrating when trying to web browse / use apps that require connection, etc.
*Note, this also happens at my Mom's house too. Same issue.
Anyone else have this issue or a fix? Would be greatly appreciated.

I've been having the exact same issue. GSM Galaxy Nexus from Rogers running stock 4.0.1, rooted, unlocked bootloader, UGKL1.
I've tried a few roms (Android Revolution, AOKP 19) with some custom kernels (franco 13.1, GN-GSM by faux123) and still had the same problems.
I've been having the same issue with my Xoom running stock ICS 4.0.3 (rooted, unlocked) as well, so I thought it was my router too. I've reset that and still the problem persists.
I've adjusted both my phone and tablet to only use 2.4ghz in WiFi -> Advanced which was no help either. All other wifi devices in the house are running without issue.
Not sure what to do at this point.

Are there many other wireless networks in your house/area? Is the 2,4GHz band crowded? You can check that with an app called "Wifi Analyzer" from the market. If it is crowded around your channel you, can try to switch it to one less crowded.

Go into Settings>Wifi Settings>Menu>Advanced. Click on "Wifi Frequency Band" and change it from Auto to 2.4 GHz Only.

Herman76 said:
Are there many other wireless networks in your house/area? Is the 2,4GHz band crowded? You can check that with an app called "Wifi Analyzer" from the market. If it is crowded around your channel you, can try to switch it to one less crowded.
Click to expand...
Click to collapse
I've looked into that and changed to a less crowded channel, no change for my phone or tablet. My Xoom was fine before when running HC 3.2.2, my N1 was fine running CM7 Nightly and all other wifi devices are fine in the house. Problems only exist with my ICS devices.
zeppelinmad4 said:
Go into Settings>Wifi Settings>Menu>Advanced. Click on "Wifi Frequency Band" and change it from Auto to 2.4 GHz Only.
Click to expand...
Click to collapse
I've made that change as well, still keeps dropping and connecting.

Have you tried giving your Xoom and GN a Fixed IP (advanced in wireless menu).

No I didn't want to have to go that route, but I guess it's a logical next step. I'll try that tonight.

Did you fix the problem?
Hey
Sorry to dig up an old thread but I have started to experience exactly the same problem with my GSM nexus.
I have had the device since release in November and have nit had any problems until recently. Wifi keeps dropping and reconnecting a few seconds later. Have tried resetting my router and have completely reset my nexus to make sure its not an app. Phone was and still is completely stock 4.0.2, my Xoom has no issues on the same wireless network.
Service centre maybe?

you might want to try the recommended radio and bootloaders and perhaps another kernel (i'd recommend Fugumod kernel)
see the link for recommended radio/bootloaders in the developers section of fugumods kernel (as i cannot post links yet)

Might also want to see if there is newer firmware available for your wireless access point…

I am also experiencing drop and reconnect issues they suck on the battery
but they do not interfere with usage
Code:
Mar 24 08:13:14 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: deauthenticated due to local deauth request
Mar 24 08:13:17 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: authenticated
Mar 24 08:13:17 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: associated (aid 2)
Mar 24 08:13:17 OpenWrt daemon.info hostapd: wlan1: STA WPA: pairwise key handshake completed (RSN)
Mar 24 08:23:05 OpenWrt daemon.info hostapd: wlan1: STA WPA: group key handshake completed (RSN)
Mar 24 08:33:05 OpenWrt daemon.info hostapd: wlan1: STA WPA: group key handshake completed (RSN)
Mar 24 08:43:14 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: deauthenticated due to local deauth request
Mar 24 08:43:17 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: authenticated
Mar 24 08:43:17 OpenWrt daemon.info hostapd: wlan1: STA IEEE 802.11: associated (aid 2)
Mar 24 08:43:17 OpenWrt daemon.info hostapd: wlan1: STA WPA: pairwise key handshake completed (RSN)
Mar 24 08:53:06 OpenWrt daemon.info hostapd: wlan1: STA 3 WPA: group key handshake completed (RSN)
Mar 24 09:03:05 OpenWrt daemon.info hostapd: wlan1: STA WPA: group key handshake completed (RSN)
the phone looses handshake every 10min and reauthes every 30min?!?!

had this exact same problem because of restoring apps and data with google during the initial rom startup. did a complete wipe using recovery mode and skipped the google apps and settings restore at the start and it's working fine since then.

puhhh not cool but I will try it

Try ddwrt if you need a custom fw on your router, openwrt doesnt seem to cut it for you.
Try resetting your router as well or check wifi settings, try wpa/wpa2, try with open network.

İ have same issue my nexus i turned off small character to normal one and gone dropped andbewconnect issue but before i did factory reset and didnt choose my data back i load my application again
Sent from my Galaxy Nexus using XDA

Hi,
could ANYONE having had or still having the specific issue comment on this post?!?
https://plus.google.com/110074557516559184630/posts/1TSvLrXnooy
Samsung has now stopped replacing phones and is throwing the ball at Google.
Please comment on the issue with your experience and tell others of this post.

DooMMeeR said:
Hi,
could ANYONE having had or still having the specific issue comment on this post?!?
https://plus.google.com/110074557516559184630/posts/1TSvLrXnooy
Samsung has now stopped replacing phones and is throwing the ball at Google.
Please comment on the issue with your experience and tell others of this post.
Click to expand...
Click to collapse
This problem started yesterday for me. No problems before yesterday. I have been always on stock. I have IMM76I now... this is annoying...

@DooMMeeR: I think the 10 minutes are just the key-rotation interval of your AP, the periodic handshakes are pretty much normal. What isn't normal are the deauth requests. Do they happen every 30 minutes, every time?
I've recently been getting those Wifi disconnects myself. I think they've started sometime after I've gotten the 4.0.4 update.
This is what a disconnect produces in my wireless logs: (802.11g WPA2 PSK AES)
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: pairwise key handshake completed (RSN)
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 RADIUS: starting accounting session 4FB97683-00000777
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.1X: authorizing port
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: received EAPOL-Key frame (4/4 Pairwise)
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 3/4 msg of 4-Way Handshake
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: received EAPOL-Key frame (2/4 Pairwise)
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/4 msg of 4-Way Handshake
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.1X: unauthorizing port
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: start authentication
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: event 1 notification
May 25 11:52:31 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.11: associated
May 25 11:52:28 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.11: deassociated
May 25 11:52:28 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.11: deauthenticated due to local deauth request
May 25 11:52:28 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 IEEE 802.1X: unauthorizing port
May 25 11:52:28 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: EAPOL-Key timeout
May 25 11:52:27 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:27 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: EAPOL-Key timeout
May 25 11:52:26 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:26 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: EAPOL-Key timeout
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: received EAPOL-Key 2/2 Group with unexpected replay counter
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: group key handshake completed (RSN)
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: received EAPOL-Key frame (2/2 Group)
May 25 11:52:25 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:25 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: EAPOL-Key timeout
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: EAPOL-Key timeout
May 25 11:52:25 hostapd: ath0_wlan0: STA ga:la:xy:ne:xu:s1 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:25 hostapd: ath0_wlan0: STA ot:he:rp:ho:ne:01 WPA: sending 1/2 msg of Group Key Handshake
May 25 11:52:25 hostapd: ath0_wlan0: WPA rekeying GTK
Click to expand...
Click to collapse
It looks like something fails during WPA key-rotation. (presumably the same thing for DooMMeeR)
I've now increased my key-rotation interval from 60s to 3600s to see if that reduces the annoyance of the bug... Which I'm pretty sure is not a wise thing to do from a security standpoint.
Hopefully the problem gets some attention from Google.

Well I've been having this issue. Been messing with my router and set it to channel 1 and its fine now
Sent from my Galaxy Nexus using xda premium

Please use for every Access Point an own SSID.
WiFi Roaming (same SSID on more APs) causes on my devices connection dropping.

How to connect USB Ethernet Adapter gadget

I am trying to connect a usb ethernet adapter to my i747 s3 without success. Has anyone tried this?
I compiled usbnet.ko and cdc_ether.ko from samsung source
insmod worked and I have an entry usb0 when connecting to the adapter (gadget). I am using a USB OTG cable.
I did "ifconfig usb0 192.168.3.100 netmask 255.255.255.0" to assign the ip address to the interface usb0
When I ping the computer on the other side, the "ping" works (packet transmitted and received by party 2) but the "pong" does not work completely (packet transmitted back by party 2 arrived at the phone but then dropped and thus the ping is not complete)
Here is my ifconfig usb0 output
Code:
usb0 Link encap:Ethernet HWaddr C6:75:9C:64:98:AF
inet addr:192.168.3.100 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::c475:9cff:fe64:98af/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:9 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:126 (126.0 B) TX bytes:846 (846.0 B)
Notice that the phone received the "pong" but then dropped it: (RX packets:9 errors:0 dropped:9)
The only related info I found is at android.stackexchange.com/questions/20541/android-usb-gadget-driver, which mentioned that there is some alignment issues. I try to make the changes suggested but was unable to get my newly compile kernel to boot (stuck in a boot loop, this may because I don't know enough about flashing kernel???).
Any pointers?
Thanks.

paganen said:
I am trying to connect a usb ethernet adapter to my i747 s3 without success. Has anyone tried this?
I compiled usbnet.ko and cdc_ether.ko from samsung source
insmod worked and I have an entry usb0 when connecting to the adapter (gadget). I am using a USB OTG cable.
I did "ifconfig usb0 192.168.3.100 netmask 255.255.255.0" to assign the ip address to the interface usb0
When I ping the computer on the other side, the "ping" works (packet transmitted and received by party 2) but the "pong" does not work completely (packet transmitted back by party 2 arrived at the phone but then dropped and thus the ping is not complete)
Here is my ifconfig usb0 output
Code:
usb0 Link encap:Ethernet HWaddr C6:75:9C:64:98:AF
inet addr:192.168.3.100 Bcast:192.168.3.255 Mask:255.255.255.0
inet6 addr: fe80::c475:9cff:fe64:98af/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9 errors:0 dropped:9 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:126 (126.0 B) TX bytes:846 (846.0 B)
Notice that the phone received the "pong" but then dropped it: (RX packets:9 errors:0 dropped:9)
The only related info I found is at android.stackexchange.com/questions/20541/android-usb-gadget-driver, which mentioned that there is some alignment issues. I try to make the changes suggested but was unable to get my newly compile kernel to boot (stuck in a boot loop, this may because I don't know enough about flashing kernel???).
Any pointers?
Thanks.
Click to expand...
Click to collapse
and just because idk, what is the purpose or benefit to doing this? and it sounds like it owuld be a Kernel issue like you said

Deputy13 said:
and just because idk, what is the purpose or benefit to doing this? and it sounds like it owuld be a Kernel issue like you said
Click to expand...
Click to collapse
* The fist use case is when you don't have wifi but you do have wired internet. I realize that you can just buy a wifi access point to solve this poblem as an alternative.
* The second use case is when you want to transmit in another band. Since the phone is only capable of the quad bands, you cannot transmit in other frequencies (think ham radio, marine/police frequencies, or just for watching over the air tv on your phone). For this to work, you need an RF head (antenna) that is capable of doing this. The one I have can only talk "ethernet over usb".

I have some more info, do you know what <incomplete> means from the arp command?
When I run arp, I got:
? (192.168.3.99) at <incomplete> on usb0
When I run tcpdump, from the phone I have:
Code:
No. Time Source Destination Protocol Length Info
1 0.000000 c6:75:9c:64:98:af Broadcast ARP 42 Who has 192.168.3.99? Tell 192.168.3.100
Frame 1: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
Ethernet II, Src: c6:75:9c:64:98:af (c6:75:9c:64:98:af), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)
No. Time Source Destination Protocol Length Info
2 0.000030 Plcom_89:ef:a5 AvlabTec_00:06:04 0xfb94 28 Ethernet II
Frame 2: 28 bytes on wire (224 bits), 28 bytes captured (224 bits)
Ethernet II, Src: Plcom_89:ef:a5 (00:02:aa:89:ef:a5), Dst: AvlabTec_00:06:04 (00:01:08:00:06:04)
Data (14 bytes)
0000 c0 a8 03 63 c6 75 9c 64 98 af c0 a8 03 64 ...c.u.d.....d
From party 2 I have:
Code:
No. Time Source Destination Protocol Length Info
1 0.000000 40:00:40:01:b2:91 45:00:00:54:00:00 0xc0a8 84 Ethernet II
Frame 1: 84 bytes on wire (672 bits), 84 bytes captured (672 bits)
Ethernet II, Src: 40:00:40:01:b2:91 (40:00:40:01:b2:91), Dst: 45:00:00:54:00:00 (45:00:00:54:00:00)
Data (70 bytes)
0000 03 63 c0 a8 03 64 08 00 8d 15 01 05 00 00 41 06 .c...d........A.
0010 03 00 f6 9c 05 00 00 01 02 03 04 05 06 07 08 09 ................
0020 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15 16 17 18 19 ................
0030 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 ...... !"#$%&'()
0040 2a 2b 2c 2d 2e 2f *+,-./

bug in usbnet driver
The problem I found out was that there were two consecutive calls to "remove header" in the driver.

Did you get this running? I am keen to get USB Ethernet support in my international s3 running cm10.1. Step by step guide would we fantastic.

Can you send the patch to usbnet.c?
paganen said:
The problem I found out was that there were two consecutive calls to "remove header" in the driver.
Click to expand...
Click to collapse
Can you send the patch to usbnet.c? I've been searching this problem for few days I am trying to get ehternet throught usb with OTG technology. I managed to load mii.ko , usbnet.ko and cdc_ether.ko. The problem is with the ARP package sent by my i9100, it have 2 bytes dislocated right, the MAC address becomes invalid.
Destination: 00:ca:ff:ff:ff:ff (00:ca:ff:ff:ff:ff)

paganen said:
The problem I found out was that there were two consecutive calls to "remove header" in the driver.
Click to expand...
Click to collapse
Dude, I need that, too!! Struggling with these 2 bytes for a long time, can you teach us how we can fix it??

Issues Tethering with codefireX

Hello,
I am currently running codefireX SR14. My provider is Petro-Canada Mobility. I am having issues when tethering through their "unlimited browsing service" Basically this service only allows http/SSL TCP traffic on ports 80/443.
Anyhow, I've been using autoproxy and this has allowed me greater functionality of most apps. Here lies the problem. When I attempt to tether (wifi hotspot or USB) Traffic is not being forwarded at all from the hotspot gateway. As a result, connected hosts cannot access the internet. After doing some initial troubleshooting, I have concluded the issue appears to be the OS itself.
Regardless of the situation, the hotspot gateway will not forward traffic with autoproxy connected, disconnected, or if I use my Junos VPN.
As a result I have 2 questions:
1)How does the Android tether operate?
2)Are there any "Backend" options I can access someone to force the gateway to forward traffic through autoproxy or my Junos VPN?
I have included the trouble shooting results below:
When tethered:
My PC IP = 192.168.43.83
gateway = 192.168.43.1
Ping to gateway is ok:
>ping 192.168.43.1
Pinging 192.168.43.1 with 32 bytes of data:
Reply from 192.168.43.1: bytes=32 time=23ms TTL=64
Reply from 192.168.43.1: bytes=32 time=2ms TTL=64
Reply from 192.168.43.1: bytes=32 time=1ms TTL=64
Reply from 192.168.43.1: bytes=32 time=1ms TTL=64
Ping statistics for 192.168.43.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
This means my PC can reach the gateway fine (with autoproxy on and off) With that in mind, I try to ping the Petro-Canada proxy server:
Proxy server IP = 10.128.1.69
Ping to Proxy server fails
>ping 10.128.1.69
Pinging 10.128.1.69 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.128.1.69:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
This happens regardless if autoproxy is connected or disconnected. What this means is that the gateway traffic on my phone is not being properly forwarded.
When I usb tether it's the same issue:
PC IP:192.168.42.142
Gateway:192.168.42.129
Ping to gateway is ok:
>ping 192.168.42.129
Pinging 192.168.42.129 with 32 bytes of data:
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Reply from 192.168.42.129: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.42.129:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Ping to Proxy server fails
>ping 10.128.1.69
Pinging 10.128.1.69 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.128.1.69:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
This happens regardless if autoproxy is connected or disconnected. What this means is that the gateway traffic on my phone is not being properly forwarded.
At this point I believe the issue to be Android OS. I am running Jellybean 4.2.2, I also have Junos VPN installed, and I have full internet from my phone when connected (all ports tcp/udp) through Petro-Canada unlimited browsing. I still run into the same issue where trying to ping any outside IP results in a timeout. (i.e Google DNS 8.8.8.8)

I fixed the issue. I'm not sure if it's the ROM or my provider.

[Q] How to get VPN (PPTP) working?

I have DD-WRT on my router, VPN using PPTP is configured and absolutely works with Windows 7 client, iPhone client, iPad client. But not Android (Note 2). It connects fine but drops the connection after approximately 5 minutes. It doesn't even know the connection has dropped. The VPN "key" icon still shows up on the notification bar and still says "VPN is connected". On the DD-WRT (server) side, the logs says:
Aug 24 09:01:35 DD-WRT daemon.info pptpd[29093]: CTRL: Client x.x.x.x control connection started
Aug 24 09:01:35 DD-WRT daemon.info pptpd[29093]: CTRL: Starting call (launching pppd, opening GRE)
Aug 24 09:01:35 DD-WRT daemon.notice pppd[29094]: pppd 2.4.5 started by root, uid 0
Aug 24 09:04:19 DD-WRT daemon.info pppd[29094]: Exit. <--- this is where the connection gets dropped
Aug 24 09:04:19 DD-WRT daemon.err pptpd[29093]: GRE: read(fd=6,buffer=41fe54,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd logs
Aug 24 09:04:19 DD-WRT daemon.err pptpd[29093]: CTRL: PTY read or GRE write failed (pty,gre)=(6,7)
Aug 24 09:04:19 DD-WRT daemon.debug pptpd[29093]: CTRL: Reaping child PPP[29094]
Aug 24 09:04:19 DD-WRT daemon.info pptpd[29093]: CTRL: Client x.x.x.x control connection finished

Firestick 4K dropping wifi after update. (DFS Channel)

Hi Guys. I have 2 FireTV 4k devives, and both of them started to have wifi issues suddenly. (I believe after a software update). My home wifi runs on DFS Channel 56 (which IS supported by FireTV. It has been running fine for over 1 year.
Suddenly this started to happen:
FireTV suddenly drops the WiFi connection. When I try to go into network settings, the device freezes. Sometimes it is able to go to network settings, but it only shows "Ethernet Disconnected".
If i try to to "My FireTV" and "restart", it freezes on the restart screen. The only way to get it back is to pull the power plug, and reboot it. Then, it connects fine to the Wifi, until it drops it again 5 or 10 minutes later.
I was able to enable ADB logs and this is what I found on the logs:
Code:
08-18 12:20:09.159 608 661 D AmazonWifiP2pServiceImpl: CREATE_GROUP
08-18 12:20:09.159 608 661 I AmazonWifiP2pServiceImpl: found saved GO, netId=0
08-18 12:20:09.159 608 661 I AmazonWifiP2pServiceImpl: ethernetConnected = false
08-18 12:20:09.160 608 661 I AmazonWifiP2pServiceImpl: Create GO group use the saved p2p property = 5280
08-18 12:20:09.161 847 847 I wpa_supplicant: P2P: The forced channel for GO (5280 MHz) is not supported for P2P uses
08-18 12:20:09.162 608 661 I AmazonWifiP2pServiceImpl: Create GO group use the default chnl =5180
08-18 12:20:09.163 847 847 I wpa_supplicant: P2P: init GO, use existing freq 5280
08-18 12:20:09.164 847 847 E wpa_supplicant: Failed to create interface p2p-p2p0-12: -12 (Out of memory)
08-18 12:20:09.164 847 847 E wpa_supplicant: P2P: Failed to create new group interface: err=1 (Operation not permitted)
08-18 12:20:09.164 847 847 E wpa_supplicant: P2P: Failed to add group interface
08-18 12:20:09.165 608 661 E WifiP2pService: InactiveStateCREATE_GROUP failed
08-18 12:20:09.165 608 661 I WifiP2pService: InactiveState CREATE_GROUP failed cnt=11
08-18 12:20:09.165 608 661 I WifiP2pService: InactiveState Sending DRIVER_HUNG_EVENT to WifiStateMachine
08-18 12:20:09.168 608 663 I WifiStateMachine: WifiMonitor.DRIVER_HUNG_EVENT
08-18 12:20:09.172 608 663 D WifiNative-HAL: stopRssiMonitoring, cmdId 0
08-18 12:20:09.173 608 664 D DhcpClient: doQuit
08-18 12:20:09.179 608 663 D WifiStateMachine: sendNetworkStateChangeBroadcast:Resetting reason code to null:state=DISCONNECTED,reason=FIRMWARE_CRASH
it seems to be related to Wifi direct and DFS channel 56. But, it has been working fine, on this same channel for MONTHS. I really have to use channel 56 or 60 in my apartment, because all other 5Ghz channels are completely congested.