Totally agreed! This most likely is an Intel driver bug. However almost all the posts describing this issue are isolated to FrameWork laptops for the very reason you just described: privacy as a feature causes the Intel driver to do things it shouldn't. - Though my opinion still hasn't changed, Intel should have never even made this "dynamic contrast" crap in the first place!
Give me a MacBook Pro or give me death! Great find and funny workaround. I wonder if they normally use the webcam for brightness detection and/or if FrameWork uses something else and that's the triggering mechanism.
On this particular laptop, there is an ambient light sensor which is always activated. The web cam (and mic) have physical toggle switches that electrically disconnect them, rather than "disable" them. Intel's driver detects no webcam, so assumes the ambient light feature wont work, but that same driver also sees the ambient light sensor, so it works. So in THAT context, I think it was just a small oversight of IF statements in different parts of the code... BUT THE FEATURE STILL MAKES THINGS LOOK LIKE HORSESHIT and shouldn't have existed in the first place LMAO
@@circuitrewind Yeah - definitely a programmer oversight. I agree it should be off by default. TrueTone on apple devices is another big issue - changes color while you're trying to color grade photos/video based on what it thinks it should be.
Does this behave the same in non-Windows OSes? My Framwork is still the 11th-gen Intel, and the screen has never been anything short of brilliant when running Ubuntu.
I personally don't run Linux on my systems, but I've not observed this behavior on FreeBSD. And from what I know, Linux and FreeBSD use virtually the same Intel GPU driver (with just different OS kernel bindings). This also never happened in ANY OS on my 11th Gen motherboard, it only popped up when I upgraded to the 13th gen!
![CAMPปลิ้น | EP.82[2/2] เมาท์มอยกับ 3 สาวเพื่อนซี้ ที่พร้อมขยี้พ่อหมีได้ทุกเมื่อ](http://i.ytimg.com/vi/Wwn7WnylNtQ/mqdefault.jpg)
I was thinking "weird" i dont have this isssue with my framework, but then i realized that ive got an AMD machine
Yeah, this didn't exist when I had the 11th Gen Intel motherboard installed either. Not sure if 12th Gen does this, but its certainly board specific!
This is clearly an Intel bug. Really sucks that this is Framework's problem now just because they're the only ones with a switched webcam.
Totally agreed! This most likely is an Intel driver bug. However almost all the posts describing this issue are isolated to FrameWork laptops for the very reason you just described: privacy as a feature causes the Intel driver to do things it shouldn't. - Though my opinion still hasn't changed, Intel should have never even made this "dynamic contrast" crap in the first place!
Hi, new to your channel, why do you use windows? isn't freebsd able to run a desktop environment?
@@BrijeshWawdhane-jm2pz I use both, and several others too. I'm not married to any one ecosystem.
Now I am wondering. When you turn the camera back off does it turn the feature back on?
@@leonmerts702 the feature remains off. However the setting in the UI also disappears again!
Give me a MacBook Pro or give me death! Great find and funny workaround. I wonder if they normally use the webcam for brightness detection and/or if FrameWork uses something else and that's the triggering mechanism.
On this particular laptop, there is an ambient light sensor which is always activated. The web cam (and mic) have physical toggle switches that electrically disconnect them, rather than "disable" them. Intel's driver detects no webcam, so assumes the ambient light feature wont work, but that same driver also sees the ambient light sensor, so it works. So in THAT context, I think it was just a small oversight of IF statements in different parts of the code... BUT THE FEATURE STILL MAKES THINGS LOOK LIKE HORSESHIT and shouldn't have existed in the first place LMAO
@@circuitrewind Yeah - definitely a programmer oversight. I agree it should be off by default. TrueTone on apple devices is another big issue - changes color while you're trying to color grade photos/video based on what it thinks it should be.
Give me user upgradeable memory and storage or give me death! Sorry, couldn't resist.😂
100% totally agree! (Sent from my MacBook Air M1, my absolutely most used computer)
Does this behave the same in non-Windows OSes? My Framwork is still the 11th-gen Intel, and the screen has never been anything short of brilliant when running Ubuntu.
I personally don't run Linux on my systems, but I've not observed this behavior on FreeBSD. And from what I know, Linux and FreeBSD use virtually the same Intel GPU driver (with just different OS kernel bindings). This also never happened in ANY OS on my 11th Gen motherboard, it only popped up when I upgraded to the 13th gen!