Closed Bug 905598 Opened 11 years ago Closed 11 years ago

UX for bug 892165 BT AVRCP1.3 Profile

Categories

(Firefox OS Graveyard :: Bluetooth, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jcheng, Unassigned)

References

Details

(Whiteboard: [u=devices c=BT p=0] )

This bug track UX work for AVRCP 1.3
Blocks: 905599
Whiteboard: [u= c= p=0]
Whiteboard: [u= c= p=0] → [u=devices c=BT p=0]
From Eric: ni? UX

As for AVRCP, it's a protocol which can let remote Bluetooth devices (usually
Bluetooth headsets, Bluetooth speakers and Bluetooth Carkits) users control
the media player on FxOS devices, namely Music app. AVRCP is always connected
after A2DP connection has been established, so we can regard AVRCP and A2DP as
the same connection.

AVRCP has two main versions: 1.0 and 1.3. AVRCP 1.0 defines basic media control
operations, including:

  Pause, Play, PlayPause, Stop, Rewind, FastFoward, NextTrack, PreviousTrack

When Gecko Bluetooth receives these commands sent from the remote Bluetooth AVRCP
device, it will notify Music app, and Music app has to take corresponding actions.

Furthermore, AVRCP 1.3 defines how to update media metadata to the remote AVRCP
device so that the remote device will be capable of showing the information of
the media if it has LCD.
Flags: needinfo?(firefoxos-ux-bugzilla)
Hi Joe - I understand what the protocol is, but the UX need is not clear. From this description, it sounds like the Music app (Gaia layer) needs to understand what it gets from Gecko, which would be for a Gaia engineer. 

It does not sound like the Music app UI (i.e. pause, play, etc.) will need to change. The Music app has those controls today, so unless the UX is changing, I don't think any specs or design work is needed here. Please let me know if you think the UI *does* need to change. Thanks!
Flags: needinfo?(firefoxos-ux-bugzilla)
hi Dominic, if you feel like you can work on AVRCP v1.3 without further UX clarifications, let's just close this UX bug. thanks
Flags: needinfo?(dkuo)
Currently I am assuming the default remote controlling behaviours are the same as controlling by fingers from the UI, so let's close this first. We can file bugs later if we encounter some conditions that we didn't consider.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(dkuo)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.