Closed
Bug 1233872
Opened 9 years ago
Closed 7 years ago
Paired bluetooth devices do not appear properly in the Settings main menu after app launch.
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(blocking-b2g:2.6?, b2g-v2.5 unaffected, b2g-master affected)
RESOLVED
WONTFIX
blocking-b2g | 2.6? |
Tracking | Status | |
---|---|---|
b2g-v2.5 | --- | unaffected |
b2g-master | --- | affected |
People
(Reporter: Marty, Unassigned)
References
()
Details
(Keywords: regression, Whiteboard: [2.6-Daily-Testing][Spark])
Attachments
(1 file)
331.44 KB,
text/plain
|
Details |
Description:
If the user is already paired with one or more bluetooth devices when they launch the settings app, the name will not appear on the Bluetooth item of the main Settings menu.
If the user navigates into Bluetooth settings, then backs out to the main menu, the bluetooth device name will be displayed properly.
If the user has two devices paired, the menu will still display ", +1" to indicate the other device.
Repro Steps:
1) Update a Aries to 20151218153622
2) Open the Settings app and enable Bluetooth
3) Pair with two other devices
4) Close and relaunch the Settings app, note the bluetooth list item on the settings main menu.
Actual:
Paired bluetooth device names do not appear in the Settings main menu after app launch.
Expected:
The first paired device name appears properly in the Settings main menu after app launch.
Environmental Variables:
Device: Aries 2.6
Build ID: 20151218153622
Gaia: d069027f9af6f835ef869f1f01b52339e5a3f423
Gecko: c5cb194cc9cb56d742fb3a7a826f0080b0404edc
Gonk: a19052e4389c3ae2d8fc3e7a74a475401baacc56
Version: 46.0a1 (2.6)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0
Repro frequency: 4/5
See attached: Video (URL), Logcat
Reporter | ||
Comment 1•9 years ago
|
||
This issue DOES occur on the latest Flame 2.6 build.
Paired bluetooth device names do not appear in the Settings main menu after app launch.
Environmental Variables:
Device: Flame 2.6
BuildID: 20151218030236
Gaia: 2f093462969d2c5f65dced3908a7abff6b1913e8
Gecko: 66fb852962c0d5f6f5fe0604204da4f5d17763c9
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 46.0a1 (2.6)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0
******************************************
This issue does NOT occur on the latest Flame 2.5 build.
The first paired device name appears properly in the Settings main menu after app launch.
Environmental Variables:
Device: Flame 2.5
BuildID: 20151218180935
Gaia: eeed1451e0e48b63abe3199e4d6906adc2a762d2
Gecko: 766600655dfb1b67c380b9da4f4b19acb505a858
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 44.0 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Updated•9 years ago
|
blocking-b2g: --- → 2.6?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: regressionwindow-wanted
Updated•9 years ago
|
QA Contact: pcheng
Comment 2•9 years ago
|
||
b2g-inbound regression window:
Last Working
Device: Flame 2.6
BuildID: 20151105192237
Gaia: 1fb7e4b7904d577a1859b91269a85b363ddc2836
Gecko: 44ff38c597cf7ae1fd1c5e7a0ca46921f9b6fda1
Version: 45.0a1 (2.6)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0
First Broken
Device: Flame 2.6
BuildID: 20151105201736
Gaia: cec4c1d3729137a24163756d15f98b0d37803966
Gecko: 1a44749d8135fcee582049cf490e6a30bfab19d4
Version: 45.0a1 (2.6)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:45.0) Gecko/45.0 Firefox/45.0
Last Working Gaia First Broken Gecko - no repro
Gaia: 1fb7e4b7904d577a1859b91269a85b363ddc2836
Gecko: 1a44749d8135fcee582049cf490e6a30bfab19d4
Last Working Gecko First Broken Gaia - repro
Gaia: cec4c1d3729137a24163756d15f98b0d37803966
Gecko: 44ff38c597cf7ae1fd1c5e7a0ca46921f9b6fda1
Gaia pushlog:
https://github.com/mozilla-b2g/gaia/compare/1fb7e4b7904d577a1859b91269a85b363ddc2836...cec4c1d3729137a24163756d15f98b0d37803966
Caused by changes made in Bug 1211341.
Blocks: 1211341
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: regressionwindow-wanted
Comment 3•9 years ago
|
||
Fred, the changes for bug 1211341 seem to have caused this issue. Can you please take a look?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado) → needinfo?(gasolin)
Updated•9 years ago
|
Assignee: nobody → gasolin
Flags: needinfo?(gasolin)
Comment 4•9 years ago
|
||
Ben, the issue was fixed in gecko several months ago, could you help check if it still works?
Flags: needinfo?(btian)
Comment 5•9 years ago
|
||
(In reply to Fred Lin [:gasolin] from comment #4)
> Ben, the issue was fixed in gecko several months ago, could you help check
> if it still works?
Gecko still work per comment 2.
Last Working Gaia First Broken Gecko - no repro
Gaia: 1fb7e4b7904d577a1859b91269a85b363ddc2836
Gecko: 1a44749d8135fcee582049cf490e6a30bfab19d4
Flags: needinfo?(btian)
Comment 6•9 years ago
|
||
Marty, I use Aries to pair with 1 foxfooding and 1 flame, and can't reproduce this issue.
The similar issue was happened when pairing with 1 earphone & 1 device several months ago.
Could you share what devices you use to test with?
Flags: needinfo?(mshuman)
Reporter | ||
Comment 7•9 years ago
|
||
I've seen this occur when paired with headsets and bluetooth speakers, but those aren't necessary to reproduce the issue. I have also seen this occur when only paired with other FxOS devices (2 Flames, or 1 Flame and 1 Aries).
Flags: needinfo?(mshuman)
Updated•9 years ago
|
Assignee: gasolin → nobody
Comment 8•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•