Closed
Bug 975297
Opened 12 years ago
Closed 11 years ago
[Flame][NFC] Keep vibrating when tapped phones together
Categories
(Firefox OS Graveyard :: NFC, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: dimi, Unassigned)
References
Details
Attachments
(3 files)
STR:
1. Enable "NFC" in
touch the phone together
Expected Result:
It will only vibrate once
Actual Result:
It will keep vibrating
Comment 1•12 years ago
|
||
Yoshi, Please take a look since Dimi is on vacation.
Flags: needinfo?(allstars.chh)
We have already reproduced it and provide log to NFC supplier NXP, will keep tracking on this issue.
Comment 3•12 years ago
|
||
tested on v170. v1.3, won't vibrate
(In reply to Mike Lien[:mlien] from comment #3)
> tested on v170. v1.3, won't vibrate
That's because v170 doesn't have nfcd running by default.
If we use v170, all NFC tags/devices won't be detected.
Even I flash my two Flame devices to Android (2/27)
with system property
[ro.build.fingerprint]: [qcom/msm8610/msm8610:4.3/JLS36C/eng.archermind.20140213.193200:eng/test-keys].
The two Flame devices still keep 'beaming' (NFC beam)
I check the log,
There's always an error callback from the libnfc-nci
llcp_link_deactivate () reason = 0xb0 (LLCP_LINK_RF_TRANSMISSION_ERR)
llcp_link_deactivate () reason = 0xfc (LLCP_LINK_RF_LINK_LOSS_ERR)
llcp_link_deactivate () reason = 0xb2 (LLCP_LINK_RF_TIMEOUT)
And if I replace one Flame to other device(Nexus 4, or Nexus 5)
and it will be okay.
NFC Beam is just happening once.
So I think the problem is from the libnfc-nci, not from nfcd nor Gecko/Gaia side.
De-assign myself.
Also I spotted one thing, the back cover will also affect the NFC functionalities.
If I took the back cover from device A to device B, then device B (with back cover from device A) couldn't use NFC at all. (I use a NFC tag, or a Nexus 4 , Nexus 5 device to tap device B, I've tried around 5 minutes, I think I only get no more then 3 TechDiscovered callbacks, but if I take the back cover from B back, NFC on device B is working again.)
Assignee: allstars.chh → nobody
Flame with Flame:
https://drive.google.com/file/d/0B9v8FGlzVIoCTlVUMTM1amR5YUE/edit?usp=sharing
Captured Video, please start with 00:15
I only have two hands and I have to take 3 devices, I wasted about 15 seconds to figure it out. :P
Also I try to look at both devices to see their screen is unlock, so you can see I keep looking at both devices.
Finally I put them on the desk.
Flame with Nexus 4:
https://drive.google.com/file/d/0B9v8FGlzVIoCSmRwa28tbVloU2s/edit?usp=sharing
Sorry I found I use 1080P as video quality so the files are huge (200+MB),
I try to make the video quality poorer, and record Flame and Nexus 4 at the same time,
It's smaller now but it still needs 50+ MB.
https://drive.google.com/file/d/0B9v8FGlzVIoCQXJvTWpSdnFFLWM/edit?usp=sharing
I am not a professional photographer. :(
Log for vibrating.
Comment 9•11 years ago
|
||
Comment 10•11 years ago
|
||
Comment 11•11 years ago
|
||
hi Walter,
please verify this issue with V10D, if it works, please close this issue.
thank you
Flags: needinfo?(wachen)
![]() |
||
Comment 14•11 years ago
|
||
E/BrcmNfcNfa( 307): nfc_ncif_cmd_timeout - 2nd time, sending core reset!!!
I/BrcmNfcNfa( 307): nfc_ncif_send_cmd.
I/BrcmNfcNfa( 307): NFC recovery is in progress...
D/NfcAdaptation( 307): NfcAdaptation::HalWrite
D/NxpExtns( 307): const CNfcParam* CNfcConfig::find(const char*) const found MIFARE_READER_ENABLE=
D/NfcAdaptation( 307): NfcAdaptation::HalDeviceContextCallback: event=0
I/BrcmNfcNfa( 307): nfc_main_hal_cback event: HAL_NFC_OPEN_CPLT_EVT(0x0), status=0
D/NxpTml ( 307): PN547 - Write requested.....
D/NxpTml ( 307): PN547 - Invoking I2C Write.....
D/NxpNciX ( 307): len = 4 > 20000100
D/NxpTml ( 307): PN547 - I2C Write successful.....
D/NxpTml ( 307): PN547 - Posting Fresh Write message.....
D/NxpHal ( 307): write successful status = 0x0
D/NxpTml ( 307): PN547 - Tml Writer Thread Running................
E/BrcmNfcNfa( 307): nfc_ncif_cmd_timeout
E/BrcmNfcNfa( 307): nfc_ncif_cmd_timeout - 2nd time, going for PN547 hard reset.
D/NfcAdaptation( 307): NfcAdaptation::HalPowerCycle
I keep seeing these log in my Flame device.
Comment 15•11 years ago
|
||
hi Yanan,
can you double check NFC solution on V10D?
Flags: needinfo?(yanan.zhao)
Comment 16•11 years ago
|
||
Al, is that the V10D(B1TC100110D0)?
Dimi and I actually verified that NFC working fine in V10D. I also tested it few minutes ago and it worked alright. I can't actually get anything from logcat like you get. Do you need a fresh flash for V10D-1?
Flags: needinfo?(wachen) → needinfo?(atsai)
Comment 17•11 years ago
|
||
hi Walter,
thanks a lot, that's a good news. once it's confirmed fixed, please kindly close this issue.
![]() |
||
Comment 18•11 years ago
|
||
Close it as Resolved. It works, now.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(yanan.zhao)
Flags: needinfo?(atsai)
Resolution: --- → FIXED
![]() |
||
Updated•11 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•