This problem seems to be getting progressively worse.
Basically what will happen is that the phone will either lock up completely or shut off unexpectedly. Upon reboot, the phone will either show that the battery is now at 0% or 3% or whatever and/or it won't be able to "see" any T-Mobile towers. If I pull the battery and reboot, the battery indicator will show the true charge % for a while, up until the next lockup or shut off.
Sometimes it'll last for hours and sometimes it'll shut off shortly after I turn it on. The only real common thing is that I'm usually actively accessing the internet in some fashion, like using Facebook or Zillow. Syncing and other background access doesn't seem to affect it, since this only seems to happen when I'm actually looking at the phone.
The IMEI matches the back sticker, and this problem has followed me across a few different roms, even after ODIN flashing a stock rom, rerooting, etc.
Any ideas? Right now I'm using my old TM506 because I don't trust my vibrant and need a working, reliable phone.
I can't be certain but it could be a bad battery, I have a few and one of them started giving me problems similar to this.
Vibrant 360° Productions
PAC, PA & BAKED (hopefully soon)
Related
Ive been lurking around this site since the shadow was the new thing on the block, and ive never had a problem i couldnt figure out by just searching the forums... well, now i do...lol
I have a 17 day old g2, completely undamaged, unscratched. for some reason, intermittently, and with no apparent cause, it will shut off completely. it does not go through the shut down process, give any warning, or restart on its own, it just turns off like you pulled the battery out. (ive checked batt. voltage and amperage with a multimeter and ensured that the battery isnt loose in any way. also, it will shut off exactly the same way while charging which leads me to believe that it cant be a power problem.)
Also, though im not sure its related, sometimes the touch sensitivity in the screen will shut off (not the screen itself, still displays beautifully). Only way to restore touch functionality is to restart device manually.
Ive tried a master reset, and called T-Mobile tech support (which was useless).
Hopefully someone will have some idea whats going on here because i sure dont
Where did you get the device from, T-Mobile?
Have you flashed a new Recovery to the phone or hacked it in any other way?
G2 Randomly shuts down
I've only had mine for a week and its doing the same thing...no hacks, tampering etc.
Have you got the OTA update ? If not then you should find it online and update your phone. HTC has fixed the issue of random reboots for the phone
After flashing PAC rom (http://forum.xda-developers.com/showthread.php?t=1957299) I've started experiencing some problems on my phone.
At seemingly random times when I am using the phone the screen flickers a bit then goes black and dies. When I try to power it up again it shows the battery as having something like 1% left and the phone usually dies again pretty fast. It doesn't matter if I had a freshly charged phone or 50% left when this happens, it still most often shows as having 1% left after it dies and restarts. I have never experienced this kind of problem before.
Sometimes the battery shows up as a bit higher than 1% left but still a lot lower than it was before. Earlier today it came on again with 12% left. When this happens I am usually unable to unlock the SIM-card with my pin even though I am 100% sure i input the correct code - it just refuses to accept it and i have to let the phone "rest" or charge it or just pray to the old gods for a few minutes to get it to start again.
I've used a few custom roms and I haven't done anything strange lately with it (except flashing). I flashed the rom with CWM, I followed the instructions and it went through problem free, and I was able to use the rom and phone for a day before this problem showed.
So... Does anyone have any idea what the problem might be? Battery related? Hardware related? Software related? I just hope my phone will survive this so I don't have to buy a new one yet since I've grown fond of this one. I appreciate any and all help!
Try different battery with your phone to rule out battery related problem. try changing kernel...
Sent from my GT-I9100 using Tapatalk 2
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
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.
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
--yep mine too. I'm thinking it has to do with the heaying problem. Mine crashes and dies when there are many apps running/ wifi on with downloads while watching youtube., etc. another is when I recprd videos at 4k pr 720p for about 8-10 mins. My phone heats up real hard. I'll try resetting it and hopefully this fixes it. ps. Haven't done anything to my z5c yet. no unlocked bootloader, no root.,etc.
Same problem
I had the same problem
Device have charge (50,60,70 or more), show 0% and turn off.
Hardware problem maybe ???
any solution found?
hi,
I know it's been a long time you posted this but I'm currently facing that exact same problem.
Could you find any solution in the end?
Thanks
ManiacalShen said:
My phone has developed a strange problem in the last week or so. Basically, it crashes randomly. Turns completely off, and when I try to turn it on again, it assures me the battery is dead by flashing the empty battery symbol. The problem is, the battery is not dead at all. This has happened at charge levels of ~30% up to almost 60%.
When I plug the phone into a charger, it suddenly shows that it's back at the original 57% or whatever and charges, turns on, and operates normally. It's like plugging it in "reminds" it that everything's okay.
Slightly before this, it also developed a problem where all my widgets often disappear after any dead battery shutdown, but this doesn't happen every time.
It's a factory unlocked E5823 on AT&T, currently on Android version 7.1.1. Some Googling around revealed people having a lot of problems with it in July, but I don't even remember when I got that update. It was definitely a while before this issue started, and other people's issues don't sound like mine. The change that most closely coincides with the onset of this problem is me installing Animal Crossing Pocket Camp. I'm not sure how that would mess with the basic operation of my phone, however.
Thoughts? If the battery was just dying, it would actually drain charge, not falsely crash the phone while really full of juice, I thought, but am I wrong? I haven't felt the need to root this phone, but I'm not at all opposed, either, if it'll help. Should I root it and reset batterystats, see if that helps?
Click to expand...
Click to collapse
It looks like your battery is just dying. This was a common issue with Nexus 6p and other phones.
Resetting batterystats won't help... it doesen't have anything to do with it