Bad pixels in the camera sensor

I've got an iPhone 4S, 64GB (Verizon) and noticed a few bad pixels during video playback on our 42" TV (played back via the HDMI adapter).  It's something that most people would not notice, including my wife as she watched the video with me, but I'm a long time video/photo enthusiast and imperfections like that stand out to me like a pimple on an otherwise perfect looking face.
After several test videos and even photos, I am able to reproduce this pixel anomaly each and every time.  There are 3 pixels, just slightly to the left of the center, that show up incorrectly in kind of an obtuse triangular formation.  Two of them favor white, the third is dark.  It's not something that is noticeable on the iPhone 4S screen because not all of the pixels are shown, but on a monitor that can render *all* pixels of 1080 HD video playback they show up.
I'm certain it's not dust as I've inspected and gently cleaned the camera window, not to mention even a small spec of dust would not show up as a single pixel (or in this case, what appears to be two pixels right on top of each other for each of the problem pixels).  The anomaly shows up when lighter colors/gradients are present in that region of the screen.  Darker colors do not reveal the bad pixels.  Just to be clear - it's NOT a screen display issue - the pixels are noticeable on our 42" TV during playback, and also on my Mac monitor and iPad screen (ONLY when zoomed in viewing on my iPad, which is possible during playback of video using the stock photo app).  The bad pixels jump around a bit because of the digital image stabilization (that should make sense to the more hard core video enthusiasts), which further supports it is a capture issue, not a video coding problem or anything like that.  The issue is either with the image sensor itself, or the hardware's processing there of.
My question - has anyone else observed similar behavior?  If so, is there something  you're aware that can be done to correct it?  This is my second iPhone 4S, the first being a perfectly-functioning 32 GB model (which did not have this issue) that I returned in favor of a 64 GB model because I was burning through space too quickly.
I'm probably going to have to go back and try to explain this to the good folks at the local Apple Store, and try to get a replacement unit, but I'm not looking forward to having to show video samples and point out three teeny little dots that most people won't even notice, but drive me crazy (especially after dropping $400 plus tax and a two-year commitment).  A huge selling point of my iPhone 4S was of course, its superior photo and video capabilities.  I understand they're not pro quality, but there shouldn't be any consistent pixel issues like this going on.
Sorry for the long post, but I'd appreciate some feedback, suggestions, input.  Thanks.

pogster wrote:
The problem with this type of communication is what you are describing and what I think you are describing can sometimes be different so my apologiies in that regard.
No worries.  I agree - text-only communication can be a rather clunky experience in trying to convey complex issues without any visual or (2-way live) verbal means.  I was a bit worried about being too wordy in an already wordy post and feared that it might just be ignored if it was too long.  Again - I appreciate your chiming in.  You seem very knowledgable in digital photography, which is exactly what I was hoping to find.
Given that my description of "bad pixels" is a bit sloppy for what is really going on, I think you understand what I mean in my usage of those words.
To answer your question, the offending pixels, or very, very small little dots of imperfections, are present in both video playback and in still photos.  After shooting several test videos against neutral and textured backgrounds to see what kind of results I'd get in the appearance of the bad pixels, I also took several stills in "burst mode" using an app called "Camera-" against a wood grain background, as the woodgrain background offered the most visible and consistent view of the blemishes.  In motion video, the dots (bad pixels) are pretty easy to see on a large display, or when zoomed in during playback on my iPad 2's screen.  In stills, it was kind of tricky to identify them, because without the persistent motion of the background, the bad pixels almost blended in as random image noise.  I was however, able to identity with certainty the same bad pixels in most of the stills.  Additionally, at the higher resolution of the stills, the offending pixels almost don't even need masking or removal with photo editing software.  Like I said - without the constant visible background motion to make them stand out as irregularities, or the ability to do a frame-by-frame analysis (which I can do easier with the video file using an app called VideoPix), the bad pixels are more difficult to identify.
The importance in identifying the bad pixels in stills, even though they are practically not noticeable, is that it can now be determined that the bad pixels are not the result of some kind of video coding glitch, but rather present in the hardware of the device itself - either as a defective image sensor, or defective hardware that translates the data from the image sensor into the pixels utilized by the software for photos and video.
As part of the tests I ran, I captured video with an app called KingCamera, and it, too, produced the same results.  KingCamera also has an option for "locking" of the auto white balance and brightness, loosely similar to setting those manually on a higher-end, dedicated camera.  Even locking the white balance and brightness, the pad pixels were present, so the potential for the issue being caused by an anomaly in the software's auto-settings management were put to rest.
In regard to being able to correct the bad pixels in stills - yep, easily done.  BUT, I shouldn't need to.  In terms of correcting them during video playback, that *is* actually something I could probably work out a method of doing.  I used to dable in production videos that involved complex imaging filters, multiple composite video layers, and automated ways of identifying specific colors, contrast points, and patterns within images/video streams and altering them (such as cleaning up sloppy image mattes or locking in on visual patterns for the application of various video effects).  Again, this is something I *shouldn't* need to do.
The still photo and video capabilities on the iPhone 4S are outstanding, in contrast to what other similar existing devices offer (arguably better than or almost as good as the best competitor offerings, depending), but the quality is not DSLR, and like I said - I'm not expecting it to be.  I do expect however, and I don't think it is unreasonable to, image rendering without persistent "bad pixels" showing - even if I am only in the 1% of people who are likely to notice such image defects.  They are, in fact, defects, and not "normal operation for a device of this caliber".
I was hoping there might be some trick to correct them, but I kind of figured there would not be.  It seemed smart to at least reach out and see what other people may know that I might be missing.  Again, I regret terribly my poor decision to return my perfectly-functioning 32 GB iPhone 4s for the 64 GB model.  Knowing a little about the very intricate technologies that make these things seem "magical", I understand that there are dozens or even hundreds of very complex little components that are mostly stamped out on an assembly line of robot fabrication means, then assembled, at least in part, by humans in a factory who are required to pump out x number of these things in short periods of time.  I worried about the possibility of trading in my perfectly functional device for something that may be just a tad less perfect - just because of the odds.  My bad for not following my natural instincts on this one.  I just didn't want to have to constantly be managing space on my device.  I failed to think through my initial choice of the 32 GB model in regard to my trigger-happy photo/video nature.  The cumulative files are much larger on this device than I was initially expecting (because I was just too excited to get my hands on one on October 14 and failed to do enough research and calculations).  Days into owning my 32 GB 4S, I was already spending time, almost daily, re-rendering videos at 720 and 580 through iMovie, being somewhat irritated about having to replace the original videos with reduced resolution versions just to keep the videos live on my iPhone (sometimes archiving the originals on my Mac first).  Anyway - enough of my rambling.
Thank you again for your input, pogster.  If you have any other ideas, please share.  I'm pretty sure I know what I have to do to feel happy with my investment, though.  I'm just not looking forward to complaining about 3 bad pixels to a Genius Bar employee who's probably going to look at me like I'm one of those "never happy with..." people.  Three bad pixels that I won't even be able to show ON the actual iPhone itself, but rather bring my iPad 2 and show zoomed-in playback of the video footage.
Message was edited by: ascii-T - fixed type-o

Similar Messages

  • Sun light affects the camera sensor?

    Hi
    I have a lumia 1520 and once driving, my phone's camera was exposed to sun light for about 5 hrs as i put it on my car's dashboard.
    after then when i take a photo i feel my images got worse in quality and color.
    Am i suspicious or sun light really affects the camera sensor?

    Hi, AmirTofighi. Any chance you can attach sample photos? The sunlight should not affect the camera sensor AFAIK. However, we like to further check on this since you have laid the scenario.
    BTW, if this is using the built-in camera app, try using lens app and compare. Also, if you have a friend who is using the same model of the device, it would not hurt to check and compare the images taken on both devices.
    Hope to hear from you soon. :-)

  • Dust bunnies on the cam sensor. Can't find a Clone Tool in Aperture....??

    My Canon 5D takes incredible shots, but I often have to deal with some "Dust Bunnies", when shooting in very arid/windy locations. I can not locate a tool in Aperture that allows me to clone these out. Does a Clone tool exist?

    Yes, the spot is too uniform and both spot and patch are very hard edged ... have to work the softness and radius to get a reasonable result. BTW, too many spot/patches really make Aperture crawl and give the JPG export version the heabie jeabies (blank areas of the image apart from the patches)on my Quad.

  • Bad Pixel in Camera

    Just got my K1 and have been going through the preloaded apps.  All was fine until I opened the camera.  There appears to be a bad pixel in the camera, near the center of the screen.  It is there regardless of whether it is set to still or video.  It appears in any picture or video taken.
    What is the repair process here?  Will the whole system just get replaced?  Can the camera just be replaced?
    Solved!
    Go to Solution.

    Chooks,
    Why not bring it in to work on Monday and well have a look at it?   If the camera has to be replaced we can set up service, but it will be good to see what you are talking about before it is repaired.
    Mark
    ThinkPads: S30, T43, X60t, X1, W700ds, IdeaPad Y710, IdeaCentre: A300, IdeaPad K1
    Mark Hopkins
    Program Manager, Lenovo Social Media (Services)
    twitter @lenovoforums
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество

  • Does anyone know the viewing angle of iPad mini's camera sensor?

    I've read the iPad mini's spec and still can't find the width/height of the camera sensor.
    I only know its focal length(3.3 mm).
    If anyone can tell me about the camera sensor's width/height, I can figure out the viewing angle.
    I would be grateful for any help you can provide.

    I believe that is the information you was looking for: http://www.boinx.com/chronicles/2013/3/22/field-of-view-fov-of-cameras-in-ios-de vices/
    Remember: they measured the horizontal angle in degree in landscape mode, and the FOV on very compact camera should be affected ( a little bit ) by the autofocus.
    Bye, Stefano

  • C6-01 main camera sensor size?

    Hi all,
    Don't know if this is on the right place, but here we go...
    I've been googling for the C6-01 main camera sensor size and I didn't found the answser anywhere. That spec is not published on Nokia site, where one can only know that the sensor resolution is 2448 x 3264 pixels (8 Mpixels) and that the lenses are F2.8. But in terms of photography, it's useless to know that without knowing the size of the camera sensor.
    I've found somewhere that the N8 main camera sensor is 1/1.83", which makes it a better sensor then the sensor of most average compact digital cameras, which have a 1/2.3" sensor. But that's the N8...
    Cheers.

    Thanks Puigchild, but I already knew that.
    What is missing is the information of the size of the camera CCD sensor. When it comes to digital cameras, that's a very important info, since the bigger the sensor, the better is the camera. Bigger sensors allow more light to hit the sensor, which is obviously a good thing.
    Most compact digital cameras (the so called 'point-and-shoot') have  1/2.3" sensors. Some new advanced compact cameras have 1/1.7", 1/1.8" sensors.
    What I'm trying to figure out is why Nokia has never revealed the size of its smarphone's camera sensors. Nokia phones are known for their good camera phones. Revealing the sensor size would therefore be a good marketing strategy. For instance, as I said before, I read somewhere that N8 has a 1/1.83" sensor, and that's why its camera is better than most poin-and-shoot.
    Regards,

  • IPhone 5 dust on camera sensor

    Hey, there are dust particles on the camera sensor on my iPhone 5. This is very noticable on any photos and videos i take. Is there an easy fix to this or will i have to take it to the apple store? I would prefer to avoid the apple store this time of the year.

    I do not believe you can clean the sensor. If there is dust on it and the Phone was not opened or damaged Apple will replace it if the damage is relevant, if not you will need to reach an Agreement with Apple people.
    iPhone 5 should be in warranty also after Xmas... wait.

  • Dust on camera sensor, internally.

    So I recenlty got my Z10 it[s been working fine. I've took it apart(back casing only) a few times to insert the abttery, SIMs A Battery removal and reinsert ,and in the process some how within the  last few days a tiny speck of dirt/dust has gotten into the camera sensor. The black speck isn't on the screen and appears if you take a photo of something/using the camera app. It's not big just a tiny speck of dust/dirt. I've tried cleaning the outer casing and removig the back case and giving the camera section a light clean with a microfibre cloth but it still appears. If i take a phto of a white/light setting the spec is there, and stays in the same photo location when moving the photo around the screen or editing it.
    How can i remedy this, should I take the z10 apart to be able to access the sensor and remove the particle with a microfibre cloth?

    I do not believe you can clean the sensor. If there is dust on it and the Phone was not opened or damaged Apple will replace it if the damage is relevant, if not you will need to reach an Agreement with Apple people.
    iPhone 5 should be in warranty also after Xmas... wait.

  • Bad pixel streak yet again and after warranty.

    MacBook Pro (Retina, Mid 2012) This is very frustrating being this should not be an issue in first place. This is a replaced screen that was replaced due to bad pixels an now more bad pixels on the new screen. Apple store said it did fail the in house screen tests but it is out of warranty and i need to pay to have it replaced. Apple employee said its like a hard drive and apple is not responsible if it fails. Very poor example, they are not the same and essentially the SCREEN should not have repetitive issues of this nature. This is clearly a defect in the product that i love and they will not replace.
    Can someone help?

    MacBook Pro (Retina, Mid 2012) This is very frustrating being this should not be an issue in first place. This is a replaced screen that was replaced due to bad pixels an now more bad pixels on the new screen. Apple store said it did fail the in house screen tests but it is out of warranty and i need to pay to have it replaced. Apple employee said its like a hard drive and apple is not responsible if it fails. Very poor example, they are not the same and essentially the SCREEN should not have repetitive issues of this nature. This is clearly a defect in the product that i love and they will not replace.
    Can someone help?

  • Bad pixel camera

    on my iphone 5, when taking the back camera shows a small purple dot,maybe bad  pixel.what to do?

    if when you transfer the image to the computer
    the pixel issue is gon
    then it's the lcd on the phone not! the camera which have the problem
    cameras don't have pixels in the repsect that lcd screens have

  • How to add bad pixels to a DNG made from a CFA sensor raw data ?

    Hello all, I'm trying to build a proper DNG file from the raw CFA image acquired directly form an industrial camera.
    As usually there are a number of bad pixels around and I would like to mark them in the DNG so they can be correctly interpolated when the image is processed.
    In the latest DNG SDK (1.4) I've only found this rather thin references:
    "Defective Pixels
    There are two ways to deal with defective pixels in DNG.
    The first is to map out (interpolate over) the defective pixels before storing the raw data in DNG.
    The second is to include a bad pixel fixing opcode in the OpcodeList1 tag."
    OK, as each program/customer/etc. seem to have its own ( best ) algorithm to interpolate the bad pixels then OpcodeList1 it is.
    But then I've got this: FixBadPixelsConstant and I'm not clear about its usage, especially BayerPhase, is the same BayerPhase that is specified as a global property of the CFA or it is something separate and what ?
    Also is there some "industry standard" value for the Constant that will make more likely the established programs to process correctly the image ?
    And this Constant value is unique per DNG or can it be more ot them added, i.e. to somehow characterize the "badness" of the pixel, like reduced sensitivity, stuck at 0/max, etc ?
    In the end if somebody can share an one-liner on how to add programatically this tag using the SDK I'll be very grateful.
    Sorry for my newebie questions and many thanks for your help.

    Hello Dear
    Look FB60 screen has two parts :
    The one in which you enter information related to vendor is Header Level, in this case you already assign Personnel No. in Vendor Master so no field is required as Personnel no. will be picked up from Vendor Master level.
    The Other is line item level is bottom half part, if you want to assign personnel no. at Expense G/L level then if you scroll right you will find a field for Personnel no. If you can't see the field check your setting at OBVV for the field status group you assign to particular Expense G/L.
    Hope you Understood
    Cheers
    IMK

  • Will shooting pics of the sun hurt the camera in anyway - e.g. burn the sensor?

    Will shooting pics of the sun hurt the camera in anyway - e.g. burn the sensor?
    Solved!
    Go to Solution.

    "I generally shoot the sun as a background to a primary subject."
    That won't hurt the sensor.  Keep in mind the sensor is an electronic device.  Just like an audio amp, it can get overloaded.  Extreme amounts of light will max it out just like extreme volumn will do so for a amp.
    But remember the sensor is only exposed for a fraction of a second, usually.   It is not exposed when you are just holding the camera.
    Just a word of caution, you should never look at the Sun directly.  It is a bad idea and practice.  Don't do it.
    EOS 1Ds Mk III, EOS 1D Mk IV EF 50mm f1.2 L, EF 24-70mm f2.8 L,
    EF 70-200mm f2.8 L IS II, Sigma 120-300mm f2.8 EX APO
    Photoshop CS6, ACR 8.7, Lightroom 5.7

  • After iOS 5.1 update on iPhone 4, some of my pictures in the camera roll become pixelated after a crop edit?

    I will elaborate.  Lets say I save an image from a website.  Then I go to the camera roll and edit crop it to make the image a tad bit smaller. Suddenly the images becomes pixelated and blocky.  When  I return to the image and tap the edit button, it becomes clear again and I can see the original picture.  When I tap cancel, it goes back to beign pixelated/blocky.  I tired restoring my phone to factory setting and losing all my data.  That didn't work.  As soon as I tested it, the same thing happened.  I tried some weird method from www.iphoneincanada.ca an that didn't work either. 
    This is very annoying!

    I have more info.  I am using a program to look at the files on my iPhone.  I did some testing and I came up with this.  When a photo is edited ( in my case cropping) an image is created in the Metadata folder.  The metadata folder is contained in a folder called PhotoData.  For some reason, the cropped JPG is put within this metadata folder.  The  DCIM folder contains the "actual image" you saved from the internet or wherever.  When a photo is edited in camer roll, a .XMP file is created for that image (Sometimes) and it's about 1kb.  Coincidentally, the image that is pixelated DOES NOT have an .XMP file associated with it in the DCIM folder.  
    To conclude, it seems that the pictures that have a .XMP file associated with it in the DCIM folder does not come out as pixelated.
    If there is a .XMP file then the photo in the Metadata folder become pixelated. 

  • I bought a brand new Mac 27" desktop that came loaded with Adobe CS6. Everything worked like a charm until the hard drive, 1Tb, developed a bad sector and the Apple Store reinstalled a new one as I had extended warranty with them. The recycled the drive i

    I bought a brand new Mac 27" desktop that came loaded with Adobe CS6. Everything worked like a charm until the hard drive, 1Tb, developed a bad sector and the Apple Store reinstalled a new one as I had extended warranty with them. They recycled the drive immediately (like a fool I didn't ask for it back to get the data off it.) But luckily I have all my data on CrashPlan. I downloaded it and it worked great except I downloaded it to the desktop and not the original location so it got squirrely. I also have an external 1.5Tb drive that I wanted to make bootable so I installed Mavericks 10.9.3 . I then went ahead and installed it on the newly installed drive too.
    I think that because I have a new drive Adobe thinks I have a news computer. I bought the 27" Mac brand new from Ebay and it came loaded with software, including CS6. I have a serial number for CS6 but Adobe said it wasn't valid. (I have owned CS2, CS4 and now CS6 which came preloaded onto the Mac by the seller who told me that the software was registered to the Mac???
    I am going to re-download the backup but this time to the original location (I still don't think it will work with Adobe. What can I do about this?
    iMac 27-inch, Late 2012
    Processor  3.2 GHz Intel Core i5
    Memory  32 GB 1600 MHz DDR3
    Graphics  NVIDIA GeForce GTX 675MX 1024 MB
    Software  OS X 10.9.3 (13D65)@

    You need to contact Adobe Support either by chat or via phone when you have serial number and activation issues.
    Here is a link to a page with options to help make contact:
    http://www.adobe.com/support/download-install/supportinfo/

  • What do i do if the motion sensor on an ipod touch goes bad?

    The motion sensor on my ipod has went bad. how can i repair it?

    Try the following to rule out a software problem:
    - Reset the iOS device. Nothing will be lost
    Reset iOS device: Hold down the On/Off button and the Home button at the same time for at
    least ten seconds, until the Apple logo appears.
    - Reset all settings
    Go to Settings > General > Reset and tap Reset All Settings.
    All your preferences and settings are reset. Information (such as contacts and calendars) and media (such as songs and videos) aren’t affected.
    - Restore from backup. See:                                 
    iOS: How to back up           
    - Restore to factory settings/new iOS device.
    If still problem, make an appointment at the Genius Bar of an Apple store since it appears you have a hardware problem.
    Apple Retail Store - Genius Bar          
    If the iPod is defective and not under warranty
    Apple will exchange your iPod for a refurbished one for this price. They do not fix yours.
    Apple - iPod Repair price      
    The sensor is on the logic board and is not replaceable.

Maybe you are looking for

  • How to handle RunTime Faults which doesn't list under System Faults?

    Hi, I have a doubt regarding runtime faults in BPEL 1.1.In BPEL 1.1 some of the run time faults are categorised as system faults.So we can handle those run time faults using the faultname or namespace(http://schemas.oracle.com/bpel/extension) of syst

  • Synching to ibooks.. dumb question

    I have two ipads.  My wife does not want my books on her ipad and I don't want her books on mine.  When I try and synch after I have mine on my ipad, and then synch hers, my books end up on hers and she looses all of hers.  How do I get around this? 

  • Is it possible to make Multiple Broadband connecti...

    Hi I have been using BT broadband for some years using a BT Homehub 1.5.   My Freesat box is plugged in to my Homehub, so that I can reliably get BBC iPlayer on the main household TV, so I am unable to move the hub to improve wireless reception elsew

  • Inserting Data from Oracle to SQL Server on the Real Time Basis.

    Hi Everyone, I need to insert data from Oracle to SQL Server on the Real Time basis, we have to fetch data from oracle approx 20 tables, and each table has more than 30 Fields. I need to fetch data in every 15 mins. I have created a job using SQL SER

  • Help!JOptionPane

    Hello, I'm currenntly facing some problems with my application. I have developed a passwordframe for an application and what i like to do is after the user keys in 3 trys of the password the frame would actaully dispose. But currently i'm having a pr