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.'"
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.
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.
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.
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/.
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.