Related
Hi
once again ppl i have a ? To ask has any of u had a loud clicking, like hard drive fail sound and the device goes very slow for a min while it scans files. i am now on my secound gs2 from phones4u first one i had completly died. so i think im not havin a good run so far, if any one ells is getting these problems please share.
Thanx :-(
My suggestion, take it back to them ASAP and reproduce the issue. They might have had a bad batch.
Just a thought.
BRONSON29 said:
Hi
once again ppl i have a ? To ask has any of u had a loud clicking, like hard drive fail sound and the device goes very slow for a min while it scans files. i am now on my secound gs2 from phones4u first one i had completly died. so i think im not havin a good run so far, if any one ells is getting these problems please share.
Thanx :-(
Click to expand...
Click to collapse
Is this your first Android phone? Have you installed something funky on it? Damaged it physically or submerged in water? More info is needed to really guess what the problem is.
dhruvmalik said:
My suggestion, take it back to them ASAP and reproduce the issue. They might have had a bad batch.
Just a thought.
Click to expand...
Click to collapse
You suspect a whole BATCH of FACTORY SECONDS?
OP did you but your phone off the back of some truck? AFAIK getting factory seconds from Samsung is not possible, they are destroyed.
kreoXDA said:
Is this your first Android phone? Have you installed something funky on it? Damaged it physically or submerged in water? More info is needed to really guess what the problem is.
You suspect a whole BATCH of FACTORY SECONDS?
OP did you but your phone off the back of some truck? AFAIK getting factory seconds from Samsung is not possible, they are destroyed.
Click to expand...
Click to collapse
Lol what an awful way of getting rid of phones that can be given to developers or other people like us.
Seriously, 4 times in the last 24 hours. Nothing to do with battery power left..
Come to think of it, I remember my ex-step-dad complaining of the same issue.
Anyways, is this...a thing that's known? A fixable thing?
SGSII GT-I9100, 4.0.3, I9100XXLPS, 3.0.15-I9100XWLP8-CL356487 [email protected] #3, IML74K.XWLP8
Rooted.
Please don't recommend a reset or wipe. Only did that a month ago and putting everything back on took forever..;-;
Even more randomly it will restart.
Very frustrating.
I think your problem is ''Sleep Of Death''. Read this two Thread http://forum.xda-developers.com/showthread.php?t=1616616 http://forum.xda-developers.com/showthread.php?t=1670600 . SORRY FOR MY BAD ENGLISH
Rizaria said:
Seriously, 4 times in the last 24 hours. Nothing to do with battery power left..
Come to think of it, I remember my ex-step-dad complaining of the same issue.
Anyways, is this...a thing that's known? A fixable thing?
SGSII GT-I9100, 4.0.3, I9100XXLPS, 3.0.15-I9100XWLP8-CL356487 [email protected] #3, IML74K.XWLP8
Rooted.
Please don't recommend a reset or wipe. Only did that a month ago and putting everything back on took forever..;-;
Click to expand...
Click to collapse
Maybe it's overload or overheating, unstable ROM/kernel, maybe it's a virus. There can be many reasons.
badbar said:
I think your problem is ''Sleep Of Death''. Read this two Thread http://forum.xda-developers.com/showthread.php?t=1616616 http://forum.xda-developers.com/showthread.php?t=1670600 . SORRY FOR MY BAD ENGLISH
Click to expand...
Click to collapse
I sure hope not. Looks like a complicated fix. But thanks.
Mariacci said:
Maybe it's overload or overheating, unstable ROM/kernel, maybe it's a virus. There can be many reasons.
Click to expand...
Click to collapse
The thing is, it's not doing anything at the time? Nothing that would overheat it. Also, it's very cold here right now, so weather wouldn't be overheating it either. The ROM/kernel have been fine until recently, neither seemed unstable. A virus...seems unlikely, but I'll install a virus scanner and have a looksie.
Rizaria said:
Please don't recommend a reset or wipe. Only did that a month ago and putting everything back on took forever..;-;
Click to expand...
Click to collapse
Why on earth would it take your forever?
Use use pro version of Titanium backup and you can restore all you backed up apps/app data in once go.
Re-stock device or re-install custom after wiping everything via recovery and if problem persists its likely a hardware issue, either main device or battery.
Didn't find a virus.
TheATHEiST said:
Why on earth would it take your forever?
Use use pro version of Titanium backup and you can restore all you backed up apps/app data in once go.
Re-stock device or re-install custom after wiping everything via recovery and if problem persists its likely a hardware issue, either main device or battery.
Click to expand...
Click to collapse
Well, I didn't have Titanium Backup Pro. So it took ages sifting through what apps I wanted, now that Google just puts them in there among a ****-ton of other apps I may have tried for a couple minutes before deleting.
I suppose.
Okay, wiped everything via recovery and flashed a new rom and all -chose [--VK--™] this time-'
Just about to leave for work and grabbed my phone. It had turned off. x: Now I'm worried.
At worst, you can use your warranty and exchange your phone for a new one.
Mariacci said:
At worst, you can use your warranty and exchange your phone for a new one.
Click to expand...
Click to collapse
Doubt it's still under warranty, and I've already done that once.
Sent from my GT-I9100 using XDA
Rizaria said:
Doubt it's still under warranty, and I've already done that once.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
warranty is without a limit
Mariacci said:
warranty is without a limit
Click to expand...
Click to collapse
If you say so. Really hoping it won't come to that though, don't wanna be without my phone for ages again.
Sent from my GT-I9100 using XDA
If the warranty deadline is not expired, you can try.
try removing your battery and replacing it firmly in place and snapping the cover on firmly into place.
I have had this issue since moving to the larger OEM Samsung battery kit occasionally and I feel it may be q seating issue with the battery, as this method solves it until it gets dropped or bumped about a few times.
Also Sleep of Death I believe requires a reset (7second power button hold) whereas my issue is resolved by turning the phone on normally (1sec power button press) hence how I found the battery issue..
just my experiences and $0.02..
It just randomly reset and took half the battery left with it. Bah. Seems to be the same issue as this topic. http://forum.xda-developers.com/showthread.php?t=1103087&page=14
Sent from my GT-I9100 using XDA
Aight so Im like 4 months in on this rooted life and i cant leave it alone lol. I was wondering if flashing too many times can lead to damage of the phone. and I dont know about yall but usually when i see a new rom or update i gotta try it out. this ish is addicting yo. My girl thinks I gotta problem hahahaha
Yes, technically flashing "madd" roms can eventually wear down your phone...provided you keep the phone well beyond what most do.
Sent from my SAMSUNG-SGH-I717 using XDA
erick161 said:
Yes, technically flashing "madd" roms can eventually wear down your phone...provided you keep the phone well beyond what most do.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
Aw damn. Aight thanx for the heads up.
Lol...on my Second Android Device (Moto Cliq) I was flashing for a good 2years. The only thing that damaged was the battery. But I got 2 brand new ones for $5 on Amazon. Well that being said, it all depends on how your phone is handled and how the tweaks are pushing the phone. How much are you pushing the CPU. What type of things you do to the phone...games, movies, reading... Everything contributes on how much life your device will have.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Double0EK said:
Lol...on my Second Android Device (Moto Cliq) I was flashing for a good 2years. The only thing that damaged was the battery. But I got 2 brand new ones for $5 on Amazon. Well that being said, it all depends on how your phone is handled and how the tweaks are pushing the phone. How much are you pushing the CPU. What type of things you do to the phone...games, movies, reading... Everything contributes on how much life your device will have.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Click to expand...
Click to collapse
Oh ok gotcha, yea I have back up batteries on deck so I should be good. As far as the usage I dont really push my phone to tough. I have my set cpu settings hooked up and my phone doesnt heat up all crazy like it use to so thats a good sign hahaha. I was just concerned about all the wiping and flashing. Thnx for the input mayne.
Lol at your girl thinking you got a problem, welcome to the club! My girl, friends, even my family except this one cousin that I introduced to android, they're always bugging out about not being able to get me on the phone, lol.
Dark Nightmare said:
Lol at your girl thinking you got a problem, welcome to the club! My girl, friends, even my family except this one cousin that I introduced to android, they're always bugging out about not being able to get me on the phone, lol.
Click to expand...
Click to collapse
hahahalol I feel you on that man
I have an htc inspire have had it since it was the new thing, and have flashed too many roms to count. The phone still works fine. I even used setcpu on it. but was careful on what settings I used.
Flashing too many times can def kill you phone. I destroyed the nand on my first n1 a couple months ago doing that. Granted i was working on ics and flashed it several hundred times it a short period (~5 times a day for 2 months).
Basically you shouldnt worry only when you get up to 2,3,4 hundred flashes do you start having problems with the nand wearing out.
I've never had any problems with flashing any of my phones... And I would flash 50-60+ times a day when making roms... (I had to have it just right)
Sent from my HTC_Amaze_4G using XDA
texasice said:
Flashing too many times can def kill you phone. I destroyed the nand on my first n1 a couple months ago doing that. Granted i was working on ics and flashed it several hundred times it a short period (~5 times a day for 2 months).
Basically you shouldnt worry only when you get up to 2,3,4 hundred flashes do you start having problems with the nand wearing out.
Click to expand...
Click to collapse
Yea I def dont flash that many times a day lol...ill keep that in mind tho
I remember this question being asked a few years ago and someone answered that NAND memory can be flashed about a 1000 times before you start to wear it out. The guy seemed quite knowledgeable at the time..
Hope this helps..
johnk1973 said:
I remember this question being asked a few years ago and someone answered that NAND memory can be flashed about a 1000 times before you start to wear it out. The guy seemed quite knowledgeable at the time..
Hope this helps..
Click to expand...
Click to collapse
No doubt...thnx
Sent from my HTC_Amaze_4G using XDA
Funny how same question come up again and again.
http://forum.xda-developers.com/showthread.php?t=1625470
IMO, it’s somewhere between 10,000 and 200,000 thousand writes per block.
Depends on flash quality a lot (i.e. manufacturer)
Tonight was second time in about one week when my phone shut itself down at night. Because of that I slept in both times Both times it was connected to charger and battery was full, also there was a lot of updated apps (notifications in status bar). Right before first time this happened I recovered from soft brick. First after recovering phone didn't work well it use to freeze on higher load so I re-installed stock ROM one more time and everything seemed fine.
Now I wonder if it's software or hardware issues. Any ideas?
Cheers in advance.
kaiseris said:
Tonight was second time in about one week when my phone shut itself down at night. Because of that I slept in both times Both times it was connected to charger and battery was full, also there was a lot of updated apps (notifications in status bar). Right before first time this happened I recovered from soft brick. First after recovering phone didn't work well it use to freeze on higher load so I re-installed stock ROM one more time and everything seemed fine.
Now I wonder if it's software or hardware issues. Any ideas?
Cheers in advance.
Click to expand...
Click to collapse
Did you UV/UC your device? And which rom/kernel are you on?
Sent from the Matrix
Donnie Sins said:
Did you UV/UC your device? And which rom/kernel are you on?
Sent from the Matrix
Click to expand...
Click to collapse
No, I didn't UV/UC. I was on rooted stock kernel.
Made factory reset today and installed custom JB ROM today to see if it helps.
I think your problem is a software related one, try using the latest stock Rom, also it may be induced bya virus or a new program which you May have installed, if this didn't help them you should think of a hardware problem.
iper said:
I think your problem is a software related one, try using the latest stock Rom, also it may be induced bya virus or a new program which you May have installed, if this didn't help them you should think of a hardware problem.
Click to expand...
Click to collapse
I was using 4.0.4 official ROM (NEE). And most of my apps are from Play store and only few from a reputable forum.
But as I said, I wiped everything today and installed a different ROM. If everything's OK for a week it will be clear that it was a software glitch.
Maybe it's tired?
****Non of this is of any importance. Just chill the f**k out and relax****
One week after installing custom ROM my SGSII has shutdown at night again. Like last times it was connected to a charger but this time there were no updated apps. So it's not ROM's fault because it happened with custom and stock ROMs.
Is it possible that soft brick damaged some part of phone's hardware (internal flash memory)? When recovering from brick I re-partitioned it.
...
MistahBungle said:
1) There's no such thing as a 'soft brick'. Your phone is either bricked (unfixable other than by authorised repairer/JTAG) or it ain't.
2) Highly unlikely anything firmware related would cause hardware issues like that.
It may well be a hardware issue given it's happened on different roms. If you're still on stock & haven't reset the flash counter, do that & send it in to Samsung/authorised repairer to be looked at assuming your warranty is still good. If it isn't, take it to a local mobile repair shop & have them take a look (if you've gone back to a custom rom, reset the flash counter & back to stock).
Click to expand...
Click to collapse
There's no warranty, therefore I won't be taking it to service center just to hear it needs new motherboard etc. because it'll cost me almost same as to buy another SGSII.
At this moment I'm only interested if there's anything I can do by myself. If not it's time for a new phone I'm afraid. The phone is still perfectly usable but I don't want to risk sleeping in and being late for work and I don't want to buy an alarm clock.
Common sense dictates you try a different battery.
TheATHEiST said:
Common sense dictates you try a different battery.
Click to expand...
Click to collapse
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
...
MistahBungle said:
Do a completely clean install of stock (format cache, data, system, & internal sd card in CWRecovery first, Odin flash after), do not restore any apps (or app data with the exception of contacts/calendar/call logs/sms) via Ti or whatever, clean reinstall a few apps at a time, test for a day or two. Install a few more apps, test for a day or two. And so on.
If it's still happening after you do that, "it's time for a new phone" in your words.
Click to expand...
Click to collapse
Thing is that when the phone got bricked I had no backup of any kind and since internal storage was re-formated we can say that it was fully wiped. I installed stock ROM first. But phone was rebooting on higher load so I did factory reset and wiped dalwik and data. Reinstalled stock ROM again (even re-downloaded to make sure it's not corrupted). This time it wasn't rebooting. But after a couple of night shutdowns I decided to try a custom ROM. I did a full wipe (including internal storage) before installing it. Clearly it didn't help
BTW night shutdown happens about once in a week.
kaiseris said:
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
Click to expand...
Click to collapse
I tried a different battery and Ive noticed when Ive connected it to the charger,a couple of times my phone has switched off as I was facing the screen wanting my sim pin.
This doesnt happen with my original battery.
So it must be the battery.
theunderling said:
I tried a different battery and Ive noticed when Ive connected it to the charger,a couple of times my phone has switched off as I was facing the screen wanting my sim pin.
This doesnt happen with my original battery.
So it must be the battery.
Click to expand...
Click to collapse
But I'm using my original battery. Also like I mentioned earlier all this started after the brick. Therefore I don't think it's the battery.
P.S.Before SGSII I owned HTC Desire for couple of years. I flashed and re-flashed it again and again, never had a brick etc. But when I decide to flash a custom ROM on SGSII for the first time phone gets bricked and even after recovering from brick phone is still f*****-up. Don't get me wrong I love this phone, it's better in every way but it's not exactly "flash friendly". Forums are full of stories of bricked SGSII. That makes me thinking should I choose a Samsung device if I'll be forced to buy a new phone...
kaiseris said:
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
Click to expand...
Click to collapse
Simple, Because you cant run your phone just via charger, it goes from charger to device via battery so if your battery is faulty you could have lost power to device.
kaiseris said:
Thing is that when the phone got bricked
Click to expand...
Click to collapse
You're devcie was never "bricked". If it was your devcie would simply not power on or if it did it wouldnt go into download or recovery mode via buttons or jig.
If you can do the above yor devcie is not bricked. There is no such thing as a "soft brick", that is just a label n00bs like to use as a label for when they cant boot to system. Liek when they get a boot loop etc.
kaiseris said:
But I'm using my original battery. Also like I mentioned earlier all this started after the brick.
Click to expand...
Click to collapse
No it didnt.
kaiseris said:
P.S.Before SGSII I owned HTC Desire for couple of years. I flashed and re-flashed it again and again, never had a brick etc.
Click to expand...
Click to collapse
And you haven't on SGS2 either.
kaiseris said:
But when I decide to flash a custom ROM on SGSII for the first time phone gets bricked
Click to expand...
Click to collapse
No it doesnt.
kaiseris said:
and even after recovering from brick phone is still f*****-up.
Click to expand...
Click to collapse
No you didnt, you simply re-flashed a rom. When you're bricked this cannot be done (without hardware access/replace) hence the word "bricked"[/QUOTE]
kaiseris said:
Don't get me wrong I love this phone, it's better in every way but it's not exactly "flash friendly".
Click to expand...
Click to collapse
Wrong, its very flash friendly. Only thing you need to look out for is wiping data on leaked stock kernel.
kaiseris said:
Forums are full of stories of bricked SGSII.
Click to expand...
Click to collapse
1000% Untrue. They are full of stories from n00bs who "think" they have bricked their device, ie all the silly "soft-brick" topics.
My advice to you would be to check battery pins for bends or corrosion and also swap battery and see if you get different results.
Before any of this though you should try a kernel cleaning script, flash stock rom via ODIN and then flash Siyah kernel.
Jeez man! Why do you waste your an my time typing this long but pointless post?! To show how "l33t" you are? If so please stay away from this thread.
As for battery, if it is faulty why it's still fully charged? Also why does it act-up just once in a while? IMHO battery is quite a simple thing, either it charges or not. It looses it's capacity over time. Mine is about six months old and still lasts me about 36 hours.
kaiseris said:
Jeez man! Why do you waste your an my time typing this long but pointless post?! To show how "l33t" you are? If so please stay away from this thread.
As for battery, if it is faulty why it's still fully charged? Also why does it act-up just once in a while? IMHO battery is quite a simple thing, either it charges or not. It looses it's capacity over time. Mine is about six months old and still lasts me about 36 hours.
Click to expand...
Click to collapse
Because I was trying to help you [email protected] ungrateful moron! How on earth was it trying to sound "l33t" (By the way its "1337").
Your problem is that you create a thread about a problem you have with device and then dont even listen to what you get told with regards to advice from multiple people, ie check rom/kernel/battery. What the hell do you expect any of us to do give you some magic words you can say to solve your problem?
What I wrote was correcting your misconceptions and giving you on advice on how to resolve your issue, Did you even bother to read what I wrote at bottom??
Also you're been very narrow minded if you think that the only symptoms of a faulty battery is if it cant charge or hold charge. Symptoms can also include random drops of output which result in your phone losing power and rebooting or powering off which is exactly what is happening to you. Now I'm not saying this is your exact problem but the fact that you are ignoring this possibility shows how much of a fool you are been especially when been hostile towards people who are trying to "waste their time" helping you.
If you dont want our advice then I suggest you GTFO and find another site to post your problem on.
TheATHEiST said:
n00bs
Click to expand...
Click to collapse
TheATHEiST said:
n00bs
Click to expand...
Click to collapse
TheATHEiST said:
[email protected] ungrateful moron
Click to expand...
Click to collapse
TheATHEiST said:
a fool you are
Click to expand...
Click to collapse
Wow, you're a real "keyboard cowboy". Do you tell same thing to people you don't know in real life? I bet you don't.
I already wrote this but I will repeat it one more time. I did full wipes, flashed a few different ROMs and kernels since this problem started. It didn't affect the problem in any way!
TheATHEiST said:
Now I'm not saying this is your exact problem
Click to expand...
Click to collapse
Reading your posts makes me think opposite. I will repeat myself shutdowns started right after recovering from "soft brick"/"NAND rw corruption" (which ever suits you better). Other reason I don't believe it's battery's fault is that I have never heard about:
TheATHEiST said:
random drops of output
Click to expand...
Click to collapse
in otherwise perfectly working battery.
Like everyone else I owned a bunch of cellphones, laptops, cordless drills, MP3 players and other battery-powered devices but never had such problem or heard about anyone having this exact problem. Would you care to elaborate about it?
TheATHEiST said:
GTFO and find another site to post your problem on.
Click to expand...
Click to collapse
I'm not going to do that only because there are a few "anal" people in this great community.
Ok, you're obviously an idiot and its pointless trying to help you. Good luck trying to find somebody who will help you now after showing how much of a **** you are to people trying to offer advice.
I'm off to play on my fully working i9100.
Bye.
I just checked my phone using "eMMC Brickbug Check" by "Vinagre" (available on Google Play Store) and it turns out that I have an insane chip.
Screenshot attached.
I know that Android 4.1.2 is supposed to fix this issue as it somehow prevents from phone to go into "Sudden Death" but still that doesn't change the fact that the chip in my phone is faulty. Plus people with Android 4.1.2 XXELLA still are experiencing brick bug!! There are tons of posts all over the internet to prove that. I have just 2 months of warranty left and sure my phone is working fine now, but there is no guarantee that it will continue to do so even after the warranty is over. What happens if my phone dies after it's out of warranty? I'll be screwed, right? What do you guys think I should do? Would Samsung Care acknowledge the result from an app & change my chip or offer me a replacement?
Please help me ASAP. I'll be very very grateful to you.
No, they won't fix it as there is nothing wrong - yet.
absolutely nothing you can do
:'(
boomboomer said:
No, they won't fix it as there is nothing wrong - yet.
Click to expand...
Click to collapse
Glebun said:
absolutely nothing you can do
Click to expand...
Click to collapse
Thank you for your prompt replies. I guess I'm just a sitting duck now. :'(
saurabh_goyal93 said:
Thank you
Click to expand...
Click to collapse
there's a button for that
saurabh_goyal93 said:
I just checked my phone using "eMMC Brickbug Check" by "Vinagre" (available on Google Play Store) and it turns out that I have an insane chip.
Screenshot attached.
I know that Android 4.1.2 is supposed to fix this issue as it somehow prevents from phone to go into "Sudden Death" but still that doesn't change the fact that the chip in my phone is faulty. Plus people with Android 4.1.2 XXELLA still are experiencing brick bug!! There are tons of posts all over the internet to prove that. I have just 2 months of warranty left and sure my phone is working fine now, but there is no guarantee that it will continue to do so even after the warranty is over. What happens if my phone dies after it's out of warranty? I'll be screwed, right? What do you guys think I should do? Would Samsung Care acknowledge the result from an app & change my chip or offer me a replacement?
Please help me ASAP. I'll be very very grateful to you.
Click to expand...
Click to collapse
The fix for the SDS is not in the Firmware but inside the Kernel. So you could use the newest Firmware but if your Kernel is not SDS Fixed then you still can have the SDS easily. I`ve seen a lot of cases where people used a firmware that they thought is safe but if you ask them what kernel they used you often get a reply that they used some outdated kernel like Siyah 1.8.6 which has not the Samsung fix for the SD included.
I don`t know of any solid case where a Sudden Death occurred where people were using a fixed Kernel.
Also sometimes you have cases where people first experienced the Sudden Death Syndroms like a lot of freezing or sudden reboots and then they decide to come to XDA and afterwards they flash a fixed kernel in hope that this will fix the problem(s) but then it`s often already to late. If you already have the symptoms chances are good that your phone will die anyway.
However if you know a case where the user had no symptoms at all and were using a fixed Kernel then please post a link to it because such a case is of big importance.
firmware includes the kernel
Glebun said:
firmware includes the kernel
Click to expand...
Click to collapse
Yes, but many people flash custom Kernels after they flash a Sammy Firmware.
Scarface1991 said:
Yes, but many people flash custom Kernels after they flash a Sammy Firmware.
Click to expand...
Click to collapse
Well, it is true that many peoples are removing their car security and safety devices.
so what? There are two alternatives:
1. They know what they are doing and what, therefore they are considering the risk;
2. They are do not know what they are doing. In this case, bricking their phone is hard, but only way to learn.
The choice is yours, boys and girls.
I thing that you can buy warranty time but I am not completely sure about that.
first, that your phone has the faulty chip, does not imply that our phone is going certainly going to die, if that was true, there would be millions of dead devices around the world, and that is not the case, as many things of life, it is a matter of luck, if its going to happen it will, if not, it wont, many users reported the issue at 5 or 6 months of use, if you pass this time period, chances are at your favor, mine is 6 months old, at the 2nd month I became aware of the sudden death issue, and flashed a rom and kernel with the fix, now, I think m PHONE IS OUT OF TROUBLE, i HAVE 7 months left of warranty period, so, dont torture yourself, use your device, and think of the best
From all that I've read about SDS you can hopefully avoid it altogther by using the latest firmware, even with the old firmware it seemed to happen more often to those who charged their phones overnight or got them too hot - although some failures seemed to be totally random.
I've always charged my batteries in an external charger, have power saving mode on and point an A/C outlet at the phone if used in the car windscreen to navigate. As a result it is always cool to the touch, electronics hate high temps - even 10 degrees higher than 'normal' can halve the lifespan of standard components, the memory chips in these phones are far from standard.
If you are too scared of SDS you can hard brick your phone and then give the phone to the service center so they will replace the insane chip free of cost
Sent from my GT-I9300 using xda premium
boomboomer said:
From all that I've read about SDS you can hopefully avoid it altogther by using the latest firmware, even with the old firmware it seemed to happen more often to those who charged their phones overnight or got them too hot - although some failures seemed to be totally random.
I've always charged my batteries in an external charger, have power saving mode on and point an A/C outlet at the phone if used in the car windscreen to navigate. As a result it is always cool to the touch, electronics hate high temps - even 10 degrees higher than 'normal' can halve the lifespan of standard components, the memory chips in these phones are far from standard.
Click to expand...
Click to collapse
Lol, far from standard?
Anyways, thank you for your reply but that's just a workaround, not a fix. I'm planning to keep this phone for another 2 years and if the chip is faulty, there's a very high chance that it'll fail sometime in the near future and I can't afford to change the whole motherboard.
saurabh_goyal93 said:
Lol, far from standard?
Anyways, thank you for your reply but that's just a workaround, not a fix. I'm planning to keep this phone for another 2 years and if the chip is faulty, there's a very high chance that it'll fail sometime in the near future and I can't afford to change the whole motherboard.
Click to expand...
Click to collapse
If you use a Kernel with the fix then the chance is not very high. In fact until this day I haven't seen a solid case where a S3 with the fix died all of a sudden. While before the fix devices were dying left and right.
nikhil18 said:
If you are too scared of SDS you can hard brick your phone and then give the phone to the service center so they will replace the insane chip free of cost
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
no, that's a felony
Glebun said:
no, that's a felony
Click to expand...
Click to collapse
I was always wondering, isn`t it also a kind of felony to reset the flashing counter via Triangle Away and then to play dumb if you get your phone hard bricked some time later?
if it was your fault and you claim it bricked by itself, then yeah, that's also insurance fraud, which is a felony
Yeah I thought so too,
haha I know so many cases here at XDA where people bricked their phones and many people just advised them to bring it to the service centre and to play dumb, so that they say that suddenly their phone wouldn't turn on.
Couldn't agree more with both of you. It's a felony, everyone is aware of that, but lots of people still do it, because at the end of the day, all they want is their phone back. Fully working.