[GH-ISSUE #921] scheduled backup and Tasker 3rd party both not working #721

New issue

Closed

opened 2026-02-26 01:31:27 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 01:31:27 +03:00

Owner

Originally created by @JoshFlory on GitHub (Sep 17, 2018).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/921

Before you report your issue, please consider perusing the https://github.com/jberkel/sms-backup-plus#faq and searching the issues page to see if it has already been reported.

Expected Behaviour

Automated backups should run on the schedule selected, and after X time has passed when receiving a text. 3rd party app calls like Tasker should execute SMS Backup when the plugin is called. *Manual backups work without issue

Actual behaviour

When the schedule is enabled backups should be performed after the elapsed time (30 min) and after the elapsed time of a text message being received. Also, when Tasker is used to call the 3rd party plugin to run backup, it should execute. If manual backup is performed it works without issue.

In the log this error is often seen when calling from Tasker:
Backup requested (3rd party)
08-31 11:54 Backup skipped, no connectivity

Steps to reproduce the behaviour

Does not work on Samsung S7 or S9 Note. Set and enable scheduled backups, send texts to the phone from another device. Wait for the period of time to elapse that should have triggered backups (two hours to test the 30 min schedule for example).

Please specify the following:

Android version 8.1.0
Phone model / brand Samsung Note 9
SMS Backup+ version installed 1.5.11
*Textra
sms_backup_plus.log

Originally created by @JoshFlory on GitHub (Sep 17, 2018). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/921 Before you report your issue, please consider perusing the [https://github.com/jberkel/sms-backup-plus#faq](FAQ) and searching the issues page to see if it has already been reported. ### Expected Behaviour Automated backups should run on the schedule selected, and after X time has passed when receiving a text. 3rd party app calls like Tasker should execute SMS Backup when the plugin is called. *Manual backups work without issue ### Actual behaviour When the schedule is enabled backups should be performed after the elapsed time (30 min) and after the elapsed time of a text message being received. Also, when Tasker is used to call the 3rd party plugin to run backup, it should execute. If manual backup is performed it works without issue. In the log this error is often seen when calling from Tasker: Backup requested (3rd party) 08-31 11:54 Backup skipped, no connectivity ### Steps to reproduce the behaviour Does not work on Samsung S7 or S9 Note. Set and enable scheduled backups, send texts to the phone from another device. Wait for the period of time to elapse that should have triggered backups (two hours to test the 30 min schedule for example). ### Please specify the following: * Android version 8.1.0 * Phone model / brand Samsung Note 9 * SMS Backup+ version installed 1.5.11 *Textra [sms_backup_plus.log](https://github.com/jberkel/sms-backup-plus/files/2389707/sms_backup_plus.log)

kerem

2026-02-26 01:31:27 +03:00

closed this issue
added the
schedule

duplicate
labels

kerem commented

2026-02-26 01:31:27 +03:00

Author

Owner

@mrandreastoth commented on GitHub (Oct 6, 2018):

I hope this issue is top priority since not only does it completely void the app, but it also makes it the top battery-drainer.

@mrandreastoth commented on GitHub (Oct 6, 2018): I hope this issue is top priority since not only does it completely void the app, but it also makes it the top battery-drainer.

kerem commented

2026-02-26 01:31:27 +03:00

Author

Owner

@andreaallred76 commented on GitHub (Nov 2, 2018):

Same issues. Are you looking to fix this or should we be looking for something else to use? I’ve used this for years so I hope there a plan to find a solution.

@andreaallred76 commented on GitHub (Nov 2, 2018): Same issues. Are you looking to fix this or should we be looking for something else to use? I’ve used this for years so I hope there a plan to find a solution.

kerem commented

2026-02-26 01:31:27 +03:00

Author

Owner

@TjrGithub commented on GitHub (Apr 2, 2019):

Same issue, except it doesn't drain battery. The scheduler has never worked for the last 3 years.

LineageOS 15.1, latest FDroid smsbackup+.

@TjrGithub commented on GitHub (Apr 2, 2019): Same issue, except it doesn't drain battery. The scheduler has never worked for the last 3 years. LineageOS 15.1, latest FDroid smsbackup+.

kerem commented

2026-02-26 01:31:28 +03:00

Author

Owner

@kurahaupo commented on GitHub (Jul 8, 2021):

Thanks everyone for the feedback.

Using the new Oreo JobScheduler API is on the roadmap.

I'm marking this as a duplicate of #758 just so we can track one issue and keep all the feedback in one place.

@kurahaupo commented on GitHub (Jul 8, 2021): Thanks everyone for the feedback. Using the new Oreo JobScheduler API is on the roadmap. I'm marking this as a duplicate of #758 just so we can track one issue and keep all the feedback in one place.