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.
Related
So i bought my incredible the second day they were released, and rooted it when unrevoked came out with their first one-click root program (so needless to say im not exactly a "new" root user). i've ran a couple roms, and lately have run stock leaks w/ added .zips for a little customization (about the past three months or so). i've been on the latest leak for like a month ish (i think its the latest one) possibly little bit longer than that. i never had a random reboot or even really any lag up, which was really amazing. then, i tried to install a custom flat black notifications bar, and i installed the update zip through recovery but it didnt do anything.
about two weeks later, i installed that new status bar power menu thing, and started to get the occasional random reboot and bog up. no really enough to really be a problem, but tonight right before bed my phone started boot looping after a random reboot (it would boot for a min or two then reboot after a lockup). so i pulled the battery and powered back on. then it loaded to the lockscreen, but every single app that should have started at startup began to repeatedly force close, so i couldnt use the phone. i tried three times but it happened every time. im nandroiding now, im sure that'll fix the problem, but any ideas what caused this? thanks!
just happened again on ruby 2.0.0, but this time all of the apps force closed AND the "click android to start" setup screen came up. I got a random reboot (which i rarely to never have), pulled battery and powered back up, it loaded to lockscreen, then it went into a soft reboot and froze at the looping bootscreen, then once i pulled battery again and powered up, i got the crashes. any idea what it is? this time, it did happen like 15 min after i had dropped my phone from about 2 feet off the ground, i guess that could be it? idk
For what it's worth, I was running 2.3 and it wouldn't mount internal or SD. This happened even after installing other ROM's. I downloaded the latest RUU, unrooted, and started from scratch.
I reformatted the SD card too. I re-rooted, and restored my SD backup. I re-downloaded the ROM I wanted, and installed it. It fixed the weird issues I was having. You may want to consider starting over from scratch.
Sent from my Incredible using XDA App
Issue: Power button won't turn screen off. Either it doesn't respond to the button push at all or it treats it as a long press and will pop up the phone options menu. Power button wakes phone just fine. Also, if I boot into recovery while experiencing this, not all power button pushes register within recovery (ouch).
It's weird because I experienced this for the first time like 2 months ago a few hours after flashing a Tiamat kernel (actual kernel may have had nothing to do with it), but after fiddling around with my phone it started working again.
Well, it started happening again on Saturday using CM 7.0.3.1 w/ GoDm0dE v5. I got it to work again by doing a factory reset, then restoring a backup. Well, it came back last night and persisted after another factory reset. It was very consistent today -- for hours it would either do nothing after pressing power or it would pop up phone options. Finally, a did a factory reset within CM7 and also within Amon-RA 2.3 and then restored a backup from yesterday and the power button functioned properly for about 1.5 hours.
Has anyone experienced anything similar?
ROM: CM 7.0.3.1
Kernel: Stock
Recovery: Amon_Ra 2.3
HW: 003
Never had that experience. Could be a number of things. It might be the Kernel/ROM mix, the Kernel itself, the ROM itself...But I would think that if it was any of these things, I would have heard about it by now from other users.
It could be something as simple as a short in your power button or the connections underneath it. Might just short out at the right times to make you think it is something you are flashing. Try shooting some compressed air in there (might help).
drgonzo712 said:
Never had that experience. Could be a number of things. It might be the Kernel/ROM mix, the Kernel itself, the ROM itself...But I would think that if it was any of these things, I would have heard about it by now from other users.
It could be something as simple as a short in your power button or the connections underneath it. Might just short out at the right times to make you think it is something you are flashing. Try shooting some compressed air in there (might help).
Click to expand...
Click to collapse
Thanks -- I actually tried the compressed air. I'm thinking it's hardware. It seems to have gotten worse in the past hour.
im having the same issue. i googled it earlier and it seems like theres alot of people have that same problem. its looking like a hardware issue. I can tell you one thing tho its pissing me off.
shdwboy said:
im having the same issue. i googled it earlier and it seems like theres alot of people have that same problem. its looking like a hardware issue. I can tell you one thing tho its pissing me off.
Click to expand...
Click to collapse
I unrooted and it actually started to do the same, but when waking the device. Brought it into Sprint and getting a replacement on Wednesday.
Had this exact same issue up until a few days ago. I took a needle and went around the power button front and back, something unjammed I guess and now it works like a charm. I've also had this with a software problem. My power button wouldn't work, even in recovery. I restored a nandroid and this fixed it. Hope this helps! Best of luck.
I had the same issue. Sprint said it wasn't the button but the board not responding to the button. Got a new phone.
Sent from my PC36100 using XDA App
I've been having issues with the phone turning off randomly and restarting, seems to do it when it gets hot. Also the phone not responding to power button. Doesn't matter which rom I flash it keeps happening. Thinking about converting back to stock to see if it helps. But I'm unsure why this started happening all the sudden any one else have similar issues??
How often is it happening? Often enough that you may be able to troubleshoot it? Such as.. turn of gps, mobile data, sync, then slowly add them back in one at a time to see what could be causing the problem.
Swyped from my Raided Evo
Also, are you under clocking or over clocking your kernel?
Swyped from my Raided Evo
My wife's Evo had that exact same problem, but hers is unrooted. We brought it into Sprint and she's getting a brand new phone tonight. They tried running diagnostics on it, but came up with nothing, so that was their last resort...
This seems to only happen to me on aosp roms and not sense.
Sent from my PC36100
[Q] My boot loops don't taste good...with or without milk...what is the reason?
My real questions are:
Has anybody experienced my experience and how did they solve the issue?
and
Can someone help me diagnose the issue?
I am seeking help on this topic also.
I have battled and one once before but don't know what was the actual fix.
I tried in the past, couple weeks ago, to upgrade to the new 2.3 roms and have had a lot of trouble with the ol' "random reboots". I don't recall what rom exactly that I tried to put on there but I don't believe that the rom was the issue in this situation do to flashing other roms and encountering the exact same reboot issues.
I originally undervolted using vipermod, updated to the new radios from the present "All Radios" post that was grouped together and then flashed a kernal over the rom that I was trying to use.
I got it booted up no problem, went through the setup and then when it was trying to get the reception and/or 3g established it rebooted...the white HTC boot screen appeared and rebooted over and over again.
I tried reflashing the rom, flashing a different rom and so on.
I sort of ruled out the radios after downgrading them and not getting any different results and started to think it was an overheating issue because when I would leave it off for a while it would work longer before the boot party began.
I read something on another thread that when you remove the battery for so long and boot it back up, it clears the internal memory or something similar to that. I searched the market for a boot logger program and found bootlog, I believe that was the name, and checked the log after pulling the battery and letting it boot up all the way. After reviewing the log I noticed that it had stuff like lowmem, deathpening, killing and what not. I then came to the conclusion that it was more than likely the memory, not a clue if it is internal or talking about the temporary stuff that it may store on the sdcard.
I then decided to check out the partitioning of the sdcard. I decided to raise the swap to something like 1 gig and the ext to 2 gig.
I loaded up CM7, nothing extra, and all was good besides maybe one or two reboots that ended up booting all the way up instead of doing the loop at the white HTC screen.
But now, I followed the instructions that was left on http://forum.xda-developers.com/showthread.php?t=1071547&page=1161 (no blame to the post or rom, just a reference) so I can try out a new sense rom...and...if you don't know by now...mayhem/boot loops. I cannot upload any of the logs because I followed the partition instructions.
I have upgraded and downgraded the PRI and the radios with no luck, I am now going to try the partition swap size again and report back.
I am writing this prior so I can get some helpful suggestions coming my way in the mean time, in case me and the Captain can't make this happen, or be able to post my method to fix my scenario so others may benefit.
Thanks in advance.
EDIT: I have S-OFF, HBOOT 0.97, radio 2.15.00.11.19
I still have been having tons of issues and I've gone back to roms I ran 6 months ago n still having the same problem. It just randomly shuts off and turns back on sometimes like 5 or 6 times in a row. This is getting very frustrating I'm gonna have to put it back to stock and take it in. I want to smash my evo with a hammer and then blow torch the sh*t out of it.
I'm having the same problem, only with the Inspire 4G though. I notice mine only happens when the screen turns off.. I'm thinking mine might be an underclocking issue or something because if I have an unread message or if the led is on or flashing at all, it works fine.. Wait, no, it just did it again fml
This is why I dont want to upgrade my radios, you say you ruled out those, but your phone is still jackin up on old roms.
It jus seems I never see an issue that cant be solved by reflashing the rom or a redownload the rom and flash, unless......you mess with the radios, then u get issues like this..im no expert, but this is what I see.
....Radios scare me!
If it was me I would proly unroot it and bring it in, or
Copy SD card to your PC.
Format SD.
Run an RUU that matches your original radios.
Copy SD card data back.
Re-root.
Should be brand new then....
EDIT: Scratch that I wouldnt unroot and bring it in. Easier to runn the RUU like I said
Sent from my PC36100 using XDA App
Never flashed a radio unless a rom came packaged with one... Couldn't tell you which one because I've flashed a bunch already seeing if that was the problem or not. I'm partitioning my SD card right now to see if that helps.. Oh, and I bought my phone off eBay cause AT&T sucks at life and it's not a year wait anymore to upgrade. God how I miss Cingular.
Think i figured it out on my end... I don't think my phone likes to be underclocked so I bumped up the mhz a little for screen off and I haven't had a problem yet
Sent from my HTC Desire HD using XDA Premium App
Again I spoke too soon
Hey all,
I've been using my HTC EVO 4G for quite some time now (nearly a year), and just recently it started acting up. As the title implies, my phone randomly shuts itself off and starts itself back up-- for reasons I cannot determine. Usually when it does it once, I find that it goes on a rampage and shuts itself off before the phone even starts up. It will continue to reset itself for 3 or 4 times before it starts working properly.
I've honestly no idea what could be wrong with it. When this first started happening, I was running Fresh ROM 4.2 (but I've already been running it for a while-- it couldn't have been the ROM), and the default kernel for Fresh. I decided to boot into recovery for an earlier version of the ROM, but to no avail.
Finally, I decided to get a whole new ROM (am currently running on Synergy) and kernel altogether (currently running on netarchy kernel), but again to no avail.
Of course, I did a complete data wipe upon installing Synergy, so it can't have anything to do with phone's software, can it? I'm assuming it must be something physical; and am seriously considering purchasing a whole new SD card. (About the SD card: whenever I try mounting my EVO as a disk drive, immediately after I select the 'Mount' option, a notification saying 'Preparing SD card' pops up, and fails to ever mount it. This, I believe, is due to the fact that I'm not on a .92 Hboot, but it is nevertheless worth noting.)
Has anyone else ever had this problem? Any help would be greatly appreciated.
Edit: The fact that I can't mount my phone as a disk drive is actually a problem in itself... I need to convert to Hboot .92, but my file system isn't FAT32 (at least, I'm assuming so, since it doesn't load my PB31I.zip IMG in Hboot) and I can't convert it if it doesn't connect to my computer... Guess I'll go back to Fresh.
Does your phone kind of heat up sometimes? Like in the front of the screen? My did and it turned out to be a physical problem. Bad charger port, sounds weird but thats what I was told. You might need to buy another one.
ruben1221 said:
Does your phone kind of heat up sometimes? Like in the front of the screen? My did and it turned out to be a physical problem. Bad charger port, sounds weird but thats what I was told. You might need to buy another one.
Click to expand...
Click to collapse
Yeah, I had originally thought it was an over-heating problem as well. It used to happen most of the time while I was driving-- with the sun hitting the phone directly. However, it's been doing it in-doors with A/C and virtually every other place . I just took notice of it in the car because that's when music was playing.
Ultimately, I might just consider transitioning to the Galaxy SII.
Thanks for reply. <3
I've been having same problem had my evo since day 1 and never any problems up unitl a few months ago.but now i definetly know i need a replacement mine phone gets super hot as well originally thought it was the rom but went back to stock all for nothing because the problem still remained
Is call power cycle the only way to fix it is to get a refurbish phone from sprint they know about it, they will do a test on it and order you another phone with the new 2.3.3 that cant be rooted, is not the sd card it is something on the hardware motherboard
Ok, so the past two-three weeks, I've been having the same issues with my phone occurring. It's the T-Mobile G2 variant, with the DZ Engineering HBOOT. Regardless of what rom I install (bear in mind all these issues are across the following, not localized to one specific type of android), be it gingerbread, ics, jellybean, kitkat, these things all occur: Firefox makes my phone freeze for some unknown reason, there is horrendous lag once in a while, even on a stock gingerbread rom, and the final and most annoying issue is that about 3-4 times a day my phone will freeze to the point where I have to take out the battery. My hardware keyboard is starting to go as well but I know that can be easily repaired. Do you think it's starting it's last leg of life? I mean, it seems kind of like it, and I'm probably going to purchase a new phone next paycheck if it keeps it up :/
Im sorry i have no idea about your device issues. As per your description, i guess its a hardware issue.
_____________________________________
For me, yesterday whole day i too was suffering seriously since my DZ started to have unresponsive touchscreen and softkeys.
Switched it off and on.
Took out the battery.
Erased cache and dalvik cache. Still no help.
Even in 4EXT recovery, touch didnt respond properly.
I too thought its time for a new Device.
Later on, what i observed was sometimes, when i locked and unlocked my device, then for some 1/2 minute, my soft keys and touch responded. And again it would go dumb.
It was so painfull.
Then i thought of, restoring my Stock nandroid back.
Deleted Android folder from SDcard, even some other folders created by some applications.
Atlast with lots of trouble, i restored back.
Now things are fine again.
Touch is perfectly fine now.
Im posting this, as someday someone may get a clue that these errors can be due to Software issues rather than a hardware.
Thanks...
arunal_123 said:
Im sorry i have no idea about your device issues. As per your description, i guess its a hardware issue.
_____________________________________
For me, yesterday whole day i too was suffering seriously since my DZ started to have unresponsive touchscreen and softkeys.
Switched it off and on.
Took out the battery.
Erased cache and dalvik cache. Still no help.
Even in 4EXT recovery, touch didnt respond properly.
I too thought its time for a new Device.
Later on, what i observed was sometimes, when i locked and unlocked my device, then for some 1/2 minute, my soft keys and touch responded. And again it would go dumb.
It was so painfull.
Then i thought of, restoring my Stock nandroid back.
Deleted Android folder from SDcard, even some other folders created by some applications.
Atlast with lots of trouble, i restored back.
Now things are fine again.
Touch is perfectly fine now.
Im posting this, as someday someone may get a clue that these errors can be due to Software issues rather than a hardware.
Thanks...
Click to expand...
Click to collapse
After reading through that, I think what I'm going to do is probably back up my essential stuff on my SD card to my computer, completely wipe it and transfer the stuff back and do a fresh, rooted stock rom install to see if that might help. I'll report back with the results here after about a day of use or so
So I tried what you posted for your issues, and it didn't help much sadly. Needless to say I have a new daily driver phone now, so I'm gonna turn my Vision into a social/media device so it doesn't go to waste