I am having problems with several keys on the keyboard. It is not consistent but just enough to be annoying. I get duplicate spaces, 'I', 'O', and several other keys. Any suggestions on how to remedy?
Thanks!
Me too
I am having the same problems. It all started after I updated the new Sprint ROM. So, if somebody has any insight or knows anything about this it would be great if you would pass it on. I'm going to go into sprint tomorrow before work and see what they say. Thanks in advance.
What have you tried to do already?? What ROM are you running??
I'd start with a Hard Reset. (Press both Soft Keys and hit the reset pinhole). If that don't work, try flashing the ROM again?
Thanks for the posts. I am using DCD 3.0.1. I have already done a hard reset and re-flashed. Interestingly, when I do a reset I see the PPC Geeks splash screen leftover from prior to DCD's 3.0.1.
Perhaps I should go back to the Alltel stock rom and see if it persists. Thoughts?
I had the same problem...with the same keys. Mine also started after flashing DCD 3.0.0 ROM (though I think that was a coincidence). The problem persisted after I flashed back to the latest Sprint ROM. I just had Sprint replace it under warranty.
count me as having these problems as well.. and it's happened ever since I upgraded to a dcd rom in feb..since then i've flashed my rom 6 times I think and each time, this problem pops up at random...really annoying. and ya i've hard reset, reflashed and all that.. this one problem alone had me considering buying a blackberry cuz I email my clients a lot from my phone and when i have to hold down O or A or R to make sure the letter registers, its annoying..any clues?
My phone has done this too. I recall it happening after flashing to the beta radio and DCD's rom. It seems like it has gone away, I'm running DCD's 3.01 on Verizon and haven't noticed for a month or so.
I flashed back to the original Alltel ROM and so far it seems to be better. Keep you posted.
Flashing back to the original Alltel Rom seemed to have resolved this issue. I may try dcd's again when 3.0.3 is released but for now, the keyboard is important enough for me to lose GPS.
I found a supposed fix at http://forum.ppcgeeks.com/showthread.php?t=23875
it seems to be working for others with this problem. Post here at xda if it does happen to work for you.
Related
I have searched this and could not come up with any fixes, but here goes.
On my 8525 most of my front buttons would quite working (Send, End, OK, Start Menu, and Both Top Menu select buttons) on every Cingular 2.06 Rom. This would be a daily thing that could be fixed by a soft reset. Then I upgraded to XDA Live 2.0 everything worked great for a while when all of a sudden all of the front buttons stopped working, all of them except the dpad. I did a soft reset and even a hard reset, and every time it would still not be working. I freaked out the only thing I could think to do is to downgrade to the original Rom 1.34 that was on it when I received it so I could try to send it in for warranty. After the downgrade all the buttons have been working now.
So in my mind I am thinking this is a software issue rather than a hardware problem. But if that is the case what would cause this? Is there any kind of fix?
I really want to put WM6 back on my device, but not at the cost of my hardware buttons.
Any help or advice would be greatly appreciated.
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Never heard of this problem before. There is a fix for the 8525 keyboard in the XDA Live extras, but I'm almost certain it doesn't affect the front buttons.
I'd almost say that its a problem physically with a broken/barely connected button membrane or something similar.. and the action of you moving the phone to reset it/pressing the button is enough to connect it again.
If you're sure its working 100% now, try flashing XDA Live again and seeing if it kills it again!
Philux-X said:
Aww cmon nobody has anything to say and nobody has ever run into this? Should I just try to reupgrade with different radio and BL. Would the BL or the Radio have any remote relation to this problem?
Need your help here GuRu's.
Click to expand...
Click to collapse
Just a couple ideas. First, what 3rd party apps have you installed after upgrading and have you changed anything in the "softkey" program? Also, when you said you did a hard reset, was it a real hard reset, or just a power down? Some people at first get the two mixed up.
Also, the radio and bl wouldn't have anything to do with a problem like this.
Like TAURUSBulba said, I would think that it HAS to do with some cab/registry or executable you install that is common to all the ROMS that makes it do this. I would suggest you check out your installed applications and research what might create this problem.
The Rest was an actual "hard reset" with nothing else installed on phone except for system files (fresh system). I did not think the BL or Radio would have anything to do with it, I just wanted to be sure. I will try to re-upgrade to XDA Live 2.0 again when I can find some extra time. I will post results if anything changes or I continue to keep having this problem.
I appreciate your feedback.
Thank You
Recently my phone has been suspending the screen and not bringing it back when I press the power button. I was running 3.2.6 before, reverted to 3.2.3. Tried hard-resets, taken out the battery, tried running with just the rom and nothing else installed after flashing, still doesn't work.. I've also tried taking out my memory card and running without that.
The power button still works because it will still turn the phone on, and bring the phone out of sleep sometimes, but if it doesn't work on bringing it out of sleep it seems that I have to soft-reset or the phone just doesn't work...
Any suggestions? Also.. I this is a bell phone, they have stock roms available on their site, but am I able to get the stock bootloader back on in case I have to warranty this thing?
You've tried most things that people could suggest, however have you tried a different ROM?
I know this used to be a very common problem when the Tilt came out, but once everybody started changing ROMs, it slowly disappeared.
My suggestion in short: Try relocking the bootloader
My Two Cents:
This is actually the most evil bug ever for this phone. I got this bug on my Sprint Mogul and couldn't get rid of it. Some people say it's because Java is running and then causes the phone to hang, but I never found that to be the issue. I got a Verizon XV6800 and experienced this problem only when I was flashing from stock to dcd 3.2.6. It occurred after I unlocked the bootloader, but after I flashed to dcd it went away. It was between having the stock and dcd roms that I found that most people experienced this problem when the loaded they new bootloader.
If I had to guess, based on my knowledge of operating systems, that some process is taking up a lot of resources, mostly CPU time, and is not allowing the phone to come out of standby. I guess this because sometimes I have had this happen and the screen would come on after a LONG delay.
This is very strange...
I had flashed to the WM6.5 beta4, and had problems with it, so I then flashed to the Reloaded R4 1.4b1. I then noticed the next day when I received a call I could not hear the conversation through the ear piece.
I then made a call and I could not hear through the earpiece, but if I turned on Speaker phone, I could hear through the speaker phone. I rebooted a few times, changed volume settings, and I could sometimes hear through the earpiece. There seems to be no correlation to the activity and it working, but I know the speaker works.
I figured it was a problem with RR4 since it is beta, so I went back to 1.3.0 and problem still persisted. I then tried DCD 4.1, and the problem still exists.
Being frustrated, I updated the RADIO rom to 3.42.50 from 3.42.40. No luck. I then went back to 3.42.40 and still no luck.
I tried loading the audiopara.cab and it seemed to work for one call but then stopped the next.
I am using the latest DCD Carrier settings for VZW.
I'm pulling my hair out, and I'm wondering if anyone has a resolution for this?
It appears to be a hardware issue, and an FRU is in the mail.
exact same thing happened to me two daya after going from stock to bitserve 1.3.2 on my second xv6800. im not blaming anything or anyone. i want to add that using the speaker phone worked and using bluetooth worked but phone ear speaker wouldn't. glad i have full warranty on the phone. getting replacement tomorrow 2/4/09
Did either one of you try a hard reset and going back to the stock ROM? Is going back to the stock ROM even possible on the MR2?
Bitserve,
before I brought it into VZW, I used the Titan Relocker to go back to SPL 2.06, then I used MR2 to update.
Speaker problem still persisted...
Could it be something that came along that is only modifiable from QPST like the GPS assist IP settings? This would mean the flashes wouldn't have affected it to fix it?
My old phone goes back tomo, so let me know if you want me to try anything
MrTek said:
Bitserve,
before I brought it into VZW, I used the Titan Relocker to go back to SPL 2.06, then I used MR2 to update.
Speaker problem still persisted...
Could it be something that came along that is only modifiable from QPST like the GPS assist IP settings? This would mean the flashes wouldn't have affected it to fix it?
My old phone goes back tomo, so let me know if you want me to try anything
Click to expand...
Click to collapse
I don't know if you realize this, but flashing doesn't do a hard reset. I'd recommend doing a hard reset after flashing back to MR2 to see if the problem remains. I know nothing about verizon and their wacky ROMs. If you had a Sprint phone, I might have some ideas. Sorry.
I'm curious now...
What is different about the "reset" after flashing vs initiating a Hard Reset? I've done both, numerous times, and they all seem to leave it in a pristine state after the first load up.
I will try and force a hard reset, but I'm not sure how it differs...
i flashed it back to stock because i was going to take it back to verizon(still under warranty) checked it with the stock rom i forget version # sorry (2.09 i think) but the radio was something like 1.30 and still did NOT work, ear speaker was "muted".
ps i never did mr1 or mr2 went from new(stock) to dcd 3.2.6 then 1.3.1 reloaded then back to verizon
I am using the dcd 4.1.2 rom and seem to have a glitchy keyboard. It randomly adds double of the key i just pressed and sometimes doesn't insert the letter i press. Anybody know what could fix this (it isnt the hardware).
known issue, with no fix as far as i know. theres some kind of conflict that creates this issue. i believe 3.2.5 was the last release with a stable keyboard
I believe this is a hardware issue. I had this problem as well (on 2 different devices), but now I have a new device that works fine. Try to get a replacement.
its the dll that came with the latest build 20931.. try using build 20755.. it worked the best for me!
yutzybrian said:
I am using the dcd 4.1.2 rom and seem to have a glitchy keyboard. It randomly adds double of the key i just pressed and sometimes doesn't insert the letter i press. Anybody know what could fix this (it isnt the hardware).
Click to expand...
Click to collapse
I may be mistaken but I am pretty sure there is a cab for a supposed fix. This can't hurt so try it out...
I am assuming that you are implying that you didn't have this problem before flashing to 4.1.2, so hopefully it is a software issue and the cab fixes it.. best of luck!
Ok, I saw someone already had this problem, but your answer was that they should check control panel for drivers. Now, in my case this is not it. My keyboards on both of my computers (desktop and laptop) don't work properly. When I turn CAPS LOCK on it flashes and it types lower and upper case letters by itself. Also, sometimes it doesn't type at all when I press letters, so I have to wait certain amount of time to type again. I think it's a virus but no anti virus program detects it. So if anyone please can help me, I would appreciate that. Thanks in advance........
bored2nite said:
I may be mistaken but I am pretty sure there is a cab for a supposed fix. This can't hurt so try it out...
I am assuming that you are implying that you didn't have this problem before flashing to 4.1.2, so hopefully it is a software issue and the cab fixes it.. best of luck!
Click to expand...
Click to collapse
I never noticed a problem before but then again I only had the phone for a day before I flashed it
I tried your cab file, it still does it. I flashed my phone trying different roms (DCD 4.1.2, nueROM v2.2 build 5770-pre8, and DCD 3.3.4 which I am currently running) and had the problem in all three.
I am going to order a parts kit from ebay (housing and keyboard with tools) and see if that fixes it. I like the all black Alltel housing to my blue Verizon housing anyways.
Ok just an update.. in the last few hours I have flashed my titan about 4 times. Once with a kitchened rom using PPC Kitchen. That managed to brick my phone so I had to google for a fix. Found a stock rom and got my phone back online. I then reflashed with the newest radio (3.42.50) and dcd's 4.1.2. I will try the zip file again tomorrow to see if it works on 4.1.2 as when I tried it earlier I was running 3.3.4. I did find out however that while running the VZW stock rom that the keyboard worked fine. So its not the hardware (and I already ordered the parts off ebay ).
P.S. I also found a related thread at PPC Geeks: http://forum.ppcgeeks.com/showthread.php?p=251338#post251338
bored2nite said:
I may be mistaken but I am pretty sure there is a cab for a supposed fix. This can't hurt so try it out...
I am assuming that you are implying that you didn't have this problem before flashing to 4.1.2, so hopefully it is a software issue and the cab fixes it.. best of luck!
Click to expand...
Click to collapse
Worked perfectly on 4.1.2. Been using it for a few days now and haven't had the problem again. Thanks!!!
My touch screen will not work at all, everything else on the phone works just fine. I tried a hard reset and now I am stuck at the alignment screen. Any suggestions.. Anyone run across this error?
Thanks
reflash bro
put the stock rom back on
and then put the modded rom on
and it should be fine
Typically means something is interfering with the recognizer.
If you are using a protective case (shell) or screen protector, try removing them temporarily to see if they may be causing your problem.
I didn't have anything over the screen.. Any idea why it would do something like that?? I'm going to reflash to stock and back to modded ROM tonight and I'll let you guys know in the morning.. Thanks for your help.
Could be a "bad" flash.
If it still happens with the stock ROM flash, you may have a defective unit on your hands.
Hardware problem?
I had the exact same problem about a week ago. I tried reflashing the device, hard reset, etc. In the end, I couldn't even get past the screen calibration wizard. My conclusion was that I had some kind of harware problem -- the touch screen would respond intermittently for brief periods of time and then go unresponsive again.
My fix: I took the phone to my ATT service center who, much to my gleeful surprise, gave me a new one (warranty exchange) without any hassle. I expected to have to fight with them, but the transaction was trivial and stress-free.
I'm now deciding which WM 6.5 ROM I like the best. Many thanks to all the hard-working contributors and chefs on XDA for providing such awesome content and support!
Good Luck with your phone
i also had this problem recently. phone was working fine in the night, went to bed and woke up and was unresponsive. Tried everything. I ended up flashing back to all the stock stuff and sent it in for repairs. I got the screen and dpad replaced under warranty. I have no idea what caused it, but it happened. Definately not a software issue if you have reflashed...
my advise, flash back to stock spl and your carrier rom and send it back.
I had a similar problem and opened a thread as well. My problem in chronological order
1. Bought a TMobile MDA IV over ebay.
2. Flashed several different ROMs of WM6.1 and was just enjoying myself.
3. Installed a 6.5 ROM the calibration screen required me to go through 3 full circles.
4. Worked fine for a day, then the device was locked and watever I tried I just couldnt get to open it up
5. Did softreset, it didnt help either. I Would end up at lock screen
6. Finally got back to HTC stock ROM 6.1, and I couldnt get past the calibration screen for a month.
7. My conclusion as well, that its a hardware problem, unfortunatel where I live I dont have Tmobile and the screen from touch pro is slightly different in size to the tmobile variant.
8. Hence it was a brick!!!!
9. After a month just last week, I thought of trying to flash back to 6.5 and see if it works.
10. Went calibrating in circles for about 10 times and guess wat!!!! It starts up!!!!
Now my conclusions are as good as anyones, it cant be an hardware issue. I am trying to find a solution so I can reflash my ROM and go to a stable version and live with my phone atleast for an year.
The Mystic ROM lite version has touch response software built in, Could this be the issue.
Anyones got any idea let me know