Messaging app making artifacts??

Chester

Hello everybody,

I'm currently using a OnePlus 5 since a few years, first with UBports 16.04 and recently with 20.04 but I'm getting errors with the messaging app. At the beginning, everything was fine. But after months of use, I started to receive "mixed" messages from friends. Let's call them "fails".
These fails are made with the beginning of the new message received, and with the end of an old one, from the same person...!? Sometimes fails are really funny!!
When I updated my OP5 with 20.04, the problem has gone for a few weeks but now, it comes again!!
Did someone observe the same fails?? Maybe it comes from the hardware or from some memory cache of the messaging app. Is there a way to erase it?
Note that these fails are only coming from a friend which is also using UBports on her phone. She never had such fails coming from me. They are "one way only".

Thanks for reading and for your help and advices

danfro

You (both of you) could try to clear the app cache. This is located under your home folder.

In filemanager unlock to view hidden files, then head to ~/.cache/messaging-app and delete that whole folder.
In Terminal run rm -f ~/.cache/messaging-app. Not sure if that would require being done with sudo. You will need to try that out.

If that does not help, you could clear all configs and data from messaging app.
Of course back those folders up before deleting them. Or try simply renaming.
Those are located under ~/.config/messaging-app and ~/.local/share/messaging-app.

Chester

Hello Danfro,

Thanks for your tricks. I deleted the cache folder from messaging app. Let's check if it helps. I'll tell you. My friend will do the same on her mobile to increase our chances of success.

Beside this bug, i've got another one concerning the messaging app: From time to time, my phone is unable to send/receive mms...!? This bug comes and goes... I tried different settings (rebooting the phone, resetting servers parameters for both internet and mms, keeping mms server but no internet, 3G only, 3G/4G, etc...) nothing is working. Any idea??

danfro

@Chester I am afraid with mms I can't help. That has never worked for me and here mms are going to be fully shut down. Some providers already did, others will follow.

Chester

After a few days of use, no fails anymore. It seems that clearing the cache of the messaging app helps a lot!!
Thank you Danfro for your trick!!

This topic is solved!!

Lakotaubp

@Chester Just marked this solved. https://forums.ubports.com/topic/6311/how-to-ask-a-question-and-then-mark-it-as-solved/7 for future reference

danfro

@Chester Glad it worked and I could be of help. Thanks for reporting back.

Chester

Concerning the mms bug, I just updated my phone from 20.04 OTA2 to OTA3 this morning and I'm able again to send/receive mms. But until when...!?

@Lakotaubp : Thanks for showing me how to mark a topic as solved.

wally

Hi Chester,
Sorry for the late response. I believe I have the same MMS bug as you. Oneplus 5T, still running 16.04 (daily driver, can't afford glitches). I've never been able to figure out what causes MMS to stop sending/receiving. I get no notification that I've been sent anything when it stops working, so it's hard to know that anything's wrong.
But once I know, to get it to work again, I go to terminal and type:
initctl --user restart nuntium
Works every time. For me I'm able to test whether it's working or not by sending a photo to myself. If only I could know when it stops working, I wouldn't occasionally miss messages entirely.

My experience is that if my MMS isn't working when somebody sends me one, it will arrive exactly one hour later if I've corrected it by then, or exactly twelve hours later, or exactly twenty four hours later. But if I didn't realize and haven't corrected the problem by 24 hours later I'll never see that message or know that it was sent.

Anyhow, people have worked hard to get MMS working as well as it does, and I'm truly grateful. Don't like to sound complainy.

If yours starts being glitchy again, I hope the restart nuntium can help.