mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #676] MMS not backing up correctly. Shows as SMS with unknown. #574
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#574
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 @spinncity on GitHub (Sep 6, 2016).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/676
I have an Android Samsung S5 Active. I have not had any issues with this up till now. For some reason MMS just started not backing up correctly. It backs up to my Gmail as "SMS with unknown". The messages are all MMS from multiple contacts. The contacts are in my address book yet it shows unknown. It is backing them all up together. Please tell me how to fix this
@spinncity commented on GitHub (Sep 6, 2016):
As an addition to the above, I just had a group text with two other contacts that were MMS and they backed up as SMS with the named contacts no problem. It seems inconsistent. I thought it was only doing the "unknown" thing with long text messages that convert to MMS or Text messages with photos attached, that's not the case. It seems inconsistent. Making me crazy breaking up conversations. Any assistance in fixing this issue is appreciated. Thank you.
@mdes commented on GitHub (Oct 30, 2016):
Edit: Same problem as "MMS oddities #663"
Phone: Oneplus Two
Android 6.0.1 (OxygenOS 3.1.0)
SMS Backup+ version: 1.5.10
Hi,
I have a similar problem.
⇒ In my following description:
⇒ Some emails have an object which is "SMS with " (this is wrong), and some others have "SMS with " (this is correct). The attached picture of the wrong mails is always named image000000.jpg (this should be a default temporary name when when attaching a picture to an MMS). The attached picture of the correct ones has a real name (as 20160921_1409121.jpg, IMG-201611.jpg, or photo01.jpg) which correspond to picture which is in my smartphone.
Thanks to fix it,
Michel.
@jberkel commented on GitHub (Nov 8, 2016):
@spinncity could you share some headers from the backed up emails (anonymized of course)?
@spinncity commented on GitHub (Nov 8, 2016):
I'm sorry, I'm not very well versed in this stuff. I just know when I have
a problem. If you can be more specific I will provide whatever it is you
need to assist in fixing the problem.
Melissa Gaston - Sent from my Android. Please excuse any typos - talking
my message. Thanks.
On Nov 8, 2016 8:48 AM, "Jan Berkel" notifications@github.com wrote:
@jberkel commented on GitHub (Nov 8, 2016):
@spinncity don't worry, maybe @mdes can help.
@mdes commented on GitHub (Nov 8, 2016):
Subject: SMS avec …
From: "… (+336…)" <…@gmail.com>
To: …@gmail.com
References: 8hg2rgtfkfgy3qhmj6ahnood.6820@sms-backup-plus.local
Message-ID: ae83fbbba43e95c43933902f8ebd2f25@sms-backup-plus.local
X-smssync-address: +336…
X-smssync-datatype: MMS
X-smssync-backup-time: 26 Oct 2016 11:25:25 GMT
X-smssync-version: 1554
Date: Wed, 26 Oct 2016 12:04:56 +0200
X-smssync-id: 179
X-smssync-type: 128
X-smssync-date: 1477476296
X-smssync-thread: 541
X-smssync-read: 1
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----UDNWK473HTNIPREH6Y2DT1KT6E3KW6"
Content-Transfer-Encoding: 7bit
------UDNWK473HTNIPREH6Y2DT1KT6E3KW6
Content-Type: image/jpeg; name=image000000.jpg
Content-Disposition: attachment; filename=image000000.jpg
Content-Transfer-Encoding: base64
/9j/4QAoRXhpZgAATU0AKgAAAAgAAYdpAAQAAAABAAAAGgAAAAAAAAAAAAD/4AAQSkZJRgABAQAA
…
@mdes commented on GitHub (Nov 8, 2016):
This one is good:
Subject: SMS avec …
From: "… (+336…)" <z…@gmail.com>
To: …@gmail.com
References: 8hg2rgtfkfgy3qhmj6ahnood.1106@sms-backup-plus.local
Message-ID: 44152ae798aa389c7be9b8bdf152587d@sms-backup-plus.local
X-smssync-address: +336…
X-smssync-datatype: MMS
X-smssync-backup-time: 19 Oct 2016 07:28:01 GMT
X-smssync-version: 1554
Date: Wed, 19 Oct 2016 09:24:06 +0200
X-smssync-id: 176
X-smssync-type: 132
X-smssync-date: 1476861846
X-smssync-thread: 42
X-smssync-read: 1
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----R2NOTO5AUGNAENPWWVMZTVPBXXRUFC"
Content-Transfer-Encoding: 7bit
------R2NOTO5AUGNAENPWWVMZTVPBXXRUFC
Content-Type: image/jpeg; name=IMG-201611.jpg
Content-Disposition: attachment; filename=IMG-201611.jpg
Content-Transfer-Encoding: base64
/9j/4AAQSkZJRgABAQAAAQABAAD/7QCEUGhvdG9zaG9wIDMuMAA4QklNBAQAAAAAAGgcAmcAFG94
@mdes commented on GitHub (Nov 8, 2016):
In fact, my problem is rather https://github.com/jberkel/sms-backup-plus/issues/663 because the SMS is logged as being sent to myself (and not to unknown, which is the object of this issue).