mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #1031] Not backing up incoming SMS messages #824
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#824
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 @dto-r on GitHub (Sep 1, 2020).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1031
Apologies if this isn't the right location to post this q, recently downloaded and used the work around. Its working as should to some degree, but only incoming messages containing an attachment are logged. All outgoing messages are there, but many text threads only have one half of the conversation. Both SMS and MMS backup are checked.
9 (9.0.11)
OnePlus 5
1.5.11
built in
@kurahaupo commented on GitHub (Sep 28, 2020):
Hi @dto-r
Yes this is the right place, though responses may be a bit slow.
There are a few possible causes that come to mind:
I suspect case (1) as the most likely case, as it appears that MMS are backing up correctly (anything with an attachment must be a MMS rather than an SMS).
Can you do a Gmail search for the missing messages, and see if they're being filed somewhere else?
If you don't find them, then can you please enable the debug log, and (after running for a day or two) upload it as an attachment to this issue?
If it was case (2) then messages would eventually turn up.
We've never seen case (3), as every client I've seen replies using the same mechanism as was used to receive the message, but it's possible in theory, and Android does not yet offer an API for third-party apps to access RCS or AM messages.
@damien-pous commented on GitHub (Nov 6, 2020):
Hi, same problem for me, many incoming messages are not backed up.
(outgoing messages are, incoming MMS are, but for incoming SMS, it looks like random: messages from the same contact and only a few minutes away are or are not backed up -- most are not).
I looked for the missing messages using gmail search tools without success.
I tried to enable the debug log but the setting is disabled (greyed) on my phone.
(willing to provide more feedback if instructions are provided...)
Android 7.0, SMS Backup+ 1.5.11
@justjoe2276 commented on GitHub (Jan 7, 2021):
I installed on an S8 edge, used the gmail workaround, sent a 'test' msg and viola! It worked. Checked again a couple days later and the only msg backed up was the first 'test' msg I had sent.
I only have incoming msg set to backup, I never did the initial full backup(didn't need those) so why would it only have worked for the first 'test' and then not again?
@kurahaupo commented on GitHub (Feb 8, 2021):
@justjoe2276 was the clock on your device correct when you did the initial test, and is it correct now?
If the recorded "timestamp of last backup" winds up being ahead of the current time on the device, that will block automatic backups from occurring. Does a manual backup work?
Some other tests that might prove informative (even if they don't fix the problem):
SMS Backup+to a different Google accountSMS Backup+SMS Backup+SMS Backup+to that accountSMS Backup+.