proximity issues

Search This thread
By:
Advanced…
B

blulite

Senior Member
Aug 28, 2010
336
167
joshm.1219 said:
Lol neither am I, disagreements dont have to be fights. But if it works on one type of software but not on the other, wouldn't you say software has something to do with it?

Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse

Just to be clear. I was having the proximity issue on CM11, so I went back to TW (thinking it was a CM11 bug). I then realized I was having issue with TW. The key difference under TW is that I was able to turn on the screen with the side power button (so at least I could use the phone). I then came across the dirty proximity thing via a Google search, "initially scoffed at it", then tried it. It worked, the proximity sensor was working like new under TW. I then went back to CM11 and confirmed it worked there, and posted my result. Since then, many have tried from the CM11 post and it helped them out. This morning I found this thread and thought I would share.

All the rest of this CM11 vs TW noise is not adding to the dialogue. It appears Samsung has a design flaw and that many of us are getting dirt under the glass (covering the proximity sensor). So load whatever firmware you like, but if you have a dirty proximity sensor then just follow my post and see if cleaning it helps out.

Nuff said.... I'm out.
 
  • Like
Reactions: swordmastr54 and spotmark
joshm.1219

joshm.1219

Senior Member
May 7, 2013
4,071
1,741
32
Philadelphia
blulite said:
Just to be clear. I was having the proximity issue on CM11, so I went back to TW (thinking it was a CM11 bug). I then realized I was having issue with TW. The key difference under TW is that I was able to turn on the screen with the side power button (so at least I could use the phone). I then came across the dirty proximity thing via a Google search, "initially scoffed at it", then tried it. It worked, the proximity sensor was working like new under TW. I then went back to CM11 and confirmed it worked there, and posted my result. Since then, many have tried from the CM11 post and it helped them out. This morning I found this thread and thought I would share.

All the rest of this CM11 vs TW noise is not adding to the dialogue. It appears Samsung has a design flaw and that many of us are getting dirt under the glass (covering the proximity sensor). So load whatever firmware you like, but if you have a dirty proximity sensor then just follow my post and see if cleaning it helps out.

Nuff said.... I'm out.
Click to expand...
Click to collapse

After clarifying things with spotmark I agree with what you're saying.

Sent from my SCH-I545 using Tapatalk
 
J

jamesd1085

Senior Member
Dec 6, 2012
929
465
Newark
Soooooo...yeah...took my S4 apart just for shiz and gigs...what matter of filth is this...it was covered...thanks to those who suggested it...wonder what kind of settings tw uses that it works...and I also wonder what kind of filthy conditions Samsung is buildIng our devices in for that much nasty to be inside...echhhh
 
D

DBak451

Member
Apr 14, 2011
18
12
I had issues with the proximity sensor on HD 10.2 with Kt kernel, I don't recall which version. Yet it always worked fine when I used the TW kernel. Seems to be software related. My friend's phone had the same issue, flashed a different ROM and used the stock kernel and no more issues.
 
F

fivejuantwo

Member
Mar 3, 2011
36
6
I removed the back to my s4 and then pulled the prox sensor off, It had a large piece of black something in front worked great ever since i remove it.
 
saul1991

saul1991

Senior Member
Jul 13, 2011
1,093
119
im having the same issue in cm but i doubt its the proximity sensor screen is black and phone will not wake up even if i press the home button.
 
B

blulite

Senior Member
Aug 28, 2010
336
167
saul1991 said:
im having the same issue in cm but i doubt its the proximity sensor screen is black and phone will not wake up even if i press the home button.
Click to expand...
Click to collapse

That's exactly how my phone was acting. It was very frustrating as I couldn't "wake the phone" to use the phone keypad. I tried home, power, volume, and nothing would wake it up. Clean the sensor and you won't believe your eyes........ I'm pretty sure it will be fixed.
 
C

ChaoticHavok

Member
Aug 28, 2013
16
0
blulite said:
That's exactly how my phone was acting. It was very frustrating as I couldn't "wake the phone" to use the phone keypad. I tried home, power, volume, and nothing would wake it up. Clean the sensor and you won't believe your eyes........ I'm pretty sure it will be fixed.
Click to expand...
Click to collapse

I'm on stock unrooted and compressed air to the earpiece did help. I too thought it might have been a software issue. I would try that solution first before messing about the software.
 
B

berfles

Senior Member
Sep 4, 2011
470
55
Compressed air didn't work for me, I had to manually recalibrate the threshold settings for the sensor outlined in a big post here somewhere. After I did that it worked instantly, and now I can actually see when debris gets on the sensor because the threshold numbers change actively in the *#0#* or whatever that menu system is. When I blow into the earpiece I can see the numbers set again to what I calibrated and it works fine.
 
You must log in or register to reply here.

Similar threads

J
[MOD][GUIDE] ISIS patch for root - Can be used anywhere PayPass is used -1.9 and 2.0
Replies
522
Views
109K
N
njgalaxy
open1your1eyes0
Verizon: Grandfathered Unlimited Data is the only data plan worth having
Replies
695
Views
118K
R
radpp16
V
Proximity sensor issues with CM 10.1 and 10.2?
Replies
17
Views
8K
Neffy27
Neffy27
T
Texting Issue with CM 11.0 Nightly
Replies
282
Views
30K
jackdubl
jackdubl
V
[Q] Bluetooth sync issues with Gen4 NAV (2004 Toyota Prius and other Lexus cars)
Replies
42
Views
15K
T
thegreener

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 2
    B
    blulite
    joshm.1219 said:
    Lol neither am I, disagreements dont have to be fights. But if it works on one type of software but not on the other, wouldn't you say software has something to do with it?

    Sent from my SCH-I545 using Tapatalk
    Click to expand...
    Click to collapse

    Just to be clear. I was having the proximity issue on CM11, so I went back to TW (thinking it was a CM11 bug). I then realized I was having issue with TW. The key difference under TW is that I was able to turn on the screen with the side power button (so at least I could use the phone). I then came across the dirty proximity thing via a Google search, "initially scoffed at it", then tried it. It worked, the proximity sensor was working like new under TW. I then went back to CM11 and confirmed it worked there, and posted my result. Since then, many have tried from the CM11 post and it helped them out. This morning I found this thread and thought I would share.

    All the rest of this CM11 vs TW noise is not adding to the dialogue. It appears Samsung has a design flaw and that many of us are getting dirt under the glass (covering the proximity sensor). So load whatever firmware you like, but if you have a dirty proximity sensor then just follow my post and see if cleaning it helps out.

    Nuff said.... I'm out.
    View
    1
    Mistertac
    Mistertac
    joshm.1219 said:
    Thats CM fanboy bullsh!t. If it's dirt on the sensor it would happen on TW too. It's a software issue

    Sent from my SCH-I545 using Tapatalk
    Click to expand...
    Click to collapse

    Lol
    CM fanboy BS

    Sent from my SCH-I545 using Tapatalk
    View
    1
    joshm.1219
    joshm.1219
    Mistertac said:
    Lol
    CM fanboy BS

    Sent from my SCH-I545 using Tapatalk
    Click to expand...
    Click to collapse

    They exist lol, won't blame anything on the code like Steve Kondik is the God of programming or something.

    Sent from my SCH-I545 using Tapatalk
    View
    1
    spotmark
    spotmark
    joshm.1219 said:
    They exist lol, won't blame anything on the code like Steve Kondik is the God of programming or something.
    Click to expand...
    Click to collapse

    I expect bugs in any ROM, including stock ones. However, I must say, that I was experiencing this issue, and without changing anything software wise, I used compressed air on the earpiece, and it fixed the problem.
    View
    1
    B
    blulite
    joshm.1219 said:
    Thats CM fanboy bullsh!t. If it's dirt on the sensor it would happen on TW too. It's a software issue

    Sent from my SCH-I545 using Tapatalk
    Click to expand...
    Click to collapse

    I had similar issues on TW. Did a quick Google search and found some stuff about dirty sensor. I too thought it sounded crazy, but gave it a try. When I disassembled my back-plate it was easy to see the black haze on the backside of the glass. A q-tip, alcohol, and all fixed. It worked very reliably (like new) on TW, so I decided to try CM11 again. Sure enough, the sensor worked fine with CM11. I posted over on that thread as many folks had been commenting of this problem and everyone assumed it was something broken in CM11.

    Read the next handful of posts in the CM11 thread. At first a few called BS on the post, then several folks started trying it and all commented that it worked.

    But again, thanks for the fanboy comment. Very constructive addition to this dialogue.
    View

New posts