Same here, except the front is hot on my 14Pro too. (the front and back get hot when it overheats.)
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Says iPhone 15 Pro's Titanium Frame Does Not Contribute to Overheating Issue
- Thread starter MacRumors
- Start date
- Sort by reaction score
I just ran Geekbench 6 with phone plugged in to charger, and it didn’t even get warm. Also, I know there’s variability in performance but my 15 Pro Max appears to be about 15% faster than average 14 Pro CPU benchmarks, about 5% faster than the quoted 10% CPU performance gains. So even if my chip runs ever so slightly hotter to achieve slightly higher scores, I didn’t feel it at all in the phone.
I highly doubt that Apple has designed a phone that is unable to run without remaining at reasonable temperatures.
I understand that there are issues with certain devices, but it isn’t every device so that means it’s not the hardware at fault.
The Apple Watch battery drain issues, paired with this just screams “software”, and iPhones suffering will have the issue rectified. Anyone that has suffered third degree burns /s are still well within their return window.
I understand that there are issues with certain devices, but it isn’t every device so that means it’s not the hardware at fault.
The Apple Watch battery drain issues, paired with this just screams “software”, and iPhones suffering will have the issue rectified. Anyone that has suffered third degree burns /s are still well within their return window.
The assumption you have clearly made is that software won’t fix the problem. Why would they need to throttle the cpu if the app is (for example) pushing the high performance cores when there is no need, and it should be using the efficiency cores? Why would instagram need to use the high performance cores for background tasks? (As a possible example).
Phone and Camera from what I've seen. I don't use the phone that much, but the camera app definitely makes my 14Pro hot. (but it always has since I got it last year.)
Equally impressive: your response had facts and useful information. Speculation and guesswork is fine too, but in this thread some posters have really far out ideas which strain credulity.
So then you're not really saying anything. All CPUs and GPUs throttle under that logic, especially all phones. No phone can run at full load without throttling.
If the 15 Pro isn't running hotter than the 14 Pro, why would Apple be "fixing" it by throttling the processor? There's no evidence whatsoever that the 15 Pro requires extra throttling.
The issue isn't that the phone is running too hot under load, the issue is software bugs running the phone under too much load inappropriately. Does that make sense?
I really do hope there is no throttling with the investment people have made with these premium 15 versions. I also recommend constant testing after each software update to make sure people get what they were told they paid for.
That is incorrect. The facade of the frame is titanium, bonded to aluminum. That has been independently verified:
The grade of titanium isn’t what I’m talking about. I’m talking about the amount of titanium. It has been independently verified that the titanium is bonded to aluminum, and there is approximately 1 mm of titanium as a facade for the aluminum:
Instead of writing all that speculation you could have just tried out stress tests on a 15 Pro next to a 12/13/14 Pro and realised with your own hands that far more heat radiates out of the 15 Pro titanium/aluminium side rails than the older stainless steel side rails.
This is objective fact and anyone with access to the phones can replicate it themselves easily. You're just wrong.
Last edited:
You can believe it or not. Apple doesn’t care.
I can’t really see how this can be anything other than a bug in iOS (or possibly the Xcode compiler) or the hardware just running too hot. There are no clockspeed APIs exposed to iOS developers; the OS (or the hardware) chooses when to reduce clock speed due to heat, its not in the control of the developer to throttle or not throttle their app.
Even if the developer is spawning tons of threads and using all the CPU and GPU resources, that shouldn’t cause overheating, the hardware should throttle back performance when the heat rises. For this to be the fault of specific apps makes no real sense to me. Maybe they’ve somehow found a way to force the hardware not to throttle back, but in that case they would be in violation of the TOS of the App Store as you’re not supposed to use undocumented API calls (I would actually be surprised if there is an API for adjusting performance though).
I just can’t see how this is the fault of the apps. I know when it comes to RAM usage iOS will force quit an app if it starts allocating too much RAM to itself too fast or using too much RAM. So again, it doesn’t make sense to me for this to be the fault of apps when Apple have had good controls for app misbehaviour for years.
Even if the developer is spawning tons of threads and using all the CPU and GPU resources, that shouldn’t cause overheating, the hardware should throttle back performance when the heat rises. For this to be the fault of specific apps makes no real sense to me. Maybe they’ve somehow found a way to force the hardware not to throttle back, but in that case they would be in violation of the TOS of the App Store as you’re not supposed to use undocumented API calls (I would actually be surprised if there is an API for adjusting performance though).
I just can’t see how this is the fault of the apps. I know when it comes to RAM usage iOS will force quit an app if it starts allocating too much RAM to itself too fast or using too much RAM. So again, it doesn’t make sense to me for this to be the fault of apps when Apple have had good controls for app misbehaviour for years.
Chronic problem in devops environments: Stuff works in Labs, fails in the real world. There's no scenario where even the biggest, best financed vendor could afford testing to "Street-Standards". Real intelligence and real life are vastly more complex. Pretty much everwhere you look, testing is a lofty goal, but largely an illusion. They do what they can, good days, bad days, some gems, some lemons, so it goes. The rest is covered under a license with liability waivers and indemnification clauses. Pays yo money and takes yo chances. Frankly, its a wonder anything works at all.
If both phones ran hot when used as intended, then both phones had insufficient cooling.
Can't hang a conclusion on one property. One question is: To what extent was the stainless frame being interfaced with the heat source? As I understand it, the aluminum innards were/are epoxied to the frame, which makes sense because welding would warp the components beyond the tolerances to which they obviously designed. Then the question is how heat-conductive was that epoxy interface before, and how might the implementation have changed? And to what extend is the rear glass used as a heat sink? More or less now then before? Apple will never reveal that data, and reverse engineering to find out would be exhausting.
Almost any phone or computer can get hot. It's within the design tolerance so how is that insufficient cooling? Please elaborate.
It sounds like you're saying that any computing device that gets subjectively hot to the touch but well within the design tolerances has insufficient cooling. Surely you're not saying that though?
But in the disassembly video, it seems that the outer frame and the inner frame are not one, and are fixed with screws.
you're comparing iPhone 14 Pro Max last year data results, here's mine just did it right now iOS 17.1 beta.
well actually yeah, not sure about titanium but aluminium is better than iron/steel for heat dissipation.
this is why modern engine blocks are made of it.
Can't wait to find out. If it is an infinite loop or something, what does that say about Apple's QC before releasing the software to the public in new devices people just spent hundreds of dollars on?