<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX ProcessorsのトピックRe: How to save overscan setting?</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/How-to-save-overscan-setting/m-p/260652#M25995</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thuan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is an issue my company is investigating as well. We have been told that Freescale is aware of this issue and that they are investigating it, but it is a low priority issue. If your primary display is HDMI, this is not what you want to hear. We are attempting to mod the BSP ourselves to implement this capability. A workaround that you might attempt for this issue involves modifying the Launcher app and hard coding overscan values that work for your device as below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;private static class PendingAddArguments {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; int requestCode;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Intent intent;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; long container;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; int screen;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; int cellX;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; int cellY;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; //add these definitions for overscan workaround&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; private static final int MAX_DISPLAY_DEVICE = 6;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; private DisplayManager mDisplayManager;&lt;/P&gt;&lt;P&gt;….&lt;/P&gt;&lt;P&gt;if (PROFILE_STARTUP) {&lt;/P&gt;&lt;P&gt;android.os.Debug.startMethodTracing(&lt;/P&gt;&lt;P&gt;Environment.getExternalStorageDirectory() + "/launcher");&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; //overscan workaround&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mDisplayManager = (DisplayManager)getSystemService(Context.DISPLAYMANAGER_SERVICE);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; for(int i=0; i&amp;lt;MAX_DISPLAY_DEVICE; i++ ) {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mDisplayManager.setDisplayXOverScan(i, 6);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mDisplayManager.setDisplayYOverScan(i, 6);&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;The key is calling the display manager class. You will probably need to set a value other than six for x and y overscan. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;Michael &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 22 Feb 2013 19:12:49 GMT</pubDate>
    <dc:creator>michaelrobbelot</dc:creator>
    <dc:date>2013-02-22T19:12:49Z</dc:date>
    <item>
      <title>How to save overscan setting?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-save-overscan-setting/m-p/260651#M25994</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Under Settings -&amp;gt; Display -&amp;gt; Advanced Display, there is an option for Width/Hieght OverScan.&amp;nbsp; After a reboot, this setting isn't saved.&amp;nbsp; Does anybody else have this issue?&amp;nbsp; Is there a way to preserve this setting?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 16 Feb 2013 00:05:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-save-overscan-setting/m-p/260651#M25994</guid>
      <dc:creator>thuanho</dc:creator>
      <dc:date>2013-02-16T00:05:18Z</dc:date>
    </item>
    <item>
      <title>Re: How to save overscan setting?</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/How-to-save-overscan-setting/m-p/260652#M25995</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thuan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is an issue my company is investigating as well. We have been told that Freescale is aware of this issue and that they are investigating it, but it is a low priority issue. If your primary display is HDMI, this is not what you want to hear. We are attempting to mod the BSP ourselves to implement this capability. A workaround that you might attempt for this issue involves modifying the Launcher app and hard coding overscan values that work for your device as below:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;private static class PendingAddArguments {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; int requestCode;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Intent intent;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; long container;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; int screen;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; int cellX;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; int cellY;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp; //add these definitions for overscan workaround&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; private static final int MAX_DISPLAY_DEVICE = 6;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; private DisplayManager mDisplayManager;&lt;/P&gt;&lt;P&gt;….&lt;/P&gt;&lt;P&gt;if (PROFILE_STARTUP) {&lt;/P&gt;&lt;P&gt;android.os.Debug.startMethodTracing(&lt;/P&gt;&lt;P&gt;Environment.getExternalStorageDirectory() + "/launcher");&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; }&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; //overscan workaround&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mDisplayManager = (DisplayManager)getSystemService(Context.DISPLAYMANAGER_SERVICE);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; for(int i=0; i&amp;lt;MAX_DISPLAY_DEVICE; i++ ) {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mDisplayManager.setDisplayXOverScan(i, 6);&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; mDisplayManager.setDisplayYOverScan(i, 6);&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;The key is calling the display manager class. You will probably need to set a value other than six for x and y overscan. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="mce_paste_marker"&gt;Michael &lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Feb 2013 19:12:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/How-to-save-overscan-setting/m-p/260652#M25995</guid>
      <dc:creator>michaelrobbelot</dc:creator>
      <dc:date>2013-02-22T19:12:49Z</dc:date>
    </item>
  </channel>
</rss>

