I'm testing as many MacBooks as possible. Here are the results.
macsforme yeah, pretty sure at that stage it's at least partially psychological. I'm literally scared to update any usable device at this point.
Interesting note, again proving my point that it's 100% software related, is that using "safe mode" makes it tolerable. Not ideal, but not as harsh as in regular mode. Most likely some sort of hardware acceleration is disabled.
Here's AHKinject_SCN078.dmg
https://mas-fx.filemail.com/d/sofofeusdcicyvs
Really interested if this works for you. Please report back! I tried on a 2019 16" MBP with Sonoma and didn't seem to work. See above. Let us know if this works on your 15"!
RobC I currently have four of these machines. All four return only "Color LCD" for that command. Three of the four (including the one I subjectively find most comfortable) return the exact same entire EDID string, while the fourth is not a byte-for-byte match but when parsed by edid-decode all values still appear to be the same. If the ability to see more panel info returned on later Macs, that is good news and may be helpful to us here.
JTL I suspect you are right about VBIOS being stored on the main firmware chip (especially the Intel integrated VBIOS, but likely the discrete AMD VBIOS as well). My initial tests consisted of reconstructing an old firmware image (with some help from some guys on the MacRumors forums) from a combination of donor dumps found online and Apple's own .fd firmware images from their macOS installers (specifically an old version from the El Capitan era). While this seems like it should include an older GPU VBIOS, my preliminary testing did not seem to show any differences in GPU info listed in the OS between old and new firmware versions on this model (although there is still more testing to do). Also interestingly, someone on this board (maybe you? 
) found an "AMDFirmware" update script in macOS installers, which seemingly suggests an AMD VBIOS update outside of the main firmware, but that could also be for different GPU models (such as those in desktop machines).
macsforme Did you tried with the following version of the command?
ioreg -lw0 | grep IODisplayEDID | sed "/[^<]*</s///"
If you put every answer line into an edid-decoder like this one: https://hverkuil.home.xs4all.nl/edid-decode/edid-decode.html you could get much more details of your panels, like the vendor and date in which they were manufactured among others.
RobC Yes, I tried the command as you posted it. As I stated, all the info is the same when parsed. Manufacturer: APP; Model: a02e; Made In: week 4 of 2015; Serial Number 0; Monitor Name: Color LCD.
- Edited
RobC This command does not work on Macbook Air m2 13. If I remove EDID part I would bunch of variables and then last two IODisplayParameters and IODisplayWrangler. Otherwise there is no EDID information available. Any ideas how I could check out my panel manufacturer? This could potentially be a game changer, since I could buy used macbook and ask to check this information before buying to make sure panel is not some mickey mouse design.
Sonnis Could you please tell what is the panel manufacturer of this laptop you have used? - "MBP 14" M1 Pro" which caused very minor symptoms for you. This could be a really good purchase once the panel details are known, since on the second hand market these laptops already going quite cheap, yet still very powerful.
macsforme I suspect you are right about VBIOS being stored on the main firmware chip (especially the Intel integrated VBIOS, but likely the discrete AMD VBIOS as well). My initial tests consisted of reconstructing an old firmware image (with some help from some guys on the MacRumors forums) from a combination of donor dumps found online and Apple's own .fd firmware images from their macOS installers (specifically an old version from the El Capitan era).
If you have any forum threads or information from elsewhere I might be of interest.
If you sent me the firmware dumps/images in question I might be able to take a look as well.
Also interestingly, someone on this board (maybe you?
Not sure I recall that exactly, but what I do remember is some desktop Mac systems used GPUs similar to the same model as commodity PCs but had "Mac Edition" VBIOS firmware for them and it's a thing to flash cards sold for PC use with "Mac Edition" VBIOS's to improve Mac compatibility. So that's some prior art for differences between Mac and PC VBIOS's, but considering what else I said I wouldn't be surprised if the situation with Macbook's is different enough that might not be relevant.
Donux In your case try:
ioreg -lw0 | grep IODisplay | sed "/[^<]*</s///"
If you put every answer with the "00ff…>" format into an edid-decoder like this one:
https://hverkuil.home.xs4all.nl/edid-decode/edid-decode.html
you could get much more details of your panels,
MAS-76 Thank you for sharing!
I found this documentation (see link) for AHKinject_SCN078.dmg on the internet. The document is from 2016. So I maybe the DMG was build for older MacOs versions, perhaps you can try to downgrade to MacOS (Catalina?) and try again. I currently don't have a macbook with amd card, but I am going to look if I can find one to try.
JTL This is the post from you I remembered. After a cursory look, those firmware payloads look like they're possibly for later Macs (iBridge references, web searches returned AMD Vega references, etc.), so not affecting my 2015 machines. I also found a few posts here suggesting that later 2015 MacBook Pro display panels replaced by Apple due to "staingate" may be harsher on the eyes. I can also confirm that one of my 2015 machines has a harsh panel while another has a calm panel (subjectively). The other two have not been tested extensively yet.
So far I have not found good/bad machine differences that I can confidently attribute to firmware (my research continues). If I discover anything, I would be happy to collaborate over analyzing the differences.
MAS-76 @Hunter20
I have 2019 16'' with Radeon Pro 5300M
Running Ventura 13.6.1
Was able to load the kext fine
$ kextstat | grep -v apple
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address Size Wired Name (Version) UUID <Linked Against>
178 0 0xffffff7f971eb000 0xff6 0xff6 com.amulethotkey.driver.ahkinject (1.1.1d1) C89AB321-97E6-3C86-ACBA-6498B6DCC100 <6 3>
tbh I'm not sure if I see/feel any difference.
btw I'm also using BetterDisplay, with the virtual screen the screen already felt more "static", thus not sure if that was already disabling dithering, so I do not see further improvements.
Oh yes that.
I see two possibilities here.
1) It's for later desktop Mac hardware.
2) It's for later laptop Mac hardware (as well), because as my later understanding indicates most laptops store the VBIOS as part of the system firmware and not on a separate flash like a desktop GPU.
So far I have not found good/bad machine differences that I can confidently attribute to firmware (my research continues). If I discover anything, I would be happy to collaborate over analyzing the differences.
If you PM me we can discuss analysis of firmware. Door's always open 
- Edited
Very bad news from me. The combination macbook air M2 + OLED monitor has been giving me major migraine problems since Saturday. I don't understand what happened, the version of macos is always 13.5, I haven't updated anything. Do you have any ideas? I am desperate, it was the only PC I could use without medication 
I could update to Sonoma but i don't understand what happened aaaaahhhhhhh
SMC and NVRAM reset maybe?!
