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.
My Screen has totally stop touching and Ive searched and searched for a solution.... and yet havent found any. I deleted the ts-calibration file and yet still screen no work
BUMP Help!
You mean that the screen is not working within android of with windows mobile?
If you mean windows mobile then your screen is broken or if you think it is because of the cab, you can try a hard reset.
If it is only in android then uninstall this version of android and download the .rar and extract it to your SDcard.
I have sort of the same issue. My screen doesn't work (most of the time). For some reason it is responsive sometime (not clear how to recreate that). I can see the screen is responding, although if I go to the menu and try to select a icon with my finger it holds the icon and drags it (and I cannot let it go)
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Deleting the calibration file doesn't work for me. Also I have tried hard resets and rom upgrades several times, with no succes. It looks like installing android changed something, but doesn't set it to his old state after removal.
Anybody?
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
yea i was having the same problem and couldnt figure out a solution, i deleted the ts-calibration, i've tried deleting all android files and starting over but the problem still exists. I think it might have something to do with the little bit of moisture i see under the screen because before i started seeing that, it used to work. But the screen works just fine when WinMobile is running so i dont know
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
arrrghhh said:
This is in WinMo you're having the problem...? I'm not sure what to tell you, Android doesn't touch the NAND whatsoever - so it shouldn't effect (affect?) WinMo whatsoever.
Click to expand...
Click to collapse
No, in both. This problem originated from the fact I was never able to start up a blazin android. It started booting, but for some reason never finished it. With the previous editions I never had any problems.
arrrghhh said:
If the screen is fine in WinMo, try a clean build. Not sure what could cause the screen to just stop working in only Android tho... unless of course you have a bad ts-calibration file...
When you do the screen calibration process in Android, does it work OK...?
Click to expand...
Click to collapse
I know you are replying on another user, but I still want to respond
Yesterday my screen was responding for a short moment. I have replaced the WinMo rom after that several times, no success. Also deleted android and reinstalled it again. (I've been trying trial and error for a while now, without any success.)
My WinMo rom btw was an energy build. Any similarities with other users experiencing this issue?
Is there some internal memory where these type of settings (keyboard layout and such) are stored and what not always change if you upgrade roms?
Perhaps I should go back to the original T-mobile rom.
Just upgraded to the original tmobile rom, but I'm stuck at the WinMo startscreen (tap the screen to start using it for the first time) I noticed that if you slide the phone open (keyboard visible) the display of the screen is correct. If I flip it back I'm missing parts of the screen.
dwaaz said:
But also my keyboard layout is messed up. It totally doesn't have any logic anymore. Only when entering a pincode the numbers are correct, but if you are trying to enter a number to call, it is totally messed up (numbers are symbols, letters are numbers)
Click to expand...
Click to collapse
I'm sorry for spamming this topic, but isn't it really weird that only for entering your pincode the numbers are correct, but afterwards the layout is all messed up?
6_7_8 = 123
Y_U_I = 456
H_J_K = 789
N=0
I have the feeling my phone is using system files (after login) of a completely different phone (and no.. I did use the right rom's ) This goes for the keyboard as well as the screen issue.
any bright ideas?
Just to bring it under the attention again, because I'm on the edge of sending it back to t-mobile. (I hope they are not going to charge me because I have a diamond 2 that also needs repairing, touchscreen doesn't work as well, and I'm seeing some costs coming up there. For some reason I always manage to wreck my phones in the first 2 years. )
Any bright ideas?
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slighty and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
It worked!
trotmanc said:
I had a possibly similar problem.... I thought my screen was going bad after the install, but the install wasn't the issue. It was just a coincidence.
Take a small pin and run it along the side of your touch screen. Sometimes dirt gets stuck in there and that stops it from working properly. If that does not do it, slightly and gently lift the touch screen a little bit and put it back down. That worked for me!
Sent from my MSM using XDA App
Click to expand...
Click to collapse
I was kind of skeptic here of this solution, because my phone looked quit clean. But there I was, on visit with my parents, fiddling with my phone, thought; let's put my nails between the lines next to the touchscreen..... and wtf.. it worked My screen is back up. Very surprising but good.
No I only have my keyboard to worry about. Any thoughts on that?
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Ettepetje said:
I'm experiencing a lot of problems with the SwiftKey App lately on my Note 10.1. Even though I switched most functions off, only auto-caps at start of new line is on, I get random inserted digits or even random auto-completion (which is very annoying I can tell you) . Anyone else using SwiftKey who experienced problems on the new Note 10.1?
It also can be very difficult to start a new line because it writes the 2nd, 3rd etc. letter on top of each other.
Edit: had to remove typos and random characters 3 times in the first alinea alone.
Click to expand...
Click to collapse
have you tried beta 4.3
tonytownsend said:
have you tried beta 4.3
Click to expand...
Click to collapse
Am doing so as we speak type. Nope, still buggy (same bugs).
I must be using the iPad too often because I find I'm unable to select words and then, afterwards, apply strike.
Edit: It also inserts spaces after it erroneously inserted "[ strike][ /strike]" (without the spaces) at the start of the post, in stead of around "speak", making me have to edit "[ QUOTE=tonytownsend" afterwards... Hopefully most of this is solvable in future.
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying touchscreen issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds without moving them
- If the touch indicators suddenly disappear, you have the same touchscreen issues
Kizune said:
This is just a guess, but could it be the touchscreen instead of SwiftKey?
Both my first and (after I returned it) second Note (which I purchased from another seller) have very annoying multi-touch issues.
I didn't notice it at first because the problem doesn't occur that often if you use the tablet with only one or two fingers. But then I started taking notes at the university and I noticed that I couldn't use the zoom gesture directly after I had put a part of my hand on the screen. It just stopped all of a sudden or it was very jumpy and hard to control. Single-finger operations and the S Pen kept working fine, though.
It became so annoying that I installed YAMTT and checked if anything was wrong with the touchscreen. And indeed, most of the time when I put my hand on the screen as if I was writing or drawing, the screen started to behave strangely afterwards.
I found a method to reproduce the problem all the time. It might be worth checking:
- Start YAMTT in "Touch tester" mode
- Put your whole hand on the screen for around two seconds, then lift it
- If there are some touch indicators still shown, ignore them and just proceed
- Put five fingers on the screen and wait for a few seconds
- If the touch indicators suddenly disappear, your touchscreen has multi-touch issues
Click to expand...
Click to collapse
I sure hope not. I started a whole topic on the Note 3 forum because I discovered it had a multitouch problem. Haven't been able to produce that type of multitouch issue on any of my other gear besides a Nexus 7. Will check with your method to see what it gives.
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
I discovered that my fingers got remembered (stayed) on the screen if I left 5 of them on the screen. Happened only ones though. Then I tried puting my whole hand on it for a few seconds and then the multitouch algorithm went bananas. Tried with different Multi-touch app too. I think this is a software issue, from the looks of it.
SwiftKey has been giving me problems on my 2014 Note 10.1 from day 1, but they had become 10 times worse today. I just rebooted my Note and it now behaves as normal (still somewhat buggy SwiftKey, like before). I think there are some issues in the Multitouch driver which can be triggered by the "whole hand" method described above, and possibly by other means. My MT driver had already become unstable, hence I could reproduce a defect (finger touches remaining on the screen) without the "whole hand" thing.
Kizune said:
I checked the videos in your thread and the behavior is indeed very similar to what I got:
(In the video I haven't used the method described above yet, I discovered it just today)
Click to expand...
Click to collapse
Kizune, I included your video in a topic about this Multi-touch issue, I hope you don't mind.
Of course it's okay. Let's just hope that Samsung will fix the problem ASAP, it annoys the hell out of me.
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Itchiee said:
I found the newest beta of Swiftkey to be buggy on the Note 1014 so I removed it and went back to Swype.
Too bad as I was enjoying the split keyboard mode.
Click to expand...
Click to collapse
I will very probably be doing the same. Thanks for getting back on topic.
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Sent from my HTC One using XDA Premium HD app
SlimJ87D said:
I installed SwiftKey for tablets, not the phone version. Absolutely no problems typing for me on my note.
Click to expand...
Click to collapse
I use the same (Tablet) version. Possibly it is caused by a combination of settings. I have most (aiding) options switched off. If I find the time I will experiment.
Try "Touchpal"..it's similar to Swiftkey.. it's free and has plenty of thenes. I actually like it better
Sent from my SAMSUNG-SM-N900A using xda premium
Newest SwiftKey is running perfectly for me on the Note 2014. It's so nice to be able to have a compact keyboard you can undock and move from any part of the screen to another. So convenient for applications. Highly recommended, please try it if you haven't
Since I got the device 2 months ago I have been facing a severe and weird issue, I don't understand if the problem is with the display or something else, what I found is when I type something in WhatApp or anywhere at the usual speed that we type, some alphabets needs to be pressed twice.
For example if I had to type a word "Motorola", it comes out like "Moorola". I have to cut and type again slowly and hardly. When I just type something like "Where are you going", its comes out to be "Whre are yo goig" or something like that.
I have even tried resetting the device, clearing data of keyboards and also using stock and 3rd party keyboards but the problem still persists.
Any Solution Please.:crying:
So I recently got the Pixel 4a 5G and all in all I am very satisfied. However, I got the feeling that typing is unusually buggy, meaning that when I type fast, the google keyboard identifies it as swype-style and enters a blank space after the gibberish it produced. At first I thought this might be a problem of the google keyboard, so I installed other keyboards but they showed similar behaviors. If they lack swype-features, it often happens that the cursor moves back into an already written word and such. Then I thought it might be the screencover I applied, but I got rid of it and the problem persists. Now I know that I am typing fast, but not that fast that it should be problematic and also I did _not_ experience something like it on my previous phone (which was a OnePlus One).
As this behaviour starts to annoy me, I'm just curious if someone experiences similar things with their phone or if it's something I'm doing wrong. Not really expecting any suggestions or solutions here, though if someone has a suggestion/solution/fix I'm probably up for it!
i haven't had this exact issue but i'm definitely having some muscle memory ones. my 3a xl had a nav bar so i'm having trouble adapting to a lower on the screen keyboard and my typing is messy. might be part of your issue but i've seen improvement over the last few weeks.
I'm having the exact same issue. When I type too fast, the keyboard registers swipe gestures.
Have you tried Settings, Display, Advanced, Increase touch sensitivity?
laughterwym said:
Have you tried Settings, Display, Advanced, Increase touch sensitivity?
Click to expand...
Click to collapse
Yes, unfortunately it has no effect. And if it doesn't register a swipe, it will simply not register one of the keys being pressed. I can't replicate it if I slow down my typing