mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #758] Automatic back-up not working reliably #625
Labels
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 $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#625
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rustyjarz on GitHub (May 15, 2017).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/758
Hi - SMS autobackup doesn't seem to be happening on the latest version of Andriod (nougat). I really liked this feature, so if you could fix it that would awesome.
@GreenHex commented on GitHub (May 24, 2017):
I am having the same problem with v1.5.10 running on Android 5.1 (Meizu M3s).
"Regular schedule" and "Incoming schedule" give the following error: "isConnection failed; ENETUNREACH". However manual backup by pressing the button works perfectly.
@mhofman commented on GitHub (May 25, 2017):
I think if you go to battery settings, battery optimizations, and set SMS Backup+ to "Not optimized" it will resume backing up automatically without delay.
@jasonab commented on GitHub (Oct 3, 2017):
I have this problem as well, just changed the setting. Is there a code change that needs to be made here?
@rustyjarz commented on GitHub (Oct 3, 2017):
I've modified the power-saving features so this app is not 'optimised' for power saving, but hasn't fixed the problem.
@gaiuslove commented on GitHub (Nov 25, 2017):
Problems lead to Solutions.
To get Android nougat to allow SMS backup to automatically backup, change this setting with these steps:
Settings, device maintenance, Battery, unmonitored apps, add apps, add "SMS Backup+" .
See screenshots to help assist you in this.
@gaiuslove commented on GitHub (Nov 25, 2017):
It won't let me leave a screenshot. Okay. But you get the picture.
@rustyjarz commented on GitHub (Nov 26, 2017):
gaiuslove none of the settings labels you're referring to in your post marry up to the setting I have.
@gaiuslove commented on GitHub (Nov 26, 2017):
I have Android 7.1.1, and that is the process by which my SMS backup's automatic backup started to work again.
@rustyjarz commented on GitHub (Nov 26, 2017):
gaiuslove any chance you could take the screenshots and put them in a document and share via dropbox or similar?
@gaiuslove commented on GitHub (Nov 26, 2017):
Now it's letting me leave a screen shot. I'm on my laptop now, not on my phone as before:
@gaiuslove commented on GitHub (Nov 26, 2017):
@jberkel commented on GitHub (Dec 20, 2017):
Please try the new beta: https://github.com/jberkel/sms-backup-plus#beta
It should work without changes to the unmonitored apps configuration
@gaiuslove commented on GitHub (Dec 20, 2017):
When I click on Google Play to install it, it says it's already installed. Will it work if I uninstall my current version of SMS back up and install this one?
Sent from Yahoo Mail on Android
On Wed, Dec 20, 2017 at 3:11 PM, Jan Berkelnotifications@github.com wrote:
Please try the new beta: https://github.com/jberkel/sms-backup-plus#beta
It should work without changes to the unmonitored apps configuration
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
@rustyjarz commented on GitHub (Dec 20, 2017):
gaiuslove if you read through the Beta Testing section of the page, it explains how to become a beta tester.
@jasonab commented on GitHub (Dec 20, 2017):
@gaiuslove have you signed up for the beta program in Google Play? If so, it should push you an update soon (mine just showed up). If not, you need to scroll to the bottom of the app page in Play and click the sign up button.
@jcrben commented on GitHub (Apr 24, 2018):
This has been added to the 1.6.0 milestone - I think the idea is to figure out how to ensure that the sleep doesn't affect the automatic backup.
@jberkel is that what you're thinking? I think we should update the title of this issue or fold it into a meta issue around this topic as this is just an unclear bug report
@jberkel commented on GitHub (Apr 24, 2018):
@jcrben it looks like a duplicate issue and should be merged
@gaiuslove commented on GitHub (Apr 24, 2018):
Google play just offered me the (once beta) 1.5.11 and I installed the update. When updating it, I also opted into the beta testing program. Has this (doesn't automatically back-up while phone is sleeping) bug been corrected in 1.5.11, (I guess I will soon see, as I now have 1.5.11), or will it be corrected in 1.6.0 ?
@kurahaupo commented on GitHub (Jul 8, 2021):
I've closed a bunch of other tickets marking them as duplicates of this one. I've selected this one because (a) it has the most comments already, and (b) it's nearly the oldest.
There are two common themes among the other tickets, other than simply "doesn't work":
To which I add my own observations:
@mwisnicki commented on GitHub (Jul 10, 2021):
FWIW It's been working for me so far on Samsung Galaxy Note 10+ with latest Android 11 after I've disabled battery optimizations.
@kurahaupo commented on GitHub (Jul 12, 2021):
@mwisnicki Yes and it works for me too. Which makes it rather frustrating to diagnose the exact problem.
@madduck commented on GitHub (Aug 5, 2021):
Not working on LineageOS 18.1 (Android 11) on the OnePlus 5T, despite the app being "not optimized" for battery.
com.zegoggles.smssyncis a running process, but it seems it never gets a chance to run, not in response to an incoming text, nor on a schedule. Been monitoringadb logcat *:S SMSBackup+:V k9:Vfor hours now, having received multiple text messages since I started.Manual backups work. I am not using Google, of course not.
@kaistian commented on GitHub (Aug 27, 2021):
It's also not working on CalyxOS 2.8.0 (Android 11) on a Pixel 5 with "not optimized"
Manual backups work fine to Dovecot IMAP server.
Just tried SMS Gate which is a fork of SMS Backup+ and it works, even when it's not set to "not optimized" yet.
So maybe look at the source there to get an idea how to fix the issue.
@Dubroamer commented on GitHub (Sep 30, 2022):
Had same issue and battery optimization did not help but noticed in MOBILE DATA section I had allowed app run in the background but not while data saver was on. So would not back up automatically even when data saver was off but once I allowed this it backed up perfectly on its own.
@madduck commented on GitHub (Oct 3, 2022):
@Dubroamer Do you think this would have an effect even if I don't use datasaver? I've flicked it now, but so far have not been able to notice a difference.
@Dubroamer commented on GitHub (Oct 3, 2022):
Perhaps. I never turned data saver on and I tried everything else without success before noticing that setting was on. Once I restarted the phone it backed up on its own
@sooyhwang commented on GitHub (Dec 8, 2022):
I turned off the battery optimization and also turned on the mobile data setting that @Dubroamer mentioned above, but nothing happened (i.e. empty log). Then I turned on the "Old backup scheduler" option under "Auto backup settings" and the auto backups started to work! I had tried this old backup scheduler option before and it didn't work, so the combination of battery and background mobile data setting as well as the old scheduler option seem to have done the trick. Phone is Pixel 7 on Android 13.
@sooyhwang commented on GitHub (Dec 13, 2022):
I spoke too soon. In addition to what I did above, the sync seems to work only when the sync log is enabled. If I turn off the sync log collection, syncing stops after about a day. Sync resumed once I turned on the log again. Has anyone noticed this?
@highfalutin commented on GitHub (Dec 13, 2022):
Automatic backup does not work on my phone despite having everything set
the way you describe, @sooyhwang
On Mon, Dec 12, 2022, 18:10 S. Hwang @.***> wrote:
@madduck commented on GitHub (Dec 13, 2022):
Same here, no automatic backups with or without log, neither on a schedule, nor on incoming SMS messages.
@mwisnicki commented on GitHub (Dec 13, 2022):
Same here actually, it looks like it stopped working.
This time Samsung S22 Ultra / Android 13. Last scheduled backup ran in Nov 16 which might've been right before update to Android 13.
@voopoo commented on GitHub (Dec 21, 2022):
Hi everyone I had this app working with Samsung note 9 and I bought a new phone s20+ android 13, after installing and configuring (imap/Outlook server) the manual sync would work but the auto sync just stood idle/never worked. After messing around I think I've fixed it by running the Samsung calendar stock app and letting it sync once. After they first sync the smsbackup+ autosync started working as it should. Hope this helps someone else. Cheers
@madduck commented on GitHub (Dec 21, 2022):
@voopoo Why would that fix it?
@voopoo commented on GitHub (Dec 21, 2022):
I don't know, it triggered something? Wish I knew. This is what I remember doing: tried installing alternative apps (since this one wasn't auto syncing since day 1), like sms gate, call log calendar, calls & sms to calendar but I wasn't happy with any of them so I froze them with titanium backup and decided to reinstall/reconfigure sms backup+ again, I went to check calendar to see if my email was showing up/syncing and I saw an entry being added automatically, that's when I found out it was working and it has been since.
@marcellusca commented on GitHub (Jan 20, 2023):
Hello,
I have a Google Pixel 5 running Android 13 Tiramisu with SMS Backup+ 1.5.11. I've already enabled unrestricted battery for the app and have no improvement as automatic backup does not run but manual backup does.
Any new developments and recommendations on the solution for this? Much appreciated.
@sshaikh commented on GitHub (Jan 28, 2023):
Pixel 6a and same issue, worked fine on previous handset.
@teezeuay commented on GitHub (Jan 30, 2023):
my backup worked flawless on a samsung galaxy s9 for years with IMAP signin. 2 weeks ago the auto backup stopped. I regenerated a new password and restarted phone which worked last time. This time NO. I see in the past everyone said to use edge but I dont have the option to authenticate that way. I checked sleeping apps and battery settings which seem all correct. What am I missing. Manual backups work tho
@highfalutin commented on GitHub (Jan 30, 2023):
@teezeuay you're not missing anything, the software isn't doing automatic backups for any of us
@teezeuay commented on GitHub (Jan 31, 2023):
THANKS, It just sucks cause it worked flawlessly for 8 months, then boom,
in the middle of the day it just stops, Like what happened. Prob google
updates we cant see
On Mon, Jan 30, 2023 at 5:05 PM highfalutin @.***>
wrote:
@voopoo commented on GitHub (Jan 31, 2023):
I had same the problem and it's working for me (auto backup/incoming and manual - on Android 13) I just can't pin point what I did to fix it, I remember reinstalling the app from scratch and messed around with calendar and email app (Samsung apps in my case) Have you tried reinstalling and reconfiguring the sms+ again? I'm using plain auth on @outlook.com
@samej71 commented on GitHub (Jan 31, 2023):
I suspect the the latest round of breaks is related to the upgrade to Android 13. As a workaround, I think I am going to try to uninstall and reinstall in the hopes that there is something in the installation process that triggers granting permission to schedule/execute background jobs that isn't happening if the app is present during the upgrade.
@teezeuay commented on GitHub (Jan 31, 2023):
i have not tried that yet. I have in the past and I had to back up all the
messages all over again which took forever! what does plain auth on @
outlook.com mean? I only have the unsupported gmail option or IMAP.
On Tue, Jan 31, 2023 at 11:38 AM samej71 @.***> wrote:
@madduck commented on GitHub (Jan 31, 2023):
It has not been working for years now. I think it stopped working for me around Android 6 or 7. Nice if reinstalling works for you, but I think the problem is a different one from what can be solved with a reinstall.
@voopoo commented on GitHub (Feb 1, 2023):
I mean I'm using plain text method for authentication (custom imap server options) and I'm using an outlook email to sync calls on calendar and sms on outlook email (sms folder) I ve been using this app for years and it's working, I recently bought an s20+ and at first the auto sync wasn't working but it is now
@samej71 commented on GitHub (Feb 3, 2023):
Update from previous comment: Uninstalling and reinstalling did not change anything for me (not surprising but wanted to rule it out).
I've been trying to dig a bit and found two things, which may or may not be significant, but to one of the contributing developers it might be useful:
Despite the FOREGROUND_SERVICES in the manifest, when I view the permissions granted to the app, this permission is not listed, but it is also not listed in denied permissions. It is listed for another app I use (Automate), so it seems reasonable to think it would be listed for SMS Backup+, too. I'm not quite sure of the purpose of this permission yet, but it might be for ongoing notifications?
In viewing debug logs, I see a log entry that I think correlates to a received SMS and is triggering the backup process:
[02-02 22:41:29.260 1691:2947 D/ActivityManager] Received SERVICE intent 0x3bc9d43 Key{startService pkg=com.zegoggles.smssync intent=act=INCOMING cmp=com.zegoggles.smssync/.service.SmsBackupService flags=0x0 u=0} requestCode=0 from uid 1000But it is then followed by a fair number of messages that could be interpreted as errors. I suspect I am getting one for every SMS message it is trying to back up:
[02-02 22:41:33.827 6880:18142 D/k9] Got untagged EXISTS with value 12345 for com.zegoggles.smssync.mail.BackupStoreConfig@7a96900:SMS/AsyncTask #1/conn213609424the value 12345 incremented by one for each message, like a counter or perhaps ID.
In researching this message, it appears to be part of the K9 email client, which at first made me concerned because I don't use this email client, but I then discovered it is also a email library that SMS Backup+ is using.
Even more interesting, is I see the backed up messages in my gmail from my tests just a few minutes ago, but the "last item backed up" timestamp in SMS Backup+ still shows the date/time of last manual backup which was three days ago.
I currently have the "legacy scheduler" option enabled, along with "sync log" and "extra debug information" options enabled.
When I view the sync log within SMS Backup+, I see (paraphrased, since typing a screenshot)
02-02 22:41 Backup requested (Incoming)
02-02 22:41 Starting backup (INCOMING)
02-02 22:41 Using config: BackupConfig{......lots of stuff not going to type....}
02-02 22:45 BackupState{...lots of stuff not going to type..., exception=null, state=FINISHED_BACKUP}
02-02 22:45 Backup finished
And now when I check the last backup in SMS Backup+, it shows Feb 02, 2023 10:39:57, slightly before the log entries, which I'm not sure how that figures... but it did actually execute for the first time today automatically and it hasn't done it since November last year.
One thing I did notice is the messages that were backed up appear to have odd threading, like there is a message thread of just the messages I've sent, and not inline with the messages I've received. I see other recently threads where both sides of the conversation are present.
I don't know if any of this information will be an "aha" for any developer, but here's to hoping.
@kurahaupo commented on GitHub (Feb 16, 2023):
@samej71 thanks that's really helpful.
The threading mismatch is a known issue; the original version of Android always presented the "sender" and "recipient" in that order, but newer versions present them in random order, meaning that we need to look for the tags to see which is which.
Unfortunately I don't know if/when @jberkel is coming back, or if someone is going to fork the project and maintain it.