@developerbayman I only know Droidian and UT. I don't know any other projects that use Halium and has actual daily driver users.

postmarketOS has always been about mainlining mobile devices so it's not that.

@grenudi
You literally raised issues about the project. What do we do with issues? Stare for eternity?

The purpose of this document is to serve as a roadmap and a reality check for newcomers. You mentioned my technical background—that is exactly the point.

Most people won't care about the things you mentioned. You had the knowledge on these things so you care about them but most don't so they don't need to the same insane effort you did or doing here

the official website markets Lomiri as a "fully Wayland-based shell environment,"

I don't know where you got this. The site said Mir and Wayland

When someone arrives here wanting to make a minor contribution—maybe a translation or a small bug fix

I don't know why they would think that since they are contributing to a project that doesn't explicitly say "We are Mobile Linux and your contributions contributes to the whole Linux community"

Anyway, you've put a lot of effort on this already. You don't like UT, we get it, it's fine. Don't you have anything else worth putting your effort into? Like for example contributing to Linux mobile?

Are you like paid to do this? Wait, are you from GrapheneOS? LOL

Everytime there's a new release (OTA update), there's a post here and a blog that lists notable changes and improvements. You can also check merge requests in the Gitlab repos if you want to get more real time changes.

@grenudi Which projects ditch halium?

@grenudi Are all these just because you didn't properly research what you're getting into?
Sorry, but the you seem to be technical and know things so I would assume you would have had the proper skills and know how to judge if UT is what you're looking for. From what I see, you're just lashing out because of that bad decision.

UT under UBports has existed for almost a decade now despite having very low man power. That has improved in recent years but it's still not as good as even the other mobile distros like postmarketOS, Mobian, etc.

Some of the issues you raised are valid but those would've have been solved long time again if they are simple to fix. You're basically asking the project to start fresh and ditch a lot of things. UT has had users since 2014/15, UBports picked it up along with those users. It's not realistic to continue the project while taking out its gut and expect users to still have a usable system.

If you don't like the project, then you're free to use and contribute on other projects. If you really want changes in UT, you are also free to contribute and address the issues you raised.

@developerbayman You can check the postmarketOS project to see how realistic it would be for UT to ditch halium.

@developerbayman That's already possible on mainline devices but it's not trivial on devices without mainline which is most of the devices. And even if they do, many things don't work.

Not sure what your realistic expectation on this

While waiting for the official solution, you can try installing Lomiri Plus Essentials via Ambot Installer from the OpenStore

This is cool. Not sure though if gamepad input now works properly in UT but the touchscreen controls would suffice

@Kadafi Do you know what kind of connection it uses? In my experience, BT3 and BT5 works better while BT4/BLE works quite bad.

@haagch There's a separate back button but I guess the mouse back button is better supported in desktop apps.
And yes, it's currently not working in UT.

@projectmoon There's a setting for that inside Ambot however it only works in unconfined apps.
Not though that there apps that use the affected components in unusual ways so the hint may show in weird places e.g. Music app, the hint shows above the currently playing bar

In regards to the global back action, we can implement it in the toolkit, you just have the back button trigger with the back button but we can't really enfore it everywhere else so it will be kind of pointless if it only works in certain apps

Do you have any other device you can test your device? Adapters and hubs that works on laptops, gaming handhelds, other phones should work on the Fairphone 5.
Can you reflash Android and test there? It might be a hardware issue.

There's no universal "back" action in UT, the same way most OSes don't have it except Android and Windows phone. There's a back button in each app but can be implemented differently and reacts to different key bindings or none at all.

This has been discussed many times already and honestly, I don't think we can have a universal back action similar to Android. The best we can do is probably to design the standard toolkit to make it easier to trigger. That's another discussion that has been discussed many times too but needs someone to actually design and implement it.

I personally have many experiments on this. My older apps like Palitan for example has swipe up on the bottom left edge to go back (or whichever button is at the top left). My newer apps like Tagatuos and Sapot Browser, you can swipe left or right on the bottom edge. Ambot Installer also has a package called MariKit which adds this gesture is apps that use UT's standard toolkit.
I personally like this gesture but there needs to be a deeper and proper discussion if we really want it

I think the closest reference you can check is Tagger or the built-in barcode code scanner. Probably worth checking them out. Be warned though that media capture and such most likely isn't as robust as on Android so there will be limitations.

@RJDan Do you have another phone to test if it has the same behavior. I think it also depends on the hub/adapter. If I remember correctly, mine usually reconnects when I disconnect the power while the display is connected.

I'm tinker with mine and see how they behave. I have a few adapters/hubs.

I don't use mine frequently but when I test it for extender period of time, I don't experience unexpected disconnections.

@jagdtigger Have you tried re-pairing. You mentioned you deleted the config so maybe that deleted all paired devices? I actually don't know which or where thar config files are.

You can also try turning off bluetooth first then run the command.

Run this command until you see all your paired devices listed again
sudo systemctl restart bluetooth.service

@projectmoon I believe that doesn't use the same wireguard that's in the system. I've never tried myself since the built in one works fine. I don't use it often

You can try Wireguard. It doesn't have GUI yet in UT but the commands are simple.

Download the Wireguard config file from your Proton account. Rename it to wg0.conf.
Then run

nmcli conn import type wireguard file wg0.conf

To connect:

nmcli conn up wg0

To disconnect:

nmcli conn down wg0