Related
When i first got this phone the gps would always take a while to lock on to satellites and even when it did, it wouldnt be very accurate. It hasnt been working at all for months but i really dont care since i dont use the gps. Ive been running Blazer Rom 4.1 and even went back to stock el29 and it still wont work. Ive tried all the gps fix apps and they do nothing.
Even though i dont really use the gps i was wondering if sprint will replace it since its a hardware problem. The screen has a few scratches and a small crack at the top of the screen and i would like to get the white version but i wouldnt mind if they gave me a black one.
Do you guys think they would replace it?
Probably not.
X_x_X_x_X_x_X said:
When i first got this phone the gps would always take a while to lock on to satellites and even when it did, it wouldnt be very accurate. It hasnt been working at all for months but i really dont care since i dont use the gps. Ive been running Blazer Rom 4.1 and even went back to stock el29 and it still wont work. Ive tried all the gps fix apps and they do nothing.
Even though i dont really use the gps i was wondering if sprint will replace it since its a hardware problem. The screen has a few scratches and a small crack at the top of the screen and i would like to get the white version but i wouldnt mind if they gave me a black one.
Do you guys think they would replace it?
Click to expand...
Click to collapse
As per my little lady, who works for Sprint - You will call in, they'll do basic trouble shooting. If that's a no fix, they'll send you to a service repair store, they'll try. If they cant fix, you'll get a refurbished replacement. If you don't have insurance, you'll pay 35 in fees.
Look up your closest service repair store on sprint and avoid the call in.
Hope this helps.
Sent from my SPH-D710 using XDA
etirkca said:
Probably not.
Click to expand...
Click to collapse
+1, It does not seem like a valid reason to replace the phone.
I did. It all depends on how nice the employees are really.
It burns when I Tapatalk...
Depends on how big the crack is. If its bigger than an inch or spiderwebbbed no way but if its just a small crack a good tech should replace it BC I remember when I first got my e4gt and my GPS didn't work for caput
kurtiskobain said:
Depends on how big the crack is. If its bigger than an inch or spiderwebbbed no way but if its just a small crack a good tech should replace it BC I remember when I first got my e4gt and my GPS didn't work for caput
Click to expand...
Click to collapse
Yeah the crack is smaller than an inch. It's right under the speaker grill but it's like 2 small lines. Not really noticeable. Hopefully they'll replace it
The_LeBoss said:
+1, It does not seem like a valid reason to replace the phone.
Click to expand...
Click to collapse
I strongly disagree. If the GPS doesn't work, then the phone is defective. It would most likely be replaced with a refurbished phone though.
Try clearing your NVRAM and reactivating your phone with sprint on stock EL29. If you can't get a lock or even see a single satellite on GPS test, then I'd guess that the GPS antenna is defective.
Wasn't this a general issue with the e4gt? Mine was the same way, however, ever since I started flashing roms it usually picks up faster. On el29 it never would for me.
Sent from my SPH-D710 using XDA
I have an issue: I've noticed that there is the odd popping sound on every video I take. It isn't a constant pop-pop-pop, but just every so often at random. But it is present on every video I've taken so far.
Wondering if anyone else has the same issue? Any suggestions?
I am running stock with the Perseus kernel.
Thanks!
I had this happen once. I thought the wind was blowing on the mic.
Do you happen to have a case on your phone? There might be something that taps the case and might be picked up by the speaker as a pop.
Rings, long nails, keys, I don't know the list could go on.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Yes, I do have a soft-shell case. I thought it might be that too, but I took it off and did some test filming and got the same result. This is really starting to tick me off now; I've had the phone for 5 or 6 weeks now and have only noticed this. What a pain!
I have also done voice recording using a voice recorder app, and no problems with that.
I tried a different camera app and the videos still have the popping.
No other suggestions?
Ok, just linking a video so you can hear what I'm talking about, in case it triggers something in someone's brain....
Again, this has happened on stock, as well as CleanRom. Different camera apps used. I've tried with data off. I've tried with SD card out. I've lowered system volume to zero. I've removed the case. There is no such issue when speaking on the phone, nor is it present when using a voice recorder app.
Everything else about the phone is perfect, but I'm ready to smash it to bits over this, I'm so pissed off. :silly:
http://youtu.be/mqvavNARGZU
Maybe your hand?
Sent from my SGH-I317 using xda app-developers app
Nope. Hold the phone by the side. But just to be sure, I've let it sit on its own on the table and same thing.
Mine made that same sound only one time. It was during the inning when my son(5yrs) got 3 unassisted outs. Pissed me off
Sent from my GT-N7105
To narrow down a software VS hardware issue, the first thing you'll want to do is restore to stock. No root, no kernel, no nuffin. If the issue persists, that is usually a purdy good indicator of a hardware issue. Should that be the case, a warranty replacement may be your best option. If the issue persists after a replacement, I'd say its a good bet its something in your environment/situation that is causing the popping.
hapticxchaos said:
To narrow down a software VS hardware issue, the first thing you'll want to do is restore to stock. No root, no kernel, no nuffin. If the issue persists, that is usually a purdy good indicator of a hardware issue. Should that be the case, a warranty replacement may be your best option. If the issue persists after a replacement, I'd say its a good bet its something in your environment/situation that is causing the popping.
Click to expand...
Click to collapse
Thanks for that. Yes, at this point I've tried everything I can think of. I don't believe it has anything to do with environment or anything, as it happens all the time. It has been driving me batty for the last week; I've done nothing but obsess over it. I hadn't noticed it before, but once I had, I started looking at every video I've taken since I bought it and found that it has been going on the whole time. I got the phone at the end of January. One of the first vids I took was a cpl of days later, which I put on youtube. I checked that vid out and sure enough the issue is there.
I called Samsung yesterday and got a UPS shipping label from them to send it in. I'm not keen on having to do all the work to unroot and make like I never rooted it, lose it for up to 3 weeks, and (if they send a replacement back), lose the $30 I spent on my Zagg screen protector.
I guess I will try what you've said; restore to pure stock and pray to God. Thanks!
I've installed CM10 and the camera with it is flawless. Why do you think that is?
Sorry for bumping this up, but I've done all kinds of experimenting and have pretty much determined that it is solely a TW based issue.
But what I'd like to ask now is: using Snap Camera, I get the same result (popping noise). However, Snap Camera has a setting for "Use Alternate Mic", which, when I choose that, there is no popping. So the question is: does anyone know how I can make the stock camcorder use the 'alternate mic' like Snap Camera does?
I have no idea where that would be edited.
Please! Thanks!
velveteen71 said:
I've installed CM10 and the camera with it is flawless. Why do you think that is?
Click to expand...
Click to collapse
Does the camera record stereo sound with cm10 too?
Hello everyone! I have been having literally the worst two weeks trying to get the proximity sensor on my Note II to behave consistently. The sensor does not provide any feedback to the system. Using Android Sensor Box just returns the "No change detected yet" message. I am seriously at wit's end with this. I tried starting over and flashing stock using Odin but it doesn't seem like the kernel is at all affected through that and does not provide reliable results. Sometimes I can flash a stock kernel and the sensor works, but as soon as I either flash a different ROM or flash a different kernel, I am not able to use the sensor. I do not believe it to be the hardware because I have tried two different assemblies with the sensor on it to no avail. Is there anyone that could help? (And yes, I have searched high and low for any kind of guidance on this) I really like this phone, but this is definitely a deal breaker.
Firstly what are you trying to do with the proximity sensor, that is not working for you? Auto brightness, or one of the samsung touchless features?
Thank you for replying. What queued me into the fact that it wasn't working was that my screen does not turn off when I put the phone up to my face during a call. But it doesn't work for any purpose. If it's of any help, the light sensor also does not work, so I'm not able to use things like auto-brightness either.
adrianjayy said:
Thank you for replying. What queued me into the fact that it wasn't working was that my screen does not turn off when I put the phone up to my face during a call. But it doesn't work for any purpose. If it's of any help, the light sensor also does not work, so I'm not able to use things like auto-brightness either.
Click to expand...
Click to collapse
What type of Rom/kernels are you flashing that makes it stop working? AOSP or touchwiz?
Have you tried several, all with the same result?
You're saying that it does work when you run stock as well?
crixley said:
What type of Rom/kernels are you flashing that makes it stop working? AOSP or touchwiz?
Have you tried several, all with the same result?
You're saying that it does work when you run stock as well?
Click to expand...
Click to collapse
Both, I've tried using Perseus, Neak, SOAPKernel and of course stock. The ROM does not matter either, I really intend to use PAC-man RC1 Milestone, but right now I am using the Stock ROM and it is still not working.
adrianjayy said:
Both, I've tried using Perseus, Neak, SOAPKernel and of course stock. The ROM does not matter either, I really intend to use PAC-man RC1 Milestone, but right now I am using the Stock ROM and it is still not working.
Click to expand...
Click to collapse
Sounds like failing hardware man :/
Is your flash counter tripped? Are you still within warranty?
crixley said:
Sounds like failing hardware man :/
Is your flash counter tripped? Are you still within warranty?
Click to expand...
Click to collapse
I have definitely flipped the flash counter, but there's always Triangle Away right? I'm actually totally screwed because I busted my screen a while back and replaced it and the one I got was for an International phone. I guess I could try a third sensor? This is bad news
adrianjayy said:
I have definitely flipped the flash counter, but there's always Triangle Away right? I'm actually totally screwed because I busted my screen a while back and replaced it and the one I got was for an International phone. I guess I could try a third sensor? This is bad news
Click to expand...
Click to collapse
You may have damaged it during the screen swap, or it could maybe just be loose or shorting, which is why occasionally it will work.
crixley said:
You may have damaged it during the screen swap, or it could maybe just be loose or shorting, which is why occasionally it will work.
Click to expand...
Click to collapse
Yeah, I actually was worried that I had damaged it when I opened it in preparation for the screen swap, but I couldn't remember well enough when it exactly stopped working. Thank you much, I should have a new one in by the weekend and then we will know.
adrianjayy said:
Yeah, I actually was worried that I had damaged it when I opened it in preparation for the screen swap, but I couldn't remember well enough when it exactly stopped working. Thank you much, I should have a new one in by the weekend and then we will know.
Click to expand...
Click to collapse
No problem man! I hope it works for you.. Maybe before buying a new one check to see if it's just a loose connection (depending on how electrically savvy you are).
crixley said:
No problem man! I hope it works for you.. Maybe before buying a new one check to see if it's just a loose connection (depending on how electrically savvy you are).
Click to expand...
Click to collapse
Okay so my mind is officially blown. Replaced the sensor with a new one and still not getting any feedback from either sensor. I really still do think it's something about the kernel, but because I have limited knowledge of these things, I am probably not the best person to diagnose the issue
The issue is definitely that the sensor just does not turn on, which is odd because the camera works. I found a thread with some proximity sensor calibration stuff but it is a bit over my head.
adrianjayy said:
Okay so my mind is officially blown. Replaced the sensor with a new one and still not getting any feedback from either sensor. I really still do think it's something about the kernel, but because I have limited knowledge of these things, I am probably not the best person to diagnose the issue
Click to expand...
Click to collapse
I find that strange though if you have tried several, all with the same issue
i am having the same issue, except tha also notification led will not work on stock roms but it will work on cm roms.
So, just a conclusion on this issue. I decided to just transplant the sticker from the original screen I had and exchange this phone using its warranty. When I was preparing the phone to return to the device support center, when I flashed back to stock and had already Triangle Away'd, the sensor did turn on and was recognized in the *#0*# diagnostic screen, but it still did not turn the screen off during calls and Motions were still not functioning. So, ultimately, no real solution in my case.
:good:
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can which perfume was over and it was only pressing Gas OFF!! :good::good::good:
Hey all,
i have some problem, with my camera, i noticed that on the photos there are some grain or noise a lot.. Its only for me ?
Please help!
marvelfreak said:
Hey all,
i have some problem, with my camera, i noticed that on the photos there are some grain or noise a lot.. Its only for me ?
Please help!
Click to expand...
Click to collapse
I have a similar problem. Curious, though. have you opened camera, settings, and at the bottom of the list, reset?
chip.hughes said:
I have a similar problem. Curious, though. have you opened camera, settings, and at the bottom of the list, reset?
Click to expand...
Click to collapse
Jap, i also try that, nothing changed..
Picture actually looks pretty good for it to be a low light indoor shot. Plus your computer monitor casts a light bleed on your picture. Have to remember this is a camera on a phone and not a high end dslr camera. So pictures in low light can always come out bad and grainy.
Sent from my HTC6500LVW using Tapatalk
Grain in dark pictures are expected. I have a canon 5d mkIII and even with a full-framed sensor, it'll still pick up some grain. Our phone does pretty well for the size of the sensor. Wouldn't sweat it unless the purple hue attacks
This is a well-documented issue with the One.
HTC says it should be fixed in software on the 4.3 update. I'm not 100% convinced. If it's not fixed, I'll be getting rid of the phone. My low-light pictures are awful compared to other phones I've owned.
As for the Canon guy.. I'm sure you have way more settings you can change over the phone's setting to make your 5D pics better
Thank you guys for yours answers,i will play again with my phone's camera's settings. I thought that the Ultrapixell kamera is perfect in low-light. i as wrong..
dbornack said:
This is a well-documented issue with the One.
HTC says it should be fixed in software on the 4.3 update. I'm not 100% convinced. If it's not fixed, I'll be getting rid of the phone. My low-light pictures are awful compared to other phones I've owned.
As for the Canon guy.. I'm sure you have way more settings you can change over the phone's setting to make your 5D pics better
Click to expand...
Click to collapse
I didn't know the grainy pics was "well documented." I only know of the purple hue issue. If I use the night setting it helps a lot and I've been pleased with the pics, better than my S4 in many settings.
I suppose you could try night mode, maybe with a low iso to see how your pics look.
Sent from my HTC6500LVW using Tapatalk
mlin said:
I didn't know the grainy pics was "well documented." I only know of the purple hue issue. If I use the night setting it helps a lot and I've been pleased with the pics, better than my S4 in many settings.
I suppose you could try night mode, maybe with a low iso to see how your pics look.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Search "htc one camera issue" and you will get a google's worth of results of discussions on the topic.
Purple Hue and Grainy are pretty much the same issue, or I have both issues with two HTC Ones now. I tried every setting in the book. Nothing made it better. Night mode made them blurry on top of it, as I'm holding the phone at a very slow shutter speed, this was expected. Tried ISO as well. It just sucks.
dbornack said:
Search "htc one camera issue" and you will get a google's worth of results of discussions on the topic.
Purple Hue and Grainy are pretty much the same issue, or I have both issues with two HTC Ones now. I tried every setting in the book. Nothing made it better. Night mode made them blurry on top of it, as I'm holding the phone at a very slow shutter speed, this was expected. Tried ISO as well. It just sucks.
Click to expand...
Click to collapse
I agree one hundred percent. I envy those of you that do not have this issue. I purchased mine second hand. To my knowledge, the warranty is non-transferable. Just hoping that the Verizon update will patch this, if it is not straight up hardware. I tried the 4.3 roms, but they are ports, and this probably goes deeper than just a surface flash.
If I may be so bold, please allow me to share my experience. I was having an issue with grainy pictures. When I covered my lens it would turn red. I sent a support request to HTC. They gave me the runaround for about 2 weeks saying to wait for 4.3, the software will fix it. Then they told me to use third-party camera apps. Eventually I got mad, closed the ticket. I sat there and fumed and then walked away. A day later I got a "tell us how we did" email. I laced into them and told them that I had a bad experience, that my camera is clearly defective and being told to use third-party apps that still have the issue isn't a fix. I got a response back and they asked if I had considered sending it for repair. I told them that I had never been given that option. The guy told me he was going to call me and he did. We talked for about 5 minutes, he took my info, he sounded like a cool guy. We joked a bit. He offered to pay shipping into HTC. I sent it in.
I got it back today. It's a night and day difference. It's actually catches focus like it should. When I cover the lens it stays jet black. It's a big difference. Send it back. Let them fix it. It sucked to be without it but it took them about a week round trip. It was worth it.
one4thewings said:
If I may be so bold, please allow me to share my experience. I was having an issue with grainy pictures. When I covered my lens it would turn red. I sent a support request to HTC. They gave me the runaround for about 2 weeks saying to wait for 4.3, the software will fix it. Then they told me to use third-party camera apps. Eventually I got mad, closed the ticket. I sat there and fumed and then walked away. A day later I got a "tell us how we did" email. I laced into them and told them that I had a bad experience, that my camera is clearly defective and being told to use third-party apps that still have the issue isn't a fix. I got a response back and they asked if I had considered sending it for repair. I told them that I had never been given that option. The guy told me he was going to call me and he did. We talked for about 5 minutes, he took my info, he sounded like a cool guy. We joked a bit. He offered to pay shipping into HTC. I sent it in.
I got it back today. It's a night and day difference. It's actually catches focus like it should. When I cover the lens it stays jet black. It's a big difference. Send it back. Let them fix it. It sucked to be without it but it took them about a week round trip. It was worth it.
Click to expand...
Click to collapse
What did they "fix"? Did they state that in the repair documents? Are you still on the current OTA release of software? I'm wondering what the fixed for free that is the root of the actual problem.
I'm on my 3rd phone in 7 weeks now (for other issues than the camera), and I still have the issue.
dbornack said:
What did they "fix"? Did they state that in the repair documents? Are you still on the current OTA release of software? I'm wondering what the fixed for free that is the root of the actual problem.
I'm on my 3rd phone in 7 weeks now (for other issues than the camera), and I still have the issue.
Click to expand...
Click to collapse
They didn't share any repair document with me at all. They just shipped my phone back in a "gift" box with a screen rag. No documentation at all. I have to assume that they replaced or repaired the camera sensor. A month or so back there was a link in the forums about trying to narrow down if it was a sensor issue or not. They had us record the camera sensor version. It involved finding a particular file and then opening it in a text file. In any case, even then with only like 35-40 responses there were at least 9 different camera sensor versions. Also, my camera seemed ridiculously sensitive to motion. I don't have the most steady hands but I also don't have seizures every time I take a picture either. The old camera (or firmware) seemed to exaggerate any motion.
As for the OTA, I sent it to them with OTA .8. They shipped it back .10. I've since flashed NuSenseONE but I have a TWRP backup of the ROM as it arrived back to me.. plus logging into a few things. If there is anything in particular that you are interested in, such as a file version or something, let me know.
one4thewings said:
They didn't share any repair document with me at all. They just shipped my phone back in a "gift" box with a screen rag. No documentation at all. I have to assume that they replaced or repaired the camera sensor. A month or so back there was a link in the forums about trying to narrow down if it was a sensor issue or not. They had us record the camera sensor version. It involved finding a particular file and then opening it in a text file. In any case, even then with only like 35-40 responses there were at least 9 different camera sensor versions. Also, my camera seemed ridiculously sensitive to motion. I don't have the most steady hands but I also don't have seizures every time I take a picture either. The old camera (or firmware) seemed to exaggerate any motion.
As for the OTA, I sent it to them with OTA .8. They shipped it back .10. I've since flashed NuSenseONE but I have a TWRP backup of the ROM as it arrived back to me.. plus logging into a few things. If there is anything in particular that you are interested in, such as a file version or something, let me know.
Click to expand...
Click to collapse
Nothing I'm particularly interested in. I was wondering if they owned up to it being software or hardware. I too, went through calling HTC, explaining the issue, going through an hours worth of diagnostics on my phone, before they told me it would be fixed in 4.3 release. Perhaps they have a 4.3 release that includes a camera sensor firmware update as well? Are are you suggesting that the camera versions are 9 different versions of hardware?
I don't know.. the camera on here just isn't what it's cracked up to be. It's great in PERFECT conditions, but sub-standard when not in perfect conditions.
dbornack said:
Nothing I'm particularly interested in. I was wondering if they owned up to it being software or hardware. I too, went through calling HTC, explaining the issue, going through an hours worth of diagnostics on my phone, before they told me it would be fixed in 4.3 release. Perhaps they have a 4.3 release that includes a camera sensor firmware update as well? Are are you suggesting that the camera versions are 9 different versions of hardware?
I don't know.. the camera on here just isn't what it's cracked up to be. It's great in PERFECT conditions, but sub-standard when not in perfect conditions.
Click to expand...
Click to collapse
I'm not at all sure what I'm suggesting now. I just went back to that survey and looked through the results, and it looks like there are literally 100's of different possible results from that sensors file. What I did find that is probably of no value at all is that my phone, before it was serviced had the following text in the sensor text file:
Before servicing:
st vd6869(1.0) cinesensor 2013-04-29
After servicing:
st vd6869(1.0) cinesensor 2013-09-16
I don't know if that is just a firmware revision, or the manufacturing date of the sensor itself, but if you look in that link to the survey results there are probably 50 different dates.
Here is something that may be of interest to you. The guy who started the thread mentioned sending it in to repair and they sent him the work order. They replaced his camera with a SHARP sensor and the results he posts are far superior to what he had before. Link here
Is this admission of guilt or just a result of part shortage? Or just typical hardware phase-out/phase-in.
one4thewings said:
I'm not at all sure what I'm suggesting now. I just went back to that survey and looked through the results, and it looks like there are literally 100's of different possible results from that sensors file. What I did find that is probably of no value at all is that my phone, before it was serviced had the following text in the sensor text file:
Before servicing:
st vd6869(1.0) cinesensor 2013-04-29
After servicing:
st vd6869(1.0) cinesensor 2013-09-16
I don't know if that is just a firmware revision, or the manufacturing date of the sensor itself, but if you look in that link to the survey results there are probably 50 different dates.
Here is something that may be of interest to you. The guy who started the thread mentioned sending it in to repair and they sent him the work order. They replaced his camera with a SHARP sensor and the results he posts are far superior to what he had before. Link here
Is this admission of guilt or just a result of part shortage? Or just typical hardware phase-out/phase-in.
Click to expand...
Click to collapse
Wow.. I just checked that thread out, and will be calling HTC soon to get a replacement. That's night and day difference, and his before results are similar to mine. It's ruined some experiences in which I thought I would have a good enough phone to captures memories..
dbornack said:
Wow.. I just checked that thread out, and will be calling HTC soon to get a replacement. That's night and day difference, and his before results are similar to mine. It's ruined some experiences in which I thought I would have a good enough phone to captures memories..
Click to expand...
Click to collapse
I'm glad it helped. I hope they get it swapped out for you and you finally have the camera that you bargained on. I know I'm far happier with my results.
one4thewings said:
I'm glad it helped. I hope they get it swapped out for you and you finally have the camera that you bargained on. I know I'm far happier with my results.
Click to expand...
Click to collapse
Also, how do you find out what version you have?
dbornack said:
Also, how do you find out what version you have?
Click to expand...
Click to collapse
These are the directions I followed from the original survey post:
Use ES File Explorer to find camera module manufacturer (does not have to be rooted). Navigate: Device > sys > android_camera > sensor Open this file as text (eg. st vd6869(1.0) cinesensor 2013-05-10)
Click to expand...
Click to collapse
one4thewings said:
These are the directions I followed from the original survey post:
Click to expand...
Click to collapse
st vd6869 (1.0) cinesensor 2013-06-07
So yeah, pretty old it seems.
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.