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
Migrating from Win10 to Elementary was great and the only downside is power management. Tere's no differentiation on options for (battery vs AC)
On Win10 i used to set my laptop to never sleep when i close lid on AC. And to sleep when lid close on battery. This work flow is essential in an open workplace where you need to perform lengthy tasks or uploads while away.
In Elementary there's option for lid close action in general but without AC/Battery customization. We need better power management in eOS
The text was updated successfully, but these errors were encountered:
peteruithoven
changed the title
Better power management options
Lid closed action customizable in both Plugged in and On Battery states
Jun 7, 2019
I don't think it's useful to call for Better power management options in general when you're just talking about one option. Issues should be as focused as possible. So let's focus this on the specific power management setting you'd like to see: Lid closed action customizable in both Plugged in and On Battery states.
I'm also moving this to the power settings repository.
I'm not sure why we're using the logindhelper here for these settings actually. It looks like GNOME Settings daemon covers settings for line power, battery, and an option here for external displays
Migrating from Win10 to Elementary was great and the only downside is power management. Tere's no differentiation on options for (battery vs AC)
On Win10 i used to set my laptop to never sleep when i close lid on AC. And to sleep when lid close on battery. This work flow is essential in an open workplace where you need to perform lengthy tasks or uploads while away.
In Elementary there's option for lid close action in general but without AC/Battery customization. We need better power management in eOS
The text was updated successfully, but these errors were encountered: