Anyone noticing random crashes with the g2 cm7? Atleast once a week when I take it out of my pocket it doesn't power on and requires a battery pull to turn it on. (No lights, nothing)
Battery voltage issue?
Different people have been having different issues. What nightly/RC are you on? did you do a full data/cache/dalvik wipe before flashing the ROM? did you try fixing permissions?
Yup, I know there are some issues but it seems strange that the whole phone goes into a stale state which requires a battery pull. I believe its happened once or twice with cm6 as well.
I have done all the wipes and fixes etc. I am right now on nightly #15, I previously was on nightly #7 for a long time so maybe it was just that release. Thanks for your reply.
Haven't had one random reboot. Still using nightly 6. My mytouch4g has not had this problem either.
From my permarooted 1209mhz G2 with CM7 nightly 6
Are you overclocked?
Sent from my %s running Cyanogenmod.
Only to 1Ghz.
Today it died while charging, dead and needed a battery pull. Any ideas?
You're not the only one with this issue (myself included), and the cause is not yet known. And it seems there may be a couple different variations of this issue with the same symptom (of the phone powering off while asleep and needing a battery pull to power back on). May be related to overclock, GPS, screen-off profiles, full moon, or who knows what. See this thread for some various thoughts on the problem.
http://forum.xda-developers.com/showthread.php?t=908095
I personally think its a kernel issue, or that the kernel is at least one of the factors. I flashed pershoot's kernel and the problem seems to be solved, so far (keeping my fingers crossed). Having the GPS on while you turn of the screen also seems to be a common trigger for many who experience this problem.
Hi there,
Thank you so much for your reply! I couldn't seem to find any information on the forum.
I just wrote a post because I had the same thing happen to me. Phone just went dead for ni reason and I had to pull out the battery. But my phone isn't rooted. So it might not be because of CM7.
Tried to call Bell, but the wait time was too long. So will try to call them when I get home.
Sent from my HTC Vision using XDA Premium App
There are at least two other threads about this on XDA and quite a few others on the net.
Google HTC phone freeze random crash reboot battery pull or some combo.
No solutions and it happens on stock phones as well as rooted.
Did you search?
Having the same problem recently on my unlocked Desire Z from Bell, using on the Rogers network. It started yesterday and all of a sudden it turns off, and the only way to turn it on is removing the battery and putting it back in. This never was an issue for months. The only thing I updated from that affects the hardware is the new Google Maps, so I think GPS may be the case. But I really need GPS on my phone...
Yesterday I did an experiment with GPS. For me GPS is the case that makes my phone to freeze. With new Google maps it freezes even faster, more often.
Sent from my HTC Vision using XDA App
Related
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
yep
+1
Not very often but very annoying if you use your phone as alarm clock.
I honestly haven't experienced either with my SGS. I can sympathise though as my Milestone used to do both way too often (hence swapping for the SGS).
It hasn't happened to me.. It might be running a software or hardware watchdog to reboot automatically when the system panics. Ensure you are using a stock rom, otherwise, it may even be faulty hardware
Would happen several times a day on my Motorola Milestone so I sent it back and got the SGS. Totally rock solid. Only time it reboots is when I want it to. Maybe you have a rogue app?
you guys have any changes to the CPU speed whatsoever, task killers and all? i once used SetCPU and it sort of sent me into a random spree of reboots and such.
i remember rebooting, scanning 10gb of media, auto-reboot... repeat 4 times. lol.
Well it hasnt happened since yesterday. I will flash to froyo today just in case it was software related
Sent from my GT-I9000 using XDA App
dakine said:
My phone decides to reboot and or power off randomly and for no apparent reason. It's just sitting on my desk. Anyone else experience this issue?
Guess i'll try a reflash if this continues.
Click to expand...
Click to collapse
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
AllGamer said:
did you see the topic on the DEV forum about Resetting the battery status?
seems like the phone (not the battery) keeps a wrong battery status if you flashed it a few times
so even when you still have battery, the phone "thinks" it rans out of juice and it does that thing you mentioned
Click to expand...
Click to collapse
Link would be helpful, because I can't find that topic.
WOW, old thread that got dug up, for me it was just a software issue. I flashed many roms since and haven't had it happen again. I never reset my battery stats but I think clockwork mod recovery has an option to do that so most of the custom roms make that easy.
I also had random reboots and power-offs, on average once every 2 weeks, running on stock-firmware JF3. Problems did not go away when I manually upgraded to JM2. Problems stopped when I upgraded to Froyo...
Earlier, my G2 shut off on me about 5 times. -_-
First, I had it sitting in the car ,tried to take a pic but the stupid voice recognition menu kept coming up so I gave up and set it down in the console. When I got home, the phone felt warm and was.. off.
Then, I turned it on.. stuffed it in my pocket. A moment later, I pulled it out and YET AGAIN when I pushed the button I was greeted by a quick vibe and the HTC screen -_-
Then a few minutes later I ran a speed test (checking HSPA+ out in Vegas).. put it down on the table.. come back.. PHONE IS *(@#% DEAD AGAIN.
I HATE YOU! *glares at phone*
It's killing me because it either happens several times in a row, or doesn't happen for days! I've tried replacing the sim card, replacing the SD card.. moving the battery... no dice.
Maybe it's my SIM card? Would that cause it? My last phone did that -_- And I'm silly to have not yet changed the SIM lol
Good thing I have a spare sitting in my bag.
What battery are you using? Aftermarket? Is so, did you remove the sticker around the battery? If you did then make sure you place a piece of tape on the battery to avoid making contact with the metal sd card holder. The metal on metal causes it to shut down.
Sent from my HTC Vision using XDA App
Interesting. I've also been having random shutdowns (not reboots, which I've seen mentioned elsewhere, due to a hardware fault) --
HTC Desire Z, using default battery, but I'll try isolating it anyway with a slip of paper or something.
OP you on a custom rom with overclock? maybe your clocking your phone too high or low?
Also if the phone for whatever reason gets too hot or cold it will turn itself off.
Please see this forum: Phone powers down and won't turn back on w/o pulling the battery
I strongly believe that this may be an issue with the GPS and/or Google Maps. Once I have the GPS off, this has not occurred. Can anyone else try this?
I have the Bell Desire Z NAM with stock HTC Sense 2.2 ROM.
It seems to be quite prevalent, see the bottom of this review: T-Mobile G2 is speedy sequel to original Android
I think you may be onto something with that GPS note, but my phone doesnt' need the battery pulled to restart.
Also, it's running the stock firmware, stock battery (just exchanged battery and got a new SIM card yesterday, and it shut off again today.. so those aren't the problem)... so any issues I'm having are 100% stock related...
This time it shut off after using Maps so....
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
fablife said:
i read somewhere (trying to find the source) that some G2's were experiencing random restarts / shutdowns due to low signal strength. Not sure how valid this is but you might want to look into this as well.
Click to expand...
Click to collapse
This was true before we received the first OTA update. Since then though the problem has been fixed.
I think it was definitely the GPS, that said I just got done with a really long phone call about this and have a replacement on the way.. but that was way too much effort AND I have to pay shipping (it's not much, but seriously.) I'm not happy that T-Mobile was THAT big a pain in the butt about getting the phone replaced with a new one in the 30 day return period.
Going by the pointers one of my close friends on sprint (that used to be on AT&T) gave me, I'd say this could've been worse with another provider.. but it shouldn't have been. The reception isn't the best so the customer service should make up for that, and it sorta does.. but it sorta doesn't.
Oh well.
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
djrajir said:
I have been experiencing almost the same thing for the past week or so. I have tried a few things such as lowering clock speeds, changing roms, and not using maps or GPS. Nothing has stopped the shutdowns. I cant seem to find a pattern in the things the phone is doing when it shuts off because it rarely does it when i have the screen on, also it never does it if music is playing or if i am watching a video. I will say that it seems to happen alot when i am in spots i know are dead spots for phone signal. I flash roms a fair amount so it is hard to say this has started after flashing a rom, but I will say it never did this before I flashed my first sensui 3.0 rom.
I am thinking its one of two things, something with the radio and/or its firmware or something with the sdcard because at least one senseui 3.0 rom said something about sdcard formatting.
I hope all this helps the smart people come up with idea on what wrong with our phones.
Click to expand...
Click to collapse
My Desire Z had the same problem and I returned it to HTC Service for repair. They said they change some cables? and a new battery. It has been nearly 3 days and I haven't experienced a single shutdown but there was one time it restarted by itself.
Yeah my only problem with that is, I am close to my upgrade date. How much did it cost. I may still do it so I can give this phone to my kid brother.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Just to update, I found that I can make it do it some times when playing with opening the hinge.
Sent from my Htcclay's SuperCM7 G2 using Tapatalk
Possible cause/fix found
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Talked to tmobile CS today and was trying to get a replacement because my phone would randomly reboot and shut off. All he told me was go and pick up a new sim card. If that didn't help then they would be willing to give me a warranty replacement.
Sent from my T-Mobile G2 using XDA App
carquote said:
I posted this in another thread here regarding the same problem but it appears it may have been overlooked so I'll post the info again in hopes of helping you and others having this problem.
A possible cause/fix has been found as posted on the T-mobile forums:
http://forums.t-mobile.com/t5/T-Mobi.../513575/page/4
There is a conductive metal strip along the back of the battery that looks like it may be shorting out. Check out the link for detailed fix with pics. I take no credit for this, just posting it since I'm experiencing this problem too.
Click to expand...
Click to collapse
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Is this possible fix something else than lining the back of the battery with a strip of paper?
whpsnp said:
Clicking your link all I got was an empty T-Mobile page with the message "Page not found" and some some java script error message when closing the window.
Click to expand...
Click to collapse
Sorry about that, I fixed the link and it should be working now.
Cool, thanks!
Sent from my HTC Vision using XDA App
I'm pretty sure mine is not caused by the metal strip since my battery's all proofed. I didn't have anything wrong with it until about half a month ago, and it always happened after using GPS and left it on. If I turn it off after navigation or any other app that requires GPS the phone won't go into SOD.
I switched back to CM7 RC2 around that time and starting to get the GPS no fix problem, and it could't be fixed by the dd=/dev/.... script. So I switched into Nightly 88 or something that at least I was able to get a fix but the not-so-random freezing started.
This morning I flashed the new 7.1.0 RC1 and the phone would just turn itself off (it used to just freeze and become hot), and I got really tired of it... My old G1 was much more reliable than this.
I tried the dd=/dev script again, so far after 5 min the phone is still on with GPS on....
@carcuote
Thank you! I haven't had this issue for months now. But the solution is so easy to do that I will try our anyways.
I had this issue the first month our so when I got the new phone, but went away permanently after the second month. Maybe the contacts in the battery got a little rusted? Don't know but the solution is simple enough to try...
Sent from my T-Mobile G2
My phone will randomly shut down and will not power back on unless I pull the battery, I have 2 batteries and it happens with either one. It does not shut down while on charger/dock. I have wiped the phone multiple times with odin, I've used several different roms/kernals,same results every time. Just curious if anyone else has been experiencing this issue.
I've been experiencing this after I went to eb13 with the custom kernels that are out. But my.phone will either lockup and I have yo pull the battery or it will reboot itself. Never had what happens to u yet.
Sent From My Evo Killer!
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
nalewis89 said:
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
Click to expand...
Click to collapse
I'm averaging 10 times a day myself
Permanent sleep
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
before updating to 2.2 - I did the DK28 and now the EB13 one - with 2.1 I would have my phone randomly reboot - I would be sitting there and here the music it makes when it starts up but I never turned it off?
other times it would just be turned off, but when I turn it back on the abttery is not low enough to cause it to turn off
all this went away with DK28 2.2 and hasnet happened since I installed EB13 2.2
This happeed to me the other morning. I wasn't able to boot until I reflashed the kernel. Twilight frozen btw.
Sent from my SPH-D700 using XDA Premium App
My first epic would randomly hard power off, even running stock ROMs. If you are running a stock ROM and seeing a hard power off at random, I suggest you go swap the phone. It's just broken.
Ive never had this problem and im on my first and only epic and ive had it since it came out,
Ive been very careful with my epic as it has been great to me, it hates me probaly tho for feeding it stuff while experimenting things that make it spit up FCS,
But my phone has been always working perfect, all the way back to d118.
CLazman said:
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
Click to expand...
Click to collapse
the buttons don't stay lit, i'm using twilight kernal right now but was happening with genocide kernal too, going back to eclair just to eliminate 2.2, ext4, etc.. to see if it's a hardware issue
First try
dk18 update.zip flash
Restored apps and data with my backup pro root
Random reboots, FC
Second try
Odin to dk18
Wipe x3
Restored apps and data with mybackup pro root
FC, music player force closing (doubletwist, stock and musicmod, poweramp worked though?), fc when trying to change ringtone or notification.
Started reading about others with the same issues and thought data backups were a reoccuring theme. Did a third try tonight and so far so good. Music players working, no force closings, keyboards working correctly, gps lock indoors. Its still early, problems might still popup, thought id share...
Latest froyotempt
Fresh backup with mybackup pro root
Wipe x3
odin eb13 prerooted (ctsy xda forum) same file from attempt 2. Did this x3 as well, read it in a thread somewhere...
backup apps only with mybackup pro root
All attempts were with genocide kernal.
So far so good, none of the previous bugs are apparent, so far... Those of you that are on the fence regarding doing the same, so far its worth the time.
Sent from my SPH-D700 using XDA App
I was thinking back-ups were part of the problem also, so I used odin and started all over from dl18 without restoring any data, same problem still occured
Still messing with my phone, everything that was broken seems to be fixed. Hopefully it stays this way...
Sent from my SPH-D700 using XDA App
That used to happened to me on eclair when I set my setcpu profiles too low when screen off. You wouldn't happen to be using setcpu would you?
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
I'll add to this thread. I seem to be having the same problem and I believe it started when I installed quantum rom... but I'm not sure. The symptoms i had were random reboots, where the screen would shut off and the 4 lights would stay on. Then I would have the sound of lost signal as if my phone rebooted and was starting over. Also, the most recent problem I get is my phone completely shuts off and I need to battery pull to get it to start up, and it loops on the splash screen of my rom. I have tried doing a complete odin wipe and not restoring anything and I believe it is still happening...
joedig52 said:
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
Click to expand...
Click to collapse
Any update?
Also, make sure the governor isn't "powersave". If you have 100-400MHz powersave governor, it still ONLY runs at the lowest speed (100MHz), even if it's 100-400MHz.
Still happening, not on powersave, doesn't matter what settings I have in set cpu. Did a hard reset back to 2.1 and it still happens, bringing it in for repair.
When placing phone call my device crashes with purple led flash.
cell signal normal, text messages work, cell data works
I'm not sure if problem lies in hardware or software(bad flash, radio, ect)
I replaced the digitizer
Currently running Kang ICS RC0-9.0 | faux123-v025
Had same problem with Neutrino 2.1
Any ideas or test suggestions?
PROBLEM SOLVED, WHERE DID MY FRIDAY NIGHT GO THOUGH?
*deleted post incorrect information
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
dac1227 said:
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
are you already on 2.3.4.91 ?
chamoy said:
are you already on 2.3.4.91 ?
Click to expand...
Click to collapse
No, I couldn't get the zip for 4.91 to flash for some reason so I did Neutrino 2.5 after sever data formats.
update: on on GB 4.5, same problem persists
SOLVED
How did you solve the issue?
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Well the issue was less solved but minimized in the end.
After many fastboot formats and CWM flashes, I ended up fruitcaking back to 2.3.4, that's when the problem started to be less of a hassle; meaning the screen would come back on and buttons/soft-keys were again responsive and a battery pull wasn't needed.
I re-installed Turls ICS and the problem is still present, but it doesn't hinder making or receiving calls, I just hold my breath with each.
I'm suspecting that when flashing either the kernels or roms, things are not getting cleaned and formatted as well as they ought to be. I know there is a universal CWM zip floating around somewhere (seen it in the skyrocket forum). We've had similar issues in the skyrocket forum where remnants of previous flashes were being persistent, or resistant to format attempts.
I messed with it for hours trying to fix so I cannot say for sure what I did to make it a non-immediate issue, but if others describe like problems I try and help.
xscottishx27 said:
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Click to expand...
Click to collapse
I was having the issue with Neutrino 2.1, 2.5; Turl ICS, and stock 2.3.4. The latter seemed to be the most effective method I employed to fix, without bricking.
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
Never had one so far. Running stock 4.2.2/Franco kernel nightly_110
-Edit- currently undervolted -75 mV.
just stop messing your phone up with stupid OCing and benchmarks... This issues are installed to protect the hardware from crashing... ( Red light of death... )
My phone just fine. never had this SOD.
Never had an issue on this device. On my old phone, dropping the min CPU speed too low would cause it a LOT.
tommyga said:
Hello everyone,
I would like to know how many of you are experiencing the different kinds of SOD on the Nexus 4.
I found few references to the SOD issue, but no one could tell exactly why this is happening.
Some say it's a software issue (some say it only started to occur at JB)...
Some say it's an hardware issue.. some of them RMAed, and got a new phone with exactly the same SOD issue.
I would like to dedicate this thread to this problem and see how many other Nexus 4 users are experiencing this SOD.
Click to expand...
Click to collapse
You don't have an option for unable to turn on phone without a reset: no blinking led. This is also a scenerio.
Please take a look here! http://forum.xda-developers.com/showthread.php?t=2195278
I've tried almost everything (wipe& re wipe , install stock ) and nothing seem to solve it.... most frustatin thing is when I hit "home" after playing heavly and ...bamm it goes black screen & hav to reboot pressin home&vol+
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Are you using a custom kernel to undervolt? That can cause SOD.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Im using it now (customROM&UV) since it doesnt affect my issue.... I tried completly stock for 2 days and keep crashin... or at least on g.earth as I didnt install any app/game to be sure its not an app related issue.
Cant figure out what happens, it can play games w/o any issue, but sometimes when I change orientation it just goes black
PD: I dont hav enough time, but ill do a logcat to see what can possibily make it freeze
My case is not listed in the poll options:
- the phone went into standy, good battery, no calls, no high loads;
- LED was inactive totally.
- then I was unable to turn it on normally (only through reboot).
While in this state, trying to call the phone resulted in "long" tones, i.e., like the network saw the phone. The phone did not ring.
This happens with the latest stock firmware on the 2nd day of my use. Non-reproducible. Phone returned.
Would be delighted to learn if that's a hardware or software issue
Not necessarily SOD but experienced extreme battery drain under these situations
1- Charging via USB and left phone connected after PC shut down.
2- Charging via Wireless Charger left it on the pod.
In 1st ASA pc is shut down
and
In 2nd ASA Phone charged completely , as I suspect the charging process goes backwards ! It someone drain current from your battery to the power source.
AFAIK none of these issue are positive with normal good old AC charging. However you can still use a workaround by using the app called "Safe Charge"
This is my experience