Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
If I downloaded this update, I would do a before & after CPU/GPU benchmark test and note as many details as possible the results give you. Anyone with a temperature tool should also note measurements while these tests are being performed.
I suspect a similar benchmark score, however there may be some serious throttling after the phone starts to get somewhat hot. Maybe run a game or intensive app, then run test again?
 
  • Like
Reactions: spartan1967
As soon as I did update. Went on TikTok and screen had dimmed. Way to cook!
Not a fan of the screen dimming. Every time that happens I can't get on the damn bus/train! By the way Apple, you have to wait for these outside! In Arizona. When it's 115 outside sometimes!

But can't use the damn QR code scanners when the screen dims to barely readable. Seems showing a ****ing bus pass is too processor intensive?! Oh so Pro!
 
Not a fan of the screen dimming. Every time that happens I can't get on the damn bus/train! By the way Apple, you have to wait for these outside! In Arizona. When it's 115 outside sometimes!

But can't use the damn QR code scanners when the screen dims to barely readable. Seems showing a ****ing bus pass is too processor intensive?! Oh so Pro!
I was looking for this! Is there any way to disable the screen dimming??? This is terrible
 
  • Wow
Reactions: decypher44
See also: analysis and journalists may have no idea what they're talking about, and everything should be taken with a grain of salt.
 
Ugh you think I can downgrade to iOS 17.03 from iOS 17.1 beta 2?
Why are you so desperate to downgrade? 17.0.3 may be worse than whatever is happing to make you want to be off 17.1. You even only wanted 17.1 B2 to allow you to downgrade before even knowing if it was good or bad. Just curious.
 
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.

Because devices do get warm when they index, and every year people complain about heat, reduced battery life, etc on the first few days post update or release. Rather than acting high and mighty, perhaps take a step back and realize they were entirely correct to suggest as much.
 
Not a fan of the screen dimming. Every time that happens I can't get on the damn bus/train! By the way Apple, you have to wait for these outside! In Arizona. When it's 115 outside sometimes!

But can't use the damn QR code scanners when the screen dims to barely readable. Seems showing a ****ing bus pass is too processor intensive?! Oh so Pro!
Screen dimming is done to reduce heat production.

The real solution is for more places to stop relying on scanning QR codes off of screens, and implement Apple Wallet/NFC support in their apps and POS terminals.
 
All I'm saying is there seems to be far more updates now than there was ten years ago. That it seems like it's near-constant, and that I find it very annoying. I just updated the thing a few days ago. I don't want to do it again. That's all.
Ten years ago there weren't even 5 generations worth of iPhone to make updates for, and each year only had one main configuration with two colors available.

In contrast, iOS 17 is compatible with 23 devices and iPad OS 17 is compatible with 20 devices. So, in total, 43 different devices are receiving this software. Software, which is exponentially more complicated than it was 10 years ago, with many more APIs and specific applications to account for.

What's remarkable is that in less than 2 weeks, they've been able to identify, correct, test, and deploy a fix.
 
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.
compared to 10 years ago, there are more features and more code, so hence more updates to fix them. Also with any MAJOR code update that adds more features you always run into more bugs. Apple like any company tests as much as they can and they listen to Dev and Public feed back on the code testing. Also deadline for getting the code out, security fixes that need to come etc,etc. its all a balancing game
 
All I'm saying is there seems to be far more updates now than there was ten years ago. That it seems like it's near-constant, and that I find it very annoying. I just updated the thing a few days ago. I don't want to do it again. That's all.
There is also one more thing to take into consideration.
Years ago we had way less HW than we have today.
Back to the iPhone 5, to name one, we just had a handful of iPhones that would get the latest iOS. Also for iPads...
Today we have a bunch of models, all running iOS, but each with different hardware so that means we have several different builds of the same SW.
That leads to more bugs because you have to adapt the same SW to different HWs..... I agree it should not happen.
 
Screen dimming is done to reduce heat production.

The real solution is for more places to stop relying on scanning QR codes off of screens, and implement Apple Wallet/NFC support in their apps and POS terminals.
I don't have much faith in waiting for the government to get on that as soon as possible. Specifically the government that is known as the State of Arizona. At least the app has Apple Pay.
 
Hopefully we get 17.0.4 soon with fixes for alarms not going off and bedtime mode not turning off...
 
All I'm saying is there seems to be far more updates now than there was ten years ago. That it seems like it's near-constant, and that I find it very annoying. I just updated the thing a few days ago. I don't want to do it again. That's all.
More devices to support - Apple actually includes old devices in their updates more than anybody. Increasing complexity and mixes of components. Tons of new APIs over the years to exposure new features. All of that take huge teams of developers, and they are human. Considering how long they support their devices and the variety across them now, their bug rate is probably pretty damn low.
 
  • Like
Reactions: MNGR and sbailey4
I love Apple's response, basically saying Kuo has no idea what he's talking about.
I mean, think about it.

What are they gonna do? They have two choices if there actually is a design problem.

1. Admit to a design issue on the newest iPhones, issue recalls and spend millions on replenishing recalled devices with new models, spend additional millions on new engineering, new frames and manufacturing and halt all iPhone sales until they're out.

Or,

2. They could just brush it under the rug, lie about it, throttle the processor secretly, get a bit of bad PR but continue selling millions of phones this year.

I'm not saying there is a design problem, all I'm saying is that there is a much easier choice out of these two.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.