mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #868] RESTORE ISSUEs - Please Help - only restores 2 sms out of thousands - Then only 4 year old sms #687
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#687
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 @TheMattD on GitHub (Apr 5, 2018).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/868
Hey guys,
I have used the restore from SMS Backup+ before with success but it takes 2-5 days for large amounts (thousands) of sms.. but it did work in the past for me on my phone. Although I am now doing a restore for my dad's phone but am having a problem..
I'm now having an issue restoring where it's only finding 2 messages instead of the thousands which are on the gmail account..
I looked through some old threads but am not finding my same situation or a solution so far.
Any ideas would be appreciated, thanks in advance.
Before you report your issue, please search the issues page to see if it has already been reported. Also, if you'd like, you can try out the beta version.
Expected behavior
Restore messages from previous backups...
Actual behavior
Only finding 2 messages to restore, but I have thousands of sms in gmail..
Steps to reproduce the behavior
I just took the normal steps to restore my sms as usual, open the app, made sure my gmail account is connected, click "restore" and follow the normal prompts. Shortly there after it shows only 2 messages were restored..?
Please specify the following:
Android version
6.0.1
Phone model / brand
Samsung Galaxy S5 from Verizon (SM-G900V)
SMS Backup+ version installed
1.5.10
Messaging app
Message+ (Verizon's app)
@TheMattD commented on GitHub (Apr 5, 2018):
**UPDATE----
I just installed the BETA version 1.5.11 and now it appears to be running as it should and restoring the thousands of SMS it normally would.
Won't know till it's done but it appears to be fixed in the beta version. I'll update later when I know more.
Hope this helps others if they come across the same issue.
@TheMattD commented on GitHub (Apr 6, 2018):
BAD UPDATE
I thought the RESTORE was going well but it now appears it did not. It ran for a couple hours but stopped and said it was canceled.
While running it showed 48890 SMS were being restored but stopped itself around 32000. I then checked what restored and mainly found messages from 2014 and no where near 32000.
To make matters worse it seems they are nearly all duplicates.
I can do another factory reset and try again if need be but I'd sure like to be sure it's going to work somehow. OR is there a way to salvage whatever I have going on?
I'd also like to know if there is a way to delete duplicates?
PLEASE, ANY suggestions / solutions would be great. Dad's already been without his phone 2 days so sooner the better obviously.
@jberkel commented on GitHub (Apr 9, 2018):
Restoring many thousand SMS doesn't work so well. Maybe limit the number to the most recent 500? (see #586)
Otherwise see https://github.com/jberkel/sms-backup-plus/#im-not-able-to-restore-all-of-my-insert-huge-number-messages
@TheMattD commented on GitHub (Apr 9, 2018):
GOOD / WEIRD UPDATE..
I tried the restore again but this time selected to restore ONLY SMS, and unchecked the call log restore box. Instead of detecting 48000+ items to restore, this time it found about 47300 SMS and ended up restoring I think all of them.
1 other thing I did this time that may or may not have helped, I kept the screen on by swiping it from bottom to top every few minutes, don't know if that did anything but in the end it worked this time so I would think there is a possibility that if I didn't do that then MAYBE a few minutes after the screen turns off it would have stopped the process maybe?? It seemed to before...
DUPLICATES: This part I really can't explain but apparently the duplicates fixed themselves... No clue how but after this second restore I haven't seen any.. Weird I know..
Hope this helps someone in need as I was.
@jberkel commented on GitHub (Apr 10, 2018):
@TheMattD thanks for the feedback. the app holds a wakelock during the restore so normally keeping the screen on should not be necessary. but i think some versions of android are quite aggressive about saving battery and will deactivate the network when the screen is turned off. at least that's my guess.
@jcrben commented on GitHub (Apr 14, 2018):
@TheMattD if this is resolved, please close it?
Seems like we should investigate the issue of this working when the call log restore box is unchecked or the screen is kept on tho
@TheMattD commented on GitHub (Apr 14, 2018):
Sorry guys, I noted the versions in my original post but since had to upgrade to the Beta version which ended up getting the restore to kick in and work.
The original version I had trouble with only letting me restore 2 sms was 1.5.10
The BETA version I used was 1.5.11-beta17
Couple things to add are:
PROPS to you guys for the APP THEME feature, I wish Android themselves would allow us to do this!! I STILL miss the darker screens from 4.4 Kit Kat that were awesome at saving battery life. No clue why they'd change it..
Also, I know thousands of messages can cause issues but I have done it many times on other versions in the past so it does work most of the time.. It did end up working in this Beta version too.
Thanks for the replies
@jcrben commented on GitHub (Apr 14, 2018):
:thumb