Closed
Bug 1077173
Opened 10 years ago
Closed 10 years ago
[Bluetooth] Bluetooth pairing never resolves to connected status
Categories
(Firefox OS Graveyard :: Bluetooth, defect)
Tracking
(b2g-v2.2 affected)
RESOLVED
DUPLICATE
of bug 1065999
Tracking | Status | |
---|---|---|
b2g-v2.2 | --- | affected |
People
(Reporter: bzumwalt, Unassigned)
References
()
Details
(Keywords: regression, smoketest)
Attachments
(1 file)
(deleted),
text/plain
|
Details |
Description:
Pairing bluetooth devices never resolves into having devices listed as connected. This seems to occur with less interference from other bluetooth bugs while connecting to bluetooth headphones.
Repro Steps:
1) Update a Flame device to BuildID: 20141002093155
2) Launch Settings and navigate to Bluetooth settings
3) Enable bluetooth and search for bluetooth headphones
4) Select bluetooth headphones from list when they appear
Actual:
Pairing begins, but never completes. The device is never connected and listed as pairing until bluetooth is disabled.
Expected:
The device pairs and connects without issue.
Environmental Variables:
Device: Flame 2.2 Master KK (319mb) (Full Flash)
BuildID: 20141002093155
Gaia: 191d805f4911628d37a8a90a1e23a6013995138f
Gecko: 5d6ec4dddf14
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 35.0a1 (2.2 Master)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Repro frequency: 3/5, 60%
See attached: Youtube video clip & logcat
Reporter | ||
Comment 1•10 years ago
|
||
Youtube video link: http://youtu.be/k4--fOOrn_8
Unable to check 2.1 due to bug 1074152
Comment 2•10 years ago
|
||
[Blocking Requested - why for this release]:
Core functional regression that is failing smoke tests.
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Keywords: regression
bug 1065999 only commits in v2.1 but not master.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•10 years ago
|
blocking-b2g: 2.2? → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•