Closed
Bug 811087
Opened 13 years ago
Closed 13 years ago
[sms] No sound is played when receiving a text message with vibration and sound enabled
Categories
(Firefox OS Graveyard :: Gaia::SMS, defect, P1)
Tracking
(blocking-basecamp:+)
People
(Reporter: marcia, Assigned: etienne)
References
Details
(Keywords: regression, smoketest, unagi)
Bug 807918 is back using today's build - found during the smoketest:
Tested with:
Gecko-11e6372e034f7f19ad0b39749b48425a462120af
Gaia-92b7a950de3ec1cdecd90fb9d2cd7f930bb1f227
STR:
1-In Settings, confirm that ring and vibrate are on, as well as the alerts box is checked.
2-Send a text message from another phone
3-Receive a text message with vibration and sound enabled
Expected result --> Device vibrates and default sound is played
Actual result --> Device vibrates but no sound is played
Bug 809680 - Notification should come up with a sound. ?
Though vibration should also be included.
| Reporter | ||
Comment 2•13 years ago
|
||
When I have tested this before, when you get an SMS there was some kind of default system sound that was made - today that is not happening. The specific smoketest that covers this is:
[SMS] Receive a sms with vibration and sound (device unlocked) & confirm notification
So perhaps something changed, but if so we will have to adjust the smoketest to reflect that.
Comment 3•13 years ago
|
||
(In reply to Marcia Knous [:marcia] from comment #2)
> When I have tested this before, when you get an SMS there was some kind of
> default system sound that was made - today that is not happening. The
> specific smoketest that covers this is:
>
> [SMS] Receive a sms with vibration and sound (device unlocked) & confirm
> notification
>
> So perhaps something changed, but if so we will have to adjust the smoketest
> to reflect that.
You are right, the sms sound is temporarily removed, and later would be merged into notification sounds.
Comment 4•13 years ago
|
||
:alive, is there a reason for temporarily removing this? sounds like this has been done intentionally.
Depends on: 801351
Comment 5•13 years ago
|
||
I have been told that it will be fixed by bug 801351
| Assignee | ||
Updated•13 years ago
|
Assignee: nobody → etienne
Updated•13 years ago
|
Component: Gaia → Gaia::SMS
Comment 6•13 years ago
|
||
Marking for C2, given this meets the criteria of known P1/P2 blocking-basecamp+ bugs at the end of C1.
Target Milestone: --- → B2G C2 (20nov-10dec)
Comment 7•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 8•13 years ago
|
||
In today's version the bug it's not resolved
Gecko-04c2d4f
Gaia-1087df8
| Reporter | ||
Comment 9•13 years ago
|
||
Using:
Gaia: 1910ebaae9bda968f7da6b0ed42eef906013af30
Gecko: 72dbb825d86b5d003929c3ee1efe1187abd3646e
I now am getting the sound again.
| Reporter | ||
Comment 10•13 years ago
|
||
Verified fixed using the build in Comment 9.
Status: RESOLVED → VERIFIED
Updated•13 years ago
|
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Comment 11•13 years ago
|
||
David did you change the the RESOLVED -> REOPENED by mistake?
Comment 12•13 years ago
|
||
Per dev-gaia, I think he was suggesting that this has regressed. I filed bug 819259, since reopening a FIXED bug is generally not a good idea (makes the bug history very confusing).
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•