Related
So I'm one of the unfortunate users that has the stupid mic muting issue. I've just been dealing with it and waiting to see if a update from vzw ends up fixing it. Well, it's been five months and still no update. I rooted my phone immediately after the first time I ran into the problem. I'm on the 4.0.4 radio now and it's still there.
So has anybody had luck switching out devices? It sucks because my screen is beautiful and the call muting issue is the only one I have. Should I go through the hassle of getting a replacement?
Edit* crap, can a mod move this to q/a.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
I've never had this issue on my LTE GNex. I don't believe its a common issue. I would definitely get it replaced.
what exactly happens that mutes it, and for how long? does it happen when you are not holding the phone?
reason i ask, is the microphone is a tiny hole on the bottom of the phone, and if you hold the phone like many do, with a finger underneath, even slightly blocking this hole will completely mute the microphone out.
cancerouspete said:
what exactly happens that mutes it, and for how long? does it happen when you are not holding the phone?
reason i ask, is the microphone is a tiny hole on the bottom of the phone, and if you hold the phone like many do, with a finger underneath, even slightly blocking this hole will completely mute the microphone out.
Click to expand...
Click to collapse
To all Verizon Galaxy Nexus users who have no idea what issue we are talking about, read the following:
http://code.google.com/p/android/issues/detail?id=24019
It basically happens on full signal (with LTE and/or CDMA turned off and on), stationary or moving, under bluetooth + speaker + ear piece while physically holding the phone or not, makes our voice turn into a choppy robotic sound and we can hear them but the other party can't hear me.
Only resolution to this problem is hang up and call again.
There is a huge variation among devices, some has this issue as soon as 5 seconds into a phone call, some have it well into 15 mins or even 40 mins into a call. Some happens basically on every other call, some happens once in a bluemoon.
Yes, we've all tried every single ROMs and radios. And yes, we are not holding it wrong to cover our mic with our finger tips.
And yes, it is not user error because it happened to all 2 new gnex and 2 refurbished replacements STOCK without any apps on it. I got mine to happened on pretty much the entire state of california (I travel very frequently from SoCal to NorCal)
The only reason a few might not face this issue is simply because 1) either they picked the cream of the crop out of all these affected devices 2) not using the GNex as a phone as much as some of us do.
I simply do not use GNex for business purposes...
To OP, getting a replacement might help a little but no promises.
Man I'd have replaced it long ago. I would imagine it's hardware related or they would've pushed an OTA to fix it. I read somewhere that Verizon stated an update would be sent out that would fix it, but I'm not buying it.
Sent from my Galaxy Nexus using Tapatalk 2
Yeah I'm just scared to swap it out and receive one with a ****ty screen. Plus I have a invisible shield on here. And there's no guarantee it will be resolved. Has anyone had any luck with swapping them out? I really don't want to switch to a different phone. I've waited for a nexus device to hit verizon for so long.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
Ya know, honestly, I'm not all that impressed with the phone. I've only had it a couple weeks, but it doesn't do anything better than the Epic 4G Touch that I came from. The E4GT was awesome, the Sprint network, not so much. The camera and battery life were just so much better and I'm struggling with that.
Sent from my Galaxy Nexus using Tapatalk 2
bangdrum said:
Edit* crap, can a mod move this to q/a.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Gotcha Bro
FNM
I just got off the phone with VZW about this very issue. They said they have a release tentatively scheduled for May, but "tentatively" could end up being August. It's a known issue so, there's no workaround for it and getting a replacement probably won't help.
The only thing they could possibly offer is switching to another device altogether. Spec-wise, the Galaxy Nexus is at the top for me so I don't want another phone. (frustration)
Alas, depending on what's important to you, you may just be better off waiting for the update. :-(
blackdiamond01 said:
I just got off the phone with VZW about this very issue. They said they have a release tentatively scheduled for May, but "tentatively" could end up being August. It's a known issue so, there's no workaround for it and getting a replacement probably won't help.
The only thing they could possibly offer is switching to another device altogether. Spec-wise, the Galaxy Nexus is at the top for me so I don't want another phone. (frustration)
Alas, depending on what's important to you, you may just be better off waiting for the update. :-(
Click to expand...
Click to collapse
This is why I'm glad I asked. I don't want to bother with getting a refurbished phone for nothing.
Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
I know it's kind of a old thread but wanted to update my experiences.
I am on my second replacement now and I'm sticking with it. I've had the issue maybe 3 times in the month I've had it. My first replacement had a terrible screen, crappy signal, and the muting issue happened just as frequently as before if not more.
I'm assuming this will never be spoken of by Samsung since we've already had the phone almost a year with no acknowledgement. I just hope the next nexus is a different manufacturer (HTC especially) since every Samsung phone I've had has had issues with the actual phone part. My first being the fascinate and now this. Especially since if I want to upgrade from now on ill end up paying full price.
Sent from my Nexus 7 using Tapatalk 2
bangdrum said:
I know it's kind of a old thread but wanted to update my experiences.
I am on my second replacement now and I'm sticking with it. I've had the issue maybe 3 times in the month I've had it. My first replacement had a terrible screen, crappy signal, and the muting issue happened just as frequently as before if not more.
I'm assuming this will never be spoken of by Samsung since we've already had the phone almost a year with no acknowledgement. I just hope the next nexus is a different manufacturer (HTC especially) since every Samsung phone I've had has had issues with the actual phone part. My first being the fascinate and now this. Especially since if I want to upgrade from now on ill end up paying full price.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I have had the same problem.
I've gone through 2 replacements and still the same issues have occurred. The update that was supposed to fix this was released in May and it fixed nothing. I called Verizon several times asking what will be done about this. Their answer is that another update will fix this. I frankly don't believe it.
Verizon also told me that Samsung is aware and they're "actively" working on a fix.
Being that I use this phone to make business calls, I can't have a phone that I can't depend on. Their answer: We can give you the RAZR. Not the RAZR Maxx - the RAZR.
I said that won't work because the RAZR doesn't compare to my phone as far as specs go. It's worth 200 less than my phone on their website.
The only phone that compares to mine is the Galaxy S3. Not to mention, I flat-out don't like the RAZR (or the RAZR Maxx). They said they couldn't give me the S3 because the phone was just released.
So, in short, I'm VERY upset with Verizon, because I don't feel like I'm being treated fairly. I'm willing to wait for this so called fix they will push out since my warranty is until December and they claim they'll get it right this time. But if this doesn't work....well, I feel sorry for whichever Customer Rep catches my evil side lol.
Yeah they are gonna get an earful tomorrow when I call. I've had the phone maybe 18 days and it didn't start this until day 11 and ever since its been non stop. I don't think any of us should suffer through calling 10-15 times per 30 minute conversation.
Sent from my Galaxy Nexus using xda premium
donnieseech said:
Yeah they are gonna get an earful tomorrow when I call. I've had the phone maybe 18 days and it didn't start this until day 11 and ever since its been non stop. I don't think any of us should suffer through calling 10-15 times per 30 minute conversation.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Good luck with that. I'd be interested to know how that works out for ya. Hopefully you'll get a decent answer.
blackdiamond01 said:
I have had the same problem.
I've gone through 2 replacements and still the same issues have occurred. The update that was supposed to fix this was released in May and it fixed nothing. I called Verizon several times asking what will be done about this. Their answer is that another update will fix this. I frankly don't believe it.
Verizon also told me that Samsung is aware and they're "actively" working on a fix.
Being that I use this phone to make business calls, I can't have a phone that I can't depend on. Their answer: We can give you the RAZR. Not the RAZR Maxx - the RAZR.
I said that won't work because the RAZR doesn't compare to my phone as far as specs go. It's worth 200 less than my phone on their website.
The only phone that compares to mine is the Galaxy S3. Not to mention, I flat-out don't like the RAZR (or the RAZR Maxx). They said they couldn't give me the S3 because the phone was just released.
So, in short, I'm VERY upset with Verizon, because I don't feel like I'm being treated fairly. I'm willing to wait for this so called fix they will push out since my warranty is until December and they claim they'll get it right this time. But if this doesn't work....well, I feel sorry for whichever Customer Rep catches my evil side lol.
Click to expand...
Click to collapse
Exact same story they told me. I'm in my 5th device. 1st one camera broke completely and signal issues. 2nd one screen had a nasty yellow tint on half the screen. 3rd one had the worst screen I had ever seen. I wish I would have taken pictures to show. 4th one was great till the ear speaker completely went out and the speaker broke. 5th one that I currently have has a beautiful screen with no issues so far.
Sent from my Galaxy Nexus using xda premium
May have to take my G back. A lot of touch screen issues where touches aren't being interpreted correctly... It is also very difficult to scroll up and down fluidly without selecting something... Honestly starting to get a little frustrated with the issue... Not cool at ALL.. Hoping this is not a bug. I actually have to push about 2-3x harder on this touch screen then any of my other phones.. If I just flick my finger to scroll through a page 1/2 the time my finger selects something instead of scrolling. That is also why I have been having so many keyboard issues. May do a hard reset tomorrow. And wait for some of you guys to get your in the next few weeks before returning mine.
Sent from my LG-E970 using xda premium
mrdumbdumb said:
May have to take my G back. A lot of touch screen issues where touches aren't being interpreted correctly... It is also very difficult to scroll up and down fluidly without selecting something... Honestly starting to get a little frustrated with the issue... Not cool at ALL.. Hoping this is not a bug. I actually have to push about 2-3x harder on this touch screen then any of my other phones.. If I just flick my finger to scroll through a page 1/2 the time my finger selects something instead of scrolling. That is also why I have been having so many keyboard issues. May do a hard reset tomorrow. And wait for some of you guys to get your in the next few weeks before returning mine.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
I notice this happens while plugged in. I think it's a mix software/hardware issue.
When plugged into the wall with the default cable it goes retarded.
I tried again with my Nexus 7 cable/charger and it was fine.
Retarded again when plugged into my laptop.
The phone is ****ing beautiful, but **** like this makes me want to return it and I've only had it for 4 hours.
EDIT: This phone is the biggest pile of garbage I've ever touched in my life. It's locked up like apple and you can't even debloat it without it crapping out.
I'm returning it tomorrow morning.
On a side note, it's the sexiest phone frame i've ever touched.
yes... Should have mentioned that... LOL... happens when it's plugged in WTF
Sent from my LG-E970 using xda premium
mrdumbdumb said:
yes... Should have mentioned that... LOL... happens when it's plugged in WTF
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
It's insane.
Band with me brother. Return it tomorrow and buy a Nexus 4 in 2 weeks.
Also, I bought it unlocked. Full price. I think I was the first guy in the city to buy one.
I have no issues with mine runs perfectly so far thnx god
Sent from my LG Optimus G
My touch screen is fine but the stock browser likes to lock up on occasion. I am not sure how much I actually love this phone.
Sent from my LG-E970 using Tapatalk 2
In Korea, it's known issue between OG users.
Cause of unstable voltage or no grounding(earthing) in your house.
OG uses 1.2A charger, it's too sensative.
Using ferrite core cable may reduce touch issue.
Someone uses Blackberry's charger. but not sure in other country
No issues with mine. Phones are not built equally. And I don't care that's its all locked up. I don't do any of that stuff anyway. People should know what they buy. I new it was going to be locked up before I bought it. You can never go wrong with a nexus device if that stuff is important to you. I just get tired of people complaining about phones that are locked up. There are more people out there that will buy this phone that have never herd of rooting or a locked downloader. I know two people that never herd of that stuff but love and buy android phones. Now granted that I'm saying this in the xda forums so it kinda pointless.
Sent from my LG-E970 using Tapatalk 2
spacecasespiff said:
No issues with mine. Phones are not built equally. And I don't care that's its all locked up. I don't do any of that stuff anyway. People should know what they buy. I new it was going to be locked up before I bought it. You can never go wrong with a nexus device if that stuff is important to you. I just get tired of people complaining about phones that are locked up. There are more people out there that will buy this phone that have never herd of rooting or a locked downloader. I know two people that never herd of that stuff but love and buy android phones. Now granted that I'm saying this in the xda forums so it kinda pointless.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
*heard (sorry)
It's not just locked. You can't debloat without the entire thing locking up.
bastardinator said:
*heard (sorry)
It's not just locked. You can't debloat without the entire thing locking up.
Click to expand...
Click to collapse
Can you freeze it? I was planning on doing that but idk if it will lock it up also. Iv always just done that because some ota updates don't work if you don't have all the stock apps.
interesting about the grounding... kind of like a gfi popping.... hmmm. my house has no ground wires and has never been upgraded in the past 80 years so that is possible phenomenon ... phone does feel a bit cooler and my quadrant scores are also tick lower too after the firmware patch
Sent from my LG-E970 using xda premium
My EVO 4G had the same exact problem when I tried to use my multi charger (car charger but could plug into the wall socket). It worked fine with the stock charger. Probably like they said, something about the grounding or just the charger is a piece of crap.
mine works perfectly, and I just dont get the people backing on this UI....very functional
I returned my Optimus G.
I wasn't able to replicate the problem in-store, so I guess it is an issue with my wiring at home.
This thread is funny because I noticed the same thing when I was looking at the Optimus G. Except this one happened on the one that was in the store. I was trying to pick between the Samsung Galaxy S3 or the LG Optimus G. I kept going back and forth not being able to make up my mind, but noticed the LG Optimus G had a very weird touch screen. It kept randomly selecting things when I tried to swipe from one side to another. I tried turning it sideways and noticed it didnt do it then so I was hoping there was something wrong with the floor model. I went ahead and got the LG Optimus G and I can easily say I am extremely happy I did. The phone has been great so far with zero problems and its already rooted which is terrific. I am having some problems removing the bloated ATT software but that is honestly the last thing on my list right now.
shoemocker said:
This thread is funny because I noticed the same thing when I was looking at the Optimus G. Except this one happened on the one that was in the store. I was trying to pick between the Samsung Galaxy S3 or the LG Optimus G. I kept going back and forth not being able to make up my mind, but noticed the LG Optimus G had a very weird touch screen. It kept randomly selecting things when I tried to swipe from one side to another. I tried turning it sideways and noticed it didnt do it then so I was hoping there was something wrong with the floor model. I went ahead and got the LG Optimus G and I can easily say I am extremely happy I did. The phone has been great so far with zero problems and its already rooted which is terrific. I am having some problems removing the bloated ATT software but that is honestly the last thing on my list right now.
Click to expand...
Click to collapse
I wouldn't remove att bloat yet. Freeze it at most. There has been issues caused by removing it.
I have the touch screen issue on both my lg charger and my old Samsung charger. Its very annoying. Not sure if it's worth returning the phone over because I love everything else about it but I would like to see if there is a way to fix the issue.
Sent from my LG-LS970 using xda premium
Noticed the bug few times too.
Not really a trouble, feels like it stops recognizing the gestures on the screen, cause simple touch actions still working good.
Pushing the sleep button fixing it.
By the way didnt happen to me last 3-4 days.
yep, i've noticed the same thing. a restart fixed the issue for now though. but yes, it was also while being plugged into the AC charger.
FYI, same issue happens with the nexus 4.
If its plugged into a usb port, the touch screen becomes unresponsive.
I recently had the random menu pop up and bottom key freeze on my E4GT. It was real bad, my phone was barely usable. Sprint replaced my phone with a refurbished warranty phone, and same exact problem with that phone. Well I went thru 3 phones all with the same problem. I was told it was a glitch with a part in the bottom of the touch screen that apparently goes bad. They replaced the so called defective piece (the whole touch screen). That was done to my 3rd phone. And still same problem. It would always happen about 24 hours after I picked up my phone and it would act up worse when I was in a bad signal area. I became very aggravated. I can understand 1 phone but 3 ? Well the 4th phone I got doesn't act up but I'm still experiencing the bottom keys randomly freezing upon waking the screen. Happens about 4 - 5 times a day. I was on stock FI27 w/ no root. And also I found it odd that when I got the ota for FL24 my phone aborted it and stuck in stock recovery. So I rebooted and went to system updates and it said my software was up to date even tho I was still on FI27. I waited 2 weeks and never got the ota again so I decided to manually update to FL24. Few days after that when QBKing posted FL24 w/ root I decided to root my phone. The bottom keys still freeze randomly only upon wake. I'm afraid to ask for another replacement in fear of getting another bad one with the menu pop up. Id rather deal with the bottom key freeze then the other problem. But it is aggravating with the bottom keys freezing. I shouldn't have to deal with any issues. Anyone familiar with this or experiencing anything like this ? Or does anyone know anything about this? Any help would be greatly appreciated. Thanks
Sent from my SPH-D710 using xda app-developers app
Its called phantom key presses. Are you in a low signal area? It happens because antennae is behind touch buttons. When your in low signal area it causes interference. Theres a thread in detail about this. My previous e4gts did this. I just received a brand new not refurb phone from insurance was built 12-2-12. I have not seen this at all. Tell them you want a new one!!
Sent from my SPH-D710 using Tapatalk 2
The manager at my local sprint store (independently owned & operated) told my brother that the S2's are still garbage and he should buy an S3 instead. Take it for what it's worth. My phone randomly freezes with the screen off and kills the battery, even while I was on stock. My sister's phone has never had a single issue. She also somehow gets 18 hours out of a single battery charge with heavy wifi use. I'm lucky to get 10 with minimal use. I swapped the batteries, and no difference.
It seems these phones have relatively poor QC, but the good ones are great. Why do you think the refurbs were sent back originally? They "test" them and then send them right back out the door.
Yeah I think ur right. And I can't upgrade for a year.
Sent from my SPH-D710 using xda app-developers app
Just as a reference I have two SGs2Epic's since Oct 2011, never had any issues whatsoever,in fact we have not set foot in a Sprint store since Aug 2011. My wife has drop her phone dozens of times,once in the toilet, took it apart, let it dry out overnight in front of ac, reassembled the next morning and its still going strong. The only thing we did to these phones was replace the batteries this past DEC. Both phones are rooted ,mine is on st/ro jelly bean, hers on GB Calk's fabulous E4GT v3.0.
Your condition sounds kind of weird? MikeTuky may be right about the low signal theory, sounds plausible.
Correction/ Did go to a Sprint store around DEC 2011,looking for a doc for our phones. / got it at Amazon.
Pp.:beer:
Transmitted from another galaxy with a Jellybean infused P-5113 full of Unicorn porn.
Well like he said the ones that are good are great, but I've had nothing but trouble. 4 replacement phones and all the same problem b
Sent from my SPH-D710 using xda app-developers app
I have tried asking for a new one, they will not do it. I've even asked for a different phone and all they offered was the Motorola photon lol they said that's the equivalent to this phone. I have called sprint many times and spoke with many different supervisors. Now that you told me they replaced yours with a new one, I'm gonna keep calling and demand a new one. Should I call sprint or the insurance company?
Sent from my SPH-D710 using xda app-developers app
Greek81, by any chance do you work or live near radiation?
Radiologist?
Microwave inspector?
Moon rock collector?
Do drag your feet on a carpet while just wearing socks?
Just curious.
Pp.:what:
sent from a jellybean filled epic touch.
No don't live near anything like that. Its definitely the phone. I just need to get them to send me a new one somehow.
Sent from my SPH-D710 using xda app-developers app
i doubt they will give out new ones now, since the s3 has been out for a while and s4 rumors are running rampant and that usually means a release in the near future. what i don't get is how Samsung/sprint can let so many defective units remain in circulation. you would think a recall would have happened at some point. i cant get my gps to work if my life depended on it and i tried every trick in the book and 2 replacements to fix it. Though i guess it doesnt matter to me at this point since im jumping ship to t-mobile as soon as the s4 drops
although, im curious to know if the other gs2 variants have the same issues just to know who i should blame.
Hello,
I've been googling for days in order to avoid a repost out of respect for the community and to avoid redundancy, but my searches have yielded inconclusive results, with varying answers. Additionally, I couldn't find one in this particular subsection of the forum.
My problem stemmed from using Cyanogenmod while the screen is hot. I was texting on maximum brightness while also downloading several files so the entire AOSP messaging app got imprinted on the screen. The keyboard is faint but noticeable. I had a samsung epic 4g before this with similar problems that went away after I completely stopped usage and turned in on one day. The one on my old Galaxy SI was much more severe and visible from reasonable distance. This one is faint but enough to bother me.
Some searches said the handful screen burn in fix will help, other threads say I should just replace my device (I hope not to go through the hassle of that one) and others say that I should leave a white screen on and a few other searches say that such problems do not exist.
If this is a repost I apologize. All help appreciated.
First, have you shut the device off and let it cool down? If not, that could fix the issue. If that doesn't fix the issue, download LCD Test from the market, set it on the white screen, making sure that you keep the backlight on, and let that run for several hours. Sounds like a pain, but it can potentially fix the issue. There are other methods, but try these two first and if they don't work, let me know and we can try something else.
Sent from my SGH-T999 using xda premium
Never had that issue or seen a phone with that issue. never even had anyone come into the Tmo store I work at with that issue. Sounds to me that if you have had it on your past 3-4 phones maybe you should look at adjusting the way your using them.
As far as fixing it. Do the white screen thing or get it replaced
Sent from my SGH-T999 using Tapatalk 2
clninja said:
Never had that issue or seen a phone with that issue. never even had anyone come into the Tmo store I work at with that issue. Sounds to me that if you have had it on your past 3-4 phones maybe you should look at adjusting the way your using them.
As far as fixing it. Do the white screen thing or get it replaced
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
That's odd since this is a fairly common issue among those who use AOSP keyboard. To be frank I had my ex's name burn in on the screen as well because we messaged so much. Poetic justice perhaps.
I have successfully returned the phone and gotten a new titanium grey one. Thank you both.
So heading says it all, did you have the issue before you installed it and did the ROM fix the issue? I've done the low ISO, I missed around with the settings and it does not fix or make it at all better. I will not settle for a replacement device that is not brand new so I am looking for a software fix. I figure a ROM made from a developer phone would fix it since their software is not affected by this issue. So let me know if you have an answer for this. The key has to be that you had the issue before you installed the ROM. Don't trash the tread with junk or speculations of what might fix it I am only interested in facts at this point I've done all the Google might fix and none did....reply away!
Sent from my HTC6500LVW using xda app-developers app
So I read an article on engadget that said the 4.3 update made improvements to the camera in low light settings. I was previously avoiding 4.3/5.5 ROMs because you can't change the lock screen image independently of the home screen. Anyhow, I flashed it last night and have been snapping away with the camera. The pictures seem better.
It's a shame, other than the camera this phone is nearly perfect.
Sent from my HTC6500LVW using Tapatalk
The gsm ones that got the 4.3 update already owners has said it did not fix the low light issue. I doubt HTC has redid the update for tbd Verizon version
Sent from my HTC6500LVW using Tapatalk
Dark Jedi said:
The gsm ones that got the 4.3 update already owners has said it did not fix the low light issue. I doubt HTC has redid the update for tbd Verizon version
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I don't know, it seems better but I don't have an objective way to measure it. I know that previously my newborn son's face always looked purple in low light pictures and now his skin looks more true to his natural color.
Also, over exposure doesn't seem as bad.
Sent from my HTC6500LVW using Tapatalk
mlin said:
I don't know, it seems better but I don't have an objective way to measure it. I know that previously my newborn son's face always looked purple in low light pictures and now his skin looks more true to his natural color.
Also, over exposure doesn't seem as bad.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Place your hand over your lens and see if the purple comes back
Sent from my HTC6500LVW using Tapatalk
Dark Jedi said:
Place your hand over your lens and see if the purple comes back
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So when you use a 4.3 sense rom found in the forums, like the one I'm running which is the NuSense 4.3 RC5, it seems like its "fixed" but what actually happens when you put your hand over the lens is that the blue hue or red will show up, but as soon as the phone detects the hue it goes away. It seems to keep doing it in a repetitive pattern.Hue shows up, then goes away, then shows up again, then away, unlike before on 4.2 where if it shows up, it'll stay there.
My guess is that on 4.2.2 like others have said, when the ISO is raised too far, the hue showed up. So really, it seems like HTC just gave the a camera a limit to not raise the ISO too far.
It's "sorta" (not really) fixed. It's a hardware issue that's been somewhat softened by software implementations.
Sounds about exactly right for what can be done. The low-light picture taking is really a hard thing to accomplish, me thinks. I have a Canon DSLR, and fast lenses are expensive (apart from prime lenses), so I'm not surprised that this overprmised technology is not meeting expectation. That said, do people really use their camera phones that heavily? I don't. And it certainly wasn't a feature I considered when buying this phone. Not to knock any enthusiasts, but this defect has made me realize how many folks are satisfied with phone camera fidelity.
For any of you interested in photography. $50 spent on a 50mm prime will blow your brains out, expectation-wise.
Zynesterysdan said:
So when you use a 4.3 sense rom found in the forums, like the one I'm running which is the NuSense 4.3 RC5, it seems like its "fixed" but what actually happens when you put your hand over the lens is that the blue hue or red will show up, but as soon as the phone detects the hue it goes away. It seems to keep doing it in a repetitive pattern.Hue shows up, then goes away, then shows up again, then away, unlike before on 4.2 where if it shows up, it'll stay there.
My guess is that on 4.2.2 like others have said, when the ISO is raised too far, the hue showed up. So really, it seems like HTC just gave the a camera a limit to not raise the ISO too far.
It's "sorta" (not really) fixed. It's a hardware issue that's been somewhat softened by software implementations.
Click to expand...
Click to collapse
Zynesterysdan said:
So when you use a 4.3 sense rom found in the forums, like the one I'm running which is the NuSense 4.3 RC5, it seems like its "fixed" but what actually happens when you put your hand over the lens is that the blue hue or red will show up, but as soon as the phone detects the hue it goes away. It seems to keep doing it in a repetitive pattern.Hue shows up, then goes away, then shows up again, then away, unlike before on 4.2 where if it shows up, it'll stay there.
My guess is that on 4.2.2 like others have said, when the ISO is raised too far, the hue showed up. So really, it seems like HTC just gave the a camera a limit to not raise the ISO too far.
It's "sorta" (not really) fixed. It's a hardware issue that's been somewhat softened by software implementations.
Click to expand...
Click to collapse
I use my camera as a camera not as some sort of blue noise detection meter. If the hue is gone from my pics and the ISO isn't so high that there is a bunch of color noise then I'm happy and for all practical uses I'd say it's pretty well fixed.
I tried putting my hand over the lens, after about 90s it started turning kinda blue around the edges then would fade to black. Better than before.
Sent from my HTC6500LVW using Tapatalk
mlin said:
I use my camera as a camera not as some sort of blue noise detection meter. If the hue is gone from my pics and the ISO isn't so high that there is a bunch of color noise then I'm happy and for all practical uses I'd say it's pretty well fixed.
I tried putting my hand over the lens, after about 90s it started turning kinda blue around the edges then would fade to black. Better than before.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
The problem with it still is that because it fades in and out, if you take the picture at the wrong time, the hue will be in the picture. That means you have to time when to take the picture, which I'm sure to many is absolutely not fixed. It's still got much room to improve.
Sent from my HTC6500LVW using Tapatalk
Over in the regular HTC one forum someone posted a video of a HTC one running kit Kat and the person had the phone laying down on a table. When he got to the camera the screen stayed black and their was no purple haze going in and out. So I hope it does fix it and look forward to a kit Kat Rom for our phones.
Sent from my HTC6500LVW using Tapatalk
Zynesterysdan said:
The problem with it still is that because it fades in and out, if you take the picture at the wrong time, the hue will be in the picture. That means you have to time when to take the picture, which I'm sure to many is absolutely not fixed. It's still got much room to improve.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Good point. I've been playing with it more today. I have been able to capture most pictures without the hue, but like you said, it kind of fades in and out.
Sent from my HTC6500LVW using Tapatalk
I can tell you this with certainty.. if you tell HTC you need a repair to take care of a camera issue, they will accept it as a legit reason for service. I told them my camera was showing the red/blue and having trouble changing a focal point once it caught one. They tried talking me into waiting for 4.3. I refused. They opened a service order, I sent it out, about a week later I had my same phone back with none of the original problems. I don't know if they swapped out the hardware or what the deal is but when I cover the lens it stays pitch black.
Yes, it hurts being without a phone for a week but it's better than living with a phone that disappoints you for some reason. And especially when that reason can be remedied.
one4thewings said:
I can tell you this with certainty.. if you tell HTC you need a repair to take care of a camera issue, they will accept it as a legit reason for service. I told them my camera was showing the red/blue and having trouble changing a focal point once it caught one. They tried talking me into waiting for 4.3. I refused. They opened a service order, I sent it out, about a week later I had my same phone back with none of the original problems. I don't know if they swapped out the hardware or what the deal is but when I cover the lens it stays pitch black.
Yes, it hurts being without a phone for a week but it's better than living with a phone that disappoints you for some reason. And especially when that reason can be remedied.
Click to expand...
Click to collapse
Did you return it to stock before sending it? I could stand being without it for a week to have it fixed
jessbowring said:
Did you return it to stock before sending it? I could stand being without it for a week to have it fixed
Click to expand...
Click to collapse
Yes, I did return it to stock before sending it in. I don't know that I needed to, but I wasn't going to take a chance on them refusing to do the work because they didn't like my icons or zooper widgets. =)
I used this thread here: http://forum.xda-developers.com/showthread.php?t=2475216
Just to update this thread I did end up sending my phone to HTC to get repaired it was a one week turn around and came back same phone and fixed. Getting my phone repaired was a big deal since I don't want a CLN or Refrib device. So phone is fixed!
Sent from my HTC6500LVW using xda app-developers app
Just to give an update, the new stock 4.4 gpe rom does a better job of preventing the blue/red noise from appearing. When I cover my hand it appears for half a second then is completely black for the rest of the time
Sent from my HTC6500LVW using Tapatalk
I'm a crack flasher so I flash just about every ROM released just to give it a go and I have to have a ROM (4.2.2, 4.3 or 4.4) that has remedied the issue. HTC swears up and down that there is a camera update coming with 4.3 but seeing as how AT&T and Sprint folks said it helped nothing at all in their forums I'm leaning towards a hardware issue. Sucks but we might be stuck with it.
Zynesterysdan said:
Just to give an update, the new stock 4.4 gpe rom does a better job of preventing the blue/red noise from appearing. When I cover my hand it appears for half a second then is completely black for the rest of the time
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Not stuck with it mine was fixed under warranty repair didn't cost me anything and it's totally gone. 1 week turn around.
Sent from my HTC6500LVW using xda app-developers app
Before and after. No modifications just point and click didn't change anything on camera since I got it back.
Sent from my HTC6500LVW using xda app-developers app
Grnlantern79 said:
Not stuck with it mine was fixed under warranty repair didn't cost me anything and it's totally gone. 1 week turn around.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Well unfortunately I can't be without my phone for more than a couple of days. I use it for work and personal. Too bad HTC doesn't have designated repair centers we can take our phones to for repairs of manufacturer defects. HTC should have acknowledged the issue and authorized cell provider stores where the device was purchased to do exchanges after the traditional 30 day exchange was up. I tried to exchange mine at the Verizon store I bought mine at and they wouldn't do it. Said I still had to go through warranty repair. It's understandable on VZW's end bc it isn't their fault HTC shipped jank phones but on the customer service side it makes both companies look bad. Glad yours got fixed though.
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
Zynesterysdan said:
Just to give an update, the new stock 4.4 gpe rom does a better job of preventing the blue/red noise from appearing. When I cover my hand it appears for half a second then is completely black for the rest of the time
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
It must be subjective bc my hue is still bad but my girlfriend's is semi-okay.