921927 - [Bluetooth] The headset can't connect with headset automatically if settings app does not run up

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[[e-mail], [e-mail]]

Settings app has the ability to restore connection for headset. But there is no this mechanism in System app. The issue is happened when Settings app is closed. So, could Gecko::Bluetooth have the ability to handle restore connection? or Gaia::System need to support it as Settings app.

Comment 1

[[e-mail], [e-mail]]

Note: The issue discussion is coming from https://bugzilla.mozilla.org/show_bug.cgi?id=872976#c68.

Comment 2

[(inactive after 6/18) Alive Kuo [:alive]]

I prefer let gecko do this.

Comment 3

[Eric Chou [:ericchou] [:echou]]

If it's implemented in Gecko, it means that the "Enabling Bluetooth" procedure would implicitly include the flow of restoring connection. Several drawbacks came up to my mind if we solve this in Gecko:

  1. With current implementation, if you turn off Bluetooth when there is a connection and restart the phone, enable Bluetooth once the phone is ready, the connection will still be restored. It means that the "last connected device" has to be kept in the database. It's more reasonable if we need to save something in Gaia than in Gecko.
  2. It will make communication between Gecko and Gaia more complicated. Assume we will start to connect with the last connected device right after Bluetooth turned on, Gaia UI needs to tell users "yes, we are connecting". That represents we need additional notifications to inform Gaia about the process of the connection, so we may need an additional "bluetooth-start-connecting" system message or an event for this case.
  3. If developers would like to change the mechanism of restore connection (for instance, bug 872976 comment 46), they have to deal with Gecko.

Currently restore connection has been implemented in Settings and it works fine. If the reason of moving it to Gecko is only because System app has to implement once again, another choice might be extracting that same part of code and put it to somewhere in Gaia.

Comment 4

[(inactive after 6/18) Alive Kuo [:alive]]

I am on the side of 'try not putting everything in system' but if this is unavoidable, let's do it...

1) Move the restore machenism in system app and restore connection via asyncStorage ? or mozSettings ?
2) Remove the restore logic in settings app

Comment 5

[Arthur Chen [:arthurcc][inactive after 6/30]]

Just want to add some infos to the description of this issue. There are two directions of reconnection:
1. The headset tries to reconnect to the phone when the headset is turned on.
2. The phone tries to reconnect to the previous connected headset when bluetooth turns enabled.

The first direction works well and the second one is only supported when users turn on bluetooth via the settings app.

Comment 6

[Evelyn Hung]

(In reply to Alive Kuo [:alive] from comment #4)
> I am on the side of 'try not putting everything in system' but if this is
> unavoidable, let's do it...
> 
> 1) Move the restore machenism in system app and restore connection via
> asyncStorage ? or mozSettings ?
> 2) Remove the restore logic in settings app

Move the restore mechanism from Setting to System. The way to restore connection is storing last connected headset via asyncStorage.

Comment 7

[BMO Automation]

Firefox OS is not being worked on