- #ASUS BRIGHTNESS CONTROL DRIVER HOW TO#
- #ASUS BRIGHTNESS CONTROL DRIVER UPDATE#
- #ASUS BRIGHTNESS CONTROL DRIVER FULL#
- #ASUS BRIGHTNESS CONTROL DRIVER WINDOWS#
It was slightly different, because it had a second screen on the back, which could be used as a tablet and thus they already had issues with having them both turned on at the same time. I've come across similar issues with another Asus notebook from 2014, the Taichi31. The problem is the linux kernel doesn't expect two internal displays, so it's not available by default. It being a LED/LCD display however, means it should be controllable through ACPI just like any other display I think.
#ASUS BRIGHTNESS CONTROL DRIVER FULL#
While the top screen is at least already consuming less energy using this method (because of how OLED works), the bottom screen will still consume full energy when using xrandr/icc-brightness since it's a LED/LCD display.
This is already helpful for me to brighten up the bottom screen seems like it's set to 0.75 by default (at least for me) which is not bright enough in daylight conditions at the office. I had tested the xrandr thing to dim the bottom screen and - yes this works. Using the cli directly instead of the watch/service causes no flicker, so my assumptions about something else (probably GNOME related) trying to adjust brightness (and failing) when I use the buttons right before icc-brightness does its thing is probably correct. So it's definitely possible to target the screen with the techniques the tool uses.
#ASUS BRIGHTNESS CONTROL DRIVER HOW TO#
But I have not got a lot of experience with WireShark apart from actual network diagnostics and I have trouble finding guides on how to apply it for something else then network readings :)Īfter another reboot and icc brightness is changing the brightness of my bottom screen again.
#ASUS BRIGHTNESS CONTROL DRIVER WINDOWS#
If I can find out how, I will try and figure out how windows is setting the brightness. There is multiple threads on "why doesn't linux kernel support brightness controls on OLED panels yet" and one of them actually mentions a laptop from System76, shipping with PopOS that has an OLED panel and the brightness control works out of the box on it. When I have time I will see how it behaves when I use the command line instead of the buttons to confirm my suspicions.Īlso, while reading this I think using ICC or xrandr is probably the only existing solution we will be able to use for the main display, as it would be related to the panel being OLED. I suspect the display (or gnome) is responding to me pressing the brightness button (but just setting max brightness because it doesn't know better) right before the icc-brightness watch kicks in. With the main display it is even clearer the flicker is really the panel changing to max brightness for a split second right before it drops to the new requested value. Since you're not experiencing the flicker I suspect it has something to do with GNOME (I'm using PopOS).
#ASUS BRIGHTNESS CONTROL DRIVER UPDATE#
+0070 70 26 30 20 30 20 35 00 58 63 10 00 00 1a 00 bb p&0 0 5.Xc.Īn update on using icc-brightness: after using the clean command, it now controls my main display instead of the ScreenPad Plus. Video input definition: 0xa5 - Digital Input (DisplayPort) Video input definition: 0xb5 - Digital Input (DisplayPort) I2C address 0x30 (EDID block#) present: false
0 kommentar(er)
