Next: , Previous: Clients, Up: Top


19 Version Specifics


Version 0.9

1) Configuration
dropped variables for schemes in /etc/sysconfig/powersave/schemes_*:
POWERSAVE_DISABLE_DISPLAY_SETTINGS=
POWERSAVE_DISABLE_SCREEN_SAVER=
POWERSAVE_DISABLE_DPMS=
POWERSAVE_DPMS_STANDBY=
POWERSAVE_DPMS_SUSPEND=
POWERSAVE_DPMS_OFF=
These settings are no longer handled by the helper scripts but by the
graphical clients like kpowersave (which can do this more easily).

2) events / scripts in /usr/lib/powersave/scripts
It was already possible in version 0.8 to put executables into
/usr/lib/powersave/scripts and use the names of these executables as event
names.
In version 0.8, only the exit status of the script was used to determine
success or failure. In version 0.9, you must now use
/usr/lib/powersave/scripts/powersaved_script_return to tell powersaved if
the event was executed successfully or not. Read more in README.events

3) Clients
Clients can now register with powersaved and get notified for specific
events, so polling is no longer needed. Take a look at the "testclient"
source code for further information.
Clients can also be notified by e.g. proxy scripts to popup a messagebox,
a progress bar or to lock the screen.

#########################################################################

Version 0.8

1) Configuration
configuration merged into one directory.
powersave.conf (etc/) and common (/etc/sysconfig/powersave)
have been merged into the files common, events, cpufreq, thermal,
sleep and battery.

Following config Variables have are new or have changed:

New general variables:
/etc/sysconfig/powersave/cpufreq:
POWERSAVED_CPU_HYSTERESIS=
POWERSAVED_CONSIDER_NICE=
POWERSAVED_JUMP_CPU_FREQ_MAX_LIMIT=

/etc/sysconfig/powersave/events:
POWERSAVE_EVENT_DAEMON_SCHEME_CHANGE=
POWERSAVE_EVENT_TEMPERATURE_CRITICAL=
POWERSAVE_EVENT_TEMPERATURE_HOT=
POWERSAVE_EVENT_TEMPERATURE_PASSIVE=
POWERSAVE_EVENT_TEMPERATURE_ACTIVE=
POWERSAVE_EVENT_TEMPERATURE_OK=

/etc/sysconfig/powersave/thermal:
POWERSAVE_ENABLE_THERMAL_MANAGEMENT=

new variables for schemes in /etc/sysconfig/powersave/schemes_*:
POWERSAVE_DISABLE_DISPLAY_SETTINGS=
POWERSAVE_DISABLE_SCREEN_SAVER=
POWERSAVE_DISABLE_DPMS=
POWERSAVE_DPMS_STANDBY=
POWERSAVE_DPMS_SUSPEND=
POWERSAVE_DPMS_OFF=

Because of confusing naming of sleep states those have been renamed:

there was:
suspend (ACPI S4, APM suspend)
standby (ACPI S3, APM standby)

now there is:
suspend to disk (ACPI S4, APM suspend)
suspend to ram (ACPI S3, APM suspend)
standby (ACPI S1, APM standby)

Therefore following variables changed in
/etc/sysconfig/powersave/events and
/etc/sysconfig/powersave/sleep:
POWERSAVE_EVENT_GLOBAL_SUSPEND2DISK=
POWERSAVE_EVENT_GLOBAL_SUSPEND2RAM=
POWERSAVE_EVENT_GLOBAL_RESUME_SUSPEND2DISK=
POWERSAVE_EVENT_GLOBAL_RESUME_SUSPEND2RAM=
POWERSAVE_UNLOAD_MODULES_BEFORE_SUSPEND2DISK=
POWERSAVE_UNLOAD_MODULES_BEFORE_SUSPEND2RAM=
POWERSAVE_SUSPEND2DISK_RESTART_SERVICES=
POWERSAVE_SUSPEND2RAM_RESTART_SERVICES=
POWERSAVED_DISABLE_USER_SUSPEND2DISK=
POWERSAVED_DISABLE_USER_SUSPEND2RAM=
POWERSAVE_SUSPEND2DISK_DELAY=
POWERSAVE_SUSPEND2RAM_DELAY=
POWERSAVE_STANDBY_DELAY=

2) Thermal Management
Thermal management is supported from now on.
see README.thermal.

3) Switch Schemes Manually

Schemes can now switched by hand using the powersave -x (overview of
all schemes) and the powersave -e scheme_to_set (switch scheme)
parameters.

4) Socket Interface

Other progs can now query the daemon for:
AC state
Suspend_to_disk enabled by admin
Suspend_to_ram enabled by admin
Standby enabled by admin
Current cpufreq policy (powersave, dynamic, performance)
Battery state (no_bat, normal, warning, low, critical)
Battery charging state (unknown, charge/discharge, charge, discharge)
Remaining percent battery capacity

by one socket connect using the send_Action_get_States() and evaluate
the return value using evaluate_States(int64_t states, int data_to_evaluate)
(in libpower/powersave_daemonlib.c)

Other progs can also switch query for a list of existing schemes using
send_Action_get_all_Schemes(SchemeList* s) and switch schemes
using the send_Action_ActivateScheme(const char *schemeName).


5) Screen Saver / DPMS

Screensaver (at least KDE) can be enabled/disabled and DPMS values can
be modified depending on the current schemes.
This allows to configure a presentation scheme (no DPMS/Screensaver)
and a more effective powersave/battery scheme (more extreme DPMS values)

Use the following variables in the scheme configuration files:

POWERSAVE_DISABLE_SCREEN_SAVER
POWERSAVE_DISABLE_DPMS
POWERSAVE_DPMS_STANDBY
POWERSAVE_DPMS_SUSPEND
POWERSAVE_DPMS_OFF


Version < 0.7