Not sure I'd say that something as complex as today's mobile OS is really "simpler software".
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 Pulls iOS 9.3.2 Update for 9.7-Inch iPad Pro After Bricking Complaints
- Thread starter MacRumors
- Start date
- Sort by reaction score
Why? Really....
QA executes a predetermined test set (active and regression). The scope of the testing is usually determined by the engineers and "fine tuned" by management. Or finance.
Blame the QA process, not the people executing QA itself.
Well, like I said, things like that would always be nice.
[doublepost=1463768238][/doublepost]
It's certainly a combination of it all--sometimes it's an issue in one area, other times in another, and yet other times it's across multiple areas.
And yet the numbers don't back up that idea. It was way worse than the percentage I came up with, but way less than the 100% you came up with.
What's enough? Clearly it seems that not everyone with iPad Pro was affected, so it's a sub-section, which means there's something about some of those devices potentially, which needs to be figured out. Again, most things like that don't happen immediately unless the impact is truly extremely widespread and uniform in its effect. I'm not saying this is the best thing or anything like that, simply pointing out that this is within the norm of the reality in which all of this exists (and is in fact even better/quicker than it is for many other companies at times).
It's not surprising that the newest version of the iPad is the one with the problems. It's probably the one in shortest supply in the QA groups.
If they can bring back the dead ones that folks are exchanging, they'll have plenty now.
If they can bring back the dead ones that folks are exchanging, they'll have plenty now.
I walked into the Apple Store and was able to make all the iPhones that had full signal go to either 1 bar or no service. It happened to me launch day and I didn't even know what was happening until reports of it hit this site. It was a design flaw that every 4 had. Granted if you had the case or if you took Steve Jobs advice of holding it different you wouldn't experience it. But the fact is if you held it a certain way its antenna would become bridged. It wasn't some flaw some had. It was a design they all had.
Case? Didn't hold it the way necessary? Unreported like most issues? Made up percentage by apple? You can take any GSM iPhone 4 and do it and it will happen.
Beyond privacy and premium prices I don't even know what this company can claim to consistently stand for.
Probably precision in hardware manufacturing, mind you I'm not saying hardware design in general.
Meanwhile, Google I/O '16 happened and while I don't want to give Google even more data about me, I must say that they show very well that you can still wow people in 2016, there really is no need to artificially hold back features to have more to fill your keynotes with a year later.
Haven't watch the entire presentation yet, but so far - and this is also true for the last couple of Google I/O's, I have not once felt bored and being fed insane rehash BS.
Apple's keynotes are now 20% bubble filler, 50% rehash (look, yesteryear's features now on our other platforms, too! WOW), 20% incremental updates, 10% what I'm actually coming for.
Well, at least that was Apple's last keynote.
Oh, I also forgot to mention the bag of disappointment and holding back.
Maybe that's part of the 50% rehash piece though.
Glassed Silver:mac
Probably precision in hardware manufacturing, mind you I'm not saying hardware design in general.
Meanwhile, Google I/O '16 happened and while I don't want to give Google even more data about me, I must say that they show very well that you can still wow people in 2016, there really is no need to artificially hold back features to have more to fill your keynotes with a year later.
Haven't watch the entire presentation yet, but so far - and this is also true for the last couple of Google I/O's, I have not once felt bored and being fed insane rehash BS.
Apple's keynotes are now 20% bubble filler, 50% rehash (look, yesteryear's features now on our other platforms, too! WOW), 20% incremental updates, 10% what I'm actually coming for.
Well, at least that was Apple's last keynote.
Oh, I also forgot to mention the bag of disappointment and holding back.
Maybe that's part of the 50% rehash piece though.
Glassed Silver:mac
It's not an engineering group that owns this, it's a quality and release group run by https://www.macrumors.com/2014/04/22/kim-vorrath-bug-wrangler/. They scrape Twitter and forums like this at release time looking for problems like this. They knew within a couple hours of release that they had a major problem.
They continued shipping this destructive update to iPad Pros for a whole week, knowing it would cause additional irreparable harm to customers. They did it because pulling the update makes them look bad. It's an admission of fault, and one that gets lots of press.
If they're screwing up trivial releases like 9.3.2, God help anyone who installs the public betas of iOS 10 and Fuji next month.
By and large the iPhone 4 was much more sensitive to the network than any previous iPhone due to that design. The sensitivity, combined with software, made the readout that displayed the bars by previous calculation pretty moot and inaccurate.
The juxtaposition lays in that you could go further than any previous iPhone while cupping it, but you could go even further by not cupping it or having a case. If the antenna issue was a flaw, they wouldn't have kept it until todays iPhone. It could have been designed better, but it was before the iPhone 4S launched. If it was a flaw it would have affected GPS and Wifi the same way, when in reality Wifi was improved by griping the phone. It was an issue, don't get me wrong, but the general populace was incorrect on what was happening and ~science~ has proven that - that's why there was no recall.
To be fair, enterprise (Pro) environments dont "do what Microsoft suggests" and update on day one the 2nd Tuesday of every month. They tend to test things 1st before rolling it out. So same thought should apply to Apple "Pro" devices.
To be clear I am not advocating this bad update was ok as it was not. And yes it should have been pulled on day 1 until they got a handle on whats going on. Just mentioning that Pro devices typically follow a different process for updates for reasons like this one.
I guess they will fire Federighi since he wont apologize for this.
On the contrary I update asap because you still have a few days to go back to previous version if things go bad. Waiting several weeks eliminates that option and you are stuck with it. Now in this particular instance apparently you cant go back to previous either but not sure that has every happened before.
yes. better than killing a lot of devices and having to replace stock. There is no real urgency in pushing the update. Hell it was in beta forever and beta 4 was two weeks. Pulling it for a few more days, THEN investigate what is actually happening may be a better plan and shouldn't be a big deal.
No, it really is. 9.3.2 is proof. Win users will feel right at home with botched updates.
Seriously, this seems to affect a very small sample of Pro 9.7 users, of which is probably the smallest user base of all iPad users given it's only a couple months old and it's price disuaded a lot of people (like me) from buying until it went on sale (which it currently is). That does make real life beta testing more difficult. I'm not excusing Apple here, esp. their reaction (and inaction) after the bricking became news, but I understand the situation. They made good and replaced bricked units at well. It would have been a bit less understandable if it had happened with an older, more widely distributed model.
That said I am glad Apple finally shut off the spigot because I was getting annoyed with the popups asking if I wanted to update.
Dunno why you gotta drag Windows into this. MS updates hundreds of millions of computers with thousands of different hardware combinations (and practically no phones!) every week and you almost never hear about an update being pulled.
You may not like Windows, but it's not a good platform to cite if you're trying to make an argument that updates are too hard to do well.
Well, the iPad can't make a phone call, so yeah guess it's disabled
[doublepost=1463770480][/doublepost]
They were hoping it'd go away on it's own. Apple is traditionally slow at acknowledging problems.
You mean management that dictates release it on date we command, even with potential bugs.
It was my understanding this was NOT the case with this error. From the sound of things it seems like you're taking the device in for it to be repaired/replaced or whatever.