Edify sleep/pause, is there a function? - HTC EVO 3D

Whats up, everyone?
Does anyone know if there is a function for edify scripting that will cause it to sleep/pause. I have some text in my script that I would like to display for a few extra seconds.
Thanks for any help

---

i dont know it myself, but check out the synergy format all zip. it has a 10 second delay, so it'll be in there.

---

Sweet!
Thanks dude

---

dkdude36 said:
i dont know it myself, but check out the synergy format all zip. it has a 10 second delay, so it'll be in there.
Click to expand...
Click to collapse
Looking at the script it seems like the pause is caused by the deletion process it is running, not by an actual pause function.
Thanks though...

---

would
Code:
run_program("sbin/sleep", "6")
work like
Code:
sleep(6);
does in C when working on a *NIX system?

---

Bamba1260 said:
would
Code:
run_program("sbin/sleep", "6")
work like
Code:
sleep(6);
does in C when working on a *NIX system?
Click to expand...
Click to collapse
Nope, sure doesn't lol.

---

Bamba1260 said:
Looking at the script it seems like the pause is caused by the deletion process it is running, not by an actual pause function.
Thanks though...
Click to expand...
Click to collapse
my bad. that's the only place i've seen anything pause before so yeah i have no idea.

---

dkdude36 said:
my bad. that's the only place i've seen anything pause before so yeah i have no idea.
Click to expand...
Click to collapse
It's all good, thanks for the tip.
Anyone else want to chime in?? You are more then welcome too

---

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

Bamba1260 said:
Anyone else want to chime in?? You are more then welcome too
Click to expand...
Click to collapse
Bamba1260 said:
would
Code:
run_program("sbin/sleep", "6")
work like
Code:
sleep(6);
does in C when working on a *NIX system?
Click to expand...
Click to collapse
short answers: no, updater-script will not use C functions or codes. although the custom recovery is mostly coded and compiled in C/C++, the actual update-script binary reads and executes "edify" commands from the updater-script.
although, the first command you quote, could work, run_program("sbin/sleep","6"). i'll give the technical explanation below since both of the ppl posting in this thread seem to be fairly knowledgable!
long more technical answers with some background:
sleep is an applet/binary compiled as part of busybox. all *good* custom recoveries include a busybox binary. most of them compile in the majority of busybox functions so their included busybox has all the standard features.
now, with all that said, recoveries generally install their busybox binary to the /sbin directory and generally also install all the applets whether actual separate binaries or symlinks back to the main busyboxy in the /sbin directory too.
you can include in your updater-script, the simple call to the /sbin/sleep binary, assuming the custom recovery has the sleep applet compiled into the busybox binary they distribute packaged with their custom recovery.
worse case, there is no sleep binary compiled into their busybox included in the custom recovery.
quick work around would be to include your own sleep binary in your .zip file. simply extract the sleep binary to /tmp and run_program from /tmp/sleep. similar to how we extract flash_image to /tmp and run_program /tmp/flash_image .. or any other binary really.
for starters, if the sleep binary is compiled as part of busybox and included as a symlink or separate applet, this command should work: run_program("/sbin/sleep","6") (notice i added a / infront of /sbin which wasnt in the original post quoted above).
if /sbin/sleep is not present, try /sbin/busybox sleep 6 and see if sleep is present in the busybox binary.
if that doesn't work, the sleep binary is not present and will probably have to be supplied in the update .zip file.
if you're interested in alternatives to accomplish the same goal, provide a delay, might put some type of load or heavy processing of random junk in order to delay the system before continuing to the next argument. this approach, is definitely less than ideal.
hope that helps!

---

joeykrim said:
short answers: no, updater-script will not use C functions or codes. although the custom recovery is mostly coded and compiled in C/C++, the actual update-script binary reads and executes "edify" commands from the updater-script.
although, the first command you quote, could work, run_program("sbin/sleep","6"). i'll give the technical explanation below since both of the ppl posting in this thread seem to be fairly knowledgable!
long more technical answers with some background:
sleep is an applet/binary compiled as part of busybox. all *good* custom recoveries include a busybox binary. most of them compile in the majority of busybox functions so their included busybox has all the standard features.
now, with all that said, recoveries generally install their busybox binary to the /sbin directory and generally also install all the applets whether actual separate binaries or symlinks back to the main busyboxy in the /sbin directory too.
you can include in your updater-script, the simple call to the /sbin/sleep binary, assuming the custom recovery has the sleep applet compiled into the busybox binary they distribute packaged with their custom recovery.
worse case, there is no sleep binary compiled into their busybox included in the custom recovery.
quick work around would be to include your own sleep binary in your .zip file. simply extract the sleep binary to /tmp and run_program from /tmp/sleep. similar to how we extract flash_image to /tmp and run_program /tmp/flash_image .. or any other binary really.
for starters, if the sleep binary is compiled as part of busybox and included as a symlink or separate applet, this command should work: run_program("/sbin/sleep","6") (notice i added a / infront of /sbin which wasnt in the original post quoted above).
if /sbin/sleep is not present, try /sbin/busybox sleep 6 and see if sleep is present in the busybox binary.
if that doesn't work, the sleep binary is not present and will probably have to be supplied in the update .zip file.
if you're interested in alternatives to accomplish the same goal, provide a delay, might put some type of load or heavy processing of random junk in order to delay the system before continuing to the next argument. this approach, is definitely less than ideal.
hope that helps!
Click to expand...
Click to collapse
Thanks Joey, I appreciate the insight!
I know C code won't work in an updater-script lol, I was just using it as a familiar reference point.
As for the the sleep binary, I had no Idea about it! Makes complete sense now though. I just fixed my "test" script with the proper placements of /, and unfortunately still no luck. I also tried seeing if busybox had a sleep binary, and no luck either.
So my question now is, where would I go about finding a sleep binary for android phones?
EDIT:
Nevermind I found one!

---

Alright well I found a sleep binary, but I still can't get it to work..
Is this correct? Assuming the sleep binary is not in any folders other then the zip.
Code:
package_extract_file("sleep", "/tmp/sleep");
run_program("/tmp/sleep", "6");

---

Bamba1260 said:
Alright well I found a sleep binary, but I still can't get it to work..
Is this correct? Assuming the sleep binary is not in any folders other then the zip.
Code:
package_extract_file("sleep", "/tmp/sleep");
run_program("/tmp/sleep", "6");
Click to expand...
Click to collapse
yea, that is a good start.
1) the above command assumes the sleep binary is in the root of your .zip file.
2) i'd recommend one tweak, set the binary chmod 755 to make sure you have permission to execute before sending the execute command.
set_perm(0, 0, 0755, "/tmp/sleep");
also, you can manually test before you setup the updater-script code. boot into recovery, adb push sleep to /tmp. chmod 755 /tmp/sleep. try sleep 6 and the command prompt should hang for 6 seconds and then return. we're also assuming the sleep binary takes input in seconds, which seems most logical.
assuming all works according to plan the final updater-script should be something similar:
package_extract_file("sleep", "/tmp/sleep");
set_perm(0, 0, 0755, "/tmp/sleep");
run_program("/tmp/sleep", "6");
if that works, feel free to post up your sleep binary and help anybody else who might come across this thread searching.
hope that helps!
for reference, i used the following to links to make sure my updater-script syntax on perfectly correct. no typos allowed in programming!
http://forum.xda-developers.com/showpost.php?p=11027417&postcount=1
http://www.synfulgeek.com/main/inde...d-off-of-kernel-source-code&catid=57:articles

---

joeykrim said:
yea, that is a good start.
1) the above command assumes the sleep binary is in the root of your .zip file.
2) i'd recommend one tweak, set the binary chmod 755 to make sure you have permission to execute before sending the execute command.
set_perm(0, 0, 0755, "/tmp/sleep");
also, you can manually test before you setup the updater-script code. boot into recovery, adb push sleep to /tmp. chmod 755 /tmp/sleep. try sleep 6 and the command prompt should hang for 6 seconds and then return. we're also assuming the sleep binary takes input in seconds, which seems most logical.
assuming all works according to plan the final updater-script should be something similar:
package_extract_file("sleep", "/tmp/sleep");
set_perm(0, 0, 0755, "/tmp/sleep");
run_program("/tmp/sleep", "6");
if that works, feel free to post up your sleep binary and help anybody else who might come across this thread searching.
hope that helps!
for reference, i used the following to links to make sure my updater-script syntax on perfectly correct. no typos allowed in programming!
http://forum.xda-developers.com/showpost.php?p=11027417&postcount=1
http://www.synfulgeek.com/main/inde...d-off-of-kernel-source-code&catid=57:articles
Click to expand...
Click to collapse
Haha yeah I know all about strict syntax. I taught myself C, C++, python and now Java lol. I'll work on it more tonight and let you know how it goes, sadly I'm in class now lol.
Thanks for the links, I'll definitely check them out.

---

joeykrim said:
yea, that is a good start.
1) the above command assumes the sleep binary is in the root of your .zip file.
2) i'd recommend one tweak, set the binary chmod 755 to make sure you have permission to execute before sending the execute command.
set_perm(0, 0, 0755, "/tmp/sleep");
also, you can manually test before you setup the updater-script code. boot into recovery, adb push sleep to /tmp. chmod 755 /tmp/sleep. try sleep 6 and the command prompt should hang for 6 seconds and then return. we're also assuming the sleep binary takes input in seconds, which seems most logical.
assuming all works according to plan the final updater-script should be something similar:
package_extract_file("sleep", "/tmp/sleep");
set_perm(0, 0, 0755, "/tmp/sleep");
run_program("/tmp/sleep", "6");
if that works, feel free to post up your sleep binary and help anybody else who might come across this thread searching.
hope that helps!
for reference, i used the following to links to make sure my updater-script syntax on perfectly correct. no typos allowed in programming!
http://forum.xda-developers.com/showpost.php?p=11027417&postcount=1
http://www.synfulgeek.com/main/inde...d-off-of-kernel-source-code&catid=57:articles
Click to expand...
Click to collapse
Well, I can get it to work when I shell in, but not from a flashable. I am going to keep trying different ways.

---

Bamba1260 said:
Well, I can get it to work when I shell in, but not from a flashable. I am going to keep trying different ways.
Click to expand...
Click to collapse
lol i know this is a really old thread, but do you know if there is a way to do this?

---

Punchieo said:
lol i know this is a really old thread, but do you know if there is a way to do this?
Click to expand...
Click to collapse
run_program("/sbin/sleep", "10");
sleep is part of recovery binaries,
what they didn't set proper permissions on the sleep binary they copy to tmp
set_perm(0, 0, 0777, "/tmp/sleep");