When I first purchased my AT&T Galaxy Note about a year ago, if the screen went black during a call, I could shake the phone and the screen would illuminate. Since then, I have updated to ICS. Now when I am on a call and the screen goes black, it does not illuminate when I shake the phone. I don't know when this change occurred, so I can't be sure that it was caused by updating from Gingerbread to ICS, or caused by something else. I am aware that there are some apps out there to provide this feature, but I have never installed one, nor am I aware of any apps that I may have deleted to cause the loss of this feature.
Any suggestions?
It didnt wake becuse you gave it a shake. It woke because you moved it away from your face. The note has a proximity sensor. You can set that in the phone settings.
Related
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
What phone are you using? Software version etc and are you rooted? This doesn't happen to me so it's not a general android issue.
Sent from my Galaxy Nexus
I have the Moto Droid X. Running CyanogenMod 7.1. Also using exDialer as a dialer replacement.
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
RTContent said:
Does it happen with the stock dialer? If not that's your answer
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yep it happened with the stock dialer on ICS and it is happening with JB as well. I am really surprised it doesn't bother more people. What is most annoying is that, I initiated a new call and put my phone to my ear to only that the call did not even establish (e.g., due to network iss ue) and when I want to place the call again, it is already locked. It is definitely due to the proximity sensor, as the same thing doesn't happen if i never put the phone to my ear and just keep watching the screen to confirm that the call did get established (and started ringing).
njmsmith said:
I am a new android owner. When I make a phone call the proximity sensor turns the screen off... great, no accidental screen pressing. However, when I finish the phone call or take the phone away from my ear... I get the lock screen. Why? Why doesn't the screen just go back on to whatever screen was on before the phone call... like the dial pad.
I find this annoying. To hang up a phone call, I have to unlock the screen first.
Click to expand...
Click to collapse
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
SachinShekhar said:
If you are rooted, disable your Proximity Sensor in a call. To do so, add following line to /system/build.prop file:
Code:
gsm.proximity.enable=false
.
Plus, make sure to make screen timeout period long. You can use Widgetsoid app (or, other toggle apps) to make it infinite.
Click to expand...
Click to collapse
I have display timeout set to 2 minutes, so that can't be the problem, as the whole experience when the call is not connected only takes 10 or 15 seconds to complete. However I have security setting to lock the screen in 5 seconds after the display goes to sleep. Perhaps that is somehow related, so I just increased it to 30 seconds, I will see if the problem goes away.
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
mrcash101 said:
I have Speed Rom 5.1 on my Amaze. When I am finished with a call, the screen stays black. I try to hit the power button, but nothing happens. I have to remove my battery in order to reboot. Can someone shed some light on why this happening? I am thinking that it may have something to do with my CPU Tuner settings, but I am not sure.
Click to expand...
Click to collapse
Probably that or a bad flash, just reflash, see if it solves the issue.
Most likely it's something simple, like an issue with your proximity sensor. I know there was an app that could calibrate that but I forgot what the app was.
Stock Rom - Black screen while phoning
There is a similar problem on my wife's phone with a stock rom (not rooted Amaze from T-Mobile). When making or accepting a call, the screen will instantly go off even without leaning the phone against anything and won't turn on unless the power button is pressed. Sometimes the screen would turn on by itself after a while after the other phone was hanged.
I've downloaded AndroSensor app: the proximity value does't change even when touching the area near the earpiece. It keeps showing ( 0.5mA ) 3.5 in.
I've found a thread which is there since april 2012 and describes quite a similar problem.
okay.. i just the original post date for this thread.. please don't bring back threads that are 6 month's old which issues might have been solved already since no ones been posting in it for 6 months...
(anyways) this is what i was gonna say
on my current s3 when my phone is placed to my ear it cuts off the display.. and if you pass your hand anywhere near the sensor's to the top near the camera it cuts off the display.. maybe there's a feature like that enabled on the stock rom also.. or you could possible check with the system settings to see "screen" on/off settings in display or power saving mode.. or something...
Thanks for the answer. I didn't notice that the thread was that old. I think I will keep up a newer one. But the current issue isn't likely to have been solved.
The problem doesn't seem to be triggered by wrong sensor measures (because the screen will go off even after disabling the sensor) nor does it depend on the rom version (same thing on the CM10).
Resolved:
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
Hello people,
I flash the ROM "CM 10.1 (Android 4.2) for Atrix" with the new kernel today and at the beginning everything worked fine.
But after a few minutes setting up the phone, the screen started shaking a moment until the display turn off (turn off but the phone is still working as if the touch also responds and physical keys are lit). When locking and unlocking the phone, the screen returns to normal.
I realized that the longer I leave it off, the longer it takes to give this bug, after turn on the screen again.
The brightness is at maximum and the phone is not too hot.
At least the phone stopped rebooting but play or do anything else is impossible (I can only make calls) because of this bug.
Any idea why this is happening?
Hi guys.I have a problem with my LG G2 D802.When I answer a call or make a call,the screen goes blank and the touch doesn't work anymore.I can't do anything else on the phone.The conversation is normal and anything else seems to be ok.Please help! Thank you.
If I answer a call,the screen goes blank,I can speak normally:After the call even the other person finishes the conversation,I still can't do anything on the phone,because the screen stays blank.If I have another call this will awake the screen and it will work normally,I mean,I can take the call,answer and speak on the phone but with the screen blank again. and so on.To have the phone back to normal,I have to reboot it by switching the phone off and on again. Very strange.This happened after I unlocked the phone ,probably because I left the SIM card in ?!!! Any possible advice/solution? I tried soft and hard/factory reset with no results.
help reguading the g2 screen blackout during calls
madafis said:
Hi guys.I have a problem with my LG G2 D802.When I answer a call or make a call,the screen goes blank and the touch doesn't work anymore.I can't do anything else on the phone.The conversation is normal and anything else seems to be ok.Please help! Thank you.
If I answer a call,the screen goes blank,I can speak normally:After the call even the other person finishes the conversation,I still can't do anything on the phone,because the screen stays blank.If I have another call this will awake the screen and it will work normally,I mean,I can take the call,answer and speak on the phone but with the screen blank again. and so on.To have the phone back to normal,I have to reboot it by switching the phone off and on again. Very strange.This happened after I unlocked the phone ,probably because I left the SIM card in ?!!! Any possible advice/solution? I tried soft and hard/factory reset with no results.
Click to expand...
Click to collapse
I actually had this same issue. my g2 is rooted, but running the stock rom. it has a screen protector but nothing else that would impede the sensors.
I found that this issue never took place in well lit areas. but if at night sitting i a poorly lit room I would go to swipe the scree it would unlock for a second or two and then lock back up. in talking with a friend. I found that the g2 has in set so in the proximity of a pocket or something dark the screen dims back so as to not allow you to mistakenly hit ay button ( i.e. butt dial) i figured my proximity sensor near the ear piece was dirty and causing much less light then there actually was. at the time there wast a firmware update ( which I have now gotten) and was desperately seeking help.
I finally got the firmware update VS98012B and it seems to have solved the issue I ( and you) was having. I would see what version you are running now and then update to the aforementioned and see if that solves your problem.
PM me and let me know what road you decide to travel and if for some reason it doesn't help you we shall figure it out.
Blank Screen
I am having sort of the same issue. But mine is wether in a well lit room or dark room it doesn't matter.
I noticed that it usually happens when i receive a call, after the conversation when i hang up it does not go back to the home screen. all i get is a blank screen. the only way i can get it to generate the home screen again is by pulling down the status bar and going into the general settings and clicking home button again.
during this blank screen i can still see the status bar, and when i bring down the status bar i can see the nav buttons but they are unresponsive.
I also noticed this takes place sometimes after closing an app (noticed on netflix)
I am rooted on stock rom and TWRP recovery. Phone Model [LS-980 Sprint]
I immediately rooted so dont know if issue was there before root.
SOMEONE PLEASE HELP.
Bam9 said:
I actually had this same issue. my g2 is rooted, but running the stock rom. it has a screen protector but nothing else that would impede the sensors.
I found that this issue never took place in well lit areas. but if at night sitting i a poorly lit room I would go to swipe the scree it would unlock for a second or two and then lock back up. in talking with a friend. I found that the g2 has in set so in the proximity of a pocket or something dark the screen dims back so as to not allow you to mistakenly hit ay button ( i.e. butt dial) i figured my proximity sensor near the ear piece was dirty and causing much less light then there actually was. at the time there wast a firmware update ( which I have now gotten) and was desperately seeking help.
I finally got the firmware update VS98012B and it seems to have solved the issue I ( and you) was having. I would see what version you are running now and then update to the aforementioned and see if that solves your problem.
PM me and let me know what road you decide to travel and if for some reason it doesn't help you we shall figure it out.
Click to expand...
Click to collapse
I decided to open the phone and check the proximity sensor.I unplugged the proximity sensor ribbon and guess what:IT WORKS.without the functions of the proximity sensor and LED.But at least,I have the keypad and the screen on during a conversation.I have even the knock-knock function.Probably,I will use it like that until a kit-kat update will be available.Thanks for your answer.
VS980 Black Screen
I have a customer phone that I replaced the LCD and Digitizer on. The new screen works fine but...now when a SIM Card is in the phone and I dial out a thin horizontal line appears in the middle of the screen and then the screen goes black.
If I remove the SIM card and place a call, the phone gives me the standard "Emergency Calls Only" and goes back to the dial pad.
The SIM Card is not activated but it is recognized by the phone.
Has anyone else had this issue? I tried a factory restore with no luck.
madafis said:
I decided to open the phone and check the proximity sensor.I unplugged the proximity sensor ribbon and guess what:IT WORKS.without the functions of the proximity sensor and LED.But at least,I have the keypad and the screen on during a conversation.I have even the knock-knock function.Probably,I will use it like that until a kit-kat update will be available.Thanks for your answer.
Click to expand...
Click to collapse
Hi,
I have the same issue , my screen turns black when calling or receiving calls , i m not really good with my hands... so do you know other solutions to disable the proximity sensor ?
thanks
Same issue here - LG G2 screen turn off and goes blank during conversations
I have exactly the same issue - LG G2 D802 screen turn off and goes blank during conversations.
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!
Another issue which I also have and is also caused by the proximity sensor is that the screen stays on and the touch buttons in the dialer aren't responsive - which means we can't switch to speaker, add a call, mute, etc... However, the main touch / navigation button (home, back and menu buttons in the bottom of the screen) are responsive, in addition to the status bar.
(This issue was already reported by @athorax 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.
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.
Bam9 said:
I actually had this same issue. my g2 is rooted, but running the stock rom. it has a screen protector but nothing else that would impede the sensors.
...
i figured my proximity sensor near the ear piece was dirty and causing much less light then there actually was. at the time there wast a firmware update ( which I have now gotten) and was desperately seeking help.
...
I finally got the firmware update VS98012B and it seems to have solved the issue I ( and you) was having.
Click to expand...
Click to collapse
So for you it was a software issue?
Is your sensor working until today with no issues?
ingoljosh said:
I am having sort of the same issue.
...
I am rooted on stock rom and TWRP recovery. Phone Model [LS-980 Sprint]
I immediately rooted so dont know if issue was there before root.
Click to expand...
Click to collapse
I'm also rooted and with TWRP.
Did it happened before you rooted?
Did you used ioroot to root andAutoRec to have TWRP?
You see, I'm really trying to find the similarities between us all in order to solve this issue...
madafis said:
I decided to open the phone and check the proximity sensor.I unplugged the proximity sensor ribbon and guess what:IT WORKS.without the functions of the proximity sensor and LED.But at least,I have the keypad and the screen on during a conversation.I have even the knock-knock function.Probably,I will use it like that until a kit-kat update will be available.
Click to expand...
Click to collapse
We already have KitKat based firmware update. For me it's D80220C.
For you it might be already D80220D. Use this link to check your version, and replace the IMEI in the end of it with your IMEI.
BobbyLG said:
...now when a SIM Card is in the phone and I dial out a thin horizontal line appears in the middle of the screen and then the screen goes black.
If I remove the SIM card and place a call, the phone gives me the standard "Emergency Calls Only" and goes back to the dial pad.
Has anyone else had this issue? I tried a factory restore with no luck.
Click to expand...
Click to collapse
When you place the call you do hear that the call is made?
If so - then you have exactly the same issue.
What is your model, what ROM are you using, and did you root your phone?
I have LG G2, unable to make call. The signal strength is fine. I have tried reinserting the sim. but i am able to receive calls. when i make a call the dialup screen come up and call ended automatically. Any Help
I purchased my S21 about 5 weeks ago and I am not sure if I have been experiencing this issue since I bought it but in the last week, I have noticed this issue. When my phone is locked, the AOD will either show for a few seconds to a minute or just won't show. I've ensured it is set to always show, power-saving not set to turn it off, no Bixby routines and any updates are installed for phone/AOD. I've even factory reset my phone and removed the case and screen protector and the issues are still persisting. Does anyone else experience this issue?
Disable all power management... it screws up all kinds of things.
Does AOD show if you tap the screen?
I have disabled all power management that I am aware of and still experiencing issues. I've set it to show on tap and while it worked the first time, subsequent taps do not show the AOD
Video demonstrating AOD tap to show issue
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
blackhawk said:
Sounds like a firmware glitch or the flash was corrupted.
Double check all AOD and screen lock settings.
Try turning AOD always on.
Try disabling screen lock... a lock out is the last thing you want anyway.
Play with it... Android's wuv attention.
The case or screen protector won't do this more than likely.
Click to expand...
Click to collapse
I normally use AOD always on, I'd tried the tap on the option to test. Going to try flashing it today to see if that helps despite the factory reset not helping.
So I've flashed the stock firmware back onto my device and the issues are still persisting. I've contacted support through the Samsung Members app and it's been escalated to the Research and Development team and am just waiting to hear back.
Did you update any Samsung apps after the reload before testing it? Go with the factory app loads.
Try disabling the lock screen... they tend to end up locking out the intended user anyway, sooner or latter.
If no one else is having this issue it very well maybe a hardware issue.
Did you ever wonder what happens when one or two micro transistor junctions out of the millions in a phone fail? Yes, well...
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
The you
brodieb321 said:
Unfortunately I can't recall if Samsung apps updated before I tested. I've already factory reset a few times so I'd rather avoid that for now. I've noticed the issues occur when using auto-brightness on AOD in lower light settings. When I say lower light, I mean in my study during the day which I never experienced issues with on my S20 FE. I've sent a report to Samsung Members and am waiting on them to come back to me.
Click to expand...
Click to collapse
Did you ever get this fixed. I have the exact same issue on my s20 ultra
Edit: Nevermind just fixed it after 3 days troubleshooting. Oddly it was the the disable AOD while in power saving mode that needed to be disabled even though I don't use power saving mode. Samsung never seem to amaze me with these dumb persistent bugs.
Glad to see you solved the issue. I'd already confirmed this setting was off for me. It's still happening. Looks like it's something to do with the level of light detection as the issue only happens when I have auto brightness set for the AOD. The problem is it's not even that dark when it's happening and never occurred with my S20 FE.