I tried http://www.thesayansblog.net/2017/11/re-enable-nfc-smart-lock.html but it didn't work for me.
I have found another way to re-enable the NFC Smart Lock feature on Android, though it still requires root and manually editing a preferences file.
Details on pastebin: https://pastebin.com/2RSZzERg
Heads up, with this workaround we might re-enable NFC Smart Lock: http://www.thesayansblog.net/2017/11/re-enable-nfc-smart-lock.html
AFAIK you need to downgrade Play Services, enable NFC Smart Unlock and then update again. I haven't tried it myself yet, though.
This needs more visibility. If we can get enough users to star this issue, maybe Google will review it and reconsider bringing back NFC to Smart Unlock.
Now there's an official statement from Google. They're deprecating NFC unlock because of "low usage" and have already removed all references to it from their online manuals.
This and the lack of communication might very well signal the end of the NFC ring. Not even the much-vaunted payment-enabled model will make up for the loss of this feature.
Came here to comment about this issue. Apparently, even if you still have the NFC Smart Lock feature enabled and working so far, you will lose it when you factory reset or otherwise log out of your Google account on your Android device. Here is a reddit thread with a good writeup on the subject: https://www.reddit.com/r/Android/comments/72tj6u/psa_google_have_quietly_removed_nfc_smart_unlock/
Can confirm 2016 rings work with Virdi AC2100:
http://www.virdi.eu/produkty/1,terminale_biometryczne_+_rfid/2,virdi_ac-2100.html
It might have something to do with Android Pay, or some other related app that has support to make payments via NFC. I've heard these need the device to have the lockscreen on for safety.
You'd have to convince the staff to register your ring as a valid tag, if they are compatible. Most of them are, the hard part is the convincing...
No, the 4-hour timeout is a different behaviour (and intended, it seems). That is, the Smart Lock feature disabling itself after 4 hours of inactivity. I think it takes longer than that.
On the other hand, the bug seems to cause the NFC radio to stop polling for tags after locking. So even though Smart Lock is enabled, it can't read them.
I've had the bug multiple times in less than an hour so it is definitely not the same as the stated timeout.
In any case, the Xposed module does nothing about the timeout. I still have to draw the pattern once every morning. But not during the day after that. Sometimes, it takes a bit longer to read the ring and the screen turns off before unlocking, but then it usually reads right away after turning on again, so it works for me. YMMV.
If by "disrupt normal battery features" you mean consuming more battery, that is in fact is one of the reasons I removed the option to enable NFC on when the screen is off. As it is now, the module can only enable NFC when the screen turns on, which is what the Smart Lock feature should be doing anyway.
As a temporary workaround, I modified the NFCLockScreenOff Xposed module to work on Marshmallow. I have it set up to enable NFC polling when the screen is on but locked.
http://forum.xda-developers.com/showpost.php?p=64611507&postcount=667
It also lets you silence NFC sounds.
I have been using this for over 3 weeks now and I haven't reproduced the bug in all this time. The downside is that it needs root and Xposed Framework.
That was it! The culprit seemed to be a rather poorly written app from our city's public transit company, that is supposed to use NFC to read transit card info, but actually never works. The keyboard issue appears to be gone with this app removed.
Thanks for the tip! I'd never have guessed it, the app wasn't active or even open as a background process.
At least we can get rid of the "New tag" popup easily without rooting.
I have root, so I went as far as to remove the Tags app completely (even cleaned cache and Dalvik partitions afterwards, so I'm positive it's gone) but my keyboards still hide whenever a tag is read.
If you're on 5.0.1 or higher, you can use the native Smart Lock (turn it on in Settings -> Security -> Advanced -> Trust Agents, then it will appear in Security -> Smart Lock) instead of the NFC Ring Unlock app.
The only place I've seen the 4-hour time limit documented is this help article from Google: https://support.google.com/android/answer/6093922?p=personal_unlocking&rd=1
My Nexus 5 always refuses to unlock with NFC Smart Lock every morning (after 5-8 hours idle). After unlocking it once by hand (by drawing the pattern), NFC unlocking works again.
The bug is a different issue - it happens at random, whether or not the device has been idle for > 4 hours, and the affected users need to toggle NFC, Smart Lock, or restart in order to have NFC unlock working again.
I checked the NTAG21x datasheet, these have no built-in encryption like the DESFire. But it is indeed possible to use the password feature to protect the NTAG216 from reading. Also, see http://stackoverflow.com/questions/32607005/how-to-manage-password-protection-on-ntag216-using-the-mifare-lite-sdk
That feature would prevent the tag from being cloned by any reader without the password.
On top of that, on the software side of things, you can use the UniqueID of a tag as a hash to encrypt the data on it, so that data can only be decrypted with the same ID.
@jasok2 Some NFC writers (I use the TagWriter app for Android) let you set a 4-character password on a tag to protect it from unauthorized writing.
I was wondering if they could be protected from reading as well. I've only skimmed through the N216 datasheets, but IIRC these have some encryption support built-in to do things like that.
I guess what I'm looking for is something like the Desfire EV1 public transport card we have here, AFAIK the data is cyphered and these cards cannot be copied.
The tags on the newer 2016 rings have password protection built in, right? Couldn't we use that to ensure the tag cannot be read (and therefore cannot be copied) by any reader who doesn't have that password?
You're right about "twice". According to the caliper, the Eclipse is 2.3mm thick, just as the datasheet says. But this Horizon is 1.85mm, and the 'comfort fit' curve makes it seem even thinner.
(By the way, the Eclipse datasheet says Horizon in the first page)
I just received the replacement Eclipse, and was surprised to see it is about twice as thick as the Horizon:
The Horizon was labeled as size 9 but was in fact closer to 9.5 (too large). That, as well as the black inlay coming unstuck, led me to order a replacement.
The replacement Eclipse seems to have the same inner diameter as the Horizon (so it is still too large - will confirm later with a caliper) but the outer diameter is even bigger due to the thickness.
Moreover, the black inlay on the replacement has a bubble, and both inlays have minor blemishes.