hello all. noob here...but i ain't scared!! full disclosure...i probably eff'd up somewhere along the way in upgrading but after the upgrade i'm seeing issues where my display power settings don't seem to be applied. this is especially true when i'm on a call. the screen will go black after about 15 secs...my setting is set to 2 mins. is this normal behavior with this rom?? or is something hosed? thanks for any help
If your talking about your display going off while you are on a call and putting the phone to your ear then it is supposed to do that. It is a proximity sensor in the phone and it does it so you don't accidently hit a button with your check while on the call.
appreciate the reply. well continuously muckin' with it seems to have things workin' as designed now...not sure what the issue was. and no ,this was happenin' when i was on a call usin' my bluetooth earpiece. i think the 2 min setting was somehow being seen as 15secs...computers!!??
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
Hello,
I have the i9505 and i have flashed it with [ROM]【4.4.4】Google Play Edition 07-17-2014 - Pure Nexus Edition build now available by @Danvdh and i absolutely love this ROM and works like a charm but there is one thing i am having issue with and i cannot say its a bug as looked over his thread but no one has mention it. i can comment or post in the developer thread due to the number of posts i have, however i come here to ask for help.
When I make a phone call, my screen goes completely black and when i try wake the screen up, it would take multiple times and sometimes i have to take the battery out. The call somehow runs in the background, so if i managed to wake the phone, i have to pull the notification down fast to hang up and this is pain in the neck.
I suspected it could be the proximity sensor in my phone, i have no cover or screen protector, i cleaned the screen and still the same. so i ran few tests to check the sensor. phone detects the sensor but it doesn't do anything.
Thank you in advance
after many research, i have found the issue and its fixed.
http://forum.xda-developers.com/showthread.php?t=2569141
you will need to reset the proximity sensor depending on the values. i can say all working now
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.
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Sounds like Doze.
I don't find anything related to Doze or "standby" about this screen.
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
David_26 said:
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Click to expand...
Click to collapse
thophan1975 said:
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
Click to expand...
Click to collapse
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
Sounds like there is an issue with the proximity sensor (not light sensor).
It's setup to turn the second screen off as well as disable knock on if the phone is in your pocket. Even during daylight hours if you put your finger within an inch of the sensor when the main screen is off, it should trigger it.
It seems your sensor may just be messed up.
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
There are a few apps on the play store you can try to fix it if you are rooted. You could also try a sensor app to see if the proximity sensor is showing feedback properly although you might need to be rooted for the apps to show the proximity sensor properly (not sure). My note 4 had a hardware test in the service menu not sure how to do it on V20 though.
Same Issue
Edit: Resolved the issue. Please read this post. There is a small rubber gasket-type thing that sits in the hole of the phone's frame where the proximity sensor is positioned. That rubber gasket was not included with my replacement screen. I pulled the rubber piece out of my original, broken screen, and installed it into my replacement screen. I am no longer having issues with the phone in the dark.
I am experiencing the same issue. I have a T-Mobile LG v20 (H918) and I cracked the screen last week. I ordered a replacement LCD assembly and installed it myself. Everything works fine during the day or in a well lit room, but at night, in a dark room, I experience all of the issues you are reporting. I am finding other posts online with our same issue, but as of yet, no resolution.
Even though the second screen is set to always be on, at night, in a dark room, it turns off almost immediately after locking the phone. It is almost as if the phone is in a "deep sleep" or something, because the following also occurs:
Knock On will not wake the phone
Fingerprint sensor will not wake the phone
Even connecting to the phone via AirDroid / AirMirror the phone doesn't wake
Need to press the power button multiple times to wake phone
Providing a light source immediately turns on second screen and resolves all issues