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.
Apple Releases iOS 9.3 With Night Shift, New Quick Actions, App Improvements, '1970' Bug Fix and More
- Thread starter MacRumors
- Start date
- Sort by reaction score
Scrap that...now I've opened weather/App Store apps I get the new 3D Touch options for them.
[doublepost=1458594976][/doublepost]
Strangely I get that on my iPad but not my iPhone.
[doublepost=1458595022][/doublepost]
Yeh, realised I had to open the app but didn't need to force close.
That does not explain why it could not be enabled manually or at a set time. If that is their reason, then it is a lame excuse and a poorly-designed feature nonetheless.
ugh, iPhone 6 and iPad mini 4 updated no problem. iPhone 5s and iPad airsick on the activation screen -.-
No , you are not alone.It happened on my husbands Air also .
Connect your iPad to iTunes on your computer and activate it from there . It worked for me .
Ok, thanks for the tip! Does it work as usual from there? Both the Apple Communities and their support Twitter is getting flooded with this now...
When I plugged in his iPad ( i'm the geek in the family...) it just asked for ID and code and it activated from there without a problem . iTunes saw right away that his iPad had been updated to 9.3 .
By the way , he is on PC and usually never connects his iPad to his computer.
Alright... Is it safe to update iTunes and OS X? So many people are spaming their Twitter about it, time to put up a warning?
UPDATE: They reached out to me via Twitter now, waiting for a response.
Yeah, does seem silly. Can't see just changing screen colours would tax the battery much if enabled manually or by time rather than 'sunset'. Probably coming as an iOS 10 / iPhone 7 exclusive feature. Wish they'd allow f.lux in the app store, even if they only allowed it to work on a schedule I'd be happy.
This is the smoothest my iPhone 5 has been since iOS 7! Excellent update.
Only complaint is no Night Shift for me
Apparently the A6 processor isn't powerful enough to slightly tint the screen orange...
So your only complaint is basically the only new really big feature not being available?
That annoying 3D Touch bug when iPhone is in Landscape mode is present and correct.
Presented itself in the last Public Beta; reported it to Apple but see they've not managed to fix it in time...
Presented itself in the last Public Beta; reported it to Apple but see they've not managed to fix it in time...
Alright, I'd be very thankful if you could respond on how it went!
I will but I can't promise I'll still be awake ! There is another hour ½ to go .652 MB on 1.56 GB
Was looking forward to night shift since it was first being reported despite the demented(?) decision to disable it in low power mode. It was the first and only thing in 9.3 that I looked for right after the update and couldn't find. Then I found the compatibility list here. I have an iPhone 5.
f.lux iOS (not allowed in store) doesn't seem to have this limitation, so I assume that Apple is still actively promoting unnecessary, wasteful, and (to many) financially foolish hardware updates with intentional but unnecessary software limitations. It's as though they're saying "Look at this cool feature.. we could make it work for you but feel that it's in our better interests if you update your phone regularly. Please don't evade our marketing decisions by jailbreaking." Reminds me of not supporting native res on the first rMBP despite having a number of scaling options, requiring a 3rd party hack or Windows in bootcamp to get the most out of the display. Who'da thought I'd need to turn to Microsoft to make Apple hardware shine. Why Apple seems to feel the need to cripple their hardware in various ways is still beyond me.
I'm not replacing a perfectly good phone for night shift, but I am annoyed. Thanks, Apple.
f.lux iOS (not allowed in store) doesn't seem to have this limitation, so I assume that Apple is still actively promoting unnecessary, wasteful, and (to many) financially foolish hardware updates with intentional but unnecessary software limitations. It's as though they're saying "Look at this cool feature.. we could make it work for you but feel that it's in our better interests if you update your phone regularly. Please don't evade our marketing decisions by jailbreaking." Reminds me of not supporting native res on the first rMBP despite having a number of scaling options, requiring a 3rd party hack or Windows in bootcamp to get the most out of the display. Who'da thought I'd need to turn to Microsoft to make Apple hardware shine. Why Apple seems to feel the need to cripple their hardware in various ways is still beyond me.
I'm not replacing a perfectly good phone for night shift, but I am annoyed. Thanks, Apple.
Confused about why I have to download the full 1.7gb update when I was already on the latest public beta...
Just updated my iPad Air via iTunes, albeit with a minor incident.
After the payload had been delivered to the iPad, iTunes bounced its icon and threw up a dialog that said "iPad could not be updated, because an appropriate response has not been received" or something to that effect. The progress bar on the iPad screen was paused, with a small bit of white.
Is that the activation error some are referring to?
After a brief panic, I checked the updater logs, which said the restore was finished and successful, which put my mind at ease. After a minute or so, the progress bar started to move, and finished the update process.
I've seen glitches like this before, where iTunes throws up a false(?) error dialog but updates complete successfully.
Apple really needs to do something about iTunes.
Edit:
Same thing with iPhone 6+. What the error actually says is "iTunes could not connect to iPhone because an inappropriate response was received" (I think).
Basically, I think what is happening is that iTunes is trying to connect to the device after it has received the payload and is in the process of updating. The device then says "bugger off," which confuses iTunes, while it continues to finish the process.
Each successive update to both iOS and iTunes has seemingly brought little glitches and changes in the way the process works...when the passcode is required, the mini-setup sequence...etc.
I don't pay enough attention to keep track of all the nuances, but as a matter of polish, and consistency, there is work to do.
After the payload had been delivered to the iPad, iTunes bounced its icon and threw up a dialog that said "iPad could not be updated, because an appropriate response has not been received" or something to that effect. The progress bar on the iPad screen was paused, with a small bit of white.
Is that the activation error some are referring to?
After a brief panic, I checked the updater logs, which said the restore was finished and successful, which put my mind at ease. After a minute or so, the progress bar started to move, and finished the update process.
I've seen glitches like this before, where iTunes throws up a false(?) error dialog but updates complete successfully.
Apple really needs to do something about iTunes.
Edit:
Same thing with iPhone 6+. What the error actually says is "iTunes could not connect to iPhone because an inappropriate response was received" (I think).
Basically, I think what is happening is that iTunes is trying to connect to the device after it has received the payload and is in the process of updating. The device then says "bugger off," which confuses iTunes, while it continues to finish the process.
Each successive update to both iOS and iTunes has seemingly brought little glitches and changes in the way the process works...when the passcode is required, the mini-setup sequence...etc.
I don't pay enough attention to keep track of all the nuances, but as a matter of polish, and consistency, there is work to do.
Last edited:
