Android Resize Resolution / Calibrate Screen Height & Position

Search This thread

Pezik

Member
Dec 26, 2005
13
0
Hello, i have the 1cm dead touchscreen zone in the top and bottom, not good for the android taskbar...

Can we recalibrate the resolution / screen parameter to reduce a little the screen height to fix the problem ??

Thank you.
 
Last edited:

I7V

Senior Member
Jul 21, 2010
252
31
35
yeeeeeeeeeeeee .. after month or more looking for solution and tried everything on web i finally found it broo
download from the play store NOmone resolution changer and use it
our default settings is 1024 768 160
u just change the first number i use 880 768 160
as i have 2 cm below of dead touchscreen :S
i hope this works for u
 

Pezik

Member
Dec 26, 2005
13
0
yeeeeeeeeeeeee .. after month or more looking for solution and tried everything on web i finally found it broo
download from the play store NOmone resolution changer and use it
our default settings is 1024 768 160
u just change the first number i use 880 768 160
as i have 2 cm below of dead touchscreen :S
i hope this works for u

Than You, i had no success with NOMONE Resolution Changer, impossible to install for me tough Play Store (not allowed in my country) and the multiple apk found on the net was not good, an error 'probleme with parsing installer' something like this.

I found "Resolution Changer Pro" who work very well, the perfect resolution for me is : 970 x 768.
 

silvake

Senior Member
Mar 5, 2010
65
5
Bucharest
Or even easier, use a simple adb debug shell command:

Code:
adb shell
wm overscan 0,300,0,400
For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
The above command will shrink the useful screen area with 300px from top and 400px from bottom.
Feel free to experiment those parameters to find the best fit for your situation.
 
  • Like
Reactions: burningwipf

eric_thefool

New member
Apr 23, 2014
2
0
Hi guys! I start to thank you a lot for your suggestions but before making any disaster i should be really grateful if you could give me an help.
I need to resize the screen of my Nexus 7 (2013) in order to fit with the car-dash enclosure where i'm willing to install it.
The enclosure i bought was supposed to fit for the nexus display but regrettably whilst the latter is of abt 15.3cm wide x 9.5 cm "tall" (sorry for my english) the enclosure has a window of 15.3 cm wide but only 8.7 cm tall which would make impossible the access to the softkeys.
In view of the above and considering also that there is no space available to enlarge the window of the enclosure i thought and hoped it would have been easier to resize the screen.
Now the question is: considering that the measures reported are relevant to the device in landscape mode may i kidly ask you the command variables that i have to amend to cut off the 0.8 cm on the bottom side of the screen (again landscape mode).

Thanks a lot in advance for your help!
 

davis_llb26

Senior Member
Nov 5, 2011
78
7
Quito
Hello, Please i need help. I have a Dead Touch Zone (at the bottom 30% aprox.), i installed and i resized screen with ADB (adb shell wm overscan 0,0,0,600) BUT... I can´t use some apps (google play, whatsaap, etc) because it shows like they are behind backgroud.. Check pics attached for understanding.
 

Attachments

  • C1.JPG
    C1.JPG
    54.1 KB · Views: 1,685
  • C2.JPG
    C2.JPG
    41.2 KB · Views: 1,774
  • c3.JPG
    c3.JPG
    30.3 KB · Views: 1,771
  • c4.JPG
    c4.JPG
    29 KB · Views: 1,632
  • c5.JPG
    c5.JPG
    31.9 KB · Views: 1,487
  • c6.JPG
    c6.JPG
    26.3 KB · Views: 1,419
  • C7.JPG
    C7.JPG
    33.4 KB · Views: 1,370
  • c8.JPG
    c8.JPG
    36.6 KB · Views: 1,472

imkmzzz

New member
Nov 23, 2017
1
0
Hello, Please i need help. I have a Dead Touch Zone (at the bottom 30% aprox.), i installed and i resized screen with ADB (adb shell wm overscan 0,0,0,600) BUT... I can´t use some apps (google play, whatsaap, etc) because it shows like they are behind backgroud.. Check pics attached for understanding.



Did u get through with this problem..??
i too have the same problem but mine is 25% of the screen so i can use whats app and all other app but the plain box is disturbing me too...
 

TrinityTrip54

Member
Jun 26, 2012
5
1
Confirm the adb route works without root!

Or even easier, use a simple adb debug shell command:

Code:
adb shell
wm overscan 0,300,0,400
For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
The above command will shrink the useful screen area with 300px from top and 400px from bottom.
Feel free to experiment those parameters to find the best fit for your situation.

A long time since the original post and answers, but I thought it should be noted that this method works well. Thanks silvake.
My Mecer tablet stopped responding in the top 2-3cm after many years of loyal service. Could have been a drop or simply age. It is still useful and wish to give it to someone in need. So searching around and several different sites yielded some results. Note this is not a mainstream device so rooting was not an option nor attempted. Indeed drivers and any info is sparse for this device.

For anyone attempting this, I will outline my method and steps.
1. Enable USB debugging. There are many tutorials. Settings->About->Build number(tap x 7); Developer Options->USB debugging
2. Connect device with USB Cable. Give permission on device. You will need to make sure that windows installs drivers. At first windows failed to install all drivers. Not sure how it managed, but it connected eventually.
3. Download adb: https://android.izzysoft.de/downloads.php. I used https://android.izzysoft.de/downloads.php?file=adb-binaries-windows-29.0.4.zip. Decompress to desired folder. Open cmd to the folder.
4. Run adb.exe with 'adb devices' and confirm device is listed. First attempt showed:

D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
0123456789ABCDEF unauthorized


I had to give permission on the device. Reconnected USB.

D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
List of devices attached
0123456789ABCDEF device


Success! Device is now connected.
Next get the current display stats:
Type 'adb shell'
Confirm connection. Mine showed: root@800P31C:/ #
Type: ‘dumpsys display | grep mBaseDisplayInfo’
Below is the capture of the operation:

D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
root@800P31C:/ # dumpsys display | grep mBaseDisplayInfo
mBaseDisplayInfo=DisplayInfo{"Built-in Screen", app 800 x 1280, real 800 x 1280, largest app 800 x 1280, smallest app 800 x 1280, 55.84 fps, rotation0, density 190 (190.0 x 190.0) dpi, layerStack 0, type BUILT_IN, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}


This is not really required but helps to determine the current stats to make a guess on the number of pixels to adjust the screen by.

Next is the command to adjust the screen. The 4 numbers are the coordinates. Since mine was the top area I adjusted only that.
Type: wm overscan 0,50,0,0
The update is live and you should see the screen drop 50 pixels from the top.
This was not enough for me so repeat until the pull down of the status bar starts working again.
Here is the whole list to adjust the screen until everything is working again:

D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
root@800P31C:/ # wm overscan 0,50,0,0
root@800P31C:/ # wm overscan 0,70,0,0
root@800P31C:/ # wm overscan 0,80,0,0
root@800P31C:/ # wm overscan 0,100,0,0
root@800P31C:/ # wm overscan 0,200,0,0
root@800P31C:/ # wm overscan 0,120,0,0
root@800P31C:/ # wm overscan 0,140,0,0
root@800P31C:/ # wm overscan 0,150,0,0
root@800P31C:/ # wm overscan 0,160,0,0
root@800P31C:/ # wm overscan 0,170,0,0
root@800P31C:/ # wm overscan 0,180,0,0
root@800P31C:/ # wm overscan 0,190,0,0
root@800P31C:/ # wm overscan 0,195,0,0
root@800P31C:/ # exit


So I had to move the screen 195 pixels down until the dead touchscreen area was excluded.
Screen is obviously smaller but the frustration of having to rotate the device 180 to be able to pull down the status bar is removed. Much worth it.
Now a child in need of education can still learn and we have saved the device from landfill and reduced the carbon footprint.

You might have to adjust the pixel density to compensate for the loss, but I left it untouched. Your results will vary so I cannot assist.
Excerpt from another site:
"Additionally decreasing the density through the settings (Display & lights > screen > LCD density) or the wm command helped compensating for the lost display area:
wm density 360"

Hope this helps someone as it helped me.
T
 
  • Like
Reactions: Jaromor
Nov 2, 2022
17
0
Hello amazing people,

I am looking for your guide/advice for solving a screen resolution issue.
I am using a 4:3 ratio screen with a LCD driver on Radxa Zero.

the poblem is that the screen looks stretched laterally. I think its due to aspect ratio becuase the lcd is of 4:3 aspect ratio.

can anyone help me how can I change the aspect ratio using adb?
I have worked with size and density but failed to produce any results.

Many thanks to this amazing community.
 

Attachments

  • WhatsApp Image 2023-01-19 at 8.07.44 PM.jpeg
    WhatsApp Image 2023-01-19 at 8.07.44 PM.jpeg
    1.9 MB · Views: 79
  • WhatsApp Image 2023-01-19 at 8.07.44 PM.jpeg
    WhatsApp Image 2023-01-19 at 8.07.44 PM.jpeg
    1.9 MB · Views: 78

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Or even easier, use a simple adb debug shell command:

    Code:
    adb shell
    wm overscan 0,300,0,400
    For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
    The above command will shrink the useful screen area with 300px from top and 400px from bottom.
    Feel free to experiment those parameters to find the best fit for your situation.
    1
    Confirm the adb route works without root!

    Or even easier, use a simple adb debug shell command:

    Code:
    adb shell
    wm overscan 0,300,0,400
    For this to work, you must have adb installed on your pc/mac and usb-debugging activated on your android device.
    The above command will shrink the useful screen area with 300px from top and 400px from bottom.
    Feel free to experiment those parameters to find the best fit for your situation.

    A long time since the original post and answers, but I thought it should be noted that this method works well. Thanks silvake.
    My Mecer tablet stopped responding in the top 2-3cm after many years of loyal service. Could have been a drop or simply age. It is still useful and wish to give it to someone in need. So searching around and several different sites yielded some results. Note this is not a mainstream device so rooting was not an option nor attempted. Indeed drivers and any info is sparse for this device.

    For anyone attempting this, I will outline my method and steps.
    1. Enable USB debugging. There are many tutorials. Settings->About->Build number(tap x 7); Developer Options->USB debugging
    2. Connect device with USB Cable. Give permission on device. You will need to make sure that windows installs drivers. At first windows failed to install all drivers. Not sure how it managed, but it connected eventually.
    3. Download adb: https://android.izzysoft.de/downloads.php. I used https://android.izzysoft.de/downloads.php?file=adb-binaries-windows-29.0.4.zip. Decompress to desired folder. Open cmd to the folder.
    4. Run adb.exe with 'adb devices' and confirm device is listed. First attempt showed:

    D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
    * daemon not running; starting now at tcp:5037
    * daemon started successfully
    List of devices attached
    0123456789ABCDEF unauthorized


    I had to give permission on the device. Reconnected USB.

    D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb devices
    List of devices attached
    0123456789ABCDEF device


    Success! Device is now connected.
    Next get the current display stats:
    Type 'adb shell'
    Confirm connection. Mine showed: root@800P31C:/ #
    Type: ‘dumpsys display | grep mBaseDisplayInfo’
    Below is the capture of the operation:

    D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
    root@800P31C:/ # dumpsys display | grep mBaseDisplayInfo
    mBaseDisplayInfo=DisplayInfo{"Built-in Screen", app 800 x 1280, real 800 x 1280, largest app 800 x 1280, smallest app 800 x 1280, 55.84 fps, rotation0, density 190 (190.0 x 190.0) dpi, layerStack 0, type BUILT_IN, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS}


    This is not really required but helps to determine the current stats to make a guess on the number of pixels to adjust the screen by.

    Next is the command to adjust the screen. The 4 numbers are the coordinates. Since mine was the top area I adjusted only that.
    Type: wm overscan 0,50,0,0
    The update is live and you should see the screen drop 50 pixels from the top.
    This was not enough for me so repeat until the pull down of the status bar starts working again.
    Here is the whole list to adjust the screen until everything is working again:

    D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
    root@800P31C:/ # wm overscan 0,50,0,0
    root@800P31C:/ # wm overscan 0,70,0,0
    root@800P31C:/ # wm overscan 0,80,0,0
    root@800P31C:/ # wm overscan 0,100,0,0
    root@800P31C:/ # wm overscan 0,200,0,0
    root@800P31C:/ # wm overscan 0,120,0,0
    root@800P31C:/ # wm overscan 0,140,0,0
    root@800P31C:/ # wm overscan 0,150,0,0
    root@800P31C:/ # wm overscan 0,160,0,0
    root@800P31C:/ # wm overscan 0,170,0,0
    root@800P31C:/ # wm overscan 0,180,0,0
    root@800P31C:/ # wm overscan 0,190,0,0
    root@800P31C:/ # wm overscan 0,195,0,0
    root@800P31C:/ # exit


    So I had to move the screen 195 pixels down until the dead touchscreen area was excluded.
    Screen is obviously smaller but the frustration of having to rotate the device 180 to be able to pull down the status bar is removed. Much worth it.
    Now a child in need of education can still learn and we have saved the device from landfill and reduced the carbon footprint.

    You might have to adjust the pixel density to compensate for the loss, but I left it untouched. Your results will vary so I cannot assist.
    Excerpt from another site:
    "Additionally decreasing the density through the settings (Display & lights > screen > LCD density) or the wm command helped compensating for the lost display area:
    wm density 360"

    Hope this helps someone as it helped me.
    T