804915 - [Phone] Have to toggle speaker phone in order to hear or talk for calls.

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia, defect)

Description

[Chenxia Liu [:liuche]]

Speaker phone button has to be toggled before any voice is audible on phone. Other phone also does not hear anything.

Using T-Mobile prepaid SIM.

STR:
Make or receive a call.

Expected:
Possible to hear and talk on call immediately after answering.

Actual:
Can't hear anything on either end. Have to toggle speakerphone to hear anything, after which it's possible to hear and speak to the other end.

Comment 1

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

This is clearly a blocker. But just putting as nomination so that we can find the appropriate owner.

Comment 2

[Randy Lin [:rlin] - Be Mozillian on 2015/01/26]

Hi Chenxia, 
Can you share the rom/device that you test? 
Do you mean you can't hear anything on receiver(handset) after phone call is connected?

Comment 3

[Mike Connor [:mconnor]]

Chenxia, can you please retry on the new build pushed yesterday and re-nominate if you can still reproduce? QA wasn't able to reproduce this in testing yesterday.

Comment 4

[Maria Sandberg [:mushi]]

I have this same problem and it's been consistent before and after today's update. Was just about to file a bug for it but found this one. I'm in MV if there is QA here who would like to take a look at the phone.

Comment 5

[Daniel Holbert [:dholbert]]

I'm hitting this as well, using the latest test-drivers build from late last week. (datestamp 2012-10-24 11:07:05)  I've actually been hitting this since I first got my B2G phone, as far as I can remember.  In all of my phone conversations, I've had to toggle speakerphone on & off before I can use the phone as a phone.

Like Maria, I'm in MV, and I'm happy to loan my phone to QA or devs

Re-nominating per comment 1 / comment 3.

Comment 6

[Daniel Holbert [:dholbert]]

Two more pieces of information:
 - When I place a call, I *do* hear audio while the phone is ringing, and I'll often hear a very short "blip" of audio when the recipient picks up (e.g. the first syllable of an voicemail greeting), but then it goes silent until I toggle speakerphone on & off.

 - The audio cut-out happens suspiciously around the same time as bug 806640's screen-lockup, so I wonder if this bug and that bug are related...

Comment 7

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

I don't understand the flag jockeying here.  This is a terrible bug, it's annoying the crap out of me on my dogfooding phone on the stable channel.  There's no way the "workaround" here will be obvious to a normal user.  I doubt the phone would get through certification.

Does someone think this bug has been resolved by work that's not yet merged to the stable channel?  If so, that's easy to test, iterate through nightly builds and find which one fixed this.

Comment 8

[Daniel Coloma:dcoloma]

None of the people on today's triage could reproduce it, it is reported as working properly in all the smoke tests we have doing lately (https://docs.google.com/spreadsheet/ccc?key=0AqDJxnTd7VDLdDRKOE1uanE3M3FtMDBOVjRIV253S1E#gid=23). 

My bad with the flags. I volunteered for assigning it to QA, if they can reproduce they will assign to an engineer and mark as blocker.


(In reply to Chris Jones [:cjones] [:warhammer] from comment #7)
> I don't understand the flag jockeying here.  This is a terrible bug, it's
> annoying the crap out of me on my dogfooding phone on the stable channel. 
> There's no way the "workaround" here will be obvious to a normal user.  I
> doubt the phone would get through certification.
> 
> Does someone think this bug has been resolved by work that's not yet merged
> to the stable channel?  If so, that's easy to test, iterate through nightly
> builds and find which one fixed this.

Comment 9

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

If this is proven to be unagi-specific, I still think we should block on it because of the risk of losing dogfooders.

Comment 10

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

(In reply to Daniel Coloma:dcoloma from comment #8)
> None of the people on today's triage could reproduce it, it is reported as
> working properly in all the smoke tests we have doing lately
> (https://docs.google.com/spreadsheet/
> ccc?key=0AqDJxnTd7VDLdDRKOE1uanE3M3FtMDBOVjRIV253S1E#gid=23). 
> 
> My bad with the flags. I volunteered for assigning it to QA, if they can
> reproduce they will assign to an engineer and mark as blocker.

That sounds like a great idea.  Like I said, I would recommend going through the nightly builds to see which fixed this bug.  I and dholbert can assure you it's not fixed in the 10-24 stable build ;).

Comment 11

[Daniel Coloma:dcoloma]

(In reply to Chris Jones [:cjones] [:warhammer] from comment #10)
> (In reply to Daniel Coloma:dcoloma from comment #8)
> > None of the people on today's triage could reproduce it, it is reported as
> > working properly in all the smoke tests we have doing lately
> > (https://docs.google.com/spreadsheet/
> > ccc?key=0AqDJxnTd7VDLdDRKOE1uanE3M3FtMDBOVjRIV253S1E#gid=23). 
> > 
> > My bad with the flags. I volunteered for assigning it to QA, if they can
> > reproduce they will assign to an engineer and mark as blocker.
> 
> That sounds like a great idea.  Like I said, I would recommend going through
> the nightly builds to see which fixed this bug.  I and dholbert can assure
> you it's not fixed in the 10-24 stable build ;).

Which hardware are you using? As you know we do not have Unagis... Do you have a pointer to the test-drivers manifest? With that info it will be easier for us to help

Comment 12

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

I didn't know that! :)  OK.  Moz dogfooders are on unagis (including me).

I think it's best for the Moz QA folks to investigate this then.  tchung, does your team have cycles for this tomorrow?

Comment 13

[Daniel Coloma:dcoloma]

OK, changing assignee from mbarone to tchung

Comment 14

[Chenxia Liu [:liuche]]

(sorry, lost my cc)

I don't see this problem in the newest OTA update, 11/01. Voice can be heard and transmitted upon answering the call. Toggling speakerphone also works as expected.

Comment 15

[Daniel Holbert [:dholbert]]

WORKSFORME in the just-released update too. Thank goodness :) (datestamp 2012-11-01 09:44:34)

Resolving WFM, and canceling the needinfo? request because I'm pretty sure it's stale after dcoloma reassigned the bug in comment 13.