My friend was looking at Viewsonic Tablet running Vegan rom and noticed the miniscule lag when scrolling, especially at the beginning of the scrolling.
This isn't really a huge LAG, but a small jump at the start of the scroll.
I have a Cappy on Serendipity vii rom + kernel (and as is the case on all other roms I've tried), there seems to be a threshold of finger movement before a scroll is registered, whether on the apps list or scrolling the wallpaper.
I did some research and came up with a variable like gesture dip or something. Don't know if this is related.
Just wondering if anyone had a definite answer whether this is a threshold coded in for features like detecting long presses, or whether it was an inherent lag between user interaction and system response.
Some touchscreen drivers do have this threshold. There is no fix but to change the value every time on boot. The kernel needs to be modded to expose the value.
Related
I am searching method for reducing performance drop while touching the screen.
Every machine i had was affected by this problem - drop is quite big - 20-30%.(asus, wizard, optipad 300(matsushimi or sth.)).
Can someone suggest reg changes that may be useful?
priority, buffer, anything?
im not sure how much you can do about this because every time you touch the screen, it has to spend recources on getting the location of the touch on the touch screen. Its bound to slow things slightly, but ive never come across that big a problem with it.
Hi all,
I notice that when sliding through the app drawer of TW3, the finger tends to move some distance before the page starts following the finger. This is especially obvious when then page is stationary and the finger has to move some distance before the app drawer page stutters and starts moving.
After reading most if not all of the discussions in this forum, I understand that our phone sustain certain level of lag in that situation, probably due to the touch mechanism itself or inefficiency in the processor or what not. But I do have an interesting observation: whenever my phone sustains a fresh reboot, it is that time that the app drawer is perfectly lagless and follows even the tiniest movement of my fingers. This snappy phenomena only lasts until I put the phone to standby, i.e. locking the phone. Thereafter it goes back to the condition as mentioned earlier on.
My question is, there's no doubt i9003 has the capability to be lag free in the context of this discussion, but it seems pretty apparent that something is inhibiting the phone from being as smooth as when it first rebooted. Could it be the priority the TW launcher is assigned with, or does the processor clock speed matter in this situation?
P.S. When testing, I made sure that no applications are opened after the fresh reboot, so issues like insufficient memory etc should not be related here.
I noticed the same things, not only when sliding through the app drawer, but also when sliding menus etc. However after a reboot, my phone behaves as always. Maybe you feel it more lagfree because of the high clock speed due to the multiples stuff your phone does on boot. Try to change your governor to performance and see if it behaves like after a fresh reboot. In this way you'll know if your lagfree experience is due to clock speed.
I read a lot of stuff too but nothing was really useful. However I noticed that I feel lags only when the touch of the screen can be interpretated in different ways (for example sliding screens and opening apps), but when touching the screen allows you to do only one thing, like moving things, there are nearly zero lags. For example when you pull down/up your notification bar or when you move a zooomed image in gallery. This make me think that it's more a software problem than a hardware problem and I think that because in some app there are less lags than in others.
I don't know if you read this, but I think it improves the touchscreen, even if the difference is barely noticeable.
TW3 is sludge!
I just did a little test with the app Multitouch Visualizer 2 (https://market.android.com/details?...y5tZXRhbGV2Lm11bHRpdG91Y2gudmlzdWFsaXplcjIiXQ..) and I seem to get input lag fråm it.
It registers all 10 fingers just ok but if I hold one finger on the display and just momentarily tap another finger to the display it seems that it doesn't register it right away.
Can anyone confirm my findings?
I did the same thing as you and I got similar results.
I think I noticed this a little bit when playing shadowgun and it would not shoot right away when moving around. But other than that it hasn't affected any other apps that I've really noticed.
I have noticed the input lag in some other games and apps though. I never noticed it under HC.
Just did another test in Input Benchmark. I constantly got 80Hz refresh rate under HC but now under ICS the value is flickering around 69-75Hz. And if I suddenly add another finger the value jumps up to around 2********Hz... just as if the readings from the digitizer would be messed up.
There is something strange about ICS for sure.
Yeah it does sound like it. I never thought to run any tests between the two since it never affected my experience. But as for refresh rate, or GPU performance, I notice sometimes the screen will flicker when doing certain actions like when opening the multi-task window or any window that 'hovers' above the current screen.
Is there any speed-governor app for the Xoom that can be configured to lock the CPU to 1000MHz whenever the soft input area is active (or better yet, whenever Graffiti input is active), and/or a way to increase the digitizer sample rate?
Historically, Graffiti has been totally unusable on my Xoom. Literally, so low of a sample rate, and so many errors, that I just couldn't use it. I finally got around to unlocking and reflashing my Xoom to CM10 last night, and locking the CPU to 1000MHz makes it work a lot better... but the accuracy is still a cruel joke compared to even my creaky, old Hero overclocked to 711MHz.
It's pretty sad, actually. On the Hero, the digitizer seems to be reporting samples at least 4-16 times as often, and I can get nearly 100% accuracy without even trying. On the Xoom locked to max speed, it seems to do a tiny bit better than my S3 gets with stock, but the sample rate still appears to be absurdly low compared to what it was on the Hero, and feedback seems to lag the actual touch by at least 100-200ms. On the Hero, feedback was literally instant... stroke, and see the pixels turn white INSTANTLY under my fingertip. On the Xoom (locked to max), they start turning white a fraction of a second after I touch the screen, and I can see the last bit of the stroke render a fraction of a second after I lift my finger away. With the stock Xoom rom, it was more like, "draw the character, and see a jagged impression of it sputter into existence about a half-second later... maybe, MAYBE even getting recognized correctly about 70% of the time".
I'm guessing that either the Xoom's digitizer has a limited sample rate, or something in the kernel or driver is limiting the sample rate... but I'm still trying to find a straight answer somewhere about whether/how you can build a custom kernel without losing your ability to run paid Market apps. Or whether it's even necessary to go to that extreme, as opposed to something like a setting that tells Android to increase the sample rate, or not throttle the CPU when an input area is active, or maybe a way to let something like SetCPU identify "soft input area active" as a profile-triggering condition. I'm also pretty sure that the Xoom's kernel (if not recent versions of Android itself) try to treat the existence of a soft input area as an excuse to massively throttle the CPU, on the theory that it's just displaying a picture of a keyboard and waiting for a blunt press. HOWEVER, I'm SURE there HAS to be an equally-official way of defeating that behavior, if only because it would also screw up Android's ability to handle east Asian input methods.
I am experience a lot of choppiness and a screen tearing like effect with my S4 One S.
I have tried multiple ROMs and kernels none of which seem to solve the issue, however I did notice it particularly bad on CM10 ROMs. I am currently running Viper 2.0 so that's a sense based Jelly Bean 4.1 I have tried "force 2D GPU rendering" to no luck.
Basically on scrolling, particularly noticeable in the launcher screen transitions and app drawer transitions, they start off smooth, then right before the animation finishes there is a little 'jump' where it misses out the end frame or two and jumps straight to the finish. It creates a really irritating laggy stuttery sensation, which makes the phone not feel smooth to use.
I have tried all the launchers you could throw at me, currently using Holo Launcher HD because I can slow the animations right down which makes it smoother, but still has the stutter at the very end...
Is anyone else experiencing these same issues?
Sounds like you got some background app slowing the device down to a halt.
I have none of the issues you are describing, and havnt had it on any rom Ive tried either.
RichardW1992 said:
I am experience a lot of choppiness and a screen tearing like effect with my S4 One S.
I have tried multiple ROMs and kernels none of which seem to solve the issue, however I did notice it particularly bad on CM10 ROMs. I am currently running Viper 2.0 so that's a sense based Jelly Bean 4.1 I have tried "force 2D GPU rendering" to no luck.
Basically on scrolling, particularly noticeable in the launcher screen transitions and app drawer transitions, they start off smooth, then right before the animation finishes there is a little 'jump' where it misses out the end frame or two and jumps straight to the finish. It creates a really irritating laggy stuttery sensation, which makes the phone not feel smooth to use.
I have tried all the launchers you could throw at me, currently using Holo Launcher HD because I can slow the animations right down which makes it smoother, but still has the stutter at the very end...
Is anyone else experiencing these same issues?
Click to expand...
Click to collapse
did you try a factory reset? it can affect wonders
maybe some roms need some time to find the right place in your phone.. my jb runs perfectly smooth after 2days and some reboots.
I always factory reset and full wipe in between flashing my ROMs.
I'm more than positive its not a bag ground process hogging CPU as I have used apps to monitor my CPU usage and it idles nice and low under 10% then shoots up during screen transitions.
I may have made the problem sound worse than it is. Its not like running the phone with the max CPU throttled down to 192MHz which does cause lag and stutter. Its more like, silky smooth everywhere, then suddenly the last frame or two of the animations skip, making it even more obvious and irritating as everything else is so smooth.
It does it with all launchers, and scrolling in apps sometimes doesn't feel smooth. ie you give it a fling, it shoots off lightning fast then as it gradually slows back down to a halt, right before the scrolling stops there is a little 'jump' or 'stutter' giving it an unsmooth feel
I'm going to try flashing a 4.2 ROM and enabling 4x MSAA to see if that will fix it. If not I might upload a video to try and capture the issue. Its almost like Vsync isn't on, or isn't working properly, but when I turn it off it only makes the screen tearing and jitter much worse!
I used AOKP 4.2 which seemed even worse than ever, it was almost like Vsync wasn't doing its job properly, then I enabled "Force 2D GPU Rendering" , "Force 4x MSAA" and "Disable HW Overlays" this greatly improved it so that it was on par with any of the other ROMs I used. However that little stutter was still there.
This ROM/Kernel supported GPU and CPU overclocking. I found out that with both cores forced to maximum speed (eg performance governor) the issues was almost completely eradicated, or extremely hard to notice. But it is just not feasable to run my phone like this. I swear I shouldn't be experiencing this stutter...
Currently running CPU1 on performance and CPU0 on badass (I am assuming CPU1 will sleep when screen is off).
Well, Im running my S with ONDEMAND governor, 1512Mhz max, 384Mhz min. I/O Scheduler is set to CFQ.
On my moms XPeria P I run SmartAssV2 / SIO, and it greatly improved both batterylife and performance on that slow-ass device
I also turned off all Window Animation things in Dev. options and turned on force GPU rendering.
Edit: These settings are applied to both cores.