> The 1080p60 bug can be fixed by cutting the plastic lid off the Chromecast and adding a fan.
I can't tell if you are serious.
I can imagine circumstances where this would work, but... they involve the chromecast having a temp sensor and software to lower the clock speed to prevent overheating, resulting in skipped frames, but at the same time somehow not be able to lower the bitrate of the video stream.
There is an extra element here... All of what you said is true, but the actual issue is not with the video decoding, but with the thread that feeds data from the network to the video decoder. That thread has some long running stuff running on it, which causes the task to enquire data to the video decode hardware to be delayed.
It used to work years ago, but as more and more software bloat has been added to run in this thread, the delays have increased to the point of stutteryness.
Some videos are jumpy because they have fewer seconds buffered in the hardware decoder.
Fan leads to the CPU throttling less, so the long-running events on the main thread run faster and delay the tasks that load data into the video decoder less.
Pretty much every single processor made in the past decade, if not two, has a core temperature sensor along with overheating regulation. Even the Raspberry Pi.
Typically embedded linux systems use the linux CPU frequency scaler, which uses various inputs including CPU temperature to scale the CPU clock frequency.
I can't tell if you are serious.
I can imagine circumstances where this would work, but... they involve the chromecast having a temp sensor and software to lower the clock speed to prevent overheating, resulting in skipped frames, but at the same time somehow not be able to lower the bitrate of the video stream.
Seems... mildly improbable.