@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

@Turbolqk Most sound like awful ideas. If you use it for long enough they're already implemented better than you think.

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?

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