Native hook issues with SM-A526B about nfcgate HOT 5 CLOSED

@Lassie111 It looks like the behavior you are describing has nothing to do with Samsung devices and everything to do with the type of NFC Chip. Your NXP chip has the same issues as many OnePlus models with the same chip (i.e. it only uses random NFCIDs and does not accept a manually set one). @cydef1 has a Samsung NFC chip, where that issue has never been reported so far.

from nfcgate.

Thanks for contributing!

Your issue looks like this other Samsung-specific issue: #146. Please try the debug-version linked here: #146 (comment). We will soon incorporate this into a future release.

from nfcgate.

from nfcgate.

Now it works perfectly

from nfcgate.

Now it works perfectly

@cydef1 Does the cloning work correctly though? For my device even after Native hook is enabled, the NFC chip does not accept the NFCID and presents a random one instead (#153).

I wonder if it is a problem with my device only or with all Samsung devices.

from nfcgate.