Closed Bug 1154852 Opened 9 years ago Closed 9 years ago

[Bluetooth] Cannot respond to another device's pair request

Categories

(Firefox OS Graveyard :: Gaia::System::Lockscreen, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.5+, b2g-master verified)

VERIFIED FIXED
blocking-b2g 2.5+
Tracking Status
b2g-master --- verified

People

(Reporter: onelson, Unassigned)

References

()

Details

(Keywords: regression, smoketest, Whiteboard: [3.0-Daily-Testing],)

Attachments

(1 file)

Description:
When a user attempts to send a pair request to another device, they will observe a new behavior:
The screen will no longer give priority to a new screen with the pair request + number of pairing connection; instead, both devices involved in the pairing will receive a 'bluetooth pairing request' notification. If the user attempts to interact with this request however, their notification tray will drop.
Cannot attach to phones or devices

Note: User may pair to other bluetooth devices, such as headsets (tested with a Motorola Commander and Arctic Headsets)

PreReq:
* a second, willing, bluetooth device
Repro Steps:
1) Update a Flame to [something-today] ** both phones
2) Open the Settings app ** both phones
3) Open the Bluetooth menu ** both phones
4) Enable, name device, set to visible and search for devices ** both phones
5) Locate opposite phone and attempt to pair
6) Observe notifications displayed on both devices
7) Attempt to pair from opposite device

Actual:
Tapping on bluetooth notification request does nothing, user cannot pair

Expected:
Tapping on bluetooh notification request enables user to pair devices


Environmental Variables:
--------------------------------------------------

Device: Flame 3.0
Build ID: 20150413010203
Gaia: 3c68964cb9fdba7cf0f6829b7f44562acaf1f1d7
Gecko: 0a46652bd992
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 40.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0
--------------------------------------------------

Repro Rate: 5/5
See attached:
creating video and logcat now, will attach shortly
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Whiteboard: [3.0-Daily-Testing] → [3.0-Daily-Testing],
[Blocking Requested - why for this release]:
Functional regression failing smoke tests
blocking-b2g: --- → 3.0?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
QA Contact: bzumwalt
Bug 1138799 seems to have caused this issue.  We are attempting to revert this patch to verify that it is in fact the issue.  Adding qawanted to track this.

The last working build in the window below correctly brings up the pairing window whereas the first broken build will only show a notification on one or both devices.  The swaps indicate a gaia problem and the only gecko change is a b2g bumper (also confirming gaia). 

B2g-inbound Regression Window

Last Working 
Environmental Variables:
Device: Flame 3.0
BuildID: 20150414195318
Gaia: db200d75c9fa50b78de6f448e234f9bfc6feb9c9
Gecko: 1b97a2509dee
Version: 40.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0

First Broken 
Environmental Variables:
Device: Flame 3.0
BuildID: 20150414201320
Gaia: 8b899668a5ef6effcd8b2bd84eea5c1450a3f207
Gecko: 4560cbc3b7f0
Version: 40.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0

Last Working gaia / First Broken gecko - Issue does NOT occur
Gaia: db200d75c9fa50b78de6f448e234f9bfc6feb9c9
Gecko: 4560cbc3b7f0

First Broken gaia / Last Working gecko - Issue DOES occur
Gaia: 8b899668a5ef6effcd8b2bd84eea5c1450a3f207
Gecko: 1b97a2509dee

Gaia Pushlog: https://github.com/mozilla-b2g/gaia/compare/db200d75c9fa50b78de6f448e234f9bfc6feb9c9...8b899668a5ef6effcd8b2bd84eea5c1450a3f207

Gecko pushlog: http://hg.mozilla.org/integration/b2g-inbound/pushloghtml?fromchange=1b97a2509dee&tochange=4560cbc3b7f0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
This issue no longer occurs with the latest gaia that has the above change reverted.

Issue DOES occur
Environmental Variables:
Device: Flame 3.0
BuildID: 20150415033818
Gaia: 2dd89fef4fae4d86fd313037ef384086c2e0e8a5
Gecko: bee53c88ced0
Version: 40.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0

Issue does NOT occur
Environmental Variables:
Device: Flame 3.0
BuildID: 20150415033818
Gaia: 294f7d301d26d49c49cf0785d07de4cff1020bc3
Gecko: bee53c88ced0
Version: 40.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0
Keywords: qawanted
Marking resolved fixed by backout, let's verify on next nightly.
Status: NEW → RESOLVED
Closed: 9 years ago
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Keywords: qawanted, verifyme
Resolution: --- → FIXED
This issue is verified fixed on the latest Nightly Flame 3.0 build.

Actual Results: The pairing dialogue correctly shows on both devices.

Environmental Variables:
Device: Flame 3.0
BuildID: 20150415160205
Gaia: 777d01f4a2c7b41c4b02e3cf87715714ccc0590b
Gecko: 53ceefb0e1c8
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 40.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:40.0) Gecko/40.0 Firefox/40.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Keywords: qawanted, verifyme
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Moving the bug to the component where the regression came from.
blocking-b2g: 2.5? → 2.5+
Component: Bluetooth → Gaia::System::Lockscreen
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: