[GH-ISSUE #66] gets stuck on mms read receipts #61

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

Originally created by @thenestor on GitHub (Oct 29, 2010).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/66

This is not a big deal, but I want to help you because I noticed this little idiosyncrasy:

When I have MMS read receipts turned on, I think the receipts arrive and are stored as MMS messages, and SMS Backup+ can't back up those particular messages.

When I try to back up MMS messages, it gets stuck on an MMS message with a read receipt, and it won't continue past that point. It still backs up the original MMS (picture, video, etc), but it fails when it tries to back up the receipt (which is usually next in chronological order). If I delete the MMS with the read receipt, the backup finishes successfully.

To fix this problem, I turned off MMS read receipts in my messaging settings, deleted the existing MMS messages with read receipts, and then sent some new MMS messages. After that, the next backup completed successfully.

I think the permanent solution is to skip MMS read receipts when backing up the MMS messages. However, if no one else is having this problem, then I'm perfectly happy just leaving MMS read receipts off because then the MMS backup works as expected.

Thank you again for your hard work on this application!

Originally created by @thenestor on GitHub (Oct 29, 2010). Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/66 This is not a big deal, but I want to help you because I noticed this little idiosyncrasy: When I have MMS read receipts turned on, I think the receipts arrive and are stored as MMS messages, and SMS Backup+ can't back up those particular messages. When I try to back up MMS messages, it gets stuck on an MMS message with a read receipt, and it won't continue past that point. It still backs up the original MMS (picture, video, etc), but it fails when it tries to back up the receipt (which is usually next in chronological order). If I delete the MMS with the read receipt, the backup finishes successfully. To fix this problem, I turned off MMS read receipts in my messaging settings, deleted the existing MMS messages with read receipts, and then sent some new MMS messages. After that, the next backup completed successfully. I think the permanent solution is to skip MMS read receipts when backing up the MMS messages. However, if no one else is having this problem, then I'm perfectly happy just leaving MMS read receipts off because then the MMS backup works as expected. Thank you again for your hard work on this application!
kerem closed this issue 2026-02-26 00:36:09 +03:00
Author
Owner

@bjdodson commented on GitHub (Oct 29, 2010):

Cool, thanks for the note. The MMS datastructure isn't terribly well documented, as far as I can tell, and I don't know much about the read receipts. They are separate mms messages? So the ideal solution would be to detect them and skip them?

Are you able to get any log messages when the app hangs?

Thanks,
Ben

<!-- gh-comment-id:503017 --> @bjdodson commented on GitHub (Oct 29, 2010): Cool, thanks for the note. The MMS datastructure isn't terribly well documented, as far as I can tell, and I don't know much about the read receipts. They are separate mms messages? So the ideal solution would be to detect them and skip them? Are you able to get any log messages when the app hangs? Thanks, Ben
Author
Owner

@thenestor commented on GitHub (Oct 29, 2010):

I'll try to check the log, but also I can try looking in the MMS database to see what the read receipts look like. I'll get back to you later tonight with more data.

<!-- gh-comment-id:503026 --> @thenestor commented on GitHub (Oct 29, 2010): I'll try to check the log, but also I can try looking in the MMS database to see what the read receipts look like. I'll get back to you later tonight with more data.
Author
Owner

@thenestor commented on GitHub (Oct 29, 2010):

Right now I'm looking at the /data/data/com.android.providers.telephony/databases/mmssms.db, and in the table "pdu" I can see that the read receipts have "m_type" = 134, and most of the other fields are empty.

<!-- gh-comment-id:503091 --> @thenestor commented on GitHub (Oct 29, 2010): Right now I'm looking at the /data/data/com.android.providers.telephony/databases/mmssms.db, and in the table "pdu" I can see that the read receipts have "m_type" = 134, and most of the other fields are empty.
Author
Owner

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

@thenestor: could you have a look at the sms table and see what value the "type" column has ? (for receipts)

<!-- gh-comment-id:515981 --> @jberkel commented on GitHub (Nov 3, 2010): @thenestor: could you have a look at the sms table and see what value the "type" column has ? (for receipts)
Author
Owner

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

Don't include receipts in backup

Closed by 95980fb7a4

<!-- gh-comment-id:517227 --> @jberkel commented on GitHub (Nov 4, 2010): Don't include receipts in backup Closed by 95980fb7a43d57e88bae7fdb8d95acb97e0cea7f
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#61
No description provided.