@nbdynl That sounds great.
Does it also work with no apps open tho?
Is this a MariKit or Lomiri Plus option?

@ChromiumOS-Guy I think this is a good idea. I currently have showdesktop pinned to the menu bar. It being part of the OS would be great.
I'm open to it being some other action aswell tho. I was thinking a full swipe from left to right while the app menu was open, so the opposite to opening the taskswitcher?
Having used OS's both mobile and desktop that allow to go to the desktop, Ubuntu Touch feels very odd without it.

@projectmoon As I understand it apps work like that currently in UT? You can use UT Tweak Tool to have apps ignore this.
Experiments you mention may vary from device to device based on the silicon which is fine if your OS is only targeted to one processor for example.

I do feel these charge limit options would fit perfect into the battery settings menu, rather than the pulldown. A maximum limit for charging also a way to hold 80% charge until say 7am (variables of these) would help the batteries in our devices last much longer.

Enabling and disabling things can get annoying tho. Part of the benefit of these features while they're enabled is that they work automatically like handsfree bluetooth connections and switching to WiFi. Having the ability to leave the settings you have alone but have a master switch for them all while adding a few extra energy focused features seems like a sensible feature.

I'm confused on the comments about accuracy tho? Are we saying devices are reporting flat when they have more to give? Or that certain devices consume too much battery with UT? Even if the mA to % calculation varies per device, I don't feel it takes away the need for a feature like a low power mode? Do I miss something?

So the feeling is these types of thing should be part of the OS and not openstore apps?

I hoped this would have generated more of a discussion but maybe it's not something that people actively seek to use, despite being common function of most OS's?
I could argue it's not just a few clicks to do what I suggested, some are available in the battery page of settings but not everything.
I'd imagine the basics would be low hanging fruit for someone that understands QML and how those settings plugins work. Being around FOSS for a long time I know if your enable to bring pull requests to the table for your ideas it's much better but it's beyond my skills for the moment.
As I say functionality could expand beyond basics of toggling a handful of features I'm proposing now.
Would features that improve the OS like this be considered for inclusion into the OS rather than unconfined apps like battery-saver?
If in wouldn't be something of interest I'll likely look into something I can engineer, are there any documentations on controlling all of the settings options via a script beyond searching the forum for bits of code?

I have been looking into improving energy consumption recently. There's capacity to greatly improve the battery life from switching off features on a device. On my FP5 I can consume overnight ~30% battery with all features on, WiFi, BT, Location, NFC, 5G, device locked. Compared to 2% with only 2G enabled and device locked.

This has had me looking into shell scripts on the forum and the battery-saver app from open-store.
I'm looking for something light that would just disable all these features without going into each option and then restore everything back as I had it.

To me this seems like something that should be included into a toggle on the Battery pull-down menu itself, much like most modern devices have a "low power mode".
How feasible would a toggle option to disable all these power hungry features and set the radio to the most energy efficient available in your location. Then toggling back would restore what you had previous. It seems like something the OS should provide and not additional apps.

Is this something people would want to use from the OS itself rather than additional possibly more flexible unconfined apps?

I would say being part of the OS leaves scope for more battery saving options if it was to be taken further as the OS matures, maybe scheduler tweaks or manual display brightness settings for example. But keeping everything a simple toggle for the UX.

How is not using Windows relevant to the suggestion to start again?
You're have plenty of issues that no-one else is experiencing, I'd say it's a sensible first step.
If something was borked during installation or you had the wrong Android version then the UT installed on top of that, may not function correctly.

Is it worth considering starting again?

Installing the correct Fairphone Andriod version listed on the ubuntu-touch website and following the install procedures for 24.04 stable?

I have none of the issue you mentioned in your multiple threads with my fp5.
The only outstanding issue is the fingerprint reader for me at the moment on stable.

I agree with Cibersheep here.
It's not part of the OS design to have a global back button like Android and not a requirement due to the edge OS controls.
Yes the in-app back being top left is awkward positioning for one handed use but I would find it more annoying that a window was closed/disappeared by accident from some other inconsistent close or back positioning.
I'm not against a top swipe for back on top of the standard style back, like in openstore Timer app but really following the development guidelines and being consistent between all apps is the important thing.

@Futura Taking your example of a car...
In this situation the vehicle chassis is the equivalent of the mainboard, the chassis number is the cars identity and in most places would then be considered a different vehicle at that point you can't swap a vehicles chassis and have the "same vehicle", however, you can swap everything else even engines.
Your unlikely to find a vehicle manufacturer that would sell you just a brand new chassis, maybe in the specialist industrial space but not domestic cars.

Anyway I'm not saying I like this in any industry. It would be nice to repair everything but unless more devices are supported natively we are stuck with these workarounds and lockouts to get nicer devices running what we need.

I'm all for repairable devices and empathise with your situation.
It does make sense that you can't replace the mainboard, at that point your not repairing the device your replacing it for a new one.
I would say you've been had by the reseller and Fairphone have been pretty fair with you considering the situation.
It's probably been too long but I would take it up with ebay.

@gpatel-fr Mine is the maximum length of 64 chars for WPA2.
It's annoying that the GUI doesn't handle that well but the device will work.

If the device can't connect it does just show "WPA" in the top bar notification with a password prompt and not "WPA & WPA2 Personal" as it probably should.
That doesn't mean you are trying to connect via WPA.
I think it would be best to follow my instruction to remove the AP and setup.

If the network is already saved then you shouldn't have an option, only when you connect to hidden networks would you enter stuff like this first time.

Is this a hidden network and you have saved the wrong settings. Hidden network are not really advised but that's a different topic...

I would suggest you delete your network settings for that AP, reboot the device and try to setup again. You shouldn't need to use the Connect to hidden network option unless its hidden.

WPA & WPA2 Personal are normally grouped together.

I have had this experience maybe once or twice on 24.04-1.x stable, I use the device daily.
I have never used Waydroid only native apps and Libertine.
When it happens the back of the device is very warm, so I'm thinking some watchdog is kicking in?
Battery settings charge level graph shows a little dip around the time it does it as well.
The seemingly unresponsive device eventually reboots itself in around 3-5 minutes and all is then back to normal.

I find SMS flaky both incoming and outgoing with VoLTE on, although I'm not on the same carrier but worth a try.
I have experienced this once on daily and couldn't work out why in the end I flashed stable (without wiping) the problem went away.

Has this been confirmed? Have you tried just reinstalling again?
Do bear in mind if you downgrade from A14 to A13 do not try to relock the bootloader as Android rollback protection kicks in.

@jilly It's fixed in 24.01-1.1
Not sure were it was tracked. Seen a forum post about it, plus the changelogs for 1.1

@enki Bug in the Bluetooth? That type of issue does happen intermittently.
Try disabling bluetooth then rebooting, on reboot wait for the phone to settle for a few minute before enabling bluetooth and trying again.
https://gitlab.com/ubports/porting/reference-device-ports/android11/fairphone-5/fairphone-fp5/-/issues/14