-
Notifications
You must be signed in to change notification settings - Fork 19
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
My laptop has a different file for the illuminance sensor (/sys/bus/iio/devices/iio\:device1/in_illuminance_input
)
#13
Comments
thanks for update, I will change the README. My last laptop with illuminance sensor is 10 years old now, and I don't have access to anything modern. What range of values do you see in this file? |
Btw, after rebooting it's no longer Here are some tests
I can add a value for being outside when the brightness usually needs to be set to max. |
I checked my laptop and I have the light sensor device in iio bus too, are you sure what you don't have it in acpi bus directory? I think acpi bus names are more stable than iio. But if you have the sensor only in iio bus it will mean that I need to search for the illuminance sensor on the start. Can you also check which driver is used for it? |
I don't think the light sensor is in the acpi bus.
I'm not sure about which driver is used by it. It might be the |
can you run |
I looked at the file and only one alternative path is through |
Yes, I would like to try illuminanced on my Chromebook. |
I finally have found time to make and test the change, also created a branch for you with your path to the illuminance file. |
I'm using NixOS so I can't test it rn. Sometime I'll test it on a normal Linux distro or create a Nix package for it. |
The section "How to test befor install"
doesn't work for my laptop (HP Elite Dragonfly Chromebook, code name
redrix
), even though it does have an ambient light sensor which I can read withcat /sys/bus/iio/devices/iio\:device1/in_illuminance_input
Should the README be updated?
The text was updated successfully, but these errors were encountered: