Related
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.
Ok I've had the Moto Z for a while and its a great phone. Or it was until a few weeks ago. In the space of a couple of weeks a few official updates were sent to my phone and thinking nothing of it I updated as requested. The last update has seriously messed the phone up.
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
What I've tried to do about it:-
- I've tried running in safe mode, which makes no difference
- I've tried a full reset, which makes no difference
- I even unlocked the bootloader and installed a custom OS (Lineage). Thinking that obviously this will wipe out the new update from Lenovo and the phone would have to work properly again. But no, nothing changes, somehow Lenovo have done something beneath the OS that's causing these problems.
The question:-
Does anyone have any idea what could be causing this or have you at least seen these issues before?
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
apocalypse_bg said:
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
Click to expand...
Click to collapse
The point of my post is obvious, I've got a issue with my phone and want to know if anyone has seen this issue with the Moto Z before and if they have any idea what may fix it. The question is right there near the end:
"Does anyone have any idea what could be causing this or have you at least seen these issues before?"
Click to expand...
Click to collapse
apocalypse_bg said:
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
Click to expand...
Click to collapse
I've tried a different ROM:
- I even unlocked the bootloader and installed a custom OS (Lineage).
Click to expand...
Click to collapse
Honestly don't know how my post was unclear at all, but I've gone and tried to make it even more clear with a quick edit, hope that helps.
I have exactly the same problem. For me it occurred after updating to nougat. So fare I tried nearly everything. Disabling nearly everything to the bare minimum, custom ROMs, resetting, trying to flash only parts of the Android 6 firmware (modem, Bluetooth, DSP) since a complete downgrade is not possible, using all kinds of battery tools with a rooted device, using custom kernels... I always ended up with a constant battery drain of 3 to 8 percent per hour no matter what I did. Same in flight modus. Since under Android 6 the device didn't show this behavior I think that the problem must be somewhere in the firmware beneath the OS level. An the cruel thing is that sometimes without a reason for maybe an hour or two my moto z doesn't drain an works fine so that I do not believe in a hardware problem.
Thanks for the post. Yeah it seems like something has been changed underneath the OS. I know that sometimes memory config gets changed with newer Android operating systems (at least I think so?), but could that cause all these problems?
BTW, do you have all three of the problems I mentioned? Battery drain, sound stops working and charging stops working?
Since in this condition the Moto z is not really usable for me I switched back to my old phone and I am not using it that much as a daily device, I cannot really tell about sound or charging problems. So far I did not notice those problems.
DonnieDio said:
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
Click to expand...
Click to collapse
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
DonnieDio said:
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
Click to expand...
Click to collapse
None of the above ever happended to me
StarStorm said:
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
None of the above ever happended to me
Click to expand...
Click to collapse
I've never seen anything like it before. Its so random as well. I mean yesterday I rebooted and then charged the phone before I left for Football at 4pm. At about 11pm that night I heard the battery low sound (45% of the battery had be used by Android OS..). First thing I thought of was that usually the phone wouldn't still be making sounds by now. Since as I said earlier usually the speaker stops working along with charging within a hour or so of a reboot and this had been over 7 hours without a reboot. So I tried plugging it in and it started to charge. But then when I woke up this morning again the sound was disabled and it won't charge, it just took longer for the problem to occur this time..
How can we stop asking to update to this patch?
I has already disabled this on the developer preferences but still asking every 10 minutes
Any suggest please
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
doug107hk said:
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
Click to expand...
Click to collapse
Yep I've also had that as part of my problem, though it had only happened a few times over the course of the month so I forgot about it with all the other problems I mentioned going on.
Basically my phone would be sitting on, say 40%, and after a reboot it would start up in the single digits.
I recently tried changing to a custom kernel to see if maybe that was causing the problem (I'd already tried changing OS). But all the problems are still there using the new kernel. Think my next step should be to try to go back to a 7.0 Android version. Are there any custom Android ROMs using 7.0?
It is said that the Motorola Manager can rescuer lost data even if the data has been covered on phone , is it true ?
Just curious what came of this. My Z, unrooted, has started running crazy hot and the battery life is not good. 6-10 hours. When I connect it to my Anker PowerDrive 2 in the car, the battery actually discharges faster or I get the slow charge warning.
Hi I have exactly the same problems as the op and tried resetting to no avail.Its driving me nuts.
Short update about the massive battery drain problem: like I wrote above, in the past weeks I tried everything from custom kernels to custom roms, resetting, deleting and so on. Nothing helped. So I went back to stock and didn't use the phone the last weeks. Today I read in an other thread about bluetooth problems that a fix for the not working bluetooth was to activate flight mode, restart the phone and deactivate flight mode. So I activated flight mode, pressed the power button for 10 seconds or so until the phone restarted an deactivated flight mode. And now the absolute strangest thing happened: for the last 5 hours the phone lost 0% battery in standby with wifi and lte on. Since I did all the mentioned things above without any effect I do not understand this at all but right now I think that this could be a (temporally) fix also for the battery drain problem.
I've noticed a couple times now that my watch is randomly rebooting or hanging since the upgrade to AW2. I did a factory reset, which improved things a bit (no hanging), but I still get the occasional RR. It appears to be related to charging, as it generally happens when I plug it in at night.
It's not a killer, but I'm wondering if it is just my watch, or if others have noticed it.
jshamlet said:
I've noticed a couple times now that my watch is randomly rebooting or hanging since the upgrade to AW2. I did a factory reset, which improved things a bit (no hanging), but I still get the occasional RR. It appears to be related to charging, as it generally happens when I plug it in at night.
It's not a killer, but I'm wondering if it is just my watch, or if others have noticed it.
Click to expand...
Click to collapse
So far I have not seen either of these issues. However I did an immediate factory reset upon installing the 2.0 update. But only 50 hrs since install of 2.0 so will continue to monitor.
I've had AW 2 for 6 days and no random reboots in that time.
Well this is fun. I guess I need to blow it away and refresh it, maybe clean the contacts. I have had to restart nearly every day this week since the update.
Still no random reboots here.
jshamlet said:
I've noticed a couple times now that my watch is randomly rebooting or hanging since the upgrade to AW2. I did a factory reset, which improved things a bit (no hanging), but I still get the occasional RR. It appears to be related to charging, as it generally happens when I plug it in at night.
It's not a killer, but I'm wondering if it is just my watch, or if others have noticed it.
Click to expand...
Click to collapse
I've been getting these as well. Just out of curiosity, does your watch reboot into recovery, and then reboot back into AW after a shirt time period?
Electronicbrain said:
I've been getting these as well. Just out of curiosity, does your watch reboot into recovery, and then reboot back into AW after a shirt time period?
Click to expand...
Click to collapse
No, when it happens it reboots into AW immediately. In effect, it goes black, then shows the ASUS animation like it got restarted. I did clean the pins and I haven't seen it since, though. It may be that AW2 doesn't care for the intermittent power when you first attach the cable.
My zenwatch 2 has started constantly rebooting until it quickly drains the battery after aw2. It is completely unusable. I have a 2yr warranty through best buy and am likely going to return it if I cannot find a solution.
Have you guys done a factory reset since the update?
It took a factory reset and then calibrating the battery sensor after the upgrade for mine to settle down..
Mine settled down after a factory reset, but it still crashes if the cord is loose (too many power events). It also drains significantly faster than it used to. I have been getting home with 62% instead of the usual 75%. Not terrible, but not great either.
I do like AW2 overall, though.
I have two V60s on A11 and noticed for the past two nights one of them will reboot while charging. Only way I notice is because I have to use my PIN in morning to login in instead of fingerprint and one app indicates a restart. This is a replacement V60 that I have had for two days.
Any thoughts?
Are you sure that it's a reboot? I noticed that if I leave my phone idle for a couple of hours (not sure how many, maybe 4 or more?), some kind of security kicks in requiring that I enter my pattern instead of using the fingerprint reader. Pretty sure this has happened both on Android 10 and Android 11. I don't commonly leave my phone idle for 4+ hours during the day, but it has happened just enough for me to notice it. And it definitely wasn't a case of the phone just randomly rebooting itself on me in the middle of the day. THAT, I would have noticed.
Positive it is a reboot. I actually saw it happen this morning. Phone will just shut off and T-Mobile reboot splash screen comes on. I think it is not related to fingerprint reader bug as I have disabled the fingerprint reader on my lock screen/AOD.
Actually been noticing it happens now even when the phone is not charging. I wish there was a way to see which app is causing the problem or get some kind of log to know what is going on.
Hmmm, other than trying to isolate which app is causing the problem, I'd probably suggest a factory reset.
I actually removed all apps and left with factory defaults and it still rebooted during a charge. I have sent the phone back and awaiting a replacement. (This one was the 2nd year promise replacement for a dying G8)
I had to ship the phone back and get a replacement. Everything I tried did not work to stop reboot while charging.
My LG started to freeze, then reboot several times a day, while in use as well as overnight. Sometimes boot loops directly after the logo, so not OS or app related, also without SIM or SD. I had the battery changed (still in warranty), but that behavior continued. So I got a replacement phone yesterday, since it was obviously a hardware issue (I guess it is a RAM failure).