Lock Device

Submitted by HtheB on Tue, 2014/06/17 - 19:31

Rating:

Your rating: None Average: 5 (4 votes)

Do you also hate to enter a password each time you lock the screen?
Tired of going through all those menus, just to change the time to lock your device immediately?

No need to wait anymore!

With this simple tool, you can now add a "Lock Device" button to the Pulley menu in your Lockscreen!

FAQ:

I've installed it, but I still don't have this damn option!?

After you've installed this, go to the "Settings > System > Shortcuts" and add "Lock Device" to the shortcut list.
That's all!

I don't have the "Shortcuts" menu in my Settings?

Be sure that you're at least running on firmware 1.0.7.16 or above!

What should I do with the beautiful icon on my homescreen?

Well, it's up to you, you may hide the (beautiful) icon that is on your homescreen into a folder.

I don't remember my password anymore.

Not my problem. And don't bother to ask your parents for your password. I'm pretty sure they wouldn't know your password...

Have fun!

Thanks to the guys at #sailfishos on Freenode.net (Jonni, spiiroin and kimmoli)

Screenshots:

Keywords:

Application versions:

Attachment	Size	Date
lockdevice-1.0-1.noarch.rpm	10.43 KB	17/06/2014 - 19:31

Changelog:

Initial Release 1.0

Comments

objectifnul

Sun, 2022/04/17 - 14:15

Permalink

Now broken again (Sfos 4.4)

asleep

Thu, 2018/03/01 - 09:46

Permalink

unfortunately no more working :-(

objectifnul

Sun, 2018/02/25 - 16:23

Permalink

The code below is now deprecated:

sh -c "dbus-send --system --type=method_call --dest=org.nemomobile.lipstick /devicelock org.nemomobile.lipstick.devicelock.setState int32:1 & dbus-send --system --dest=com.nokia.mce --print-reply --type="method_call" /com/nokia/mce/request com.nokia.mce.request.req_display_state_off"

Does anyone know why?

ade

Sat, 2018/03/03 - 00:49

Permalink

The syntax has slightly changed:



sh -c "dbus-send --system --type=method_call --dest=org.nemomobile.devicelock /devicelock org.nemomobile.lipstick.devicelock.setState int32:1 & dbus-send --system --dest=com.nokia.mce --print-reply --type="method_call" /com/nokia/mce/request com.nokia.mce.request.req_display_state_off"

alina

Fri, 2015/07/10 - 02:55

Permalink

Exactly what I want. Thanks!

objectifnul

Tue, 2015/03/10 - 15:37

Permalink

Isn't RAM usage a bit high (114 Mbytes) for a small utility?

HtheB

Tue, 2015/03/10 - 18:12

Permalink

Lock Device is not an 'app', it just executes a command to trigger the Device Lock.
So this 'app' shouldn't even be listed on the ram :)

In your case: It's probably the device lock itself that takes up that RAM.

alina

Fri, 2015/07/10 - 14:57

Permalink

After some times of using the app, the process “lipstick” is renamed to “Lock Device”. Seems strange!

Edit: This occurs in Memory app. Other apps such as Crest and Lighthouse show the lipstick process correctly. So it seems to be a Memory app bug in getting process names.

Edit2: Ok, I guess I found the problem. Memory app uses .desktop files to get the process names, and here we have the name "Lock Device" for the command "org.nemomobile.lipstick". So while you have the app, the lipstick process will be called as "Lock Device".

To avoid this, you can please use a bash file to execute the command and in .desktop file run that script file instead of the command directly.