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.

Just want to point you to discussions here.
https://forums.ubports.com/topic/12184/battery-saving-low-power-mode-within-os-discussions
I long for an toggle-able option like this available from the battery pulldown.
With some knowledge of QML and the layout of lomiri-system-settings I believe its possible to implement.

@nbdynl
On my opinions for resolving this with the indicator panel... I'm picturing if you double tap the indicator panel it would latch in a half open state (or just big enough to have all the options on show). Then you can swipe around and use it with it latched open until you tap outside the pulldown.

I like all the indicators and the feel of most things while at home or sat down but when your doing active things or only have one hand free is where UT always feels awkward.

@RJDan
I would say that making the device difficult to use by turning down the brightness is the problem and that having to use the device like this should be fixed before anything else. I do understand your point but it can't be expected to resolve a weird workaround of turning the brightness to an unusable level that's been implement by yourself.
I agree other things need to be fixed here, either in the app itself or improving the way location services work while out of focus.
Regarding emergencies as an idea an extra feature could be provided in the OS, maybe you press the lock button 5 times fast and if you don't cancel it on screen it will call your pre-determined contact from your device. It would be a nice feature similar to iOS I suppose.

I have done this myself to save battery and struggled to see the device to change the settings in full sunshine.
I do agree with your opinion I feel there can be a lot of cases like this with UT. Using the device as a sat-nav and/or media-player in a car dock the panel is not the best either.

One possible solution for your case would be not changing the brightness but disabling app suspension for your app (and it's dependencies OSM?) with Tweak Tool.
I haven't used Activity tracker but this should work for your use case.

Overall 24.04-1.2 seemed to work perfect in my day to day usage.
Whereas 1.3 has some occasional quirks/regressions/differences? that are noticeable to me but not breaking enough to remember or make a note of each of them while out at work.
This signal strength was a noticeable one, I know the nearest mast is not far away and I know what is displayed now is very different to 1.2. Which is correct/accurate is another matter, if it's correct that's fine but ultimately people want to know at a glance if they can make a call and an empty triangle with even poor signal is not a helpful indicator if a call would be possible. Is there a different symbol for no signal as I haven't seen it? I believe you have to pull down and look at the carrier showing "Searching..." for this?
Another change I can remember is cellular data, before I could open the default browser anywhere and just browse straight away. Now intermittently with no WiFi available the browser will not have a data connection, the quick way I found to resolve this is shuffle cellular data off and on again.

Possible issue found in 1.3, maybe this could be checked it's not only myself?
Bluetooth can't be disabled or enabled from the battery menu. The toggle moves but it doesn't work and stays in the same state.
I use this regularly as a quick way to achieve some power savings from one place, part of discussions on usage here
Disabling from there own respective pull down works correctly.

Signal strength isn't the issue, I wouldn't expect them all to be the same.
I know the signal strength is displayed much lower on 1.3 for 5G and 4G compared with 1.2 is the point

@kristatos Same for me on FP5.
It depends on the cellular connection selected.
With 5G selected signal shows empty, with 4G it's either low or half and with 2G or 3G its full.
All of these previously were full signal I'm pretty close to my nearest cell mast which has 2G/4G/5G

Having a way to have no sidebar like the showdesktop app, maybe I see "home" differently. A blank space with only the top bar to distract me

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