My proximity sensor always show 0.0cm and the screen is always black when I make a call.
I have tested 2 different ICS stock roms (XXLQ9 and ZCLPD) (flashed with odin), and about 5 different custum rom (CM10.1,Rootbox ...). I did 3 wipe between every rom and nothing works. When this problem started my screen start to "leak light" and every pixel became "bigger", now the screen is good again but the proximity sensor still doesn't work. Now I wonder if it's a hardwear problem and if it's possible to diasable proximity sensor during calls in CM10.1.
Are you using a screen guard? If you don't mind then try if removing the screen guard solves your problem.. That way you'll know if the sensor is dysfunctional or something else..
From my CM10.1 powered galaxy R
Hi guys, I have a issue with proximity sensor, it happend from 4.4.2 and now i'm in 4.4.4 and still facing with it.
At the first time I think that is my app problem, so I don't care at all. But today, I found it (maybe to late) happend with all thing include call and the test in hidden menu.
This is the way how I made it:
1. cover the proximity sensor
2. start the call
-> screen go off
3. un-cover the proximity sensor
-> screen not turn on even the call ended. All thing you can do is press Power button twice
If this only happend with call, ok, I can accept it like a feature.
But when I try reproduce the issue in *#*#7378423#*#* - Service tests - Proximity Swich test, the result show that the proximity sensor cannotchange state and always "Detected".
So idk the problem is my phone or sony firmware, anyone can confirm that? I did some searching but can't find anything.
Thank you.
i think the problem is in proximity sensor because as u say it happend in 4.4.2 and 4.4.4, and i've use both firmware and i dont face any problem like that, and u can check if u have ur screen guard on ur proximity sensor, because it happens with me once i put my screen guard on proximity sensor thinking nothing will be wrong because screen guard is transparent but that my proximity sensor becomes like what u say, always detect, check it
It's not the problem of sensor, this problem is in firmware. I am facing the same problem and my frd too.
ChetanLokhande said:
It's not the problem of sensor, this problem is in firmware. I am facing the same problem and my frd too.
Click to expand...
Click to collapse
i never face this problem,
which kernel you are using, i am using vinays nitrogen kernel, does this problem occur on stock ?
So, I have stumbled across this weird issue since January wherein if the proximity sensor is covered during an incoming call, the screen will remain off. What's weird is that this only happens on CM based ROMs and not on AOSP based ROMs. Of course, all full wipes and clean flashes. I have also tried flashing all the Marshmallow compatible modems available but none solved my issue. I'm using TWRP 2.8.6.0 to flash the zips.
CM based ROMs that I have tried so far;
1. Resurrection Remix M
2. Bliss ROM (both official and unofficial)
3. Marsh CM13
The older builds (December and early January) did not have this problem but of late, every CM based ROM activates the proximity sensor for an incoming call. The reason I'm posting this here is because no one else seems to have this problem and it's not specific to any one ROM.
On AOSP ROMs, everything works fine (no matter what modem I use). I have tried Darkobas ROM and I'm currently on CandySix where I don't have any issues with the proximity sensor.
Any idea why this could be happening? I miss all the customization on CM ROMs and I'm not a huge fan of Layers, so help would be appreciated.
Cheers!
This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...
Thanks for your response, mate. But CM seems to have fixed this issue because I just flashed the 02/03 CM13 nightly and the proximity sensor works just as it should during an incoming call; no issues there.
I'm going to try flashing another ROM on top of this.
AcmE85 said:
This is the exact bug description:
1. when on a call, cover the proximity sensor >> screen turns off
2. while covering the sensor doubletap the screen (this is the reason for this issue!)
3. uncover the sensor >> screen stays off
The problem is that the doubletap is registered as a power button press and therefore the screen stays off.
It only happens if you accidentally touch the screen with your face, which is likely to occur on a phonecall.
I've already mentioned this in a commit and they said they know about this issue.
The needed commit needs to be ported from cm12.1.
So I guess we can only wait...
Click to expand...
Click to collapse
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.
girishb said:
I just went through your post again and it seems that you misunderstood my issue.
Apart from the issue that you mentioned, the proximity sensor is turning off the screen even before I have answered an incoming call. So, for example, I get a call when the phone is in my pocket. When I take it out, it takes a while for the screen to turn on which is frustrating. If I don't answer the call, the screen should remain on for as long as the phone rings, irrespective of whether the proximity sensor is covered or not. But, in my case, if the proximity sensor is covered when the phone is ringing, the screen turns off. Am I being clear now?
So, after a few intense sessions of flashing different ROMs, it seems that the official CM13 nightly and CandySix are the only ROMs where the proximity sensor is not broken for incoming calls. I guess I'll be sticking with CandySix for the foreseeable future.
But I'd really appreciate if someone can identify why this is happening with all other ROMs and not with official CM13 and CandySix.
Click to expand...
Click to collapse
actually i think u messed up a bit mate dont mention calling ! something like screen OFF when i recieve a call from someone even when not answered or something like this ! and now getting back to your query i flash RR and CM13 by jgcaap right now just for checking ur issue and i dont have this i kept the phone on the table , called from my other phone and covered the proximity sensor with my hand ! screen was still ON .. and i should mention my RR build is a bit old ! i have been using jgcaap cm 13 from many days ! so
Well, there was only so much I could put in the title. I think my OP explains the issue clearly.
Also, can you try the latest version of RR or Bliss ROM? Because as I said, I wasn't having this issue on the older builds. I also don't have this issue on the official CM13 nightly or CandySix. I just want to find out what's causing this issue on my phone with other ROMs.
@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?
AcmE85 said:
@girishb
Ok I see. The way you put it, I thought cm based roms includes stock cm13.
Regardless. The commit which fixed the proximity sensor with screen off has been merged on 02/20.
When did the other cm based roms get their last update?
Click to expand...
Click to collapse
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht
thepico said:
but still that issue of phone getting locked furing call persists right ? i mean during call i get this lock sounds sometimes and i need to double tap agn to disconnect the call ! anyways im sure there is a more recent build after 20/2 for rr ! anyawys i should check and get back on taht
Click to expand...
Click to collapse
Im on RR 24 and i can still see this issue. Lets see wht RR Mod comments on that.
Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.
girishb said:
Uh, I'm pretty sure that's a different issue. What you guys are facing is basically the screen getting locked when a call is going on, which should not happen. This issue is consistent across all ROMs that I have tried, even AOSP ones. So I don't think that's a CM issue.
My original issue is slightly different. During an incoming call, the screen should remain on for as long as the phone rings, right? If I choose to answer the call, that's when the proximity sensor should kick in and turn off the screen as I move the phone to my ear. However, in my case, if the proximity sensor is covered during an incoming call, it keeps the screen off so I can't see who's calling unless the sensor is uncovered. This should not happen. I hope this explains the issue properly.
Click to expand...
Click to collapse
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.
YoshiShaPow said:
What firmware are you on? Most proximity sensor issues are due to incompatible/old firmware.
Click to expand...
Click to collapse
I have tried all modems from this topic (other than the h2os and oxygen one). I have also tried clean flashing the latest CM13 nightly before clean flashing any ROM. I also tried dirty flashing a ROM over the CM13 nightly with no luck. I used TWRP 2.8.6.0 for all of this.
What I can't seem to figure out is why I don't have these issues on the official CM13 nightly build or on CandySix ROM. All other ROMs that I have tried have this issue. If it's a firmware related issue, then shouldn't I be having this problem on all ROMs?
Any solution for this problem coz its really annoying.
I'm having the exact same problem with my phone running CyanogenOS 13.1.2-ZNH2KAS3P0-bacon. The screen doesn't turn on automatically if the proximity sensor is blocked in the beginning of the incoming call or alarm.
If someone finds a solution, please reply to my post
The Tampered, Unclocked, S-Off, Cid-11111111, HBoot 2.22, Rooted HTC One Mini that I have doesn't ring when Proximity Sensor reads "NEAR".
I'm aware of Sense 6 options like "Ring louder when in pocket" but none of them worked on making the phone ring when a call is received.
That happened when the phone was completely stock, so recently I went through all the process of S-Offing it to install a new Rom. I choose the latest Insert Coin 5.0.8, but the problem persists. so now I'm almost certain it's an hardware issue...
The phone has several years old and returning it for repair/replaced isn't really an option.
Since I'm giving this phone to my mother, I really need it to ring and vibrate when someone calls her or else she'll never pickup any calls with the phone in her purse.
I've tried installing Xposed Framework to have a try at the sensor disabling app, but the whole rom crashed badly and I needed to reinstall everything.
Other usefull info:
Kernel: [email protected] [email protected] #1 SMP FREEMPT
Is there a way to override proximity sensor when a call is received and/or making the phone ring regardless of proximity sensor state?
Looking foward for an expert tip. Thanks.
I've installed "[ROM][M4 - 4.14.401.1] Official Stock Sense 6 Rom v3 & Firmware" from xXminiWHOOPERxX -> Installed xPosed -> Sensor Disabler
Then I tried to Disable Proximity, Disable Light sensor, Mock Proximity to FAR, Disable both proximity and Light, Block Call app from accessing Proximity....nothing worked: Meaning the sensors still function normal...
BUT then I noticed something strange:
Running "Sensors Test" app,
IF I put my finger just over light sensor -> proximity reads "NEAR"
IF I put my finger just over proximity -> proximity reads "NEAR"
....Meaning that the light sensor is acting as proximity!
My next step was to identify which "dot" was the light sensor, since both acted as proximity and I used some black tape covering one of the sensors (that I've identified as the proximity)...and now the proximity sensor always reads "FAR"!!
To be sure it wasn't xPosed doing the trick I reset all things to normal and uninstalled everything...and with the black tape covering the sensor it still reads "FAR" thus resolving my issue of the phone not ringing when a call is received...
I now have to figure out if painting the sensor black has the same result, because tape looks ugly. I'll make a vídeo and post the link here.
Everytime i call someone and end hte call , the phone would have went deep inside either into some setting or app , because of the touch of my ear , due to proximity sensor not working properly. I removed the screen guard and still the same issue.
I used the proximity sensor fix app as suggested in one of the threads here , still nothing.. Its really making me soo annoyed.
Can someone please help me. I am using Havoc 4.19 Version.