iPhone 5 camera error – pink stripes

This story has been updates as of Nov 2013. Skip to: Replacement iPhone


After having taken around 1000 pictures and over 30 minutes of flawless HD video with my iPhone 5 (64Gb), it suddenly started giving me weird results.

The first Pink Stripes

The first irregularity appeared as stripes in the top of a video, giving resemblance to a severely broken VHS tape. I first thought the irregular pink stripes was only on-screen, but reviewing the recording proved the noise was burnt in.

ARVE Error: id and provider shortcodes attributes are mandatory for old shortcodes. It is recommended to switch to new shortcodes that need only url

Five hours passed until I tested the camera again. This time the noise was much more apparent, sometimes filling almost the entire screen. The camera was active the whole time, so I took a few snaps and screenshots.

Not only video

Screen capture from iPhone 5, showing a band of digital noise

At this stage, the signal/noise ratio was approximately 3:1, making it difficult, but not impossible to take a noiseless picture. I managed to get a comparison by taking pictures in a fast rate. These two images are approx. ½ second apart.

Still image from an iPhone 5, showing a band of digital noise

The problem was also apparent in 3d party apps like ProHDR.

After 30 minutes of active testing, the S/N had scaled to such a degree that the camera was practically useless. The stripes appeared 80-90% of the time the camera was active, and would now freeze the camera app completely after 10-15 seconds.

The first stripes were taken 16:45, the last 23:54. Although I wasn’t taking film and pictures the whole time, the noise was “active” for a good 7 hours, going from just a little to a whole lotta love in this period of time.

Troubleshooting

First of all, I was on our cabin in the mountains when this occurred. There is no 3G there (or at least very little), and the signal bars on the iPhone vary from 1-5 bars of Edge. The atmospheric conditions on this particular night was medium snowfall, dense skies, temperature around 0°C (Thats 32°F for you non-metric people).

I’m no electro engineer, but taking hints from my days of stage-PA and the EMR effect any cellphone radio can have on other electronic equipment – my best guess would be that this has something to do with proximity between the antenna and the camera circutry. I base this on the purely subjective fact that – when holdning the iPhone in the vicinity a loudspeaker, the audio noise from the speaker seemed to cohere with the visual noise.

My guess is that the Edge network, operating at the lower 850 MHz band, interfered with the camera module, and because of the atmospheric conditions, the network handshaking needed extra output power. Or the other way around, that the phone found a weak 3G signal, and tried real bad to connect to it by upping the antenna gain. If this assumption is right, my guess would be that this video is from an area with similarly low coverage / Edge.

ARVE Error: id and provider shortcodes attributes are mandatory for old shortcodes. It is recommended to switch to new shortcodes that need only url

A Working (Quick)Fix

As pointed out by Pete in the comments, there is a working fix: Just Turn Airplane Mode on, and shoot noise–, error- and stripe-less pictures and video to your heart’s content. Although this is no optimal or permanent solution, it will give you access to the camera in a pinch. You can also try the old, ‘temporary fix’.

Temporary fix (old version)

As noted in the comments, this fix has proven to be too flimsy for real world use. Since you might have use for it, I’m not going to delete it. Click here (or scroll down) for a working fix.

I concluded that rebooting didn’t work, but a hard reset seems to have fixed the problem for the time being. The stripes reappeared the first minutes, but diminished and then disappeared completely after some time. This might be purely coincidental. Perhaps the skies cleared out, perhaps the phone was out of pink juice for the time being.

Refund / replacement

I was hoping this problem might be fixed via a software update, or that it would reduce in intensity / not be that much of a problem, but no software updates has helped, and photographing in rural areas is just pure pain. I am now asking for a refund/replacement phone from Apple. Will post how the progress. (August 2013)

Refund pt. 2: Updated November 2013

After coming home from vacation, I immediately got on the line with Apple and asked for a replacement. Since the problem is very sporadic, and that the problem is somewhat undocumented on the net (also – my girlfriend has the exact same model iPhone as me, bought only a few months later. She has never seen the pink static.) I was worried that normal diagnostics wouldn’t suffice, and that I would get the old phone back. I made it very clear that the static only became apparent in rural areas with low coverage / on EDGE or 3G with bad signal / high antenna gain. While the Apple support members I spoke with didn’t seem to have first hand experience with this problem before, the process went smooth.

I asked for a replacement phone while they diagnostisiced it. As everything Apple support, the process went fast and smooth. I had a new phone in my hand by the end of day 2 or 3, and two weeks later my original phone was (seemingly) recalled.

So – what about my new iPhone? Is the problem gone?

As a matter of fact – NO, it isn’t. But at least – this version has far less of it. So far, I have only had pink static two times, in the same rural areas. But as far as support goes, it should be no problem for you experiencing this problem to get a replacement unit. That being said – Norway (where I reside) – has three years of complimentary guarantee for all mobile devices, put forth by the government. Your mileage may vary in other countries, and AppleCare might be necessary if you’re out of the 1 year complimentary guarantee of Apple.


Gallery of iPhone 5 camera static/stripes/noise

Update february 2013: I have taken over 15 minutes of video and around 300 pictures since the first pink party. Some in dense 3G areas, some in Edge county. None has any of the artifacts described in this post.

Update march 2013: New pink stripes. This time taken in the subway in the middle of Oslo. Camera was fine when exiting the subway.

ARVE Error: id and provider shortcodes attributes are mandatory for old shortcodes. It is recommended to switch to new shortcodes that need only url

Update, march 2013: Back on our cabin, and thick lines of noise appear instantly.
20130329-195054.jpg20130329-195108.jpg

Update, June 2013: Northern part of Norway = bad reception and lots of pink striping. Some of these images are HDR’s, so you’ll see some examples with trasparent noise. The completely white/pink image, could be a digital correction mask for camera vignetting.

20130620-155601.jpg20130620-155512.jpg20130620-155543.yjpg20130620-155751.jpg20130620-155457.jpg20130620-155437.jpg20130620-155630.jpg

FCPX vs Adobe

Adobe Premiere Pro CS6 Icon

I visited the Adobe Roadshow when Premiere Pro CS5 was announced, and I must say I was impressed. After half a decade of intermediate formats, transcoding and all that, the mercury playback engine was miles ahead of FCP7 in terms of uninterrupted workflow.

Final Cut Pro 7

At the time, DSLR video was about to become a major player, and Final Cut Pro wasn’t doing anything about it. Being able to edit in any codec was a godsend for editors more than ever mixing formats. As we all know by now, the background rendering version bumped 64bit of Final Cut Pro never arrived. Instead came a shitstorm of epic proportions following the release of what some called the iMovie Pro – the FCPX.

The Compressed Footage Editing Challenge

FCPX icon

I still haven’t familiarized myself too much with FCPX, but I recently had a small, interesting experience that struck me; Working on a documentary, I was receiving .H264 preview files from my editor. Wanting to test some cuts, I imported the clip into FCPX and told it to not transcode or optimize the file. What happened was just what I was expecting from a modern NLE: hazzle free, real time playback of a compressed 720i@H264 file. No intermediate file, no transcoding, no nothing. It just worked. Great!

But – while FCPX now supports XML, it doesn’t support FCP7 readable XML, so all my rough cuts would have to be redone manually by my editor, requiring a lot of time we didn’t have. This didn’t seem like a smart idea, so I fired up a trial of CS5.

[EDIT: I have later learned that there are multiple plugins avaliable for this process, like Xto7 and 7toX]

Adobe Premiere CS5

Based on the highly advertised mercury playback engine, I was completely sure the proess would be as smooth as in FCPX. I was proven wrong. Trying the same procedure with Premiere Pro CS5 was … crappy. Never mind the heavily touted Breakthrough performance with mercury playback engine; neither my old MacPro, nor my 2011 MacBook Air seemed to cope with the same file. First it needed to conform the video (a process that took a good ten minutes and somehow had to be repeated every 30 minutes or so. But the playback still was terrible. Giga crunchy blocks was appearing between all the GOPs, making the editing session unbearable. In addition, video was breaking up, and I was losing audio sync.

Since I’m missing the FCP XML support from FCPX, and given all the free advertising AVID and Premiere seemingly did get from the killing of FCP7, I thought the new version of Premiere, CS6 would have taken the advantage of fixing this this, so I downloaded it. How would it cope?

Adobe Premiere CS6

Trying CS6 was a bit better, the blocks were gone, but playback was only sporadic; It was impossible to switch between apps without being prompted with a black screen or the media pending window for 20-40 seconds before it let me edit again, and I got the exact same behavior from both my Macs.

So what am I saying really?

Even if they have had two years of perfecting their mercury playback engine, working with Adobe isn’t a breeze either. Compressed H264 might have or not have too much in common with native DSLR footage, but while this might not be anything but a biased test, it is far from insignificant, far from uncommon, and contains a factor I would greatly appreciate from a modern NLE.

In short, Adobe have been beat by a contender that was a laughing stock of the professional editing business only months ago…

Does that qualify for reevaluating FCPX? Not as a single cause, but based on these unscientific tests, it might show proof that Apple actually have done a very deep, and perhaps even superior job in their playback engine, and they aren’t even evangelizing about it. I guess I’m only saying although it still has a long way to go, I have begun taking FCPX seriously.

ALL YOUR AVID ARE BELONG TO US

Prøver å reversere lyd i AVID, et program jeg forlot for en dekade siden. Jeg trodde noe hadde skjedd på disse ti årene, men tok feil. All your base is not belong to you; det er AVIDs way eller ingenting. Skal vedde på at det er raskere å reversere lyden i Word. Blæh. (Men si gjerne ifra hva jeg tydeligvis gjør feil.)

All_your_avid

 


 

 

What happens if it actually works?

Italienere skaper kald fusjon (E24 link) i et rørsystem som ligner mest på noe nordmenn mekker billig sprit med.

Bortsett fra det minnet nyhetsklippet og den teoretisk sett største oppfinnelsen i moderne historie, kledt i sølvfolie (romfartsalderens og kjøkkenbenkens stiligste produkt) meg først og fremst om filmen Primer.

Primer-poster

Filmen, en seig perle av en sci-fi indie-film tar for seg den tilfeldige oppdagelsen av tidsreiser, og har undertittelen What happens if it actually works?“. 

Et godt spørsmål for oljelandet Norge om italienerenes kjøkkenbenkpregede sølvfolietroll faktisk viser seg å ikke sprekke i solen.

 

PS: Filmen anbefales forøvrig sterkt om du ikke lar deg skremme av at manusforfatteren, regissøren, klipperen, komponisten og en av skuespillerene alle er samme person, at han i utgangspunktet er matematiker, og at filmen etter sigende slår selv de fleste shoestring-budget filmer ned i støvlene med sitt produksjonsbudsjett på 7.000$.

Jeg falt pladask for den etter å ha sett denne XKCD-stripen. Her er traileren. Den sier ikke mye om filmen, men det er jo tross alt sånn de beste trailerene er.