Closed
Bug 1026276
Opened 10 years ago
Closed 10 years ago
[B2G][Settings][Ringtones]Newly created custom ringtone doesn't immediately appear in Manage Ringtones area
Categories
(Firefox OS Graveyard :: Gaia::Ringtones, defect)
Tracking
(blocking-b2g:2.0+, b2g-v2.0 fixed, b2g-v2.1 fixed)
People
(Reporter: mclemmons, Assigned: squib)
References
()
Details
(Whiteboard: [2.0-flame-test-run-2])
Attachments
(1 file)
(deleted),
text/plain
|
Details |
User taps Settings App and selects Sound under Personalization section. Beneath Manage Sounds, user selects Manage Ringtones. When user selects the '…' option to right of Firefox ringtone options (i.e. Classic Prism), user has option to Share ringtone. When this option is chosen, user selects Ringtones and saves on the Create Ringtone screen. After receiving the notification, user is taken back to the Manage Ringtones screen. However, the new ringtone doesn't appear in the Custom section. User has to left arrow out of Manage Ringtones and select Manage Ringtones again to see the newly created custom ringtone selection.
Repro Steps:
1) Update a Flame to 20140616000203
2) Tap Settings, select Sound
3) Tap Manage Ringtones and select the '…' option to the right of any Ringtone
4) Select Share Ringtone, then select the Ringtones option
5) Select Save in upper right corner and observe device behavior
Actual:
User is taken back to the Manage Ringtones screen. However, the new ringtone doesn't appear in the Custom Ringtones section. User has to left arrow out of Manage Ringtones and select Manage Ringtones again to see the newly created custom ringtone selection.
Expected:
User is taken back to the Manage Ringtones screen with the Custom Ringtone selection displayed.
Notes:
Repro frequency: (10/10, 100%, etc.)
See attached: (video clip = https://www.youtube.com/watch?v=TAjCJYhAxg0 logcat, etc.)
Unable to provide Flame logcat due to issue reporteed at https://bugzilla.mozilla.org/show_bug.cgi?id=1010993.
Issue reproduces on the Open C and attached logcat is from the 2.1 Open C.
Environmental Variables:
Device: Flame 2.0
Build ID: 20140616000203
Gaia: a6988c15b361938bea5976c846c147ecdc1121c0
Gecko: 52a276202888
Version: 32.0a2 (2.0)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Reporter | ||
Comment 1•10 years ago
|
||
This issue reproduces on 2.1 Flame, 2.1 Buri, Open C 2.1, Open C 2.0, and 2.0 Buri following the STR from Comment 0. User is taken back to the Manage Ringtones screen. However, the new ringtone doesn't appear in the Custom Ringtones section. User has to left arrow out of Manage Ringtones and select Manage Ringtones again to see the newly created custom ringtone selection appear for all of the above mentioned devices/builds.
Environmental Variables:
Device: Flame 2.1 - Master
Build ID: 20140616040202
Gaia: dfc4703bb81d1fa4f2087a1a6124b47a80a5d1de
Gecko: 80431d4fd0da
Version: 33.0a1 (2.1 - Master)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Buri 2.1
Environmental Variables:
Device: Buri 2.1 - Master
Build ID: 20140615103005
Gaia: dfc4703bb81d1fa4f2087a1a6124b47a80a5d1de
Gecko: 80431d4fd0da
Version: 33.0a1 (2.1 - Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Open C
Environmental Variables:
Device: Open_C 2.1 - Master
Build ID: 20140616040202
Gaia: dfc4703bb81d1fa4f2087a1a6124b47a80a5d1de
Gecko: 80431d4fd0da
Version: 33.0a1 (2.1 - Master)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Open C
Environmental Variables:
Device: Open_C 2.0
Build ID: 20140616000203
Gaia: a6988c15b361938bea5976c846c147ecdc1121c0
Gecko: 52a276202888
Version: 32.0a2 (2.0)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Environmental Variables:
Device: Buri 2.0
Build ID: 20140616063005
Gaia: a6988c15b361938bea5976c846c147ecdc1121c0
Gecko: f2413cf1965e
Version: 32.0a2 (2.0)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Reporter | ||
Comment 2•10 years ago
|
||
This issue does not reproduce on Buri 1.4 as this feature was not implemented during this build/version.
Environmental Variables:
Device: Flame 1.4
Build ID: 20140616000202
Gaia: 164644d91290708a71436dfdf4301e33b92e2c77
Gecko: 2949e8bef869
Version: 30.0 (1.4)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Comment 3•10 years ago
|
||
Your last comment is missing the environmental variables for Buri 1.4. Also, you stated this issue does not occur on the Buri 1.4 but included the Flame 1.4 environmental variables. What test case does this issue fail? Please fix.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(mclemmons)
Comment 4•10 years ago
|
||
Basic use case with poor UX, so we probably need to get this fixed.
blocking-b2g: --- → 2.0?
Comment 5•10 years ago
|
||
Moving to Ringtones area since it probably fits that better given the recent work done to add this feature.
Component: Gaia::Settings → Gaia::Ringtones
Reporter | ||
Comment 6•10 years ago
|
||
(In reply to ktucker from comment #3)
> Your last comment is missing the environmental variables for Buri 1.4. Also,
> you stated this issue does not occur on the Buri 1.4 but included the Flame
> 1.4 environmental variables. What test case does this issue fail? Please fix.
Correction to Comment 2:
This issue does not reproduce on Flame 1.4 as this feature was not implemented during this build/version. This issue does not fail any particular test case. This was found during exploratory testing around an existing test case.
Environmental Variables:
Device: Flame 1.4
Build ID: 20140616000202
Gaia: 164644d91290708a71436dfdf4301e33b92e2c77
Gecko: 2949e8bef869
Version: 30.0 (1.4)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
Flags: needinfo?(mclemmons) → needinfo?(ktucker)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Updated•10 years ago
|
blocking-b2g: 2.0? → 2.0+
Assignee | ||
Comment 7•10 years ago
|
||
This is fixed by bug 1015513. You should never have been able to share from the ringtones app to itself, so it's no surprise the behavior was bad.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 8•10 years ago
|
||
Jim,
Assigning this to you. Please investigate.
Thanks
Hema
Assignee: nobody → squibblyflabbetydoo
Comment 9•10 years ago
|
||
Maybe I'm missing something here, but if bug 1015513 isn't fixed, this isn't either, is it?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 10•10 years ago
|
||
OK, Jim clarified on IRC that the workaround patch in bug 1015513 fixes this issue, but not the general issue that bug is tracking. I've uplifted that patch to v2.0.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Depends on: 1015513
Resolution: --- → FIXED
Target Milestone: --- → 2.0 S4 (20june)
You need to log in
before you can comment on or make changes to this bug.
Description
•