LiveCode Forums.

I need to add NFC reading abilities to an Android 11 Tv Box. My needed reading is limited to a string from a TAG.
The Tv box does not have the OS software or the hardware for this, so I was thinking of using an external hardware (like the ACR1552U) and creating an extension in LCB, since the current Android NFC of LC10 does not recognize the external NFC hardware.
Before attempting to do this, I am trying to understand why the Android NFC capabilities in LC are listed in the standalone setting, not as an extension.

Is this NFC code embedded in LC? If not, where is it located? Could it be interfering with my project of an extension?

Thanks for any help
Trevix.

Yes, NFC is part of the LC engine, intended for mobile use on Android.

Hello everybody.
I was able with Claude.AI to create the extension, that uses an external NFC reader to read NFC from LC.

Now I have a much more complicate problem:
When launching the test app, with the external reader connected, the Android 11 OS of the tvBox shows, on the first time, a dialog alert:

"Allow TestNFCHD to access ACR122U PICC Interface?"

In this dialog there is not a "remember" check box.

My problem is that re-booting the Tv Box and, after that, launching again the Test app, I get again the same dialog box.
That is, it does not behave like Bluetooth, camera, etc permissions, when it ask you only once.
I understand that in this case is different then other permissions.

I tried to put a "usb_device_filter.xml" file on the "res" folder of the extension and on the Android runtime of LC10, also modifying the runtime Manifest, but I get an error when trying to install the test stack (see attached image).
Probably because there is already a "nfc_tech_filter.xml" file, in the runtime folder?!?

I confess that I don't understand any of this. Claude.AI suggests the following: "LiveCode selectively includes only specific XML files (not all of them)".
Is there any solution?
Thanks.
Trevix

I've never tried that, so your bestie bet is to contact LC support and see if they can help.

Solved using Macrodroid and a DEX file (Javascript byte code) that runs via shell command with root.
Now the dialog, after reboot, does not appear anymore after the first time.
So long.