@libremax Wow, nice! Thanks to whoever did the work and thanks for letting me know!

@pparent Thanks for posting that article, I hadn't heard.

Low probability of success can be offset by low cost and high value of success.
I think the moment we're in presents opportunity like never before. In addition to the French government looking at digital sovereignty, the Danish government is trying to get away from American tech companies. I could imagine many other governments may be considering this.

We don't have the interoperability rules here in Canada, but I'm still going to be suggesting to my member of parliament and a couple of ministers that the government should be proactive in examining and acting on the threat posed by the fact that most members of our government, military, and general populace use privacy-intrusive smartphone OSes controlled by a couple USA-based tech companies whose CEOs have already demonstrated a willingness to comply with what increasingly demonstrates itself to be an aggressive and authoritarian government.
(I respect the forum's rules about not getting political and hope this didn't cross any lines, but I think what I said is factual and relevant to the point I'm making. I'm not taking a position here on whether annexation is cool, just trying to explain why I think there's an opportunity for UT.)

Matrix has benefited from being adopted by various governments and militaries, even if in pilot projects. The challenge is much greater with mobile OS adoption, but if the resources and the need are there, it doesn't seem impossible.
My government, for example, is suddenly trying to spend vastly more than ever before on the military and routinely falls short of its spending targets. I could make the argument that a secure, private and functional mobile OS is of strategic military importance
And I will! Opportunities like this don't always last very long.

@ChromiumOS-Guy Thanks for the response. Didn't realize the website had a repo, but I very much don't understand the world of repos yet. Sloooowly learning things
Glad the issue is raised. Don't want to badger the website team, they do plenty!

A number of times people have posted along the lines of "Why is VoLTE listed as unsupported?" While it's important not to overpromise, at this point I think the claim that "VoLTE is not suppoted" isn't informing people properly.

I'd suggest

• a rewording of the Global Issue along the lines of "VoLTE remains in the (experimental? beta?) stage, and functionality cannot be guaranteed"
• the addition of a new category under Cellular, "VoLTE", which at present could be listed as "Partia" for any devices with VoLTE abilities and "Not Working" for the rest.
  -perhaps also considering 5G at the same time?

Maybe if people think this change is a good idea we could help the website folks with wording and with which devices should be listed as Partial.
Open to thoughts. Many thanks to the website team for considering this, and for the excellent website!

@oldbutndy Yeah, this topic has been raised a few times on the forum. To me, it does seem like at this point the website's Devices page may be out of date on this issue.

I've made a post in the Design section of the forum, where I've seen the Website team post before.

@DJac Yep! If you want, you could scroll to top, click the gear icon near the blue reply button, Mark as a Question, then Mark as Solved. Helps with forum tidiness.

@UBportsNews What is meant by "Supportive Member" as opposed to "Free Member" when signing up to help with Writing, Testing, etc?
Is signing up under the Get Involved section of the website still a good way to go about joining these teams? It hasn't worked the past couple times I've tried.

Thanks for keeping us informed and entertained!

Pure Maps, " Slim and " Unconfined are all available in the OpenStore as viewed from 20.04 again.
Thanks Jonatan!

@DJac Version 3.1.0 was for Xenial, 16.04. You need to use a newer version for Focal, 20.04. I'd uninstall the other one first if I were you.

I did mention this for you on the Matrix channel I mentioned above and Jonatan was unaware that it had disappeared, so perhaps it'll reappear in the OpenStore for those on 20.04 soon.

@HarryBass Hmm. I don't have any great answers, but a couple ideas.
First, please state what version of UT you're using (20.04 OTA__ / 24.04___), it could help others assist you.

This thread is mostly about MMS issues, but at one point the user describes losing SMS messages as well. After a few days of SMS not working, it seems that the Terminal command sudo systemctl restart ofono caused a bunch of undelivered messages to come streaming in.
The poster has not described whether they rebooted during the time that SMS wasn't working, but I'd suspect that one would've tried that at some point, and that for some reason the restart ofono command did something that a reboot did not.

Receiving SMS half the time seems different, but I thought I'd provide what I could.
I have what seems to be unique issues with my OP N10, which also involves undelivered SMS, but if a flickering screen upon shutdown/reboot happens to you, let me know.

@DJac There you go, you should be able to install from Bolly's link. You'll want one of the arm64 builds.
Still not clear exactly why it's not visible in the Openstore from a 20.04 device. Did you contact anyone?

@garsbenjoe Please note that this thread has been inactive for 4 years before one recent comment. Also, I think vertical scrolling doesn't work well in desktop mode across the board, not just in Morph, and is a known issue.
Thanks for your input though!

@gpatel-fr Thank you for the explanation. Slowly, very slowly, I learn more about the technical end of things.
If indeed it was SMS that came flooding in after ofono was restarted, it makes me wonder if they had tried rebooting the phone prior to that, during the three days that they were unable to receive SMS.

@gpatel-fr Ah, I understand your interpretation, but I think the flood of "plain text messages" to which they're referring is not logs, but a bunch of undelivered SMS which suddenly were all delivered at once after the daemon and ofono restarted.
They go on to talk about the dating of the messages and reference "text messages", which generally means SMS.
I think they're saying that the SMS timestamps were all from right then, when the SMS were delivered, which is how UT lists timestamps in Messages (although under Notifications one can see the time at which an SMS was actually sent).

@ezst036 Can you clarify whether by flood of plain text messages you mean logs or SMS?

@gpatel-fr Thanks for the help! I don't have the MMS issue anymore, so can't provide logs. There's history of this in the forum, going back to when it was an initctl command under 16.04. In another thread Lionel theorized that perhaps nuntium was being started too early in the boot process, but again nobody provided logs. I tried to recreate the issue on a broken old phone just for the logs, but failed.

Thanks for the clarification on the other commands. The reason I was hopeful it might fix my situation was having read:
@ezst036 said in How can I troubleshoot broken SMS?:

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.

I really appreciate people looking for the root of an issue like you are, and recognize that even if the restart-nuntium command works, it's a quick fix that doesn't help anyone solve any underlying bugs unless logs can be provided.

@DJac Hmm, yes, I can't find it either from 20.04.
Maybe if you're smarter than me at using git you'll find a way to install it from here: https://github.com/rinigus/pure-maps
Or contact somebody? https://matrix.to/#/#pure-maps:matrix.org

@ezst036 MMS always mostly worked for me though, and then both MMS and SMS stopped at once. Plus the other strange stuff with the flickering. I think my weirdo problem is separate.
I do recommend trying systemctl --user restart nuntium though, just in case. It's quick to try at least. I don't really understand why that would fix things when a reboot doesn't, but it always did for me when I'd see no sign of an incoming MMS, and it has worked for others on the forum too.

@gpatel-fr Thanks for the reply, but I meant the daemon-reload and restart ofono commands that ezst036 mentioned.

@ezst036 Hmm. I thought we might have the same problem - I'm also using Oneplus N10, and lost SMS receipt, but not sending, upon upgrading to 20.04 OTA 11.

I was excited to try the two terminal commands you referenced, but still can' receive SMS, so maybe we have different problems? Did yours stop working after upgrading to OTA-11? Do you ever get a strange glitch where upon receipt of a notification, the phone freezes and the phone screen starts rapidly flashing, and won't power off? If not I'll go back to assuming my problem is unique and my particular OP N10 is just cursed

(Also, I always have had the odd MMS that just wasn't received, though mostly they work for me.. often the right APN setting is the trick if they aren't working at all, maybe two different APNs, one for Internet, one for MMS. Sometimes MMS used to break in a way that a reboot didn't fix, but systemctl --user restart nuntium would. But I'm pretty confident MMS issues are totally separate from SMS issues.)

@oldbutndy If you mean that it turns WiFi on/off depending on your location, then no. If WiFi is on it'll connect automatically to known networks and, when connected, prefer that over cellular. But nothing I know of to trigger WiFi specifically based on location.

Really cool! I think this will be a very welcome app.
The security concerns do seem significant, but perhaps it can improve over time.
Thank you for your work on this!!