Im currently on AICP 2.5 ROM and for the past couple of weeks I have been experiencing keyboard lag. Sometimes a button on the keyboard just stops working even though the rest are working. Even swipe does not help. Ive used Swiftkey and the default AOSP keyboard but in vain. Any idea what the problem might be? This seemed to be the problem on CM11 as well.
burjism said:
Im currently on AICP 2.5 ROM and for the past couple of weeks I have been experiencing keyboard lag. Sometimes a button on the keyboard just stops working even though the rest are working. Even swipe does not help. Ive used Swiftkey and the default AOSP keyboard but in vain. Any idea what the problem might be? This seemed to be the problem on CM11 as well.
Click to expand...
Click to collapse
you might try to change governor/scheduler... i faced the same issue on another rom once and solved this way
lukes91 said:
you might try to change governor/scheduler... i faced the same issue on another rom once and solved this way
Click to expand...
Click to collapse
I'm currently on Smarmax governor with 51-1200 as min and max hz. What do you recommend?
Try ondemand or interactive and max freq 1.3
Sent from here
Related
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
After originally sending Tillus a PM as he had a similar issue with another ROM I thought I had better post here.
I have tried Oxygen, CM7 and Redux but I get this problem with all of them. Everything runs fine for a few days and then I go to unlock my phone and the screen stays blank. The keys light up but the screen stays just blank. Tried Back-Trackball-Vol down (as suggested in post linked to in PM below) but it didn't work. I then have to take out the battery and restart.
Once it starts happening the gaps between it happening get smaller and smaller. It has happened 4 or 5 times today alone.
First time, on Oxygen, my phone eventually wouldn't turn on any more and I had to get HTC to fix it under warranty.
Then I tried Redux where it happened after a few days. Someone on here suggested I look at the CPU settings. I did and saw that Redux had a power save mode, so I tried that and it seemed to work but after a few more days the same thing happened. Although this was after a reboot so perhaps the phone didn't retain power save mode afterwards.
On Sunday I loaded CM7. Worked for about 24 hours before the blank screens started.
Running ONDEMAND governor, Min 245 Mhz, Max 998 Mhz.
Any ideas?
Here is the PM I sent to Tillus for info:
Tillus said:
d10brp said:
Tillus,
Hope you don't mind me sending you a PM. I noticed you had the same issue as me (screen not turning on from lock screen http://forum.xda-developers.com/showthread.php?p=9652281#post9652281). Did you ever find a permanent solution? I'm getting this issue with Oxygen, Redux and CM7.
Thanks
Alan
Click to expand...
Click to collapse
Hi,
uhm, I think this was a specific Auraxtsense issue which was resolved eventually. I never experienced this fault again - neither in a later auraxtsense version nor in oxygen (2.0.3) which I am using now.
Are you overclocking your cpu? Maybe you set the screen-off frequency too low? Or are you using a undervolt-kernel with very low settings, especially in low cpu frequencies?
As I said, I haven't experienced this issue for a while now.
Click to expand...
Click to collapse
Did you try keeping the power button pressed for a few seconds? I know, it sounds silly
Are you sure you don't have this problem on a 2.2 rom? I don't see you mentioning it in your post. Only that you have this issue with 2.3 roms.
What kernel do you use? Try a SVS kernel, don't use a HAVS kernels for now.
Also are you sure you tried the latest version for let's say Oxygen? From the oxygen changelog:
v2.0.3
Fixed font bug introduced in previous version
Fixed pmem exhaustion *
* The pmem exhaustion was causing the so called 'black screens'
at random intervals
Click to expand...
Click to collapse
I'm fairly new to this so I have only tried 2.3 ROMs since rooting. Obviously phone has been running official sense just fine on both 2.1 and 2.2 for about a year.
Also, apologies for this, but I don't know what the kernal is. Just followed the noob video tutorial. Is it Alpharev?
Haven't tried Oxygen since RC7 so I might try it out.
Seems to be memory related as just after I posted, something slightly different happened, I pressed the lock button and the lock screen appeared but then froze. After a couple of minutes the screen eventually locked again with a very slow jerky animation. So I have just removed a couple of apps that seem to be running all of the time, App protector pro and StumbleUpon. No crashes since then (2 hours).
Sent from my HTC Desire using XDA App
So that worked for about 2 days. Now thinking maybe it is the SD card. Ordered a new one.
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.
Hi! So i installed JJ's hybrid rom 3.2, amazing rom. Been using it for a day and i noticed something odd with swiftkey 3. Sometimes when i'm typing halfway it just stops showing what i typed. it's still responding to touches but nothing comes out. The only way to fix this temporarily is to change the input to android default then return to swiftkey again. I've even tried reinstalling the app, clearing app data. problem still persists. Anyone having similar issue? Any help suggestion is appreciated
My specs:
Xperia arc LT15i
JJ's HYBRID ROM 3.2
Supercharged
Arcknight kernel 3.3 OC 1.2GHz
=EDIT=
and i also stumbled upon a serious bug. which is whenever i call someone there wont be any sound and all i could hear is the tone when they hang up. they can hear me but i cant. fixed it by factory reset, havent re-supercharge...do i need to? not sure whether its the rom the kernel or the supercharger now..
I just installed JJ's Hybrid too, I'll try swiftkey and let you know
btw, I use TouchPal ...I find it better than swiftkey
try it
working
hey, I tried swiftkey, its working smoothly
try using a different keyboard, see if thats slow too, maybe its your phones speed problem
check if the ram/cpu is full ?
Hey guys, I have updated to Android 10 from quite a sometime now(was a beta tester) and was noticing that device practically become usable after a few days of usage. Keyboard stops popping up, apps get killed in background and so on..
This issue gets fixed by a restart though. Has anyone else noticed something similar?
I am also facing issues after Android 10 update. Please let me know if you find permanent fix or solution.
Yes, same here. I reverted back to Pie. I thought I was the only one!
Sent from my SM-G960F using Tapatalk
Nope, you are not alone :crying:
i can confirm the exact same issue since OTA update to Android 10 on S9 (DBT). currently with second minor Update to DTAD build problem still there. Tried different things to work around but yet nothing helped. i assume it has something to do with memory leak on swap partition. memoryinfo & swapcheck app always show 0 byte free swap memory which cannot be freed again when this occurs. As stated before, only reset phone helps, but after 24h its the same. struggling with this since the first Q Update Version. Any suggestions highly appreciated.
Olioaglio
Auto-restart every morning
I didn't find any issue, and I didn't factory reset my device after installing the update. My phone runs quite smoothly, no issues whatsoever.
The only minor bug is that the transition animation of the clock from the lock screen to the always on display is laggy, and sometimes the instructions like "hold your phone more upright" get stuck on the always on display. I hope this will get fixed in the next update.
@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio
Olioaglio said:
@icoolguy1995
any news on this issue? Perhaps it's any app or launcher or tool some of us use in common, since it seems not everyone is affected. i have to admit, that i have really a ton of apps on my device and freqently use it. But I already had the same conditions on Pie and there never run in this lag problem,so....
Cheers, Olioaglio
Click to expand...
Click to collapse
Well I am still researching about this issue. I reported this issue couple of times to Samsung during beta testing; they said, they are unable to reproduce this issue neither they are able to see it on logs which I have sent. For me, the issue starts to appear after 91 hours of usage without a restart. Weirdly, using any keyboard other than Samsung Keyboard seems to help somewhat. I tried using Gboard and the issue somewhat mitigated but still annoying enough.
Did you guys tried reflashing the firmware using Odin?
icoolguy1995 said:
Did you guys tried reflashing the firmware using Odin?
Click to expand...
Click to collapse
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
I have reflash the firmware because it was getting unbearable. It's been 3 days, no issues yet. Will keep you guys updated.
I just cleared the System Chache and my phone is working fine now.
Same issue here. After android 10 update it's laggy as hell. Android auto crashes randomly. Spotify stops working..
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
No effect of reflashing. Same issue popup up after 4-5 days. I wonder if this is more like a hardware related issue then software?
No, i don't think so.
Got a new update, it made issue worse. Now, instead of 90 hours free of system killing spree I am getting 70 around-ish hours with good ram management. So my workaround for this is now to set auto restart in 3 days interval.
Olioaglio said:
No, i didn't. But, out of sudden since a few days the low memory bug seems gone However, i am not aware that i did something to affect this
how about you?
Olioaglio
Click to expand...
Click to collapse
Did you change your default keyboard?
icoolguy1995 said:
Did you change your default keyboard?
Click to expand...
Click to collapse
yeah, i use SwiftKey since ages.
Two updates passed (currently on G960FXXS9DTD7), so far so good (despite no mention in the changelog).