This is a bug report for Android 5.0+

MMS either incoming or outgoing, including picture, audio, vcf, group messaging etc. does not work with AOSPs new MMS protocol.

I've tried several VPNs including:

FreedomeVPN https://play.google.com/store/apps/details?id=com.fsecure.freedome.vpn.security.privacy.android

Vypr https://play.google.com/store/apps/details?id=com.goldenfrog.vyprvpn.app

BetterNet https://play.google.com/store/apps/details?id=com.freevpnintouch

Hotspot Shield https://play.google.com/store/apps/details?id=hotspotshield.android.vpn

Disconnect https://disconnect.me/mobile/disconnect-mobile/sideload

Even VPNs that have app whitelisting cause MMS to fail.

I tried Textra as a texting replacement app (for other reasons). In the settings it has an option to use either System or Legacy protocols for MMS. It even tells the user to try System if they have a VPN enabled. I switched to System from the default Legacy, and now my MMS works flawlessly with a VPN running.

I've double checked to see if MMS still fails using other texting apps, including Google's own Messaging app, and several others, MMS still fails.

Something about the protocol differences causes MMS to fail when running a VPN. This leads to a poor UX, and defeats the purpose of running a VPN causing users to constantly have to enable and disable it just to send messages. Whether it's to connect to servers for work, or for users who just want a little extra privacy, users should be able to run VPNs and still be able to send MMS.

Side note: This issue also causes regular SMS to send and receive much slower than normal. THey all go through eventually it just takes a lot longer, up to a couple of minutes.

Issue 37074617

Links (7)

Issue metadata