Hi, my DROID 2 has a keyboard issue, it seems that whenever I type, it'll randomly type the same letter multiple times. Thinking it was a Liberty GB issue, I used it as an excuse to jump ship to CM7. I'm running CM7, it's amazing. But, I still have the multiple entry problem. It's really bugging me, as my DROID 2 has never been better, and I don't think I can send it in for a warranty replacement due to it's cracked LCD, and I don't want to switch to my Xperia Play for messaging, because it doesn't have a hardware keyboard. I looked around, and it seems that it's a gingerbread problem, not specifically my phone, although I've not noticed the problem when using the soft keyboard, only the hard one, and only since I've started using Liberty and CM7. I was running an old version of Zombiestomped before, and I did not have that problem.
I'm running Miui and have never run into that problem. So it shouldn't be a GB problem. My guess is that it is either a CM/Liberty problem or a hardware problem (sticky keyboard).
I've been having the same problem. I used to use Fission, then I bumped up to CyanogenMod nightly #4, and last night I updated to #40. I THINKKKK I had the problem towards the end of using Fission, but I could be mistaken, that was a while ago and I can't really remember. It seems to have gotten progressively worse over the time that I've noticed it, which has led me to believe there might be something like dust in the keyboard which is causing it to fidget, or something along those lines.
Related
Anyone using CyanogenMod or Desire Rom encounter the random touch misalign problem that has flooded the google's forum http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en
helloworld1 said:
Anyone using CyanogenMod or Desire Rom encounter the random touch misalign problem that has flooded the google's forum http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en
Click to expand...
Click to collapse
happens occasionally, but now rarely (almost never) with the latest cyanogenMod (5.0.3.1) - turn off the screen and turn on fixes it.
i think it will be eradicated completely with the next offical (and cm update)
yes, it is better for me too with CyanogenMod 5.03.01, I feel it is more due to the new .32 kernel
Now that you mention it--yeah, the problem has all but disappeared ever since I flashed CM and now Modaco's Desire. I think I encountered it a grand total of once in two-three days, though admittedly I still haven't spent enough time with the Desire ROM.
I wonder whether the touch screen driver in CM is the same as the one in the official ROM>
No problems at all with Desire image and rarely using latest cyan. It was making my stock unusable.
Ha, id totally forgot about that issue, I havent experienced it at all since switching to Cyan, atleast not that I can remember
I noticed that the alignment/calibration problem has been improved. not perfect...but improved.
I've been actively trying to palm-wrap and tilt the screen at an angle that usually gave me calibration problems on stock. Nothing; touch alignment etc remains perfect. I guess it was a software and not hardware issue after all!
So the CM does not eliminate the problem. I hope google will fix the driver in the source code, or the problem will not be gone.
i have a question, does it fix the 3g dropping/switching to edge problem?
I still have it on cyanogen 5.0.3. Actually quite often and this really annoys me, I did a wipe install.
So today while in class at college, my phone was acting very funky. I noticed that touch screen response was going crazy (Even the capacitive buttons were freaking out). Pushing on the screen would type randomly, bring the notification bar down, etc. Pushing on the capacitive buttons would usually do nothing, vibrate, or do the exact opposite it is suppose to do. I can usually alleviate the issue by turning the screen off and turning it back on, but it will only be responsive for a very short time.
So, I was thinking there was something wrong with my install of the CM 6.1.1 ROM, so I flashed the Liberated Aria FR008 ROM and... it does the same. So then I load the CM 7 (18 nightly) and it seems fine with it happening every now and then, but I don't want to use CM7 (Albeit great, it's sluggish and isn't up to what I want to use as my daily driver).
I've treated my Aria with care ever since I got it after my transfer from Alltel. I'm usually able to fix my own problems, but this one has me stumped. Any ideas as to why it's freaking out?
CM7 is now up to nightly 39 and there was a big improvement in speed/performance from 34 and later.
I have 34 loaded right now (Just found it in my Dropbox folder); however, the touch screen is still very sensitive.
I've been having very similar problems with my Aria recently; unresponsive, misreads where my finger is, Swype goes nuts, but a quick lock/unlock will correct it for a little while. I thought it was just that my cracked screen was finally giving up. Now I'm downloading CM7 build 39 to see if it's something else.
EDIT: The CM7 build didn't help my problem. I'm upgrading to an Inpsire 4G tomorrow, but I might try a few more things first or while I'm rooting it.
So I found my backup of the stock ROM and flashed it back on there. Still getting the same issue.
I upgraded the stock ROM to the "latest" AT&T version and I'm taking it into AT&T tomorrow.
perhaps its an isolated defect on your phone. hopefully your hardware is still under warranty, but alas we already flashed. maybe you can get a technician to look at it.
Took it into the store and the guy said it's "shot". I'll be able to replace it under warranty.
I should be fine. I'm still confused about how the touch screen became unresponsive, and like I said... I'm usually able to figure this stuff out (Going to college for computer engineering).
OK, so far I have resisted the urge to root my Xoom because I don't have an extra SD Card, and am not really feeling any slowness on the system to want to overclock.
But then it occurred to me...
Does anyone have the latest Tiamat kernel installed and have the Motorola Bluetooth keyboard? If so, do you still have the stuck/repeating key problem, or is it fixed? To be able to actually use the keyboard again (I pretty much don't since getting a stuck repeat eliminates any speed advantage from touch typing) would be worth rooting my Xoom.
Please let me know one way or the other!
FWIW, I've been building my own kernels from upstream (i.e, with all the latest new stuff from Linus/NVidia/Google/Motorola) and I haven't seen the repeating key problem with my Apple Aluminum keyboard, so maybe there is something to that.
Can now confirm that after rooting and flashing Tiamat 1.4.0 that my Bluetooth problem with my keyboard is history. Feel free to spread the word
im running tiamat 1.4.1 and i havent seen the issue come back since.
kcrudup said:
FWIW, I've been building my own kernels from upstream (i.e, with all the latest new stuff from Linus/NVidia/Google/Motorola) and I haven't seen the repeating key problem with my Apple Aluminum keyboard, so maybe there is something to that.
Click to expand...
Click to collapse
I've found that the bluetooth problem only creeps up if the Xoom hasn't been rebooted for a while... in like four or five days. I have no idea what this means. Since I got in the habit of shutting it off from time to time, it's been much less of a problem (though it still occurs).
Perhaps, but my X only gets rebooted if I have a new kernel to load, so maybe there is something to the new kernels (but admittedly, I've only seen the issue once).
I have been hoping that this would be corrected once the OTA dropped, but that is not the case. Also, I have come across people having this issue with the Asus Transformer, however, it seems that they had a bad piece of hardware. I doubt that is the case with my Epic, as the error only occurs on Gingerbread roms (including CM7).
On the left side of my screen, in either portrait or landscape orientation, that will be unresponsive for what seems to be a random period of time, or until I turn the screen off and on again. It is in the left-center of the screen, all the way to the S key on a soft keyboard, down to Z, and up past the text entry field.
Has anyone else experienced this, or have any recommendations on correcting this?
I have experience that exact same issue on both ACS ICS Rom and ERA RC1 rom. I'm currently on ERA rom and switch backed to the Android keyboard because it seems like the Swype keyboard was giving me more issues. Hopefully someone looks into this because I really like the swype keyboard better.
I have experienced this on Froyo roms as well. Mine has always been down the center of my screen. That really sucks since most notifications are in the center. When I upgraded to Gingerbread this got much worse! I filed an insurance claim with best buy yesterday for some physical damage on the phone, so i am hoping my new epic doesn't have this issue.
oh and on GB, my phone does this on stock without root. it is maddening i tell ya lol.
So was it deemed a hardware problem?
I haven't had this problem and i've been running Cyanogen on it for a while, my girlfriend is running stock and hasn't mentioned anything like that to me.Revert to stock and do an OTA to the stock gingerbread build and see if it still happens.
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.