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.
Related
Does anyone have an issue with your cheek pushing buttons while you are on the phone? I am running liberated_aria and whenever i am on the phone, my screen does not shut off like other phones and I end up either hanging up on people or moving widgets and even adding widgets..
has anyone else noticed this? is there a fix for it?
Its happened to me once on an Aosp rom. Haven't had any problems after that though.
Sent from my HTC Liberty using XDA App
I haven't had any problems. The proximity sensor is on the top right of the phone, where the AT&T logo is. Try making a call, to voicemail or something, and then waving your finger over the sensor. Does it ever turn the display off? Could be a software bug I suppose, or just a faulty sensor.
if you use your left hand/ear its pretty easy to dodge the sensor, unfortunately.
I tried a call using my right hand and I dont have that problem. Only the left.. I guess Ill have to start making all my calls right handed.
It figures...
Us southpaws always get the short end of the stick. FWIW, I almost always hold my phone(s) left handed, and only rarely seem to have this problem. ( It might just be that I have a huge head, and big ears. )
Im a righty and sometimes when making calls i get a haptic vibration from my face touching the nav buttons i think, nothing happens though.
My girlfreind is having the same issues with her handset.
We found her an Aria about 2 weeks ago at Best Buy Mobile for $1. They are running some great special for non-iphone handsets. The Aria was giving her problems and we ended up exchanging it. The 2nd Aria also has the same issue. While on the phone, her cheek will press random buttons and even hang up. Sometimes she just feels vibration, sometimes its a number pad press, and sometimes she just hangs up all of a sudden.
It seems to be some sort of sensor issue. Does anyone have some insight as to how to fix it? It's kinda of a big deal if the phone function is impaired by having to hold it away from your face.
Thanks!
NomeUF said:
My girlfreind is having the same issues with her handset.
We found her an Aria about 2 weeks ago at Best Buy Mobile for $1. They are running some great special for non-iphone handsets. The Aria was giving her problems and we ended up exchanging it. The 2nd Aria also has the same issue. While on the phone, her cheek will press random buttons and even hang up. Sometimes she just feels vibration, sometimes its a number pad press, and sometimes she just hangs up all of a sudden.
It seems to be some sort of sensor issue. Does anyone have some insight as to how to fix it? It's kinda of a big deal if the phone function is impaired by having to hold it away from your face.
Thanks!
Click to expand...
Click to collapse
Other then making sure her head is covering the sensor, she canlock the phone in mid call and it should stop her phone from registering her cheek while on a call
Sent from my Behold II using XDA App
ryan92084 said:
if you use your left hand/ear its pretty easy to dodge the sensor, unfortunately.
Click to expand...
Click to collapse
Huh. I'm a righty, but I talk left hand / left ear, and I never have any problems. Do you tilt the phone in some strange way?
Sent from my HTC Liberty using XDA App
psychoace said:
Other then making sure her head is covering the sensor, she canlock the phone in mid call and it should stop her phone from registering her cheek while on a call
Sent from my Behold II using XDA App
Click to expand...
Click to collapse
Thats a good idea. Thanks.
This issue is really pissing me off. I love this phone a lot but the proximity sensor is not working as it should, atleast with my head shape.
Seems almost in every other call I make/receive my cheek contacts the screen and pushes something because the proximity sensor is not detecting me head.
I've tried locking the phone with the button on top of the phone but that does not work, it's only temporary until the proximity kicks back in.
And, the funny thing is, when I try to "test" it out or replicate the situation I can never seem to do it again! It always happens unexpectedly.
I'm in the same boat with this too, but it's a hit or miss thing and really could be much worse.
Sent from my HTC Liberty using XDA App
i can't say i've ever run into this specific problem. i've actually been impressed with how well the sensor has been working.
i would agree with the previous poster who suggested to lock the screen once the call is active. make your call then tap the power button to lock the screen and that should help you avoid the issue.
mattbollenbach said:
i can't say i've ever run into this specific problem. i've actually been impressed with how well the sensor has been working.
i would agree with the previous poster who suggested to lock the screen once the call is active. make your call then tap the power button to lock the screen and that should help you avoid the issue.
Click to expand...
Click to collapse
This doesn't work unfortunately.
Sent by Aria
Hi guys just wondering if you noticed this strange behaviour.
I noticed a quite frustrating delay after a call when i take the phone away from my ear, it takes 2-3 sec for the screen to turn back on.
Has anybody experienced the same?
Do you know if there is a solution for this?
Sent from my GT-I9100 using XDA App
yes, think its normal. looks like the same delay when pushing power button for screen on.
sent from my SGSII via T*patalk
Thank you.
That seems strange as it is something really basic that you expect to work in a phone of this price range. Moreover it's something you come across quite often.
Do you know if the latest firmware improves this?
Sent from my GT-I9100 using XDA App
i am on ke7, so no.
sent from my SGSII via T*patalk
Cuz80 said:
Thank you.
That seems strange as it is something really basic that you expect to work in a phone of this price range. Moreover it's something you come across quite often.
Do you know if the latest firmware improves this?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
You can just turn off the sensor in the call app, if you want your screen to be available just after a call.. I don't see the problem.. but my delay is also just around a second or so.
mljjlm said:
You can just turn off the sensor in the call app, if you want your screen to be available just after a call.. I don't see the problem.. but my delay is also just around a second or so.
Click to expand...
Click to collapse
But if I do that i will drain battery unnecessarily. I don't know you guys but I find it really annoying having to wait 2sec after a call for the screen to wake up. I want to be able to hang up immediately i think I'm not asking something ridiculous.
Sent from my GT-I9100 using XDA App
you can also set the power button to terminate the call and you will not have to wait for the screen to turn on...
Reading the data from an analogue sensor (such as the proximity one) is always tricky... You need time to level out the values coming back from it, then determine that, over a period of time, the distance is suitable to enable the screen.
Only then can it be turned on etc
dfi2k5 said:
you can also set the power button to terminate the call and you will not have to wait for the screen to turn on...
Click to expand...
Click to collapse
How do you go about doing this? Can it be changed in the setting sor does it require a separate App?
xiga said:
How do you go about doing this? Can it be changed in the setting sor does it require a separate App?
Click to expand...
Click to collapse
Pls go to settings then call then calls answering ending and tick power key ends calls
Yes i find this very annoying too!
Especially when on a call center, press 2 (wait for screen) then press 4 (wait for screen) you get the idea
this is actually the only problem i have with the SGS2 since ke7
Sent from my GT-P1000 using XDA App
pulser_g2 said:
Reading the data from an analogue sensor (such as the proximity one) is always tricky... You need time to level out the values coming back from it, then determine that, over a period of time, the distance is suitable to enable the screen.
Only then can it be turned on etc
Click to expand...
Click to collapse
sgs 1 managed it fine though?....or am i missing something
Yeh my i8000 had no delay with the proximity censor.
But the screen delay seems to be everywhere. Turning on from sleep, time to adjust to ambient light and obviously the proximity sensor after pulling it away from your face.
Its not a major drama for me but I agree that it would be good to not have the delay.
I just noticed that when I use Skype the sensor works really well, meaning there is almost no lag.
I'm confused..
Sent from my GT-I9100 using XDA App
Yes! Very annoying.
Yep! I was commenting on this the other day. To be honest, I make and receive very few calls from my phone but when i do, I feel the rage rising inside me everytime because of the sensor delay.
It's the small things that annoy you the most.
As mentioned, you can opt to have the power button hang up the phone. It also does not turn the screen off, so you can continue working on the phone.
This is actually under accessibility settings, not call settings.
Menu -> Settings -> Accessibility -> Cancel the prompt -> Tick 'The power key ends calls'.
I also find the lag on waking up very annoying. Even once the screen has woken up, it takes a second for the touch input to be recognised so the pattern unlock only registers my last two or three inputs depending on how quickly I start swiping. I have to enter the pattern again. Very annoying.
pulser_g2 said:
Reading the data from an analogue sensor (such as the proximity one) is always tricky... You need time to level out the values coming back from it, then determine that, over a period of time, the distance is suitable to enable the screen.
Only then can it be turned on etc
Click to expand...
Click to collapse
I also have this problem, although I'd estimate it only takes about 1-1.5 seconds for the screen to come on.
I do however not think that this is a sensor problem, but rather a software problem.
Type *#0*# in the dialer, and press Sensor.
The phone will now vibrate once you trigger the proximity sensor. And it seems to be very fast and responsive here.
i have the problem using Skype...when i start a call it turns automatically the screen off ! i need then to push on home button to get out of skype...very ennoying...
last time i made an order online, my bank sent me a code by phone and following the instruction, the voice asked me to push the number i hear...i simply could not !! the screen was completely off ! and i could not succefully purchase online, my order was cancelled !.....due to this problem of screen..i think it is seriously ennoying and must be fixed in an update firm or something .
Agreed, this is a very annoying and unnecessary delay. Especially coming from an iPhone, where the screen turns on instantaneously when removed from the ear.
Hoping for a fix.
im ready to pay to get this fixed
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.
Anyone else have proximity sensor issues on the G2? Ever since I got it, it's been very wonky, even when it was purely stock. The worst problem is often when I take the phone away from my ear it doesn't turn back on, and then it seems that the knock on sensor stops working, and I have to hit the power button. Sometimes when I put the phone to my ear when getting a call the phone goes to sleep and the call gets cut off.
I do have it set to automatically answer the phone when I raise it to my face, so maybe that's an issue. I'll disable that and see if it helps.
Anyone else? I'm kind of bummed as I use my phone as a phone first and having something like the proximity sensor work is absolutely crucial in my phone use.
spinedoc said:
Anyone else have proximity sensor issues on the G2? Ever since I got it, it's been very wonky, even when it was purely stock. The worst problem is often when I take the phone away from my ear it doesn't turn back on, and then it seems that the knock on sensor stops working, and I have to hit the power button. Sometimes when I put the phone to my ear when getting a call the phone goes to sleep and the call gets cut off.
I do have it set to automatically answer the phone when I raise it to my face, so maybe that's an issue. I'll disable that and see if it helps.
Anyone else? I'm kind of bummed as I use my phone as a phone first and having something like the proximity sensor work is absolutely crucial in my phone use.
Click to expand...
Click to collapse
I've noticed that everything works well with this. Surprisingly so. On the s3 i would always get the black screen issue when pulling away from my ear. Ringtone even lowers as i pick it up. I could never get that to work on my s3. Not that, that matters.
spinedoc said:
Anyone else have proximity sensor issues on the G2? Ever since I got it, it's been very wonky, even when it was purely stock. The worst problem is often when I take the phone away from my ear it doesn't turn back on, and then it seems that the knock on sensor stops working, and I have to hit the power button. Sometimes when I put the phone to my ear when getting a call the phone goes to sleep and the call gets cut off.
I do have it set to automatically answer the phone when I raise it to my face, so maybe that's an issue. I'll disable that and see if it helps.
Anyone else? I'm kind of bummed as I use my phone as a phone first and having something like the proximity sensor work is absolutely crucial in my phone use.
Click to expand...
Click to collapse
Yes, but not all the time. When it does happen, i can't get the screen to come back on at all until after the call ends. It doesn't do it on every call but when it does it's really bad.
I'm running tge Verzion Clean Rom right now but it did it on the unrooted stock too.
I have a crack in my screen which seems to make the phone's sensor think it's constantly pressed against my ear, thus not allowing me to use the keypad during calls, switch apps during calls, and on incoming calls, not even hang up.
I was wondering if anyone knew of any way to disable the automatic screen shutoff so I can get around this. I am using CyanogenMod 10.2 on a rooted Sprint galaxy s4, but have had the same problem with the derrick Samsung os.
Thank you, and if I'm posting this in the wrong place, apologies and please let me know where it belongs!
Sent from my SPH-L720 using xda app-developers app
The screen off during calls is controlled by 1 of the top sensors, not by screen touch...Maybe there is damage to or on the surface area above the sensor...
shmulie said:
I have a crack in my screen which seems to make the phone's sensor think it's constantly pressed against my ear, thus not allowing me to use the keypad during calls, switch apps during calls, and on incoming calls, not even hang up.
I was wondering if anyone knew of any way to disable the automatic screen shutoff so I can get around this. I am using CyanogenMod 10.2 on a rooted Sprint galaxy s4, but have had the same problem with the derrick Samsung os.
Thank you, and if I'm posting this in the wrong place, apologies and please let me know where it belongs!
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I know you're on CM but here's how it's done in stock, you can toggle the "Turn off screen during calls" when you bring up the dial pad and hit menu then call settings.
Unselecting that item keeps the screen on as it won't use the proximity settings (like when you put it to your ear) to turn off the screen...which is essentially what you've already described that you think is occurring with the crack in your screen...
hope that helps.
sainthooligan said:
I know you're on CM but here's how it's done in stock, you can toggle the "Turn off screen during calls" when you bring up the dial pad and hit menu then call settings.
Unselecting that item keeps the screen on as it won't use the proximity settings (like when you put it to your ear) to turn off the screen...which is essentially what you've already described that you think is occurring with the crack in your screen...
hope that helps.
Click to expand...
Click to collapse
Never noticed that, thanks! I wasn't able to find something similar in my OS. I love CM, but I might have to switch back to stock for this.
Btw I also noticed it's accessible through settings > my device > call in stock.
Anyhow, instead of moving from CM, have you tried something like this app to turn off the sensor in calls https://play.google.com/store/apps/details?id=com.itsme4ucz.screenoff
or tried to use the Tasker app to toggle it off? might be worth a shot.
EDIT:
There was a mod for this, so you're likely to find something around that will coincide with what your running on yours - see this: http://www.modaco.com/topic/362514-mod-disable-proximity-sensor-cm101-based-roms-only/
also have you seen this thread on issues with this in CM http://forum.xda-developers.com/showthread.php?t=2409698 ?
AND the other option is to try blowing air in might help, just in case it isn't related to your screen crack....see also: http://forums.androidcentral.com/sa...edition/311795-s4-proximity-sensor-issue.html
(Proximaty sensor repairs/reset ) app in Google play fix the problem