After two years of use my Desire HD has developed some strange problems after I dropped it. The volume rocker does not work, the WiFi and bluetooth dont work and finally the strangest problem, that the keyboard does not come on when you want to input text for any App. The screen and touch input work without fault, scolling and selecting icons without problem. Making phone calls and internet connection seems to be OK as well.
I suspect I have damaged the motherboard or some other hardware, so before I buy a new phone I was wondering if anyone else had any of these problems and if so was it easily fixed.
Cheers
zen_hamster_lid said:
After two years of use my Desire HD has developed some strange problems after I dropped it. The volume rocker does not work, the WiFi and bluetooth dont work and finally the strangest problem, that the keyboard does not come on when you want to input text for any App. The screen and touch input work without fault, scolling and selecting icons without problem. Making phone calls and internet connection seems to be OK as well.
I suspect I have damaged the motherboard or some other hardware, so before I buy a new phone I was wondering if anyone else had any of these problems and if so was it easily fixed.
Cheers
Click to expand...
Click to collapse
i knw this may sound strange but try flashing another ROM first,worth giving a try..
I did as you advised, which fixed the keyboard problem. The other faults are still evident so I guess I have damaged some hardware or cable. At least I can now use the phone to text message.
I will have to have someone take a look at the inside of the phone. Checked a diss amble video out and it looks complicated.
Sent from my MZ604 using xda premium
Nice to hear tht wht else is broken now.
Sent from my HTC Desire HD using xda app-developers app
Related
Hi. I've had my Desire for some weeks now. But some day or two ago the text vibration stopped working. It's only the vibration when I get a text that doesn't work. When someone calls, feedback when I'm writing also work.
Anyone of you that know what it could be? I've checked settings etc.
SkFly said:
Hi. I've had my Desire for some weeks now. But some day or two ago the text vibration stopped working. It's only the vibration when I get a text that doesn't work. When someone calls, feedback when I'm writing also work.
Anyone of you that know what it could be? I've checked settings etc.
Click to expand...
Click to collapse
I had the very same problem with my first Desire on a week or two after I got it. I tried literally everything. I called HTC they had no idea what to do nor how to fix it. So I called T-Mobile (who I got the phone from) told them about it, they couldn't fix it either so I got a replacement phone.
Seemingly there is no way of fixing it. The motor is fine, but something is bugged. Perhaps one of the more astute Desire users (using custom ROMs) may be able to shed some more light on the problem, but as far as I know, it is unfixable.
Ok. I guess I need to contact the store I got it from. Thanks
Sent from my HTC Desire using XDA App
This is a known issue which means the text vibration stops working when the battery gets low and it doesn't come back after charging the phone.
Download and install sound manager from Android market, use it to turn on text message vibration and it'll all work again for you. Best of all It's all completely free.
Let us know if it works for you like it did for me.
Rik.
Sent from my HTC Desire using XDA App
Well sound manager worked. Thanks a lot
Sent from my HTC Desire using XDA App
I just love a problem like this that seems unfixable only to find a detailed and workable fix. Bravo.
I wish I would've known that before getting a replacement phone. Ah well, it didn't cost me anything.
Glad it worked for you all, can't remember where I first heard it but it worked for me
Sent from my HTC Desire using XDA App
sounds i have different problem...my vibration can not be switched off...i might try the sound manager too...
SkFly said:
Well sound manager worked. Thanks a lot
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
it worked for me too
I installed sound manager after, I observed that the vibration does not work on my phone.For the beginning all was OK,I began testing and saw that from 5 calls 3-4 are without vibration and 1 is with the vibration,though the vibration is on from phone settings and sound manager.I didn't try to factory reset the phone because I would lose everything .Any ideas would be appreciated.
I had this problem a while ago. Download 'Sound Manager' from the Market, and there's an option in it, 'Vibrate Always' or something. That did it for me anyway, hope it helps you
Sent from my HTC Desire
BUTCHER0123 said:
I installed sound manager after, I observed that the vibration does not work on my phone.For the beginning all was OK,I began testing and saw that from 5 calls 3-4 are without vibration and 1 is with the vibration,though the vibration is on from phone settings and sound manager.I didn't try to factory reset the phone because I would lose everything .Any ideas would be appreciated.
Click to expand...
Click to collapse
@BUTCHER0123
I had an intermittent problem with the vibrate function after about 6 months. I sent my phone back to HTC. Initially they replaced the motherboard which didn't fix the problem. I sent it back again (set as priority) and they replaced the vibration module. It all works fine now. It's an option to consider if you can put up with being without your phone but I think it's worth doing.
I'm pretty much having the same issue as:
CM Issue 2851: screen remains blank after call..
..except my phone is the HTC Slide (HTC Espresso), so the fix doesn't work.
Does anyone have a similar fix for this? Basically it seems as though my proximity sensor is malfunctioning.
I've tried wiping and installing CM6.1.1, CM7.0.1, & CM7.0.3. All have the same issue.
Sorry I couldn't post the link to the CM Issue because of the forum's spam protection.
Thanks for any help in advance!
I had this issue awhile back and it lead to other issues as it was a hardwware problem not a rom issue which is wwhat it SEAMS is happening to your phone as well.
cidica said:
I had this issue awhile back and it lead to other issues as it was a hardwware problem not a rom issue which is wwhat it SEAMS is happening to your phone as well.
Click to expand...
Click to collapse
But people having the same problem (from CM Issue 2851) were able to fix it with that proximity callibrator app. But the app doesn't work cuz it wasn't made for the Espresso.
Does anyone know of a proximity calibrator for the HTC Espresso (HTC Slide)?
cidica said:
I had this issue awhile back and it lead to other issues as it was a hardwware problem not a rom issue which is wwhat it SEAMS is happening to your phone as well.
Click to expand...
Click to collapse
cidica, did you end up replacing your phone because of this problem?
My sons was doing that, ended up being a faulty ribbon cable, replaced the cable and all has been fine since.
Sorry this is late been kinda busy. Yes i did end up replacing the phone cause of it. I called T-Mobile and talked to one of the reps there and we went through a quick troubleshoot (since i had been troubleshooting it myself the entire day). I even went as far as unrooting the cell and going back stock with the same issues. The rep i talked to just said ok well im sending you a new phone few days later i had my new slide.
Sent from my HTC Salsa C510e using XDA Premium App
Hi,
sometimes the touchscreen of my defy stops working (but the phone is not frozen)
and the only way to fix it is to lock/unlock the screen...
does anyone have the same problem (and can help me)?
thanks
P.S
i've had the problem both with stock rom (2.2) and with cyanogenmod rc 1.5
When this happens, do the 4 buttons below your display still give you haptic feedback (little vibration) or do they react not at all?
Also, does this only happen when there's the normal launcher/standby screen active or when there's an other app active too ?
Did you undervolt ?
Edit: Also, this seems to be a hardware problem which seems to be well known in a certain German android forum but I cannot find much about it in here. In short, the digitizer unit seems to be broken for some people and locking/unlocking helps because it disconnects and connects power for the digitizer. The people there fixed the problem by replacing the digitizer (which isn't easy at all!).
It would be nice to have someone from XDA who had this problem before too, to confirm this problem!
First of all, thank you for the answer
When I have the problem, 4 buttons stop working too.
It usually happens after a period of stand-by, i don't undervolt or have some other application running than the launcher (ADWlauncher).
I bought the phone one week ago, if it is an HW problem, i can't repair it by myself...
I'd recommend to wait and see whether xda has other suggestions for you and if not, just check the Motorola hotline and ask whether they know something and if they do change it for free.
Also, what you describe fits perfectly to what I've read elsewhere (don't know whether I'm allowed to post a link here or if it were useful at all because it is in German). So it sounds like your digitizer could really be defect.
ok, even if i hope to solve the problem by myself...
News: They've changed the touch screen, but the problem is still present...
Can it be a sw problem??
Keep sending it back, they will replace it in the end.
Sent from my MB525 using Tapatalk
the whole phone?
Yes, the whole phone. They have two year warranties, but don't put up or make do, you should have a phone that works right
Sent from my MB525 using Tapatalk
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
I wonder when it happens ,are you charging?
nameite said:
I use to get that problem on stock and some versions of CM.
Was definitely a software problem for me, havent had that problem since I'm on nightlies.
Click to expand...
Click to collapse
What nightly version are you using?
The problem happens even if i'm not charging...
Hello xda members! I have been experiencing a strange problem with my "T-Mobile G2"'s microphone and would like to share it with you in case you had any insight on it:
My phone's microphone is not working - I cannot use voice input, music recognition services, etc. all it picks up is silence. What makes it a "strange" problem? Well, the microphone will work during calls, but ONLY IF I first snap out the keyboard and then snap it back in! Sometimes the microphone will fade out and then go silent again, at which point I'll open/close the keyboard again so that the other party can hear me again.
I thought it was software at first, but then I flashed it to stock and still had the same issue. Now I'm worried it might be a problem with the ribbon cable that connects the two halves. Have any of you ever heard of a similar problem? Any suggestions as to how I might fix it?
If it is intermittent and you reflashed then my guess would be hardware like you suggested.
Most likely you mic is loose. Does it behave the same as opening and closing if you just hit it or shake it?
Sent from my ghdudsjihfr using dhhcdfhuf.
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
jervill said:
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
Click to expand...
Click to collapse
Do you superwipe?
killj0y said:
Do you superwipe?
Click to expand...
Click to collapse
Yup I did use superwipe.
Incidentally, the issue returned after 2 days of working perfectly. Doing a wipe and then installing that same ROM fresh (not a backup) did not fix it so that new most likely ROM had nothing to do with it. I'm giving up then and calling this a hardware issue, period. I guess it's a good thing that the HTC One phones are are coming out soon!
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
kozij said:
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
Click to expand...
Click to collapse
I had this same problem for two different reasons with two different phones.
The first time, which seems unlikely for you, was a problem with DSP Manager that comes with CM9 causing my phone to crash and restart.
The second is manufacturer error. The phone has a titanium case, and due to some errors in assembly, when I would plug in headphones, the system would freeze and restart. Because I still had warranty, I had it replaced and the problem disappeared.
If you have a multimeter there are ways to check for a short, but I'm not sure if you are familiar with this.
Hope this helps!
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
blutooth
Sent from my HTC Vision using xda premium
kozij said:
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
Click to expand...
Click to collapse
If you still want to try and find a solution, get some electrical tape (or another strong insulating tape) and cut off a thin strip lengthwise (about 0.8-1cm width x 3-4 cm length) and tape it to the top of the headphone plug on your headphones so that it blocks any contact with the titanium.
demkantor said:
blutooth
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I use a pair of Bluetooth headphones and a Bluetooth-enabled car radio. But alas, if you care a lot about your sound quality, then Bluetooth certainly is *not* the way to go.
But if you care that much about audio quality, you would have a dedicated device which uses all it's processing power for playback, right?