mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #1078] Does not Backup any MMS messages #863
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#863
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 @saymahub on GitHub (Apr 19, 2022).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/1078
Expected behaviour
Backs up MMS messages and attachments into gmail logs
Actual behaviour
Only backs up SMS message
Steps to reproduce the behaviour
As indicated in the screenshot, I selected MMS messages, attampted a backup, and found that there were no messages to backup for some reason, despite the majority of my recent texts being mms.
Please specify the following:
@kurahaupo commented on GitHub (Sep 5, 2022):
It's likely that what appear to be MMS messages are in fact RCS messages.
Does your messaging app have any way to check the "technical details" of a message to see which transfer protocol it used?
Background
RCS is a new protocol that provides the same features as MMS, but uses completely different mechanisms: instead of using telco "channels", and insanely expensive Telco-grade store-and-forward, RCS uses end-to-end IP (probably TCP), so it can negotiate features between devices.
But beyond that, there's not much information available. Last I looked (about a year ago), the Android RCS API documentation was available only to telcos - presumably under an NDA - and unusable by any open source project.
Unfortunately RCS vs MMS vs SMS is dictated on a message-by-message basis by the sender; the recipient just has to cope.