1061175 - [Flame][Intermittent] Sometimes after receiving a call, user is unable to make another phone call

Status: VERIFIED WORKSFORME

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

Description

[Marcela Oniga]

Steps to reproduce:
1. Receive a phone call
2. Hang up and then try to call another contact
3. Open contacts and select a contact to call

Expected results:
Call should be performed, no errors.

Actual results:
Sometimes after receiving a call, user is unable to make another phone call. Nothing happens when clicking on the contact.
This is also reproducing when dialling a phone number (if the contact is not saved in contacts), nothing happens when clicking the button "call".

Please note that I've seen also this issue intermittently on the previous builds.

Platform version: 34.0a1
Build identifier: 20140831040205
Git commit info: 2014-8-31 2be78d83
Nightly build.

Comment 1

[Marcela Oniga]

Note: *The workaround is to reboot the phone, however it doesn't work 100%.

Comment 2

[Anthony Ricaud (:rik)]

To help us debug this, we'll need logs from the Radio Interface Layer. 

Hsin-Yi: Do we have a page with some instructions on how to easily enable them and collect them?

Comment 3

[Marcela Oniga]

Attachment: logs

Comment 4

[Marcela Oniga]

I have some logs, you can find them attached, I used adb logcat to get them.

I also updated my device with:
Gaia   e7d31f0e9b6b19d9b484eeec8fb980718bc40d79
SourceStamp 532b5fb77ba1
BuildID 20140901091008
Version 34.0a1

I reproduced the issue easily while trying to call a contact from "Call log". I run in terminal adb logcat command and what I noticed is that every time I tried to call a contact from "Call log" I got:

"D/wpa_supplicant(  994): wlan0: Control interface command 'SIGNAL_POLL'
D/wpa_supplicant(  994): nl80211: survey data missing!
E/QCALOG  (  433): [MessageQ] ProcessNewMessage: [XTWiFi-PE] unknown deliver target [OS-Agent]
E/QCALOG  (  433): [MessageQ] ProcessNewMessage: [XTWWAN-PE] unknown deliver target [OS-Agent]
E/QCALOG  (  433): [MessageQ] ProcessNewMessage: [XT-CS] unknown deliver target [OS-Agent]
E/GeckoConsole( 1438): [JavaScript Error: "ReferenceError: FontSizeUtils is not defined" {file: "app://communications.gaiamobile.org/dialer/gaia_build_defer_index.js" line: 74}]
D/wpa_supplicant(  994): RX ctrl_iface - hexdump(len=11): 53 49 47 4e 41 4c 5f 50 4f 4c 4c
D/wpa_supplicant(  994): wlan0: Control interface command 'SIGNAL_POLL'
D/wpa_supplicant(  994): nl80211: survey data missing!"

Comment 5

[Anthony Ricaud (:rik)]

The FontSizeUtils error was bug 1061122. Should be fixed if you update.

Comment 6

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Hi, 

Please refer to https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Changing_preferences "RIL Debugging" to enable gecko ril debugger.

Once you enabled it successfully, you will see a bunch of messages with prefix "RIL Worker"

Thanks!

Comment 7

[Marcela Oniga]

Hsin-Yi:Thank you for details, I did enable ril debugger on device.PLease see atached logs.

I was able to reproduce the issue using:

Gaia   44bf2e3bc5ddea9db9a8c851bd353cb234aa883c
SourceStamp c360f3d1c00d
BuildID 20140902040205
Version 34.0a1

Comment 8

[Marcela Oniga]

Attachment: logs_ril.txt

Logs with RIL enabled.

Comment 9

[Marcela Oniga]

Attachment: logs

Output after catching the bug

Comment 10

[Marcela Oniga]

This is also happening from time to time using:
OS version: 2.2.0.0 prerelease
Build no: 39
Build identifier: 20141210040201
Platform version: 37.0a1

After making or receiving several call, the user is unable to perform another call. Nothing happens after you click on the Call button. The workaround is to reboot the phone.

Can someone please investigate this issue? I've seen it quite often and I think this is a critical bug for users.

Comment 11

[Johan Lorenzo [:jlorenzo]]

This is very likely due to bug 1110872. To check this, next time it happens, can you go to Settings and see if you don't see the data in 'Device Information'/'More Information' like explained in bug 1093932?

Comment 12

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Hi Ben,
Mind taking a look at this? Thank you.

Comment 13

[Marcela Oniga]

(In reply to Johan Lorenzo [:jlorenzo] (QA) from comment #11)
> This is very likely due to bug 1110872. To check this, next time it happens,
> can you go to Settings and see if you don't see the data in 'Device
> Information'/'More Information' like explained in bug 1093932?

It has nothing to do with Settings, I mean the data in 'Device Information'/'More Information' is still there, nothing is changed.

Comment 14

[Ben Hsu [:HoPang]]

Sure, I'll take it.

Comment 15

[Johan Lorenzo [:jlorenzo]]

(In reply to Marcela Oniga from comment #13) 
> It has nothing to do with Settings, I mean the data in 'Device
> Information'/'More Information' is still there, nothing is changed.

Did you check just after you weren't able to perform a call? When bug 1110872 happens, you're not able to make phone calls, send text messages, or activate carrier data. I experienced this multiple times on my dogfooding device.

Comment 16

[Marcela Oniga]

(In reply to Johan Lorenzo [:jlorenzo] (QA) from comment #15)
> (In reply to Marcela Oniga from comment #13) 
> > It has nothing to do with Settings, I mean the data in 'Device
> > Information'/'More Information' is still there, nothing is changed.
> 
> Did you check just after you weren't able to perform a call? When bug
> 1110872 happens, you're not able to make phone calls, send text messages, or
> activate carrier data. I experienced this multiple times on my dogfooding
> device.

Yes, I did. 'Device Information'/'More Information' is still there as expected

Comment 17

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Nominate this as 2.2+ because the very fundamental feature is broken. Per information from Ben, the reproduce rate is over 30%

Comment 18

[Ben Hsu [:HoPang]]

(In reply to Hsin-Yi Tsai [:hsinyi] from comment #17)
> Nominate this as 2.2+ because the very fundamental feature is broken. Per
> information from Ben, the reproduce rate is over 30%

Hi Hsinyi, 
The high reproduce rate is obtained when testing on a specific build(Build ID: 20140831040205). However, when testing on a more recent build(Build ID: 20141210040201), I am still trying to reproduce this issue.

Comment 19

[Hsin-Yi Tsai (she/her) [:hsinyi]]

(In reply to Ben Hsu [:benhsu] from comment #18)
> (In reply to Hsin-Yi Tsai [:hsinyi] from comment #17)
> > Nominate this as 2.2+ because the very fundamental feature is broken. Per
> > information from Ben, the reproduce rate is over 30%
> 
> Hi Hsinyi, 
> The high reproduce rate is obtained when testing on a specific build(Build
> ID: 20140831040205). However, when testing on a more recent build(Build ID:
> 20141210040201), I am still trying to reproduce this issue.

Oh, that's good to know! Thanks for the kind update :)

Comment 20

[Wesley Huang [:wesley_huang] (EPM) (NI me)]

removing the nomination as it seems non-reproducible now.
Marcela, are you able to repro?

Comment 21

[Marcela Oniga]

(In reply to Wesley Huang [:wesley_huang] (EPM) (NI me) from comment #20)
> removing the nomination as it seems non-reproducible now.
> Marcela, are you able to repro?

I will try to reproduce it, but since the bug was intermittent it might take a while to reproduce it. Let's not close it yet.

Comment 22

[Ben Hsu [:HoPang]]

Hi Marcela,
Currently, I have successfully reproduced this issue on three builds you specified in your previous comments (20140831040205, 20140901091008, and 20140902040205), but I cannot reproduce it on build(20141210040201). Besides, if I didn't open 'Device Information'/'More Information' before the issue happens, the details listed in 'Device Information'/'More Information' will disappear after it happens. Do you mind checking 'Device Information'/'More Information' again?

Comment 23

[Marcela Oniga]

Unable to reproduce on the latest builds.

Comment 24

[Johan Lorenzo [:jlorenzo]]

Per comment 23.

Comment 25

[Marcela Oniga]

Verified.