Multiple card support + huge thanks for the project

[TostoyKir]

Hello!

First of all, I want to sincerely thank you for this project.
TensorCardEmulator is an impressive and very well-thought-out solution — especially considering how limited NFC emulation usually is on Android devices. The fact that this works on Tensor-based Pixels is really great work. Respect for making this open and usable for the community.

I would like to ask about the possibility of adding support for multiple cards (multiple UIDs) in the future.

At the moment, the emulator works perfectly with a single card, but in real-life usage scenarios this can be limiting. For example:

• home access
• office or workplace access
• parking or garage systems
• multiple buildings or entrances

Being able to:

• store multiple cards
• switch between them inside the app
• or quickly select which UID to emulate

would make the project significantly more powerful and practical for daily use.

From a user perspective, this would greatly improve usability.
From a technical perspective, it would make TensorCardEmulator one of the most complete UID-based NFC emulators available on Android.

Thank you again for your amazing work and for sharing this project.
If this feature is already planned or technically feasible in the future, I would really appreciate any information.

Best regards!

[eXtreames]

Thank you, very nice! Soon I will add the ability to save several cards. The main problem is to come up with a beautiful design 😜

[TostoyKir]

That’s great news, thank you so much! 🙌
Really appreciate your openness and fast response.

Totally understand the design challenge 😄
From a user perspective, functionality is the most important part — even a simple list or basic selector would already be incredibly useful. The UI can always be improved later.

In any case, thank you again for your work and for listening to feedback.
Looking forward to the update!

[TostoyKir]

Hi!

I would like to report an issue and ask for your help.

After updating my device to Android 17 Beta 1, the card emulation stopped working.
Before the update, everything worked perfectly.

Current behavior:

• NFC scanning works correctly
• The card UID is read and saved
• However, the phone no longer emulates the card when tapped to the reader

Device details:

• Google Pixel 8
• Tensor SoC
• Android 17 Beta 1
• Root via Magisk

Nothing else was changed except the Android update.

Could this be related to changes in NFC or system security in Android 17 Beta?
Please let me know if there is anything I can test or provide (logs, debug info, etc.).

Thank you very much for this amazing project and for your time!

[eXtreames]

Most likely something has changed in the NFC system. This can be checked, enable card emulation and try to pay for the purchase through Google Pay. If the purchase is paid, my theory is correct. I myself am still on Android 16, because of this, I can not personally fix it.

[TostoyKir]

I’ve collected logs on Pixel 8 with Android 17 Beta 1, and I think I found the root cause.

It looks like Android 17 has tightened SELinux restrictions related to NFC and Magisk.
During card emulation, the app tries to modify the NFC HAL config file
(/system/vendor/etc/libnfc-hal-st.conf) via su, but this operation is now blocked.

Log highlights:

• SELinux denies access to /debug_ramdisk/.magisk/device/socket
• su (Magisk) crashes with SIGTRAP
• As a result, the NFC HAL config is not applied

Google Pay and other HCE-based NFC apps work correctly, so NFC itself is fine.
The issue seems to affect only low-level / UID-based NFC emulation.

Most likely, Android 17 no longer allows modifying NFC HAL configs at runtime via Magisk.

Let me know if you want the full log file or if you’d like me to test any workaround.
I’m happy to help with further testing.

[eXtreames]

My method uses systemless approach. I don't change files in /system. I copy configs from system to overlay in magisk module and modify it. By the way, you can try to reinstall the module, this may help. Check for files libnfc-hal-st.conf and libnfc-hal-st-proto1.conf in /system/vendor/etc.

[eXtreames]

By the way, it's quite possible Magisk issue 🫣

[TostoyKir]

I’ve checked the files on my Pixel 8 (Android 17 Beta 1).

In /system/vendor/etc/ I can confirm that both files are present:

• libnfc-hal-st.conf (6856 bytes)
• libnfc-hal-st-proto1.conf (40 bytes)

So the config files do exist on the system.
It’s possible that on Android 17 the NFC HAL is now using proto1, or that the behavior of vendor overlays for these files has changed.

Also, just to clarify — I don’t see any general issues with Magisk itself.
Root works correctly, other Magisk modules function as expected, and I haven’t noticed any abnormal behavior after updating to Android 17 Beta 1. From the user side, Magisk seems to be working fine.

That said, it could still be related to how overlays or vendor configs are handled specifically in this case on Android 17.

Let me know if you want me to:

• check which config file is actually being used at runtime
• test a modified proto1 config
• try different Magisk versions (stable / canary)
• or compare behavior with KernelSU

I’m totally fine with continuing testing and trying different scenarios.
Please let me know what you’d like me to check next, and I’ll do it.

[eXtreames]

Hm, proto1 weighs too little, can you throw off both files?

[TostoyKir]

I’ve attached a ZIP archive with both NFC config files from my Pixel 8 (Android 17 Beta 1).

• libnfc-hal-st.conf
• libnfc-hal-st-proto1.conf

[eXtreames]

libnfc-hal-st-proto1.conf no longer exists. what are the files in this folder starting with libnfc***?

[TostoyKir]

Here is the list of files in /system/vendor/etc/ starting with "libnfc" on my Pixel 8 (Android 17 Beta 1):

Please let me know which file you expect to be used by the NFC HAL on Android 17, and I can test or modify it if needed.

[TostoyKir]

Hi!

Just a quick follow-up in case my previous message got lost.
I’m still very interested in testing a fix or an updated version on Android 17 Beta 1 and would be happy to provide any additional logs or test results if needed.

No rush at all — just wanted to let you know I’m here and ready to help with further testing.

Thanks again for your work on the project!

[eXtreames]

Hi, I don't have much time right now, but as soon as I do, I'll try to either fix the current method or try it through LSPosed.