Q: IOS 7.1.2 is buggy, don't update

AmishCake wrote:

 

I don't remember anyone ever saying that, anywhere.

Only PoochJD said it, and he was the one complaining about it

PoochJD said it

Yup, that's the only place I can find anything like that.  No one here ever said Apple was infallible.  Anyone remember iOS 7.0.6, and the main reason it was released?

Hi,

Okay then:

Page 10 of this thread - Lawrence Finch says: "It was not released until all of the problems reported by those testers were resolved."

Page 10 - Lawrence Finch says: "because most of the problems that have been listed, at least in this thread, have nothing to do with the update. Which means that either Apple missed dozens of bugs, or that Apple didn't miss any, but something in the usage pattern of the phone is what caused the problems after the update. Or some combination of the above."

Page 11 - Petermac87 claims: "Seems most people are having no issues. But leave feedback with Apple if you believe otherwise."

Page 12 - Tjbusmc1973 says: "It's very simple.  If it was the operating system that was at fault (and not a faulty install or a hardware related issue), then every single iOS device running iOS 7.1.2 would have the same issues.  But they don't."

Page 12 - Tjbusmc1973 says: "Regardless of how the iOS update was installed, if it was installed correctly, then it will work the same on all identical devices."

Page 13 - Tjbusmc1973 says: "If you have an intermittent issue with the connection, you can get a bad install.  So, you simply reinstall the iOS.  Doesn't mean the iOS is 'buggy'.  It means something interfered with the installation process."

Page 13 - Tjbusmac1973 says: "As far as your corrupt iTunes backups, iTunes doesn't create corrupt backups.  Something else on your computer corrupted the backup."

All of those are pretty much the same as saying to everyone who complains about the Updates, that "The updates aren't at fault, it's you or your iDevice or anything but the update!" If any/all of you had just written, "Don't criticise the Update, for the Update is God!", I'd have had marginally more respect for you all, but no. Instead, you just belittle and criticise others, for posting legitimate complaints. You fob them all off, with a two-fingered-salute attitude, and then get pissy with everyone when they don't take too kindly to your high-and-mighty, "You're all beneath us" demeanour!

No wonder people get so wound up, when this is the kind of snotty perspective you all take. It's always something else, but never the Update! Talk about deluding yourselves!

Pooch

None of which support your claims.

I don't see words like "perfect", "infallible", "flawless" in any of those quotes.

And everything I stated there is true, and none of that says that Apple is infallible, perfect or flawless. 

There's a difference between 'a bug' and a 'bad install', which is why reinstalling the iOS is one of the standard recommendations.

You're trying to twist words around or add new ones to my mouth.  So, yes, this is libel on your part.

PoochJD wrote:

 

Hi,

 

Okay then:

 

Page 10 of this thread - Lawrence Finch says: "It was not released until all of the problems reported by those testers were resolved."

 

Page 10 - Lawrence Finch says: "because most of the problems that have been listed, at least in this thread, have nothing to do with the update. Which means that either Apple missed dozens of bugs, or that Apple didn't miss any, but something in the usage pattern of the phone is what caused the problems after the update. Or some combination of the above."

 

Page 11 - Petermac87 claims: "Seems most people are having no issues. But leave feedback with Apple if you believe otherwise."

 

Page 12 - Tjbusmc1973 says: "It's very simple.  If it was the operating system that was at fault (and not a faulty install or a hardware related issue), then every single iOS device running iOS 7.1.2 would have the same issues.  But they don't."

 

Page 12 - Tjbusmc1973 says: "Regardless of how the iOS update was installed, if it was installed correctly, then it will work the same on all identical devices."

 

Page 13 - Tjbusmc1973 says: "If you have an intermittent issue with the connection, you can get a bad install.  So, you simply reinstall the iOS.  Doesn't mean the iOS is 'buggy'.  It means something interfered with the installation process."

 

Page 13 - Tjbusmac1973 says: "As far as your corrupt iTunes backups, iTunes doesn't create corrupt backups.  Something else on your computer corrupted the backup."

 

All of those are pretty much the same as saying to everyone who complains about the Updates, that "The updates aren't at fault, it's you or your iDevice or anything but the update!" If any/all of you had just written, "Don't criticise the Update, for the Update is God!", I'd have had marginally more respect for you all, but no. Instead, you just belittle and criticise others, for posting legitimate complaints. You fob them all off, with a two-fingered-salute attitude, and then get pissy with everyone when they don't take too kindly to your high-and-mighty, "You're all beneath us" demeanour!

 

No wonder people get so wound up, when this is the kind of snotty perspective you all take. It's always something else, but never the Update! Talk about deluding yourselves!

 

 

Pooch

It was not released until all of the problems reported by those testers were resolved.

This is correct.  But that doesn't not suggest that ALL possible problems were detected.  There has never been a software release in the history of technology that has never had a glitch or a bug after it's public release.

Most of the problems that have been listed, at least in this thread, have nothing to do with the update. Which means that either Apple missed dozens of bugs, or that Apple didn't miss any, but something in the usage pattern of the phone is what caused the problems after the update. Or some combination of the above.

This is also correct.  Most of the reported problems weren't update related.  Also, the way a phone is used (especially with third party apps and mail accounts) changes the experience for each user.  Which is also why making a backup then restoring the device as new is recommended; to make the device identical in operating system and user data as every other iPhone of the same model.

Seems most people are having no issues. But leave feedback with Apple if you believe otherwise.

This is also true.  The vast majority of people aren't having problems.  It's only a very small minority.  And Apple has channels for people to report issues.  Peter made a very logical statement and a useful recommendation.

It's very simple.  If it was the operating system that was at fault (and not a faulty install or a hardware related issue), then every single iOS device running iOS 7.1.2 would have the same issues.  But they don't.

Again, this is correct.  And again, why restoring as new is recommended, to determine if it is a hardware or user data issue.  When 99.999% of all iOS 7.1.2 devices have no issue, then it's illogical to look at the iOS as the most likely cause.  This is called Occam's Razor.  Among competing hypotheses, the one with the fewest required assumptions without proof is usually the correct answer. Or, the simplest answer is usually the right one.  It doesn't say that, with contradictory evidence for a competing hypotheses that you can't consider it.  But to gather that contradictory evidence, you would have to have sufficient data.  And you don't.  A few anecdotal comments that have no documentation isn't reasonably sufficient evidence to contradict anything.

Regardless of how the iOS update was installed, if it was installed correctly, then it will work the same on all identical devices.

Again, also true.  An incorrect install can cause a wide variety of symptoms.  But a correct install on identical devices will perform identically.  If we both have iPhone 5S units, and they are both restored as new properly with a fresh copy of the iOS system, but your Touch ID doesn't work but mine does, then that's a hardware issue, not a software issue.

If you have an intermittent issue with the connection, you can get a bad install.  So, you simply reinstall the iOS.  Doesn't mean the iOS is 'buggy'.  It means something interfered with the installation process.

Again, this is true.  Since the installation of the software first requires it to be downloaded, and if the download is interrupted, then yes, that can cause problems.  That's how software works.  Try a test sometime.  Go to any other website, start a download of a program, and as soon as the download is halfway done, intentionally interrupt your internet connection.  Wait 30 seconds, then reconnect your internet.  If the download continues, try to run the program, and see if it performs properly.  Odds are, it won't.  Which, again, is why we recommend reinstalling the iOS.

As far as your corrupt iTunes backups, iTunes doesn't create corrupt backups.  Something else on your computer corrupted the backup.

Yup, this again is true.  iTunes creates the backup, and then hands it off to the computer's operating system to store.  If that process has a problem during handoff or storage, the backup can get corrupted.  Which is again why we recommend having more than one backup, not only of your iOS device, but also of your computer.

So... we done here?  Nothing we ever said that you quoted suggested that Apple was infallible.   We simply outlined recommendations to test the specific issue that someone was having.  Until actual troubleshooting is done (and many people, yourself included, seemed resistance to doing any troubleshooting), then claiming the iOS is buggy is pure conjecture. 

You yourself refused to do any troubleshooting, remember?

"Regardless of how the iOS update was installed, if it was installed correctly, then it will work the same on all identical devices."

"iTunes doesn't create corrupt backups"

"Until actual troubleshooting is done (and many people, yourself included, seemed resistance to doing any troubleshooting), then claiming the iOS is buggy is pure conjecture."

Fantastic! And still the Apple Update defenders insist that it's always the user, the user's iDevice, or something else, it's simply never the Update that is the problem!

Like I said, 100% totally delusional!

If it is the Upgrade then it is extremely random as I have suffered no ill effects on any of our devices. But you seem to have evidence that differs, so if you could provide a link it would be much appreciated.

Thanks in advance

Pete

It is not always the users fault, but in your case ...... it could be.

As you won't check we can't help.

Good luck.

PoochJD wrote:

 

"Regardless of how the iOS update was installed, if it was installed correctly, then it will work the same on all identical devices."

 

"iTunes doesn't create corrupt backups"

 

"Until actual troubleshooting is done (and many people, yourself included, seemed resistance to doing any troubleshooting), then claiming the iOS is buggy is pure conjecture."

 

Fantastic! And still the Apple Update defenders insist that it's always the user, the user's iDevice, or something else, it's simply never the Update that is the problem!

 

Like I said, 100% totally delusional!

Since you've refused to do any troubleshooting, as I said, you have no information to refute any of our points.

And we've never, ever said it's never the update. 

We said: The same iOS, if installed correctly, will operate the same on all identical devices.

That even includes the rare 'glitch or bug' in an update.

Since you refuse to do any troubleshooting or report your results, we don't have any more information for you.  We can only speak in generalized terms, for what applies to the vast majority of situations. 

None of my statements are incorrect.  Read them again, think about what you're reading, and stop jumping to assumptions.

Well I feel silly now;  because of all the warning posts here and there and my still unconquered back up password issue, (if they won't fix it they should at least warn you when you set it "it is not 1 time, it is forever until the end of time), I had not updated my iphone 4, but it was acting very erratic and would need at least a restore anyway so I saved my shsh blobs, and then updated on the phone without connecting to a computer, took awhile, and now it is like a new phone. no issues, no battery issue, works much faster, not slower, and just a far better ios experience.  I did not have to do full restore reset  so still have time to look for itunes backup password before I get a 6. Obviously some have issues and mmv, but others wary like me might want to try it.

Lobomojo wrote:

 

Well I feel silly now;  because of all the warning posts here and there and my still unconquered back up password issue, (if they won't fix it they should at least warn you when you set it "it is not 1 time, it is forever until the end of time), I had not updated my iphone 4, but it was acting very erratic and would need at least a restore anyway so I saved my shsh blobs, and then updated on the phone without connecting to a computer, took awhile, and now it is like a new phone. no issues, no battery issue, works much faster, not slower, and just a far better ios experience.  I did not have to do full restore reset  so still have time to look for itunes backup password before I get a 6. Obviously some have issues and mmv, but others wary like me might want to try it.

They do warn you: iTunes: About iOS backups

When your backup is encrypted, you'll need to enter the password when enabling or disabling encryption or when restoring from the backup.

Warning: Make sure it's a password that you'll remember or write it down for safekeeping. If you encrypt an iPhone backup in iTunes and forget your password, you can't restore from backup and your data will be unrecoverable.

If you can't remember the password and want to start again, you must perform a full software restore and chooseset up as a new device when iTunes prompts you to select the backup from which to restore.

Yes because everybody first looks up the support section, (dated Aug 2014, though I am sure prior versions may have been there earlier), on any activity before pursuing it; as the diagram from your link shows, there still appears to no such warning where it actually makes the most sense, and actually might be clearly seen prior to undertaking the first encrypted backup.

As can be seen in this other thread it is a quite common and very annoying issue with 404175 Views

Re: Lost Password to iPhone Backup