when you killed the apmd process, the phone will never sleep again, so you can use shell run as long as you wish
command:
start-stop-daemon -K -p -n apmd
I've found it impossible to be able to schedule any event longer than 2 minutes in shell script.
After a test determined that 'sleep 300' took nearly two hours to complete with the flip shut, I gave up on this tact and tried my hand with cron. I got busybox crond up and running with little issue, then setup the following crontab
* * * * * /usr/SYSqtapp/phone/vibrateprocess
Instantly my phone started buzzing every minute, on the minute. If I flipped it shut, I would get one final buzz then nothing at all. On opening the phone, cron would instantly wake up and start buzzing me every minute again.
Anyone know what's going on? Doesn't cron talk to the hardware clock? Clearly this can't be suspended or the Alarm app would also fail, no?
My poor timer/event scheduler is all dressed up with nowhere to go...
when you killed the apmd process, the phone will never sleep again, so you can use shell run as long as you wish
command:
start-stop-daemon -K -p -n apmd
Cool idea! I bet it'll be hell on battery life tho! lol This idea will be great for the countdown timer, but I wonder if the loss of battery life to enable the cron scheduler would be worth it.
I'm still curious as to how the alarm app is able to work through apmd...