So I've noticed my AOD isn't turning off at all. While I do have it set to "Show Always", it should still turn off after a short time if the proximity sensor is covered., as was the case with the S7, S8 and S9.
Could you guys please confirm if this is the case for your AOD too? Turning the phone face down or put it in your pocket (or just cover the top half of the display) for a few minutes, see if the AOD turns off. Let me know if anyone sees it turn itself off.
You have to have AOD set to "Show Always" for this test to be valid.
I suspect this could be a bug which Samsung might need to be made aware of, hence my request for others to test. Unless I'm missing something VERY obvious. Or Maybe this is by design?
Thanks :good:
EDIT: thinking about this further, I reckon the proximity sensor is only active while it's flashing, such as when a call is being made. Because it's a "behind the display" type sensor. So maybe they made a trade off with AOD?
It's a sad news for you. S10+ doesn't have a proximity sensor as a trade-off for the screen (sounds ridiculous?). And some features are like sh*t due to the lack of proximity sensor. I don't know if I can go through with this so-called flagship
GialanG said:
It's a sad news for you. S10+ doesn't have a proximity sensor as a trade-off for the screen (sounds ridiculous?). And some features are like sh*t due to the lack of proximity sensor. I don't know if I can go through with this so-called flagship
Click to expand...
Click to collapse
Ummm, of course it has a proximity sensor.....
Try making a call to someone (use voicemail if you want). You'll see a little white flashing dot to the left of the cameras, near the battery icon. This is the proximity sensor: https://hothardware.com/news/blinking-white-pixel-samsung-galaxy-s10-feature-not-bug
Try covering it up while in a call. The display will go off. Because you just covered up the proximity sensor. Because they do have one.
the_scotsman said:
Ummm, of course it has a proximity sensor.....
Try making a call to someone (use voicemail if you want). You'll see a little white flashing dot to the left of the cameras, near the battery icon. This is the proximity sensor: https://hothardware.com/news/blinking-white-pixel-samsung-galaxy-s10-feature-not-bug
Try covering it up while in a call. The display will go off. Because you just covered up the proximity sensor. Because they do have one.
Click to expand...
Click to collapse
No it's not. Can you check it on your phone with *#0*# in the dialer or any proximity checking app? The result is always 0.
I had troubles with the double tap to wake and the show fingerprint features, and sometimes with calls when my phone behaves abnormally. Then I checked and it turns out that S10 doesn't have a proximity sensor. Samsung did other things to replace the proximity sensor's function, but it has been much worse than before
the_scotsman said:
So I've noticed my AOD isn't turning off at all. While I do have it set to "Show Always", it should still turn off after a short time if the proximity sensor is covered., as was the case with the S7, S8 and S9.
Could you guys please confirm if this is the case for your AOD too? Turning the phone face down or put it in your pocket (or just cover the top half of the display) for a few minutes, see if the AOD turns off. Let me know if anyone sees it turn itself off.
You have to have AOD set to "Show Always" for this test to be valid.
I suspect this could be a bug which Samsung might need to be made aware of, hence my request for others to test. Unless I'm missing something VERY obvious. Or Maybe this is by design?
Thanks :good:
EDIT: thinking about this further, I reckon the proximity sensor is only active while it's flashing, such as when a call is being made. Because it's a "behind the display" type sensor. So maybe they made a trade off with AOD?
Click to expand...
Click to collapse
tried it on a S10E, the AOD always stay on even when in pocket.
Can confirm on my s10+. AOD does not turn off in my pocket or laying face down.
did anyone notice the werid little flashing spot above the the signal bars? that`s the only place where when I put my finger over it the screen goes off during call
GialanG said:
No it's not. Can you check it on your phone with *#0*# in the dialer or any proximity checking app? The result is always 0.
I had troubles with the double tap to wake and the show fingerprint features, and sometimes with calls when my phone behaves abnormally. Then I checked and it turns out that S10 doesn't have a proximity sensor. Samsung did other things to replace the proximity sensor's function, but it has been much worse than before
Click to expand...
Click to collapse
Seriously, it has both a proximity sensor and light sensor as per normal. They may work slightly different, hence why crappy test apps from the Play store don't work. And why AOD is no longer turning off in pockets.
Watch JerryRigEverything's teardown, specifically here, where he physically points them out: https://youtu.be/kHzmFPoZbCA?t=427
2003vstrom said:
did anyone notice the werid little flashing spot above the the signal bars? that`s the only place where when I put my finger over it the screen goes off during call
Click to expand...
Click to collapse
Read the link I posted in my earlier post. That's the proximity sensor.
the_scotsman said:
Seriously, it has both a proximity sensor and light sensor as per normal. They may work slightly different, hence why crappy test apps from the Play store don't work. And why AOD is no longer turning off in pockets.
Watch JerryRigEverything's teardown, specifically here, where he physically points them out: https://youtu.be/kHzmFPoZbCA?t=427
Read the link I posted in my earlier post. That's the proximity sensor.
Click to expand...
Click to collapse
Not only apps in Store, but the SS diagnostic mode doesn't show either. Check the attached pics of S10+ and Note 5 in SS stock diagnostic mode
the_scotsman said:
Try covering it up while in a call. The display will go off. Because you just covered up the proximity sensor. Because they do have one.
Click to expand...
Click to collapse
Same here.
Tbh it's not really a trade off I'm happy with because it makes AOD a source of battery drain at this point. I want to be able to put my phone face down to save battery. Do you think this might actually be a bug?
Started a thread in the Samsung community forum. Maybe some of you guys can top up with your own findings.
https://us.community.samsung.com/t5/Galaxy-S10/Always-on-display-not-turning-off/m-p/473981#M2111
Sent from my SM-G975W using XDA Labs
GialanG said:
No it's not. Can you check it on your phone with *#0*# in the dialer or any proximity checking app? The result is always 0.
I had troubles with the double tap to wake and the show fingerprint features, and sometimes with calls when my phone behaves abnormally. Then I checked and it turns out that S10 doesn't have a proximity sensor. Samsung did other things to replace the proximity sensor's function, but it has been much worse than before
Click to expand...
Click to collapse
Found this article which confirms the existence of a proximity sensor.
https://hothardware.com/news/blinking-white-pixel-samsung-galaxy-s10-feature-not-bug
The trade-off might be due to the fact that's the sensor is tied to that blinking pixel and is only active while making phone calls.
Sent from my SM-G975W using XDA Labs
Same here, AOD doesn't turn off when flipping it over or covering top portion of the screen.
I'm starting to think this is why they added the feature of AOD only turning on when you tap the screen once as a trade off for it not automatically turning off
mrnovanova said:
Found this article which confirms the existence of a proximity sensor.
https://hothardware.com/news/blinking-white-pixel-samsung-galaxy-s10-feature-not-bug
The trade-off might be due to the fact that's the sensor is tied to that blinking pixel and is only active while making phone calls.
Sent from my SM-G975W using XDA Labs
Click to expand...
Click to collapse
I tend to agree. I carry my S10+ in my shirt pocket and have noticed that AOD remains on.
Additionally, if double tap to wake the screen is on, the screen will wake on in your pocket without double-tapping it. I have disabled this feature as its annoying that this is also buggy!
pickwit said:
I tend to agree. I carry my S10+ in my shirt pocket and have noticed that AOD remains on.
Additionally, if double tap to wake the screen is on, the screen will wake on in your pocket without double-tapping it. I have disabled this feature as its annoying that this is also buggy!
Click to expand...
Click to collapse
This combined with the lift to wake option interpreting placing in pocket as lifting and the ultrasonic fingerprint reader activating in pockets is giving us of a real annoyance.
I hope Samsung are aware of this and do something about it.. .. ..
---------- Post added at 06:48 PM ---------- Previous post was at 06:23 PM ----------
Very strange... just tried disabling double tap to wake the screen and it didn't stop it happening... Doh
It's a bug, they forgot to link the older aod behaviour with the new implementation of this sensor, I expect it to be fixed in the next update, along with everything else.
I'm constantly getting this too. Even with AOD off and the option to not turn screen on when in pocket(can't remember exactly name) I'm still constantly having my phone turn on in my pocket. At work I get a break every 2.5 hours and sometimes 45 minutes or more of that it'll be on in my pocket. I've pulled it out several times and the emergency call screen be on with a lot of numbers pressed. It's definitely a huge annoyance. My battery almost died during a 10 hour shift because of this.
Sent from my SM-G975U using Tapatalk
Hi everyone. Any thoughts on this issue? This still persists for me even though my phone is up to date and it's may already.
I too think that there's a trade off with the in-screen proximity sensor and the fact that the phone doesn't recognise that's in a pocket. Mine keeps going on while in it.
There must be a way to get around this issue but I'm suspecting we'll never see an optimal fix since the proximity sensor uses that lit pixel to work and nobody would like to see it blinking every second.
I blame bad engineering here. Thumbs down for Samsung mobile.
I blame the new in screen proximity sensor. I doubt they will ever get a fix for their first gen type used on our devices. It'll probably be fixed on the note 11 or S11. I hope not though.
Sent from my SM-G975U using Tapatalk
folks, its a bug in Oneui which existed in all S10 and s10+... its had been reported since day one and still Samsung still unable to solve this issues till date. And they published an notice in Samsung member app, next update will be addressing this issues finally. so lets wait for May updates and see they really solve it.
https://www.sammobile.com/2019/05/13/samsung-galaxy-s10-future-updates-improvements
ramnkc said:
folks, its a bug in Oneui which existed in all S10 and s10+... its had been reported since day one and still Samsung still unable to solve this issues till date. And they published an notice in Samsung member app, next update will be addressing this issues finally. so lets wait for May updates and see they really solve it.
https://www.sammobile.com/2019/05/13/samsung-galaxy-s10-future-updates-improvements
Click to expand...
Click to collapse
Oops accidentally thanked you.
Samsung will never resolve it on the s10, you heard it from here first.
Sent from my SM-G975U using Tapatalk
Related
Hi as the question says
Did anybody notice a small blinking circle (will be around 1mm size), around 1 cm to the right of the camera when you place a call on the note 10 +
or is it only me?
During calls I noticed it.
Sent from my SM-N975U1 using Tapatalk
It appears to be the prox sensor (for turning the phone screen off when its up to your ear). That's what I've been seeing in comments of other people seeing the flashing during calls.
I believe it is the proximity sensor
charlieb620 said:
During calls I noticed it.
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Fullmetal691 said:
It appears to be the prox sensor (for turning the phone screen off when its up to your ear). That's what I've been seeing in comments of other people seeing the flashing during calls.
Click to expand...
Click to collapse
dchurch85 said:
I believe it is the proximity sensor
Click to expand...
Click to collapse
okay thanks... was worried it might be dead pixels
Hopefully a sensor and not a pixel issue. Happening to me
Yes, proximity sensor. S10+ 5G has it also.
Sent from my SM-N975U1 using Tapatalk
That would be the proximity sensor
It is the proximity sensor.
And by the way it doesn't work well at all on my S10 plus. When I am on the phone the screen would turn on and then my ear would start tapping on the screen turning things on and off.
Pretty annoying, so I had to learn to manually turn the screen off with the power button every time before I answer or make a call...
I sincerely hope they have somehow found a way to improve it with the Note
just now saw it whilst playing a whatsapp voice message. when i put my finger over it, the phones speaker will shut off which seems to confirms its proximity sensors.
i did notice after some seconds, maybe a minute, the blinking light stops on whatsapp if you are listening to a speaker call on whatsapp... i have the whatsapp on full screen mode so the green part of the phones GUI is up there...
I noticed this today also when I placed a call. I dont make calls much so I just noticed it after 2 days. Just had some free time now and quickly rushed to locate this thread I had seen yesterday I believe.
What a relief it's the proxi sensor.
tiho5 said:
It is the proximity sensor.
And by the way it doesn't work well at all on my S10 plus. When I am on the phone the screen would turn on and then my ear would start tapping on the screen turning things on and off.
Pretty annoying, so I had to learn to manually turn the screen off with the power button every time before I answer or make a call...
I sincerely hope they have somehow found a way to improve it with the Note
Click to expand...
Click to collapse
Working quite well for me so far.
It shows that Samsung has the ability to create camera under screen, but they didn't most likely due to photo quality
Good to know it's the proximity sensor.
Mine appears to flash rapidly more than blink though lol.
I thought I had a defective note. Thanks for the info.
Sent from my [device_name] using XDA-Developers Legacy app
It's the same thing just like S 10
those of us coming from the Note 9 that didn't have this, it's a new thing to discover...
When I first noticed it I thought dead pixel lol but it only visible during calls iv noticed
Yes, it is the proximity sensor, it is sad that this sensor implementation does not allow third party apps to use it, I used gravity screen in my past devices to turn screen off when in pocket or turn it on waving over the sensor, but now the app became useless, I use macrodroid, but it is not as good as gravity screen
does anyone else have a problem with the proximity sensor not turning the screen off during the call over telegram, threema etc.?
iopah said:
does anyone else have a problem with the proximity sensor not turning the screen off during the call over telegram, threema etc.?
Click to expand...
Click to collapse
Literally read the post before yours.
I've been using Tasker to keep my phone off in my pocket with a combination of 'orientation on right side' and 'proximity sensor' active. Googling a bit, I see some mention about a software upgrade breaking the proximity sensor not long ago.
Anyone know more about it? Sensor seems to work ok when phone is on - maybe it got broken for non-phone things?
(note - turned off double-tap to wake & lift to wake to try to keep phone off when in my pocket)
since s10, proximity sensor is internally controlled only on certain activities. example: phone calls
Sent from my SM-N975F using Tapatalk
jemfalor said:
since s10, proximity sensor is internally controlled only on certain activities. example: phone calls
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I was just researching this again & found this, which matches what you say:
The proximity sensor is indeed under the screen and a pixel has to be turned off for it to work properly. This means proximity apps will not work properly any more unless Samsung writes them.
So Samsung turns off a pixel so that the Proximity Sensor can see/work (like during a call) - and that means my Tasker screen off will not work. Wonder if there is a Tasker "if front camera covered".. gonna go look that up now - actually that won't work, would require the camera to always be on.
Hmm.
polstein said:
I was just researching this again & found this, which matches what you say:
The proximity sensor is indeed under the screen and a pixel has to be turned off for it to work properly. This means proximity apps will not work properly any more unless Samsung writes them.
So Samsung turns off a pixel so that the Proximity Sensor can see/work (like during a call) - and that means my Tasker screen off will not work. Wonder if there is a Tasker "if front camera covered".. gonna go look that up now.
Click to expand...
Click to collapse
tried. had tasker as well and was relying on proximity sensor. gave up
jemfalor said:
tried. had tasker as well and was relying on proximity sensor. gave up
Click to expand...
Click to collapse
I was trying to play with the light sensor with no luck - so I stripped my profile down to just Orientation Right Side = off...and it failed. The screen off works when i manually test it in Tasker, not sure why orientation fails too.
Maybe this is for another thread - what the heck are people that keep the phone in their pockets doing? I've read keep screen away from leg which is a pain for me and the flygrip I use on my phone. Must be a better way!
Is there a way for aod to stay off in confined environments but immediately turn on when taken out off them?
asbogdan said:
Is there a way for aod to stay off in confined environments but immediately turn on when taken out off them?
Click to expand...
Click to collapse
It should automatically turn of if proximity sensor detects something.
You can test it by simply turning phone upside down on the table, after a couple of seconds, AOD will be turned off.
Same goes with pocket or whatever.
I am actually not sure if proximity sensor is in charge for that or just multi touches on the screen, but it works anyway.
Well, Since I read your reply, I tried to replicate the AOD behaviour you describe, to no avail, is there a setting or something to achieve it?
winol said:
Well, Since I read your reply, I tried to replicate the AOD behaviour you describe, to no avail, is there a setting or something to achieve it?
Click to expand...
Click to collapse
There is never.a setting for this since AOD.is born. Always automatica turn off in pocket
winol said:
Well, Since I read your reply, I tried to replicate the AOD behaviour you describe, to no avail, is there a setting or something to achieve it?
Click to expand...
Click to collapse
Mine is also not turning off in pocket, etc.
My Note 8 always has.
it seems it does not work as intended. Should call customer support on Monday.
Might be due to the fact that the proximity sensor is in the screen now. The flickering point on the right of the camera when you initiate a call
Now that I check I don't think the proximity sensor is working at all when not on a call.
As reference, I have the T-Mobile Note 10+. Before the September update, the AOD on my phone used to turn off when my flip case is closed. Now that I updated to the September update, that function stopped working, the AOD is still on when my case is closed. The update fixed the flashing camera hole issue (now works great on apps like aodNotify) but now problem with the AOD. I hope they fix this issue asap with an AOD update or something.
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
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.