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..
Its been sometime that we are having this issue on the Note 10.1 2014 .. Its that the screen starts to shake when holding and scrolling or it jitters and shakes when we pinch to zoom ..
There is a thread in the forums for the Note 10.1 2014 about it but wanted to ask on a broader forum if there is any solution to fixing or even reducing the issue in the Android OS
Is there a way in android to reduce the touch sensitivity so that the screen is more stable ..
There is also an app called Artflow that does not exhibit this issue even though the rest of the os there is a shake issue ..
Does any one know of a overlay software fix for this so that the touch screen can be more usable .. or slow down the sensitivity
Or at least mod the internet browser to be less sensitive when scrolling , I am rooted so any root solutions would be great ...
The issue is also in a youtube video ...
http://www.youtube.com/watch?v=YuZKn0W9aIo
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
Hello,
Iam planing to Upgrade my Car Infotainment System.
I want to integrate an ultra wide Display with an Display Ratio of 21:6
And operate it with an Android Board Like an Odroid xu4
As the Display is ultra wide i want to permanently Display 2 apps at the same time next to each Other. These Apps should be displayed in a fixed Layout (one App Covers 2/3 of the width and the Other 1/3)
as the Layout should be fixed and i want the Apps displayed next to each Other right from Startup iam searching for a way to achiev this.
I need a way to permanently "Split"/devide the Screen and a way to start on These splitted Screen halfes an App on Startup.
Is there Any way to achiev this?
I hope for some ideas.
With Kind regards.
I've been on Android for years and only when I upgraded from Android 11 to Android 12 has my Auto-Rotate constantly been turned on, even as I turn it off every single day whenever the darn thing rotates on me.
I NEVER want my phone screen to rotate.
Yet, it does.
Why?
I googled and found out that Android 12 did add to the "intelligence" of the auto-rotate functionality; but I don't see others with the same problem that I have that it keeps turning itself on even after I have turned it off.
How to use Android 12’s clever new auto-rotate system
With Android 12, Google has introduced a smarter way to control when your screen switches between its vertical and horizontal orientations. Instead of relying solely on your phone’s accelerometer to figure out which way you’re holding the device and then rotate your screen accordingly, Android 12 allows your device to use its front-facing camera as a guide. That way, the software can sense how that striking face of yours is positioned at any given moment and make sure the screen is always positioned to match. The advantage is that you then avoid those awkward situations where you’re lying down — and thus holding your phone at an angle — and the screen then flips into its landscape orientation when you’re actually looking at it in its portrait mode. Since the system pays attention to the position of your face, it makes the screen match the way you’re actually using the device, no matter how you might be holding it.
Click to expand...
Click to collapse
I do NOT know if that Android 12 "intelligence" is the REASON my phone keeps auto rotating, which is why I'm asking here if the rest of you are also having to turn OFF the auto-rotate time and again, day in and day out, all day every day, on Android 12?
And yes, I searched first:
Search results for query: rotate
Search results for query: automatic rotate
Search results for query: auto-rotate android 12
It doesn't seem to be a problem for others - so why is it a problem for me?
Anyone have any debugging ideas to figure out WHAT is turning on the automatic rotation feature of Android?