If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[Ringtones] Do not show secondary information based on metadata (artist/source) on "Manage Tones"



Firefox OS
3 years ago
3 years ago


(Reporter: Alison Shiue, Unassigned)


Firefox Tracking Flags

(Not tracked)



(3 attachments)



3 years ago
Created attachment 8482596 [details]

Gaia      e7d31f0e9b6b19d9b484eeec8fb980718bc40d79
Gecko     https://hg.mozilla.org/mozilla-central/rev/532b5fb77ba1
BuildID   20140901160203
Version   34.0a1
Base image v123

1. Insert a SD card with a song(MP4_AAC(Audio) with secondary information under /Ringtones folder
2. Go to Settings -> Sound
3. Under the "Tones" category, select "Manage Tones"
4. Check the song

Expect result:
Display Filename of ringtone and secondary information based on metadata (artist/source)

Actual result:
Do not show secondary information

Comment 1

3 years ago
Created attachment 8482598 [details]
MP4_AAC (Audio).m4a

Test source


3 years ago
QA Whiteboard: [COM=Gaia::Ringtones]

Comment 2

3 years ago
The UX spec for this shows the filenames instead of the metadata. We never planned on showing metadata for SD card ringtones, since that would require the ringtones app to understand how to read the various metadata formats, which is a lot of code for something that I don't think is super-valuable.

Comment 3

3 years ago
Created attachment 8483194 [details]
[2.1] Ringtones TransferSDCard.pdf

Since I found the spec on UX doc page 6, "Display Filename of ringtone and if/when
possible secondary information based on metadata (artist/source)", ni? UX for checking this design.
Flags: needinfo?(kcaldwell)

Comment 4

3 years ago
Thanks for checking in with UX on this, for 2.1 - ringtones from SD Card will display source (SD Card) and for ringtones from music, will display artist metadata (made available from music app). Please note: we do plan to revisit this in the future.
Flags: needinfo?(kcaldwell)

Comment 5

3 years ago
Based on comment 4, since this behavior is intentional, I'm marking this WONTFIX. If we do decide to revisit this in the future, I expect we'll do something different altogether and file a new bug.
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.