Well, i'm refering to the very low FPS in games, apps, etc when dragging on the screen. This was reported time and time again, i remember Menneisyys complaining about it too. Well, i'm 99% sure this is fixed on the Kaiser, but only with the latest 6.1 ROM. maybe the experts can port this to other phones so we can all enjoy. And maybe you can tell me of a way to test this for sure.
RPG0 said:
Well, i'm refering to the very low FPS in games, apps, etc when dragging on the screen. This was reported time and time again, i remember Menneisyys complaining about it too. Well, i'm 99% sure this is fixed on the Kaiser, but only with the latest 6.1 ROM. maybe the experts can port this to other phones so we can all enjoy. And maybe you can tell me of a way to test this for sure.
Click to expand...
Click to collapse
Wowz! Great!
(BTW, the easiest way of testing this is via acbTaskMan.)
I'm not sure what to think... I used acbTaskMan and when i move the stylus on the screen i get the CPU to 60% usage (the most i got by moving the stylus VERY FAST). Is this the same behaviour as usual ?
The reason i think it's better with the new ROM is my own application which would go from 25 FPS to about 6 when touching the screen BEFORE, and now the FPS stays at 25 FPS even if i touch the screen.
RPG0 said:
I'm not sure what to think... I used acbTaskMan and when i move the stylus on the screen i get the CPU to 60% usage (the most i got by moving the stylus VERY FAST). Is this the same behaviour as usual ?
Click to expand...
Click to collapse
It is the same behaviour - on XScale devices, there isn't any CPU usage during this. The non-XScale drivers are ****ed up.
The reason i think it's better with the new ROM is my own application which would go from 25 FPS to about 6 when touching the screen BEFORE, and now the FPS stays at 25 FPS even if i touch the screen.
Click to expand...
Click to collapse
They may have tweaked the system somewhere else? Dunno.
Despite all apps/menus being fast, the Sensation 4G still feels sluggish due to a significant touchscreen input lag, also known as "touch lag" or "touchscreen latency". I see the same amount of lag with clean installs of stock GB 2.3.4 and ICS ARHD 6.6.1 /w overclock to 1.6Ghz.
This video/article (of a Galaxy SII) illustrates the problem.
Here is another video showing the effect that I'm talking about.
I've tried increasing/decreasing the "windowsmgr.max_events_per_sec" in build.props but that only affect smoothness, not overall lag or latency in following my finger. I've been using the free "Touch Test" app to compare different phones. The iPhone 4 and Galaxy S Blaze have MUCH less lag, and hence feel more responsive overall. The Blaze is an Android phone, so all of Android is not to blame (as the first video suggests).
Is there a hidden setting somewhere to help fix this or is the touch sensor in the Sensation just too slow? A fix for ARHD ICS would be ideal since I plan on running that.
UPDATE
I am a programmer but new to Android and mobile platforms. Assuming the touch screen is implemented as a polling input device, is a kernel hack that increases the polling rate possible? I am looking at the Sensation ICS kernel driver code, but I have no idea what I'm doing... Not even sure which driver's are applicable to the touchscreen yet...
Nvm, we need to decrease the touchscreen latency, polling rate won't affect that...
UPDATE
The following seem to have no effect on the touch lag:
Upgrading to ICS with ARHD 6.6.1 or Virtuos 4.0.1
Using Sebastian or faux123 kernels for ARHD
Overclocking up to 1.7Ghz
Using SuperCharger /w or w/o Nitro Lag Nullifier
Increasing/decreasing windowsmgr.max_events_per_sec in build.props
I have never experienced any lag at all with my phone running ARHD...
I cant recall seeing any threads regarding this either ??? Maybe its a hardware fault ?? If it is a really noticeable severe lag
azzledazzle said:
I cant recall seeing any threads regarding this either ???
Click to expand...
Click to collapse
This (old) thread mentions the Sensation. There are a couple threads around in other phone forums (SGS2 and DROIDX)
azzledazzle said:
Maybe its a hardware fault ?? If it is a really noticeable severe lag
Click to expand...
Click to collapse
It is not "severe". I have 2 Sensations and both behave similarly. I'm new to Android so maybe its just something I'm not used to, but seeing as how the Galaxy Blaze 4G hardly has any, the Sensation seems slow by comparison.
Really it seems like there should be a (hidden) setting somewhere because the CPU isn't struggling in the slightest. If the touch digitizer is just slow though, then there is no hope...
Well certain kernels and tweak apps have lots of hidden features. GPU rendering and such.... I dont really understand what they all are because i dont have any issues, so i dont bother to learn about things that dont affect me lol
maybe you could try a custom kernel and install leedroid tweaks. ??
azzledazzle said:
maybe you could try a custom kernel and install leedroid tweaks. ??
Click to expand...
Click to collapse
Yeah, I'm in the process of just trying everything. I was hoping maybe someone knew something about it so that I could avoid the shotgun approach
Ideally the fix would be a setting at the firmware level. The lag is even apparent in 4EXT and CWM Touch for example. But I would gladly settle for a kernel level hack so I have fast touch when actually using my phone...
demonsavatar said:
Despite all apps/menus being fast, the Sensation 4G still feels sluggish due to a significant touchscreen input lag, also known as "touch lag" or "touchscreen latency". I see the same amount of lag with clean installs of stock GB 2.3.4 and ICS ARHD 6.6.1 /w overclock to 1.6Ghz.
This video/article (of a Galaxy SII) illustrates the problem.
I've tried increasing/decreasing the "windowsmgr.max_events_per_sec" in build.props but that only affect smoothness, not overall lag or latency in following my finger. I've been using the free "Touch Test" app to compare different phones. The iPhone 4 and Galaxy S Blaze have MUCH less lag, and hence feel more responsive overall.
Is there a hidden setting somewhere to help fix this or is the touch sensor in the Sensation just too slow? A fix for ARHD ICS would be ideal since I plan on running that.
Click to expand...
Click to collapse
i have the same lag i had the lag from gb rom and now on ics arhd i really hate it when you touch somewhere and it shows the touch later rather than picking it up straight away
Recommend v6 supercharger and nitro lag nullifier. Makes my 1.5GHz sensation feel like 1.8GHz!
http://forum.xda-developers.com/showthread.php?t=991276
sent from HTC Pyramid using Tapatalk
The easiest way to see the lag if you have an ICS rom installed is enable Settings->Developer Options->Show touches. Move your finger around on the screen and see how far back the dot trails your finger.
Shery4life said:
i have the same lag
Click to expand...
Click to collapse
Good to know I'm not the only one. I think more people may have it, but they are used to it?!? If this could be fixed it would make the phone feel much faster. I actually played with a single-core lumia 710 windows phone and the touchscreen responds quite fast. Same thing with Iphone 4. This is part of how Microsoft/Nokia/Apple make their slow hardware feel fast.
stringer7 said:
Recommend v6 supercharger and nitro lag nullifier.
Click to expand...
Click to collapse
Tried these. Supercharger is also an option when installing ARHD, which I did choose. Nitro Lag Nullifier is a bunch of build.prop settings which didn't make a difference in the touch lag.
here watch this video
http://research.microsoft.com/apps/video/default.aspx?id=160670
and tell me in which latency htrc senastion falls
and also with you experience can you also tell which one iphhone 4 falls under
here what i think about all the andriod that they have latenc of 100 millisecond
and for iphone, ipad, and ipod have latency of 50 millisecond
and since i have used alot of andriod devices i think that some andriod devices have latency of 200 millisecond or more
but for iphone i think that there latency are 50millisecond
Shery4life said:
here watch this video
http://research.microsoft.com/apps/video/default.aspx?id=160670
and tell me in which latency htrc senastion falls
and also with you experience can you also tell which one iphhone 4 falls under
here what i think about all the andriod that they have latenc of 100 millisecond
and for iphone, ipad, and ipod have latency of 50 millisecond
Click to expand...
Click to collapse
Yeah I saw that video. Not sure how fast they are moving their finger, but if we are talking in relative terms, the Sensation is definitely in the 100ms range, the Windows phone is somewhere between 100ms and 50ms. The iPhone and the Galaxy Blaze are around 50ms. Again, these are relative comparisons, the numbers dont mean much unless we know how fast he is moving his finger in the video.
The limit is clearly not the entire Android platform as the Galaxy S Blaze responds quickly.
I am looking through the kernel driver code to see if anything makes sense. I am a programmer but I've never touched Android or mobile platforms before, so I have no idea what I'm doing...
Any DEVs with kernel and driver experience care to join the discussion? I'm guessing the touch screen is implemented as a polling input device. If we can increase the polling rate, it may go faster. Of course, the hardware may impose some limit on that...
UPDATE: I just realized polling rate has nothing to do with it. It is just input latency. Harder problem to fix...might just be hardware limitation.
demonsavatar said:
Yeah I saw that video. Not sure how fast they are moving their finger, but if we are talking in relative terms, the Sensation is definitely in the 100ms range, the Windows phone is somewhere between 100ms and 50ms. The iPhone and the Galaxy Blaze are around 50ms. Again, these are relative comparisons, the numbers dont mean much unless we know how fast he is moving his finger in the video.
The limit is clearly not the entire Android platform as the Galaxy S Blaze responds quickly.
I am looking through the kernel driver code to see if anything makes sense. I am a programmer but I've never touched Android or mobile platforms before, so I have no idea what I'm doing...
Any DEVs with kernel and driver experience care to join the discussion? I'm guessing the touch screen is implemented as a polling input device. If we can increase the polling rate, it may go faster. Of course, the hardware may impose some limit on that...
UPDATE: I just realized polling rate has nothing to do with it. It is just input latency. Harder problem to fix...might just be hardware limitation.
Click to expand...
Click to collapse
I live in UK and I don't think we have galaxy blaze in UK but then again I can be wrong
But like I said I have used iPhones iPod and iPad and the experience I had from these devices made me think that the latency is around 50 and my phone like sensation have 100 and I'm not sure if galaxy s2 have 100 or 50 latency but one thing I can say is that s2 is much more responsive than any other android I have used. But compare to iPhone I would say it is a bit laggy and I would put it around 75 and even 75 latency touch experience is still better than 100 I would love it manufacturer stay making new devices with 1 latency. But even if they bring out 10 latency I wouldn't mind but to keep the devices with 100 latency I think is bull**** and as a customer I will love a device with good touch experience.
Sent from my HTC Sensation using xda premium
demonsavatar said:
Yeah I saw that video. Not sure how fast they are moving their finger, but if we are talking in relative terms, the Sensation is definitely in the 100ms range, the Windows phone is somewhere between 100ms and 50ms. The iPhone and the Galaxy Blaze are around 50ms. Again, these are relative comparisons, the numbers dont mean much unless we know how fast he is moving his finger in the video.
The limit is clearly not the entire Android platform as the Galaxy S Blaze responds quickly.
I am looking through the kernel driver code to see if anything makes sense. I am a programmer but I've never touched Android or mobile platforms before, so I have no idea what I'm doing...
Any DEVs with kernel and driver experience care to join the discussion? I'm guessing the touch screen is implemented as a polling input device. If we can increase the polling rate, it may go faster. Of course, the hardware may impose some limit on that...
UPDATE: I just realized polling rate has nothing to do with it. It is just input latency. Harder problem to fix...might just be hardware limitation.
Click to expand...
Click to collapse
Sorry to resurrect an old thread, but there isn't much discussion on the internet going on regarding this issue. I used to own a HTC Desire (Oxygen Rom 2.3) and recently upgraded to a Galaxy S3 (LTE) and the input latency is no different. I have also tested using hardware controllers via bluetooth such as Wiimotes and PS3 gamepads, same results on 2 very different devices.
I was planning on using my device for some emulation (SNES, etc) but the input latency makes platforming games unplayable. I've read that AMOLED screens are supposed to be as responsive (in both pixel reponse and input delay) as plasma screens, so I'm pretty sure that the screen hardware isn't at fault here. From the little information I have scrounged together from the internet, it is the Android OS and the way it is written. All devices, all applications.
When my HDMI adapter for my S3 arrives, I'm going to test using both the touch screen and a hardware gamepad on a screen I know to have negligible input lag.
Some people aren't sensitive to noticing input latency, but its very frustrating for people like me that do. I have a quad core in my pocket with 2GB ram and I'm dealing with 100ms+ input latency in everything I do, despite getting awesome buttery smooth frame rates.
iOS has Android beat in this area, and I'm yet to use one yet, but the Microsoft Surface is said to boast a 1-2ms delay on their touch input.
Knowing that my hardware is more than capable of great response makes me sad. But I have a feeling that rom nor kernel alone can fix this issue.
I've done a bit of searching for an answer & I got to that point, you know, the one which coincides with a deep psychological urge to start ripping out your own hair. Yeah, that one! So, even though I am not technically a developer, I decided to register. I figured my input on ROMs & whatnot would, to some extent, eventually be appreciate, despite my... disability.
Anywho, here's the deal. I want to disable my devices primary display in favor of an external display connected via MHL. I am aware that there could be hardware limitations which would prevent such a configuration, but it would be interesting to know what they are if that would happen to be the case. If you're still somewhat interested, I'm running Android 4.4.2 on a Verizon Galaxy Note 3 (SM-N900V).
If you're wondering why, the Note 3 caps the secondary displays refresh rate at 30Hz (as far as I know). There's also a pretty significant performance hit over MHL (go figure) so I'm guessing the 30Hz refresh rate is in place to prevent the system slowing to a crawl. It would be awesome if I could completely disable the screen on the Note 3 in favor of an external display & in so doing achieve full performance. I understand this could entail loosing all the functions associated with the screen & I'm okay with that, but seeing as how the Snapdragon should support an external display resolution of 1080p @ 60Hz (on paper, sort of, I figure): I'll remain curiously frustrated for the time being.
So, yeah. There it is. Thanks. =)
Hi,
I've noticed micro-stutter in transition animations to the point where im convinced its capped to 30fps.
I looked into the issue and checked the hardware specs using adb, and noticed that the display itself only had a refresh rate of 58hz. This shouldnt be a problem (doubt anyone could see a 2hz difference) but somehow it seems to be. I believe it has something to do with vsync recognizing this and cutting the fps to 30 since it doesnt support 58fps. Either that or vsync is capped to 30fps, in which case it'd be helpful if someone could tell me what I can do, if anything. (is it posisble to disable vsync altogether in /sys/module/DC/vsync_enabled? It's not exposed)
Don't really know why it bugs me so much, but it does, it makes everything look choppy.
Thanks.
Hi there and welcome to assist,
Tell us more about your device, please.
Thanks
The first day I had my GS22U I noticed what I thought was some sort of odd screen adjustments but thought it may be adaptive brightness learning my habits. As I've used the phone I was able to reliably replicate my issue. Anytime I'm using adaptive refresh rate and I'm using a text field I can see what appears to be very subtle gradient shifts or flickering both when I start typing and when I stop typing. This is especially noticable in Google chromes search bar, Facebook messenger and reddit text fields. If you use a camera to look at the display it almost appears as an old school crt monitor when you see it through a camera. I was able to replicate this issue on my wife's device as well and the issue can be resolved by lowering the refresh rate to 60hz.
Has anyone else noticed this issue, or would car to try to replicate the issue? It is extremely subtle and easiest to detect using a camera to record it. Is there anyway to lock my refresh rate to a higher frequency with root permission?
Update, I happened to scroll down and see the galaxy max hz app that allowed me control over the refresh rate and I noticed that certain frequency would create the aforementioned issue and certain frequencies wouldn't. It seems as if seeing the min to 60 and max to 120 has resolved my flicker issue. Edit: never mind. It seems that different frequencies or the changing of frequencies tends to make the issue worse.
i turned it off, phone is very laggy with it. my screen is flickering
Now it seems as if I'm having a hard time noticing it with my naked eye but it seems to be getting worse when I look at it through a camera. I'm wondering if I should trade this in as a defective device.
yourself88xbl said:
Now it seems as if I'm having a hard time noticing it with my naked eye but it seems to be getting worse when I look at it through a camera. I'm wondering if I should trade this in as a defective device.
Click to expand...
Click to collapse
do you look at your phone through a camera often?
Lennyuk said:
do you look at your phone through a camera often?
Click to expand...
Click to collapse
No but worried it's going to get worse and become even more noticable with the naked eye. I wouldn't have thought to look at it through a camera if I wasn't noticing something I noticed with my naked eye.
yourself88xbl said:
Update, I happened to scroll down and see the galaxy max hz app that allowed me control over the refresh rate and I noticed that certain frequency would create the aforementioned issue and certain frequencies wouldn't. It seems as if seeing the min to 60 and max to 120 has resolved my flicker issue. Edit: never mind. It seems that different frequencies or the changing of frequencies tends to make the issue worse.
Click to expand...
Click to collapse
Hey bro , did you fix that issue ??