Related
For the past few days I seemed to be getting a lot of random force close errors on my legend, with no discernible pattern. This continued up to the point where all of a sudden pretty much every app crashed and wouldnt remain open more than a few seconds. I then tried to reboot, and since then the phone just gets stuck in a bootloop at the rom loading screen. I've tried four or five different roms, all with the same error.
I would assume this was a memory/processor malfunction, however the fact that I can still flash roms and make backups with clockwordmod suggests to me the hardware could be ok? Does anybody know of some sort of diagnostic rom I could run to check this?
Thanks guys
Matt
Here's some stuffs to check out, don't over clock, Max 600mhz, not every phone can be oc'd, maybe even try less processor speed say 480 MHz. Have u been ocing your phone on extream speed for long time, like 806+ mhz, that will kill a processor for sure.
Have you done a fix permissions with clockwork mod? This can help heaps with fc's.
If using an ext partition which type are you using 2 3 or 4, apparantly if your using ext4 and your phone is crashing it can cause even more issues.
Using lots if widgets on your screens?
Have you tried a different/new SD card?
My understanding is your rom space can eventually fail if your flashing lots n lots of roms, but you said you can flash successfully, so that sounds good.
There is a few to start you off.
Sent from my Legend using XDA
Amazingly I have managed to completely fix the problem. In a last moment of desperation before buying a new phone I decided to try wiping the battery stats, simply because I had never tried it before (didnt see the need to). Miraculously this did the trick, and I managed to boot into cyanogen 6!
I then restored a backup I made when the phone first died, and confirmed it was still broken as I expected. I then wiped the battery stats , and viola it worked!
I have no idea what is stored in the battery stats, but I am very surprised this made a difference. Thanks for your help anyway ranger.
Latest Thread Update :
16/04/2013 ---- Added Rob's DFG trick Method for new comers to save searching for it .
04/03/2013 ---- Added XXEMB1 as Most reliable freeze free build .
01/03/2013 ---- added advice on kernels with SDS Fix .
26/02/2013 ---- Added links to LagFix (fstrim) premium ,and DFG.
Now that the Galaxy S3 Sudden Death Syndrome has supposedly been fixed by the Update 7 by Samsung patched for Kernel and Recovery ,
There is some poping up posts about the Galaxy S3 freezing with lockups,Lockscreen not responding that requires pulling out battery
and ending up with unsual rebooting and bootlooping which is a very awkward and annoying issue, especially the Q&A section which contains
a lot of angry S3 users reporting this problem ; Ex
Galaxy S 3 keeps freezing every 5 mins (50+ freezes a day)
Galaxy S3 keeps freezing
Well i decided to make this thread in the benefit of spotting the problem and to make sure we have accurate causes and eventually elaborate a solution to this disturbing problem.
Share your experiences down by posting the ROM, the Kernel, the Recovery and the Bootloader that you are on right now, so we can filter the answers and relate them with the freezing problems on The Galaxy S3.
Reported Issue Reasons :
1) - Facebook app for Android.
2) - Google Chrome Browser.
3) - Some Samsung Based Android 4.1.2 builds/Roms causing freezing.
4) - In Some cases, Media Scanner causing lockups.
5) - In Some cases, Swiftkey Flow Bêta causing freezing.
Possible Direct Reason :
Originally Posted by : Rob2222
The freezes are caused by the sudden death fix. On that kind of freezes the phone unfreeze itself after 5-25 minutes.
The phone freezes when writing data to an affected eMMC block.
An eMMC block is affected, when it's internal block pararameters (as f.e. write count for that block) are in such a state, that these parameters trigger a corrupted block without SD-fix (4.1.1) or trigger a freeze with SD-fix (4.1.2).
When a phone is hitting an affected block with a writiing operation is completely unpredictable.
So these freezes can occur on almost each situation on the smartphone when it writes data.
But you have indeed a higher chance to trigger a freeze when writing much data.
Click to expand...
Click to collapse
Possible Current Solution :
I. If the phone freezes, wait until it unfreezes itself. I think this is the important part.
II. The DFG "Dummy File Generator" is only used to trigger the freezes.
III. I think you could also just wait for the freezes to be triggered by all-day-use, but this would be very impractical to wait 20 minutes to
unfreeze when you need the phone.
IV. So we write dummy data with DFG to provoke the freezes.
Highly Recommended Advice :
The write access to an affected block without Sudden Death fix seems to damage the data on this block which _can_ lead to a sudden death.
Because of that I would recommend to stay with KERNELS that have the Sudden death fix included, even if it could cause freezes.
Reported Most Stable " Freeze Free " Build/Rom :
XXEMB1 and all Custom Roms based on this build.
Dummy File Generator :
Alternate Working Solution :
LagFix (fstrim) Premium
Rob's Dummy File Generator Method to solve persistant freezes on the Galaxy S3 :
Rob's DFG Method , Please take a moment to thank him for his contribution to solving this problem.
Let me repeat it again:
Whoever has problems with freezes, please try this at least and give positive or negative feedback here. We have good experience with this method to sightly reduce and/or completely eleminate the freezes.
No, this means that the problems occur when writing the eMMC, not reading.
Try to wait for the phone to unfreeze (5-25 minutes) it seems that it helps and the freezes get less.
If you have that kind of freezes, that are caused by the SD-Fix your phone will unfreeze after that time without reboot.
To provoke the freezes you can also empty your internal storage as much as possible and then use the dummy file generator (generate all) to fill the internal memory 1-2 times.
After each run you can simply delete the dummy files with the delete button.
https://play.google.com/store/apps/d...nomunomu.dummy
Free up 8GB or more to have enough free space on internal memory.
If you have 8 GB free internal space, write 2 times dummy files. 2x8GB are 16GB. The internal wear leveling algorithm spreads these writes over the whole 16GB physical chip area.
There is a good chance that writing EACH sector on the eMMC resets/averages out the internal block data (f.e. write counters) that trigger the Bug and the Fix (Freeze).
If the phone freezes while writing the dummy data (it propably will), just let the phone do what it wants. It will continue to work after 2-25 minutes for each freeze.
This unfreeze after 5-25 minutes seems to have a positive effect.
You can have more than one freeze while doing this. Just let the phone do what it wants. If the dummy file generator crashs cause of a freeze, just restart the App.
When your finally able to write a amount of 16GB data (2x8GB dummy files) in subsequent runs without freezes you have a good chance that your freezes are gone for now or maybe even forever.
You need to write a minimum amount of 16GB data (or more) with this procedure! If you write less data, you didn't even need to thest this DFG method.
The idea behind it:
The SD-Fix causes freezes when writing eMMC blocks in a specific eMMC block parameter state. There parameters are for example the block write counter. Just some few blocks are affected, but when they get written, the SD-Fix freezes the eMMC. Now it seems to have a positive ("healing") effect to wait for the eMMC to unfreeze itself, which happens after 5-25 minutes. For all day use this is not very practicable. So we write just some dummy data to the eMMC to trigger the freezes when we do have the time to wait for the unfreeze. Thats all.
-- From the forums I monitor I get 80-90% positive feedback that the S3 gets again long-time-stable (usable) with this DFG-method.
I got from 10-15 freezes/day to only 1 single freeze in the last 2 weeks without factory reset.
-- Some people needed to write 60-80GB of data until the phone became stable.
In the hardest case (only 1 case) I know, someone wrote about 1TB (1000GB) of data and then the phone became finally stable. He didn't got warranty so DFG was his last resort and after that it finally got stable.
In most cases 20-60GB written data should be enough to get back the phone on a stable state.
If youre familiar with odin, you can also flash XXEMB5 or newer firmware, cause it seems this includes a new, better SD-Fix that doesn't casue freezes anymore. DFG is not needed in this case.
PIT File :
nhariamine said:
Now that the Galaxy S3 Sudden Death Syndrome has supposedly been fixed by the latest update 7 by Samsung patch for Kernel and
Recovery ,There is some poping up posts about the Galaxy S3 freezing and ending up with unsual rebooting and bootlooping which is a
very awkward and weird and annoying issue, especially the Q&A section which contains a lot of angry S3 users reporting this problem.
Click to expand...
Click to collapse
It's a shame that this post has been mostly ignored in favour of the "SDS" one, but I do actually believe both issues are related. My I9300 is running stock - always has been - and suffered with "proper" SDS last November.
The initial symptoms were that my previously perfectly-behaved phone would would randomly FC apps that didn't before, and some of my photographs and video taken on the phone suddenly became corrupted and unusable.
Finally, one Saturday morning, I woke up to find the phone stuck in a boot loop, going from the "Samsung Galaxy S3" black-and-white boot scree to the first blue sweep of the Samsung logo, then reboot. It would power-off and power-on and I could enter ODIN or recovery modes fine, but it wouldn't boot any further.
I managed to get my photos and stuff off the phone through USB in recovery, and decided to wipe and flash the same stock ROM via ODIN.
This process failed - it couldn't partition the device correctly. None of the flash counters were reading anything so I popped it into my local Vodafone shop where they said it just needed the firmware popping back on and they'd have it ready in an hour.
I went back and they said they hadn't been able to load the software and it would have to go off for repair. *sigh*
It came back about 5 days later with a repair report stating that they'd replaced the "main board" - presumably because of the eMMC lockup bug.
It was only after this that the whole "Sudden Death" news came about and I realised what had happened to my phone. The eMMC check app says that my new controller is the same "faulty" version so I've been waiting with baited breath for "safe" official firmware.
The update system threw XXELL5 my way just before Christmas, and I thought that was that, but a coule of weeks ago the phone started hiccuping again. I knew I'd seen this before and my heart sank.
Last week another update was available, this time XXELLA. Since then, all hell has broken loose on my phone. It is locking up about 5 times a day. Initially, I was rebooting it manually (by holding in the power button). Tuesday morning I was woken by my wife saying "shouldn't you be up by now?" - glanced at my phone and it was frozen on the black-and-white boot logo - no alarm! Arrggh! It's dead!
Powered off, back on again and it booted fine. Hmmm, this isn't quite the same as before then. Having seen the advice about leaving it when it's locked, I've been doing that religiously and, so far, it's always woken up again by itself, but it's definitely indicative of a fault somewhere.
I've tried to check what's happening with adb logcat (I'm not rooted - fully stock - so can't see dmesg) and there is always some sort of I/O error when the freeze happens - often an sqlite database. Then, a couple of days ago, three photos and one video suddenly became corrupted.
I've realised that there are two issues, and only one of them has been "fixed".
The main problem, I believe, is that the flash memory is dying quite rapidly. We all know that flash memory has a limited write life, and wear levelling is supposed to extend that life beyond the typical lifespan of a device (say 5 years for a PC SSD drive?). For some reason, the flash in these devices is wearing out MUCH more rapidly.
The "faulty" eMMC controller obviously had a problem when dealing with faulty flash cells and would get stuck in a permanent loop, bricking the device. As far as I'm aware, the "fix" that has been applied prevents this permanent loop. The system still needs to try and handle disk errors with the flash memory, but it's not a permanent freeze any more and eventually (once it's finished dealing with flash faults - often unable to recover the problem) the system will break out of the freeze and carry on as before.
Sometimes this means that an app has bombed out as it couldn't read it's data correctly, but most people would either have forcibly rebooted their phone, or not notice as that app would just restart next time they used it. Sometimes, however, it means that something more important has crashed due to the disk I/O problem, resulting in the phone needing to spontaneously reboot itself.
What this boils down to is - yes, I believe that there has been a fix applied for the "faulty" eMMC controller getting stuck in a permanent, irretrievable loop. But no, I don't believe the actual original problem has been addressed - namely that the flash memory is dying at an unacceptably fast rate for ... well ... who knows what reason.
I do have a theory on that too. Recently a friend of mine was looking to change his laptop hard drive for an SSD. I investigated for him and decided that the Samsung 830 series would be his best bet, if he could get hold of them. And why not the newer 840 series? Well - that's purely because the "consumer" version of the 840 uses Samsung's latest triple level cell flash memory. Newer, faster, cheaper to manufacture almost certainly but ... more importantly in this case ... less resilient. How does 1000 write cycles grab you? They claim that the wear levelling algorithm in the drives mean that their lifetime is still pretty reasonable, but I'm not convinced in the real world.
Any idea what flash they use in the S3? I have no idea, but I betcha it's something (a) cheap and (b) new(ish).
I'm now at a bit of an impasse with my phone, however. When I returned it for repair last year it was properly frozen. No-one could do anything to fix it, the flash wouldn't format or write firmware - the only recourse was replacing internal hardware (or the entire phone).
This time, however, it works ... sort of. I'm occasionally losing photos I've taken and occasionally finding it's locked up and occasionally having to wait for it to recover. No repair centre has the time to "live with" my phone for half a day, waiting to see what happens with it - and even if they did, they'd blame a rogue app or "something left over from the upgrade" - they'll just factory wipe it, maybe flash the firmware and send it back again "repaired".
It's tempting to "lose" it and pay my insurance excess ... but even then, I won't know when the problem will strike again - but that's the thing ... I'm certain it would be back.
I used to love this phone. Now I can't rely on it. I can't rely on it storing the photos I take with it. I can't rely on it ringing when someone calls. I can't rely on texts getting through to me on time. I can't even rely on it waking me up in the morning.
It's sat next to me now,lying on the desk with the screen all shiny and black. I have no idea if it's fine, or frozen. Is someone calling me right this second? I have no idea. Oh, there we go - pressed the lock buton - it's awake. I shouldn't have to check my phone every ten minutes to see if it's working or not.
*sigh* sorry - rant over.
Suffice to say, that's my take on it. If I thought it would help diagnose something "fixable", I'd root and see what dmesg is doing, but I'm convinced this is hardware and I'm also certain that Samsung aren't going to take the blindest bit of notice.
I'm pretty sure there will be more and more people complaining that their phones are misbehaving over the next few months, but it's vague enough of a problem that the "repair" will be wiping - just long enough to take them over the first year warranty...
QorbeQ said:
It's a shame that this post has been mostly ignored in favour of the "SDS" one, but I do actually believe both issues are related. My I9300 is running stock - always has been - and suffered with "proper" SDS last November.
The initial symptoms were that my previously perfectly-behaved phone would would randomly FC apps that didn't before, and some of my photographs and video taken on the phone suddenly became corrupted and unusable.
Finally, one Saturday morning, I woke up to find the phone stuck in a boot loop, going from the "Samsung Galaxy S3" black-and-white boot scree to the first blue sweep of the Samsung logo, then reboot. It would power-off and power-on and I could enter ODIN or recovery modes fine, but it wouldn't boot any further.
I managed to get my photos and stuff off the phone through USB in recovery, and decided to wipe and flash the same stock ROM via ODIN.
This process failed - it couldn't partition the device correctly. None of the flash counters were reading anything so I popped it into my local Vodafone shop where they said it just needed the firmware popping back on and they'd have it ready in an hour.
I went back and they said they hadn't been able to load the software and it would have to go off for repair. *sigh*
It came back about 5 days later with a repair report stating that they'd replaced the "main board" - presumably because of the eMMC lockup bug.
It was only after this that the whole "Sudden Death" news came about and I realised what had happened to my phone. The eMMC check app says that my new controller is the same "faulty" version so I've been waiting with baited breath for "safe" official firmware.
The update system threw XXELL5 my way just before Christmas, and I thought that was that, but a coule of weeks ago the phone started hiccuping again. I knew I'd seen this before and my heart sank.
Last week another update was available, this time XXELLA. Since then, all hell has broken loose on my phone. It is locking up about 5 times a day. Initially, I was rebooting it manually (by holding in the power button). Tuesday morning I was woken by my wife saying "shouldn't you be up by now?" - glanced at my phone and it was frozen on the black-and-white boot logo - no alarm! Arrggh! It's dead!
Powered off, back on again and it booted fine. Hmmm, this isn't quite the same as before then. Having seen the advice about leaving it when it's locked, I've been doing that religiously and, so far, it's always woken up again by itself, but it's definitely indicative of a fault somewhere.
I've tried to check what's happening with adb logcat (I'm not rooted - fully stock - so can't see dmesg) and there is always some sort of I/O error when the freeze happens - often an sqlite database. Then, a couple of days ago, three photos and one video suddenly became corrupted.
I've realised that there are two issues, and only one of them has been "fixed".
The main problem, I believe, is that the flash memory is dying quite rapidly. We all know that flash memory has a limited write life, and wear levelling is supposed to extend that life beyond the typical lifespan of a device (say 5 years for a PC SSD drive?). For some reason, the flash in these devices is wearing out MUCH more rapidly.
The "faulty" eMMC controller obviously had a problem when dealing with faulty flash cells and would get stuck in a permanent loop, bricking the device. As far as I'm aware, the "fix" that has been applied prevents this permanent loop. The system still needs to try and handle disk errors with the flash memory, but it's not a permanent freeze any more and eventually (once it's finished dealing with flash faults - often unable to recover the problem) the system will break out of the freeze and carry on as before.
Sometimes this means that an app has bombed out as it couldn't read it's data correctly, but most people would either have forcibly rebooted their phone, or not notice as that app would just restart next time they used it. Sometimes, however, it means that something more important has crashed due to the disk I/O problem, resulting in the phone needing to spontaneously reboot itself.
What this boils down to is - yes, I believe that there has been a fix applied for the "faulty" eMMC controller getting stuck in a permanent, irretrievable loop. But no, I don't believe the actual original problem has been addressed - namely that the flash memory is dying at an unacceptably fast rate for ... well ... who knows what reason.
I do have a theory on that too. Recently a friend of mine was looking to change his laptop hard drive for an SSD. I investigated for him and decided that the Samsung 830 series would be his best bet, if he could get hold of them. And why not the newer 840 series? Well - that's purely because the "consumer" version of the 840 uses Samsung's latest triple level cell flash memory. Newer, faster, cheaper to manufacture almost certainly but ... more importantly in this case ... less resilient. How does 1000 write cycles grab you? They claim that the wear levelling algorithm in the drives mean that their lifetime is still pretty reasonable, but I'm not convinced in the real world.
Any idea what flash they use in the S3? I have no idea, but I betcha it's something (a) cheap and (b) new(ish).
I'm now at a bit of an impasse with my phone, however. When I returned it for repair last year it was properly frozen. No-one could do anything to fix it, the flash wouldn't format or write firmware - the only recourse was replacing internal hardware (or the entire phone).
This time, however, it works ... sort of. I'm occasionally losing photos I've taken and occasionally finding it's locked up and occasionally having to wait for it to recover. No repair centre has the time to "live with" my phone for half a day, waiting to see what happens with it - and even if they did, they'd blame a rogue app or "something left over from the upgrade" - they'll just factory wipe it, maybe flash the firmware and send it back again "repaired".
It's tempting to "lose" it and pay my insurance excess ... but even then, I won't know when the problem will strike again - but that's the thing ... I'm certain it would be back.
I used to love this phone. Now I can't rely on it. I can't rely on it storing the photos I take with it. I can't rely on it ringing when someone calls. I can't rely on texts getting through to me on time. I can't even rely on it waking me up in the morning.
It's sat next to me now,lying on the desk with the screen all shiny and black. I have no idea if it's fine, or frozen. Is someone calling me right this second? I have no idea. Oh, there we go - pressed the lock buton - it's awake. I shouldn't have to check my phone every ten minutes to see if it's working or not.
*sigh* sorry - rant over.
Suffice to say, that's my take on it. If I thought it would help diagnose something "fixable", I'd root and see what dmesg is doing, but I'm convinced this is hardware and I'm also certain that Samsung aren't going to take the blindest bit of notice.
I'm pretty sure there will be more and more people complaining that their phones are misbehaving over the next few months, but it's vague enough of a problem that the "repair" will be wiping - just long enough to take them over the first year warranty...
Click to expand...
Click to collapse
I'm really sorry for the issues you've been living with mate, sure thing is that what you said about memory lockups and blocking writing
firmware is totally true except mine doesn't freeze which is strange, mine is the affected model and is shown in eMMC brick bug check ;
-VTU00M
-06/2012
-Yes, Insane Chip.
The poll i made is permanant, but you have to post down Rom and kernel and recovery and bootloader to be more accurate to spot the problem and maybe some DEV can fix it as soon as possible.
Thanks for sharing ur experience with us mate.
I am totally stock jellybean not rooted etc. Was having bad problems with phone freezing and lagging so started uninstalling things to try and fix. I found the problem was chrome, I had chrome, chrome to phone and chrome beta on took them all off now running silky smooth again.
Sent from my GT-I9300T using Tapatalk 2
kiwiflasher said:
I am totally stock jellybean not rooted etc. Was having bad problems with phone freezing and lagging so started uninstalling things to try and fix. I found the problem was chrome, I had chrome, chrome to phone and chrome beta on took them all off now running silky smooth again.
Sent from my GT-I9300T using Tapatalk 2
Click to expand...
Click to collapse
First ever user to report Chrome as one source of the problem, thanks mate, if any other symptoms occur and have anything to do with freezing, let us know ok !
I made a similar thread here:
http://forum.xda-developers.com/showthread.php?t=2127443
TL;DR?
Phone started to freeze too much,every 5-10 mins.
Unrooted went to total stock after a megawipe.
Phone died after 2 days.
GOt 16 GB motherboard replaced with 32 gb.
I dont get it, you have a 2 year warranty. If it happens, and im sure the vast majority wont have any issues, take it for warranty.
Sent from my GT-I9300 using xda app-developers app
---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------
eggman89 said:
I made a similar thread here:
http://forum.xda-developers.com/showthread.php?t=2127443
TL;DR?
Phone started to freeze too much,every 5-10 mins.
Unrooted went to total stock after a megawipe.
Phone died after 2 days.
GOt 16 GB motherboard replaced with 32 gb.
Click to expand...
Click to collapse
This though seems vere interesting. Ive read that a few mention their board got replaced by a 32gb. Which prolly doesnt have the bug. So im guessing samsung is very aware of this bug.
Sent from my GT-I9300 using xda app-developers app
This though seems vere interesting. Ive read that a few mention their board got replaced by a 32gb. Which prolly doesnt have the bug. So im guessing samsung is very aware of this bug.
Click to expand...
Click to collapse
I suppose that freezing problem is occured when a device is severly damaged even when on safe kernel and recovery, as much as i hate to admit it i think freezing S3 is the last symptom before SDS. Let's hope it's not.
nhariamine said:
I suppose that freezing problem is occured when a device is severly damaged even when on safe kernel and recovery, as much as i hate to admit it i think freezing S3 is the last symptom before SDS. Let's hope it's not.
Click to expand...
Click to collapse
I got 16gb Motherboard replaced with 32gb.
So it may not be as bad as it seems :cyclops:
nhariamine said:
I suppose that freezing problem is occured when a device is severly damaged even when on safe kernel and recovery, as much as i hate to admit it i think freezing S3 is the last symptom before SDS. Let's hope it's not.
Click to expand...
Click to collapse
I don't know if this is true in every case (freezing S3 is the last symptom before SDS) since I have 4 or 5 freezes on 2 consecutive days about 2 months ago. After that the phone runs normally, not a single freeze since then. And another thing my SGS is the 32 Gb model which is supposed to be safe from SDS (it has a different version of eMMC)
thank goodness for this thread.
this phone has been killing itself up to 3 times in 10 minutes. i really dont know what the hell is going on with this.
i will try uninstalling chrome and see if it helps..
my phone is bone stock running 4.1.2 with the latest firmware updated just today.
data connection is maybe the problem
Hey guys,
i have these freezes too since i updated to 4.1.2.
but in my case it's only when i have mobile data connection or w-lan connection turned on. If i turn off any data connection, it works the whole day without freezing!
It's for two weeks now and today i decided to install CyanogenMod 10.1 to try if this solves my problem.
I'm about to synchronisize my apps (does it automatically when entering google account and choosing "restoren from my account") and the first freeze occured (W-Lan on). But this time the light of the touch keys is full functional. When i touch the screen, the background light of the touch keys turns on. But power button, volume up/down and the touchscreen are frozen.
What I've done:
- rooted and installed CWM
- Cleared Dalvik cache
- wiped all other cache partition and stuff
- installed CyanogenMod 10.1 nightly build 20130208
- factory reset and so on like described in the manuals for installing CFs
Original data of my phone before installing CyanogenMod:
Galaxy S3
AP: I9300XXELL4
CP: I9300XXELL4
CSC: I9300DBTELL1
Android Version:
4.1.2
Kernel-Version:
3.0.31-566833
[email protected]#1
No Branding.
So it is a bit confusing that this only happens with data connection turned on.
I've also read some threads with analytics of the update code and the SD fix so i am well informed now and think it's because of the eMMC bug where it tries to repair the corrupted sectors and freezes while doing this (cause after ~20 minutes everything is fine like nothing happened).
Has anyone an idea or a solution now besides sending it to the local dealer and change it for warranty reasons?
Thanks,
Dark Smile
Odp: **Ultimate Galaxy S3 Unusual Freezing Thread**
It happened to me once, about 2 weeks ago, just after the release of the new firmware LM2. So I have flashed back with PC Odin to the previous LLA but the problem persisted. The phone was freezing after about 5 minutes of use. Forced reboot was needed.
So then I flashed some older 3 files-low level firmware (can't remember what one) in PC Odin nd then back to LM2 again, and everything is alright since then.
Strange...
Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2
After 2 Freezes it's running stable for the moment... i'll watch it over the weekend and give feedback.
Mine is freezing lots now.
First time it went to o2 repair (UK) they claimed they had fixed it, pretty sure they just did a factory reset (which I had done already 3 times). So when I collected it, it froze within 2 minutes.
I'm tracking this repair publicly at http://myo2repair.wordpress.com so you can check out how this sort of thing pans out.
Problem is it can be intermittent, so you could get a couple of hours without a freeze. So it's gone back to repair and they say no fault found. So a bit stuck now.
It will definitely happen again when it's returned. They say after 3 attempts they will give me a refurb device. Samsung themselves give you a brand new sealed device as a replacement. Recommend going through Samsung if in same predicament.
Yes mine also got replaced by a 32 gb one from samsung india today
Sent from my GT-I9300 using xda app-developers app
good news.
after updating today (and uninstalling google chrome) my SGS3 is no longer freezing itself every few minutes!
will report if it starts doing it again. If you dont see me post, assume all is good now.
freeze after 4.1.2
I've had constant freezes when I upgraded to 4.1.2. I tried many versions. all the same.
I rolled back to 4.1.1 and the phone is freeze free for one week now.
Mine started to behave strangely and then started to freeze constantly. Didn't happen after an upgrade, just started happening out of the blue.
So I wiped it completely and flashed it with the latest wanamlite rom (I was on a rooted stock rom before).
Now it only freezes once every few days (still it NEVER used to freeze before, ever).
I think it might have some connection to the facebook app. I've noticed it only freezes shortly after I have been using the facebook app.
SiggiJarl said:
Mine started to behave strangely and then started to freeze constantly. Didn't happen after an upgrade, just started happening out of the blue.
So I wiped it completely and flashed it with the latest wanamlite rom (I was on a rooted stock rom before).
Now it only freezes once every few days (still it NEVER used to freeze before, ever).
I think it might have some connection to the facebook app. I've noticed it only freezes shortly after I have been using the facebook app.
Click to expand...
Click to collapse
So far, users are reporting Chrome and Facebook as one of the sources of the freezing in Galaxy s3.More to come, Share ur experiences down
After many weeks of hesitation I finally took the plunge, unlocked my bootloader (using DrakenFX's guide) and installed LineageOS. The process went smoothly except for the part where my battery is now hosed.
Basically, regardless of how much charge the battery has, the phone doesn't seem to read the level accurately. It doesn't matter whether the phone is turned off (while showing the battery symbol/charging indicator), in recovery mode, or booted to the OS. It might at one moment read 63%, then 1% the next. The interesting thing is that when I boot the phone to TWRP with a fully charged battery, disable the screen timeout and crank the brightness to 100%, it will take 3 days for the battery to discharge even if TWRP is reporting 1% battery, as if TWRP reads the battery as being full regardless of the level it's reporting.
However, if I boot to the OS with a fully charged battery, the OS will read 63% at first (it's always 63%), then within a few seconds will drop to 1% and the phone will shut down (every time). So far I've tried battery calibration apps, draining the battery in TWRP until it shuts off, then leaving it on the charger for 6+ hours (read somewhere that's supposed to reset the battery counter) and, of course, wiping cache/dalvik cache/system/data/internal storage and re-flashing not only LOS, but several other ROMs/kernels as well. I also tried different chargers/cables/power sources, etc. Still FUBAR.
Can anyone offer any insight as to what I may have done to cause this? Is my only option at this point to re-lock the bootloader, go back to stock and send it in for warranty service? I've been dealing with this for 2 weeks now, and the phone is basically a paperweight unless plugged in. Any suggestions here would be greatly appreciated.
That really sucks. it sounds like the battery is toast. try flashing the stock rom to see what happens? Perhaps a hardware issue was happening before you did that but it didn't show until after you took the plunge. Happened to me with the HTC One m8. Had speaker issues a day or two after I unlocked the BL and I know unlocking the bl didn't cause it, so i was mad.
twilighttony said:
That really sucks. it sounds like the battery is toast. try flashing the stock rom to see what happens? Perhaps a hardware issue was happening before you did that but it didn't show until after you took the plunge. Happened to me with the HTC One m8. Had speaker issues a day or two after I unlocked the BL and I know unlocking the bl didn't cause it, so i was mad.
Click to expand...
Click to collapse
The battery was great right up to the point where I wiped/flashed LOS the first time. I'm wondering if it was caused by a combination of A) the battery not being fully charged during the initial unlock/wipe/flash process (it might actually have been at 63%, but it was plugged in) and B) having wiped cache/dalvik cache/system/data/internal storage before the first install.
Going back to stock is my next step. I've been avoiding it because, for one, I don't think it's gonna fix the problem, and two, even if it does fix the problem I'm back to dealing with ZTE's maddening software, which is what drove me to LOS in the first place. Sigh...
n00bsville0123 said:
The battery was great right up to the point where I wiped/flashed LOS the first time. I'm wondering if it was caused by a combination of A) the battery not being fully charged during the initial unlock/wipe/flash process (it might actually have been at 63%, but it was plugged in) and B) having wiped cache/dalvik cache/system/data/internal storage before the first install.
Going back to stock is my next step. I've been avoiding it because, for one, I don't think it's gonna fix the problem, and two, even if it does fix the problem I'm back to dealing with ZTE's maddening software, which is what drove me to LOS in the first place. Sigh...
Click to expand...
Click to collapse
I personally don't think installing Los caused the problem for the simple fact that battery functions are controlled by the kernel which is Linux based (doesn't seem like it correlates but hear me out) just like the los kernel, and that part wouldn't have changed too much, if at all. I think it is a hardware issue. I have seen weirder coincidences happen when doing things like this.
I'd try clean flashing LOs or RR again (a fresh download) and see if that fixes it? Maybe even a complete format to make sure all traces of the last install are gone.
Something may have gotten corrupt the first time, possibly?
tele_jas said:
I'd try clean flashing LOs or RR again (a fresh download) and see if that fixes it? Maybe even a complete format to make sure all traces of the last install are gone.
Something may have gotten corrupt the first time, possibly?
Click to expand...
Click to collapse
So far I've tried 4 different ROMs and 3 different kernels, and each time I'm wiping cache/dalvik cache/system/storage/internal storage before flashing. I'm actually on RR now. I'm re-locking the bootloader and going back to stock today. I guess we'll see how good ZTE's warranty service is.
I was on oreo
I have backup so data not an issue thankfully.
Was using Nitrogen rom with its stock kernel but rom is not the issue since literally no one else is affected, im positive its my phone. Possibly hardware related.
Short version: As you can tell from the title. My phone is freezing randomly while flashing, or sometimes on booting it just stays at google logo. After freezing for 20 seconds and the phone getting hot, the screen goes off. It does not however bootloop.
It does not power off when the screen goes off in the normal sense either since if i attach a charger nothing shows, no battery icon, but i know it charges because then if i go into bootloader and then twrp back again, battery is increased. but if no charger, the screen stays off and battery is not decreased, like a power off :/ what is wrong?!
Full disclosure: i had my cpu(motherboard) repaired 2 weeks ago when it just dropped dead after freezing and me trying to reboot it, which it never did.(that was aquarius rom)
After repair i flashed nitrogen and all went fine until it happened yesterday too but thankfully i could access bootloader and occasionaly twrp. i somehow (after the 100th time of it finally not freezing in flashing or splash screen) managed to clean flash my rom again and it booted.
All went good for a day then suddenly it froze today and when i hard rebooted it, it never went past the google logo again, and screen turns off, which is where i am now. But now i can access twrp most of the time without it freezing now.
What ive done so far: Since this time it actually opens twrp 90% of the time unlike yesterday and freezes only few times, ive managed to flash a few different rom versions and even tried going back to nougat. ALL leading to -> Google logo 20 seconds, screen off.
I'm in the process of downloading factory images and OTAs, which will take 6 hours since i have a slow connection. but i dont know which i should flash (ill be using Heisenbergs guide). Which is a better option at succeding?
what i think is wrong: probably the flashing takes a toll on the cpu and it just freezes n gets hot n shuts off. NO bootloop. Ive attached logs from ''copy log'' option in twrp, i dont know if that will help.
Can it be a hardware issue? Anything else i can do besides factory images/OTA? Should i look into disabling my big cores?
I'd highly appreciate some technical expertise and advice as to how i should procees from now.
Thank u for taking the time to read it!
Lord. Tech said:
.... Can it be a hardware issue? Anything else i can do besides factory images/OTA? Should i look into disabling my big cores? I'd highly appreciate some technical expertise and advice as to how i should procees from now. Thank u for taking the time to read it!
Click to expand...
Click to collapse
Probably a hardware issue related to the motherboard, but you should treat it as a bootloop and follow the workaround you mentioned. If that solves your issue then you will know it is hardware for sure. I guess you don't have a warranty on the motherboard because you didn't mention that route. If you do get it running on small cores, run Accubattery (if you haven't already) and get an estimate of remaining capacity of the battery. If you do send it back for 2nd repair, replace the battery at the same time. Why not? It's only $20 and there would be no labor.
v12xke said:
Probably a hardware issue related to the motherboard, but you should treat it as a bootloop and follow the workaround you mentioned. If that solves your issue then you will know it is hardware for sure. I guess you don't have a warranty on the motherboard because you didn't mention that route. If you do get it running on small cores, run Accubattery (if you haven't already) and get an estimate of remaining capacity of the battery. If you do send it back for 2nd repair, replace the battery at the same time. Why not? It's only $20 and there would be no labor.
Click to expand...
Click to collapse
Yes im out of warranty sadly. Im going to try flashing stock images, if that doesnt work then will look into turning off my big cores. Any advice on if full OTA images would be better than flashing Factory images?
i agree, i shoulve gotten it replaced the first time i had it fixed, regretted that as soon as i got it back. accubattery showed 60% left, the rest seems degraded.
i really hope something works. I'm starting to get fedup of this device i loved so much n still do surprisingly! i hate that google did this to us, that too out of all the devices on the last and most anticipated 'nexus' of all time! Embarassing end to the series.
Lord. Tech said:
Yes im out of warranty sadly. Im going to try flashing stock images, if that doesnt work then will look into turning off my big cores. Any advice on if full OTA images would be better than flashing Factory images i agree, i shoulve gotten it replaced the first time i had it fixed, regretted that as soon as i got it back. accubattery showed 60% left, the rest seems degraded.
i really hope something works. I'm starting to get fedup of this device i loved so much n still do surprisingly! i hate that google did this to us, that too out of all the devices on the last and most anticipated 'nexus' of all time! Embarassing end to the series.
Click to expand...
Click to collapse
Flash full images because OTA's don't contain the full partition image. Just set up fastboot on your PC and follow Google's instructions on the page you d/l the images from. Due to using several custom ROMs, I would recommend you fastboot format Boot, System and Userdata before flashing, then use Google's flash-all.bat script. Battery: at 60% your battery is beyond toast and may well be contributing to your problem. You need a new battery, period. Good luck. :good:
v12xke said:
Flash full images because OTA's don't contain the full partition image. Just set up fastboot on your PC and follow Google's instructions on the page you d/l the images from. Due to using several custom ROMs, I would recommend you fastboot format Boot, System and Userdata before flashing, then use Google's flash-all.bat script. Battery: at 60% your battery is beyond toast and may well be contributing to your problem. You need a new battery, period. Good luck. :good:
Click to expand...
Click to collapse
Thank u for the how-to advice! i was a little confused with the particulars, Glad u cleared it up for me. The images are still downloading, damn the slow connection, so it'll be while before i know if it works, i'll update with the results soon.
Yes, ur spot on. i barely got 2.5 hours SOT, usually just 1.5 hours! if i can get my phone running again, im ordering a battery tomorrow as well!
Lord. Tech said:
Thank u for the how-to advice! i was a little confused with the particulars, Glad u cleared it up for me. The images are still downloading, damn the slow connection, so it'll be while before i know if it works, i'll update with the results soon. Yes, ur spot on. i barely got 2.5 hours SOT, usually just 1.5 hours! if i can get my phone running again, im ordering a battery tomorrow as well!
Click to expand...
Click to collapse
Just be sure you're clear on fastboot formatting Boot, System and Userdata. Make sure they all finish without errors. If any errors, capture the text. Important. Problem with the battery (for you) is getting a quality one. Lots of junk out there and you are located in BFE.
fastboot format boot
fastboot format system
fastboot format userdata
v12xke said:
Just be sure you're clear on fastboot formatting Boot, System and Userdata. Make sure they all finish without errors. If any errors, capture the text. Important. Problem with the battery (for you) is getting a quality one. Lots of junk out there and you are located in BFE.
fastboot format boot
fastboot format system
fastboot format userdata
Click to expand...
Click to collapse
LOL i agree, cant even get a decent internet connection out here let alone battery spare parts to a back-closed phone 95% people haven't even heard of, including the 3 repair shops i took it to the first time!! i had to google it and show them pics and videos on how to open it imagine. But since it was dead weight at the time, that botched joke surgery of my phone was still my best hope haha.
well, in other news, nothing worked i guess the phone is toast now. it just keeps freezing no matter what, stock images, 4 cores off, modified boot.img, everything. I got it in Pheonix Arizona from best buy 2 years ago when they had the 50$ off on the gold version. so cant even freaking RMA it to google! Gonna send it in for repair as a last resort, though i dont know what they can do at this point, repair cpu?
Maybe i should start looking into replacements perhaps the OP3T.... damn this is depressing.
Thanks for the help, i guess u win some, u lose some...
I apologise in advance if this has already been discussed elsewhere, because I have been unable to find said topic if it exists.
My problem:
I have a Moto E4, bought from Republic Wireless in 2017, shortly after its launch. Up until last week, I have had no serious problems with it. This last week, however, I suddenly have had 50% reduced battery runtime, in addition to noticably slower performance.
After some quick digging, I determined that the culprit is not an app, but the OS (battery stats under settings places "Android System" around 70% of the battery's usage). I installed a CPU monitoring app, and discovered that the CPU speed was stuck at the max 1.4 GHz (it never scaled down) with an idle utilization of 25%. Although I am unable to see the utilization of each of the 4 cores, I believe one of them is running a code loop. Restarts, and cache, app cleaning have had no effect thus far.
As I have done no more digging (I am on vacation and haven't had much time), I would like to know what next steps I should take. I have not performed a factory reset, but it is one of my next options for when I return home.
I do not want to root if I don't have to, but I know how to do so if it's absolutely required.
Thank you in advance, i know this post is lengthy...
~Nup
TheNupster said:
I apologise in advance if this has already been discussed elsewhere, because I have been unable to find said topic if it exists.
My problem:
I have a Moto E4, bought from Republic Wireless in 2017, shortly after its launch. Up until last week, I have had no serious problems with it. This last week, however, I suddenly have had 50% reduced battery runtime, in addition to noticably slower performance.
After some quick digging, I determined that the culprit is not an app, but the OS (battery stats under settings places "Android System" around 70% of the battery's usage). I installed a CPU monitoring app, and discovered that the CPU speed was stuck at the max 1.4 GHz (it never scaled down) with an idle utilization of 25%. Although I am unable to see the utilization of each of the 4 cores, I believe one of them is running a code loop. Restarts, and cache, app cleaning have had no effect thus far.
As I have done no more digging (I am on vacation and haven't had much time), I would like to know what next steps I should take. I have not performed a factory reset, but it is one of my next options for when I return home.
I do not want to root if I don't have to, but I know how to do so if it's absolutely required.
Thank you in advance, i know this post is lengthy...
~Nup
Click to expand...
Click to collapse
A factory reset is probably the next step if you prefer not to root. Also try to identify the source with a monitoring app like BBS or GSAM (I prefer the latter). You'll need to grant a few extra permissions via ADB on an unrooted device to get the full picture. GSAM walks you through the procedure via the overflow (3 dot) menu. Good luck.
I installed GSAM, used my PC to enable permissions, and checked the app after awhile. Once again, it's showing "Android system" as the main CPU AND battery hog, at over 74.6%. I would attach a picture, if I could figure out how to do it... (Please tell me how, I feel dumb). But that's what I have done this far. When I get home, I'll work on factory resetting it.
However, I am still worried that a factory reset might not fix the problem, since it is with the Android system. If all else fails, would it be possible to reflash the OS? The phone shipped with Republic Wireless software, so I would need the ROM from them..... And I would probably have to ask them for it. But that is only if reset fails to fix my problem. Is a reflash even possible...?
TheNupster said:
I installed GSAM, used my PC to enable permissions, and checked the app after awhile. Once again, it's showing "Android system" as the main CPU AND battery hog, at over 74.6%. I would attach a picture, if I could figure out how to do it... (Please tell me how, I feel dumb). But that's what I have done this far. When I get home, I'll work on factory resetting it.
However, I am still worried that a factory reset might not fix the problem, since it is with the Android system. If all else fails, would it be possible to reflash the OS? The phone shipped with Republic Wireless software, so I would need the ROM from them..... And I would probably have to ask them for it. But that is only if reset fails to fix my problem. Is a reflash even possible...?
Click to expand...
Click to collapse
If it's the 1768 then the retail firmware should be fine (I'd say preferable even). Unless you need that extra software that is.
After factory resetting my phone, I reinstalled everything. BUT, to my surprise, as soon as I installed Snapchat, the same problem BEGAN HAPPENING AGAIN. I used GSAM, expecting to see Snapchat this time. Yet, it still said Android System was hogging the battery.
So I uninstalled Snapchat.
Surprisingly, the problem ceased to exist.
To be sure, I reinstalled Snapchat. The problem appeared. Uninstalled, problem disappeared.
So it appears that a factory reset might not have been necessary, but I'm wondering what aspect of Snapchat was causing the core overload. Regardless, I am never using Snapchat again, until I hear word of this problem being looked into/fixed. (I did capture and send them a bug report, but that might be of no help regarding this situation)
TheNupster said:
After factory resetting my phone, I reinstalled everything. BUT, to my surprise, as soon as I installed Snapchat, the same problem BEGAN HAPPENING AGAIN. I used GSAM, expecting to see Snapchat this time. Yet, it still said Android System was hogging the battery.
So I uninstalled Snapchat.
Surprisingly, the problem ceased to exist.
To be sure, I reinstalled Snapchat. The problem appeared. Uninstalled, problem disappeared.
So it appears that a factory reset might not have been necessary, but I'm wondering what aspect of Snapchat was causing the core overload. Regardless, I am never using Snapchat again, until I hear word of this problem being looked into/fixed. (I did capture and send them a bug report, but that might be of no help regarding this situation)
Click to expand...
Click to collapse
Did you grant permissions (via ADB) to allow GSAM to disambiguate resource consumption on an unrooted device. Try using Greenify to rein in bad app behaviors. Works a treat on rooted devices and *should* be effective on user installed apps if unrooted.
I'll try that. And yes, despite using my laptop to give GSAM permissions, it only showed Android system as using the power. I'll install Snapchat, see if the problem appears again, open GSAM, and give it some time. I'll also install the other app and set that up too.
Between those two, I should be able to determine if Snapchat is causing this issue; and if so, what part is. (Phone is unrooted, because I don't want to void warranty (Motorola needs to give me the key to root, and I don't want to do THAT just yet) so we'll see what happens)
Okay. After extensive testing, the phone has finally "cooled down". Snapchat no longer hogs battery, and now I get more battery life than before this problem even began. I wonder if, somehow, somewhere, a system file became corrupted, instead of Snapchat causing the problem...
Whatever the cause, a full system reset forced the loop to break.
Now I'll use Snapchat (and every other app) with caution now... I have a CPU monitoring app running 24/7 (it uses almost no battery)
Feel free to close this thread