Great news everyone!
u/crt09 has managed to wake their Studio Display using WinI2C! Apparently, by pressing the "Standby Test" button, the appropriate wake up signal* is sent and the Studio Display starts displaying a picture. In the same
post,
@Synceen also found out that the Studio Display supports any resolution as long as it has an 80kHz horizontal frequency. Looks like we've finally cracked the nut and freed these beautiful monitors. Thank you all for your contributions!
*The only caveat of this solution is that it only works on Windows and macOS machines, still, loads better than having to use a G4 era mac! With that said, I'd still like to figure out what the signal actually
is. A cursory look at the tools provided in the Hackaday post leads me to believe that the Studio Display manages its power state through appropriate DPMS requests, but I still haven't been able to test that since I can't communicate with my Studio Display. I'm not sure if it's because of an incorrect connection or if it's due to a noisy power supply. Apparently the I2C bus is quite delicate and even very slight voltage fluctuations can disrupt communication. I've noticed that I can "feel" some current whenever i slide my hand on my laptop.
Also, to answer
@Titania , I have a feeling that the reason why ddcutil fails to detect the Studio Display is that it simply doesn't reply to DDC requests. If you think about it, the DDC lines in the Studio Display see very little use. They're only used to transmit the EDID information and the wake up signal. That would explain why Apple didn't bother fully implementing the standard. I believe you can force ddcutil into sending a command by specifying the bus that the Studio Display is connected to. I'll be trying that as soon as I can get mine working.