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.

@iceman198 The clickable software will output a .click "Clickable"
From what you posted you have installed the clickable software on your Ubuntu machine as a Snap package. I have it installed from the ubuntu apt repo. If the software is now working for your needs then it's nothing to worry about.

I've never used the snap version. But I'm not fond of snaps and there issues myself.
Does the same thing happen if you just install clickable from apt?

It does work on Apple devices from iOS 18.
If there is only Googles implementation of the open standard available then it will be difficult to move forward on it. I can't see carriers running the backend to support "alternative" OS devices.
I'd be happy with just XMPP working within Messages if RCS is not feasible.

This is OMEMO legacy. The images send but if the last message was an image the chat disappears from the chat list.

@projectmoon Only after I had these issues. I'm starting to get messages through now. There is no read confirmation from what I can tell. I now have it were the chat has disappeared as the last thing I sent was an image. I have to use contacts to find chat. The invisible messages I got before this are stuck as unread on the appbar

Most public IRC Networks have easy access to cloaking now.
I seem to be having issues with recieving messages in Livewire. I can send and read my own messages to another person from Livewire but they only ever show one tick. The messages from the other person dont appear at all in Livewire client not even errors just silence. Other clients show them fine.
I also have 2 unread messages on the notification side app menu but nothing is unread.

Thank you I have been hopeful a working UT OMEMO XMPP chat client would come soon.
This is very heavy but functions which is great.
I have a few questions.
How far away are features like:- OMEMO MUC, In band registration, support multiple accounts, audio/video calls?
If Libervia is a backend is there a possibly it could be merged into the existing messages app?

@ChromiumOS-Guy
https://commons.wikimedia.org/wiki/File:Cell_Broadcast_Alert_Tone.oga
There is a standard for the tone as covered on https://en.wikipedia.org/wiki/Cell_Broadcast#Public_warning_systems

I'm using a Bluetooth headset myself on FP5 with no 3.5mm available. I have found this intermittent on both stable 1.2 and 1.3, sometimes outputting to the speaker and sometimes just to the headset, I'm not sure if this is some volume setting that gets changed somewhere.
Personally I would have always preferred if the device made no sound with the headset plugged in but never thought of the use case were you could miss a call if you leave the headset connected.

I only had this issue start when moving from stable 1.2 to 1.3