Android Lollipop Trusted Device + NFC Ring = perfect



  • 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.



  • I recently bought a nfc ring because of lollipops native support for nfc in the smart lock function.
    I stumbled across this thread and read the bug post on google. According to the link posted in the bug file, it seems to be a wanted feature to switch off the lock functionality. Take a look at this: http://forums.androidcentral.com/android-5-0-lollipop/532617-smart-lock-phone-locked-after-4-hours-inactivity.html. Seems to be as intended to deactivate this feature after 4 hours.
    I'll see if the can be 'workarounded' with the xposed module, too. Nephiel only mentioned the marshmellow behaviour.
    Would it differ if one uses the nfc ring app? Is the nfc ring app less secure than the native android smart unlock feature?
    Thanx in advance.



  • 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.



  • @Nephiel said:

    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.

    Yeah, and this annoyes me. I want to use a hard password i only have to use in case of lost nfcs. This password would not be memorizable then. But if i have to input my pw every morning i have to choose a very soft one. Thats not what i wanted. I - of course - dont blame you or jonny for this, only google.



  • So interestingly, since my replacement ring this has stopped happening to me, its currently worked 100% of the time for the last few days.

    I don't see how that could be but there it is. Maybe it is just because I removed all the old trusted devices and added new ones since the last phone update or maybe it the ring.

    Maybe some of you guys could try removing all of your trusted devices and adding them again, see if that helps.



  • Removed all, then only added ks2016 ring same effect - works well for a short period then fails to play nicely with other there after.



  • @jasok2 said:

    So interestingly, since my replacement ring this has stopped happening to me, its currently worked 100% of the time for the last few days.

    I don't see how that could be but there it is. Maybe it is just because I removed all the old trusted devices and added new ones since the last phone update or maybe it the ring.

    Maybe some of you guys could try removing all of your trusted devices and adding them again, see if that helps.

    Since the last phone update...Whats your current android version?



  • @ave2000 said:

    Since the last phone update...Whats your current android version?

    6.0.1 patch level 1 January 2016

    EDIT - and just as I wrote that 1 Feburary 2016 patch came through, so I will keep you all posted on that too.



  • @jasok2 Its now happened just once with the 1 Feburary update.



  • This post is deleted!