Geek asks and answers

Android Beam error when data transfer length is out of range

I just implemented an Android Beam project for transferring text data from Nexus S to an NFC card reader using the CreateNdefMessageCallback callback and creating the NdefMessage method in the createNdefMessage (NfcEvent) method. At first, everything is fine, but I found that if the length of the transmitted text is more than 42 bytes (do not include the NDEF head), it could not output the data. Although I pressed the screen several times, there is no answer. I also tried recording NDEF Records, but the SDK suggested that "applications should not try to manually block NDEF records." Does anyone encounter the same issue? It would be very grateful for your suggestion. thank!

+3
source share
1 answer

I already sent NDef messages between two Android devices (several Galaxy Nexus, Nexus S, 4.0.1, 4.0.2 and 4.0.3) with 32,000 bytes + NDef header. If you are really careful (do not move the device) and the patient (this lasts several minutes), this can be done with any problem.

So, the problem should not be in the Android part, but I have not tested it with a card reader.

+1
source

More articles:


All Articles