I'm not sure if anyone else has run into this issue or maybe it's just my phone but my keyboard seems to lag (both stock android and smart keyboard pro). When I hit a key, it refuses to respond. I'll have to "warm up" my phone a bit by leaving it on for about 15 seconds before I can start typing comfortably, where every key is responding.
suggestions? known issue on all ROMs?
...or just my phone?
I noticed this too on AOSP ROMs but only when I had the phone plugged in. When I installed the Tiamat kernel it disappeared. What keyboard are you using? If it uses a dictionary it might need to be reset.
TheMavic said:
I noticed this too on AOSP ROMs but only when I had the phone plugged in. When I installed the Tiamat kernel it disappeared. What keyboard are you using? If it uses a dictionary it might need to be reset.
Click to expand...
Click to collapse
I'm running the tiamat kernel, too. I experience the issue on android and smart keyboard pro.
*wait, I just checked and I'm running cm7 kernel. let me try flashing tiamat again and see if that fixes the issue
**nope, I don't think flashing tiamat worked. I changed governor to "performance" so let's see what happens then
***I guess the issue is with cm7. I experienced keyboard lag with omfgb and cm7. not a fan of MIUI so I'm not sure if there's keyboard lag on that ROM. I'm running TSM now and experiencing no lag with the keyboard (or any keyboard) so I think the problem is with AOSP ROMs.
I have the same lag with any keyboard I use. I also had the same problem with my Tbolt. This happens regardless of charging or not.
I don't mean to hijack the thread but has anyone else noticed a bad lag with the XDA app? I hate it. I press see the general section and nothing happens so I hit it again and BAM it loads and in a specific thread. I understand it takes a little bit of time to build the long list of forums but not a general section of the INC2 or other device.
Related
Has anyone had this issue? I'm currently running Fresh 3.1.0.1, ran Burnt, and the stock rooted OTA ROM. When I connect my phone to the USB port or into the wall, typing in messages (handcent) responds slower than normal. There is definitely a noticeable difference in response time. It corrects itself in spurts but slows down and continues to play this tug o' war. I have netarchy's latest kernel and everything runs great. When I remove the phone from the charger, I NEVER have this problem.
What's the culprit? I have setCPU set to OC and UC when screen is off.
I can confirm a similar experience using CM6
Sent from my PC36100 using XDA App
Are there really no opinions on this matter?
I noticed that I don't have the lag issue with the new multi-touch keyboard (running 2.2). It may just be that version of the keyboard.
Best of luck
Anyone else have this problem?
I'll go into Handscent to reply to a text or open up the Dolphin browser to surf the web, and my touch input keyboard doesn't work. I'll have a cursor in the field and the DINC will vibrate when I hit the keys, but nothing appears. I have to back out and go back into whatever app I'm using sometimes five or six times for it to correct itself. It's getting very frustrating. I have tried switching to the Android keyboard when the problem is going on and have found it has the same issues.
I am running SkyRaider 3.3.2 with the 07.28 radio. Stock kernel, and stock everything else I'm pretty sure.
If anyone has any ideas or an actual fix I'd be greatly appreciative.
To me, it sounds like a kernel issue. Try flashing a different kernel like Lou's #4 and see if that helps improve the issue.
Thanks for the suggestion.
I just upgraded to SkyRaider 3.5 and so far the problem hasn't resurfaced. If it does, I may try your idea.
Thank you.
I get this problem sometimes i always have even on stock
I flashed about 2 days ago from stock to RHD 4 Beta 1, hoping that the problem will solve.
Problem is, that very often I would say, when touching the screen and even the 4 buttons it doesn't take the command.
Sometimes if I am quick enough, I press 2 times and still not receiving feedback, so I would say it lasts from 2-3 seconds and if I continuously use the screen, about 4 times per minute.
That is very annoying. It happened also in ROM stock and also now.
Anybody had that? Any ideas ?
That doesn't sound like a common issue, and it's possible you might have a hardware defect with your phone.
I'd flash it back to stock, or as close as you can find, and take it back to wherever it was purchased for a replacement or repair.
raulttro said:
I flashed about 2 days ago from stock to RHD 4 Beta 1, hoping that the problem will solve.
Problem is, that very often I would say, when touching the screen and even the 4 buttons it doesn't take the command.
Sometimes if I am quick enough, I press 2 times and still not receiving feedback, so I would say it lasts from 2-3 seconds and if I continuously use the screen, about 4 times per minute.
That is very annoying. It happened also in ROM stock and also now.
Anybody had that? Any ideas ?
Click to expand...
Click to collapse
mine does the same with stock, but its not that common it happens like once a week for like 2-3 secs, and you dont need to have apps running, i just took it as it is
I m having no such issues in my DHD and i have used ARHD since very early versions.
Are you using any programs like setcpu or cpuspeed? Which kernel are you using?
If you have your htcsense account on, it would be a better idea to turn it off as well. And finally you can recalibrate your G-sensor (settings ---display)
I did some test with more ROMs. I can confirm that it happens frequently with Stock, Revolution HD 4.0 and LeeDroid 2.3.4.
I also flashed the CM7 Rom and I didn't had that problem, but it was only for test purpose as I still wan't to use HTC Sense.
So it's clearly soft related issue. Something must do this delay. As i am handling very fast everything I use, for me it is not acceptable.
I don't use cpuspeed or setcpu
Kernel is: 2.6.35.10-g4a4b278 ( Wed 16 Feb 2011 )
I don't use HTC Account. Reclibration doesn't help.
I don't think it's a performance problem, because all runs smoothly and it happens regularely exactly after restart ( when processes are starting loading etc ) and when no application runs in background and CPU / RAM is not being heavily used.
I see you use ADHD 2.0.15 and you also tested ADHD 4 beta 2, what I am actually using.
How would you compare those? I assume you don't have the problem.
Ah! ok...it is really a strange problem though, i would say. I never had this issue being touch unresponsive.
Yes of all the ARHD builds 2.0.15 is the best one, IMO. Well, the GB build is still in beta and it lags. The battery life is claimed to be slightly better though. But i could not live without search function (which FC all the time), the tweaks we have for Froyo builds and the overall user experience with froyo is just awesome...and Mike has done great job. At the moment the version i m using is priceless...
Hi,
I have this problem where the screen doesn't respond to my touch for a few seconds.
It's not all the time, but when it happens, it is like it for a while.
My phone is on Orange UK and has not been rooted. It is just as from the factory with apps added.
I will be interested to find out if this is a serious problem or just a minor glitch as it seems to be for me.
Matthew
MattOsprey said:
Hi,
I have this problem where the screen doesn't respond to my touch for a few seconds.
It's not all the time, but when it happens, it is like it for a while.
My phone is on Orange UK and has not been rooted. It is just as from the factory with apps added.
I will be interested to find out if this is a serious problem or just a minor glitch as it seems to be for me.
Matthew
Click to expand...
Click to collapse
You have a similar problem as mine, but not so often.
What do you mean by a serious problem? It depends if it is disturbing you or if you can live with it. It won't get worse as I've seen it is not a hardware problem.
You can do the test by installing CM7 ROM and check if it does again. For me that solved the problem, but as I like to use HTC Sense, it is not an option to stay on the CM7 ROM.
raulttro said:
I did some test with more ROMs. I can confirm that it happens frequently with Stock, Revolution HD 4.0 and LeeDroid 2.3.4.
I also flashed the CM7 Rom and I didn't had that problem, but it was only for test purpose as I still wan't to use HTC Sense.
So it's clearly soft related issue. Something must do this delay. As i am handling very fast everything I use, for me it is not acceptable.
I don't use cpuspeed or setcpu
Kernel is: 2.6.35.10-g4a4b278 ( Wed 16 Feb 2011 )
I don't use HTC Account. Reclibration doesn't help.
I don't think it's a performance problem, because all runs smoothly and it happens regularely exactly after restart ( when processes are starting loading etc ) and when no application runs in background and CPU / RAM is not being heavily used.
I see you use ADHD 2.0.15 and you also tested ADHD 4 beta 2, what I am actually using.
How would you compare those? I assume you don't have the problem.
Click to expand...
Click to collapse
Just a really wild guess, which launcher are you using? As I'm using launcher pro plus and it has a tendency to freeze after restart and the screen has no response for a while, usually it force closes automatically and restarts instantly after and works perfect. I'm on CM7 latest nightly and haven't tried other roms for a while so it might not be comparable. So if you are using launcher pro then try to manually restart it if it doesn't force close itself and start again. And if you're not, well just ignore this
Hi guys,
Long time lurker, first time poster. I've been using CM7 RC2 without any issues, and recently updated to RC4. As soon as I did, my touchscreen lost a lot of responsiveness. Sliding open the drawer was no longer a simple swipe, I had to baby it along to get it to open, same thing applies to any other functions. Typing was a nightmare, because I had to press longer and harder on the screen to get it to recognize each of my keystrokes.
As soon as I switched back to my nandroid backup of RC2, everything's fine again. Any ideas? I've searched everywhere and can't find any mention of this problem, and didn't see it in the known bug list. I am using LauncherPro on top of CM7, might this be causing the issue?
Hardware 004, stock CM7 with default kernel if it matters.
THANKS!
Well I would recommend upgrading to the latest stable version, clean install, and see if that takes care of it first, along with the latest gapps.
beenyweenies said:
Hi guys,
Long time lurker, first time poster. I've been using CM7 RC2 without any issues, and recently updated to RC4. As soon as I did, my touchscreen lost a lot of responsiveness. Sliding open the drawer was no longer a simple swipe, I had to baby it along to get it to open, same thing applies to any other functions. Typing was a nightmare, because I had to press longer and harder on the screen to get it to recognize each of my keystrokes.
As soon as I switched back to my nandroid backup of RC2, everything's fine again. Any ideas? I've searched everywhere and can't find any mention of this problem, and didn't see it in the known bug list. I am using LauncherPro on top of CM7, might this be causing the issue?
Hardware 004, stock CM7 with default kernel if it matters.
THANKS!
Click to expand...
Click to collapse
Definitely would go with the stable release and you should be good to go.
Hi all,
I'm unable to post my question in the development thread for this rom (http://forum.xda-developers.com/showthread.php?t=2085828), but hopefully some of you are running the Stable 4.2.1 version of Slim's rom and can help address my question.
First off, this rom is pretty much flawless and battery life is excellent (once I found the right Kernel). The only problem I'm experiencing is with the use of my Home Button. Often times when I go to hit the Home button it pulls up the Recent Apps, as if I'm "long pressing", instead of taking me to my home default screen. I also noticed that when this happens, if I hit the Menu Button it launches Google Search, as if I were "long pressing" it.
So it's as if the Rom/Phone thinks I'm "long pressing" when not. Typically a reboot fixes it for part of the day and then the issue returns. I've used the Halo Launcher that is included in the rom as well as my preferred NOVA Launcher and the problem persists with both. I've also tried full wiping and re-flashing but the problem always turns up.
I searched the thread as well and novone has mentioned it as an issue, I'm wondering if it's a hardware problem with my actual phone? For now, Ive enabled the on-screen nav keys as a work around.
Any thoughts or help on this would be much appreciated.
-Ryan
imryanthompson said:
Hi all,
I'm unable to post my question in the development thread for this rom (http://forum.xda-developers.com/showthread.php?t=2085828), but hopefully some of you are running the Stable 4.2.1 version of Slim's rom and can help address my question.
First off, this rom is pretty much flawless and battery life is excellent (once I found the right Kernel). The only problem I'm experiencing is with the use of my Home Button. Often times when I go to hit the Home button it pulls up the Recent Apps, as if I'm "long pressing", instead of taking me to my home default screen. I also noticed that when this happens, if I hit the Menu Button it launches Google Search, as if I were "long pressing" it.
So it's as if the Rom/Phone thinks I'm "long pressing" when not. Typically a reboot fixes it for part of the day and then the issue returns. I've used the Halo Launcher that is included in the rom as well as my preferred NOVA Launcher and the problem persists with both. I've also tried full wiping and re-flashing but the problem always turns up.
I searched the thread as well and novone has mentioned it as an issue, I'm wondering if it's a hardware problem with my actual phone? For now, Ive enabled the on-screen nav keys as a work around.
Any thoughts or help on this would be much appreciated.
-Ryan
Click to expand...
Click to collapse
This seems to be a common issue with 4.2.x ROMs. As far as I've heard the exact cause is unknown and there is no known permanent fix as of yet. For what it's worth, I'm running LiquidSmooth RC2 (4.2.2) and have the same issue periodically, as do many others. As you've noticed, a reboot is the only current fix. I'm sure it's something they will eventually work out, but for now it's a minor intermittent annoyance.
melocil ate
fingolfin14 said:
This seems to be a common issue with 4.2.x ROMs. As far as I've heard the exact cause is unknown and there is no known permanent fix as of yet. For what it's worth, I'm running LiquidSmooth RC2 (4.2.2) and have the same issue periodically, as do many others. As you've noticed, a reboot is the only current fix. I'm sure it's something they will eventually work out, but for now it's a minor intermittent annoyance.
Click to expand...
Click to collapse
Ahh, gotcha. I hadn't searched through any of the other 4.2 Rom threads. Thanks.
Something just got submitted to fix it I believe. http://review.cyanogenmod.org/#/c/33383/
Sent from my SGH-T999 using xda premium