Hi! I think I found a bug, or something similar.
I have 2 desktops, and I am using the second of them as a lock screen. The first desktop has 3 screens, and the second desktop has a single screen.
I have 3 gestures defined. Swipe down to open the notifications tab, swipe up to go to “All apps” and swipe sideways with 2 fingers to switch between desktops.
On the second desktop I have an unlocker (a visible icon).
Most of the setup works perfectly, but I found a bug, or at least something very odd.
Most of the times, the swipe up gesture gets me to the lock screen. I touch the unlock icon again, and I am back on the main desktop. That is how i know that I was in the lock screen and not the second desktop. The unlock icon on the second desktop does nothing, and a pop-up says that the screen was not locked.
So, I tried playing with the gestures settings, like not setting global gestures and only use desktop gestures, or the other way, or even use both. But I always get the same non-desired behaviour.
I even tried to leave gestures, and set the “Back” button to “All apps”, but I get the same bad behaviour: after touching the back button on the main desktop I get to the lock screen, and not to “All apps”.
My phone is a Samsung Galaxy S3, from Rogers Canada, rooted.
]]>
D5 Creation
< ![CDATA[
That’s quite strange, it seems like the device is locking itself (or rather: Lightning “thinks” that the device has been locked). If you disable the lock screen from the general settings, but keep the second desktop as is, without modification, do you still reach the lock screen when using the swipe up gesture ?
]]>
< ![CDATA[
Ok! I will test it during the day. Just to be more precise. In Android settings, I have chosen no lock screen at all. The lock screen was only from Lightning. Now I have disabled it, and the power and home button turn on the phone in the first desktop directly.
I will later post how do All apps shortcuts and gestures work.
]]>
< ![CDATA[
Disabling the lock screen completely fixes the issue. Of course, I can’t leave my phone without lock screen, but I hope it serves you to find out what is going on.
]]>
< ![CDATA[
Thanks for the test! This definitely mean that somehow the launcher is locking itself. That means I need to double check the condition for locking and identify which one is wrong.
By the way, which Android version is your S3 ?
]]>
< ![CDATA[
4.3
]]>
< ![CDATA[
Hi! I do not want to rush you or anything. I just wanted to know if you intend to fix this in the future or it is a too minor issue.
Thanks a lot for all your work.
]]>