Closed Bug 1088201 Opened 10 years ago Closed 10 years ago

[Settings][Bluetooth] Disconnect/Unpair dialog stays on the screen after unpairing a BT headset

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.1 unaffected, b2g-v2.2 affected)

RESOLVED DUPLICATE of bug 1090694
Tracking Status
b2g-v2.1 --- unaffected
b2g-v2.2 --- affected

People

(Reporter: ychung, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [2.1-exploratory-3])

Attachments

(1 file)

Attached file Logcat_UnpairDialogStays (deleted) —
Description:
After the user unpairs a BT headset, "Disconnect/Unpair" dialog reappears, and does not get dismissed by selecting any options.

Pre-requisite: DUT is paired and connected with a BT headset.
   
Repro Steps:
1) Update a Flame device to BuildID: 20141023040204.
2) Go to Settings > Bluetooth.
3) Select the BT headset under "Paired devices".
4) Select "Unpair" > "OK". 
  
Actual:
"Disconnect/Unpair" dialog reappears, and does not get dismissed by selecting any options.
  
Expected: 
BT headset is unpaired properly, and the main Bluetooth settings screen is brought back.
  
Environmental Variables:
Device: Flame 2.2 Master
BuildID: 20141023040204
Gaia: 27a1d1baaa8e375b70e043efee67d5f2206c330b
Gecko: 88adcf8fef83
Gonk: 05aa7b98d3f891b334031dc710d48d0d6b82ec1d
Version: 36.0a1 (2.2 Master)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Repro frequency: 100%
See attached: logcat, video
http://youtu.be/tL7BkK8O8mc
This issue does NOT occur on Flame 2.1:

Flame 2.1 

Device: Flame 2.1 (319mb)(Kitkat Base)(Full Flash)
BuildID: 20141023001201
Gaia: 1e48e3e40e0780c0cd07a3457e5fe2efeeb542d1
Gecko: 09fb60a37850
Gonk: 05aa7b98d3f891b334031dc710d48d0d6b82ec1d
Version: 34.0 (2.1)
Firmware: V188
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

The main Bluetooth settings screen is brought back properly after unpairing a BT headset.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
Nominating this to block 2.2. The user will experience a page with non functional buttons. Poor UX and a regression
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
Bug 1007600 seems to be the cause of this issue.

B2g-inbound Regression Window

Last Working 
Environmental Variables:
Device: Flame 2.2
BuildID: 20141020205719
Gaia: e09e1734ad523cf63351a28f6f84454319349fbe
Gecko: 4da1f6a151d6
Version: 36.0a1 (2.2) 
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

First Broken 
Environmental Variables:
Device: Flame 2.2
BuildID: 20141020214218
Gaia: ba10744d64411a8a12ae68f7cf1ec3e3ac897d21
Gecko: bcc5df613d83
Version: 36.0a1 (2.2) 
Firmware Version: v188
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Last Working gaia / First Broken gecko - Issue does NOT occur
Gaia: e09e1734ad523cf63351a28f6f84454319349fbe
Gecko: bcc5df613d83

First Broken gaia / Last Working gekko - Issue DOES occur
Gaia: ba10744d64411a8a12ae68f7cf1ec3e3ac897d21
Gecko: 4da1f6a151d6

Gaia Pushlog: https://github.com/mozilla-b2g/gaia/compare/e09e1734ad523cf63351a28f6f84454319349fbe...ba10744d64411a8a12ae68f7cf1ec3e3ac897d21
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Broken by Bug 1007600 - can you take a look Arthur?
Blocks: 1007600
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(arthur.chen)
We've found the root cause and filed a bug. Duplicate to that bug.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(arthur.chen)
Resolution: --- → DUPLICATE
blocking-b2g: 2.2? → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: