hey guys
does anyone else have a problem with their atrix, where if you type extremely fast (2-3 char per second), the atrix does not register the key?
i'm not talking about they normal keyboard lag (type and then then 3-4 sec later it shows up on the screen, got rid of that by turning off haptic feedback), my issue is that when I type fast, i can see the popup for a key, but it won't register on the screen.
for example, if i type happy, i would see the popup on the keyboard for each individual letter (H A P P Y), but it would only register H P P Y, almost like the multitouch isn't working properly.
the effect is very pronounced on aftermarket keyboards (i've tried a lot, ICS, GO, swiftkey), and they are all WORSE than the stock keyboard. the simplest fix is to type slowly, but that just ruins my train of thought.
can anyone help?
rp_guy said:
hey guys
does anyone else have a problem with their atrix, where if you type extremely fast (2-3 char per second), the atrix does not register the key?
i'm not talking about they normal keyboard lag (type and then then 3-4 sec later it shows up on the screen, got rid of that by turning off haptic feedback), my issue is that when I type fast, i can see the popup for a key, but it won't register on the screen.
for example, if i type happy, i would see the popup on the keyboard for each individual letter (H A P P Y), but it would only register H P P Y, almost like the multitouch isn't working properly.
the effect is very pronounced on aftermarket keyboards (i've tried a lot, ICS, GO, swiftkey), and they are all WORSE than the stock keyboard. the simplest fix is to type slowly, but that just ruins my train of thought.
can anyone help?
Click to expand...
Click to collapse
yeah I noticed this too, it seems like the multitouch doesn't work properly. What ROM are you using? I'm on WetDream 1.2 still. I don't know why it's this way but it makes me very sad. It's very annoying. Anyone else have this?
I have this problem as well. I went on a rampage downloading a million different keyboards, but to no avail.
I have the same problem. Could it be the digitizer?
Are you guys running any CM9 ROM? If so, that's your problem. Since these ROMs are using older drivers that are not made for ICS, you are going to face these problems until Motorola....more like MotoLOLa....releases the ICS drivers later this year.
Sent from my MB860 using XDA
TheMan0790 said:
Are you guys running any CM9 ROM? If so, that's your problem. Since these ROMs are using older drivers that are not made for ICS, you are going to face these problems until Motorola....more like MotoLOLa....releases the ICS drivers later this year.
Sent from my MB860 using XDA
Click to expand...
Click to collapse
I accidentally hit the "thanks" button when I meant to hit "quote" but anyways, I'm using cm7 and this problem happens on every different rom that I have tried. I have never had so much problems with a new phone before that I'm starting to think that motorola can't even make phones that work anymore.
Yes I believe the problem is poor implementation from Motorola.
IF you use the stock keyboard (the multittouch one) this problem goes away. Just figured this out this morning.
I am using a blur based stock rom (one of nottach's) so I still have that keyboard available. I think this will be enough to keep me on stock based roms or at least roms that will have that keyboard.
Atrix_Owner said:
I accidentally hit the "thanks" button when I meant to hit "quote" but anyways, I'm using cm7 and this problem happens on every different rom that I have tried. I have never had so much problems with a new phone before that I'm starting to think that motorola can't even make phones that work anymore.
Click to expand...
Click to collapse
That is very weird. When I was using CM7, I never faced any keyboard issues. It kills me that the Atrix's worst keyboard, IMO, was when I was using stock GB. Absolutely the worst thing ever.
Sent from my MB860 using XDA
bump for more attention.
I've always had this issue on every ROM with every keyboard I've ever used including the stock Motorola one. I just chalked it up to the multitouch not working since it doesn't seem to work correctly for anything.
Sent from my MB860 using XDA
I've only ever had this problem with the stock ICS keyboard on a CM9/ICS Rom, the 'solution' was to disable either the keyboard's or android's spelling correction. Can't say I've know exactly what's causing it on anything else, I'm afraid.
Related
Hello guys!
Just got my Epic a few weeks ago to replace the old Moment.
Unfortunately.. I like everything about the phone except the main reason I got it over the Evo.. the keyboard. It seems to drop keys a lot, and I know for a fact I pressed them.
For example I can open up a text and type "lalalalalalalalalalalala" and it will drop a l or a or two. It's extremely annoying, the main reason I opted for the keyboard was for good accuracy when replying to emails for work..
As anyone else experienced this issue? Is this a software glitch or is hardware related? If this is a hardware problem.. I will be trading in for the Evo since I'm still within my 30 days.... not to mention the much better support Evo has for updates.. oh and my Network Based Location doesn't work.. wth really? So no location based app can find me with the real gps off. Why couldn't it of been HTC Epic 4g..
Anyways any input on the hardware keyboard would be greatly appreciated.
Sadly, this is a issue with the Epic's keyboard.
All of the Epic's i've played with have this problem, and I think its a combination of hardware and software.
Typing very quickly will cause it to lag and skip a few letters. You have to slow down about 2seconds and it will be fine.
Yeah, I was in the IRC talking to some people and it came off that its a known issue, happens in recovery to (although not quite as bad).. must be a hardware issue.. very disappointing considering the selling point to this phone over the evo is the keyboard mainly.
Does the keyboard have a buffer setting in the kernel somewhere? Maybe a seasoned developer would know haha, my gut tells me this is a buffer issue, you type to fast the buffer will fill up, and a letter or two will drop. Seems logical..
Is it possible that it doesnt deal with "multi touch" well. I know thats a soft keyboard term but typing to fast on the hard keyboard could surface issues if you have not fully depressed the previous key when typing fast???
Just a thought
mikeschevelle said:
Is it possible that it doesnt deal with "multi touch" well. I know thats a soft keyboard term but typing to fast on the hard keyboard could surface issues if you have not fully depressed the previous key when typing fast???
Just a thought
Click to expand...
Click to collapse
IF I hit the A and S key at the same time it properly puts in "as"..when I slide "asdfghjkl" it misses a few characters..its not too big of an issue for me as I don't type that fast but there is definitely something :/
Out of curiosity I also tested the same thing on an Samsung Intercept..and Intercept is not effected..
Seems like my keyboard has gotten worse over time. I can't type a word without missing a letter. Really annoying.
I have the same problem with mine. I figured it's a hardware issue and not really so much an issue with lag. I can hit a key and it just won't show up period so that's not lag.
I'm glad I don't type that fast.
It does it to me whether typing fast or not. Every time I send a text I allot myself time for corrections because I know every time it misses 1-2 letters. It's pretty annoying. Not only that but i'm constantly getting unsent txt errors with this phone...never had that problem before.
Ever since ditching Swype for Ultra keyboard I haven't had this problem. I have it enabled so that its auto correct system works for the physical keyboard as well.
I've also had this problem. Very annoying especially being a fast typer. I feel like it is mostly a software issue too. It would be nice to have one of the great developers here take a look into it. This is my biggest problem with the epic.
Yeah it is particularly sad, especially considering that phones like the G1, Motorolas Devour & Cliq (*Puke, my old phone*) as well as other mid-range phones could type flawlessly. Yet one of the best phones in the world IMHO and you can't even type as fast as you'd like.
I'd also like to start a bounty for this soon, I'd be glad to donate to any developer that tracked down the issue and abolished it. (Unless its a hardware issue, in which case were just screwed.)
I am starting to get it as well. Seems to be a known issue but very annoying. If it gets any worse I am just going to get a single piece phone case and say goodbye to the keyboard forever. Sucks to say it but there is no point in using a keyboard that is inaccurate to the point that I need to go back and correct things when I know I typed it correctly the first time
Could it have anything to do with the fact that our keyboards can handle multiple key presses at once? No other phone I have ever had could handle pressing multiple keys at the same time. It might just be an issue of not fully letting go of the previous key when the next key is hit. Or there might be a small delay after a keypress where the phone is waiting to see if another key is going to be pressed in combination to alter the consequences of said key press.
Yeah I noticed I need to slow down. I come from the touch pro 2s sick keyboard.
Sent from my SPH-D700 using XDA App
Gotta say I was having the same problem... then someone here said to try ultra keyboard... and for some reason it has stopped missing the keys.. so I do believe it is more of a software problem. I am on the 24 hour trial and so far it works.
Sent from my SPH-D700 using XDA App
I personally believe this is a software buffer issue with this particular keyboard.
Every physical keyboard needs a buffer, even on your PC. I think if we could increase the buffer on our Epic's keyboard driver which is built into the kernel we could alleviate this problem.
If a actual Dev would be willing to check it out that would be awesome! Not sure if Froyo still has this problem.
I agree with the disappointment... my Moment never missed a beat texting with the keyboard or writing an email, my Epic with all of its potential drops the ball in this department currently.
I hope it can be fixed. And no the solution is NOT to type slower..
I disabled the swype keyboard and it seems to have helped the issue. Maybe its just me? I am running the normal android on screen keyboard with swype unchecked in my settings
muyoso said:
Could it have anything to do with the fact that our keyboards can handle multiple key presses at once? No other phone I have ever had could handle pressing multiple keys at the same time. It might just be an issue of not fully letting go of the previous key when the next key is hit. Or there might be a small delay after a keypress where the phone is waiting to see if another key is going to be pressed in combination to alter the consequences of said key press.
Click to expand...
Click to collapse
no its not the problem..I did a test by pressing both "a" and "s" key at same time and it registered as "as"..if that was the problem it wouldn't have registered that
Bigjim1488 said:
I disabled the swype keyboard and it seems to have helped the issue. Maybe its just me? I am running the normal android on screen keyboard with swype unchecked in my settings
Click to expand...
Click to collapse
I just disabled swype and did the "asdfghjkl" test and it worked flawlessly...I then re-enabled swype and it still worked fine :/ (running the dj29 froyo rom)..we may need more testing into this I guess?
Bigjim1488 said:
I disabled the swype keyboard and it seems to have helped the issue. Maybe its just me? I am running the normal android on screen keyboard with swype unchecked in my settings
Click to expand...
Click to collapse
Sometimes I use swype whenever I need to type a short message. It's the best of both worlds. Sad if you need to disable one of the features just to get the keyboard to work properly.
EDIT: Look at the fail rate when typing ab for a solid minute on my KB:
Abababababababababaababababababababababababaabababababababababababababababababababbaababaababababababababababababababababababaabababababababababbabababbababbabababababbabaababaabbababaababababababababababababababababababbaabababababababaababababaababababaabababababababaabababababababababababaabababababababaababababaababababababababaabababababababababababababbabababababababababababababababababaababababb
This is with swype disabled.
In the past few days, my keyboard has been acting up. I've been using Smart Keyboard pro since the day I got my phone and LOVED it, but for the past few days, it's been acting the bollix. Basically, I could be pressing the delete button for maybe 4 or 5 times, and it would enter 2 z's and delete 3 charachters?
I thought that it might just be the keyboard, so I switched to the default one, and it did happen, but not as much. I have just installed the Gingerbread Keyboard from the market, and it seems to be working ok, but it's still annoying. Anyone else had any problems with their keyboard entering random letters?
Nhialor said:
In the past few days, my keyboard has been acting up. I've been using Smart Keyboard pro since the day I got my phone and LOVED it, but for the past few days, it's been acting the bollix. Basically, I could be pressing the delete button for maybe 4 or 5 times, and it would enter 2 z's and delete 3 charachters?
I thought that it might just be the keyboard, so I switched to the default one, and it did happen, but not as much. I have just installed the Gingerbread Keyboard from the market, and it seems to be working ok, but it's still annoying. Anyone else had any problems with their keyboard entering random letters?
Click to expand...
Click to collapse
Mine always put full stops outta nowhere its.like.its gone nuts or something..
Sent from my R800i using XDA Premium App
Nhialor said:
In the past few days, my keyboard has been acting up. I've been using Smart Keyboard pro since the day I got my phone and LOVED it, but for the past few days, it's been acting the bollix. Basically, I could be pressing the delete button for maybe 4 or 5 times, and it would enter 2 z's and delete 3 charachters?
I thought that it might just be the keyboard, so I switched to the default one, and it did happen, but not as much. I have just installed the Gingerbread Keyboard from the market, and it seems to be working ok, but it's still annoying. Anyone else had any problems with their keyboard entering random letters?
Click to expand...
Click to collapse
Try removing the factory installed screen protector... it does wonders for touch sensitivity and brightness of the screen. I highly recommend it.
Frogybloop said:
Try removing the factory installed screen protector... it does wonders for touch sensitivity and brightness of the screen. I highly recommend it.
Click to expand...
Click to collapse
already done that
I too have had this problem twice now.
The first fix was to install Gingerbread Keyboard and it seemed to fix.
Then i had the same problem again (If i pressed "p" it would also press "t" and pressing "delete" would also press "c") and fixed it by cleaning the screen with a wet wipe.
The problem for me when it happens is basically when you press the right hand side of the screen in landscape mode, it also think you are pressing the middle of the screen at the same time.
Its only happened twice so im not all that bothered.
Try cleaning the screen with wet wipe and see if it fixes.
I've been using swype...and as cool and innovative as it is...I'm always having to double our triple check my text msgs and posts...lately I've been having to correct my corrections..its a bit ridiculous so I'm trying to get into the habit if reading what I type every few words..
Sent from my R800x using XDA App
I just posted a thread about a multitouch issue on the xperia play. I think it may be causing your problems. It may not make sense what I am saying right now but if you read my thread it might make sense.
Basically when you are typing fast you will definitely have 2 touch points on the keyboard. and the Xperia Play is counting more than 2 touch points. So your third touch maybe registered as a 3rd finger.
Here is my post if you want to take a look
OK. I've just cleaned the screen with a wet wipe. I'm going to post this message and leave it if it makes any incorrect entries.
Seems to have worked. I will now try landscape orientation.
OK, so portrait seems to have worked well enough. I'm trying out the landscape input now. Seems to be working. I was kinda worried about this problem, but cleaning the screen seems to have sorted it out.
Also, I have installed swype, but I do not really like it. Its awkward. I used to love it on my WinMo 6.1 phone (Omnia) however, I do not feel that i should be restricted to what keyboard I can use because of the phone not responding to input properly.
Back to portrait, OK. Seems to have worked. Nope, its doing it again now. Dunno why?
Stress
Sent from my R800i using XDA App
I have a question.
Is this problem consistent like it happens every single time or does it come and go?
I personally use swype and I love it. I have not had this problem yet.
It's not a software problem, it is hardware.
When mine has had the problem, it does it on stock keyboard, chinese keyboard and gingerbread keyboard.
Basically, for me, when i touch the furthermost right hand side of the screen in landscape mode, it also registers as touching in the middle of the screen too.
Well it only started happening in the past few days. I'm gonna reflash back to 2.3.3 stock and see does that fix the issues. If not what's everyone's suggestions?
Sent from my R800i using XDA App
RacecarBMW said:
I just posted a thread about a multitouch issue on the xperia play. I think it may be causing your problems. It may not make sense what I am saying right now but if you read my thread it might make sense.
Basically when you are typing fast you will definitely have 2 touch points on the keyboard. and the Xperia Play is counting more than 2 touch points. So your third touch maybe registered as a 3rd finger.
Here is my post if you want to take a look
Click to expand...
Click to collapse
Tried to replicate this problem using the stock keyboard, and couldn't get the problem to happen.
So i'm not the only one who is having this problem?
dsswoosh said:
Tried to replicate this problem using the stock keyboard, and couldn't get the problem to happen.
Click to expand...
Click to collapse
Well that was just my theory to the OP. The multitouch problem does exist but I thought the problems with the OP's keyboard was related to this. Turns out its not.
I flashed CM7 and haven't experienced this problem yet, but I'm sure I will at some stage... *sigh*
Sometimes when I'm typing a message via Swiftkey X (only happened so far with Swiftkey X, just switched to Swype 3.25 yesterday), the keys in the middle of the screen are unresponsive. Especially the letter "T". I'll try typing and it wont seem to register T!!! T is a very essential key in the English language, so I need it to work. Some workarounds I've tried is setting the minimum CPU to 200 instead of 100 and it (seemed) to fix it, but it may be coincidence. Does anyone else have this problem???
It's weird because I think my unit may be a dud (only sometimes).
EDIT: I'm running Oxygen 2.2.2 on Nexus S 4G, Matr1x kernel v6.
I have a similar issue with my NS4G. Mine is unresponsive towards the bottom of the screen where it curves. It doesn't happen often, but it's somewhat bothersome when it does. I haven't found a fix for it yet.
I'm running Oxygen 2.2.2 with Netarchy 1.4.0 CFS.
elementur said:
I have a similar issue with my NS4G. Mine is unresponsive towards the bottom of the screen where it curves. It doesn't happen often, but it's somewhat bothersome when it does. I haven't found a fix for it yet.
I'm running Oxygen 2.2.2 with Netarchy 1.4.0 CFS.
Click to expand...
Click to collapse
I just got my nexus and have noticed this too in the bottom right for me, i have to hit it a few times to get a icon or something in that spot
Happens to me too. When it does that, turn the phone off and on and it should be fixed. (Temporarily)
Overstew said:
Sometimes when I'm typing a message via Swiftkey X (only happened so far with Swiftkey X, just switched to Swype 3.25 yesterday), the keys in the middle of the screen are unresponsive. Especially the letter "T". I'll try typing and it wont seem to register T!!! T is a very essential key in the English language, so I need it to work. Some workarounds I've tried is setting the minimum CPU to 200 instead of 100 and it (seemed) to fix it, but it may be coincidence. Does anyone else have this problem???
It's weird because I think my unit may be a dud (only sometimes).
EDIT: I'm running Oxygen 2.2.2 on Nexus S 4G, Matr1x kernel v6.
Click to expand...
Click to collapse
Try this Android Market Link
It worked for me!
Overstew said:
Sometimes when I'm typing a message via Swiftkey X (only happened so far with Swiftkey X, just switched to Swype 3.25 yesterday), the keys in the middle of the screen are unresponsive. Especially the letter "T". I'll try typing and it wont seem to register T!!! T is a very essential key in the English language, so I need it to work. Some workarounds I've tried is setting the minimum CPU to 200 instead of 100 and it (seemed) to fix it, but it may be coincidence. Does anyone else have this problem???
It's weird because I think my unit may be a dud (only sometimes).
EDIT: I'm running Oxygen 2.2.2 on Nexus S 4G, Matr1x kernel v6.
Click to expand...
Click to collapse
I had a similar problem but much worse - the entire center of the screen would be unresponsive after waking the phone.
Does quickly sleeping/waking the phone fix the problem temporarily?
Overstew said:
the keys in the middle of the screen are unresponsive. Especially the letter "T". I'll try typing and it wont seem to register T!!!
Click to expand...
Click to collapse
It's weird because I think my unit may be a dud (only sometimes).
Click to expand...
Click to collapse
I'm running stock nexus s and I've had the issue with multiple keyboards!
i have the same problem bt going out of messaging and coming back again fixes it
Something strange is going on with my touch screen. Earlier the p/0 key wouldn't work always recognizing it as O/9. I did the language and keyboard -> calibrate tool and that now allows the screen to recognize P instead of O but the number 0 still comes through as 9. I'm running mikshifted-g 2.0.
Any ideas? Thanks.
Are you using the Stock KB?
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
Are you using the Stock KB?
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Sorry, what does KB mean? Kernel?
ks-man said:
Sorry, what does KB mean? Kernel?
Click to expand...
Click to collapse
Key board
Sent from my PG06100 using Tapatalk
Yeah, I guess it is the stock keyboard. The only thing I did was flash Mikshifted 2.0 and the radios so I'd imagine I'm on the regular keyboard.
Is it a Fresh Flash? Did you do a FULL Wipe before Flashing? Or where you running this before, and it just started?
I did a full wipe. I've been running it for about 3 months without issues. This just started the last day or two.
So this is really weird. I restored from an old Nandroid Backup to the stock Sense.
After I was back on Sense the keyboard did't recognize the P or 0. It registered them as O/9 depending if I was on letter or numbers.
I then did the Language and Keyboard -> calibrate tool again and once again it now recognizes the P key but when I go to numbers it won't recognize 0 and just gives me 9. Based on this it seems that the calibration only recognizes letters and not numbers or symbols. I'm confident that the touchscreen is working since post calibration recognizes P but does anybody know how I can calibrate the screen when in the number mode?
This is really frustrating. Thanks.
Have you installed any apps lately? Are there any other strange issues? If there are you may want to try a FULL Wipe and Flash. Your Backup Restore may have had some corrupt data.
prboy1969 said:
Have you installed any apps lately? Are there any other strange issues? If there are you may want to try a FULL Wipe and Flash. Your Backup Restore may have had some corrupt data.
Click to expand...
Click to collapse
Yeah, I'm guessing that is what I may need to do and hope it fixes it. The only really different thing I've done is that I typically wouldn't use 4G since it isn't great in my area and a battery killer. I went a week or two using it and the phone started having some issues (freezing, slow responsiveness etc) and then I turned it off. I don't know if these issues are a coincidence of running 4G or not.
The phone hasn't given me anything but problems (I should really clarify, it is my wife's phone that I've taken over to try and help her). I was hoping by rooting and installing a new Rom it would solve many issues. It did make things better for a little bit but still has never gotten away from functioning the way we feel it should.
Well the New MikShifted G v2.1 is out. Also Supreme Sense v9.2, and newSense RC1, all very good Roms. Lots of extras, all very reliable. Just make sure you do a FULL Wipe before flashing any of these. Yes they're all Sense Roms, but then again that's all I run .
ks-man said:
Yeah, I'm guessing that is what I may need to do and hope it fixes it. The only really different thing I've done is that I typically wouldn't use 4G since it isn't great in my area and a battery killer. I went a week or two using it and the phone started having some issues (freezing, slow responsiveness etc) and then I turned it off. I don't know if these issues are a coincidence of running 4G or not.
The phone hasn't given me anything but problems (I should really clarify, it is my wife's phone that I've taken over to try and help her). I was hoping by rooting and installing a new Rom it would solve many issues. It did make things better for a little bit but still has never gotten away from functioning the way we feel it should.
Click to expand...
Click to collapse
Usually if you get a phone that's having hardware issues, rooting will NOT fix them, and only make it harder to get the phone repaired Until you unroot, its never recommended to root a phone that needs to see a repair shop. I'm holding my original shift I've owned since 3 weeks after launch and she is still solid as a rock.
Usually people root to fix software bugs/glitches that the manufacture refuses to fix. Like GPS being flawed but not broken,or to tweak the system to avoid Sense reloads.
Sent from my PG06100 using Tapatalk 2
I noticed that some patterns of typing consistently fail to properly register letters, in particular, words like "college" and "coming," particularly when there are letters nearby on the keyboard. Type as fast as you can and as accurately as you can and maybe you'll see what I mean.
I loaded Swype on my Nexus and it appears what the behavior is doing is that it is viewing the fast presses as a sort of dragging behavior. Swiftkey ameliorates this somewhat due to the way it handles typing errors, although it's too buggy for me to use. Typing fast on Swype produces almost incomprehensible results, while stock keyboard tends to omit a lot of letters.
Is anyone else getting this? Anyone know of any possible way to fix this? Is this a hardware issue? Using the multitouch app there doesn't appear to be any anomalies that I am aware of, and no, this is not the deadzone issue where turning the screen off/on temporarily fixes it (although I do get that).
I am getting increasingly frustrated with this device.
Drapetomania said:
I noticed that some patterns of typing consistently fail to properly register letters, in particular, words like "college" and "coming," particularly when there are letters nearby on the keyboard. Type as fast as you can and as accurately as you can and maybe you'll see what I mean.
I loaded Swype on my Nexus and it appears what the behavior is doing is that it is viewing the fast presses as a sort of dragging behavior. Swiftkey ameliorates this somewhat due to the way it handles typing errors, although it's too buggy for me to use. Typing fast on Swype produces almost incomprehensible results, while stock keyboard tends to omit a lot of letters.
Is anyone else getting this? Anyone know of any possible way to fix this? Is this a hardware issue? Using the multitouch app there doesn't appear to be any anomalies that I am aware of, and no, this is not the deadzone issue where turning the screen off/on temporarily fixes it (although I do get that).
I am getting increasingly frustrated with this device.
Click to expand...
Click to collapse
I think I've figured out part of my problem--the touch screen is so sensitive, it will register my touch even if my finger is close enough but isn't actually touching it! Wow! Anyone know of a fix for this?
Drapetomania said:
I think I've figured out part of my problem--the touch screen is so sensitive, it will register my touch even if my finger is close enough but isn't actually touching it! Wow! Anyone know of a fix for this?
Click to expand...
Click to collapse
I have screenshots showing the dev mode options demonstrating what is going on but the forum won't let me post links.
Just tried typing college with zero issues. Elephantitus of the thumbs?
Sent from my Nexus 7
You may want to try locking the device and then unlocking it. One unconfirmed theory is that the touchscreen calibrates capacitance when it is turned on. More than once it has helped me when the display either seems to be missing touch points or if it is is too sensitive.
Sent from my Nexus 7 using xda app-developers app
Sent from my GT-I9100G using xda app-developers app
BTW, SwiftKey received an update yesterday and it is now much, much, MUCH better. No more bugs.
b34tn1k said:
Just tried typing college with zero issues. Elephantitus of the thumbs?
Sent from my Nexus 7
Click to expand...
Click to collapse
I obviously considered that. The device seems to be too sensitive, if my thumbs are something like a millimeter away from the screen so some very very short gap it'll still read it as there being finger contact. I'm rather amazed at that level of sensitivity, but that clearly is no good for typing where your fingers may hover a very small distance over the keyboard when typing going over to different keys.
Don't just type it once. Keep typing it ("coming" gets better results for me") over and over again and you'll notice that most specifically the o gets omitted because it's reading it as a swipe down towards "m"; the stock keyboard not registering keypresses if you slide off the key.(swype does obviously which is why this issue gets even worse, and swiftkey is just pure magic and corrects for this to some extent).
When I get enough posts I'll post the screen shots. It's clear by the fact that the dev console is showing a lot of the swipe line to be dark purple, which I think means that very very little pressure is being put on it, or something (maybe one of you will understand it better than I will). Additionally some of the line geometry may seem suspect and may indicate other problems, I'm not sure.
eager27 said:
BTW, SwiftKey received an update yesterday and it is now much, much, MUCH better. No more bugs.
Click to expand...
Click to collapse
if it has corrected the bugs for stuff like facebook where I can't submit responses and the weird backspace bug I was getting then I'm definitely going back to that. It's not perfect but it does the job better than the other two keyboards I've tried due to this odd issue.
IS there a way to turn sensitivity down? I want to see if that helps. This tablet is, in theory, very very nice for the price, but due to all the odd issues...
I may end up RMAing it as I get the touchscreen connection bug anyway, but I'm waiting a few months for that because I don't want to risk getting a tablet with worse issues; this one doesn't have any left-side glass issues for example.
I was going to create the same thread.. same issue here. I KNOW for sure my typing is accurate. Unless I type slow, there are letters not getting displayed. Kind of annoying. Wish I had a bluetooth keyboard to try out.
I have similar issues.
I am using a favorite, Thumb keyboard.
Rob
Rob has sent this from his Nexus 7 using Tapatalk 2
Drapetomania said:
I noticed that some patterns of typing consistently fail to properly register letters, in particular, words like "college" and "coming," particularly when there are letters nearby on the keyboard. Type as fast as you can and as accurately as you can and maybe you'll see what I mean.
I loaded Swype on my Nexus and it appears what the behavior is doing is that it is viewing the fast presses as a sort of dragging behavior. Swiftkey ameliorates this somewhat due to the way it handles typing errors, although it's too buggy for me to use. Typing fast on Swype produces almost incomprehensible results, while stock keyboard tends to omit a lot of letters.
Is anyone else getting this? Anyone know of any possible way to fix this? Is this a hardware issue? Using the multitouch app there doesn't appear to be any anomalies that I am aware of, and no, this is not the deadzone issue where turning the screen off/on temporarily fixes it (although I do get that).
I am getting increasingly frustrated with this device.
Click to expand...
Click to collapse
Totally understand what you're talking about.
Tying in portrait mode using the standard keyboard was driving me absolutely bonkers.
I turned off typing sounds, and it seems to have made the situation slightly more bearable. Typing "college" is fine, still struggling with "coming". Space key sometimes doesn't register between words.
Yep, landed on this thread cause I was also searching if others had this problem. I'm on CM10, which I think has the same keyboard as stock?
I've been using Swype for a while on my phone, and it used to behave like this, but Swype is for swiping. The latest version (regressed version numbers back to 1.xx) fixes this, but screws up other things (which are OT for this thread, but check the Swype forums for many complaints).