mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #80] Not working with undownloaded MMS #67
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#67
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 @endolith on GitHub (Nov 12, 2010).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/80
Whenever my friend sends me a MMS message, it shows up as 3 separate messages. The first downloads as expected, and the other two won't download, and eventually expire and are deleted.
While they are in the limbo of not being downloaded and not being expired, it seems SMS Backup+ can't backup anything else? Or at least not anything else after that date, from any sender.
To clarify, it says that "there is nothing to back up", but any messages after this date are not in my SMS label.
When the weird extra messages expired today and were deleted, it finally backed up the subsequent messages from other people.
@jberkel commented on GitHub (Nov 12, 2010):
maybe some some sort of read receipts? they should get filtered out though.
really hard for me to debug this since i don't use MMS.
you could check the sqlite db and see what kind of messages are in there.
@endolith commented on GitHub (Nov 13, 2010):
Ok, I copied out the db, before and after downloading a text, and installed Sqlite Manager, but I'm clueless as to how to interpret this. I've found the text strings from SMS, but the MMS don't seem to be included?
@jberkel commented on GitHub (Nov 13, 2010):
you need to look at the pdu table:
https://skitch.com/jberkel/ryg1f/sqlite-manager-users-jan-projects-sms-backup-plus-mmssms.db
i think 128 / 132 are the normal m_type values (sent / received)
@endolith commented on GitHub (Nov 13, 2010):
Ok, before downloading (when there were three messages each with download buttons) I see 2 with mtype 132 and 3 with mtype 130.
After downloading, one of the messages disappeared? and the other two became images, both the same image. Now the pdu table has 4 with mtype 132.
When other people sent MMS, I would likewise get three messages in a row with download buttons, but when i click the first one, it downloads the image. the other two can't download and eventually expire. so maybe it depends on the carrier sending them to me? I'm on T-Mobile Pay As You Go, so that might affect how I receive them, too?
@jberkel commented on GitHub (Nov 13, 2010):
ah so mtype == 130 is a placeholder message with a download button, which will download the attachment and then delete itself after it's done.
it's probably for pay as you go, because users with a dataplan don't necessarily need the confirmation.
i still don't see why having those messages in your inbox would prevent it from backing up any other message which arrive later?
@jberkel commented on GitHub (Nov 13, 2010):
i've rewritten some of the backup code - could you try this version please:
https://github.com/jberkel/sms-backup-plus/sms-backup-plus-v1.2.1-pre.apk/qr_code
@jberkel commented on GitHub (Nov 21, 2010):
@endolith: is it working with the version above?
@endolith commented on GitHub (Dec 1, 2010):
Sorry, I haven't had time to test this. Do you still need me to?
@jberkel commented on GitHub (Dec 1, 2010):
no, but let me know if you still experience problems with the latest release
@endolith commented on GitHub (Dec 2, 2010):
It does work correctly with the latest release and pending undownloaded messages.
@jberkel commented on GitHub (Dec 2, 2010):
glad to hear that :)