ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #14484
Re: RFC- Having a bluetooth service to handle pairing
Hi,
thanks a lot for starting this topic. IMO this is very needed. At latest
when we want to implement OBEX Object PUSH, MAP or PBAB, the BlueZ
architecture would require some running service anyways. IMO that could
be all part of the same Bluetooth service.
Br,
Michael
On 28.07.2015 16:14, Sebastien Bacher wrote:
> Hey there,
>
> Currently the only bluetooth agent available in ubuntu touch is
> implemented in system settings. Which means the settings application
> need to be open for bluetooth pairing to work.
>
> We received some bugs reports suggesting that the is a need for having
> request handled at any time because that's the most robust things to do
> and the less confusing for users (ideally known/trusted device would
> always be able to auto reconnect, but it seems that in practice sometime
> the trusted link is lost and the system need to prompt again, also other
> action are done in settings which make the pairing less reliable)
> https://launchpad.net/bugs/1474296
>
> To address this issue we are thinking about moving the auth agent out
> from system settings to be a standalone service. We are going to start
> working on that but wanted to check first if anyone feeling strongly
> against it. The service might lead to a bit more power usage, but it
> would only be active if bluetooth is on and things like visibility would
> probably be configurable as well.
>
> (oh, we also though about adding the agent to indicator-bluetooth which
> would make sense, but that is currently discarded for practical reason,
> the existing indicator-bluetooth and agent code are using different
> language/toolkits and we don't want to rewrite either at the moment)
>
> What do you think?
>
> Cheers,
> Sebastien Bacher
>
>
>
>
>
>
Attachment:
signature.asc
Description: OpenPGP digital signature
Follow ups
References