Automatically turn on/off data when downloading MMS With my Galaxy S3, my girlfriend's Galaxy S4 and her mother's Galaxy Core, we cannot download MMS automatically. We have to turn on data before doing so.
This problem is not happening with her sister's Galaxy Ace: whenever they receive a MMS, data is automatically turned on, and then off once the MMS is downloaded.

Now, this isn't a real problem most of the time (more of an annoying one), but my girlfriend's mother has a very low data plan (100mb) and often forgets to switch off data once the MMS is received, so she often maxes out her data plan.

I have tried something I found here: copy the existing APN and setting only "mms" as APN type, but it doesn't work.

My girlfriend and I are Orange (France) and her mother is Bouygues.

Thanks for your help!
Again something tasker is able to solve (and maybe one of its "free alternatives" such as llama as well – but as a Tasker user, I can better describe it for that):

Both apps can act on events, and execute tasks. So let me construct a fake-profile (use it as "guide", not literally):


Condition:

Received Text (Tasker does not differentiate between SMS and MMS here)

Task:

Mobile Data → On
Wait → 1 min (set a time frame sufficient to connect and download the MMS)

Exit-Task: (optional)

Mobile Data → Off



The Exit-Task is optional. By default, Tasker restores the "before-state" automatically.

So what would this do? Whenever a message (SMS or MMS) is received, it would turn on mobile data for a minute to download the text, and then automatically switch it off again.

As I'm not sure whether an incoming MMS would even be signaled with data off, let's have a "Plan B":


Condition:

State→Mobile Network is On

Task:

Wait → 10 min (adjust time frame to fit your needs)

Exit-Task:

Mobile Data → Off



This would be a kind of "don't forget me" timer: If your girlfriends mother turns on data to receive the MMS, and forgets to turn it off again, it would automatically be turned off after the configured time-frame. Here the exit-task is mandatory, so Tasker does not restore the "before-state".