To progress further with the initial flashlight idea, controlling the flash directly appears to work fine in the following way.

#!/usr/bin/env bash

flashOff() {
	printf '%s' "0" > /sys/class/leds/led:torch_0/brightness
	printf '%s' "0" > /sys/class/leds/led:switch_0/brightness
}

flashOn() { # 2 appears to be the minimum brightness value possible
	printf '%s' "2" > /sys/class/leds/led:torch_0/brightness
	printf '%s' "1" > /sys/class/leds/led:switch_0/brightness
}

So with a loop I can have a nice flashing pattern at the minimum brightness.
Just need to find what to hook into so I can have it only running only while there is a green notifications icon.

As for using the screen, I think the green envelope icon, possibly slowly moving along the top edge of the screen (to minimise any burn in); would be a nice option there.

Just a quick post for forum lurkers that updating to 24.04-1.0 stable on Fairphone 5 has gone smoothly for me.
To install use the ubports-installer select stable and leave the wipe data unchecked.
Then do reinstall all apps from the system settings menu.

Issue with Libertine is resolved only thing I have seen an issue with is OSM server not starting for Pure Maps but I haven't tried debugging yet.

@knuddel823 It's recommended to install Fairphone version of Android 13 as per the install instructions.
https://devices.ubuntu-touch.io/device/fp5/release/noble/#installerDownload

This is a workaround that I have been trying for a little while.
Try constructing the message then switching airplane mode on then off before sending.
I read something similar on another post and it seems to work for me so far.

All notifications are affected.
The current options are wait for it to be fixed in stable or switch to daily.

Comparing with flashlight on and off.

Off
/sys/class/led/led:switch_0/brightness = 0
/sys/class/led/led:torch_0/brightness = 0
/sys/class/led/led:torch_3/brightness = 0

On
/sys/class/led/led:switch_0/brightness = 1
/sys/class/led/led:torch_0/brightness = 127
/sys/class/led/led:torch_3/brightness = 127

I'll need to test if changing these will trigger the light, certainly just making switch_0 = 1 doesn't work.
Not sure if this is the correct way to interface with these.

As for monitoring for new messages I'm wondering if dbus-monitor could be used...

Run the installer, it should detect your device and then use the option to reinstall but don't tick the wipe personal data option.

@gpatel-fr I believe you are experiencing:-
https://gitlab.com/ubports/porting/reference-device-ports/android11/fairphone-5/fairphone-fp5/-/issues/37
Which I occasionally have had on the current stable version anyway.
You can force it to happen if you play with the Network toggle buttons for a bit but in my general usage I find it's rare to trigger this bug.

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

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