| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If we want the computer to be able to take useful action about the low
battery, we should have a slightly higher "low" percentage level so that
power saving made really makes a difference in runtime.
Also bump "critical" slightly so that doom isn't quite as near but in the
distance nonetheless.
The "action" level stays the same, as 1% is too close to some batteries'
actual switch off point, eg. the computer might brown out before we see
1%.
|
| |
|
|
|
|
|
| |
It's not used by gnome-settings-daemon any more, logind reads the
Lid status itself.
https://bugs.freedesktop.org/show_bug.cgi?id=92920
|
| |
|
|
|
|
|
| |
It is now based on the percentage of battery left, rather than the
usually unreliable "time left". See configuration file for more details.
https://bugs.freedesktop.org/show_bug.cgi?id=92920
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The IsDocked property has been incorrect for a number of laptops for a
while, as it thought that laptops with hybrid graphics cards were always
docked.
The alternative would have been to use the platform/dock_station
devices, but those are only exported for ACPI docking stations.
Instead, whether an external display is attached (which isn't really
docking) should be checked in the same place where the policy depending
on the value should be applied, such as gnome-settings-daemon.
https://bugs.freedesktop.org/show_bug.cgi?id=36818
|
| |
|
|
|
|
|
|
| |
For system integrators. If your firmware is helpful to user space
and automatically sends out uevent when the battery level changes
(rather than just the battery state) as on most machines,
you can enable "NoPollBatteries" in the configuration option,
and reduce power consumption from UPower and its listeners.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Paraphrasing from the configuration option:
The action to take when "TimeAction" or "PercentageAction" above has
been reached for the batteries (UPS or laptop batteries) supplying
the computer.
This is done 20 seconds after the warning-level variable got set
to UP_DEVICE_LEVEL_ACTION has been set, to give the opportunity
to front-ends to display a (short) warning.
This is only implemented for the Linux backend, using logind.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
They are few are far between, and users of the device can
spare the time to enable this by default.
https://bugs.freedesktop.org/show_bug.cgi?id=33846
|
| |
|
|
|
|
|
| |
Defaulting to true, it controls whether we want the powersave commands
to be run when running on battery/plugging ac.
Signed-off-by: Richard Hughes <richard@hughsie.com>
|
| | |
|
| |
|
|
| |
don't suspend at session start
|
| |
|
|
|
|
|
|
| |
Annoyingly, the device used in the Watts Up Pro device seems to be a generic
USB->serial adaptor, which means it doesn't have a unique vendor and product
ID. If we try to probe for the WUP device, we can actually upset other devices
that are not expecing to be probed. This fixes #33846 although we actually
still need to be more strict in detecting a true WUP device.
|
| | |
|
| |
|
