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
Related
Hello all,
Not sure if anyone has had this happened to them as well.
I am looking to root the phone and this is the only thing holding me back in fears that would be a hardware issue and then can't replace. But thing that it is software.
Here is what happens, like in the mourning I will wake up and check time on device by just pressing lock once and put down (has happened even with out doing that) then will see that alarm won't go off and try and wake the phone with power button and will get no response from the device just black screen and phone is getting warm.
I will actually have to remove and reinsert the battery to get to come back on.
Has been doing this since the update. I have tried to go an uninstall all the programs I don't use and don't have anything on it that my mytouch is not running and that device has no problems. Tried master resetting the device a few times.
I have reset from the recover wipe data option and from spl neither seemed to help
Problem only seems to happen after the phone has been on for over 100 hours.
Weird thing I took notice is after a master reset it redownloads all the apps again right away. Don't know how to stop that.
Right now mine is running the stock software the shipped version manually update to official touch update from sdcard.
So my question is there anyway to have the phone keep the logs since logcat is reset when the phone is restarted to find the problem. Or if this something you all have seen. Any ideas would be appreciated.
Hopefully you have a software-only problem... and I don't know how to prevent logcat from resetting after restarting the phone... but I can recommend one possible solution...
1. Get the stock Google/HTC signed EPE54B firmware... http://forum.xda-developers.com/showthread.php?t=642811
2. Rename it to PASSIMG.zip, copy it to the root of your SD card.
3. Reboot in bootloader and select Bootloader from the menu. Your phone should start scanning for the PASSIMG.zip and ask you to apply the firmware update...
And, yeah... no you won't void your warranty by doing this, since this is a stock signed original firmware....
I get this (or a similar) problem too. I'm not yet sure if it's a hardware or software problem, and am therefore avoiding rooting my phone until I'm sure.
I have noticed that this happens more often, or at least seems to be more likely, when the phone is cold... I've not had it happen during the day (when it's nice and warm in my pocket), but when I leave it on my night stand whilst sleeping, or for an extended period on my desk at home, it seems to freeze up then.
I'm an electrical engineer and suspect that this problem may be due to silicon right on the edge of it's qualification range (similar to how some people are able to overclock to 1.2 GHz stably, mine is unstable even at 1 GHz... :-( ), I think my device is unstable at 998 MHz at whatever voltage it's running at currently (looks like Qualcomm changed the recommended voltage from 1.25 to 1.275 and finally to 1.3V over the course of early 2010).
See some of these commit comments for more details:
https://www.codeaurora.org/gitweb/q...it;h=6ede969b4418be5f8f2bd128d0cd4fbd3fd97e72
https://www.codeaurora.org/gitweb/q...it;h=ff61966464a2a2d2da36c0194d326370d3c3caeb
https://www.codeaurora.org/gitweb/q...it;h=a129aec2ec8b0b8ef9943e437415073620f15678
Based on them, I would guess we can expect more stability in the FroYo release (assuming it's using the 2.6.32 kernel, and is coming soon). In which case I'll wait.
I will try that rom next. In my tinkering I went back to erd and let it auto update to ere on its own. and will see how that does. If it fails again I will try the other rom. I can still revert back from that to erd if I want later right?
everything except the radio... i believe the radio can only be downgraded on an unlocked phone... so i've heard...
It happen to one of my nexus one too, the other one never hangs. It happen mostly when i'm charging on the dock with screen on.
I address this problem with HTC once, and they told me to try remove the micro sd card and see if it happen again. So i switch a newer sd into the phone and its running fine waiting to see if it hangs again if it does, HTC say will they come send a carrier over to fetch the phone to check it.
Running fine for 4 days already, just weird tho how can a sd card cause this?
Could also be a low memory issue with the stock ROM. My wife's does that until I kill a bunch of background apps. I look at the available memory and it's at 13MB. She also hasn't reboot her phone in weeks...so that's probably why it was low on memory. I guess the internal Android task killer doesn't do it's job very well!
I got my first Vibrant on launch day with high hopes. Two weeks later I had a new one due the phone freezing EVERY time I opened Google Maps. I've held on to this one now waiting for a GPS fix and JI6 worked great for me....for about the first week. Now its just as bad as ever.
I get an initial fix much quicker, but after about five minutes it loses GPS signal completely and indefinitely. In the past week my phone has begun freezing AGAIN, including three times today alone. Two of the times I would go to unlock my phone and nothing would happen. The screen would remain off, softkeys wouldn't light up, and a long press on the power button does nothing. I have to pull the battery out and reboot.
This is incredibly frustrating because this phone takes nearly 5 minutes to boot (never actually timed it but I have to imagine somewhere close to that). So its a long wait before I can do what I intended to do. I did notice that Shopsavvy was sucking on the GPS signal when I rebooted the phone so perhaps that's what was secretly crashing it (Needless to say, ShopSavvy got the boot after the second freeze).
I've tried uninstalling and re-installing the Maps updates w/ no change. I would bring the phone back but T-Mo doesn't have any other phones I want. My Touch 4G is hideous and I don't want another QWERTY like the G2.
So did I just end up with another dud Vibrant or is there a fix? Would rooting fix my problems? This phone has never been rooted or hacked in any way.
Any ideas???
Short answer: Yes.
Short but longer answer: At least install a LagFix. I got back and forth between stock JI6 and Fusion 1.1 a lot. JI6 with a custom kernel and LagFix is butter. Fusion is even better.
You may have a dud though. I haven't had that many problems except for things I did myself.
atvman29 said:
I got my first Vibrant on launch day with high hopes. Two weeks later I had a new one due the phone freezing EVERY time I opened Google Maps. I've held on to this one now waiting for a GPS fix and JI6 worked great for me....for about the first week. Now its just as bad as ever.
I get an initial fix much quicker, but after about five minutes it loses GPS signal completely and indefinitely. In the past week my phone has begun freezing AGAIN, including three times today alone. Two of the times I would go to unlock my phone and nothing would happen. The screen would remain off, softkeys wouldn't light up, and a long press on the power button does nothing. I have to pull the battery out and reboot.
This is incredibly frustrating because this phone takes nearly 5 minutes to boot (never actually timed it but I have to imagine somewhere close to that). So its a long wait before I can do what I intended to do. I did notice that Shopsavvy was sucking on the GPS signal when I rebooted the phone so perhaps that's what was secretly crashing it (Needless to say, ShopSavvy got the boot after the second freeze).
I've tried uninstalling and re-installing the Maps updates w/ no change. I would bring the phone back but T-Mo doesn't have any other phones I want. My Touch 4G is hideous and I don't want another QWERTY like the G2.
So did I just end up with another dud Vibrant or is there a fix? Would rooting fix my problems? This phone has never been rooted or hacked in any way.
Any ideas???
Click to expand...
Click to collapse
I did not know what a real smartphone was supposed to be until I rooted and custom rom(ed) it.
For the first 3 months I had the phone... I was reluctant to root. But ofcourse... It was just another phone... laggy and slow...
Until I rooted and installed Bionix. Now its smooth as butter.
Good things in life are always free. I paid for a suffocated phone... xda developers free services released and refreshed my phone.
Well
I would install Fusion 1.1 with the Core kernel from Sombionix and see if that fixes it. Stock is totally unacceptable.
If it stills sucks, its likely a dud.
You must either be getting dud phones, or you're installing some app that's messing them up(?) I'm stock/unrooted, and very happy. Not that I doubt the happy results reported by folx like those above, but I don't have bothersome "lag" or freezing etc. -- no issues that even tempt me to ROM-swap (I wouldn't have kept the phone if I weren't satisfied w/it stock).
My GPS did used to lose signal as you report; haven't given it a good comparison test since JI6 update.
Well I've rooted using OCLF and also applied the lag fix. No change.
I still find the phone dead 2-3 times a day with no warning. I'll go to wake it up and nothing happens.
Some of you think installing a new ROM with help? How can I do that? The one time I tried using ODIN, it was never able to identify my phone.
Ugh, why can't this POS just work.
atvman29 said:
Well I've rooted using OCLF and also applied the lag fix. No change.
I still find the phone dead 2-3 times a day with no warning. I'll go to wake it up and nothing happens.
Some of you think installing a new ROM with help? How can I do that? The one time I tried using ODIN, it was never able to identify my phone.
Ugh, why can't this POS just work.
Click to expand...
Click to collapse
Did you make sure you had the Samsung USB Driver for the Vibrant? If you don't Odin won't recognize your phone. Also important to have a newer version of Odin. Like I have 1.7. And last as Odin is a little troublesome, you should have Odin up and running before you connect your phone. Read the Bible in the Dev section for links.
1) Could be a dud, it happens
2) When I first got my Vibrant, it boots up so fast. Its because there are hardly any apps installed that as part of the boot up process, go and check on. I think it has to do with the cache, because once you load it up with apps, the time it takes to get to the home screen is noticeably longer.
Also ShopSavvy is a bit wonky with the gps, so I disabled that setting in the app. But my though is you might have a bad app installed or something funky on the internal/sd memory that its fighting with. I'd say as something to just try for kicks, backup everything, copy memory to your pc, wipe the memory and do a factory reset(You could odin to stock, but you'll lose the Sims app). If things work, slowly add your apps back in.
As for gps, yes before the update it just wouldn't lock or would take forever, but still not be very accurate. After the update(but then also after alot of flashing different roms, then finally just going back to stock), gps works like a champ. But I would also point out that gps is vulnerable to several things. Don't place the phone near any large metal or magnetic object, this will throw the compass off. And always try to have a clear view of the sky, without being in a 'canyon' of buildings. The buildings distort the signal(which in the case of gps is just a signal that tells the time) and can throw off the reading(which is where the a in agps is supposed to come in).
I have searched through XDA and read all the threads regarding the 'suspend process' issue. The specific issue is outlined in Issue # 11126 on the Google Code/Android project home...
http://code.google.com/p/android/issues/detail?id=11126
I am trying to get to the bottom of this, as best as possible. For all intents and purposes, this really appears to be a mystery. Ultimately, it appears as though there is (currently) absolutely no specific reason a to why 'suspend' runs wild until the device is rebooted.
My question is (I know we can all only speculate):
Is there any chance that this could be Google account-specific?
The reason I ask is, I've been doing some "testing," just to try and make sense of this for myself. Here is what I've done/come across thus far...
- My fiancee's first MT4G was a black one manufactured in Taiwan. It had the inferior LCD-SH-C2 screen. Her battery was draining VERY quickly - i.e. before noon, without using the phone for much else other than texting.
- I enabled USB Debugging for her, to "rule out" the init process issue.
- Even though she only had Handcent, Facebook and Angry Birds installed, I removed all of them, leaving only Watchdog.
- I factory reset her phone, twice.
- For all of the above, the device was not rooted. I have since rooted her phone via the steps in this thread.
I'm in the process of creating a new Gmail account for her, exporting ONLY her contacts and then using that account for her new MT4G (Plum) that's scheduled to arrive today. I'm actually thinking of NOT using her new Gmail account at first though, so I can use her original Google account on this new, clean device and see if the suspend issue persists.
I might just be wasting my time, but I enjoy doing this and I don't think it's a complete waste to try and find SOME constant here. Am I nuts for thinking it's tied to the Google account? The Google account seems to be a black box of sorts. There is more than just contacts, apps and settings, yet there is no "window" into everything else that comes down - e.g. I can't log in to Gmail and "configure" it to not restore her wallpaper or WiFi settings. So that's why I say it's a black box of sorts, since it's doing more in the background than we have control over.
Nothing is truly random, at least not in the context of Android and the hardware affected. There has to be some reason why users of various devices, either do or do not experience this issue. Whether it's a specific action or the something that differs between one person's action vs. another person's, there has to be SOMETHING that's triggering this on her device, yet never triggers it on mine. I guess I'm just trying to flush everything out and hope that discussing it will help rule out/rule specific variables.
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
mwelliott said:
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
Click to expand...
Click to collapse
According to XDA and Issue #11126, you're not alone.
What's really bugging me is that neither my first MT4G, nor its 1st replacement or its 2nd replacement, have ever done this. My fiancee's first phone did this. She is now using my 2nd replacement while she waits for hers to arrive (today). So a device that never exhibited this issue, over the course of at least a week of normal-for-me use, started exhibiting this issue for my fiancee maybe a day or so after using the phone.
I thought I had "solved" it when I didn't see it crop up the first day she used my replacement phone. She was quick to let me know I was incorrect.
So I've got serious pressure here - all of my MT4G's haven't exhibited the out of control 'suspend process' issue while I was using the devices, but with her, it does. <queue the jokes>
We own our own business, so we're in the same room all day long while we use our phones. I was the first to tell her, "it's something you're doing." I'm only repeating myself by saying that I blamed it on an app she installed or something she "did" to cause it. After factory resetting, what...2, 3 times...I'm starting to forget; after checking the apps that are installed (and removing all of them); after verifying every setting from USB Debugging, screen brightness, account sync, etc. I seem to at least be able to say, "every single setting, shortcut, widget, app or usage pattern, does not produce the issue on any device I have used with my Google account, whereas it does with my fiancee."
That's the most difficult part to get absolute - the usage pattern. She's doing such basic things though, but I know that even the slightest of difference can produce different results.
I will most certainly report my results, futile or not.
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Chadastrophic said:
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Click to expand...
Click to collapse
That seems to be the constant, to a degree. I'm seeing people state that they're having this issue on anything from the Samsung Galaxy S (i9000) to a Nexus running Cyanogen 6.1. That's people stating it though, so I'm not sure if they're actually experiencing the same issue or not.
I am biting my tongue, but I think I found another common denominator...I am going to post back in a coupla days once I've seen it last for this entire week.
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
zero_oli said:
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
Click to expand...
Click to collapse
Yeah, it didn't seem 100% related to devices running Sense, so thanks for posting back to this.
My fiancee was experiencing this across her first two MT4G devices and has yet to experience the issue on her third and final MT4G. I want to see it run the rest of the week though before I share, but the issue did pop-up for her pretty much within 24-48 hours on her first two MT4G's.
Shlongwoodian: I have been following your posts as the "suspend" process has been affecting me since I received my phone the first day available. However, I am reluctant to send for a replacement as all else is great on the unit I have and there seems no gaurantee that a new phone fixes this issue.
I have tried Tmo and HTC and both seem clueless; therefore, I appreciate your research and look forward to any "fix" short of waiting for Gingerbread.
Anyone have any wisdom to pass on? This issue is driving me crazy! I've noticed it most on my black MT4G (w/the good screen) after browsing the web, youtube or using the media player. My wife's red MT4G (w/the inferior screen) has had no issues and her battery is amazing! The first day she got her phone her battery lasted 24 hours without even conditioning it! Granted she doesn't use it like I do mine, but it is still a huge difference. When this issue comes up on mine, I'm dead within 3-4 hours. I have Watchdog set so when it alerts me I just soft reset. That clears it up until it decides to come back at random intervals. It usually doesn't come back until I open the browser, etc. With as much as I use my phone (I am constantly on the road), it becomes a major pain to have to constantly monitor battery life. Any help is greatly appreciated!!!
Man, I am sorry to report that I gots nothin'. Ok, here was my original theory...
I was speculating that "something" inside the Google/Gmail account was the cause. My reasoning being, essentially, your info is stored in a database. When you get an Android device, that online database is synced locally with the phone's database. We each have different databases and there is more than just your apps, Market links, contacts, etc. I never exhibited the /suspend issue on phones that she experienced the /suspend issue on. I figured it was database-specific.
If a table contains a value, or rather, does not contain a specific value (or if columns are missing, etc.), it can cause an application to respond in a negative way. Sometimes, this causes an error to bubble up in an application. Other times, it doesn't. In my experience, I've seen much more subtle issues in databases, that don't cause errors or a crash, but instead just cause "undesirable results."
When my fiancee got her final, good replacement Plum Glacier, we started with a completely new Google account. We thought we nailed it, when a handful of days passed without seeing /suspend get out of control, leading to Android System and/or OS sucking down battery life. I think it was nearly a week into it and one day while she was out, she realized she lost battery life really quickly - i.e. left the house with 90% and by the time she got to the store, shopped for a bit and looked, her phone was down to like 30-40%. She knows how to check for /suspend and it was, of course, back.
It's still not something that can be completely ruled out, since it's not a very air-tight test. There could be something about my Google account (which I've had pretty much since Gmail beta was available) that's keeping me (and others like me) from getting it or that idea could be crap.
For some reason, I have never, ever seen this happen on my Glacier(s) running stock 2.2.1. Phones that I never saw the issue on, she saw the issue on. There is so much speculation around it, but it just seems like "some people" don't experience it and "some people" do. It's all over different devices, different skill levels, etc. No apps, same apps, whatever and it happens to some but not others.
Sorry to get anyone's hopes up. I'll keep looking for differences/similarities though and if I find anything at all I'll - or if anyone else finds anything, no matter how ridiculous it sounds (yes, we've tested the 'rock' and it doesn't appear to suffer from the /suspend issue) - post it here.
Thanks for trying! It was a good theory. So . . . now what? Is there any way to get this ranked higher with Google, HTC, etc. to get more people working on it? It is really driving me nuts! It mainly happens after I use the web browser, then put the phone on standby for some reason. I can't even use the browser any more without needing to reboot it to save battery life. There is another thread, but specifically for the Evo and I think one for the Nexus one, all with the same problem. What if a new thread were started that is not device specific? That way we can get more people to star it and maybe Google or whoever will pay more attention to it! I would hate to think that we are stuck with this problem until when and if we get upgraded to 2.3. I would suggest rooting and flashing a new ROM, but even those with custom ROM's are having the same problem, so that's not going to help. Thoughts???
jpiano said:
It mainly happens after I use the web browser, then put the phone on standby for some reason.
Click to expand...
Click to collapse
It truly is a mystery to this day. I've seen people say, "it happened right after I installed Handcent" or "it happens as soon as I do..." No one has come up with any concrete evidence thus far.
My fiancee has Handcent, I have Handcent. I used Handcent heavily, never had an issue. She stopped using Handcent - still has the issue. We've gotten so granular in our troubleshooting, we're literally tracking every step. LOL i.e. I pressed the trackpad to wake the phone, once; I unlocked the phone, I swiped my thumb once to view my Watchdog Widget on the screen to the left of my homescreen, etc., etc., etc.
So, for now, we just wait? My phone (and all previous phones) have been just fine. My fiancee however...yeah, I'm trying to find a fix pretty quickly.
One common theme that I've seen with this issue is that it only happens after I put the phone to sleep. I have never seen it crop up while actually using the phone. Maybe we're going about it the wrong way in trying to identify an app, etc that's causing the problem... perhaps it is simply the code involved in putting the phone to sleep and that's why there hasn't been any consistency with what one does to make it appear. In your experience, have you ever seen or heard of it showing up while the phone is being used? Perhaps it's just on mine that it works that way, but I thought it was worth mentioning. I know nothing about code or how android works so please forgive the noob comment if this is an obvious one. Merry Christmas!
I've got this problem big time. Returned my first phone because I thought it was the phone. First few days were good but lately its back and as bad as ever. First thoughts were angry birds twitter or wifi but I have no idea. If I can't figure this out I might have to sell this phone.
I will try to post some more thoughts. I think you're onto some good ideas here.
Sent from my HTC Glacier using XDA App
(Re-posting from the developer's Google blog where others are following this issue): Interesting about using the phone without a Google account. Not sure if this is relevant or not, but I've noticed something else with consistency. Granted I wasn't able to document the behavior through system panel at the time, but this has consistently happened. When suspend goes crazy, I can get it to stop simply by charging the phone! Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot. Noob speaking here but perhaps the part of android that actually logs the battery usage is suspending when the phone goes to sleep? When it us charging, this log is reset and clears the process from running. If this is even possible, then could someone write an app that clears this system log? Maybe by mimicking what happens when the phone is charging, we can at least temporarily clear the issue without the need tovl reboot? Again, I know nothing about all this so sorry if this is all irrelevant. Just sharing what I've noticed to be consistent. Thoughts??
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
jpiano said:
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I wonder if you're on to something with the SD card. I've been thinking I haven't seen the suspend issue return on my phone in quite a while. I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems. For those who are having the problem still, I wonder if removing or formatting their cards would show any improvement? Worth a shot if at least to eliminate another possible factor.
Sent from my HTC Glacier using XDA App
That's cool that this thread is flushing out other ideas and possible variables. I like the idea of connecting it to the charger for a couple of seconds, but my fiancee is so used to just rebooting her phone each morning and sometimes again by mid-day, that it's easier for her to do just that.
jpiano said:
Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot.
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I like the microSD Card notion. This is such a weird issue, that it's so easily associated with other items - e.g. applications, usage patterns, etc. This seems feasible though, but the only way to know for sure is to reproduce it. My fiancee experiences the suspend issue daily, if she doesn't reboot regularly. So, I should be able to take her microSD card and use it in my phone and get the suspend issue. I don't want to 'muddy' up by swapping microSD cards, so I'll try reformatting her card and see if that makes any difference. She usually sees the issue within 24-48 hours of a fresh boot, so it shouldn't be long before we see if that fixes it or not. I can check the card for errors, etc. as well.
werk said:
I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems.
Click to expand...
Click to collapse
I'll be upgrading to a 16 GB Class 10 soon, so I can give her my Samsung if need be. I'd really like to see if this is it though. It would explain the "some people get it and some people don't" pattern.
I also noticed that the minute I plug the phone in the problem goes away. Not sure why, just confirming it happens to me too. I also should note that when I returned my phone, they popped my old SD card into my new phone. So if there is an SD card issue with a corupt file/photo that could be something as well. I wonder woody if your girlfriends phone has had the same SD card after how many times did you say you traded it in? BTW, a side note, how did you exchange it so many times? After I took mine back to the store on day 14 they told me I wasn't able to exchange it again.
I do have a 16GB SD card but just haven't had time to install it. Wanted to double check which things I need on the new one from the old one, but it might be a good way to test this issue. Let me know some ideas before I swap the cards and maybe I can help test this.
Also, one more thing, what is the app you're using to log stuff? I'm just using Watchdog Lite right now.
I've got to figure this out or this is a dealbreaker for me. I have waited 3 years to upgrade phones, first time on Android, really wanted iPhone but wanted to stick with month to month from TMob. If this continues I think I will move to Windows Phone 7 or iPhone if I have to, but I really like this phone when the battery is not draining like a leech.
Thanks.
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
royhobbs said:
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
Click to expand...
Click to collapse
Just straight copied the existing files over from the old card to new one (new one in phone connected via USB, old card in SD adapter in my laptops SD card slot). I think some Angry Birds files didn't make it due to long paths, but reinstalled it and no problems since then.
Problem 1:
I've just rooted my nexus-s and I'm not sure whether it's due to rooting or a software conflict with apps installed on the device that's not compatible with android 2.3, but I'm experiencing quite a frequent phone reboot while I am in the middle of an active call.
Is there a way to capture the log of the phone's function and see what's causing the reboot?
Are anyone experiencing this problem as well?
Problem 2:
I probably have only used 240 Mb of the USB storage, and it shows that I have 13Gb free. However, when I put the check boxes beside the applications that can be moved to the USB storage (i.e. native apps2sd), I seem to have surpassed the limit allowed for moving the app for USB storage. I've got 21 apps that can be moved, but it won't allow me to move the 21st app. Error message says "[! Move Application] Failed to move application. There is not enough storage left." I've tried checking and unchecking boxes of different applications, and it has nothing to do with the 20 apps limit, but rather it's the amount of memory being moved to the USB storage
********************* updated 01-12-2011 **********************
Please report to Issue 13674 on google's bug reporting page.
hXXp://code.google.com/p/android/issues/detail?id=13674
Sorry, I'm a newbie, so I can't post outside link. Please change the XX to tt in the link above.
************************************************************
Well I have 23 apps on my USB storage, and I have the Voodoo Root kernel as well. It shows 2.1gb used, 11gb free.
I did notice a 'soft reboot' earlier today but it wasn't during a call, don't know what caused it but yeah. Honestly if I were you and the problem persists just reformat and start over.
Im having the same phone reboot problem as you during phone calls. I thought it was due to an app called Screebl being incompatible, but i just made a test call and it rebooted after about 18 minutes. Im going through my apps to see what else effects the phone state during phone call.
Ive heard of some people having problems with google maps causing problems during phone calls, or sprint nav (but we dont have sprint nav) So im going to try shutting down maps, and uninstalling my task killer, which i also heard can cause problems.
Have you been able to figure anything out? I really dont want to have to reset my phone and lose all my save data information from my games. My phone is not rooted, and i dont plan on rooting yet, so i cant use titanium backup for my data.
Phone only Reboots during active phone call, i can play games or surf the web on it all day long with no reboots.
So software issue in android 2.3, or some kind of app incompatibility im thinking
you can capture the log with adb logcat command, or download a logcat app from the Market http://www.appbrain.com/search?q=logcat
Why are you bothering with apps2sd? The Nexus S shares the Galaxy S line's hugh, I mean HUGE, 1GB of "disk" space for apps. I've got almost 100 apps on my phone and not a hint of low space. See the screen capture I've attached: 284mb used for apps, 724mb still free!
oh crap! please let it not be the same problem as in the SGS i9000m
that's one of the sign before the internal SD goes belly up
AllGamer said:
oh crap! please let it not be the same problem as in the SGS i9000m
that's one of the sign before the internal SD goes belly up
Click to expand...
Click to collapse
Didn't they switch the type of flash memory used from earlier Galaxy S phones? I saw some discussion about it not being movinand any longer, or at least some sort of physical difference between what the NS has vs the SGS line.
distortedloop said:
Why are you bothering with apps2sd? The Nexus S shares the Galaxy S line's hugh, I mean HUGE, 1GB of "disk" space for apps. I've got almost 100 apps on my phone and not a hint of low space. See the screen capture I've attached: 284mb used for apps, 724mb still free!
Click to expand...
Click to collapse
Haha this may be the case, but I've inherited the habit of obsessively moving apps to sd/usb from using my Nexus One. Combined, I am using about 450MB of space for my apps at the moment. But this is a huge improvement from the Nexus One.
DumbUglyDragon said:
Haha this may be the case, but I've inherited the habit of obsessively moving apps to sd/usb from using my Nexus One. Combined, I am using about 450MB of space for my apps at the moment. But this is a huge improvement from the Nexus One.
Click to expand...
Click to collapse
Oh yes, I was the same on my N1 and even EVO 4G, but once I got a Galaxy S, never even considered it.
I'll wager the nand used for the "rom" space is faster than the nand for the "sdcard", another thing to consider. You're not even half-way used up with that 450...
americancrew said:
Problem 1:
I've just rooted my nexus-s and I'm not sure whether it's due to rooting or a software conflict with apps installed on the device that's not compatible with android 2.3, but I'm experiencing quite a frequent phone reboot while I am in the middle of an active call.
Is there a way to capture the log of the phone's function and see what's causing the reboot?
Are anyone experiencing this problem as well?
Click to expand...
Click to collapse
I haven't rooted my Nexus S,but i've experience the same soft reboot during call.
I have the "End call using power button" option enabled. Im not sure if i was leaning on the button when it happened, but stock doesn't have a reboot option, so its unlikely. I suspect its a OS bug, rather than a rooting issue.
Let me know if you make any progress, i've since made calls with no problems.
Psosmith82 said:
Im having the same phone reboot problem as you during phone calls. I thought it was due to an app called Screebl being incompatible, but i just made a test call and it rebooted after about 18 minutes. Im going through my apps to see what else effects the phone state during phone call.
Ive heard of some people having problems with google maps causing problems during phone calls, or sprint nav (but we dont have sprint nav) So im going to try shutting down maps, and uninstalling my task killer, which i also heard can cause problems.
Have you been able to figure anything out? I really dont want to have to reset my phone and lose all my save data information from my games. My phone is not rooted, and i dont plan on rooting yet, so i cant use titanium backup for my data.
Phone only Reboots during active phone call, i can play games or surf the web on it all day long with no reboots.
So software issue in android 2.3, or some kind of app incompatibility im thinking
Click to expand...
Click to collapse
You know, I thought there were software incompatibilities too at the first place. I did not use "End call using power button". But after running the same stock rom with rooting and apps for a week, I didn't see the soft reset during the phone call. I have just installed a new rom on my nexus s, the R2 version of MoDaCo Custom ROM for the Samsung Nexus S. Running great so far. No soft resets.
** Edit **
Actually, after posting this post yesterday, I did experience another soft reset whilst talking on my phone. I have the same apps that I have been running in the background, mainly: google pinyin, paypal, k-9 mail, ebay, rhapsody, google voice, bluetooth share, and swype. I am not experience the soft reset in all calls, after I have installed the R2 version of MoDaCo Custom Rom. I will post any problems again if I do see this happening again.
I did a factory reboot/restore and that seemed to take care of the soft reset during call problem.
Have made several calls without issue
Its doing it again, this phone is going back. The screen coating is already wearing off as well. Hopefully number 2 will be better.
I have yet to get one android phone that hasnt had to be exchanged once. Android phones really need to have better QC before leaving the factory.
Droid 1: 3 times (keyboard, GPS problems)
Evo: 4 times (terrible screens)
epic: 1 time (Keyboard)
Nexus: 1 time (so far) Screen Coating, Constant Reboots
Phone reboots itself during an active call.
I have been experiencing this problem and it seems to escalate in frequency. I got this Nexus S on day one when it came out. However, I have not experienced soft reboot issue until last week, after the OTA update. Since then, it keeps doing it more and more and now it's like almost every active call I make. First, I thought it's software conflict. Now, having read this whole thread, I think it's an OS issue.
I also sometimes encounter with completely losing signal. The phone can not register to any network, and I have to reboot.
One more issue is the voice search apk sometimes activates itself when I shake or move the phone.
My phone is stock, and I do not have any issue with USB storage.
I like the phone for its speed, and the contour screen. It handles most tasks very quickly, even it's still a stock phone, unrooted.
I still have it until Jan 14 to decide whether I will keep it or not. Hopefully, there are some ways to fix these issues.
Mine is restarting during calls and also when not in use. It restarted 3 times during calls within 10 days, and I witnessed it restarting by itself at least once when the phone was locked and not in use.
I have an unrooted Nexus S, which I started using yesterday. The OTA came almost immediately after setting up, so I installed that. It appeared to be working flawlessly until this evening when I made the first call on it. It rebooted a few minutes into the call. After redialing it did it again, the third call I ended without problem, but was shorter than the previous two. A few mins later I made some test calls and it rebooted during both of them.
I did a factory reset and wipe of USB storage - I didn't bother adding my Google account and just made a test call which lasted 13 mins before I hung up.
I'll have to make some more calls tomorrow and if they work, I'll try adding my Google account and restoring stuff.
I had this same thing happen to me quite a few times reboot during a call or locking up after a call. I work to a company and we purchased three phones. So I switched with another one and guess what? Same problem definitely looking like a software problem.
This just happened to me for the 1st time a little bit ago. About 35 mins into the call/conversation, phone rebooted itself. Non-rooted here, I hope it's a software issue, that can be corrected within the next OTA update.
Are the spontaneously rebooting phones possibly overheating? Do they feel warmer to the touch than normal when it happens?
distortedloop said:
Are the spontaneously rebooting phones possibly overheating? Do they feel warmer to the touch than normal when it happens?
Click to expand...
Click to collapse
While I cannot speak for anyone else having this issue, in my case - no. The phone didn't get warmer, or seem to overheat. Odd issue to say the least.
Stock ROM (2.3.1) here as well. Just had it reboot 10 minutes into a call, then one minute into the following call to apologise for the first dropped call!
Its been a long time since iv been this stumped, about a week ago my phone started acting very strangely, laggy performance, freezing randomly and occasionally rebooting itself, now its getting worse, getting to a point where the phone is probably rebooting itself 5-6 times a day, iv uninstalled every app, iv factory reset it, wiped cache, replaced battery, removed the SD card (in case of file system corruption) using Samsung Smart Switch did an emergency flash back to original Rom, installed every troubleshooting app out there, monitored RAM and CPU usage, all i can see is that the CPU suddenly spikes to 100% with no real reason, i cant link any particular app or process thats causing this, all of the cores on the processor appear to be coping with no faults.
The only thing i can think of thats causing this issue is either iv got a pending hardware failure on the board, or possibly bad blocks on the nand memory, however i cant see any simple way of determining this without rooting and using the likes of ODIN or other 3rd parties etc - linux commands etc.
I dont want to root it particularly if i can help it as i was thinking about selling it on to mazuma or the like and let them sort it out instead, but i think i might have to bite the bullet and try it.
Can anyone suggest anything that i might have missed?
Actually iv seen an existing thread which appears to match my issues, so iv installed wakelock on the phone for now which seems to be helping a bit, time will tell, however this isnt a solution but more of a work around, but im still thinking this could be a motherboard issue myself, however, as i think this phone is over 2 years old, i doubt samsung will replace the component, nor would they necessarily believe me if i turn around to them and say its the board that needs replacing!
Terry6680 said:
Its been a long time since iv been this stumped, about a week ago my phone started acting very strangely, laggy performance, freezing randomly and occasionally rebooting itself, now its getting worse, getting to a point where the phone is probably rebooting itself 5-6 times a day, iv uninstalled every app, iv factory reset it, wiped cache, replaced battery, removed the SD card (in case of file system corruption) using Samsung Smart Switch did an emergency flash back to original Rom, installed every troubleshooting app out there, monitored RAM and CPU usage, all i can see is that the CPU suddenly spikes to 100% with no real reason, i cant link any particular app or process thats causing this, all of the cores on the processor appear to be coping with no faults.
The only thing i can think of thats causing this issue is either iv got a pending hardware failure on the board, or possibly bad blocks on the nand memory, however i cant see any simple way of determining this without rooting and using the likes of ODIN or other 3rd parties etc - linux commands etc.
I dont want to root it particularly if i can help it as i was thinking about selling it on to mazuma or the like and let them sort it out instead, but i think i might have to bite the bullet and try it.
Can anyone suggest anything that i might have missed?
Click to expand...
Click to collapse
Deleted...