Impossible to send or receive MMS since 3 days...
-
Hello,
End of August, I bought a second-hand Oneplus Nord N100 (after I failed to install UT on a Xiaomi...) and everything was fine until this week : she cannot receive or send MMS whereas it worked perfectly these last 15 days.
The only thing she did was to download a game app called "Tux Racer" which crashed (the app didn't work but the music of the app was still running). She said she thought that the phone also crashed.
If somebody has an idea... I don't understand why this was working and why this doesn't work anymore...
Thanks in advance,
-
@Amarurtuuq
Have you updated the device since ? You are on 20.04 ? No issue for internet with cellular data ? Also Wifi must be off + cellulardata on ( in most cases ) in order to send/receive them -
@lduboeuf
No, I haven't updated the device. It is on 20.04 OTA9.
Internet is working with cellular data.
She never uses the wifi (except to check the updates)
It is a real mystery because we exchanged a lot of pictures since August, and now she cannot send me a picture and she doesn't receive mines (they go I don't know where...).I also have UT on my smartphone (I have a Volla X23) and I never had any issues with MMS, so it is beyond my skills...
Oh, also... the device is very slow now. For example, if I click on "network", it takes some time to show the screen.
-
@Amarurtuuq I'd recommend turning Wifi off altogether. I'm one of the few that has had MMS working with Wifi on in the past, but it often doesn't work.
Another thing to try is the following Terminal command:
systemctl --user restart nuntium.serviceIn the past my MMS used to stop working without notice and I wouldn't see incoming MMS or even an error, they were just lost to the abyss. This always fixed it, where reboots would not.
-
@Amarurtuuq
I have no idea what is happening.
I would try to reset the APN config again and recreates manually if needed.
Or maybe just needed a reinstallation ? -
@wally
Thanks for your reply.The wifi is always off on her smartphone. She doesn't use it.
So, maybe I should try your terminal command. My daughter is on her boarding school at the moment, so I will try next week-end and keep you advised.
-
@lduboeuf
Well, I didn't try to reset the APN, I am scared that nothing works afterwards.I will try the terminal command proposed by Wally (I hope this won't have bad effects on SMS) and if nothing changes, maybe I will try to reset the APN.
I won't try a reinstallation, I am not expert enough of UBports (that's why I bought this second-hand smartphone with UT already installed).
If I cannot succeed in fixing the problem, well, my daughter will live without MMS (but it's a pity because this is our only way to exchange pictures during the week when she is on boarding school).
-
@Amarurtuuq
The terminal command shouldn't have any risk, it just restarts a process. It was suggested elsewhere on the forum and I used it extensively when my phone used to stop sending/receiving MMS for reasons I could never figure out.I wouldn't get too scared off by playing with the APN either, that can make all the difference, and doesn't take too long. Take screenshots of your current settings first, and you can always go back to that. It's easy enough to look up APN settings online for a given cellular carrier.
Some people have better luck with one APN setting for "Internet and MMS", others need to have a separate setting, one for MMS, one for Internet. It may vary by carrier or other things that I don't understand.Even re-installing isn't a scary experience. You download the Ubuntu Touch installer, plug your phone into the computer, and then you can install without wiping data. As long as you don't unplug your phone during the process and don't wipe data, it's pretty easy.
-
@wally said in Impossible to send or receive MMS since 3 days...:
The terminal command shouldn't have any risk, it just restarts a process. It was suggested elsewhere on the forum and I used it extensively when my phone used to stop sending/receiving MMS for reasons I could never figure out.
Interesting you've said that doing it manually is different than rebooting ( even if it is supposed to do the same ). So maybe the service is started too early, that could be a lead.
-
@wally next time it happens for you before restarting the service, could you give the output off:
journalctl --boot --identifier=nuntium --identifier=ofonod