Skip to content
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

Not returning to full brightness RPI3 B+ Raspbian Buster / Octoprint #2

Open
morganlowe opened this issue Feb 19, 2020 · 1 comment

Comments

@morganlowe
Copy link

I use the official RPI Touchscreen as a kiosk with Chromium displaying the octoprint page. The script works placed in root's cron @reboot however it will not return to full brightness. It stops at level 12 it seems.

Any ideas why? The script is placed in /usr/local/bin and has 120 seconds and event0 set. The screen is the only input on this Pi and it does go from off to dim when touched then off again after 2 minutes.

The behavior is the same weather in /etc/rc.local, run in terminal or in cron.

Thank you for any help!

@msweany
Copy link

msweany commented Jun 26, 2020

I know this is late, but I used this script for a Raspberry Pi project I am working on. I found it was dropping to 12, even when I changed it back to 255 manually. In the timeout.c code, it says that it grabs whatever the value is at when timeout is first called. I found that if you set the brightness right before calling timeout in run-timeout.sh, it looks like it returns to that value on boot, after touch etc...

This fixed it for me.

sudo bash -c "echo 255 > /sys/class/backlight/rpi_backlight/brightness"
nice -n 19 /usr/local/bin/timeout $timeout_period $dev &

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants