That is not the issue as we keep saying, ITS THE UNITS!!!!!!!!!!!
You are exactly correct and here is the following test and settings proving where the problem really is found compared to two other popular streaming devices:
This is a lead I discovered on what's causing the persistent "Overscan" problem many have been frustrated with regardless of the settings on their varying TVs for the last few years. It appears to me to be an automatic/inflexible/static/hardcoded signal coming FROM the Roku itself that overrides the TV's over-scan setting that keeps forcing the problem on some LCD TVs.
I can recreate and solve the problem on a Best Buy branded INSIGNIA television using two other competing streaming devices by changing ONE setting that is NOT available on either my updated Roku StreamingStick 4k OR Streambar Pro.
Example 1: On a "Chromecast with Google TV" there is a "Color Format" setting under "Dynamic range & Color format" that also causes the overscan when using YCbCr 12-bit or 8-bit. SETTING COLOR FORMAT TO RGB 8-BIT SENDS A SIGNAL THAT DOES NOT FORCE OVERSCAN. Roku devices don't have a setting to change "color format" so the problem continues.
Example 2: On an "Apple TV 4K" there is an "HDMI Output" setting that again causes the overscan problem when using YCbCr. SETTING HDMI OUTPUT TO EITHER RGB HIGH OR LOW SENDS A TV SIGNAL THAT DOES NOT FORCE OVERSCAN. Roku devices don't have a setting to change "hdmi output" so the problem continues.
In other words, Roku streamers do NOT have an equivalent USER setting to be able to SEND a RGB signal to any TV to solve the problem. Even if the TV has its own "overscan off" setting, it is still overridden by the hdmi signal coming FROM the Roku. So after all this troubleshooting the user question remains, why do the other two primary competing streaming devices have this convenient user setting that solves this problem but the Roku does not?
Wow, good find. But are you sure it's not your tv turned on its side or placed sideways or some other idiotic excuse they keep trying to serve rather than, as you said, fixing their hardware. Oh but wait that would be admitting its their fault. We can't have that now. It always HAS to be the user's equipment or be a Tuesday with a full moon.
You do see my point. The fact that Im able to change the TV overscan response by changing a single setting on the other two competing devices proves that the issue is "baked" into the roku and its signal output because of the lack of a comparable setting.
You might find it interesting that I've yet to see any moderator here acknowledge or reply to any posts documenting this proof test base find this week.
It's your TV. The overscan is normal on HDTV's receiving what is in a broadcast TV video format, YCbCr. The TV set is what converts that signal to RGB. It may allow underscan, or zero overscan, when presented with an RGB signal from a PC, or a device with that type of format.
You'll find no problem with this with even an entry level 4K set. You can find a workaround with a different device that outputs an RGB signal to your HDTV. Or you can put in a feature request to a manufacturer to add RGB output over HDMI not for compatibility, but to "enhance" the viewing area by 1 or 2 % on what are essentially obsolete displays, while providing no advantage to current and future 4K sets when HDMI bandwidth can be conserved by using YCbCr with 4:2:2 or 4:2:0 sampling over the uncompressed 4:4:4 or RGB formats, especially at 30 and 36 bit depths.
Good luck with that last one, though.
