Wifi Direct connection issues

[othy74]

Hi, I'm using Wifi Direct API's on two GN devices, both running 4.0.2.
Using my code, I can establish connections and make use of the high
speed wireless connection. Which is just great!

However, from a certain point on (often rather quickly) the callee
device will stop responding to wifiP2pManager.connect() requests. When
this happens, the wifi broadcast receiver on the called device will not
receive CONNECTION_CHANGED_ACTION events anymore and the logs of _both_
devices show something like this:

E/WifiP2pService( 149): Unhandled message { what=147486 when=-332ms
obj=network: null
E/WifiP2pService( 149): isGO: true
E/WifiP2pService( 149): GO: null
E/WifiP2pService( 149): interface: p2p-wlan0-2 }

Nothing I can do in code then seems to be able to fix this. Restarting
the apps has no positive effect. Disabling and re-enabling wifi direct
does not help. Even rebooting either device individually does not
resolve the issue. Only when I reboot _both_ devices do I get to
establish Wifi Direct connections again.

Looks like the onChannelDisconnected() method in WiFiDirectDemo seems to
be aware of the issue. It contains this error message: "Severe! Channel
is probably lost premanently. Try Disable/Re-Enable P2P."

Anyone else experiencing this?

[deepthi gowri]

Hi,

May i know how are you sending -ip2p-wlan0-2 wps_pbc in ics code, how supplicant is executing this command instead.

Thanks,
Deepthi. 

--
You received this message because you are subscribed to the Google Groups "android-platform" group.
To post to this group, send email to android-...@googlegroups.com.
To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.

[othy74]

Hi,

I'm not "sending ip2p-wlan0-2". I just see this in logcat. I'm using
the documented API's only. Nothing beyond what WiFiDirectDemo does.

I upgraded my devices from 4.0.2 to 4.0.3 AOSP master (radio XXKK6).
Issue is still there. Everything is working for a while and really
well... but then bang, the callee just won't "pick up" anymore. For
completeness: I'm getting status=2 (failed) from onPeersAvailable()
just before WifiP2pService reports "isGO: false / GO: null /
interface: p2p-wlan0-3".

If the instability is likely in the stack, I think you should
communicate this towards developers. If you think this is unlikely,
that would be very valuable information for me as well.

Thank you.

[Irfan Sheriff]

On Mon, Jan 23, 2012 at 6:09 AM, othy74 <oth...@googlemail.com> wrote:

Hi,

I'm not "sending ip2p-wlan0-2". I just see this in logcat. I'm using
the documented API's only. Nothing beyond what WiFiDirectDemo does.

I upgraded my devices from 4.0.2 to 4.0.3 AOSP master (radio XXKK6).
Issue is still there. Everything is working for a while and really
well... but then bang, the callee just won't "pick up" anymore. For
completeness: I'm getting status=2 (failed) from onPeersAvailable()
just before WifiP2pService reports "isGO: false / GO: null /
interface: p2p-wlan0-3".

Does your connection go down on its own ? Can you explain your API calling sequence that causes the issue ?

[othy74]

Irfan Sheriff wrote:
>
> Does your connection go down on its own ? Can you explain your API calling
> sequence that causes the issue ?
>

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?

[Jean-Baptiste Queru]

Note that AOSP builds use the factory firmware on the wifi chip, which
is different from the one that ships on retail devices, for licensing
reasons. It's possible that AOSP builds don't properly support all the
functionality of that chip.

JBQ

> --
> You received this message because you are subscribed to the Google Groups "android-platform" group.
> To post to this group, send email to android-...@googlegroups.com.
> To unsubscribe from this group, send email to android-platfo...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/android-platform?hl=en.
>

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[Irfan Sheriff]

> (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?

This likely means that the group got removed and the message seems to be discarded by the framework. Am not sure why that is happening, a full bugreport will provide more insights.

[othy74]

Thank you for pointing this out. I'm not sure I understand the
implications. Is the factory wifi firmware not part of the radio
image? Can you please elaborate? I was under the impression I could
restore the original setup from recovery backup. Or at least using
yakju-icl53f-factory-89fccaac.tgz. In any case, the situation didn't
change (positive or negative) after switching to AOSP.

[Jean-Baptiste Queru]

Sorry, I was unclear.

The wifi chip comes with a built-in default firmware, so it can be
used as-is with the functionality that is supported by that firmware.

Consumer system images include an updated version of that firmware
which is expected to work better. That firmware is loaded at each boot
and doesn't survive reboots.

Images built from AOSP don't include any updated firmware and use the
default firmware instead, so it's likely that there will be
differences between a consumer system and an AOSP system built from
the same platform source.

JBQ

[othy74]

Wow, interesting. Very kind of you to explain. Obviously I would like
to configure AOSP now to use the updated firmware. The idea that my
AOSP builds are at a disadvantage is bugging me now :o)

[Jean-Baptiste Queru]

Unfortunately at this point we don't have a license to include that
file in AOSP build. I'm investigating a workaround.

JBQ

[othy74]

Irfan Sheriff wrote:
> >
> >
> > > (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?
> >
>
> This likely means that the group got removed and the message seems to be
> discarded by the framework. Am not sure why that is happening, a full
> bugreport will provide more insights.
>

I'm probably not fully up to speed with the procedure. Can you explain
what would make this a satisfying bugreport? I'm willing to do the
best I can.

Some more info: when I run into this issue, switching p2p off does not
give me back access-point WiFi. Switching p2p on again does not give
me back the ability to p2p-connect. If I keep hitting the p2p-connect
button, I can actually make Android reboot itself rather quickly. It
could be that my code is bad, but...

Are you aware of any disadvantages (with respect to p2pWifi) when
using AOSP with the default wifi firmware, compared to using the
updated wifi firmware in a consumer ROM?

[Paul Gardner-Stephen]

Hi,

Depending on the differences in the WiFi driver and kernel versions,
it may be possible to use the firmware.bin from one in the other, and/
or to use the .ko from one in the other (assuming the driver is loaded
as a kernel module).

While Google/Android cannot redistribute these binaries, there is
generally no impediment to you using which one you prefer in your own
device, provided that you don't distribute them. Obviously seek
actual legal advice (which this isn't) if you are unsure.

Paul.

> > >> > For more options, visit this group athttp://groups.google.com/group/android-platform?hl=en.

>
> > >> --
> > >> Jean-Baptiste M. "JBQ" Queru
> > >> Software Engineer, Android Open-Source Project, Google.
>
> > >> Questions sent directly to me that have no reason for being private
> > >> will likely get ignored or forwarded to a public forum with no further
> > >> warning.
>
> > > --
> > > You received this message because you are subscribed to the Google Groups "android-platform" group.
> > > To post to this group, send email to android-...@googlegroups.com.
> > > To unsubscribe from this group, send email to android-platfo...@googlegroups.com.

> > > For more options, visit this group athttp://groups.google.com/group/android-platform?hl=en.

[othy74]

> Some more info: when I run into this issue, switching p2p off does not
> give me back access-point WiFi. Switching p2p on again does not give
> me back the ability to p2p-connect. If I keep hitting the p2p-connect
> button, I can actually make Android reboot itself rather quickly. It
> could be that my code is bad, but...

Actually, no 3rd party software is needed to crash the WiFi Direct
stack. Using the original WiFiDirectDemo app running on two Galaxy
Nexus devices will do.

Try to connect three or four times in a row. The first three times
will get you connected. The 4th connect attempt will fail. And if you
keep trying, you will make the device crash and reboot. I verified
this again running 4.0.2 stock (yakju-icl53f-factory-89fccaac) on both
devices. As well as running 4.0.3 master (Jan. 29th) on both devices.

It would be really helpful if some expert could confirm the issue.

[Irfan Sheriff]

From the look of it, you are hitting a driver issue here. It is a first implementation and we have not had a huge amount of feedback on Wi-Fi direct due to a lack of real application at launch.

A number of enhancements are coming in the near future and the stability should improve.

[othy74]

On Jan 30, 4:25 am, Irfan Sheriff <isher...@gmail.com> wrote:
> From the look of it, you are hitting a driver issue here. It is a first
> implementation and we have not had a huge amount of feedback on Wi-Fi
> direct due to a lack of real application at launch.

A-ha. And I almost thought it's only me. Thank you for the update!

> A number of enhancements are coming in the near future and the stability
> should improve.

Will the required changes all come through AOSP? How will I find out
when it happens?
Will this be in for 4.0.3 still?
Is there any way to follow this development more closely?

(To @Jean-Baptiste + @Paul: I was doing what you have suggested above
- manually adding the closed source Maguro drivers - for a while
already. I started doing this mainly because I was missing Bluetooth
in my AOSP builds. I was just not aware that the wifi blob was any
different or even 'better'.)

[Dirk Jäckel]

Hi!

It would be great if you (Irfan Sheriff or JBQ) could tell us where to
check when these issues are resolved.

Is it resolve in the 4.0.4 firmware images published today?

Regards,
Dirk

[Irfan Sheriff]

unfortunately, the driver fixes for wi-fi direct did not go in 4.0.4.

A refresh of the Wi-fi Direct API and various fixes is planned for a later release.

[Irfan Sheriff]

Yes, we have feature enhancements & API updates planned for the next release. 

On Fri, Jun 8, 2012 at 4:06 AM, Emre Baykal <bayka...@gmail.com> wrote:

Hi,

I would like to know if there will be an update about a refresh of Wi-Fi Direct API soon. If so, in which release is it planned for?

Thanks.

--
You received this message because you are subscribed to the Google Groups "android-platform" group.

To view this discussion on the web visit https://groups.google.com/d/msg/android-platform/-/mIB2yZh2M-sJ.

[othy74]

Hello,

Are the API updates required for fixing the instability issue? Or will
the existing demo app just work with the next release and the new API's
are for added functionality?

Will it be possible to use AP Wifi and Wifi Direct together? And if not,
is this a fundamental problem, or more of a shortcoming with the current
hardware and/or software?

Thank you.

[Irfan Sheriff]

On Fri, Jun 22, 2012 at 6:09 PM, othy74 <oth...@googlemail.com> wrote:

Hello,

Are the API updates required for fixing the instability issue? Or will
the existing demo app just work with the next release and the new API's
are for added functionality?

The instability has nothing to do with API. It will just work with the update.

Will it be possible to use AP Wifi and Wifi Direct together? And if not,
is this a fundamental problem, or more of a shortcoming with the current
hardware and/or software?

It will be possible. Its a limitation of current s/w & in some cases h/w

[othy74]

On 23.06.2012 07:00, Irfan Sheriff wrote:
>
> The instability has nothing to do with API. It will just work with the
> update.

Is Wi-Fi Direct on GNex devices running JB supposed to be stable? I'm
probably doing it wrong somehow, but while trying to connect two GNex
4.1 devices, using only the new Wi-Fi Direct system popup menu, I can
quickly raise this NPE in WifiP2pService.java:

I/wpa_supplicant( 382): p2p-p2p0-7: Associated with a2:0b:ba:d5:f6:13
I/wpa_supplicant( 382): p2p-p2p0-7: WPA: Key negotiation completed with
a2:0b:ba:d5:f6:13 [PTK=CCMP GTK=CCMP]
I/wpa_supplicant( 382): p2p-p2p0-7: CTRL-EVENT-CONNECTED - Connection
to a2:0b:ba:d5:f6:13 completed (auth) [id=0 id_str=]
I/wpa_supplicant( 382): p2p0: P2P-GROUP-STARTED p2p-p2p0-7 client
ssid="DIRECT-RN-
I/wpa_supplicant( 382): adb6" freq=2462
psk=a6d1992c51ce3133c62cef711e1917a57ee2e576a9006daf54c54ecf23bc6f43
go_dev_addr=a2:0b:ba:d5:76:13
W/dalvikvm( 1823): threadid=37: thread exiting with uncaught exception
(group=0x40cef300)
E/AndroidRuntime( 1823): *** FATAL EXCEPTION IN SYSTEM PROCESS:
WifiP2pService
E/AndroidRuntime( 1823): java.lang.NullPointerException
E/AndroidRuntime( 1823): at
android.net.wifi.p2p.WifiP2pService$P2pStateMachine$GroupNegotiationState.processMessage(WifiP2pService.java:1076)
E/AndroidRuntime( 1823): at
com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:895)
E/AndroidRuntime( 1823): at
com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:756)
E/AndroidRuntime( 1823): at
android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 1823): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 1823): at
android.os.HandlerThread.run(HandlerThread.java:60)
I/Process ( 1823): Sending signal. PID: 1823 SIG: 9

Both devices are quite stable otherwise.

>
>
>> Will it be possible to use AP Wifi and Wifi Direct together? And if not,
>> is this a fundamental problem, or more of a shortcoming with the current
>> hardware and/or software?
>>
>
> It will be possible. Its a limitation of current s/w & in some cases h/w
>

Since JB has been released, maybe you can elaborate a bit on this. What
h/w is supposed to provide trouble free Wi-Fi Direct functionality? What
h/w may provide limitations?

Will I be able to run AOSP 4.1, say, on a panda board, put a Wi-Fi USB
stick in and use Wi-Fi Direct?

[Irfan Sheriff]

On Mon, Jul 2, 2012 at 2:04 AM, othy74 <oth...@googlemail.com> wrote:

On 23.06.2012 07:00, Irfan Sheriff wrote:
>
> The instability has nothing to do with API. It will just work with the
> update.

Is Wi-Fi Direct on GNex devices running JB supposed to be stable? I'm
probably doing it wrong somehow, but while trying to connect two GNex
4.1 devices, using only the new Wi-Fi Direct system popup menu, I can
quickly raise this NPE in WifiP2pService.java:

Can you pull in a full bugreport with "adb bugreport" for me from the device showing the exception ?

The driver issues have been fixed on JB and it should be stable - especially with the use of PBC.

 

>
>
>> Will it be possible to use AP Wifi and Wifi Direct together? And if not,
>> is this a fundamental problem, or more of a shortcoming with the current
>> hardware and/or software?
>>
>
> It will be possible. Its a limitation of current s/w & in some cases h/w
>

Since JB has been released, maybe you can elaborate a bit on this. What
h/w is supposed to provide trouble free Wi-Fi Direct functionality? What
h/w may provide limitations

As for the nexus devices, WiFi direct is supported on nexus 7 & galaxy nexus (BCM 4330 based).

They support single channel concurrency (STA & Wifi Direct operation on the same channel).

I dont believe we have tested for Wi-Fi direct support on panda board - so thats unclear to me.

[othy74]

On 02.07.2012 18:46, Irfan Sheriff wrote:
>
> Can you pull in a full bugreport with "adb bugreport" for me from the
> device showing the exception ?

After the NPE is raised, on the device where the connect request is
being accepted, the device will immediately reboot. Just now, I got
three reboots on three successive connect attempts. To be fair, I
sometimes also see it working three times in a row.

This feels so much like Wi-Fi Direct on 4.0. Can it be, I'm using the
wrong radio maybe? My baseband = XXLF1, JB build = JRN84D.

> As for the nexus devices, WiFi direct is supported on nexus 7 & galaxy
> nexus (BCM 4330 based).

What about BCM 4329 devices like Nexus S and Xoom?

[Irfan Sheriff]

On Mon, Jul 2, 2012 at 3:23 PM, othy74 <oth...@googlemail.com> wrote:

On 02.07.2012 18:46, Irfan Sheriff wrote:
>
> Can you pull in a full bugreport with "adb bugreport" for me from the
> device showing the exception ?

After the NPE is raised, on the device where the connect request is
being accepted, the device will immediately reboot. Just now, I got
three reboots on three successive connect attempts. To be fair, I
sometimes also see it working three times in a row.

This feels so much like Wi-Fi Direct on 4.0. Can it be, I'm using the
wrong radio maybe? My baseband = XXLF1, JB build = JRN84D.

What device is this on ? And I would have to look at the bugreport to see what is going on with your setup.

On galaxy nexus & nexus 7, we had two external apps test out the API (tapestry & opengarden)  without the issues you describe. You could check with how tapestry runs for comparison.

> As for the nexus devices, WiFi direct is supported on nexus 7 & galaxy
> nexus (BCM 4330 based).

What about BCM 4329 devices like Nexus S and Xoom?

They are not going to support it.

[othy74]

>> My baseband = XXLF1, JB build = JRN84D.
>
> What device is this on ?

JB/GNex. Please, what is the correct radio/baseband for this to work?

> And I would have to look at the bugreport to see
> what is going on with your setup.

I'm unable to generate a bugreport in the split moment between the NPE
and the reboot.

> On galaxy nexus & nexus 7, we had two external apps test out the API (

> tapestry<https://play.google.com/store/apps/details?id=com.ekatasystems.apps.tapestry&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5la2F0YXN5c3RlbXMuYXBwcy50YXBlc3RyeSJd>&
> opengarden<https://play.google.com/store/apps/details?id=com.opengarden.android.MeshClient&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5vcGVuZ2FyZGVuLmFuZHJvaWQuTWVzaENsaWVudCJd>)

> without the issues you describe. You could check with how tapestry runs for
> comparison.

So far I'm not using apps. My issue is with the on board WiFi direct
connect functionality.

>> What about BCM 4329 devices like Nexus S and Xoom?
>>
>
> They are not going to support it.

There must be technical reasons for this, I assume?

[Irfan Sheriff]

On Mon, Jul 2, 2012 at 4:46 PM, othy74 <oth...@googlemail.com> wrote:

>> My baseband = XXLF1, JB build = JRN84D.
>
> What device is this on ?

JB/GNex. Please, what is the correct radio/baseband for this to work?

The baseband radio should not affect wifi direct behavior.

> And I would have to look at the bugreport to see
> what is going on with your setup.

I'm unable to generate a bugreport in the split moment between the NPE
and the reboot.

A bugreport after the restart should be fine
 

> On galaxy nexus & nexus 7, we had two external apps test out the API (

> tapestry<https://play.google.com/store/apps/details?id=com.ekatasystems.apps.tapestry&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5la2F0YXN5c3RlbXMuYXBwcy50YXBlc3RyeSJd>&
> opengarden<https://play.google.com/store/apps/details?id=com.opengarden.android.MeshClient&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5vcGVuZ2FyZGVuLmFuZHJvaWQuTWVzaENsaWVudCJd>)

> without the issues you describe. You could check with how tapestry runs for
> comparison.

So far I'm not using apps. My issue is with the on board WiFi direct
connect functionality.

>> What about BCM 4329 devices like Nexus S and Xoom?
>>
>
> They are not going to support it.

There must be technical reasons for this, I assume?

Yeah, the firmware on the old chipset has trouble handling wifi direct - it is not officially supported.

[othy74]

On 03.07.2012 02:15, Irfan Sheriff wrote:
>
> The baseband radio should not affect wifi direct behavior.

Just curious: how does wifi firmware get updated then?

>
> A bugreport after the restart should be fine
>

bugreport is on it's way to you.

[othy74]

On 02.07.2012 18:46, Irfan Sheriff wrote:

> As for the nexus devices, WiFi direct is supported on nexus 7 & galaxy
> nexus (BCM 4330 based).

Are you saying both devices use the same chip? If N7 is using different
h/w, this could explain why it's WiFi Direct is more stable than GN, no?

[Irfan Sheriff]

ok, the issue seems to be you have a misformatted device name that is not being handled properly.

adb5 is fine:

07-03 03:29:09.334   378   378 I wpa_supplicant: p2p0: P2P-GROUP-STARTED p2p-p2p0-0 GO ssid="DIRECT-eh-adb5" freq=2412 passphrase="KckFk1Z5" go_dev_addr=a2:0b:ba:bb:f2:51

adb6 is not:

07-03 03:29:27.811   378   378 I wpa_supplicant: p2p0: P2P-GROUP-STARTED p2p-p2p0-1 client ssid="DIRECT-vl-

07-03 03:29:27.811   378   378 I wpa_supplicant: adb6" freq=2412 psk=deb79d16c655dc45898eed68369dacd84bcc2ecaf4a06ea571fd6383038964bf go_dev_addr=a2:0b:ba:d5:76:11

The parsing fails perhaps from a newline character in adb6. Try to change the device name for that device. Did you configure these names from settings or some other way ?

On Mon, Jul 2, 2012 at 6:48 PM, othy74 <oth...@googlemail.com> wrote:

On 03.07.2012 02:15, Irfan Sheriff wrote:
>
> The baseband radio should not affect wifi direct behavior.

Just curious: how does wifi firmware get updated then?

I dont quite follow your question - wifi firmware is updated like any other part of the system, as part of the build or an OTA.

[Irfan Sheriff]

Yes, both N7 & GN use the same chip with a firmware difference being that N7 does not support 11a for regular wifi operation. 

[othy74]

Yes! I had a newline right before the device name. Tsss, must have
entered it via the phone GUI. Well, removing it let's me connect
*without* device booting. Great!

One other thing: In *some* cases, after manually disconnecting a direct
connection, the device names do not come back (to be shown as Available
again). Normally they do, but sometimes they don't. Going back and forth
between the views may eventually bring them back. But this can take a
relly long time. Sometimes only one device re-appears. This may sound
like a minor problem, but can be super annoying in real life situations.
Just saying.

> Yes, both N7 & GN use the same chip with a firmware difference being
> that N7 does not support 11a for regular wifi operation.

This http://www.ifixit.com/Teardown/Nexus-7-Teardown/9623/2 describes
the N7 wifi as "AzureWave AW-NH665". Is this a BCM 4330 under a
different name only?

Finally, I found the new service discovery API's. I assume a more
prosaic documentation will be made available soon? Looking forward.
Thank you.

[Irfan Sheriff]

On Tue, Jul 3, 2012 at 10:19 AM, othy74 <oth...@googlemail.com> wrote:

Yes! I had a newline right before the device name. Tsss, must have
entered it via the phone GUI. Well, removing it let's me connect
*without* device booting. Great!

You were not seeing a device reboot. You were seeing the runtime restart. There is a bug here to sanitize device name input which I will fix.

 

One other thing: In *some* cases, after manually disconnecting a direct
connection, the device names do not come back (to be shown as Available
again). Normally they do, but sometimes they don't. Going back and forth
between the views may eventually bring them back. But this can take a
relly long time. Sometimes only one device re-appears. This may sound
like a minor problem, but can be super annoying in real life situations.
Just saying.

Going back & forth is stopping & starting discovery. Note that both devices have to be in discovery (searching on UI) to see each other. Otherwise, one might not see other.

 

> Yes, both N7 & GN use the same chip with a firmware difference being
> that N7 does not support 11a for regular wifi operation.

This http://www.ifixit.com/Teardown/Nexus-7-Teardown/9623/2 describes
the N7 wifi as "AzureWave AW-NH665". Is this a BCM 4330 under a
different name only?

Yes, Azurewave is a brand module for the BCM chipset.

 

Finally, I found the new service discovery API's. I assume a more
prosaic documentation will be made available soon? Looking forward.
Thank you.

All the current documentation is available at 

http://developer.android.com/reference/android/net/wifi/p2p/WifiP2pManager.html

It will improve further over time.

[othy74]

On 03.07.2012 19:29, Irfan Sheriff wrote:
>
> You were not seeing a device reboot. You were seeing the runtime restart.
> There is a bug here to sanitize device name input which I will fix.

Cool. Yes, I did notice how quickly that went.

>> One other thing: In *some* cases, after manually disconnecting a direct
>> connection, the device names do not come back (to be shown as Available
>> again). Normally they do, but sometimes they don't. Going back and forth
>> between the views may eventually bring them back. But this can take a
>> relly long time. Sometimes only one device re-appears. This may sound
>> like a minor problem, but can be super annoying in real life situations.
>> Just saying.
>>
>
> Going back & forth is stopping & starting discovery. Note that both devices
> have to be in discovery (searching on UI) to see each other. Otherwise, one
> might not see other.

I was only starting to go back and forth after the device names did not
show up for three or more minutes. Please be so kind and take a look at
this.

[Irfan Sheriff]

On Thu, Jul 5, 2012 at 4:08 PM, dhakim <dha...@trxsystems.com> wrote:

Ran across this thread through a link in the bug report on Android Bug Reports.  This seems to match what I'm seeing on the Galaxy Nexus phones using wifi direct, both the demo app and my own attempts.  One of the final log messages is indeed the start of a direct wireless network and cuts off.  But I am not sure I understand the prescribed solution. 

What build & device are you using ? 

Device name for wifi direct on JB can be changed from settings > wifi > wifi direct

 

Is there a way I can fix the devices to not crash without rooting them?  What exactly do I have to set and how do I go about setting it?  Can it be done through ADB or other tools? 

[othy74]

Would it not be good to make the new Wifi Direct peer selector in JB
accessible via dedicated intent? (Maybe this is already implemented?)
And why not make it also accessible as a dedicated Settings shortcut?

[othy74]

A Wifi Direct link was created between two GN devices running JB. Data
is being exchanged. Life is good. At one point wpa_supplicant logs this
(on both devices in parallel):

GO:
p2p-p2p0-1: AP-STA-DISCONNECTED a2:0b:ba:... p2p_dev_addr=a2:0b:ba:...
p2p0: AP-STA-DISCONNECTED a2:0b:ba:... p2p_dev_addr=a2:0b:ba:...

Wifi Direct client:
wlan0: Trying to associate with 1c:e6:76:... (SSID=... freq=5180 MHz)
p2p0: P2P-GROUP-REMOVED p2p-p2p0-0 client reason=FREQ_CONFLICT

FREQ_CONFLICT? (No AP-Wifi and no 3G were being used in parallel.)
For the GO this is it. The client continues (1c:e6:76:... = my Wifi-AP)
with no end:

wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
Retrying assoc Iteration:1
wlan0: Trying to associate with 1c:e6:76:... (SSID=... freq=5180 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
Retrying assoc Iteration:1
wlan0: Trying to associate with 1c:e6:76:... (SSID=... freq=5180 MHz)
wlan0: CTRL-EVENT-ASSOC-REJECT status_code=16
Retrying assoc Iteration:1
wlan0: Trying to associate with 1c:e6:76:... (SSID=... freq=5180 MHz)
...

What could this mean?

[Irfan Sheriff]

This means Wifi Direct connection failed when the STA is connected on a different channel to an AP. 

We do not support multi-channel concurrency yet. There is a system UI planned to notify a user when this happens as part of an update.

--
You received this message because you are subscribed to the Google Groups "android-platform" group.

[Irfan Sheriff]

Ah, you seem to mention no AP-STA connection was active. Was this case on both the devices ?

[othy74]

On 07.07.2012 18:09, Irfan Sheriff wrote:
> Ah, you seem to mention no AP-STA connection was active. Was this case on
> both the devices ?

No AP-STA on both devices. This seems to be part of the problem.

A WiFI Direct link was established, similar to how WiFiDirectDemo would
do it. Data is being exchanged, no problems. Then a 3rd-party app is
started, using the active WiFI Direct link. The app communicates with
the other client just fine. But after a while it looks as if the app is
trying to activate AP-WiFi, and by doing so it is killing the active
WiFi Direct link. (This seems wrong. But it is not the root problem.)

I guess the app is calling ConnectivityManager getActiveNetworkInfo()
and because no network (other than our existing Wifi Direct link) is
active, null is being returned. While not true, the app is now under the
impression that the network has just dropped. And by trying to activate
AP-STA the app will kill the working Wifi Direct link.

I was able to "fix" the problem, by deleting all configured AP's on the
device. Not being able to activate any existing AP-STA connection, the
app cannot take harmful action and the Wifi Direct link won't be dropped.

Would it be smart to add an active Wifi Direct link to the list of
ConnectivityManager, so that getActiveNetwirkInfo() will not return
null, when there is no other active link?

[Irfan Sheriff]

On Sat, Jul 7, 2012 at 3:28 PM, othy74 <oth...@googlemail.com> wrote:

On 07.07.2012 18:09, Irfan Sheriff wrote:
> Ah, you seem to mention no AP-STA connection was active. Was this case on
> both the devices ?

No AP-STA on both devices. This seems to be part of the problem.

A WiFI Direct link was established, similar to how WiFiDirectDemo would
do it. Data is being exchanged, no problems. Then a 3rd-party app is
started, using the active WiFI Direct link. The app communicates with
the other client just fine. But after a while it looks as if the app is
trying to activate AP-WiFi, and by doing so it is killing the active
WiFi Direct link. (This seems wrong. But it is not the root problem.)

If an app tries to connect to AP on a different channel, Wifi Direct connection will drop and this is working as intended since STA connection gets priority over wifi direct.

[Irfan Sheriff]

You are running ICS - so you are not running into this issue.

On Fri, Jul 6, 2012 at 8:30 AM, dhakim <dha...@trxsystems.com> wrote:

I don't think Jelly Bean is out yet on Samsung's international version Galaxy Nexus phones. 

Model Number:
Galaxy Nexus

Android Version:
4.0.2

Baseband Version:
I9250XXKK6

Kernel Version:
3.0.8-gaaa2611
android-build@apa28 #1

Build Number
ICL53F.I9250XWKL2

We have Galaxy's and Nexus's as well as a few tablets, also.  But the Galaxy Nexuses looked like they would have the best wifi direct support. 

--
You received this message because you are subscribed to the Google Groups "android-platform" group.

To view this discussion on the web visit https://groups.google.com/d/msg/android-platform/-/xqWiroUI5yYJ.

[Irfan Sheriff]

Can you get bugreport for me b/w N7 & galaxy nexus ?

The original issue on this thread was fixed.

On Mon, Jan 21, 2013 at 6:03 PM, Mike Perez <mgam...@gmail.com> wrote:

As far as I am aware, nothing in this thread actually got fixed. I can't connect my N7 4.2.1, Galaxy Nexus 4.1.2, or LG Mach 4.0.4 reliably at all to each other. In fact, the devices reboot often on first connect, and accepting an invite typically locks the entire system up.

On Monday, December 17, 2012 12:14:41 PM UTC-7, David Smith wrote:

Has this issue been resolved? After reading over the replies, it is not clear the root cause of the Wi-Fi direct failures, or how to fix it.

I am observing the Wi-Fi Direct crash reported in this thread. To reproduce, I am using a Galaxy S3 to connect with a non-android device that supports Wi-Fi Direct. I find that the Galaxy S3 running 4.1.1 will crash during the connection. However, a Galaxy S2 running 4.0.4 will not crash and will establish a connection correctly. The SSID of the non-android device is DIRECT-IBTest, which should not lead to parsing issues.

Here is the log of the WI-Fi Direct connection up to the crash on a Galaxy S3:

/WifiP2pService( 2165): InactiveState{ what=139271 }
I/p2p_supplicant( 1641): [wpa_supplicant_ctrl_iface_process] : P2P_STOP_FIND
I/p2p_supplicant( 1641): p2p0: P2P-FIND-STOPPED
D/WifiP2pService( 2165): InactiveState sending connect
D/WifiP2pService( 2165): Sending join to GO
I/p2p_supplicant( 1641): [wpa_supplicant_ctrl_iface_process] : P2P_CONNECT b7:8a pbc join
I/p2p_supplicant( 1641): SS: Go oper channel is = [0]
D/WifiStateMachine( 2165): WifiManager.SEC_COMMAND_ID_SET_WIFI_ENABLED_WITH_P2P mSkipScanAssoc : true
D/WifiNative( 2165): callSECApiBoolean - ID [13]
D/WifiP2pService( 2165): GroupCreatingState
D/WifiP2pService( 2165): GroupNegotiationState
D/WifiService( 2165): WiFi Enabled with p2p -> Stop Scan, Stop Assoc
D/WifiP2pService( 2165): GroupNegotiationState{ what=147493 }
D/WifiP2pService( 2165): GroupCreatingState{ what=147493 }
D/WifiP2pService( 2165): P2pEnabledState{ what=147493 }
D/WifiP2pSettings( 2335):  connect success
D/WifiP2pService( 2165): GroupNegotiationState{ what=139283 }
D/WifiP2pService( 2165): GroupCreatingState{ what=139283 }
D/WifiP2pService( 2165): P2pEnabledState{ what=139283 }
D/WifiP2pService( 2165): DefaultState{ what=139283 }
D/WifiP2pSettings( 2335): setScanTimer - scan : false, listen : false
E/WifiP2pStateTracker( 2165): getNetworkInfo : NetworkInfo: type: WIFI_P2P[], state: UNKNOWN/IDLE, reason: (unspecified), extra: (none), roaming: false, failover: false, isAvailable: true
D/lights  ( 2165): button : 0 +
D/lights  ( 2165): button : 0 -
W/PowerManagerService( 2165): Timer 0x7->0x3|0x0
I/PowerManagerService( 2165): Ulight 0x7->0x3|0x0
D/LightsService( 2165): setLightLocked is called
E/SMD     (  180): DCD ON
D/Tethering( 2165): interfaceAdded p2p-wlan0-0
D/Tethering( 2165): p2p-wlan0-0 is not a tetherable iface, ignoring
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, false
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, false
I/p2p_supplicant( 1641): rfkill: Cannot open RFKILL control device
D/Tethering( 2165): interfaceLinkStateChanged p2p0, true
D/Tethering( 2165): interfaceStatusChanged p2p0, true
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
I/wpa_supplicant( 1602): Skip scan -> bUseNetwork false !!!!!!!!!!!!!!!!!!!!!
E/Sensors ( 2165): accelHandler -0.449066 5.888155 7.370673
E/SMD     (  180): DCD ON
W/SignalStrength( 2165): getGsmLevel=3
W/SignalStrength( 2165): getLevel=3 (SignalStrength: 10 0 -120 -160 -120 -1 -1 99 2147483647 2147483647 2147483647 2147483647 gsm|lte 0x3)
W/SignalStrength( 2277): getGsmLevel=3
W/SignalStrength( 2277): getLevel=3 (SignalStrength: 10 0 -120 -160 -120 -1 -1 99 2147483647 2147483647 2147483647 2147483647 gsm|lte 0x3)
W/SignalStrength( 2277): getGsmLevel=3
W/SignalStrength( 2277): getLevel=3 (SignalStrength: 10 0 -120 -160 -120 -1 -1 99 2147483647 2147483647 2147483647 2147483647 gsm|lte 0x3)
D/STATUSBAR-NetworkController( 2277): onSignalStrengthsChanged signalStrength=SignalStrength: 10 0 -120 -160 -120 -1 -1 99 2147483647 2147483647 2147483647 2147483647 gsm|lte 0x3 level=3
W/AlarmManager( 2165): FACTORY_ON= 0
W/SignalStrength( 2165): getDbm 1
W/SignalStrength( 2165): getGsmDbm=-93
W/SignalStrength( 2165): getDbm=-93
W/SignalStrength( 2165): getAsuLevel 1
W/SignalStrength( 2165): getGsmAsuLevel=10
W/SignalStrength( 2165): getAsuLevel=10
I/p2p_supplicant( 1641): Trying to associate with 01.B7.8A (SSID='DIRECT-IBTest' freq=2437 MHz rssi=-48dBm)
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
I/p2p_supplicant( 1641): Associated with 01.B7.8A
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
I/p2p_supplicant( 1641): p2p-wlan0-0: CTRL-EVENT-EAP-STARTED EAP authentication started
I/p2p_supplicant( 1641): p2p-wlan0-0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=14122 method=1
I/p2p_supplicant( 1641): p2p-wlan0-0: CTRL-EVENT-EAP-METHOD EAP vendor 14122 method 1 (WSC) selected
E/SMD     (  180): DCD ON
I/p2p_supplicant( 1641): p2p-wlan0-0: WPS-CRED-RECEIVED
I/p2p_supplicant( 1641): p2p-wlan0-0: WPS-SUCCESS
I/p2p_supplicant( 1641): p2p0: P2P-GROUP-FORMATION-SUCCESS
I/p2p_supplicant( 1641): p2p-wlan0-0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
D/WifiP2pService( 2165): GroupNegotiationState{ what=147483 }
D/WifiP2pService( 2165): GroupNegotiationState go success
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
I/p2p_supplicant( 1641): Disassociation notification
I/p2p_supplicant( 1641):  * reason 0 (locally generated)
I/p2p_supplicant( 1641): CTRL-EVENT-DISCONNECTED bssid=00.00.00 reason=0
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
I/p2p_supplicant( 1641): Trying to associate with 01.B7.8A (SSID='DIRECT-IBTest' freq=2437 MHz rssi=-50dBm)
I/p2p_supplicant( 1641): Associated with 01.B7.8A
I/p2p_supplicant( 1641): CTRL-EVENT-CONNECTED - Connection to 01.B7.8A completed (auth) [id=0 id_str=]
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
I/p2p_supplicant( 1641): P2P-GROUP-STARTED p2p-wlan0-0 client ssid="DIRECT-IBTest" freq=2437 passphrase="" go_dev_addr=01.B7.8A
D/WifiP2pService( 2165): GroupNegotiationState{ what=147485 }
D/WifiP2pService( 2165): GroupNegotiationState group started
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
I/p2p_supplicant( 1641): Disassociation notification
I/p2p_supplicant( 1641):  * reason 2
I/p2p_supplicant( 1641): CTRL-EVENT-DISCONNECTED bssid=01.B7.8A reason=2
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
I/p2p_supplicant( 1641): P2P: [EVENT_DEAUTH] Removing P2P_CLIENT virtual intf.
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceLinkStateChanged p2p-wlan0-0, true
D/Tethering( 2165): interfaceStatusChanged p2p-wlan0-0, true
D/WifiStateMachine( 2165): WifiManager.SEC_COMMAND_ID_SET_WIFI_ENABLED_WITH_P2P mSkipScanAssoc : false
D/WifiNative( 2165): callSECApiBoolean - ID [13]
E/WifiHW  ( 2165): ##################### set firmware type 0 #####################
D/WifiStateMachine( 2165): setWifiEnabled : WifiNative.setFwType(0)
E/WifiService( 2165): WiFi Eanbled with p2p -> disable
D/WifiP2pService( 2165): GroupCreatedState
I/dhcpcd  ( 5222):  dhcp main start 
I/dhcpcd  ( 5222): get_bssidinfo p2p-wlan0-0 failed
I/p2p_supplicant( 1641): p2p0: P2P-GROUP-REMOVED p2p-wlan0-0 client reason=UNAVAILABLE
W/dalvikvm( 2165): threadid=49: thread exiting with uncaught exception (group=0x41df8438)
D/WifiP2pService( 2165): GroupCreatedState{ what=147486 }
E/WifiP2pService( 2165): GroupCreatedState group removed
E/android.os.Debug( 2165): !@Dumpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_sys_error
E/AndroidRuntime( 2165): *** FATAL EXCEPTION IN SYSTEM PROCESS: WifiP2pService
E/AndroidRuntime( 2165): java.lang.NullPointerException
E/AndroidRuntime( 2165):     at android.net.wifi.p2p.WifiP2pService$P2pStateMachine$GroupCreatedState.processMessage(WifiP2pService.java:1925)
E/AndroidRuntime( 2165):     at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:895)
E/AndroidRuntime( 2165):     at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:756)
E/AndroidRuntime( 2165):     at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 2165):     at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 2165):     at android.os.HandlerThread.run(HandlerThread.java:60)

--
You received this message because you are subscribed to the Google Groups "android-platform" group.

To view this discussion on the web visit https://groups.google.com/d/msg/android-platform/-/61IpKgejsMIJ.

[Mike Hsu]

Hi othy74,

I also meet Wifi-direct connection fail problem between one android device as source and another android device as sink.
Did you already fix the problem? By your comments, is deleting all configured AP's on the device?
If yes, could you share how to do?

Thank you!
Mike

othy74於 2012年7月8日星期日UTC+8上午6時28分33秒寫道：

[ac field]

Hi all,

I'm sorry if I'm annoying, but I cannot find a solution to my problem.

I'm working on an app using wifi direct protocol. I need to debug WifiP2pService class of android framework, using eclipse on a windows computer. Unfortunately this class doesn't appear in .jar library even though the source code folder

sdk\sources\android-19\android\net\wifi\p2p

contains the WifiP2pService.class file.

Does someone know how i can debug such class?

thanks for your time