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.
iPhone 14 Pro Owners Complain of 'Slow' Camera App
- Thread starter MacRumors
- Start date
- Sort by reaction score
Thank you. I thought it was me. This thing feels so slow compared to my iPhone 13 Pro
To avoid sensationalism and balance the need for clicks my guess is two taken from any combination of here, Twitter, Reddit, heard it from a friends cousins uncle who heard it from their gym partner.
Have not yet had the slightest problem of any kind so far on my 14 Pro, but I don't use Snapchat or the IG photo app, and I sure as hell don't use TikTok.
I took several hundred photos yesterday in both standard and raw formats, from pano to macro and everything in between, and they look great.
I took several hundred photos yesterday in both standard and raw formats, from pano to macro and everything in between, and they look great.
iOS 17? You have to be joking. This **** needs to be fixed asap
I've had no issues with my 14 Pro Max since I received it on Friday thankfully. Also, the issues reported so far are still better than the Note 7's catching on fire, lol.
I have a 14 Pro ordered and will arrive between the 3rd and 10th of Oct, looking at all that is wrong with this phone, I am considering cancelling, it's certainly looking like a "Lemon." Just looking at Mac Rumors, the first 3 items were about faults with this phone.
People always think it's the buggiest app update ever. It's also why I usually wait a few months before getting the newest phone.
The whole switching experience from iPhone 12 Pro to 14 Pro was rather miserable tbh. Super slow transfer, cancelled transfer, icloud glitches, messages not loading, etc. Worst yet - and I’ve been on iPhones since the first one.
Which I did... Like in previous years, I purchased a 14 Pro Max.
I am preparing a comparison for a video and then the 13 PM goes to my father.
13PM here and the photo sound actually is late but the picture is fine. It's kind of weird, but not a functional issue (yet). The first few times I thought I got a picture inside my pocket again. It's kind of funny actually.
But anyway...
But anyway...
Next MR article: User complain about the glass used by Apple smudging easily after eating pizza and not wiping hands.
Hopefully an update fixes it.
People blow everything out of proportion.
Hopefully an update fixes it.
People blow everything out of proportion.
Way back in 2016 or so Apple fixed slow Camera launch with a Camera-specific scheme.
The basic idea (to simplify) is that instead of having a unified pool of free pages available to all apps, we have two pools, a pool of "really" free pages, and a pool of pages that are relevant to the execution of the camera app. Under normal circumstances we only need pages from the "really" free pool, and we only tackle the "camera" pool when things get bad.
This solves the fast camera launch problem but is not optimal in another way; it does mean that, overall, apps may run a little slower because they may be using less memory than they could.
It's possible that what we are seeing is a bug.
Or it's possible that a deliberate decision was made that it was now time to end this special case situation for the Camera, and that the slight slowdown was acceptable. Normally it shouldn't be too bad because most of the pages are part of general shared iOS libraries that will be present anyway. Perhaps this situation occurs in cases like large games that take over the entire phone and mostly use their libraries for everything, not Apple libraries, so any subsequent app launch (Camera or otherwise) seems slower than normal?
(One way to improve things may be to retain the special pool, but make it limited more to common Apple libraries and less about specifically the Camera app?)
The basic idea (to simplify) is that instead of having a unified pool of free pages available to all apps, we have two pools, a pool of "really" free pages, and a pool of pages that are relevant to the execution of the camera app. Under normal circumstances we only need pages from the "really" free pool, and we only tackle the "camera" pool when things get bad.
This solves the fast camera launch problem but is not optimal in another way; it does mean that, overall, apps may run a little slower because they may be using less memory than they could.
It's possible that what we are seeing is a bug.
Or it's possible that a deliberate decision was made that it was now time to end this special case situation for the Camera, and that the slight slowdown was acceptable. Normally it shouldn't be too bad because most of the pages are part of general shared iOS libraries that will be present anyway. Perhaps this situation occurs in cases like large games that take over the entire phone and mostly use their libraries for everything, not Apple libraries, so any subsequent app launch (Camera or otherwise) seems slower than normal?
(One way to improve things may be to retain the special pool, but make it limited more to common Apple libraries and less about specifically the Camera app?)
Now is it any wonder why apple wants these lazy asses to come back to the office. The results speak for themselves.
I would be incredibly surprised if any issues you've have over the years with your camera are related to this particular issue. If your issues are related, I would have expected them to surface on various forums as quickly as this one did.