Related
This is not a troll posting. I swear...
I've had the AT&T flavored Nexus One since the day it was announced and I just can't suffer with it anymore. I'm running stock FRF91 with an unlocked bootloader. The only reason I unlocked the bootloader was so I could root and uninstall the apps that drained my battery or sucked resources that I never used - Twitter, Amazon-MP3, Genie-Widget, etc.
Pre-Froyo, it seemed pretty stable but the OS was very immature. Some things were just not well thought out. Activesync for example.
Post-Froyo: Turn on GPS, reboot. Talk on the phone for a long period of time, reboot. Charge the phone, reboot. Use Bluetooth, reboot. GPS is 100% useless now as after just a few minutes of use, the phone gets hot and reboots the phone. Hell, leave the phone in the sun in your car and it gets hot and reboots. Froyo offers some new features but some areas of the OS are still neglected and way behind where they should be. Can't move emails to a folder? Seriously? Can't undelete an email you accidentally deleted? That's just stupid. And there are a few other things that Windows Mobile had right for the last 10 years.
Yesterday alone, my phone rebooted several dozen times because I was trying to find a location with GPS and I was completely turned around with no idea where I was. I finally had to power off the phone, leave it off, and go ask someone at a gas station for directions. The phone reboots as soon as it gets hot and it appears everything makes the phone get hot.
Rip on Windows Mobile all you want, but I never once had a Windows Mobile device reboot on me and not do what it normally does. I'll throw CM6 on my N1 when it becomes final to see if things get better and I'll thrown on Gingerbread when that finally drops, but unless one of those solves the constant reboot issue, I'm done with Android. I've kept up with the Google forums and many, many, many people have the same issues I have so my N1 is obviously not an isolated case.
There are a lot of things I do like about Android so I'm not bashing Android. I like Android enough that if my phone didn't reboot constantly it'd be my primary platform moving forward.
/rant
-Mc
I've had my N1 since the day after they were released and it has never rebooted spontaneously. Your phone is a lemon.
Try calling HTC?
vzontini said:
I've had my N1 since the day after they were released and it has never rebooted spontaneously. Your phone is a lemon.
Click to expand...
Click to collapse
I agree, the only time my phone gets hot is when I leave it in my landscaping truck while I'm mowing, but I think any phone would have problems when it's 112 degrees outside and probably 140 in the truck.
Sounds like a bad phone. The only time my N1 rebooted was when I had an experimental rom on it.
Sounds like something is just borked, I use my phone all day it only reboots because I want to go into recovery.
Are yur using custom recovery? Wipe the cache and dalvik-cache.
Same as the above poster, mine never rebooted spontaneously even when hitting over 40C degrees. Only does so when I'm running some cutting-edge alpha kernels/ROMs, and then very rarely.
I was thinking it was specific to my device as well. I then googled "Nexus One overheating" and was overwhelmed by the number of people with the same issue. I also own over a dozen HTC devices, I've had ZERO problems with any of them. I've wiped my cache quite a few times. I've even wiped the phone and started fresh.
I've googled every specific issue I have had and found many others complaining about the same thing. Overheating/locking up the device when charging overnight - check. Rebooting/overheating when using GPS - check.
Lately, I've been uninstalling anything that runs in the background that isn't an essential part of the OS. Makes no difference. When I first got my N1, I used the GPS and Car Home app to drive an 8 hour trip. Not a single problem. The very first time I tried to use Car Home after going to Froyo it rebooted after just a few minutes and it's been that way since. I found MANY posts that confirmed this on Google's forums.
Personally, I think my device is fine. I suppose it's always possible that an app is causing the reboots. For example, the Weather Channel app is always running and that's not the most beautifully coded app I've ever seen...
Any suggestions, keep 'em coming. I'm not thrilled with Windows Mobile 7 yet.
Here's my installed apps (I love that program BTW). If you see anything as a possible suspect, let me know:
Adobe Flash Player 10.1 (v10.1.92.8)
andLess (v1.2.3)
Android Agenda Widget (v1.3.5)
AT&T myWireless Mobile (v6.0)
Audalyzer (v1.14)
Barcode Scanner (v3.4)
BlueRSS (v3.0.4)
Chrome to Phone (v2.0.0)
eBay (v1.1.2.3)
eBuddy (v1.8.1)
Ethereal Dialpad (v2.5.2)
FCC Test (v1.0.7)
Flashlight (v2)
FREEdi Video Download Helper (v1.3.1)
FrostWire (v0.3.7)
Google Translate (v1.1.1)
GPS Status (v3.2)
gStrings (v1.0.5)
HistoryEraser (v2.1.1)
HTC_IME mod (vv.27)
JScreenFix (v2.0)
Keyboard Calibration (v2.10)
Linda Manager (v1.5.12)
Listen (v1.1.3)
Log Collector (v1.1.0)
Music Junk (v3.0.4)
My Battery Status (v2.0.8)
MyAppsList (v1.4 BETA)
Network Info II (v0.3.4)
Note Pad (v1)
OSMonitor (v1.1.6)
Pandora (v1.3)
Penguin (v1.2.0)
RealCalc (v1.4.1)
Scanner Radio (v1.9.2)
Secrets (v1.9.2)
Shazam (v2.0.2-B70005)
Shopper (v1.12)
Solo Lite (v1.25)
Terminal Emulator (v1.0.12)
Tetronimo (v1.5.1)
The Weather Channel (v2.3.17)
Titanium Backup (v3.4.2)
Trapster (v1.6.3)
Tricorder (v5.11)
TTS Service Extended (v2.0)
Universal Androot (v1.5.3)
Voice Recorder (v2.0.7)
Wifi Analyzer (v2.4.8)
WiimoteController (v0.3b)
XDA (v1.2.1)
Device Summary
Device: HTC Nexus One
Android Version: 2.2
Build: FRF91
List Generated By: MyAppsList (market://search?q=com.boots.MyAppsList)
By the sound of it, it's not an app. The phone should be able to take a good amount of heat and not reboot - the only time I got it to reboot was under direct sunlight in a car, it was probably hitting 50 degrees Celsius. If yours reboots every time you do anything - it's time to nandroid, take out the battery and clean the battery contacts really well (on the battery and the phone, using alcohol), flash a bone stock FRF91 or something really close to it, try to repeat the things that made it reboot (shouldn't be very difficult), and if the reboots continue - then I'm sorry, but you have a lemon. And if they don't - change to your favorite ROM and start incrementally installing stuff in small packs, until your testing shows reboots again. Defining anything other than Google account (like Exchange account) is also considered "installing something".
E-Mail quirks are taken care of by E-Mail clients. Exchange server push might be draining the hell out of your battery and heating your phone, check the relevant thread. I really hope you find the problem in SW, but it doesn't look very much like it.
P.S. There are so many ways to get a WinMo phone stuck (my wife has one, I regularly practice using the reset button when doing something with the system) it's not even funny.
thanks for the tips. I'll give them a shot. I read in a couple different threads that HTC has been sending replacement batteries to those with overheating issues. I have a hard time believing it's the battery but what do I know?
One thing I forgot to add about WinMo, I soft reset my device every morning on the way to work. Just a habit I got into with Windows.
-Mc
Yeah sounds like you got a faulty device. If the above suggestions don't work, call HTC and they should do a swap for you
went to the Google "Device Troubleshooter" support page: http://google.com/support/android/bin/answer.py?hl=en&answer=185837
Step 1: What are you having an issue with?
selected: A hardware problem I'm having with the Nexus One
Step 2: A hardware problem i’m having with the Nexus One
selected: My device overheats
Then it said this:
It is normal for your phone to get warm after an extended period of continual usage, such as a long phone conversation. If your phone becomes so warm that you cannot hold it comfortably, please try removing the battery and waiting until the phone cools off before replacing it.
If your phone overheats to the point of shutting itself off repeatedly, there may be a hardware defect with your phone's battery. Please visit our warranty information page.
Click to expand...
Click to collapse
So I called support (open 7 days a week - nice) and they are shipping out a new battery tomorrow and if that doesn't work, I'll send it in for repair. Didn't want to replace it because it was engraved.
I really hope this fixes it. I do like Android and I love the community work. iOS blows and Windows Mobile 7 just doesn't have me wanting one.
I'll update this thread when the new battery arrives and if necessary, after the repair work...
I used to have the same problem, but i don't think it was rom specific for me. I had a black case on my phone and my car mount was a black universal one mounted on my windshield. I would use GPS nav and play music at the same time and sometimes make phone calls and it would reboot pretty frequently. Through SetCPU i noticed that the temp was somewhere between 45-50degrees C. only way i was able to use my phone was to remove the battery and stick it in my AC vent along with the phone itself.
So since then i got myself a AC mounted carmount and no longer use my case and its been fine ever since. When ever it gets hot in my car i usually have AC on and the phoen gets cooled by it also. Average temp was around 15-18degrees C while i was using GPS/Music/Calls.
lulz, sounds like your phone had a hardware issue if it was rebooting all the time like that.
I have had my phone on for literally weeks at a time with out a reboot. Android is rock solid stable.
Way to not get your issue fixed and go back to a dead mobile OS that was never developed properly in the first place. Good luck with that champ.
My phone could stab me in the balls all day long and I still wouldn't revert to the current winmo.
McHale said:
This is not a troll posting. I swear...
I've had the AT&T flavored Nexus One since the day it was announced and I just can't suffer with it anymore. I'm running stock FRF91 with an unlocked bootloader. The only reason I unlocked the bootloader was so I could root and uninstall the apps that drained my battery or sucked resources that I never used - Twitter, Amazon-MP3, Genie-Widget, etc.
Pre-Froyo, it seemed pretty stable but the OS was very immature. Some things were just not well thought out. Activesync for example.
Post-Froyo: Turn on GPS, reboot. Talk on the phone for a long period of time, reboot. Charge the phone, reboot. Use Bluetooth, reboot. GPS is 100% useless now as after just a few minutes of use, the phone gets hot and reboots the phone. Hell, leave the phone in the sun in your car and it gets hot and reboots. Froyo offers some new features but some areas of the OS are still neglected and way behind where they should be. Can't move emails to a folder? Seriously? Can't undelete an email you accidentally deleted? That's just stupid. And there are a few other things that Windows Mobile had right for the last 10 years.
Yesterday alone, my phone rebooted several dozen times because I was trying to find a location with GPS and I was completely turned around with no idea where I was. I finally had to power off the phone, leave it off, and go ask someone at a gas station for directions. The phone reboots as soon as it gets hot and it appears everything makes the phone get hot.
Rip on Windows Mobile all you want, but I never once had a Windows Mobile device reboot on me and not do what it normally does. I'll throw CM6 on my N1 when it becomes final to see if things get better and I'll thrown on Gingerbread when that finally drops, but unless one of those solves the constant reboot issue, I'm done with Android. I've kept up with the Google forums and many, many, many people have the same issues I have so my N1 is obviously not an isolated case.
There are a lot of things I do like about Android so I'm not bashing Android. I like Android enough that if my phone didn't reboot constantly it'd be my primary platform moving forward.
/rant
-Mc
Click to expand...
Click to collapse
Your phone is defective. I've NEVER experienced a spontaneous reboot.
uansari1 said:
Your phone is defective. I've NEVER experienced a spontaneous reboot.
Click to expand...
Click to collapse
Same here** (only when I played with different kernels )
GldRush98 said:
Way to not get your issue fixed and go back to a dead mobile OS that was never developed properly in the first place. Good luck with that champ.
Click to expand...
Click to collapse
you're not much of a reader, are you?
JCopernicus said:
My phone could stab me in the balls all day long and I still wouldn't revert to the current winmo.
Click to expand...
Click to collapse
Fact: Windows Mobile still does several things much better than Android. And those things are important to me on my primary device.
I get what you're saying though. Despite a few issues, Android is dominating everything in it's wake. But instead of Android spending so much time with new flashy features, they should focus their attention getting the basics right first. Their contact and email handling B L O W S. How about proper email folder handling and a basic undelete function...
I agree with the rest. To be honest, I didn't get my Nexus new, it has had two users before me. It came with Cyanogen Mod, and to be honest I find it gives better battery life and performance compared to the stock OS. If I were you I'd try it out once you get the Nexus back.
I use ROM manager to download and install ROMs, give it a try.
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).
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!
For awhile now, my Droid 2 has been slow - slow to launch applications, slow to respond to touch, etc. I cannot attribute it to any newly installed application. Updates, maybe, but I'd have no idea which. I had it rooted with Z4Root, but then Verizon pushed out 2.3 and the phone became so slow that it is totally unreliable. I'll receive phone calls and 25% of the time the call will go to voice mail before I can get the phone to respond. I'll try to make a call and it may be 30 or more seconds between initiating the call to when the dialer appears and dials. Data speeds are slow.
At times the phone seems to operate at almost normal speeds and then it gets slow again. I've removed root access and uninstalled applications that require root access. I've also removed many other applications that I just don't need or use.
On my SD card it says I have 6.11GB free (out of 14.83 total). For "Application Storage" it says I have 5.63 Available Space.
I can't figure out what's wrong. Are there any suggestions short of resetting the phone to factory defaults and staring over?
Thanks,
Andrew
This has happened to my phone before also (droid2 rooted stock rom).
What i did to fix the situation, was the only thing i could think of.
I just did a factory reset to froyo and my phone was fast again.
Just back up all you apps and do a factory reset, its your only real option far as i can tell.
You could try installing something like 3g watchdog to monitor your apps and see if maybe 1 of them is eating up your phones processor.
Good luck.
Far as i can tell these phones are not much different from a home pc, in that they acquire so much extra pointless bull**** during their use that it just clogs the system. Forcing a reinstall just like a home pc.
Once they are reset back to factory, their performance returns to normal along with battery life.
Just be careful not to keep putting useless apps you dont even use onto your phone, just the apps that are absolutely necessary.
Keeping to this formula keeps my phone in tip top shape, short of changing roms or major tweaking.
Sigh I guess I'll need to try the reset.
I do have Watchdog installed and the last reported 'incident' was three days ago. No help there.
Everything is backed up, so here it goes... (I'll post back once I recover.)
Sent from my DROID2 using XDA App
I am having the same issues. I have an R2D2 stock, never rooted. Since the Gingerbread update, it has been flaky and getting worse. It is rebooting several times a day. I miss calls because the screen won't respond. Sometimes the hard keyboard won't respond and I have to manually reboot the phone to get the keyboard back. At least once, the soft keyboard wouldn't work either. I am hating Gingerbread but am at a loss on how to remove it. I'll be watching for your updates.
The gingerbread update has been reported to have several annoying as hell bugs, i never installed it for that reason alone. Besides i don't feel like loosing the ability to tether wireless, just to upgrade to a buggy version of android. Ill wait for ice cream to hit then maybe upgrade if i see something worth upgrading for. Till then its froyo, maybe try cyanogen mod 7.1
Far as going back to froyo from gingerbread, i know its been done and is fairly easy to do. Not sure how much different it is from a factory reset.
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