Related
Go to HKLM/Software/HTC/Camera/Common and change EnableFrameRateInfo to 1
ok now go back to either your camera or video camera and you'll see there's now a little box telling you the frames per second. If you play with it you'll notice that it gets very poor in low light (probably around 3 fps) to slightly better in bright light (15 or so). Either way, these frame rates are probably causing the blurry photos. Not sure of the answer, but this shows the problem. Any one have thoughts on if this is a software or hardware issue or any way to tweak this? If you're getting 3fps then the image needs to be entirely still to not blur...
thanks bugsy. i've tried powering off the screen while in camera mode for 10-15 secs and then turning it back on which seems to reduce some of the camera lag or low framerates and now i can more accurately judge what the difference really was. i went from 3-5 fps, to 15-20 fps.
!
10x for the tip bugsy i never got to 20fps even ouside in day lite so i really
hate the way TP is recording....if you move your hand it records like
crap...found a funny one: while using flash lite the lite is reflecting in the
picture so i try to fix it (take one photo with flash lite in dark and then
take another one with the back cover from TP off ) look in the right side of picture to see the diference ,to fix it i painted with a black marker inside the
phone back cover near camera and flash !!!
any ideas how to fix this? 3 frames per second is a total joke. I can point it at a light and move the camera all over and get 15 fps with all sorts of movement. If I move it to low light I'm at 3fps... 15 is tolerable...3 is almost unusable.
dansobolanu said:
10x for the tip bugsy i never got to 20fps even ouside in day lite so i really
hate the way TP is recording....if you move your hand it records like
crap...found a funny one: while using flash lite the lite is reflecting in the
picture so i try to fix it (take one photo with flash lite in dark and then
take another one with the back cover from TP off ) look in the right side of picture to see the diference ,to fix it i painted with a black marker inside the
phone back cover near camera and flash !!!
Click to expand...
Click to collapse
I had noticed that flash reflection too, it really ruined flash shots! Well, I did like you said and took a dark marker and marked the metal part on the inside of the back cover, and now no more crappy flash photos, THANK YOU much for this tip!
bugsykoosh said:
Go to HKLM/Software/HTC/Camera/Captparam/Common and change EnableFrameRateInfo to 1
ok now go back to either your camera or video camera and you'll see there's now a little box telling you the frames per second. If you play with it you'll notice that it gets very poor in low light (probably around 3 fps) to slightly better in bright light (15 or so). Either way, these frame rates are probably causing the blurry photos. Not sure of the answer, but this shows the problem. Any one have thoughts on if this is a software or hardware issue or any way to tweak this? If you're getting 3fps then the image needs to be entirely still to not blur...
Click to expand...
Click to collapse
On mine, that key is found under HKLM/Software/HTC/Camera/Common.
californiarailroader said:
On mine, that key is found under HKLM/Software/HTC/Camera/Common.
Click to expand...
Click to collapse
you're right - I'll change the first post
No worries, thanks for the registry tip on this!
eastvanchinaman said:
thanks bugsy. i've tried powering off the screen while in camera mode for 10-15 secs and then turning it back on which seems to reduce some of the camera lag or low framerates and now i can more accurately judge what the difference really was. i went from 3-5 fps, to 15-20 fps.
Click to expand...
Click to collapse
10x but not really working for me,but i see that it works for many other people so i think that this have something to do with the battery power then i unchek Auto adjust backlight from power menu then start the camera it shows 8 to 12fps then in 1-2secs it checks it self somehow Auto adjust backlight box automatic and gose back to 3fps .... :-?? so i think the problem is from battery power that camera uses .... !!! (sry for my english )
californiarailroader no need to Thank me mate,i'm really glad i can help xda-developers with something (more or less) !
I want to see if anybody else is experiencing this issue.
Please post if you're rooted/unrooted and if you are rooted, what ROM you're using.
At this point in time, I have submitted a support ticket to HTC as well.
If you are in a low light/low-ish light setting (maybe even more, haven't tried all of them), and you hold your camera close to an object, the phone has trouble auto-focusing. It will attempt to focus, then revert to the blurred image. It seems that the only way to get focus is to find a way to get the camera to focus that image at a moderate distance and move it in close...but very slowly. That doesn't even work all the time. I think this is a SW bug...but I'd like to be sure.
I'm running CleanROM 3.1. (I've experienced this on CleanROM 3.0 as well )
Opened up camera and had the same problem you were describing, then just focused on a farther away object and tried to refocus up close and it worked fine (not using the focus on the object and slowly move closer method)
I tried that, it works sometimes and doesn't work other times (Automatically tries to re-focus and then reverts to a blurry, pre-focus image). It seems inconsistent, but it can work to get focus on close objects. I'm still hoping that HTC irons this one out
yellowfddriver said:
I want to see if anybody else is experiencing this issue.
Please post if you're rooted/unrooted and if you are rooted, what ROM you're using.
At this point in time, I have submitted a support ticket to HTC as well.
If you are in a low light/low-ish light setting (maybe even more, haven't tried all of them), and you hold your camera close to an object, the phone has trouble auto-focusing. It will attempt to focus, then revert to the blurred image. It seems that the only way to get focus is to find a way to get the camera to focus that image at a moderate distance and move it in close...but very slowly. That doesn't even work all the time. I think this is a SW bug...but I'd like to be sure.
I'm running CleanROM 3.1. (I've experienced this on CleanROM 3.0 as well )
Click to expand...
Click to collapse
I have been looking at this since I picked up the HOX on release day. I'm now running fully stock ROM on the official 1.85 OTA release and I have seen a major increase in up-close focusing from the camera. I haven't made any changes to settings, but since the OTA I have absolutely noticed a marked improvement in ability to lock focus on macro-level objects, even when not in macro (Close Up) mode.
I've had this and even replaced my phone, AND tried several store units and they all do it.
yellowfddriver said:
I tried that, it works sometimes and doesn't work other times (Automatically tries to re-focus and then reverts to a blurry, pre-focus image). It seems inconsistent, but it can work to get focus on close objects. I'm still hoping that HTC irons this one out
Click to expand...
Click to collapse
Did some further testing, I can get it to work but it is inconsistent
News flash, cameras struggle to focus on subjects in low-light. My $5000 Nikon D4 doesn't always achieve focus correctly. So expecting a cell phone to be perfect in low light is ridiculous.
My One X can't focus on anything close up regardless of light level.
feanor512 said:
My One X can't focus on anything close up regardless of light level.
Click to expand...
Click to collapse
Have you tried the close up setting?
Sent from my HTC One X using xda premium
kleeman7 said:
Have you tried the close up setting?
Click to expand...
Click to collapse
Yep. No effect.
feanor512 said:
Yep. No effect.
Click to expand...
Click to collapse
Hmm, mine works great, I did flash the 20mbps camera mod, but that wouldn't effect that.
Sent from my HTC One X using xda premium
In 4.2.2 you just press and hold the screen while trying to take a picture and it does AF and AE but I tried the same thing in 4.1.1 but I can't get it to focues. Especially while taking pictures at night. Does anybody know how to lock AE and AF in 4.1.1?
Super sensitive touch:
Sometimes car keys work, other times they don't. I have thick gloves- doesn't really work consistently there either. It's weird- I can use the screen a few times with metal devices then they no longer work until I toggle the sensitivity setting.
Speakers:
The on device speakers pop when I change volume (while music is playing). This actually happens on my Windows 3.1 Compaq computer (except it happens there when no music is playing)! Interesting that such an ancient problem has come back to haunt me... It can be hard to hear in certain songs, but in a soft, slow song it is easily heard.
Colors/Rendering:
A couple times now, I noticed that my screen has misrendered colors. Like, I'll be typing something, and the entire screen becomes paler, as if the contrast were turned up high (as in, *actual* contrast, not "high contrast" mode which just changes the colors to black and white). It would change back within seconds. Is this the "daylight" mode or something?
Is something wrong with my device or is this normal...?
Thanks. I only have 13 days to return it for another.
I've experienced the first two problems.
I only experience the second problem with music on my sd card.
As for the third, are you typing with the phone held horizontal, and possibly have your finger over the light sensor at the top near the front camera, this will cause the brightens to go down.
You can change the screen sensitivity. They say when it is on high u can use it with gloves.
jambo89liam said:
I've experienced the first two problems.
I only experience the second problem with music on my sd card.
As for the third, are you typing with the phone held horizontal, and possibly have your finger over the light sensor at the top near the front camera, this will cause the brightens to go down.
Click to expand...
Click to collapse
No, it was in portrait orientation at the time. Hasn't happened since...
Sent from my 820 using Board Express
You always get these kind of quirks with new hardware software, mine has random reboot issues. I'm sure they will be ironed out. You always have your 2 year Nokia Warranty, i'd stick with it its a great device.
jambo89liam said:
You always get these kind of quirks with new hardware software, mine has random reboot issues. I'm sure they will be ironed out. You always have your 2 year Nokia Warranty, i'd stick with it its a great device.
Click to expand...
Click to collapse
It's a question of 'does mine have hardware defects and should I get another' rather than getting a different phone altogether. It would be easier to walk into an AT&T store and walk out with a new phone than to go through a warranty process (you are allowed to do this within 14 days). I think I've determined these are all software bugs though, so that shouldn't be necessary.
Sent from my Windows 8 device using Board Express Pro
Hello, i'm from Colombia and my english is not that good.
But i'll try.
27th Dec 2012 i bough and HTC One X at&t from Amazon, got delivered by Jan12 Saturday 2013 about 15:00 hours, retrieved, unboxing bla bla bla, i was testing the device, i came with ICS 4.0.4, Sense 4 and RUU 2.20, everything was working fine, data, wifi, screen, sound, but, when i was about to try the LED Flash of the Camera (to find out if it has AF Assist Lamp, witch it hasn't) i found a very weird artifact
This is it, i took 2 photos to a paper on a tablet.
The left one <-- was taken with LED Flash On (NOT AUTO, ON) and the right one --> was taken with it off (OFF, NOT AUTO)
This is so frustrating, practically there is no way to take photos with flash, is not a hardware issue (i think cuz when i record a video and take a photo while recording with LED LIGHT ON, the photo is fine, there is no such artifact), another way was changing the auto whitebalance to fluorescent and the photo becomes a little decent, and i thoght that i can handlet it, but no, when on Instagram, Facebook Cam, Cymera, etc. There is no sense Cam interface to take Photos while recording a video, neither the auto white balance option to get rigde of the "sephie like effect" so, i decided to change the ROM just to try:
Tried Vyper XL 3.0 and 2.4 and was the same ****, so i decided to reflash the device back to stock with and RUU 2.20, right now it has OEM ROM with Bootloader relocked and no root. and is in the same that was when i got it.
So, the Q are:
Is there another person who has experience the same issue?
Is there a way to fix it? Since i think it is a software problem, maybe yes maybe not.
Thanks.
I was thinking about sending back to LA for Warranty but... It will cost me $74 and a month of waiting.
i searched on Google and here but found nothing.
UP (?)
I don't think there is anything to "fix" here, and the camera is basically working as intended. It looks like just a matter of taking a picture of a completely white frame combined with the flash, which is throwing off the white balance. I'm sure there a plenty of other color/light combinations that will similarly result in odd white balance results. Its just a computer algorithm that is trying to interpret the lighting conditions and guess the "best" white balance, and its not going to be correct all the time.
You've already found the workaround, which is to either turn off the flash, or change the white balance manually. Or you might be able to fix the color after the fact with the built-in editing feature or 3rd party apps. I certainly wouldn't suggest warranty service, and don't think it will fix the problem anyway.
Flash isn't recommended for macro/close range shots, anyway. You get unsightly reflections like the one in your example. Even aside from the "sepia" tone, your second (no flash) example just plain looks better in every way. So why even use the flash, unless you for some reason have a need to regularly take photos of documents in low light, requiring a flash?
redpoint73 said:
I don't think there is anything to "fix" here, and the camera is basically working as intended.
Click to expand...
Click to collapse
Wtf? xd
I have also a Infuse 4G, 8 Mpx too, LED Flash, and the results with the Flash on, no matter if it's needed or not, are as it should be.
But this? here are two more examples, and i just took about 50 pictures, all with the LED On, and the sephie tone is everywhere, from a bathroom with zero light to outside, with sunlight, and even blocking the LED light with the finger.
This is so frustrating. I hope that is there a fix .
Another factor may be that the white balance by default is significantly "over-saturated", presumably by HTC to make colors more vivid and "pop" more. This could be why you are seeing this effect on this phone, when you don't on other phones or digital cameras.
But the latest photos you posted look pretty funky. Also, I've also tried to duplicate the effect by taking a picture of a printed page, and can't get the sepia tint. In fact, my photos actually look more white with the flash (more of a yellowish tint with flash off). These factors make me re-think my previous statement that it is working the way its supposed to.
Does the yellowish tint happen with subjects farther away too? Such as taking a picture of a person or landscape?
Defect with the camera? Maybe.
A "fix" aside from repair or exchange? Doubtful. The fact this issue persists across multiple ROMs suggests it may be a hardware problem.
redpoint73 said:
Does the yellowish tint happen with subjects farther away too? Such as taking a picture of a person or landscape?
Yes, no matter what, if the flash is On, the "sephia like effect" persist
Defect with the camera? Maybe.
A "fix" aside from repair or exchange? Doubtful. The fact this issue persists across multiple ROMs suggests it may be a hardware problem.
I have tried Viper XL 2.4 and 3.0 but not with CM 10 or AOSP ROMs.
Click to expand...
Click to collapse
:V
Negruka said:
I have tried Viper XL 2.4 and 3.0 but not with CM 10 or AOSP ROMs.
Click to expand...
Click to collapse
Couldn't hurt to try a AOSP-based ROM. ViperXL uses a different camera from stock 2.20 firmware, although its a newer version of the Sense camera.
I noticed the other night as I was using my pixel 2 and viewing a security camera monitor when it's infra-red/night vision was active that the IR beacon on the front of my phone pulses regularly even when I am not using the front camera of my phone, and don't have a camera app running at the time. Does anyone know why the phone is using the IR light and sensor when I'm not using the phones front camera?
I don't think the pixel 2 has an ir on it.
leveleyed said:
I noticed the other night as I was using my pixel 2 and viewing a security camera monitor when it's infra-red/night vision was active that the IR beacon on the front of my phone pulses regularly even when I am not using the front camera of my phone, and don't have a camera app running at the time. Does anyone know why the phone is using the IR light and sensor when I'm not using the phones front camera?
Click to expand...
Click to collapse
Are you talking about the notification LED that sits in the top left hand corner or the camera LED flash? Your confusing me with this infrared/IR business. The pixel 2 doesnt have infrared.
enzyne said:
Are you talking about the notification LED that sits in the top left hand corner or the camera LED flash? Your confusing me with this infrared/IR business. The pixel 2 doesnt have infrared.
Click to expand...
Click to collapse
No, I am certain it is not the notification LED. That is visible in normal lighting conditions. What I am referring to is only visible in night vision, which uses an infrared light and sensor. So this is clearly a blinking infrared light on the top of the front/face of the phone. I believe it is normally used to detect the distance of subject matter to help adjust the front camera focus depth.
Also, I don't know how the "n" in infrared got deleted after I finished typing in the rest of the title for this post, but I assure you that when I typed the word it showed up as "infrared" not "I frared". And now I can't seem to figure out how to edit the title of the post, so I guess it's stuck like this.
I'm starting to wonder if I've stumbled upon something that may be evidence that the phone is always using the front-facing camera - even when the user isn't using the camera or any app that uses the camera. I had my fiancée also come into the room so I could see if the same happened with her iPhone 6. On hers, no light on the front was active until she unlocked the phone. But as soon as she did, an infrared light on the face of it stayed illuminated *constantly*, whereas the one on my pixel 2 just flashes periodically.
My inner conspiracy theorist is starting to wonder WTF is going on here, and why these sensor arrays are active even when the front camera isn't in use.
I'm hoping a well-informed Android or Pixel 2 developer will see this and respond to address these concerns.
leveleyed said:
No, I am certain it is not the notification LED. That is visible in normal lighting conditions. What I am referring to is only visible in night vision, which uses an infrared light and sensor. So this is clearly a blinking infrared light on the top of the front/face of the phone. I believe it is normally used to detect the distance of subject matter to help adjust the front camera focus depth.
Also, I don't know how the "n" in infrared got deleted after I finished typing in the rest of the title for this post, but I assure you that when I typed the word it showed up as "infrared" not "I frared". And now I can't seem to figure out how to edit the title of the post, so I guess it's stuck like this.
I'm starting to wonder if I've stumbled upon something that may be evidence that the phone is always using the front-facing camera - even when the user isn't using the camera or any app that uses the camera. I had my fiancée also come into the room so I could see if the same happened with her iPhone 6. On hers, no light on the front was active until she unlocked the phone. But as soon as she did, an infrared light on the face of it stayed illuminated *constantly*, whereas the one on my pixel 2 just flashes periodically.
My inner conspiracy theorist is starting to wonder WTF is going on here, and why these sensor arrays are active even when the front camera isn't in use.
I'm hoping a well-informed Android or Pixel 2 developer will see this and respond to address these concerns.
Click to expand...
Click to collapse
That's interesting. I will try with my phone and nest camera and see if it acts the same on mine.
I just tested it again, holding the phone at varying angles from the security camera, activating and deactivating its night vision/IR mode to see the difference. I recorded a video of it and will post a link tomorrow. When infrared is active, there is a clearly visible blinking light located in the center of the top of the phone just above the speaker bar (the one to the right of the front camera).
I'm really curious to get to the bottom of this so that I can dismiss the paranoia that big brother is constantly watching me through my phone's camera.
leveleyed said:
I just tested it again, holding the phone at varying angles from the security camera, activating and deactivating its night vision/IR mode to see the difference. I recorded a video of it and will post a link tomorrow. When infrared is active, there is a clearly visible blinking light located in the center of the top of the phone just above the speaker bar (the one to the right of the front camera).
I'm really curious to get to the bottom of this so that I can dismiss the paranoia that big brother is constantly watching me through my phone's camera.
Click to expand...
Click to collapse
?It's the proximity sensor.
ajrty33 said:
?It's the proximity sensor.
Click to expand...
Click to collapse
Exactly!!
But why is the proximity sensory active all the time? Is it so the Ambient display doesn't turn on when face down?
oSandmaNo said:
Exactly!!
But why is the proximity sensory active all the time? Is it so the Ambient display doesn't turn on when face down?
Click to expand...
Click to collapse
Its constantly trying to see if your phone is up to your ear or not.
I'm also wondering why the phone would need to have the proximity sensor active when I'm not using Ambient mode, and not currently engaged in a call. There's no need for it to be using the proximity sensor when I'm just browsing my home screen or using some other app. My phone isn't configured to turn off the screen if I set it face down for awhile or anything like that. So there shouldn't be anything using the proximity sensor.
This is common in modern phones, it's checking if you're holding it, if it if is by your face, in your pocket it allows gestures like wave to wake
Get used to it, it's not going away.
mrkhigh said:
This is common in modern phones, it's checking if you're holding it, if it if is by your face, in your pocket it allows gestures like wave to wake
Get used to it, it's not going away.
Click to expand...
Click to collapse
But the pixel doesn't have any of those features.
if u want to turn the sensor, disable all option in ambient display.
koax88 said:
if u want to turn the sensor, disable all option in ambient display.
Click to expand...
Click to collapse
Nope. I tested that a few months ago (this isn't the first time this has been spotted). You can turn the ambient display off completely and the sensor is still active.
Unless of course they've realised in the meanwhile that this is pointless and fixed it in a software update - I've not retested it recently.
Large Hadron said:
Nope. I tested that a few months ago (this isn't the first time this has been spotted). You can turn the ambient display off completely and the sensor is still active.
Unless of course they've realised in the meanwhile that this is pointless and fixed it in a software update - I've not retested it recently.
Click to expand...
Click to collapse
I Just tested my phone, the sensor did not blink at all if u turn off all setting in the ambient Display section. Even double tap to wake will make the sensor blink. I noticed this since 8.0 tho.
Sent from my Pixel 2 using Tapatalk
oSandmaNo said:
But the pixel doesn't have any of those features.
Click to expand...
Click to collapse
It certainly does. I use it to keep the screen off when my phone, in an Otterbox Defender, is in the holster, or when I lay it down face down. Both the front and rear cameras can see into the infrared. Just aim a TV remote at them when any camera app is running and press a button and you'll see the remote's IR LED going. (It has no IR output, though.)