Random Hot Boots - Galaxy S III Q&A, (US Carriers)

At random times, my ATT SGSIII will do a hot boot (looks like the phone resets itself quickly. Not full reboot.) I don't know why it's doing this, but it's done it on the stock ROM and on Ultimatum ROM. The only thing I can think that has caused this was rooting it, but I haven't seen anyone else mention anything about it so I'm worried I screwed something up.
I attached a picture of my battery stats graph that shows the skips/jumps each time this happens. It also throws off the "time on battery" by a large margin.
Any ideas?
Thanks

Just to concur that this happened to me today, after I messed around with Bluetooth stuff (turn it on and off).

I'm still stock, unrooted and it happened to me twice in the last day. 1st time I just finished using a flashlight app and the phone froze and then rebooted. 2nd time it had been in my pocket for about 5 minutes. Both times - 2 vibrations, reboot, startup sound and graphics.

Related

[Q] Checking for problems due to overheating

So first a little background. I woke up in the middle of the night with an EXTREMELY hot phone. Somehow it had gotten under my pillow while it was charging (I have no idea how this happened but it did). The phone had a battery symbol with a temp sign, obviously way overheated. Well I quickly pulled the phone from the charger and the battery out of the phone to cool it down. After a few minutes when it had cooled down, I tried to boot it back up. At first everything looked good, TW bootscreen came up, but then nothing else happened. The phone would act like it had fully booted (captive buttons would light up then screen would time out and go black) but the boot screen animation would still be going if I pressed the power button to light the screen back up.
At that point I thought it was all over. I put in my spare battery and got the same results. So I went into recovery and wiped to see if the phone could read from the memory. I didnt have any problems with the wipe or reflashing (running next-gen TW). The phone booted up just fine. I haven't seemed to have any problems since.
So I guess my question is do you think I am in the clear? I ran quadrant to stress the phone to see if anything happened and I am still seeing the same scores. I thought I might have problems with data but it seems to be running ok now.
Is there more stress tests I should run to make sure everything is ok? I have always been cautious with my electronics so I havent run into overheating them before so I am not sure what to look for in this area.
Thanks guys/gals you all are awesome, love the community Usually I don't post/create new threads because search is my friend and I dont like to crowd threads with my stupid answers lol. Thanks again all!
PSS sorry for the long post and confusing explination let me know if I need to re-explain anything. and sorry if this is the wrong section just let me know and/or move to correct location.
My phone got stuck in the boot animation with Trigger v3.2 once. It had nothing to do with overheating.
I remember just doing a reboot and it got stuck in the animation. The screen timed out as if it had booted normally. I rebooted again and it was fine, never had that problem since. It has only happened to me with Trigger v3.2, which is based on KB5 (I think Bionix NextGen is also based on KB5).
So it's probably a software related bug and not related to heat damage or anything.
That's what I am hoping, guess the only way to really know is see if I start having problems over the next few weeks. Thanks for the replay

SGS2 not waking after locking screen

so heres the story:
when i lock the phone, the screen turns off as normal. but when i hit the power/home button to wake it and unlock it, nothing happens. literally, nothing happens. its as if the phone has turned itself off.
So whats happened is, I left the phone on the charger last night. it woke perfectly this morning when the alarm went off. no issues there.
I put the phone into my pocket and headed into work. i went to check my phone when i got on the bus and this was the first tme that I noticed that the phone wasnt waking. i eventually pulled the battery to get the phone to restart. i tried it again and the same thing happened.
later I made a phone call. the same thing happened again when i took the phone away from my head (the screen didnt restart, and I couldnt hit the End Call button cause there was none.)
since then, i've figured that to make sure the phone doesnt go to permanent sleep i have to do one of 2 things,
1) keep the phone music player running constantly, or
2) keep the phone connected to the usb charger.
clearly this isnt exactly practical for a mobile.
im not running any other Rom, its still the stock rom, android v 2.3.5, not rooted or anything else?
is this somethign anyone else has seen?
its called 'sleep of death' or SoD. some people has experienced this and some are able to fix it. it depends on what is causing it.
some blame it to the battery and the battery's contact point..
sometimes it fix itself after few reboots..
cheers for the info. Ill look into it and see if its worth trying to fix or just sending back.
no problem, i have this problem and cant do anything about it. i used load monitor to keep the phone awake, u/v a bit so it wont drain so much battery. but battery drainage still noticeable like 1% every 5 min..
just wondering, does it feels hot/warm near the camera lens when it happens? bcause mine does.
not particularly.
i finally got through to my provider and will be able to get it fixed/replaced soon. they just dont half drag their feet

[Q] Crashing Phone and Faint Green LED light.

Right, I've had the x10 mini for almost a year now, and I've had the miniCm 7 (and I have the nAa kernel 2.6.29.6-nAa-08)for almost all that time, and there's never been any trouble whatsoever. But yesterday, something happend. I woke up, and tried to use my phone. It had charged during the night, and had a 100 percent, so I sent som texts, and everthing was fine. But when I tried to surf on the internet, the screen went black. Odd, I thought, and i tried to press some button the light it up again. It didn't work, so I pressed the boot buttun (the one on the top) and a faint green light flashed twice, and after maybe 10 seconds, the phone booted up. Odd, i thought, and after the booting was completed, I tried using the phone, and the same thing happend again. I realised it was something wrong, as i now had 20 percent battery. I let i drain, recharged to hundred, and wiped battery stats. I booted the phone once again, but this time, I could literally SEE the battery go down, it took like six seconds! I kept my calms, and I did this
http://forum.xda-developers.com/showthread.php?t=1078100. still didn't do it.
I thought, that this might have been caused by a faulty battery, but the battery have worked fine, just until now and i've had computers and other phones where the battery have died, and in those cases i've seen a detoriation in the quality over a period of time, but this happend over night.
I've also tried to "reinstall" cm7. Didn't work
What do you think I should do, the garranty is void, and I don't have much money, so is it possible to do something without contacting Sony?

[Q] GT-I9300: Purple/pink screen flickering/freeze (not SDS) and strange behavior

Hello,
I have an international unlocked Samsung Galaxy S III (GT-I9300) that is no longer in warranty and that started behaving strangely (unresponsive) a couple of weeks ago on Android 4.1.2 (official ROM, rooted with CF-AutoRoot).
After reading several threads here on XDA I believed it was subject of Sudden Death. So I started with a factory reset and rooted the phone again with CF-AutoRoot but after that I still experienced the same freezes and started my mission to try and resolve this using whatever method was required.
I starting with trying the DFG app but to no avail. The freezing was provoked but did not go away after many days of iterations and freezes (it always recovered out of a freeze).
Next I tried the eMMC check app to verify on what version I was so that I could help my in further pinpointing the problem. It said I was safe, but while running that app the phone freezed again but this time the screen turned purple/pink and it did not recover from the freeze after several hours until I finally removed the battery. The purple/pink turned into purple/pink with black lines and after removing the battery I could not power on the phone.
In all desperation I started trying out different "SDS-safe" custom kernels, ROMs and bootloaders (all flashed using Odin on my laptop) but the problem did not go away. In fact, I discovered a very strange correlation between the time that I leave the battery out the phone and the time it takes before the purple/pink freeze occurs again.
If I wait half an hour, put the battery back in the phone and boot it (in whichever mode) it would freeze/flicker/die after about 20 seconds. If I would wait several hours, put the battery back in the phone and boot it it would freeze/flicker/die after a solid 1 or 2 minutes.
Whether the phone is connected to the laptop or not makes no difference. I also tried with a different battery but the same behavior occurs.
After waiting a solid day, in still in act of desperation, I decided to flash the leaked 4.2.2 (I9300XXUFME7) official ROM. But even after a factory reset and wiping of cache I found that the problem still remained.
Now I believe I've tried almost everything I've found on these forums I'm not sure what I can still do. It seems it's not battery, ROM, kernel or bootloader related and it also does not seem a case of Sudden Death (I never heard mention of the purple/pink flickering, and it also never snaps out of the freeze; also the strange correlation between battery out of the phone and time before it freezes is something I haven't read about).
From all the research I've done I've not encountered anyone with the same symptoms (does not wake out of freeze, purple/pink lines appear on screen when freeze starts and keep flickering for hours, there seems to be a correlation between the time the battery is out of the phone and how long I have before it freezes again when I turn it on) and I'm running out of ideas.
I believe it is hardware related (but not a screen issue) rather than software related because the USB connection with the laptop disconnects when it freezes, purple/pink flickering and no recovery; but I have no idea what options I still have.
Before I give up on the phone does anyone have any recommendations of what I can try before sending it to a Samsung repair center?
Attached are 4 pictures to show the typical process after waiting ~4 hours and powering on the phone:
Phone boots OK
The phone freezes and a purple/pink overlay appears
More and more flickering making the screen turn more and more purple/pink
The screen seems to be divided in 4-5 parts
Everything is pink and black lines start to appear
Thank you for your time.
I'd say you need a new motherboard or screen, possibly both - you've ruled out any software causes.
just had this issue
Did you find a solution, given the fact that this happened a long time ago?
I was watching a video and my screen turned pink like the 4th photo you posted.
Now it wont work, get the pink screen everytime is turned on.
dendera said:
Hello,
I have an international unlocked Samsung Galaxy S III (GT-I9300) that is no longer in warranty and that started behaving strangely (unresponsive) a couple of weeks ago on Android 4.1.2 (official ROM, rooted with CF-AutoRoot).
After reading several threads here on XDA I believed it was subject of Sudden Death. So I started with a factory reset and rooted the phone again with CF-AutoRoot but after that I still experienced the same freezes and started my mission to try and resolve this using whatever method was required.
I starting with trying the DFG app but to no avail. The freezing was provoked but did not go away after many days of iterations and freezes (it always recovered out of a freeze).
Next I tried the eMMC check app to verify on what version I was so that I could help my in further pinpointing the problem. It said I was safe, but while running that app the phone freezed again but this time the screen turned purple/pink and it did not recover from the freeze after several hours until I finally removed the battery. The purple/pink turned into purple/pink with black lines and after removing the battery I could not power on the phone.
In all desperation I started trying out different "SDS-safe" custom kernels, ROMs and bootloaders (all flashed using Odin on my laptop) but the problem did not go away. In fact, I discovered a very strange correlation between the time that I leave the battery out the phone and the time it takes before the purple/pink freeze occurs again.
If I wait half an hour, put the battery back in the phone and boot it (in whichever mode) it would freeze/flicker/die after about 20 seconds. If I would wait several hours, put the battery back in the phone and boot it it would freeze/flicker/die after a solid 1 or 2 minutes.
Whether the phone is connected to the laptop or not makes no difference. I also tried with a different battery but the same behavior occurs.
After waiting a solid day, in still in act of desperation, I decided to flash the leaked 4.2.2 (I9300XXUFME7) official ROM. But even after a factory reset and wiping of cache I found that the problem still remained.
Now I believe I've tried almost everything I've found on these forums I'm not sure what I can still do. It seems it's not battery, ROM, kernel or bootloader related and it also does not seem a case of Sudden Death (I never heard mention of the purple/pink flickering, and it also never snaps out of the freeze; also the strange correlation between battery out of the phone and time before it freezes is something I haven't read about).
From all the research I've done I've not encountered anyone with the same symptoms (does not wake out of freeze, purple/pink lines appear on screen when freeze starts and keep flickering for hours, there seems to be a correlation between the time the battery is out of the phone and how long I have before it freezes again when I turn it on) and I'm running out of ideas.
I believe it is hardware related (but not a screen issue) rather than software related because the USB connection with the laptop disconnects when it freezes, purple/pink flickering and no recovery; but I have no idea what options I still have.
Before I give up on the phone does anyone have any recommendations of what I can try before sending it to a Samsung repair center?
Attached are 4 pictures to show the typical process after waiting ~4 hours and powering on the phone:
Phone boots OK
The phone freezes and a purple/pink overlay appears
More and more flickering making the screen turn more and more purple/pink
The screen seems to be divided in 4-5 parts
Everything is pink and black lines start to appear
Thank you for your time.
Click to expand...
Click to collapse

[Q] Phone won't turn on

Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.

Categories

Resources