Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
As in basically reality?
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.
How are they slow when often enough they acknowledge issues and release updates to fix them in a matter of days, when that is not exactly something that is common throughout the industry?
 
Last edited:
How are they slow when often enough they acknowledge issues and release updates to fix them in a matter of days, when that is not exactly something that is common throughout the industry?


Considering that they have refused to acknowledge manufacturing defects often until there is a class action suit, I'd say they are often slow to acknowledge problems.

Look at how many of their "lemon" machines have had warranty extensions due to class action suits.

My iMac was in the landfill by the time they finally acknowledged the faulty capacitor manufacturing defect.
 
Considering that they have refused to acknowledge manufacturing defects often until there is a class action suit, I'd say they are often slow to acknowledge problems.

Look at how many of their "lemon" machines have had warranty extensions due to class action suits.

My iMac was in the landfill by the time they finally acknowledged the faulty capacitor manufacturing defect.
So basically doesn't apply to this case and many like it then?
 
This is my situation.... Did the update the afternoon it was released and had no issues. But you have to wonder what's really going on here. My *guess* is, Apple must have sourced a component from multiple vendors and the 9.7" iPad Pros with one brand of the chip in them work ok with the update, but it bricks those using the other vendor's variant of the same chip?

What happens if your iPP 9,7 is already updated and working fine?
 
This is what happens when you "invest" in programmers from India. Terrible. Code. Apple, please please PLEASE don't do this. You think you're saving a few bucks, but the quality loss will cost you billions. We love your products because unlike Android and Windows, you're stuff works. If you put that in the hands of thousands of outsourced resources you effectively kill you brand and the reason why we love your products.
 
Actually, I'd say the whole PC industry has this problem. They screw up and then try to delay acknowledging issues as long as possible.

Years ago, a good friend of mine dropped a load of cash on the "best" Toshiba laptop available at the time, a Qosimo with a 17" LCD screen and the whole bit. Just past the 1 year warranty period, it was completely dead ... wouldn't boot at all. Turns out the motherboards in these were defective and often dying like that, but Toshiba only had a "silent recall" on them, meaning it was never published anywhere. You had to call in and throw a fit, getting it escalated to a higher tier of support person, who could then authorize a free replacement.

And my workplace just went through this with HP, too. We bought a bunch of their "Elitebook 840 G1" laptops, only to discover an obscure bug where it crashed on certain Excel spreadsheets. After more firmware and device driver updates, it finally got the point where it no longer crashed, but would miscalculate rows on the "problem" spreadsheets instead, unless you caught the math error and clicked recalculate multiple times. Suddenly, it would fill in a correct value! HP never did provide a full fix for the bug, and instead just discontinued the machine, coming out the the "840 G2" which was practically the same machine with a slightly different chipset.

Considering that they have refused to acknowledge manufacturing defects often until there is a class action suit, I'd say they are often slow to acknowledge problems.

Look at how many of their "lemon" machines have had warranty extensions due to class action suits.

My iMac was in the landfill by the time they finally acknowledged the faulty capacitor manufacturing defect.
 
  • Like
Reactions: dk001 and flyinmac
This is my situation.... Did the update the afternoon it was released and had no issues. But you have to wonder what's really going on here. My *guess* is, Apple must have sourced a component from multiple vendors and the 9.7" iPad Pros with one brand of the chip in them work ok with the update, but it bricks those using the other vendor's variant of the same chip?

Exactly my thoughts, perhaps a networking problem causing the install to abort?
 
I used to be incredibly excited every time that I heard a new update was coming out for one of my Apple products. I even remember that years ago (when I was in college and didn't have a job lol) I would stay up all night for some of the major releases, trying to download them AS SOON as they were available. I just couldn't wait to play with the new features.

Now I act as I did with Microsoft products before I made the big switch... Hold off on updates and hope that when I do finally upgrade, I will be able to still just use my Apple product as I had. Rather than being excited for new features (which are often lackluster), I simply hope that functionality won't be removed on account of a broken product...
 
So, with Apple it just works.......

What's this, the 4th time an update has been pulled due to bugs?
They must need an awful lot of bananas to feed those monkey's they have in the internal iOS quality assurance teams!
You see, those people would be fired at the first time if Steve was still around. But you know, Steve isn't around anymore. And Mr. Tim Cook focus on environment protection, equal right, trip to Asia or watch band than its products.
Yep, those monkeys know and they aren't afraid.
 
25% more tells me you're getting screwed by somebody. Where I'm from, the devices aren't 25% more than comparable products.

And here I thought he was being generous with the 25% remark. Where I am (Oz), retail prices for Apple equipment is substantially more than 25% higher, compared to a similarly spec'ed and built wintel machines. The higher up the chain you go, the larger the difference (a 15" MBP with dedicated graphics starts at AU$3800 here, I can get a better performing windows laptop for half the price).
 
And here I thought he was being generous with the 25% remark. Where I am (Oz), retail prices for Apple equipment is substantially more than 25% higher, compared to a similarly spec'ed and built wintel machines. The higher up the chain you go, the larger the difference (a 15" MBP with dedicated graphics starts at AU$3800 here, I can get a better performing windows laptop for half the price).

You have my attention. I'd love to see these machines. Maybe Apple is screwing Australia over?
 
Ok, so this clears it up for me. Thx.
[doublepost=1463766042][/doublepost]
Maybe. Certainly wouldn’t use the term relented though. Would have been a mistake.

Great example.
iPad Mini 2. No passcode is set. General use for around house by anyone.
Auto downloads are off.
It is now running 9.3.2. Automatically downloaded in back ground. Between 3:00AM and 5:00 AM the update was automatically installed.

iPad Mini 4. Passcode and TouchID set. Personal use.
Automatic Downloads are off.
It is running 9.3.1. Automatically downloaded in background. Attempted automatic install that failed due to passcode.
932_SS.PNG
No user actions taken at all other than connected to WiFi and plugged in at night while sleeping.
 
It applies in the sense that Apple has frequently attempted to wait it out and hope that the problem will go away, or the customers with problems will be discredited and silenced by loyalists before they are forced to actually deal with the problem.
But seemingly m not in the sense that in this case and some other similar ones where Apple acknowledged the situation, investigated, took action, and is working on a resolution.
 
I think you mean the press made a big deal out of it. Apple (SJ) initially blew it off. Apple only reacted when it was clear the reports were hurting the Apple brand. SJ fell on his sword and also gave out free swag and magically everyone was happy again.

I don't think this episode is a huge deal, but, again Apple is slow to react. That's what hurts them, that air of arrogance that it's always the user's fault.

My son had the phone. It was affected also. As far as I'm concerned every one was affected. It seemed like a small amount because most people held their phone in a way that didn't bridge the antenna. Either that or they used a case. At the time it seemed odd to me one case they offered was just enough to take care of the problem. Makes me wonder if they knew about the issue before the phone was released.
 
It's always a "small number" lol.

Anyway, I picked up a 9.7 Pro 128GB couple days ago. I already read about this bricking report, so I was a bit apprehensive, but I let it update anyway. It's been working great, so I'm in the "big number" group who is fortunate enough not to run into the problem :D
 
I'm waiting for a version of IOS that turns my Brick into a phone.

That's going to require the jailbreak version. However I'm thinking the brick would be more useful to break out of jail.

On the other hand, with a phone you could call a friend to come with the chains and horses to break the bars off the window. :D
 
  • Like
Reactions: Demo Kit
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.