Related
I read that some peoples have issues with the touchscreen sensitivity. I've thinked i've got the same problem until i activate some developers options Options: "Show touches" and "Pointer location". Thereafter i realized that the touchscreen is perfectly responsive, the only issue is that when i click somewhere, my finger sometimes slip a bit and the touchscreen take it as a Swipe, then i have to click another time. The TF701 have a high density PPI (300) and it seem the touchscreen is not calibrated in accordance to that density.
By example (I don't know the real values!)
on my Motorola XOOM (150 PPI), the device need at least 30 pixels movement to detect a swipe = about 2/10 inches
on my TF701 (300 PPI), the device need at least 30 pixels movement to detect a swipe. = about 1/10 inches
What do you think about it?
Is it tunable by an application?
I found TouchScreenTune on the PlayStore but have never tested it since it's not marked as TF701 compatible, and i'm not root.
I found editing the following options makes a huge difference.
In the build.prop add the following lines:
Code:
# Improve Touch Pressure
touch.pressure.scale=0.001
ro.min.fling_velocity=90000
ro.max.fling_velocity=200000
Obviously the first line is just a comment
Also you can speed up browsing by enabling debugging mode in the browser by typing the following in the address bar
Code:
about:debug
Then go to the settings and the new debug menu and enable:
enable hardware accel
enable cpu upload path
enable light touch
Click to expand...
Click to collapse
Or just unlock and flash CROMi-X for all these and loads of other tweaks built in
Is there a way to change these settings without flashing a new ROM?
dutchguy said:
Is there a way to change these settings without flashing a new ROM?
Click to expand...
Click to collapse
Well you need to be rooted but yes just follow the instructions above. The browser set won't stick on a reboot though so you'll have to keep doing it.
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
android apps are almost all for smartphones only a few apps have extensions that allow you to make better use of your tablet's screen size,
after installing some apps that have a different shape on the tablet i noticed that on mediapad m3 nothing changes, they are the same shape as a larger smartphone,
i wonder and wonder you:
maybe the m3 is not recognized as a tablet or needs to be changed some settings?
There have been quite a few threads or sub-threads on this. the DPI needs to be changed to have the M3 render some apps in their tablet modes, most of the discussions revolve around Chrome (no tabs in original DPI and YouTube). Try running this command from ADB:
adb shell wm density 320 && adb reboot
320 works well for me on Nougat, but you might need to experiment with what works well for you and the version you are on. If you haven't changed your view mode, the change should stick after rebooting, if you have then chances are you will need to use a DPI changing app to update your settings after each reboot.
johje said:
There have been quite a few threads or sub-threads on this. the DPI needs to be changed to have the M3 render some apps in their tablet modes, most of the discussions revolve around Chrome (no tabs in original DPI and YouTube). Try running this command from ADB:
adb shell wm density 320 && adb reboot
320 works well for me on Nougat, but you might need to experiment with what works well for you and the version you are on. If you haven't changed your view mode, the change should stick after rebooting, if you have then chances are you will need to use a DPI changing app to update your settings after each reboot.
Click to expand...
Click to collapse
thanks for the reply, i already knew the change of DPI,
maybe i have not explained the problem well, so let's take an example:
if you install Metatrader 5 on smartphone and on a true tablet you will see two different shape on display while on mediapad m3 i see the same shape no difference,
the same problem occurs each time i install an application that must appear on a tablet differently from a smartphone
There is no general "tablet" identifier, but apps decide based on screen size / resolution / dpi if they change their layout or not: https://developer.android.com/guide/practices/screens_support.html#qualifiers
So changing the DPI is the currently best option.
(Perhaps some apps tweaked this by overwriting these qualifiers for certain models based on the device identifier.)
fluxxis said:
There is no general "tablet" identifier, but apps decide based on screen size / resolution / dpi if they change their layout or not: https://developer.android.com/guide/practices/screens_support.html#qualifiers
So changing the DPI is the currently best option.
(Perhaps some apps tweaked this by overwriting these qualifiers for certain models based on the device identifier.)
Click to expand...
Click to collapse
thanks for your contribution, something strange happens that i explain:
also my bank offers an app that has a different shape depending on where it is installed and installing it from google play to the mediapad m3 comes on the tablet version, unfortunately the layout is not compatible with the screen but changing the dpi the issue is solved and the app becomes fully usable, while the metatrader 5 app does not seems to recognize mediapad m3 as a tablet and it installs with the shape of the smartphone.
maybe i understand where the issue is:
i belive that mediapad m3 has a wrong package installer or a bug in it.
I came to this conclusion after this test:
i download the apk file on pc then transfers it to old consumer tablet and also to mediapad m3,
so i manually installed it in both
then i saw that in the mediapad m3 had been installed the smartphone version while in the “old tablet” had properly installed the tablet version,
what do you think?
@johje, @fluxxis, i was confusing, i was thinking in wrong way, i apologize, your suggests was right
There is a choice of display settings in system settings. You can choose small, medium or large.
Probably this setting changes the logical resolution of the display. Small is the right setting, after reboot the tablet behaves as a tablet should.
antisztar said:
There is a choice of display settings in system settings. You can choose small, medium or large.
Probably this setting changes the logical resolution of the display. Small is the right setting, after reboot the tablet behaves as a tablet should.
Click to expand...
Click to collapse
Hi... so we have to change display settings in the small view and launch the adb command?
In another thread I read the chance of modify the minimum value from 640 to 720 dpi in the developer settings.
What's the right choice?
Thanks.
Oneplus 7 Pro
Force 90hz Refresh Rate in almost every App (and Games)
*also uncaps FPS (since Vsync is on by default for Android)
Requirements:
1. A Windows PC (Windows 10 64 Bit is preferred)
2. Oneplus Drivers
3. A USB Type-C Cable
4. Your Oneplus 7 Pro
Steps:
1. Plug in your Oneplus device and select File Transfer mode in your phone's notification selection, then open My Computer and you will see the drive for Oneplus Drivers.
2. Install Oneplus Drivers (you may be prompted to reboot afterwards). You may need to plug and unplug the device to finish driver recognition. Unplug your phone once it is finished.
3. In your phone, go to Settings > About Phone, and tap Build Number multiple times in fast succession until the message "you are now a developer" appears.
4. Go to Settings > System > Developer Options, and turn on USB-debugging.
5. Go to Playstore and download jOnePlus Tools
6. Plug your device in your PC.
7. Anywhere on the empty desktop of your PC, press shift + right click, and select "Open Powershell window here"
8. Wait for Powershell to load
9. Type "adb shell" without the quotes
10. A permission prompt will appear in your Oneplus 7 Pro's screen, allow it.
11. Type "adb shell" once again and press Enter, and you should see your device like this "Oneplus7Pro:/ $"
12. Type or copy-paste the text below without the quotes:
"pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS", and press Enter.
13. Once you've entered that, it should repeat what you've typed in the next line.
14. Unplug your device, and open jOnePlus Tools app.
15. Tap Screen Refresh Rate and select Force 90Hz
16. Congratulations, you are done! To confirm, you can go to Settings > Display > Screen Refresh Rate and you should see it as 60Hz from the outside, but when you tap it, you will see that nothing from the 2 choices is selected. It means you are using the 3rd Hidden Setting.
Tip: You may need to reselect Force 90 Hz from the jOnePlus Tools if you have selected 90hz or 60hz from the settings.
Note: This will enable 90hz (and up to 90 fps) for apps and games, unless the app itself has an even stronger FPS-controller then it will tone-down the FPS to the standard set by that game. But for most games without an FPS controller or 30-FPS-locked games without an in-game FPS-controller, it will work 100%.
Credits:
C3C076 (XDA Developer, Dev of GravityBox)
JRoot3D.dev (jOnePlus Tools Developer)
Guide Maker: Ares (Freyelis - XDA Senior Member)
RIP Battery Life?
stanley08 said:
RIP Battery Life?
Click to expand...
Click to collapse
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Freyelis said:
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Click to expand...
Click to collapse
Maybe I will
stanley08 said:
Maybe I will
Click to expand...
Click to collapse
Enjoy better gaming man. Try it on Assassin's Creed: Identity too, that game has awesome graphics but was locked at 30 FPS... Not anymore
Freyelis said:
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Click to expand...
Click to collapse
Anyway to set auto brightness but less than 50% always ??
Or you could simply use Smurf kernel which already has this in the config and stays set through reboots. Or just use the original method from C3C076 which sets it permanently no need for this extra stuff or to have joneplus tools constantly in background for no reason...
9 hrs SOT? @op do you have qhd or fhd?
Stock kernel? Any mods?
if i restart my phone will the settings i made gone?
se7ensde said:
Or you could simply use Smurf kernel which already has this in the config and stays set through reboots. Or just use the original method from C3C076 which sets it permanently no need for this extra stuff or to have joneplus tools constantly in background for no reason...
Click to expand...
Click to collapse
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
bubu23 said:
if i restart my phone will the settings i made gone?
Click to expand...
Click to collapse
No
Xalph92 said:
Anyway to set auto brightness but less than 50% always ??
Click to expand...
Click to collapse
Either set it manually, or use YAAB app as a replacement for auto brightness, which you can set the maximum ang minimum brightness.
virtyx said:
9 hrs SOT? @op do you have qhd or fhd?
Stock kernel? Any mods?
Click to expand...
Click to collapse
Dynamic, stock kernel.
No mods, I just control every background app using built-in background restriction, deepclear, and deep battery optimization.
Just for information, my kernel config has a switch to apply 90Hz, auto or 60 HZ.
Gesendet von meinem xXx_NoLimits_7.1 on GM1913 mit Tapatalk
Freyelis said:
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
Click to expand...
Click to collapse
Did you actually test it? "ADB shell settings global put" command changes user settings that are stored in the filesystem and are thus persisted across reboots until explicitly changed by the user.
Freyelis said:
Dynamic, stock kernel.
No mods, I just control every background app using built-in background restriction, deepclear, and deep battery optimization.
Click to expand...
Click to collapse
Have you restricted system apps too? Did you do this for each app one by one?
Do you have a list of what you've restricted
thanks!
thanks!!!so after doing this im rooted already?because jtools need root right?
Freyelis said:
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
Click to expand...
Click to collapse
Stays through reboots for me... And like I said there are easier simpler and faster ways to achieve this without need of all this extra stuff. Smurf kernel already implemented this in his config so it stays like that too. And C3C076 had made qs tiles for this. I've been using his method for over a week now through several reboots no issues.
C3C076 said:
Did you actually test it? "ADB shell settings global put" command changes user settings that are stored in the filesystem and are thus persisted across reboots until explicitly changed by the user.
Click to expand...
Click to collapse
Sorry, thanks for the clarification sir, great work as always, will revise this one
virtyx said:
Have you restricted system apps too? Did you do this for each app one by one?
Do you have a list of what you've restricted
Click to expand...
Click to collapse
I did not restrict system apps, only the apps that I installed. Apps that I need notifications from such as Telegram, is not included in the restriction. All other apps are, like games, editors, etc..
[Re-posting this here after I confirmed it work with the Pixel 7 as well]
To be clear, this is not the same as the developer option.
Enter the following ADB commands (you can also modify these values using the app SetEdit in the Play Store, no root required):
adb shell settings put system peak_refresh_rate 24.0
adb shell settings put system min_refresh_rate 24.0
The reason this works is because by assigning it a random and unsupported value, we are [kind of] breaking the refresh rate. As a result of which, the OS won’t be able to adjust this rate, and hence stick with the maximum available rate.
You can also enable the "Force Refresh Rate" in Developer Options. I tried it, but don't really care to keep DO enabled. Also you can enable "Show Refresh Rate" in DO. I did that also, and realized that with keeping it at 60(normal), and keeping "Smooth Display" on, the phone kicks it into 90 the moment you touch the screen. So forcing 90 100% of the time is a waste of battery in my opinion. Only when the phone is not touched for three seconds does it drop back to 60. Otherwise any use of the phone it stays at 90 normally.
bobbyphoenix said:
You can also enable the "Force Refresh Rate" in Developer Options. I tried it, but don't really care to keep DO enabled. Also you can enable "Show Refresh Rate" in DO. I did that also, and realized that with keeping it at 60(normal), and keeping "Smooth Display" on, the phone kicks it into 90 the moment you touch the screen. So forcing 90 100% of the time is a waste of battery in my opinion. Only when the phone is not touched for three seconds does it drop back to 60. Otherwise any use of the phone it stays at 90 normally.
Click to expand...
Click to collapse
Started my day today at 100% 7AM and am at 52% 11PM so I am happy. I can't stand Snapchat being 60.
Update on my observation. It may be a placebo effect, but knowing that it changes makes me see a slight stutter. Forcing 90 at all times "seems" much smoother, so I'm leaving it on also. Cheers!
this trick is irrelevant, you can do it in developer tool....
Vio281 said:
this trick is irrelevant, you can do it in developer tool....
Click to expand...
Click to collapse
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Jonnyswboy said:
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Click to expand...
Click to collapse
Jonnyswboy said:
The developer option does not force in many cases. In Snapchat when you swipe to the left and the camera is still initialized it stays at 60hz. Once the camera is not initialized it goes to 90hz. I believe it is the same in Instagram.
Click to expand...
Click to collapse
Has a fix been found for this cause I found this doesn't seem to be an issue at all on iPhone but incredibly frustrating on Android especially Snapchat.
lukeah02 said:
Has a fix been found for this cause I found this doesn't seem to be an issue at all on iPhone but incredibly frustrating on Android especially Snapchat.
Click to expand...
Click to collapse
My fix is in the original post. Has been working great for me.
Been using this for a while, but let's saym hypothetically if I wanted to restore it to default settings, which values do I need to put on the adb commands?
If I do those ADB commands and decide I want to not have them anymore, how would I revert?
To get your default values before doing the change, use:
Code:
adb shell settings get system peak_refresh_rate
and
Code:
adb shell settings get system min_refresh_rate
For me on stock firmware unrooted, peak_refresh_rate = null, and min_refresh_rate = 0.
Thanks for your fix! I was wondering why some apps were low hz.
heisenberg17 said:
Been using this for a while, but let's saym hypothetically if I wanted to restore it to default settings, which values do I need to put on the adb commands?
Click to expand...
Click to collapse
Get default values before doing the change:
adb shell settings get system peak_refresh_rate
adb shell settings get system min_refresh_rate
Default values (stock unrooted):
peak_refresh_rate = null
min_refresh_rate = 0
Thanks for your fix! I was wondering why some apps were low hz.
I've just got a Pixel 7 and thought I'd try this.
Observations, stock not rooted etc
Peak refresh rate = 90
min refresh rate = null
Applied the settings in post 1
and both come back as 24 when 'getting' peak/min rates from adb.
However, turning on show refresh rate in developer options show 90 when using the screen, but drops back to 60 if you leave it for a few seconds.
it only stays at 90 if you turn on Force peak refresh rate in Developer options.
This is only so far when messing about on the home screen, not tested in any apps etc, but it looks like these settings can't be fixed by setting a random number as post 1 implies
As a quick follow up, setting both peak and min to 90 does fix them, but seems a bit pointless as you can turn it on/off within developer settings.
This is not a bash at the OP, but maybe recent update have taken this 'feature' out
Does this survive a reboot?
xduox said:
Get default values before doing the change:
adb shell settings get system peak_refresh_rate
adb shell settings get system min_refresh_rate
Default values (stock unrooted):
peak_refresh_rate = null
min_refresh_rate = 0
Thanks for your fix! I was wondering why some apps were low hz.
Click to expand...
Click to collapse
Though the above might be a possible solution, here is the proper way to revert using ADB:
adb shell settings reset system peak_refresh_rate
To dig further into the possible System settings (amazing topic ^^)
adb shell settings list system
MrPeaski said:
seems a bit pointless as you can turn it on/off within developer settings.
This is not a bash at the OP, but maybe recent update have taken this 'feature' out
Click to expand...
Click to collapse
You can't force peak refresh rate in developer settings. It will still drop at times, like in Snapchat when the camera is accessed, on Google Maps, etc. It still automatically drops to 60hz despite the developer option being enabled.
And after updating to the Android 14 beta this workaround does not work anymore, and I am very frustrated that I am unable to truly force 90hz anymore.