Apple squashes iOS 11 bugs with quick release of iOS 11.0.1
Just a week after iOS 11 was launched to the public, Apple has quickly followed up with iOS 11.0.1, a small update intended to address bugs and fix various issues with the software.
Release notes accompanying iOS 11.0.1 simply state that the update "includes bug fixes and improvements for your iPhone or iPad."
There are two builds of the software: 15A402 for current iPhones and iPads, and build 15A403 for the forthcoming iPhone X.
iOS 11 includes a new voice for Siri, as well as the ARKit tools that developers can use to create advanced augmented reality applications. It also boasts a redesigned App Store, and various features like Do Not Disturb While Driving and a revamped Music app.
On the iPad, iOS 11 brings an all-new app dock that can be used for multitasking and app switching, as well as dragging and dropping files in between applications.
iOS 11 is compatible with the iPhone 5s and newer, the iPad 2 and up, the iPad Air and newer, and all iPad Pros. It is also compatible with the sixth-generation iPod touch.
Release notes accompanying iOS 11.0.1 simply state that the update "includes bug fixes and improvements for your iPhone or iPad."
There are two builds of the software: 15A402 for current iPhones and iPads, and build 15A403 for the forthcoming iPhone X.
iOS 11 includes a new voice for Siri, as well as the ARKit tools that developers can use to create advanced augmented reality applications. It also boasts a redesigned App Store, and various features like Do Not Disturb While Driving and a revamped Music app.
On the iPad, iOS 11 brings an all-new app dock that can be used for multitasking and app switching, as well as dragging and dropping files in between applications.
iOS 11 is compatible with the iPhone 5s and newer, the iPad 2 and up, the iPad Air and newer, and all iPad Pros. It is also compatible with the sixth-generation iPod touch.
Comments
in my ebay app, I get a freeze. Scrolling stops, tapping on something results in nothing. I have freezes in some others too. Doesn’t last for long, sometimes for just a few seconds. For example, in Eric’s Solitaire, when I select which game to play in the menu, sometimes nothing happens, and I have to select it again. Sometimes, when moving cards, they magnify as they’re supposed to, and freeze in that magnified state, only partly moved. I have to tap them to finish the move.
Sometimes, when I swipe an app to close it, nothing happens, and I have to do it again, maybe two more times.
and I’m still getting all the first letters of a new paragraph in lower case, entirely on this site. That’s why they’re not capitalized. It’s just too much trouble to constantly go back and delete it and then type it again, though, when I do, it will properly capitalize. Sometimes it will lose the ’ in a word such as “I’ve” if it’s the first.
When I updated to watchOS4, I got a battery low warning way early in a day I did some workouts right after the update (the next day, I think.) That seems to have mysteriously gone away, but the workout app eats battery. I can manage, as with occasional workouts in a day, I have just enough battery to get me through. I usually see about 15-25% battery when I put it on the charger at night. My wife's 38mm original AW is not so lucky. She is much more active than I am, and usually she runs out of battery after about 12-15 hours. If you are an athlete (she is) you will often not get "all day battery" from an original 38mm AW.
Yes, I know this is because of the HR sensor. You can turn it off, yes, but sort of what is the point then? And that is a rhetorical question.
1. Just got my Series 3 Apple Watch and then thing that bugs me the most is the red crown. Actually, had problems getting it set up on launch day, but it seems the was caused by AT&T's systems taking a hit. Got it up and running and making calls and GPS without my iPhone.
2. As a developer, I can say that this has been a great build. I've reported a number of bugs, but most or cosmetic and can be worked around. Apps developed on older SDKs work well running on iOS11. Does it have bugs? Yep. So does EVERY NEW OS RELEASE. The trick is, don't go and update immediately unless you want to be on that cutting edge.
3. All hearsay at this point. You're applying a rumor to reality. I'm pretty sure supply will be constrained simply due to the laws of economics. From the standpoint that Tim is judged on (profitability) he will be doing just fine with a six month back log of $1K+ devices.
4. Conjecture. I believe that Apple expected this when they released two phones. In the famous words of Steve Jobs, "we rather cannibalize our own sales" in regard to iPad. Same goes for iPhone X vs iPhone 8. You're complaining now that Apple is competing with itself?
5. No, AppleTV clearly supports H.264 and H.265 video standards. They don't support VP9, a stolen bit of IP designed to get around paying a licensing fee. It's up to Google to support H.265 and then devices that run it, not Apple.
5b. Dolby Atmos is coming in an update very soon so get over it.
if yoûre talking of that pos MacRumors site, I’d. Wager most people whining don’t actually own an iPhone...
also, you’re wrong about some things. LTE problems have been explained, and they’re not entirely Apple’s fault, though they can be annoying to those who are experiencing them. The problem is mostly with the WiFi standards regarding acquiring new networks. It was never intended for a device like the Apple Watch. It’s like my dentists Office. When I turn my iPad on in the waiting area, and go to safari, the WiFi network comes on asks for my password. Once I give it, and click “done” on the page, I’m transferred from LTE to their network. That’s how it’s supposed to work.
but it can’t do that on the Watch. So it gets stuck. As has been pointed out, turning airplane mode on and off fixes it. Apple will have an update. It’s been explained that Apple’s testers very likely didn’t encounter this so they weren’t aware of it. But fine, blame Cook.
what is Cook supposed to do here? He doesn’t do software. You can pretend that Jobs never had this issue, but he did. Remember MobileMe? A total mess. After it came out, Jobs was pissed, but he didn’t see the problems before it came out. Apple does a dance between bugs, features, and a needed date for release. Juggling that is difficult. Sometimes, depending on how difficult some of the work is, more bugs get released. That’s software development.
so you’re also blaming him because suppliers are having difficulty manufacturing complex parts on schedule? Seriously? It’s his fault that 40% of the OLED screens are faulty because of the difficulty of cutting the notch? It’s also his fault the the Face ID sensor module are also difficult to make?
weak sales of the 8 are being attributed to the high number of people wanting the X. Estimates are that Apple will see 40-50 million preorders for the X, and that it could go higher. This is a bad thing, according to you?
i do agree that Apple should rethink support for Google’s 9, but there’s another widely backed payment free standard being worked on that may replace it, called V1. Google is in that group, though Apple is not, for some reason. This is the only thing I can agree with you here. Atmos support is coming, as Apple has said, though almost no one will ever use it.
These are all pretty made up issues you’ve created. None of them are actually major, or even under Apple’s control.