Q: IOS 7.1.2 is buggy, don't update

najuvm wrote:

 

Same problem here. Thanks Apple, like we don't have anything better to do than spend a sunday evening restoring iOS, contacts, apps and everything. Thanks.

You are not talking to Apple here. Try giving Apple feedback

Cheers

Pete

Lots of other replies violated the same TOU, but weren't reported no Apple fanboy would consider doing that (or removed because they contained negative feedback on Apple products).

Good thing censorship cannot revert time and cancel the emails sent out to subscribers

RJV Bertin wrote:

 

Lots of other replies violated the same TOU, but weren't reported

And that means what?

The site moderators decide what gets removed, our opinions are not a part of that process

If you agreed to the terms of use (which you did) then keep your word or if you can't keep your word expect your posts to be removed from time to time.

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. 

Do the recommended troubleshooting on your iPhone, including restoring it as new properly [iOS: How to back up your data and set up your device as a ...].  If, as new, you continue to have performance issues, then contact Apple who will either have more troubleshooting steps, depending on the specific issue, or recommend hardware replacement.

This is a very simple concept.

We don't know what it is (and we're, sadly, not really supposed to speculate on here). OS, 1st, 2nd or 3rd party apps, the code handling the firmware update, they might all be involved.

As to an OS issue expressing itself on all devices: reality is a bit more complex than that. Think of how we can be infected with a disease without ever developing the disease. More specifically, a couple of years ago it was very unwise to issue OpenGL calls from a background instead of an application's main thread. This is not unheard of, but contrary to other OSes it could provoke kernel panics on OS X. In other words, a programming error in an application caused OS instability.

RJV Bertin wrote:

 

We don't know what it is (and we're, sadly, not really supposed to speculate on here).

Was that to let us know that speculation was about to begin?

And you, trying to be helpful by teaching me about speculation? Despite what first impressions might be, there is none in my previous post - except maybe unintentionally so if I forgot to include a possible cause and thus suggested it was NOT involved.

TJBUSMC1973 - You say: "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."

Wrong, wrong, wrong! You are assuming (once more, like so many others) that an update is already faultless, which I think is evidently not the case.

You are doing the very thing, I am trying to get some of you to understand, but which you are refusing to accept, because it doesn't fit in with your own narrow experiences. Namely, that you believe the update is perfect in every way, and thus, it has to be something else - the user, an app, more than one app, a combination of apps, etc, etc - anything BUT the update, that is causing the problem! Yet not one person in this thread can provide any evidence. And there's a reason why they can't, because they know that no such evidence exists to backup that claim! It's just guesswork on their part!

You are also assuming that every single Apple user will install the update in the exact same manner, using the exact same methodology and tools, which they don't. Some people updated from 6.1.3, some from 7.1. Some people used Macs, some used PC's. Some people used Windows 8, some used Windows Vista. Some will have used iTunes 9, some iTunes 10, and some iTunes 11. Some used iPhone 3GS's, some 4's, some had 4S's, and some used 5C's. As I think is obvious, this is absolutely not the case at all!

As that is not the case, and there are hundreds of different ways of installing an update, the one and only static fact that links every single person who attempts the update, is the update itself! It's the single common denomination. It's the only thing that is always the same irrespective of anything else. So, by your flawed rationale, the 1% of the equation that is guaranteed/constant, is the one thing that is perfect, whilst the other 99% is the stuff that must be problematic!

So, why do you keep assuming that the update is perfect/flawless?

To then insult users by telling them how to backup their devices, just demonstrates the continuing gulf between those people who installed the 7.1.2 update without any problems, and everyone else, and - still - the problem is always everything and everyone else, but never the update!

And even when people DO backup's, as I did (if you'd read my posts in full), then you'd realise that even having one or more backup's won't necessarily make an update install correctly.

Ergo, we come back to the start of the problem again, that the problem has to be that the update itself isn't perfect, and hasn't been tested enough.

yeah me too i really hope i dont have to get a new ipod cause this is rediculous

RJV Bertin wrote:

 

We don't know what it is (and we're, sadly, not really supposed to speculate on here). OS, 1st, 2nd or 3rd party apps, the code handling the firmware update, they might all be involved.

As to an OS issue expressing itself on all devices: reality is a bit more complex than that. Think of how we can be infected with a disease without ever developing the disease. More specifically, a couple of years ago it was very unwise to issue OpenGL calls from a background instead of an application's main thread. This is not unheard of, but contrary to other OSes it could provoke kernel panics on OS X. In other words, a programming error in an application caused OS instability.

iPhones are not organic beings, and therefore the 'disease' analogy is flawed.

If there is a flaw in the design of the operating system, then all devices (or a very, very high percentage of devices) running that iOS would exhibit these 'bugs'.

The operating system, in this case, could be compared to standard human physiology.  Without any genetic aberrations or defects, most humans aren't allergic to, say, peanuts.  However, some humans are.  This doesn't mean that humans, in general, are flawed.  It means that particular physiology of that specific individual is flawed.  Which is analogous to a faulty iOS install (or possibly corrupt user data).  This is why there's the recommendation to reinstall the iOS and test the device as new.

Very few humans have an allergy to peanuts.  Very few iOS devices have glitches.

You can't reinstall your physiology or replace your biology.  But you can reinstall the IOS, or replace the hardware, of an iPhone.

PoochJD wrote:

 

TJBUSMC1973 - You say: "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."

 

Wrong, wrong, wrong! You are assuming (once more, like so many others) that an update is already faultless, which I think is evidently not the case.

 

You are doing the very thing, I am trying to get some of you to understand, but which you are refusing to accept, because it doesn't fit in with your own narrow experiences. Namely, that you believe the update is perfect in every way, and thus, it has to be something else - the user, an app, more than one app, a combination of apps, etc, etc - anything BUT the update, that is causing the problem! Yet not one person in this thread can provide any evidence. And there's a reason why they can't, because they know that no such evidence exists to backup that claim! It's just guesswork on their part!

 

You are also assuming that every single Apple user will install the update in the exact same manner, using the exact same methodology and tools, which they don't. Some people updated from 6.1.3, some from 7.1. Some people used Macs, some used PC's. Some people used Windows 8, some used Windows Vista. Some will have used iTunes 9, some iTunes 10, and some iTunes 11. Some used iPhone 3GS's, some 4's, some had 4S's, and some used 5C's. As I think is obvious, this is absolutely not the case at all!

 

As that is not the case, and there are hundreds of different ways of installing an update, the one and only static fact that links every single person who attempts the update, is the update itself! It's the single common denomination. It's the only thing that is always the same irrespective of anything else. So, by your flawed rationale, the 1% of the equation that is guaranteed/constant, is the one thing that is perfect, whilst the other 99% is the stuff that must be problematic!

 

So, why do you keep assuming that the update is perfect/flawless?

 

To then insult users by telling them how to backup their devices, just demonstrates the continuing gulf between those people who installed the 7.1.2 update without any problems, and everyone else, and - still - the problem is always everything and everyone else, but never the update!

 

And even when people DO backup's, as I did (if you'd read my posts in full), then you'd realise that even having one or more backup's won't necessarily make an update install correctly.

 

Ergo, we come back to the start of the problem again, that the problem has to be that the update itself isn't perfect, and hasn't been tested enough.

Regardless of how the iOS update was installed, if it was installed correctly, then it will work the same on all identical devices.  And there's only one way to verify that your device is identical to another iOS device:  Restore it as NEW.

Make a backup of the device.

Restore the device and reinstall the iOS via iTunes.

With the device set up as a new device, test the issue.

If issue remains, it is highly likely it is a hardware issue.  Get the device serviced or replaced by Apple.

If the issue disappears, then it was related to either faulty iOS install or user data on the device.  Then, restore your backup.  If the issue remains gone, it was likely a faulty iOS install.  If the issue remains, it is related to your user data.

This is basic, logical troubleshooting, that lets you isolate the problem to one of three possible root causes:

A) Hardware failure

B) iOS faulty install

C) Corrupt user data.

It is that simple.

Pogster writes: "Any software on any kind of device will show some 'bugginess' on some devices and there's always some degree of risk. It's the nature of computers. The vast majority never have a problem so your 'warning' is not called for. For the record I have 5 idevices and not once have I ever had a problem due to software upgrades."

That's why it would be nice if Apple would let us downgrade. But they don't, and then when you download a buggy version, your up the creek. When I upgraded to 5.0 i suddenly found it almost impossible to bring up the video scrub bar. 19 times out of 20 or so I would get the notification screen, which being on my iPod, and for which I almost never got Wi-Fi signals, due to my not hanging out at Starbucks all day, was totally useless anyway.

I recently upgraded to 7.1.2 on my iPad (3, I think -- just before the 4G reception version), I can't watch TV shows. Tapping a show brings it up for an instant and then it either disappears or says "could not load video". Nice.

Apple doesn't allow you to downgrade your iOS, because that could cause far, far more problems that it 'solves'.  For example, you can't restore an iOS 7.1.2 iTunes or iCloud backup to a device running iOS 7.1.1.  That means you could lose all your saved data, until you update back to 7.1.2 again.  Also, some apps will crash or encounter catastrophic failures if you 'forced' the iOS to downgrade.

And that's just the tip of the iceberg.  Failure to properly connect to wi-fi networks, cellular networks.  Bluetooth connection failures.  Apps not updating properly, or losing your data.  Contacts & calendar events disappearing.  Messages not being received or sent properly, or being lost from memory.  Notes disappearing into the ether, lost forever.  Device crashing into an unrecoverable state.  Failure of the temperature alert being displayed properly, or not auto-shutting off the iPhone when it gets dangerously hot (possibly causing physical injury or property damage)... Shall I go on?

And the only possible methods (which I won't explain here) to force downgrade your iOS require unauthorized modifications to your iOS device... which then exposes you to the possibility of malware, as well as VOIDING your warranty.  Meaning all of your private, personal information (including bank account numbers, mail counts, credit cards, website accounts, and all the associated passwords) is at risk.

Downgrading your iOS doesn't resolve any technical issues.  Reinstalling your iOS can resolve faulty iOS install issues.  But if reinstalling your iOS doesn't resolve a 'glitch', then it's either the hardware or the user data.

I updated my iPhone 5s to 7.1.2 and iCloud activation lock came when the phone rebooted. Its asking me for the old owners Apple ID. Ive been countless hours on the phone with ATT and Apple and no one has helped me yet. They want the original receipt, but i dont have it. So thanks to this update. I have a fancy paperweight on my desk. The original ower game me his info but its inside the phone.. So no access to it.

Well, what a crappy OS to be vulnerable to all that just from a downgrade.

Glitch? Safari keeps crashing. I can't watch my TV shows. I could before. I tried to reinstall (and stay with 7.1.2), but the reset function failed with unknown error 3004. Nice.

I still have 7.1.1 on my iphone and I can still do all the things you said I couldn't do if I downgraded my iPad to 7.1.1. I just want to put my iPad back to the state it was in before I upgraded. What's the harm in that? My ihpone is at 7.1.1. As far as I know, this is working out fine. I can watch my TV shows. Now, you're telling me that if I upgraded it to 7.1.2, and if Apple didn't have this annoying anti-downgrade policy built into its OS, that going back to exactly what I had before the upgrade would break all kinds of things? (That would break the "reflexive property of equality"! Yes, this stunningly obvious fact actually has a name.)

When I upgraded to 5.0 on my ipod, it suddenly become next to impossible to bring up the video scrub bar. Glitch? Nothing fixed that except finally the release of 5.1.

You say that using unauthorized methods to downgrade would cause a problem. Well, if the OS weren't designed that way, it wouldn't be a problem that way.