You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Power Options does not disable GNOME Power Profiles. This leaves the user unsure how the app and the built in tool interact with one another. For example, if I want better battery, should I choose Power Options' Powersave and also change GNOME Power Mode to Battery Saver?
It would be helpful to at least have a note in the README regarding this issue.
The text was updated successfully, but these errors were encountered:
I’m not exactly sure of the specific power settings that GNOME’s solution offers so I can’t create an accurate comparison, but I had built power-options with the intention for it to be as feature rich as possible and I tried to add any feature that I’ve found in alternative tools such as TLP, PPD, or tuned. Therefore generally it will provide more settings than the default OS solutions and enabling both at the same time may add an overlap of settings. The ultimate intention for power-options is for it to be the only or the main power management program in the users system, and that is what I recommend.
However for complex integration with other tools I recommend the webview frontend as you can make the daemon ignore some settings that you want another program to handle.
Currently, Power Options does not disable GNOME Power Profiles. This leaves the user unsure how the app and the built in tool interact with one another. For example, if I want better battery, should I choose Power Options' Powersave and also change GNOME Power Mode to Battery Saver?
It would be helpful to at least have a note in the README regarding this issue.
The text was updated successfully, but these errors were encountered: