Forgot your password?
typodupeerror
Bug IOS Iphone Software Upgrades Apple News

iOS 6.1 Leads To Battery Life Drain, Overheating For iPhone Users 266

Posted by timothy
from the that's-a-drag dept.
An anonymous reader writes "We have started seeing an increase in iPhone issues related to battery life and overheating. All of them seem to be related to users upgrading their devices to iOS 6.1. Furthermore, Vodafone UK today began sending out text messages to iPhone 4S owners on its network, warning them not to upgrade to iOS 6.1 due to issues with 3G performance. The text reads, 'If you've not already downloaded iOS 6.1 for your iPhone 4s, please hold off for the next version while Apple fixes 3G performance issues. Thanks.'"
This discussion has been archived. No new comments can be posted.

iOS 6.1 Leads To Battery Life Drain, Overheating For iPhone Users

Comments Filter:
  • by Jarik C-Bol (894741) on Saturday February 09, 2013 @02:40PM (#42844679)
    And this is why I refuse to install system updates for at least a month after they are released. Let some other poor sod brick their phone with an obscure bug, and get the fixed update once they finish the croudsourcing beta test.
  • Re:Upgrade to 6.1? (Score:5, Insightful)

    by Anonymous Coward on Saturday February 09, 2013 @02:53PM (#42844777)

    I've been reading /. since 1998 or something and one thing that would always make me mad were the assholes that would reply to a problem in a particular OS with the suggestion that the solution to that problem would be using another particular OS. Normally it would be a MS Windows issue and always there was an asshole saying that with Linux that particular problem would not happen.

    So to get back to point. Next time you have a headache, please remember, that the problem is that you have a faulty head and should be using another, better one. So please have someone chop it off, and replace it with a new one.

  • by node 3 (115640) on Saturday February 09, 2013 @03:15PM (#42844929)

    Troll much?

    There are hundreds of millions of people without any problems whatsoever, and hundreds, maybe even a few thousand, who are having problems. After all, if what you said were true (and not just the standard Slashdot drivel), you'd see not just a sensational headline and story, but an outcry from the users.

    Don't worry yourself about it, though. Trolling Apple here will get you points.

  • by Anonymous Coward on Saturday February 09, 2013 @03:45PM (#42845151)

    Because the manufacturer of my 1 year old phone has decided that it isn't *worth* updating. No problem - I just installed Cyanogen mod and I'm good ... well, except that the camera isn't supported yet, and the battery life is 1/2 what I get on the manufacturer's ROM.

    Suddenly, overheating Apple phones don't look so bad - at least iPhone owners can be reasonably certain that Apple will actually release a fix, in a timely fashion.

  • by _xeno_ (155264) on Saturday February 09, 2013 @04:12PM (#42845331) Homepage Journal

    Except last I checked, iOS 6.1 contains security fixes, a few of which are not related to blocking jailbreaking.

    So your choices are apparently "useful battery life" or "able to browse webpages safely." Sounds about normal for Apple, since this isn't the first upgrade that completely killed battery life for most users.

  • by inglorion_on_the_net (1965514) on Saturday February 09, 2013 @04:59PM (#42845639) Homepage

    Coming from the Microsoft world I have been very surprised at how little attention Apple pays to legacy compatibility. It's only recently become impossible to run 16 bit Windows apps in the latest Microsoft OS. Compare that to the constant forced churn in Apple desktop software.

    Huh? Are you talking about the sample Apple that let desktop software developed for 68K CPUs run on Power Macs, software developed for classic Mac OS run on OS X, and software compiled for PowerPC to run on x86?

    Are you talking about the same Microsoft that replaced Visual Basic with the incompatible VB.NET, changed the way to develop for smartphones in Visual Studio 2008 and then again in 2010, so that applications developed in VS 2008 will only compile in that version? The same Microsoft that pushed PlaysForSure DRM, and then released the Zune with an incompatible DRM scheme, so that the music its allies had been selling wouldn't play on the Zune? The same Microsoft that got half the world writing code that only worked in Internet Explorer 6, and then broke compatibility in IE7, that pushed Silverlight as the primary way to develop for Windows Phone, and then discontinued Silverlight?

    Maybe, coming from the Microsoft world, you really are used to better backward compatibility than what you've seen from Apple. But both companies have cases where they went to great length to preserve backward compatibility and cases where they didn't.

  • by csumpi (2258986) on Saturday February 09, 2013 @05:07PM (#42845679)
    How about the other way around? Every time there is a major OSX release, Adobe programs break, Autodesk products stop working. And of course you don't find out about the software incompatibility until you upgrade.

    I have both OSX and Windows machines (although most of them run Linux), and have never run into software incompatibility issues with Windows upgrades. Not even from Windows XP -> Win7. On OSX, need to purchase a new version of Adobe and Autodesk products with every upgrade. New versions not available until several months _after_ the OSX upgrade, which completely blows. That's no "best legacy support", sorry.

    You called your parent a troll, not knowing what he's talking about - the pot calling the kettle black.
  • by BasilBrush (643681) on Sunday February 10, 2013 @10:53AM (#42849971)

    It seems background audio from Safari and other browsers is broken as well.

    Not broken. Prevented. Thank god. Web pages what play background audio are the spawn of satan.

    Audio that you choose to play still works perfectly of course.

Any given program, when running, is obsolete.

Working...