Related
Does anyone have a problem with a slow lagging keyboard while typing text messages. I noticed it after I installed the Black 2.5 rom. I have installed the keyboard mapping fix but that did not help the lagging issue.
I been typing like crazy today on my 8525/2.5 with MSN Live Messenger. Seems very fast to me..
I had the same delay...Can't remember if disabling the word completion took care of it or installing the memory performance cab from JJ that took care of it. I'm banking on the memory performance cab though.
I have noticed this issue a little bit, but if I remember correctly Ive had the problem even before isntalling any of the roms, and it only happened for the first set of characters that I types (usually the first word).
Has anyone else noticed this with the standard wm5 roms?
I've experienced the same issue.
I wonder if it was one of the patch cabs that I installed cause I have not seen a lag at all [yet]. Perhaps it is just waiting to pop up on me.
odie3 said:
I wonder if it was one of the patch cabs that I installed cause I have not seen a lag at all [yet]. Perhaps it is just waiting to pop up on me.
Click to expand...
Click to collapse
Are you talking about the pop up keyboard?
I think what the OP was taliking about is that when you first start typing with the pull out keyboard there is a slight lag, like with me, I'll start typing - it hesitates - and then it like catches up. Not only that but the screen even goes dim for a moment .
I don't remember if I had this issue before or not.
Nope, I was talking about the pull out keyboard. Seems to work very well so far. I just retested it in Work and in MSN IM.
odie3;1250895 said:
Nope, I was talking about the pull out keyboard. Seems to work very well so far. I just retested it in Work and in MSN IM.
Click to expand...
Click to collapse
Oh well.
I'm not going to concern myself too much with it, because I'm hoping by tomorrow I'll be running 3.0
Similiar typing issue here on 8525
I've noticed the same typing issue using both Black 1.2 and Black 2.5 were it often lags or simply skips a letter (usually "h" after "t" leaving "te" instead of "the" or "s" after "i" leaving "I" instead of "is")
I tried uninstalling and reinstalling the 8525 keyboard fix cab, but it does not help.
Two things I have noticed:
1.) The typing problem does not seem to appear until several days after I flash the ROM.
2.) It really only seems to affect the Messaging app. (When I type into PIE forms or Notes, the problem does not seem to exist)
Definitely did not have this problem in WM5, so I am hoping that the problem will be gone in Black 3.0
this is a real problem. I have experienced it with all wm6 roms I have installed. I have a strong feeling its related to the suggested word list that comes up....but this is a rediculous problem for us to have to deal with and should be fixed. I also agree that its limited to the messaging app.
Ezra
yes the problem i was originally talking about is with the messaging app only. i have no problems in word, or IE. I have the memory performance cab installed but noticed it before that as well. does anyone see a difference with the suggestive words disabled?
Put 3.0 on Hold
njmarchetti said:
...clip...I am hoping that the problem will be gone in Black 3.0
Click to expand...
Click to collapse
I'll PM JJ and ask him to hold off on the release of 3.0 until he's sure we won't have this issue.
Just Kidding. .
I actually started a thread about this a while ago but titled it in reference to skipping keys because I type so fast with the thumb keyboard that the device cannot keep up and omits some of my key-presses. However, someone suggested something that I had tried with WM5 (but it didn't work then) but hadn't thought to do with WM6.
Go to Settings>Input>Word Completion(tab) and change the "Suggest after entering" setting to something such as 3 or more letters. I have mine set to 4 letters and have zero problems with skipping or slow typing unless in a third party program such a TomTom.
a little out of topic...
but after changing to black 2.5 my time zone seems to be weird....i had tried to set it to GMT+8 Singapore time....but after a while it will change to another country thats GMT+8 but when i change it back to GMT+8 Singapore time.....it will be one hour early.....
I have the slow keyboard problem too.. Its making me mad.. And the black2.5 rom seems to slow down a heck of allot after a week or so use.. Any ideas why would this be aswell?? I only have 4apps installed.. One on today screen and rest only when i use it..
a slow keyboard is one thing, but skipping letters is another. (This issue pertains to not only Black, but also Custel, LVSW, and Dutty)
The thing is, when i text message, i start typing immediately after the window pops up. But for some reason, it lags, and then when it catches up i notice that my first 3 words are so are all butchered cuz letters were dropped. I didn't experience this issue with my MDA Vario / 8125. The worst that would happen is the text would lag, but would eventually catch up to my typing. And it WOULD NOT drop any letters. With the new wm6 roms for hermes, im noticing lag and letter dropping. I've tried the suggestion of even turning off autocomplete, and setting 1 word, 2 words, 3 words, and 4 words. Still having the same issue. I opened a thread about it long ago, but it just got closed because they "supposedly" deemed it a fixe issue. Well its not!
To clarify: I'm not trying to bash any of the rom chefs' work, as i am very thankful for what they do. But it would be very nice to have this issue addressed and fixed.
Has anyone tried changing the Up/Down Control repeats....
Settings/Buttons/Up Down Control?
I put mine up to max, and seems to have fixed my problem....
@ **Milo**
Hi and thanks for the sugestion , i tried it and my slow typing issue has gone. As an experiment i switched the rate back to where it was (about one third of the way up the slider) and its still gone. It seems switching the slider up to max cleared whatever setting was causing the slow down.
Im going to leave the phone on standby for a while then try it again to see if this has any effect on it.
*MILO* said:
Has anyone tried changing the Up/Down Control repeats....
Settings/Buttons/Up Down Control?
I put mine up to max, and seems to have fixed my problem....
Click to expand...
Click to collapse
And it seems to have cured mine too. Thanks mate.
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
mine is unresponsive sometimes and i have to tap on the back of the phone to get to work again. i thinks its going out soon
That's what I thought about my old one, I figured I had dropped it to much.. because I did lol but now I got a new one 2 weeks old and I'm running into the SAME problems.. I'm assuming I must be doing something wrong with how I've got **** set-up
j18yo said:
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
Click to expand...
Click to collapse
j18yo i think that your problem might be that to many programs run when you start your vogue that happened to me before and i hated it but then i heard of a program named "Space Reclaimer" FREE and it made my vogue much more responsive because the program stops any programs that start when you turn on your vogue or any windows mobile phone
I have the same problem usually under the same conditions. Mostly happens in the morning after the device has been off. Works fine for a few seconds then stops responding correctly i.e., the D-Pad stops scrolling correctly with a lag on touch response. I use CleanRAM and it still doesn't fix the prob once it occurs. Sometimes when I run CleanRAM it will occur. I've tried putting biotouch.exe and everyting BUT the kernel processes in the exceptions list and a Level 1 clean. Hard reset yesterday and haven't had the problem yet. If it continues to work, I'll post my settings.
BTW, I'm on a stock 6.1 ROM with a few apps.
j18yo said:
I had one before, dropped it a few times.. I wrote it off as that being why, well I just got a replacement one sent.. haven't dropped it once, it's been here only about 2 weeks
Randomly sometimes it won't respond to almost anything.. I'll be trying to slide the screen, it either won't at all or will go halfway like I barely touched it. I'll try clicking on things, programs, start, whatever... it'll not respond at all, I end up having to press with way more pressure than I should have to, way more.
Then sometimes without even a reset it'll start working just about normally again.. but that's rarely, usually I'll soft reset or pull the battery for a second and then it'll be fine.. for days even.. then I'll run into it again..
I noticed 2-3 times it was because I had **** updating at the time (motweets) or was receiving email.. but I've since made everything manual regarding email, and motweets updates once every 15 minutes and the amount of tweets is limited so it's not a lot..
Still, I run into this problem, and I've made sure it wasn't a program updating but I can't think of what else would make this happen, am I the only one??
Is it because there's a way to clear cache on internets and other programs and I have no idea how? (I fully close them, that's not the problem, I know my Vogue I just can't figure this out an it seems nobody else has this problem).. Not to mention I have my internet cache's directed to my storage card so as to keep my phone memory as free'd up as possible
If anyone can help..
Click to expand...
Click to collapse
What ROM are you running? I asume that wehn your new device came you loaded it the same as the old one. It has to be something with the ROM you are runnning or a problem with a program causing your issue.
My phone would do this periodically too, with Vin's latest ROMs. I turned off Manila and am running Titanium now. Interestingly - no lags when unlocking since. I'll keep Titanium on for some time to see if that makes it go away. I had an issue with both his current v2 and v4 (which I am running now).
Ive had to replace my screen twice and the whole phone once because of touch screen problems. Thank God for the insurance.
Ah yes... to what OP mentioned:
I do not beleive it is a more pressure thing. I do not think it is more pressure that is required but rather that the phone is non responsive. If you are unlocking and typing a PIN, it takes the PIN and all but it takes perhaps one digit every 5 seconds. That's my experience anyway. So it is just slower, as if something was consuming the CPU and UI is not responsive.
crazylegs91 said:
I have the same problem usually under the same conditions. Mostly happens in the morning after the device has been off. Works fine for a few seconds then stops responding correctly i.e., the D-Pad stops scrolling correctly with a lag on touch response. I use CleanRAM and it still doesn't fix the prob once it occurs. Sometimes when I run CleanRAM it will occur. I've tried putting biotouch.exe and everyting BUT the kernel processes in the exceptions list and a Level 1 clean. Hard reset yesterday and haven't had the problem yet. If it continues to work, I'll post my settings.
BTW, I'm on a stock 6.1 ROM with a few apps.
Click to expand...
Click to collapse
THIS..
It has to be the problem.. I have CleanRAM run every 12 hours or 6 hours because I figured it would help.. lol but now your saying sometimes it happens WHEN you run cleanRAM.. Im assuming it does something, or erases something it shouldnt?
This is like the 1 sole thing I have run on a schedule, I've turned off my email and everything to manual, I went into my startup folder and there was about 4-5 things I didn't need which made the battery 100% better than it was in terms of how long it lasts.. and I set-up this CleanRAM schedule on my last phone I THINK I forgot but I do know as soon as I got this 1 going I did it and I'm bout to delete the program completely and see if it'll help, I have speedbooster too which does a cleanup too I'm curious if it would have the same result..
I'll let everyone know if this ended up being my problem incase anyones in the exact same boat with the same apps
PS: I was doing level 3 cleans
j18yo said:
THIS..
It has to be the problem.. I have CleanRAM run every 12 hours or 6 hours because I figured it would help.. lol but now your saying sometimes it happens WHEN you run cleanRAM.. Im assuming it does something, or erases something it shouldnt?
This is like the 1 sole thing I have run on a schedule, I've turned off my email and everything to manual, I went into my startup folder and there was about 4-5 things I didn't need which made the battery 100% better than it was in terms of how long it lasts.. and I set-up this CleanRAM schedule on my last phone I THINK I forgot but I do know as soon as I got this 1 going I did it and I'm bout to delete the program completely and see if it'll help, I have speedbooster too which does a cleanup too I'm curious if it would have the same result..
I'll let everyone know if this ended up being my problem incase anyones in the exact same boat with the same apps
PS: I was doing level 3 cleans
Click to expand...
Click to collapse
Update: I don't think CR erases things as much as it kills processes that won't restart. Thru trial and error, I've adjusted my CleanRAM settings to where I haven't had the problem for a couple of days. I'm able to do a Level 3 cleans on a once a night schedule and during the day if need be. In settings, I have it to close all apps, launch startup progs, and display today screen. I have no exceptions listed for either running progs or startup progs. I have the most up to date version from the OTA update in the program.
The program links in my StartUp folder are: poutlook (original on ROM), sddaemon (original on ROM), WLMUpdate (original on ROM), Glossybars.exe (I added this), biotouch.exe (I added as I thought CR killing this was the source of the problem), pocketwit.exe (I added), and SIPChange (I added).
One thing I did do was delete the link for TouchPal from the Startup folder. I did this for other reasons (I use FingerKeyBoard). Not sure if this was part of the problem.
I can scroll with d-pad and no touch lag.
On a side note, can I delete any of poutlook, sddaemon, or WLMUpdate from the startup folder to save battery power?
I'm probably just a bit above a newb so sorry if I don't make sense.
Update: Just for kicks, I deleted the links for glossybars.exe and pocketwit.exe from my StartUp and it started locking again after running CleanRAM. I put them back in and it works again even after running CleanRAM. Maybe someone with more knowledge can explain this. I'm just keeping it the way it is now...
Hmm weird that you removed something not very important like pocketwit an cleanram caused problems again.. someone has to have some info on this??
I deleted everything from my StartUp folder but my SPB Mobile Shell.. I didn't have sddaemon, but I did have poutlook and WLMUpdate both of which I deleted.. then I had some other programs that aren't necessary for the phone.. I have no problems on restart or anything, and the % showed being used is stays around the 30's now instead of 40s/50s.. and when I run programs it usually reachs 50% tops now instead of 60/70% I used to get.
PS: Pocketwit isnt bad I used to praise the program but now I've tried MoTweets and.. I can't think of the other one now.. ****.. it's really good though but it seems to use a lot more phone power than MoTweets so I went back to that.
Pocketwit kept giving me problems, started saying I need to install that NET 3.5 or whatever but when I try to it says I have a later version already so it won't install, then other times it'll work completely fine.. but MoTweets I like better anyways
Ok, I give up. I restored everything to the way I had it when it was working and now I'm having problems again. After the screen turns off and I turn it back on, it locks up and won't scroll and has the touch lag issue.
Hope someone figures this out. Shouldn't have messed with success. Good luck.
crazylegs91 said:
Ok, I give up. I restored everything to the way I had it when it was working and now I'm having problems again. After the screen turns off and I turn it back on, it locks up and won't scroll and has the touch lag issue.
Hope someone figures this out. Shouldn't have messed with success. Good luck.
Click to expand...
Click to collapse
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
bigboy292000 said:
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
Click to expand...
Click to collapse
I'm running a stock Sprint 6.1 ROM. Thanks though.
bigboy292000 said:
Are you running TouchFLO?
As mentioned before -for me, turning off TouchFLO (and running Titanium) fixed this 100%...
Click to expand...
Click to collapse
I'm not using the TouchFLO interface, does that mean its still on though?
I'm not completely up on understanding all this
This was happening with Vin's Rom for me as well. I was tripping out pressing ON so many times with no screen showing up but phone light on! I believe it could be the power settings. I disabled the "Turn off device" which I believe was mentioned in his notes about the rom.
I gave up on this problem for a while but found something when researching how to disable to cube. I used the registry edit in this thread to disable to cube post #69. I didn't do any of the other steps because I'm not having memory probs (42% with pocketwit in the bckgrd).
http://forum.xda-developers.com/showthread.php?t=368269&page=7
I noticed that biotouch.exe never shows up in the running processes menu in CleanRAM and I don't have the "lock/freeze" scrolling problem any longer and I can run CleanRam without the problem occurring. I can press any item on the screen as well with no delayed response.
However, this stops you from being able to finger scroll and do the "side to side" scroll in Messaging. I never really finger scrolled and prefer using the d-pad for scrolling so losing that functionality isn't a big deal to me.
If anyone can figure out how to keep this working so smooth and have the option to finger scroll, I'd be much obliged. It just seems that biotouch.exe craps out sometimes and locks up the d-pad. If they could both work equally well....
I know there are other threads like this but each phone is unique. Wondering of anyone else is having similar issues. Every now and then (throughout the day) ill open up messages. Handecnt kik. Browser etc... And ill start typing haptic feedback working. But no letters show up. I've tried stock. Better. And gingerbread keyboards all seem to have the same issue. Any way to fox this? My Inc 1 dis the same stuff sometimes but its quite annoying. I'm also running Atk like I always do I ignore keyboard messenger.and I've also tried without ignoring it. Is this an Atk problem or glitch with these HTC devices?
Happens to me sometimes too. I usually works if i hit the back button then where im trying to type again. It must be a little software bug.
So I got rid of Atk, problem solved
So randomly my phone will be really glitchy and i don't know why. It's kind of tough to explain, but its like an extra set of hands (not mine) is touching the screen. For example i'll be in the middle of typing a word in sms and it's as if someone clicked on the screen so it stopped in the middle. Or it'll go from my keyboard typing screen to the conversation and then to select which messages to delete. It starts randomly vibrating like it does when the screen is being touched when i'm not touching it. It's really annoying cause it seems to always happen when i need to be having a serious convo lol! it'll just start vibing like crazy and then exit sms go to my apps or just open up the convo and then somehow scroll all the way up to the top! and just random **** like that. it's so annoyinggg someone helpp meeeeeee
Task Killers, Non oem chargers, and/or not doing a factory reset after the gingerbread ota will cause this possibly. You can also try clearing cache for messaging.
sent from my inc2
What's your OS.stock no stock,what's running in the background.
did you hard reset after update like above person said
Sent from my ADR6400L using XDA App
Try recalibrating it, if that doesn't work then i'm afraid you'll have to factory reset it.
sorry for the late response thanks for all you're help so far.
i'm running RMK's gingersense. i did a full wipe after installing it and updating it. i did have a lot of text messages so i changed the setting to auto delete after 100 and i stopped using task killer. it looks like its helping it hasn't occured since. thanks for all you're help guys. i just remembered that the battery would get really hot when it would glitch so maybe i just had too many messages for it to handle. thanks guys!!!
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Dubadai said:
I have a problem where, I am in a conversation in Whatsapp, and i am done writing a message, and then i lock the screen, and when i unlock it maybe 15 seconds later, i type, but nothing is showing up, its just records what i press but doesn't type. I have to go the the main screen, and reopen Whatsapp to get it working again...
Anyone else notice this?
Its really annoying if you are in an intense conversation and have to act fast
ROM: Codename Android 1.5.5
Kernel: FrancoKernel Milestone 2
I have wiped everything 1000x times and reinstalled everything. Found some people who had the same issue, but no one found a solution.
Thanks XDA,
David
Click to expand...
Click to collapse
Happens sometimes to me too and I am rooted on stock. Pretty sure it has nothing to do with us and everything to do with whatsapp having an ICS bug.
Sent from my Galaxy Nexus using Tapatalk
Whatsapp used to have exact same problem on my Nokia 5800XM too, I think it happens because of Whatsapp.
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Confirmed bug for me too
Galaxy Nexus GSM
AOKP M4
Franco M2
To everyone who replied, thank you! Makes my life easier knowing its not ROM/Kernel etc...
Filed a complain to Whatsapp, such a great app apart from this bug!
Miasmic said:
confirmed this happening occasionally on LG optimus one.
therefore, it is definitely because of the whatsapp app itself
usually i just press back button for once, back to conversation list and go back to my conversation. typing works back so you dont need to go homescreen thats two steps back
Click to expand...
Click to collapse
I usually press home button and then my Whatsapp icon on my main screen, usually goes fast, but still... rather annoying
How deep would this 'error' lie? Could devs fix it?
I get this exact same problem with Handcent! Currently using Swype, and like 30% of the time I will have to go back to the conversation list and re-select my conversation to start typing again.
Sent from my Galaxy Nexus using Tapatalk
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
ohh3nry said:
Quick question, is everyone using NovaLauncher too? It sometimes happen with normal SMS as well. But 95% of the time it is Whatsapp
Click to expand...
Click to collapse
I am also using Nova, but I'm not sure why that would affect other apps like this.
Any solution to this problem?
Got the very same at my galaxy s6, too. Android 5.1.1
I'd also like to know if there's any workarounds for this. My wife's having the issue and she's blaming me. :silly:
I may have a workaround. I have the galaxy note 3 and i use a custom rom thats pretty much close to stock and I notice that if I lock the device and unlock shortly after, I can't type anywhere, on kik, what'sapp, gosms pro, even google search. So I've just decided to test things out and see what's going on and here is what I found....
Eventually I can type again if I simply wait, but no one likes to wait but this is the longest solution.
Clearing the RAM using built in cleaner or 3rd party memory cleaner seems to allow me to type again.
I didnt like playing the guessing game in knowing how long to wait before I can type again so in kik or go sms pro, I would type one of the native apps' emoticon and then hold the backspace button down until it erases it...then I knew it was ready to let me type again (I have haptic feedback on for keyboard presses so I can look away as I hold down the backspace button - this would let me know when it eventually erased due to the haptic feedback of the smiley getting deleted).
Since the issue occurred only after unlocking, I tried turning off the lock screen completely and turning off phone and back on again....keyboard types right away with no issues!
Its more secure to have a lock screen on the phone so turning off lock screen isn't the best option unless you're like me and are the only person at home with no worries of someone else taking your phone so I decided to try something else that seemed to solve the issue, and that is..............turning off "Multiple Widgets" in lock screen.....tested and worked! I can totally type again right away after unlocking the lockscreen shortly after locking it.
This is what worked for me and for you developers out there....if you can use this to pinpoint why this happens on android, perhaps you can use this information to rectify it.
Hope I helped!!!