ST25DV64KC NFC doesnt connect on Motorola phones (ST25 official App)

GLeon.4 · ‎2023-01-30

Hello, currently testing the new ST25DV64KC tags to replace the old M24 in our product lines....All the test phones managed to read/write via NFC, using your ST25 app....

...Except the motorolas. G30 and G50 never go past the the "please tap an nfc tag" screen. The tag is found, phone vibrates, but connection fails.

Using our own test app, i can see that the tag_connected event always fails, with java.io.IOException.

Did anyone experience the same? Are there other problematic phone brands with the ST25DV tags?

PS: on the same phones, same device and antenna, the ST M24LR work flawlessly.

Olivier L · ‎2023-01-30

Hello,

We have been contacted recently for a similar issue with a Motorola G62. We have used an NFC spy to see the commands exchanged when the tag is read by the smartphone and we have seen a problem with one of the commands sent by the Motorola G62: When sending the command "Get extended System Info", the Most Significant Byte of the UID is missing. Consequently, the tag doesn"t understand the command and cannot be used.

This problem only happens with TypeV tags with High Density (Mem >= 16 kbits). For lower density, the command "Get extended System Info" is not used so there is no problem.

This problem is not due to the ST25DV64KC tags. We have reported this issue to Motorola and they are investigating: https://forums.lenovo.com/t5/A-Series-Vibe-B-Vibe-C-Smartphones/How-to-contact-your-technical-team-to-signal-a-bug-in-your-NFC-Driver/m-p/5198326

A side comment concerning M24LR. This tag was created before the TypeV standard so it uses slightly different commands to address the extended memory. This is the reason why it doesn't have the same issue.

Best regards

Olivier

View solution in original post

Olivier L · ‎2023-01-30

Hello,

We have been contacted recently for a similar issue with a Motorola G62. We have used an NFC spy to see the commands exchanged when the tag is read by the smartphone and we have seen a problem with one of the commands sent by the Motorola G62: When sending the command "Get extended System Info", the Most Significant Byte of the UID is missing. Consequently, the tag doesn"t understand the command and cannot be used.

This problem only happens with TypeV tags with High Density (Mem >= 16 kbits). For lower density, the command "Get extended System Info" is not used so there is no problem.

This problem is not due to the ST25DV64KC tags. We have reported this issue to Motorola and they are investigating: https://forums.lenovo.com/t5/A-Series-Vibe-B-Vibe-C-Smartphones/How-to-contact-your-technical-team-to-signal-a-bug-in-your-NFC-Driver/m-p/5198326

A side comment concerning M24LR. This tag was created before the TypeV standard so it uses slightly different commands to address the extended memory. This is the reason why it doesn't have the same issue.

Best regards

Olivier

Olivier L · ‎2023-04-24

Hi,

The issue has been fixed by Motorola (please see

https://forums.lenovo.com/t5/A-Series-Vibe-B-Vibe-C-Smartphones/How-to-contact-your-technical-team-to-signal-a-bug-in-your-NFC-Driver/m-p/5198326)

I have tested that a Moto G62 5G has received the fix.

Regards

Olivier