MMS Backup - Wrong Recipient

[jasonwdo]

Hi,

I installed SMS Backup+ on my new Nexus 5 with Android 4.4. I don't know if the issue is because of the new OS, the device, Hangouts or that I've set it up incorrectly.

The problem I'm finding is that after a picture MMS msg that I've sent is backed up, the gmail msg puts it in a thread where the sender is myself (correct), but the recipient is "+15556667777 [email protected]" (incorrect). The person I've texted is my wife and she exists in my contacts, but instead of her name and number, there is no name and the phone number (15556667777) is my own. The email address attached is exactly what is shown above ([email protected]). It is correctly labelled as "SMS".

I've used this app before on my old Samsung Galaxy S and it worked perfectly fine. The MMS msgs would have the correct recipients and be in the same thread as the regular SMS msgs with the same person.

For MMS msgs I receive, they are backed up properly with the correct sender and recipient, plus exist in the proper threads with the other SMS msgs. Both sent and received SMS msgs are backed up properly.

Is there a setting I missed or is this a bug?

Any help would be appreciated.

Thanks, Jason

[ghost]

I also have this issue on my Nexus 5. Did not exist (i.e. MMS backups worked correctly) on my Nexus 4.

[ghost]

I paste a log below for which the MMS was backed up with wrong recipient as described in this issue.

12-01 08:12 Backup requested (manual) 12-01 08:12 Starting backup (MANUAL) 12-01 08:12 Backing up (6 SMS, 1 MMS, 0 call log) 12-01 08:12 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://xoauth2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=0, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS]} 12-01 08:12 Backing up (6 SMS, 1 MMS, 0 call log) 12-01 08:12 Using config: BackupConfig{imap=BackupImapStore{uri=imap+ssl+://xoauth2:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@imap.gmail.com:993}, skip=false, currentTry=1, maxItemsPerSync=-1, groupToBackup=ContactGroup{_id=-1, type=EVERYBODY}, backupType=MANUAL, debug=true, typesToBackup=[SMS, MMS]} 12-01 08:12 Backup finished

[ghost]

Since posting, I have changed in from using Hangouts for SMS to Textra, only bwcause in Hangouts I got tired of accidentally sending a Hangout (which is probably what Google wants to happen). Correct recipient now seems to work. It definitely did not work at first with Textra. My current version of SMS Backup+ is from 12/8/13, Textra is from 12/20/13, and I had a wrong recipient MMS on 12/20/13. First correct one on 12/23/13. My guess is that the 12/20/13 Textra bug fixes fixed this. Don't know if it would with Hangouts, I don't want to test at this time.

[davidc1857]

I'm currently having this same problem. Any MMS message I send is not going into the thread of the person I'm sending it to. Instead, it shows the subject as my name (by name), to <[email protected]), and from me. All regular messages show like they should.

I changed my settings to do a detailed log. After I do some more texting I can send it.

I'm using a Samsung Galaxy Proclaim (SCH-S720C), running 2.3.6 on Straight Talks network.

I will be upgrading to a Galaxy S3 next week. Maybe that will make it better too.

[dg4u]

I'm having the same problem. Nexus 5, Lollipop, using Hangouts as default SMS client.

SMS messages get backed up correctly to gmail, with my email address as the sender and my recipients name and/or phone number shown as "sent to", but MMS messages incorrectly show my email address as the recipient and "[email protected]" as the sender.

[dg4u]

Today I installed the 1.5.10 update to SMS Backup Plus. The Nexus 5 MMS addressing error still exits. SMS messages back up correctly (showing both the from and to information), but MMS messages do not show "me" as the sender or the name of the recipient, instead it uses my phone number in both fields.

Needless to say, this breaks conversations and makes it nearly impossible to determine to whom an MMS message was sent.

[dg4u]

Here is the gist of my syc log: https://gist.github.com/dg4u/62e734cfe79eb6db33e1

[jberkel]

I don't have an Android (phone) right now; the emulator does not support MMS messages so unfortunately somebody else needs to look at this.

[dg4u]

MMS backup is working, and always has for me. The problem I was reporting, and which this thread was about from the start, is that MMS messages I send do not show the recipient's name and phone number, like SMS messages do, but instead they show my own name, email address, and phone number. They show up in gmail as if I sent them to myself rather than to the actual recipient.

Additionally, the messaging app which I use on my Google Nexus 5 phone is Hangouts, and for some time now it automatically splits the text part of MMS messages off and sends that separately from any images as an SMS message. This pretty much solved my problem because the SMS backup headers in gmail are correct and I delete the MMS photo attachments anyway (because they take up too much space and my phone automatically makes backup copies of photos anyway.)

[jcrben]

seems like https://github.com/jberkel/sms-backup-plus/issues/390#issuecomment-135928764 did use 15.10 so I'm reluctant to close it

As far as @dg4u's comment:

The problem I was reporting, and which this thread was about from the start, is that MMS messages I send do not show the recipient's name and phone number, like SMS messages do, but instead they show my own name, email address, and phone number. They show up in gmail as if I sent them to myself rather than to the actual recipient

I'm looking at my backup with an image and I see this in one place:

Both my messages and the receiver messages show that they are sent by the receiver. It's kind of the reverse problem (or what @davidc1857 reported). But in general this hasn't happened (both before and after this string of messages), and I wonder if this was from when I fell back to using my Samsung S5 or something.

@jberkel I'm guessing you picked up an Android by now?

[gpion]

Add me to the list of the victims of this old issue. recipient is OK for SMSs, MMSs are stored with my own address/phone number

[goldeneye89]

I am also seeing this problem: MMSs which are being attributed to me when they were actually sent by someone else in the chat thread. What is interesting is that this only happens for MMS's from two members in the chat group. All other MMS's are properly attributed to the right sender.

[goldeneye89]

Here's a gist which might provide more info on the bug: https://gist.github.com/goldeneye89/89d69daa60877b85671e924ab0e54fa2

[goldeneye89]

here's a gist with more info on the bug: https://gist.github.com/goldeneye89/89d69daa60877b85671e924ab0e54fa2

[kurahaupo]

@goldeneye89 I note that in all the messages where SMS Backup+ attributes you as the sender, your phone number appears first in the list of addresses; it also appears a second time (actually, last) in the two messages where you are wrongly attributed.

@jberkel in light of aforegoing observations, it appears that the method MmsDetails.getRecipientAddress():

1. should be named getSenderAddress(), and
2. rather than simply picking the first element of addresses, getDetails should pick out the sender from the cursor when addresses.getInt(addresses.getColumnIndex("type")) == 137, saving it in string MmsDetails.sender, and removing bool MmsDetails.incoming as it's no longer needed.

Changes would be around line 97 in MmsSupport.java.

It would also be nice to replace the various "magic literals" with their respective API constants, but I lack sufficient knowledge of the API to do this.