Related
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
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.
I have downloaded an app called touch sampling rate checker and my Moto Edge 20 only shows a rate of 90-117hz regardless of screen refresh rate setting, however when using the same app on my mi11 it shows a constant 250hz and the mi 11 seems smoother in Twitter and Facebook etc am I missing something here?
Touch sampling rate and refresh rate are two different things. If you want a refresh rate checker, you can find it in developer options.
PhotonIce said:
Touch sampling rate and refresh rate are two different things. If you want a refresh rate checker, you can find it in developer options.
Click to expand...
Click to collapse
Yeah I get that but I thought this phone has a 576hz touch sample rate? Unless the app is inaccurate ?
Not sure about the app, maybe try a different one.
nealyblue said:
Yeah I get that but I thought this phone has a 576hz touch sample rate? Unless the app is inaccurate ?
Click to expand...
Click to collapse
You have to enable game mode for individual apps for max touch sampling rate to be enabled.
dannejanne said:
You have to enable game mode for individual apps for max touch sampling rate to be enabled.
Click to expand...
Click to collapse
Unfortunately I already did that and the maximum I see is 250hz. Where have the 576hz they said gone?
fulltronservice said:
Unfortunately I already did that and the maximum I see is 250hz. Where have the 576hz they said gone?
Click to expand...
Click to collapse
Yeah the highest I've seen is 400hz with game mode
nealyblue said:
Yeah the highest I've seen is 400hz with game mode
Click to expand...
Click to collapse
So that means that the value is dynamic up to 576hz. nothing to worry about then
Android apps dont usually report the correct sampling rate. Connect the phone through USB to a PC and run through ADB run the commands: "Adb shell getevent -r -t -l" and then start swiping on the display. It should report the correct sampling rate.
Username: Required said:
Android apps dont usually report the correct sampling rate. Connect the phone through USB to a PC and run through ADB run the commands: "Adb shell getevent -r -t -l" and then start swiping on the display. It should report the correct sampling rate.
Click to expand...
Click to collapse
That ADB thing really helped. Now I can see the real use of touch sensitivity. From the huge list that came out I could see a maximum of 473hz. So the capability that Motorola offers is installed.
Thanks
fulltronservice said:
That ADB thing really helped. Now I can see the real use of touch sensitivity. From the huge list that came out I could see a maximum of 473hz. So the capability that Motorola offers is installed.
Thanks
Click to expand...
Click to collapse
It varies on how fast you can drag your finger across the screen. I'm sure that if you drag it fast enough you'll hit 576Hz.
Username: Required said:
It varies on how fast you can drag your finger across the screen. I'm sure that if you drag it fast enough you'll hit 576Hz.
Click to expand...
Click to collapse
Yes, I was able to notice that. When I made a simple contact, the response barely reached 100hz, but if I made aggressive contacts, the response was quite high.
fulltronservice said:
Unfortunately I already did that and the maximum I see is 250hz. Where have the 576hz they said gone?
Click to expand...
Click to collapse
I just found out by experimenting Game Turbo:
1. Add your Game App/ Touch Tester App to game mode/turbo
2. Enable Auto Rotation mode (Portrait / Landscape mode)
3. Rotate ur Phone to Landscape even if the app doesnt support it
4. Touch the Screen while in Landscape and see the result Increases to Max Touch Rate
Follow what i said. I want to see the result.
Ty
cjlaysico said:
I just found out by experimenting Game Turbo:
1. Add your Game App/ Touch Tester App to game mode/turbo
2. Enable Auto Rotation mode (Portrait / Landscape mode)
3. Rotate ur Phone to Landscape even if the app doesnt support it
4. Touch the Screen while in Landscape and see the result Increases to Max Touch Rate
Follow what i said. I want to see the result.
Ty
Click to expand...
Click to collapse
Thanks for the tip man I was freaking out with my Xiaomi 11T Pro who supposedly have 480hz sampling rate screen and was just getting 250hz tops within checker apps, until I run them through Gaming Mode as you suggested with Pro mode enabled and YES the sampling rate wen above 500hz tops.
So the range is dynamic? Supposedly to save battery I guess?
Regardless thanks!
Tested on OnePlus 7 Pro with Open Beta 1 OOS 12 - GM1911.11.H.20
Force Highest Refresh Rate in Android 12 with commands
First Make sure you select high refresh rate in settings (that is auto mode by OnePlus described as "High")
Then use these commands
Without ROOT
Connect phone to pc with usb debugging enabled
In Command Window type this command:
adb shell settings put system peak_refresh_rate 59.0
adb shell settings put system min_refresh_rate 59.9
=======
With Root
In app (Like Termux), type this command:
settings put system peak_refresh_rate 59.0
settings put system min_refresh_rate 59.9
Or Use SetEdit app from PlayStore and in system table change the value of peak_refresh_rate to 59.0 and min_refresh_rate 59.9
NOTE 1:
min_refresh_rate = 59.9
peak_refresh_rate = 59.0
NOTE 2:
If you have selected 60 (lowest refresh rate) in settings and then apply above commands
Then that will also work but until you device screen gets off. Once screen gets off when you turn it on, it will be back to 60 and not forced to highest.
So make sure set it high first in settings app in OnePlus device.
With Regards
5s without touching the screen and it's back to 60hz. Any solution?
Diatomix98 said:
5s without touching the screen and it's back to 60hz. Any solution?
Click to expand...
Click to collapse
5s?
Hi everyone, I enabled the 144hz mode using adb command, but when I check if the screen is really run 144hz with the option in "developer mode", "refresh rate" or using a website, the tow methods displays that the screen is running 120hz,
Plz is there a way to check if the screen is really runnin 144hz??? thanks,
The adb command that I I'm using :
settings put system peak_refresh_rate 144.0
settings put system min_refresh_rate 144.0
settings put global vivo_screen_refresh_rate_mode 144
thebestOne1 said:
Hi everyone, I enabled the 144hz mode using adb command, but when I check if the screen is really run 144hz with the option in "developer mode", "refresh rate" or using a website, the tow methods displays that the screen is running 120hz,
Plz is there a way to check if the screen is really runnin 144hz??? thanks,
The adb command that I I'm using :
settings put system peak_refresh_rate 144.0
settings put system min_refresh_rate 144.0
settings put global vivo_screen_refresh_rate_mode 144
Click to expand...
Click to collapse
It works in certain apps only. In AnTuTu Benchmark it works for example.