FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

ST25DV04KC android 16 problem

DanZak
Associate

‎2025-10-20 6:44 AM

Hello, I have a problem after updating the system to Android 16. Before, everything was great. I have a custom application to work with ST25DV04KC. Now, the NFC service crashes before connection, and the system app opens NDEEF. Only on the first "tap," after turning NFC on/off, the connection is correct. Is there any workaround before they change it in Android? Thanks for any help.

5 REPLIES 5
JordiCasadevall
Associate II

‎2025-10-24 2:18 AM

I also have a problem after updating to Android 16. I have a working app with ST25DVCTag and Android <= 15, but with Android 16 I must manually restart toggle NFC in the device before the re-estarting the app.

0 Kudos
Brian TIDAL
ST Employee
In response to JordiCasadevall

‎2025-10-28 2:51 AM

Hi @JordiCasadevall @DanZak ,

Which model of Android phone do you use (Manufacturer, Model)?

"I have a custom application to work with ST25DV04KC": Is this custom App based on ST25 SDK? If yes, which version?

Can you read the tag with the ST25 NFC Tap App? With other NFC app such TagInfo?

Rgds

BT

 

In order to give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
0 Kudos
JordiCasadevall
Associate II
In response to Brian TIDAL

‎2025-10-28 3:43 AM

Hi BT,

with TagInfo app, ST25 NFC app and our developed app: After a tag is discovered and then lost, it does not work unless I toggle NFC in the mobile or I wait for a 60/70 seconds aprox. 

My Android is a Samsung Galaxy S23 upgraded to One UI Version 8.0 Android 16.

With Android 15 everything perfectly without having to wait between tag lost and new tag discovering.

The App is based on ST25 SDK v1.10.0 and st25_android_reader_interface-1.0.10-release. Tried with S25 SDK v1.13.0 but is compiled with JDK 21 (class file major version 65). We need JDK 17 (class file major version 61) since it is the max stable version fully supported by Android and React Native, and Android Gradle Plugin.

I look forward to your response, thank you,

Jordi

0 Kudos
France Berthelot
ST Employee

‎2025-10-30 7:12 AM

Hi @JordiCasadevall @DanZak ,

 

I did some tests on Pixel8/Android16 and Samsung S25/Android16 and not seen direct issue....

We talk also about some version and JDK, on my side i have JDK17, you can find on st.com materials build with JDK17....

Please see : STSW-ST25001 | Product - STMicroelectronics

At the end of page, you have an apk + src of this apk. With sources you can find in the android project, both ST25SDK + ReaderInterface at version : st25sdk-1.13.0, st25_android_reader_interface-1.0.13-release.

Can you please advise if theses artefacts are usable on your side and able to allow progress to be made on the problems?

Rgds, FB

0 Kudos
JordiCasadevall
Associate II
In response to France Berthelot

‎2025-10-30 8:27 AM

Hi @France Berthelot 

JDK17 issue solved, from https://www.st.com/en/embedded-software/stsw-st25001.html I found libraries compiled with Major 52 (ok for jdk 17)

Previously I downloaded from https://www.st.com/en/embedded-software/stsw-st25sdk001.html  with Major 65 (jdk 21)

So I was able to compile my app with ST25 1.13.0 and st25_android_reader_interace-1.0.13, good.

But the NFC issue with my Samsung S23 updated to Android 16 continues with our app and also your app "ST25 NFC Tap", while with Android 15 everything worked fine. 

The problem with ST25 and some devices with Android 16 has also been reported here: https://forum.developer.samsung.com/t/one-ui-v8-update-causing-nfc-readermode-to-crash-low-level-driver/42606

0 Kudos
Top