Ever since I've bought OnePlus 7T, the proximity sensor is giving me a lot of problems. Sometimes the screen lights up while I'm speaking on the phone and the speaker is activated. Sometimes the call gets recorded. Sometimes if the phone is in my pocket and I try to unlock it, it says too many attempts.
Yes it very annoying, when removing it from pocket accidently my fingerprint matches and something something happens.
vinay3190 said:
Ever since I've bought OnePlus 7T, the proximity sensor is giving me a lot of problems. Sometimes the screen lights up while I'm speaking on the phone and the speaker is activated. Sometimes the call gets recorded. Sometimes if the phone is in my pocket and I try to unlock it, it says too many attempts.
Click to expand...
Click to collapse
It's issue on most OnePlus phones.. I had the issue on 6T, 7 Pro.. annoying
1rahul1996 said:
Yes it very annoying, when removing it from pocket accidently my fingerprint matches and something something happens.
Click to expand...
Click to collapse
This is the biggest reason I may be going Pixel 4...
Yes I too have this issue with my OP7T
Yup, same issue here.
Another thread about it here - https://forums.oneplus.com/threads/proximity-sensor-doesnt-work.1147600/
Also issue present on OP7Pro forums.
Seems to be related to this "Virtual Sensor":
https://www.ellipticlabs.com/2019/0...eaner-design-to-oneplus-7-series-smartphones/
So we have to wait and hope (could be this same as Never Settle? :d) that can be fixed with a software update.
It seems to get worse the more I use my phone. Anyone else notice this? Brand New it never did it
Josh McGrath said:
It seems to get worse the more I use my phone. Anyone else notice this? Brand New it never did it
Click to expand...
Click to collapse
Someone on the OP7T forum suggested it may be Tap the Screen to Show (let's call it TSS) feature.
I enabled DTW. This will trigger Ambient Display -> "Tap the Screen to Show" to be disabled.
Tried and the screen still won't turn off when on a call with the phone on my ear.
Both options disabled (no DTW and no TSS), still won't turn off.
What did work though, was to turn off screen once with the power button:
- I was in a call and the screen was on,
- turned off the screen using power button,
- I took the phone off my ear -> Screen on
- put the phone back on my ear -> Screen off
Maybe someone can make more sense of it.
trveller72 said:
Someone on the OP7T forum suggested it may be Tap the Screen to Show (let's call it TSS) feature.
I enabled DTW. This will trigger Ambient Display -> "Tap the Screen to Show" to be disabled.
Tried and the screen still won't turn off when on a call with the phone on my ear.
Both options disabled (no DTW and no TSS), still won't turn off.
What did work though, was to turn off screen once with the power button:
- I was in a call and the screen was on,
- turned off the screen using power button,
- I took the phone off my ear -> Screen on
- put the phone back on my ear -> Screen off
Maybe someone can make more sense of it.
Click to expand...
Click to collapse
I tried the above also same thing. I am tired of this BS. I am constantly pressing hold or dialing with my face unless I have the phone shoved in my ear. I almost didn't buy the 7t cause of this issue coming from the 6t with the same issue
Josh McGrath said:
I tried the above also same thing. I am tired of this BS. I am constantly pressing hold or dialing with my face unless I have the phone shoved in my ear. I almost didn't buy the 7t cause of this issue coming from the 6t with the same issue
Click to expand...
Click to collapse
Yeah, I am starting to remember good ol' days with the OPX. Every OTA was fixing one thing and breaking 3 other.
At that time I said no OP again, but still, this one seems to be be a good phone. Time will tell.
Coming back to our issue, I am puzzled that only a few people reported this.
Are you guys are on stock kernel or something custom?
I don't think I have this issue, but the sensor seems to function a bit differently from what I'm used to. When the phone is horizontal, covering the sensor does not turn off the display. But now do the motion of raising the phone to one's ear, and the display turns off. Just an observation, yet to experiment properly.
Does anyone know where the sensors are located on this phone? Is there a picture on the internet that points out the different sensors?
Edit: Yep. This one has a virtual sensor. It works differently.
roofrider said:
Are you guys are on stock kernel or something custom?
I don't think I have this issue, but the sensor seems to function a bit differently from what I'm used to. When the phone is horizontal, covering the sensor does not turn off the display. But now do the motion of raising the phone to one's ear, and the display turns off. Just an observation, yet to experiment properly.
Does anyone know where the sensors are located on this phone? Is there a picture on the internet that points out the different sensors?
Edit: Yep. This one has a virtual sensor. It works differently.
Click to expand...
Click to collapse
Not rooted, but using a custom dialer as the default Phone app (True Phone).
When I switched the default Phone app to Oneplus App, I could not reproduce the issue.
Testing for a few days to see if this works. Would be such a pity if the app is the problem because I really like it.
Also I just sent a log to OP support (they contacted me after I logged the issue on the feedback).
Yes, it is using the virtual sensor as you said (link in my previous post).
How does the virtual sensor work?
Sent from my [device_name] using XDA-Developers Legacy app
I couldn't find anything concrete on how this software-based proximity sensor, Elliptic Labs INNER BEAUTY, works. The keywords are: ultrasound, sensor fusion, and machine learning. A hardware-software I guess.
The 7T does have an IR sensor under the display, but I think this is only used for DT2W and Tap to Show to prevent the display from accidentally turning on when the phone is in the pocket and so on. Not for calls.
Fully Unmodified phone - same issue here. Phone regularly turns on airplane mode while I’m on a call cause it is registering face touches. Screen regularly flickers while on calls as if rapidly moving away from my face....
This was not a problem on my 3t a while ago and the issue is driving me to switch phones alongside some software instability (random lag and keyboard jitter) (animation issues after launcher swap) (soft-lock on navbar or gestures but not a play store replacement)I usually fix by rom swapping on one plus phones andddddd twrp is dead (for now) and no ones working on a valid replacement.
Will be keeping this phone in hopes of twrp eventual return, but need that stability
igotlostintampa said:
Fully Unmodified phone - same issue here. Phone regularly turns on airplane mode while I’m on a call cause it is registering face touches. Screen regularly flickers while on calls as if rapidly moving away from my face....
This was not a problem on my 3t a while ago and the issue is driving me to switch phones alongside some software instability (random lag and keyboard jitter) (animation issues after launcher swap) (soft-lock on navbar or gestures but not a play store replacement)I usually fix by rom swapping on one plus phones andddddd twrp is dead (for now) and no ones working on a valid replacement.
Will be keeping this phone in hopes of twrp eventual return, but need that stability
Click to expand...
Click to collapse
Twrp is out for the 7t. It's not flashable last I checked but it is bootable and usable for what I used it for which was a backup of stock rom
Related
Hi,
I'm using an original ROM for TP2 with Manilla 2.1.38158.2 (as shown in Settings | About).
AFAIK this version should include the "in-call curtain" functionality, on which the call buttons are locked during a call. However, I see no sign for this anywhere.
Does anyone have an idea how this feature can be turned on, or how do I add it?
The curtain is unnecessary. Your device as a proximity sensor that turns off your display when you hold you face it. You don't need the curtain to lock the buttons. When you move the device away from your face, you probably want to use the touch screen so it turns back on.
I usually talk using a Bluetooth headset while the device is kept in my bag or pocket. The proximity sensor should theoretically detect that the device is covered and keep the screen off, but it often fails to do so, allowing random buttons to get pressed.
S2U2 doesn't solve this either, as it keeps the device unlocked during phone calls. There's TouchLockPro, but I don't like the way it works.
Have you tried CSDEVCTRL? I recall it allows you to lock the device during and after a call.
Yes, I found it in one of the forums here a couple of weeks ago. For some reason it didn't keep the device locked during calls, though specifically configured to do so. I haven't looked deeper into that, since I thought that the supposedly built-in curtain would do.
BTW, a simple test shows that the proximity sensor is completely useless for this scenario. I put a small object on the sensor, locked the phone and turned it off. I then called it from another phone and answered using the Bluetooth headset. Although the screen was blocked with an object, it was completely unlocked and could be pressed. The proximity sensor turned the screen off only if a movement was detected towards the screen, and not when something was already blocking the screen.
I repeated this test several times with the phone in a bag. I locked it, called, answered using the Bluetooth headset and tried to press against it from outside the bag. In every single time on-screen buttons got pressed.
As a matter of fact, the TP2 is way worse than the original TP in this sense. In my previous TP I could answer a call using the headset, take out the phone (carefully so it won't hang up by a screen press), lock it again and put it back in the bag/pocket. Now with the TP2 the proximity sensor wakes up the device unexpectedly, so I can never keep it inside anything during a call.
There is a shareware Pocket Shield which provides a screen curtain. You may have a try for your TP2 at this link:
http://pocketshield.netserver01.com/download.htm
erezshermer said:
Hi,
I'm using an original ROM for TP2 with Manilla 2.1.38158.2 (as shown in Settings | About).
AFAIK this version should include the "in-call curtain" functionality, on which the call buttons are locked during a call. However, I see no sign for this anywhere.
Does anyone have an idea how this feature can be turned on, or how do I add it?
Click to expand...
Click to collapse
I tried installing the InCallCurtain from my Touch Pro ROM and it does not work with the TP2. It is a different dialer so the calls for the curtain may not be in there.
My phone has no problem turning itself off when it gets near my face. Why would you want a call curtain?
Kloc said:
My phone has no problem turning itself off when it gets near my face. Why would you want a call curtain?
Click to expand...
Click to collapse
Did you read the thread ?!
Thanks Angler, I just tested Pocket Shield. I must say I like the progress of this program since the last time I tried it.
I won't use it as a general lock utility because of a severe issue: for some reason my Bluetooth headset loses the ability to answer calls while it's locked. I click the headset button, the ring sound moves to the headset, and the call is not picked up.
I'm thinking about only using its curtain feature - use only the protection during phone calls without locking. This seems to work, however PocketShield locks my device whenever it powers on and I can't find a way to cancel that without completely turning it off. Any ideas here?
(edit: removed double post)
erezshermer said:
BTW, a simple test shows that the proximity sensor is completely useless for this scenario.
Click to expand...
Click to collapse
Prox sensors come in different types. They aren't all configured to turn off "when covered" by just anything. Since the primary purpose is to save screen power when held against your face, it may well be technically designed to detect things that can conduct electricity, like you. If you're curious about it, as I am, next time you test it, cover the prox sensor with your thumb.
If that doesn't work, I recommend on second test. Just because there is a prox sensor doesn't mean that HTC is using only that for turning off the screen. In order to avoid accidentally turning it off while you're trying to use it, which would be annoying, they might be using the accelerometer to detect whether it's being held like a phone or not, and not turning it off if it isn't. Test two is to hold it in a position at an angle as if you would if you were talking on it, and hold your thumb over the prox sensor.
I don't have my TP2 yet, that's why I haven't tried it myself. If you're already on to your current solution and don't want to I understand, but if you do, I'd be curious as to your results.
fortunz said:
Prox sensors come in different types. They aren't all configured to turn off "when covered" by just anything. Since the primary purpose is to save screen power when held against your face, it may well be technically designed to detect things that can conduct electricity, like you. If you're curious about it, as I am, next time you test it, cover the prox sensor with your thumb.
If that doesn't work, I recommend on second test. Just because there is a prox sensor doesn't mean that HTC is using only that for turning off the screen. In order to avoid accidentally turning it off while you're trying to use it, which would be annoying, they might be using the accelerometer to detect whether it's being held like a phone or not, and not turning it off if it isn't. Test two is to hold it in a position at an angle as if you would if you were talking on it, and hold your thumb over the prox sensor.
Click to expand...
Click to collapse
Tested that with some objects and with my hand. Same results. Even with the phone being held vertically like I'm talking with it, the screen won't turn off if it was covered before the call. When removing the hand/object from the proximity sensor and covering it again - the screen turns off immediately.
Maybe this is not a limitation of the sensor but a simple programmed behavior. If so, perhaps it can be patched... <evil grin>
Update. Under HKEY_LOCAL_MACHINE\Software\HTC\Proximity there are 3 keys: ProximityDetectStatus, ProximitySensorOn, UnexpectedWakeup.
The first key is updated live by whatever the sensor detects. I now know for sure that the sensor continously knows if there's something on top - the dialer behavior is programmed.
I'm not sure what the other keys do. ProximitySensorOn was set to 0 on my registry and now when it's 1 I see no difference. Gotta go, will continue with that later.
Switching the Proximity Sensor off...?!
erezshermer said:
Update. Under HKEY_LOCAL_MACHINE\Software\HTC\Proximity there are 3 keys: ProximityDetectStatus, ProximitySensorOn, UnexpectedWakeup.
The first key is updated live by whatever the sensor detects.... I'm not sure what the other keys do. ProximitySensorOn was set to 0 on my registry and now when it's 1 I see no difference.
Click to expand...
Click to collapse
Although I was looking for other reasons -- see below -- I get the same result; & even when you do change ProximitySensorOn to 1, it doesn't survive a soft reset: simply reverting to 0....
What I was looking for was some way of disabling the Proximity Sensor (PS) altogether: because (i) I'm deaf, & I therefore Bluetooth all calls directly to my 'hearing instruments'; & (ii) I've just bought a case which covers the darned thing (meaning the PS) up, permanently locking the touch-screen when it's on! (Aargh.)
Having spent the last couple of hours (plus) searching the TP2 forums on here (& a related one on PPC Geeks...), I've discovered that: (i) lots of people are having PS-related problems; (ii) some of these problems are to do with TouchFLO 3D; (iii) some may be related to various forms of screen-locking; (iv) some may even be caused by other tweaks or hacks we've carried out; & -- last, but not least, as lots of other proud TP2 owners have bought similar cases -- (v) I appear to be the only one having this particular problem (...probably caused by (iv)?)!
It's as if my particular sensor thinks my ear is permanently glued to the screen... -- I can operate all the buttons & the keyboard; but the screen (even though I can turn it on with the power switch) just will not respond while the case is attached (& therefore covering the sensor...).
If anyone has any ideas -- apart from drilling a hole in the case, somewhere (randomly) to the left of the HTC logo... -- please let me know!
Thank you for reading...
- $.
PS: I have a UK-spec., unbranded, GSM Touch Pro2 (...not that this seems to make any difference); & I've already tried turning off any locks & PINs (& changing their duration), as well as the owner information screen....
Forget the Curtain.
This enables your proximity sensor even when you are using your BT
leepriestenator said:
Forget the Curtain.
This enables your proximity sensor even when you are using your BT
Click to expand...
Click to collapse
What is this CAB doing? Because I am also interested in adding support by the Proximity Sensor in TouchLockPro. So how can I start programmatically the proximity sensor? Just changing a registry key
leepriestenator said:
Forget the Curtain.
This enables your proximity sensor even when you are using your BT
Click to expand...
Click to collapse
It works 。Thanks
Has anyone else noticed that when in a dark area, pressing the main button will turn on the screen but it will then automatically and immidiately turn off?
Several times I've gotten into a battle with the phone only to lose, turning it on and it turns off, then turning it on again and so on...
To compound the issue, in these situations it seems that double tap is signifigantly less responsive to activate the screen as well.
I'm pretty sure this phone is using some sort of facial recognition, it has smart stay doesnt it? I think it has gravity/accelerometer to turn on the screen when you pull it out of your pocket. In the back of my mind I'm thinking that since it cant see me it is shutting off but this doesnt seem consistent...
I'm running stock rom, rooted with twrp. Any ideas?
I have not experienced that. Did your G3 do that out of the box?
Sent from my LG-D851 using Tapatalk
Never heard of it. Screen is set to auto off in 30 seconds. Change it to 2 min and you should be good. If u running without a case then maybe the hand is touching the edges of screen this will also shut screen off in double tap.
BAD ASS G3
sublimaze said:
I have not experienced that. Did your G3 do that out of the box?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
I didn't notice it until the last week or so. but I kind of feel like that was because I hadn't used the phone that much up until then. I didn't make any major changes to the phone immediately before I started noticing it either, I had already had it rooted for about a week. I feel like the stock rom does have some glitches to it.
The G3 does have a "smart screen" feature that detects your face (Settings > Display). Disable that and see if it helps.
I've not run into this in the dark but have when I try and use my arm band holder when running. The holder covers the ambient light sensor so the phone thinks it was accidentally turned on like in a pocket and shuts right off. Super annoying.
Noticed similar behavior when the phone is in my bike mount at night. Basically it's acting like the proximity sensor is covered. In my bike mount's case, it is covered by a clear screen cover, but normally that doesn't trigger the proximity sensor. But when it's very dark out (not under a street light etc.), it seems to think it's blocked and turns itself off. Annoying.
randyspants said:
I've not run into this in the dark but have when I try and use my arm band holder when running. The holder covers the ambient light sensor so the phone thinks it was accidentally turned on like in a pocket and shuts right off. Super annoying.
Click to expand...
Click to collapse
speedrabbit said:
Noticed similar behavior when the phone is in my bike mount at night. Basically it's acting like the proximity sensor is covered. In my bike mount's case, it is covered by a clear screen cover, but normally that doesn't trigger the proximity sensor. But when it's very dark out (not under a street light etc.), it seems to think it's blocked and turns itself off. Annoying.
Click to expand...
Click to collapse
Have you tried disabling smart stay as sublimaze recommended?
Apache0c said:
Have you tried disabling smart stay as sublimaze recommended?
Click to expand...
Click to collapse
Tried but remains the same... This was the only thread I found concerning this.
Ive had this issue too investigating now
Had that issue when I was using the lock screen face unlock. In the dark it didn't see my face and then it shut off. Setting is in lock screen section
Sent from my G3
gabrielshaste said:
Had that issue when I was using the lock screen face unlock. In the dark it didn't see my face and then it shut off. Setting is in lock screen section
Sent from my G3
Click to expand...
Click to collapse
Lol.
I have the same issue EVERY night. Why is that? It's very annoying
Same issue here
it seemed to resolve itself when I factory reset my phone
but after I got my apps reinstalled from my google backup it started again
so it seems like it's a software issue - not sure to which app it is related to
let me know if you find a fix - this is quite annoying
Me too. I've been facing this issue at night, when it's very dark.
Me and my buddy were in the car during a roadtrip and it was very dark, I mean like: No lights outside, no lights inside the car, the double tap feature didn't even work to begin with and whenever I tried to use the "Power Button" It would come on and then suddenly 'boom' Turn off, now this would happen a few times until it stays on. Weird...
I just experienced this myself, first time I've seen it happen in the 30 + G5's that I've sold. If it's in the dark it just doesn't turn on at all. I hope LG is fixing this. I'm about to Factory Reset it right now and hope for the best! Someone else mentioned that this is the only forum that is disccusing this issue. It must be a very few that are effected. I'm testing another one as we speak.
Has this issue been resolved? My friend's G3 also has this issue. Day time no problem. When it is dark the screen wont' stay on.
Same problem, no fix yet
Same problem here - Pointing it at any light and pressing the power button will turn it on. (As will plugging it into power). Tried tinkering with all sorts of settings (face recognition/auto dimming feature/etc) nothing worked. Tried factory reset, that didn't work either.
My issue started after i had my screen replaced (by a shady shop) who probably didn't do a good job of packing it back together....I'm going to see if I can have someone open it up and clean it out a bit..
I have the same issue on my G3. Even if you're under the covers in bed, the thing doesn't turn on until it gets light. It basically doesn't turn on in the dark through double tap and actually not even with the power button. It could become a safety hazard for someone in an emergency situation.
Nahdont said:
I have the same issue on my G3. Even if you're under the covers in bed, the thing doesn't turn on until it gets light. It basically doesn't turn on in the dark through double tap and actually not even with the power button. It could become a safety hazard for someone in an emergency situation.
Click to expand...
Click to collapse
I have also same problem. No solution yet.
After a few days of using this device i noticed that my screen turns on during phone calls. After doing some research it came out that the proximity sensor is not working properly when phone is being tilted to horizontal position with screen upwards. It just immediately shows that it is far away from any object even that it isn't. The fun fact is that when covering the sensor with my hand while phone is laying on his back doesnt switch it and rotating the phone to vertical position also does not make any effect like the sensor would be locked. Covering it again in that position makes it work.
Can anybody help me with this issue? It's very annoying for me and makes my phone unusable for making calls.
Edit: similar problem here https://forum.xda-developers.com/android/help/huawei-nova-5t-proximity-sensor-problem-t4136595
Same problem here...
here also
I am so lost. What do I do with the phone? What? When does it happen? (Also subscribing.)
Same here, and i notice i have also problems with whastapp and telegram audio notes.
Sometimes screen goes blank randomly and with no reason when i'm listening a audio note.
Hi. Its a well known problem. Its becouse the device has a ultrasonic sensor not like any other. Sensor like you already find out works only in vertical position of the phone. Its well described in the net how it works. Just search. In 4PDA in the section for our phone. But you need to know russian.
I found that thread and it seems that not everyone notices that... Not spending more time on reading this I found a workaround on my own: an app that keeps the screen disabled after first switching proximity sensor. Then you just need to use the power button if you want to use the phone.
Same problem here, it's very frustrating. I can turn the screen back off during a call once I see it's turned on by itself, but it keeps turning back on. I'm sick of muting calls and hanging up on people by pressing buttons when I'm on the phone.
What is the app that you are using @Spectre45?
Spectre45 said:
I found a workaround on my own: an app that keeps the screen disabled after first switching proximity sensor. Then you just need to use the power button if you want to use the phone.
Click to expand...
Click to collapse
Can you please tell us what app you are using?
kage00 said:
Can you please tell us what app you are using?
Click to expand...
Click to collapse
try proximity screen off or call proximity screen fix
LightSmok said:
try proximity screen off or call proximity screen fix
Click to expand...
Click to collapse
Thanks
Listen. There is no proximity sensor at all. The upper mic, speaker and the sensor for orientation are doing the job. When you pick a call the speaker is sending ultrasonic signal and if it locate your ear it dims the screen. Once it works it is working in all positions. But if you move your phone away only in horisontal position it will nit work untill you mive it in vertical again.
Edit: Experienced this issue too. Annoying.
Does using Xiaomi.EU fix this problem? This issue really gets on my nerves. I started daily driving this device (finally I was able to unlock) and I just cannot use it for calls, which is kinda ridiculous from a phone.
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
I was using the phone with cover provided by MI, upon removing that back cover I encounter no such issues.
h8Aramex said:
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
Click to expand...
Click to collapse
I didn't have any proximity issues on stock with google dialer. It's not google dialer, it's how you position your head against the earpiece. Sensor is ultrasonic, so it probably doesn't detect properly depending on the position people hold their phones in...
I have the same problem with my work phone - redmi note 9. Tried the app "proximity screen off" but MIUI keeps killing it no matter what i do to keep it alive. It seems that sensor is located on front top right side of the phone so sometimes it gets behind your ear if you are right handed (mine are pretty small) and then the muting starts. When using the phone with left hand - no problems at all.
I would love to have a working app to keep screen off during call.
h8Aramex said:
Flashing Xiaomi.EU fixed the issue and calls now work totally fine.
I believe it's Google Dialer making all the trouble, so basically EEA default rom will always be troublesome until Xiaomi decides to fix it. This is only a theory however. All I know is that the Xiaomi.EU rom saved my phone.
Click to expand...
Click to collapse
I also flashed EU rom and the problem persistes.
Just wanted to know if other users have this issue.
I do a lot of phone calls for my work and since I switched to this phone I can not make a decent phone call at all... lol
Every couple of minutes or less the call breaks off. That is either because the other side can't hear me anymore, either the connection breaks off.
Also noticed that when receiving notifications during calls, the screen lightens up so I do get false touches which results in a total chaos on my screen...
I already placed sim to other slot, tried all different preferred network type, rebooted...nothing helps.
This is really annoying as on my other phones like F2 Pro and MI9 all ok.
Anyone having the same issue?
EDIT : 16.04.2021 I noticed now that due to the bad ultrasone proximity sensor the screen lightens up and makes a lot of false touches resulting sometimes in a mute of the mic on dialer or even shutting down the phonecall itself
Yes, it has also happened to me that the screen does not go out when I am on the phone. If you take the phone away from your ear for a moment and then go back to it, the display goes off.
CHGICEMAN said:
Yes, it has also happened to me that the screen does not go out when I am on the phone. If you take the phone away from your ear for a moment and then go back to it, the display goes off.
Click to expand...
Click to collapse
Yea already am doing that often because of the screen lightens up.
But did you also encounter a lot of false touches and even the call shutting off?
Check you up * # * # 6484 # * # * Light Sensor or calibrate.
CHGICEMAN said:
Check you up * # * # 6484 # * # * Light Sensor or calibrate.
Click to expand...
Click to collapse
This is related to proximity sensor
Value is 5.0 when no covered and 0 when covered.
Test is ok but in call screen didn't turn off.....so should be a softaware bug I think.
CHGICEMAN said:
Check you up * # * # 6484 # * # * Light Sensor or calibrate.
Click to expand...
Click to collapse
nicnic94 said:
This is related to proximity sensor
Value is 5.0 when no covered and 0 when covered.
Test is ok but in call screen didn't turn off.....so should be a softaware bug I think.
Click to expand...
Click to collapse
Yea I already tested that before this post. It's working fine. No problem with that.
Problem is that when receiving a notification the screen lights up and it shouldnt. I cannot find the issue for now.
Also and this is more important : when making a call, the line gets cutoff (people cant hear me but I can).
This happens so often and never had this with my other phones running.
Already unchecked 5G, even 4G and now on 3G. Same issue.
Will look further into it...
Do you use always on display ? Maybe that's the cause? Maybe Miui optimization?
I didn't put sim card from my f1 to f3 yet, but you are making me check this out. Ill put the sim card as soon as I get case and glass. On telegram I have not seen anyone to mention this issue.
osemoka said:
Do you use always on display ? Maybe that's the cause? Maybe Miui optimization?
I didn't put sim card from my f1 to f3 yet, but you are making me check this out. Ill put the sim card as soon as I get case and glass. On telegram I have not seen anyone to mention this issue.
Click to expand...
Click to collapse
Nope not using AOD. Things are set to basic as to rule out issues.
Saturday I'll be unlocked though and going to check the fastboot xiaomi.eu rom
If you can make a test later on, do make a longer phone call. Also send a message to your phone when you're making a call and see what happens.
Had the same issue with my poco x3 nfc - same issue with the f3. I think either I got used to it with the X3 or it got fixed....
umairmalik2410 said:
Had the same issue with my poco x3 nfc - same issue with the f3. I think either I got used to it with the X3 or it got fixed....
Click to expand...
Click to collapse
Yea I read.
Anyway, the phonecall shutting off (other cant hear me) was all due to the fact that I accidentally muted the mic (or even false touched the red button or whatever) on the screen because of the false touches when screen suddenly lightened up.
The ultrasone proximity sensor is not the best solution to dim the screen when calling.
You can even test that in kernel settings. The value 5 goes to 0 even from behind or from the top. So in some cases the screen will light up suddenly.
On tweakers forum there are a lot of people who have the same issue with the proximity sensor too.
An infrared sensor would have been much better....
raystef66 said:
Yea I read.
Anyway, the phonecall shutting off (other cant hear me) was all due to the fact that I accidentally muted the mic (or even false touched the red button or whatever) on the screen because of the false touches when screen suddenly lightened up.
The ultrasone proximity sensor is not the best solution to dim the screen when calling.
You can even test that in kernel settings. The value 5 goes to 0 even from behind or from the top. So in some cases the screen will light up suddenly.
On tweakers forum there are a lot of people who have the same issue with the proximity sensor too.
An infrared sensor would have been much better....
Click to expand...
Click to collapse
I have a similar issue. I use a pretty thick case and it breaks the proximity sensor such that during a call the screen turns off but after the call when i move the phone away from my head, it remains permanently off, like it still thinks the phone is near my head.
Which tweakers forum are you referring to?
lukesky said:
I have a similar issue. I use a pretty thick case and it breaks the proximity sensor such that during a call the screen turns off but after the call when i move the phone away from my head, it remains permanently off, like it still thinks the phone is near my head.
Which tweakers forum are you referring to?
Click to expand...
Click to collapse
That's indeed true. It happens that the screen remains black after moving the head from the screen during call. You can even trigger that when opening the sensor part in the kernel (tap on it for a few times and test the proximity sensor - you'll notice that you even can let it stay on 0 by slowly removing your hand...)
But for me these false touches due to the screen lights up during a call makes it even worse.
tweakers translate if needed - starts from end of page 6.
Btw, I'm just using the case that came with the package.
Anyway, since they fixed the haptic crackling sound issue on v1204 eu and having already no issues on battery drain (9%/h SOT and 0.4%/h idle) , the only issue for me remains the proximity sensor.
If you pick up the call and wait 1sg or so to raise it to the ear, the screen turns off well, but if you pick up the call quickly it does not turn off, it may be a google dialer failure
Perhaps you can bring this issue to Poco's attention directly via: https://c.po.co/global/
I would also like to know if it's a hardware or software related issue.
Nemix77 said:
Perhaps you can bring this issue to Poco's attention directly via: https://c.po.co/global/
I would also like to know if it's a hardware or software related issue.
Click to expand...
Click to collapse
I already did as for the haptic motor sound issue (which is fixed now).
So lets wait for a response...
raystef66 said:
That's indeed true. It happens that the screen remains black after moving the head from the screen during call. You can even trigger that when opening the sensor part in the kernel (tap on it for a few times and test the proximity sensor - you'll notice that you even can let it stay on 0 by slowly removing your hand...)
But for me these false touches due to the screen lights up during a call makes it even worse.
tweakers translate if needed - starts from end of page 6.
Btw, I'm just using the case that came with the package.
Anyway, since they fixed the haptic crackling sound issue on v1204 eu and having already no issues on battery drain (9%/h SOT and 0.4%/h idle) , the only issue for me remains the proximity sensor.
Click to expand...
Click to collapse
For me if I use the case that came with the package, proximity sensor works fine , it also works fine if the phone is naked. but with a thick case, then it becomes a bit crazy such that i have to map the power button to end the call, else I wont be able to access the phone after or during a call unless i shake it hard
Reboot and shutdown issues have been acknowledge by Poco, will addresses in the upcoming updates:
Poco F3 battery drain & random reboot issues to be fixed with next update
A community mod has informed that the battery drain and random reboot issues on the Poco F3 are to be fixed with the next update.
piunikaweb.com
I really hope it's a software issue because I plan on placing my order for phone this weekend.
I wonder where's the proximity and ultrasonic sensor. *#*#miui#*#* can't test it. Using nillkin's case, one works perfectly, while the one with the thicker camera protector blocks the sensor and calling won't dim the screen.....
experienced this with the global rom but now flashed EU rom so far everything is ok.
choobs95 said:
experienced this with the global rom but now flashed EU rom so far everything is ok.
Click to expand...
Click to collapse
I see. So it's a software issue huh? Then I'm gonna flash into eh and see how this weekend.
Hi,
I have a problem with my OP 9Pro.
After a phone call, the display sometimes stays black and it takes a while before you can use the device again.
Does anyone else have that and, above all, how can I solve the problem?
Many greetings and thanks
Mars
Are you on OOS12? I only experienced that bug in the short time I ran OOS12. One of the main reasons I reverted to OOS11 actually.
Yeah I get this too. From what I can tell, it seems to have something to do with the proximity sensor killing the screen when you put it up to your ear, then hanging when the call ends.
OOS11
Me too. On 11. Thinking it may be from Nova or Adguard. Until I figured out that I could hit the "screen on" button to regain control I would wait till the other person hung up. So, as a workaround that's what I do, hit the button.
That happens when the proximity sensor it's being blocked. If you have any screen protector over the camera notch (where the proximity sensor is) then that's why it's turning the screen off.
If you don't have anything covering the sensor then try making a call on another app (like WhatsApp) to see if the issue persists there too. If not then it might be the dial app, try restarting your phone.
If it happens on many messaging apps, and there's nothing covering the sensor, try downloading a sensor tester app to see if the proximity sensor is being triggered all the time. If it is then it's a hardware issue and you'll have to return your phone a get a new one.
chetqwerty said:
Me too. On 11. Thinking it may be from Nova or Adguard. Until I figured out that I could hit the "screen on" button to regain control I would wait till the other person hung up. So, as a workaround that's what I do, hit the button.
Click to expand...
Click to collapse
Power button is unresponsive when the phone goes pitch black. Even switching the alert slider to something different doesn't trigger the fingerprint sensor on.
I'll try disabling pocket mode. I also found positive feedback about this when you enable the "Override force-dark" setting in Developer Options. See if that helps.
Has been happening to me from time to time since A12. I just hold volume up, volume down and power button at same time and reboot to recovery and restart from there. That fixes it really quick for me.
Yes, I'm on A12 because I thought it would get better here. But I had the same problem with the A11.
I haven't managed to solve the problem yet.
It also happens on Android 11 but it's not quite as bad here. The display turns on after a little while.
Where is the sensor actually? It's not the camera. It's to the right of the speaker. or?
Hi, Guess!
I got a solution from the Oneplus team. (1800 202 8888) / general phone tech support team helped me with these steps:
1- under setting search reset
2- click on Reset all settings
3- Reset all settings. click it.
As this is a normal reset will not lose your data.
The last option is if this doesn't work then we have to backup all data from the phone and do a factory reset.
or it's a hardware issue.
e-regards!
Piyush Sahni