Good day all,
I got my Z1 and updated to 4.4.2. Its a non rooted one. I have issues in camera. The camera preview itself flickers all time, even though pictures taken were clear. I tried clearing cache and data files, factory reseted too; didn't help !!! I Is there any way to overcome this bug?
Thanks!!
Reg,
Raj.
Not sure if this is what you mean, but I also have a lot of noise in the viewfinder/camera etc. (hard to describe exactly but sort of like watching analogue television not quite on the station correctly).. have never seen this on any other smartphone..
My phone is brand new.. seems to really only be a problem indoors/low light etc..
Does everyone have this? coming from an S3 its a bit off putting.
Flickers in camera preview
Yea exactly the same as you told. Is there any app or something to fix this ?? Does rooted phones also has this issue?
RajiveZ1 said:
Yea exactly the same as you told. Is there any app or something to fix this ?? Does rooted phones also has this issue?
Click to expand...
Click to collapse
There is no difference in Rooted or Not, this is related to the Update, one of many issues. I think there is no fix, just try different Rom, even stock.
Camera Preview not working
since lollipop my camera preview does not work. I can see the small thumbnail but it will not open
I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.
FunYunZ said:
I was wondering if anyone else had this issue with the front facing camera. There's a couple people that had this issue as well, check the
mentions for SamsungSupport on Twitter a couple days back(at the time of this post)
There's even a video of it in action: https://twitter.com/Hired_Assassin5/status/918633351510200320
As you can see at the top, there's some major discoloration going on. It's almost like a negative image.
https://i.imgur.com/2ipVzgS.jpg
I got the phone on Sep 15th, release day. The camera was working fine up until around Oct 5th that I know of. Taking selfies with the dog, etc.
Well, I opened it up on the 12th, haven't used it for a while, and I noticed that issue you see in the first image. I contacted Samsung and they had me
go through the whole troubleshooting process, all the way to me factory resetting my device. Factory Reset, then skipped all the setup wizards
and went straight to testing the camera. Issue is still present!
So the next day, I went to my carrier store, they said they never seen that before. So they're ordering me a shipment to replace it, possible defect.
Well, that night, I decided to try and look deeper into the issue. Flashlight on camera lenses, didn't see anything. Then I remembered from previous
android phones, there's hardware codes you can enter into the Dialer, so I input *#0*#, which is the hardware testing screen.
It looks like this:
https://i.imgur.com/RhJD4WJ.jpg
So obviously, one of the options is "FRONT CAM". I thought I would "test" it. I clicked on it, and it was working fine! I said oh sh!t, WTH.
This is the screenshot of it:
https://i.imgur.com/2BiaA7U.jpg
Then I took the picture as well, and it turned out just fine, like a normal camera. Well when you tap the screen again, it backs out, and switches
into a different mode, or something. And well sure enough, that issue I was having in my main camera app showed up!
This is a screenshot of it:
https://i.imgur.com/kGgJDD1.jpg
Now this is where I'm wondering if the Geniuses and good people here at XDA can figure out.
If you notice in the first screenshot of the "test" https://i.imgur.com/2BiaA7U.jpg
It says SUB AP at the top left....
Then in the next one, the defective one or whatever https://i.imgur.com/kGgJDD1.jpg
It says SUB CC.
Does anyone know what those are, or what they stand for? And if possible, how can I get my camera app to go back to using the correct mode or whatever that is.
This issue happens in all camera apps, the Samsung default camera app, play store camera apps, etc.
Thanks.
Click to expand...
Click to collapse
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?
lennie said:
I'm not having that issue *knocks on wood*
But it doesn't sound like a hardware issue though.
Sub AP, Sub CC are probably different Samsung settings not available to end users. Any advice I'd give is to back up, hard reset, test if problem still present, if problem fixed restore data.
When does the problem usually happen, in bright or low light?
What if you use the front camera "flash" does it still happen?
Click to expand...
Click to collapse
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?
FunYunZ said:
I originally thought it was a hardware issue, but seeing it function normally when I did the diagnostic testing, I knew it had to be
something that triggered the software to not work correctly.
the issue is still present no matter what settings I change. Changing resolution, flash on/off, picture size, HDR on/off/auto, all the settings
I can find, the issue is still exists.
EDIT: Is a hard rest the same as a Factory Reset?
Click to expand...
Click to collapse
hard reset = factory reset
have you tried using Odin and doing a fresh FW install?
htc-8925 said:
have you tried using Odin and doing a fresh FW install?
Click to expand...
Click to collapse
I have not. I did a factory reset.
My friend had the same issue.
whiteangelcl said:
My friend had the same issue.
Click to expand...
Click to collapse
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.
FunYunZ said:
Dam, that's unfortunate. That's 4 people now that have had this issue. I wonder how much worse it will get. Hopefully the new replacement doesn't have this issue.
It's weird because it was working fine for a few weeks, and then something happened. Not sure if it auto updated without me knowing and caused this issue.
Click to expand...
Click to collapse
sounds like they're sending you a replacement. make sure you are satisfied with the replacement because they might send you a refurb.
i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?
emazens said:
i have the same issue as well ... so what happened at the end ? did they end up finding the issue ? how they fixed it ?
Click to expand...
Click to collapse
Nope, Samsung never got back to me. I just went to the Tmobile store and they were like, yep, never seen that before. So they overnight me a new one.
I just begun to have the same issue on my phone and I'm not happy after spending 1k on it. I'm going to my career tomorrow but unfortunately don't know I this will be resolved. Please Let me know what Samsung did for you.
Same problem on my Note8. Following for solution.
solution anyone?
did anyone of u find a solution?
---------- Post added at 12:41 PM ---------- Previous post was at 12:38 PM ----------
i'm suffering with this problem presently and is trying to find a solve.
totaldepth said:
Same problem on my Note8. Following for solution.
Click to expand...
Click to collapse
i am seeing when i open camera ,camera failed
can anyone advise on how to fix?
If you did not mistreat the device, dropped it or fiddle with system settings or something of the sort, warranty is the all time solution for these problems
Hey my note 8 front camera just experienced the same issue. I've talked to Samsung support, and frankly it seems like it is a hardware issue. It is recommended that you use Samsung Support to make a service request. Free shipping both ways, so if you can live without your phone for a week or two (or have a backup phone to use), that's the route I recommend people going.
Original Problem:
MENU / COMMON APPLICATION ( NATIVE) - CAMERA / VIDEO - CAMERA EFFECTS NOT WORKING
Problem found:
FRONT CAMERA FAIL
Solution:
REPLACED COMPONENT
Click to expand...
Click to collapse
Did you manage to find the cause of the problem?
My front selfie camera has the same problem!
sorry to raise up this issue again.. my s8+ is from Indonesia region, and facing the same issue when try to use front camera is failed with notification Warning Unknown Error Occured.
already try Wipe cache partition and hard reset but still facing the same issue..
but if i use front camera for video call thru whatsapp it's working fine, but yet again if check thru *#0*# for Front Camera it's Camera Failed..
is it hardware issue or FW issue ?
Front Facing camera has double image
Has anyone found a fix for this issue yet? Mine started this issue last year and I haven't found a remedy for it yet. Ugh.
I am not much interested in camera when i bought Mi A2, it works fine. but recently when i was taking picture, it was half side blur and i was not able to make focus on upper side of camera. i tried all modes but no use. I have Note 6 Pro and it's camera functions and focus properly.
in mi A2 I observed when in MANUAL mode i select Lens as LOW LIGHT, it works (but in manual mode only).
do any one has some solution or give reason to behave camera like this.
Same here
It was a February patch bug and it seems to persist in March patch... Xiaomi.
pushpendrak said:
I am not much interested in camera when i bought Mi A2, it works fine. but recently when i was taking picture, it was half side blur and i was not able to make focus on upper side of camera. i tried all modes but no use. I have Note 6 Pro and it's camera functions and focus properly.
in mi A2 I observed when in MANUAL mode i select Lens as LOW LIGHT, it works (but in manual mode only).
do any one has some solution or give reason to behave camera like this.
Click to expand...
Click to collapse
This is a hardware problem, I also had this, give the phone a guarantee.
P.S. sorry for english(
How so we both have exactly the same problem and mine started with pie?
Looks like this is a hardware issue, I'm having the same problem after 4 months of use.
Same here, I also took it to guarantee and they told me it was a software problem, but when they gave it back to me nothing had changed. Camera still not working
nachocattoni said:
Same here, I also took it to guarantee and they told me it was a software problem, but when they gave it back to me nothing had changed. Camera still not working
Click to expand...
Click to collapse
I had to order a new camera module, I'm still waiting to arrive to replace it..
osvaldo.17 said:
I had to order a new camera module, I'm still waiting to arrive to replace it..
Click to expand...
Click to collapse
Please let us know if this fixes it. I have this problem too and I'm thinking about ordering a new camera module.
Ulver said:
Please let us know if this fixes it. I have this problem too and I'm thinking about ordering a new camera module.
Click to expand...
Click to collapse
I had ordered it from this website but I had paid the cheapest shipping, I'm from Mexico so it will take a while to arrive to my country.. maybe next month..
I had the same problem and replaced the camera module with a new one, and the problem was fixed... temporarily because 3 months after it started happening again with the new camera, so either I am super unlucky, or it must be some other defect in the phone that tends to breaks the primaey cameras...
At this point I don't think I am going to replace it again. Do you know of any way of recording videos with the low light camera?
I have the same issue. In fact this issue persists in the video mode as well. Its okay for videos of objects nearby but move even a few metres away and it becomes very difficult to focus. I was at this concert and wanted to record the performance but only got a very blurry video with muffled sound. For photos this issue is especially an inconvenience when taking photographs of documents etc where you could very well do without the unnecessary bokeh effect. In MANUAL mode this does reduce a bit, but not to any extent that helps.
I was just told by a friend that installing the Google camera mod might help, but I'm yet to try it out.
I have same problem with upper side blur. Seems that switching to "manual" mode and change "lens" from "regular" to "low light", as said by the original user. It works fine with me. Thanks for the tips ! ........ so it is not the hardware problem, it is a software problem. Changing camera may not work ! Don't know if they are going to release new firmware to solve it or not ?? Any idea how to upgrade the firmware ?
JTSin said:
I have same problem with upper side blur. Seems that switching to "manual" mode and change "lens" from "regular" to "low light", as said by the original user. It works fine with me. Thanks for the tips ! ........ so it is not the hardware problem, it is a software problem. Changing camera may not work ! Don't know if they are going to release new firmware to solve it or not ?? Any idea how to upgrade the firmware ?
Click to expand...
Click to collapse
If it is a hardware problem I do not see why it would prevent using the secondary camera, it can be a problem with the lenses (Have you thrown or hit your phone?) and not with the module. There are those who have returned to Oreo and the problem persists.