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.

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.