809649 - Crash when dialing with bluetooth headset

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: General, defect, P1)

Description

[Greg Grisco]

Attachment: stack trace

Steps to reproduce:

1.  Pair and connect to BT headset
2.  Dial a number

In-call audio is heard through headset

3.  hang up call
4.  double-tap BT headset

Call is made, but sometimes the device crashes (stacktrace attached)

Gecko Version:
commit 464613e22cc553a840b5c67e7bac554aa9325fef
Author: Dão Gottwald <[e-mail]>
Date:   Tue Nov 6 11:20:34 2012 +0100

Gaia Version:
commit bc0c53493b5240132e238a544a2a871c7936e3f7
Merge: c638579 e0e2eeb
Author: David Scravaglieri <[e-mail]>
Date:   Tue Nov 6 01:17:10 2012 -0800

last thing seen in adb log:
E/GeckoConsole(  707): [JavaScript Warning: "HTTP "Content-Type" of "text/html" is not supported. Load of media resource app://communications.example.com/dialer/oncall.html failed." {file: "app://communications.example.com/dialer/oncall.html#unlocked" line: 0}]
E/GeckoConsole(  612): [JavaScript Warning: "HTTP "Content-Type" of "text/html" is not supported. Load of media resource app://communications.example.com/dialer/oncall.html failed." {file: "app://communications.example.com/dialer/oncall.html#unlocked" line: 0}]

Comment 1

[Gina Yeh [:gyeh] [:ginayeh]]

I followed steps above a few times and still cannot reproduce this issue. 

Could you help to check the system message part? I'd like to make sure that we did send out a system message with type 'bluetooth-dialer-command' when tapping 2 times. If we did send out the message, then I think we might want to check the implementation of Dialer app.

Comment 2

[Gina Yeh [:gyeh] [:ginayeh]]

cc Eric: developer of Bluetooth
cc Etienne: developer of Dialer app

Comment 3

[Greg Grisco]

I'm having a difficult time reproducing now.  When I got it to happen earlier today, I'm pretty sure it reached dialer because the call still went through.  I'll spend a little more time tomorrow to try and repro and provide the system messages.

Comment 4

[Greg Grisco]

hcidump:

I/Gecko   (  124): -- SystemMessageInternal 1352748897666 : received SystemMessageManager:Message:Return:OK telephony-new-call for app://communications.example.com/dialer/index.html#keyboard-view @ app://communications.example.com/manifest.webapp
I/Gecko   (  124): -- SystemMessageInternal 1352748897686 : received SystemMessageManager:Message:Return:OK telephony-new-call for app://communications.example.com/dialer/index.html#keyboard-view @ app://communications.example.com/manifest.webapp
I/Gecko   (  124): -- SystemMessageInternal 1352748921042 : Broadcasting bluetooth-dialer-command {"bluetooth-dialer-command":"BLDN"}
I/Gecko   (  124): -- SystemMessageInternal 1352748921044 : Asking to open {"uri":"app://communications.example.com/dialer/index.html#keyboard-view","manifest":"app://communications.example.com/manifest.webapp","type":"bluetooth-dialer-command"}
I/Gecko   (  124): -- SystemMessageInternal 1352748921070 : received SystemMessageManager:Message:Return:OK bluetooth-dialer-command for app://communications.example.com/dialer/index.html#keyboard-view @ app://communications.example.com/manifest.webapp
I/Gecko   (  124): -- SystemMessageInternal 1352748921130 : Broadcasting telephony-new-call {"number":"18588455723","state":1}
I/Gecko   (  124): -- SystemMessageInternal 1352748921132 : Asking to open {"uri":"app://communications.example.com/dialer/index.html#keyboard-view","manifest":"app://communications.example.com/manifest.webapp","type":"telephony-new-call"}
I/Gecko   (  124): -- SystemMessageInternal 1352748921166 : Broadcasting telephony-new-call {"number":"18588455723","state":1}
I/Gecko   (  124): -- SystemMessageInternal 1352748921169 : Asking to open {"uri":"app://communications.example.com/dialer/index.html#keyboard-view","manifest":"app://communications.example.com/manifest.webapp","type":"telephony-new-call"}

Comment 5

[Gina Yeh [:gyeh] [:ginayeh]]

It seems like we did receive "BLDN" from bluetooth headset and send out to dialer app. Then, we made a new call and crashed? If so, we may want to check the problem from dialer app. Etienne. any idea for this issue?

Comment 6

[Etienne Segonzac (:etienne)]

(In reply to Gina Yeh from comment #5)
> It seems like we did receive "BLDN" from bluetooth headset and send out to
> dialer app. Then, we made a new call and crashed? If so, we may want to
> check the problem from dialer app. Etienne. any idea for this issue?

Not really...
The device reboots?

Comment 7

[Greg Grisco]

I think the b2g process restarts.  

If I return right away in openCallScreen then the crash isn't seen.  

Otherwise, I printed urlBase and screenState:

open window:  app://communications.example.com/dialer/oncall.html#unlocked

the crash happens shortly after the page is displayed.  openCallScreen is still called three more times before the crash, but returns right away since callScreenWindow is true.

Comment 8

[Etienne Segonzac (:etienne)]

(In reply to ggrisco from comment #7)
> I think the b2g process restarts.  
> 
> If I return right away in openCallScreen then the crash isn't seen.  
> 
> Otherwise, I printed urlBase and screenState:
> 
> open window:  app://communications.example.com/dialer/oncall.html#unlocked
> 
> the crash happens shortly after the page is displayed.  openCallScreen is
> still called three more times before the crash, but returns right away since
> callScreenWindow is true.

Ok. This may be caused by bug 808743.
Is it still reproducible on a recent build with bug 808743 fixed?

Comment 9

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

I crashed as well doing something similar:
1. connect bluetooth headset
2. reboot device
3. make a call

Comment 10

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

oops.  forgot to mention I had the headset turned off as well prior to the call.

Comment 11

[Gina Yeh [:gyeh] [:ginayeh]]

Naoki, please help to attach log or stack trace for your problem although I don't think this is caused by bluetooth (since you have restarted the device after connecting with a bluetooth headset and also turned off the headset before making a new call).

Comment 12

[Alex Keybl [:akeybl]]

Marking for C2, given this meets the criteria of known P1/P2 blocking-basecamp+ bugs at the end of C1.

Comment 13

[Andreas Gal :gal]

Whats the status here?

Comment 14

[Walter Chen[:ypwalter][:wachen]]

Hi,

I believe this is related to 
https://bugzilla.mozilla.org/show_bug.cgi?id=813872
or other bugs recently addressed.

It used to crash a lot when receiving or dialing call.
As far as I tested it for past 2 hours, I think by using new builds, it might be able to reproduce. Please provide more details and try to reproduce it in new build.

Comment 15

[Walter Chen[:ypwalter][:wachen]]

PS. I was using 11/21/2012 nightly release build to test. It didn't crash at all.

Comment 16

[Michael Vines [:m1] [:evilmachines]]

WIth beta right?

Comment 17

[Evelyn Hung]

This is NOT a Gaia issue, so I won't take it.
I believe Gecko Dev will handle this if someone can reproduce it.

Comment 18

[Walter Chen[:ypwalter][:wachen]]

Michael, sorry for the confusion. 
I mean daily build of current beta(v18). -> https://releases.mozilla.com/b2g/
Thanks.

Comment 19

[Michael Vines [:m1] [:evilmachines]]

Thanks Walter.  We'll try to reproduce this at the tip here again.

Comment 20

[Chris Jones [:cjones] inactive; ni?/f?/r? if you need me]

Any update on this?

Comment 21

[Joe Cheng [:jcheng] (please needinfo)]

+ qawanted

Comment 22

[Johnny Stenback (:jst)]

Eric, can you own this one? If not, please feel free to pass along to a better owner.

Comment 23

[Eric Chou [:ericchou] [:echou]]

Because we haven't got more information about this bug since Gina asked in #comment 11, I suggest that we should close this bug after the confirmation from QA.

Walter, could you help to check again if you can reproduce this? Thank you.

Comment 24

[Walter Chen[:ypwalter][:wachen]]

Hi,

I double checked it with 11/28/2012 daily(beta, v18) released code.
I still didn't see any issue causing by the actions mentioned.

There were some bugs on early Nov that phone might crash if you tried to call or receive phone calls. That used to be gaia issues. However, I thought that they fixed them already.

Since, I still couldn't reproduce it, I will close this as worksforme.

However, if you do have some other related information, please reopen this bug.
If you do want to let us know about the bug more, please give us information about the cell phone you are testing, like build identifier, git commit info, and date of your build(Settings > Device information > More information). In that case, we can quickly reproduce the bug and solve it.

Closed this as resolved/worksforme

Comment 25

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

reassigning to Steven to redistribute.  If you guys don't have a blue tooth headset, feel free to assign this bug back to me ( :nhirata )

Comment 26

[Allen Maxwell]

Issue no longer occurs on Unagi Build ID:20121231070201
Unable to verify on Otoro, only have Unagi