After playing with it for a week now I can more or less confirm that the LED flash in our Note II is not as strong as I had on my S II. The images taken with flash at complete dark is not as bright as before. Say it's decreased by some 20%.
What about you guys? Any workaround or that's how it is?
TIA.
i've still got my sgs2 and i'd say you're right. not a massive difference but enough to notice.
Can you not see it or something? I don't think anyone needs a 1000 watt notification LED, no?
no, but it shouldn't be a downgrade. a pic taken with the sgs2 in low light will be better than the note 2 due to the note not having a bright enough flash. hell, the note 2 might not even take the photo as it could be too dark to focus properly.
it's not huge, but it is an issue.
ericshmerick said:
Can you not see it or something? I don't think anyone needs a 1000 watt notification LED, no?
Click to expand...
Click to collapse
Hes talking about the camera LED flash not the notification light
tommo123 said:
i've still got my sgs2 and i'd say you're right. not a massive difference but enough to notice.
Click to expand...
Click to collapse
So it is an issue then. Hardware most probably? They changed the led unit or something?
Sent from my GT-N7100
or maybe the power supplied to it? who knows. either way it's not huge (for me). in 18 months i never took a photo with my sgs2 where i needed the flash so unlikely to bother me. i used it as a torch tbh since i'm weird and don't change lightbulbs in my house
Okay, but it shouldn't be like this. I mean it's a premium phone after all. It should've been as strong as S2, if not stronger.
Btw- When you use it as torch, is it bright enough like S2, or you notice the dimness there too?
Sent from my GT-N7100
that's how i tested it when i read ths thread. there's a diff.
Yup, right. Coming from S3, I can tell that its not as strong as S3 led flash. Not cool at all.. Dont know why Samsung design it this way ? ..
yogi7272 said:
Yup, right. Coming from S3, I can tell that its not as strong as S3 led flash. Not cool at all.. Dont know why Samsung design it this way ? ..
Click to expand...
Click to collapse
I can answer this one...! its simple - to keep costs down...
Bobo
probably. if you take a lot of low light photos it will be an issue though
led flash is broken
hi when i try to find a solution about my problem and google showed this page so can you help me ? i had the galaxy note 2 and i dropped it first day i have it. then i realised the led flash stopped working. (i don't know if it's working before but it was the day i have it from a foreign land so there's no warranty of it) i hope you to help me to repair it. should i replace the led flash or is it connected to a flex cable ? and where can i get a new one ? i've disassembly galaxy s i9000 before i know how ir's like and i can do it again but it is problem that getting the replacement staff. try to help me if you know something about this please. thanks
cemosir said:
hi when i try to find a solution about my problem and google showed this page so can you help me ? i had the galaxy note 2 and i dropped it first day i have it. then i realised the led flash stopped working. (i don't know if it's working before but it was the day i have it from a foreign land so there's no warranty of it) i hope you to help me to repair it. should i replace the led flash or is it connected to a flex cable ? and where can i get a new one ? i've disassembly galaxy s i9000 before i know how ir's like and i can do it again but it is problem that getting the replacement staff. try to help me if you know something about this please. thanks
Click to expand...
Click to collapse
You should probably get it to a computer repair shop or if possible, Samsung. With or without warranty.
You don't wanna mess with the hardware so quickly even if you nearly know what you are doing :good:
jujuburi said:
After playing with it for a week now I can more or less confirm that the LED flash in our Note II is not as strong as I had on my S II. The images taken with flash at complete dark is not as bright as before. Say it's decreased by some 20%.
What about you guys? Any workaround or that's how it is?
TIA.
Click to expand...
Click to collapse
For some reason, the flash is not full strength with stock samsung widgets (assistive light) Download app called "led light." Night and day difference.
https://play.google.com/store/apps/details?id=jp.picolyl.led_light
yogi7272 said:
Yup, right. Coming from S3, I can tell that its not as strong as S3 led flash. Not cool at all.. Dont know why Samsung design it this way ? ..
Click to expand...
Click to collapse
Correction.. The led flash is very strong. Just use any third party app like tiny flashlight & led and see the difference. Samsung have set it at a lower intensity when used with stock torch widget.
boodies said:
For some reason, the flash is not full strength with stock samsung widgets (assistive light) Download app called "led light." Night and day difference.
https://play.google.com/store/apps/details?id=jp.picolyl.led_light
Click to expand...
Click to collapse
Yeah, we all know that by now. I always use the app called Tiny Flashlight + LED. And yes, there is heaven and hell difference.
yogi7272 said:
Correction.. The led flash is very strong. Just use any third party app like tiny flashlight & led and see the difference. Samsung have set it at a lower intensity when used with stock torch widget.
Click to expand...
Click to collapse
Nope, it's still weaker than S3 or S2. And I don't think the the bright LED which comes out by using a third party app is same when you use it for camera flash, it's always weaker.
Sent from my GT-N7100
So far, after flashing Hypermod rom based on 4.2, the camera flash certainly seems alot brighter than when on sammy roms, I personally think that samsung did this on purpose for whatever reason
Sent from my GT-N7100 using xda premium
Related
So I'm sure SOME of you must have noticed that the Galaxy Nexus screen isn't as sensitive as.. lets say Nexus S or S2.
If you check, the pressure required to get a touch registered is around 0.30. This value is much lower on other phones (like about 0.15 on Nexus S).
There were apps for Galaxy S that fixed screen sensitivity issues.. What I'm wondering is, is there any such app for the Galaxy Nexus?
Well yes, check out my thread about it.
http://forum.xda-developers.com/showthread.php?t=1576739&goto=newpost
However I'm fine with 0.30, I can get to 0.28 even. But there is a bug after a few minuted of use it decreases and stops detecting values below 0.40. Locking the screen temporarily resets it. Someone should dig tgru the kernel code to see if we can change this.
Interesting. Maybe that's why I miss keys while typing. Seemed my G2x was great in this regard.
Sent from my Galaxy Nexus using xda premium
Its weird how none of the developers have paid attention to this. These sensitivity values should be fixable by them no? It would be great if someone can pay attention to this.
player911 said:
Interesting. Maybe that's why I miss keys while typing. Seemed my G2x was great in this regard.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I miss tons of key presses, so probably yes. When I lock then unlock the screen I miss none and its super sensitive again. Its like night and day difference.
---------- Post added at 06:27 AM ---------- Previous post was at 06:26 AM ----------
ASKnASK said:
Its weird how none of the developers have paid attention to this. These sensitivity values should be fixable by them no? It would be great if someone can pay attention to this.
Click to expand...
Click to collapse
I think this is a very hard issue to diagnose. Must be some type of memory leak or something.
I have been noticing this more and more.. hope some dev figures out a way to up the sensitivity!
this mod will help with sensitivity, its made for the galaxy s but it works for the nexus. it can change the sensitivity, minimum motion and duration to register touch. you need root for this.
Anyone know where these settings are located so they can be change without the app?
https://play.google.com/store/apps/...Nob3A0YXBwcy50b3VjaHNjcmVlbmJvb3N0ZXIuY29tIl0
I've don't know if I experience the same issues you guys talk about but sometimes I can't use the softkeys. Like they're unresponsive... I have to pick up me GN or wait for a good 4 to 6 seconds before it registers my touch. I have no idea if it's because of the touch issue you guys are talking about. But has anybody any idea what causes this or if I'm on a totally different issue here?
Sent from my Galaxy Nexus
neotekz said:
this mod will help with sensitivity, its made for the galaxy s but it works for the nexus. it can change the sensitivity, minimum motion and duration to register touch. you need root for this.
Anyone know where these settings are located so they can be change without the app?
https://play.google.com/store/apps/...Nob3A0YXBwcy50b3VjaHNjcmVlbmJvb3N0ZXIuY29tIl0
Click to expand...
Click to collapse
I'm 99% sure this has no effect beyond placebo for the Galaxy Nexus. I installed it, thoroughly tried it out going back and forth between the options, and there was no increase in sensitivity. Light touches were still being missed.
neotekz said:
this mod will help with sensitivity, its made for the galaxy s but it works for the nexus. it can change the sensitivity, minimum motion and duration to register touch. you need root for this.
Anyone know where these settings are located so they can be change without the app?
https://play.google.com/store/apps/...Nob3A0YXBwcy50b3VjaHNjcmVlbmJvb3N0ZXIuY29tIl0
Click to expand...
Click to collapse
bengrulz said:
I'm 99% sure this has no effect beyond placebo for the Galaxy Nexus. I installed it, thoroughly tried it out going back and forth between the options, and there was no increase in sensitivity. Light touches were still being missed.
Click to expand...
Click to collapse
Placebo it is.
It doesn't work for the GNexus, though it DOES work for the Nexus S (reviews).
I wish someone would fix this :s
How light are you guys pressing the screen?
I have a clear coat shield on and Im typing this post as light as possible and don't seem to have a problem at all.
Sent from my Galaxy Nexus using xda premium
ASKnASK said:
Its weird how none of the developers have paid attention to this. These sensitivity values should be fixable by them no? It would be great if someone can pay attention to this.
Click to expand...
Click to collapse
Because we don't see the issue?
natious said:
How light are you guys pressing the screen?
I have a clear coat shield on and Im typing this post as light as possible and don't seem to have a problem at all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My phone responds to the touch of the skin on my leg, through my jeans pocket.
natious said:
How light are you guys pressing the screen?
I have a clear coat shield on and Im typing this post as light as possible and don't seem to have a problem at all.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm pressing the screen EXTREMELY light, like barely touch inputs. When I do fast typing the finger tips kinda fly around on each letter.
It works fine and just as accurate as normal. Then the bug kicks in and the sensitivity reduces and suddenly misses about 50% of the presses. It feels mushy. Lock the screen and it fixes it back to normal. It must be some memory leak type issue.
How do you know it isn't a memory leak with an installed application?
adrynalyne said:
How do you know it isn't a memory leak with an installed application?
Click to expand...
Click to collapse
are you saying your gnex have not this issue?
please can you make a test?
go to dev setting and enable 'pointer location'; on up/dx of the screen you have 'prs' ... pressure of every your touch... try to register a touch at 0.30 or less pressure.... it's not possible, i think 0.27/0.28 is the limit... lighter touch don't register (gs2 or NS register this kind of touch)
Exactly, 0.28 is the best I can register. When the bug kicks in, suddenly you can't register below 0.40 or 0.45, no matter how much you try. Lock the screen and it fixes itself. So frustrating.
Lowest I got was 0.27 after playing with it for a minute or so. Anyways, I don't really notice a difference coming from an LG G2x. I guess there is, but I'm assuming I always press hard enough that I don't notice.
As to the other bug of not registering under .40 or higher, never had it. Running AOKP 37 + Franco M3 if that makes a difference.
I've the same problem with my 24h new Nexus are there devices without this bug ?
Inviato dal mio Galaxy Nexus con Tapatalk 2
I am having this exact same issue. Upon initial unlocking the deice registers key presses smoothly and will continue to do so until a lull of interaction. One the device is inactive but the screen remains on the screen comes highly unresponsive. I would say that those who are not experiencing on their stock devices probably have their screen lockout time low enough that the bug does not have time to appear prior to the phone requiring it be unlocked anew.
I have a 32 GiB Stock Nexus 7 running 4.1.1 Build JRO03D.
My screen timeout is set to 10 minutes.
Is the rattle sound I hear near the camera housing on my S3 normal? Everything seems to be working fine. Just making sure and asking here since this is the only place where I can get real answers.
Thank you all,
AJ
That doesn't sound normal to me... there is no noticeable rattle on either of the Galaxy S III's I have access to. How long have you had the phone for?
kennkcna said:
That doesn't sound normal to me... there is no noticeable rattle on either of the Galaxy S III's I have access to. How long have you had the phone for?
Click to expand...
Click to collapse
about 5 months. My old S2 had it too. Someone told me a long time ago that it was the Auto Focus and that it was normal on it.
On my moto photon the lens rattles. If you start the camera app it stops.
Sent from my MB855 using xda premium
So this would be considered normal then? I'm hoping so LOL.
asjdwf said:
about 5 months. My old S2 had it too. Someone told me a long time ago that it was the Auto Focus and that it was normal on it.
Click to expand...
Click to collapse
I just double checked, my old Galaxy S II LTE (aka Skyrocket) has a noticeable rattle when you shake it but I'm not hearing it on the S III (perhaps it's more subdued?). A quick Google search however shows that several other people have experienced the same thing and the general consensus seems to be that it's nothing to worry over.
kennkcna said:
I just double checked, my old Galaxy S II LTE (aka Skyrocket) has a noticeable rattle when you shake it but I'm not hearing it on the S III (perhaps it's more subdued?). A quick Google search however shows that several other people have experienced the same thing and the general consensus seems to be that it's nothing to worry over.
Click to expand...
Click to collapse
Yeah I just finished looking too. Thanks all
AJ
Try dropping it a few times see if the rattle will stop
Sent from my SAMSUNG-SGH-I747 using xda premium
So it comes and goes now. Checked some of my buddies phones and there's don't do it but the att stores s3's all do it. So frustrating. LOL
This plus I can't upgrade to Jellybean because it kills data connection to my phone and battery drain!!
AHHHH
AJ
Send it in if ur not happy,, dosens samsung give u a year manufacturer warranty?
sent from outside ur window
I just shook my phone and heard the power button rattling back and forth. Put you finger on it and it stops.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Sorry if this has been asked. I haven't been on since I return mine 2 months ago.
Just wondering if anyone fixed this yet?
( When I flash root and watch videos in the dark and the brightness is set to low, blacks on the screen would get a reddish tint to them. )
I dont have this problem. . U sure ur screen isnt defective?
Sent from my GT-I9505 using xda app-developers app
pezlomd said:
I dont have this problem. . U sure ur screen isnt defective?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Dont know, but some other people had the same issue as me.
I got a new GS4 today, but havent tested it i'm screwed it will happen again.
It would only happen after I would root the phone. It work normal when it was running the stock rom.
I have the same issue. It dose it when I scroll in the Greyed out parts of the settings menu or any time the screen is dark
Sent from my SGH-M919 using Tapatalk 4 Beta
i have a pink tint on my mine top screen =( i already exchanged it 3 times and all 3 have the same problem but in different places of the screen ....
T mobile says I can Warrenty it. I'll report back when the new one gets here
Sent from my SGH-M919 using Tapatalk 2
Yeah I just did an exchange today behind this issue. I'm debating on whether to exchange again, or just deal with it. Just chiming in verifying with others this issue exist in some units.
I'm just sayin
---------- Post added at 09:12 AM ---------- Previous post was at 09:08 AM ----------
omf05 said:
Dont know, but some other people had the same issue as me.
I got a new GS4 today, but havent tested it i'm screwed it will happen again.
It would only happen after I would root the phone. It work normal when it was running the stock rom.
Click to expand...
Click to collapse
If this only happened to you after rooting and changing roms, then your issue is not hardware.
I'm just sayin
I got a new one last week and there was no longer an issue with it.
I'm now able to root/flash and the Black are pitch Blacks!
Hope you all get this fixed I know how annoying it can be!
I've never noticed the issue, but i hate the distorted colours on stock. Whites arent white, and colours all seem off tinted. Its something i only noticed on my Galaxy S3 when i first got the ability to use Trinity Colour settings. Since then and when i first got my S4, the first thing i did was flash with Trinity Colours on cool settings, and it just makes the colours soooo much more real and vibrant and clear. It fixes the display and gives you that true colour experience that stock lacks. I find the default colours are more offset with a yellowish tint though, which looks terrible in my eyes.
omf05 said:
I got a new one last week and there was no longer an issue with it.
I'm now able to root/flash and the Black are pitch Blacks!
Hope you all get this fixed I know how annoying it can be!
Click to expand...
Click to collapse
Would you please state the production date and where it was manufactured please.
I'm just sayin
I just did my 3rd exchange today and stubble upon one that I'm sound with.
I'm just sayin
I got my exchange this week. .. Still looks the same
Sent from my SGH-M919 using Tapatalk 4 Beta
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:
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.