Earlier quoted context omitted.
Initially, I was thinking the same thing. Given how fast the average Apple consumer updates to major iOS releases, I imagine that rolling it out over a point release is actually part of the plan. Presumably, if something does go wrong on the individual level, the support burden on the genius bars will be lower (since major iOS releases have traditionally come alongside hardware releases), and if a major bug is found,…
Additionally, it may be a way of hedging their bets. If it all goes smoothly, great. However, if it turned into a big flaming dumpster fire, an iOS point release has a lot less to lose than a major release (and the associated new hardware that comes with one). "iOS Update Causes Widespread Outages" plays a lot differently with the average person on the street (who already distrusts software updates in general) than "…
Apple releases iOS 10.3
81–90 of 103 posts
Re: Apple releases iOS 10.3
#82Earlier quoted context omitted.
Initially, I was thinking the same thing. Given how fast the average Apple consumer updates to major iOS releases, I imagine that rolling it out over a point release is actually part of the plan. Presumably, if something does go wrong on the individual level, the support burden on the genius bars will be lower (since major iOS releases have traditionally come alongside hardware releases), and if a major bug is found,…
Rolling it out first on iOS at all doesn't seem like the right approach. If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as officially supported on the Mac, but off by default. 2) a year or two later, ship it as officially supported on the Mac, on by default, but still allow HFS+ as an option. 3) A year or two after that, if all has gone well, then introduce it into iOS (where presumab…
Re: Apple releases iOS 10.3
#83Here's the security info: https://support.apple.com/en-us/HT207617 Notably, ten kernel arbitrary code execution bugs, seven from Google Project Zero and two from Qihoo 360's research team. There are also a few WebKit RCEs, so it seems like it's prudent to update as soon as possible, lest a malicious website silently jailbreak your phone.
Re: Apple releases iOS 10.3
#84Earlier quoted context omitted.
> the upgrade time wasn't even significantly longer I wonder if it works like FileVault, where there's a notion of a "partially converted" volume and blocks are slowly converted as a background-idle task after the update completes.
Could be, it may be more like the ext3/4 -> BTRFS conversion process[1], where metadata for the new filesystem is written in the free space, but with pointers to the original data which isn't moved or re-written. [1] https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3
Re: Apple releases iOS 10.3
#85"An error occurred installing iOS 10.3"
Re: Apple releases iOS 10.3
#86Re: Apple releases iOS 10.3
#87Backup first. Both my parents phones went to recovery mode. They have an iphone 5c and another old model. Going to see if I can extract data. They didn't have itunes backups.
It's generally never a good idea to upgrade immediately to the new versions of iOS, as there are invariably problems.
Re: Apple releases iOS 10.3
#88Just updated all my devices and I must admit that things feel snappier, even the 5.
Re: Apple releases iOS 10.3
#89Earlier quoted context omitted.
There are two views when looking at ratings in the iOS App Store: Current version All versions It defaults to "Current version"
This is true, and also, when searching the app store the star ratings displayed next to each app are based on the "current version", so if an app is recently released it might say "0 reviews" even though it previously had thousands.
As an example: For my country (which is all I can see) Instagram has ONE rating on the current version and WhatsApp has none. For all versions, they have just 21k and 17k respectively. There are probably amongst the most popular apps, so their star-rating in the lists are based on one or less ratings.
Re: Apple releases iOS 10.3
#90Earlier quoted context omitted.
Rolling it out first on iOS at all doesn't seem like the right approach. If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as officially supported on the Mac, but off by default. 2) a year or two later, ship it as officially supported on the Mac, on by default, but still allow HFS+ as an option. 3) A year or two after that, if all has gone well, then introduce it into iOS (where presumab…
iOS has always used case-sensitive HFS, while macs usually need case-insensitive HFS. Since it looks like APFS will drop support for the case-insensitive file system mode, it makes sense to do the forced upgrade on the system that already uses a case-sensitive file system (= iOS). Plus, it's more straightforward recovering from a broken FS upgrade on iOS since many customers will have iCloud backups enabled, or at le…
Maybe misremembering. But someone had hacked it to run as a boot drive, and in doing so, found the setting.