Obsolete
Status Update
No update yet.
Comments
cc...@gmail.com
I have same issues as well.
From my galaxy nexus, it was working for 4 times, the fifth time it crashed and reboot.
After reboot it is working for another 4 times, and the things continues.
Logcat:
02-13 10:11:41.015: E/wpa_supplicant(1065): Failed to create interface p2p-wlan0-4: -12 (Out of memory)
02-13 10:11:41.015: E/wpa_supplicant(1065): P2P: Failed to create new group interface
02-13 10:11:41.015: E/wpa_supplicant(1065): P2P: Failed to allocate a new interface for the group
From my galaxy nexus, it was working for 4 times, the fifth time it crashed and reboot.
After reboot it is working for another 4 times, and the things continues.
Logcat:
02-13 10:11:41.015: E/wpa_supplicant(1065): Failed to create interface p2p-wlan0-4: -12 (Out of memory)
02-13 10:11:41.015: E/wpa_supplicant(1065): P2P: Failed to create new group interface
02-13 10:11:41.015: E/wpa_supplicant(1065): P2P: Failed to allocate a new interface for the group
is...@google.com
Can somebody attach a full bugreport from device on here for reference ?
is...@google.com
We are aware of a broadcom driver issue that causes stability issues on the ICS release.
I dont have an update timeframe right now, but will update here once we have the fix in a upcoming release.
I dont have an update timeframe right now, but will update here once we have the fix in a upcoming release.
cc...@gmail.com
Thanks for the update.
Here is the log.
Steps:
Try to connect 2 Galaxy Nexus using WiFi Direct sample App.
After a few trial, Phone 2 rebooted, follow by Phone 1.
Refer to log1.txt and log2.txt for each Phone.
Here is the log.
Steps:
Try to connect 2 Galaxy Nexus using WiFi Direct sample App.
After a few trial, Phone 2 rebooted, follow by Phone 1.
Refer to log1.txt and log2.txt for each Phone.
mo...@gmail.com
would this work for a similar problem with ASUS tablet?
ot...@googlemail.com
The issue exists on ASUS tablet's as well? Probably because ASUS is using the same broadcom driver? Can someone clarify?
ga...@gmail.com
4.0.4 on gnexus GSM and 4.0.3 on Asus transformer prime... same problem as OP
za...@gmail.com
I am still having the same issue on nexus running Jelly bean 4.1.1
mg...@gmail.com
Issue still exists on 4.1 (all versions) and 4.2 (up to 4.2.1 so far)
is...@google.com
@Mgaremrz2 can you get bugreport from devices running 4.2 ?
mg...@gmail.com
I will try. I am programming a wifi direct application and seem to have to reboot often. It's much less reliable on my Galaxy Nexus (I left it on 4.1.2). I'll try to upload one when I can.
mg...@gmail.com
This is one of the bugs I have found. I have attached an adb bugreport, but the report never finishes and it hangs - I am not sure if the file dump finished. I appears that it logged everything but failed to return.
Issue: Connected from Galaxy Nexus 4.1.2 to Nexus 7 4.2.1 via WiFi Direct menu in system settings. Nexus 7 NFC appeared to be off so I went to Settings>More (under the Wireless section).
Expceted: Open the fragment.
What happens: Settings UI blocks and nothing finishes. Happens only when using wifi direct /sometimes/, not all the time. Typically signals that the next connection attempt will crash the wifi driver causing wifi to go off entirely or a device reboot. Settings UI never recovers. Log indicates the NFC service has hanged. NFC settings are always set to on and never changed on my N7.
Files: Settings locked: Dump during settings blocked by something related to NFC/wirelss
Settings: Dump directly after Settings hung (and I force closed it).
Let me know if there is anything else I can do for you.
Issue: Connected from Galaxy Nexus 4.1.2 to Nexus 7 4.2.1 via WiFi Direct menu in system settings. Nexus 7 NFC appeared to be off so I went to Settings>More (under the Wireless section).
Expceted: Open the fragment.
What happens: Settings UI blocks and nothing finishes. Happens only when using wifi direct /sometimes/, not all the time. Typically signals that the next connection attempt will crash the wifi driver causing wifi to go off entirely or a device reboot. Settings UI never recovers. Log indicates the NFC service has hanged. NFC settings are always set to on and never changed on my N7.
Files: Settings locked: Dump during settings blocked by something related to NFC/wirelss
Settings: Dump directly after Settings hung (and I force closed it).
Let me know if there is anything else I can do for you.
mg...@gmail.com
I have a logcat log from my device. It just crashed (twice!) on my Nexus 7. Invited the N7 from LG Mach 4.0.4 first with a pin code. System hung up but eventually recovered. I then declined the next invitation prompt (since the first one didn't work). I then invited it with the push button.
System hung, and did a 'soft' reboot (showed nexus logo). I copied all the logcat out of eclipse before it all got erased. I don't have a bugreport because as soon as I copied the text the device did a hard reboot (google logo).
It has some debug info in it and possibly some of my app tags (NFCWIFITRANS).
System hung, and did a 'soft' reboot (showed nexus logo). I copied all the logcat out of eclipse before it all got erased. I don't have a bugreport because as soon as I copied the text the device did a hard reboot (google logo).
It has some debug info in it and possibly some of my app tags (NFCWIFITRANS).
is...@google.com
ab...@gmail.com
Doesn't receive files via WiFi Direct on Nexus 4 running android 4.4.3
is...@google.com
sa...@google.com
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
Bug was confirmed on android-platform:
Reproduce: Run the original WiFiDirectDemo sample app on two Galaxy Nexus devices. Try connecting three or four times in a row. The first three times will likely get you connected. The 4th connect attempt will fail. If you keep trying to connect then, Android will soon crash and reboot. Verified with 4.0.2 stock (yakju-icl53f-factory-89fccaac) running on both devices. As well as with 4.0.3 master (Jan. 29th 2012) running on both devices.
More detail:
A+B: both devices will be set up to be client + server
(start 1st session...)
A: wifiP2pManager.connect()
B: CONNECTION_CHANGED_ACTION / networkInfo.isConnected=true
A: CONNECTION_CHANGED_ACTION / networkInfo.isConnected=true
(switching to ip)
wifiP2pInfo.isGroupOwner==true: new ServerSocket(port) /
serverSocket.accept()
wifiP2pInfo.isGroupOwner==false: new Socket() / socket.bind() /
socket.connect()
(both clients are communicating over input/outputStreams, fast,
trouble free ...)
(A: want's to disconnect)
A: sends disconnect token
B: receives disconnect token
A: socket.close; (isGroupOwner: serverSocket.close);
wifiP2pManager.removeGroup
B: socket.close; (isGroupOwner: serverSocket.close);
wifiP2pManager.removeGroup
(end of ip)
B: CONNECTION_CHANGED_ACTION / networkInfo.isConnected=false
A: CONNECTION_CHANGED_ACTION / networkInfo.isConnected=false
(start 2nd session...)
A: wifiP2pManager.connect()
B: CONNECTION_CHANGED_ACTION / networkInfo.isConnected=true
A: CONNECTION_CHANGED_ACTION / networkInfo.isConnected=true
... (everything good, just like in session 1)
(start 3rd session...)
A: wifiP2pManager.connect()
B: WifiP2pService: isGO: true / GO: null / interface: p2p-wlan0-3
A: WifiP2pService: isGO: true / GO: null / interface: p2p-wlan0-3
A: huh?