Strange bug I have regarding LL.unlock() and touch event.

I have a lock screen on my tablet with a full screen item as background

That item have a script in the touch event

That script unlocks when you swipe in any direction more than a specific length (it draws also a circle, a bit ugly but functional)

The problem is that it works fine at the beginning (after closing the launcher with force kill/update…)

But then after some unlocks it doesn’t work (defined later).

I tested that it happened sometimes after launching an app from the status bar, or even from the lock screen (I have some app shortcuts)

I finally found steps to reproduce this problem.

The script have simply a LL.unlock() in the MotionEvent.Action_Up case (and some checks). I also tried launching an item with the ‘unlock’ shortcut, but it’s the same. I added a toast to know if the command is executed.

After force closing the launcher and reopening again, it works, it unlocks and says ‘unlocked’ (the toast)

But, if I press the home button while in the lock screen, after some flashing of the default lock screen, it no longer works. It says the ‘unlocking’ toast, but it doesn’t unlock.

Important: I have the tablet lock screen set to swipe. While writing this post I tried setting it to none, and the bug is fixed. However now the recent app button is shown in the LL lock screen.

I posted this because it is a bug, and maybe it helps to find something more (and because I spend time writing the report, and didn’t want to threw it 😛 )

Edit: it happens also with none as default lock screen, but the ‘press home button’ not always force the bug 🙁

Samsung galaxy tab 2, android 4.4.2. Can provide backup/script if necessary.

]]>