Hi, curious question.
I'm wondering why the Nexus7 doesn't allow you to slow scroll/pan down at single pixel steps. Always seems to be in 2-3 pixel jumps. I got a bad habit of scrolling web pages while reading from iOS but on my N7 I get these kinda anoying start/stop jerks.
Is this related to the virtual pixel resolution being lower than the actual screen resolution? And would changing it allow one to match the virtual pixels to the screen pixels and get smoother slow speed panning?
Anyone know if some custom ROMs optimize for this?
BR
POTS101 said:
Hi, curious question.
I'm wondering why the Nexus7 doesn't allow you to slow scroll/pan down at single pixel steps. Always seems to be in 2-3 pixel jumps. I got a bad habit of scrolling web pages while reading from iOS but on my N7 I get these kinda anoying start/stop jerks.
Is this related to the virtual pixel resolution being lower than the actual screen resolution? And would changing it allow one to match the virtual pixels to the screen pixels and get smoother slow speed panning?
Anyone know if some custom ROMs optimize for this?
BR
Click to expand...
Click to collapse
I have been struggling with this issue for days. Looked into kernel code hoping to find anything related to scrolling or touchscreen but nowhere to find such a thing. It has nothing to do with virtual pixel resolution. If you swipe your finger at a degree of between 45-90 (accapted as scroll up by the system), Y coordinates change by 3 pixels where as X coordinates can change by 1.. Therefore its not a limitation, it is kind of scroll sensitivity which is 3px.. I've seen other devices can scroll by 1 pixel.
I believe google has set this value to 3 because of rendering issues, since its gonna render the screen 3 times more if it is set to 1. Maybe it is the optimum sensitivity. Lower than 3 pixels may disrupt buttery smoothness but its just a guess..
I hope one dev can lead us the right piece of code where it is set to 3 and we can change it ourselves to test the best..
You guys can try the problem yourself actually by installing the "Multi-touch accuracy check" app from market, which shows the exact pixel of the touch..
the xy coordinates readout from the developer "show touches" setting shows the 3pixel increments too.
when panning something just a bit faster than dead slow then suddenly gets rid of the jumps and goes smoother as well.
could it be a battery saving thing that they just get rid of taxing the cpu/gpu when people like me do these constant slow scroll pans on webpages and books etc.?
POTS101 said:
the xy coordinates readout from the developer "show touches" setting shows the 3pixel increments too.
when panning something just a bit faster than dead slow then suddenly gets rid of the jumps and goes smoother as well.
could it be a battery saving thing that they just get rid of taxing the cpu/gpu when people like me do these constant slow scroll pans on webpages and books etc.?
Click to expand...
Click to collapse
2 more thoughts:
a) this relatively coarse sensitivity can lead sometimes (not often) lead to a +/-3 pixel uncertanty in a UI element and cause it to jittter - sometimes happens when finger pressure changes.
b) I had for a while thought that it may be linked to the size of the touch sensors on the display. Being a lower cost device I figured that the HW resolution may be lower than pixel count. But I'm pretty sure that you must be always hitting multiple sensors and the system should just interpolate to a finer resolution.
POTS101 said:
the xy coordinates readout from the developer "show touches" setting shows the 3pixel increments too.
when panning something just a bit faster than dead slow then suddenly gets rid of the jumps and goes smoother as well.
could it be a battery saving thing that they just get rid of taxing the cpu/gpu when people like me do these constant slow scroll pans on webpages and books etc.?
Click to expand...
Click to collapse
When scrolled a little bit faster, it still increases by 3px , not 1.. I also assume that it is about battery saving but if I can find a way to decrease the step size, I'd love to try it by myself..
Also It can be related to the sensors , as you mentioned, but not likely.. It can catch 1px changes when swiped horizontally..
Any news on this?
As far as I can see, this is only related to touch screen; if you use a usb mouse, you can actually see the scroll by one pixel at time, and there is no graphical issues. With mouse all seems smoother...
At this point, I think It's an hardware issue of the touch screen, as the system can easly support 1px scrolling
aLPaSLaN07 said:
I have been struggling with this issue for days. Looked into kernel code hoping to find anything related to scrolling or touchscreen but nowhere to find such a thing. It has nothing to do with virtual pixel resolution. If you swipe your finger at a degree of between 45-90 (accapted as scroll up by the system), Y coordinates change by 3 pixels where as X coordinates can change by 1.. Therefore its not a limitation, it is kind of scroll sensitivity which is 3px.. I've seen other devices can scroll by 1 pixel.
I believe google has set this value to 3 because of rendering issues, since its gonna render the screen 3 times more if it is set to 1. Maybe it is the optimum sensitivity. Lower than 3 pixels may disrupt buttery smoothness but its just a guess..
I hope one dev can lead us the right piece of code where it is set to 3 and we can change it ourselves to test the best..
You guys can try the problem yourself actually by installing the "Multi-touch accuracy check" app from market, which shows the exact pixel of the touch..
Click to expand...
Click to collapse
My two cents...I tried this approach and when you move your finger with about 5 degree you can get 1 pixel change by Y and 3 pixels change by X. And if you move your finder with about 85 degree you get 1 pixel by X and 3 pixels by Y. It seems that hardware can handle the 1 pixel change by X or Y. It looks like the touch events are throttled by the system based on the distance between points.
There is no decent and satisfying answer to this yet .. I'm still waiting for a solution..
So I play a game that's called wordzee. Works fine on first start.. but If I move to a new app and come back to the game the frame rate is a stutter fest.
Even if I close and restart the game, it sometimes still stutters.
This also happens with Chrome browser. But on the browser, it happens immediately after I use Smart Select with the spen. The scrolling stutters. Only way to fix is to close and reopen.
Anyone with similar experience? Is it the 120hz to blame? (It almost looks like it goes below 60hz)
yes most games are locked to 60 fps
vandal4e said:
yes most games are locked to 60 fps
Click to expand...
Click to collapse
What's weird is that if i put the phone in standard 60 then launch the game, it is a smooth 60. If the phone auto adjusted from 120 to 60... it is a janky 60. It's visually noticeable.
I'm also showing the frame rate from developer settings. The phone never dips below 120. Even on static images.
Guess I'm not sure how this adaptive refresh rate is actually supposed to work.
So, I've tested this phone for a while now and saw that something was up with the refresh rate of the display. I use Nova Launcher and I could tell that it wasn't as smooth as their own launcher, or the system settings for example. In developer options I turned on the "show refresh rate" toggle and the values were weird, to say the least. When it is operating at 120Hz and everything is smooth, it shows the number 10, but when I go to Nova Launcher, or Reddit Sync for example it shows 60. All of this only happens on the Auto mode, but that is the point of the LTPO Display, so it can work its magic. So as it seems the software doesn't show correctly when its running in 120Hz mode. Also, I would very much like to have Apps that I deem worthy run in 120Hz mode too, not just the ones it chooses by itself.
Strange. My phone is working like it should. Shows 10 fps when the screen is not moving. Shows 120fps as I start moving. I also tested YouTube and videos show the correct fps. 30 fps and 60 fps depending on the video.
RedNas74 said:
Strange. My phone is working like it should. Shows 10 fps when the screen is not moving. Shows 120fps as I start moving. I also tested YouTube and videos show the correct fps. 30 fps and 60 fps depending on the video.
Click to expand...
Click to collapse
Mines exactly the same
well Imma guess that it's something related to me importing my old backup, cause that messed up the AOD too (doesn't matter what I do, it won't turn on)
admirdante said:
Also, I would very much like to have Apps that I deem worthy run in 120Hz mode too, not just the ones it chooses by itself.
Click to expand...
Click to collapse
Is there any app that can adjust this per app? I also use some apps that only run at 60hz
admirdante said:
So, I've tested this phone for a while now and saw that something was up with the refresh rate of the display. I use Nova Launcher and I could tell that it wasn't as smooth as their own launcher, or the system settings for example. In developer options I turned on the "show refresh rate" toggle and the values were weird, to say the least. When it is operating at 120Hz and everything is smooth, it shows the number 10, but when I go to Nova Launcher, or Reddit Sync for example it shows 60. All of this only happens on the Auto mode, but that is the point of the LTPO Display, so it can work its magic. So as it seems the software doesn't show correctly when its running in 120Hz mode. Also, I would very much like to have Apps that I deem worthy run in 120Hz mode too, not just the ones it chooses by itself.
Click to expand...
Click to collapse
In principle, the level of brightness that you have on influences, manual brightness, I think that from 80-85% brightness it goes from 5 to 1 in refresh rate. I put a capture.
Definitely to do with brightness
At lowest brightness on auto refresh rate, it seems to never drop below 120hz except in certain apps like maps where it'll go to 60hz.
But if I put brightness at about 30%, it can drop to 10hz.
So I wonder what's more battery efficient 0% brightness at 120hz or 30% brightness at 10hz
When in a dark environment, and forced into the 120Hz mode, the LTPO panel’s power consumption isn’t all that different from an LTPS panel ~180mW power penalty that is present at all times, even on a black static screen, because of 120 Hz. That penalty comes from the measured power, with 640 mW and 465 mW in the respective 120 and 60Hz modes. Under a brighter ambient conditions, the panel showcases its technology advantages, and power consumption drops drastically. In the 120Hz mode but with the minimum refresh rate now in the regular '48 Hz' setting, the power figure drops from 640mW to 428mW, which is a massive 220mW drop.
Click to expand...
Click to collapse
The phone operating under dark conditions seems to disable the 'seamless' variable refresh rate display, that allows the phone to go into lower frequency modes, but not in all circumstances
Click to expand...
Click to collapse
When it comes to the difference in the battery runtimes between running the phone in a dark or a bright environment, there are somewhat small difference. In the 60Hz maximum refresh mode, VRR/LFD gains the phone an additional 4% of battery life. In the 120Hz mode, we see a larger 8.5% jump in runtime.
Click to expand...
Click to collapse
via https://www.oled-a.org/ltpo-phone-s...-to-extend-phone-battery-life-etc_070421.html
admirdante said:
So, I've tested this phone for a while now and saw that something was up with the refresh rate of the display. I use Nova Launcher and I could tell that it wasn't as smooth as their own launcher, or the system settings for example. In developer options I turned on the "show refresh rate" toggle and the values were weird, to say the least. When it is operating at 120Hz and everything is smooth, it shows the number 10, but when I go to Nova Launcher, or Reddit Sync for example it shows 60. All of this only happens on the Auto mode, but that is the point of the LTPO Display, so it can work its magic. So as it seems the software doesn't show correctly when its running in 120Hz mode. Also, I would very much like to have Apps that I deem worthy run in 120Hz mode too, not just the ones it chooses by itself.
Click to expand...
Click to collapse
I am having this issue also. I get only 60Hz with Nova but using default launcher I get 120Hz and it is adaptive.
So far I setting entire device at 120Hz but would prefer if there was option to enable adaptive working with Nova
_zen_aku said:
I am having this issue also. I get only 60Hz with Nova but using default launcher I get 120Hz and it is adaptive.
So far I setting entire device at 120Hz but would prefer if there was option to enable adaptive working with Nova
Click to expand...
Click to collapse
The problem is not that the GT2 PRO does not have an option to enable adaptive refresh rate with Nova, the problem is that Nova is not fully optimized with Android 12.
spiral5 said:
The problem is not that the GT2 PRO does not have an option to enable adaptive refresh rate with Nova, the problem is that Nova is not fully optimized with Android 12.
Click to expand...
Click to collapse
It seems to be incorrect. In nova Discord, Administrator said Nova work well with LTPO 2.0 screen. And as far as I can see, all launcher I tested don't work with LTPO on realme GT 2 pro except default launcher...
Use set edit and put peak_refresh rate to 1 Also i added user_refresh rate to 1 and min_refresh rate to 1. Now is working 120 & variable rate in all app.
criszz said:
Use set edit and put peak_refresh rate to 1 Also i added user_refresh rate to 1 and min_refresh rate to 1. Now is working 120 & variable rate in all app.
Click to expand...
Click to collapse
How? Can you explain a bit more about that?
Look here, marked with red in set edit app. Ignore my mistake on cameră, i was in hurry
criszz said:
Use set edit and put peak_refresh rate to 1 Also i added user_refresh rate to 1 and min_refresh rate to 1. Now is working 120 & variable rate in all app.
Click to expand...
Click to collapse
It seem ok after reboot ! I don't know how you find this but good work. Thank you.
Edit : after few minutes nova go back to 60htz. System setting "peaking_refresh_rate" automatically go back to 60
Set your screen to 120 (High) in settings, and never change )
Will this just force 120hz or working LTPO for 3rd party apps?
Working ltpo, If You want only 120 enter same settings by adb.
Ok but what's exactly the point of your settings?
If I set 120hz always in settings, LTPO will also work and go down to 60-30-10hz if not touching the display
Lol, this is for apps with no 120hz support like camera, some browsers, other launchers, even some games
Hi,
I have the problem, that the refresh rate on the inner display keeps switching back to 60hz.
If I restart the phone unfolded und use it, the screen displays in 120hz. As soon as I close the device and use it again, scrolling is laggy and on 60hz (refresh rate in developer options still shows 120hz, but it's definitely 60hz).
The only way to make it work on 120hz again is rebooting unfolded, then it keeps on working again until it's folded again.
Can anyone confirm this too?
Looks like this is still an issue even for the S23 Ultra:
Picture in Picture, Split Screen etc - Refresh Rate drops to 60Hz (EXYNOS)
Hi there, I'd not noticed this before the Android 12 update, but refresh rate appears to drop from 120Hz to 60Hz when using Picture in Picture or Split Screen views. Can anyone else reproduce this please? You can confirm this by going into...
forum.xda-developers.com
"...refresh rate appears to drop from 120Hz to 60Hz when using Picture in Picture or Split Screen views"
Therefore seems like Samsung have made this a permanent change, and I can't understand why.
Try samsung galaxy maxhz, set constant high, meaning is always 120hz
[App]Galaxy Max Hz (Refresh Rate Mods, Screen-off Mods, QS Tiles, Tasker Support and More)
About this app: Refresh Rate Mods Change default refresh rates - Easily change the overall refresh rate settings of devices supporting multiple refresh rates. - Set supported mid refresh rates as the maximum refresh rate limit for battery...
forum.xda-developers.com