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.
same problem here .. heeeelp
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
I7V said:
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
Click to expand...
Click to collapse
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.
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.
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!
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.
eric_thefool said:
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.
!
Click to expand...
Click to collapse
Did you solve the problem?
davis_llb26 said:
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.
Click to expand...
Click to collapse
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...
Confirm the adb route works without root!
silvake said:
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.
Click to expand...
Click to collapse
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: [email protected]:/ #
Type: ‘dumpsys display | grep mBaseDisplayInfo’
Below is the capture of the operation:
D:\Downloads\Apps\adb-binaries-windows-29.0.4>adb shell
[email protected]:/ # 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
[email protected]:/ # wm overscan 0,50,0,0
[email protected]:/ # wm overscan 0,70,0,0
[email protected]:/ # wm overscan 0,80,0,0
[email protected]:/ # wm overscan 0,100,0,0
[email protected]:/ # wm overscan 0,200,0,0
[email protected]:/ # wm overscan 0,120,0,0
[email protected]:/ # wm overscan 0,140,0,0
[email protected]:/ # wm overscan 0,150,0,0
[email protected]:/ # wm overscan 0,160,0,0
[email protected]:/ # wm overscan 0,170,0,0
[email protected]:/ # wm overscan 0,180,0,0
[email protected]:/ # wm overscan 0,190,0,0
[email protected]:/ # wm overscan 0,195,0,0
[email protected]:/ # 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
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.
the side of may cellphone is not working
Related
to increase resolution on webtop
edit xorg.conf file (/osh/etc/X11/xorg.conf)
Code:
Section "Screen"
Identifier "Screen HDMI"
Device "Tegra HDMI"
Monitor "HDMI"
DefaultDepth 24
SubSection "Display"
Depth 24
# Uncomment to override the preferred resolution chosen by UseEDIDModes
Modes "1280x720"
ViewPort 0 0
# Defaults to the size of the chosen mode
Virtual 1366 1024
EndSubsection
EndSection
change line Virtual to eg
Code:
Virtual 1920 1080
and from a terminal execute
Code:
xrandr -s 1920x1080
Does that resolution work with the dock?
Sent from my NINJATRIX
I tested it with multimedia dock and fullHD TV
error
something to the tune of "size not in available modes"
i'm using the hdmi hack, no dock
aaron.a said:
error
something to the tune of "size not in available modes"
i'm using the hdmi hack, no dock
Click to expand...
Click to collapse
Make sure you use a resolution your tv/monitor supports. Technically you should be able to set the res from the little monitor icon on the top of the screen.
For more flexibility you can comment the virtual mode out and write several resolutions in modes like : Modes "1920x1080 1680x1050 1280x800" and so on. Than use the xrandr command for different monitors/tvs
Lapdock?!?
How about the Lapdock? I have a strange problem in lapdock, where when I try to change the default display resolution (on the settings icon inside webtop) it does nothing at all, and my screen stops being full screen (i get black straps on the monitor edges).
Should I change this line to make my screen defaults to lapdock native display resolution of 1366x768?
Code:
# Uncomment to override the preferred resolution chosen by UseEDIDModes
Modes "1366X768"
ViewPort 0 0
And still alter the other line as well for when i plug my phone on my Full HD TV?
Code:
# Defaults to the size of the chosen mode
Virtual 1920 1080
Thanks in advance.
this requires the webtopmod? not able to run xrandr.
this is from a-trix.net site right?
Hi,
If I change the resolution to full HD and if I try the webtop on a HD Ready TV, will it work ?
Thank you.
Ronaldo_9 said:
this is from a-trix.net site right?
Click to expand...
Click to collapse
yes I first publish on that forum
-JFK- said:
Hi,
If I change the resolution to full HD and if I try the webtop on a HD Ready TV, will it work ?
Thank you.
Click to expand...
Click to collapse
You can obtain different configuration changing xorg.conf file
a desktop at fullHD resolution that scroll on HDready resolution
or a desktop at fullHD scaled on another resolution
for reference
http://www.x.org/releases/current/doc/man/man5/xorg.conf.5.xhtml
i got it going. an error on my part. i added an additional line for my resolution instead of adding it inside the quotes
thanks for sharing you're knowledge's =D
can you elaborate please, is this done inside webtop? cause i searched my /osh folder with root explorer and there's no etc folder in it
I get xrandr: not found.
Point me the right way please?
<edit> Would this be a path issue?
^^^^^^^^^^^^^^^^^^
Same
Sent from my MB860 using XDA App
CaelanT said:
I get xrandr: not found.
Point me the right way please?
<edit> Would this be a path issue?
Click to expand...
Click to collapse
The same to me!
And I am needing the webtop for videos.
But...
One thing that I realized, for pictures and musics the resolution its ok, but for videos not. Why?
xrandr appears to be in /usr/bin so that shouldn't be an issue.
Code:
# which xrandr
/usr/bin/xrandr
#
My issue is that when I run xrandr (and this is on a Photon, not an Atrix) is that it comes back with "No display".
John Kotches said:
My issue is that when I run xrandr (and this is on a Photon, not an Atrix) is that it comes back with "No display".
Click to expand...
Click to collapse
Solved this, also set up the adas user to pull up @ 1920x1080 automatically on login by updating .profile.
Regards,
I just picked up a VIVO XL3 running Marchmallow. It's a bit of a mess with bugs but here are a couple things you might find useful. Connect to the phone using ADB and USB Debugging from a PC. (Nothing special -- see other guides on how to do this.)
One Note: this phone is pretty insecure -- it seems to have no incorrect fingerprint limit (Where it will require a password/PIN.) I recommend you go into Settings -> Security and enable Require password at boot. Otherwise, even on reboot, you do not need a password ever -- the fingerprint will unlock it right away.
Anyway, onto the guide. Use ADB and open up a shell to the phone: (adb shell)
------
To see a list of apps that can run in the background run:
appops query-op RUN_IN_BACKGROUND allow
To set a particular app to not run in the background: (replace package-name below with a package from the list above.)
appops set package-name RUN_IN_BACKGROUND ignore
Example:
appops set net.slickdeals.android RUN_IN_BACKGROUND ignore
------
To hide (Debloat an app)
Unfortunately, this doesn't work on this phone. This won't be possible without root.
Trying to hide an app with "pm hide" command will give you this error:
Error: java.lang.SecurityException: Neither user 2000 nor current process has android.permission.MANAGE_USERS.
------
Since there is no way to change the screen DPI in the settings app, you can do it in ADB. The stock density setting is 360 and that makes everything way too big for my taste. The smaller the number, the smaller things get on the screen. I find 280 is a good setting and you can fit a lot more on the screen while my old eyes can still read it. I also set the font size to smallest in the settings app.
wm density 280
I did notice if I got too low system_ui crashes. Before you reboot the phone you MUST reset the DPI otherwise the phone may not boot back up again!! System_ui can crash and you'll still be on on the ADB connection:
wm density reset
Reboot after making changes.... although feel free to poke around to make sure you like the setting.
Thank you for posting this. The DPI setting helps tremendously because holy cow...
I'm curious if anyone knows where to get TWRP recovery image. I wish I could install Magisk on it.
Blu Vivo XL3+ change dpi in develpers options w/ no mod
adrianblack said:
I just picked up a VIVO XL3 running Marchmallow. It's a bit of a mess with bugs but here are a couple things you might find useful. Connect to the phone using ADB and USB Debugging from a PC. (Nothing special -- see other guides on how to do this.)
One Note: this phone is pretty insecure -- it seems to have no incorrect fingerprint limit (Where it will require a password/PIN.) I recommend you go into Settings -> Security and enable Require password at boot. Otherwise, even on reboot, you do not need a password ever -- the fingerprint will unlock it right away.
Anyway, onto the guide. Use ADB and open up a shell to the phone: (adb shell)
------
To see a list of apps that can run in the background run:
appops query-op RUN_IN_BACKGROUND allow
To set a particular app to not run in the background: (replace package-name below with a package from the list above.)
appops set package-name RUN_IN_BACKGROUND ignore
Example:
appops set net.slickdeals.android RUN_IN_BACKGROUND ignore
------
To hide (Debloat an app)
Unfortunately, this doesn't work on this phone. This won't be possible without root.
Trying to hide an app with "pm hide" command will give you this error:
Error: java.lang.SecurityException: Neither user 2000 nor current process has android.permission.MANAGE_USERS.
------
Since there is no way to change the screen DPI in the settings app, you can do it in ADB. The stock density setting is 360 and that makes everything way too big for my taste. The smaller the number, the smaller things get on the screen. I find 280 is a good setting and you can fit a lot more on the screen while my old eyes can still read it. I also set the font size to smallest in the settings app.
wm density 280
I did notice if I got too low system_ui crashes. Before you reboot the phone you MUST reset the DPI otherwise the phone may not boot back up again!! System_ui can crash and you'll still be on on the ADB connection:
wm density reset
Reboot after making changes.... although feel free to poke around to make sure you like the setting.
Click to expand...
Click to collapse
If you do into deveoplers option there one called "smallest width" in "drawing" section just under "networking" where you set USB to MTP.PTP or charging. Default setting was 360. Ive tryed 360, 420, 480, 720. All work well - Display adapts in seconds w/o reboot. When you go from 720 back down to 480 it asks you to reboot. No need to worry anymore if you an MOD or if your gonna soft brick. Personnally I like 480 with font size et to small (720 is great for watching vids and probably gaming - but leaves everything to small for day to day use, unless you have miget baby finger)
PScript - Im useing Microsoft Launcher instead of stock Launcher (See Screen Shots)
I own a Oneplus 3T, on which the bottom 1cm of the screen does not register any touch. I've concluded the problem to be with the digitizer, but am not in a state to replace the display. So, I was wondering if I could shift the bottom border about 100px upwards. I tried the
Code:
adb shell wm overscan 0,0,0,100
method, but that seems to break a lot of apps. The margin seems to vary for different apps. I also tried the
Code:
adb shell wm size 1080x1820
(original resolution being 1080x1920 pixels), and the apps had no problem adapting to the new resolution. But the resolution-resize resulted in the extra 100px being distributed on top and bottom equally as 50px. Now all that's remaining is to shift the display-area 50px upwards on the y-axis. Is there a command to do that? If not, are there any other alternatives for me to achieve the same result? Please help!
As an additional request, where can I get a list of all available ADB commands?
PS: I've already tried to enable the on-screen navigation buttons and use it to offset the display, but my Oxygen OS 5.0.3 does not allow both hardware and on-screen buttons to be active at the same time.
Hi guys!
Does anyone know how we could change the resolution on the phone. Or at least the external screen?
My use case would be connecting the phone via USB-C to a TV.
TV is 1920x1080 and phone is 2340 x 1080.
Because of that I get black bars on top and bottom.
It's also only a mirror image. Is there some app or way to kill the mirror of the screen and then launch an app only on the connected screen in whatever the resolution the screen is (most often 1920x1080)
My use case for this is to play with bluetooth joysticks on a TV for example.
Mad_Duke said:
Hi guys!
Does anyone know how we could change the resolution on the phone. Or at least the external screen?
My use case would be connecting the phone via USB-C to a TV.
TV is 1920x1080 and phone is 2340 x 1080.
Because of that I get black bars on top and bottom.
It's also only a mirror image. Is there some app or way to kill the mirror of the screen and then launch an app only on the connected screen in whatever the resolution the screen is (most often 1920x1080)
My use case for this is to play with bluetooth joysticks on a TV for example.
Click to expand...
Click to collapse
I use second screen to change resolution and dpi settings, you need to do a bit of back end work to support, the app walks you through the options but only allows mirroring.
Swellwoo said:
I use second screen to change resolution and dpi settings, you need to do a bit of back end work to support, the app walks you through the options but only allows mirroring.
Click to expand...
Click to collapse
App requires root unfortunately
You can run the following on a pc with phone in developer mode and USB debug
"adb shell pm grant com.farmerbb.secondscreen.free android.permission.WRITE_SECURE_SETTINGS"
You need to install Android sdk. Command line on pc but you do not need to root phone.
Swellwoo said:
You can run the following on a pc with phone in developer mode and USB debug
"adb shell pm grant com.farmerbb.secondscreen.free android.permission.WRITE_SECURE_SETTINGS"
You need to install Android sdk. Command line on pc but you do not need to root phone.
Click to expand...
Click to collapse
Thank You!
Does this work guys?
It's annoying the black bars on top and bottom.
Before I try, do I need to have it plugged into the pc and TV at same time?
Or once done it's change forever?
Cheers
Has anyone noticed when connected via USB-C to the monitor/TV now, Tablet mode is missing on Android 10 (compared to 9) it only has Mirror and TwinDock Modes now where as before it has the 3 options.
yes this does work, ive just done my Motorola nexus 6
Setup ADB on your PC.
Enable USB debugging on your phone:
Open Settings & go to About phone and tap seven times on Build number, this will enable Developer options.
Now go back to Settings and youll see Developer options, open it.
Tick the USB Debugging checkbox.
Connect phone to the PC.
Open a command window on the PC and issue the following commands to change screen resolution to 720 x 1280 and density to 280:
adb shell wm size 720x1280
adb shell wm density 280
Reboot phone with the following command:
adb reboot
this works perfect playing codmobile, it no longer overheats and gaming become alot faster for me
the asus rog 2 has a physical resolution of 1080 x 2340 Pixels, and a pixel density of 391 on a 6 inch screen
change it to
adb shell wm size 720x1280
adb shell wm density 280
and you will notice longer battery life, no more overheating and your gaming will become alot faster.
Hi all,
After casting my screen to chromecast, is not showing correct the resolution on my TV, as there is black lines on up and down sides.
Is any way to change the resolution cast without root?
Thanks!
You can change resolution with adb.
Before changing resolution remember your original resolution with this:
adb shell dumpsys display
And change it with this:
adb shell wm density *ppi*
adb shell wm size *whidth*x*height*
I already try it, but it didn't work for me.