@fair I know that, as per your other thread on this topic, you just don't like gestures. But if you don't manage to make buttons, or even just until you do, you could consider trying the UT Tweak Tool, and playing with the settings under Edge Sensitivity.
Changing the edge barrier width can make a big difference.

I wouldn't personally want these options, but perhaps others would, and will speak up here.
I suspect that if others wanted it too, if you got it all working, and if it were totally stable, it's possible it could be introduced as a system option down the road. But it wouldn't happen quickly.

As an example, I understand that the wonderful manual screen rotation tool from Ambot Installer / Lomiri Plus got introduced as part of the OS in 24.04.

@pparent This is, of course, incredible news!
I'm surprised you don't already have a lot of folks jumping up to test. I don't have Signal but will try to get it in order to test, maybe not til next week though. I had mixed luck in the past trying to set up an account on an Android emulator.

I doubt there's anything that a non-dev can do to be particularly helpful, but if any tasks are THAT tedious, don't hesitate to send me a message.

@pparent Some of us old-fashioned (and long-winded) folks LIKE to be able to press <Enter> without sending the message
But however it worked in the end, I sure wouldn't complain!

Congrats on what sounds like an amazing start on this!

@CiberSheep Thank youuuuuuu!!

@pparent Very cool! So good to have more than one option (and also good to know about Sturm on Noble not working yet)
Thank you for your work!

@Vlad-Nirky Note that this is the thread for last weekend's Q&A. There's now one open for Q&A 176

@O.o. Agreed, I've always been amazed at how nicely UT works.
If you do make progress on a charge limiter, one way or another, I'm sure others will be interested to hear!

@O.o. There's an app in the Openstore called Upower Indicator Fork which I think can halt chargimg on some devices. Otherwise you'll atleast get a notification at a set charge level. You'll find more info on the gitlab linked from the Openstore.

Welcome to the community by the way! Thanks for showing your work here. Nice to see how well you've been able to get things working (although a swipe keyboard may be a long way off, and autocorrect has its bugs).

@Opolork I imagine app developers do their own write ups for the open store anyway? So maybe better to contact them directly. I don't know that for certain though.
I'd also suggest that if it's not likely to cause the communication to be misunderstood, it might not be the most pressing issue. But I dunno, I guess it's probably an easy enough fix.

@pparent Thanks for showing your work! I mostly get by just fine with Puremaps, but google maps is awfully handy when one needs traffic data. I'll have to try this.

Bit of an aside, but have you had issues with GPS crashing apps, be it Morph, uNav, Puremaps, etc, like in the thread linked below? And if so, any changes with your webapp?
https://forums.ubports.com/topic/8930/20-04-focal-unav-freezes-with-gps-enabled/18

@bestenaizena Yes, while the option to upgrade to 24.04 was talked about as a major aspect of 20.04 OTA 10, 24.04 isn't released quite yet.
From what I understand, now that you have OTA-10 the option will appear to upgrade to 24.04 once it's released.

Just for interest, I've asked them a few questions. They said they'd get back to me tomorrow.
I asked if the device already existed as a prototype, if they were doing the work that a porter does and taking care of it being fully functional, and if it was based on Halium.
I guess I could also ask specifically about VoLTE and how long they'd act as maintainer of the device.
Any other questions?

I suspect it's just one of a million prototypey things that could be made by such companies if a minimum order quantity were reached. But if they have an operational device, that's kinda interesting. No harm in asking.

@lduboeuf Yeah, sounds like a hard issue to solve indeed. Maybe one day more modern messengers will become more fully interoperable and we can forget about SMS.

Thanks for helping me understand how this works, and for filing that issue.

@lduboeuf Thanks for the help. Sounds like if on somebody else's phone a message was sent to me, but it never appeared in my notifications, threads view, or messages, it probably just won't be recoverable. The missing messages don't seem to be in history.service, so it's not just some problem of failing to be displayed in the messaging app.

The messages that I know about which didn't come through aren't the problem of course, it's not knowing how many other people messaged me without the messages arriving, and without the senders knowing that I didn't receive them.

My best guess is that this may relate to one or both of picking up messages after the phone has been powered off and being either in low signal or in an area where my cell provider has an agreement with other networks. It happened to me a lot with this phone when I was on a carrier who had a limited network, where I was out of normal network more frequently. I quickly switched cell carriers.
But I think it also may be either device specific or some glitch on my particular installation.

Hi! Does anybody have a clever way to try to seek out missed SMS messages? A terminal command or something?
It seems that when my phone is off, some messages don't get discovered. Unclear why some do and some don't. Not knowing who might have messaged me is tricky.
I'm using Oneplus Nord N10 on 20.04, for the record. Things were a bit glitchy when I moved to this phone and imported my old messages by moving history.sqlite over, but seemed to iron themselves out over time. I almost always have the phone on, so this problem could have been happening all along.

So far I've tried putting the SIM into another phone, and no new messages appeared, which I presume means the cell carrier thinks they were delivered.
I'm presently trying to examine history.sqlite in database software and realizing that I have no idea what a database is or how to find anything

@Amarurtuuq Very glad to hear it worked!
If it does happen again and you get the chance, it'd be great to get a readout of the Terminal command that @lduboeuf listed above, so folks who know more than you and I can understand what's going on.

journalctl --boot --identifier=nuntium --identifier=ofonod

Take care!

@vverve Thanks for testing further and reporting. I'm still on 20.04 and as this is my daily driver, used for my contracting business, have been hesitant to update.

I think that in short it's still unknown whether this device will get working VoLTE or not. Ruben has done great work on the port, but it's just one person maintaining it as far as I understand. I don't have much sense how much work it is, but had heard that it may be hard or impossible on Anroid 10 based ports like this one? But I'm really not sure.

I haven't seen anything about when Fizz/Vidéotron will end 3G (je suis aussi Canadien, d'Ontario). But out of network, Rogers already has, Telus is ending it in December, and Bell not til December 2026. So it could become more of an issue when roaming outside Vidéotron's network.

The Gitlab page is https://gitlab.com/ubports/porting/community-ports/android10/oneplus-nord-n10/oneplus-billie
I don't notice anythimg pertinent there, but am not really savvy enough to know.

If I hear anything on the Telegram channel, I'll post about it here.

@lduboeuf Thanks a lot for the suggestions. That's interesting to hear that the nuntium restart command should be the same as rebooting. It happened often enough that I feel confident saying a reboot didn't happen.
Now that I've heard your idea about booting I wonder if the trigger that would cause the issue was reboots all along. I'd be disappointed with myself for not making that connection, but it's definitely possible.

I don't have this issue anymore, it occurred both on a previous phone (Oneplus 5T) and with a different cell provider (not sure which change fixed it), but I'll try swapping my SIM into that broken old phone and see if I can reproduce it just to see.

As ever, thanks so much for your work on MMS and for the help!

@vverve Merci! I appreciate the report.

It still leaves me uncertain about what this means. When I have a call going on, the status bar always changes to 3G. Are you sure this doesn't happen?

I thought I'd seen a separate icon in a screenshot on the forum that said VoLTE on the top status bar, but maybe that changed.
It would be a big deal if VoLTE was working on Oneplus Nord N10!

@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.