Closed Bug 820277 Opened 12 years ago Closed 12 years ago

[Dialer] No ring tone for incoming calls when set ring tone is not available anymore

Categories

(Firefox OS Graveyard :: Gaia::Dialer, defect, P1)

Product:
Firefox OS Graveyard
Component:
Gaia::Dialer
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(blocking-basecamp:-)

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-basecamp -

People

(Reporter: whimboo, Assigned: alive)

References

Details

(Keywords: dogfood, regression, unagi)

Attachments

(1 file)

adb logcat output
294.31 KB, text/plain
Details 
As discussed on the b2gtestdriver mailing list we have noticed that for incoming calls no ring tone can be heard. Only the vibration is activated. 

When I connect my unagi device via adb I can see the following error:

E/GeckoConsole(  661): [JavaScript Warning: "HTTP "Content-Type" of
"text/html" is not supported. Load of media resource
app://communications.gaiamobile.org/dialer/oncall.html failed." {file:
"app://communications.gaiamobile.org/dialer/oncall.html#locked" line: 0}]

This was working before so one change caused this problem lately. Would be good to know the regression range.
Seems having the symptom at Bug 820130. Include the related people.
QA Contact: fyen
Triage: This is clearly a blocker if as described.
blocking-basecamp: ? → +
Priority: -- → P1
This needs an owner. Please reassign as you see fit, Alive.
Assignee: nobody → alive
Henrik can you try to go to Settings -> Sound and try to change your ringtones to see if it fixed the issue?
I tried switching to the other two ringtones but neither of them make any sound, just vibrate.
With ADB logcat I saw these messages which might be useful:

> E/AudioPolicyManager(  113): setPhoneState() state 0
> W/AudioPolicyManager(  113): setPhoneState() setting same state 0
> ...
> W/AudioFlinger(  113): Thread AudioOut_1 cannot connect to the power manager service
> E/AudioHardwareMSM76XXA(  113): Parsing error in AudioFilter.csv.
> ...
> E/AudioHardwareMSM76XXA(  113): Parsing error in AudioFilter.csv.
> ...
> W/AudioFlinger(  113): Thread AudioOut_1 cannot connect to the power manager service
> E/AudioHardwareMSM76XXA(  113): Parsing error in AudioFilter.csv.
(In reply to Jared Wein [:jaws] from comment #6)
> E/AudioHardwareMSM76XXA(  113): Parsing error in AudioFilter.csv.

This isn't B2G, but some commenters on this forum [1] had the same issue with their Android hardware and they came to the conclusion of a corrupted update. Maybe that is the reason?

[1] http://forums.androidcentral.com/lg-optimus-s-rooting-roms-hacks/170942-parsing-error-audiofilter-csv.html
That's audio hal requirement file and it control the sound quality, it shouldn't only affect ringtone sound.
I should note that I do get a sound to emit for incoming text messages and missed phone call notifications.
As for a regression range, this worked on the 12/03 build and then stopped working with the 12/06 build on my Unagi phone.
I cannot reproduce with Gecko: 5bad6f1d595945a4b4acc1125447ec0669bf6474
Gaia:  f448522a0f1481c9118519f94dfbc6e29f2a0042

Change the ringtone in settings app also WFM.
Keywords: qawanted
Can not reproduce with unagi_2012-12-11 nightly build.

- Have ring tone for incoming calls ... OK
- Change ring tone in Settings ... OK
- Change the volume of ring tone ... not work (might be Bug 784184 ?)
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
For the comment 11,
I cannot reproduce it for the first incoming call.
In the second incoming call, the call screen won't be showing and ringing again.

For the comment 1,
I think it could not be relative.
Because of the first incoming call is normal with ringtone.
So I was still able to reproduce with the 121211 build on my unagi device. No ring tone even for multiple calls. So I checked the sound settings and most likely no selection was made here. Sorry that I can't say that for sure but I selected the first entry before I realized to check the whole page for the currently set item. Once it has been saved the ring tone is back.

So I believe we somehow lost the setting for the ring tone to use. We shouldn't mark it as WFM until we know why we lost it. Can anyone who also sees this issue check my above assumption? Thansks.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
I've tried changing the ringtone to the other ones and it still doesn't work on my 1206 beta build.

If this is fixed in the 12/11 build, we should still figure out why this broke and get some tests on it since we can't ship a phone with a broken ringer.
After test two unagi cell phones, cannot reproduce with the 20121212 nightly build (build identifier: 20121212080107) in FRESH environment.

However, after run gaiatest, the ringtone doesn't work.
(In reply to Henrik Skupin (:whimboo) from comment #14)
> So I was still able to reproduce with the 121211 build on my unagi device.
> No ring tone even for multiple calls. So I checked the sound settings and
> most likely no selection was made here. Sorry that I can't say that for sure
> but I selected the first entry before I realized to check the whole page for
> the currently set item. Once it has been saved the ring tone is back.
> 
> So I believe we somehow lost the setting for the ring tone to use. We
> shouldn't mark it as WFM until we know why we lost it. Can anyone who also
> sees this issue check my above assumption? Thansks.

I guess the settings has been lost when we introduce the final ringtones. See bug 807431
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WORKSFORME
(In reply to Vivien Nicolas (:vingtetun) from comment #18)
> I guess the settings has been lost when we introduce the final ringtones.
> See bug 807431

Sounds reasonable. But I still wouldn't call this bug resolved yet. Means whenever we rename/delete a ringtone an user has set on his phone the same issue will happen again. We should make sure that we fallback gracefully. I think the default ringtone by the system should be chosen then.
Blocks: 807431
Status: RESOLVED → REOPENED
Keywords: regressionwindow-wanted
Resolution: WORKSFORME → ---
An automated test would also be very appreciated.
Flags: in-testsuite?
(In reply to Henrik Skupin (:whimboo) from comment #19)
> (In reply to Vivien Nicolas (:vingtetun) from comment #18)
> > I guess the settings has been lost when we introduce the final ringtones.
> > See bug 807431
> 
> Sounds reasonable. But I still wouldn't call this bug resolved yet. Means
> whenever we rename/delete a ringtone an user has set on his phone the same
> issue will happen again. We should make sure that we fallback gracefully. I
> think the default ringtone by the system should be chosen then.

I'm fine with keeping it opened. I think my main concern is having this as a blocking-basecamp bug while this is not something that should block the release since it's not a normal behavior and likely require some 'defaults' settings / compatibility scripts that nobody has the time to write for now (since they have no purpose for the release) :(

blocking-basecamp?
blocking-basecamp: + → ?
Sounds fine with me and I agree. Most likely something for post v1.
Summary: [Dialer] No ring tone for incoming calls → [Dialer] No ring tone for incoming calls when set ring tone is not available anymore
I don't follow. If the settings were lost when the ringtones got changed, how come I can't change my ringtone to one of the other values and have it start working again?
Which build are you using Jared? Also do you see any failures via adb logcat?
Flags: in-testsuite? → in-testsuite+
qawanted: try testing around changing the ring tones and changing the prefs.  Comment 17 leads me to believe that default settings will not show this issue.  I believe there might be some other state that's causing the ringtones not to occur.
Flags: in-testsuite+ → in-testsuite?
Attached file adb logcat output — 
(In reply to Henrik Skupin (:whimboo) from comment #24)
> Which build are you using Jared? Also do you see any failures via adb logcat?

I am using the beta 1206 build. I have attached my adb logcat output. I do see the same failures that were mentioned earlier about the failure to load content type "text/html" in oncall.html
Renominate if too many users are impacted
blocking-basecamp: ? → -
Still can not reproduce with:
- unagi_2012-12-16 nightly build (b2g18) + unagi-kernelupdate3.
- unagi_2012-12-16 nightly build (b2g18) + unagi-kernelupdate4.
I got this working with the 12/12 beta build, and it potentially worked before.

I'm pretty sure the problem I ran into was that I was changing my ringtone but not hitting the "Done" button in the top right of the page. Instead I was hitting the back arrow, which apparently didn't save any of my changes. I filed bug 822740 for this usability issue.

Closing.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WORKSFORME
This is not working in the 12/18 build.  in fact there are no ringtones listed in the sounds.

When you click on done after going to the settings and then dial the unagi phone, you get one short lived drop down of the incoming call during the first ring and then it disappears and you do not get a notification of the ring.  Reopening issue.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
It still works for me on 12/18 build from https://releases.mozilla.com/b2g/
If you are using custom build, please using b2g18 gecko branch with master gaia.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WORKSFORME
Just got a phone for dogfooding. By default the sound does not work.
One needs to go to settings and select a ringtone *and remember to press Done*.
Clearly non-optimal UX.
(In reply to Olli Pettay [:smaug] from comment #32)
> Just got a phone for dogfooding. By default the sound does not work.
> One needs to go to settings and select a ringtone *and remember to press
> Done*.
> Clearly non-optimal UX.

I had the same complaint, see bug 822740.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: