[GH-ISSUE #234] Instant backup #194

New issue

Closed

opened 2026-02-26 00:36:30 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 00:36:30 +03:00

Owner

Originally created by @gigozz on GitHub (Apr 20, 2012).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/234

Hi sir, is it possible to backup a sms in the same moment that it arrive or decrease wait time from one minute to few seconds?
Kind regards

Originally created by @gigozz on GitHub (Apr 20, 2012). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/234 Hi sir, is it possible to backup a sms in the same moment that it arrive or decrease wait time from one minute to few seconds? Kind regards

kerem closed this issue

2026-02-26 00:36:30 +03:00

kerem commented

2026-02-26 00:36:30 +03:00

Author

Owner

@CzBiX commented on GitHub (Apr 26, 2012):

if you heavy care about that, you can try to bulid it yourself before jberkel to update.
just change the value of "auto_backup_incoming_schedule_values" in /res/values/arrays.xml

@CzBiX commented on GitHub (Apr 26, 2012): if you heavy care about that, you can try to bulid it yourself before jberkel to update. just change the value of "auto_backup_incoming_schedule_values" in /res/values/arrays.xml

kerem commented

2026-02-26 00:36:30 +03:00

Author

Owner

@rsyring commented on GitHub (Dec 24, 2013):

I'm wondering if consideration could be given to revisit this issue. I'm not 100% sure how the code works, but automatically making a backup every minute doesn't make sense if no texts have been received or sent. Wouldn't it make more sense to have allow an "instant" backup option that triggers only when a text has actually been received or sent. I'm not familiar with Android development, but I'm guessing this could be triggered by an event notification of some kind from the OS.

Another option might be to instantly make a local cache of texts and then sync them with gmail on a regular schedule.

The specific use-case I'm trying to cover is when texts are deleted soon after being received or sent and before the scheduled backup triggers.

Thanks.

@rsyring commented on GitHub (Dec 24, 2013): I'm wondering if consideration could be given to revisit this issue. I'm not 100% sure how the code works, but automatically making a backup every minute doesn't make sense if no texts have been received or sent. Wouldn't it make more sense to have allow an "instant" backup option that triggers only when a text has actually been received or sent. I'm not familiar with Android development, but I'm guessing this could be triggered by an event notification of some kind from the OS. Another option might be to instantly make a local cache of texts and then sync them with gmail on a regular schedule. The specific use-case I'm trying to cover is when texts are deleted soon after being received or sent and before the scheduled backup triggers. Thanks.

kerem commented

2026-02-26 00:36:30 +03:00

Author

Owner

@chaoqing commented on GitHub (Dec 18, 2018):

@jberkel Hi, I know this issue have been closed a long time ago, but the feature request seems still not handled. The minimal "Incoming Schedule" interval is one minute, which make me wondering whether this is somehow a really needed minimal interval or just one of enum configurations. If it is the second case, does it mean that I can add one interval option like "1 seconds" without introducing bugs?

@chaoqing commented on GitHub (Dec 18, 2018): @jberkel Hi, I know this issue have been closed a long time ago, but the feature request seems still not handled. The minimal "Incoming Schedule" interval is one minute, which make me wondering whether this is somehow a really needed minimal interval or just one of enum configurations. If it is the second case, does it mean that I can add one interval option like "1 seconds" without introducing bugs?

kerem commented

2026-02-26 00:36:30 +03:00

Author

Owner

@chaoqing commented on GitHub (Mar 13, 2019):

if you heavy care about that, you can try to bulid it yourself before jberkel to update.
just change the value of "auto_backup_incoming_schedule_values" in /res/values/arrays.xml

I have already tried this, adding options like 5 seconds. But it seems the incoming backup no longer work. I tried to search the code for some kind of hard limit on minimal interval but do not success. I noticed the actual trigger is done through com.firebase.jobdispatcher.

@jberkel can you explain why this do not work?

@chaoqing commented on GitHub (Mar 13, 2019): > if you heavy care about that, you can try to bulid it yourself before jberkel to update. > just change the value of "auto_backup_incoming_schedule_values" in /res/values/arrays.xml I have already tried this, adding options like `5 seconds`. But it seems the `incoming backup` no longer work. I tried to search the code for some kind of hard limit on minimal interval but do not success. I noticed the actual trigger is done through `com.firebase.jobdispatcher`. @jberkel can you explain why this do not work?

kerem referenced this issue

2026-02-26 01:32:23 +03:00

[PR #194] [MERGED] Mostly translation polish #923