undefined | Better HN

0 pointsewpratten1y ago0 comments

Thank you very much!

Something's clearly up there. You can see that even IOS and Android disagree with each other on what NDEF should look like by a few bytes. Very interesting.

0 comments

stavros1y ago

Yep, 89 EC A9 7F 8C 2A 00 00 on iOS versus FF FF FF FF FF FF on Android. Interesting how the number of bytes is different, I should play with them a bit.

ewprattenOP1y ago

There's lots of info about the NDEF "packet" format online.

I used this page as reference when I was putting together the "magic bytes" in the final section of the blog post: https://www.oreilly.com/library/view/beginning-nfc/978144932...

stavros1y ago

This is fantastic, thanks!

Also, one thing that might be of interest: Even after a wipe and an ndefformat, my Android-written tag can be read by my iPhone 15.

NFC tools will only read it in compatibility mode, though.

1 more reply

j / k navigate · click thread line to collapse

0 pointsewpratten1y ago0 comments

Thank you very much!

Something's clearly up there. You can see that even IOS and Android disagree with each other on what NDEF should look like by a few bytes. Very interesting.

0 comments

stavros1y ago

Yep, 89 EC A9 7F 8C 2A 00 00 on iOS versus FF FF FF FF FF FF on Android. Interesting how the number of bytes is different, I should play with them a bit.

ewprattenOP1y ago

There's lots of info about the NDEF "packet" format online.

I used this page as reference when I was putting together the "magic bytes" in the final section of the blog post: https://www.oreilly.com/library/view/beginning-nfc/978144932...

stavros1y ago

This is fantastic, thanks!

Also, one thing that might be of interest: Even after a wipe and an ndefformat, my Android-written tag can be read by my iPhone 15.

NFC tools will only read it in compatibility mode, though.

1 more reply

j / k navigate · click thread line to collapse