Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Waiting for iOS 8.0.2 thread

Status
Not open for further replies.
batting1000 said:
Surprised they didn't hot fix it and release it yesterday. I still don't get how an issue like this gets by the software team and the carriers.
Click to expand...

Me too, there are still thousands of people out there with phones that are bricked. It will most likely be tomorrow. They specifically said a few days which means they are giving themselves a deadline.
 
BrettDS said:
Haha... If you search back in this thread you'll find a quote from me saying exactly that same thing. But after apple's statement about the issue and the fact that said it may be several days it makes me think that they are treating it less like the emergency I thought it was and more like a normal release.
Click to expand...

It's an emergency, but, do you really think they can fix it in 12 hours or so, no, the fact that they are working on it is the only thing that matters, they have to fix it and test it, after what happened with the release of 8.0.1, I don't think they will risk it.
 
im kinda hoping they adding more bug fixes to iOS 8.0.2 then what we saw with iOS 8.0.1

besides the obvious fixing cellular and touch ID issues
 
C DM said:
A lot of landlines today are provided by non-phone company providers, like cable providers for example, and those go through a modem and work almost like VoIP so if the power goes out, short of a backup battery in a modem that lasts for a bit, there's no landline service.
Click to expand...

Yep. That's why I still have an old school copper wired land line, and keep an analog phone in the bedroom.
 
nikicampos said:
It's an emergency, but, do you really think they can fix it in 12 hours or so, no, the fact that they are working on it is the only thing that matters, they have to fix it and test it, after what happened with the release of 8.0.1, I don't think they will risk it.
Click to expand...

Testing? Lol there was plenty time including carrier testing for iOS 8.0.1 and they didn't notice that 6/6+ signal and touch id are broken? Maybe they didn't get 6/6+ for testing because Tim wanted more proft? o_O
 
i thought touch ID and cellular service was only broken if you did OTA and it worked fine through iTunes? meaning the fix should not be that hard to resolve in a matter of a few days.. to me it sounds like OTA was broken and needs fixing.
 
mattburley7 said:
i thought touch ID and cellular service was only broken if you did OTA and it worked fine through iTunes? meaning the fix should not be that hard to resolve in a matter of a few days.. to me it sounds like OTA was broken and needs fixing.
Click to expand...

That's true.
 
mattburley7 said:
i thought touch ID and cellular service was only broken if you did OTA and it worked fine through iTunes? meaning the fix should not be that hard to resolve in a matter of a few days.. to me it sounds like OTA was broken and needs fixing.
Click to expand...

iTunes also broke it.
 
I love how the speculation of when the new fix will come. Someone said fix it and text it before releasing.... Huummm I thought they did that with 8.0.1 On the up side, I feel for all those that ran the update only to end up with a mostly useless object. At least until they get a fix for the damage they caused.
 
karstas said:
Testing? Lol there was plenty time including carrier testing for iOS 8.0.1 and they didn't notice that 6/6+ signal and touch id are broken? Maybe they didn't get 6/6+ for testing because Tim wanted more proft? o_O
Click to expand...

So you are saying they won't test 8.0.2 after what happened to 8.0.1

You are funny!!
 
i still think they will wait till 10am and release it like they have done for all iOS releases emergency or not.
 
I7guy said:
Absolutely true.

But the OTA is update is a convenience feature and you have to think the process through on how critical your phone is to you at a given point in time in the future if the OTA fails; and can't be easily restored.

You might want to think through, for example, doing a full backup and then having iTunes install the update at a time when you didn't need to call 911 for a period of time.

It is possible an OTA could bork the phone for a myriad of reasons beyond this specific last incident. So if a mission critical item for you is calling 911, then you think through the ramifications of having an OTA fail. It's on your shoulders, not apples to ensure you follow best practices.
Click to expand...

Yea, I normally schedule my emergencies too. Next time I update my phone I'll check my emergency calendar and make sure I don't have one coming up anytime soon.
 
WordMasterRice said:
Yea, I normally schedule my emergencies too. Next time I update my phone I'll check my emergency calendar and make sure I don't have one coming up anytime soon.
Click to expand...

Sarcasm in this instance doesn't work very well. As then you shouldn't be updating your phone for a non-critical updates in light of potential emergencies. If that is really the case, like MDs, you need a backup phone or pager.

The reality is, these updates do fail above and beyond the 8.0.1 issue.
 
I7guy said:
Sarcasm in this instance doesn't work very well. As then you shouldn't be updating your phone for a non-critical updates in light of potential emergencies. If that is really the case, like MDs, you need a backup phone or pager.

The reality is, these updates do fail above and beyond the 8.0.1 issue.
Click to expand...

Whatever makes it easier for you to dismiss Apple's failures. More power to ya.
 
I7guy said:
Sarcasm in this instance doesn't work very well. As then you shouldn't be updating your phone for a non-critical updates in light of potential emergencies. If that is really the case, like MDs, you need a backup phone or pager.

The reality is, these updates do fail above and beyond the 8.0.1 issue.
Click to expand...

I don't believe fault lies with the consumer of the devices involved. I believe fault resides with the company that issued the update.

It is reasonable, that the average user of the device (upon seeing an update was available) would update the device at the earliest convenience. The consumer had no way to know that the device would be affected in such a manner as to render the phone inoperable.
 
It's bizarre it's not out yet. This makes it look worse than it already is. Hopefully Apple employs teams of folks that work 24 hours for 30 days after an new iOS version comes out.

But seeing how long it took them to fix iOS7+5S random rebooting issue, there's not much hope left for this company.
 
Razeus said:
It's bizarre it's not out yet. This makes it look worse than it already is. Hopefully Apple employs teams of folks that work 24 hours for 30 days after an new iOS version comes out.

But seeing how long it took them to fix iOS7+5S random rebooting issue, there's not much hope left for this company.
Click to expand...

All hope is not lost for Apple.
 
Razeus said:
It's bizarre it's not out yet. This makes it look worse than it already is. Hopefully Apple employs teams of folks that work 24 hours for 30 days after an new iOS version comes out.

But seeing how long it took them to fix iOS7+5S random rebooting issue, there's not much hope left for this company.
Click to expand...
That seems like a long time to work, I hope they get breaks.
 
mattburley7 said:
im kinda hoping they adding more bug fixes to iOS 8.0.2 then what we saw with iOS 8.0.1

besides the obvious fixing cellular and touch ID issues
Click to expand...

I have nothing to base this one, however I suspect that with the PR spanking that Apple has taken this week, they are going to make sure that 8.0.2 is darn good. Maybe not perfect, however I suspect that it will have numerous bugs worked out.
 
BasicGreatGuy said:
I don't believe fault lies with the consumer of the devices involved. I believe fault resides with the company that issued the update.

It is reasonable, that the average user of the device (upon seeing an update was available) would update the device at the earliest convenience. The consumer had no way to know that the device would be affected in such a manner as to render the phone inoperable.
Click to expand...

However you see on various threads on this site that there are one-off situations where phones seemed to be "bricked" after an update.

Therefore, it should always be in the back of your mind, should I make a major download or download an app update if I find myself in a situation where I am unable to recover. Like at an airport getting on a 24 hour flight.
 
Status
Not open for further replies.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back