SUMMARY This driver exists for a reason: it allows applications to query system-wide energy saving mode even if there's no hardware support. Since Plasma ignores these profiles, it's not possible to set power-saver mode so applications consume less battery. STEPS TO REPRODUCE 1. Have hardware without power-profiles-daemon special driver 2. Try to enable energy saving mode OBSERVED RESULT Plasma lets me to do so EXPECTED RESULT Plasma hides the option from the UI SOFTWARE/OS VERSIONS Operating System: NixOS 23.05 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.12-zen1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 5.7 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics
Oops, swap the observed and expected results
We recently thought about doing this, but the conclusion was that given the only thing that happens in this placeholder performance mode on the end of the power profiles daemon is a change in charge method with unclear effectiveness, it would seem like a false promise to expose this. If (as was the idea behind that mode) other software would use this information to do their own power saving measures, this would change matters. Do you know of any applications that actually make use of this? Related: the idea of Plasma doing some power saving on its own: https://bugs.kde.org/show_bug.cgi?id=467253
I need that to debug the use of the API in an application I contibute to
Can you be more specific? Where does Plasma exposing the profiles enter the equation? Given that for the purposes of app development, you can just interact directly with the power profiles daemon service, the question here is whether there are enough apps that do anything with this information that it would be worth for Plasma to show a UI for the user to interact with the profiles.
I don't know any other than the one I contributed the implementation to - Telegram Desktop
Do i need to provide any other info?
I also think this is kind of chicken & egg problem. I wanted to test the UX a typical user would get but when I noticed no UI for the API in Plasma I thought it's not supposed to be used by applications like that. Fortunately I checked other DEs (GNOME) and found this behavior is specific only to Plasma. I guess various GNOME applications can use this API as well but as long as Plasma doesn't provide the UI to users, the Qt world just won't see a reason to use the API I guess by thinking there's no such feature just like you think right now that there's no one who would like to use it.