Related
some keys i have to press super hard, other keys i tap and it types the key like 3 times
like when i press a
it types
aaa
and im like wha?
i am still under warranty, should i just put original stock rom back on and ask them to repair it or try and get it switched out for a vogue 0.o
I have a similar problem on my device. Is this a known problem?
Ditto here, the Function key has to be pressed hard, and some keys in the first row are acting up as well, but primarily the Q key.
I'm not sure that this has been officially acknowledged by HTC or any providers but it seems to be a widespread issue for end users.
While the "hard presses" for Function, Q and P seem to be a physical problem many users have reported that using the following CAB fixes the duplicate entries.
The CAB is being provided by UTStarcom and be downloaded at the below page.
http://handsets.utstar.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Direct link to the CAB.
http://handsets.utstar.com/downloads/XV6800 QWERTY Keyboard Fix 1-9-08.zip
This is deff a problem. My phone does the exact same thing as OP.
I press a and it types it three times. This is the only key that this happens on.
I didn't realize how bad the keyboard was degrading until yesterday, when my Mogul was replaced. For me, the ./0, y/1 and function key were the worst offenders. The unit was swapped because the usb port broke. The port failed because it's a really cheap design, 2 pins broke off . The rep in the repair center insinuated that it was a really common issue, she didn't even look at the port when I explained the problem. On the plus side,I got rid of the dreaded white spot and my keyboard works well again, but for how long? The keyboard, screen and usb port problems are all common complaints on this board and others. What I surmise from this is that HTC makes a pretty crappy product! When this phone is retired in a year or so, I'm hopeful that I'll be able to replace it with a non HTC/non Windows Mobile (or whatever MS calls it next). Every time I use my phone, I wonder if it be wonderfully helpful tool this time, or a frustrating pain in the ass? Unfortunately, the later happens all too often!
the 0ne said:
I'm not sure that this has been officially acknowledged by HTC or any providers but it seems to be a widespread issue for end users.
While the "hard presses" for Function, Q and P seem to be a physical problem many users have reported that using the following CAB fixes the duplicate entries.
The CAB is being provided by UTStarcom and be downloaded at the below page.
http://handsets.utstar.com/phone_downloads.aspx?bid=89&cid=1&mid=287&carrier=Verizon Wireless
Direct link to the CAB.
http://handsets.utstar.com/downloads/XV6800 QWERTY Keyboard Fix 1-9-08.zip
Click to expand...
Click to collapse
These cabs dont necessarily fix the hardware keyboard issues. It fixes the old issues of the function button always being on in certain applications.
The issues that people are having is just wear and tear. The XV6800 has a cheap build.
hi guys,
same here, when i type "a" either doesnt do anything or it gives me a duplicate of 3 a's. and that started happening since i upgraded to dcd 3.2.0 an on.
also when i switch to landscape mode it sometimes writes an H or Y or P. don't know if it is OS related or hardware but it is a brand new phone and i never recall having this before going to dcds greatest 3.2.X.
edit: also i've been using quickmenu ever since 3.2.0 because of the x-button issue so i was thinking is any of you using quickmenu too?
fn key problem
So I guess many people have this "hard press fn key" issue. Annoys me a lot, especially with password sites where I cannot see the entry. Would this justify replacement from spring, i have full insurance?
[email protected]$ said:
These cabs dont necessarily fix the hardware keyboard issues. It fixes the old issues of the function button always being on in certain applications.
The issues that people are having is just wear and tear. The XV6800 has a cheap build.
Click to expand...
Click to collapse
I don't really think it's a hardware degradation issue. This is because there is no gradual degradation. If it were I would think just a few keys would start acting this way and then eventually a bunch of them would. With me I just all of a sudden noticed one day that all my keys were acting wonky. I think it was after a ROM flash but I can't recall any specific one that broke it (I change the ROM more often than I use my keyboard I think haha).
The CAB seems to help a little. I still have to take more care in typing than I used to but it's better than having so many repetitions of the same key.
unL33T said:
I don't really think it's a hardware degradation issue. This is because there is no gradual degradation. If it were I would think just a few keys would start acting this way and then eventually a bunch of them would. With me I just all of a sudden noticed one day that all my keys were acting wonky. I think it was after a ROM flash but I can't recall any specific one that broke it (I change the ROM more often than I use my keyboard I think haha).
The CAB seems to help a little. I still have to take more care in typing than I used to but it's better than having so many repetitions of the same key.
Click to expand...
Click to collapse
I still say it's a hardware thing. Because if it was the software / ROM you would just be able to hard reset and your keyboard would be back to the state it was before.
My keyboard has issues with the E,O,H,Function Key, Space Bar, and the L.
It's something we will have to live with or just return our phones for a new one and wait for that one to wear out.
Just like the spots on the screen, loose stylus and so on. The 6800 was a bad build for HTC.
I Did Not Typs0r That! I Did Not Typs0r That!
ya well. it is definitely hardware. spoke to 4 co-workers with same company issued phone. one of them still has the stock rom on it, lol.. anyway
all now reporting this same issue.
i mean i was able to use my keyboard 2 months ago, and now i can't at all. its like i have a fat vogue minus 64 megs of ram. i mean i really got used to just using the on screen one.
i gotta figure out how to get stock rom back on so i can bring it to verizon and demand... satisfaction! only prob is nochem said something about it bricking your phone after putting radio 3.39 on it
torankusu said:
hi guys,
same here, when i type "a" either doesnt do anything or it gives me a duplicate of 3 a's. and that started happening since i upgraded to dcd 3.2.0 an on.
also when i switch to landscape mode it sometimes writes an H or Y or P. don't know if it is OS related or hardware but it is a brand new phone and i never recall having this before going to dcds greatest 3.2.X.
edit: also i've been using quickmenu ever since 3.2.0 because of the x-button issue so i was thinking is any of you using quickmenu too?
Click to expand...
Click to collapse
Hmmm.... anyone go back to an older rom to see if this resolves it. if it does, i must throw away everything i know about electronics.
My gift to the WORLD!
keyboard fixed.
wow it was the software.
i built a rom without the htc diamond keyboard and it works fine now.
wtf? but im happy, keyboard is working normally
hummm... I have problems with the "Q" and the left softkey, I have to press them hard...
keyboard failing on Telus P4000
I got the same problem with my Telus P4000..
I think this is how I ran into this problem ...
I had radio 3.39 and dcd 3.1.2 at the time ...
I then decided to upgrade to radio 3.42.30 and another OS ROM (version I dont quite recall.)
That is when I ran into this issue with the keyboard.
So I went back to dcd 3.1.2 (kept 3.42.30 radio)
Same problem.
So i decided to revert back to stock ROM on TELUS (2.13) and radio 1.32
Still having this issue... I hope I do not have to bring in my phone to have it repaired. It will be the second time I bring it in
Flashed yesterday to DCD3.2.3 which uses the same keyboard driver as 2.1.4 (according to the changelog).
My keyboard was wonky as hell before this flash unless I installed the fix and even with the fix it would sometimes mess up. With the new ROM (and old driver) my keyboard works almost flawlessly without the fix installed.
Still everyone thinks it's hardware-related but it definitely showed up all of a sudden with a flash months ago and it disappeared just as quickly (for me anyway).
If you have keyboard issues maybe try the new ROM and see if you have a successful fix like I did.
definitely software, i should make a youtube vid to show it.
loaded up the stock rom to bring back to verizon to return saying keyboard was all quirky and i was standing there and everything was fine. im like what the hell?
what the hell brah?
ok so here is the instructions that fixed it for me:
restored stock rom
tested keyboard to see it working fine
flash it with the newer roms with radio 3.39
everything seems fine.
i can't explain it but it works.
my Problem possibly due to environment fluctuations: Heat-Cold-Humidity
jigjiggidy said:
I got the same problem with my Telus P4000..
I think this is how I ran into this problem ...
I had radio 3.39 and dcd 3.1.2 at the time ...
I then decided to upgrade to radio 3.42.30 and another OS ROM (version I dont quite recall.)
That is when I ran into this issue with the keyboard.
So I went back to dcd 3.1.2 (kept 3.42.30 radio)
Same problem.
So i decided to revert back to stock ROM on TELUS (2.13) and radio 1.32
Still having this issue... I hope I do not have to bring in my phone to have it repaired. It will be the second time I bring it in
Click to expand...
Click to collapse
Ok... after I went back to TELUS stock, i then proceeded to flash up to dcd's latest at the time: 3.2.3 with 3.42.30 radio. Keyboard issue was still there ... So.. where to go from here right ...
Well, I recalled that I began having this issue not long after flashing 3.42.30 RADIO i think it was initially. If i recall correctly, it was not immediate. I left to go camping for 4 days and my battery died .. So I left the phone off for most of those 4 days. When I got back from camping, that is where the keyboard issue began. Note: It did not get wet, but it obviously gets damp at night. My thought: phone off for extended amount of time in damp environment, somehow affected the keyboard. I don't know how, maybe some sort of rusting of sorts due to the hot/cold/humid fluctuations inside the tent (estimated environmental fluctuations>15-30 celsius with 60-90%RH). Reason I say this is the following:
I decided to pass my fingers accross the keyboard on every buttoms back and forth with a decent amount of force. Idea being that I could maybe create enough friction or force to disrupt whatever is causing the issue under my keyboard .. I did that for a bit. And my keyboard is working better. Not perfect, but I would say 90%. I barely notice it now ..
Thanks for bringing this thread up. I have beeen getting a few missed keys, and in particular, the Fn key has been flaky. Either not working or double pressing so the Fn light comes on and locks.
So, when I heard others having the same issue, a short while back I sprayed the keyboard with contact cleaner. All better now. Now the typing mistakes are all my fault, not the keyboard.
If you try this, use a plastic safe cleaner. I used Caig Pro Gold.
For some reason, after a bit of use, the ball will decide to just stop spinning. not that it gets stiff, but it just doesn't react with the interface. This is definately a hardware problem, which means I'm porbbaly (annoyingly) going to have to send it to Orange.
Is there anyway to go back to the official rom while not losing any of my modifications? Maybe by using a nand backup? I'm on modaco 3.1.
This happened to my hero. It went away again after a couple of days.
In the case that mine doesn't, I remember going past a thread that showed how to prepare the phone for being sent to repair. Any one know where that is, thanks
I get this as well. Try taking the battery out and putting it back in to see if the problem resolves itself.
I had this problem as well after playing some games that used the ball.
I think I just pressed down on it while scrolling the other ways. (The game was more or less only using 1 way on the ball.)
But it started working again after a little abuse to the other sides
Hi, I'm having a big problem with my device, I've bought the European version and didn't touch the ROM or radio for a cool 3 months, but I often update to the latest Cookie HT, and lots of different apps. Then it got a weird behavior that if I use the device and it got a little hot it would restart by itself and after the restart got stuck on the white logo screen. It would happen often when plugged and Activesynced to my computer.
I lived with this situation for the past month but now I had enough, I've updated the radio to the latest I could find, and the ROM to Energy with Cookie HT.
Now it's worse, I can't get it to stable on the Home screen, I can see it but can't play with anything, stuck...
And BTW when it get stuck the bottom of the phone is quite hot, even if I left it for quite some time.
Edit : The Sense UI isn't loading and it actually a good bug, cause the device is running smoothly even on ActiveSync. It feels like the CHT is to blame, at least the latest one to date.
Edit 2 : Sorry, I was wrong, now it got stuck during SPB backup restoring connected to ActiveSync.
Edit 3, Sorry 2 : I've let it cool, turned it on and somehow the CHT is back and working wonderfully, this is weirder then I thought.
Edit 4 : I've managed to run Android 2.1 Desire and it was running good until it got a little warm and then froze. I'm beginning to suspect this is a hardware issue.
I realy need help feaguring this one out.
I've replaced a couple of Radio versions and this device keep jamming up, it's now unusable. I need to get it relaxed and cold before I try to turn it on again.
Can it be that the ROM is responsible ? should I go back to the stock with no mod at all (it would KILL me though).
I'm frastrated and thinking of selling the phone if anyone would buy this piece of crap.
i am in the same boat mate.
mine is going back to htc tomorrow.
In the end i removed everything and took the rom/radio back to stock still the 'heat' issue exists.
It has been like this on test for nearly two weeks if i try to run the youtube app the phone switches off anything more intense and it hard resets itself.
I have learnt that if you leave it too cool down battery out etc it will switch back on and if you do nothing but make phone calls it will be ok?
Having read alot it appears this issue happens if the device goes over a certain temp. For example folks have been moaning about the phone switching off if used in a car whilst charging running sat nav.
I advise you to contact htc as i have done.
you may have already done this, but did you do a task 29 before flashing the rom (task 29 wipes the phone and gives you a clean base to start from). Also delete the application data on your mem card(important). If your phone wont boot you can enter the bootloader by removing batt and holding vol down as soon as you you put the batt back in,This will put you onto bootloader screen ( if you have hspl installed?) from here you can do task 29 and reflash your chosen rom. Oh and make sure you have required radio for the rom you choose. hope this is of some help thought id try
Just wanted to update that HTC took an effort and accepted my unwarranted device for fixing. They replaced the board and sent it back on their expense. The device now is working flawlessly !
Thanks to HTC for a GREAT customer service and support !!!
Starting today, my touchscreen just doesn't register anything. It's not cracked or damaged at all. It just stopped responding. I can still use my dpad but my phone is extremely limited at this point.
I'm currently running Myn's Warm Eclair: http://forum.xda-developers.com/showthread.php?t=691174
I really don't want to format my phone to figure out if it's a software problem but does anyone know if this is just a problem with this android build or with android on our phone in general?
thehelios said:
Starting today, my touchscreen just doesn't register anything. It's not cracked or damaged at all. It just stopped responding. I can still use my dpad but my phone is extremely limited at this point.
I'm currently running Myn's Warm Eclair: http://forum.xda-developers.com/showthread.php?t=691174
I really don't want to format my phone to figure out if it's a software problem but does anyone know if this is just a problem with this android build or with android on our phone in general?
Click to expand...
Click to collapse
It has been a problem for me with some builds. I suggest you to make a backup with some app like Titanium Backup and reinstall Android. Try with different kernels if you still have the problem. Don't worry for the moment!
I have had this problem a few times. I still can't quite figure out exactly what makes it happen but it seems to be something to do with sleep. My solution is to restart and go into NAND then do a backup apps and then quit. something gets woken up in the screen and it starts to work again. No idea why, it just does. Good luck.
So I guess my touchscreen is just dead. I reinstalled android, reflashed my phone for the froyo rom, and I even flashed a windows rom onto my phone but nothing. I even opened my phone to see if it was connected properly to the mobo but all seems right.
On the windows rom, when it does the screen calibration, I can mash the crap out of my screen and I guess it picks up some sort of signal every now and then because the crosshair moved.
If anyone knows anything about this, please reply. I don't really want this to be the end of my vogue. It's been a good 3 years so far!
http://cgi.ebay.com/Touch-Screen-Di...749473?pt=PDA_Accessories&hash=item439b537fa1
You may just need a new Digitizer.
Can get them pretty cheap on e-bay - just have to wait since coming international mail.
I am having similar problems. Usually when the phone goes to sleep and I wake it up the touch screen is unresponsive. Only way to get touch to respond is to reboot.
I have tried it on my vogue on both the fresh froyo and experimental fat free froyo using both the 10-9 and 9-29 kernel on nand. I have also used nbh editor to change the panel types (vogue uses auto detect so I changed it to Polaris) and still the same problem. I thought perhaps there was a problem with a program but I have no programs installed right now and the problem still persists.
Does anyone have any suggestions? My phone was working fine up to a few weeks ago and I would hate to be forced to use windows again. I have reinstalled windows and it works fine there so I don't think it is hardware related. It seems something happens when it goes to sleep.
Well there might be a driver issue. Try going back to the stock rom for your device and see if the touchscreen works, if it doesn't work, then it's probably broken. Try opening the vogue and disconnecting and reconnecting and then turning your device back on and test it again. if it still doesn't work, then yea you will have to get a new digitizer.
You can also try using other releases/roms with different kernels.
good luck!! and may your vogue live on!!
Thanks, I've installed a windows rom and the touchscreen has no issue there so it leads me to believe it is not the digitizer, especially because it seems to break when it goes to sleep.
I will try even older kernels and perhaps a donut build to see if the problem still exists.
Try to figure out when things broke for you by trying the kernels that have been released over the past month. Maybe we can isolate the change that broke things for you. Maybe not, but it's worth a try.
n2rjt said:
Try to figure out when things broke for you by trying the kernels that have been released over the past month. Maybe we can isolate the change that broke things for you. Maybe not, but it's worth a try.
Click to expand...
Click to collapse
Hi! I had this problem, that was the reason why I put back WM. I experienced it using .32. I think it was from 1-Oct-2010 approximately when it started to fail.
IT'S A CONSPIRACY!!!! Last week my screen broke as well. I was running "not so super froyo" and it would work for a second then just be completely unresponsive... needless to say I now have a droid x *fap**fap*
Installed IceCreamTosti HD2 ROM 0.9 worked well for a day or two then all of a sudden my screen would stop working when it went to sleep. I researched and found that there is an undervoltage script that could be causing this problem. So i deleted the script. Then it started happening again. Task29'ed, installed HyperDroid Gingerbread Xtreme to see if that would fix my problem, nope still happening. It works when it wants but the funny thing that if I get it to work, I can use it until I have to go back to the previous screen, then I would have to hit the power button to put it to sleep, unlock it for the screen to become responsive. I know it sound like a Digitizer problem but I was wondering if anyone has any other suggestions before I buy it.
Thanks!
read here http://forum.xda-developers.com/showthread.php?t=993787
I've already read that. Thanks
Im just seeing if it could be a Kernel problem or something of that sort.
I've had this problem on one of the ROMs i used, not sure which one since i didn't stay on it for to long.
After i flashed a different ROM it fixed it. This might seem like a lot of work but why not reinstall MAGLDR,
CWM & a new ROM. Maybe try RAFDROID HD. Yes i know its a really old ROM but its a goodie and this
would be for test purposes anyway. You can always switch back.
I read the mentioned thread before too and im sure it does sound like it happens but since it happened so
soon after you installed a new ROM it makes me think its the ROM, eventhough you tried to reinstall a
different one. Maybe you can make a backup of your SD card and repartition both your phone and SD.
PC10DaTruth said:
Installed IceCreamTosti HD2 ROM 0.9 worked well for a day or two then all of a sudden my screen would stop working when it went to sleep. I researched and found that there is an undervoltage script that could be causing this problem. So i deleted the script. Then it started happening again. Task29'ed, installed HyperDroid Gingerbread Xtreme to see if that would fix my problem, nope still happening. It works when it wants but the funny thing that if I get it to work, I can use it until I have to go back to the previous screen, then I would have to hit the power button to put it to sleep, unlock it for the screen to become responsive. I know it sound like a Digitizer problem but I was wondering if anyone has any other suggestions before I buy it.
Thanks!
Click to expand...
Click to collapse
After reading the other guys thread about the end key it does seem like a bad digitizer . i read other threads explaining your exact same issue . the only way to figure out if its ROM related is to flash the stock winmo 6.5 ROM . yes , i said it , winmo but thats the last resort before deeming something hardware related . if you tried the end key option , pressing really hard on the key , then i guess i would change tto winmo and try to see if it still happens then
I do have to admit it could just be coincidence and the digitizer went up but considering this happened
only a few short days after he installed a new ROM makes me feel that there is a possibility its the ROM,
or maybe even the partition he changed (if it applies) when flashing that ROM over. I still suggest to start
over from MAGLDR on, including repartitioning your phone to the proper needs of the new ROM to see
if it helps before doing something drastic like reverting back to winmo.
Thanks for the help everyone, opened the phone up. Was hard as hell! But I cleaned the dust on the contacts under the end button, still no luck. I bought a new phone. Going to get a digitizer down the road and fix this one, If anyone want to buy it just let me know.
You will get a lot more people to see your interested in selling the phone if you post it in the xda marketplace found here.
Just open a new thread there and post how much you would want for the phone. I'm sure people would be interested
especially when you can get a new digitizer off ebay for so cheap.
change an other rom,if the problem still exist,i am sorry to tell u that u should send it to fix the touch screen..