Implement standalone bluetooth agent handler
Bug #1492892 reported by
Simon Fels
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Confirmed
|
High
|
Alejandro J. Cura | ||
bluez (Ubuntu) |
Invalid
|
Undecided
|
Simon Fels | ||
indicator-bluetooth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
ubuntu-system-settings (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Currently the settings app registers an agent instance against BlueZ which can only be triggered when the application is currently active. To provide a better user experience we need a different place to implement the agent to have it running in the background all the time. indicator-bluetooth sounds like a suitable component for this but we need to sort out how we present the different user interface screens (trusted helper, notifications, units8, ....).
affects: | ubuntu-system-settings (Ubuntu) → canonical-devices-system-image |
Changed in bluez (Ubuntu): | |
assignee: | nobody → Simon Fels (morphis) |
tags: | added: bluez5 |
tags: |
added: after-bluez5 removed: bluez5 |
Changed in canonical-devices-system-image: | |
assignee: | nobody → John McAleely (john.mcaleely) |
milestone: | none → backlog |
status: | New → Confirmed |
To post a comment you must log in.
seems the work here is to refactor the code from the BT settings page to the indicator service so an agent is always running
this could potentially solve some current connection problems where devices complete the process in multiple steps