Change Screensaver Timeout (how long before sleeps)

[xueyou2]

Originally Posted by dave2008

Maybe you can try run following command with launchpad before you go to sleep.

lipc-wait-event  -s 0 com.lab126.powerd goingToScreenSaver && killall mplayer

You are the first people who help me from foreign country ! I feel very well.
If there is anyting you need help in china ,just say. I will do my best!
Thank you !
感激不尽！

[thomass]

Originally Posted by xueyou2

You are the first people who help me from foreign country ! I feel very well.

You should walk around in this forum a little much.

[xueyou2]

Originally Posted by dave2008

Maybe you can try run following command with launchpad before you go to sleep.

lipc-wait-event  -s 0 com.lab126.powerd goingToScreenSaver && killall mplayer

Except my poor english, my linux is bad too.
I have install this Change Screensaver Timeout (how long before sleeps)
i think we can kill the Mplayer when the screensaver starts!so i can use this to controll
the Mplayer!
And i do not know how to do this!so please give me detai step!
Thank you!

[thomass]

I'm not sure if this works but you can try :

append this line to the [Actions] part of one of ini files in the launchpad folder

S M = !lipc-wait-event  -s 0 com.lab126.powerd goingToScreenSaver && killall mplayer

then refresh launchpad with [shift shift space]
and execute this via [ shift S M ] whenever you need it to be active.

[xueyou2]

Originally Posted by thomass

I'm not sure if this works but you can try :

append this line to the [Actions] part of one of ini files in the launchpad folder

S M = !lipc-wait-event  -s 0 com.lab126.powerd goingToScreenSaver && killall mplayer

then refresh launchpad with [shift shift space]
and execute this via [ shift S M ] whenever you need it to be active.

I append this to launchpad.int .
I just try it ,and it works!
In my country it very late at night.and i can use it right now!
Thank you! You are another icefrog!

[xueyou2]

Originally Posted by xueyou2

I append this to launchpad.int .
I just try it ,and it works!
In my country it very late at night.and i can use it right now!
Thank you! You are another icefrog!

I find Change Screensaver Timeout can do this too!When the screensaver starts
the mplayer will be killed in about 2minutes.
.

[inameiname]

Originally Posted by xueyou2

I find Change Screensaver Timeout can do this too!When the screensaver starts
the mplayer will be killed in about 2minutes.
.

Thanks for pointing this out to all of us. I did not know it will close Mplayer (or presumably any open and running program) not long after this screensaver timeout runs.

[xueyou2]

Originally Posted by inameiname

Thanks for pointing this out to all of us. I did not know it will close Mplayer (or presumably any open and running program) not long after this screensaver timeout runs.

The trouble is that if you close the screensaver and want to start the mplayer again,you have to first stop the mplayer for three times and then you can start it with launchpad.

[thomass]

Originally Posted by xueyou2

...you have to first stop the mplayer for three times...

for a quick and temprorary soln you can try to add them to this command also

what I mean is this:

S M = !lipc-wait-event  -s 0 com.lab126.powerd goingToScreenSaver && killall mplayer && killall mplayer && killall mplayer && killall mplayer

if you are using a different command to stop mplayer then replace each of the last three "&& killall mplayer" with it

may work

[inameiname]

Originally Posted by xueyou2

The trouble is that if you close the screensaver and want to start the mplayer again,you have to first stop the mplayer for three times and then you can start it with launchpad.

I see. Weird. But glad you pointed that out.

Now, does Thomas's Launchpad command negate having to stop mplayer three more times, or do you also have to do that as well, just as if you just the screensaver alone run and kill mplayer anyway, as you mentioned it does automatically after a few minutes) If so, I guess Thomas's latest tweak of his Launchpad command works. I was just unclear as to if you had to do that whether you set his Launchpad command or not.

[xueyou2]

Originally Posted by inameiname

I see. Weird. But glad you pointed that out.

Now, does Thomas's Launchpad command negate having to stop mplayer three more times, or do you also have to do that as well, just as if you just the screensaver alone run and kill mplayer anyway, as you mentioned it does automatically after a few minutes) If so, I guess Thomas's latest tweak of his Launchpad command works. I was just unclear as to if you had to do that whether you set his Launchpad command or not.

Thomas's Launchpad command works very well.It is a smart idea.Sorry to replay it late!
Now i can listen to music whether falling asleep.：P
Thank you very much!

[inameiname]

Originally Posted by xueyou2

Thomas's Launchpad command works very well.It is a smart idea.Sorry to replay it late!
Now i can listen to music whether falling asleep.：P
Thank you very much!

Thank you. I am glad it works great for you.

[K3w]

Coudn't find "/etc/init.d/powerd" on KT. "/usr/bin/powerd" doesn't work with parameter "restart". Have someone an idea, to let powerd-deamon reread the "t1_timeout"?

[phui]

how to do it on kindle 4 non-touch?

[NiLuJe]

Probably via something like

kdb set system/daemon/powerd/t1_timeout 600

but it requires a rw rootfs, may not be safe, may break updates, may need a restart to get taken into account, and I didn't test this the slightest bit.

(That's part of the reason I pulled the packages the code that's used in the first post came from).

[600 seconds seems to be the default value on K4/K5]