Im still trying to figure out what a normal non-techie person would do in this situation if they updated via OTA. Even your typical Android user would not know what to do let alone iOS users if they lose cell service. I never had issues with my non-techie wife accepting updates until today. Nothing good can come out of this. This is worst then those iCloud leaks. Losing cell service is pretty critical.
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.
iOS 8.0.1 Causing No Service, Touch ID Issues on iPhone 6/6 Plus, Apple Support Recommends iTunes Restore
- Thread starter MacRumors
- Start date
- Sort by reaction score
Im still trying to figure out what a normal non-techie person would do in this situation if they updated via OTA. Even your typical Android user would not know what to do let alone iOS users if they lose cell service. I never had issues with my non-techie wife accepting updates until today. Nothing good can come out of this. This is worst then those iCloud leaks. Losing cell service is pretty critical.
If Apple knew what's best for them, they better have a team pulling an all-nighter with an ultimatum to have it released by the morning. Seriously, are their heads up their asses? ****ing Safari can't copy and paste? Now this? Don't they ever even test **** out there? This is embarrassing.
Yes, that worked.. Picked up right where it left off. A little nervous pulling that plug but it worked!!!! Thanks!!
Yea, this one was a doozy! I guess having the previous version fully downloaded and at the ready won't hurt or at least having links to sites that keep them.
To be honest though, many normal users would be screwed and probably would have to call Apple Support or take the phone in.
Yeah, that's what I thought, which made me question this statement.
Yet it doesn't make sense. Those who updated OTA had these bugs, those who updated via iTunes did not (hence the "fix" to update via iTunes). How could the OTA update for the 6 and 6 Plus differ from the iTunes update?
Ahh, that makes sense.
Apple Maps was not forgivable IMO. Beta testers frequently complained about the inaccurate data, Apple knew about the inaccuracy of Apple Maps yet they chose to release it anyway. Apple could have delayed, but they chose to release anyway. It wasn't up to par with the product it was replacing ( no transit, for example ).
So what if the data was sourced elsewhere? Doesn't matter, it was on the onus of Apple to get the product in a stable position for release. Apple can't blame a bad dataset and release anyway. The data set was from TomTom was it not? TomTom wasn't unreliable?
For US customers Maps may have been just about ok, but for anyone else, it was not a good product release.
Last edited:
My smartphone might be bent but it is made out of aluminum so it's all ok.
----------
Bah.. big deal. It's fixable without the customer spending money or exchanging for a new phone.
How do you fix a bent phone or a bad camera parts of a phone? I don't think they have apps for that.
And Apple deserves everything they get in this case. They are their own worst enemy right now.
Is it "bah , its apple, big deal... I'll give Apple a pass since its my favourite company"... by any chance?
Maps put Apple in a bad light.. I'm sure that Apple looks negative with bendable phones!
Up to Apple to maybe compensate the customers affected if the level of bendable is exceptional.
Yeah what I was thinking. That seems to be the normal now. Past 2 months MS updates have been pulled and reworked.
I like Apple. Been a customer and early adopter for 15+ years but this is another example of recent shoddy output,
1. Health apps pulled.
2. U2 album mess - a removal tool? Really?
3. Bendy phones.
4. Rushed update bricking phones. Users gotta jump through hoops to fix it.
They need to slow things down, get back to thorough testing, and ship when ready, not by deadline.
1. Health apps pulled.
2. U2 album mess - a removal tool? Really?
3. Bendy phones.
4. Rushed update bricking phones. Users gotta jump through hoops to fix it.
They need to slow things down, get back to thorough testing, and ship when ready, not by deadline.
The maps fiasco was bad PR but there were a few differences. First, it was Apple's very first foray into an area they weren't experienced in. There were also alternatives people could readily use that still functioned fine, although due to the way iOS behaves you can't set those other choices as default.
This on the other hand, broke the most basic function of the device, possibly cutting off the very connectivity it would need to get fixed as well. It's one thing to leave users uncomfortable, but it's a totally different story when you completely cripple a device.
You are seriously missing the point. Aluminum is known to bend if pressure is applied in various situations. Plastic will crack. What part of DON"T SIT ON YOUR PHONE do you not get? If you sit in a curved chair with all your weight on top of your aluminum phone, it will bend. It's not rocket science.
I can forgive software issues (or data issues, as was the case with Maps) as Apple has had a history of releasing updates that fixed the issues.
Hardware issues, not so much.
iOS 8.0.1 in of itself I don't really care about. But evaluated within the greater context which includes bend-gate and camera-gate, the evidence seems to be mounting that attention to quality is just not there.
You're on the wrong website if you don't want to see jokes get run into the ground, regurgitated and repeated... (think Safari snappiness) Not that I approve of that behavior, though.
