Question 1.1.4 Update Made the Main Camera WORSE... - Nothing Phone 1

I mentioned this in another thread but I feel it deserves its own thread. Until 1.1.4 hit, I was really enjoying the cameras on the Nothing phone. But they really mucked up the main camera after the update. They brightened up the image and the HDR is worse now as well. Others have mentioned it in the 1.1.4 thread, and there are even more who have mentioned it in the Nothing Phone reddit forum.
I have a standard pic I take to test my smartphone cameras. It's a great picture to test the exposure and dynamic range. I take a picture of my fireplace from inside my family room. To either side of my fireplace are windows where you can see blue sky and the back yard. On 1.1.3 the pictures were BEAUTIFUL. The inside of the family room was properly exposed and the brilliant blue sky and back yard could be seen thru the windows. Now after the update to 1.1.4 the family room is too bright/overexposed and the back yard and blue sky thru the windows are totally washed out. You can barely make out the blue in the sky or any back yard detail. HDR is wonky now. This SUCKS. I left feedback on the Nothing feedback form. Hopefully they fix it.

So just yo be clear, only the HDR algorithm was affected? If it's off, is there a difference?

Same here.Washed .Oversaturated noise oversahrpened.

" If it's off, is there a difference?"
No options on/off full automatic.

Have to reported to developers?

miris83 said:
Have to reported to developers?
Click to expand...
Click to collapse
He has done so already and so should everyone else

Nyssa1104 said:
He has done so already and so should everyone else
Click to expand...
Click to collapse
Sorry, there should have been "Have you", not "Have to". I also report bugs if there is no solution in here or anywhere else but I also know the majority usually starts here and waits for someone else's reports. As I have not received the update yet, I cannot give any feedback on this.

miris83 said:
Sorry, there should have been "Have you", not "Have to". I also report bugs if there is no solution in here or anywhere else but I also know the majority usually starts here and waits for someone else's reports. As I have not received the update yet, I cannot give any feedback on this.
Click to expand...
Click to collapse
Yes I reported to the Nothing via their official feedback form located here:
Issues and New Features Form
Please fill in this form to report issues and suggest new features.
forms.gle

Related

Weird camera colour balance?

After taking a few pictures outside today, it seems the colour balance is completely shot on my HD2.
The effect is especially evident if you view the photos as thumbnails - there's a huge band of red in the centre of the photos.
I've attached a couple of examples, resized to VGA.
Has anyone else noticed a similar effect?
UPDATE: 22/11/2009 - numerous members are affected by this problem, see List of members with / without this problem here - post 138 in this thread
UPDATE: 10/12/2009 - HTC official hot fix available here:
http://www.htc.com/europe/supportdownloadlist.aspx?p_id=297&act=sd&cat=all
This occasionally happened to X1 photos. And it was because lens cover coating of the lens wore off. It was rather visible if you looked at the lens cover. Could be just dirty, too.
Yes, it is a common known problem of the hd2 camera.
can be moisture/glitch in white-balance (Very noticeable during video recording). I don't expect to get great results with this camera... so it doesn't really bother me.
to solve this issue change the auto white balance to outdoors not setting after auto, u will find this is best all round as i have after doing existence camera testing thought the day, i have some sample pics i took today ill add them once phones charged
DAMIEN123_666 said:
to solve this issue change the auto white balance to outdoors not setting after auto, u will find this is best all round as i have after doing existence camera testing thought the day, i have some sample pics i took today ill add them once phones charged
Click to expand...
Click to collapse
same here outdoor delivers the best balance
Thanks for the replies guys. I'm pretty sure I was using 'outdoor' white balance in the photos above. Quite a few of the leo photos I've seen now have the red blotch in the middle to a greater or lesser extent.
I need to do a bit more testing.. just need some sun first!
The red splodge in the centre of pictures is quite shocking really!
Here's a picure of a plain wall which clearly shows the problem, the other picture has had the levels adjusted to highlight the problem even more
have you guys been in contact with HTC? i know i will if my phone turns out like that to.. power of the people!
Have you tried lowering the ISO sensitivity?... this looks like a defective ccd, rather than just wrong white-balance setting.
Fatherboard said:
Have you tried lowering the ISO sensitivity?... this looks like a defective ccd, rather than just wrong white-balance setting.
Click to expand...
Click to collapse
OMG, it gets worse
First pic is from a Diamond 2, ISO manually set to 100 and Fluorescent colour balance. The second shot is exactly the same settings on the HD2 !!!!
br3nt said:
have you guys been in contact with HTC? i know i will if my phone turns out like that to.. power of the people!
Click to expand...
Click to collapse
I've just sent off a report with a link to this topic to HTC.
'If/When' I receive a reply I'll let you know.
Beards said:
I've just sent off a report with a link to this topic to HTC.
'If/When' I receive a reply I'll let you know.
Click to expand...
Click to collapse
Nice one
My HD2 doesn't do this. All the pictures I've taken so far were just fine.
Last thing to try (under fluorescent lighting) - if there's a "FLICKER/FLICKERING" setting, try to play with it.
European devices should be set to 50Hz, In America/Asia - 60Hz.
maati said:
My HD2 doesn't do this. All the pictures I've taken so far were just fine.
Click to expand...
Click to collapse
1. Any possibility in passing on what settings you are using so that we all can further discuss this.
2. Have you tried pointing the camera at the ceiling indoors (or a large white space) and taking a shot. Is the shot clean and what colour does it show?
Fatherboard said:
Last thing to try (under fluorescent lighting) - if there's a "FLICKER/FLICKERING" setting, try to play with it.
European devices should be set to 50Hz, In America/Asia - 60Hz.
Click to expand...
Click to collapse
Yes, I've tried both 50Hz & 60Hz but both submit the same result.
GSMARENA.com have confirmed that too - http://www.gsmarena.com/htc_htd2-review-418p9.php
try these guys...
camera and camera dll from the 148 rom
Beards said:
I've just sent off a report with a link to this topic to HTC.
'If/When' I receive a reply I'll let you know.
Click to expand...
Click to collapse
Okay.... I have now received a reply back from HTC.
The content of their reply is as follows:-
Dear valued HTC customer, Thank you for contacting our Customer Support Center. We are dedicated to providing you with the best quality service and answering all of your questions and concerns. This could be a driver conflict and we recommend to try a hard reset on it make sure that you back up all your data before the reset. If the problem still going on after this then contact us and we will send your device to be repaired or returned this device to the re-seller and exchange fo another one. If these steps have not helped, please let me know by responding using the link provided and I will be happy to check again for you. Best regards, HTC customer support team HTC Corp. Global Service Division http://www.htc.com/europe/CA_Hotline.aspx Call Center at: 44-120-271-4530 if you have further questions.
--------------------------------------------------
My reply back to this read as follows:-
Dear Support,
This is not a driver conflict issue and a hard reset is not going to cure this problem.
It is either a generic hardware fault that is effecting countless HD2's or a software error.
This will either have to be addressed as a recall of all machines exhibiting the problem or a ROM patch.
Regardless, this problem is now being reported not just by me but by other sites as well ~ including the site I mentioned in my initial message to you which again can be found at:- http://forum.xda-developers.com/showthread.php?p=4969313#post4969313
Thanking you.
--------------------------------------------------
I'll continue to keep you all updates as and when further material is sent to me.
Note:
In the meantime; I shall be in Theatre all day today and will be away from my computer for the next 15hrs.
I will re-log on tonight at midnight GMT and check for any replies from HTC.
Beards
Has anyone tried fards's solution?...

trackball colors *Post 108*

Can you change the trackball colors on the nexus one?
Mod Edit:
Per lilHermit:
OK I've moved the initial su request to before the main screen is drawn to see if that helps.
lilHermit
Click to expand...
Click to collapse
Apk:
TrackballColoursConcept.zip
Yup, this, too, was one of the big surprises for me today when I got mine. I use and love several apps that flash the notification LED different/custom colours, but on the Nex1, the only colour I get is white.
I'm really, really, hoping that OS2.1 just changed the API and that updated apps will be able to do colours. I'm really, really scared that they cheaped out and put a white LED behind the trackball. >.<
][
People are saying that when Bluetooth is paired is flashes blue.
I heard when you have voicemail it flashes red. I haven't tried any of them yet though so I wouldn't know.
its a tri color led so it CAN do any color its just a matter of the third party apps adapting to be able to control it, cant wait
White, red, blue....
Anyone else wish they had green?
Though it was very patriotic of HTC.
AndroTMO said:
Anyone else wish they had green?
Click to expand...
Click to collapse
all colors can be reproduced... just depends on the software that lights up the ball.
indeed it can be changed
unfortunately it stops working after a notification is fired...
Install NotifyLight from XDA:
http://forum.xda-developers.com/showthread.php?t=575024
then set up the pulselight on and change the values in:
/sys/devices/platform/i2c-adapter/i2c-0/0-0066/leds/jogball-backlight/color
ie:
Code:
adb shell echo "255 0 0" > /sys/devices/platform/i2c-adapter/i2c-0/0-0066/leds/jogball-backlight/color
this will give you a nice red jogball.
"255 0 0" is in RGB format.
And off course you need root for this to work...
AndroTMO said:
White, red, blue....
Click to expand...
Click to collapse
When white, it is actually the red, green, and blue all on at the same time.
Would love to see an app to configure all sorts of different notification colors for missed calls, texts, emails, etc, and the blink frequency.
Btw.. MissedCall works, but it can't change the colors.
Once the SDK drops for 2.1 and Nexus One codes and such are released, we should have notifications fixed and custom notifications.
http://twitter.com/missed_Call
I have to say that Google disabled multicolor LED notifications on the Nexus One! (the hardware can do them) #missedCall #NexusOne #fail
xManMythLegend said:
http://twitter.com/missed_Call
I have to say that Google disabled multicolor LED notifications on the Nexus One! (the hardware can do them) #missedCall #NexusOne #fail
Click to expand...
Click to collapse
I can't even to express how disappointed I am at this news. Multicolored notifications was one of the most useful features for me...
cliffy15 said:
I can't even to express how disappointed I am at this news. Multicolored notifications was one of the most useful features for me...
Click to expand...
Click to collapse
As are others. Seriously pissed.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=0493493845dff4e4&hl=en
From all this drama going on, I'm gonna assume this guy has noooo idea what he is talking about:
Or what o_0
... and seriously over reacting.
Eclair~ said:
From all this drama going on, I'm gonna assume this guy has no idea what he is talking about:
Or what o_0
Click to expand...
Click to collapse
Well, it's unlikely that there are 3 led's in there, just one tri-colour.
I've just installed the NotifyLight application and echo'd values to is and it works fine.
People are seriously over reacting, suggesting that this is a deliberate move by google - get a grip, it's probably an oversight. I agree that it's very useful to have but I'm not throwing my toys out of my pram over it.
SC
ScaredyCat said:
Well, it's unlikely that there are 3 led's in there, just one tri-colour.
I've just installed the NotifyLight application and echo'd values to is and it works fine.
People are seriously over reacting, suggesting that this is a deliberate move by google - get a grip, it's probably an oversight. I agree that it's very useful to have but I'm not throwing my toys out of my pram over it.
SC
Click to expand...
Click to collapse
Every sign including feedback from one of the most popular notification apps Devs points to it not working.
If all of a sudden custom ringtones and contact pictures were removed you'd see the same reaction.
Google already closes off the ability to add codecs or EQ bands.
Considering how many apps took advantage of this I dont see why peoples reactions arent justified. You dont pay 500+ for something to lose functionality.
xManMythLegend said:
Every sign including feedback from one of the most popular notification apps Devs points to it not working.
If all of a sudden custom ringtones and contact pictures were removed you'd see the same reaction.
Google already closes off the ability to add codecs or EQ bands.
Considering how many apps took advantage of this I dont see why peoples reactions arent justified. You dont pay 500+ for something to lose functionality.
Click to expand...
Click to collapse
I'm not saying it's not, not working (without rooting). I'm suggesting that the mechanism (API and underlying implementation) has simply changed and it's an oversight. Looking at the link you provided earlier there was mention that the notification API hasn't changed in a long time.
"The SDK hasn't change in terms of Notifications since SDK version 1."
Perhaps that's the reason it's not working, perhaps the API needs an update rather that being deliberately disabled as that poster went on to say.
"Google just disabled that feature in Android 2.1."
That's simply an unsubstantiated claim by someone on the internet.
People are suggesting that this was a deliberate move by google to close off Android bit by bit. Perhaps waiting until we get some sort of response rather than flying off at the deep end is the best course of action.
2.1 is a new release and the Nexus One is a new device. That's what you paid for. You're an early adopter and really should understand that things might not be perfect in the first instance.
Since you're a senior member of the forum and by implication have been in here for a while and have obviously had more than one android phone, I'm a little surprised and your outrage.
SC
ScaredyCat said:
I'm not saying it's not, not working (without rooting). I'm suggesting that the mechanism (API and underlying implementation) has simply changed and it's an oversight. Looking at the link you provided earlier there was mention that the notification API hasn't changed in a long time.
"The SDK hasn't change in terms of Notifications since SDK version 1."
Perhaps that's the reason it's not working, perhaps the API needs an update rather that being deliberately disabled as that poster went on to say.
"Google just disabled that feature in Android 2.1."
That's simply an unsubstantiated claim by someone on the internet.
People are suggesting that this was a deliberate move by google to close off Android bit by bit. Perhaps waiting until we get some sort of response rather than flying off at the deep end is the best course of action.
2.1 is a new release and the Nexus One is a new device. That's what you paid for. You're an early adopter and really should understand that things might not be perfect in the first instance.
Since you're a senior member of the forum and by implication have been in here for a while and have obviously had more than one android phone, I'm a little surprised and your outrage.
SC
Click to expand...
Click to collapse
In and of itself youre 100% right.
But in context with every thing that has been coming out in the last week there could be much more to it.
For all I know there could be something N1 isnt capable of long term that these types of notifications may exploit.
Via Twitter and another via Email Ive seen 2 devs of notification apps confirm that the LED lights and patterns cant be manipulated.
Sure it can be an oversight or just some hitch. Perhaps Im giving these devs too much credit.But its the sqeauky hinge that gets the oil. While it may annoy other posters theres simply no better means than to continually raise a ruckus. Im not up in arms saying screw google F the nexus. Just being adamant about displeasure.
The only way any of us can expect a response is by having these conversations.
The 3g/edge issue doesnt seem to effect me but if its there a stink should be raised.
Frankly if a fix came out tomorrow for the rooted community and never by google Id be just as annoyed. I want the OS to move forward not backwards.

Possible Nexus Camera "Issue"

So I like most everything about my nexus but the way it takes pictures. Its not so much a real issue because it doesn't prevent the camera from working.. but it seems the chip/sensor they used for the camera gives a red spot in all pictures in the center of the image, most noticeably in pictures with a white or light background/image. I'll attach a picture so everyone else can confirm what I mean... I was hoping we could get HTC to replace the phones that have this issue via the warranty as this seems to be an issue with many nexus ones (based on a couple of reviews and the pictures they provided there). Here's my sample picture. You can also see it on screen when looking at what you're going to take a picture of.
Also I do research in a lab and its a procedure for an experiment I'm doing... just realized what I was posting might seem odd... didn't really read it before posting.
It is a software issue, so they are not going to do a warranty replacement. Droid had the same deal with it, seems to be something with the base 2.0/1 Android framework, I am sure it will be fixed when google releases their bug fix update(don't ask when, no legit idea beyond guessing sometime around the start of February, since that seems to be the typical timeline with phone bug updates, about 30 days after launch the first update is released).
Correction. It's a HARDWARE issue. Dont believe me? leave your cammera on for a couple minutes.. Goes away right? Its cuz droid camera was the same.. or similar? They had a bad batch. Mine has no pink eye(N1) =>
The Droid's issue was partially a software problem...
http://www.engadget.com/2009/11/17/motorola-droid-camera-autofocus-fixed-in-secrecy/
As well, it is a "who really knows?"
http://wmpoweruser.com/?p=10749
It seems many phones, with different camera's and so forth are having this issue... CCD seems to be the manufacturer of all the sensors, though, so perhaps there is a problem with the firmware from CCD causing this?
I highly doubt that every single camera sensor ever made by this company happens to have this sort of issue due to hardware. That would be pretty insane! However, if it was a firmware issue, then it would be present in every handset that uses a CCD manufactured/firmware supported camera, and this seems to be the case.
As well, it has already been stated the HD2 will get an update that fixes it. Hopefully the Nexus One is in the same boat. I didn't notice it on the test unit I used, but I asked the current tester if it was happening, and on all 3 it is present. It isn't noticeable in most pictures, though, especially with the flash on, FXcamera set to the proper white balance, and so forth.
EVERY Nexus One you get will have this issue. IT IS SOFTWARE. My N1 has it, the replacement I got has it too.
I've just taken a load of pictures and no pink from what I can see with both flash on and off.
Took pictures of a white surface and no pink. Must be hardware.
EDIT: http://picasaweb.google.com/lh/phot...authkey=Gv1sRgCNKM3fOF452TyQE&feat=directlink
http://picasaweb.google.com/lh/phot...authkey=Gv1sRgCNKM3fOF452TyQE&feat=directlink
Do you have any camera apps installed? FXcamera with proper white balance settings(sometimes auto is perfect, sometimes you have to do it manually) makes it go away a lot of the time too.
Eh Hem.. Guys are you all forgetting that my N1 DOES NOT HAVE PINK EYE
From what I understand this is a hardware issue. This was also present in an earlier HTC phone (I think the HD2) running a different OS altogether.
yes this was a widespread issue on the HD2... and it was completley fixed by a SOFTWARE UPDATE! >.<
A cursory search of the words "hd2 pink camera issue" on Google seems to imply that this is actually a hardware issue.
Edit: The source of the confusion http://www.redmondpie.com/fix-pink-camera-problem-on-htc-hd2-9140202/:
HTC first confirmed it as an hardware issue but then later they found out that it was infact a software issue, rather than a hardware one.
Click to expand...
Click to collapse
http://www.gsmarena.com/a_hardware_fault_causes_htc_hd2_*pink*_camera_issues_confirmed-news-1276.php
I believe the SOFTWARE update is just overcorrecting the blue/green settings on the center of the camera (Guess...) to cancel out the HARDWARE problem with YOUR camera. But again.. It is a Hardware issue for sure. Sorry guys xD I win!
I wouldnt trust htc if you ask them though.. I dont think they are certain what planet they are on half the time.. I asked about how they know that I unlocked my bootloader and his answer was basically.. voodoo. Soooo yaaahhhh... Notice that the cameras are the same for droid HD2 and Nexus one? and those are the only 3 with the issue? Not the G1 with ported software? => hardware folks
flamerider88 said:
I wouldnt trust htc if you ask them though.. I dont think they are certain what planet they are on half the time.. I asked about how they know that I unlocked my bootloader and his answer was basically.. voodoo.
Click to expand...
Click to collapse
You asked someone in support; customer support for any company is always uninformed. These aren't the people making press releases or even official forum posts.
flamerider88 said:
I believe the SOFTWARE update is just overcorrecting the blue/green settings on the center of the camera...
Click to expand...
Click to collapse
I agree, just because the manufacturer releases a software fix doesn't mean its a software problem to begin with.
The first day I had the phone, I really noticed the pink spot. Yesterday I took 30 pictures, I didn't notice it at all. Today If I look hard enough I think I see a little tiny pink, viewing the image of a white piece of paper in the same place (office) I first tested the camera.
Yeah I noticed this too. It only really shows up if I take pictures of white paper or a white wall. Every other normal pic I take turns out fine but I do hope they can fix it with a software update... wouldn't be too hard.
dinan said:
Yeah I noticed this too. It only really shows up if I take pictures of white paper or a white wall. Every other normal pic I take turns out fine but I do hope they can fix it with a software update... wouldn't be too hard.
Click to expand...
Click to collapse
My n1 has it too. Ive tried it now in room with room light and it gives this violett spot when i tak a picture with automatic colorbalance, if i put room light as colorbalance there is no spot...
google already knows about that issue and a fix will be released!
"I have great news! The issue has been fixed and should be included in the next update to Android. I say "should" because things can change at the last minute. Keep an eye on your notification bar for a system update."
source: http://www.google.com/support/forum/p/android/thread?tid=7a22ebb69da2b253&hl=en#all
navahoo said:
google already knows about that issue and a fix will be released!
"I have great news! The issue has been fixed and should be included in the next update to Android. I say "should" because things can change at the last minute. Keep an eye on your notification bar for a system update."
source: http://www.google.com/support/forum/p/android/thread?tid=7a22ebb69da2b253&hl=en#all
Click to expand...
Click to collapse
I followed the link, but didn't see the response you quoted...?
flarbear said:
I followed the link, but didn't see the response you quoted...?
Click to expand...
Click to collapse
That's because it was removed by Google. I read it this afternoon. Is not there any longer. The Google employee was "Tommy" and you can't find his posts any more.
You can read other people's response to his post but his don't show up any longer.
well, that post is very hopeful. i suppose all we can do is hope for the best. i dont know if google deleting the post is good or bad though

Camera update adds Moto 360 support

The Moto X phone just received a camera update which allows the Moto 360(smart watch) to take a picture. When you open the camera on the phone the app on the watch also activates. You can then tap the screen on the watch and the phone will count down a few seconds and take a picture. After the picture is taken it appears on the watch face.
Not sure it is super useful but I guess if you prop your phone up and take group shots you can now do it remotely and also verify the pic is ok(albeit in very tiny form on the 360 screen)
It is nice to see Motorola continues to add features.
Steve-x said:
The Moto X phone just received a camera update which allows the Moto 360(smart watch) to take a picture. When you open the camera on the phone the app on the watch also activates. You can then tap the screen on the watch and the phone will count down a few seconds and take a picture. After the picture is taken it appears on the watch face.
Not sure it is super useful but I guess if you prop your phone up and take group shots you can now do it remotely and also verify the pic is ok(albeit in very tiny form on the 360 screen)
It is nice to see Motorola continues to add features.
Click to expand...
Click to collapse
It says performance improvements, too - we can only hope!!!!
There is no point if they keep adding features if not fix the problems that are currently with the camera and flash on android 4.4.4.
Apparently remains the same and the photos remain obscure disaster ...
http://forum.xda-developers.com/moto-x/moto-x-qa/white-photos-flash-update-to-4-4-4-t2895048
emmanueldmc said:
There is no point if they keep adding features if not fix the problems that are currently with the camera and flash on android 4.4.4.
Apparently remains the same and the photos remain obscure disaster ...
http://forum.xda-developers.com/moto-x/moto-x-qa/white-photos-flash-update-to-4-4-4-t2895048
Click to expand...
Click to collapse
Not everyone has your issue though. Who knows how many out there do. It could be a very small percentage and therefore unnoticed by Motorola.
My wife's X on 4.4.4 is fine. Nearly as good as my M8 anyway.
Though both don't compare to my $120 Kodak camera. Lol
KJ said:
Not everyone has your issue though. Who knows how many out there do. It could be a very small percentage and therefore unnoticed by Motorola.
My wife's X on 4.4.4 is fine. Nearly as good as my M8 anyway.
Though both don't compare to my $120 Kodak camera. Lol
Click to expand...
Click to collapse
I'm not the only one with this problem, in fact I have been participating in many forums about this, and apparently is something unified in the upgrade to 4.4.4
emmanueldmc said:
I'm not the only one with this problem, in fact I have been participating in many forums about this, and apparently is something unified in the upgrade to 4.4.4
Click to expand...
Click to collapse
I know your not the only one. But no, its not "unified"....as many, myself included, do not have the issue. ?
emmanueldmc said:
I'm not the only one with this problem, in fact I have been participating in many forums about this, and apparently is something unified in the upgrade to 4.4.4
Click to expand...
Click to collapse
I think my camera has always been bad in low light no matter what the version.
I think all 444 cams are bad. My Maxx too.
Any with good no ambient light pics w/flash? Please chime in.
Go in a totally dark room, set flash to always, shoot something, post a good pic, please!
aviwdoowks said:
Go in a totally dark room, set flash to always, shoot something, post a good pic, please!
Click to expand...
Click to collapse
Can any phone cameras do well in a totally dark room?!?!?!!?!?!?
Wansanta said:
Can any phone cameras do well in a totally dark room?!?!?!!?!?!?
Click to expand...
Click to collapse
With the flash it should not be over exposed, at least.
aviwdoowks said:
With the flash it should not be over exposed, at least.
Click to expand...
Click to collapse
I understand Motorola is not the best manufacturer of cameras for mobile phones, but if this is a mistake, since before 4.4.2 did not happen.
The first photo was taken with Moto X, the second with a galaxy S3 with no light in the room, only the flash.
? I much prefer the first pic. Taking pics of real people is a drag when its too dark like pic 2.
Guess everyone is different . ?
---------- Post added at 02:39 PM ---------- Previous post was at 02:38 PM ----------
Plus the flash on the white is obviously reflecting the light back.

Front camera blurry

Having issues with front camera taking blurry pictures . Anyone having same issues. Please suggest possible solutions ?
Sent from my iPad using Tapatalk
note4 guy said:
Having issues with front camera taking blurry pictures . Anyone having same issues. Please suggest possible solutions ?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
First thing first. Check if it is an external or internal issue. To check if it is external, take a closer look to the camera (if possible with a zoom ?) and if you see the lens is foggy or some moist inside there, then you will have to open it. To check if is internal, install 2 or 3 other cameras that work with selfies and see if it is blurry too.
Could you post an example?
CHH2 said:
Could you post an example?
Click to expand...
Click to collapse
1st, if you want someone to answer to you, you must click on the reply button. otherwise, that person might never know that you are asking him something.
Now, this is a picture of how more or less a foggy/moist lens would look like (like fog accumulating on the interior).If you take a close look and you dont see anything abnormal, then it is more likely to be something inernal (software related) but in order to see whether is that too then, you might want to install several camera apps and try each one. if none of the show a blurry image, then it is software related. if all of them show you the same result then ... it might be external and you would have to open the phone.
jinkerz9430 said:
1st, if you want someone to answer to you, you must click on the reply button. otherwise, that person might never know that you are asking him something.
Now, this is a picture of how more or less a foggy/moist lens would look like (like fog accumulating on the interior).If you take a close look and you dont see anything abnormal, then it is more likely to be something inernal (software related) but in order to see whether is that too then, you might want to install several camera apps and try each one. if none of the show a blurry image, then it is software related. if all but if all of them you the same result then ... it might be external and you will have to open the phone.
Click to expand...
Click to collapse
A) If the OP is serious about this thread, they'll come back and actually check it and see my request. If they need me to hit the reply button, that's just lazy and not giving a care. If they don't care, I don't care.
B) If you meant to attach a photo, you forgot to.
C) I'm not really interested in seeing what you have, I'm here to help the OP. I've been doing photography for over 30 years now. I pretty much have seen it all. Not sure why you think I want to see what you have since you are not the OP.
CHH2 said:
A) If the OP is serious about this thread, they'll come back and actually check it and see my request. If they need me to hit the reply button, that's just lazy and not giving a care. If they don't care, I don't care.
B) If you meant to attach a photo, you forgot to.
C) I'm not really interested in seeing what you have, I'm here to help the OP. I've been doing photography for over 30 years now. I pretty much have seen it all. Not sure why you think I want to see what you have since you are not the OP.
Click to expand...
Click to collapse
This is what i mean.
https://www.google.com/search?q=fog...AUIBygB&biw=424&bih=632#imgrc=A7--V8Kg202lBM:
And to be honest. If you want s fast response then the usual approach is a reply.
Seems like you took my comment the wrong way. i dont know why since it is just a suggestion which make sense (didnt they created the reply button for that reason?) . Also, you are talking to someone who had that same issue. Maybe not with this phone but with the samsung galaxy s5.
jinkerz9430 said:
This is what i mean.
https://www.google.com/search?q=fog...AUIBygB&biw=424&bih=632#imgrc=A7--V8Kg202lBM:
And to be honest. If you want s fast response then the usual approach is a reply.
Seems like you took my comment the wrong way. i dont know why since it is just a suggestion which make sense (didnt they created the reply button for that reason?) . Also, you are talking to someone who had that same issue. Maybe not with this phone but with the samsung galaxy s5.
Click to expand...
Click to collapse
Er, the OP started the thread and commented about blurry photos, what made you assume the thread was suddenly about you?
And there's about a million different reasons for photos to come out blurry which is why it is best to ask for examples instead of jumping on a solution that is probably somewhere at the bottom of the list out of possible reasons first. Makes complete sense that I was talking to the OP if you're actually here to help the OP.
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
note4 guy said:
Having issues with front camera taking blurry pictures . Anyone having same issues. Please suggest possible solutions ?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Since someone else seemed to hijack, I'll need examples please.
CHH2 said:
Er, the OP started the thread and commented about blurry photos, what made you assume the thread was suddenly about you?
And there's about a million different reasons for photos to come out blurry which is why it is best to ask for examples instead of jumping on a solution that is probably somewhere at the bottom of the list out of possible reasons first. Makes complete sense that I was talking to the OP if you're actually here to help the OP.
---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------
Since someone else seemed to hijack, I'll need examples please.
Click to expand...
Click to collapse
Ah. nevermind I thought I was talking to the OP but now i figured out i was talking with someone else.
Do you know what a hierarchy chart by any chance? (dont go taking this question the wrong way now)
Yes, I know what a hierarchy chart is but I fail to see how that solves the OP's issue without the OP coming back and giving us examples of his/her blurry photos.
To get back on track, and yes this is almost pointless without samples of the blurry pics, my front camera seems to "smooth" selfie pics as if to make them seem better. They look, to me, like they have been processed to look "better"--like some people often do on Facebook to pics of themselves, particularly if they are above a "certain age."
Mike
jinkerz9430 said:
First thing first. Check if it is an external or internal issue. To check if it is external, take a closer look to the camera (if possible with a zoom [emoji361]) and if you see the lens is foggy or some moist inside there, then you will have to open it. To check if is internal, install 2 or 3 other cameras that work with selfies and see if it is blurry too.
Click to expand...
Click to collapse
Thanks for all the suggestions. It turns out lens had collected dust under the screen protector. I took some pics without screen proctor they came out just fine. I am sorry to reply so late due to hectic work schedule. Truly appreciate the advice. I didn't mean to post a question and disappear.
Sent from my iPad using Tapatalk
Just bought the V20 and I've got to say how disappointed I am with the front camera, particularly auto mode. It's almost impossible to take a picture that isn't blurry. The only way to get a decent picture is to switch to manual mode and increase shutter speed. Once you toggle between shutter speed and iso, you can capture really decent pictures. Where this causes problems is when you need to snap a picture really quickly and don't have time to sit and adjust settings. I'll probably return this phone and go for a Samsung. At least I know I'll get great pictures. Very disappointing.
the front camera sucks because of the focus, that's why mines blurry anyway. it's like infinity focus so anything closeup, like a selfie, is not sharp. the galaxy s7 was the same way.. the ffc was garbage on it bc of this. weird, bc my note 4 ffc was 10x better than both and that phones 3 years old lol
Sent from my LG-US996 using Tapatalk
jayochs said:
the front camera sucks because of the focus, that's why mines blurry anyway. it's like infinity focus so anything closeup, like a selfie, is not sharp. the galaxy s7 was the same way.. the ffc was garbage on it bc of this. weird, bc my note 4 ffc was 10x better than both and that phones 3 years old lol
Click to expand...
Click to collapse
I think it has something to do with with the stupid beauty filter on the front cam for selfies. Even if you turn it down to 0 it still looks like it's applying a smoothing effect and there is no way to turn it off as far as I know.
Just doing a comparison shot in another camera app like the Google camera I can tell a difference in the detail of my skin. The Google camera sucks because there is too much noise overall but I can actually see the individual hairs on my beard whereas on the LG one with the beauty thing turned to 0 it still looks like a smoothed out mish mash

Resources