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
Related
Hello everybody!
I bought yesterday a Galaxy Nexus. I’ve rooted, installed clockworkmod and the ROM Android Revolution HD™ 1.3.1 | High Quality & Performance | GSM.
The big problem which I found till now is:
The screen rotates very very slow. (web browser, photos gallery, pdf documents…) with everything.
Sometimes even don’t rotate. I have deactivate all screen animations and the same duration. (2 seconds or more)
My nexus s was much faster with a beta rom with android 4.
Do I have an issue? Do you have the same problem?
Thanks in advance!
With stock rom is all so fast and smooth.
No problem at all.
MaxDNet said:
With stock rom is all so fast and smooth.
No problem at all.
Click to expand...
Click to collapse
Hello
With stock rom do you mean original rom?
Thanks in advance!
ortigosano said:
Hello
With stock rom do you mean original rom?
Thanks in advance!
Click to expand...
Click to collapse
Yes with original (Uk i believe) Version Rom.
Base Band : I9250XXkk1
Kernel : 3.0.1-ga052f63
Build : ITL41F
ortigosano said:
Hello everybody!
I bought yesterday a Galaxy Nexus. I’ve rooted, installed clockworkmod and the ROM Android Revolution HD™ 1.3.1 | High Quality & Performance | GSM.
The big problem which I found till now is:
The screen rotates very very slow. (web browser, photos gallery, pdf documents…) with everything.
Sometimes even don’t rotate. I have deactivate all screen animations and the same duration. (2 seconds or more)
My nexus s was much faster with a beta rom with android 4.
Do I have an issue? Do you have the same problem?
Thanks in advance!
Click to expand...
Click to collapse
Its googles choice for that not an issue. If you want faster rotation you should flash pauls custom rom
MaxDNet said:
Yes with original (Uk i believe) Version Rom.
Base Band : I9250XXkk1
Kernel : 3.0.1-ga052f63
Build : ITL41F
Click to expand...
Click to collapse
Grazie mille!
DJTaurus said:
Its googles choice for that not an issue. If you want faster rotation you should flash pauls custom rom
Click to expand...
Click to collapse
I will, thanks a lot!
By the way...
Wich tool for transfer data are you using for Windows?
For Mac? => http://www.android.com/filetransfer/
For Linux?
Thanks in advance!
Not sure how people are saying it's fast on stock. To me it's anything but fast... it's slow as hell.
vapotrini said:
Not sure how people are saying it's fast on stock. To me it's anything but fast... it's slow as hell.
Click to expand...
Click to collapse
Agreed. Sometimes I have to shake it after I turn it for it to even do anything. The accelerometer needs tweeking in the stock rom.
its very laggy .. and if that was " google choice " then i think it was a bad choice!
Can you guys quit repeating that google intentionally put a delay in it.
I noticed this as well - i'm quite aware of the difference between the screen not rotating and there being a delay.
There's something really quirky that's causing the phone to not recognize sometimes, I thought the new update fixed it but alas it didn't.
wonshikee said:
Can you guys quit repeating that google intentionally put a delay in it.
I noticed this as well - i'm quite aware of the difference between the screen not rotating and there being a delay.
There's something really quirky that's causing the phone to not recognize sometimes, I thought the new update fixed it but alas it didn't.
Click to expand...
Click to collapse
No, because it is a fact. There is a purposeful rotational delay.
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
No, because it is a fact. There is a purposeful rotational delay.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
What was the purpose - to make everyone think there is a problem ?
randypurcz said:
What was the purpose - to make everyone think there is a problem ?
Click to expand...
Click to collapse
So your screen doesn't accidentally rotate from holding it at a slight angle.
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
No, because it is a fact. There is a purposeful rotational delay.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
When it works right, after about a 2 second delay - it rotates.
But sometimes, it just doesn't work, I'll hold it for 10 seconds and it won't rotate like the phone didn't register it, so I have to turn the phone back and forth and the accelerometer seems to wake up again and works.
Does no one else get this behavior?
Im running the stock rom, no animations either and my screen rotation isnt all that speedy but i prefer it to my galaxy s which rotated at the slightest tilt of the phone. At least the proximity sensor on this phone doesnt lag like the GS did. I hated having to wait for the screen to respond before i could hang up the phone LOL.
wonshikee said:
When it works right, after about a 2 second delay - it rotates.
But sometimes, it just doesn't work, I'll hold it for 10 seconds and it won't rotate like the phone didn't register it, so I have to turn the phone back and forth and the accelerometer seems to wake up again and works.
Does no one else get this behavior?
Click to expand...
Click to collapse
See this is different.. I have not experienced this and had no idea you were talking about this. The delay on rotating the two seconds that you observe is intentional.. can't say not rotating at all is something I have experienced though sorry :/
Sent from my Galaxy Nexus using xda premium
Screen rotation is VERY poor on mine. Im not talking about a "lag". Sometimes there is no rotation.
Same here, if the screen is touched it rotates and behaves normal.
Please click the star here:
http://code.google.com/p/android/issues/detail?id=22561
Not noticed any issues with mine, on stock or with android revo HD 1.3.1.
Then again, it really pissed me off when my old phone always rotated with the slightest turn. Hated it. Had screen rotation turned off most the time due to it.
Only time I do like to see a landscape view is in videos, where the 'delay' is not really an issue.
So I guess I'm one of the few people who can thank google for implementing such a useful feature.
But seriously, who uses landscape often? Why?
That said, I wish the lag upon pressing the recent apps button was removed.
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.
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.
I found this on a post on another forum, the person stated that it didn't make a big difference for him.
I tried it and found a noticeable difference.
Passing it on.
Root not required.
Under Developer Options
(search Google: "Enable Developer Options LG G4") if you're not familiar
Change:
Window animation scale to .5
Transition animation scale to .5
Animator duration scale to .5
Check "Force GPU rendering"
I have been running these settings for about a week
Response time and keyboard issues seem normal, no skips or delays
Battery life does not seem to be effected
Thanks for sharing... but it's doubtful that this will have a significant impact on the touchscreen issues.
Thanks! I'll give it a shot, what's the default supposed to be for Force RTL layout direction as I'm not sure if I accidentally toggled it on or not.
Almighty1 said:
Thanks! I'll give it a shot, what's the default supposed to be for Force RTL layout direction as I'm not sure if I accidentally toggled it on or not.
Click to expand...
Click to collapse
Unchecked
Please report back your results, would like to see if others see the difference that I have. Thks
JacRyan said:
Unchecked
Please report back your results, would like to see if others see the difference that I have. Thks
Click to expand...
Click to collapse
Thanks, I noticed that with it checked, the word Password in apps was shifted to the right side so I changed it back to off... Will report back.
I will say that I am texting at my normal speed again.
Before it was 60% mistype failure.
You also can use touchscreen booster for galaxy, also works great...
Sent from my VS986 using Tapatalk
DADER said:
You also can use touchscreen booster for galaxy, also works great...
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
worked for me too!
DADER said:
You also can use touchscreen booster for galaxy, also works great...
Sent from my VS986 using Tapatalk
Click to expand...
Click to collapse
You have a link ?
Didn't make a difference for me.... What are the default/original settings for the following?
Window animation scale
Transition animation scale
Animator duration scale
Touch screen had been fixed in software release 13B, no more need for any of these placebo fixes that don't make a difference anyways.
13b might have fixed the issue but installing 13b means eliminating any possibility of a bootloader hack if it ever does come out in the near future, it's more of a bandaid solution if one is staying with 10b.