Database Users

[Q] Calling Problems

I've started experiencing some problems when trying to make a call. Whenever I call someone, my phone turns off and locks, and I'm not able to turn the phone back on and the soft keys won't light up for 30 seconds or so. It's almost as if the phone turns completely off, but it's still making the call. This is only if I make a call. If someone calls me, the phone turns the screen off and on by itself no matter where I position the phone. It just flashes on and off.
I've been running jt's super clean v0.4 and the 11/02 kernel, and I had been running them for a few days before this started happening. I even flashed back to stock and nothing changed so I've flashed back to jt's rom and kernel.
Any help or suggestions or anything would be helpful. Thanks.

And I bet after a boot first couple of calls might be fine? Sounds like you may be using a task killer.
Put
com.samsung.phoneinfo and Call settings
in the ignore list.
good day.

Nope, uninstalled ATK and still the same problem. And the first call after a reboot still had the same problem.
Also, the only way it unlocks itself is if the other person hangs up.
Sent from my SCH-I500 using XDA App

Mine does that too.
It often blanks when I look at it, and stays on when I put the phone to my ear.
In my case the phone isn't actually turning off. It's as if the proximity sensor often doesn't work right.
The proximity sensor is that thing next to the speaker on top. It turns the display and touch screen off so that you don't press the buttons with your ear, and so that the phone doesn't feel too warm on your ear.
I highly suspect that the hardware is fine, but the phone isn't task switching fast enough when the hardware raises an interrupt.
This is the only time that lag bothers me.
This became less bothersome to me when I realised that the phone wasn't actually broken.
I also do not use task killers, because this ain't Windows.
Sent from my SCH-I500 using XDA App

So we now have new causes for an old problem. Sorry I couldn't help.
good day.

Bump
Sent from my SCH-I500 using XDA App

Same here my proximity sensor just locks me out, i am trying to use the keypad and i have to unlock it over and over again. I restored my lock screen to original and it did not do it with a test call. But ill have to keep an eye on it. My biggest issue is the 3g connection dropping to 1x when i hit the web.

It was my screen protector. I guess it covered the sensor enough to block it. Hmm.
Sent from my SCH-I500 using XDA App

My screen sensor doesn't actually cover it, but I am easier able to live with it since I know what's happening.

[Q] Proximity Sensor Fails

Just wanna ask if there is any temporary fix to the proximity sensor of nexus 4.
During calls the screen doesn't turn off when placed close to the face.
I didn't get the chance to test it on stock 4.2 because when i turned my phone on it updated first to 4.2.1. Ever since then it has had proximity sensor not working during calls.
And i have never had any screen protectors on the screen.
Tried many custom ROMS as well but no difference at all.
Sent from my Nexus 4 using xda premium

how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken

I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.

isnt there a proximity senor app which lets you test it on the market?

dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
Click to expand...
Click to collapse
Using stock. No issues on the sensor. Turns off on calls and turns on when I remove from the face. Have a spigen protector on with a cutout for it
Sent from my Nexus 4 using Tapatalk 2

dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.
Click to expand...
Click to collapse
I was on stock 2 weeks ago when I started noticing it.
I am on cm now as well and its very much messed up.
Sent from my Nexus 4 using xda premium

bobola said:
isnt there a proximity senor app which lets you test it on the market?
Click to expand...
Click to collapse
There is.
I've installed and tested.
According to the app results, The proximity sensor seems to know when my hand is on it and when its off it. The value changes from 1.0 to 2.0
It just won't work on phone calls.
Sent from my Nexus 4 using xda premium

noobdeagle said:
how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken
Click to expand...
Click to collapse
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium

slimldj said:
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mine is stock and during calls it usually goes to my settings menu and changes my clock setting. When I get off the phone, screen is blank and I hit power button to end call. Still annoying at times when the clock changes.

any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.

feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium

feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I'm suffering this same problem too, hope they fix it soon..

slimldj said:
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes I think the fact that the app testing showed the sensor working so it points to software. Something is missing when the phone is in a call its not connecting to turn off. I thing Jellybean was flawed in many ways. My drop down brightness slider doesn't work for me nor auto brightness its OK for me cause I don't use either but still makes me mad.
Using Tapatalk 2

meetoo
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.

treaty said:
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.
Click to expand...
Click to collapse
Having the exact same issue here too on stock ROM.
Good idea on the accessibility settings! Will work until/if they fix it..
Also no screen protector.

I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.

Dav_prime said:
I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.
Click to expand...
Click to collapse
It was the same fix for mine when I first got my bse it worked fine for about a week but then over time it got worse. It was the screen protector just that lil bit worth of it wear caused enough blockage of the sensor. I got some new bse's and they now have a cutout for the proximity sensor and are screen optimized.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2

use Proximity Actions by Novum Inceptum in playstore

rat99 said:
use Proximity Actions by Novum Inceptum in playstore
Click to expand...
Click to collapse
That won't fix anything.

Proximity sensor

I have noticed that during a phone call proximity sensor doesn't while to taking i could hear those click sound(touch sound) and after i end call somehow i am in gallery or whatsapp or some other app.
Sent from my D6503 using Tapatalk

Can't say I've experienced that myself
Sent from my D6503 using Tapatalk

I get my calls cut off occasionally. That happened with my previous SIII so I guess it is just a standard problem with proximity sensors - they're not as effective as the manufacturers would have you believe.
Sent from my D6503 using XDA Free mobile app

The proximity sensor turns the screen off when the phones in a normal talking position. If you're led down, it's likely it won't. Try it, move the phone around and put your hand over the sensor.
Sent from my D6503 using Tapatalk

its not a proximity problem as the screen stays off if it was the sensor the screen would keep lighting up
I have had this problem and posted about it already
I have tried with the double tap to wake feature off to see if it was that but no such luck!!
---------- Post added at 09:43 PM ---------- Previous post was at 09:42 PM ----------
heres the thread I started http://forum.xda-developers.com/showthread.php?t=2769679

i also find myself in different places after call, this happens with flap cover closed

I usually have same problem, I click on power button to turn off the screen and usually it solves the click problem.
Don't know why android phones proximity sensor doesn't works as good as iPhone. Never had that problem in any iPhone and for android it seems all the phone have this problem.

ikm19 said:
Don't know why android phones proximity sensor doesn't works as good as iPhone. Never had that problem in any iPhone and for android it seems all the phone have this problem.
Click to expand...
Click to collapse
never had this problem on my HTC one X
and I have never heard of the problem on other phones either!!

I also used to have problems with proximity sensor not waking up the screen during a call. It seemed to be completely random: sometimes it happened after only 1 min of talk time, other time after 5 minutes, other time it worked ok even after 20 minutes of talk time. I turned off "double tap to wake up" and I never had any problems since. I'm not sure it's not a coincidence, but it worked so far (10 days).
About the cut off calls:it's not the proximity sensor. For me that happened on any European firmware. I tried the original .55 Vodafone Germany (the one that the phone came with), .55 UK and .402 Germany. It happened randomly on all of them. I tried repair firmware, factory reset, re flash with FlashTool. Nothing worked. The ones that work flawlessly for me are TW firmwares. I tried both .69 TW and currently on .402 TW. No cut off calls, no problems, no overheating in 4K (about 10 minutes recording).

Turning of double tap to wakeup seems solved my problem.

my PS works great. never had that issue. maybe you should take your phone to diagnostics.

Im having the same issue. Hearing ticks/clicks when im on a call and I end up somewhere after a call. I hope Sony fixes this. Temporarily I lock my phone to prevent this problem.

ikm19 said:
Turning of double tap to wakeup seems solved my problem.
Click to expand...
Click to collapse
No it doesn't I tried that weeks ago

In the Diagnostics app, go to Test Device and run the Ear Proximity test. Mine passed just fine.
Sent from my D6503 using Tapatalk

Fixed my Proximity/Ambient light Sensor
Hi, I had this problem since new and I tried installing lots of stock and custom roms (Stock US, Stock SP, Stock TW, Miui, CM11) but it was until I installed EXISTANZ rom, and a hard reboot, and then it magically started working. I knew it wasn't a Hardware issue because when the phone boots it worked for few minutes, then stop reading samples. But I've been with this rom for 3 weeks and I don't have any problem with this (Already installed and update, reset the phone and still working).
So if you have the chance, install this rom.

double tap to wake issue
raducanmihai said:
I also used to have problems with proximity sensor not waking up the screen during a call. It seemed to be completely random: sometimes it happened after only 1 min of talk time, other time after 5 minutes, other time it worked ok even after 20 minutes of talk time. I turned off "double tap to wake up" and I never had any problems since. I'm not sure it's not a coincidence, but it worked so far (10 days).
About the cut off calls:it's not the proximity sensor. For me that happened on any European firmware. I tried the original .55 Vodafone Germany (the one that the phone came with), .55 UK and .402 Germany. It happened randomly on all of them. I tried repair firmware, factory reset, re flash with FlashTool. Nothing worked. The ones that work flawlessly for me are TW firmwares. I tried both .69 TW and currently on .402 TW. No cut off calls, no problems, no overheating in 4K (about 10 minutes recording).
Click to expand...
Click to collapse
Hi ,
I also encountered this issue and i performed a test with and without the "double tap to wake" option.
The result is: without the option activated all is fine but when the "double tap to wake" option is activated and the proximity sensor is covered(screen is black) if you double tap the screen it remains closed. So seems that if you are engaged in a conversation and you miss touch twice the screen, it will remain closed.

Hi all,
First sorry from bringing an old thread.
I am an owner of two black d6502 xperia z2
One of them is running perfectly, the other suffers from the same behaviour the op describe.
When handling a call, the proximity sensor works fine, it is making the screen black but it is NOT LOCKING the menu, I.e the screen is black but you can swipe the status bar down and enter different menu while the proximity sensor is keeping the screen black.
My second xperia z2 behave normally, when handling call, proximity sensor turn the screen black and locks the menu, if i swipe on the screen the software ain't responsive.
Was anyone successful to fix this issue?
Elie.

The problem is in the screen protector. There is a post in the Sony Forum how to solve the problem.

It's simple hardware problem... you have to remove back cover, find connector of proximity sensor, remove it and put again, press hard and it will work...
for long time I've had that issue, but until I ordered new sensor tried to do that trick and it helped

Disable proximity sensor with Android L

This past summer I had my Nexus 4 LCD and digitizer replaced, after which the proximity sensor stopped working. I installed the Proximity Screen Off app as a workaround to keep the screen alive during phone calls. Ever since I upgraded to Android L yesterday, this fix no longer seems to work. Is there anything that I can do besides sending the unit in for repair? I lack the tools to take apart the phone.
This problem is rather crippling as I cannot use the dialer or speakerphone during phone calls, or even hang up when the screen is off.

I have this exact same issue, and was also hoping to find a fix. Any ideas?

One thing to end calls. Accessibility - power button ends calls
Sent from my Nexus 4 using XDA Free mobile app

n2d551 said:
One thing to end calls. Accessibility - power button ends calls
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. I have done this, for the time being, as it's difficult to end calls, otherwise. However, not being able to use the keypad whilst in call is posing to be an issue. Prior to the update and using 'Proximity Screen Off' app, I was able to catch the 'Home' button when pressing the power button, which allowed me to use the phone screen whilst in a call. With the new update, I am unable to do this.
I have come across a Disassembly Video (watch?v=AZDAIgwbXk4), but I'm not sure how confident I feel taking my phone apart.
The screen on my Nexus 4 has previously been replaced. When it was replaced, I'm fairly sure the Proximity Sensor did work, but then I dropped it on wooden flooring, and after that it no longer worked. It was a seemingly short drop, but this has somehow damaged the sensor. I'm not sure if the rubber cover (as shown in the video) has just moved out of place, or if it is completely broken. The light sensor works fine, in any case.

BobSmith9 said:
I have this exact same issue, and was also hoping to find a fix. Any ideas?
Click to expand...
Click to collapse
Admiral Nelson said:
This past summer I had my Nexus 4 LCD and digitizer replaced, after which the proximity sensor stopped working. I installed the Proximity Screen Off app as a workaround to keep the screen alive during phone calls. Ever since I upgraded to Android L yesterday, this fix no longer seems to work. Is there anything that I can do besides sending the unit in for repair? I lack the tools to take apart the phone.
This problem is rather crippling as I cannot use the dialer or speakerphone during phone calls, or even hang up when the screen is off.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2657176

mene82 said:
http://forum.xda-developers.com/showthread.php?t=2657176
Click to expand...
Click to collapse
I thought I had fixed it, but unfortunately the fix was short-lived. I discovered that I'm missing the gasket covering the proximity and light sensor, and this is causing an issue.
Anyone have any workable alternatives?

Screen stays on during calls, faulty proximity sensor?

When I make phone calls the screen stays on when I put it to my ear. This results in touch presses ranging from muting the call, typing digits or really doing anything through the phones interface. Bloody infuriating.
It's very annoying and it shouldn't be doing it. I say shouldn't because it doesn't always; some times a reboot will seem to fix the problem but that seems to depend on how soon after the reboot a call is made/answered.
I have used AndroSensor to test the sensors (accelerometer, light, proximity etc) and they all seem to be registering values. For proximity, putting my finger over the sensor can result in a drop in value to 0.4in or 1.2in. This could be the cause of the issue as 1.2in is far to high a reading to correctly disable the screen afaik.
Possibly related; when the screen stays on, and the call is long I believe the normal screen timeout will kick in and the screen goes blank, meaning to hangup I have to wake the phone and unlock etc.
My questions are;
Has anyone else experience this?
Is it a setting, bug or faulty hardware?
Can someone else perform the same tests with AndroSensor to see if their results are the same as mine?
Moto X Play XT1562
Android 6.0.1
Build MPD24.107-52

Do you have screen protector applied?
Sent from my XT1562 using XDA-Developers mobile app

pijes said:
Do you have screen protector applied?
Sent from my XT1562 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope.

Did you ever get this sorted out? I'm having the same issue, but the proximity sensor numbers don't change at all. No screen protector, stock unrooted device on Marshmallow.

Same Problem
Actually even i have been having the same problem. It is not smethin that has been there forever it has started in the past few weeks.

I had this problem once, but a simple restart had solved it.