starred/sms-backup-plus-jberkel
1
0
Fork 0
mirror of https://github.com/jberkel/sms-backup-plus.git synced 2026-04-26 01:15:58 +03:00
Code Issues 181 Projects Releases 10 Packages Wiki Activity

[GH-ISSUE #761] Backups always fail with "Backup skipped, no connectivity" message unless done manually #630

New issue
Closed
opened 2026-02-26 01:31:10 +03:00 by kerem · 26 comments
kerem commented 2026-02-26 01:31:10 +03:00
Owner
Copy link

Originally created by @FelisPuma on GitHub (Jun 15, 2017).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/761

Hey there. My backups work great if I manually press the backup button, but won't happen automatically. My log has a bunch of lines
Backup requested (incoming)
Backup skipped, no connectivity
Backup finished
over and over. I have a Galaxy S8 and power saving is disabled for the app.

Thanks!

Originally created by @FelisPuma on GitHub (Jun 15, 2017). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/761 Hey there. My backups work great if I manually press the backup button, but won't happen automatically. My log has a bunch of lines `Backup requested (incoming)` `Backup skipped, no connectivity` `Backup finished` over and over. I have a Galaxy S8 and power saving is disabled for the app. Thanks!
kerem 2026-02-26 01:31:10 +03:00
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jun 18, 2017):

Exact same problem for me on Galaxy S7
Always worked fine with my previous device (Moto X)
--EDIT--
Workaround found: disable in app auto backup and schedule backups externally with Tasker by sending intent "com.zegoggles.smssync.BACKUP" as documented
This even allow better fine tuning of automatic schedule window.

<!-- gh-comment-id:309283352 --> @CoooolRaoul commented on GitHub (Jun 18, 2017): Exact same problem for me on Galaxy S7 Always worked fine with my previous device (Moto X) --EDIT-- Workaround found: disable in app auto backup and schedule backups externally with Tasker by sending intent _"com.zegoggles.smssync.BACKUP"_ as documented This even allow better fine tuning of automatic schedule window.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jun 20, 2017):

Unfortunately workaround doesn't work: still getting "no connectivity" errors in the log file even for entry logged as "third party triggered"

<!-- gh-comment-id:309729502 --> @CoooolRaoul commented on GitHub (Jun 20, 2017): Unfortunately workaround doesn't work: still getting "no connectivity" errors in the log file even for entry logged as "third party triggered"
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Jul 14, 2017):

@CoooolRaoul how is the phone connected? Wifi/3G?

<!-- gh-comment-id:315293156 --> @jberkel commented on GitHub (Jul 14, 2017): @CoooolRaoul how is the phone connected? Wifi/3G?
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jul 14, 2017):

WiFi: I've scheduled 3 syncs at one hour intervals each evening when at home.
None has ever worked.

<!-- gh-comment-id:315298460 --> @CoooolRaoul commented on GitHub (Jul 14, 2017): WiFi: I've scheduled 3 syncs at one hour intervals each evening when at home. None has ever worked.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Jul 14, 2017):

@CoooolRaoul does it work on a mobile connection?

<!-- gh-comment-id:315300770 --> @jberkel commented on GitHub (Jul 14, 2017): @CoooolRaoul does it work on a mobile connection?
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jul 14, 2017):

I've to set up a test case: I forgot to mention that, even on Wifi, it work when screen is on.
For example, when manually launched with a Tasker shortcut to my "SMS Backup Sync" task, sync is successful.
Stay tuned, I'll be back

<!-- gh-comment-id:315302982 --> @CoooolRaoul commented on GitHub (Jul 14, 2017): I've to set up a test case: I forgot to mention that, even on Wifi, it work when screen is on. For example, when manually launched with a Tasker shortcut to my "SMS Backup Sync" task, sync is successful. Stay tuned, I'll be back
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jul 14, 2017):

Here's my Tasker task used as test case:

Screen off sync sms (267)
	A1: System Lock 
	A2: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ] 
	A3: Send Intent [ Action:com.zegoggles.smssync.BACKUP Cat:None Mime Type: Data: Extra: Extra: Extra: Package: Class: Target:Broadcast Receiver ] 
	A4: Play Ringtone [ Type:Notification Sound:Beep Once Stream:5 ]

That one works (on Wifi)
I'm afraid that the "no connectivity" errors arise only when phone has been idle for a sufficient long delay

I've no battery saver tools nor setting which will shut down network when idle (and the phone is always reachable: I'm using "Join" app which allow remote actions and that one responds always even when phone has been idle).

Here's a link to SMS Backup log if it can help
(BTW: mybe should be OK to have the log in english instead of phone default language)

<!-- gh-comment-id:315306555 --> @CoooolRaoul commented on GitHub (Jul 14, 2017): Here's my Tasker task used as test case: ``` Screen off sync sms (267) A1: System Lock A2: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ] A3: Send Intent [ Action:com.zegoggles.smssync.BACKUP Cat:None Mime Type: Data: Extra: Extra: Extra: Package: Class: Target:Broadcast Receiver ] A4: Play Ringtone [ Type:Notification Sound:Beep Once Stream:5 ] ``` That one works (on Wifi) I'm afraid that the _"no connectivity"_ errors arise only when phone has been idle for a sufficient long delay I've no battery saver tools nor setting which will shut down network when idle (and the phone is always reachable: I'm using "Join" app which allow remote actions and that one responds always even when phone has been idle). Here's a [link to SMS Backup log ](https://pastebin.com/LSvpsgFh)if it can help (BTW: mybe should be OK to have the log in english instead of phone default language)
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jul 14, 2017):

To be complete, here's my daily backup Profile (which fails):

Profile: SMS Backup 
	Time: From 20:00 every 1h Till 23:00
	State: Wifi Connected [ SSID:* MAC:* IP:* Active:Yes ]
Enter: SMS Backup
	A1: Send Intent [ 
        Action:com.zegoggles.smssync.BACKUP
        Cat:None Mime
        Type: Data: Extra: Extra: Extra: Package:
        Class: Target:Broadcast Receiver ]
<!-- gh-comment-id:315313275 --> @CoooolRaoul commented on GitHub (Jul 14, 2017): To be complete, here's my daily backup Profile (which fails): ``` Profile: SMS Backup Time: From 20:00 every 1h Till 23:00 State: Wifi Connected [ SSID:* MAC:* IP:* Active:Yes ] Enter: SMS Backup A1: Send Intent [ Action:com.zegoggles.smssync.BACKUP Cat:None Mime Type: Data: Extra: Extra: Extra: Package: Class: Target:Broadcast Receiver ] ```
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Jul 14, 2017):

Hmm, that is strange. It is probably some powersaving mechanism, somewhere, Android got really aggressive about that. Have you tried the backup while running "Join" (supposing it does something to keep the network connection alive?)

<!-- gh-comment-id:315483332 --> @jberkel commented on GitHub (Jul 14, 2017): Hmm, that is strange. It is probably some powersaving mechanism, somewhere, Android got really aggressive about that. Have you tried the backup while running "Join" (supposing it does something to keep the network connection alive?)
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jul 15, 2017):

Have you tried the backup while running "Join"

Join is always running in background (it always reacts to external events)
And, according to its log file, SMS Backup don't seem to be killed or Frozen when phone is idle.
I guess it's the way it tries to detect network connection which maybe has issue.

<!-- gh-comment-id:315514278 --> @CoooolRaoul commented on GitHub (Jul 15, 2017): > Have you tried the backup while running "Join" Join is always running in background (it always reacts to external events) And, according to its log file, SMS Backup don't seem to be killed or Frozen when phone is idle. I guess it's the way it tries to detect network connection which maybe has issue.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jul 15, 2017):

Browsing the code, I guess it's here , in SmsBackupService.checkConnectivity, that network connectivity is checked.

Which seem totally OK for me.
Really weird.

<!-- gh-comment-id:315515317 --> @CoooolRaoul commented on GitHub (Jul 15, 2017): Browsing the code, I guess it's [here](https://github.com/jberkel/sms-backup-plus/blob/20949b1fdd38b7dc183f8f2de5d8b30484b3ed31/src/main/java/com/zegoggles/smssync/service/SmsBackupService.java#L168) , in SmsBackupService.checkConnectivity, that network connectivity is checked. Which seem totally OK for me. Really weird.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Jul 15, 2017):

Yes, it's the recommended way, and haven't heard of any other problems with it. maybe I can create a version with some more debug logging for you.

On 15 July 2017 at 10:01:08, CoooolRaoul (notifications@github.com(mailto:notifications@github.com)) wrote:

Browsing the codes, I gues it's here(github.com/jberkel/sms-backup-plus@20949b1fdd/src/main/java/com/zegoggles/smssync/service/SmsBackupService.java (L168)) you check networkconnectivity.

Which seem totally OK for me.
Really weird.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub(https://github.com/jberkel/sms-backup-plus/issues/761#issuecomment-315515317), or mute the thread(https://github.com/notifications/unsubscribe-auth/AABJy7A7U-cLkr_mdWzSLhSF9b91wWvpks5sOGO0gaJpZM4N6o4x).

<!-- gh-comment-id:315515807 --> @jberkel commented on GitHub (Jul 15, 2017): Yes, it's the recommended way, and haven't heard of any other problems with it. maybe I can create a version with some more debug logging for you. On 15 July 2017 at 10:01:08, CoooolRaoul (notifications@github.com(mailto:notifications@github.com)) wrote: > > > Browsing the codes, I gues it's here(https://github.com/jberkel/sms-backup-plus/blob/20949b1fdd38b7dc183f8f2de5d8b30484b3ed31/src/main/java/com/zegoggles/smssync/service/SmsBackupService.java#L168) you check networkconnectivity. > > > Which seem totally OK for me. > Really weird. > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub(https://github.com/jberkel/sms-backup-plus/issues/761#issuecomment-315515317), or mute the thread(https://github.com/notifications/unsubscribe-auth/AABJy7A7U-cLkr_mdWzSLhSF9b91wWvpks5sOGO0gaJpZM4N6o4x). > > > > >
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jul 15, 2017):

haven't heard of any other problems with it

@FelisPuma , initial poster has this issue too.

maybe I can create a version with some more debug logging for you.

no problem, I'll be glad to help.

<!-- gh-comment-id:315516735 --> @CoooolRaoul commented on GitHub (Jul 15, 2017): > haven't heard of any other problems with it @FelisPuma , initial poster has this issue too. > maybe I can create a version with some more debug logging for you. no problem, I'll be glad to help.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jul 15, 2017):

Since I'm at home now, I've modified the task schedule to have it run every 15 minutes
I don't understand why but it seem to be working (no more errors in the log)
I will collect the logs tomorrow to better pinpoint when it fails
Stay tuned

<!-- gh-comment-id:315521092 --> @CoooolRaoul commented on GitHub (Jul 15, 2017): Since I'm at home now, I've modified the task schedule to have it run every 15 minutes I don't understand why but it seem to be working (no more errors in the log) I will collect the logs tomorrow to better pinpoint when it fails Stay tuned
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@CoooolRaoul commented on GitHub (Jul 16, 2017):

Stay tuned

No connectivity errors since yesterday! (full log here: https://pastebin.com/e2skA93u)
I don't know why my Tasker 15mn schedule stopped working after midnight but that's another issue
I going to switch to built-in auto backup to see if it works again too.

<!-- gh-comment-id:315594925 --> @CoooolRaoul commented on GitHub (Jul 16, 2017): > Stay tuned No connectivity errors since yesterday! (full log here: https://pastebin.com/e2skA93u) I don't know why my Tasker 15mn schedule stopped working after midnight but that's another issue I going to switch to built-in auto backup to see if it works again too.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@FelisPuma commented on GitHub (Jul 16, 2017):

I appreciate all the work @CoooolRaoul is doing tracking this down, but I'm pretty my issues is different. Notice that my manual backups are always successful, as are the INCOMING triggered ones for awhile, before they start getting the connectivity error. https://pastebin.com/v5FbEv3k Seems a lot like power management, but app is set to unmonitored.

<!-- gh-comment-id:315595190 --> @FelisPuma commented on GitHub (Jul 16, 2017): I appreciate all the work @CoooolRaoul is doing tracking this down, but I'm pretty my issues is different. Notice that my manual backups are always successful, as are the INCOMING triggered ones for awhile, before they start getting the connectivity error. https://pastebin.com/v5FbEv3k Seems a lot like power management, but app is set to unmonitored.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@gpion commented on GitHub (Aug 6, 2017):

I don't think I've a different issue than yours @FelisPuma : like you, my manual backups are always successful. It's only ones automatically triggered in background which fails.
I've modified my Tasker task to ping www.google.com and redirect output to sms_backup_plus.log just before triggering the backup:

Profile: SMS Backup (249)
	Time:  Every 6h
	State: Wifi Connected [ SSID:* MAC:* IP:* Active:Yes ]
Enter: SMS Backup (257)
	A1: Run Shell [ Command:ping -c1 www.google.com Timeout (Seconds):0 Use Root:Off Store Output In:%out Store Errors In: Store Result In: ] 
	A2: Write File [ File:sms_backup_plus.log Text:%out Append:On Add Newline:On ] 
	A3: Send Intent [ Action:com.zegoggles.smssync.BACKUP Cat:None Mime Type: Data: Extra: Extra: Extra: Package: Class: Target:Broadcast Receiver ]

It appears that although ping is successful, log file show that backup fails with error.

Here's the log excerpt of a failed backup

PING www.google.com (74.125.206.105) 56(84) bytes of data.
64 bytes from wk-in-f105.1e100.net (74.125.206.105): icmp_seq=1 ttl=46 time=42.2 ms

--- www.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 42.244/42.244/42.244/0.000 ms
05-08 18:00 Sauvegarde demandée (application tierce)
05-08 18:00 Sauvegarde non effectuée, aucune connection
05-08 18:00 Sauvegarde effectuée

("Sauvegarde non effectuée, aucune connection" is the French for "Backup skipped, no connectivity")

That's driving me crazy since it makes that app pretty much useless for me.

<!-- gh-comment-id:320487124 --> @gpion commented on GitHub (Aug 6, 2017): I don't think I've a different issue than yours @FelisPuma : like you, my manual backups are *always* successful. It's only ones automatically triggered in background which fails. I've modified my Tasker task to ping www.google.com and redirect output to sms_backup_plus.log just before triggering the backup: ``` Profile: SMS Backup (249) Time: Every 6h State: Wifi Connected [ SSID:* MAC:* IP:* Active:Yes ] Enter: SMS Backup (257) A1: Run Shell [ Command:ping -c1 www.google.com Timeout (Seconds):0 Use Root:Off Store Output In:%out Store Errors In: Store Result In: ] A2: Write File [ File:sms_backup_plus.log Text:%out Append:On Add Newline:On ] A3: Send Intent [ Action:com.zegoggles.smssync.BACKUP Cat:None Mime Type: Data: Extra: Extra: Extra: Package: Class: Target:Broadcast Receiver ] ``` It appears that although ping is successful, log file show that backup fails with error. Here's the log excerpt of a failed backup ``` PING www.google.com (74.125.206.105) 56(84) bytes of data. 64 bytes from wk-in-f105.1e100.net (74.125.206.105): icmp_seq=1 ttl=46 time=42.2 ms --- www.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 42.244/42.244/42.244/0.000 ms 05-08 18:00 Sauvegarde demandée (application tierce) 05-08 18:00 Sauvegarde non effectuée, aucune connection 05-08 18:00 Sauvegarde effectuée ``` (_"Sauvegarde non effectuée, aucune connection"_ is the French for _"Backup skipped, no connectivity"_) That's driving me crazy since it makes that app pretty much useless for me.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@jberkel commented on GitHub (Sep 11, 2017):

hmm, maybe it should just try to open the connection, regardless of what the system says

<!-- gh-comment-id:328384638 --> @jberkel commented on GitHub (Sep 11, 2017): hmm, maybe it should just try to open the connection, regardless of what the system says
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@rkleivel commented on GitHub (Oct 7, 2017):

Got the same problem on my new Galaxy Note8. It has worked flawlessly on my previous LG G5 on Android 7.0, and also on Galaxy S5 and Note3 before that.
Manual backup works every time, but automatic logs the following:

-10 07:35 Backup requested (regular)
06-10 07:35 Backup skipped, no connectivity
06-10 07:35 Backup finished
06-10 07:35 Next backup scheduled for: 13:35
06-10 08:44 Backup requested (regular)
06-10 08:44 Backup skipped, no connectivity
06-10 08:44 Backup finished
06-10 08:44 Next backup scheduled for: 14:44
06-10 19:31 Backup requested (incoming)
06-10 19:31 Backup skipped, no connectivity
06-10 19:31 Backup finished
06-10 19:31 Backup requested (incoming)
06-10 19:31 Backup skipped, no connectivity
06-10 19:31 Backup finished
06-10 21:07 Backup requested (incoming)
06-10 21:07 Backup skipped, no connectivity
06-10 21:07 Backup finished
06-10 21:10 Backup requested (incoming)
06-10 21:10 Backup skipped, no connectivity
06-10 21:10 Backup finished
07-10 11:17 Backup requested (incoming)
07-10 11:17 Backup skipped, no connectivity
07-10 11:17 Backup finished
07-10 13:01 Backup requested (manual)
07-10 13:01 Starting backup (MANUAL)
07-10 13:01 Backing up (32 SMS, 3 MMS, 13 call log)
07-10 13:02 Backup finished

<!-- gh-comment-id:334927748 --> @rkleivel commented on GitHub (Oct 7, 2017): Got the same problem on my new Galaxy Note8. It has worked flawlessly on my previous LG G5 on Android 7.0, and also on Galaxy S5 and Note3 before that. Manual backup works every time, but automatic logs the following: -10 07:35 Backup requested (regular) 06-10 07:35 Backup skipped, no connectivity 06-10 07:35 Backup finished 06-10 07:35 Next backup scheduled for: 13:35 06-10 08:44 Backup requested (regular) 06-10 08:44 Backup skipped, no connectivity 06-10 08:44 Backup finished 06-10 08:44 Next backup scheduled for: 14:44 06-10 19:31 Backup requested (incoming) 06-10 19:31 Backup skipped, no connectivity 06-10 19:31 Backup finished 06-10 19:31 Backup requested (incoming) 06-10 19:31 Backup skipped, no connectivity 06-10 19:31 Backup finished 06-10 21:07 Backup requested (incoming) 06-10 21:07 Backup skipped, no connectivity 06-10 21:07 Backup finished 06-10 21:10 Backup requested (incoming) 06-10 21:10 Backup skipped, no connectivity 06-10 21:10 Backup finished 07-10 11:17 Backup requested (incoming) 07-10 11:17 Backup skipped, no connectivity 07-10 11:17 Backup finished 07-10 13:01 Backup requested (manual) 07-10 13:01 Starting backup (MANUAL) 07-10 13:01 Backing up (32 SMS, 3 MMS, 13 call log) 07-10 13:02 Backup finished
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@jcrben commented on GitHub (Mar 31, 2018):

@participants could any of you please try out the latest beta? https://github.com/jberkel/sms-backup-plus#beta

We want to know whether this is fixed before releasing 1.5.11.

<!-- gh-comment-id:377706875 --> @jcrben commented on GitHub (Mar 31, 2018): @participants could any of you please try out the latest beta? https://github.com/jberkel/sms-backup-plus#beta We want to know whether this is fixed before releasing 1.5.11.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@FelisPuma commented on GitHub (Apr 4, 2018):

I've installed the update, I'll let you know if there's a fix in a couple days. Thanks for looking into this issue!

<!-- gh-comment-id:378735039 --> @FelisPuma commented on GitHub (Apr 4, 2018): I've installed the update, I'll let you know if there's a fix in a couple days. Thanks for looking into this issue!
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@jcrben commented on GitHub (Apr 14, 2018):

@FelisPuma ping - would be good to get confirmation before releasing 1.5.11

<!-- gh-comment-id:381338845 --> @jcrben commented on GitHub (Apr 14, 2018): @FelisPuma ping - would be good to get confirmation before releasing 1.5.11
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@FelisPuma commented on GitHub (Apr 17, 2018):

Honestly I'm not 100% sure. As far as I can tell it is running the scheduled backups and incoming message backups as it should, but when I went to manually backup there were a few extra messages for some reason (but just 10s out of 100s, not sure why those were left). If it's not fixed it's much better though, since before it would stop backing up completely after a few days. Here's the log:

This is the error that still occurs, but it doesn't seem to be causing any problems, since it works on 3rd retry.

04-11 12:17 Starting backup (INCOMING)
04-11 12:17 Backing up (1 SMS, 0 MMS, 3 call log)
04-11 12:18 General error: Cannot connect to host imap.gmail.com:993 (exception: com.fsck.k9.mail.MessagingException: Cannot connect to host imap.gmail.com:993)
04-11 12:18 Backup finished
04-11 12:18 Backup requested (incoming)
04-11 12:18 Starting backup (INCOMING)
04-11 12:18 Backing up (1 SMS, 0 MMS, 3 call log)
04-11 12:19 General error: Cannot connect to host imap.gmail.com:993 (exception: com.fsck.k9.mail.MessagingException: Cannot connect to host imap.gmail.com:993)
04-11 12:19 Backup finished
04-11 12:20 Backup requested (incoming)
04-11 12:20 Starting backup (INCOMING)
04-11 12:20 Backing up (1 SMS, 0 MMS, 3 call log)
04-11 12:20 Backing up (1 SMS, 0 MMS, 3 call log)
04-11 12:20 Backup finished

Here is a manual update that finds something, even though previous incoming update says no messages. Not sure exactly why or if it would have resolved itself if I hadn't done manual. Like I said, I'm not sure if this is even an issue at all, so probably safe to mark fixed?

04-14 02:42 Starting backup (INCOMING)
04-14 02:42 Skipped (no items found)
04-14 02:42 Backup finished
04-14 14:22 Backup requested (manual)
04-14 14:22 Starting backup (MANUAL)
04-14 14:22 Backing up (18 SMS, 1 MMS, 2 call log)
04-14 14:22 Backing up (18 SMS, 1 MMS, 2 call log)
04-14 14:22 Backup finished
<!-- gh-comment-id:381810121 --> @FelisPuma commented on GitHub (Apr 17, 2018): Honestly I'm not 100% sure. As far as I can tell it is running the scheduled backups and incoming message backups as it should, but when I went to manually backup there were a few extra messages for some reason (but just 10s out of 100s, not sure why those were left). If it's not fixed it's much better though, since before it would stop backing up completely after a few days. Here's the log: This is the error that still occurs, but it doesn't seem to be causing any problems, since it works on 3rd retry. ```04-11 12:17 Backup requested (incoming) 04-11 12:17 Starting backup (INCOMING) 04-11 12:17 Backing up (1 SMS, 0 MMS, 3 call log) 04-11 12:18 General error: Cannot connect to host imap.gmail.com:993 (exception: com.fsck.k9.mail.MessagingException: Cannot connect to host imap.gmail.com:993) 04-11 12:18 Backup finished 04-11 12:18 Backup requested (incoming) 04-11 12:18 Starting backup (INCOMING) 04-11 12:18 Backing up (1 SMS, 0 MMS, 3 call log) 04-11 12:19 General error: Cannot connect to host imap.gmail.com:993 (exception: com.fsck.k9.mail.MessagingException: Cannot connect to host imap.gmail.com:993) 04-11 12:19 Backup finished 04-11 12:20 Backup requested (incoming) 04-11 12:20 Starting backup (INCOMING) 04-11 12:20 Backing up (1 SMS, 0 MMS, 3 call log) 04-11 12:20 Backing up (1 SMS, 0 MMS, 3 call log) 04-11 12:20 Backup finished ``` Here is a manual update that finds something, even though previous incoming update says no messages. Not sure exactly why or if it would have resolved itself if I hadn't done manual. Like I said, I'm not sure if this is even an issue at all, so probably safe to mark fixed? ```04-14 02:42 Backup requested (incoming) 04-14 02:42 Starting backup (INCOMING) 04-14 02:42 Skipped (no items found) 04-14 02:42 Backup finished 04-14 14:22 Backup requested (manual) 04-14 14:22 Starting backup (MANUAL) 04-14 14:22 Backing up (18 SMS, 1 MMS, 2 call log) 04-14 14:22 Backing up (18 SMS, 1 MMS, 2 call log) 04-14 14:22 Backup finished ```
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@pcandme commented on GitHub (Apr 18, 2018):

Same issue here on Galaxy Note 8. I doubt this problem only happens on the Galaxy phones. Anyway, my phone's Android version is 8.0.0, the app version is 1.5.10, and the log is as follows:

(...many same errors...)
04-17 15:46 Backup requested (incoming)
04-17 15:46 Backup skipped, no connectivity
04-17 15:46 Backup finished
04-17 17:23 Backup requested (incoming)
04-17 17:23 Backup skipped, no connectivity
04-17 17:23 Backup finished
04-17 17:23 Backup requested (incoming)
04-17 17:23 Backup skipped, no connectivity
04-17 17:23 Backup finished
04-18 09:33 Backup requested (manual)
04-18 09:33 Starting backup (MANUAL)
04-18 09:33 Backing up (141 SMS, 18 MMS, 67 call log)
04-18 09:33 Backing up (141 SMS, 18 MMS, 67 call log)
04-18 09:39 Backup finished

As you can see, manual backup works well.

Thank you.

<!-- gh-comment-id:382209743 --> @pcandme commented on GitHub (Apr 18, 2018): Same issue here on Galaxy Note 8. I doubt this problem only happens on the Galaxy phones. Anyway, my phone's Android version is 8.0.0, the app version is 1.5.10, and the log is as follows: ``` (...many same errors...) 04-17 15:46 Backup requested (incoming) 04-17 15:46 Backup skipped, no connectivity 04-17 15:46 Backup finished 04-17 17:23 Backup requested (incoming) 04-17 17:23 Backup skipped, no connectivity 04-17 17:23 Backup finished 04-17 17:23 Backup requested (incoming) 04-17 17:23 Backup skipped, no connectivity 04-17 17:23 Backup finished 04-18 09:33 Backup requested (manual) 04-18 09:33 Starting backup (MANUAL) 04-18 09:33 Backing up (141 SMS, 18 MMS, 67 call log) 04-18 09:33 Backing up (141 SMS, 18 MMS, 67 call log) 04-18 09:39 Backup finished ``` As you can see, manual backup works well. Thank you.
kerem commented 2026-02-26 01:31:10 +03:00
Author
Owner
Copy link

@pcandme commented on GitHub (Apr 19, 2018):

It started to work well since I did it manually yesterday. I changed the auto backup settings to 1 h for regular, 30 min for incoming schedule from shorter schedules, I'm not sure if this affects it.

<!-- gh-comment-id:382606822 --> @pcandme commented on GitHub (Apr 19, 2018): It started to work well since I did it manually yesterday. I changed the auto backup settings to 1 h for regular, 30 min for incoming schedule from shorter schedules, I'm not sure if this affects it.
kerem commented 2026-02-26 01:31:11 +03:00
Author
Owner
Copy link

@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.

<!-- gh-comment-id:876791483 --> @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.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
cyber1000-docker
multisim
update-build-process
gh-pages
jcrben-patch-1
workmanager
jcrben-patch-2
old-sms-backup
1.6.0-BETA2
1.6.0-BETA1
1.5.11
1.5.11-BETA22
1.5.11-BETA21
1.5.11-BETA20
1.5.11-BETA19
1.5.11-BETA18
1.5.11-BETA17
1.5.11-BETA16
1.5.11-BETA15
1.5.11-BETA14
1.5.11-BETA13
1.5.11-BETA12
1.5.11-BETA11
1.5.11-BETA10
1.5.11-BETA9
1.5.11-BETA8
1.5.11-BETA7
1.5.11-BETA6
1.5.11-BETA5
1.5.11-BETA4
1.5.11-BETA3
1.5.11-BETA2
1.5.11-BETA1
1.5.10
1.5.10-BETA1
1.5.9
1.5.9-BETA6
1.5.9-BETA5
1.5.9-BETA4
1.5.9-BETA3
1.5.9-BETA2
1.5.9-BETA1
1.5.8
1.5.8-BETA2
1.5.8-BETA1
1.5.7
1.5.7-BETA2
1.5.7-BETA1
1.5.6-DEBUG
1.5.6
1.5.6-RC1
1.5.6-BETA11
1.5.6-BETA10
1.5.6-BETA9
1.5.6-BETA8
1.5.6-BETA7
1.5.6-BETA6
1.5.6-BETA5
1.5.6-BETA4
1.5.6-BETA3
1.5.6-BETA2
1.5.6-BETA1
1.5.5
1.5.5-BETA2
1.5.5-BETA1
1.5.4
1.5.4-BETA2
1.5.4-BETA1
1.5.3
1.5.2
1.5.1
1.5.0
1.4.8
1.4.7
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.7
1.3.6
1.3.5
1.3.4
1.3.3
1.3.1
1.3.2
1.3
1.2
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1
1.0.11
1.0.10
1.0.9
1.0.8
1.0.7
1.0.6
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
1.0
Labels
Clear labels   
AM+RCS

   
FAQ

   
awaiting response

   
backup

   
bespoke

   
bug

   
calendar

   
call log

   
cannot reproduce

   
cloudless

   
device-specific

   
documentation

   
dual- & multi-SIM

   
duplicate

   
feature-request

   
fixed in beta

   
good first issue

   
half-missing

   
help wanted

   
helpful

   
meta

   
misattribution

   
mms

   
other message sources

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
rejuvenation

   
restore

   
schedule

   
security

   
stale

   
task

   
thanks

   
v1.5.1

   
v1.5.10

   
v1.5.11

   
v1.5.2

   
v1.5.3

   
v1.5.3

   
v1.5.4

   
v1.5.4

   
v1.5.5

   
v1.5.5

   
v1.5.6

   
v1.5.7

   
v1.5.8

   
v1.5.9

   
v1.6β

   
xoauth

   
~$ bounty $~
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/sms-backup-plus-jberkel#630
No description provided.