it seems that the time-out for locking the device automatically, not happened correctly like it is defined in the device-lock options.
On my device, if I set-up this time to 5 minutes, i observed that my device is locked between 3min and 3"30.
Time-out set-up to 10min, then the device is locked between 6min and 7min.
Time-out set-up to 30min, then the device is locked before 20min.
It locks itself too early.
Actually I don't know if it happened the same for the 60min time-outs.
That's too long for me, i don't know how i could observe the event exactly when it engage itself.
The best would be to observe a kind of dedicated event message in a terminal, through ssh (dev-mode).
Furthermore i noticed that, the lockscreen activate by itself automatically during the use of some applications.
For example with the native game "machines vs machine", after i finish to play with it, i come directly to the lockscreen. I'll try to notice with which other app i have the same issue.
Last weekend happened some further weird things.
The device locked itself during a skype (android) call.
One Time it locked itself directly after an unlock action. And as poddl remarked, i rebooted my device too. After it, it didn't spare itself before 4min for a 5min lock-time.
Seems for me that there is at last 2 kinds of bug for the lock-screen:
- One with the time-out drift (firstly noticed and reported here).
- The other one would be the automatic lock in background of an app (afterwards noticed, and reported here too).
Myself i have a JP1 with sfos 18.104.22.168.
Offset seems to be observed on a jolla-C to.
Has anybody the same issues? which device do you have and with which OS Version?
And what are the apps that you commonly use , which may take a lot's of OS resources (like a game or communication, video, compression tool).
Have good continuation.