Created attachment 8635595 [details] logcat-fmd-in-call.txt Description: If the device is already in a phone call when it receives an FMD Ring command, it will vibrate 3 times, but will not ring, and will not display any UI to the user explaining why it vibrated. The user will notice the vibrations during the call, but will not know why it vibrated after the call has ended, as there will be no notification or other indication that it vibrated. Repro Steps: 1) Update an Aries to 20150717125848 2) Log into a Firefox Account 3) Enable Find My Device 4) From another computer or device, navigate to find.firefox.com and log into the same Firefox Account 5) From another phone, call the DUT 6) From the website, select the Ring command while the DUT is in an active phone call. Actual: The device will vibrate, but not give any other information or indication what the vibration means. Expected: The Ring command will not result in confusing vibration behavior without information or indication of what caused the vibration Environmental Variables: Device: Aries 2.5 Build ID: 20150717125848 Gaia: 77bc0d940bde2a5d2d4dfadfcccc6d8d77456d36 Gecko: 15155971639c Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 42.0a1 (2.5) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0 Repro frequency: 10/10 See attached: Logcat
This issue DOES occur on the latest Flame 2.5 build. The device will vibrate, but not give any other information or indication what the vibration means. Environmental Variables: Device: Flame 2.5 Build ID: 20150717010206 Gaia: 77bc0d940bde2a5d2d4dfadfcccc6d8d77456d36 Gecko: 8d262d1d0ae5 Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 42.0a1 (2.5) Firmware Version: v18D User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0 ------------------------------------------------ This issue does NOT occur on the latest Flame 2.2 build. The device will put the active call on hold and ring audibly through the in-call audio channel. Environmental Variables: Device: Flame 2.2 Build ID: 20150715002506 Gaia: 84d0c76370dcd3d25813b00de55194730884355b Gecko: a5db6d9850f6 Gonk: bd9cb3af2a0354577a6903917bc826489050b40d Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
NI component owner to take a look.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(npark)
Supposedly the person who triggered the FMD is the owner of the phone in most instance, I don't think it's a blocking bug, although if a text description could appear on the phone while it's ringing. (But I think there was also an icon that appears while FMD ring is activated, if so then the user would know that the vibration came from FMD)
[Tracking Requested - why for this release]: Since there is no gaia work being done for FMD or FxA, putting it as backlog
tracking-b2g: --- → backlog
Firefox OS is not being worked on
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.