Slashdot Mirror
iOS 6.1 Leads To Battery Life Drain, Overheating For iPhone Users
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.'"
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.
I've decided to Diversify my Holdings. I've divided my cash between my left and right pockets, instead of all in one.
iOS 6.1 - iPhone 4S - no issues. Don't know where TFA is getting this from.
It's a feature to keep user's hands warm during the cold winter months, which will be turned off in a future release when the seasons change.
- Apple PR
Trolling much?
http://www.phonesreview.co.uk/2012/12/17/galaxy-s3-jelly-bean-problems-since-verizon-update/
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.
...to keep from fucking things up all the time.
Nice attempt at trolling, but since Apple is a licensee to the ActiveSync protocol, they are fully within control of how they implement that spec and thus responsible for any issues that crop up when none existed before...
"proprietary" and "non-standards compliant" doesn't equate to "shit", it just equates to "I can't download the spec from a website and implement it". If you implement the protocol badly, it doesn't matter whether it's proprietary or not. If you don't control both ends of a connection, then you are entirely dependent on how the other end implement the protocol, proprietary or not.
One of the strong points of iPhone is the fact that it is very manufacturer supported. It is *THE BEST* menufacturer supported consumer device out there. I don't care what you cheer for or what you bought, I think there's simply no denying Apple's iPhone is at the top in this category. They get updates. They get fixes. The carrier does not and cannot get in the way. (Though in the early days with AT&T demanding Apple disable tethering and all that kinda sucked.) After saying all this, you would think I'm another Appe fanboy. I'm not. I'm not any kind of fan boy, but I choose Android over all others and choose carrier independence by going with unlocked, rooted and custom ROM'd phones. So all that out of the way, what am I talking about cutting both ways?
Well, this: Apple pushes updates to the whole OS -- kernel, apps and all, to all users and all [selected] phones. "The experience" is pretty important to Apple and that it should be consistent is a high priority to them. I think their rate of updates appear to be okay but their all-or-nothing thing is a problem in that problems like these occur and from what I understand, going back to a previous version is not done... not casually anyway and requires jailbreaking maybe?
The power of the various versions of the iPhones vary. Android devices vary a LOT more. And as I look at the potential of the devices, it is easy to observe that the hardware has limits which shouldn't be exceeded. I've been pissed off at T-Mobile and Samsung for not updating my SGS2 soon enough or for long enough, but sometimes the argument that the hardware can't support the software is true. This Apple story rather reminds me of that fact.
So it cuts when the device (iPhone or Android) doesn't get the updates users crave, but it also cuts when the updates kill the phone. I guess it's time for me (and anyone else who hasn't yet) to accept that my expensive phone(s) are to be considered short-term use devices with a life expenctancy of about a year... maybe a year and a half. (And certainly not the duration of the contracts that most people sign in order to get their new shiny.)
Wouldn't it be nice if we could have a more PC like experience with our phones? By that I mean, choose our body/case, display, processor, RAM, storage, radios and all that? I know... too much to hope for. Still, to fight be able osolecence would be nice.
Apple provides some of the best legacy support for their devices of all mobile vendors. By a WIDE margin, in many cases given that most other mobile vendors stop supporting a device the instant it's sold...
Also, on the desktop side, they continued supporting OS9 apps for almost a decade after moving on from that OS, as but one example of their legacy support. They not only provide some of the best legacy support in the industry, they also provide a great deal of advance warning of when that legacy support os going to end.
So, aside from just being a troll, I don't have a clue what you're talking about.
I solved my 6.1 battery issues by deleting and recreating my two exchange email profile.
Apparently this a common issue after iOS upgrades.
Apparently if you update a calendar item on your iOS device, it tries to update Exchange and fails.
It then retries continuously, chewing through battery life and log files: http://wmpoweruser.com/exchange-server-acting-up-blame-those-ios-6-1-users-then-ban-them/.
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.
I suggest switching to Linux.
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.
Please correct me if I got my facts wrong.
Every civilized person shouldn't venture more than 4 feet away from an outlet. Swapping batteries is so bohemian. This isn't some hippy love-in we're talking about.
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.
I thought the M$ thing was cool when I was a kid. Then I realized that Apple (and later Google) were all about making profits, too, so the whole $ thing seemed rather juvenile. No company is perfect, either with their products or their business tactics.
Anyway, to the topic on hand: As far as I know, it's a relatively uncommon issue. I haven't noticed any battery problems with my iPhone 5; I still recharge it every other night, and LTE/3G seem the same speed as usual. I'm not claiming that some people don't see the problem, but that it may not be as big a deal as the article/summary/headline makes it out to be. As is common for modern /., the headline itself makes it seem as if it's a problem with every iPhone running the new update. Also keep in mind that people will post complaints, and be more vocal about them, more often than they will post compliments.
For those who are experiencing this issue, though, I hope Apple fixes it soon.
If you can't convince them, convict them.
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.