-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OLED screen turn off #4
Comments
Camera has screen off delay by its own which works on RVF mode too. Lower it when using RVF and here you go. |
It looks like the usual X11 screen saver controls fall short on this device:
Changing the screensaver parameters does not have any effect, and neither is it activated. Going the framebuffer route seems to have no effect either:
|
You can disable and enable the LCD from the command line using the Display off: Display on: Full documentation of
I tried to make a script that monitors As an alternative, I've written a script that counts how often you press the +/- EV button, and turns off the LCD after three consecutive presses: #!/bin/sh
export DISPLAY=:0
powersaving=0
counter=0
script -q -c "xinput test keyboard1" | while read key press id ignore ; do
if [ "$press" = "press" ] ; then
if [[ $powersaving -eq 1 ]] ; then
st lcd set 3
powersaving=0
counter=0
else
if [[ "$id" = 181 ]] ; then
counter=$((counter+1))
if [[ $counter -eq 3 ]] ; then
powersaving=1
st lcd set 4
counter=0
fi
else
counter=0
fi
fi
fi
done Unfortunately, I can not get this script to run from autoexec.sh, as it immediately terminates without any output. If you have telnetd enabled, you can telnet onto the camera and run the script from there. |
Could it be possible to turn the OLED screen off with a combinations of Key events (such (+/-) and (trash) pressed together)?
The aim is, when using the camera with an remote shooter, reduce the battery consumption.
I have no experience on programming (nothing at all...) If it could be done by you, I would gladly pay (not so much...) for the development.
The text was updated successfully, but these errors were encountered: