View Single Post
peterleinchen's Avatar
Posts: 4,118 | Thanked: 8,901 times | Joined on Aug 2010 @ Ruhrgebiet, Germany
#1630
Originally Posted by don_falcone View Post
Sure? Did you copy the header of file 'dbus-script' then, or why does it show the same first lines?
Yes, pretty sure. I installed manually and checked all existing or non-exisitng items.
dbus-scripts existed
dbus-scripts-session needs to be created on ones own
I think karam mixed here a little bit in the rush.
So, do not provide dbus-scripts, but only dbus-scripts-session with following content:
Code:
description "dbus-scripts-session"
author "Graham Cobb <g+770@cobb.uk.net>"

start on started hildon-desktop
stop on stopping hildon-desktop

console none

exec run-standalone.sh /usr/sbin/dbus-scripts --session
respawn
About that thing with telephony and vfs_cache:
Yes, karam, You are right. There is no need to add anything. I tested it and vfs came to 100 on call arriving and was set back to 10 after call with inactivity events. So please forget my former sayings.

BUT:
the vfs was also set to 10 during a call, because of proximity sensor and locking state.
I added/modified following to the cpu_sleep.sh:
Code:
#!/bin/sh

brightness=$(cat /sys/class/backlight/acx565akm/brightness)
keyboard=$(cat /sys/devices/platform/gpio-switch/slide/state)
proximity=$(cat /sys/devices/platform/gpio-switch/proximity/state)

if [ "$brightness" == "0" -a "$keyboard" == "closed" -a "$proximity" == "open" ]; then
        echo 10 > /proc/sys/vm/vfs_cache_pressure
fi
This will add the check for the proximity sensor.
If we keep a finger on it, the pressure will not be reduced, but kept at 100 (as feature someone may claim it as bug for accidentally keeping the sensor closed while locking, but I see it as feature )
This will also keep track and solves everything related to phone calls. Keeping pressure on 100 during a call...
 

The Following 2 Users Say Thank You to peterleinchen For This Useful Post: