**** SAMSUNG HAVE APPLIED A SUDDEN DEATH FIX VIA A SOFTWARE UPDATE****
STOCK KERNEL: XXELKC AND NEWER
STOCK RECOVERY: XXELKC AND NEWER
ALSO ANY CUSTOM KERNEL AND RECOVERY THAT ARE BUILT FROM THE UPDATED SOURCES. THERE HAVE BEEN CASES OF SDS ON DEVICES THAT HAVE UPDATED BUT TO WHAT EXTENT THE DAMAGE WAS AT ALREADY BEFORE FLASHING WE DON'T KNOW.
WHO'S AFFECTED?
It seems that at the moment the only devices that have suffered from SDS are the 16GB version with:
eMMC: VTU00M
FW Rev: 0xF1
To check your eMMC version download eMMC Brickbug Check from Google Play.
What you want is the eMMC version and the FW Rev.
THE FIX
Samsung have now released a Sudden Death Fix via a patched Kernel and Recovery in latest firmware. Firmware Version: XXELKC
Simply update OTA or download XXELKC firmware (or newer) from sammobile.com and flash using Odin.
You need both the stock recovery and kernel installed for it to work properly, or a custom kernel and recovery built from the updated sources
ie Latest Perseus Kernel and PhilZ Recovery are examples
LINKS
For more info about SDS, who could be effected and how to fix check out this awesome thread by rootSU
For a detailed look at how the fix works check out this thread here.
WARRANTY
For those of you in Europe who have rooted your phone it appears that this doesn't void warranty. Check this thread for more info.
Also this website could prove very handy for anyone with a European or UK handset that has died.
Okay, here's what just happened to me:
I went to sleep in the night with my phone's battery at around 29%. I just woke up and my phone's home button wouldn't respond. Then, the power button wouldn't respond! I took the battery out and put it back in. It still wouldn't respond! So, I plugged the charger in and then it showed me that it had begun charging. I turned the phone on and as soon as it reached the lock screen, it turned itself off. It did that twice more so I decided to let it rest. Now, it turns on. (>_>)
Apparently, 29% of its battery was somehow consumed last night. I really don't know how!!!! My wifi was on,it seems, but around 30% battery drain in just a few hours?!! That's insane! I'm on stock DL4. Not even rooted!
So it's not a "death" case, per se, but I had a really bad scare.
What happened: Went to bed, left phone on charge, woke to the green "fully charged" light, but no response to buttons. Pulled the battery to make it reboot, and now nothing. Neither download nor recovery modes, no charging light, nothing. It's off for repairs.
What ROM/Firmware: Wanam's J5 (which I'm convinced had nothing to do with it.)
What kernel: stock
OV or UV: Nooooo
Where phone was made: No idea
Where battery was made: stock; no idea
Seems like a weakness somewhere on the motherboard. Mine died on charge about a month ago. No led no nothing bought in late May. New motherboard working fine. Hoping the problem is identified and fixed now and I don't have the same **** again in three months time.
My story started last Tuesday night. My S3 was working fine: used it as satnav getting to work for night shift and used it a few times at work until I checked it at approx 9:30pm (about three hours into shift) and it was dead - nothing would make it respond.
Got home next morning and my caring wife asks me if it's still the same - I dishearteningly relied that it was. Then she announces that hers was now dead! She had been using hers normally the night before, as I had. She had plugged it in to charge overnight and when she woke in the morning the green light was on, but she couldn't turn it on - she did battery pull, etc, but nothing would revive hers either.
Clearly something has killed our S3's, but not spontaneously as we were in different places at the time of failure. Mine had been happily charging whist I traveled to work and it had over 80% the last time I had noticed / used it before it died - my wife's just died on the charger overnight at our house.
Two dead S3's in the space of 9 hours and I have no idea why...
Both were stock unrooted international models purchased from carphone warehouse at the same time. Both had the recent JB update too (I did both via Kies when it was released).
The only common element I consider could be a cause is the charger we use in our house (but as mine died some time later after being used for several hours away from my house I really don't see any technical explanation for it).
I'm baffled - Carphone warehouse faults tracker now says they have fixed them both and they are awaiting dispatch to our store for collection - maybe they can then offer soom explanation of thefaults / causes.
Either way I reckon I'll bin the "common" charger as a "just in case"!
That's really odd that both yours and your wife's phones suddenly died at around the same time.
Do you share a charger?
Can let us know some details about both phones, where phones and batteries were made etc
It appears, from what I can gather, that it is a hardware fault. The ROM and kernel don't seem to matter. People's phones are dying regardless of which ROM they're running.
At least CPW have fixed both your phones for you
Maybe you could ask if they have had a few customers bringing back dead phones?
It'll be interesting to know what their technicians say about it.
Sent from my GT-I9300 using xda app-developers app
this is happening a lot to people... I hope Samsung do something about this!!
Sent from my GT-I9300 using Tapatalk 2
What happened: Used as Satnav, it was charging on a 1A car charger, battery probably pretty full. Brought it in tried to turn it on and nothing happened. Had a white pulsing LED, after battery pull no reaction.
What ROM/Firmware: CM10
What kernel: Can't remember
OV or UV: Nope
Where phone was made:
Where battery was made: Standard battery but I do use a Anker battery as well, can't remember if it was in the phone at the time.
On the bright side, I have just got it back from Samsung who repaired it without question. They have also given me a 32GB model instead of the 16GB I had before.
Very happy dervish.
I know it is a hassle, but could people please post where their phone came from (language which was default on phone might be good, for example mine was Greek). Might allow us to isolate a particular region/batch
tqgia2 said:
I know it is a hassle, but could people please post where their phone came from (language which was default on phone might be good, for example mine was Greek). Might allow us to isolate a particular region/batch
Click to expand...
Click to collapse
My 2 S3's were purchased at the same time from mobiles.co.uk (CPW) - English language by default, unlocked and with no network branding. I had not tampered with these devices in any way. They are totally stock handsets running JB (updated via Kies). They were only used with the Samsung chargers too. Mine had approx 100 apps on it, but my wife hardly had any on, just about twenty or so.
I'll update this page once I get them back so we can share the causes / fixes in my case
What happened:
Phone was charging on Zenis dock. Checked it at 95% and returned 1 hour later to find it stuck on Samsung boot screen. Had to remove battery to unfreeze it. Phone would not boot and stuck on Samsung screen. Would only boot into Download mode but would not accept any relash of OS via Odin. Reflash attempts met with Invalid PIT partition fault. Tried to reflash a PIT as advised on XDA but with no success. On connection to charger phone displayed grey battery graphic.
Handed into Samsung service centre who confirmed battery was completely dead and that new battery allowed phone to turn on but no ability to reload software. Phone now has been sent to Samsung in the UK
What ROM/Firmware:Stock T Mobile 4.1
What kernel: STOCK
OV or UV: Nope
Where phone was made: UK model bought in June 2012 from Mobiles.co.uk
Where battery was made: Dont Know
Phone is English language version and has run fine for months. It was updated via OTA to 4.1 about 2 weeks ago when Tmobile released the ROM. since then I re-rooted it but have never flashed any other ROM.
What happened: Picked up phone after its usual overnight charge , was showing the normal green "full charge" light but phone was completely dead - black screen, no download or recovery mode via key combo, no response to jig.
No self-reboot, freeze or anything that would indicate a problem prior to phone dying.
What ROM/Firmware: official UK ICS, (can't remember the firmware number now, but whatever the latest official UK unbranded was by mid-October)
What kernel: stock (rooted with cf-root)
OV or UV: Nope
Where phone was made: just says "made by Samsung"! UK sim-free, received 16th June
Where battery was made: Original Samsung battery. Made in Korea, assembled in Vietnam
Anything else that could be of use:
Always left my phones and other toys to charge overnight, been doing the same with the S3 since getting it on 16 June, using the Samsung charger that came with it. No longer doing that with the S3 just in case!
Phone came back with new innards, battery is the one the phone went in with.
As to really getting to the bottom of it, I guess only someone at Samsung might be able to tell us why so many S3 are committing suicide...
Sent from my GT-I9300 using xda premium
Did you guys tried a electric shock?
Maybe your gs3 back to life?
Hit thanks when its okk :thumbup:
Sent from my GT-I9300 using xda app-developers app
What happened:
I just flashed Wanam 4.2 ROM. Booted up normally. Then i proceed to install TiBu, and restore apps + data. After 10mins, I came back just to check the progress. It was dead.
What ROM/Firmware: Wanam 4.2
What kernel: Stock
OV or UV: Nope
Where phone was made: It wrote, "Made in Korea by Samsung"
Where battery was made: "Cell made in Korea, Assembled in Vietnam"
I sent my device to service centre, they repaired it within 2 working days.
Sent from my GT-I9300
romeo57 said:
Then i proceed to install TiBu, and restore apps + data.
Click to expand...
Click to collapse
This is a stretch, but I wonder if Titanium could have anything to do with the bricking. I had an auto-backup scheduled in the middle of the night, after which the phone died. I don't know there's a connection, but interesting you mentioned TiBu.
UncleBeer said:
This is a stretch, but I wonder if Titanium could have anything to do with the bricking. I had an auto-backup scheduled in the middle of the night, after which the phone died. I don't know there's a connection, but interesting you mentioned TiBu.
Click to expand...
Click to collapse
Neither mine nor my wife's phone had Titanium backup installed - not saying it wasn't that in your cases, but wasn't in mine
I'm not sure if it's relevant but I checked the stock charging voltages on my S2 and it's a Wall:650Mah, USB:450.
The default on S3 is the same for USB(450Mah) but the wall charging voltage default is apparently 900Mah!
I know the battery is higher capacity but my S2 has a 2100Mah Samsung battery in it and charges just fine @ 650Mah.
Maybe 900Mah is just too high?
I'm no electronics expert so I could be talking rubbish but it's an idea.....
Sent from my GT-I9300 using xda app-developers app
Obagleyfreer said:
I'm not sure if it's relevant but I checked the stock charging voltages on my S2 and it's a Wall:650Mah, USB:450.
The default on S3 is the same for USB(450Mah) but the wall charging voltage default is apparently 900Mah!
I know the battery is higher capacity but my S2 has a 2100Mah Samsung battery in it and charges just fine @ 650Mah.
Maybe 900Mah is just too high?
I'm no electronics expert so I could be talking rubbish but it's an idea.....
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Where did you check the stock charging voltages bro? I experienced something almost to this effect except that I woke up this morning and the menu and return keys were lit up (screen was off) , tried pressing some buttons but nothing responded. I then long pressed the power key and then it booted up normally and since has been working ok. Was so worried and paranoid at the time! I'm from South Africa if it's any use. Just to make sure these scares/sudden death issues are not just in one continent/country.
Sent from my GT-I9300 using xda premium
Password1234 said:
Where did you check the stock charging voltages bro? I experienced something almost to this effect except that I woke up this morning and the menu and return keys were lit up (screen was off) , tried pressing some buttons but nothing responded. I then long pressed the power key and then it booted up normally and since has been working ok. Was so worried and paranoid at the time! I'm from South Africa if it's any use. Just to make sure these scares/sudden death issues are not just in one continent/country.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Well it's not very scientific but I use Siyah Kernel on both my S2 and S3 and just checked the default settings on there.
Actually Gokhan states that the stock charging voltage for a wall charger on the S3 is 1000Mah! (Siyah default). But another member on here (an electronics professional) said it's 900Mah so I just went with that.
It might be over kill but to be on the safe side I have lowered the voltages in Stweaks down to 900Mah and 450Mah and I am only charging my phone through USB until we figure out what is causing this problem.
It seems that this issue is worldwide, it's not specific to country, Android firmware version, Kernel etc
It seems this is totally random and can happen without warning to anyone, scary stuff.
dervish666 said:
What happened: Used as Satnav, it was charging on a 1A car charger, battery probably pretty full. Brought it in tried to turn it on and nothing happened. Had a white pulsing LED, after battery pull no reaction.
What ROM/Firmware: CM10
What kernel: Can't remember
OV or UV: Nope
Where phone was made:
Where battery was made: Standard battery but I do use a Anker battery as well, can't remember if it was in the phone at the time.
On the bright side, I have just got it back from Samsung who repaired it without question. They have also given me a 32GB model instead of the 16GB I had before.
Very happy dervish.
Click to expand...
Click to collapse
I hope mine breaks and I get a free 32GB model!!
Related
Update - After 2 months I couldn't take it any more so I sold it and actually got a rating of "good". The other solution involved a sledge hammer. I can't believe they didn't notice the 1 hour battery life. More proof that quality control worldwide is going down hill. Apologies to who ever gets mine as a refurbished unit or parts from it.
Screenshots
http://forum.xda-developers.com/album.php?albumid=6825
Battery Life from 100% to 0%
ICS .11 & .17 - 6 to 8 minutes (Pic 1)
ICS .21 - 35 to 52 minutes (Pic 5)
ICS .24 - 50 to 65 minutes (Pic 11)
Bug count
RR & Boot Loop - once on may 14th after 2 months on ICS
Battery meter stuck at 100% - 4 times
Irregular charge and discharge cycles - lost count
Battery meter continues to go up a few % after charger is unplugged - lost count
Screen flickered - 8 times
Screen unresponsive / no input - 11 times
No sound what so ever - once
Irregular charging ping sound - lost count
ICS .24 - Finally got over 1 whole hour of battery life from a full charge.
ICS .21 - Since the 9.2.1.21 update I had it 4 times total, it's been alternating with another bug where it goes from charged to zero battery and shuts down the second I unplug the charger. The infinite power bug must only be triggered by OTA update because I tried reinstalling the .21 firmware. The zero battery "bug" could be the result of the infinite power bug allowing the tablet to actually stay on long enough to completely drain the battery. Since .11 update the charging ping sometimes stutters and sometimes plays half a ping and stops. Just had a new bug of no charging ping. The tablet and the sound was on at the time. Battery was at 82% and icon changed to charge mode but no ping sound.
ICS .11&.17 - battery drain from 100% to 0% in about 7 mins and charges up in about the same amount of time. Had this bug for over a month from march onwards. I first got the infinite power bug after upgrading to ICS, it's where the battery meter stays at 100% for hours on end without being plugged in for charging.
My TF101 is from the B30 batch.
I do not have the dock.
I haven't used the camera since HC and I just noticed there is dust on the INSIDE of my case after the "repair". There's no way to clean it except to open it myself. The trim is also now separating a bit from the main body on the top left and bottom left. When I got it back from the repair center it was just a little on the left side only.
Things I have tried
Downgrading to HC, but method was very old and likely not a complete downgrade as it did not work. Battery status wipe, Reboots, factory data resets, cold boots, changing various settings, etc. I sent it in for repair which was a waste of shipping costs. Emailed ASUS twice, response time is longer than 1 week. Calling is much faster but same results no one knew if it was hardware or software problem. After sending it in for repair the left side of my TF101 looks like it had been spudged open so they could have already check the hardware. Dragging around a 12FT extension cord is still currently the best solution I've come up with.
Thanks for making a dedicated thread!
Suggestion: Throw a couple more keywords in the title to help others find it. Eg: based on your symptoms, maybe add something like "battery meter issues, shutdown when unplugged from charger" or something similar.
did you try wiping the device?
I managed to pre order my TF101 a full week before the official release date. Now it's come back to bite me in the rear end cause my warranty is up today. I have the service number and RMA from march so maybe they will still honor it if it turns out to be a hardware issue.
Nullinvoid said:
did you try wiping the device?
Click to expand...
Click to collapse
That would probably be my first step as well, if we assume it's not a hardware problem.
knoxploration said:
That would probably be my first step as well, if we assume it's not a hardware problem.
Click to expand...
Click to collapse
Do you guys mean the factory data reset cause I tried that at least about 25 times by now in the span of a month.
yanbo2012 said:
Do you guys mean the factory data reset cause I tried that at least about 25 times by now in the span of a month.
Click to expand...
Click to collapse
Yep. Have you tried doing a reset and supplying a brand-new Google account, so that it doesn't immediately copy any old data to the tablet? (Or even just not supplying an account or connecting to WiFi / Bluetooth at all, so it's 100% stock)?
Has it ever had a custom ROM or been rooted?
knoxploration said:
Yep. Have you tried doing a reset and supplying a brand-new Google account, so that it doesn't immediately copy any old data to the tablet? (Or even just not supplying an account or connecting to WiFi / Bluetooth at all, so it's 100% stock)?
Has it ever had a custom ROM or been rooted?
Click to expand...
Click to collapse
The bug occurs even if no account is entered. Wifi, gps, bluetooth on or off it still happens. I had it rooted to overclock on android 3.2.1 I rolled back to 3.0.1 to unroot and get ICS, quite regretting that decision as it ran fine except for a few browser crashes which doesn't seem like a big deal now. I also tried downgrading to 3.0.1 from ICS, still had the bugs. It's running stock ICS right now and the browser rarely ever crashes.
did you try up up down down left right left right b a start?
Sorry, couldn't resist....
gee one said:
did you try up up down down left right left right b a start?
Sorry, couldn't resist....
Click to expand...
Click to collapse
If it had a game controller attached I would have tried that also.
yanbo2012 said:
The bug occurs even if no account is entered. Wifi, gps, bluetooth on or off it still happens. I had it rooted to overclock on android 3.2.1 I rolled back to 3.0.1 to unroot and get ICS, quite regretting that decision as it ran fine except for a few browser crashes which doesn't seem like a big deal now. I also tried downgrading to 3.0.1 from ICS, still had the bugs. It's running stock ICS right now and the browser rarely ever crashes.
Click to expand...
Click to collapse
How did you downgrade? It's my understanding that some methods leave the kernel Asus shipped with ICS in place, and hence aren't truly 100% downgrading...
knoxploration said:
How did you downgrade? It's my understanding that some methods leave the kernel Asus shipped with ICS in place, and hence aren't truly 100% downgrading...
Click to expand...
Click to collapse
That's most likely why it didn't work. I had the link to that guide saved but since it didn't work I deleted it. I'll have to wait for an official release or a better more complete method of downgrading.
I had a similar issue with my phone at one point. I went into cwm and wiped battery stats and it seemed to clear my problem up. I'm sure if it would work in this instance but it couldn't hurt to try.
headbangerkorn said:
I had a similar issue with my phone at one point. I went into cwm and wiped battery stats and it seemed to clear my problem up. I'm sure if it would work in this instance but it couldn't hurt to try.
Click to expand...
Click to collapse
Tried that too, twice.
I really don't think this is an ICS issue as you are the only one reporting it (that I've seen). Sounds more like a hardware problem to me....
Sent from my Transformer TF101 using Tapatalk 2
jtrosky said:
I really don't think this is an ICS issue as you are the only one reporting it (that I've seen). Sounds more like a hardware problem to me....
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I have sent it in for repair, no change. The left side looks spudged open so they could have checked, but no one can tell me if they actually did check the hardware. They ask me to send it back for repair again. If they did replace it with andother TF101 it could be a refurbished one that has other kinds of bugs and be scratched and in worse condition than mine. If they gave me a brand new one it could also still have these or other issues. I am waiting on official or better unofficial way to downgrade to HC.
If anyone knows more about the hardware for the TF101 please post your thoughts on what could be going on with these bugs.
Could your battery not just be simply shagged?
cspiby said:
Could your battery not just be simply shagged?
Click to expand...
Click to collapse
A few days before ICS update I had 7 hours of use out of one full charge. I always shut down instead of sleep. Normal battery life is usually 6 and half to 7 hours and 15 mins. The combined total hours of use during the 100% power bugs after .21 was 4-5. If it is really the battery then ASUS is the stingiest company in the world cause they should have replaced it at the repair center when I sent it in.
has anyone suggested to clear your battery stats in clockworkmod (assuming you have it)
Sent from my Transformer TF101 using Tapatalk 2
Hi,
I was right in the middle of a meeting, my SGS2 was on the table and it kept flashing for apparently no reason! By flashing I mean going from sleep mode (dark screen) to lock screen. There was non incoming call or messages, no running application. So, as this was weird to me and it was disturbing every one, I tough it could stop doing this if I restarted it. I made a long press of the on/of key thinking it would reset the system! Since this time the phone turns off to never wake up! Is there something I can do to have it back to life?
Thank you for your help!
lockiller said:
Hi,
I was right in the middle of a meeting, my SGS2 was on the table and it kept flashing for apparently no reason! By flashing I mean going from sleep mode (dark screen) to lock screen. There was non incoming call or messages, no running application. So, as this was weird to me and it was disturbing every one, I tough it could stop doing this if I restarted it. I made a long press of the on/of key thinking it would reset the system! Since this time the phone turns off to never wake up! Is there something I can do to have it back to life?
Thank you for your help!
Click to expand...
Click to collapse
Did you try to connect to the charger?
Sent from my GT-I9100 using xda premium
lockiller said:
Hi,
I was right in the middle of a meeting, my SGS2 was on the table and it kept flashing for apparently no reason! By flashing I mean going from sleep mode (dark screen) to lock screen. There was non incoming call or messages, no running application. So, as this was weird to me and it was disturbing every one, I tough it could stop doing this if I restarted it. I made a long press of the on/of key thinking it would reset the system! Since this time the phone turns off to never wake up! Is there something I can do to have it back to life?
Thank you for your help!
Click to expand...
Click to collapse
that sounds like you just powered it of and it may had low battery, also you will propbably have to wait sometimes undil it can power on again
Dude she needs charging!
samomamo said:
Did you try to connect to the charger?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
When I got home I connected it to the computer, I've wait some times as nothing happened I took it to press the power buton but, it was so hot that I had to drop it to avoid burning! I unpluged it, I put a fan on if and, I removed the battery! after a while I replace the battery and plug it back to the computer, the same thing happend! actually it is pluged to a wall outlet for about half an hour, it's not hot, just a little bit but, stil there,s no sign of life!
BRO!!! SAME AS MEEEEE!! (similar i guess)
In the night after i flash miui v4 and neak kernel v2.0.6 (its old..) i plugged in the power and went to sleep. Next morning when i took my phone for my morning news THE PHONE WAS HOTTTTTT (very!) Ok..... i did the usual and checked my cpuspy mostly was 500mhz and 200 mhz NO DEEPSLEEP! dafuq? Ok reason found... So i guessed it was the kernel issue and so i flash a newer neak kernel. From there i went to school. Once there i checked my phone and it was warm.... cpuspy states decent deepsleep so i guess its just me but after awhile it got hot again! so i gave in and flash siyah 3.3.2 (used neak in the first place as some games wont work on siyah)(after initial boot from the new kernel there was major batt drain!!! From unplug to me flashing the newer neak kernel i already lost 60% batt wts??!? But after flashing siyah kernel i was left with 14% batt from 40%.... ok never mind i will just UV UC and other power saving stuff which helped a lot on previous days. Those "did" help and yeah all was cool till about 6% when the phone (you can guess right?) got hot.... HOT! So i gave in and powered down the phone..... i pulled the batt and separated the two for awhile. After the main body cooled i replaced the batt and rebooted the phone. After booting the batt was at 4% after seeing the batt level i powered the phone down and left it that way. Not even 1hr later the phone refused to boot.... no buzz no light no screens no nothing! I had to wait a few hours before getting home from school (omg yes it all happened in school zzomg ) now im at home with my charger and all (a different charger this time made sure it worked first) and no matter how i try to boot the phone plugged in with and with out the batt it refused!?!!?! WTS IS THIS BS?!?!
Sorry for the vulgarities and caps peeps...
Click to expand...
Click to collapse
Now i got the phone back after sammy changed my battery but it still has weird over heating and fast battery drain issues with stock rom and even on custom roms(UV and UC) ... looks like il be back to sammy again soon...
That's scary.
Have you tried to access download mode?
Sent from my Galaxy S2 using Tapatalk
Well i dint..
damn it, my phone dead 8 days ago, same like u, check my recent post
---------- Post added at 08:09 AM ---------- Previous post was at 08:08 AM ----------
it hv no respond at all......
By the way, what rom and kernel were you using?
Sent from my Galaxy S2 using Tapatalk
100% thinks its hardware
alwaysbboy said:
By the way, what rom and kernel were you using?
Sent from my Galaxy S2 using Tapatalk
Click to expand...
Click to collapse
I know nothing about Android, I'm new to this platform, my first smartphone was the N8, it has been stole, after I had an iPhone 3g I change for galaxy cause it was cheaper than iPhone 4 or 4s, andt it's a beautifull piece of hardware but, for all the rest I was disapointed and I've never liked it so much! I think I'm going to return to samsung to have an other one and when his back, I'm gonna sell it!
I think your usb/charger port is broken.. that is what happend to me. Try to charge the battery with an external charger to see if it turns on. Then get your phone to default (unroot/stock fw) if its working and let it repair. For me it just took 2 hours an i had my phone back for free.
GT-I9100 with Tapatalk 2
Mine was fixed by getting a new battery but now it died of the same reason (something wrong inside with the boards i think) sammy better get me a new one
Help people, I have the nexus 4 for over 3 weeks and great but a few days ago when it was nearly full battery (around 80% or so) suddenly shutted down and I couldn't turn it back on until after 1 min or so plugging in. I did not care about it the first time ... But today, after having it charging about 2 or 3 hours I disconnected the cable to use the phone and the battery dropped from 90%+ to 8%, so I connected the cable and put it back to 100%, used it for 1 hour and it suddenly dropped back to 2% from 80% and then shutted down instantly.
Here are some screens.
Help please, and yes I have used the search function, but didn't find the solution on other posts.
tacwold said:
Help people, I have the nexus 4 for over 3 weeks and great but a few days ago when it was nearly full battery (around 80% or so) suddenly shutted down and I couldn't turn it back on until after 1 min or so plugging in. I did not care about it the first time ... But today, after having it charging about 2 or 3 hours I disconnected the cable to use the phone and the battery dropped from 90%+ to 8%, so I connected the cable and put it back to 100%, used it for 1 hour and it suddenly dropped back to 2% from 80% and then shutted down instantly.
Here are some screens.
Help please, and yes I have used the search function, but didn't find the solution on other posts.
Click to expand...
Click to collapse
What apps have you installed lately, maybe there is a rogue one. Install BetterBatteryStats for app behaviour and Cpu Spy for deep sleep issues.
Are you rooted? Custom rom or kernel? Undervolted or overclocked?
gee2012 said:
What apps have you installed lately, maybe there is a rogue one. Install BetterBatteryStats for app behaviour and Cpu Spy for deep sleep issues.
Are you rooted? Custom rom or kernel? Undervolted or overclocked?
Click to expand...
Click to collapse
I'm not rooted, all at stock. I didn't touch the voltages, I didn't do anything. I installed some games (vector, pudding thd, order and chaos) evernote, mega manager, pulwifi.
I'll install betterbatterystats and cpuspy, thank you.
Edit: look what happened to the battery now...
Also I attached a pic of the cpuspy, I can't install betterbatterystats because it costs 2 dollars
tacwold said:
I'm not rooted, all at stock. I didn't touch the voltages, I didn't do anything. I installed some games (vector, pudding thd, order and chaos) evernote, mega manager, pulwifi.
I'll install betterbatterystats and cpuspy, thank you.
Edit: look what happened to the battery now...
Also I attached a pic of the cpuspy, I can't install betterbatterystats because it costs 2 dollars
Click to expand...
Click to collapse
I think there is a free version of BBS on XDA , here http://forum.xda-developers.com/attachment.php?attachmentid=1240843&d=1344068311. Consider buying it on Play in the future if it benefits you.
Battery levels can be inconsistent at times, especialy after deep sleep.
gee2012 said:
I think there is a free version of BBS on XDA , here http://forum.xda-developers.com/attachment.php?attachmentid=1240843&d=1344068311. Consider buying it on Play in the future if it benefits you.
Battery levels can be inconsistent at times, especialy after deep sleep.
Click to expand...
Click to collapse
Here it is, and thanks for the replies.
Look in Partial Wakelocks for the biggest consumers.
gee2012 said:
Look in Partial Wakelocks.
Click to expand...
Click to collapse
I looked but I don't know what does that mean, sorry I'm a little noob. Is there anything wrong with it? I though that was just the sound cause I had it at max while I played after that happened.
Edit: I ordered it by count and the RILJ thing is the one at the top. (its not the attached pic)
tacwold said:
I looked but I don't know what does that mean, sorry I'm a little noob. Is there anything wrong with it? I though that was just the sound cause I had it at max while I played after that happened.
Click to expand...
Click to collapse
I see nothing abnormal on usage, just use the phone and see if this behaviour continues. If it does better do a factory reset or reflash the latest factory image.
gee2012 said:
I see nothing abnormal on usage, just use the phone and see if this behaviour continues. If it does better do a factory reset or reflash the latest factory image.
Click to expand...
Click to collapse
Okay I'll uninstall the latest apps I installed and will use the phone normally, if this happens again I'll do a factory reset and if the problem continues I'll call google. Thank you :good:
I wish I could be more help but I had the exact same issue. I could not figure out what was wrong with it but I had previously broken the screen and sent my N4 back to LG for repair. Since it was still under limited warrenty from that repair I sent it back to them again. They said they replaced the charger connector. I got it back and it seems to work fine now.
My issue started after I updated to 4.2.2 I believe. I don't know the root of it but my advice would be to do what you said and call Google or LG.
stones1313 said:
I wish I could be more help but I had the exact same issue. I could not figure out what was wrong with it but I had previously broken the screen and sent my N4 back to LG for repair. Since it was still under limited warrenty from that repair I sent it back to them again. They said they replaced the charger connector. I got it back and it seems to work fine now.
My issue started after I updated to 4.2.2 I believe. I don't know the root of it but my advice would be to do what you said and call Google or LG.
Click to expand...
Click to collapse
Thank you anyway
Similar issue here - I've been using the same apps since I first installed them after N4 purchase (meaning no new apps/games installed in the last few days and no settings changed). Took a nap for a couple of hours and woke up to see N4 completely dead - 0% batt. Charging it now and looking at partial wakelocks etc, havn't seen anything out of the ordinary. Hopefully it doesn't occur again but in the meantime still looking for a reason why this would suddenly happen.
Are you guys using the stock chargers? And charging through mains?
Rizy7 said:
Are you guys using the stock chargers? And charging through mains?
Click to expand...
Click to collapse
Yeah, am on stock JB 4.2.2, unlocked and rooted though, no other change like new roms flashed or anything. I use the stock charger and charge through mains.
I think there have been a few threads with this issue and nexus4s even prior to 4.2.2 and supposedly it was hardware. I called support while talking it through she had heard a few similar cases and it seems to be a hardware/software design issue. My wonder is how can I enforce 'never deep sleep' because my kernel doesn't seem obey.
I woke up this morning with the indicator light on but phone dead requiring reset (charged though - if not overly so). Just now it died again while sitting on my desk at 80% charge and deep sleeping again.
---------- Post added at 06:24 PM ---------- Previous post was at 06:13 PM ----------
Guiding.God said:
Yeah, am on stock JB 4.2.2, unlocked and rooted though, no other change like new roms flashed or anything. I use the stock charger and charge through mains.
Click to expand...
Click to collapse
I've read in a few places today the stock charger has been causing a lot of the charging issues and plan to switch to my old g2's charger tonight
Just RMA'd my nexus for powering off for no reason - would do it a few times a week (and extremely buzzing earpiece - which I was living with), never had a problem putting it back on though or had issues by battery levels being eratic) did quite a bit of testing over the space of a few weeks and found it continued to do it after wiping/fomatting everything and on Stock 4.2.2 non rooted and locked BL. As far as I am concerned if its still doing it with the stock out of the box set up its a hardware fault.
Mine has powered off unexpectedly twice in 30 days. Should I get it rmad?
Sent from my Nexus 4 using xda premium
gamepr said:
Mine has powered off unexpectedly twice in 30 days. Should I get it rmad?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Dunno about that its up to you mine was doing it 2-3 times per week. I would wipe everything including userdata, reflash stock rom and monitor before going through the rigmorole of the RMA to make sure its deffo a hardware fault. Biggest problem with the RMA is the fact they put a hold on your credit/debit card for the price of the phone. So basically if you don't have the funds available you are shafted (I think you would have to send off to LG in that case).
I got the same problem ..just that my n4 back cracked while was charging :-\
maybe you should try to flash other kernel and rom if you cant solve this issus. if your N4 is unrooted then just bring it to LG store, you got warranty rite ?
Since last week I am experiencing a really strange behavior of my battery.
Sometimes my phone (in a random app) just vibrates, the screen goes black and then it reboots. After the reboot I have lost 40-50% battery life. Sometimes the phones isn't even able to complete the reboot because it spontaneously has too little power left. See attached screenshots.
Has anybody had similar problems? Or knows a solution?
About my setup: The problem seems to be not rom or kernel related. It occurs no matter what rom or kernel setting I am using. Currently I am running coool boy's 4.3 GE witch KT's kernel (no OC or UV).
Is it possible that the battery is physically damaged? I have NO IDEA...
Experiencing the same problem. I've flashed back to stock and still experiencing this. Phone randomly turning off, not starting, sudden battery drops. Driving me crazy.
Sent from my GT-I9505 using Tapatalk 2
This looks pretty strange 0.o
Consider buying a new recovery
HITTTTTTT THANNNKKKKSSS
galaxy star duos ****rooted*** xda offical app ) )
I've seen the same sort of graph on my old i9000. You're not gonna like this, but it got worse over time, and eventually my battery wouldn't last more than 5 mins. I thought buying a new battery would help, but it didn't. When I sent it in to Samsung they said they would have to replace the entire motherboard...
I think it's got something to do with the motherboard not being able to correctly sense the battery voltage/whatever/%. The phone reboots automatically because it thinks the battery is flat (even though it isn't).
If you're under warranty I suggest sending it in soon... Hopefully it's not the same as what I had heh.
nwsk said:
I've seen the same sort of graph on my old i9000. You're not gonna like this, but it got worse over time, and eventually my battery wouldn't last more than 5 mins. I thought buying a new battery would help, but it didn't. When I sent it in to Samsung they said they would have to replace the entire motherboard...
I think it's got something to do with the motherboard not being able to correctly sense the battery voltage/whatever/%. The phone reboots automatically because it thinks the battery is flat (even though it isn't).
If you're under warranty I suggest sending it in soon... Hopefully it's not the same as what I had heh.
Click to expand...
Click to collapse
Well *#!$
I'll observate it for the next few days and see if it's getting worse...
If your phone is rebooting as opposed to just powering off, then I suspect it is hardware related (motherboard) as already mentioned.
I do hope I'm wrong though.
Maybe try using it for extended periods while plugged into a charger and see what happens. If it doesn't reboot then it may just be the battery.
Right as OP I'm suffering the same exact problem or there abouts. I've flashed back to stock rom, fully charged to 100% drained to 0% back to 100% yet still phone keeps shutting off randomly and the only way it works properly is with the charger plugged in. It's escalated quite badly with now after a few mins of YouTube turning itself off and not rebooting. I've requested a repair by o2 who I'm in contract with and see what will happen. I've heard crap stories about their repairs before taking it to Samsung.
I9500 owner. Had this exact same problem when using older firmware. After updating to the latest one, never had this issue again. Its been two months now, even more.
Try this. Flash the latest available firmware for you phone, not talking about OTA but the downloadable one from any region (whichever is latest for i9505). I guess it may have something to do with the kernel too.
Edit: wait a minute, why is your battery level going up when it isn't even charging in the second screenshot. Middle of the battery timeline. That's weird. I guess you should send the phone back
Sent from my GT-I9500 using xda premium
Its a hardware issue(motherboard).I hope your under warranty.Best of luck .
i have something strange like that also on my device ..
http://forum.xda-developers.com/showthread.php?t=2409284
Thank you guys :good:
In the last few days the problem occurred more often. But now it is just shutting down (no reboot after vibrate) and after plugging it to the charger and restarting it sometimes I haven't lost any battery. Strange!
I fear there is nothing else to do than turning it in (warranty)
E_Cartman said:
Thank you guys :good:
In the last few days the problem occurred more often. But now it is just shutting down (no reboot after vibrate) and after plugging it to the charger and restarting it sometimes I haven't lost any battery. Strange!
I fear there is nothing else to do than turning it in (warranty)
Click to expand...
Click to collapse
Same problem here. It started three days ago and today I'm barely able to use it... I'm still on warraty and I even have insurance, but it's a major inconvenience anyway.
Mines gone in for repair back to my carrier still no movement despite them having it for 2 days now really should have sent it back to Samsung directly. Will keep you guys posted.
Sent from my Nexus 4 using Tapatalk 2
Will send it in tomorrow. Lady on the hotline told me apparently the motherboard is defect and I'll get a new S4. Exchange, no repair. I'm fine with that...
Sent from my GT-I9100 using Tapatalk 4
That's good to hear, just inconvenience but at least you won't have to pay for it (or have the defect materialize a year later or something)
E_Cartman said:
Since last week I am experiencing a really strange behavior of my battery.
Sometimes my phone (in a random app) just vibrates, the screen goes black and then it reboots. After the reboot I have lost 40-50% battery life. Sometimes the phones isn't even able to complete the reboot because it spontaneously has too little power left. See attached screenshots.
Has anybody had similar problems? Or knows a solution?
About my setup: The problem seems to be not rom or kernel related. It occurs no matter what rom or kernel setting I am using. Currently I am running coool boy's 4.3 GE witch KT's kernel (no OC or UV).
Is it possible that the battery is physically damaged? I have NO IDEA...
Click to expand...
Click to collapse
nikzDHD said:
Experiencing the same problem. I've flashed back to stock and still experiencing this. Phone randomly turning off, not starting, sudden battery drops. Driving me crazy.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
nikzDHD said:
Right as OP I'm suffering the same exact problem or there abouts. I've flashed back to stock rom, fully charged to 100% drained to 0% back to 100% yet still phone keeps shutting off randomly and the only way it works properly is with the charger plugged in. It's escalated quite badly with now after a few mins of YouTube turning itself off and not rebooting. I've requested a repair by o2 who I'm in contract with and see what will happen. I've heard crap stories about their repairs before taking it to Samsung.
Click to expand...
Click to collapse
im4eversmart said:
Its a hardware issue(motherboard).I hope your under warranty.Best of luck .
Click to expand...
Click to collapse
Hey
I am new here.
but i was looking for information becuase my s4 9505i has the same problem
shuts of almost everytime i open apps too quickly or stream youtube or some other high usage apps etc.
battery drops up to 50 percent then back 40 percent then to 0 percent, the fact it that the phone never seems to know where the battery is.
by the way my phone is not rooted and i have done the factory reset a few times.
samsung... hmmm.. they seem to be real hard to talk to on the phone, i have had to call them 4 times already about the s4 i ahve had since june, and they just play me off like i am some kind of idiot etc. and deny that there is possibly any reason for random shutdowns, phone freezing, and now this battery/motherboard issue.
next bit is kinda stupid, the phone has a few internal scratches on it from when i ahve stupidly had the phone next to keys and all that. im sure they are going to try and void my warranty and say i have mistreated the phone...
had many phones before, maybe close to 50 and never, never, never have had to ring up a company to try and complain etc.....
any ideas.
I am in Australia,
I am thinking of trying the CONSUMER AFFAIRS kind of threats, but i have to word it the right way...
Has anyone noticed the battery percentage on their replacement note 7 stuck at 100% when it should be around 30%??
pluigie said:
Has anyone noticed the battery percentage on their replacement note 7 stuck at 100% when it should be around 30%??
Click to expand...
Click to collapse
Mine isn't.
You shoukd probably state whether you are rooted or not though, and what firmware version you have.
Sent from my SAMSUNG-SM-N930A using Tapatalk
Stock phone not rooted. Only think I have aside from a few apps is nova launcher. Android version 6.0.1. Thanks for the reply
I did notice weird spikes on the battery graph. I have actually had it off the charger since 6:10 this morning. At one point I did plug the charger in for about a min. to see if that would reset it after trying to reboot the phone a couple of times to see if that would work. Apparently that just reset the battery stats. I'm really confused because I've been messing with it most of the day playing games,youtube,xda and music just to see if I can get the battery to drop or die. It just keeps on going though with no sign of any battery drain other than a little lag here and there. This phone seems to not like more than 3 apps open at once before it starts to lag.
OK so around 5:30 the phone died. I plugged in the charger and the battery icon you get when there's not enough juice to turn on the phone showed 0%. I waited til 15% and turned the phone back on. It seems back to normal now but we'll see when it gets to 100%
I think the AT&T update for the green battery messed up the phone. I'm hoping the September security update will fix the issues.
I think your right. 2nd battery cycle since the issue and all seems well. Thanks
I had a weird thing happen. My device was off. I plugged in the charger and battery immediately dropped from 90+ to 15℅ then showed a red triangle briefly.
Sent from my SAMSUNG-SM-N930A using XDA-Developers mobile app
I just read through the thread to catch up. I dont think it's the update because most of us have it (myself included), and are having no issues (reported anyways). Many of us replaced our phones though.
First, do you have the fixed Note7, or the defective (combustible) one?
Second, if you have a fixed version, you may have a bad battery and should get it exchanged as a defective unit.
If you have the version that was recalled, then yes, this may indeed be the update's fault, but at this point, I wouldn't expect it to get fixed. It could be some sort of glitch caused by some safety procedure implemented in order to prevent to batteries being charged completely, or something. Who knows.
Sent from my SAMSUNG-SM-N930A using Tapatalk