OK following up on this. Because I'm using nightly builds on my ROM, I went back to the last stable one, on Android 4.3. Things worked better. So I cherry picked a nightly release from April 10, 2014, and this build seems to work just as well for me as the older stable 4.3 release did. All tests below are on PACman 4.4.2 build April 10, 2014. Now I can reliably read/write to all 4 inlays, still with some strange issues.
Here are some things that I tried on my Galaxy S3 phone:
- Creating a text tag "The quick brown fox jumps over the lazy dog." works just fine. I get the little pop up indicating that it worked, and reading it confirms that.
- Creating a text tag "The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog." works fine.This works on all 4 inlays.
- Creating a text tag "The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog. The quick brown fox jumps over the lazy dog." fails to write. I will hear the double beep tone indicating that it successfully accessed a NFC tag, but then the app freezes. This happens consecutively with multiple attempts on all 4 inlays.
- Creating a text tag "0123456789012345678901234567890123456789" actually fails to write.
- Creating a text tag "012345678901234567890123456789" fails.
- Creating a text tag "01234567890123456789" reads/write fine.
All Twitter, Facebook, YouTube, and URL tags work. Long URL tags also fail, seems to also be a limitation of the memory size (which is expected).
What's irking me is that a string of 30 consecutive digits fails, but a string of 90 characters (letters and spaces) can be saved? Is this a bug with the application or maybe the tag?
I'm going to try and install the non-beta 0.1 version and see if this same issue with long digits happens.