Develop Bugs

BA d-pad stop responding occasionally. help !

Hi.
I hope anyone have/had this problem. But I can't find any mention of it anywhere.
My Blueangel's D-pad stops responding from time to time.
The BA doesn't respond only to D-PAD keys for several seconds, and then it starts responding again.
I't only the D-PAD problem. BA is responsive for keyboard/stylus input.
Funny thing: When I touch the screen during the d-pad_non_response_time_period, the effect is gone instantly.
I'm using BA with WM2003 1.40.176 WWE extrom (i-mate)

robal said:
Hi.
I hope anyone have/had this problem. But I can't find any mention of it anywhere.
My Blueangel's D-pad stops responding from time to time.
The BA doesn't respond only to D-PAD keys for several seconds, and then it starts responding again.
I't only the D-PAD problem. BA is responsive for keyboard/stylus input.
Funny thing: When I touch the screen during the d-pad_non_response_time_period, the effect is gone instantly.
I'm using BA with WM2003 1.40.176 WWE extrom (i-mate)
Click to expand...
Click to collapse
I'm having this since ages, touching the screen and i have my dpad back..sounds like some hardware issue cause i had this even on WM5. I can live with it, though.

this problem is the very reason why i always get killed during intense gaming.. ive gotten used to it though. :roll:

I had the same problem. And it happens even under WM5.

Thank's for replies
Well then... it seems that it's BA hardware issue. If it's that much ROM independent.
Anyone daring to post it somewhere... hm... microsoft... htc.. ?

BA Keyboard turns off - softreset needed.

I have a problem,
after a while my BA keyboard turns off. the blue backlight isn't lit anymore, and i can't typde. After a softreset everything works fine again.
Anyone have the same problem, or better, a solution to this problem?!

I used to have this problem a LOT with my new BA device, but with the 1.40 ROM I never saw it again. Since you're on 1.40 already, then I guess I don't know how to help. But hey, are you using the i-mate ROM?

No I am using the (dutch) Qtek.nl ROM.
So an official Qtek ROM.
Upgraded from an T-mobile (also dutch) ROM.
Don't know if the problem was there too, because i updated the devices when i got it.
But since all data has been overwritten this shouldn't be a problem.

Are you using the keyboard too much and then it does this problem?
People, anyone else having this problem?

Yes,
when I use the keyboard for sms it takes a while to "shut down", when i use it for MSN (so much more) it doesn't take that long.
So it seems like it "shuts down" after a number of characters, but it hasn't done that while i was typing.
Only with an time-out, so when the backlight turned off; then i can't use it anymore.
don't know for sure in what time period this takes place, because this changes a lot!

The same exact problem used to happen, but now that I barely use MSN Messenger, its gone. I am absolutely positive that this is not from Messenger itself... There is no specific configuration I use for my keyboard. The keyboard backlight is set to turn off in 10 seconds. Maybe this is a problem when it's under heavy usage. We all know the shortcomings of the BA make a long list, and here's one of them.

Oh...forgot to mention: it used to freeze at any time with me even while typing. The keyboard backlight goes off, and whoops, gone.

Persisting problem with keyboard.

After updating to WM6 (firstly xda 0.1) then to Vanilla I noticed that when typing on a keyboard I got eg. "tu" when typing "t" or "u"; the same situation with "gj" when typing "g" or "j". I also got the problem of getting wrong symbols (eg. "**" instead of 8). I've got 2 T-Mobile UK version (HERM300) devices, one updated tens of times and the other one oneuntouched. After checking the registry I can say that both are the same as far as know keyboard registry fixes are concerned.
Is it a hardware thing or something I could fix. I searched over the forum, but others had different keyboard issues with their devices.

you could try going into the input options and toggling the predictive text to not kick in till after 4 words have been typed or just disable it. this may be the problem, its set to try right away by default and I see all kinds of wierd errors when it is set like this.
or you could try to go on a vigirous finger diet and excersise routine with the hope that your fingers shrink in size.
or you could use a hip top, the hiptop 2 has the best keyboard IMHO though the herald/kaiser is very nice as well

Unfortunately turning off all the predictive text options doesn't help. I start thinking that this is some kind of hardware issue as everything in the registry is as it is supposed to be. I just wonder how it could happen as it was working flawlessly (even under WM6) and suddently started working weirdly.

mean-machine said:
Unfortunately turning off all the predictive text options doesn't help. I start thinking that this is some kind of hardware issue as everything in the registry is as it is supposed to be. I just wonder how it could happen as it was working flawlessly (even under WM6) and suddently started working weirdly.
Click to expand...
Click to collapse
I have not come across this problem, this might not work and I doubt it will! but try this keyboard fix cab file for the 8225, you can always remove it with remove programmes if it is a no go.

boz said:
I have not come across this problem, this might not work and I doubt it will! but try this keyboard fix cab file for the 8225, you can always remove it with remove programmes if it is a no go.
Click to expand...
Click to collapse
I was experiencing the same problem and this cab file worked for me. Thanks. Just don't forget to power cycle the device once the cab is installed.

Unresponsive keys on Hermes

Does anyone else experience unresponsive Messaging, IE, ok, etc, keys?
I know there were brief threads about this a while back, and most were either not conclusive, or someone blamed the hardware.
I did a test, and flashed almost all current cooked and uncooked WM6 ROMs, and every single one of them has this issue.
Then I flashed WM5, and voila! No key problem.
Any ideas, or suggestions to further troubleshoot this?
TIA
Ali -

i have problems with unresponding keys too. I have too push very hard on the qwerty keyboard. Espesially the "U" key. No matter what ROM I use.

Sounds similar to what I'm referring to in this thread:
http://forum.xda-developers.com/showthread.php?t=319516

I can confirm that you're not alone. I have random problems with an unresponsive keyboard as well. It happens occasionally on all WM6 Roms I've used (currently on AT&T leaked rom), and without any discernable pattern. I don't THINK it is a problem with the actual keyboard hardware, but I've not tested this specific issue enough to be totally sure. Only a soft reset will bring the keyboard back, and then it may be fine for days. I haven't tried pressing hard on the keys to try to bring it back, as others have. If normal force doesn't work, then I will just reboot.
I hope this info helps.

Seems to be a common thing. I get this sometimes too. I have found it happened slightly less often with either Faria's super-clean or Black Satin. That could be coincidence thoguh.
Although a physical problem which requires the insides to be cleaned is something that could happen to any unit, there is an issues with Hermes keys failing to respond either quickly or at all in certain situations.
I'm honestly not sure if anyone's done enough testing to ascertain the exact circumstances that this can come up in, but it seems that a Soft Reset will always sort it as you'd expect - except for 'physical' problems of course.

Im also getting this problem now and then.. It just happens when im using the keypad allot, or typing faster then the ppc can put it on screen it seems.. But its almost most of the time when im using java apps and MMS and SMS. Wierd..
I got this problem even worse when i had Black Satin installed.. It will happen as soon as i start typing something..

updates?
I hate to ressurect this old thread, but was there any update to this issue that I might have missed? I am still having the dead keys issue, and I know it's not hardware as the pressing of the keys wakes up the device but doesn't do what the key is supposed to do.

I've had this Happen to Me Since Upgrading to WM6. When On WM5 It never Happened. Usually after a soft reset It's ok on WM6. I say Test out some WM5 for like a Week And if it doesnt' happen then It's the OS. Prolly Software to Hardware issues.

Keyboard random failures

Hey all,
I am running the Cingular 8525 variant of the TyTN with WM Black Satin.
Since the days of Black 1.2 I have rarely, but randomly had the keyboard randomly fail while using the device. When this failure happens, the Nav keys and Soft keys on the face of the phone still work, just the slide out keys do not. Also, the screen based "soft keyboards" and other input methods still function.
I am pretty sure this is software related because a SR is all it takes to fix the problem.
What I am wondering is:
1) Does anyone else experience this problem?
2) Does anyone know what specifically causes it?
3) Does anyone know of a way to fix it without a SR? (sometimes I am in the middle of things where resetting isn't an option until I am done my task)
Thanks for taking the time to read this, and thanks for any useful input.