Thuan,
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:
private static class PendingAddArguments {
int requestCode;
Intent intent;
long container;
int screen;
int cellX;
int cellY;
}
//add these definitions for overscan workaround
private static final int MAX_DISPLAY_DEVICE = 6;
private DisplayManager mDisplayManager;
….
if (PROFILE_STARTUP) {
android.os.Debug.startMethodTracing(
Environment.getExternalStorageDirectory() + "/launcher");
}
//overscan workaround
mDisplayManager = (DisplayManager)getSystemService(Context.DISPLAYMANAGER_SERVICE);
for(int i=0; i<MAX_DISPLAY_DEVICE; i++ ) {
mDisplayManager.setDisplayXOverScan(i, 6);
mDisplayManager.setDisplayYOverScan(i, 6);
}
The key is calling the display manager class. You will probably need to set a value other than six for x and y overscan.
Michael
