1119853 - WiFi Direct is flaky and requires device rebooting after first or second connection

Status: RESOLVED DUPLICATE of bug 1124507

(Firefox OS Graveyard :: Wifi, defect)

Description

[Doug Sherk (:drs) (inactive)]

Tested on Flame, v188, master Gecko/Gaia.

I'm finding that WiFi Direct is very flaky. After 1-2 connections, the devices have to be rebooted, or they can't connect. At this point, if we attempt to connect in software, they fail and disconnect. After rebooting, it works on the first shot.

Comment 1

[Doug Sherk (:drs) (inactive)]

Henry, is there any info I could provide here that would be helpful?

Comment 2

[Henry Chang [:hchang]]

Hi Doug,

Could you provide the app that you tested with? Thanks :)

Comment 3

[Vincent Chang[:vchang][changyihsin]]

Henry will help to fix the problem. It would be nice if you can provide detail STRs. We can help to reproduce the problem following your STRs.

Comment 4

[Guillaume Marty [:gmarty]]

I have identified the following issue:
1. I launch an app and connect my devices together.
2. navigator.mozWifiP2pManager.groupOwner is populated with the relevant data.
3. I kill and relaunch the app one of the devices. OR I reflash the app using the WebIDE.
4. navigator.mozWifiP2pManager.groupOwner is now null.

Though the connected state is maintained across sessions, the value of navigator.mozWifiP2pManager.groupOwner is not persisted.

What do you think Henry?

Comment 5

[Henry Chang [:hchang]]

(In reply to Guillaume Marty [:gmarty] from comment #4)
> I have identified the following issue:
> 1. I launch an app and connect my devices together.
> 2. navigator.mozWifiP2pManager.groupOwner is populated with the relevant
> data.
> 3. I kill and relaunch the app one of the devices. OR I reflash the app
> using the WebIDE.
> 4. navigator.mozWifiP2pManager.groupOwner is now null.
> 
> Though the connected state is maintained across sessions, the value of
> navigator.mozWifiP2pManager.groupOwner is not persisted.
> 
> What do you think Henry?

I think I know how to fix this up. I'll file another bug to address this 
concrete issue.

Thanks!

Comment 6

[Henry Chang [:hchang]]

Just filed Bug 1124507 to address the issue described in comment 4

Comment 7

[Guillaume Marty [:gmarty]]

Another thing I've noticed is that `navigator.mozWifiP2pManager.enabled` is always false, even if you do `setScanEnabled(true)`, even if you're connected to a peer.

It's not a big bug as long as we know that this property isn't reliable, but still needs to be fixed.
Henry do we need to fix this property or completely remove it?

Comment 8

[Henry Chang [:hchang]]

(In reply to Guillaume Marty [:gmarty] from comment #7)
> Another thing I've noticed is that `navigator.mozWifiP2pManager.enabled` is
> always false, even if you do `setScanEnabled(true)`, even if you're
> connected to a peer.
> 
> It's not a big bug as long as we know that this property isn't reliable, but
> still needs to be fixed.
> Henry do we need to fix this property or completely remove it?

I've got the spot of the bug and it's a duplicate of Bug 1124507.
Will fix it in that bug.

Thanks :)