dblazie
commented
8 years ago When I attended a Google I/O conference a few years ago, I was told by one of the platform developers that we could get around this overscan issue by changing a parameter in a call to one of the Accessibility modules. I documented this in an email to Zone24 but I have yet to find it. It has to do with the screen magnification feature in Android that was added by the accessibility group. It would be good to find this and give it a try. Low priority.
Deane
On Tue, Jan 12, 2016 at 3:25 AM, Ruvinda Dhambarage < notifications@github.com> wrote:
Approximately 8 columns of pixels on the left edge are lost due to over-scanning.
On devices like the original Raspberry Pie, the video driver provides a configuration file which allows the users to add offsets to compensate for this over-scanning issue. The Beagleboard BSP driver doesn't include this capability. Modifying the BeagleBoard BSP driver to is non-trivial and was decided that payoff is not worth the effort.
We reported this issue to the TI support forums here: https://groups.google.com/forum/#!searchin/beagleboard/$20Out$20image$20cropped$20on$20composite$20video$2Fs-video$20out/beagleboard/KbWMebhJ5jM/KUhceRkL-vsJ But could not get a solution through them.
— Reply to this email directly or view it on GitHub https://github.com/b2gdev/Android-JB-4.1.2/issues/2.
Approximately 8 columns of pixels on the left edge are lost due to over-scanning.
On devices like the original Raspberry Pie, the video driver provides a configuration file which allows the users to add offsets to compensate for this over-scanning issue. The Beagleboard BSP driver doesn't include this capability. Modifying the BeagleBoard BSP driver to is non-trivial and was decided that payoff is not worth the effort.
We reported this issue to the TI support forums here: https://groups.google.com/forum/#!searchin/beagleboard/$20Out$20image$20cropped$20on$20composite$20video$2Fs-video$20out/beagleboard/KbWMebhJ5jM/KUhceRkL-vsJ But could not get a solution through them.