The focus on my camera died the morning after I got Nougat. I turned it in to T-Mobile for a refurb.
The refurb is garbage on so many fronts but worst of all the low performance of the main camera mode is atrocious. Even in shadows in decent light it is super dark. I can correct it with manual mode but if I take the same shot with the wide angle camera, it's super bright. The two cameras are night and day. It's a frustrating experience.
I'm trying to determine if Nougat screwed up the camera's low light or if this refurb just sucks.
*update*
Factory reset fixed everything. Not sure why factory reset fixed the low light performance of the camera app's automatic mode, but it did. Hopefully this will help anybody else who runs into this extremely random issue.
Related
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.
1. The sensor reading often jumps to 30000lx momentarily, (measured using Lux Dash in Debug mode), and so the phone blinds you for while. This happens in a repeatable fashion when you hold the phone at certain angles. Try it yourself.
2. The N5 reads zero lux even in moderate/dim light, while my old N4 still reads around 10 lux. The N4 was much better as you could make a distinction between the dim light and no light at all.
On the new N5 you have to set the zero lux level so it's bright enought for moderate light, which means it's far too bright at night.
Why is the N5 sensor so poor? Or is the kernel? Really, this is pretty basic stuff. Come on Google, we want the autobrightness to work fine without having to download apps to try and fix the most basic settings.
(As per other threads, the N5 stock autobrightness is almost unusable!)
Same here. Only occurs in the kitchen under the spotlights. I've had 2 phones and the same has happened on both using lux.
Sent from my Nexus 5 using Tapatalk
Happy to see others having this issue as well. I always figured it was a Kitkat bug.
I had some dead pixels on my first N5, so I got a replacement. The replacement is now exhibiting this weird sensor issue (also spiking up to 30,000lux based on device orientation).
I have the same issue on my N5, sudden freak peaks of 15000 lux or more, then suddenly back to normal values of 50-80. Same behavior on stock kernel and Francos Kernel.
Hoping for a quick fix by Google.
Kusie
I'm having the same issue too, but it appears to be under certain lightbulbs that I have this issue. For example in 2 different situations, one I was in a restaurant and another while I was in my bathroom, and my phone would constantly pick up either 0 lux or 30000 lux (depending on the angle of the phone under the light). This is under halogen lighting.
When I get out of the restaurant and under regular lighting and when I'm in my bedroom (LED/CCFL lights), the light sensor would behave normally.
Anyone else have these issues?
Aria807 said:
Anyone else have these issues?
Click to expand...
Click to collapse
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Can the sensor be calibrated or is it just bad hardware? This is a real annoyance. My S4 doesn't read 0 lux unless there is absolutely zero and it never jumps around. Even it's own screen reflecting on my face will cause it to read 1-10. That level of sensitivity is great for setting up lux to go subzero. Maybe the kernel is translating the sensor voltage output incorrectly?
Sent from my Nexus 5 using xda app-developers app
rabaker07 said:
Yes, and it's not really reproduceable for me but it's very annoying and sometimes painful. This screen can get very bright and it's blinded me in the dark when this happens.
Is it the light sensor? Is it LUX? Does this happen without lux installed?
Click to expand...
Click to collapse
Lux is a measurement of brightness.
I thought it was Lux causing it, but I have tried full wipe + reflashing a new rom, and my sensors still go a lil whack. This is flashing new rom + immediately downloading a sensor tool and checking the readings before installing Lux or any other apps.
However, Lux came out with a new version a week or so ago and it seems to have been waiving those spiked readings, so my phone atm isn't acting up super dim to super bright and back.
I still have this issue on 4.2.2.,very annoying. Is this a software issue or bad sensors?
Starts to piss me off so badly I think about sending my N5 back to google.
Happens both on stock auto brightness and yaab.
Help please?
Kusie
Yeah same here, very annoying, have to use Manuel britness very often
I have this same problem too. Using the Lux app debug mode I rotated the phone while in a room lit with incandescent bulbs and one lit with daylight. When rotating the phone I sometimes see a spike of 30000 lx but more importantly the sensor drops to 0 even though there is plenty of ambient light. During daylight I don't see the 30000 lx spikes but I still see the sensor dropping to 0 when there's plenty of ambient light.
I feel like the sensor is too far recessed into the phone and causing a tunnel effect. If the phone is looking at a dark shirt or surface that's a foot away from it, it will register 0 even though there's plenty of ambient light. This seems like a design flaw or a flaw in android's API.
Using the full version of Lux app might be able to fix it since it allows you to use the camera for ambient light detection but I haven't purchased the full app yet so I don't know.
Really wish android would have a solution for this because it's quite irritating.
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
clocinnorcal said:
Are you guys using the Lux app? I haven't had this problem with stock auto brightness.
Click to expand...
Click to collapse
With the stock auto brightness it was too bright in most cases and also in some cases the brightness would spike. Downloaded the free version of lux app in order to try to fix the problem and while it can adjust the brightness to be lower, the problem is that the light sensor gives low readings straight from the api.
I just installed Lux and I can't reproduce it on my Nexus. Mine always behaves correctly in automatic brightness, so I guess it's a hardware problem that only affects some devices?
I jump now in here as i have the same problem unfortunatley. I have no clue if its hardware related or software, but on my HTC One with kitkat running the same rom i dont have such issues s i guess its a HW fault. If anyone finds a solution or something that fixes this mess, would highly appreciate if wwe could keep this thread alive
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
coolguy949 said:
I hope it's just a kernel issue where it's not translating the sensor output to the OS granularly enough. On my S4, it has to be truly zero light for it to see 0lx. Even in low low light, it's registering a value between 1 and 100. It makes it very easy to distinguish between no light (laying in bed) and low light (driving in the car, movie theater, etc). I hope they fix it because it's rather annoying that we're having this issue.
Click to expand...
Click to collapse
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
n3ocort3x said:
The next interesting thing is that it happens only in 1 out of 6 rooms at home. I hope I'm not totally crazy but could it be a bad combination between a sort of light bulb and the sensor?? I know this sounds totally stupid but I only can reproduce it with one light bulb. Or it is because that one light bulb is really low dimmed. I have to test that further tomorrow. Only have one dimmable light bulb atm to test so I will dim the others tomorrow that working atm.
noNeedforAsig
Click to expand...
Click to collapse
I remember reading something weeks ago that the sensor doesn't work well with certain bulbs. I can't seem to locate the thread though.
No idea if its normal, but I keep hearing this strange noise, almost like the shutter is turning on or opening, whenever I open up an app that uses the camera. don't really see any actual performance issues, but it's a weird noise.
It is actually something that has been known to the s6. It is a hardware problem and so you should just return it for repair. I did last month so Sammy is fully aware.
I am running Honor 8 on Android 7.0.So when i switch to slow motion the video seems to be low light or gets dark.In natural day light even though it gets darker it still bright enough to see things but in artificial lighting or indoor condition the video gets too dark,Is this normal or only i am getting the issue here.
Hey guys
Do you experience also light sensor issues like wrong brightness in certain environments and the sensor is to slow in adjustment?
Yeah i do, mostly in the camera App. It always gets really dark for no reason.
Yeah, i've noticed this in low-light areas, the brightness goes back and forth a lot but mostly stays lower than expected
Light sensor in xperias is adaptive. If you think that your mobile got brightness wrong in a certain environment just correct it by using brightness slider. After couple of days and adjustments it will get every light situation right.
I find this approach to work better then with other brands even though it takes som time to get it just right
Thanks for all the answers. I can also confirm that the expected brightness is lower and after some days off correction the results are getting better.