Develop Bugs

[Q] SD Card causing Power Button to be Unresponsive?

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.

Evo Issues Random Restarting and Freezing Power button not turning on Screen

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

HTC DHD freezes up!

Hi all!
Since a couple of days my HTC DHD has been freezing up. Most of times it happens when i take it out of sleep mode. The bottom buttons (home, menu, back and search) do light up, but the phone doesn't respond at all. Sometimes this also happens when using the phone. The screen moves slowely, like a frame every couple of seconds before it freezes up completely. Only way to get it back on is taking out the battery and put it back in. I have installed Cyanogenmod 7.2 about a week and a half ago so i thought the problem might lie there but i switched back to Cyanogenmod 7.0 (which i have been using for the past 6 months or so without any problem at all) and the device still freezes up. This happens twice of more every day! I have wiped everything and updated all my apps and the problem still occurs. I'm really clueless on how to solve this problem.
I can provide a logcat but i have never used that before so i'm not sure on how to do this. Even then, how can i make a logcat when the device freezes up and i need to take out the battery?
Any help would be much much appreciated!!
Thanks!

Did you do a full wipe; all caches, Dalvik e.t.c
Sent from my Desire HD using Swype beta for Android!

The best way to get a logcat is using adb and perhaps a terminal emulator.
Try using the phone without the sd card to see if the problem persists.
Sent from a dream

Thanks for your replies! Sorry for the late response but had to install SDK and get it up and running.
@ GuyInTheCorner, Yes did all that except for a full wipe. Don't want to loose all my data.
@ Teichopsia, Ok did what you said and i have Logcat running now. Just tested it and it seems to be working. It's huge tho with only a couple of seconds running! Now i have to wait for the device to freeze up again and i can get to my computer while it doing it. As soon as that happens i will make a logcat and post it here.
Thanks for you help so far!

You've changed roms without full wiping? Try it without the sd card to see if there is something in the sd card causing the problem. However, you will probably need to full wipe. If after the full wipe problem persists, check without the sd card, if so, wipe the sd card.
The logcat will help figure where the problem is, but I don't know how to read one.
@guyinthecorner: I beat you this time
Sent from a dream

Teichopsia said:
You've changed roms without full wiping? Try it without the sd card to see if there is something in the sd card causing the problem. However, you will probably need to full wipe. If after the full wipe problem persists, check without the sd card, if so, wipe the sd card.
The logcat will help figure where the problem is, but I don't know how to read one.
@guyinthecorner: I beat you this time
Sent from a dream
Click to expand...
Click to collapse
Meh, chalk one up for you
I agree with Teichopsia, do a FULL WIPE without SD Card to see what happens and take it from there
Sent from my Desire HD using Swype beta for Android!

Ok, so it took a while but my DHD finally froze up again while i had acces to a computer. So i did a logcat. Results are in the Logcat.txt file. I hope anyone out there can read it and figure out what the problem is. Many thanks in advance!!

I started a thread for a similar problem ( http://forum.xda-developers.com/showthread.php?t=1734707 ) but the behaviour you describe is identical to what was going on with my DHD.
Try disabling Wifi and see if it stalls up on you - Mine runs great so long as Wifi is turned off. With it turned on I get random freezes, and the screen not turning on with the backlit buttons lit. Removal of the battery is about the only way to get it to respond again.
I tried changing ROMs, kernels, recoveries, radios and bootloaders with varying results but nothing seemed to fix it.
I ALWAYS full wipe and clear any files relating to the previous ROM off the SD card when changing ROMs.
On 2.2 ROMs Wifi would just turn itself on and off, the phone would not freeze though. Wifi was mostly un-usable as data didn't seem to transfer 80% of the time that it was turned on.
On 2.3.x ROMs Wifi started out doing the same thing as on Froyo, but after about a week it started to freeze the phone and would not return from sleep.
On 4..0.x ROMs Wifi would generally cause a complete freeze of the phone almost as soon as it was turned on.
I hope you find a solution. Mine is the 24 month warranty.

@Max-E-Moose
Thanks a lot for your quick and thorough reply.
I get random freezes, and the screen not turning on with the backlit buttons lit. Removal of the battery is about the only way to get it to respond again.
Click to expand...
Click to collapse
Sounds exactly like my problem. I see you have done way more research on this problem then me looking at the thread you started. So i guess the problem lies in the WIFI hardware then. If so, i could send it back for repairs. I also have 24 months warranty. Problem i have, my device fell into a bucket of water when i had it just 3 weeks (about 16 months ago) It never gave me any problems tho! Worked just fine until now. All my warranty labels turned red. I could pull them out and replace them of course. Or tell HTC that it got wet during rain and it was in my pocket. But that wouldn't be honest now would it. A friend of mine has a DHD as well but he tells me he never has this problem which makes me guess the problem only occurs with some builds of the device.
I have been using my WIFI a lot lately for tethering on my laptop. So i will try your solution of turning WIFI off first and just see what happens. Also i will go back to stock rom when ICS becomes available. See what happens ten.
For now thanks a lot Max-E-Moose for your help. I will update this thread if something occurs or i find a solution. :good:

Did u check for apps installed on sd. Try moving them on phone memory if u have space. That can help
Sent from my Inspire 4G using xda app-developers app

grigoriisi said:
Did u check for apps installed on sd. Try moving them on phone memory if u have space. That can help
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
Nope didn't try that. I just ordered a new Samsung 32gb class 10 SD card. Should arrive tomorrow. Will try that first. Maybe it helps.
Thanks anyway.

Any luck ONeils? Updatey?
Due to where I am situated, I have not had the opportunity to bring my phone in yet so am still using mobile data almost all of the time.
I didn't mention before, because I forgot about it, but have you tried using WiFix Manager from the market? I read in another thread that this solved a similar problem for some people.
I think the process is: install WiFix, install the fix from the app, then restart the phone. It should be that simple, if it works - it does nothing for my poor DHD.
Currently using JellyTime Beta 7 and I have noticed that I can turn my WiFi on, and use it for a while, but if I forget to turn it off then the phone doesn't want to wake up once the screen turns off. Wifi hasn't froze the phone entirely on this ROM... Yet.

One V lock screen/dim lock stays on

Ok so I've had this phone for about a week, ordered it right from the Cricket website, I use it often at night as I work third shift and I noticed several times that when I hit the power button to lock the screen it goes black but sometimes still remains just slightly lit. It's happened several times and I have no idea what causes it and I have tried several different things I do all the time before locking it but I still have no definitive reason it might do this. I kept myself from messing with it to see how long it would remain like this and I managed to leave it for about 32 mins, which ate up about 8% of the battery. Any ideas what might cause this out how to fix?
Sent from my HTC One V using xda app-developers app

HTC One V screen lock issues
I'm also having this same issue. I've had the phone for a very short time maybe three weeks now at the most. I've noticed it does this more often when the phones been in standby for extended periods of time. Sometimes it'll do it multiple times in a row (eg: ill lock the screen, notice that it doesnt power off all the way so I'll unlock it and lock it again and the screen will still remain slightly powered.) Also, the screen "blurs" and gets lines through the image when this happens and doesnt have that crisp blacking out of the screen that it should when locking the phone. I havent been able to find any other mention of this problem other than right here. Phone is not unlocked and is serviced by Cricket. If anyone has info on how to fix this I'd really appreciate it.

Unexpected Rage said:
Ok so I've had this phone for about a week, ordered it right from the Cricket website, I use it often at night as I work third shift and I noticed several times that when I hit the power button to lock the screen it goes black but sometimes still remains just slightly lit. It's happened several times and I have no idea what causes it and I have tried several different things I do all the time before locking it but I still have no definitive reason it might do this. I kept myself from messing with it to see how long it would remain like this and I managed to leave it for about 32 mins, which ate up about 8% of the battery. Any ideas what might cause this out how to fix?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
This is a known issue, I have it on my Virgin Mobile One V. (Rooted but all stock except I use Nova Launcher)

mine too. i did notice the problem went away when i flashed a custom rom. this used to bug the heck out of me, so i am glad i got this solved.
by the way, if you flash a custom rom for a cricket follow this guide for mms
http://forum.xda-developers.com/showthread.php?t=2120559

problems with a refurb

hey all-
youve been a great community since ive been around (last december) and i was wondering if anyone had any insight on a problem im having.
I recently got a replacement phone that is refurbished from sprint, because the power button on my old e4gt was completely stuck
when i got the phone i immediately rooted it and went to my usual set up of Blazer 4.1 with the rogue 1.4.1 kernel.
since then ive been having some trouble:
the touchscreen is very wonky, ill be in the middle of texting and it will all of a sudden start selecting things all over the screen. simply turning the screen off and then back on usually works, but ive noticed that the frequency of this is increasing. also the menu home back and search keys all pick and choose when they want to work, and when they dont. sometimes ill press them and they wont work, other times ill be browsing the web and the menu button will start going off and on, without me pressing it.
ive also been experiencing quite a few random reboots, this wouldnt be such a problem however sometimes the phone will just shut off, with the red led light still on, but the screen wont come on when i press the power button. ive also noticed that sometimes the phone will randomly reboot, and then hang on the samsung screen. this has happened a few times at night and caused me to miss class because my alarm didnt go off (lol). when any of this happens i just hold down the power and vol up button to reboot into recovery, and then reboot the phone from there.
the only visible difference i can tell is that under the build number it says: "Blazer v4.1 ~ PI:FG-X^2I^2
i dont remember the last part of that being in any of the previous build numbers; ive been running this build pretty much since it came out, theres just something about the speed, snapiness, and battery life of this gb build that has me hooked.
if anyone knows if these problems are hardware related, or if i just had a bad flash, id greatly appreciate your feedback.
i know this has turned into a long post, but i just have one more question:
i use google play music as my music player, and absolutely love it. my favorite part about it is the fact that i can "download" songs to stay available even when i dont have a data connection, this comes in reallyyyy handy. HOWEVER, i use titanium backup to backup my apps, and when i flash to a new rom and restore play music, it restores all my music, but not the music that i have stored on the device. this is annoying because i then have to wait for a stable wifi connection to download the 500 or so songs that i usually keep on the device. My question is whether or not there is a way to backup all of the cached music, or if i could move the app+app data to my sd card, so i wouldnt have to redownload all the songs when i flash a new rom.
again youve all been a great community and im thankful for all the devs and all the work they do. i apologize for this post being so long, i dont usually post much but when i do ive always gotten the solutions for the problems ive had.
have a great day everyone, and you stay classy san diego

replace
put the phone back to stock and see if these problems still occur. If the do still occur then take it into a service center and have it replaced

ryandoubleu said:
put the phone back to stock and see if these problems still occur. If the do still occur then take it into a service center and have it replaced
Click to expand...
Click to collapse
i wish i could take it to a service center however when i had the battery out of it someone spilled water on the battery so the water damage sticker is now red even though the water never got on the phone.

Brick it and get a new one. They messed up.
Sent from my SPH-D710 using xda premium

Ctanferno22 said:
i wish i could take it to a service center however when i had the battery out of it someone spilled water on the battery so the water damage sticker is now red even though the water never got on the phone.
Click to expand...
Click to collapse
A service center should take the phone apart and check the sticker in the inside. You could also just buy a battery from amazon and use that when taking it in.
sent from MY BAD A$$ ET4G

Will sprit replace a brick phone. Cause I know if you try tweak it and f it up that your fault.
Sent from my SPH-D710 using xda premium

Get android assistant from play. It will allow you to move apps to your SD card. Tools>App2SD
Buy a new battery and send that back with the phone if you continue to have issues