Hi eveyone,
I have a HTC desire, originally bought unbranded and unlocked. About two months ago I rooted with unrevoked (after downgrading the HBOOT as I had installed the OTA vanilla Froyo). I have been running OpenDesire and was until recently using v.4.0.34.
Everything has been working fine until yesterday, when it was in my pocket and I got caught in a rainstorm. It got damp, but not super-wet, and was still working fine at the time. Inside the back case and under the battery was dry. Several hours later I updated to 4.0.36. Immediately after update, it was fine and acting normally. In the morning when I woke up and ever since then, the phone has not been vibrating at all. I first noticed it in Swiftkey entering text and thought it must be a setting, but it doesn't vibrate on texts, phonecalls, turning on, turning into vibrate mode, anything.
I thought I might as well reflash from scratch in case something had gone wrong with 4.0.36 so I went to do a wipe, reflash the radio and the rom, and see if this fixed it.
At this point I got back to ClockworkMod recovery and couldn't use the trackpad. It doesn't scroll, it doesn't press, nothing. It also doesn't do anything when booted. Every other bit of my phone works perfectly - charger, headphones, touchscreen, volume and power buttons, the lot.
I am *assuming* these problems are related to the damp rather than anything software-related, but other than the update to 4.0.36 I haven't done anything different or installed any new software. I would also be surprised if it was due to the water, cos it really wasn't that damp.
Any help would be appreciated. I am *this* close to stripping it down and taking it to bits to clean all the contacts of any deposits or anything, but just in case that's a bit OTT, I thought I'd ask you guys on here, because, well, you know everything
Cheers,
Dan
I have this on very rare occasions. Softly hitting the phone on the back helps. If you unsure what I mean. Just drop the phone on your bed once and it'll fix. (Atleast for me it does then)
Related
Hi guys/gals.
Got a bit of a problem, and not sure whether it's the actual phone at fault, or the software...
Had the phone for about 4 months now, and have noticed this to get worse and worse... I'm pretty sure it's happened before on the stock rom, but can't remember whether it happened before I unlocked the phone to be able to install custom roms (not security/sim unlock, just a standard unlock to allow custom roms).
Anyway, this is basically how my phone's life has been: I got phone, used standard htc rom. Then, the spl unlocker came out, and I installed that about 2 weeks after it came out (waited just to check people had no probs ). Then, I installed one of the energy roms as my first rom. Installed a few other roms in between, then an updated energy rom etc. Then, I installed the official wwe 6.5 rom. Then, I went back to the energy rom. Currently, I'm using the 26th October (iirc) rom. As I said, not sure whether it happened when I had the official 6.1 rom on (spl locked), but I'm quite sure it happened while I had the official 6.5 rom on (spl unlocked). It has happened tho with all different custom rom images I've used...
Basically, what I've noticed, is that sometimes I'm replying to a text message or email, click reply, pull out keyboard, and it seems to cause the phone to power off. Pressing the power button starts it again. Sometimes, I've not been doing anything, and it's turned itself off. Sometimes, I've dropped the phone (even only a slight drop of about 1cm), and it's caused it to power off.
I've also had times where it's turned itself off, and nothing's allowed it to come back on, other than taking the battery out the back of the phone and re-adding the battery. Then, pressing the power button powers the phone on.
Is this a problem with the roms, a problem with the spl unlocker, or a problem with my phone itself? Am I best contacting htc?
Any advice welcome, as it's very annoying coming to use the phone, and finding it's turned itself off, or when I go to reply, I open the keyboard, and then have to wait for it to load up and power it on to reply!!!
Many thanks in advance
Hi.
It's very anoying for you..
I suppose you should try to (re)install the latest Hard SPL, and to install the latest Radio too. After it, make a hard reset. Next, flash with your favorite ROM And come back here to say us what happens.
See you, and good luck for these manips.
lovelldr said:
Hi guys/gals.
Basically, what I've noticed, is that sometimes I'm replying to a text message or email, click reply, pull out keyboard, and it seems to cause the phone to power off. Pressing the power button starts it again. Sometimes, I've not been doing anything, and it's turned itself off. Sometimes, I've dropped the phone (even only a slight drop of about 1cm), and it's caused it to power off.
Click to expand...
Click to collapse
I've had this same trouble. It would happen to me when I would finish typing a text message and hit the send key and slide the keyboard close at the same time. I only really noticed it when I was running the energyroms, however I can not say for sure that they are the root cause of it, as I have waited till the message was sent before closing my keyboard ever since.
Well, since I wrote this message this morning, it's happened at least twice. Both times whilst the phone has been in my pocket...
I will try installing the latest hard spl. Think the radio I have is the latest already. Will also try a different ROM just in case it is energy roms which is causing it (but am pretty sure it happened with other roms).
Thanks for those suggestions, will let you know any outcomes
try Valkyrie. ^^
Well, I went through and installed the new hardspl (altho not sure if any different to the one I had, how would I tell?!). I then installed the image from josh, which had the latest radio and rphone.dll (or whatever the file is called) matched to it. However, doesn't appear to have made any difference. Still doing it...
Does anyone else suffer much with it, and it's just a design fault? Or should I contact htc? As surely it should just turn off when in your pocket?!
No-one else? I'm just the only person. Guess I best drop htc an email then...
my att Rhodium /tilt2 does it too
Ive been dealing with this for awhile now also.... , also return my phone for new one but this one does the same thing my radio is 4.47.25.24 and i have 1.6beta rom by josh build 21882.5.073 .
Hi folks, I've lurked here for quite a while and gotten some invaluable info; so first off thanks for all of the contributions from the gurus here!
Now, I have a pretty strange issue that I haven't been able to find an answer on anywhere. I'm hoping that someone can help me sort this.
The background story:
My wife has a MyTouch 3G Slide that I bought for her back in July. Last week she managed to drop it in some water. It DID NOT get fully submerged since the water was very shallow. However, it did get a slight amount of intrusion. She pulled the battery in a relatively quick amount of time and we let it sit in a bowl of rice to dry out for a couple days.
The current deal:
When I felt the phone was sufficiently dried after a few days, I fired it up. It took a very long time to get out of the MyTouch splash screen and loaded noticeably slower than normal. Once in, the phone functioned perfectly normal. Absolutely no issues at all with any functionality once you get past the security pattern.
However, whenever you put the phone to sleep, it does some funky stuff. The screen goes black for a second and then comes back on, ready for you to swipe down and then enter the security pattern again. Then it will go black again. Then it comes back on. It just continues to do this, never stopping. Sometimes it will go to the security pattern screen too.
So I figured this may have been some hardware issue since it was acting like someone was just repeatedly pressing the power button. First I wanted to try a simple reboot though. Upon rebooting, the phone would not get past the splash screen. It just froze there.
I pulled the phone apart to see if maybe there was some corrosion on the PCB from the water intrusion. Everything looked fine, but while I was in I did a little wipe-down with some alcohol, then I put it back together. After multiple attempts, I was able to get it to boot again. But the boot process was still VERY slow. Occasionally, it would boot into safe mode as well. But when it booted normally, everything would always function great once logged into the phone. This convinced me that it wasn't a hardware problem since the phone would not cut into sleep mode or anything when logged in. It worked perfectly fine. So I figured that maybe there was some sort of corruption that occurred in the software.
So I tried a hard reset. Didn't fix it.
Then I figured that maybe I needed to do a reflash. So I rooted the phone since the water plunge voided the warranty anyways. Once rooted, I flashed TeamFenix 1.7.1 successfully.
But the phone still only fully boots intermittently, and the boot process is still slow. It also has the same problem in sleep mode which is killing the battery fast since the screen is pretty much constantly on. But once in, the flashed ROM works perfectly just like the stock ROM.
Video of the condition:
Since I'm new, I'm not allowed to put any links in my post. But if you type in the string below after the YouTube url, you'll see a quick video I posted of the condition.
watch?v=dX55URtaRHo
So it seems that there is some crazy issue only upon bootup and when the phone is put to sleep. Can anything be done to fix this? Is there a way to locate and fix corrupted software? Any and all help is appreciated!
Sorry for the self bump. Any devs out there have any suggestions? I gotta get this thing sorted.
If its happening on both stock and teamfenix, I'm pretty sure it's a hardware issue. Flashing a rom completely replaces the software, so it doesn't sound like its that.
Sent from my T-Mobile myTouch 3G Slide using XDA App
It actually seems like a problem in the power button. Did you check the contacts for the power button? Repeatedly pressing the power button will first lock it initially and dim the screen. Press again, then it gives you the chance to unlock. Press again and it goes back to sleep. Wash rinse repeat...
Yes, I understand. But if it were an issue with the power button, when you logged into the phone, it would randomly put itself to sleep. It doesn't do that, it functions perfectly normal with no errors whatsoever when you are logged into the phone. This problem is only exhibited in sleep mode which would rule out a hardware issue with the power button.
So about a week ago or so I began, out of the blue, to have power button issues. The power button would turn my incredible on when it was off. It would wake it when it was asleep/screen off. After that it became hit and miss. When the screen was on it was highly unresponsive. Sometimes it took several presses to get it to turn off, sometimes I couldn't turn it off at all. Sometimes a tap would bring up the shut-down menu as if I had long-held it. Long holding it usually didn't work either. A few times I had to do a battery pull just to shut it off. I eventually downloaded quickboot and a screen lock widget just to get that functionality back. The last thing I remember downloading before this started happening was 'reddit is fun'. I uninstalled that after the problems, but to no avail.
Now lets go over what I was set up with. I have an amoled unit. I was at the time using CM7 Final and whatever kernel was included with it. Although I have used it a lot in the past, I didn't have setCPU installed or running this time. The only root-required thing I can remember running was autostarts. No changes were made to autostarts in the weeks leading up to the problem. I have used many roms; Frankenrom, Virtuous, Ruby, ShadowRom, IncDoes AOSP, The New Guy, Warm 2.2, Redemptive, SkyRaider, Evervolv, and several of the CM Nightlies. While using Redemptive my radio completely quit working across the board. Returning it to stock and then re-rooting fixed it. As far as I can remember I had only used SkyRaider, Evervolv, and the CM Nightlies up until I was using CM7 Final.
So after the problem started happening I decided easiest thing to do would be to try and flash a nightly over it. Tried that, didn't work. That was kind of a long shot, and I decided I might need a full wipe. Did the full wipe and installed the latest nightly. The problem persisted. I think I flashed the latest SkyRaider then, still had the problem. This was starting to seem kind of serious so I did another complete return to stock. I booted into the stock rom and used it for a bit, maybe a few hours, it seemed to work. Since things seemed back to normal I flashed the latest CM Nightly again. Seemed to work for a minute, then it was back to the same old problem.
Now around this point I, for reasons I can't remember, remove my 16 GB SD card and put the stock 2 GB one back in. I have SkyRaider on that and I flash it, it works perfectly. In fact it continues to work for a day or two. All this time my old 16 GB is sitting out on my desk. I eventually decide to clean it up, deleting a bunch of stuff I didn't need on there, and throwing it back in. After putting the 16 back in the problems creep back in. Here and there, then only working half of the time, then barely working at all.
About this time I come up with the idea that maybe something on the SD card, or the card itself, is causing this problem. Seems like a long shot, but I can't think of any other reason that would fit. I do not install apps to my SD card.
So I pull the SD card out. I was at work and I didn't have my old 2GB, so I just left the slot empty. It seemed to still be messed up, but over the course of the next hour or so it began to work correctly again.
Now I'm at home and I have deleted everything from my 16GB, and reformatted it completely. I'm about to flip it back in and see how things go.
The strange thing about this whole situation was that the problem didn't seem to just start and stop. It was as if it phased in and phased out over time, but always being caused by certain things. It seems organic if you know what I mean by that.
Feel free to tell me this is a really ridiculous idea. I think it might be. Is there something critical to the android system that could possibly be stored on the SD card?
Maybe its a hardware problem that's being affected by the weather in your area, because you can run android fine without an SD card. You would be surprised how the humidity affects electronics. This is just a crazy thought to a crazy problem lol
Wow, finally there is someone else out there with this problem.
Mine didnt have this problem till i flashed MIUI latest rom....but even after somehow making it into the recovery mode...i was able to restore my previous cm7 build...
BUT....the problem persists....
So I think I am going to pull out the 8gb sd card my friend gave me from his EVO 4g.
It annoying because sometimes i cant get into even hboot with power + volume down.
I know the volume buttons work because i can change volume on phone.
I can still see the power button still being pressed down, its not stuck or anything...it works 50/50
Can you give an update OP, please?
I also have an AMOLED Incredible..and dont want/can afford another phone...
have any of you opened up your phone to see if the button was still soldered to the board?
- i did and it is, same issue.
I hope someone might actually help me out with this. I used my phone perfectly good yesterday, tonight, i put it on standby, and go to bed. Woke up in the morning, i grab my phone, turn it on from standby mode, everything's fine, but digitizer is not answering to my touch. Soft-reset, and try to put pin, but all i get is pressing 1 / 4 / 7 no matter which part of the screen i actually touch. I haven't been flashing it for months, and i had the latest simplicity rom when this happened. Thought it was an alignment problem, so i navigated with keyboard till the align screen, and tried to align. It went in loop, as soon as i pressed the last align point, it went back to the first point, without letting me exit. Tried to re-flash with a stock rom, same problem. Tried to re-flash with an energy rom, same problem. Anyone got any ideas of what the hell happened?
May be some condensation/moisture in between the outside screen and the touch screen. This happens to me all the time when its in my pocket and its hot out. Try using your finger nail, or something, to go around the edges of the screens plastic. It will let moisture escape.
Good luck.
Hello all,
BIG problem here.
A few hours I update the MildWild oxygen rom from 4.6 to 4.6.5. For a few hours everything went totally amazing. But a few minutes ago I turned on wi-fi, but he didn't connect. So I went to MySettings app, but he didn't response. Nothing worked anymore. Only screen of and on, but then I hadn't also the lockscreen. Then the screen turned off, and I couldn't get it on
Pulled the battery out, and put in back in, but my phone didn't restart. Now I plugged in the charger, even the light of charging isn't turning on.
What the hell is the problem with my Desire? He can't be broken in a second if everything worked super well a few seconds before that all?
Tried a different battery but also then he isn't doing a ****... This whole problem came just out of the blue, that's what makes it really awkward to me.
I hope you can help me, I don't want to leave my lovely Desire.
Greets Ramon.
After all sort of things trying, I thought... let's take the sd card out. And luckily he turned on, feels like heaven...
Sd card back in, phone worked also. Don't know what the problem could have been, but my Desire works again.
I hope this maybe could help some other people who had/have/ gonna have this problem!
Close thread please :good:
Hello,
This morning suddenly, the same problem happened... Turned the screen on, swiped to unlock, but during the swipe the phone hang.This time no fear, because I knew what I had to do: take out the SD card.
Too bad, this doesn't work this time. The problem is exactly the same as last time, but know even without the SD card, the phone don't boot, don't charge. Couldn't get into bootloader also. The day before yesterday I flashed Mildwild REDUX V1, but this worked good.
What could it be?
Thanks in advance!
Greets Ramon
Edit: The last time this happened, when the phone finally booted, I directly got a message called something like "android.....com stopped unexpectedly". So that was the reason the phone stopped. Now it would be the same problem I think, but I can't turn the phone on. I just called with HTC, and because I'm out of the warrenty period, I will have to pay the repair (if needed) I think it's not broken, it's probably the same problem as last time...
The phone 'works' again... But it's in a bootloop, and going to recovery results into a bootloop also so I can't access the recovery. So I flashed the recovery again using ADB, but still I get the bootloop! What should I do?