Previous 1 40 41 42 43 44 Next 649 Replies Latest reply: Aug 16, 2014 8:54 PM by commorancy Go to original post Branched to a new discussion.
  • iinami Level 4 Level 4

    ITAY83 wrote:


    Sorry to disapoint you guys... just upgraded still same problem.


    maybe in 6.1.4 they will admint they've got a bug!

    no battery drain problem ever on any iphone in my i have to ask "what bug can they admit to"?

  • Lawrence Finch Level 8 Level 8
    Mac OS X

    Many people believe that if they have a problem it must be a bug.

  • Zeljko83 Level 1 Level 1

    But how will you use your phone if you take a SIM card of ?i dont understand it what that means!!

  • Theweirdguy Level 1 Level 1

    I've updated to 6.1.3 OTA.Current usage time is 2 hours 21 minutes and standby is 4 hours 24 minutes(I'm on wifi the whole time) and battery is at 86%.

  • DarrylR Level 1 Level 1

    Apple is good at sneaking fixes into a update.

  • Jameson! Level 1 Level 1

    If they wouldn't admit to a problem, how could they admit to fixing it?  

    DarrylR wrote:


    Apple is good at sneaking fixes into a update.

  • Lawrence Finch Level 8 Level 8
    Mac OS X

    From the posts, they didn't sneak very well, because some people are claiming that 6.1.3 made their battery life worse, and most say it didn't improve battery life.

  • DarrylR Level 1 Level 1

    Some say that it improved some say it didn't, who knows what people are doing. I never had a issue with the updates battery life matches the tech spec for my devices sometimes I get more hours then what it says. I know one thing it is not the iOS like some are saying.

  • Retox Level 1 Level 1

    I have kinda backed off because I was lucky enough to get two of our five iPhones replaced under warranty. Both have had great battery life as I certainly didn't update to 6.1.2. The other three (2 iPhone 5's and 1 4) have had abysmal battery life since updating to 6.1.2 even after applying every work around posted in this great thread. We certainly appreciated Lawrence's undying support and everyone else who has made a suggestion. It's great to see people pulling together. That was the bad news for us


    The good news, I updated the two other iPhone 5's last evening to 6.1.3. I am happy to report that battery life seems to be back to where it was prior to 6.1.2. Needless to say I have two ecstatic users here. I have no idea what Apple specifically did in this update, all I can say is that ours appear back to "normal".


    I hope everyone else gets the same kid of results.



  • commorancy Level 1 Level 1

    Hi Lawrence,


    Unfortunately, someone has deleted the thread, so the best I can do is offer up the following reply.  While there are many reasons for battery drains on small devices (and no, not all of them are bugs), it does seems that you aren't taking one important thing into account.  Changes to software can introduce regressions and Apple is not immune to them. Regressions are easily reintroduced for a variety of reasons and, in fact, it certainly seems like this is a regression as it is affecting more than one type of device.


    As I said, it's easy to blame a battery drain on 'normal activity' and 'known issues' (i.e. low or no signal) problems which is clearly how you see this issue. Unfortunately, there is no explanation for a dead battery in less than 4 hours on a WiFi only device with full bars on the WiFi.  The heat generated by the unit does indicate high CPU load.  The apps I had loaded at the time were mail (of course) and the music player (not playing anything).  There was nothing else loaded at the time.  I always make sure my process list has no more than 2-3 apps running at any one time.  Usually 2.


    So, it is either a bug introduced into this version of iOS or it is simply a regression.  I won't discuss the debugging aspect as that's likely the reason the thread got removed, but suffice it to say that I wasn't saying you could fix any problem that way. You jumped to that conclusion.  In fact, no one other than Apple can likely fix this problem as it likely will require an OS update.  Sure, you can kill or delete whatever app may be triggering the fundamental problem, but removal of the app is simply a workaround.  Also, removal of the offending app doesn't necessarily mean that it's still not the OS causing the fundamental problem.  Sure, bad code can be written that can do stupid things and drain the battery. But, if the app is doing normal things in documented ways, that shouldn't happen.  And, if I'm running only Apple apps, it shouldn't happen at all.


    Basically, you cannot rule out a newly introduced problem within a specific OS version simply because users have complained about previous versions having this issue.

  • dblumfrommd Level 1 Level 1



    What's a regression?


    After trying all the solutions offered in this thread, I still have the severe battery drain issue if I have my email set to push.  If it's set to fetch, all is fine. 

  • Lalman Level 1 Level 1

    Absolutely correct. Spot on. I fully endorse your comment. This was my experience too. Wifi only with a good strong signal. Stock iOS. Working well under 6.0.1. Only app store apps. Then suddenly after 6.1.2 with same settings, same usage, huge drop in battery combined with body heating up.


    And...even if it happens with every new iOS, the question is should it? Is that acceptable? That a so called upgrade sends thousands scrambling to find out what functions to disable in order to regain battery life?

  • commorancy Level 1 Level 1



    For everyone who doesn't work in the software industry, a code regression is any bug that was thought to have been fixed in an earlier release, but has resurfaced in a later release. The reason why these happen can range from something as simple as merging two different sets of code together (e.g., older and newer) to rewriting a new feature that re-introduces a similar (or the same) problem a second time. There are lots of reasons a regression can occur when writing software. Many times these tend to stem from legacy code written by former employees long ago that is not completely understood by new employees who are tasked to write new features. So, old dormant code may be re-introduced to solve a new problem but which also re-introduces an old fixed bug.


    Typically, a quality engineering team should run regression tests on the code before any release.  However, if the bug was fixed several years before, the QE team may no longer run those specific regression tests on the release after a certain number of releases test negative.  This is usually done to reduce the number and amount of tests that have to be run prior to a release. Dropping regression tests from test suites can then allow old bugs to slip back into a release and resurface.  Sometimes, if the bug is similar to but not identical, it can get past regression tests because the test suite is looking for signatures that are too specific.

  • Theweirdguy Level 1 Level 1

    Now at 55% battery 3hours 52minutes usage and 18 hours 54 minutes standby.First 2 hour 30 minutes were on wifi,as i've stated on my previous post here and the remaining on cellular.Is this good?

  • Wendycisme Level 1 Level 1


    I am forced to lave y phone connected to a plug while using it, the camera and any of the apps.  I am lucky that I am able to stay at home.  I have made attempts to update the update but now I am only more lost.  I read now that it is permanent? Yikes!!! Do you say this because you "KNOW"??

    Can someone give me an opinion as you any advice on how to edit my updates that have caused my phone to be a pain in my booty!