2018-01-18 07:27 PM
My Samsung mobile upgraded from Android 6.0 to 7.0. But after that the 24SR seems can't detect from mobile NFC.
It happens only after the 24SR IC locked in read/write. For unlocked the chip by 24SR discovery board hardware, 24SR can detect by mobile again. I tested in Android 4.4,5.0 and 6.0 and all work. So is there any changes in Android 7.0 that cause this problem ? Please advise and thanks.
Solved! Go to Solution.
2018-06-04 07:18 AM
Hi,
iOS ST25NFC Tap source code is available under
http://www.st.com/en/embedded-software/stsw-st25ios002.html
Hope it helps.
Br,
VL2018-01-22 01:46 AM
Dear Customer,
This behavior is indeed unexpected. In order to help you out, could you please share the content of the System File that is programmed in M24SR before and after the lock?
Have a good day,
Regards,
2018-01-22 05:54 AM
Dear All,
I check the system file content and all info. is the same before and
after lock.
System file length : 18
I2C Protection : the I2C host has the SuperUser right
I2C Watchdog : watchdog is off
GPO Config : when RF session is opened
GPO low when command is computed
GPO low when programming
GPO low when session active
when an I2C session is opened
GPO low when session active
RF Enable : RF interface enabled
Memory size: 8192
Ndef file number : 1
UID :0284000206C384
ICRef :0x84
Remark: I use another LG mobile installed Android 7.0 ex-factory(not
upgraded) and work all OK with locked 24SR.
So the problem is only after I upgraded my Samsung C5 Pro mobile to
Android 7.0 from 6.0.
Thanks and any information you need please let me know.
best regards
Sunny.
在 2018-01-22 17:46,NFC product support3 写�:
STMICROELECTRONICS COMMUNITY
RE: ANDROID 7.0 PROBLEM IN LOCKED 24SR
reply from NFC product support3 in ST25 NFC/RFID Tags and Readers - View the full discussion
2018-01-24 07:31 AM
Hello Sunny,
as Android is evolving it is indeed possible some specific versions have particular issues.
Could you please send also the content of the Capability Container?
Based on that, different alternatives can be explored.
Best regards,
Jose
2018-01-25 09:55 PM
Hi,
CC file without lock read and write.
max read APDU 246
max write APDU 246
CCLEN 15
Map version 0x20
TLV control file
TLV type :04
length : 6
File ID : 0x0001
TLV File size :8192
TLV read access : 00
TLV write access :00
CC file with lock read and write , all is the same except ( TLV read and
write access : 80)
best regards
Sunny.
在 2018-01-24 23:32,Jose Mangione 写�:
STMICROELECTRONICS COMMUNITY
RE: ANDROID 7.0 PROBLEM IN LOCKED 24SR
reply from Jose Mangione in ST25 NFC/RFID Tags and Readers - View the full discussion
2018-01-30 06:31 AM
Hello Sunny,
It is difficult to comment precisely on the changes that might have happened between Android 6.0 and 7.0 on a particular phone, which is phone and manufacturer dependent.
Custom applications based on Android can normally handle proprietary read and write access conditions.
Proprietary write access is part of the NFC Forum T4T specifications. Android is natively supporting Proprietary write access conditions since Android 8.1, meaning that for example an url that is write protected on a tag (write access rights = 80h), will result in a web browser opening on that url. Smartphone manufacturers are sometimes customizing Android for their own purposes. I advise you to check with the smartphone manufacturer for updates of Android supporting this capability.
Proprietary read access is also possible. The difference is that Android does not support it natively as NFC Forum requires the NDEF file to be readily accessible (read access rights = 00h), meaning a NDEF file with an url protected in read access will not open a web browser. A custom application will be able to read the NDEF file though once the proper password has been presenting.
I hope this answer your question.
Regards,
Jose
2018-02-06 02:54 AM
Hi Jose,
Thanks and have you test any upgraded 6.0 to 7.0 phone working OK ?
best regards
Sunny.
在 2018-01-30 21:32,Jose Mangione 写�:
STMICROELECTRONICS COMMUNITY
RE: ANDROID 7.0 PROBLEM IN LOCKED 24SR
reply from Jose Mangione in ST25 NFC/RFID Tags and Readers - View the full discussion
2018-02-07 08:57 AM
Hi Sunny,
We've seen no difference of behavior on the phones we've tested between 6.0 and 7.0 and upgrading to 7.0 from a native support or from a custom application point of view. It sounds like it could this particular phone that behaves differently. If
Samsung C5 Pro supports it, w
ould it be possible for you to upgrade to 8.1 and see if the behavior is now as you expect?Regards,
2018-02-07 10:02 AM
Hi Miller,
Thanks for information. I will test my phone once can upgrade to 8.1
Best regards
Sunny.
在 2018-02-07 23:59,JP Miller 写�?�:
STMICROELECTRONICS COMMUNITY
RE: ANDROID 7.0 PROBLEM IN LOCKED 24SR
reply from JP Miller in ST25 NFC/RFID Tags and Readers - View the full discussion
________________ Attachments : blocked.gif : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006Hxt7&d=%2Fa%2F0X0000000b3P%2Fo4helxz2W6HNR_jq6wyWwDBR4QivFoBu1PohpBynot4&asPdf=false2018-02-07 09:35 PM
Hi Miller,
Moreover, any source code for iPhone NFC App ?
I can't find in website.
Thanks and best regards
Sunny.
在 2018-02-07 23:59,JP Miller 写�?�:
STMICROELECTRONICS COMMUNITY
RE: ANDROID 7.0 PROBLEM IN LOCKED 24SR
reply from JP Miller in ST25 NFC/RFID Tags and Readers - View the full discussion
________________ Attachments : blocked.gif : https://st--c.eu10.content.force.com/sfc/dist/version/download/?oid=00Db0000000YtG6&ids=0680X000006HxiY&d=%2Fa%2F0X0000000b3M%2F5Cz_mbo6CON2zZ1CD1ulrYbFepn1qjfJQHZDtMlG0HY&asPdf=false