Came up as an update on my 12 mini. So likely yes.Is this update only for the iPhone 15 or all iPhones?
Came up as an update on my 12 mini. So likely yes.Is this update only for the iPhone 15 or all iPhones?
You got the placebo release!Oh, the irony. My iPhone overheated while installing the update to prevent overheating.
That’s how you get more bugs not less.nice, quick fix out. now fire the inept engineers who manage to miss it in the first place.
That's the thing my Phone was working fine before the update, so hopefully they didn't do anything funny to screw up anything
It means Apple’s excuse is full of ****, at least partially filled with it. If an iOS update is going to fix anything then it is global, regardless if any app has done something wrong. If the new iOS 17 demands some changes that an older version of the app not updating to a new API or something, we would have seen the issue much more wide spread, or that Apple will say it.How does any of this help people who are complaining that their phone gets 'hot' on phone calls or even taking pictures?
Any more importantly, no one would be around to learn from their previous mistakes, so if there was any software still being written, it would have even more bugs.If people got fired every time a software release had bugs in it, nobody would be employed.
Just posted one above yours, I let mine cool first. I think most are running Geekbench while the phone is still warm from the update.View attachment 2288558
A lot of people are going to eat their words now if true. This is from a Twitter user so feel free to verify.
Cycle count refers to how many times you used the listed amount of mAh based on your iPhone model so you can use 70 percent one day and 30 for another day and that is considered 1 cycle. So not necessarily has to be fully charged and then fully depleted, also a quote from an website below.Anyone notice their Cycle Count increase on the Battery for no reason after the update? I'm up to 3 now - Phone has never been charged to 100% yet? - bizarre.
It's amazing to me that users have kept gaslighting those who encountered the issue: "it's just warm. that's not overheating"; "it's indexing"; "you are using it too much"; "no issue with mine"; "first world problems"; "just be grateful"...on and on and on. The issue is with Apple's end all along. Even Apple admits it. Next time, just accept that some people might have problems with their devices that might not be happening to yours, and that the problem could be with Apple and not the users. You can believe other people's complaints and still be happy with your own device. Don't take it personally.
People need to stop diving into these Geekbench runs just after installing the new update. Give it time to settle or re-index then run it after a few hours later.View attachment 2288558
A lot of people are going to eat their words now if true. This is from a Twitter user so feel free to verify.
Exactly. Lotta panic from people benching their phones that are already hot from the updateSo, again:
Before (17.0.2):
View attachment 2288571After (17.0.3):
View attachment 2288575
That's within the acceptable range (every bench is different on 17.0.2 as well). So they not underclocked the CPU.
That's cool that you'd prefer that, but I'm not sure you understand how complex it is perfecting an entire OS consisting of dozens of millions of lines of code across dozens of devices of all different hardware configurations, every single time. Maybe you can join Apple and help them out if you have ideas on how they can do better. Frankly I think it's a borderline miracle they're able to achieve the level of quality they're at with only a couple occasional minor issues here and there.I'd prefer them get it right the first time. Or, failing that, get less wrong less often.
How’d you run both benchmarks at 11:53? Two separate phones? Both just happened to be at 72 percent battery? Just curious.View attachment 2288558
A lot of people are going to eat their words now if true. This is from a Twitter user so feel free to verify.
I see two reasons: iOS is much more complex now than ten years ago (the complexity likely has gotten out of control), and also the general attitude in software development has been shifting away from placing a lot of value on high quality and robustness, since nowadays you can always push a bugfix a couple weeks later, and users have been accustomed to nothing ever working flawlessly, and they have not a lot of choice anyway, so it doesn’t seem to hurt the bottom line that much.Maybe some of you guys who've been here for years can chime in but... it sure seems like there's way too many updates these days compared to ten years ago. Seems like every few days, there is a reported issue, then I have to sit through another update. And another, and another, and another and... it's just out of control.
Famous last words.Finally the controversy can rest