Hi All
Just received the phone and all in all very impressed bar for one very annoying bug. When calling an automated line requiring keypad responses, as soon as i remove my the phone from my face and attempt to invoke/press the keypad it dissapears. This happens repeatedly until i hold the phone at arms length so presumably the problem is the proximity sensor that kills the screen when the phone is up against your head.
Anyone else witnessed this?
C
Related
I have got the problem that sensors turn out my screen after calls start (incoming/outgoing) and it does not activate again when I want to end the call.
I have realized that after a call is started and the phone is moved (e.g. after typing a number, dialling and then move the phone to your ear) that this (or actually any movement) locks the screen.
I have realized that the movement actually activates the 'dial pad' (just as you would press the icon on the screen during a call) but somehow also fully de-activates the screen. You can get the screen activated again only by sliding the hardware keypad out. Then you can press 'x' on the screen to get back to the normal call screen (and then end the call normally).
I have got the 2nd SK17 now and it has got the same issue regardless which firmware I use (branded 4.0.A.2.335 from vodafone, 4.0.A.2.335 Generic or 4.0.2.A.0.58 Generic).
Anyone else got this issue and has got a solution.
Same here. its because of the light sensors.
http://forum.xda-developers.com/showpost.php?p=18404603&postcount=6
heres a guide to turn it off
Thanks for the quick response. Much appreciated.
However, I am afraid this does not resolve the issue. When applying as described in the guide the screen is de-activated straight after answering a call (without moving the device) and even when sliding the hardware keyboard out and pressing 'x' on the screen (to return to normal call screen) and then close the hardware keyboard again the screen is de-activated straight.
Ending calls now is only possible when the hardware keyboard is slided out.
Before applying as described in the guide at least the screen returned to be active after sliding keypad out, pressing 'x' and sliding keypad back in (and then not moving the device).
Therefore I have reverted back to what is was before for the time being.
Any other thoughts, hints, help.
----------
UPDATE 2011/11/27:
I have got my SK17 exchanged again (got the 3rd one now) and on this one it does not occur respectively call screen and sensors work perfect. Finally SE or vodafone seem to fix it on newly produced devices.
Hi!
I have a peculiar problem with my Lumia 920. During a phone call the screen is black and unresponsive. I can't hang up, and I always have to wait for the other person to do so. Then after 5-10 seconds, it wakes up and I see the call log. If I quickly tap the sleep button I see the ongoing call screen for a split second.
Any ideas why this may happen? Is it happening to you? I'm on Portico.
did you use any screen protectors? this can happen when proximity sensor is blocked or malfunctioned...
also on black AT&T Lumia noticed gap between case and front camera and dust can enter and "broke" proximity sensor http://wmpoweruser.com/nokia-lumia-920-front-facing-camera-and-proximity-sensor-dust-fix-on-the-way/
also some people notice if press top left corner of phone temporally fix proximity sensor
This is because of Portico! After u update to 1308/1314 the issue will be fixed!
I just installed AOKP Unofficial 4.2.2 from this thread.
If I simply make a call, the proximity sensor functions as expected and near perfectly (I think there's slightly too much lag between removing the phone from one's ear and the screen coming back on... but not unbearable). With the keypad shown, I've found the behavior to be quite unpredictable. On my first call with the new ROM, I called my company voicemail and between inputting my password and cradling the phone, I could hear a bunch of key presses occurring. It ended up disconnecting the call. This is quite reproducible for me.
I'd like to know if this is a reproducible issue, intended function, and/or bug (which I will report if others can verify).
Method:
- Dial a number
- Set phone on table
- Put hand in viscinity of top of the phone
- Observe screen turning off and on as you move your hand over the sensor and then away
- Pull up keypad
- Repeat hand test and observe that the screen is not predictable
In trying this several ways, there's either a lag in detecting proximity, or it's just flaky. I actually find it really hard to reproduce consistently. Sometimes it actually will turn off (I can see peripherally that if I put it to my ear), however if cradling (with phone still well within what I could call "proximity" to my face/ear), it will dial numbers. In putting my hand in various positions over the phone, sometimes it turns off, sometimes not. With the keypad hidden, it turns off reliably 100% of the time.
The biggest difference I can reproduce is that if you put a single finger over the full width of the top of the phone (over the HTC logo -- the sensor is just to the left of the logo), it will reliably turn off the screen without the number pad, but not with it. I get that the sensor probably needs to account that one's fingers will be pushing on the screen to enter numbers, but something directly over the sensor (simulating an ear pressed to it) should turn it off even with the number pad shown, I would think.
Thanks for any suggestions of if you'd like any further information.
----------
ETA: S-off, unlocked bootloader, AOKP: aokp_jewel_unofficial_Mar-12-13, baseband 1.12.11.1210, Android 4.2.2.
Hi,
I've just had my screen replaced on the LG G5. However, post screen replacement I am facing the following problems:
- As soon as I dial a number the screen goes black and locks itself. I need to press the button at the back to unlock the screen.
- If i make a call using whatsapp, as soon as I hit dial the screen locks itself
I checked and it looks like my proximity sensor is not working. In the apps that I use to test it, it either just reads '0" for the proximity sensor or "NEAR".
Anyone else faced similar issues or have a solution?
I just had my screen/frame replaced and am having the same problem. Tap to wake rarely works and while making a call the display stays on while phone is to my ear. Did you find a fix?
I fixed my problem doing some Googling. I can't post the link to the thread but Google "LG G5 Proximity Sensor Reddit mobile repair".
"I had a similar problem. I replaced my display/frame myself and the tap to wake function rarely worked and the phone display would stay lit when held to my ear. Following the advice here, I found that there was a rubber grommet around the prox sensor window on the old screen that I hadn't transferred over. It's very hard to see and almost looks like it is molded into the frame. I dug it out with some tweezers and transferred it over and it is back to normal."
Been using my Pixel 6 for my daily driver since I received it after launch. Recently, I have had quite a bit of trouble with the phone screen waking in my pocket and calling random people or 911 (emergency services) or just filling the PIN unlock screen with random numbers. I believe the screen is interacting with the fabric of my clothing. I make sure to power off the screen before I put it in my pocket, and facing the screen outward instead of inward seems to make a bit of a difference. I have scoured the settings and can not find anything. The only other option I see is a full wallet type case that closes over the phone so there is no way anything can interact with the screen. This started happening with alarming frequency in April.
Am I missing something? Any suggestions on how to prevent this? Turning off wake from notifications?
Thanks in advance!
draexo said:
Been using my Pixel 6 for my daily driver since I received it after launch. Recently, I have had quite a bit of trouble with the phone screen waking in my pocket and calling random people or 911 (emergency services) or just filling the PIN unlock screen with random numbers. I believe the screen is interacting with the fabric of my clothing. I make sure to power off the screen before I put it in my pocket, and facing the screen outward instead of inward seems to make a bit of a difference. I have scoured the settings and can not find anything. The only other option I see is a full wallet type case that closes over the phone so there is no way anything can interact with the screen. This started happening with alarming frequency in April.
Am I missing something? Any suggestions on how to prevent this? Turning off wake from notifications?
Thanks in advance!
Click to expand...
Click to collapse
Sorry for not being able to add anything other than I too am experiencing this issue, exactly as described.
I think it could be the double tap to wake I wear jeans and don't have that problem but 8 am using a pixel 6 pro though
Same issue here.
Please use the feedback form in device settings -> about the phone to send the bug report to Google as well.
Thanks!
this never happened to me.
are you using screensaver? AOD? any kind of app which controls the screen on/off?