Database Develop

slow keyboard

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.

Anyone try cleaning the keyboard?

From searching this forum, I can tell that others are having the same issue I am having. It started out with just a couple keys and now about 50% of my keys require me to push really hard for them to type. It is not a lag issue as covered by another thread. It just feels like the there may be dirt or something under the keys that makes it harder to type. This issue also is not ROM related as I have flashed my device with several ROMS with the same result.
Has anyone had any luck taking apart the keyboard and cleaning underneath the keys? If so -- maybe post some tips on what worked or not.
Thanks.

I'd vote for compressed air

I agree. You might be able to disassemble the phone and take the keyboard out and use compressed air. That would make certain that all the dirt is really out of the board...

A work mate of mine did this the other day. He took it fully apart and cleaned it out with contact cleaner. Ill ask him wether it worked or not but I think it did because I saw him using the phone today.

contact cleaner
I've never heard of contact cleaner. I'll have to try that. After looking at this video for disassembly, it doesn't look like you can get underneath the keys. How did your co-worker do it? Pop off the keys like a laptop keyboard?

I guess some older thread on how to replace Kaiser keyboard will be useful.
Found this
About screen, but went through keyboard also ..

anagarika said:
I guess some older thread on how to replace Kaiser keyboard will be useful.
Found this
About screen, but went through keyboard also ..
Click to expand...
Click to collapse
Yes, I found that as well and it was not of much use. The problem is not removing the keyboard from the phone. The problem is getting underneath the keys. You can see the keyboard front/back removed from my attached image. According to this other thread #119, #126, #127 they say it is impossible to get at the keypad underneath.
I might just take a can of compressed air and spray on top of the keys as best I can to see if it helps.

mwoelmer said:
Yes, I found that as well and it was not of much use. The problem is not removing the keyboard from the phone. The problem is getting underneath the keys. You can see the keyboard front/back removed from my attached image. According to this other thread #119, #126, #127 they say it is impossible to get at the keypad underneath.
I might just take a can of compressed air and spray on top of the keys as best I can to see if it helps.
Click to expand...
Click to collapse
Hmmm, seems that no other way but perhaps replace the keyboard ..

You cant get under the "actual" keyboard without breaking it off the housing. The keys can be pulled off from the top, but the actual buttons are sealed below.
For what little it cost, just replace the whole thing and problems are solved. Just did my son and daughters couple weeks ago.

Im foolish I forgot to ask him about it. Thinking back he may have damaged it lol. He does kind of charge into things and then realise he cant fix it.

Agree with carhigh, just replace the whole thing. Kaiser parts not that expensive nowadays. Just need time to open it up.

I have the same problem. Tried blowing compressed air from the top, but didn't have much success with the keys. I'll probably get a new keypad and replace it!

Sorry if this is a common question but where do people recommend getting kaiser parts? My N key and spacebar dont work without pressing it really hard and it's doing my head in!
Cheers.

Dommo said:
Sorry if this is a common question but where do people recommend getting kaiser parts? My N key and spacebar dont work without pressing it really hard and it's doing my head in!
Cheers.
Click to expand...
Click to collapse
Your problem will slowly get worse. More and more keys will require extra pressure. Not sure where you could buy a replacement now (the phone is kind of old). After attempting to clean the keyboard, I gave up. I am just using onscreen keyboard program that is included in TPC's ROM. I think it is called finger keyboard. After a little practice, I am actually faster typing on that than I was with sliding the keyboard.

Try this guys - worked for me in fixing my S key:
http://forum.xda-developers.com/showthread.php?t=431925

Ah. Did not realize the keyboard did not come out of the housing...

Nexus One Screen Accuracy Issues

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.

[Q] Touch screen dead spots

This may be a problem beyond the scope of android, but seeing as I'm running it, I thought I'd try here first.
I've noticed that the lower left hand side of my screen has a "dead spot" where touch is simply not registered. To illustrate, I went to screen calibration's test screen and drew a straight line along the edge of the screen. (See Attachment)
I've tried recalibrating the screen (manually and resetting to default calibration) as well as wiping data and reinstalling the system. Reinstalling the system worked once, but then the problem came back and subsequent reinstalls did not fix the issue.
I'm running Incubus26jc super froyo [RLS 12] on the 15-07-10 340X480 Froyo Kernel.
Anyone else seen anything like this? As far as I can tell, the problem is not getting any worse. Currently, it's only a hindrance when trying to use keys in that region, but I can work around it by switching to and from landscape. It's a bit of a hassle, so I'm hoping someone may be able to shed some light on the situation.
I was sure it was hardware until the system reinstall fixed it, but am now baffled as I can no longer replicate the fix.
I have not tried reinstalling the kernel but will at some point in the next day or so. I'd like to avoid switching back to WM to check if the problem persists, but may have to... we'll see. Doing everything I can to make this phone last until the Incredible month of February when I'm up for an upgrade.

dont know the issue resolution... but i have the same with my touch vogue.. and in the same 'area' apparently as well.
hard for me to hit the 'a' key on my keyboard. hehe

I'm glad to see I'm not the only one... anyone else?

Bottom right corner for me... I was able to calibrate around it but it took a few tries.
Sent from my Full Android on Vogue using XDA App

The sensitivity across my screen was inconsistent some time ago. I found that years of my abuse had taken a tole on the exterior of my phone. It eventually got worse and I bought a new housing (with a new digitizer) on ebay for a reasonable price. If it is hardware then it really isn't that hard to fix if you like taking things apart.
If you're sure that win mo accepts input from that part of the screen then nevermind my post. I would play with a painting app though and investigate the hardware further.
I may be talking a little out my a$$ with this part but.. is it possible that in calibrating your screen the os may change it's settings on how hard you have to press and such also. that may be how you got it working.
In any case, my investment in a hew housing was well worth it considering how modern my old phone has become thanks to the developers here.

gooph said:
I may be talking a little out my a$$ with this part but.. is it possible that in calibrating your screen the os may change it's settings on how hard you have to press and such also. that may be how you got it working.
Click to expand...
Click to collapse
In my case, no - when drawing a straight line down or across the screen, the line starts 'moving' away from the stylus (like the picture in the OP).

Gah... now it's shutting itself off randomly and the dead spot has grown. Not good at all.

Yeah, mine was better for a while then 'slid' again. I ended up swapping the digitizer with my other Vogue and things are back to normal.
Sent from my Full Android on Vogue using XDA App

I have another vogue, but am weary of doing anything like that. How hard was it to get done?

All you need to do is switch the front half of the housing rather than the digitizer itself- it's not hard. There's a teardown guide somewhere in the forum, Google Vogue teardown and it should be at the top.
Sent from my Full Android on Vogue using XDA App

The only thing that worries me is that my spare vogue exists because it was dropped in a muddy puddle. I'm hoping the water damage isn't too bad. Guess we'll just have to see.

it is really annoying
I have the exact same problem and I too thought it was a hardware issue till I saw this Thread. I was ignoring it till two days ago when it started really bugging me. Now, I don't even need to press any button and it automatically gets pressed around the curve and I have a google search box there, so it keeps on searching for eee or sss randomly and started draining my battery. Is there a proper fix for this?

I thought I'd chime in too... I could never seem to calibrate the touchscreen properly in either Android or Debian. Changing the screen resolution (i.e. msmfb scaling) seems to have no effect, whether it's 240x320 or 640x480. Any area within 5mm or so of the edges of the LCD will register as the edge, making "A" and several other keys on the virtual keyboard impossible to hit. Passing calibration values to the kernel didn't seem to fix anything, but it's possible I was using them the wrong way...

i have the same kind of problem on my Kaiser... i think its realted to hardware... either the housing or the digitizer...

I am experiencing the same problem on X10 mini pro. the same screen spot exactly, i have to try very hard to get z or x or shift to work. Sometimes when I try locking the screen and unlocking it back, it works.

update
so after a very long time with this problem i decided to change the digitizer and problem is gonne. visualy the broken digitizer had nothing wrong with it. The fix was fairly easy though, there is no glued parts involved into getting a new digitizer on the u20i.

Touch Screen
I just bought a brand new Cubot One and it looks more than perfect! It has just a little problem with the touch screen ( I think its the software, need ROM change). There is a dead line on the right side of the screen that touch doesn't work at all. Any solutions? Anyone faced that before? Can I fix it myself or do I have to send it back for replacement? Is there any video or guide that shows its done?
I uploaded a video on YouTube to show the problem but i cant post it yet.. (new member)
You can write "Cubot One touch screen problem" and it's the 1st one.
Thank You!

Keyboard trouble: missed spacebar keypresses and/or sticking keys?

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.