MMS is only received from "unknown sender"

[Patrick Poulin]

When I receive a MMS, the message is received and put under "Unknown sender" in the app.

Expected behaviour would be either to show the contact name or telefon number of the sender.

Might add that I am using SIM2 only, due to hardware fail in my SIM1 tray.

Device: BQ E5
Build number: 229 - but have had this issue since release of the phone.

[Pat McGowan (pat-mcgowan)]

@patrick can you confirm this is not bug #1532899, from the description it seems you do get the message just not the sender's proper identify from the contacts

[Pat McGowan (pat-mcgowan)]

Also is this for all MMS messages, group chats and messages with attachments?
Normal SMS texts are always shown correctly even from the same sender?

[Patrick Poulin (pcpnielsen)]

@pat. I see some similarities to your bug #1532899 in regards to the notification and listing under "Unknown Number". The main difference is that I do receive the message and picture just fine. Just without the sender ID or contact name.

All content is received, and is for all MMS' - Picture, sound and text. I have not been part of a group chat, hence this have not been tested.

SMS behavior is as expected and is listed correctly with either senders ID or contact name.

[Patrick Poulin (pcpnielsen)]

@pat - I tested the group chat yesterday, and I got the responds from "unknown sender" ID.

[Pat McGowan (pat-mcgowan)]

Did this happen before your SIM1 failed?
Can you check that the cellular settings are all correctly selecting SIM2
What carrier are you on?

[Pat McGowan (pat-mcgowan)]

@tiagosh any ideas?

[Patrick Poulin (pcpnielsen)]

Sorry for late reply, as I have not used the E5 for quite some time. I have just switched carrier and now tested MMS and are now receiving MMS' with correct sender ID.

Problem solved :) Thanks Pat

[Teja Cetinski (teja)]

I had this problem as well after the last update. After restarting the phone MMS seems to be working as expected, i.e. messages have the sender specified and are included in the correct thread.

[Pat McGowan (pat-mcgowan)]

closing this per the reporter but note bug #1532899 is active