1019846 - After making a call to a different device and getting a busy signal the speaker mode turns on by itself

Status: RESOLVED WORKSFORME

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

Description

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

1. from Tarako device, make a call to another device
2. on the other device, hang up

Expected: Tarako does not have speaker mode turned on
Actual: Tarako gets the message that you got a busy signal and speaker mode turns on and an audible busy tone is heard.

Video : http://www.youtube.com/watch?v=E_jj7FnRt1M

Gaia      fbead7b3bafb865fbbf269c6cd53ac1866f64f27
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/dbdc98109fef
BuildID   20140603014004
Version   28.1
ro.build.version.incremental=eng.cltbld.20140603.050805
ro.build.date=Tue Jun  3 05:08:12 EDT 2014
Tarako

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Does not occur with Buri.  I swapped sims to verify.
The dialer closes after being hung up, there is no overlay message, no speaker mode, and no audible busy tone.

Gaia      5bd226b03a2d63dfe9df204f7c0afb9984e8fd42
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3/rev/57cd741e4d0b
BuildID   20140530024008
Version   28.0
ro.build.version.incremental=324
ro.build.date=Thu Dec 19 14:04:55 CST 2013
Buri

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Attachment: logcat.txt

Modified STR:
1. launch dialer
2. make a call from the other phone to this phone and hang up ; this is to place the call in the call log
3. go to the call log
4. select the call from the Tarako phone
5. on the other phone hang up.

Note: make sure the phone number is not associated with a contact.

I found when I did these exact steps, then I was able to reproduce on 1.3 buri

Comment 3

[Ken Chang[:kenkai]]

The error cause sent from network is "BusyError".
...
06-03 18:24:21.801: I/Gecko(86): TelephonyProvider: handleCallDisconnected: {"state":3,"callIndex":1,"toa":129,"isMpty":false,"isMT":false,"als":0,"isVoice":true,"isVoicePrivacy":false,"number":"14085823028","numberPresentation":0,"name":null,"namePresentation":0,"uusInfo":null,"isOutgoing":true,"isEmergency":false,"isConference":false,"rilRequestType":18,"rilRequestError":0,"failCause":"BusyError"}
...

In this case, dial app should notify user that the MT side is busy and can not answer this call. Therefore, I don't think this bug is a real bug. But this is a UX design and owned by dail app. Change the component so that the expert can provide his feedback.

Comment 4

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Hi Ken, thanks for the input.

What didn't make sense to me is that if the number is associated with the contact then the BusyError does not occur.

Comment 5

[Doug Sherk (:drs) (inactive)]

We can't repro this on master.