Related
I know that there are topics made about this issue. I'm wondering though how many of you actually have it. The main culprit from my research seems to be that the OTA has some bugs that is making the Camera go on the fritz.
If this indeed is true, then would another OTA fix it? My return date is tomorrow so I have some time to think before I exchange it for a fresh new one. If it indeed is a OTA issue, then I don't want to exchange it since I have applied a nice screen protector.
i doubt its the ota. i took all of the ota so far. i have no issue with camera.
Really? That's disheartening..
I googled "evo 3d camera freeze" and many, many people held discussions in other forums about their camera freezes. A lot of them also pointed out that they didn't have the problem until after installing the OTAs.
I really don't know what to do.
There are other threads on this but the bottom line is that the camera software is buggy and yes, it freezes a lot. I can't say anything about prior OTA's but I am confident that future OTA's will fix the camera bugs because they all appear to be software to me.
Mike
Thanks. I think I'll just keep the phone.
Worst comes to worst, I'll still be covered under HTC's warranty and can schedule a free repair with them. Sure I'll be phoneless but it's better than exchanging a otherwise perfectly functional phone and risking getting a phone that's worse.
Same here I have that problem to and I have latest ota. Hopefully this gets fixed.
Sent from my PG86100 using Tapatalk
mikeyxda said:
There are other threads on this but the bottom line is that the camera software is buggy and yes, it freezes a lot. I can't say anything about prior OTA's but I am confident that future OTA's will fix the camera bugs because they all appear to be software to me.
Mike
Click to expand...
Click to collapse
The other thing that I like to point out is..
Why isn't this a bigger issue than it is? Is it mainly because, those who don't have this issue did NOT take the OTAs? I know that everyone is waiting for root so most people on here probably did not take the OTA to ensure full root functionality. I mean that's assuming the main factor for freezing is from the OTAs (which some lucky ones who did install the OTA didn't get this issue like the above.).
I don't know. I just feel like this issue isn't widespread for HTC to notice. :/
My camera is extremely buggy. I did the OTA so that I could see the Green Hornet (Which never worked for me :'( Only option is to buy it) and now my camera is all but totally worthless it locks up so bad
It doesn't seem to concern htc as they contacted me back through email that they currently aren't experiencing any camera issues... Lies.... So the only remedy they offered me was to factory reset... Done that twice.. Or to take it to a repair center. But I believe this is a software issue.
Sent from my PG86100 using Tapatalk
This is a huge issue for me and it's getting worse. Its got to the point now I have to turn the phone off and sometimes even pull the battery. At first it was simply kill the camera and try to open it. After opening it about 7 times it would work. I'm going to start looking in to this further as it has gotten out of control. I'll post back here if I find anything worth sharing.
alanmv567 said:
It doesn't seem to concern htc as they contacted me back through email that they currently aren't experiencing any camera issues... Lies.... So the only remedy they offered me was to factory reset... Done that twice.. Or to take it to a repair center. But I believe this is a software issue.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
This is what they told me as well. The support rep assured me that the phone might need repairs. I mean, they are a big company, so they probably don't want a big issue like this being on the front page to Engadget. So they're most likely downplaying all the issues and we can hope that a fix in the near future is out there...
blkout01 said:
This is a huge issue for me and it's getting worse. Its got to the point now I have to turn the phone off and sometimes even pull the battery. At first it was simply kill the camera and try to open it. After opening it about 7 times it would work. I'm going to start looking in to this further as it has gotten out of control. I'll post back here if I find anything worth sharing.
Click to expand...
Click to collapse
Whoa. This is exactly my problem. Except, mine isn't getting worse but if you have anymore info on this issue, feel free to speak your mind. I do feel your pain brother, I love photography and thought this would be my point and shoot while shopping for a DSLR.
I too am experiencing the freeze up once in a while but my main gripe is well yes it is a down step from the 8meg pixel camera on the original EVO, and I understand that but I came from the Hero with a 5meg camera also and it seems to take sharper and better quality photos than my 3vo...of course in 2D. A little disappointed to say the least.
So far tempt rooting doesn't seem to make the freezing stop. Oh well...I haven't found much use for the camera as of lately. The phone itself is flawless though..
This is my second Evo 3D and both did it. Same issues as discussed here. This is how I can seem to "force" it. If I take a picture and the preview is up and I touch the screen before the preview goes away then it stays of the preview. Have to close and restart camera bunch. Also if I am in the camera and I hit the little thumbnail in the lower left to go to the gallery, also stuck on the first preview it brings up. SOMETIMES if I close the camera and then go to the actual Gallery and then come back to the camera it will work.
I also experience these type of issues when switching from 2D to 3D. Again, this is my second (I had to return the first one fore defective screen) and they both had the exact same behavior. Both BEFORE and AFTER OTA.
It is actually very embarrasing to try to show off your new technology and it freezes everytime you try to show it off. I have had several people just laugh at it. "Yeah nice phone."
If you absolutely do not have to. Don't exchange it. My phone works flawlessly minus the camera freezing and I ended up not taking the risk of getting a phone with a myriad of issues in this forum.
As soon as HTC sends out another OTA fixing this, as I'm sure this is a software issue, I will be extremely pleased.
yeah i dont know what to do, because htc is assuring me that it could be hardware related. Although i dont think thats the case since it hasnt fully failed yet. Camera app works to a point where i start messing with the 2d/3d switch or hold the phone from portrait mode to landscape mode.
Same with mine. It works on and off (mostly off) so I am at least 90% sure it's a bug in the software for the camera.
chlehqls said:
Same with mine. It works on and off (mostly off) so I am at least 90% sure it's a bug in the software for the camera.
Click to expand...
Click to collapse
thanks for your response, i guess we'll just play the waiting game since everything else works flawlessly on this phone
I took all ota's. No camera bugs here.
Sent from my 3rd Dimension of Evolution
The issue is the SD card.
The factory one is SLOW. It takes time to write to a slow card....hence camera lag while it's writing the image file.
That was tough....next.
Hello.
I have an unique problem and I really tried to find for someone with the same problem. My camera has a very strange behavior and it is just the rear camera. Its complicated to explain but please see the attached screenshot that I took. There are some pink/red stripes when the camera is on and when I take the pictures gets a little bettler.
Any ideas of what is going on?
regards
S3
4.2.2 - i am running now Omega latest version but doen not matter, all roms that i tried has the same issue.
Thanks for any help
Renato
mussacredi said:
Hello.
I have an unique problem and I really tried to find for someone with the same problem. My camera has a very strange behavior and it is just the rear camera. Its complicated to explain but please see the attached screenshot that I took. There are some pink/red stripes when the camera is on and when I take the pictures gets a little bettler.
Any ideas of what is going on?
regards
S3
4.2.2 - i am running now Omega latest version but doen not matter, all roms that i tried has the same issue.
Thanks for any help
Renato
Click to expand...
Click to collapse
Well, with all I know about cameras by being a freelancer photographer and with my little knowledge about android what I can say to try to help you is:
Did you wipe your phone between flashes? I'll guess you did since you tried multiple roms. If you didn't, You'd better try to...
If stock ROMs also show the problem I'm afraid to tell you that the only circumstances I saw this kind of problem in my life was in faulty camera sensors.
Were your sensor hit by any kind of laser or a very strong light while trying to snap a picture? Similar problems happened lately with photogs attending a concert. See link:
http://www.diyphotography.net/20000k-red-epic-sensor-burnt-lasers
If this didn't help and the problem started out of nowhere then maybe you got a faulty unit, are you still on warranty? If so, it's time to revert to stock and go to a service center!
Kindly hope I'm very wrong though... Good luck!
[READ THlS FlRST] POST QUESTIONS IN THE Q&A SECTION AND NOT HERE!!!!
lucalunardi said:
Well, with all I know about cameras by being a freelancer photographer and with my little knowledge about android what I can say to try to help you is:
Did you wipe your phone between flashes? I'll guess you did since you tried multiple roms. If you didn't, You'd better try to...
If stock ROMs also show the problem I'm afraid to tell you that the only circumstances I saw this kind of problem in my life was in faulty camera sensors.
Were your sensor hit by any kind of laser or a very strong light while trying to snap a picture? Similar problems happened lately with photogs attending a concert. See link:
http://www.diyphotography.net/20000k-red-epic-sensor-burnt-lasers
If this didn't help and the problem started out of nowhere then maybe you got a faulty unit, are you still on warranty? If so, it's time to revert to stock and go to a service center!
Kindly hope I'm very wrong though... Good luck!
Click to expand...
Click to collapse
Thanks, The funny thing is sometimes works fine and sometimes works like the pic attached. No idea at all. The phone has never felt or had anything like you said such as strong light or laser.
thanks
Search the forum... Maybe a camera fw upgrade may help. Worth a try. Good luck.
Sent from my phone using the "Send" button.
mussacredi said:
Thanks, The funny thing is sometimes works fine and sometimes works like the pic attached. No idea at all. The phone has never felt or had anything like you said such as strong light or laser.
thanks
Click to expand...
Click to collapse
My feeling is that this could well be a hardware problem, not a software problem - ie nothing to do with your ROM, as you said you've flashed a few. If it is a hardware fault then see if you can get it fixed under warranty - but as has already been said, you'd need to return to your stock rom first otherwise they wont honour the warranty.
Having said that... were all the ROMS you tried AOSP / AOKP based? While I haven't had the problem you have and it does seem very unique, I have had more issues and bugs with the camera when using ROMS built from these sources on my i9300 than anything else. At the end of the day, Samsung know best how to drive their camera hardware, and so it doesn't surprise me that the vanilla Google roms can be a bit buggy when it comes to device-specific hardware such as the camera.
You could try flashing a stock-based custom rom - one built from Samsung firmware. Omega ROM that you are currently using also do a stock-based rom built on the 4.2.2 Samsung leak, I have used it and can confirm that it was pretty darn stable and the camera worked really well. It has a few mods in it, nothing spectacular, but it is stable.
Hope this helps.
This looks like a hardware problem. But can't be 100% sure.
I had a camera and someone dropped it, after dropping it, the camera started taking photos like that with stripes of different colours.
Did you drop it or water got on it?
very weird
I tried to fix permission, wipe dalvik and wipe bats and the camera starts to work again. Have no idea how long it will take. so far it is working as has never had a problem.
thanks for all answers...
and sorry to post this on the wrong section.
Bad news not working...dont know what the hell is that...sometimes works sometimes does not
mussacredi said:
Bad news not working...dont know what the hell is that...sometimes works sometimes does not
Click to expand...
Click to collapse
Return phone to stock for warranty and find a service centre .
jje
Hello,
it's about 2 months since I've had this problem with my camera. To be honest my phone falls alot but rly didn't ahve any problems with it so far. Until this problem occured. I had omega 44 when this suddenly appeard on my back camera. These vertical lines just appeared and when it's darer it's easier to notice them. My front camera works normally and I don't have any problems with it. I've thought about ordering new camera from the ebay but I just want to be sure that it's rly hardware problem. Now I'm on this new omega 8.1 version and this problem still persists.
Does anyone knows what is the most probable problem here? It would help me a lot in making my decision here.
Thanks
joskolokas said:
Does anyone knows what is the most probable problem here? It would help me a lot in making my decision here.
Thanks
Click to expand...
Click to collapse
obviously the problem is with your camera hardware. get it replaced from service center.
Ok thanks. I think they'll charge me to much for that simple replacement. I want to change it by myself but I saw there are a lot of cameras on the ebay and I'm not sure which one to order. Don't know if there are different editions of cameras for s3, or some kind of regional key so if someone knows what should I look for I'd be grateful. Thank you
Sent from the outer space
try using camera apps like camera jb+ if the proble stills maybe it s the hardware
I've tried using many other softwares and the problem is still there. I'll be ordering new camera, it's jut that i'm not sure if there is some kind of regional lock or version of camera. Just don't want to give money for a wrong camera
way back Google has acknowledged this issue and hoping it will be fixed in Android 7.0 update, but still there. This issue seems to be related to the noise-cancelling mic found on the back of the device.
I know some people posted some workaround such as covering up the mic fixes the issue, or persist.audio.fluence.voicecall=true, and changing it to false in build.prop (if rooted, which I am not).
I know there are tons of post related this (searching Google gives many of them), I was just wondering if anyone seen any improvement after 7.0 update or pretty much the same or any other workaround that worked for you..
share your thoughts and findings would be great..
It's a hardware defect. RMA your device and get one that works. I had the same issue with my first device. Returned it and now all is good in the world... You shouldn't have to disable the noise cancelling mic... It's there for a reason
Smallsmx3 said:
It's a hardware defect. RMA your device and get one that works. I had the same issue with my first device. Returned it and now all is good in the world... You shouldn't have to disable the noise cancelling mic... It's there for a reason
Click to expand...
Click to collapse
ohh well, this is factory refurbished one, so I don't think I can do RMA now...well I guess I can live with it for a while until I dump this phone with better alternative...
jazzespresso said:
ohh well, this is factory refurbished one, so I don't think I can do RMA now...well I guess I can live with it for a while until I dump this phone with better alternative...
Click to expand...
Click to collapse
Did you get it from Google?
Smallsmx3 said:
Did you get it from Google?
Click to expand...
Click to collapse
No. I got it from BestBuy couple months ago...checked with Google, and re-turn period is over for this phone, and BestBuy has 90 days return, which is also over...
and I know noise cancelling mic. is there for a good reason, but it is better people can hear me when I speak is more important, so I am planing to put a small tape on mic back of the phone and give a try and see if any improvement...
other than, I really love my Nexus 6P, but this small annoying issue really really bothers me..
If it's a hardware issue why does it work fine when your in speaker phone? At least mine does.....
Sent from my Nexus 6P using XDA-Developers mobile app
Mine also works fine in speaker mode, using the handset speaker everyone always complains about the quality
Sent from my Nexus 6P using Tapatalk
I've putting up with this problem for nearly a year now. It sucks that Google continually ignores that fact it exists and none of the major tech sites have taking them to task over it. I've only now read of two people who have resolved the issue via RMA. Everyone else who RMA their phones reported the same behavior with the replacement according to the Google forums.
Anyhow, I just followed the advice of someone from Reddit which I posted below and I then tested twice with my one friend who always have a problem hearing me when I call her iPhone. Now, the problem seems to be cleared up but I don't know if this was a permanent fix or not. Hopefully, I will know by early Nov. which is when my 1 year warranty expires.
----------------
Restart your phone in safe mode. Hold the power button until 'Power off' comes up. Then touch and hold that box until it asks to reboot in safe mode. Make a call in safe mode and see if that works. Then reboot normally. Fixed the problem of my phone calls sounding bad. It resets something, not sure but it fixed my problem. If that doesn't work then RMA (They will probably ask you to do what I just mentioned since this is what just happened to me).
mrsean said:
I've putting up with this problem for nearly a year now. It sucks that Google continually ignores that fact it exists and none of the major tech sites have taking them to task over it. I've only now read of two people who have resolved the issue via RMA. Everyone else who RMA their phones reported the same behavior with the replacement according to the Google forums.
Anyhow, I just followed the advice of someone from Reddit which I posted below and I then tested twice with my one friend who always have a problem hearing me when I call her iPhone. Now, the problem seems to be cleared up but I don't know if this was a permanent fix or not. Hopefully, I will know by early Nov. which is when my 1 year warranty expires.
----------------
Restart your phone in safe mode. Hold the power button until 'Power off' comes up. Then touch and hold that box until it asks to reboot in safe mode. Make a call in safe mode and see if that works. Then reboot normally. Fixed the problem of my phone calls sounding bad. It resets something, not sure but it fixed my problem. If that doesn't work then RMA (They will probably ask you to do what I just mentioned since this is what just happened to me).
Click to expand...
Click to collapse
Here is my add to this. I was a purchaser of a Note 7. Returned it during the recall and bought a Nexus 6p directly from Google. I received the device and was having issues with people on the other end complaining of echoing if they could hear me. Alot of time I could hear them and they couldn't hear me at all. I called Google and explained the situation. They shipped me my replacement device (which by the way was a new device and not a factory refurb). My replacement device does not have the audio issues and I am extremely happy. So I can confirm that it is indeed a hardware issue and the only fix is an RMA.
Do you guys have a case on your phones? I found that my Spigen case was causing issues. It seems to have stretched a bit and was covering the noise cancelling mic.
Sent from my Nexus 6P using Tapatalk
MedicStuder said:
Here is my add to this. I was a purchaser of a Note 7. Returned it during the recall and bought a Nexus 6p directly from Google. I received the device and was having issues with people on the other end complaining of echoing if they could hear me. Alot of time I could hear them and they couldn't hear me at all. I called Google and explained the situation. They shipped me my replacement device (which by the way was a new device and not a factory refurb). My replacement device does not have the audio issues and I am extremely happy. So I can confirm that it is indeed a hardware issue and the only fix is an RMA.
Click to expand...
Click to collapse
You just quoted someone that said he fixed his in safe mode and then you said it's for sure a hardware issue......?. It could be a hardware or software issue depending on you situation. I believe mine is software because it works great in speaker phone.
Sent from my Nexus 6P using XDA-Developers mobile app
skw5115 said:
Do you guys have a case on your phones? I found that my Spigen case was causing issues. It seems to have stretched a bit and was covering the noise cancelling mic.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Hello there!
Same problem here, opposite side is always telling me, that I sound like from garbage/drain or some pipe and also opposite side has echo of it's voice, so practically they hear only themselves with echoes and me very bad or not at all...
I'm using my 6P with Spigen Rugged Armor, and I also tried to make calls without it, and it looked like it's better, so I tried another cover case - Nilkin Perfect Fit, same problems as Rugged Armor and now for the third time, I'm trying Spigen Thin Fit and don't be surprised, it's all the same. So again I tried to use phone without cover and problems appeared same as with cover, so there is no straight connection between cover and these problems in my opinion!
I was preparing to make a ROOT and disable back microphone, but I've read some posts about it and decided to try RMA first, I will come back, how it will end up.
I have the same problem, but only when using the internal mic. Other end says I sound muffled, and I'm only 10" away from the mic. I have to be about an inch or so away and NOT on speaker for them to understand me. I can hear them clear as can be. I have the Unicorn Beetle case, and the noise canceling mic isn't covered, or dirty. I'll try a reboot into safe mode, call, and reboot again. Of course, it could also be just certain people are having a hard time hearing me. I'll see what I can come up with.
Originally Posted by mrsean
I've putting up with this problem for nearly a year now. It sucks that Google continually ignores that fact it exists and none of the major tech sites have taking them to task over it. I've only now read of two people who have resolved the issue via RMA. Everyone else who RMA their phones reported the same behavior with the replacement according to the Google forums.
Anyhow, I just followed the advice of someone from Reddit which I posted below and I then tested twice with my one friend who always have a problem hearing me when I call her iPhone. Now, the problem seems to be cleared up but I don't know if this was a permanent fix or not. Hopefully, I will know by early Nov. which is when my 1 year warranty expires.
----------------
Restart your phone in safe mode. Hold the power button until 'Power off' comes up. Then touch and hold that box until it asks to reboot in safe mode. Make a call in safe mode and see if that works. Then reboot normally. Fixed the problem of my phone calls sounding bad. It resets something, not sure but it fixed my problem. If that doesn't work then RMA (They will probably ask you to do what I just mentioned since this is what just happened to me).
Click to expand...
Click to collapse
This worked for me. Thx!
For those who sufferef from muffled voice/bad microphone, try loose the screw at the bottom back of your 6p, you have to open the cover first by using guitar pick/cutter>loose the screw (centre)>put the cover back> completed. No complaint from the other end at all.
Stock 6p, dp4
Solution- Safemode restart...
Thanks guys..I just tried the Safemode restart and it worked perfectly. Then restart in normal mode and the interference could be heard again..so it's one of the apps..not the handset. Thanks again, saved a lot of hassle by avoiding the RMA nightmare.
Ok, so here's my solution/problem - I've rooted, edited build.prop:
persist.audio.fluence.voicecall=true ---->>> false
persist.audio.fluence.speaker=true --->>> flase
It fixes the issue with garbled/muffled voice from both me and the person on another end; however, now the speaker volume is too high (even on the lowest setting). Editing lines in mixer_path xml makes phone calls unusable - the dialer shows it's connected but I cannot hear anything and the person says their volume is stuck at 0 ....
Any one knows the correct way to edit the "steps" for speaker colume for voice calls?
EvoX2008 said:
Ok, so here's my solution/problem - I've rooted, edited build.prop:
persist.audio.fluence.voicecall=true ---->>> false
persist.audio.fluence.speaker=true --->>> flase
It fixes the issue with garbled/muffled voice from both me and the person on another end; however, now the speaker volume is too high (even on the lowest setting). Editing lines in mixer_path xml makes phone calls unusable - the dialer shows it's connected but I cannot hear anything and the person says their volume is stuck at 0 ....
Any one knows the correct way to edit the "steps" for speaker colume for voice calls?
Click to expand...
Click to collapse
Turn the "speaker" line back to true.
Geezerooo said:
Turn the "speaker" line back to true.
Click to expand...
Click to collapse
Is it a known issue when I recover from a backup, wifi won't work? It was a full backup - system, data, etc
Had to put back the official 8.0 image, just rooted and getting my stuff set up, will try the "speaker" toggle when done in an hour.
EvoX2008 said:
Is it a known issue when I recover from a backup, wifi won't work? It was a full backup - system, data, etc
Had to put back the official 8.0 image, just rooted and getting my stuff set up, will try the "speaker" toggle when done in an hour.
Click to expand...
Click to collapse
Did you reflash the correct vendor?
My lg g5 main camera is not focusing. It was fine before vut now it is not focusing even in manual mode, it is not focusing i can get a subject in focus but only for 1 sec. Is so.ething wrong with the hardware?
I am glad that I decided to come around here today and found your post. I do not take a LOT of pictures but do use my camera most days. I started noticing a couple days ago the same thing you are mentioning here. The camera starts to auto-focus, focuses on the subject for a split second, and then starts auto-focusing again but never on the correct subject. I am glad to hear that it is not a isolated incident on my phone only. My phone has not had any physical damage so I guess the next step is to check into software issues. Hopefully we can find a quick/easy fix to this as it is terribly annoying to say the least.
FiLiNuX said:
I am glad that I decided to come around here today and found your post. I do not take a LOT of pictures but do use my camera most days. I started noticing a couple days ago the same thing you are mentioning here. The camera starts to auto-focus, focuses on the subject for a split second, and then starts auto-focusing again but never on the correct subject. I am glad to hear that it is not a isolated incident on my phone only. My phone has not had any physical damage so I guess the next step is to check into software issues. Hopefully we can find a quick/easy fix to this as it is terribly annoying to say the least.
Click to expand...
Click to collapse
By mistake i posted this question twice and on the 2nd post one guy told me that my hardware failed, replace your camera. What do u think about it software or hardware?