Paikinho…. wrote:
How so?
How exactly is replacing old code on a device stressing it out?
~Belisarius~
"ONE WORD: FIRMWARE. If you have not worked with it to see how it bricks electronics, I recommend you have a quick 101 read. or at least links below. It is the most dreaded upgrade for any IT specialist. It is only done if a must - Apple with OS rollouts, or special requirements."
I was unaware that you were talking about stressing out IT guys when you said that updates were stressing things and revealing hardware problems. That seems to be the gist of what your words now indicate is not some sort of hardware stress as you seemed to indicate before.
Indeed I have worked with firmware throughout the last 30 years of my life. And yes I have performed many dozens of firmware updates in my time. They are not really needed much outside of the manufactures sphere and an infrequent necessity for various devices or computers once devices are in the wild for for the most part. Firmware updates are definitely a couple of orders-of-magnetude less required than the constant updating needed by the OS to fix various dynamic bugs in this multivariate iPhone ecosystem.
Personally, I have never really had a problem with any firmware updates, so the dread with which you wish to elevate the importance of firmware is somehow lost on me. I have managed to dodge a couple of rushed out Firmware updates which would have messed up my machines but have not had any Firmware mess up my systems to where they weren't retrievable. To me Firmware is not really that scary any more than ripping apart machines and devices to fix them is. There are risks, but with care an diligence things almost always are fine.
Just 3 days ago I performed a firmware update on a device, but I don't recall it being very stressful. Maybe it is just me.
First you talked about how the "iOS 10.1 Battery drain"... the subject of this thread is a pretty much a battery issue, now you are bringing up Firmware updates. Why?
Was the 10.1.1 update an iPhone Firmware update? I thought is was simply an OS update. You said updates are stressful, but tie that to Firmware. Are Apple iPhone updates firmware updates as well as OS updates?
Neither in my view stresses hardware in the sense of breaking the physical function of it. Poor programming could make it a brick, but we are not talking bricks in this thread. We are talking about diminished function after and iOS update. And at least for me it seems I may have come upon a solution which would negate your assertion that this is merely a battery issue. If my battery where shot by the upgrade then it wouldn't be lasting a day and 1/2 after I factory reset things.
Once more I struggle to discern what your point really is. I struggle to understand your motivation in this matter entirely.
Having performed hundreds of upgrades, fresh installs, re-installs on many hundreds of devices I am not very certain that doing so results in any more stress than just using the system.
Have you any literature which sheds light on your assertion that an update stresses a phone in this case more than say running it day to day or running an intensive game?
I guess I don't yet buy into what you are say
Each time it is done, IT techs anticipate a certain failure rate.
Yes and the failure rate can vary a lot.
IT directors and teams who roll this stuff out have to worry about a lot... test, re-test and document everything. Once they are certain they have flawless FIRMWARE they roll it out.
Still there could be some glitches in the real world as some things are not apparent. What does this have to do with whether the iPhone is or isn’t stressed by a firmware update?
And are the iOS updates all firmware updates?
PC vendors generally avoid OTA firmware updates altogether- although modern BIOSs on expensive MOBOS are so advanced that copanies such as Dell roll it out quite comfortably.
Wait a minute. You just got done telling me that Firmware updates are scary. Now you are saying no big deal?
And your arguments for replacing the battery are that the Update revealed a flaw in the controller. Or is it a flaw in the programming that could brick the controller? But if the controller were bricked then wouldn't the battery fail entirely perhaps. Or if the controller were flawed, how then would someone be able to get their phone back and going from being bricked and achieve the battery performance and function they had before?
Car manufacturers avoid letting dealerships do ECU flashes- any sports car living and breathing by it- as once done, the likelyhood of the hardware failing the event is too much of a risk.
Why would dealerships ever do ECU flashes?
If someone wants to change the engine control unit to get their care to run hotter for more horsepower or other performance changes, why on earth would a dealership do that? The Engine Control unit is set the way the manufacturer wants it. Why would dealerships willy nilly mess with that. Liability for cooking an engine, I would think would play a bigger role in the thinking of any business. Risk and being on the hook for doing adjustments to the performance of a car requires greater expertise and insight than a typical dealership would have on staff.
So batteries have controllers and a buch of programming, and any new iOS releases software and FIRMWARE on top of the key hardware. Software controlls your OS functionality, firmware, physical hardware.
Of course since not all hardware works perfectly- anyone here believing the contrary should really get a reality check- it also fails.
I think everyone here... and indeed for the most part, on the planet is well aware that not all hardware works perfectly. Neither does all software. I don’t think there are many people who would make a statement of believing in perfect software and hardware. Our lives as humans are replete with examples of such failures and I think that nobody needs a reality check.
No company in the world makes 100% perfectly working hardware, it does not exist in the engineering world. All these are facts.
It seems you are making a statement that everyone agrees with so again I fail to understand how this furthers your argument that everyone just needs to buckle down and buy a new battery and the issue will be fixed.
This issue is certainly complicated, it could be software or hardware related. iPhones are complicated devices which is why there is a continual stream of new code to fix or bypass issues that arise.
Anyhow, although it is an option to replace the battery... that is merely one choice and not a fix all for everyone. I think everyone is already aware that replacing the battery is an option since that is generally the first thing Apple people suggest. If others wish to try to find other solutions and post their experiences here, they should be able to do so without being met with so many and frequent suggestions by one person that the battery needs to be replaced. They should not be met with comments which seem to diminish their experiences either.
As to FIRMWARE being the culprit in some way... perhaps, but one would have to know if iOS 10.1.1 altered the firmware first. Do you have insight into the firmware being altered by this OS update?