Wonder how it runs on the ipod touch 6........yeah i know like HELL!!
Ok. Someone needs to ask this: since the last iOS was 11.2.2. Why the next one is iOS 11.2.5??
What about iOS 11.2.3 and iOS 11.2.4?
Anyone running iOS 11 on an SE?
I would like to update it, but I have been too scared to update my devices lately due to a some horrible issues I have experienced on multiple devices.
Thanks, I will probably wait to upgrade, or maybe I will stick with iOS 10.Simple, do not update.
I use it on SE, and it is full of bugs. I didnt try this last update and maybe i wont. With every update phone is working slower. Clock is disappearing, sometimes cant answer phone, bluetooth with my car connection is worse since ios 11. etc..
Before, everything was fine.
Wow, thanks for sharing! We'll be sure you feedback gets back to Apple immediately!The control panel is still way too busy looking. I still prefer my iOS 9.3.5 control panel. No, still not updating.
my iPhone 5s is running iOS 11.2.5 just fine, just updated it last night and so far this morning it is working good.
Thanks, I will probably wait to upgrade, or maybe I will stick with iOS 10.
This seems to be the new norm for Apple. It seems like every iOS since iOS 8, every update causes problem. Although some updates are worse on some models than others.
For me iOS 9 made my iPad Mini 2 unusable, although iOS 10 made it a little better. It was perfect with iOS 8.
Anyone still having the bug where apps are blurred so you have to reopen them to use? iOS has been a train wreck of bugs on the X...
Please do yourself a favor and DO NOT listen to other people’s hatred. UPDATE your iPhone ALWAYS, whatever the model!! Internet is full of rubbish about Apple, coming mainly from ignorant and jealous people! Please do not follow their idiotic recommendations!! I have been updating always, on day 1, from my first iPhone 5 up to the loving iPhone X and never faced ANY problem!! Please do not listen to the Android jealousy!!!
I might agree with you, if it wasn't for my own experience upgrading iOS devices.
I started with the original iPhone, and used to do what you did and upgrade right away, and I would look forward to it.
But, starting a few years ago, it seems like updates started to suck. Not only the bugs, and glitches, but also problems with slowdowns. Safari on my iPad Mini 2 was basically unusable after the iOS 9 update from iOS 8.
There is also an issue with Apple removing features with new updates.
I also have noticed a big inconsistency with experiences with updates, and not just with different devices, but with the same models. Some people update their device and have issues, another with the same model has no issues.... I am not sure what is going on...
Maybe, but if problems don't exist on one iOS version, but suddenly appear on the next version, I would be more likely to contribute the problem to the upgrade, not the device.I believe problems are not caused by updating, but mostly due to problems of the device itself, or its battery.
It's not taking a quarter year to implement, it takes some time to design and actually code, and then there's testing and the beta process, as is fairly typical for releases with new features. Is this somehow new or surprising?The issue came up in December and we’re talking about a fix in March, and all it’s supposed to be is the ability to see battery health and possibly toggle throttling. Basically just letting the user see information that the OS has always had. I can’t imagine why that should take a quarter of a year to implement.
Wasn't expected in essentially a bug fix release that has been known for some time. iOS 11.3, that's a different story: iCloud Messages Returns to iOS in First Beta of iOS 11.3Teacher from Ferris Bueller's Day Off (Voice): iMessages in the Cloud........iMessages in the Cloud.......iMessages in the Cloud.......
It's not taking a quarter year to implement, it takes some time to design and actually code, and then there's testing and the beta process, as is fairly typical for releases with new features. Is this somehow new or surprising?
[doublepost=1516823648][/doublepost]
Wasn't expected in essentially a bug fix release that has been known for some time. iOS 11.3, that's a different story: iCloud Messages Returns to iOS in First Beta of iOS 11.3
Designing how that information is displayed, what information is displayed, what messaging is shown for different states and conditions, what controls are available, etc., certainly takes some times. It's not some small tweak or bug fix, it's a new set of user facing features basically. Factor in other features that are going into a release that are being worked on and need to be tested and need to go through a beta process, and all of that takes some time. Security breaches don't generally require designing whole new user facing features but patching up an exploit, and the priority there is certainly quite different as well.Other issues seem to be addressed much more quickly, is all. Especially since, as I mentioned, providing the user with battery data doesn’t actually require changing how the OS operates or anything. It must already be assessing the battery internally in order to trigger the throttling. All Apple has promised is letting users see what the OS is already doing behind the curtain. I’m admittedly not an expert or even a novice, but I can’t imagine that that takes months of coding and beta testing. We see Apple and other OS developers respond to much more complex issues like security breaches much faster than that.
you have a genuine software corruption issue or a hardware issue. restore without restoring from back up..For the first 12 or so hours running this, I didn’t experience a single bug. Messages were in order again, my AirPods would sync, and i could make phone calls without my phone crashing. Now I can’t play audio of any kind, the podcast app freezes, messages are out of order, and I’m getting artifacts. YMMV, but I for one am taking my iPad and iPhone in; there has to be something wrong with both, however unlikely that may be. Been an iPhone user since the 3G, and devout iPad fan since day 1, so I’m not saying this from the perspective of an iOS/Apple hater.
Well, zachcsnyder is definitely having a point, imho.Security breaches don't generally require designing whole new user facing features but patching up an exploit, and the priority there is certainly quite different as well.
I understand the wishful thinking of having things as soon as possible, but the reality of nature of software releases is somewhat different nonetheless.Well, zachcsnyder is definitely having a point, imho.
If it’s a ’feature’ as Apple calls it, and it is toggled on by default as Apple sys, the interface and the actual cosing of the toggle command can not be that complex. The whole feature is let’s say already developed, it just needs a toggle. With the battery of personnel at Apple, sorry, this can’t be taking much time.
Priority you said? The longer it takes for Apple to deal with this issie, the more they show that their way out of the whole problem is not just like what it pretends it to be... minimizing a suspicion needs optimal recovery, and we’re not seeing that!
Or better: what’s the point of mentioning features that are unfinished? Because if one has such a world wide client base, why on earth would one prioritise whatever market to use that feature? Deployment to other markets with inconsistent equivalence of function, is like beta testing. Once the feature is discontinued, probably it was just good to be launched. Rolling eyeballs is a growing side effect of Apple’s experiences lately.Why has Apple not released Apple News for Canada? We have a "widget" but not a proper app. What's the holdup?
The reality of Apple’s story on the case is somewhat different.I understand the wishful thinking of having things as soon as possible, but the reality of nature of software releases is somewhat different nonetheless.