I was on my way home from vacation (5 hour drive) and I had my phone plugged in the car charger with GPS, Google Maps and Pandora running all at the same time, when my phone overheated and shut-down. A warning sign came on saying that it was either "too hot or too cold to charge." Well, i decided to swap batteries and that point when I booted the phone, I got a FC boot loop. I had journaling ON btw.
I had a CWM backup ready, and simply restored it. So nothing was lost. But still, i didn't know our phones could heat up like that.
btw: i was on srf 1.2 w/Genocide 1.2. Underclocked to 800mhz and undervolted slightly.
Anyone else experience and issue like this?
Yep, except I was on bonsai and my problem with the fc made me Yank the battery. Upon reboot there was the android telling me to touch him to begin.
Sent from my Illudium Q-36 Explosive Space Modulator.
I've had that happen once, while using the tethering function, but couldn't replicate it even when trying (yes, I don't know why I tried to break my phone either, but I guess that's what they say about curiosity killing things..)
I did over memorial day weekend. Visiting the west side of Mi... Phone outside charging via wall, streaming pandora through wifi, plugged into speakers sitting in the sun. I use a battery monitor widget that gives a readout of temp... I looked ay the phone and it was at 128°F! Quickly unplugged, shut down the phone, pulled battery and took inside to cool. After 30 minutes when phone and battery seemed to return to room temp I turned the phone back on and once the os booted up everything fc... Nothing would run at all! Luckily I also had a backup to cover me. I was on srf 1.1.1 btw...
Sent from my SPH-D700 using XDA App
i disassembled my entire phone and when i reassembled it i got a bunch of force closes till i restored a back up.
I have had this happen quite often.. It is usually when I am charging and talking on me way home from work.. I will have the phone sitting on the seat next to me, using a headset, sitting in the sun most the time. And it will give me the warning and then reboot, usually when I get off the phone. And when it loads FC's out the butt and just loops. I normally never have a backup, so I just clockwork and reload the rerfs zip and it takes me back to rooted stock and i reload from there.. I can do it pretty quick these days... It actually did it over the weekend and I tried clearing the dalvik cache(sp??) and the cache and it seem to fix the fc's. But I need to just get in the habit of keeping a current backup.. Any way to schedule one in clockwork??? That would be a nice feature..
I actually had a post on this a long time back and got 1 reply..
I think thats a serious flaw in the design of the phone.
You can't charge AND use the phone at the same time? Because it will over heat and cause data corruption? That's ridiculous.
Does this only happen to rom'd phones? or does this happen to stock phones as well?
futureprospect said:
I think thats a serious flaw in the design of the phone.
You can't charge AND use the phone at the same time? Because it will over heat and cause data corruption? That's ridiculous.
Does this only happen to rom'd phones? or does this happen to stock phones as well?
Click to expand...
Click to collapse
i think it only happens to phones with journaling off.
it happen to me as well
but it messed everything up had to wipe and reflash sfr then everything was good but the phone was useless. luck was on my side and it was at the end of my trip.
I have always ran with journaling on!! And dang it, just got back from lunch and guess what... I didnt even have the phone plugged in.. Just talking on it.. It was sitting on my seat and all of a sudden it just rebooted. When it came back up the fc's were there and the same loop as always.. I am currently trying to see what will get me going again. I did the wipes and nothing.. The last time I got the fc's to stop, I also hit fix permissions by accident.. So I am running that now. I am not even sure what that does, but like I said last time it seemed to work.. We shall see... LOL and yeah no backup to use in clockwork.. You think I would have made one this morning huh? And I never noticed this problem until after froyo...
BTW- The fix permissions and combo cache wipe has me back in business..
I think the ability to schedule a regular backup weekly or something would be a GREAT feature for any recovery....
Sent from my SPH-D700 using XDA Premium App
Related
I'm running DamageControl 2.07.
I happened to be up in the middle of the night, and I caught my phone randomly restarting. I've seen it happen before but didn't pay it any mind before, but now this is starting to bother me.
Is anyone else experiencing this?
I have this too. Running DC 2.07.2 and when I'm doing something normal (tweeting on Touiteur, texting, etc.) and the phone doesn't actually reboot, it just..... shuts off. This happens at any battery level from 100 to 0. I turn it on and it's fine, but.... it's really annoying.
Yep i experienced this with all the new Rom base on DC. i dont really know how to fix but changing to an other Rom will fix it. The problem is almost all the new 2.1 Roms that came out are base on Dc so i flashed DarchLegend 5.0.5 and its been 3 days and my phone hasn't done that yet
noticed this too when running regaws mod. flashing darch now with the darchstar theme, gunna give it a go.
anyone know of a white taskbar(with 3g) for darchs latest rom?
I've had this happen to me even with stock 1.5, lol.
I don't know what causes it, it's a pain in the ass. It happened a few times after I rooted too. Lately I haven't had this problem anymore.
my phone rebooted on its own last night, second time thats happened. there was talk of this about 2 weeks ago and the thought is this is a battery issue, apparently a couple people bought new batteries and the rebooting didn't happen after.
Alright this is starting to really bother me now. It's rebooting like 3 times a day now. I keep thinking my phone is hacked.
It's happened to me before on 1.5... I was going to charge my phone overnight while I slept, and no matter what I did, I couldn't keep the damn thing to stay off. Everytime I kept plugging it in, it would just turn on again. Eventually I just pulled the battery, put it back in, and plugged it in and stayed off.
this is the first thread i read upon my return from being banned for 7 days. this sh*t scared the living f*ck outta my a**
ahem
sorry
it happened to me right after i installed the latest regawmod
i simple wipe and fresh flash fixed the issue immediatly
i also pulled my battery, and my nandroid was corrupted
i was scared. i was like damn, 7 says and i come back to this?!
Has anyone else experienced this?
Sometimes (5-6 times in the last 24 hours) when the phone is sleeping, it will not wake when I hit power/unlock. I have tried installing no lock, hoping it was a glitch in the lock screen, but it still happens. The only way to fix it is to pull the battery.
Any advice?
Web sites are over-rated, when you have apps like these
bryon13 said:
Has anyone else experienced this?
Sometimes (5-6 times in the last 24 hours) when the phone is sleeping, it will not wake when I hit power/unlock. I have tried installing no lock, hoping it was a glitch in the lock screen, but it still happens. The only way to fix it is to pull the battery.
Any advice?
Web sites are over-rated, when you have apps like these
Click to expand...
Click to collapse
Are you running setcpu? Mine was doing this when I would lower the speed with a screen off profile. I just uninstalled setcpu for now. I don't think the kernel supports it anyway.
Sent from my SGH-T959 using XDA App
No, I had it, but since I can't overclock yet, there was no need to keep it installed. I did a factory reset, so we'll see if this fixes things.
Sent from my SGH-T959 using XDA App
bryon13 said:
No, I had it, but since I can't overclock yet, there was no need to keep it installed. I did a factory reset, so we'll see if this fixes things.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
let us know how it goes... If you experienced any unable to wakes after the reset...
Seems to be working fine. I'm not sure what the problem WAS, but the reset seems to have fixed it.
Root and busybox were still intact. Had to re-do the lag fix. (Method 1)
I'll update if I get the issue again.
My phone is just so...VIBRANT
Samething happened to me yesterday morning. Woke up found my phone wouldn't go back up. I thought it was dead, until I pulled the battery. I haven't Root hack it or installed SetCPU.
Sorry to throw this issue in this topic, but anyone have any problem with the phone rotating sideway for WEB and Messaging? I thought when I first got it, it worked.. now it doesnt..
There is probably a common app here or something causing this because I don't ever recall hearing this type of issue with the Vibrant before this thread.
I had the same thing happen to me and found after much trial and error that when I pulled my SD card out I was then able to wake the phone up. Apparently there was some problem with my SD (I was using it with my previous phone..MT3G) that was causing the Media scanning process to get stuck.
I ended up backing up what I needed from the SD and reformatting it. Since then I haven't had any issues. We may or amy not have the same root cause but hopefully this does help.
I'm thinking the problem HAS to be software related. After the reset, I've reinstalled everything I had before, and it's working like a charm! I've even used Titanium Backup to remove a lot of the bloatware, and still ruining great!
I just wish we could get a logcat, but when it happens, the phone is dead until you pull the battery.
My phone is just so...VIBRANT
bryon13 said:
I'm thinking the problem HAS to be software related. After the reset, I've reinstalled everything I had before, and it's working like a charm! I've even used Titanium Backup to remove a lot of the bloatware, and still ruining great!
I just wish we could get a logcat, but when it happens, the phone is dead until you pull the battery.
My phone is just so...VIBRANT
Click to expand...
Click to collapse
I am almost 100% SETCPU is the problem..
My phone would not come out of sleep.. I had to pull the battery and when I turned it on it would say "auto update of time and date".. That made me think the phone lost its internal battery and the phone was bad..
It started doing it right after I configured SETCPU... I installed the program last Thursday but never clicked on it.. I set it for on demand and that is when it started not coming out of sleep..
So I removed SETCPU and it still would not come out of sleep..
So I did a wipe all user data and it started working fine.. I installed SETCPU and it was still working fine.. I setup SETCPU for performance and it started messing up again and not coming out of sleep..
So, I wiped all user data again last night and it has been working perfectly since.. So I do not plan on reinstalling SETCPU...
I've had a SII for a couple of weeks now (new user to android) and I have flashed it to Lightning Rom 1.5. But even before doing this and also afterwards the phone seems to crash/lockup at 5am on about 5-6 occasions.
Is there any program/app I can install to monitor what is kicking in at this time so that I can disable/uninstall it?
Thanks
What do you mean by crash exactly ? Reboot ? Freeze ?
What you could do is plug your phone to your computer before it crashes, and start adb logcat, wait for the crash, and then look at the log to see what caused the crash.
It is completely frozen. I get up at 6:15am and the phone has a blank screen, but I can press a button to activate the screen and the clock is stopped at 5:01am and you cannot do anything else except turn the phone off and back on.
Maybe its the rom? Have you checked its thread? Try flashing bacm to stock. See if problem occurs.
Sent from my GT-I9100 using XDA Premium App
I checked the thread but doesn't appear to be anyone else with same issue. I might try the stock ROM to see if the problem persists. Although I sure it happened once on the firmware that came on the phone (KE2 I think it was).
scheduled backup?
I couldn't find any backups scheduled. So I wiped the phone last night and applied the Lightning 1.5 ROM again and it seems to have been fine this morning..no lockups.
Thanks for the advice.
I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device
OccasionalDroid said:
I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device
Click to expand...
Click to collapse
I'll keep that in mind if it happens again..cheers. Been OK this morning so shall see how it goes.
Its done it a few more times since I did a factory reset, always at 5:01am. After rebooting the phone and checking the battery stats it appears that 'Cell Standby' has used 52% of all battery consumption and the battery drained from 100% to 9% over 8 hours. The problem also occurs even if the phone is on charge over night.
So maybe it is a buggy radio? Gonna take it back to the store tomorrow to be looked at.
Ok odd thing keeps happening. My epic will randomly power off but will not power back on until i do a battery pull. I am currently running 2.2.1 RandomRom 2.2 Final EC05. I dont think it is the rom but who knows. Any Ideas would be great! Thanks Everyone in advance.
Do you use setcpu or anything like that? Some phones dont like to run below 200mhz.
Posted by Mr. Z's Epic 4G via Tapatalk
Nope not running anything. It only does it when the phone is not charging. If its on the charger it stays on. If i pull it off the charger it could turn off 20min to 3 hrs later.
harmhimself said:
Nope not running anything. It only does it when the phone is not charging. If its on the charger it stays on. If i pull it off the charger it could turn off 20min to 3 hrs later.
Click to expand...
Click to collapse
My last one did that, but it was because I dropped it. Have you ruled out a hardware problem?
Posted by Mr. Z's Epic 4G via Tapatalk
Not that i know of. Its never been dropped. I wonder if i should factory reset and start all over. I just dont know what else it could be.
It's most likely that it's a third party app causing the issue.
That said, the best way to exonerate the software is to ODIN to the stock EC05. If it does it with that, it's probably a hardware issue. If it doesn't, it's probably a ROM or kernel issue.
P.S. it's humorous that RandomROM might be causing RandomREBOOTS.
Haha.....yea. I liked it at first but guess its back to finding something new.
Yeah I'm having a similar problem also but only recently like no more then a couple weeks... my phone doesn't shut down completely but it randomly restarts itself and the ODD thing is that when it would power back up it would be in AIRPLANE mode. No matter how many times I tryed to disable airplane mode it just would not turn off! Even after I would shut down my phone and power back up it was still in airplane mode. So I took out the battery for a couple of seconds and put it back in, powered up and every thing works fine again... its only happened about 3 times I'm running that new gingerbread leak so that might be the issue but I've been rnning it for a while now and only recently had this problem with the phone.
I run ACS Frozen 1.2 have the same issues, I've had the same issue since froyo sourced roms have come out.... phone randomly powers off..... only happens maybe once or twice a week. It happened extremely more frequently before I changed back to RFS and turned journaling on. It didn't completely correct the problem, but it helped a lot.
Nothing like waiting for a text back from your GF only to find out that your phone has turned off sometime in the last hour since you sent out a text. I call it "The Samsung **** Block"
this happens to me sometimes, if you have journaling off, something might be corrupted. when the phone tries to access the corrupted data it puts the phone in an infinite loop, you might notice a huge decrease in battery life when you do reboot. A fresh clean install is the best way to fix it.
mrhocuspocus said:
this happens to me sometimes, if you have journaling off, something might be corrupted. when the phone tries to access the corrupted data it puts the phone in an infinite loop, you might notice a huge decrease in battery life when you do reboot. A fresh clean install is the best way to fix it.
Click to expand...
Click to collapse
Thanks. I've noticed this.
Sent from my SPH-D700 using XDA Premium App
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
CapsLockKey said:
Everything was fine until today when I decided to remove the stock recovery reload script, reodined CWM and also flashed the CRT off zip.
Click to expand...
Click to collapse
Was the CRT script based on the EI22 framework?
I got it from the EI22 CRT off thread in the theme section.
Last night I also had an odd reboot. Not like the old random reboots that would happen when the phone was asleep, this one seemed like it was caused by a GPS crash. I had been using an app that triggered the GPS, (weatherbug I think) and when I closed it, the GPS icon stayed on. Even after I turned off GPS it still stayed on. The phone also started getting pretty warm. GPS itself no longer worked. After a few minutes of trying to shut down GPS the phone locked up. A minute later it did a "partial" reboot, playing the startup sound and eventually giving me the launcher screen. It was still not running right, with the GPS icon stuck on and the phone very sluggish. I did a shutdown and restart. The phone took a long time to start up, sitting on the "big S" for a while just like on it's first startup. Makes me think something got corrupted in the cache and it had to rebuild it.
I don't know if this was just a random event or the sign of problems to come.
This was on Stock EI22, installed as an OTA upgrade over a fresh EC05 install. The only mod was the CRT off / Circular battery mod that I created at the UOT kitchen.
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
CapsLockKey said:
Well fortunately my phone hasn't done it since. Thinking back, it may have been somehow triggered from a WiFi issue as I leave my WiFi toggle on most of the time and I had just pulled into my garage so the phone obviously was switching from 3G to WiFi around that time.
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
poit said:
Perhaps clearing data on LauncherPro and rebuilding the setup from scratch will solve that for you.
Click to expand...
Click to collapse
Tried clearing data, reinstalling, etc. Doesn't matter, still FC's immediately after reboot. Problem must be with Launcher Pro not liking something, because I just flashed CleanGB Rom (which includes the CRT-off and several other tweaks) to try it out and it does the same thing on that.
Update: Seem to have solved it, but not sure why. Had Voodoo Plus set to load module on boot, when I turned that off LP did just fine after rebooting. Decided to flip the load on boot back on to see if it would start FCing again and magically enough it hasn't.
I just had a random reboot and im in stock EI22..... Why?
Sent from my SPH-D700 using XDA App
Been on it since it was released, no reboots here... Working great for me.
ive had this off and on for a few days now. i find it to be caused by having multiple launcher in my case spb shell .had it running stock the first day so i flashed a rom and its still there. also other apps that use alot of resources will cause it. it partail reboots about 3 or 4 times and then runs normal.
CapsLockKey said:
I am still having a weird issue though where Launcher Pro force closes initially every time I reboot the phone ever since then.
Click to expand...
Click to collapse
I have the same issue with Zeam Launcher, clearing defaults doesn't seem to help. I wonder if there's some kind of half-assed check to make sure that TWLauncher is running? I dunno, but it's obnoxious considering how many times a day I'm forced to reboot EI22, added to the fact that they got rid of the deathgrip reboot.
My phone has "Randomly" rebooted on me several times, usually in an area with little signal coverage. Each time, it seems like there's some program (like Spotify or DI.FM) running that's making network calls when the signal craps out.
EI22 has been nothing but problems for me.
Just had my first random reboot. I'm stock EI22 not rooted yet. Imanually installed on the first day and this was my first. Phone was off just sittin on the table and the screen come on showing low battery but was still sittin at 30% and it shut off and the samsung screen come up and went thru the boot up process.
Sent from my SPH-D700 using xda premium
Please see this thread if you get random reboots with WIFI on.
http://forum.xda-developers.com/showthread.php?t=1359315
My Stable setting with no random reboots !!!!
After trying out virtually every rom/kernel out there (started with stock) I finally got a configuration in which I hadn't got any random reboot (or any other silly issues). My current setting are :
ROM : ERA Lagendary RC2
Kernel : Samurai 2.0.1 (inbuilt with Rc2)
Theme : Ei22Ics version 2 (just for fun !!!)
I have used Voltage control to OC it with settings : 400 Mhz minimum(recommended somewhere in dev post), 1340 Mhz maximum(~1400 mv voltage which I think maximum my handset can handle) with ONDEMAND governor.
My Epic is running flawlessly with no random eboots of FC's since last 4 days (while it used to reboot atleast 3-4 times daily earlier).
Hope this helps !!!!
Epic Timezzzzzzzzz !!!!!!
I still get random reboots in EI22, but not as many as I did on the GB leaks. I can cause a reboot by scrolling to fast in Settings, Applications, Manage Applications, All. I have had the phone run for 90 hours without a random reboot so I'm happy.
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
rando991 said:
Had 2 reboots over the past week, where after charging all night I pulled the usb charger cable out and it rebooted. Stock EI22 except rooted, keyboard/CWM flash, and GPS_fix.
Click to expand...
Click to collapse
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
i dont get any with
ROM = ASC AICS 5.5
Kernel : Samurai 2.0.6
Theme = Shake & Bake Mix Up v.5.9
kennyglass123 said:
Sounds like your USB port or charger cord is going bad. That is not random. If connections are shorted momentarily it will cause a reboot. Happened once to me on my cheap car charger.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Well I did notice it only happened on that particular charger (from Walmart)...also, my wife's epic didn't reboot, but had the charging light stuck on all day. I had to power it off and remove the battery to end it. Would that be maybe the same problem?
Been on CleanGB for quite a while. Went out of town this weekend to Chicago and ended up being rebootpalooza on my phone. Probably had almost half a dozen, once it just shut down in the middle of a phone call at the train station after the low battery notice came up, even though after I powered it back on it still had 28%. Another reboot was I unplugged the car charger shortly after the "full" indicator light came on. Others were just amazingly random. I've loved my Epic up until this trip when it turned into the most unreliable thing I've had.