4 ms·
I suppose it's a type of problem that solves itself: If companies are dumb enough to store brightness settings in EEPROM, they're only doing it because no one u
by arghwhat 6y ago
I suppose it's a type of problem that solves itself: If companies are dumb enough to store brightness settings in EEPROM, they're only doing it because no one uses DDC/CI.
Use DDC/CI, and they'll stop. Even NAND is wrong if brightness is actually dynamically controlled, it should just be RAM.
- toomuchtodo 6y agoAhh, but this information needs to make it to consumers so they don't get stuck with dud monitors that have internal storage that rapidly wears. How, as a consumer, do I know which monitors store settings in such a manner and therefore avoid them when making purchasing decisions? Perhaps Lunar and Flux could make monitor recommendations with affiliate links, Wirecutter style. I don't want to have to research, just tell me what works best so I can pull my credit card out.
- arghwhat 6y agoYou don't. Such monitor recommendations could only be based on people tearing down things, which is outside the scope of Lunar and f.lux. There is never a guarantee that you don't get stuck with a dud monitor, in any aspect. However, companies making products with bad reliability is going to face high support/warranty fulfillment costs and get a bad reputation. And if it fails within warranty/consumer protection periods, you lose nothing. So, write away, and flood bad manufacturers in complaints. It's all you can do as a consumer - the alternative boing to get AMD, nVidia or Intel (or Displayport/HDMI interest forums) to be interested in making requirements against display manufacturers on the matter.