faerbit / android-crond Goto Github PK

Hi,

thanks for this app, the first android crond that works for me.

However it reports a lot of "Invalid cron expression" if crontab contains:

• commented lines, starting with #
• empty lines
• lines with fields separated by Tabs instead of spaces

Also, it would be nice to have crontab and log in (larger) separate windows and buttons and checkboxes in a settings page or menu.

I updated the app and added some new strings. So the spanish and japanese translations need updating too.
Care to take another shot at it @Eskuero and @naofum ?

Moto X XT1053 (Root)
Andorid Version: 5.1
System version: 222.201.1.ghost_row.Retail.en.US
Build Number: LPAS23.12-15.5-1

url:https://f-droid.org/repo/it.faerb.crond_16.apk

error info: Unfortunately, crond has stopped.

@Faerbit Tried this from F-droid, but, when run, it says it needs root (& I'm not gonna just for this app).

• Please make sure app manifest requests root
• Please update F-droid description w/ that, too.

Thanks!

Faerbit,

Thanks for this app - it is just what I needed because I didn't want to install BusyBox.

My simple script works from the command line but with this crontab:

10 * * * * root /data/media/0/bin/db.sh

I get the above error message - how to debug?

Thanks,
Phil.

Could you please explain in the README why android-crond requires root? I would like to schedule a cron job of a command which can be run as a non-root user. Regular, non-Android Linux lets non-root users create cron jobs so why must I root my phone to use crond?

Hello all !
Thanks for this very simple sheduler.

I'm facing an app FC whenever I plan a shedule on Sundays (either with a 0, or a 7 or even with 'sun'). Others days are fine.

I tried to read the code to find some relevant code, but my Java Fu is not very effective, I think :p.

Using the latest crond from f-droid, with the latest lineageOS on athene (Moto G4 Plus).

Will you please check your code to give it the proper treatment, it would be very kind.

Thanks for reading. -- A satisfied user.

On Marshmallow (23) and up, Doze mode can kick in and prevent timers from firing. I normally have my phone on a charger overnight, which apparently stops Doze mode from engaging. However, last night I did not, and as a result, crond did not start my job at the correct time.

There is a whitelist that end users can use that can help (Settings -> Battery -> Battery Optimization), but the best way to avoid the issue is to call a different API method:

    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
        alarmManager.setExactAndAllowWhileIdle(AlarmManager.RTC_WAKEUP, next.getMillis(), alarmIntent);
    } else {
        alarmManager.setExact(AlarmManager.RTC_WAKEUP, next.getMillis(), alarmIntent);
    }

Please consider the cron log below :
`2017-05-31 03:53:24.4060 Scheduled line 0 at 2017-05-31 06:45:00.0000

2017-05-31 07:09:59.6570 Execute line 0
2017-05-31 07:10:38.0580 Executed line 0`
The script (to turn off airplane) is not executes at the time it was meant to (6:45 am). Rather, it was executed at 7:09, when I explicitely opened my phone.

Is there some kind of weirdness with the way latest android versions try to minimize battery usage with their "doze" feature ? I tried to turn off "Battery optimization" for crond, but it did not change a thing.