[GH-ISSUE #84] Duplicate texts on restore? #70

Closed
opened 2026-02-26 00:36:11 +03:00 by kerem · 11 comments
Owner

Originally created by @randomman on GitHub (Nov 21, 2010).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/84

When restoring messages, the app says it detects about 15 dups out of 1200 texts, and does not restore them. I can go through and find which ones were not restored. If I delete all my texts, and try to restore again, it says the same number of dups were detected, and the same exact texts do not show up.

I have a feeling that this is a problem with the Droid Incredible, as for some reason it likes to delete all my texts randomly once I start going over 1000+ texts. Do you know of any way to resolve this?

Originally created by @randomman on GitHub (Nov 21, 2010). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/84 When restoring messages, the app says it detects about 15 dups out of 1200 texts, and does not restore them. I can go through and find which ones were not restored. If I delete all my texts, and try to restore again, it says the same number of dups were detected, and the same exact texts do not show up. I have a feeling that this is a problem with the Droid Incredible, as for some reason it likes to delete all my texts randomly once I start going over 1000+ texts. Do you know of any way to resolve this?
kerem closed this issue 2026-02-26 00:36:11 +03:00
Author
Owner

@jberkel commented on GitHub (Nov 21, 2010):

there's a max thread size in android which defaults to 200. i think it will delete texts once it reaches that limit (per thread). but deleting all your texts sounds like a bug to me.

<!-- gh-comment-id:557495 --> @jberkel commented on GitHub (Nov 21, 2010): there's a max thread size in android which defaults to 200. i think it will delete texts once it reaches that limit (per thread). but deleting all your texts sounds like a bug to me.
Author
Owner

@randomman commented on GitHub (Nov 21, 2010):

If I manually delete all the texts and then restore, it seems like there are some "hidden" texts that SMS Backup+ thinks are duplicates and won't restore them.

I think MMS are currently considered dups, but not all the dups are accounted for by the number of MMS I have. There are still a few missing texts that aren't getting restored.

<!-- gh-comment-id:557604 --> @randomman commented on GitHub (Nov 21, 2010): If I manually delete all the texts and then restore, it seems like there are some "hidden" texts that SMS Backup+ thinks are duplicates and won't restore them. I think MMS are currently considered dups, but not all the dups are accounted for by the number of MMS I have. There are still a few missing texts that aren't getting restored.
Author
Owner

@jberkel commented on GitHub (Nov 21, 2010):

MMS are not restored at all, they shouldn't show up as dups.
any patterns observable in the missing texts?

<!-- gh-comment-id:557618 --> @jberkel commented on GitHub (Nov 21, 2010): MMS are not restored at all, they shouldn't show up as dups. any patterns observable in the missing texts?
Author
Owner

@randomman commented on GitHub (Nov 21, 2010):

Alright, I took an in-depth look at what's going on. Here's the math. After restore, SMS Backup+ says "Successfully restored 1149 items (13 dups)," for a total of 1162 items.

After restore, I count exactly 1149 SMSs on my phone, so that part is being counted correctly.

In my gmail account, there are 1162 total items, with 1153 SMSs and 9 MMSs. So of the 13 "dups" that SMS backup+ is counting, 9 of those are MMS "dups" (obviously not being restored because that feature isn't available yet) and 4 are SMS "dups" that aren't being restored. I looked for those 4 missing SMSs, and they were all texts sent by me. Maybe the texts are somehow being misclassified as MMS, which is why they're not being restored. (I probably shouldn't get so hung up on 4 missing texts out of 1162.)

<!-- gh-comment-id:557708 --> @randomman commented on GitHub (Nov 21, 2010): Alright, I took an in-depth look at what's going on. Here's the math. After restore, SMS Backup+ says "Successfully restored 1149 items (13 dups)," for a total of 1162 items. After restore, I count exactly 1149 SMSs on my phone, so that part is being counted correctly. In my gmail account, there are 1162 total items, with 1153 SMSs and 9 MMSs. So of the 13 "dups" that SMS backup+ is counting, 9 of those are MMS "dups" (obviously not being restored because that feature isn't available yet) and 4 are SMS "dups" that aren't being restored. I looked for those 4 missing SMSs, and they were all texts sent by me. Maybe the texts are somehow being misclassified as MMS, which is why they're not being restored. (I probably shouldn't get so hung up on 4 missing texts out of 1162.)
Author
Owner

@jberkel commented on GitHub (Nov 22, 2010):

are the 4 missing really long texts? i think sometimes these get converted to MMS automatically even if they don't contain any pictures etc.

<!-- gh-comment-id:558497 --> @jberkel commented on GitHub (Nov 22, 2010): are the 4 missing really long texts? i think sometimes these get converted to MMS automatically even if they don't contain any pictures etc.
Author
Owner

@randomman commented on GitHub (Nov 24, 2010):

Nope, they're pretty short. Is there any way to check if it is an MMS?

<!-- gh-comment-id:564290 --> @randomman commented on GitHub (Nov 24, 2010): Nope, they're pretty short. Is there any way to check if it is an MMS?
Author
Owner

@rojer commented on GitHub (Dec 21, 2010):

i'm moving my messages to another phone and have the same issue.
Only in my case it's not 13 of 1162 but 333 fake dups out of 357: "Successfully restored 24 items (333 dups)".
I can see 357 messages in the IMAP folder, and i delete all messages and reset sync state before restoring - result is the same.

<!-- gh-comment-id:626234 --> @rojer commented on GitHub (Dec 21, 2010): i'm moving my messages to another phone and have the same issue. Only in my case it's not 13 of 1162 but 333 fake dups out of 357: "Successfully restored 24 items (333 dups)". I can see 357 messages in the IMAP folder, and i delete all messages and reset sync state before restoring - result is the same.
Author
Owner

@rojer commented on GitHub (Dec 21, 2010):

actually, the result is not always the same and repeating restore without resetting sync state or deleting messages pulls in more messages, so after a few tries i think i've got most of them. but the first attempt (after reset + delete all) always pulls just a small fraction - usually 24, sometimes 32.
one interesting point: the progress bar goes bit by bit (adding 1-3 messages) until 66, then suddenly jumps to 166, then goes slowly up to 357 again. but it still pulls just 20-30 messages on the first pass.

<!-- gh-comment-id:626269 --> @rojer commented on GitHub (Dec 21, 2010): actually, the result is not always the same and repeating restore without resetting sync state or deleting messages pulls in more messages, so after a few tries i think i've got most of them. but the first attempt (after reset + delete all) always pulls just a small fraction - usually 24, sometimes 32. one interesting point: the progress bar goes bit by bit (adding 1-3 messages) until 66, then suddenly jumps to 166, then goes slowly up to 357 again. but it still pulls just 20-30 messages on the first pass.
Author
Owner

@jberkel commented on GitHub (Dec 22, 2010):

Fetch only mails we can actually restore, fix restore order

Closed by 250bc996c2
Closed by 250bc996c2

<!-- gh-comment-id:628702 --> @jberkel commented on GitHub (Dec 22, 2010): Fetch only mails we can actually restore, fix restore order Closed by 250bc996c29ab1e6356147b4bdfb0eb383487a9e Closed by 250bc996c29ab1e6356147b4bdfb0eb383487a9e
Author
Owner

@jberkel commented on GitHub (Dec 22, 2010):

please try again with the latest sms backup+. dups should now only show up if they are really dups. (previously mms would be shown as dups)

<!-- gh-comment-id:628761 --> @jberkel commented on GitHub (Dec 22, 2010): please try again with the latest sms backup+. dups should now only show up if they are really dups. (previously mms would be shown as dups)
Author
Owner

@randomman commented on GitHub (Dec 28, 2010):

Restored texts with the latest version, and the 4 missing texts are still missing, but now the app says there are only 2 dups. I did the restore twice and got the same result. It's no big deal, as I'm more concerned with the backup to gmail (which is working great!) than restoring the texts to my phone.

<!-- gh-comment-id:637744 --> @randomman commented on GitHub (Dec 28, 2010): Restored texts with the latest version, and the 4 missing texts are still missing, but now the app says there are only 2 dups. I did the restore twice and got the same result. It's no big deal, as I'm more concerned with the backup to gmail (which is working great!) than restoring the texts to my phone.
Sign in to join this conversation.
No milestone
No project
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#70
No description provided.