It seems like just last week Apple CEO Tim Cook was apologizing for Mappsgate. As we all know, and have ridiculed constantly, Apple’s new maps app for the iOS 6.0 fell short of their typical “magic”. In a bold move Cook acknowledged that Apple Maps didn’t deliver the quality that iOS users are accustomed to. They even went as far as to suggest that users download other apps like Waze or use the Google Maps website.
Well late last week another problem started making it’s way onto the interwebs. Users of the new iPhone 5 (released just two weeks ago), have discovered a purplish haze in photos and videos shot with their iPhone 5’s when shooting against something bright, like the sun.
The problem has been officially described as:
“a purplish or other colored flare, haze, or spot is imaged from out-of-scene bright light sources during still image or video capture.”
While it’s nothing that’s going to affect the overall performance of the iPhone 5, nonetheless it can be annoying especially when the iPhone camera is touted as one of the best in the way of smartphone cameras. Many users have ditched their traditional point and shoot cameras in favor of the 8 megapixel iPhone camera.
Apple has now released a support document entitled “iPhone: Camera image effects”
In the document Apple doesn’t take responsibility for the problem the way they have in the past with Maps and Antennagate, instead they say:
“Most small cameras, including those in every generation of iPhone, may exhibit some form of flare at the edge of the frame when capturing an image with out-of-scene light sources. This can happen when a light source is positioned at an angle (usually just outside the field of view) so that it causes a reflection off the surfaces inside the camera module and onto the camera sensor. Moving the camera slightly to change the position at which the bright light is entering the lens, or shielding the lens with your hand, should minimize or eliminate the effect.”
So there’s no running back to the Apple store or Best Buy on this one. If you’re having this issue with your iPhone 5 you’re evidently, holding it wrong.
Linkage: