@gpatel-fr

Yeah, I noticed that about the logs too. The phone "thinks" I sent a text, and then it "thinks" I sent another text, but in the middle the phone does "not think" that I tried sending a photo message. Which I did. There's actually three message attempts in that timeframe. The photo message send(MMS) just might as well have never happened at all. It's completely missing, my human activity is not there logged in that moment.

So the text messaging app itself probably would have sent the photo over to my carrier but it just never knew I attempted to send the photo from the OS to begin with? I don't know for now but I'm going to have to do the hard reset and wipe it all and start over. For now I need this working. I haven't gotten any text messages in over a week now and and I know how to get it working again. It just is what it is.

I need to think about how I will add this to the bug report.

It did not come to me right away, but I kinda remembered one of the terminal commands I could issue to get the log. This should have been easier and that is a problem.

journalctl -e -u ofono > /home/phablet/Documents/errorlog.txt

I created a bug report on the lomiri-messaging-app Gitlab which I am not sure is the best location for it but I only have what I have at this moment.

@gpatel-fr said in How can I troubleshoot broken SMS?:

@ezst036 said in How can I troubleshoot broken SMS?:

How can I basically clear this file?

the simplest way is to 'rm' the file (using sudo), do a 'sudo systemctl daemon-reload', and restart the ofono daemon. Extra logging will then stop. You can attach the log file here if you save it as a .txt file.

Thank you. I ran into a probably much more simple problem. What is the name of the file and where does it live? And what program on a desktop do you use to read them if not a regular text editor like Kate or Vim?

I had assumed I could find it in /var/log or even var/log/journal or if nothing else I could press CTRL+S from the terminal program that was opening and reading them and save the file as I pleased with whatever name I wanted. The files I have are not text file readable so I can't view them first, but then I wouldn't send this to anybody else either.

Most of the files in /var/log/journal appear to have GUIDs in the file names. user-1001@GUID, system@GUID, and user-2011@GUID. There's also a system.journal file here. But none are seemingly plain text readable.

Thank you for sticking with me.

@gpatel-fr

What I meant by flood was that I all of a sudden had many text messages from like 6 people all in the same one moment and I do not believe all of them sent their messages exactly at the same time.

Since my text messaging was clearly broken, these text messages were waiting around as if my phone had been shut off and I had a several days worth accumulation of new text messages I had never seen while the text messaging was broken. Restarting ofono fixed at least the text side of my text messaging.

Hello @wally,

It could be that we do have a variation of the same problem it just manifests itself in a slightly different way.

My main problems are related to MMS, picture messaging. I've only had plain-text messaging break on me once and that was when upgrading from 20.04 to 24.04.

I have seen slow downs when messages received, it doesn't happen very often though. More often though is I see slow downs when trying to open either the phone app or the text messaging app. It just stops and sits for like 10-15 seconds before it'll do anything. The phone app will say "initializing......" at the top of the screen.

@gpatel-fr

Thank you. How can I basically clear this file? (I'm gonna wipe the phone anyways, so might as well get a small/targeted "clean" log file)

What I want to do is enable the extra logging, reboot the phone, send a picture message and let it sit for like 30 seconds, and then use that log file to create a bug report on Gitlab that SMS keeps breaking over and over again.

If there was any other troubleshooting that could be done I suspect someone else would've mentioned it. So I'm going to assume this log is good enough and start there.

I appreciate you and others sticking with me.

Interesting. As soon as I restarted the daemon with 'sudo systemctl daemon-reload' and 'sudo systemctl restart ofono', a flood of plain text messages instantly came in. They're all dated for now, but they're probably from over the course of the last several days.

The last text message that my phone thinks I received was three days ago, 1/12/26. That's not all of a sudden because everybody texted me all at once this moment, especially at this time of the night.

Hopefully these logs contain some super magic.

I hadn't had a chance until now to get to this.

@gpatel-fr Thank you, I will do these things a little later today.

I'm not really too worried about disk space at this point. I feel like once I have something tangible and I can put in a bug report I'm going to try to do a full reset and wipeout anyways. Nuking it from orbit has always worked for me.

@gpatel-fr said in How can I troubleshoot broken SMS?:

@ezst036 said in How can I troubleshoot broken SMS?:

version 11.2 of the ubports-installer no longer contains the checkbox option for a clean wipe user data install.

I just checked and this is not correct; after clicking 'Install' there is in the following screen a checkbox to wipe personal data (it is not checked by default)

Oof, I can see it in your screenshot. on my screen it looks invisible. I checked on where it is and it lights up. Thank you. But still, I do not want to be in this cycle anymore. I want to try to troubleshoot this with logs or something, put in a bug ticket first.

@lduboeuf Hello, good to see you again.

I have not yet pinged the porter about this but I have seen this problem on multiple phones. I am currently now on a OP Nord but I saw the same issue on a FP4. Also saw it on a Pixel 3.

I may try the daily channel soon.

Things have gotten worse now, actually. I was on 20.04 as of Friday. I cannot receive regular text based text messages now. But I can still send messages out, if I call and ask. The text based will be received successfully.

@gpatel-fr said in How can I troubleshoot broken SMS?:

If you want to read the debug information of ofonod, it's possible to enable it but this is not a light reading.

ofonod sounds wonderful, I have been struggling with this issue on and off for quite some time and I have had exactly nothing by way of troubleshooting so far.

Where this is going is I need to create a bug report but I am not interested in just creating something on gitlab that says its broke can you fix it?

I do have wifi disabled (its grey) and cellular data is on (switch is green). I can access websites currently.(if it matters)

How can I access ofonod?

@gpatel-fr said in How can I troubleshoot broken SMS?:

I can't imagine how wiping out all user data could fix this problem.

I have always interpreted the wipe option that is in the ubports installer as a clean wipe of everything on the phone(settings, etc), not just removing what is in one or two folders. Admittedly I know much less about linux on a phone than I do on a linux desktop, have been a linux user for over a decade. Also troubleshooting desktops is a little better well documented in a lot of different places than these phones. I can only tell you what has happened. Any time I have lost the ability to send photos through text, I back up my data and phone book, do a full reinstall/wipe with ubports installer, and back to functioning properly it goes. For a while. Then I have to wipe again. But now I can't do that anymore.

My expectation currently is that I should be able to open the camera app from the side bar, take a photo of something with the phone's camera, then go to the text messaging app and send the photo to someone in my contacts list. To be clear, this functionality does work after I do a clean wipe. It just stops working intermittently and I don't know why.

@uxes said in How can I troubleshoot broken SMS?:

@ezst036 if you have issues downloading images in messages that may be issue of turned on wifi when mms is not working

Thank you. Currently receiving photos does not function either, and my wifi is disabled. If I tell someone to send me a photo, its just nothing. Nothing happens. No warning, no click here to download, nada. It's just dead silent as if nothing ever happened.

Hello,

My SMS (picture messages) has stopped working again, what happens is when I try to send a picture the spinner just never stops.

Fun times since the newest version 11.2 of the ubports-installer no longer contains the checkbox option for a clean wipe user data install. So my only option for fixing this is completely gone.

What do I do?

Its a Oneplus Nord 10 5G, with stable 24.04-1.

@mihael said in Suspention of Phone app in noble:

@kugiigi Oh, I thought this was a UT thing... Ok, thank you very much for your answer, I will report this.

Was curious, could you provide a link to the bug report? Thank you.

Thank everyone for their thoughts.

I have not changed network providers recently or done anything else which would seem to stand out. No new app installs from the store or anything.

I'll keep looking for a way to troubleshoot this and report back if it is found.

When I open up the phone app recently, now it has changed so that I have to wait like 6 seconds and there is a message at the top left that says "Initializing..."

How can I troubleshoot and fix this?

Seems to be the same whether or not I have security in place or no locking code.

I normally have no lock code. So when I turn the screen on the phone is simply ready to do things. That is probably considered a bad practice, but it is for this reason why I always have developer mode disabled.

Do you keep a lock code and then developer mode (most of the time)enabled?

When I plug my Ubports phone into my computer, I would like to see a popup on the phone screen with a yes/no in it to allow file transfers via USB, a sort of limited permissions granting. Right now in Dolphin KDE the phone does appear but the window is completely empty.

I do not want to always enable admin developer mode on the phone with maximum permissions just to grab a few photos. Is this currently possible to enable in Ubports settings somewhere?

I was just curious of someone around here had an idea of if support for displaying an attached bluetooth device's battery level was seeing some progress.

Or else, if I completely missed where I can see it then someone set me straight. Being able to see what the battery level of my headphones, or a bluetooth keyboard would be very useful.

I looked in the bluetooth panel, in the slide down battery panel from the top, and the system > battery control panel.

I'm really hoping that an APNDB update that appears to have been backported to Focal 20.04 will fix a long-standing issue I've been experiencing where after a few months, photo messaging just completely stops working.

https://gitlab.com/ubports/development/core/packaging/lineageos-apndb/-/merge_requests/2

I only have one single phone, wish I could actively contribute for RC but also, my issue usually manifests several months later and that isn't going to help an RC window that closes in 1 to 2 weeks anyways. I can't for now use my daily driver for testing.

Looking forward to more VoLTE supported phones!(FairPhone4 here) Thanks to all who have helped with this release.

@wally said in Why does picture messaging stop functioning after a few months?:

@ezst036 Sorry to hear those things haven't worked. I assume that if restarting nuntium didn't fix the problem, it's just a different issue than I was having.

I hope you're able to resolve it somehow without a full backup and re-install. I presume that in the past when this has happened to you, flashing without wiping data didn't fix the issue?

I have only found backing up and using the UBPorts installer to start fresh as a resolution.

It's working again now, wiped and now have OTA-5.

EDIT: (3/10/25):

I marked the discussion as solved, and wanted to make a few notes for reference.

I updated to OTA-8. This is important compared to other OTA-x because there was an update commit made to the apns-conf.xml in the source tree after I made some requests on Gitlab. My cell provider's APN by default was out of date. Now when I do a fresh UBports install I do not have to change the APN information, the default is correct.

Hopefully that prevents the software from getting confused between my "custom" APN setting and the "default" outdated APN contained in the source xml file. I only need the default.

I will create a new discussion or Gitlab bug request should the issue come back.

@wally said in Why does picture messaging stop functioning after a few months?:

@ezst036 Can I ask what device you're using?

I currently have a Fairphone 4. I started out with a Pixel3a though and it happened on that one once too.

I followed the steps you provided as best as I could:

change my MMS APN to something incorrect, disable MMS, restart phone, correct the MMS APN, enable MMS again, restart phone again, and then it works.

This did not work, but I could not follow the steps as typed. It seems that on 20.04 OTA4 when the phone restarts all APNs are enabled, not the disable as I left it. I thought I might get around this by shutting off all mobile data in its place within these steps, but the icon still only spins and spins.