Disable Adaptive Brightness 2021 PERMINATELY??

Member Posts: 3 New User
Anytime I am on a darker chrome page, the entire screen dims, and when my hand hovers over the sensor as I type, the screen will dim.  (Horrible placement for the sensor)
ABSOLUTELY nothing works to disable this.  I have tried everything, Intel settings, power settings, disabling my sensor (services.msc), Chrome settings etc etc.  Is this a known issue with Acer?? It will be my last Acer purchase if so.

Device name Work-Acer
Processor Intel(R) Core(TM) i3-8130U CPU @ 2.20GHz   2.21 GHz
Installed RAM 6.00 GB (5.88 GB usable)
Device ID C61A76D5-0B2C-44DA-BD6A-8F8193D0BDF6
Product ID 00325-80118-74228-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display

Answers

  • Leostat
    Leostat ACE Posts: 3,043 Pathfinder
    Assuming that windows is ignoring the addvie brightness settings in the graphics pannel (if its even still there!)  In the intel control panel, is there any power options hidden away?

    There may be an option along the lines of enhanced power saving or intel dynamic power control or display power saving, thats what intel called their adative brightness who knows why 🤷‍♀️ there may also be a option for the power plan in there (not the windows power plan) which if you select max performance it sometimes disables it. Could you post a screen cap of it incase they have changed the name of the setting again!
  • Member Posts: 3 New User


    Supposedly Acer "Quick Access" is supposed to have a setting for this as well... it does not.


  • Leostat
    Leostat ACE Posts: 3,043 Pathfinder
    Humm thats a tad odd, i wonder if intel have broke it again. Whats the version of the driver you have for the iGPU?
  • Member Posts: 3 New User
    Leostat said:
    Humm thats a tad odd, i wonder if intel have broke it again. Whats the version of the driver you have for the iGPU?
    Intel(R) UHD Graphics 620
    Driver version: 23.20.16.5038
    Driver date: 04/18/18
    DirectX version: 12 (FL 12.1)

    The issue seems to have now gone away, but I have ZERO idea why it stopped and when it will return... it always does....