Related
Just wondering if anyone else's Tilt is acting up like mine, the keyboard when sending texts will sometimes miss a good bit of key presses and I have to go back 3 or 4 times to register the key.
It worked fine at first so I figured it was something I did so I tried a hard reset and after about 30 minutes it started again.
yup - my keyboard has been crappy since day 1. i often miss key presses and the 'click' feedback isn't there on some presses.
never had a problem with my 8525s - had 3 of them and the keyboard was always flawless.
waiting for a store to get more stock so i can see if have a faulty keyboard.
yeah i have strange problem with my keyboard too. it only seems to be missing key presses for double-letters, like the 'pp' in 'happy' or 'll' in 'hello'. the second letter sometimes doesn't show up.
its strange because typing things like 'apapapapapapa' quickly over and over again, it doesn't seem like any of the letters are getting dropped.
rking84 said:
yeah i have strange problem with my keyboard too. it only seems to be missing key presses for double-letters, like the 'pp' in 'happy' or 'll' in 'hello'. the second letter sometimes doesn't show up.
its strange because typing things like 'apapapapapapa' quickly over and over again, it doesn't seem like any of the letters are getting dropped.
Click to expand...
Click to collapse
is this with the AT&T rom? the HTC rom? or both?
this is the at&t rom, without the bloatware installed.
With all the crap that AT&T did to their ROM, I don't know why anybody on here uses it. I had it for half an hour before I couldn't stand it anymore and switched to the HTC ROM.
same bug with german t-mobile rom... its like the device is busy.
unfortunately the same on HTC Tytn II German Rom too.
so is this a defect with the hardware or the software? i dont want to bother exchanging it if it happens on every device.
disable word complete and auto correct and see if it works a little better
did for me
dld
I experience missed key presses but rarely. I do however experience a probelm when using shift quite a bit. If I want to capitalize a letter I hit shift and then type the word, sometimes it will also capitalize the second letter. So Happy would be typed out as HAppy. It's annoying going back to fix it!!!!!!!!!!
RacerX10 said:
disable word complete and auto correct and see if it works a little better
did for me
dld
Click to expand...
Click to collapse
Disabling these solved it.
decepticon said:
Disabling these solved it.
Click to expand...
Click to collapse
didn't work for me. German HTC ROM. Only happens if double letters are typed quickly. second letter gets lost. it is definitely a bug!
I noticed that the "C" button I have to press harder to get it to work.. I'm going to see if I can have my tilt replaced ..
Just info no solution.
Using HTC shipped ROM
There are two issues outlined: Repeated letter getting missed and Shift causing capitalization of second letter as well as the first.
Issue one I cannot reproduce even with auto correct and word completion set to on. No matter how fast I get the letters in, both letters appear. The implication is that it may be a ROM issue, but also of course may be due to other apps installed. Less likely to be hardware, except in as much as some people may be pressing less firmly for the second letter???
The second issue where after pressing shift two letters instead of the first only are capitalized. I can reproduce this but only under fixed circumstances:
1.
There needs to be a clear release of the first letter before the second is pressed. So for example if you hit (shift) then an "A" with your left thumb and "L" with your right thumb the both letters will be capitalized if you are still pressing the "A" when you hit the "L". Never will it then give a third capitalized letter because clicking the second letter cancels the (shifT) key.
2.
If the first letter and the second are very close together say "D" and "E" it is possible to move from one to the other without releasing the first and again both letters will be capitalised.
So in conclusion I think this happens when either the letters are imediately adjacent to each other or if the first letter is not being released fast enough ie before the second one is pressed (easy to do if you are using two fingers to type quickly)
Mike
ya, this is an issue with the kaiser and the tilt (i've owned both). It was the samew ay with the blackjack. This is VERY annoying and i would LOVE to find a fix for it.
Thanks,
re: Mike
thanks for the test. it does seem like it would be a software problem, but i have installed both the att and the cooked rom from the kaiser upgrading forum, and they both have the double-letter problem.
i tried it right after i loaded the cooked rom, so i dont think it would be any software i loaded. and whether auto-correct/word completion on, it happens.
anyone else have any ideas?
alaiwy said:
ya, this is an issue with the kaiser and the tilt (i've owned both). It was the samew ay with the blackjack. This is VERY annoying and i would LOVE to find a fix for it.
Thanks,
Click to expand...
Click to collapse
double letter or capitalization issue?
the double letter is the only issue i have with the keyboard and it makes me crazy.
alaiwy said:
the double letter is the only issue i have with the keyboard and it makes me crazy.
Click to expand...
Click to collapse
some just posted this in howardforums:
have you tried changing this?
Start->Settings->Buttons->Up/Down Control and make the delay short.
i tried it and it seemed like it made it better? it doesn't seem to refer to the keyboard but it works i think...?
I have been running a older version of Dutty's Kaiser ROM for some time with great results, however, I have noticed that my hardware keyboard is slower than it should be. I can press a button and either get no response or two characters typed. Anyone else experience this and know what causes it?
thanks ahead of time,
Levi
Use Disable T9 cab
I also had more performance with different radios and spls
There is a recen thread on this
do you know where the recent thread is? or where the disable T9 cab is located? i did a forum search but turned up too many hits and after reading the first page of hits i gave up.
The problem has escalated!
you know I tried that disable T9/XT9 cabs and tricks, but they didn't help. I investigated further as to why my hardware keyboard doesn't respond correctly. I think that I have found that is is strictly a hardware related issue. Only a few of the buttons on my device have this problem, and their not really slow, they just don't type each every time I press them. I also found that the harder I pressed those problem buttons, the more likely it was to actually type them. I might end up trying another ROM and hard resetting the device but if not, I may try taking the device apart and cleaning the keyboard, I suppose I have just typed it to death! If all else fails unless anyone else has suggestions, time for a new phone. Anyone else have this problem with the Kaiser, and another thing. Have a kaiser?, look at the front of it and inspect the shiny button cluster. Does your button cluster move about the opening sort of loosely jiggling around? hmmm........ mine does!
Levi
this is a known issue with alot of ROMs that are made from the AT&T OEM rom.
blacksage said:
you know I tried that disable T9/XT9 cabs and tricks, but they didn't help. I investigated further as to why my hardware keyboard doesn't respond correctly. I think that I have found that is is strictly a hardware related issue. Only a few of the buttons on my device have this problem, and their not really slow, they just don't type each every time I press them. I also found that the harder I pressed those problem buttons, the more likely it was to actually type them. I might end up trying another ROM and hard resetting the device but if not, I may try taking the device apart and cleaning the keyboard, I suppose I have just typed it to death! If all else fails unless anyone else has suggestions, time for a new phone. Anyone else have this problem with the Kaiser, and another thing. Have a kaiser?, look at the front of it and inspect the shiny button cluster. Does your button cluster move about the opening sort of loosely jiggling around? hmmm........ mine does!
Levi
Click to expand...
Click to collapse
I second both observations.
On my keyboard, it's the R and H buttons that are unresponsive. As to the shiny button cluster, mine moves too. But not as much as my friend's TYTN II does.
spip72 said:
I second both observations.
On my keyboard, it's the R and H buttons that are unresponsive. As to the shiny button cluster, mine moves too. But not as much as my friend's TYTN II does.
Click to expand...
Click to collapse
You may want to check your key repeat speed and delays in settings->buttons. I had mine set to lowest delay and highest speed. I tried to double the delay, and reduce the speed to less than half. My keys seems to work a little better now (but i've just been testing for a few minutes).
jiggly buttons
my hardware buttons jiggle around a lot. they still work fine, but yes I believe they are just jiggly by poor deisgn.
Sometimes, like once a week or so, my Diamond gets pretty weird. It register the touch i make with my thumb or stylus as being further to the left than it actually is, sometimes all the way to the left of the screen and sometimes just a cm or two.
This happens even if I've just installed a new ROM, (got 2.03.413.1 official atm). It usually happens when the phone is pretty slow/warm/busy. Like when I've spoken for a long time, or when I'm browsing through many images. But then, all of a sudden and without me doing anything in particular, the phone fixes itself.. Takes from a few minutes to several hours.
Question is: Have you heard of this before? I've searched but found nothing like it. And, do you reckon it's a hardware or software error?
Still have warranty, but I hate turning in the phone and being without one for weeks if unlucky.
Thanks in advance,
Daniel
Hi
I purchased my AT&T 3G compatible Nexus One the first day it went on sale, I just updated to Froyo and I notice that sometimes my screen fails to respond. I have to power on and off my screen for the issue to go away. Some examples are when im typing and I hit and key and it chooses another one or i'm trying to scroll on the menu and even if im picking something from the top the phone highlights the menu icon at the bottom. Are this issue just with my phone? has anybody been able to fix this?, If i call HTC support and they send me and new phone will it have the same issues?
Please guys let me know... this is driving me crazy
MEGABYTEPR said:
Hi
I purchased my AT&T 3G compatible Nexus One the first day it went on sale, I just updated to Froyo and I notice that sometimes my screen fails to respond. I have to power on and off my screen for the issue to go away. Some examples are when im typing and I hit and key and it chooses another one or i'm trying to scroll on the menu and even if im picking something from the top the phone highlights the menu icon at the bottom. Are this issue just with my phone? has anybody been able to fix this?, If i call HTC support and they send me and new phone will it have the same issues?
Please guys let me know... this is driving me crazy
Click to expand...
Click to collapse
the screen on this phone blows... plain and simple... you will just have to get used to it...
do you think i should get rid of it?
Hi,
Don't get rid of the phone. You don't have to reboot, just lock the screen by pressing the power button, then unlock it. I've had it a couple of times but it goes away when I do that.
Also, be aware that it's very sensitive to any part of your hand that might be leaning over the edge of the screen, or hovering over the touch buttons. For example if my finger is hovering over the home button but not touching it, and then I touch somewhere higher up on the screen, it may respond as if I had pressed menu.
cmstlist said:
Also, be aware that it's very sensitive to any part of your hand that might be leaning over the edge of the screen, or hovering over the touch buttons. For example if my finger is hovering over the home button but not touching it, and then I touch somewhere higher up on the screen, it may respond as if I had pressed menu.
Click to expand...
Click to collapse
So...are you saying we are holding the phone the wrong way? Lol.
the nexus has this issue with the screen. its not a big deal, just lock the screen and unlock it, it fixes the problem. its some kind of mis calibration issue. yeah it sucks, but not the end of the world. only takes 2 seconds to fix it.
joshlusignan said:
So...are you saying we are holding the phone the wrong way? Lol.
Click to expand...
Click to collapse
Heehee. I guess Android isn't immune to that either. Nor is the EVO or Droid Incredible (not identical problems but they're still there). I think it's inevitable that as we try and jam more and more "magic" into a single unit, things start to crosstalk in unpredictable ways and glitches emerge.
I have to say, the touch-sensitive buttons on Milestone & N1 really throw off people who haven't used them before. If I pull up a picture or video and I'm showing it to someone, inevitably they clutch the phone with a finger on a touch button, and then I have to get them back into the app and explain what not to touch. That's one reason I'd rather have physical buttons such as on the Desire.
I have this touchscreen problem as well, and yes its a big deal for me! I spent $580.00 for this phone. This shouldnt be happening at all! I've tried all sorts of troubleshooting(deleting cache partition, updating to the latest froyo, restoring factory settings, tried without installing 3rd party softwares, etc..) before i finally came to the realization that this is a hardware issue. Ive tried narrowing down to possibly when and how it occurs, but you can't. It just happens when it happens. It's impossible to predict. When this problem occurs, watch closely to where the calibration is off. During the problem, the calibration is only off on the bottom half of the screen, more so close to the bottom right. The top part will work perfectly. You can test this out by swiping left to right or vice versa on the homescreen. This problem will also affect the Pinch-to-Zoom in Browser, and the ability to type correctly using the default keyboard or 3rd party's like Swype. I received an exchange thru HTC a couple days ago, and not only was this exact touchscreen issue prevalent in this unit, but also it suffered from the purplish screen tint. This issue seems to have existed since they first launched this phone, but for some reason there has been no fix for it. It's funny that the EVO received a software fix promptly after the issue was reported by many. Why not the N1?? Because it's hardware, that's why! Feature wise, this phone is by far my best PDA, I mean I really love this phone, but $580.00 is too much for such an issue to exist. I'm hoping that there's only a number of bad batches floating around. I would say, if i receive 4 exchanges, all with the same exact issue, i may look into a class action. I definitely wouldn't want to be stuck with this problem after my year warranty is up!
I haven't had the 'crazy screen' thing since FRF85B, I assumed they'd fixed it.
I haven't had it since upgraded to Froyo too
not hardware problem
I encounter this problem a couple of times and I tested two things: useing trackball I ran touch sens app and tested the touch sensor, it was fine, second I killed all apps using a task man and it fixed the issue. I am on froyo.
Sent by my Nexus one.
I experienced this yesterday for the first time on FRF91 (unrooted Stock build). I couldn't press the "enter" button on stock keyboard. It just kept choosing Delete instead. Lock/unlock screen via power button sorted it.
So the problem is still there in latest build of FroYo (for me anyhow!)
Anyone else?
I've had this problem ever since I got my N1. Sometimes made me want to switch back to my iPhone! Makes it a lot harder for my son (2 1/2) to use the phone too.
Seems reports are mixed to whether froyo fixes it or not. But it gives me hope. I've been using CM5.0.8, holding out for their final release but this gives me a reason to try MCR.
I have upgraded to FroYo FRF91 but still see the same issue.
Sometimes I face with the calibration's flaw for the left bottom corner of the touch screen.
What a shame I have paid 750$ here for this phone. I really love it but this flaw screwed up all the pleasure.
cpm said:
I experienced this yesterday for the first time on FRF91 (unrooted Stock build). I couldn't press the "enter" button on stock keyboard. It just kept choosing Delete instead. Lock/unlock screen via power button sorted it.
So the problem is still there in latest build of FroYo (for me anyhow!)
Anyone else?
Click to expand...
Click to collapse
i have two n1, one has this problem occasionally, the other one never. Both run same kernel, rom and apps
A quick lock and unlock fixes the problem
watercool said:
i have two n1, one has this problem occasionally, the other one never. Both run same kernel, rom and apps
A quick lock and unlock fixes the problem
Click to expand...
Click to collapse
So it is a hardware issue? Maybe we can get htc to replace our phones.
Well looks like I still have this issue with frf91.
crimsondr said:
So it is a hardware issue? Maybe we can get htc to replace our phones.
Click to expand...
Click to collapse
i think no one really knows. Would be a strange hardware issue which can be fixed by locking and unlocking.
Hi all,
I was just curious if anyone else is seeing some physical keyboard keypress/release detection issues on their Droid3s? The most common problem I'm seeing is a lack of detection of spacebar keypresses (i.e., I'll find words joined together). Sometimes it also fails to detect the release of the spacebar (or other keys), thus repeating a row of letters.
The keyboard is physically clean. This is however a "day one" phone and I've used it/the keyboard fairly extensively for the nearly two months I've owned it.
The problem seems most likely to occur when typing quickly. I'm certain I am pressing the spacebar though.
Have not modified the stock software.
Thanks
--Tod
Been having the sticking issue with my Droid3 as well. Haven't notice it skipping any keys, though. My spacebar, period, and backspace keys all like to stick every so often. Which can be rather infuriating when you've just typed a lengthy message, only to make a single typo, and have the backspace key wipe out everything you just wrote.
I've been thinking about getting a replacement, but I think I'd rather deal with a minor annoyance than get a refurbished phone.
Same thing.
https://supportforums.motorola.com/thread/55080?tstart=30
tliebeck said:
Hi all,
I was just curious if anyone else is seeing some physical keyboard keypress/release detection issues on their Droid3s? The most common problem I'm seeing is a lack of detection of spacebar keypresses (i.e., I'll find words joined together). Sometimes it also fails to detect the release of the spacebar (or other keys), thus repeating a row of letters.
The keyboard is physically clean. This is however a "day one" phone and I've used it/the keyboard fairly extensively for the nearly two months I've owned it.
The problem seems most likely to occur when typing quickly. I'm certain I am pressing the spacebar though.
Have not modified the stock software.
Thanks
--Tod
Click to expand...
Click to collapse
I just got a replacement today. My first d3, the middle of the spacebar wouldn't press in. It would usually register a keypress, but sometimes it wouldn't . It got really annoying because I always pressed in the middle. And it would seem to randomly add many spaces untill I pressed another button or not space at all.
Sent from my DROID3 using XDA App
Thanks all, just called 611 and ordered a warranty replacement. Very much hoping it's a new device rather than a refurb.
My current one has also has been experiencing the reboot issue with greater frequency lately.
I'm having the same issues but it's happening to the spacebar AND the backspace. I'll delete a mistake I made than all of a sudden the phone will delete everything like I was holding it.
what do you guys think? if it's software I'll wait for a patch. If it's hardware then I may need a new phone. but I agree with RandomEncounter, I'd rather deal with than get a referb.
Husky
Never had this issue on either one of my Droid 3's. I'm on .890, might make a difference.