CM11 and call/screen (proximity sensor) problem --- ALSO CM12!!! - G2 Q&A, Help & Troubleshooting

Hi, I've been having this issue since installed CM11 on this phone (D800, happens aswell on other models). Sometimes the proximity sensor will not trigger when incall and taking away the phone from your face. So the only way to get the screen back (to hang-up the call for example) is hitting the back button -wich is annoying-. The sensor is ok since it is working fine (call and screen) on a G3 based rom. Is there any workaround for this? Can anyone help to fix this?
Thanks all in advance!

I have same issue and been searching and posting to find the cause and solution.
But unfortunaly no responses and/or fixes so far.....

Incredibly, this bug happens me aswell on cyanogenmod 12 (lollipop)... Should I start thinking about a radio problem? Wich other radio could be tested with this roms?

Related

Mid Call Proximity Sensor Problem

Does anyone know if there is a way to adjust the proximity sensor.
It's proving a problem for my wife who uses the phone. When she's on a call the phone is intermittently sensing if she's holding it to her ear.
Hence being a capactive screen, when her cheek brushes the screen during a call the other end either hears DTMF or gets cut off by it touching the end call.
I called her yesterday and kept getting random DTMF digits sent to me, then I got sut off.
I was watching her use the phone and the screen was de-activiting (correctly going blank) for part of the call then coming back on, this would happen several times during one call.
Is this a hardware issue or software bug. Has anyone else suffered this problem?
Also happened to me a few times touching end call wih my cheek, really annoying.
Anyone else having the same problem with the proximity sensor intermittently not working during a call?
I had that problem on the old 1.43 ROM but it was fixed when I upgrade to 1.48.
I have this problem and I constantly have to call back and say sorry to my customers and blame it on the phone...
I have reported several errors to HTC and all i get back is "Take it to the retailer and get it changed, it must be a hw error", annoying as hell
1.48 not yet official in sweden.
TouchLockPro
You can try TouchLockPro, it has an InCallTweak, using the GSensor. Searching for accessing programmatically the Proximity Sensor though, for more options (e.g unlock by Proximity Sensor). It works on HTC Leo, people confirmed.
Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil
philtrick123 said:
Thanks ZuinigeRijder.
I've tried the software and I think it might work.
I loaded the software and it worked without any further config I presume that is currect.
Phil
Click to expand...
Click to collapse
Indeed, TouchLockPro detects itself the available sensors and uses the available ones. Of course you can configure detailed things (via pressing the BattClock), but the defaults are already the sensible ones
Thanks again ZuinigeRijder.
Just been doing some more testing and occasionally the screen flashes on for a brief moment during a call. Could it be the proximity sensor trying to turn on the screen? Or is it the G sensor not being very accurate?
In the application is there a way for me to adjust the G-Sensor angles that activate the screen off? i.e. 45+ Degrees activate ??
Or are there any other adjustments I could make during testing??
I found one more problem... I checked it several times....
If u make a call using portrait orientation of phone app (Rotated using BSB Tweak). Proximity sensor doesnt work at all.... i made a while lyin on the bed and no matter wat i tried it wasnt turning off the screen....
Then i kept it in portrait position for a few seconds den proximity started working again...
Is there anyone who can confirm me with this problem.... or is this issue only with my HD2

[Q] Need help to disable proximity sensor/driver.

Hi guys, I have strange but I think common problem. My problem is, when I use earphones/headphones and I try to call (proximity sensor is on) I can hear buzz sound, Its VERY annoying. I tried viber/tango and had same problem with them. So next I tried skype, because skype is not turning on proximity all was fine.
So my question is, how can i disable driver/proximity sensor. I tried this http://forum.xda-developers.com/showthread.php?t=1683884 But this app cant find proximity sensor, all what I saw was led/touch/camera and magnetic field sensors, nothing about proximity... Next I tried http://forum.xda-developers.com/showthread.php?t=1626611 and still nothing, but I think its only for gsm...
Can anybody help me with that? Now what I have is Aokp M1 and trinity kernel, thanks in advance.

[Q] wierd problem on calls - maybe proximity sensor

Hello to all.
I have this wierd problem. While I am on a call if I put the phone on my face it turns black. Then when I put it off and it lights up BUT then the HOME button and the right and left virtual buttons stop working ! I can only end the call.
If I do the same but without touching the proximity sensor everything works fine . The problem begins after the use of proximity sensor. Could this be softare or hardware? Anyone else with this problem? Any advice on this?
Doing a hard reset seems to fix the problem. Maybe it was a conflict with some app...thank you though.
Sent from my SM-N9005 using Tapatalk

[Q] In-Call dialer unresponsive...

So I have seen this issue on multiple forums, across multiple roms/devices, but can't seem to find any solution.
I have a LG G2 on VZW (VS980) currently running AOKP 5/24 nightly (but I have had this issue for months now).
When I make a call, the in-call dialer interface is completely unresponsive. I can't hang up, open the dial pad, speaker phone, mute, etc... the only way I can hang up is to hit the back navigation button and then pull down the notification and hang up that way. I am running PA micro gapps, but I have had the same problem with other gapps as well.
Does anyone else have this problem or has found a solution?
Bump. Really looking for any ideas on how to fix this.
I'm in the same boat here. Would really appreciate if someone could provide a fix.
liwei8759 said:
I'm in the same boat here. Would really appreciate if someone could provide a fix.
Click to expand...
Click to collapse
I fixed my issues by flashing the "Google Dialer" in this thread
Same issue - can't use the touch keys in the dialer while in conversation in LG G2
liwei8759 said:
I'm in the same boat here. Would really appreciate if someone could provide a fix.
Click to expand...
Click to collapse
Did you manage to solve it until now?
athorax said:
I fixed my issues by flashing the "Google Dialer" in this thread
Click to expand...
Click to collapse
Thanks a lot for posting your workaround.
I have exactly the same issue - I can't use the touch keys in the dialer while in conversation in LG G2 D802 (Intl).
However, the Google Dialer is an old app that got replaced by Hangouts Dialer.
Did you switch to Hangouts Dialer, or you stayed on KitKat 4.4.2 with the old Google Dialer from the post you provided?
By the way, I posted issue CYAN-6090 in the CyanogenMod JIRA in order to try and get resolution to this issue.
Are there any other users with this issue?
Did you solve it somehow?
note: sorry for not posting links. I have that annoying new user limitation...
there's a similar issue - LG G2 screen turn off and goes blank during conversation
It seems that there are two similar issues in LG G2 which are both caused by the proximity sensor during conversation:
The screen stays on and the touch buttons in the dialer aren't responsive.
The screen turn off and goes blank.
(This issue was already reported by @madafis here)
In both of these situations the only quick way to end a call is to pull down the status and notifications bar and hang up from there.
Thanks to @Bam9 and @EtherBoo , who suggested to clear the proximity sensor from the outside and squeeze the top left corner of the phone, I tried to clean it and put some stress on it - and it worked!
I have a glass screen protector (which don't block the proximity sensor), and I am rooted and using CyanogenMod 11 ROM.
I used ioroot to root and AutoRec, which comes with TWRP 2.7.0.0, to install CyanogenMod ROM.
However, going back to stock ROM (in my case, LG G2 D802, it's D80220C) won't help since the issue still exists.
What I'm sure is that it was pretty much okay in the beginning, and the situation became worse and worse - occurring randomly, until it arrived to a situation in which I can't use the phone properly during conversation.
Now that I discovered that I can put some stress on the proximity sensor it seems that I have a hardware rather than a software issue.

Proximity sensor triggering Capacitive keys in stock Roms

Hey guys.. I've been having a strange problem with my S4 i9500.
I know there are a lot of people having Proximity sensor bugs but my problem is different.
My Proximity sensor is working totally fine with phone calls and everything seems fine with the sensor.. however whenever the proximity sensor is triggered (switched from far to near) it acts as a press on the menu button (in stock rom it opens the search and in s6/note5 ports it opens multi-window. but the weird thing about this bug that it doesn't happen in GearCM.. only in stock based roms.
it's sounds like not a bug deal bit it is.. cuz whenever my phone reboots 80% of the times it gets stuck in safe mode because of this. and I cannot get out of it untill I do a cache/dalvic cache wipe .
And Ideas ? does anyone had a similar problem? I hope I explained it well.

Categories

Resources