Closed Bug 1156458 Opened 10 years ago Closed 10 years ago

[Bluetooth] Screen may flash white when attempting to pair Bluetooth devices

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v2.1 unaffected, b2g-v2.2 affected, b2g-master affected)

RESOLVED WORKSFORME
tracking-b2g backlog
Tracking Status
b2g-v2.1 --- unaffected
b2g-v2.2 --- affected
b2g-master --- affected

People

(Reporter: onelson, Unassigned)

References

()

Details

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

Description: When a user attempts to pair 2 different bluetooth devices (tested with 2 phones that send Bluetooth pins to eachother), they may observe the screen flash white very briefly while the dialog screen attempts to load. PreReq: * second device with bluetooth enabled, visiblity enabled Repro Steps: 1) Update a Flame to 20150420010204 2) Open the Setting app 3) Navigate to Bluetooth 4) Enable bluetooth 5) Send a pair request to your second device 6) Observe screen when dialog spawns Actual: Screen flashes white when pair-request dialog appears on screen Expected: Screen transitions with no faults when pair-request dialog appears Environmental Variables: ------------------------------------------- Device: Flame 3.0 Build ID: 20150420010204 Gaia: cb41d8421da5dc4f16ea566ea2917a9b7f828154 Gecko: 50b95032152c 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 Device: Flame 2.2 BuildID: 20150420002502 Gaia: c15a2b6d3a783813959c2b3bffd2a131f4270b9e Gecko: cc02ee38b252 Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 37.0 (2.2) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0 ------------------------------------------- Issue DOES NOT REPRO on 2.1 for flame devices Results: Screen transitions to black before producing bluetooth pair-request screen Device: Flame 2.1 BuildID: 20150420001205 Gaia: bbe983b4e8bebfec26b3726b79568a22d667223c Gecko: b85d4f4a6d61 Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429 Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 ------------------------------------------- Repro frequency: 3/10 See attached: video- https://youtu.be/BEnsskPiHQk
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Minor regression with low reproduction, finding a window will be too costly. Not nominating to block 2.2 but NI on component owner for tracking.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga) → needinfo?(ashiue)
Keywords: regression
Transfer to current component owner, Teri. Hi Teri, could you please help to check this issue? Thanks.
Flags: needinfo?(ashiue) → needinfo?(twen)
Mark bug tracking base on comment 1.
Flags: needinfo?(twen)
Dear Teri, Does this issue have the patch? Thanks, Xiaodong
Hi Teri, would you mind helping us identify if this bug Bug1177163 is the duplicate of this bug ? Thank you very much ! https://bugzilla.mozilla.org/show_bug.cgi?id=1177163
Flags: needinfo?(twen)
Hi Rachelle, Yes, bug 1177163 is a duplicate. The repro rate was not consistent on flame.
Flags: needinfo?(twen)
ni? gfx gecko dev Jerry. Jerry, can you help check whether gfx can fix the symptom in comment 0 video (youtube link)?
Flags: needinfo?(hshih)
The failure can give support, sure is the same as the bug1177163.
Flags: needinfo?(wu.jiabin)
I will try to compare the frame tree between v2.1 and v2.2 first.
Dear Jerry, Is there any method or tool to compre the frame tree between v21. and v2.2? Thanks, Xiaodong
Dear Jerry, Is there any update for this issue? Thanks, Xiaodong
I'm not sure what's going on here. I can't reproduce this problem with my flame device(flame-kk 2.2 20150420002502) The white screen might the background color in system's css setting, but we use black color currently. I can see the different color when I create the bluetooth pair with the following css changing. In $GAIA_PATH/apps/system/style/window.css: .appWindow:not(.homescreen):not(.searchWindow):not(.lockScreenInputWindow):not(.globalOverlayWindow) { background-color: black; <=== please change to another color and test again. }
Flags: needinfo?(hshih) → needinfo?(duan.xiaodong)
(In reply to Jerry Shih[:jerry] (UTC+8) from comment #13) > I'm not sure what's going on here. I can't reproduce this problem with my > flame device(flame-kk 2.2 20150420002502) > > The white screen might the background color in system's css setting, but we > use black color currently. I can see the different color when I create the > bluetooth pair with the following css changing. > > In $GAIA_PATH/apps/system/style/window.css: > > .appWindow:not(.homescreen):not(.searchWindow):not(.lockScreenInputWindow): > not(.globalOverlayWindow) { > background-color: black; <=== please change to another color and test > again. > } I'll give it a try, thanks you Jerry
Flags: needinfo?(wu.jiabin)
Dear Jerry, This issue can be reproduced on ZTE OPENL(MSM8909) FFOS2.2 platform with more frequences. Thanks, Xiaodong
Flags: needinfo?(duan.xiaodong)
Hi Xiaodong, Does the ZTE OPENL device still show the white screen even though with different css color? .appWindow:not(.homescreen):not(.searchWindow):not(.lockScreenInputWindow):not(.globalOverlayWindow) { background-color: red; <=== how about change to red and test again? }
Flags: needinfo?(duan.xiaodong)
Dear Jerry, 1.First, Screen shows read backgroud. 2.Then white screen shows immediately in 1-2 seconds. 3.Finally,Screen shows normal bluetooth setting window. Thanks, Xiaodong
Flags: needinfo?(duan.xiaodong)
From checked with Jerry, the current situations are: 1. Flame device is not easy to reproduce. I will try to ask for a fixed way to reproduce it. 2. Since we don't have ZTE OPENL code base to look into this issue, we can't do anything on OpenL. Adding qawanted to find out a fixed way to reproduce it.
Keywords: qawanted
Dear Vincent, Which part of code do you need? Gaia and Gecko for OPENL on latest version? Thanks, Xiaodong
Dear Vincent, BTW,We use the below tag for fetching code from Qualcomm. AU_LINUX_GECKO_LF.BR.1.2.3.00.00.00.000.173 Thanks, Xiaodong
(In reply to Duan Xiaodong from comment #19) > Dear Vincent, > > Which part of code do you need? Gaia and Gecko for OPENL on latest version? > > Thanks, > Xiaodong If you can offer the way you get for Gecko/Gaia, it would be better way to go. The current code base I got for OpenL can't launch b2g.
Unable to find better Repro rate and STR (than what is listed in Comment 0) for this issue. Both test devices I used had the following variables... Environmental Variables: Device: Flame 2.5 BuildID: 20150714010206 Gaia: 7676b68b4d32ed13243eeb719188847121bd5611 Gecko: 0931671a14ef Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 42.0a1 (2.5) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0 Leaving qawanted tag for other testers to try.
For me the repro rate is extremely low, maybe 1 in ~20 attempts. I don't think we are going to find a better STR for this bug but leaving the tag for one other to attempt. Tested on: Device: Flame (full flashed, 319MB, KK) BuildID: 20150720010206 Gaia: 3fac3ed7b8c887351098ffc677769ddc36abb3d0 Gecko: 202e9233d130 Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4 Version: 42.0a1 (2.5 Master) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
I was also unable to find better STR for this issue. I had slightly better luck than the others, 4/26 attempts between both Flame and Aries, but no changes to the steps made it occur more often. Environmental Variables: Device: Flame 2.5 BuildID: 20150721010202 Gaia: 4fe0507781f3ed56c8ae5e66dd9489165d1ff68e Gecko: 3a4bfa5d2d02 Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423 Version: 42.0a1 (2.5) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0 Environmental Variables: Device: Aries 2.5 BuildID: 20150721215303 Gaia: 84c3bf622e211046d905803b34de5d331761f22d Gecko: a6b93cceaf4e Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd Version: 42.0a1 (2.5) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Unfortunately, we cannot find better STR for this issue after several attempts. This just appears to be a very low reproducible issue. Removing qawanted.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Keywords: qawanted
Teri could you help do the final check and close this issue if it's not reproducable
Flags: needinfo?(twen)
No longer reproducible on the latest aries-kk master. Resolve as WORKSFORME. Aries Build ID 20151127111703 Gaia Revision ee6d8625c9d76de2f6614c87bb82b301bc37c7a9 Gaia Date 2015-11-27 07:50:14 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/47b49b0d32360fab04b11ff9120970979c426911 Gecko Version 45.0a1 Device Name aries Firmware(Release) 4.4.2 Firmware(Incremental) eng.worker.20151127.103319 Firmware Date Fri Nov 27 10:33:27 UTC 2015 Bootloader s1 Flame Build ID 20151110034006 Gaia Revision cf650aa1521151d5e4ac6d04188f911712271ec1 Gaia Date 2015-11-09 19:24:01 Gecko Revision https://hg.mozilla.org/mozilla-central/rev/4a7526d26bd47ce2e01f938702b91c95424026ed Gecko Version 45.0a1 Device Name flame Firmware(Release) 4.4.2 Firmware(Incremental) eng.worker.20151110.030132 Firmware Date Tue Nov 10 03:01:41 UTC 2015 Bootloader L1TC000118D0
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(twen)
Resolution: --- → WORKSFORME
Thanks Teri!
You need to log in before you can comment on or make changes to this bug.