Addressing overscan issues.
The reason why overscan does not effect the stock Ouya is simply put they placed all of their lettering near the center of the screen for all of their actions. Leaving a large margin produces less of a need for a user to demand overscan to really be fixed.
Flat panel televisions are designed a little differently then regular computer LCDs. Sometimes the picture falls off of the screen known as overscan. Because in most android environments such as Lineage, ASOP, and Cyanogen. Items and status bars are placed on the edge of the screen resulting in preventing the user from really seeing what is going on.
Overscan fix in Cyanogen.
For Cyanogen you will need an ADB shell and/or a Terminal application to login to the android shell locally.
su setprop persist.sys.hdmi.overscan 1
setprop persist.sys.hdmi.overscan.val [example: 0.0 – 0.2] The value is a minimum of 0.0 and a maximum of 0.2 for overscan compensation. As an example. My 32″ Vizio my overscan settings are as follows:
setprop persist.sys.hdmi.overscan.val 0.02
And my Apex 27″ is as follows:
setprop persist.sys.hdmi.overscan.val 0.13
The value of your flat panel TV may be different then mine so adjust accordingly.
you will have to reboot in order for your adjusted overscan values to take effect.
Fix for Lineage OS and ASOP.
Interesting ASOP 5.0 and Lineage both behave the same about this where the setprop commands no longer work. We will also need ADB shell for this but a few settings must be setup in the settings menu of Android to make this work or else nothing will happen.
For this we will need to access out android “Settings” icon and scroll all the way down to “About tablet.” Then, arrow down to build number and click on it 5-6 times and the “Developer options” window will appear.
Change Root access so that Apps and ADB are selected.
This will now give us the appropriate access to pass shell commands that can effect the system. Jump into Android shell or “adb shell” if you are doing this remotely and type in the following.
adb shell wm overscan 15,30,10,20
The breakdown of this is: wm overscan <<<Left>>,<<Top>>,<<Right>>,<<Bottom>> . The example used above is what we did for our monitor. It should also be noted that this command unlike the classic setprop command only effects the launcher and that apps and games may ignore this setting all together.
Anyhow, hope this helps with overscan issues and whatever box your running be it Ouya or something else.
+++ END OF LINE