797281 - [Settings][bluetooth] Only allow one device to be connected at a time.

Status: VERIFIED FIXED

(Firefox OS Graveyard :: Gaia, defect)

Description

[Evelyn Hung]

Per platform implementation, only one device can be connected (Handsfree) at a time, so need Gaia prompts alert to notify user that he is trying to connect another device and will disconnect the original one.

Comment 1

[Evelyn Hung]

Attachment: this patch implement request from platform: only allow one device connected at a time.

Comment 2

[Tim Guan-tin Chien [:timdream] (please needinfo)]

Let's make sure we can land this by getting approval to land or blocking+ first.

Comment 3

[Alex Keybl [:akeybl]]

Needs product input before deciding on blocking+/-. Is the plan to have only one handsfree allowed at a time clee?

Comment 4

[Chris Lee [:clee]]

My understanding was that the device can only connect to one device at a time.  Are we able to connect to 2 handsfree devices concurrently?

If the above is true and only one device can be connected at once, is UI necessary or can we just swap over to the new device?

Comment 5

[Mark Finkle (:mfinkle) (use needinfo?)]

We need some more info from the platform side to figure out the answers to comment 4.

Comment 6

[Evelyn Hung]

(In reply to Chris Lee [:clee] from comment #4)
> My understanding was that the device can only connect to one device at a
> time.  Are we able to connect to 2 handsfree devices concurrently?
> 
No, only one handsfree device at a time.
> If the above is true and only one device can be connected at once, is UI
> necessary or can we just swap over to the new device?
Now we just swap over to the new one without any alert prompted. Need UX confirm this is acceptable.

Comment 7

[Mark Finkle (:mfinkle) (use needinfo?)]

Larissa - Can you give some UX feedback on the design?

Comment 8

[Evelyn Hung]

(In reply to Mark Finkle (:mfinkle) from comment #7)
> Larissa - Can you give some UX feedback on the design?
Let's landed this patch so QA can test this.
If Larissa has UX comments on switch device connection, please file a issue to track it.
Thanks!

Comment 9

[Larissa Co [:lco]]

Just checking: this only applies to hands-free devices (i.e. headsets), right? Could I potentially connect to a bluetooth keyboard and a headset at the same time? Or is there still going to be a conflict? What about the case where I'm paired with someone else's phone and someone else tries to pair with me? I won't be able to pair with both at the same time, presumably.

As for UX input:
I agree, let's swap them for now without feedback and see if this is acceptable. The heuristic for determining that the user wants to swap devices should be that:

1. The user is currently connected to device A
2. The user tries to connect to device B (from the phone or from device B)
3. The user is disconnected from A and connected to B. Disconnection from A means that A's state in the settings page shows that it's paired, but not connected.e

Comment 10

[Evelyn Hung]

(In reply to Larissa Co from comment #9)
> Just checking: this only applies to hands-free devices (i.e. headsets),
> right? Could I potentially connect to a bluetooth keyboard and a headset at
> the same time? Or is there still going to be a conflict? What about the case
> where I'm paired with someone else's phone and someone else tries to pair
> with me? I won't be able to pair with both at the same time, presumably.
For v1, we only can connect to headsets, one at a time. But we can pair with many devices, so we probably could share file with them (if they are phones, computers, ...etc).
So:
For connection: paired headset only, one at a time. (it's what this issue focuses)
For file sharing: device that we've paired and allow file sharing connection. (this feature is not in Settings App, but in Bluetooth File Sharing App)
For pairing: any device, if any one requests pairing and user accepts, go into pairing process.
> 
> As for UX input:
> I agree, let's swap them for now without feedback and see if this is
> acceptable. The heuristic for determining that the user wants to swap
> devices should be that:
> 
> 1. The user is currently connected to device A
> 2. The user tries to connect to device B (from the phone or from device B)
> 3. The user is disconnected from A and connected to B. Disconnection from A
> means that A's state in the settings page shows that it's paired, but not
> connected.
Yes, that's what I currently implemented.

Thanks!

Comment 11

[Tim Guan-tin Chien [:timdream] (please needinfo)]

https://github.com/mozilla-b2g/gaia/pull/5675

Merged. Thanks.

Comment 12

[cbarker]

Verified Fixed in Unagi Build 20130102070202