Closed Bug 977595 Opened 12 years ago Closed 11 years ago

[zffos1.3][P3] (Local) The DuT automatically activates the speaker phone.

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: fang.chen1, Unassigned)

Details

(Whiteboard: [closeme 3/6/2014])

User Agent: Mozilla/5.0 (Windows NT 6.1; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; TCO_20140227092630; rv:11.0) like Gecko Steps to reproduce: A.- Overview Description (technical background, concise explanation of the bug): The DuT automatically activates the speaker phone. ________________________________________________________________________________ B.- Steps to Reproduce (initial conditions, required resources, step by step instructions to reproduce): Perform an outgoing voice call from DuT to a busy fixed network number. Make sure not having call waiting service activated. Actual results: The DuT automatically activates the speaker phone when the distant part is busy.
Built ID :20140218180032 OS version 1.3.0.0-prerelease QC RIL commit: a406d321 Add null check when handling set preferred network type QC RIL TAG version: AU_LINUX_GECKO_B2G_JB_3.2.01.03.00.112.223 gaia commit: 744fb691 Merge pull request #15526 from steveck-chung/bug-961231 gecko commit: 6840e8c2 Bumping gaia.json for 1 gaia-1_3 revision(s) a=gaia-bump
Feels like a vendor problem, but let's double check. Can someone confirm this on the Moz side?
Keywords: qawanted
Tried several times with the given STR and a few methods of my own that did not yield any reproduction of this issue on Buri 1.3 --Listing steps I took/Variables, below: 1. Used three devices. (A DuT, a personal phone, and another testers Buri 1.3) 2. Had the personal phone, and the other testers Buri start a call with one another. 3. Used the DuT to call the other testers Buri and recieved a message "User is currently unavailable." - Speaker remained "off." - Repeated this 6 times. - Speaker did not turn on. 1. Then searched online for a number that results in a busy tone. 2. Used the DuT to call the number I found online. (Resulted in a busy tone.) - Speaker remained "off." - Repeated this step 7 times. - Speaker did not turn on. Environmental Variables: Device: Buri 1.3 MOZ BuildID: 20140226004002 Gaia: da50b2b62ed96993cf4df22e3d69c435b28506bd Gecko: 3c39d1e487d9 Version: 28.0 Firmware Version: V1.2-device.cfg
Keywords: qawanted
Whiteboard: [closeme 3/6/2014]
QA Contact: pfield
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.