Originally Posted by Eva2016
I agree with you, it is too big of an issue just to be ignored.
I understand LG wants to be careful, but at the end of the day this is firmware update to fix just one single issue for which the solution has been already provided, there´s nothing else they have to "update".
When did Dolby supply the fixed code to LG? It sounds like it was fairly recent based on the Forbes article.
Integrating third party code, and then running a full test suite and regression on all of the 2016 and 2017 LG OLED models, with all of the their variations in regional firmware, different apps etc is a lot of work. After QA signs off, LG probably push the firmware out to an alpha group first, and wait for reports, then to a beta group, and more waiting. Finally, we get it!
Not to mention, it's quite possible the Dolby fix is stuck in the queue behind some other important LG releases, like the firmware for the 2018 models, which is probably on a tight timeframe tied to LG's manufacturing plant and can't easily be changed without costing them millions. I doubt LG has excess capacity in their software development teams.
Also, it's never just 'one single issue'. At a previous gig, we received an urgent security patch to a critical piece of third party software. Unfortunately, the patch was bundled with a entirely new version of the Mono runtime that introduced numerous changes across our software environment. It took us months of engineering and testing to make that change without breaking anything, just for 'one single issue'.