Just go and use Android or other Android like OS if you want something like that...
Have you considered that doing something different is not ignoring anything.
As for intuitive this is relative to what people have used before.
People will have there own personal and group goals for these FOSS projects. Just because they don't align with your vision of what you believe should be done, doesn't give you the right to complain other people are wrong. It contributes nothing to moving forward.

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

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

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

@t12392n
I can confirm this too.

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.

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

@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

@pparent Dino could be a good candidate chat works but no voice or video calls possibly due to missing dependencies. The UI is not touch friendly.
Personally I think these types of calls should be part of the calls and messaging apps.