Closed Bug 1010123 Opened 7 years ago Closed 7 years ago
Improve the stability and sensibility of NFC Card Emulation Modes
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140506152807 Steps to reproduce: Test Configuration: 1. Google Nexus-5 2. NFC-SIM card 3. reader side POS simulator to monitor the presence of contactless card Test Action: tap phone against SCM reader 10 times and say how many times work correctly Actual results: 8 times fail to get CE established between handy/SIM and reader; 2 times work. Expected results: 10 taps, at least 7 taps should work immediately. in case occationally failure, the user need to tap again.
Dimi, in the attached nfcd-test.log, go the end of the file and the last block of logs are for a success tap. prior to that, I did several tries, but all fails, which means that I cannot see any "contactless smart card" emulated during the tap on the reader side.
(clear whiteboard) This is derived engineering work from bug 989889. So we don't need to re-tag the [ucid:xxx, 2.0, FT:RIL] again. Setting corresponding dependency is good enough.
Whiteboard: ucid:NFC17, 2.0, FT:RIL
blocking-b2g: --- → backlog
feature-b2g: --- → 2.1
Assignee: nobody → dlee
feature-b2g: 2.1 → 2.0
this is stability defect instead of feature.
blocking-b2g: backlog → 2.0+
feature-b2g: 2.0 → ---
I didn't see this issue happen on Flame which should be higher priority. Change 2.0+ to 2.0? to triage.
blocking-b2g: 2.0+ → 2.0?
Ming, can we close this bug as WORKSFORME?
(In reply to Yoshi Huang[:allstars.chh] from comment #5) > Ming, can we close this bug as WORKSFORME? yes.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.