Problem when "Secure lock" is unchecked

[bedlia]

https://www.youtube.com/watch?v=g1vVxscfo6Y&feature=youtu.be

This video showcase the problem. Screenshots 1 and 3 too. Basically, if you uncheck secure lock, go back to homescreen, double tap to lock, then 'change you mind' and press the lock (or home) button to go back to homescreen and then do again a double tap to lock, this set a custom screen timeout as ( ) [which is around 3 sec, as shown in the video]

[hundeva]

That's weird, what device do you have?

[bedlia]

I'm using a Galaxy J5 2016. Do this happens also on your device?

[hundeva]

Nope, none of my test devices reproduces this, I'll have to work something out for this.

[hundeva]

The next version is going to contain a few changes regarding this. The launcher will try to restore your timeout more aggressively. As the worst case scenario, when for whatever reason restoring your selected timeout fails after locking, the launcher should default to 1 minute timeout, and not to an unrecognised thing, such as "()" is. Hopefully it is going to work out.

[bedlia]

Ops. I wrote something 5 days ago but only now I see I didn't press "comment", my bad. Basically I tried on other 2 Samsung phones running Android 6.0.1 and the problem didn't appear. Also on a Sony with 6.0.1 and the launcher asked (see screenshot) which never happened before, but the problem wasn't present here either.

So, the problem should be only with Samsung phones with Android 7.1.

And thanks for trying to fix this, I will look into it when the new version comes out!

[bedlia]

1.0.9 update does not fix "()" timeout for Samsung devices running Android 7 and up (still have to test on more devices, but I'm quite sure it' 7.1 and later versions). I'm sorry to bring this news, I really appreciate you work. That being said, for me it's not a big issue, I always use secure lock.