Snap, crackle ... patch! Apple kicks out iOS 11.0.2 to tackle crappy calls, fix email glitches Apple has pushed out a software update to address the handful of bugs that were nagging its latest iPhone models and flavor of iOS. The iOS 11.0.2 release consists of a trio of fixes that were reported by fans shortly after the arrival of version 11.0 of the operating system and iPhone 8 and 8 Plus last month. Most notably, …
It is interesting that only a "handful" of devices were affected. I don't know how many that is, but I know someone who bought an 8 and hasn't had any static on calls so it definitely isn't everyone. If it were some sort of manufacturing defect that would explain why only some are affected, but that can't be it or it wouldn't be possible to fix with an OS update.
I'd guess there is some component in there that's different for different models, perhaps the DAC, and they needed a software tweak (different hardware register settings or whatever) for the ones that were built with that different component.
They can test all they want, but if they use different hardware on any phones when mass production begins the testing won't catch it. Given the huge production volumes they require, they can't sole source every single tiny part so I guess it isn't terribly surprising.
”...so why is the quality testing failing?“
Arguably I’d say the testing is succeeding; it’s just that it’s the customers doing the testing instead of employees.
Seriously though - mobile OSen are seriously complicated these days. The kernel can run into hundreds of MBs, and the RTM image is up in the gigabytes. That’s a lot of code (and vulnerabilities) to check so it’s pretty much inevitable that a few will slip through the net.
Still on 10, maybe I should wait until 11.0.3? I have to somewhat agree with the first post, there were quite a few people on the beta (I know of two). Though at times like this I do wonder how many people on the beta were active (bug reporting) participants and how many just wanted to play with the latest and greatest(ish).
"Waiting 4 months gives them ~40 less potential problems? I think that makes waiting a winning strategy."
With Android (and this is just a comment not a dig) there's usually the issue of tradeoff between how long you wait after release for all the hardware bugs to be ironed out (like the LG G4 reboot problem) given that the time to the end of updates is also shrinking, but so is the cost.
I have a feeling there's a potential non-linear program there varying by vendor which gives you the maximum bang per buck with the minimum potential hassle. Where's Big Data when we really need it?
I suspect that if you don't want the very fastest processor the MBPBMPH of some of the second tier vendors like Sony or Huawei (though they re heading for first tier) may well exceed Apple or Samsung, but it's something that would be nice to have quantified. Does paying the Apple price actually pay off in duration of updates and device longevity, or does your hardware and software stay more current if you buy reasonably high spec Androids once the price has dropped significantly?
Whether 'paying the Apple price' pays off in duration of updates and device longevity depends on how much you value duration of updates and device longevity.
Sure, you can buy a higher end Android after the price has dropped a lot six months after release, but you are also six months closer to seeing the last update it'll ever get...
@ Jay 2 "Still on 10, maybe I should wait until 11.0.3?"
I'm still on 10.3.3 and will be waiting until 11.1.2-ish. I don't have to be at the bleedin' edge (security fixes notwithstanding) so I'm happy to let others do the field beta testing. I've seen it said (probably in this fine organ) that Apple get x.0 right for the new HW then concentrate on the older hardware problems with x.1
That's Apple Innovation, just like the brave innovation of removing the 3.5mm jack.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
