Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
After receiving a replacement phone that has the same issue as the original I’ve been in contact with apple support engineers about this issue and have uploaded pics, screen recordings of taking photos with the blue line and uploaded diagnostics. Hopefully they work out something soon. Apple engineer suspects software.

I was just relieved to hear them admit the issue. The person I talked to said she was working with a few other people with the same problem.
Let's hope to hear the good news about this being software and not hardware related!
 
  • Like
Reactions: TonyC28
I really doubt this is just software related and that it's some combination of hot pixels and image processing.

My theory is when the sensor has some hot pixels (and specifically blue ones) the image processing is seeing this as "light" and turns up some processing for the image. Most examples posted does seem to have brighter pixels that are blue.
Some users posting complete black test photos have red hot pixels, so the processing doesn't seem to work the same with those.

Apple could probably have some sort of digital remapping function for the camera sensor, if that is even possible (some DSLRs have this feature).
Or that their camera software can identify them and remove them during processing photos (but then in a stage where other parts of the photo is not affected).
 
  • Like
Reactions: winxmac
Do you mean a “real picture”? If you do then in a dark enough environment Night Mode comes on automatically and you don’t need any camera settings. Handheld Night Mode gives 1 to 10 second exposures automatically, depending on how dark it is. To get up to 30 secs you need a tripod.

But sticking to handheld… go outside at night, well after sunset and well before sunrise. My garden is dark enough to automatically get to 10 seconds, but with significant light pollution it might be less. Try and take a landscape picture of the horizon, ideally at least half sky and ideally a clear night so that there are some stars. You can have trees, water or buildings etc on your horizon.

If it’s nice and dark you should see the Night Mode icon (circled red) in the camera app. In my example it’s 3 sec but can be up to 10 sec. It depends on how dark. Then just press the shutter - done. See if you can see any odd blue patches.
He can also set nightmode to max then he will get the 10 secs most times if it's dark enough.
 
Well now I'm losing faith in Apple's engineers. They called me back today to ask some follow-up questions. They asked if I'm experiencing this long exposure Night Mode issue in videos, or just pictures. :rolleyes: Then they said some "noise" is common when taking a picture in very low light, or no light at all. I had to explain that my I tested this on two iPhone 16 Pros and one iPhone 12, and only one of the 16 Pros has the blue issue, which is not simply noise.

The problem is that even if this issue were widespread, most users are not taking 30-second exposure pictures in very low light conditions.
 
I talked to an Apple Support engineer today who confirmed they know about the blue long exposure issue and that it’s software-related.

Not likely. The blue noise is related to differences in how the sensors handle high ISO. I had both a 16 Pro and 16 Pro Max. The 16 Pro had the blue issue and the 16 Pro Max had not, and when shooting a regular RAW in manual camera app at 10K ISO the amount of noise was night and day. So it is surely a hardware difference causing this.

The only thing Apple can do software wise to "solve" this is to apply additional noise reduction and post processing which will lead to less detail on the phones affected.
 
Not likely. The blue noise is related to differences in how the sensors handle high ISO. I had both a 16 Pro and 16 Pro Max. The 16 Pro had the blue issue and the 16 Pro Max had not, and when shooting a regular RAW in manual camera app at 10K ISO the amount of noise was night and day. So it is surely a hardware difference causing this.

The only thing Apple can do software wise to "solve" this is to apply additional noise reduction and post processing which will lead to less detail on the phones affected.
Slight tangent - can’t help but notice all the hardware issues going on between this, the screen brightness, and the touch issues thread — all of these seem to improve with hardware replacements? This is on top of the typical OLED lottery
 
Not likely. The blue noise is related to differences in how the sensors handle high ISO. I had both a 16 Pro and 16 Pro Max. The 16 Pro had the blue issue and the 16 Pro Max had not, and when shooting a regular RAW in manual camera app at 10K ISO the amount of noise was night and day. So it is surely a hardware difference causing this.

The only thing Apple can do software wise to "solve" this is to apply additional noise reduction and post processing which will lead to less detail on the phones affected.
But how do we reconcile one iPhone 16 Pro having the issue and another not?
 
My other half has a heap of crash reports from her using the 16 Pro Max camera

She has a nail business and needs the camera to take shots of her clients nails, and the camera crashing every time or freezing is doing her head in!
 
From recent discussions in online communities, it appears that Apple has reportedly begun rejecting returns over this matter. An internal note suggests that Apple views this method of testing as invalid, labeling it as part of the standard processing for 30-second exposure photos, which supposedly few people actually use.
 
Last edited:
Slight tangent - can’t help but notice all the hardware issues going on between this, the screen brightness, and the touch issues thread — all of these seem to improve with hardware replacements? This is on top of the typical OLED lottery

This is by far the worst release Apple has ever made. Unfinished software and poor quality control. But they do offer great customer service and happily replaces phones that have any of these issues.

But how do we reconcile one iPhone 16 Pro having the issue and another not?

It is a hardware issue and some units have faulty (or out-of-spec) image sensors for the primary camera (1x). The statement that it is a software issue makes no sense at all to me. If Apple would "solve" this with software, I would be pretty worried that they just made the issue harder to see.

My other half has a heap of crash reports from her using the 16 Pro Max camera

She has a nail business and needs the camera to take shots of her clients nails, and the camera crashing every time or freezing is doing her head in!
I would attempt a full restore (Recovery mode) and then setup the phone without restoring iCloud backup and see if that helps. It seems to be a universal fix for all sorts of software related issues with the 16 series.
 
  • Like
Reactions: leebroath
Unfortunately, from what I've been reading in other forums / groups the past few days, there have been multiple reports that Apple has stopped accepting returns based on this issue (they have an internal memo saying that this method is not acceptable as a test and that this just normal processing of 30s exposure photos that apparently no one uses).
If this were the case, then it would be replicated on all phones. The simple fact that several phones running identical backups and firmware exhibit different results with the test.

Some are completely black, some are completely blue and the others and degrees inbetween.

The really kicker here is that if you actually take a 30 second exposure photograph at night, you can see the issue, it’s just that the “test” makes it easier to see.

Jason
 
  • Like
Reactions: TonyC28
It is a hardware issue and some units have faulty (or out-of-spec) image sensors for the primary camera (1x). The statement that it is a software issue makes no sense at all to me. If Apple would "solve" this with software, I would be pretty worried that they just made the issue harder to see.

Yes, exactly. Maybe Apple could reduce the issue with software if the issues are from what I'm theorizing is from blue hot pixel issues with the sensor/sensors, but they probably won't or are able to.

Unfortunately, from what I've been reading in other forums / groups the past few days, there have been multiple reports that Apple has stopped accepting returns based on this issue (they have an internal memo saying that this method is not acceptable as a test and that this just normal processing of 30s exposure photos that apparently no one uses).

Where did you read this? Seems like if there is issues with the hardware it should be on warranty.
 
Yes, exactly. Maybe Apple could reduce the issue with software if the issues are from what I'm theorizing is from blue hot pixel issues with the sensor/sensors, but they probably won't or are able to.



Where did you read this? Seems like if there is issues with the hardware it should be on warranty.
On Reddit and FB group
 
I would attempt a full restore (Recovery mode) and then setup the phone without restoring iCloud backup and see if that helps. It seems to be a universal fix for all sorts of software related issues with the 16 series.
Not restoring from an iCloud backup will be the last resort, she has heaps of things she'd need to do if setting up as new
 
Yes, exactly. Maybe Apple could reduce the issue with software if the issues are from what I'm theorizing is from blue hot pixel issues with the sensor/sensors, but they probably won't or are able to.

Normally there are just a few pixels that are calibrated out of spec and reacts bad to higher current (hot pixels). Not the entire sensor as is the case with phones that has this issue.

It will not be possible to fix this but it will not be a big issue when shooting in normal conditions. Only for more extreme low light.
 
My iPhone 16 Pro Max shows the blue in the bottom right. iOS 18.2 beta 1
IMG_6385.jpeg
 
  • Like
Reactions: BugeyeSTI
16PM, this is what it looks like for me - vertical ISO8000, horizontal ISO10000. Exposure time 30s
 

Attachments

  • ISO 10000.JPEG
    ISO 10000.JPEG
    46.6 KB · Views: 82
  • ISO8000.JPEG
    ISO8000.JPEG
    46.6 KB · Views: 77
This is normal. Will not be an issue in normal photography.
Yes, I understand what you're saying but I would like to do some astrophotography in the future and I'm worried it may be an issue at that time. This is a picture I took in my backyard on a dark night. Long exposure without a tripod high ISO: Crappie photo but blue streaking is noticeable
8B731E47-85B2-4DCD-894F-DEF2A0C0DFF7.jpeg
 
Yes, I understand what you're saying but I would like to do some astrophotography in the future and I'm worried it may be an issue at that time. This is a picture I took in my backyard on a dark night. Long exposure without a tripod high ISO: Crappie photo but blue streaking is noticeable
View attachment 2442169
And herein lies the problem. It is not good enough from Apple, this really needs to be addressed. I’m convinced it’s a hardware problem.

If the blue lines are showing up in an image, then it’s not fit for purpose. No point having a long exposure night mode if it doesn’t work properly

Jason
 
And herein lies the problem. It is not good enough from Apple, this really needs to be addressed. I’m convinced it’s a hardware problem.

If the blue lines are showing up in an image, then it’s not fit for purpose. No point having a long exposure night mode if it doesn’t work properly

Jason

Exactly! It’s not acceptable. My iPhone 14 took better Night Mode images and astrophotography pictures than this. In two years you don’t expect to go backwards!
 
My newest natural 16 pro seems to be better, but the ISO was only 5000 (30 sec shot). I’ve had some phones with hot pixels, some with the blue streaks, but this is the first one that had nothing.
 

Attachments

  • IMG_0035.jpeg
    IMG_0035.jpeg
    46.6 KB · Views: 66
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.