atkinchris
Member since May 2017 • Last active May 2017Most recent activity
-
-
-
Which app were you using with your Nexus 10 to test @Gordon? I used both NFC Tools and NFC TagInfo by NXP, the latter of which created far more NFC events.
With both apps and @AntiCat's FW, I can see Select CL1 commands reaching the JS event system (would have expected these to be handled and not propagated).
-
-
-
Playing with this more, crashes appear to be more common when the reader is removed, such as tapping the phone against the Puck then lifting it again.
Doing this with
digitalPulse(LED3, true, 300)
being called in response to the event, I managed to get the Puck to crash with the LED remaining on until the battery was pulled. -
-
I can reproduce this same issue using the Web IDE command pane and
1V92
.NRF.nfcURL('https://www.google.com');
- Touch tag to phone. Observe website is opened.
NRF.nfcURL();
- Touch tag to phone. Observe no website is opened.
NRF.nfcURL('https://www.google.com');
- Touch tag to phone. Observe no website is opened.
N.B. My Nexus 5X opens a new tab in the foreground with the URL, every time the tag is tapped, if the web browser is in the background.
Both - I was using
NFCon
events in1v92
(downloaded from here https://www.espruino.com/binaries/) andNFCrx
in AntiCat's.NFC TagInfo gives me more information on a tag - and was much easier to trigger crashes with.