(06-20-2016, 07:17 AM)gbjensen Wrote: It helped me, I had to adjust the setting for my "Logic" TV used for my initial testing of the Pine. My Philips TV did not require any configuration changes.That's great, and good to know about the TVs.
For a (BestBuy) Dynex TV, I had to change the Overscan setting to Off). It was in the Advanced Video submenu of the Picture settings. In Linux, I really suffered with all the edges hidden, until I found that setting. I'd looked for it a couple times before I finally found it.
Android wasn't so bad, since pretty quickly, I managed to find method 2.
That experience made me decide to do a little research for other menu settings, to write the OP.
(06-20-2016, 08:36 AM)phloog Wrote: I'll likely just live with it, because I'm not sure that my main TV can adjust ONE HDMI input separately from the rest - - you would HOPE that it would, but I'm always amazed by how many features my very expensive TV does NOT have.
On my fairly cheap, BestBuy store-brand TV (Dynex), Overscan had been cutting off the borders of everything. So turning it off meant that everything improved -- Pine/Linux, Pine/Android, Netflix, Amazon, everything.
This message sent from Pine 64+, running Firefox (IceWeasel) on Debian-XFCE, and later edited from Pine 64+ using Chrome on Android Lollipop.
NexusDude of Central Texas
- Setup: Pine64+ 2GB, On/Off button, RTC battery, 5V fan, LG 1.8A power adapter, Cat6 Ethernet, HDMI to TV, USB keyboard & mouse, SanDisk Ultra mSD "32GB" (28.7GB). Using Win32DiskImager.
- Best OS experiences: Debian XFCE >> Android Lollipop > the rest