starred/sms-backup-plus-jberkel

Fork 0

mirror of https://github.com/jberkel/sms-backup-plus.git synced 2026-04-25 17:05:59 +03:00

[GH-ISSUE #779] Auto Backup Not Working #639

New issue

Closed

opened 2026-02-26 01:31:11 +03:00 by kerem · 13 comments

kerem commented

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

Owner

Originally created by @srewobwj on GitHub (Aug 12, 2017).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/779

Moto G4 | Android 7.0

"Auto backup" is checked but no longer works, automatically. Manual backups work fine.

Please advise.

TIA

Originally created by @srewobwj on GitHub (Aug 12, 2017). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/779 Moto G4 | Android 7.0 "Auto backup" is checked but no longer works, automatically. Manual backups work fine. Please advise. TIA

kerem

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

closed this issue
added the
backup

v1.5.10
labels

kerem commented

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

Author

Owner

@scottkolman commented on GitHub (Aug 20, 2017):

Same issue. It has been a long time now.

@scottkolman commented on GitHub (Aug 20, 2017): Same issue. It has been a long time now.

kerem commented

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

Author

Owner

@scottkolman commented on GitHub (Aug 20, 2017):

Moto Z Force. Android 7.0. SMS Backup+ 1.5.10

@scottkolman commented on GitHub (Aug 20, 2017): Moto Z Force. Android 7.0. SMS Backup+ 1.5.10

kerem commented

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

Author

Owner

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

Already signaled here:
https://github.com/jberkel/sms-backup-plus/issues/761

@gpion commented on GitHub (Aug 26, 2017): Already signaled here: https://github.com/jberkel/sms-backup-plus/issues/761

kerem commented

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

Author

Owner

@srewobwj commented on GitHub (Aug 28, 2017):

Not sure it's the same issue. I don't get a "connectivity" warning after backups fail, because auto backups never start, to begin with.

@srewobwj commented on GitHub (Aug 28, 2017): Not sure it's the same issue. I don't get a "connectivity" warning after backups fail, because auto backups never start, to begin with.

kerem commented

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

Author

Owner

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

Not sure it's the same issue.

ok then, since there were so few information given (partial logs contents to start with) it was uneasy to make the difference.

@gpion commented on GitHub (Aug 28, 2017): > Not sure it's the same issue. ok then, since there were so few information given (partial logs contents to start with) it was uneasy to make the difference.

kerem commented

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

Author

Owner

@beaudire commented on GitHub (Aug 29, 2017):

I have got exactly the same problem. It's not automatic anymore and it's been like this for months now. So it's becoming pretty useless.

When i check the log, it's totally empty, even after a successful manual backup.

@beaudire commented on GitHub (Aug 29, 2017): I have got exactly the same problem. It's not automatic anymore and it's been like this for months now. So it's becoming pretty useless. When i check the log, it's totally empty, even after a successful manual backup.

kerem commented

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

Author

Owner

@OmenLW commented on GitHub (Sep 10, 2017):

Same issue here as well. Manual backups work, auto backups do not.

LG V20

@OmenLW commented on GitHub (Sep 10, 2017): Same issue here as well. Manual backups work, auto backups do not. LG V20

kerem commented

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

Author

Owner

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

See #572

@jberkel commented on GitHub (Sep 10, 2017): See #572

kerem commented

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

Author

Owner

@PlainJane2017 commented on GitHub (Sep 14, 2017):

I can't help but wondering if the Auto syncing issue started when Gmail disabled their XOAuth to XOAuth2. If I remember correctly, Gmail user should receive an email in 2015 notifying the user they will be changing their Authentication Method to XOAuth2 (wish I have that email). This is the time I believe the SMS Backup+ was having issue with the Auto syncing. If you look on the SMS Backup+ app go to “Advanced settings” then “IMAP server settings the Authentication Method default for Gmail is “XOAuth”. Should that be change to XOAuth2? I could be wrong, but good or bad comment I would like to hear what your take on this. I’ve used this app and thought this was a great app. Hopefully it can be fix.

@PlainJane2017 commented on GitHub (Sep 14, 2017): I can't help but wondering if the Auto syncing issue started when Gmail disabled their XOAuth to XOAuth2. If I remember correctly, Gmail user should receive an email in 2015 notifying the user they will be changing their Authentication Method to XOAuth2 (wish I have that email). This is the time I believe the SMS Backup+ was having issue with the Auto syncing. If you look on the SMS Backup+ app go to “Advanced settings” then “IMAP server settings the Authentication Method default for Gmail is “XOAuth”. Should that be change to XOAuth2? I could be wrong, but good or bad comment I would like to hear what your take on this. I’ve used this app and thought this was a great app. Hopefully it can be fix.

kerem commented

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

Author

Owner

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

@PlainJane2017 it could be that user tokens got invalidated, and that backup stopped working. in this case it should be enough to reconnect to the account.

the auth mechanism used is XOAuth2, i've just updated the UI strings to clarify

@jberkel commented on GitHub (Sep 17, 2017): @PlainJane2017 it could be that user tokens got invalidated, and that backup stopped working. in this case it should be enough to reconnect to the account. the auth mechanism used is XOAuth2, i've just updated the UI strings to clarify

kerem commented

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

Author

Owner

@mgollo commented on GitHub (Mar 9, 2018):

I am using an IMAP account with plaintext as Authentication method using STARTTLS for transport encryption and for me, the Auto Backup settings are completely unavailable (greyed out) on the latest version of SMSBackup+ from F-Droid on LineageOS 14.1. I had the app on my old phone (CopperheadOS based on Android 8.1) and as far as I remember, Automatic Backup did work there. I guess this is related to this issue.

@mgollo commented on GitHub (Mar 9, 2018): I am using an IMAP account with plaintext as Authentication method using STARTTLS for transport encryption and for me, the Auto Backup settings are completely unavailable (greyed out) on the latest version of SMSBackup+ from F-Droid on LineageOS 14.1. I had the app on my old phone (CopperheadOS based on Android 8.1) and as far as I remember, Automatic Backup did work there. I guess this is related to this issue.

kerem commented

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

Author

Owner

@jberkel commented on GitHub (Mar 9, 2018):

@mgollo this has been fixed recently, the version on f-droid is not the most recent. you can download a version from the releases

@jberkel commented on GitHub (Mar 9, 2018): @mgollo this has been fixed recently, the version on f-droid is not the most recent. you can download a version from the [releases](https://github.com/jberkel/sms-backup-plus/releases)

kerem commented

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

Author

Owner

@jberkel commented on GitHub (Mar 28, 2018):

Closed as duplicate of several other issues

@jberkel commented on GitHub (Mar 28, 2018): Closed as duplicate of several other issues

kerem referenced this issue

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

[GH-ISSUE #857] Call Log not saved to Calendar since switch to Android 8 #679

kerem referenced this issue

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