I have the same phone and no such thing happened.
Do you mean the phone got slightly warm? That’s not overheating, it’s just what happens when you use an app that leverage the CPU for anything non-trivial. It’s not overheating.
It will dim the screen soon that it's unusable outdoors. I wasn't able to capture a photo outdoors yesterday using this app because of this. The first photo slowly finished processing but the app crashed, lost the photo. Then the device was overheating, the screen dimmed to unusable the FPS dropped, the app become unresponsive and the music went away, the AirPods re-connected. Couldn't even try to capture a second one.
It wasn't even that hot, just 28C.
I bet this a software bug of some sort - like they’re using the cpu where it should be using Metal or something. Hopefully they can sort it out.
Apple got caught purposely slowing down older model iPhones.
https://www.npr.org/2020/11/18/936268845/apple-agrees-to-pay...
I still think that Apple was right there by not implementing this switch, and judge was an idiot. But that's just me.
They're not even the only consumable part anyway.
>Batteries ... are already easily replaceable
Is this[1] what easy looks like?
Batteries tend to degrade to about 85% quickly and then spend a long time at that capacity. Couldn't tell you why.
A USB battery is a more useful thing to have, for instance because you don't have to turn off the phone to use it.
> Is this[1] what easy looks like?
For something you'd do every 2-3 years, sure. He's put in some extra steps in that video I think.
So, "Apple killed battery swappability" is a fair thing to say.
iPhones being hard to repair, let alone change the battery is such a ridiculous meme.
If it helps I believe the EU just made it illegal two days ago to release updates that make battery life worse. But I could've confused some of the details there.
They just implemented iOS 7 with much more compute requirements, so only newer phones were able to run it smoothly. The progress of mobile CPUs these old days was crazy, so I don't really complain about it, it was inevitable.
Yeah, that's a bug. Any regression on any supported device is a bug.
That was a very, very rushed release.
It certainly felt intentional. Considering the effect of the bug, I'd argue this falls into malice and not a simple oopsie bug.
This wasn't fixed. They never intended to fix it. It looked intentional from the user perspective.
It seems like A would have been whistleblown by now, and B would be idiotic for them to do on purpose since it would make their new devices unnecessarily slow too.
My opinion is basically B but without malice, it's just that they're obsessed with tons of animation and other eye candy, and added a lot of bloat in those years in general, rushing code out the door out of a desire to hit iOS release dates and the synchronized iPhone release dates they used to have.
Yes, they did in fact prove that. That's why Apple had to pay $500 million dollars to settle, because they got caught doing shady shit.
It was still the correct course of action, and obviously not done maliciously -- a phone that was so slow it was annoying to use, and a phone that reboots 10x a day are equally 'incentive' to buy a new phone, so I fail to see how the throttling benefited Apple one bit.
In fact, I'd say the unreliable rebooting one would have provided stronger incentive to replace it vs. a slow one.
>"In March, Apple agreed to pay up to $500 million to settle claims of intentionally slowing down older phones."
They got slapped on the wrist. This resulted in them making the batteries slightly easier to replace, but their batteries are still impossible to replace by the average iPhone owner.
Now the reason is valid and should have been a toggle from the get go but they still told us they were not doing it when they were.
On the other hand night photos seem like garbage - there’s a bit more stuff visible than on default 3sec night mode but the colors are nonsensical and details nonexistent, certainly nothing even remotely close to what adobe promises on their webpage.
All in all I’m not sure what use it is with the terrible performance, outside of long-range photos that you really want to shoot at 6x zoom and keep as much detail as possible.
The built in iOS camera app can do something sort of similar - you can set it to shoot in adobe raw (12mpx scaled down from the 48mpx sensor). Often the phone will shoot HDR by combining multiple photos. And in night mode (either manually activated or auto) it will stack (combine) multiple exposures for long exposure noise reduction and (maybe) exposure stacking. Setting it to a longer amount (max is 7 seconds I think) should thereotically combine more photos.
The adobe raw format can store this info (it's actually quite underrated - I first switched to iOS with the 15 pro and immediately tried to find a way to shoot a true "normal" raw like a .DNG). I'm very into photography and used to be a professional film editor and one my favourite hobbies is astrophotography (with a real camera and tripod).
The cool thing about adobe raw specifically is that the HDR stack is not baked into the file. If you open one in Lightroom mobile, for example, there is a slider under the far right "profiles" editing section. The slider defaults to the middle (50) which is basically the default stacked HDR look from Apple. Moving the slider all the way left will have it use a single exposure (normal raw - no HDR no stack). Anywhere in between will be a blend of the two. If you don't see the slider then you haven't properly opened the adobe raw file in Lightroom mobile (you may have opened a jpeg preview or accidently shot in .heif)
It's quite counterintuitive because "profiles" when editing a non adobe raw is a totally different function (more like adding preset looks). If the file was not taken in HDR then the slide will do nothing. I'm not exactly sure what moving the slider to the right does (it seems to increase the amount of HDR or something - I never use it).
I've noticed that when editing adobe raw on iOS messing with this slider seems to be by far the most CPU intensive aspect. Sometimes the image preview updates immediately and sometimes it takes awhile and the phone heats up. Sometimes the app just crashes. It might be using a similar algorithm to what the Adobe Indigo app is using here for image capture.
Editing raw files also kills my battery life faster than anything else I've done (which makes sense) considering that it's a fairly intensive process. This was also true on previous Android phones so it's not limited to iOS. I usually stop any music playing at the same time and make sure the phone is out of direct sun and it seems to handle heat buildup well when doing this. If it does heat up I remove the case and put it in front of my car AC vent or some other ventilated area and it cools relatively quick.
The app is so heavy that the phone is overheating after the first photo. it consumes so much resources that’s the music was playing in the background stopped because my AirPods connection dropped. For the very first time on this phone I felt like I need an upgrade, it felt like the last days of my iPhone 6s. I didn’t know you can do that to an iPhone.
The photo quality is supperb though, obviously not DSLR replacement but it really gives you that feel. Apple’s own processing has become too boring, sometimes I use Halide just to have unprocessed raws.