I went from an Optimus 3D to the Note II
The Note 2 is times better of course, but there is one thing i cant get over.... INPUT LAG
The Optimus 3D is much more responsive in games... I just cant get the timing right in most games because of it... its very noticble
Is there anything i can do about this?
No there is no solution. The Tegra 3 devices have the lowest input lag. The Note 2 is a horrible device. The Nexus 4 is by far the "smoothest" Android device i.e. there is much less microstuttering in the animations, but it also have visible input lag. If you want minimimal input lag buy an iPhone. Once you use an iPhone 5, you'll facepalm for every Android device that you foolishly thought was responsive or had "surpassed" the iPhone.
You might want to try aosp on your phone.
Sent from the rabbit hole.
bushako said:
You might want to try aosp on your phone.
Sent from the rabbit hole.
Click to expand...
Click to collapse
It's a hardware issue. No ROM can counter the input latency between when you touch the screen and it registers the touch.
I think it's do with software optimization/config. I'm not that thorough with this kind of issue but I read a while back its just the way android and iOS handles touch input. The lag is probably due to the way android processes between an accidental or intentional touch.
Sent from the rabbit hole.
bushako said:
I think it's do with software optimization/config. I'm not that thorough with this kind of issue but I read a while back its just the way android and iOS handles touch input. The lag is probably due to the way android processes between an accidental or intentional touch.
Sent from the rabbit hole.
Click to expand...
Click to collapse
Accidental touch filtering will have no effect when dragging an object on the screen. Even while dragging a list or page it is centimetres behind you finger. On iOS it is almost stuck to your finger. The Show Touches developer option will demonstrate this clearly.
The problem exists because of the nonstandard 58hz display refreshrate on our note2. There's no way to get around it.
from my understanding, most of the lag is caused by project butter. vsync with constant triple buffer means frames are being prerendered, which means response to touches will be seen 2-3 frames behind each time. thats around 16.6ms of lag introduced per prerendered frame (assuming 60hz), which can be noticeable in fast paced games.
I havent noticed any input lag with the Galaxy S/S2/S3 and Note 1, I would suppose all of the devices have the same input lag?
KurianOfBorg said:
Accidental touch filtering will have no effect when dragging an object on the screen. Even while dragging a list or page it is centimetres behind you finger. On iOS it is almost stuck to your finger. The Show Touches developer option will demonstrate this clearly.
Click to expand...
Click to collapse
Yea just checked it out and I have to agree. Although the iPhone does have lag but not as much as the Note 2.
Sent from the rabbit hole.
EarlZ said:
I havent noticed any input lag with the Galaxy S/S2/S3 and Note 1, I would suppose all of the devices have the same input lag?
Click to expand...
Click to collapse
Hi,
Then you probably don't notice it, maybe cause for you, this is the way a phone has to respond, and maybe you're not used to very low latency devices (and also screen and computer mouses that can sometimes approach 0ms latency).
My hope is that a screen can't have that much latency, so it HAS to have a way to reduce this horrible input lag. Yes, for me it's horrible cause i'm used to no latency, and there is obviously more than 1/10s latency here : more than my SGS1. :facepalm:
Kernel... Kernel... Kernel...
Sent from my GT-N7100 using xda premium
oulouloul said:
Kernel... Kernel... Kernel...
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Didn't wanna tweak my note 2 but i will maybe be forced to it...
I'm talking about input lag, not being laggy, do you confirm that you saw an improvement on display/touch latency with another kernel ? If yes, wich one(s) please ?
UltimateByte said:
Didn't wanna tweak my note 2 but i will maybe be forced to it...
I'm talking about input lag, not being laggy, do you confirm that you saw an improvement on display/touch latency with another kernel ? If yes, wich one(s) please ?
Click to expand...
Click to collapse
i have rooted and tweaked my note2 (just like all of my android devices) first day. Because of this i cant give an answer for stock kernels..
But i never noticed lag problem on games or any other area on NEAK kernel.
Hope it helps
Siyah-Beyaz Ölüm-Yaşam 1903
lag not found in sgs i9000
i know about this lag, its very obvious for note2. but for my old sgs i9000 with cm10.1, there's not lag. its both jelly bean. i think it has to do with vsync which only max out at 60. could this be modified at the kernel level?
Maybe this app can do this
https://play.google.com/store/apps/details?id=rs.pedjaapps.KernelTuner
Siyah-Beyaz Ölüm-Yaşam 1903
oulouloul said:
i have rooted and tweaked my note2 (just like all of my android devices) first day. Because of this i cant give an answer for stock kernels..
But i never noticed lag problem on games or any other area on NEAK kernel.
Hope it helps
Siyah-Beyaz Ölüm-Yaşam 1903
Click to expand...
Click to collapse
Nope, doesn't help, cause maybe you don't even notice it, like at least 80% of poeple.
I'll try rooting and your app first, thanks for trying to help.
psycotrompus -> Not a problem to be limited to 60fps, as the screen is 60hz (or 58hz here, not sure), but for sure yes : Vsync adds latency, it pre renders between 2 to 4 frames, so 2 to 4x 1/60s : 30 to 60ms latency, just for that step. Add the capacitive detection, the screen hardware input lag : Can be easy 120ms latency minimum. :s
I consider that after 50ms, the feeling isn't even natural, and above 100ms, it feels unresponsive.
I'm still searching but i'm not sure if old methods for rooting are working on the updated ROM, if i could avoid formating or using my JigRig, would be good , please does anyone know ?
It's pretty bad on the Note 2 I find. My old Desire was better as is my wife's Xperia Ray.
For anyone who doesn't notice it bring down the notification bar and move your finger up and down and your finger can easily be 2cm ahead of where the bar is on screen. Or maybe don't do it or you might start noticing it.
Chrissssssss said:
It's pretty bad on the Note 2 I find. My old Desire was better as is my wife's Xperia Ray.
For anyone who doesn't notice it bring down the notification bar and move your finger up and down and your finger can easily be 2cm ahead of where the bar is on screen. Or maybe don't do it or you might start noticing it.
Click to expand...
Click to collapse
You can also go to your app list, put your finger on an icon, move right and left (or up and down depending of the scrolling orientation of your app list), quite fast => If at anytime you're able to see the icon that is supposed to be under your finger, means the display's late compared to your finger, and you can conclude that there IS input lag. Then if you don't notice it in basic use, then good for you, but I (some of us) do.
Related
I am getting significant lag when switching from portrait to landscape orientation, which was not present on my Galaxy S2. Anyone getting this as well?
Yes, me too. It's even slower than my Desire. Only got it yesterday afternoon so haven't played with it a massive amount, but I have a gut feeling it's an ICS issue.
kingronnie said:
Yes, me too. It's even slower than my Desire. Only got it yesterday afternoon so haven't played with it a massive amount, but I have a gut feeling it's an ICS issue.
Click to expand...
Click to collapse
I am getting this as well but I don't think its an ICS issue.. it seems more like an ICS feature.. who knows.. its not that bothersome though.
I remember with my orginal desire I wished the rotation was less responsive.
Are you referring to the animation lagging or that there is a delay before it starts the transition?
If it's the latter, i do believe it's considered a "feature" to prevent accidental changes in orientation.
Theres going to be a whole host of errors and issues... brand new os barely out of beta.
Should be fun!
I started a thread about this yesterday its my main issue with the device.
i actually prefer it taking a while to spin, my Desire used to annoy me so much the way it was so sensitive i ended up disabling auto rotate most of the time :/
FISKER_Q said:
Are you referring to the animation lagging or that there is a delay before it starts the transition?
If it's the latter, i do believe it's considered a "feature" to prevent accidental changes in orientation.
Click to expand...
Click to collapse
It's the latter. Transition animations can be turned off and it doesn't change a thing. Probably a good thing to prevent accidental orientation changes, but I would give users an option to set it the way they want.
alsex87 said:
i actually prefer it taking a while to spin, my Desire used to annoy me so much the way it was so sensitive i ended up disabling auto rotate most of the time :/
Click to expand...
Click to collapse
Yeah - I wouldn't class this as "lag", it's just a delay to stop accidental rotation.
This used to annoy the hell out of me too on the Desire Don't have this problem anymore.
FISKER_Q said:
Are you referring to the animation lagging or that there is a delay before it starts the transition?
If it's the latter, i do believe it's considered a "feature" to prevent accidental changes in orientation.
Click to expand...
Click to collapse
Yes, it's the latter. My Desire didn't bother me, so it's a personal preference thing. With this in mind, surely there should be an option to change the delay time? Maybe something for 4.1!
I suppose everyone has their individual preferences; for me it's a bit annoying with the delay especially when looking at photos in the gallery, where I want the transition to be pretty quick.
I have 2.3.4 and sense 2.1. Everything works fine except the lock screen is very unresponsive. I literally have to punch the screen with my finger a few times before it wakes up. I was wondering if the newer versions of sense fix the lock screen?
I have the same problem from time to time. Restarting my phone normally sorts it out.
I wish that was my answer but Its not. At least not for me.
Others have found this post useful and it seems it is similar to your issue. ;-)
I've tried that several times. Infact it helped me calibrate my touch screen after I broke the original. I've honestly had the same issue even with the original screen.
Cataulin said:
I have 2.3.4 and sense 2.1. Everything works fine except the lock screen is very unresponsive. I literally have to punch the screen with my finger a few times before it wakes up. I was wondering if the newer versions of sense fix the lock screen?
Click to expand...
Click to collapse
If you aren't adamant about Sense, you could try flashing a Sense-less ROM. In my experience, it improves much on performance.
When i bought my WildfireS i had the same problem , stock came with 2.3.3 . But when i updated to the official 2.3.5 problem solved. U Can try different rom also .
Sent from my Wildfire S using XDA
sorry for taking so long to get back to you guys.
I've got a VM Wildfire S thats CDMA and well.....None of the other roms seem to work. I;ve tried Wildchild but its not picking up my service. Simonsense3.5 seems to be okay but things like music crash every now and again. I do still have the unresponsive screen issue but its not as bad with simonsense. I do seem to have a deadzone on my screen for the I key. Specificly the I key. if I switch into that horrible swipe the screen does not track any inputs exactly on or bordering that specific letter. Anyway I can fix that?
Also what else should I be doing now that i've been able to get this phone in a better rom?
Set the minimum overclock limit in No frills to something lieke 245 Mhz or above until it solves.
It worked for me when I used sense roms.
Hope it helped..
Try editing your build.prop
With the touch responsive tweak.
It worked for me
Sent from my HTC_A510c using XDA
cpie20 said:
Try editing your build.prop
With the touch responsive tweak.
It worked for me
Sent from my HTC_A510c using XDA
Click to expand...
Click to collapse
And which tweak are we talking about here? My lockscreen gets quite unresponsive as well. Tried reverting to the slide lockscreen off earlier versions but didn't help either. Tried the solution mentioned on the other thread (Post#4) and neither did that. I have a hunch it has something to do with the sensor, atleast on mine. I've noticed it acts crazy especially under low-light areas, or say if it had been in my pocket for ages. Ah well, hoping to find a solution soon.
spit_fire said:
And which tweak are we talking about here? My lockscreen gets quite unresponsive as well. Tried reverting to the slide lockscreen off earlier versions but didn't help either. Tried the solution mentioned on the other thread (Post#4) and neither did that. I have a hunch it has something to do with the sensor, atleast on mine. I've noticed it acts crazy especially under low-light areas, or say if it had been in my pocket for ages. Ah well, hoping to find a solution soon.
Click to expand...
Click to collapse
This worked for me.
#Helps Scrolling Responsiveness windowsmgr. .performance.tuning=1 Video.accelerate.hw=1
Sent from my HTC_A510c using XDA
spit_fire said:
And which tweak are we talking about here? My lockscreen gets quite unresponsive as well. Tried reverting to the slide lockscreen off earlier versions but didn't help either. Tried the solution mentioned on the other thread (Post#4) and neither did that. I have a hunch it has something to do with the sensor, atleast on mine. I've noticed it acts crazy especially under low-light areas, or say if it had been in my pocket for ages. Ah well, hoping to find a solution soon.
Click to expand...
Click to collapse
Did you try turning off Settings -> Sound -> Quiet ring on pickup & Pocket mode & Flip for speaker?
As cpie20 also stated you can try doing the following to your build.prop to help speed things up.
CHANGE:
Code:
view.touch_slop = 2
ADD:
Code:
# Force Launcher into Memory
ro.HOME_APP_ADJ = 1
# Enable Graphic Processor Unit
debug.sf.hw = 1
# Improve Overall Touch Responsiveness
debug.performance.tuning = 1
video.accelerate.hw = 1
# Improve Scrolling Responsiveness
windowsmgr.max_events_per_sec = 150
Thanks for that. I did switch off the Sound settings as you mentioned earlier. Apart from that, I noticed that most of the tweaks were already present on the build.prop I'm currently running on. Just changed the following:
Code:
view.touch_slop = 2 [COLOR="Red"](Was 15)[/COLOR]
# Force Launcher into Memory
ro.HOME_APP_ADJ = 1 [COLOR="red"](Wasn't there)[/COLOR]
# Improve Scrolling Responsiveness
windowsmgr.max_events_per_sec = 150 [COLOR="red"](Was set on 120)[/COLOR]
So yeah, will see how that helps and report back later.
EDIT: Seems to work great upto now. The build.prop tweaks seem to have finally fixed it. Will report back if I head into any issues but seem quite unlikely.
help
Sorry but I didn't know where to add the other code
so I have to add them at the end ... or after the code:
view.touch_slop = 2
& with thanks and respect
Ok, guys.
Everybody knows about screen rotation lag on Android. Somebody has 1 sec, somebody 5 sec lag.
At code.google.com people say it is intentional. And I do believe so. Just try landscape in browser and press home without rotating device, my screen rotates super fast and without any lag.
So does anyone know any possible way to change the delay between the phone being put in landscape and the screen start rotating?
BTW I'm on AndroidME 1.5 CM10 ROM and I did my own research with google with no luck.
Rotation lag has completely disappeared for me since I run JB.
Sent from my Galaxy Nexus using Tapatalk 2
Which ROM Do you run? I'm on JB as well and I do have 1 sec lag.
Stock.
Sent from my Galaxy Nexus using Tapatalk 2
motionz said:
Which ROM Do you run? I'm on JB as well and I do have 1 sec lag.
Click to expand...
Click to collapse
I have about a second of lag too, but it's hard for me to consider this lag. The orientation is dependant upon the accelerometer. The hardware recognizing an adjusted angle and switching the orientation all within a second seems within the confines of reason in my opinion.
Sent from my Galaxy Nexus using Tapatalk 2
The lag you speak of I believe is to make sure the user actually intended to rotate their phone. Its never really bothered me to be honest. Back when I used my Nexus S, CNA had an option to increase the response of this rotation. Not sure if that's included in their JB release though.
But that lag bother me a lot, try rotating phone while in camera you'll how amazingly fast the rotation can be.
Well yeah. It's the camera. Like I said, that tiny bit of lag is to make sure the user intentionally rotated the phone. I'm sure you can edit this via the build prop or something else.
That's why I want to know how I can do this, but I can't find the answer anywhere.
The camera app itself doesn't rotate.
Try holding the phone in landscape then click next where the onscreen keys are, you'll see that they're sill in the portrait orientation.
So I was searching around for something that would allow me to change my screen sensitivity. And I'll tell you now this app did wonders try it out on super optimized and check start on boot and restart your phone and see the difference. Its called touch screen booster in the app store
Sent from my Galaxy Nexus using Tapatalk 2
About to try this out.
SocialReject said:
About to try this out.
Click to expand...
Click to collapse
let me know if it works for you it felt different to me!
I selected super optimized and I think I feel a difference. Although, it could be all in my mind lol.
SocialReject said:
I selected super optimized and I think I feel a difference. Although, it could be all in my mind lol.
Click to expand...
Click to collapse
hahaha see that is what im afraid of lol. But if you feel different and I feel different, then maybe just maybe it is different.:victory:
SGS Touchscreen Booster?
banditnich said:
SGS Touchscreen Booster?
Click to expand...
Click to collapse
Bingo.
This was suggested before in the sensitivity bug thread. Tried it myself, doesn't do diddly squat, my pressure measurements in the development settings still read in the .40s.
SocialReject said:
Bingo.
Click to expand...
Click to collapse
isn't it only for Samsung Galax S up to Android 2.3.x.?
I tried it, set the sensitivity to 0.28 and the time to register a tap to 1 , and the UI really was quicker, overall it was alot snappier, it's not just a placebo... although , i the press values remained the same according to pointer location from developer's settings...
I lowered the sensitivity to 0.26 and managed to get a 0.27 press value, never succeeded before to go under 0.28. Anyways , with lower values than 0.28 and with quick swiping the ui starts to stutter.. not to mention even though the UI felt snapier on 0.28 + register tap 1 , but the sensitivity drop was bigger, and it needs now even harder press..so i ended up uninstalling the app...
I really hate the "recent apps" bug, the sensitivity drops, it's driving me crazy
Sent from my Galaxy Nexus using xda premium
For press values I wasn't able to get under 28 before or after applying the "Fix". Will keep using it over the day to see if I notice any difference.
Running the latest global beta 7.6.1 ROM just updated tonight... was same on 7.5.16 too
My Google pixel does not experience this.. It is really bad on games too - like Pixel Gun and Minecraft PE
I have similar stuff happening on 7.5.19 Xiaomi EU ROM. But it doesn't bother me.
Basically, I think the ROM gives some tolerance on how far should the initial movement has gone to unlock the pointer from the initial position. Definitely not a hardware problem.
Does anyone else have this issue? I am thinking about returning my MI6.. can anyone else take a video using the multitouch tester like me, and doing a touch and fine movement on the screen without making the circle move? please help! I really need to know if this is just the phone, or whether mine is faulty. thanks so much in advance
cheetah2k said:
Does anyone else have this issue? I am thinking about returning my MI6.. can anyone else take a video using the multitouch tester like me, and doing a touch and fine movement on the screen without making the circle move? please help! I really need to know if this is just the phone, or whether mine is faulty. thanks so much in advance
Click to expand...
Click to collapse
Actually the touch is very sensitive, just the way they decide that if you put down the finger like that, no mistouch (no movement is recorded). Whenever I play game, just push enough and move your finger and I have no problem with that (as a habit of gamers, I don't stiched my fingers on the screen that much).
Actually if you put the finger down and move it a little, it move the circle. But if you hard push for longer, slightly move don't move the circle. Hope you can sort it out.
Sent from my MI 6 using Tapatalk
That's what I have suggested to him too.
There shouldn't be a problem if you immediately move your finger upon touch. It's just if you don't move, it'll create some threshold in order to the cursor to be movable from the initial position.
Does the multitouch works good when you are not holding the phone in the hand? try putting the phone on a pilliow and try using 5 fingers on the screen with this multitouch tester app and see if it recognize all 5 fingers.
I had the nexus 7 2013 and it had that problem :/
someone261 said:
Does the multitouch works good when you are not holding the phone in the hand? try putting the phone on a pilliow and try using 5 fingers on the screen with this multitouch tester app and see if it recognize all 5 fingers.
I had the nexus 7 2013 and it had that problem :/
Click to expand...
Click to collapse
There's actually no problems at all touching the screen. its only when I touch then drag, I need to move my finger greater than 5mm for it to recognise the finger is moving - if moving the finger slow... Watch the video I posted in first post and you understand.
In a game, for example. playing a FPS game like Minecraft - you select the block you want to remove and then you swipe your finger from that block to the next its very jerky, because the pointer does not unlock with small finger movement. takes big movement then its unlocked. once unlocked its fine - the whole time I don't lift my finger from the screen..
So its really annoying playing games - because I have to touch the screen, then swipe to unlock the pointer, then I can aim and shoot at the enemy or remove blocks in minecraft.
Some have said its the game, but you can also try with the stock launcher - going between screens of apps, you swipe left or right, it takes 5mm finger movement before the screen starts to move to the next..
I tried the inbuilt Finger touch sensor tester, and the touch and move finger 5mm is represented as 2 pixel dots - instead of a line. so something is farked up in the software. I have 2 x MI6 (bought another to test) and both seems the same... Xiaomi need to fix...
Well my Mi 6 is on the way from GearBest China and when i will get it i will install the Global Rom and will try to do this test with this app and will see if i have the same problem as you.
Purchased mine on Gearbest aswell (international rom), came with 8.0.2.0 upgradeable to 8.2.2.0, I upgraded and I have not this problem at all.
Maybe they fixed it with the latest update?
someone261 said:
Maybe they fixed it with the latest update?
Click to expand...
Click to collapse
I'm on 8.2.2.0 stable global. nup..
someone261 said:
Does the multitouch works good when you are not holding the phone in the hand? try putting the phone on a pilliow and try using 5 fingers on the screen with this multitouch tester app and see if it recognize all 5 fingers.
I had the nexus 7 2013 and it had that problem :/
Click to expand...
Click to collapse
I also have Nexus 7 2013. The problem was jittery touch when you do multi-touch. It's kinda different problem.
But the case in Nexus 7 2013, it can be fixed by pushing the fix via ADB.
Same here.
But i think the developers want it.
I think it is a feature, not a bug. For better usebility.
Yes lol, a feature that we don't really want exactly like the notification light new feature which is that it only have one color - white.
Hmmm.. Maybe I'll order the OnePlus5 when its out... and use the MI6 as a spare
cheetah2k said:
Hmmm.. Maybe I'll order the OnePlus5 when its out... and use the MI6 as a spare
Click to expand...
Click to collapse
Some googling suggests that's it possible to to calibrate the touch screen, did you try that?
https://www.reddit.com/r/Xiaomi/comments/37umy0/tip_calibrate_your_xiaomis_touchscreen/
-Zteam- said:
Some googling suggests that's it possible to to calibrate the touch screen, did you try that?
https://www.reddit.com/r/Xiaomi/comments/37umy0/tip_calibrate_your_xiaomis_touchscreen/
Click to expand...
Click to collapse
There's no "Touch calibration" option in my Xiaomi.eu ROM. Only "pass" or "fail"
-Zteam- said:
Some googling suggests that's it possible to to calibrate the touch screen, did you try that?
https://www.reddit.com/r/Xiaomi/comments/37umy0/tip_calibrate_your_xiaomis_touchscreen/
Click to expand...
Click to collapse
There's no way to calibrate the screen... a few apps on play store do nothing..
ArcOnFire said:
There's no "Touch calibration" option in my Xiaomi.eu ROM. Only "pass" or "fail"
Click to expand...
Click to collapse
cheetah2k said:
There's no way to calibrate the screen... a few apps on play store do nothing..
Click to expand...
Click to collapse
Okey, I don't own this device so I had no way to check, if it was possible or nor, I do consider buying this device myself, but that touch issue, sounds really annoying....
-Zteam- said:
Okey, I don't own this device so I had no way to check, if it was possible or nor, I do consider buying this device myself, but that touch issue, sounds really annoying....
Click to expand...
Click to collapse
I tested this, on a friends Xiaomi Rednote 4, the touch delay wasn't there as far as we could see, so it doesen't seem to a feature of MIUI, maybe it's a bug or something.
It was running MIUI 8.1 I believe.
If it is a bug, you should ask Xiaomi to fix it.