Clight icon indicating copy to clipboard operation
Clight copied to clipboard

ALS and Display backlight strange behavior

Open skynet80 opened this issue 7 months ago • 1 comments
trafficstars

Hi guys,

I use clight in my embedded linux project. I've got clightd and iiod as systemd services running. Whenver I start clight, for example by calling "dbus-launch clight &" it starts regulating the backlight and however just decreases the brightness down to 20%. Then nothing happens at all, no matter what I do, I put more strong light onto the light sensor or cover it. Any changes in the clight.config don't have impact. I have only devname = "iio:device2"; in my sensor.config and verbose=true.

Logoutput:

root@:~# dbus-launch clight dbus[761]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/wayland" is owned by uid 521, not our uid 0 Config file /root/.config/clight.conf not found. GAMMA forcefully disabled as Clightd was built without gamma support. SCREEN forcefully disabled as Clightd was built without screen support. DPMS forcefully disabled as Clightd was built without dpms support. Clightd found, version: 5.9-d4e88b1. Disarmed timerfd on fd 10. AC screen backlight curve: y = -0.024825 + 0.191641x + -0.008928x^2 BL ^ | ** | **
| *
| *
| *
| *
|
| *
|*
|
---------->BR BATT screen backlight curve: y = -0.010629 + 0.153844x + -0.007284x^2 BL ^ |
|
| *** | **
| *
| *
| *
| *
|
|

*---------->BR Set timeout of 30s 0ns on fd 15. init_kbd_backlight(): No such file or directory Keyboard backlight calibration unsupported. org.freedesktop.ScreenSaver dbus interface exposed. Disarmed timerfd on fd 33. AC cable connected. Laptop lid opened. Emitting 'AcState' property Emitting 'LidState' property Could not find location cache file. geoclue_ping(): The name org.freedesktop.GeoClue2 was not provided by any .service files Geoclue2 is not present. Set timeout of 0s 1ns on fd 15. Failed to init (no geoclue2 present?). Killing module. No location provider found; fallback to DAY daytime. Emitting 'Location' property Set timeout of 0s 1ns on fd 13. Sensor '/dev/iio:device2' is now available. Resumed as a sensor is now available. Emitting 'DayTime' property Emitting 'SensorAvail' property Captured [5/5] from '/dev/iio:device2'. Ambient brightness: 0.165. Ambient brightness: 0.165 -> Screen backlight: 0.266. Set timeout of 600s 0ns on fd 13. Emitting 'AmbientBr' property Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.75. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.70. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.65. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.60. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.55. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.50. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.45. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.40. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.35. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.30. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.27. Emitting 'BlPct' property Entering dimmed state... Emitting 'DisplayState' property Pausing BACKLIGHT: DISPLAY Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.22. Emitting 'BlPct' property Backlight 'lcd0_backlight' level updated: 0.20. Emitting 'BlPct' property

Any idea what might be wrong with my setup/configuration?

When I access both the ALS device and the backlight with cat or echo... they are available and I can see raw ambient light values and I can adjust the backlight by pushing values into its device.

Thanks a lot in advance

skynet80 avatar Apr 11 '25 12:04 skynet80

from your log see“Entering dimmed state...” , in dim mode ,the backlight adjustment not working.

Qingwu-Li avatar May 26 '25 03:05 Qingwu-Li