Chosen Solution
Hello, i have a problem with my iPhone 5S. A few weeks ago it started to shut down randomly, sometimes 10 times a day. It just turned off. I suspected it was the battery, so i replaced it, but it didn’t stopped. But it only shuts down, when its running on the battery. If i have it on the power plug it runs fine. I looked at the diagnostic data and saw a lot of ResetCounter entries with exact that time when it crashed starting at that day when a replaced the battery. All the days before i replaced it were filled with LowBattery entries like this: Incident Identifier: 88437E57-EDCB-46D0-BF4F-ED80CD72C765 CrashReporter Key: 444932e96edba90279b56e6bbc65a6bf3bfb6334 Date: 2015-02-22 13:33:10 +0100 OS Version: iPhone OS 7.1.2 (11D257) SpringBoard: com.apple.springboard.idle NoIdleSleepAssertion == 255, held for 00:00:41 Hardware Model: N53AP Awake Time: 04:15:50 (15349) Standby Time: 28:00:28 (100828) Partial Charge: 1 Capacity: 0 Voltage: 3667 mV After replacing the battery the ResetCounter entries started. Here is an example entry: {“name”:“Reset count”,“bug_type”:“115”,“os_version”:“iPhone OS 8.1.3 (12B466)”} Incident Identifier: A01C9870-64C5-46B4-A4B3-35029BE0CBD2 CrashReporter Key: 444932e96edba90279b56e6bbc65a6bf3bfb6334 Date: 2015-03-01 16:08:41 +0100 Reset count: 0 Boot failure count: 5 Boot faults: rst vdd_under Boot stage: 80 Boot app: 2681261667 Has anyone an idea? I searched a lot about “rst vdd_under”, but never find an answer except that i should replace the battery. Should i replace it a second time (I think it isn’t the battery particularly because i just replaced it). But vvd_under sounds to me that the iPhone recognize a too low voltage. I already restored iOS, but that didn’t help. Christian
Bad batteries are a dime a dozen. Start with a new new battery and go from there.
I have the same. I solve it by stop auto brightness
I have similar behavior. Happens more when in my pocket.
Man I’m havin the exact same problem with my iPhone 5. My iphone also Never crashes wen its plugged in. But wen I m out & about it randomly crashes, than I turn it on with the button on the top right & it almost always turns on. & sometimes wen I can’t turn it back on. I have to wait till I get home & plug it in. & wen I do plug it in it turns on right away with the apple logo. Man I am so sick of this BS. I pay like $75 a month for this piece of S H I T & its not even working half of the time. & they won’t give me a new iPhone. Or even a deal. I just have to fork over another $1000 just to get back online, or just to be in touch with the world. Sometimes I think they mess up our phones on purpose just in time for a new contract, so we R forced to buy a new phone & a contract. & be stuck for another 2 years. Until they start this whole process all over again.
Im having the exact same issue at the moment. replaced battery just over a month ago. do i really have to replace the battery again? :(
Have the same here.. I replaced my iPhone 6 Plus battery and now my crash report show me the same message… I`ll try disable auto brightness
Hi any suggest or more ideas about this bug? My iPhone became like this too. Please
Two answers: simple short and the truth of my individual case and what was happening both software/hardware wise. Keep in mind to have my issue you could have had a bogus battery repair done by am amateur or knocked your phone around one to many times and a microscopic connection or small pert could have gone bad due to heat etc. but since I understood through research the charging system and monitoring points at which values are checked i was able to isolate the hardware issue but software would only ever be fixed by staying below ios9 since its in everything after it. Short answer: change out the caps by the battery from a ebay purchased donor board (usually less than 20 bux) by taking it to a technician who knows how to micro solder with proper equipment DONT DO IT YOURSELF unless you want to buy ALL of the proper tools. Im serious now proper tools. Chances are you are missing one or one has gone bad like in my case. Long answer: As i went and studied it more The bug directly relates to the fact the max capacity variable( remember this is a software side bug) which is what internally (seen in batt life apps {jailbroken}) not publicly shown in battery settings or else where. What I discovered was a accidental work around which prevented the crash but didnt solve the problem. My solution skipped the internal process that led to the phone shutting down but while doing that kept the phone alive it changed the internal max capacity variable to %(0-100) instead of actual amount (around 1570 mah sometimes lower sometimes higher as the two oem and two aftermarket batteries were all different). This leads the function shortly after boot to put your phone into shutdown because it believes its well beyond expiration. Apple in hardware design goes overboard with its monitoring and software checking at various points in all of their hardware looking for specific voltage drops etc and since at that time hadn’t admitted to forcing device obsolescence by software means (all devices post iphone 4) by adjusting clock speed by changing voltage at those various points(now claiming data integrity because of battery cycles{not battery cycles but age:move your device to a couple years ahead and use it offline for a weeks and look at battery health plummet}). So that recurring function to check and adjust “for your own good aka so you buy a new faster device” battery stats causes the crash now letting it crash too many times had a weird effect on hardware as not until opening my phone much later did i discover a bad capacitor where i am positive there wasnt one, but replacing it (microsoldering skill needed so go to a trained technician not a kiosk or anywhere you dont see a industrial digital microsope and soldering stations not radioshack irons if you have the same issue). Now once that was switched out and i replaced the whole row of them from a clean donor board of some locked 5s that functionality returned and the software “bug” which isnt a bug but a general apple kill command that happens when max capacity of a battery is less than a certain amount (safe to say well above the 100% mark which through the bug translated to 100/1570 instead of 157x/157x) now i do believe hardware was ultimately to blame but issues truly only arose because of apples post ios 9 (whenever they hid the battery stats) forced monitoring and artificial slowing which as i stated above is bypass able by forcing the device to do anything else during that time and making it reschedule for next reboot. So the capacitor ahead of the value check that sets max capacity in Mah was bad not the max capacity % which was accurate but because the percentage value is defaulted to if the mah cant be determined it freaks out at the life of the battery at 100% being 100/15xx which it thinks is near death. It will also freakout if it was ever seen to be significantly higher than their set range like 5500/15xx which would be like 200+%. thats all i know -dns
