Add another proximity sensor issue to the list - Galaxy Note 3 Q&A, Help & Troubleshooting

I read a few posts on here about the proximaty sensor not working on the Note 3. Well mine is a little different, My screen stays on even when I put the phone to my head. It started doing this just today, so well out of my 14 day return period.

Limeybastard said:
I read a few posts on here about the proximaty sensor not working on the Note 3. Well mine is a little different, My screen stays on even when I put the phone to my head. It started doing this just today, so well out of my 14 day return period.
Click to expand...
Click to collapse
Assumption that you have a clean screen and that you haven't flashed some ROM that could be the problem instead of the actual hardware.

Screen protector not covering sensor.......?

Bizzare rebooted, its all working now. Not rooted.

Related

Proximity Sensor ADC Value - Please Weight In

My current Note has the proximity senor issue where it thinks my face is to the phone all the time and therefore gestures don't work and the screen goes black instantly when making a call. This has been outlined in a few threads. Here are two good ones:
This post has actual values for ADC:
http://forums.androidcentral.com/sa...-sensor-issue-during-calls-3.html#post3234634
Another with the same problem:
http://forum.xda-developers.com/showthread.php?t=2520118
I looked at a new note today that Bell is going to let me exchange my current note for. Its value with nothing close to it is about 30.
I would like to know what other peoples ADC values are. Simply enter *#0*# into your dialer, then choose sensors and you will see the ADC value with the proximity sensor. Could you please report that value with nothing close to the screen.
I'm trying to determine what the normal ADC value should be on a new working phone so I can figure out if the new phone (that has an ADC value of 30) is ok or not.
Thanks and hopefully this will help out other people.
Mine seems to stay at 33-35 until about 20cm away from the screen then starts increasing.
I don't have any problem what so ever with the screen turning off/on when calling. Not even once failed.
My values for ADC are 0, constantly 0, if nothing in front of the device. If i approximate my hand it starts increasing, and then the screen turns green and the phone vibrates when the proximity sensor goes from 0 to 1. If i put my finger on top of the sensor it stays at ADC 1003.
Is this how it is supposed to work?
N9005 with MJ7 firmware.
Mine is always below 10 if nothing is in front. Fluctuate between 5 and 9.
Sent from my SM-N9005 using XDA Premium 4 mobile app
My ADC values fluctuate between 30 - 34. @antt00, how come yours so low?
My first note idiled at around 29-30. My second replacement note idles between 0-1. I had proximity problems with my S4 so I check it religiously. While values around 30 would be okay for now, but you may run into problems later. The problems come when you have some dust that gets stuck inside on the sensor and causes a higher adc value. This is what causes the sensor to not work correctly. I have to take apart my S4 every 3 month or so just the clean it and then the number will drop back down to 6. Also keep in mind, the reading goes up a bit in direct sunlight. IMO I would get one that idles around 0, this will give you more headroom for dust.
Thanks for the feedback. I didn't get a chance to read all the posts before I went and got an exchange. For some reason their system let me exchange it even though I past 15 days so I kind of jumped on the chance. The new note at home reads around 20. Not as low as some but better then what I returned. I'll have to see how long it lasts and I'll keep and eye on it. It definitely sounds like its a combination of possibly bad/poor sensors. Dust build up inside which is a design flaw. And maybe poor calibration from samsung as it look like from a post I've see that you can re-calibrate the sensor, though I not sure if that may have some negative effects.
I didn't try and push them to let me cherry pick a phone, they were nice enough to let me check the ADC value and firmware version before the exchange. Hopefully this one works out or I'll have to try and get a better one. I'll see in time as my previous one definitely had the dust issue. It was pretty obvious because I could lower the ADC value if I blew compressed air in the ear piece.
i did notice the proximity sensor screwing around on phone calls, it would delay getting the screen back after distancing from it...
the procedure you gave me shows ADC values contentiously flipping from 9 to/through 13 (sometimes chronologically)
putting your hand over seems to green-out the window showing that proximity is working, nice, however, im having shadow greens, meaning, just leaving it on the table, once a minute it goes green, yet nothing moves over it...strange.
ps, no plastic cover used, dont see a reason to use protection with this quality
williamyi said:
My ADC values fluctuate between 30 - 34. @antt00, how come yours so low?
Click to expand...
Click to collapse
I have no idea.
Sent from my SM-N9005 using XDA Premium 4 mobile app
antt00 said:
I have no idea.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you applied the glass m sp gotten from Alex?
Sent from my SM-N9005 using XDA Premium 4 mobile app
williamyi said:
Have you applied the glass m sp gotten from Alex?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes but that does not obstruct the sensor. It only reaches below it.
Idling 0 with and without direct artificial light (no tested against sunlight). As my palm gets closer the number progressively increases. The screen turns green after reaching 120
I had no idea that a proper cleaning could fix the sensor. Thanks for the info
iiSo say we all!! From my Note 3 (N9005)
Well now I'm at about ADC 40. In two days the value has doubled. I can't win....
I have this problem with my AT&T N900A and the ADC value is between 82 and 85 at idle. If I wave my hand over the sensor it will go to 1000 but unfortunately its still not responding when I pull the phone from my face after a phone call.
I'm not rooted so I'm not going to manually adjust anything. Is the fix just to get another phone. This is sort of pissing me off. I've had 6 or so Samsung phones and never a problem so frustrating as this one.
And now I'm at ADC 90 and when I activate the sensor (screen goes green and vibrates) it won't stop when I move my hand away. There must be a serious design flaw that allows dust to get onto the sensor. Unfortunately I don't see any way to solve this....I don't know how many times I can return the phone and hope to get one that doesn't allow dust in. I guess the next step is to try and talk to Samsung.....
Has anyone gone as far as to replace the sensor? There is a part out there. Its listed as a 9000/9005 part, not sure if it works with US carrier models. I'm having a hard time finding it in stock anywhere though.
http://rounded.com/samsung-galaxy-note-3-n9005-front-camera-proximity-sensor.html?sl=EN
I have zero desire to send my device to a Samsung service center. I'd have to order a phone to use in the mean time until it came back. I'd rather just swap a new part in.
0/0/0
when i move one hand about 14-16cm above the device (and move it closer to it) the numbers start to increase
aygriffith said:
Has anyone gone as far as to replace the sensor? There is a part out there. Its listed as a 9000/9005 part, not sure if it works with US carrier models. I'm having a hard time finding it in stock anywhere though.
http://rounded.com/samsung-galaxy-note-3-n9005-front-camera-proximity-sensor.html?sl=EN
I have zero desire to send my device to a Samsung service center. I'd have to order a phone to use in the mean time until it came back. I'd rather just swap a new part in.
Click to expand...
Click to collapse
I have a strong feeling that its just dust getting in the way. I was at ADC 90, blew air at the ear piece and it dropped to ADC 60. Though I don't know how it looks like inside. I have a feeling some are sealing out the dust completely and some are not.
I do find it odd though that mine started out from factory at ADC 30
bnevets27 said:
I have a strong feeling that its just dust getting in the way. I was at ADC 90, blew air at the ear piece and it dropped to ADC 60. Though I don't know how it looks like inside. I have a feeling some are sealing out the dust completely and some are not.
I do find it odd though that mine started out from factory at ADC 30
Click to expand...
Click to collapse
I'm not really satisfied with the idea of periodically blowing into the ear piece of the phone with a can of air I don't regularly have otherwise. They need to accommodate the issue with a software fix for the sensor sensitivity if they can't fix the manufacturing process.
Sent from my Nexus 7 using Tapatalk 4
Now I'm ADC 99 and my screen doesn't turn on or off properly again. Haven't had a chance to call Samsung yet but this is really annoying. I also don't want return it and get a phone with the new bootloader. Ugh

touch screen problems?

I have a small line on my screen that is unresponsive. It goes straight across the top of the screen exactly where the install button is in the play store (about 1" from top of screen at roughly 1/4" thick). Its in a pretty awkward spot and causes a lot of problems. For some reason it has also disabled the tap to wake feature of my phone.
I installed the "Touch Test" app which shows that my entire touch screen is working. However it shows the phone recognizing 2 pointers (touches) being active whenever I touch that area of my screen. I've been having this problem for 2 or 3 months now and all of a sudden today on my lunch break it went away. I was able to tap to wake the screen (worked perfectly the 20 or so times I attempted it), I was also able to hit the install button in the play store and life was great... Or so I thought. A few hours later on my next break my phone went back to annoying piece of junk that I completely dislike using.
Now I dont know exactly when this started happening. I did notice it sometime soon after the 4.4 update, and flashing a custom rom/kernel has made no improvement. Anyone got any ideas? I loved this phone before this started, and my phone is so frustrating now that I completely disrespect the thing and have scratched the crap out of the screen. I'm really hoping this can be fixed so I can go on with enjoying whatever life I have left with the g2, if not I'll probably just abuse it until it breaks then switch over to a water proof z2 or something along those lines... Phone was very well taken care of before the problem started, wasnt dropped or exposed to water (other then using outside in the rain for a few min at a time)
mikeinaus said:
I have a small line on my screen that is unresponsive. It goes straight across the top of the screen exactly where the install button is in the play store (about 1" from top of screen at roughly 1/4" thick). Its in a pretty awkward spot and causes a lot of problems. For some reason it has also disabled the tap to wake feature of my phone.
I installed the "Touch Test" app which shows that my entire touch screen is working. However it shows the phone recognizing 2 pointers (touches) being active whenever I touch that area of my screen. I've been having this problem for 2 or 3 months now and all of a sudden today on my lunch break it went away. I was able to tap to wake the screen (worked perfectly the 20 or so times I attempted it), I was also able to hit the install button in the play store and life was great... Or so I thought. A few hours later on my next break my phone went back to annoying piece of junk that I completely dislike using.
Now I dont know exactly when this started happening. I did notice it sometime soon after the 4.4 update, and flashing a custom rom/kernel has made no improvement. Anyone got any ideas? I loved this phone before this started, and my phone is so frustrating now that I completely disrespect the thing and have scratched the crap out of the screen. I'm really hoping this can be fixed so I can go on with enjoying whatever life I have left with the g2, if not I'll probably just abuse it until it breaks then switch over to a water proof z2 or something along those lines... Phone was very well taken care of before the problem started, wasnt dropped or exposed to water (other then using outside in the rain for a few min at a time)
Click to expand...
Click to collapse
I have this problem too, any fixes?
Well I am in shock as to how we all have the same exact problem.
I first thought it was hardware failure on the screen itself and was pretty bummed. But now I see people have the exact same unresponsive touch screen in the exact same spot as mine? What ROM/Kernel are are you guys running? I am running what is in my sig and had not noticed it before until a couple of days ago. Coupled with the unresponsiveness, my Knock on does not work and the phone becomes mildly warm faster than usual. I think it might be a kernel software issue.
Ugh... I was hoping this wouldn't turn in to this big of a problem. I've got the same thing here, VS980 after flashing a Cloudy ROM.
I took over a thread here recently http://forum.xda-developers.com/showthread.php?p=52858791 , but I'll post here again anyways. I wonder if it's the same spot with you guys too. It's right where the install button is on the Play Store, right? For a few hours after it started it went back to normal, then messed up again permanently.
TOT'ing back to 12B didn't help, so I got a replacement device from Verizon. I've yet to send back my old one because I'm worried about the unrooted flag in the bootloader and settings.
I don't have enough posts yet to be able to do this, but can someone alert a dev about this? Particularly in the thread of whatever ROM it was that you last used? A lot of people in the last thread said it came from Cloudy, and I figured it might make sense as Knock Code was supposed to be a feature on there even though the VS980 source wasn't out. Then again I probably have no idea what I'm talking about, but I'd love to hear from someone who does.
I dont think my blacked out area is quite as thick as yours but yes its in the exact same place. To confuse things even more my phone just started working properly again (for how long is another story). Its very odd that It hasnt worked once in 2 months or so and now twice in 2 days its started working.
As a side note I'm pretty sure I started having this problem immediately or very shortly after the OTA kitkat update. I'm now running cloudypro II 2.0 with 3.4.0 kernel, which as i said before didnt fix the problem in the 1 month ive been using this rom.
I originally thought it may have been a software issue, but for it to randomly start/stop working all of a sudden after so long of no function (with no software being added or changed) I'm thinking its more likely a hardware problem? When I fly home on Monday I'm going to try opening up the phone and cleaning the contacts to the from the touchscreen to the mainboard.
If it is software related it may have something to do with air plane mode. I get almost no signal where I'm working at the moment and the constant searching for signal kills my battery pretty fast so I've started using air plane mode the past few days. Thats the only thing out of the ordinary that i've done software wise.
Having the same issue!!
Has anyone found a solution ?
Please reply.
hashir1296 said:
Has anyone found a solution ?
Please reply.
Click to expand...
Click to collapse
Yes, we've sent it to LG for repairs and they were able to fix it easily.
Sfkn, was your phone rooted when you sent it to them? I'm having the same issue, and it either started happening today, or I just noticed it today, but it's bugging the crap out of me. I'm running stock kk, rooted with twrp and on the cloudyfa kernel.
Sent from my LG-D801 using XDA Free mobile app
Had the same today but at the middle of the screen, I pressed on the corners and around the screen pretty hard and it is back to normal(for now).
Hope it wont come back.
You can unroot the device by flashing original rom with LG flash tool.
THISISINSANE said:
Sfkn, was your phone rooted when you sent it to them? I'm having the same issue, and it either started happening today, or I just noticed it today, but it's bugging the crap out of me. I'm running stock kk, rooted with twrp and on the cloudyfa kernel.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
No, I am completely stock.
Yeah I used the LG mobile support tool and that unrooted it. Now I'm just waiting for my replacement phone to arrive.
Sent from my LG-D801 using XDA Free mobile app
THISISINSANE said:
Yeah I used the LG mobile support tool and that unrooted it. Now I'm just waiting for my replacement phone to arrive.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
You claimed insurance rather than with LG repair?
Sfkn2 said:
You claimed insurance rather than with LG repair?
Click to expand...
Click to collapse
I went with T-Mobile's warranty replacement. I already sold my backup phone so I couldn't send the phone to LG for repairs and still have a phone
Sent from my LG-D801 using XDA Free mobile app

[Q] Kernel/rom that disables or modifies the proximity/light sensors?

I got one of these from Ebay and the thing was in great condition for costing 160. The only issue is that in very dark environments the screen can be a chore to turn on as it keeps turning itself off, likely due to my proximity sensor being a tad finicky or something (no issues in any reasonably lit environment, even street lamps at night, but it seems like I have to be like 1 foot away from the thing sometimes). Are there custom ROMs/Kernels that disable this functionality or make a workaround where if you say hold two of the keys at once the screen will turn on regardless? I think I'm describing something from a thread a few threads down but it's rather old. This is a really simple question. I know it's not good to ask for recommendations on ROMs/kernels but I'm asking for a very specific feature.
Bump I guess...
I think I figured out what the issue was, it seems to be the proximity sensor specifically. The light sensor seems to be working as expected because this doesn't happen in bright conditions. I also looked up where the proximity sensor is located and it looks like there are a few pieces of dust there or something. I guess since no one is making any suggestions on what has or hasn't worked, I'll just open it up and wipe that dust off by taking out the sensor. Looking at the teardown the top section doesn't look terribly complicated. I've had to fix my Vita's left joystick before so this shouldn't be too much different. I just hope those aren't scratches on the back of the glass or something.
Edit: Actually nevermind I just went ahead and did a Towelroot and then installed CM11. AFAIK all is well now and I'm also rooted, so 2 birds with one stone. Technically 3 since all that friggin bloatware is gone.

my S7 Edge screen bleeds purple smudges

Exactly like this, I was just enjoying some Fallout Shelter, then the screen just turned bright, like washed out.
Then BAM! Prince Purple Rain memento right there!
https://youtu.be/VA8CGoEKZrY
I've read around that people experiencing this problem, their phones died a couple of days later,
gotta get rid of all my files
Have you fixed your phone yet dude?
I had the same issue, took it to Samsung and they replaced it.
I seen your post on Reddit. I would definately suggest you take that to Samsung. They'll replace it under warranty.
That's not normal mate, get it replaced pronto!
Damn it, mine just started this crap. No stores here, I hope they mail you one first.
--edit--
Wow, I have to make this piece of crap back to them. 10 business day turn around. Samsung doesn't take care of you.
--more edit--
The screen went out 2 hours after noticing the issue for the first time.
--edits strike back--
Just keeping up with this incase another comes across the problem. I just got an email stating the part to fix it is on back order. So this must be a common issue.
Yep, common problem. Happened to me too. Sent it under warranty, they replaced the screen. When I got it back, the screen was damaged from within. Sent it back, they replaced the screen. When I got it the second time, there was a dead pixel in the center of the screen. Sent it back, obviously. Still waiting for it.
Hi, just getting this out of the depths of the board,
My phone also started to do this, like 6 or 7 weeks ago. I couldn't get it replaced because I was off to go abroad for two months but I will send it in once I return. I'm still well in the two years of warranty so that isn't a problem to get it replaced after.
My screen didn't die though. It works fine and if you use the app Screen Adjuster Free and turn all sliders up by +5, the problem is gone except when the phone is very hot.
What I find VERY odd is that I only see those smudges in bright light. e.g. direct sunlight, or a LED lenser. And what makes it more odd is that, once I block the light with my hand for example, the smudges are gone. I can have a HUGE smudge all over the screen and when I block the light with my finger, literally only that area where the "shadow" of the finger would be goes normal again. It's like the LED crystals react to bright light and cause this.
Let me show you what I mean.
That is some weird ass malfunction.
I have KNOX triggered though so I hope they'll replace it anyway. No experience with Samsung warranty handling so far.

Weird screen flickering

Hello,
This is my first post in this part of XDA.
My wife has an s7 Edge and the screen started flickering. I got out of this state messing with the power buttons etc. Mainly getting the touch screen to unlock the phone and it somehow cleared right up.
Is this a software issue? The screen when it came back is working as usual when I restarted the phone it became crap again.
Im think it maybe the lock screen causing this, I never heard of parts being corrupted.
I've attached a little clip of the screen.
Thoughts?
Thanks in advance!
https://youtu.be/gFSTlcDWGQY
I have never seen this happen before. If I were you I'd flash a new ROM on it in Odin and if it still happens take it to the Verizon store.
k1ska said:
I have never seen this happen before. If I were you I'd flash a new ROM on it in Odin and if it still happens take it to the Verizon store.
Click to expand...
Click to collapse
Forgot to mention, it's not rooted completely stock.
So screen is messed up?
I had this issue. My phone fell from less than a foot off the ground and landed on the corner. Barely any force, but after that the screen would flicker intermittently. For a day or two it would come and go, and then it became permanent. It looked exactly like yours. If your bootloader/recovery/download mode flickers then it is a hardware problem, since the ROM isn't even loaded yet. With Verizon, your phone is fully covered from manufacturing defects for one year, so you should be able to get it replaced. Sorry bro. Wish I had better news.
v1ral said:
Forgot to mention, it's not rooted completely stock.
So screen is messed up?
Click to expand...
Click to collapse
Honestly with a screen issue like that, I really recommend taking it to the Verizon store and asking them about it. It seems like a hardware issue to me but that's just my opinion.
My screen has done some weird things as well fresh out of the box. I would have random areas of the screen pixelize until I smack the back of the phone. Even after root It will randomly do it every other month. My father in law had the same exact issue you're having. He brought it into T-mobile where the screen literally failed and went black in the employees hand. Neither his or my phone has ever been dropped. This is definitely a hardware issue. It's almost like a bad connection between the LCD and main board. Make verizon get you a new one before the screen goes black!
Okay...
Is it okay to say I can get a new screen and do that repair myself?
I wanna make sure that the issue I am having is just "buy a new screen and be good to go".
Thanks for your time!

Categories

Resources