Closed
Bug 820634
Opened 13 years ago
Closed 13 years ago
Selected ringtone not being honored
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect, P1)
Tracking
(blocking-basecamp:+)
People
(Reporter: marcia, Assigned: alive)
References
Details
(Keywords: regression, unagi)
Attachments
(2 files)
Seen while running unagi using
Gaia: bf21e0c83930
Gecko: f1c0c74ea9f5
STR:
1. Set a ringtone in settings
2. Call you phone
Expected: I would hear the selected ring tone
Actual: It defaults back to classic prism
Updated•13 years ago
|
Comment 1•13 years ago
|
||
P1+C3 because smoketest blocker.
Priority: P2 → P1
Target Milestone: --- → B2G C3 (12dec-1jan)
Comment 3•13 years ago
|
||
More than happy to take a look at this. Right now I'm still waiting to get my SIM card in the mail though. I'll see if I can test this with one of my existing SIM cards though.
Comment 4•13 years ago
|
||
Marcia, are you still seeing this? Works for me in the 12/13 nightly.
Keywords: qawanted
| Reporter | ||
Comment 5•13 years ago
|
||
Dylan: This is working for me using today's build. Resolving as WFM.
(In reply to Dylan Oliver [:doliver] from comment #4)
> Marcia, are you still seeing this? Works for me in the 12/13 nightly.
Status: NEW → RESOLVED
blocking-basecamp: + → ---
Closed: 13 years ago
Keywords: qawanted
Resolution: --- → WORKSFORME
I'm seeing issues with the ring tones in today's build 12/21
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
This occurs when I select Wind chimes. There might be some other ones. Certain ones do seem to sound.
Comment 8•13 years ago
|
||
Looks like every ringtone except the wind chimes works for me. It appears that there is a filename mismatch currently. I'm testing it out now, but the fix should be pretty simple. Would nominate that we block for this.
This new issue is different than the originally reported issue, but still related to ringtones.
blocking-basecamp: --- → ?
Comment 9•13 years ago
|
||
Attachment #694988 -
Flags: review?
Comment 10•13 years ago
|
||
I don't think we'd block on this one but would definitely take the fix after review.
On today's build I'm not able to exit the ringtone select screen if I choose wind chimes, so if that's the behavior it does suck but you aren't going to end up in a situation where your phone doesn't ring.
Updated•13 years ago
|
tracking-b2g18:
--- → +
Comment 11•13 years ago
|
||
Removing smoketest -- this bug has morphed into something less serious since that tag was applied.
Keywords: smoketest
Comment 12•13 years ago
|
||
WORKSFORME with changeset
gecko-b2g18: b27b0eadf48c
gaia: 2d8eee9753ad7d3ee1c74ec99e2b6629c35e3f99
Please renominate if needed
blocking-basecamp: ? → -
Comment 13•13 years ago
|
||
Hi David,
I'm still seeing the broken ringtone with fresh builds of B2G/gaia on master branch. Did you specifically test the "Wind Chimes" ringtone?
I'd really like to see this one land if possible - the fix is extremely simple (one character), and has no possible regressions. It just feels very wrong to ship with a broken feature, and is extremely jarring if I'm going down the list listening to all ringtones and one does not work.
blocking-basecamp: - → ?
Comment 14•13 years ago
|
||
Triage: comment 13 seem to be different from what this bug is originally reporting. Should be a different issue.
Comment 16•13 years ago
|
||
Triage: BB+, P3, C3 - confuses the user on whether their ringtone is set or not. even if they check the UI, it seems like the ringtone is correctly chosen but actually not.
Updated•13 years ago
|
blocking-basecamp: ? → +
tracking-b2g18:
+ → ---
Comment 17•13 years ago
|
||
Comment on attachment 694988 [details]
Github pull request pointer
Just looking for a quick review for this one character change, thanks!
Attachment #694988 -
Flags: review?(etienne)
Attachment #694988 -
Flags: review?(21)
Attachment #694988 -
Flags: review?
Comment 18•13 years ago
|
||
Comment on attachment 694988 [details]
Github pull request pointer
Kevin is fixing one of the issue, this can be a good part 1 patch.
The underling issue is about the behavior of [OK] on the top right and the [Back] on the top left of the selection dialog.
- If the user hits back, we should revert the selection when the user goes into the panel dialog again since the selection is not saved into the database
- Only if the user hits OK we should update the database and the selection when the user enter the panel next time.
It's really not hard, but the current Settings app dialog behavior is really messy....
Attachment #694988 -
Flags: review?(etienne)
Attachment #694988 -
Flags: review?(21)
| Assignee | ||
Updated•13 years ago
|
Assignee: kgrandon → alive
| Assignee | ||
Comment 19•13 years ago
|
||
Patch v1:
1. Reset ringtone preview when leaving sound selection panel
2. Reactivate ringtone selection when entering sound selection panel
3. Uh, there's no stop() function in audio element....fix it.
Attachment #695702 -
Flags: review?(ehung)
Comment 20•13 years ago
|
||
Comment on attachment 695702 [details]
https://github.com/mozilla-b2g/gaia/pull/7187
r=me, I trust your manual tests!
Attachment #695702 -
Flags: review?(ehung) → review+
| Assignee | ||
Comment 21•13 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Comment 22•13 years ago
|
||
Defect is verified as fixed using Unagi, build 20130103070201
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•