Revision history [back]

Hello all,

it seems that the time for locking the device automatically, not happened correctly like it is defined in the device-lock options.
On my device, I set-up this time to 5 minutes, and i observed that after 3"30 my device is locked.
Not after 5 minutes. It locks itself too early. After 3 Minutes it is still free

Has anybody the same issue?

Cheers

Hello all,

it seems that the time for locking the device automatically, not happened correctly like it is defined in the device-lock options.
On my device, I set-up this time to 5 minutes, and i observed that after 3"30 my device is locked.
Not after 5 minutes. It locks itself too early. After 3 Minutes it is still free

Has anybody the same issue?

Cheers

Hello all,

it seems that the time for locking the device automatically, not happened correctly like it is defined in the device-lock options.
On my device, I set-up this time to 5 minutes, and i observed that after 3"30 my device is locked.
Not after 5 minutes. It locks itself too early. After 3 Minutes it is still free

Has anybody the same issue?

Cheers

Hello all,

it seems that the time for locking the device automatically, not happened correctly like it is defined in the device-lock options.
On my device, I set-up this time to 5 minutes, and i observed that after 3"30 my device is locked.
Not after 5 minutes. It locks itself too early. After 3 Minutes it is still free

Has anybody the same issue?

Cheers

Hello all,

it seems that the time time-out for locking the device automatically, not happened correctly like it is defined in the device-lock options.
On my device, I set-up this time to 5 minutes, and i observed that after 3"30 my device is locked.
Not after 5 minutes. It locks itself too early. After 3 Minutes it is still freefree. Actually I don't know if it happened the same for the other time-outs.

Has anybody the same issue?

Cheers

Hello all,

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, I set-up this time to 5 minutes, and i observed that after 3"30 my device is locked.
Not after 5 minutes. It locks itself too early. early.
After 3 Minutes it is still free. free.
Actually I don't know if it happened the same for the other time-outs.

Has anybody the same issue?

Cheers

Hello all,

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, and i observed that after 3"30 my device is locked.
Not Time-out set-up to 10min, then the device is locked after 5 minutes. 8min.
Time-out set-up to 30min, then the device is locked after 20min.
It locks itself too early.

Hello all,

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 after 3"30 my device is locked.locked between 3min and 3"30.
Time-out set-up to 10min, then the device is locked after 8min.
Time-out set-up to 30min, then the device is locked after 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).

Has anybody the same issue?

Cheers

Hello all,

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 after 8min. between 6min and 7min.
Time-out set-up to 30min, then the device is locked after 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).

Has anybody the same issue?

Cheers

Hello all,

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 after 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).

Has anybody the same issue?

Cheers

Hello all,

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.

Has anybody the same issue?issues?
Have good continuation.

Cheers

Hello all,

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.

Edit 21.11.2016:
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.

Myself i have a JP1 with sfos 2.0.4.14.
Has anybody the same issues?
issues? which device do you have and with which OS Version?

Have good continuation.

Cheers

Hello all,

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.

Edit 21.11.2016:
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.

Myself i have a JP1 with sfos 2.0.4.14.
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?

Have good continuation.

Cheers

Hello all,

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.

Edit 21.11.2016:
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.

Edit 23.11.2016:
Seems for me that there is at last 2 kinds of bug for the lock-screen:
- One with the time-out drift.
- The other one would be the automatic lock in background of an app.

Myself i have a JP1 with sfos 2.0.4.14.
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?

Have good continuation.

Cheers

Hello all,

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.

Edit 21.11.2016:
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.

Edit 23.11.2016:
Seems for me that there is at last 2 kinds of bug for the lock-screen:
- One with the time-out drift.
- The other one would be the automatic lock in background of an app.

Myself i have a JP1 with sfos 2.0.4.14.
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.

Cheers

Hello all,

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.

Edit 21.11.2016:
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.

Edit 23.11.2016:
Seems for me that there is at last 2 kinds of bug for the lock-screen:
- One with the time-out drift. drift (firstly noticed and reported here).
- The other one would be the automatic lock in background of an app.app (afterwards noticed, and reported here.

Myself i have a JP1 with sfos 2.0.4.14.
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.

Cheers

Hello all,

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.

Edit 21.11.2016:
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.

Edit 23.11.2016:
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 2.0.4.14.
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.

Cheers

Hello all,

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.

Edit 21.11.2016:
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.

Edit 23.11.2016:
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 2.0.4.14.
Offset seems to be observed on a jolla-C to.

Edit 21.04.2017:
New observation with sfos 2.1.0.11.
Shortly i noticed that after the update to the last release, some days after it happens that the device lock itself after any calls. If the lock option is set to lock automatically without delay.
I report it in an old thread that i found here.
But was surprised that the issue disappear after restarting the lipstick interface.
Is that the same bug, or is to be handled separately?

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.

Cheers