View Single Post
peterleinchen's Avatar
Posts: 4,118 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#1794
Originally Posted by karam View Post
i'm afraid you are wrong (tklock_mode_ind unlocked) gets activated
only when the user unlock the screen using the unlock button

so display_status_ind on is needed to change vfs to 100
when you press the power button and swipe to unlock
or when you receive a call
I might be wrong, no question!
But I just tested it again and it worked flawlessly.

Here I post my vfs_cache_pressure file from /etc/dbus-scripts.d/
Code:
# This file was generated by dbus-scripts-settings
# If you edit it by hand you might confuse the program,
# and you might lose your changes next time the program runs.

#:vfs_100
/opt/scripts/cpu_normal.sh * * com.nokia.mce.signal tklock_mode_ind unlocked

#:vfs100
#/opt/scripts/cpu_normal.sh * * com.nokia.mce.signal display_status_ind on

#:vfs_10
/opt/scripts/cpu_sleep.sh * * com.nokia.mce.signal tklock_mode_ind locked

#:vfs_10
/opt/scripts/cpu_sleep.sh * * com.nokia.mce.signal system_inactivity_ind

#:vfs_10
/opt/scripts/cpu_sleep.sh * * org.freedesktop.Hal.Device Condition ButtonPressed cover

#:vfs10
#/opt/scripts/cpu_sleep.sh * * com.nokia.mce.signal display_status_ind off
With these settings, the pressure is always set to 10 after device got locked (even after keyboard closed, when it was open during locking). So only chance to keep pressure at 100 is the proximity sensor.
I like it that way...
 

The Following User Says Thank You to peterleinchen For This Useful Post: