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...
Related
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
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.
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Sounds like you need to Odin.
bigdreco said:
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Click to expand...
Click to collapse
I got that on EB as well. It's weird because it didn't start as soon as I flashed it. It was maybe about a week later when it started doing that. When it happened to me my phone would vibrate sporadically and then the screen would finally go "black" or turn off. The odd thing is the bottom four buttons would stay lit. I would have to pull the battery. It started happening more and more frequently. I've since flashed to EC and am rooted but that's it. I've been flashing back and forth between different set ups, so I haven't been on this current set up for more than 2 days. I did however have the same problem today at lunch. I had to pull the battery to get it to reset. I was playing a video I recorded on my phone before the screen went black. I don't know if it was media related. I will play some more videos and see if it does it again.
k0nane said:
Sounds like you need to Odin.
Click to expand...
Click to collapse
I Odined a fresh EB a couple of times and it would eventually come back. Not sure if it was a program I was using that triggered it on EB. I don't know if it might be a media issue. I use my camera and video pretty frequently, so that's the only thing I can think of at this point. It's the only thing I really use, even on EC, on a regular basis except my XDA app. I hope it's not that!...
cpcormier3 said:
I Odined a fresh EB a couple of times and it would eventually come back. Not sure if it was a program I was using that triggered it on EB. I don't know if it might be a media issue. I use my camera and video pretty frequently, so that's the only thing I can think of at this point. It's the only thing I really use, even on EC, on a regular basis except my XDA app. I hope it's not that!...
Click to expand...
Click to collapse
Have you tried formatting your SD card yet?
k0nane said:
Have you tried formatting your SD card yet?
Click to expand...
Click to collapse
I haven't with EC, but I did with EB and I still had those problems. Today was the first day that it's happened to me. I've only been on this set up for the last couple of days, because I flashed a couple of things and hoping that I would have better luck with stock. I will try re-formatting when I get home. I tried playing a coulpe of videos (the same ones as before) to see if I could replicate the problem, but haven't been able to yet. Hopefully that was just a situation to where the phone just needed to reboot....
bigdreco said:
Is anyone getting the Screen of Death.. (or whatever its being called).. on EC05??
im on EB13 and I have to pull my battery out at least 8 to 10 times a day because the screen wont come back on...
is anyone getting this on EC05 or has the issue been fixed??
Click to expand...
Click to collapse
!!! Y E S !!!
It happened to me four times today!
Does anyone know a way to get logs to continuously write to disk? Otherwise I have no idea how to troubleshoot this.
I'm running, midNIGHT EC05 with minimal apps installed. I use SetCPU, and I've just changed the settings. I'm thinking this may have started after trying to use 100MHz and "startass" setting. My profiles are now set to 200Mhz minimum and "ondemand." I'll let you know how that goes.
Having to use my old BlackBerry Bold as an alarm clock now, just in case!
EDIT: I did not format SD with this install but have formatted less than 2 weeks ago.
Happened again after setCPU settings were changed.
That happened to me but what's weird isnit only happened when I was on di18 kept having to pull the battery and once I updated to eb13 it all stopped
Sent from my SPH-D700 using XDA Premium App
Do you have Beautiful Widgets installed? Is one of their widgets on your HS? .. Had this problem on DK28..
Same here. Like the term sod, btw. Happening when I use flash. I'm on stock ec coming from fresh odin, and formatted sd.
Sent from my SPH-D700 using XDA Premium App
alfiej said:
Do you have Beautiful Widgets installed? Is one of their widgets on your HS? .. Had this problem on DK28..
Click to expand...
Click to collapse
No Beautiful Widgets here.
I am running Go Launcher, which is new to me. Will likely eliminate that tomorrow. Oh yeah, the only other widget new to me is "Android System Info" (which is great, btw).
I run Pure Grid calendar and Sense Analog Clock widgets, but I've been running those without trouble for months.
Does anyone know how to change logging levels?
The only rom I was able to use without the SOD was myfrankenstein DK28. While on
EB13 it did it contstanly and much hasnt changed while running EC05. I formatted my sd card and only installed minimal apps. I tried not restoring from Titanium or Astro. Fresh install from market and it still happens. I've stopped using SetCPU, that didnt help either. I do have Beautiful widgets running on my home screen, but I aslo had that while running DK28. I have no idea what the problem is. It is a complete pain having to check my phone every couple of mins to make sure that its still on. Over night forget about it, every morning the phone is dead. Can anybody help me please.
I just Odin to EC05 last night.. and installed the new syndicate frozen rom... and my screen just went blank today.. so far it has done it twice in less then 5 minutes....
but I have noticed that if the phone is plugged into the charger that it wont do it.. no matter how long goes past.. thats the only way I know my alarm is gonna go off in the morning.. is to have it plugged in..
do anyone know if its doing it on plain Stock untouched modem and stock rom??
because if not imma flash over to that.. I cant take this crap too much longer..
I have had this so called SOD for almost 3-4 months and as a matter of fact I just ordered a replacement 10 minutes ago. My SOD involves the phone either rebooting or completely going black except for the bottom cap buttons, then vibrating in order once, then 3 times, then once, and so on until a battery pull. This has happened on the charger as well for some roms. I can tell you it does it on a stock rom. I just did a full reset, stock eb13, updated to ec05 OTA, wiped sdcard and everything except contacts. The problem exists, so I am almost 100% that it is a hardware flaw somewhere. I even did the ##786# reset. I'll let you know if a new phone fixes the issue :]
damn.. even on the stock rom huh???
well do anyone know if it might have something to do with rather journaling is on or off??
other wise.. i have not a clue of what could be causing it..
I have EC stock rom, but am rooted. It happens to my phone. It doesn't happen quite that often like you guys, but it happens maybe about once a day. It happened more frequently when I was on EB. It would happen at least 5 or 6 times a day. It's strange cause it never happened right when I flashed EB or EC. I was fine for a couple of days before it happened. Not sure why....?
I had to pull the battery 20 or more times today, same issue. Mine started doing it right after I added the news and weather widget to the homescreen. If it does it tonight im thinking of takin it back to stock and getting a replacement.
EB13 btw, flashed EC05 a few minutes ago and will try it out.
sultan.of.swing said:
I had to pull the battery 20 or more times today, same issue. Mine started doing it right after I added the news and weather widget to the homescreen. If it does it tonight im thinking of takin it back to stock and getting a replacement.
EB13 btw, flashed EC05 a few minutes ago and will try it out.
Click to expand...
Click to collapse
I had about six today. I'm flashing stock and running untouched starting tomorrow. If that doesn't fix it, it's replacement time for me too.
Sad, because a stress test on my phone at 1.4ghz ran fine.
Btw, I still use set cpu, but only in known safe configurations, no OC.
I just received my replacement. Brand new phone, I installed a formatted sdcard and synced contacts... within 10 minutes it seemed to be happening again. The phone was stock di18, then it updated to stock EB05... I have no idea what the problem could be now, since this phone is brand new.
Is there any way at all to disable the Fascinate from ever loading into safe mode again? It's really annoying when it happens because I have to reset all my widgets.
I've flashed my phone several times and it happens with every rom that I've had on it so is it part of the baseband kernel?
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
johnnyplaid said:
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
Click to expand...
Click to collapse
X2
List off the steps you used when flashing these last few roms (and what rom specifically) that you say are making you boot into safe mode...I've only seen it once on my phone and 1 reboot fixed it and I never seen it again, but that was months ago and I just chalked it up to me missing a step?! I have flashed many roms since and never see safe mode again.
Sent from my SCH-I500 using XDA App
Im starting to think that it's more a problem with my Fascinate than anything else. It usually happens when I have to pull the battery due to it locking up. Sometimes pulling the battery out a second time still doesn't get me out of safe mode and I have to continuously do it until it does.
For the past few months I've been using CM7 and updating with nightlies. On Monday I updated to the stable GLITCH kernel and so far it seems to be running much better. It's always had a problem with randomly bringing up my keyboard and backing out of apps and I have not had that problem yet since putting the GLITCH kernel on it.
Figured I'd also note in here that the GLITCH kernel is not currently working with the newest Cyanogen nightlies. It bootloops and I found that out the hard way.
For now im running GLITCH v11.1ML and CM7 Nightly 35 and it's been great so far.
so glad I havent run into safe mode
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