ST25DV64K application crashes

[Greidimar]

I'm trying to read the ST25DV64K memory but the ST25 NFC Tap app just keeps trying to read it, it keeps blinking as if it's trying to read it and then fails and the screen goes back to normal. I'm using a Samsung S24 Uktra with Android 16.

[Brian TIDAL]

Hi,

how many bytes do you try to read? Does it work for 64 bytes? Is your device an ST25DV64K or an ST25DV64KC? Do you use an ST demo board such as X-NUCLEO-NFC07A1 or a custom board?

Which version of the ST25 NFC Tap do you use?

Rgds

BT

[Greidimar]

Hi,

I can't read the bytes; it keeps flashing.

The device is an ST25DV64KC-I.

ST25 NFC Tap version V3.12.0.

It works on Android 13, 8, and 15. It doesn't work on Android 16!

 

[Brian TIDAL]

Hi,

Do you use an ST demo board such as X-NUCLEO-NFC07A1 or a custom board? If custom board is being used, could you describe the antenna characteristics (size, etc.)?

What do you mean by "it keeps flashing"?

Rgds

BT

[Greidimar]

I researched it and the problem is that Android 16 has an NFC reading error, as explained on the Git website.:

 https://github.com/nfcim/flutter_nfc_kit/issues/222

 

[France Berthelot]

Hello

Based on your findings, i did some tests:

1. Pixel8/Android16 ST25NFCTap V3.12.0 with ST25SDK 1.13.0 and Reader Interface 1.0.13: Memory content / Read = works fine on 64 or 8192 bytes reading
2. Samsung S25/Android16/OneUI 8.0 ST25NFCTap V3.12.0 with ST25SDK 1.13.0 and Reader Interface 1.0.13: Memory content / Read = works fine on 64 or 8192 bytes reading

Just want to clarify:

Do you confirm that you have issues with ST25NFCTap delivered? 

With your own implementation?

Have you rebuild the apk (in this case can you give us more informations on JDK used,...) ?

 

The only difference between your env and mine, is overall the phone. I got on my side the apk from: STSW-ST25001 | Product - STMicroelectronics

For information, i use a ST25DV64KC as delivered on the Discovery kit, having an AAR NDEF.

Rgds,FB

[Geraud-Iotize]

Hello,

We are using ST25DVx devices in our products and ended up with the same issue on our apps, with Samsung devices older than S25 (S24, A35,...) running on Android 16 / One UI 8.0. No issue with Pixel phones on Android 8.

From our analysis, the NFC service crashes on these devices on its own.
The GitHub link provided earlier shows the same error. While it is not explicitly said by the user, I think they are using one of those phones for the test.

We could also find issues with other NFC applications through the Samsung forums describing the same behaviour.
It appears that the manufacturer is aware of the issue, but I did not find any official statement around this.

A workaround found on the A35 that I use for testing is to deactivate/reactivate NFC from the quick settings menu before each NFC connection.

I hope this information may help you.

 

Best Regards,
Géraud