New Knock On Password Feature Keeps defaulting back to swipe

[faithalone]

Like many other I got the ATT update a few days ago with the new Knock On unlock pattern feature. I really like it and began using it right away. The problem that I am having is that it seems to work for maybe half a day or so and then all of a sudden it is not working and it takes just the old regular double tap to wake the phone and then a swimpe (my former default method) to unlock the phone.

It is like the phone is changing the option back to my default. Anyone else experiencing this?

 

[Scotty719]

Just picked up an ATT G2 with 4.4.2 out of the box and it does the same thing. I wish it didn't. I really do like the Knock Code feature and hopefully someone or LG can find a fix.

 

[faithalone]

Glad to know not just me, wonder why no other responses though? Odd..

 

[Scotty719]

I tried some different settings and it seems to work if I have "Power Button instantly locks" checked and hasn't defaulted to swipe yet. If I uncheck it, it goes back to swipe after a few unlocks.

Sent from my LG-D800 using AC Forums mobile app

 

[faithalone]

I actually already had that option checked, I unchecked it and will give it a go and see if I get any different results and will report back.

 

[ol chap]

So that's an lg bug? It's never happened to me until I started using exposed framework so I assumed it was that. Glad to hear I didn't screw up my phone already

Posted via Android Central App

 

[faithalone]

i have exposed framework also... i am also using a pebble watch with an app that auto locks my phone if the bluetooth connection is lost, perhaps that is a possible culprit?

 

[ol chap]

Possibly, I've been using knock unlock since I've gotten the phone and its never switched to swipe unlock until I installed a couple xposed framework modules. Wonder if it will affect other lock methods or only knock code.

Posted via Android Central App

Update: had a pin code running phone went to sleep and when I turned it on the swipe lock was there, it's either a LG bug or xposed framework