Hi Everyone -
I just flashed to DCD ROM 3.2.5.
Now whenever i try to text using my QWERTY keyboard, it defaults to all CAPS. I have to turn on the caps button to have it switch to normal lower case.
This is happening with emails also as long as I am using the keyboard.
It appears that the functionality of CAPS and NOT CAPS has been turned around.
Anyone have this issue also or have a solution?
Thank u!
arifiano said:
Hi Everyone -
I just flashed to DCD ROM 3.2.5.
Now whenever i try to text using my QWERTY keyboard, it defaults to all CAPS. I have to turn on the caps button to have it switch to normal lower case.
This is happening with emails also as long as I am using the keyboard.
It appears that the functionality of CAPS and NOT CAPS has been turned around.
Anyone have this issue also or have a solution?
Thank u!
Click to expand...
Click to collapse
Reflash and let me know if it persists.
Strange - But I re-flashed and it is working normally now.
It must have been something when i flashed from DCD 3.2.0 - 3.2.5
arifiano said:
Strange - But I re-flashed and it is working normally now.
It must have been something when i flashed from DCD 3.2.0 - 3.2.5
Click to expand...
Click to collapse
Great, I was pretty sure that would work. Glad to hear.
Related
I have recently installed a number of apps like the "Kitchen" with windows 6.1, s2u2, weatherpanel ... and others. This phone is very cool now. The only issue, and perhaps someone out there has the same prob as me, is that when dialing a number the touch buttons on the screen with the numbers do not respond quickly by any means. I have to hold the button for about a second for the number to dial and for the image showing the pressed button to switch. If I do not hold for about a second the number will dial but the is no image switch to show the pressed button. This isn't really a big deal just annoying when the rest of the phone works so fast. Is there anything I can to to lower the delay? I have to add here that this was the case before I flashed the new rom. Any help would be great. Thank you!
Oh, I should add, It's a Verizon XV6800 with Windows Mobile 6.1 Pro, ROM version dcd 3.2.6, Radio Version 03.37.20. Thank you
I am experiencing the same problem, if there is a solution I would like to know as well.
Currently running dcds 3.2.6 and everything is running fast except for the dial pad
Thanks
Since 3.2.6 DCD release, there have been many newer versions. I like 3.3.4 the best, altough 4.1.2 is the newest. Check out the Titan upgrading subforum for more information on it.
I get this problem too but it doesn't last. I think there is a background process that is sucking all of the CPU clock cycles away from user input.
go to options and turn off the sounds for the dialpad
GeLopez said:
go to options and turn off the sounds for the dialpad
Click to expand...
Click to collapse
That worked great! Thank you very much
is anyone else having a problem on R2BA020 where when you try to calibrate the htc keyboard all it does is force close on you. I reinstalled the keyboard and I even put the updated one (wasn't keeping track of it and didn't know they had new versions) and the same thing still happens O_O
Mines fine...
Mind you tho' i always do a factory reset after a firmware update. Im just a*&l like that lol..
mark28 said:
is anyone else having a problem on R2BA020 where when you try to calibrate the htc keyboard all it does is force close on you. I reinstalled the keyboard and I even put the updated one (wasn't keeping track of it and didn't know they had new versions) and the same thing still happens O_O
Click to expand...
Click to collapse
Yeah...me too
though I had this problem before updating my firmware as well
mark28 said:
is anyone else having a problem on R2BA020 where when you try to calibrate the htc keyboard all it does is force close on you. I reinstalled the keyboard and I even put the updated one (wasn't keeping track of it and didn't know they had new versions) and the same thing still happens O_O
Click to expand...
Click to collapse
Mine is fine upto the point that I don't use the calibrate option.
AFAICT, the keyboard actually performs better with no calibration data. If I do calibrate it... it is more error prone in the sense that key presses are out of whack. No crashes or other bugs, just calibrate seems to un-calibrate... thats all
Has anyone else noticed the keyboard has taken a turn for the worst in 3.1? Multi touch no longer seems to work, nor does holding a key produce key repeat or shift characters. What the hell?! Can someone shed some light on this? Pretty please? It's driving me crazy.
Thumb Keyboard ftw!
Khassy said:
Thumb Keyboard ftw!
Click to expand...
Click to collapse
10char......
Yeah, I just can't get used to the split layout.
keyboard working fine for me. Multitouch and all. Still a tad laggy on XDA though. Although I should say that scrolling and general performance on XDA is great now.
jonnypedantic said:
Yeah, I just can't get used to the split layout.
Click to expand...
Click to collapse
I thought so at first, too, especially since I'm not used to tap typing at all. I swipe using Ultra Keyboard on my Evo. But after a little while, it became pretty easy. Easier, of course, in portrait, especially for small hands like mine, but I don't have much problem now in landscape, either.
i agree. Its pretty frustrating actually
I dont got any prob with my multi touch either. Verizon 3g xoom 3.1
Sent from my Xoom using XDA Premium App
I reapplied the 3.1 update, and that seems to have solved the issue, although I have to start from scratch again. Thanks for your help, everyone.
Edit: Nevermind. The problem's back.
jonnypedantic said:
I reapplied the 3.1 update, and that seems to have solved the issue, although I have to start from scratch again. Thanks for your help, everyone.
Edit: Nevermind. The problem's back.
Click to expand...
Click to collapse
Two suggestions that may or may not help:
Go into recovery and
1) Do a fix permissions.
2) wipe dalvik cache in advanced. (note: this will cause a longer that usual boot up time on the next reboot)
3.1 rooted wifi, no problems here
Latest version of thumbs keyboard has a mode to go back to the full keyboard.
Click the thumbskeyboard icon and it will switch modes
Thanks again, everyone. Third time wiping and reflashing was, apparently, a charm. Hopefully it's for real this time, otherwise my Xoom might just find itself transformed into an expensive frisbee. I still don't know what went wrong. I never did get a chance to try fixing permissions or wiping Dalvik cache. Anyway, it's appropriate that today is Friday the 13th.
i never rooted the Zoom and I have that problem with my keyboard too. Long press on the / sign and the @ don't pop up like it used to. Or any other keys showing there alternate. Or holding the Backspace button and it doesn't delete charectors all together?
dscribe said:
Two suggestions that may or may not help:
Go into recovery and
1) Do a fix permissions.
2) wipe dalvik cache in advanced. (note: this will cause a longer that usual boot up time on the next reboot)
Click to expand...
Click to collapse
How do you do this?
2 factory resets fixed the problem. Wtf
Same problem on my wifi only xoom non root. Is there a way to get this keyboard working without having to factory reset as more then half the memory is already used and I really don't want to move it to my computer.
just switched to thumb keyboard and did a long press and it worked like normal so I left it in caps lock and switched to the stock keyboard and it starting working again.
I'm really confused about this now???
Working just fine here.
Sent from my Xoom
Any getting the double letter thing also with stock keyboard?
Like typing hello coming out as hehello ?
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
Hi!
With my HTC HD2, whenever I try to, for instance, type a message, the keyboard on my HD2 barely reacts or hits the wrong key. Installing a swype-like keyboard like TouchPal may solve this but for some apps like games this may get an issue later on.
I'm running tytung's NexusHD2 v2.3-HWA, which runs fine (thanks!). Just this issue.
No idea if this also occurs in WM6.5, but not going to switch back just to check that
How can this be fixed?
Aside from that, is there any way to speed up the ROM? It's fast enough as of now but speed is always useful
Thanks!
Was am issue with my ROM, flashed another one and now it works fine!
Sent from my HD2 using xda app-developers app
Try disabling the keypress vibration or sound when typing. It helps ALOT for me.
same problem for me
i had the same issue with ROM,after flashing to another one it works great
In the future, just run a ROM from SD and see if that changes things, that way you don't lose your current ROM.
But yeah glad you fixed it
From an SD card it's even worse, lmao
Yoshi2889 said:
Hi!
With my HTC HD2, whenever I try to, for instance, type a message, the keyboard on my HD2 barely reacts or hits the wrong key. Installing a swype-like keyboard like TouchPal may solve this but for some apps like games this may get an issue later on.
I'm running tytung's NexusHD2 v2.3-HWA, which runs fine (thanks!). Just this issue.
No idea if this also occurs in WM6.5, but not going to switch back just to check that
How can this be fixed?
Aside from that, is there any way to speed up the ROM? It's fast enough as of now but speed is always useful
Thanks!
Click to expand...
Click to collapse
Most likely you won't be able to fix this(unless you replace digitizer, but it's not 100% solution!).
Sometimes, it's true very rarely, some HD2 hardware is not fully compatible with android(more often touchscreen function related!), but could be fully working on WM.
Even it seems a bit hassle, you should flash a WM and see what happens!
Thanks for your reply.
It works fine now, so I am not going to fiddle around anymore
Yoshi2889 said:
Thanks for your reply.
It works fine now, so I am not going to fiddle around anymore
Click to expand...
Click to collapse
Did you end up flashing it back to WM?
Yoshi2889 said:
Thanks for your reply.
It works fine now, so I am not going to fiddle around anymore
Click to expand...
Click to collapse
A simple push on THANKs button would be better, don't you agree?
quickbird144 said:
Did you end up flashing it back to WM?
Click to expand...
Click to collapse
No, myMIUI works better than the other ROMs. WM6.5 sucks, I'd never switch back to that
@bib*oops: Sure.