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..
im running JB 4.1.1, not rooted, running in performances mode, I have constantly lag issues, this is my current Display setup:
In the end i noticed that i was getting less lag on higher settings:
Draw distance 100%
Screen Resolution 100%
Visual Effects High
Dynamic Shadows On
Frame Limiter: On
It seems that the more i tried to lower all settings at once or individually, the more lag i was getting or using default settings. Im sure this is not an issue with the Prime hardware.
Anyone has any suggestions?
so i just upgraded from an old lg optimus 4x hd phone (android 4.0.3) to a new xiaomi redmi 4 prime (android 6.0.1) and what is annoying me most is a strange software effect filtering all input motion from the touchscreen.
for example when im trying to scroll in settings menu, but moving the finger slightly up and down, the motion is getting filtered completely. when trying to scroll slowly the lag/filter is most annoying. with android 4.0.3 this doesnt happen, all motion input from the touchscreen is getting directly forwarded without any delay/lag/filter.
this touchscreen input filter behavior also occurs in apps like for example realvnc viewer, with android 4.0.3 its pretty easy to accurately control the cursor, with android 6.0.1 its almost impossible to control the cursor because all touchscreen input motion is getting filtered/delayed.
is there any way to disable the touchscreen motion filter behavior and make the touchscreen input to be direct like it was in previous android versions like android 4.0.3?
I have now uploaded 2 Videos of the Xiaomi Redmi 4 Prime and LG Optimus 4X HD which in comparison should show clearly what i mean with "touchscreen input motion filter":
youtube.com/watch?v=qgLqw47wsjY
youtube.com/watch?v=_ac1RgK2Xhw
At 0:00-0:37 (and especially at VNC Viewer test 1:21-1:53) you can clearly see how the Xiaomi Redmi 4 Prime creates some kind of a "smooth-scroll-effect", it continues scrolling very slowly, even though the finger has already stopped moving. This clearly must be a software effect, i cant imagine a hardware problem.
At 0:37-1:21 and 1:53-2:36 you can see, how much the touchscreen has got an input travel almost like the steering wheel of a car, smaller up/down/left/right movements are just being ignored and filtered out. Also here i can only very hardly imagine that this is a hardware issue, for me it clearly looks like a software effect.
I also tested 2 other Android 6/7 phones (Cubot Note Plus and Homtom HT17 pro), both show exactly the same behavior as seen in the video of the Xiaomi Redmi 4 Prime.
The questions that im now asking myself are: Where does this touchscreen software effect come from? What is it called? And how do i remove it? (If necessary, i also agree to root/unlock or install a custom rom on my Xiaomi phone)
bumpp
bump
Try SGS touch screen booster app.
It let's you adjust the motion filter amongst other touch latency Android touch settings and you don't need root.
I'm aiming for as close as I can get to iPhone iOS touch response...
Still playing with it but this is where my Honor 8 is currently set.
Couldn't be happier with the results
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.
I've noticed that the S21 has a small but noticeable touchscreen latency when using the touchscreen. When I say small I mean about 0.1 or 0.2 seconds.
I'm guessing this is just how the hardware works but am I missing any configuration to change it?
It's not much of a delay but as an example when you start an app from the home screen by touching the screen quickly you can get your finger off the screen completely before the app begins to start and the screen changes.
I'm not talking about the transition and animation scales in developer settings, the lag is noticeable with or without them on.
My other half has an A52 5G and this doesn't have the same lag and if it's a simple app being opened or a switch to an already open app the A52 is often quicker.
Has anyone else noticed this?