Music player is not autostarted when a play command is issued
Bug #1524017 reported by
Michael Zanetti
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Confirmed
|
Wishlist
|
Unassigned | ||
media-hub (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
A play command can be issued with:
* the sound indicators playback controls
* Bluetooth and wired headsets with controls
* Bluetooth car kits
* SmartWatches etc
However, currently those only work if the music app is up and running already. Additionally exactly those are the use cases when the user doesn't want to pull out the phone from the pocket just to start it. If no active playback source is currently registered at media hub, it should launch the music player and continue playing from the last state. In the future, we might want to have a way to allow the user changing the default music app to e.g. make it launch PodBird instead.
Changed in canonical-devices-system-image: | |
assignee: | nobody → John McAleely (john.mcaleely) |
importance: | Undecided → Wishlist |
milestone: | none → backlog |
status: | New → Confirmed |
Changed in canonical-devices-system-image: | |
assignee: | John McAleely (john.mcaleely) → nobody |
To post a comment you must log in.
As a smatwatch user and headset with built-in control user, I +1 this bug as launching the default music app and then apply the 'play' is the expected behavior when using the play/pause button when the default music app is not yet launched.