MMS settings not working properly on Pro 5

Bug #1593129 reported by Tomas Öqvist
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
messaging-app (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Device: Meizu Pro 5
OS: OTA-11
SIM slot 1: SD card
SIM slot 2: Tele2 Sweden SIM

I have used slot 2 for my SIM from the beginning with my Pro 5 as I have understood the two SIM slots work identically, except that I can only have an SD card in slot 1.

After the SIM card is automatically registered with my carrier, I get the APN settings for Tele2 Norway, which are similar to the Tele2 Sweden APN settings below only with a dfferent proxy address and ".no" instead of ".se". With the Norwegian settings I can send MMS to other people, but I am not able to receive MMS from others. However, I can send and receive MMS to/from myself (maybe that is because my settings are Norwegian both sending and receiving). Changing to the Tele2 Sweden settings manually in the mobile settings, I am not able to send or receive MMS to/from anyone, instead it ends with a "Failed to send" in the messaging app. Mobile surfing works on both Swedish and Norwegian APN settings.

Default settings for MMS for Tele2 Sweden:

Username: Leave blank
Password: Leave blank
Protocols: HTTP
APN: 4G.tele2.se
Proxy address: 130.244.202.030
Port number: 8080
Home page / Message Server: http://mmsc.tele2.se

Default settings for surf

Username: Leave blank
Password: Leave blank
Protocols: HTTP
APN: 4G.tele2.se
Home: http://mobil.tele2.se

About a year back, I experienced send/receive MMS problems on my Bq Aquaris E4.5 and Nexus 4, but those got resolved with later updates. After that I haven't encountered any MMS problems with Tele2 Sweden until switching to Meizu Pro 5. I am using the same SIM card and carrier, only that it is the first time I have access to a device capable of 4G.

This is really problematic, as I cannot receive long SMS messages either (as they get converted to MMS).

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in messaging-app (Ubuntu):
status: New → Confirmed
Tomas Öqvist (tomoqv)
description: updated
Revision history for this message
Tomas Öqvist (tomoqv) wrote :

Update:
Did a reset of all the APN settings (I had them manually set to Tele2 Sweden before) and it reverted to Tele2 Norway. The standard settings are as follows:

APN: internet.tele2.no
Proxy address: 193.12.40.14
Proxyport: 8080
MMSC: http://mmsc.tele2.no

After this, the Pro 5 won't connect to mobile data at all this time! Not even following a reboot. The strange situation occurs that the top bar indicator show no connection, but pulling indicator down shows Tele2 4G (see attached image). I have also tried to change APN to 4G.tele2.no, but same problem.

Manually adding the Tele2 Sweden settings, gives me mobile data back, but still no MMS.

Revision history for this message
Anssi Leino (anssi-n) wrote :

I have the same problem with my operator (Sonera) in Finland, MMS is not working correctly on Meizu Pro 5:
To send MMS I need to disable wifi. I can't receive MMS, regardless of whether wifi is on or off. I am using the correct APN settings from my operator (Sonera), and the latest OTA-11.

Revision history for this message
Tomas Öqvist (tomoqv) wrote :

There seem to be quite a bit of "hit and miss" when it comes to mobile connectivity on the Pro 5. Did another reset of APN settings today, which reverts me to Tele2 Norway, and I am now able to send MMS again.

Revision history for this message
zzarr (rasmus-jonsson) wrote :

Hello!

I have a Meizu MX4 and it affects me too.

I can't receive MMS, I don't even get a SMS with a link as I used too.

Best Regards
/ Rasmus

Revision history for this message
Tomas Öqvist (tomoqv) wrote :

@zzarr:
Hi, which telecom operator do you have?

/Tomas

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.