I was really happy with my LG G5, until after a week or so, I noticed that the screen actually seems to have problems with "fast" change of movement. And I am really annoyed at this point by it, because I compared it with other devices of mine, and it's not that bad on these older devices. For example my old phone, a Samsung Galaxy S3, doesn't have this issue at all.
You can easily notice it in the Android settings (use list view). When you now slowly move up/down with your finger, you see that all fonts have a "ghost-effect" (get blurry) of not properly refreshing in time. There is a bit of border / re-draw affect around each word on the screen.
You will notice it also for example on the app store scrolling down / up, or in an app drawer (if you have a launcher with app drawer) and scroll through the app list.
On my phone i have no ghosting or problems with fast change of movement. There is a website called "testufo" where you can test your display for ghosting and FPS.
Related
Hello everyone, I am new to the forums and new to the S3 (only been mine for almost a week) and I rooted it once, unrooted (using 9300XXBLFB_I9300OXABLFB_BTU.zip firmware, probably a bit outdated since it had added a brightness slider in the status bar menu, and changed brightness to color in browser, no big deal). Anyways, the small problem (most likely software) is that when I go to camera, and then to gallery (using the shortcut on the lower-left side) and then get out of the gallery, the 8MP sensor seems to have a black bar on the lower side when holding vertically, or the right/left side when held at corresponding horizontal positions. Easy fix for this would be to just close and relaunch the camera app, but it happens every time. No matter what launcher I use as well.
Had anyone else encountered this "problem" or glitch? And is there a way to permanently fix it?
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..
I've used instagram on an iPhone, a galaxy s4, note 3, and note 5, and instagram has never been as unresponsive as it has on my lg v10. The app still works on my lg as it should, but it's fluidity seems to be lacking. For example, I scroll through my feed pretty hastily, and sometimes when I double tap a photo to "like it" and scroll down to view more, it registers it as a down-stroke, and scrolls up instead. The lg v10 doesn't do this with any other app, however, and the only "touch issues" I had was on the top left portion of my screen (which was caused by Facebook's messenger app). Could this be a glitch within the instagram app? On a completely irrelevant note, I was using Google keep today and noticed that the framerate was really low. Scrolling up and down seemed very choppy as well as pulling the side menu from the left.
Anyone?
I've used instagram on an iPhone, a galaxy s4, note 3, and note 5, and instagram has never been as unresponsive as it has on my lg v10. The app still works on my lg as it should, but it's fluidity seems to be lacking. For example, I scroll through my feed pretty hastily, and sometimes when I double tap a photo to "like it" and scroll down to view more, it registers it as a down-stroke, and scrolls up instead. The lg v10 doesn't do this with any other app, however, and the only "touch issues" I had was on the top left portion of my screen (which was caused by Facebook's messenger app). Could this be a glitch within the instagram app? On a completely irrelevant note, I was using Google keep today and noticed that the framerate was really low. Scrolling up and down seemed very choppy as well as pulling the side menu from the left.
Title, pretty much. I change my color settings and they only apply to the dual screen when attached, and not at all when disconnected. It's the exact opposite with specific game settings. I can change a game's resolution and framerate settings and this works on the main screen, but NOT on the dual screen. When I swipe the app on lower settings from the main screen to the dual screen I can see the resolution increase.
EDIT: Specs - Verizon model, newest update. Which I'm irritated about because I kept myself on the base firmware this whole time waiting for root and finally gave up, hoping it would fix this, along with a plethora of other issues. It fixed some of the minor ones, but not the big ones like this or others.