check if you have other applications that use NFC running in the background (e.g. if you lock your device having the NFC ring control app open) as this will result in problems with directing the NFC input to the right app
Ok, new phone, app is still telling me its not an NFC ring when I try and register.
Exact message is "Uh oh This might not be a genuine NFC Ring, please try the other side of your Ring"
When I try the other side, same message. Also this message appears multiple times, this time it was 16 times (the number appears to go up each time I test the ring" Other applications (NFC Tag Writer) can read the NFC tags on the ring. Why does the app not think my ring is genuine? Please fix your app!
It seems like your tag is either overwritten or some application is stopping the unlock app from registering the ring.
please try to remove the tag in the unlock app an then add it again. Please note that the tag which is used for unlocking (with the NFC ring unlock app) can not be used for something different than unlocking.
hope this helps.
@JimmyDingDongs did you try this? Try registering both sides as keys, and then test.
If you can still access the app using the ring then the ring still works, it's just not launching the unlock properly when the phone is locked.
Unlock App writes data to the inlay which must be retained unaltered in order for it to work.
Alternatively, if you're rooted then why not try something else that will allow you to bypass the standard lock screen using a ring?
Hey @hauspro , i've just replied to your support ticket with full information and this issue should now be resolved for you. Really sorry this has taken so long for us to sort for you. Let us know if you have any further issues.
@Kris - have you updated the NFC Ring Control app to the latest version from the Play store?
If you have done so and are still getting the issues - shoot us an email to firstname.lastname@example.org with the email address you are trying to register and i'll check it out for you. We did identify an issue with the way data way being saved in our database, but made some changes a good few weeks ago now that should have solved the issue.