I'm on Xenial and I've been daily driving for a couple months now. Overall I'm generally happy with the performance (I know it's "outdated"), but a handful of things still irk me:

1. The finicky lock screen. If you saw my post in here https://forums.ubports.com/topic/1010/lock-screen-doesn-t-lock/6, I've run into what appears to be a longstanding issue (2018-2025). Unless I can find a solution, I feel a lot more vulnerable now than I did with an iPhone.

2. The inconsistent alarm bugs. https://github.com/ubports/ubuntu-touch/issues/982. Sometimes alarms I set will ring, sometimes they wont. It is so inconsistent, I cannot rely on the phone to announce alarms whatsoever. This unreliability means I cannot confidently use the phone as an alarm.

3. Libertine did not want to play nice with the command line utility I wanted... nothing but errors. Couldn't find any solutions online.

4. Unencrypted partitions... I've read a few threads (such as this one https://forums.ubports.com/topic/1012/one-method-to-encrypt-home-phablet) but it also seems a bit finicky... I'd be more inclined to encrypt the phone if there were a method more "officially" supported, perhaps baked-in like how some desktop installs have options for luks.

I guess I'm open to investing in new hardware if the lock screen is more solid and alarms are reliable on a newer release... But if these bugs from 2018, or similarly annoying newer bugs, are still persistent today, on a current release, I can't help but feel a mainstream iPhone/Android is the better option as a daily driver. I've been developing a new app in my spare time and I almost feel like my time would be better spent investigating the alarm bug or something. Can anyone talk on their experience with Focal, or perhaps bestow any "little known tricks" for these old bugs I'm dealing with on Xenial?

I realize this is an old thread, but when searching the forums for a fix this is the thread that appears first for this issue... and it makes more sense to me to keep the issue organized here than create another newer thread and reference this.

Running the latest Xenial (16.04 OTA-25), I've somehow glitched the lockscreen to only ever require swiping, regardless of passcodes or passphrases being toggled, or the password changed with passwd.

Related issues that were opened at one time or another and closed with no solution:
https://github.com/ubports/ubuntu-touch/issues/260
https://github.com/ubports/ubuntu-touch/issues/410

Rebooting several times saw no change at all, and using the wipe/reset phone option under Settings did not restore the proper lockscreen functioning. Reflashing the phone as mentioned above is probably the only fix at this point, and I'll have to do that soon, but I'd be curious to know if anyone has had the same problem on Focal and if there has been any fix for it found? I don't really want to try enabling a passcode on my daily driver only to find out it's also glitched and it needs to be reinstalled too.

I look forward to watching the Q&A. Hopefully it's not a problem if I just rattle off several questions for the devs... I'm new here.

• How many developers are currently involved in developing the base Ubuntu Touch OS? (Not including unofficial app or core app developers.)

• What is the next target version for UT? 20.04 already seemed a bit old when UBports ported it. Would you be open to skipping 22.04 and going directly to 24.04?

• With that in mind, previously supported devices are subsequently dropped from the "supported"/"compatible" recommendations... but is this a result of just having low resources, and unable to test and port on all those devices, or do the devices become explicitly incompatible? Take for example a (random) 16.04 5-star fully-compatible device (https://devices.ubuntu-touch.io/device/suzu/release/xenial/) that is seemingly not supported on 20.04 at all; could 16.04-compatible devices technically get on a newer version of UT? Or is hardware of that era just too old for 20.04+ upgrades at this point?

In other words, if a phone is already 16.04-compatible, is that good enough? Would it technically be compatible with subsequent versions of UT? Notwithstanding whether or not the devs can/will provide support for it.

• How vulnerable to security/kernel exploits are users going to be going forward with a 16.04 UT phone? Would it be recommended not to use WIFI at all, or to try and backport the latest versions of apps/utils?

• Lastly, in regards to apps, are they sandboxed from each other, or could I end up writing an app that someone else then writes a specific exploitative app/util for?

Thank you

With further investigation I have found the visual artifacts do not occur in a VM of Ubuntu 20.04.5. App window appeared as normal both when logged in on X11 and logged in on Wayland session. QtStandardPaths and shader cache warning still appears.

Still not sure why it's not working right on my host system (Debian stable).

@arubislander

AMD, using the drivers from the main repo.

I've searched the forum and could not find any preexisting topics.

The clickable templates, by default, build broken with broken graphics/visual artifacts for me. In the generated window (created using clickable desktop) various different forms of artifact glitches appear. The only default template build that actually works is the Godot template. Not sure what this could be. Resizing the window to a very small height x width seems to fix the output, but at any usable size the graphics break.

Any ideas/fixes? Thanks.