My handset has been freezing for the past 3 weeks, it's gone back for repair twice and the freezing got worse and worse. The shop agreed to order me a refurb replacement - in the week and a half since I've been waiting the phone has slowly stopped freezing to the point where it just never happens any more. I think this was what some people referred to as the SDS freezing bug. I let the freezes continue without rebooting my phone and that seems to be what's fixed it.
My replacement is due on Wednesday. It seems to me highly unusual that a phone can fix itself (it's been reflashed loads and factory reset even more) - do you think my phone could be considered reliable now or should I go for the replacement. Of course, I'm just curious as to what you personally would do in my situation.
questions go in the questions section.
go for the replacement
Replacement... But still it's only a refurbishment be careful try and get a device without the dodgy emmc
Sent from my GT-I9300 using Tapatalk 2
Please read forum rules before posting!
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Related
Hi, I've had my SGS2 for around 3 weeks now, and in that period I have had 2 random shut downs.
The first time it happened I was using the original firmware out of the box. The second time it happened (yesterday) I was using the latest firmware via Kies.
The phone is unlocked and unbranded from buymobilephones.net (UK), and I'm on the T-Mobile UK network.
The phone is NOT rooted and I am not overclocking.
Is my phone faulty or is this a software problem? Baring in mind this has only happened twice in the past 3 weeks.
backup data and factory reset would be my first step.
Followed by a return to the store .
jje
JJEgan said:
backup data and factory reset would be my first step.
Followed by a return to the store .
jje
Click to expand...
Click to collapse
Cheers, just did a factory reset. Should I ring Samsung to fix the phone (comes with 12 month warranty) or return it to the online retailer? Not sure what to do.
Just send it off to sammy
Sent from my MB860 using XDA App
... 2 shut downs in 3 weeks?
It's not faulty.
Your contract is with the retailer not Samsung .
I would see if phone restarts again before returning it .
But would inform the retailer of the problem to be within 28 days .
jje
drm111 said:
... 2 shut downs in 3 weeks?
It's not faulty.
Click to expand...
Click to collapse
I've owned several phones over the past 15 years and I've never had such problems before, even with my previous Android the Orange San Francisco. Seriously, if I have a £500 phone I don't expect it to shut down randomly even it it's only twice in 3 weeks. I've missed some important calls and texts because my phone has shut down without me knowing.
JJEgan said:
Your contract is with the retailer not Samsung .
I would see if phone restarts again before returning it .
But would inform the retailer of the problem to be within 28 days .
jje
Click to expand...
Click to collapse
roharia said:
Just send it off to sammy
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Alright cheers, I'll ring buymobilephones.net and see what they say.
beggin said:
Hi, I've had my SGS2 for around 3 weeks now, and in that period I have had 2 random shut downs.
The first time it happened I was using the original firmware out of the box. The second time it happened (yesterday) I was using the latest firmware via Kies.
The phone is unlocked and unbranded from buymobilephones.net (UK), and I'm on the T-Mobile UK network.
The phone is NOT rooted and I am not overclocking.
Is my phone faulty or is this a software problem? Baring in mind this has only happened twice in the past 3 weeks.
Click to expand...
Click to collapse
I think you mean two weeks ago.....
If it continues, you may have a faulty one.
Well I have the same issue, it's in my pocket, next thing when I push the power button the screen just stays black.
Have to hold down the power button to drop it and then restart it.
Sooo, I had this happen once when it was on the table which took the phone in my pocket out the mix.
In the end I tried the battery fix with some geckostrip (that rubber easy removable strip you use on the back of phones to stop them sliding)
I put the strip on the underside (opposite of the connections) and wrapped it around the back (facing the cover).
This makes for a VERY tight snug fit in the unit.
It has now been 2 weeks without one single shutdown...so as much as I thought "this must be software or hardware related", it looks like it very well may be "hardware related" on the battery front.
For those who still have this issue try what I did and let us know your findings.
Cheers
Sheldon
Update: Okay never mind on the battery thing, phone lasted 2 weeks but just blacked out again.....
I had the same problem for many months but it stopped after I uninstallrd dolphin hd browser. No idea if coincidence or not but read a few others with sgs2 and dolphin installed had same problem. Do you by chance have it installed?
Sent from my GT-I9100 using XDA App
I've actually experienced problems similar to this twice now with my SII.
First time was straight out of the box. I charged it up and then took it travelling with me. I kept taking it out of my pocket to find out it had turned off. I thought it was my fault with the power button being in a bit of a silly place. But then it turned off whilst it was lying on my desk or in my hand whilst I was using it. Whenever it turned back on again the battery usage history showed a big sudden drop (10+%) in battery level and then it would increase slowly for a while after. Spoke to O2-UK and they got me to do a software reset and then a hardware reset when it reoccurred, which didn't fix the problem either. They then did a next day replacement.
After I got the most recent update to TW I started to experience times when I'd come to unlock my phone but the screen would stay black. It would, however, give haptic feedback when I pressed the power button but not respond to touch. I recently did a software reset of my phone due to another problem (it kept thinking it was docking this time - but stopped on the day I took it into the O2 Shop) and haven't experienced this since.
For so expensive device I expect only 2 "legal" reasons to shut down while running stock ROM with no additional software or changed hardware (i.e. battery):
1. Battery went completly empty (or as empty as power saving settings allow)
2. I forced it to shut down via power button
If it shuts down on its own under this conditions, first doubt is faulty hardware.
And then it should be quickly replaced by provider/shop/wherever it came from.
Everything else might raise doubt in faulty piece of additional software.
Have had similar issues. Uninstalled the go weather app / widget and nothing since. Might just be a coincidence though.
Sent from my GT-I9100 using Tapatalk
So I've read about this "sleep of death" that sounds like the same thing as what this is.
It appears to affect a wide margin of Samsung devices over time.
One post suggested it was because WIFI activates while the screen is off and the device is in sleep mode, thus blaming the like of apps such as Juice Defender and WIFI managment built into gingerbread.
I have uninstalled gingerbread, enabled watchdog to monitor utilization (out of curiosity) and set the WIFI sleep mode to NEVER.
One day down without a issue, I'll see what happens over the next few weeks.
-Sheldon
I heard that frequent shutdown/reboots happens with 2.3.6 release.
If you got it, better go back to 2.3.5 or earlier. Iit worked for me.
I have 2.3.4 and i get these problems once a month or so.
Wy OH has the same firmware but she gets a random shutdown once a week. We both have the 1900 Anker battery (not stock one) - weird. I am going to try a different ROm and see if it makes a difference.
same issue but after i have deleted à few apps the issue was gone...?
Sent from my GT-I9100 using xda premium
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
guys im having the same issue too. its happened like 2 times in a month now. it previously happened when i was on 2.3.3 and stock ROM.
today it just happenned again even after being on superatmos 2.1, on 2.3.6.
whats going on?
As I was cycling, my htc rezound fell on the pavement. The battery popped out.
There are few scratches but no visible damage.
I start the phone and it's fine as long as I don't use data. Once I use data, the phone uses "1" may be it's ev-do. speedtest shows 129 kbps down rate. If i download something big, the phone restarts.
I tried flashing and installing a leaked ICS. that didn't solve the problem.
I would think that the damage was because of the physical shock of hitting the ground (nothing broke). so is there a way to diagnose it? to check if 4g is still working? is there anyway to fix this?
If its still under warranty I would take it back and get a replacement. Chances are dropping it is not covered under warranty, but if the device doesn't show any signs of a hard landing you'll probably be fine. Just tell them data stopped working on your phone for some reason.
good call, i completely forgot that i can go to verizon.
i was going to send it to HTC. i have to pay for shipping there. and the repair might be expensive (from what i read) if not under warranty.
eh, now i just have to get it into stock shape (i was running ICS)
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Solved
Just to let you know,
I put on a leaked version of android 4.0.3 and brought it to verizon.
they didn't notice the difference. they played with it for 2 hours. they tried changing the sim-card and did a factory reset at the very end.
the girl that was working with me told me that it's probably a problem because i did "clear data" (not even factory reset). I was listening to all of that without saying anything
got a replacement. it works fine and i'm happy.
thanks for the tips
I apologize if this has already been hashed out, but I have combed through the archives and didn't find any solutions.
I got my Tab last July. Right out of the box, it had some sort of screen issue... if I move it physically at all, the screen freezes and the touchscreen is unresponsive. I have to hit the power button off/on to get things moving again. It happens all the time, and basically makes it unpleasant to use.
This unit is unrooted, and has all the stock updates. Do you think rooting and trying a new ROM might fix my problem?
I've been trying to submit a repair request through Samsung, and it will not recognize my serial number.
We also have a Viewsonic G-Tab and a Nook Color, both rooted. It's frustrating when the tablets that cost half of what mine did work so much better...
Thanks so much for any and all help; I'm kind of at a loss these days.
Have you factory reset it? No success? If so, take it back to where you purchased it if you can. That's likely sounds hardware related.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Looks like its hardware issue, the sensors arent reading your touch
Hey guys. Im gonna try to make this short and sweet as it's 9AM and I havent gone to bed, not because of the phone but because I just finished my night shift.
Anyways the problem is that recently my phone stopped having sound. Like 0 sound. I can call people but I can't hear anything. I tried doing a normal recovery through settings. And it fixed it, for about 30 seconds. So what I did is I got a stock Rogers firmware and deleted EVERYTHING. I reinstated a firmware, pit file, etc and it STILL doesnt work. I think I've done everything thats possible by even using another stock Rogers ROM other than mine. Could be as stupid as being my SIM card? lol.
Any suggestions?
Worse case scenario: Reset to stock recovery, reset flash counter, send in for exchange. (Still under warranty) I wanted to try and fix this myself as it can take a few days to get the new phone
And now
When I am sending an SMS it takes a horribly long time for text to appear (Lag?) Like Ill take a few letters the phone will freeze, and if I keep pressing the letters, they'll all appear 3-4 seconds later when it unfreezes.
Call audio was a problem that was fixed by switching to a new kernel for me. I can suggest 4Aces, but flappjaxxx might work for you too.
For sms.... Maybe try a new keyboard? Or reboot if you haven't in a while to clear Ram. Last possible suggestion is over clock.
Don't know if this will work 100%, but hopefully it will help a little
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Dear all,
There's something wrong I don't understand with Samsung repair services and the sudden death problem found on the Galaxy S3.
One day, the touch screen on my phone stop working randomely for no reason, sometimes more than 15 times a day, depends on what I am doing. My phone is a GS3 with 16gb and I bought it just few weeks after it has been released. Then I tried to search on internet and found the 'sudden death problem' that many people are suffering with.
According to my use, I did not modified anything on my phone which mean it has never been rooted or something like this. Instead of that, I prefer to keep it clean and send it back to the Samsung repair services to fix this issue.
The problem is, after 2 requests from Samsung, the random problem of the touch screen was still there.
- The first time, Samsung kept my phone about 2 weeks and they said that they had just made a firmware upgrade. When I recovered my phone, I was very disappointed to see that Samsung did not fix the problem. Then I decided to send it back again.
- The second time, Samsung kept my phone 2 weeks more and when I recovered it, they said that nothing wrong has been found. Of course, I made a letter for them to explain clearly what was wrong with this phone. But they did not care about this problem.
So, I was very angry and don't know what to do. I recovered my phone and the problem was still there. Of course, I thought I can throw this expansive phone to the rubbish bin, but when I search over the internet if this problem can be fixed, I found that many solutions was explained clearly in many forums and all over the world.
At the same time, I met one other person who has got the same problem with the same phone and he told me when he called Samsung, they replied they don't want to accept phones with this kind of problem.
So my question is, why Samsung refuse to fix this problem which is under their responsability ? If many forums explain how to solve this issue, why Samsung repair services cannot do it by themself ? Many people are not an expert and are allergic to the idea of thinking that they should try to fix this problem by themselves!
It's amazing! Just tried to search over google by yourself and you will find that many people send their phone with the same problem and Samsung did not fix anything to solve it. This is is unbelievable !!!
Thanks.
Regards
Which country are you in?
http://forum.xda-developers.com/showpost.php?p=40403702&postcount=4
mikep99 said:
Which country are you in?
Click to expand...
Click to collapse
JJEgan said:
http://forum.xda-developers.com/showpost.php?p=40403702&postcount=4
Click to expand...
Click to collapse
I'm from France but the problem with Samsung repair service seems not only happen in my country.
For example, you can check here also ... and I'm sure you will find many other places where customers have problems with their GS3.
http://www.sammobile.com/2013/01/02/galaxy-s3-sudden-death-to-be-fixed-by-firmware-update/#.UOQyFuttoyY.twitter
http://www.androidetvous.com/2013/04/06/samsung-le-galaxy-s3-un-correctif-aux-effets-secondaires/#comment-21192
JJEgan said:
http://forum.xda-developers.com/showpost.php?p=40403702&postcount=4
Click to expand...
Click to collapse
Sorry Man, but this is an expansive phone and nobody seem taking care of this problem so here is one post with more explanation ... if necessary, you can delete the other post but very sorry for the double post.
Just trying to help other people which have the same problem and don't know what to do with their defective touch screen phone ...
Thanks for you understanding
Well man suggest a post in Question and Answers with symptoms of your problem may lead to a solution .
Your phone is not dead it does not have sudden death so your title is misleading ..
You have a problem with the phone FREEZING .
Suggest you start at the beginning and factory reset phone .
Then post the actual problem in Q&A along with your firmware details .
jje
JJEgan said:
Well man suggest a post in Question and Answers with symptoms of your problem may lead to a solution .
Your phone is not dead it does not have sudden death so your title is misleading ..
You have a problem with the phone FREEZING .
Suggest you start at the beginning and factory reset phone .
Then post the actual problem in Q&A along with your firmware details .
jje
Click to expand...
Click to collapse
The freezing problem seems coming from the emmc chip related to the sudden death as many people are talking about.
There are already many posts to solve that problem like here http://forum.xda-developers.com/showthread.php?t=2133401
so no need to add another question and answers for that issue.
My freezing issue is already fixed by me and not by samsung.
So if you've got the freezing problem and decide to send your phone to Samsung repair services, they will give it back to you with exactly the same problem. That's what happened to many people. Very strange and unusual from an after sale services, don't you think so ?
The repair centres probably don't know the difference between the update 7 sds fixes (that causes freezes a lot) or the newer fixes (XXEMB1 and newer) that freeze much, much less.
Samsung really should be pushing all carriers to release newer builds so the service centres can flash them and everyone can be freeze free. A lot of carriers are still pushing pre MB1 builds and the service centres can only flash the latest for each carrier.
The cause of the freezes is within the kernel anyway. Its not hardware so sending for repair is pretty pointless
Sent from my GT-I9300 using Tapatalk 2