Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Reason to update to 8.2 without buying an apple watch
- Thread starter zoneee
- Start date
- Sort by reaction score
Thank you for your contribution to the thread
----------
He is trolling since one of my first posts here, you are wasting time. he probably ignored also all of the discussion about battery life.
upgrade to iOS 8.2, it is faster
updated both iPhone 6 (16 and 64 GB) and iPad 4 - the 3 now feel faster. Seems like they tweaked animation speed a little. iPad 4 rotation, five finger gesture, app opening cinematics are smoother. Enjoying it.
updated both iPhone 6 (16 and 64 GB) and iPad 4 - the 3 now feel faster. Seems like they tweaked animation speed a little. iPad 4 rotation, five finger gesture, app opening cinematics are smoother. Enjoying it.
You had 8.0.2 installed? Each update fixes bugs, adds new features, tweaks things, etc.
Plus, there are SECURITY FIXES. Once an update is out, Apple publishes a list of fixes. It's important to update, as information on how to exploit the older versions is now in the public.
Here's some security fixes you don't get by staying on 8.0.2:
8.1 security fixes:
CVE-2014-4428: A malicious Bluetooth input device may bypass pairing
CVE-2014-4448: Files transferred to the device may be written with insufficient cryptographic protection
CVE-2014-4449: An attacker in a privileged network position may force iCloud data access clients to leak sensitive information
CVE-2014-4450: QuickType could learn users' credentials
CVE-2014-3566: An attacker may be able to decrypt data protected by SSL
8.1.1 security fixes:
CVE-2014-4460: Website cache may not be fully cleared after leaving private browsing
CVE-2014-4455: A local user may be able to execute unsigned code
CVE-2014-4461: A malicious application may be able to execute arbitrary code with system privileges
CVE-2014-4451: An attacker in possession of a device may exceed the maximum number of failed passcode attempts
CVE-2014-4463: A person with physical access to the phone may be able to access photos in the Photo Library
CVE-2014-4457: A malicious application may be able to launch arbitrary binaries on a trusted device
CVE-2014-4453: Unnecessary information is included as part of the initial connection between Spotlight or Safari and the Spotlight Suggestions servers
CVE-2014-4452, CVE-2014-4462: Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution
8.1.3 security fixes:
CVE-2014-4480: A maliciously crafted afc command may allow access to protected parts of the filesystem
CVE-2014-4481: Opening a maliciously crafted PDF file may lead to an unexpected application termination or arbitrary code execution
CVE-2014-4455: A local user may be able to execute unsigned code
CVE-2014-4483: Opening a maliciously crafted PDF file may lead to an unexpected application termination or arbitrary code execution
CVE-2014-4484: Processing a maliciously crafted .dfont file may lead to an unexpected application termination or arbitrary code execution
CVE-2014-4485: Viewing a maliciously crafted XML file may lead to an unexpected application termination or arbitrary code execution
CVE-2014-4486: A malicious application may be able to execute arbitrary code with system privileges
CVE-2014-4487: A malicious application may be able to execute arbitrary code with system privileges
CVE-2014-4488: A malicious application may be able to execute arbitrary code with system privileges
CVE-2014-4489: A malicious application may be able to execute arbitrary code with system privileges
CVE-2014-8840: A website may be able to bypass sandbox restrictions using the iTunes Store
CVE-2014-5352: A malicious application may be able to execute arbitrary code with system privileges
CVE-2014-4491: Maliciously crafted or compromised iOS applications may be able to determine addresses in the kernel
CVE-2014-4495: A malicious application may be able to execute arbitrary code with system privileges
CVE-2014-4496: Maliciously crafted or compromised iOS applications may be able to determine addresses in the kernel
CVE-2014-4492: A malicious, sandboxed app can compromise the networkd daemon
CVE-2014-4493: A malicious enterprise-signed application may be able to take control of the local container for applications already on a device
CVE-2014-4494: Enterprise-signed applications may be launched without prompting for trust
CVE-2014-4467: Visiting a website that frames malicious content may lead to UI spoofing
CVE-2014-4465: Style sheets are loaded cross-origin which may allow for data exfiltration
CVE-2014-3192, CVE-2014-4459, CVE-2014-4466, CVE-2014-4468, CVE-2014-4469, CVE-2014-4470, CVE-2014-4471, CVE-2014-4472, CVE-2014-4473, CVE-2014-4474, CVE-2014-4475, CVE-2014-4476, CVE-2014-4477, CVE-2014-4479: Visiting a maliciously crafted website may lead to an unexpected application termination or arbitrary code execution
8.2 security fixes:
CVE-2015-1063: A remote attacker can cause a device to unexpectedly restart
CVE-2015-1065: An attacker with a privileged network position may be able to execute arbitrary code
CVE-2015-1061: A malicious application may be able to execute arbitrary code with system privileges
CVE-2015-1062: A malicious application may be able to create folders in trusted locations in the file system
CVE-2015-1067: An attacker with a privileged network position may intercept SSL/TLS connections
CVE-2015-1064: A person with physical access to the device may be able to see the home screen of the device even if the device is not activated
Sources:
https://support.apple.com/en-us/HT203119 (8.1)
https://support.apple.com/en-us/HT6590 (8.1.1)
http://support.apple.com/en-us/HT204245 (8.1.3)
https://support.apple.com/en-us/HT204423 (8.2)
Overall it's not faster than 7.1, but it's faster than 8.1.3 which is faster than 8.0.2.
I can see te differences between iOS 7.1 and iOS 8, but not really anything really noticeable between the different iOS 8 updates.
Maybe you just have a bad battery and you need to take it to the Apple store to check it out? Actually you can call or set up support call from internet and they will send you a text message that will run diagnostics on your phone. This will tell right out the gates if you have a bad battery.
Sometimes it really is that simple. iOS is not the root of all hardware problems.
I always install the latest patch. Maybe not right away, but at least within a day or two.
Security patches are the primary reason, but 8.2 does seem to contain tweaks that make the animations on my iPhone 5 smoother.
Security patches are the primary reason, but 8.2 does seem to contain tweaks that make the animations on my iPhone 5 smoother.
It does feel a little snappier to me as well, but this may just be placebo effect. The synthetic benches look to be similar to 8.1 for me.
I was, however, having an issue with Safari where individual tabs would crash and reload occasionally that appears to have been fixed. OTOH, 8.2 wiped out my Safari favorites (but not other bookmarks).
There's "bug fixes" in every update. It never says "This update contains these bugs:", but that happens.
It sounded like your original comment was saying, "go ahead, don't update, you don't get all these bug fixes", assuming it won't add bugs the updater hadn't anticipated.
Okay, that's my iPhone 5 result with iOS 8.2. No cellular data, only wifi.
Attachments
Updated my 5s with ios 8.2. The changes in health app are very positive. I know it's too early to tell for sure, but battery life seems to be about the same. Personally, I've adopted the strategy of just doing latest updates as soon as they are available. Saves me the agony of deciding, do I, or do I not.
I'm not seeing any speed improvements, not that my phone was especially slow to start with. 8.2 does perhaps seem slightly less buggy overall, and the battery life has improved for me. Aside from the battery, which was definitely worth me updating for, I can't really see any night and day changes.
----------
The battery on my i5 took a monumental downturn when iOS7 was released and it never improved with any of the subsequent updates. My father has it now and he refuses to put iOS8 onto it after iOS7 ruined his previous iPhone 4. The bottom line for me is that the iPhone 5 had poor battery life. I got around 5 hours of usage with heavy use. My 6+ returns more than double what my i5 ever did.
5 hours of heavy usage wouldn't be bad for an iPhone 5. It would actually be even a bit more than just OK.
Updated my 5s with ios 8.2. The changes in health app are very positive. I know it's too early to tell for sure, but battery life seems to be about the same. Personally, I've adopted the strategy of just doing latest updates as soon as they are available. Saves me the agony of deciding, do I, or do I not.
Plus with this strategy you can go back to previous version if for whatever reason the newest causes any issues. (for a few days at least)
----------
Wow finally you didn't loose another hour or two! Great news. Also the status bar appearing in pics in iMessage is fixed as well (some were really annoyed with that)
It was just continuous WiFi web browsing. Perhaps not 'heavy use' as such, no games or 3G use. On iOS6 it returned 8.5 - 9.5 hours doing the same thing...
My old iPhone 5 used to get me by almost and entire day and that's with moderate usage of emails, texting, and phone calls. I'm thinking your battery is/was losing charge and needed to be replaced. I'm sure if you had it tested or ran a battery app to test it it would confirm my thoughts. I think if you bought a new battery that would eliminate the problem.
Old news now, I don't have the phone anymore but the battery tested out fine. It was awesome until the moment iOS7 was installed and then I instantly lost approx three hours of usage time per charge cycle. I never got to the bottom of it.