Closed Bug 1041470 Opened 9 years ago Closed 9 years ago
[Flame][NFC] Peer to peer connection keep disconnecting and connecting
1. Enable NFC 2. reboot device 3. tap two device together 4. both device will keep vibrating
9 years ago
See Also: → 1034418
After checking bug 1034418, i think these two bugs describe the same issue. Mark this one as duplicate
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
This issue is almost 100% reproducible after both devices reboot and use NFC p2p connection for first time. This issue also happened in old build (central-2014-0601) or old version of nfcd. Following is the reproduce step: 1. Enable NFC on both device 2. Reboot both devices and make sure both devices should not enter screen off state (This is issue can't be reproduced if screen is off then on) 3. Open image in gallery on both devices. 4. Tap two devices together. Expect result: Both device show shrinking UI. Actual Result: One device may not shrink and the other device will keep shrinking for a while. After this step if you tap two devices together nothing will happen. If manually enter screen off state and then resume to screen on, p2p sharing will work correctly.
Hi wesley, This issue is not related to gaia/gecko/nfcd and needs vendor's help to check. Also i think this bug affects the NFC stability so should we set it to 2.1+ ?
blocking-b2g: --- → 2.1?
Summary: [NFC] Peer to peer connection keep disconnecting and connecting → [Flame][NFC] Peer to peer connection keep disconnecting and connecting
Francis, Can vendor take a look at this bug?
Flags: needinfo?(whuang) → needinfo?(frlee)
may i know whats the base image you use? V122 or V123? and whats the gaia/gecko version you flashed?
(In reply to Francis Lee [:frlee] from comment #5) > may i know whats the base image you use? V122 or V123? > and whats the gaia/gecko version you flashed? The reproduce step described in description is tested with mozilla-central pvt build 2014-06-01-04-02-03 and also the latest central build with full image flashed. I also tested V122 image but then the reproduce step will be a little different. In V122 image, it will not be able to reproduce this bug after reboot and tap for first time. But if you keep taping/untaping multiple times, then one of the device will keep vibrating.
This bug is fixed after updating NXP config file with v123 build provieded by vendor
Attachment #8463816 - Flags: review?(mwu)
blocking-b2g: 2.1? → 2.1+
9 years ago
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Target Milestone: 2.1 S3 (29aug) → 2.1 S1 (1aug)
Verified on Gaia b67ddd7d40b52e65199478b8d6631c2c28fdf41d Gecko https://hg.mozilla.org/mozilla-central/rev/005424a764da BuildID 20140730160200 Version 34.0a1
Status: RESOLVED → VERIFIED
This issue has been successfully verified on Flame 2.1 See attachment: verify_video.MP4 Reproducing rate: 0/5 Flame 2.1 versions: Gaia-Rev f8d3bf44029e0afc0124600a4bb34dba8fc1ad21 Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/f70a67a7f846 Build-ID 20141120001207 Version 34.0 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20141120.034911 FW-Date Thu Nov 20 03:49:22 EST 2014 Bootloader L1TC00011880
You need to log in before you can comment on or make changes to this bug.