Closed Bug 1069690 Opened 11 years ago Closed 11 years ago

[Flame][KK] Bluetooth pairing request window is not showing up

Categories

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

x86
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.1+)

RESOLVED WORKSFORME
blocking-b2g 2.1+

People

(Reporter: pcheng, Unassigned)

Details

(Keywords: regression)

Attachments

(1 file)

Attached file logcat of issue
Description: The pairing request dialog doesn't show up. It pops up an alert informing user that there is a pairing request, but when pulled down the utility tray and tap on the notification, nothing happens. Steps to Reproduce: 0) Reset the phone via Settings > Device information 1) Go to Settings > Bluetooth 2) Attempt to pair with another device Expected: The Bluetooth pairing request window shows up with a security PIN. User can tap to confirm pairing. Actual: The Bluetooth pairing request window doesn't show up, instead an alert shows up in notification tray. When tapping on the notification, nothing shows up. Environmental Variables: Device: Flame 2.2 Master BuildID: 20140918150023 Gaia: d37950eb09e28aa18d0e01df9ff90574bd4337e0 Gecko: d6f78faaefcc Version: 35.0a1 (2.2 Master) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Notes: 1) This issue doesn't occur after a phone reboot 2) Repro frequency: 2/3 3) Attaching a logcat. Video will be added later.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Qa-Wanted for a branch check
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
I can reproduce. This looks like a Gaia issue, ni Ian, Gaia::Bluetooth developer, to do more investigation.
Component: Bluetooth → Gaia::Settings
Flags: needinfo?(iliu)
This issue occurs on Flame 2.1, and Open C 2.2 Master. Observed behavior: Bluetooth pairing request window fails to show up. Device: Flame 2.1 BuildID: 20140918145021 Gaia: 9f3588e8fdd37f6f354b5518dbeab7299b118a9d Gecko: 6f26d4fce19c Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Device: Open_C 2.2 Master BuildID: 20140919052449 Gaia: d170091ba1b5597b05f37fb259f6b8eb02568798 Gecko: 3475e6a1665a Version: 35.0a1 (2.2 Master) Firmware: P821A10v1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 ----------- This issue does NOT occur on Flame 2.0. Observed behavior: Bluetooth pairing request window shows up correctly and device can be paired properly. Bug repro rate: 0/3 Device: Flame 2.0 BuildID: 20140918082321 Gaia: 31434a3949556171f3565ca47ac2b44e810e95e6 Gecko: 5cf783171d5c Version: 32.0 (2.0) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawantedregression
[Blocking Requested - why for this release]: regression in a major core feature (Bluetooth)
blocking-b2g: --- → 2.1?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
QA Contact: pcheng
b2g-inbound regression window: Last Working Environmental Variables: Device: Flame BuildID: 20140824235254 Gaia: 5fae8a02bc31d28a4a76371bd9b0c8ef98a4b4f4 Gecko: e8efd2cf56e8 Version: 34.0a1 Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 First Broken Environmental Variables: Device: Flame BuildID: 20140825011754 Gaia: c36879d1d2644b5e059ef06aa855def460f8e08f Gecko: 42091f9dd02f Version: 34.0a1 Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 First broken gaia & Last working gecko - issue DOES repro Gaia: c36879d1d2644b5e059ef06aa855def460f8e08f Gecko: e8efd2cf56e8 First broken gecko & Last working gaia - issue does NOT repro Gaia: 5fae8a02bc31d28a4a76371bd9b0c8ef98a4b4f4 Gecko: 42091f9dd02f Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/5fae8a02bc31d28a4a76371bd9b0c8ef98a4b4f4...c36879d1d2644b5e059ef06aa855def460f8e08f Maybe caused by Bug 1043892 ?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Greg - this window seems a little odd as your patch seems to deal only with lockscreen issues but I had the QA-worker thoroughly double check her window here - so is it possible Bug 1043892 caused this?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(gweng)
Triage: regression, blocking.
Assignee: nobody → iliu
blocking-b2g: 2.1? → 2.1+
Have no idea now. As you said, the patch should only affect LockScreen. I would give a check after my current works done.
I have updated my image for flame with kk. But I'm not able to reproduce the issue with following build version. I think the issue is relative with Bug 1043892 as comment 6 mention. The unexpected respond of request mozSettings will make the pairing process abnormal. As the record in comment 1, it should not fire a notification for the incoming pairing request. Obviously, it got `lockscreen.locked = true` while the screen is unlocked. Since Bug 1043892 is fixed and uplifted to v2.1, we can duplicate the issue to it. Gaia-Rev ff6dbb006e4e60edba697639aa2a2a199b07069b Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/afc933adf723 Build-ID 20140923162022 Version 35.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental 12 FW-Date Tue Jul 22 17:32:24 CST 2014 Bootloader L1TC30011620
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(iliu)
Resolution: --- → DUPLICATE
Update flag for master. And will need QA for checking v2.1.
This issue is still reproducible on latest Flame 2.2 Master and latest Flame 2.1. Tested on: Device: Flame BuildID: 20140923233152 Gaia: ff6dbb006e4e60edba697639aa2a2a199b07069b Gecko: 1e2993c99323 Version: 35.0a1 (2.2 Master) Firmware: v180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Device: Flame BuildID: 20140924061258 Gaia: 020e6283a033e8fbcf65e7ed81c5b75ba0095f22 Gecko: d6b762814638 Version: 34.0a2 (2.1) Firmware: v180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
I'm able to reproduce the issue with following build version. The rate is 1/5. After the issue is happened, I can reproduce it every time. But my symptom is not sync with record in comment 1. After clicked to pair with remote Bluetooth device in devices list, it will not have notification. And the pairing dialog will not be shown. Hi Pi-Wei, do you meet the above symptom as me in comment 12? I never see the symptom of record in following build version. Hi Ben, I also put some console.log for tracking 'bluetooth-pairing-request' event. In this case, the remote device will receive our pairing request with dialog. But we don't receive 'bluetooth-pairing-request' system message any more after I reproduced it. Gaia-Rev 03d7bcad57ea281869976a9aed0a38849f7c8bc5 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/1735ff2bb23e Build-ID 20140924141054 Version 35.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental 12 FW-Date Tue Jul 22 17:32:24 CST 2014 Bootloader L1TC30011620
Flags: needinfo?(pcheng)
Flags: needinfo?(btian)
Remove duplicate of Bug 1043892 since we can reproduce it.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Per comment 13, reset the flag for status-b2g-v2.2.
ni? Shawn instead to check firing of 'bluetooth-pairing-request' system msgs. (In reply to Ian Liu [:ianliu] from comment #13) > Hi Ben, I also put some console.log for tracking 'bluetooth-pairing-request' > event. In this case, the remote device will receive our pairing request with > dialog. But we don't receive 'bluetooth-pairing-request' system message any > more after I reproduced it.
Flags: needinfo?(btian) → needinfo?(shuang)
(In reply to Ian Liu [:ianliu] from comment #13) > After clicked to pair with remote Bluetooth device in devices list, > it will not have notification. And the pairing dialog will not be shown. > > Hi Pi-Wei, do you meet the above symptom as me in comment 12? I never see > the symptom of record in following build version. No, my symptom has always been what was described on the original write-up at comment 0. When I tap a device to pair, the pairing request window is replaced with a notification, which leads to nothing when tapped on. > Gaia-Rev 03d7bcad57ea281869976a9aed0a38849f7c8bc5 > Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/1735ff2bb23e > Build-ID 20140924141054 > Version 35.0a1 > Device-Name flame > FW-Release 4.4.2 > FW-Incremental 12 > FW-Date Tue Jul 22 17:32:24 CST 2014 > Bootloader L1TC30011620 I have tried to locate the above build and I've found it here: https://pvtbuilds.mozilla.org/pvt/mozilla.org/b2gotoro/tinderbox-builds/mozilla-central-flame-kk-eng/20140924141054/ Did you obtain the build here? I tried both full flash from Flame-KK.zip and shallow flash of Gecko and Gaia on top of v180 base, both reproduced the issue as originally observed. The device I tried to pair with is my own Android phone. Not sure if it makes a difference. Tested on: Device: Flame BuildID: 20140924141054 Gaia: 03d7bcad57ea281869976a9aed0a38849f7c8bc5 Gecko: 1735ff2bb23e Version: 35.0a1 (2.2 Master) Firmware: v180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Flags: needinfo?(pcheng)
I just flash my image to Flame_2.0_v180_1. I think this is Firmware v180. But I still cannot reproduce it. The pairing dialog is working fine. And the 'bluetooth-pairing-request' event is coming normally. Do not meet any issue which is mentioned in comment 13. Gaia-Rev a06714c555ca7068545f10b4437a16c14cd8e7f5 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/9e3d649b80a2 Build-ID 20140925134737 Version 35.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental 27 FW-Date Thu Sep 4 14:59:02 CST 2014 Bootloader L1TC10011800 Leave assignee since I cannot reproduce it. Please give more STR to guide me to reproduce.
Assignee: iliu → nobody
Hi Pi Wei, are you still seeing this issue if using the latest or the build in Comment 18?
Flags: needinfo?(pcheng)
(In reply to howie [:howie] from comment #19) > Hi Pi Wei, are you still seeing this issue if using the latest or the build > in Comment 18? I can no longer repro this issue on latest 2.2 master. Repro rate: 0/3 on shallow flash, 0/3 on full flash. Tested on: Device: Flame (shallow/full flash) BuildID: 20141001060621 Gaia: a23d2c490b39c4699c9375e25c4acdf396a2fa85 Gecko: 835ef55e175e Version: 35.0a1 (2.2 Master) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 ------ However this issue is still reproducible on latest 2.1. Repro rate: 1/1 on full flash. Device: Flame (full flash) BuildID: 20141001060122 Gaia: b327c640fea887770d011a127e349838b3b44724 Gecko: 7359d0d0222d Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf Version: 34.0a2 (2.1) Firmware: V180 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 ------- Additionally, I noticed that on instances that the request window appears successfully in master, after pairing the paired device is NOT shown as a paired device either, so it seems that there are multiple issues on pairing with bluetooth.
Flags: needinfo?(pcheng)
(In reply to Pi Wei Cheng [:piwei] from comment #20) > Additionally, I noticed that on instances that the request window appears > successfully in master, after pairing the paired device is NOT shown as a > paired device either, so it seems that there are multiple issues on pairing > with bluetooth. Yes, I also noticed the issue as your comment. It is relative with bug 1065999.
Hi Alison, can you also try if you can reproduce this? Thanks.
Flags: needinfo?(ashiue)
I could not reproduce this issue on following KK builds. [2.1] Gaia-Rev 778ebac47554e1c4b7e9a952d73e850f58123914 Gecko-Rev https://hg.mozilla.org/releases/mozilla-aurora/rev/aa98eb8873a2 Build-ID 20141005160206 Version 34.0a2 Firmware v184 [2.2] Gaia-Rev 83f495a1c12687970f7f2840c2729795c4b88177 Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/0ed32d9a42d6 Build-ID 20141005160202 Version 35.0a1 Firmware v184
Flags: needinfo?(ashiue)
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → WORKSFORME
Flags: needinfo?(gweng)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: