Closed
Bug 1220062
Opened 9 years ago
Closed 8 years ago
Implement NFC API
Categories
(B2GDroid Graveyard :: General, defect, P1)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: qiutian, Assigned: reuben)
References
Details
Attachments
(3 files)
544.35 KB,
text/plain
|
Details | |
732.64 KB,
video/3gpp
|
Details | |
46.52 KB,
patch
|
Details | Diff | Splinter Review |
[1.Description]:
[B2GDroid]Launch "Settings" and observe, there is no NFC option.
Found time:9:53
See attcchment:AriesKK_NFC.3gp & logcat_B2G2.txt
[2.Testing Steps]:
1. Launch "Settings".
2. Observe.
[3.Expected Result]:
In step 2, there is a NFC option and user can launch NFC.
[4.Actual Result]:
In step 2, There is no NFC option in Settings.
[5.Reproduction build]:
Gecko: 44.0a1
Android version:
4.4.4(Build Number 23.0.A.2.93)
[6.Reproduction Frequency]:
Always Recurrence,5/5
[7.TCID]:
10580
[8.Note]:
This function works normally on latest build of flame v2.5 & aries v2.5.
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Updated•9 years ago
|
status-b2g-v2.5:
--- → unaffected
Product: Firefox OS → B2GDroid
status-b2g-v2.5:
unaffected → ---
Priority: -- → P1
Summary: [B2GDroid]There is no NFC in Settings. → Implement NFC API
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → reuben.bmo
Assignee | ||
Comment 2•9 years ago
|
||
This handles peer and tag discovery and writing NDEF data to peers. There's an impedance mismatch between the Android and WebNFC APIs, since Android does peer discovery synchronously and the WebNFC API is all async. Sometimes this causes the peer to be lost by the time we do the round trip from Android to Gecko and back, but I think it can be fixed by using nfc.tech.* directly instead of the Android Beam API. This is required for writing NDEF to tags anyway, so it's not a problem.
Assignee | ||
Comment 3•8 years ago
|
||
Closing B2GDroid bugs.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•