Received my Navy blue FE yesterday, and its all working pretty well. I noticed that the Blue Light filter works just fine while the phone is unlocked and is use but the Lock Screen maintains the bright blueish tint which means the filter is not working on the lock screen. My S10, which I will be mailing in sometime next week, keeps the filter on all the time including on the lock screen. Anyone else having this issue? Also, anyone have a link to a good ultra thin TPU case for the FE? Most of the one's I have found on Amazon look hideous or will take a month to get here. Thanks.
I noticed the same with the blue light filter not being active in the lockscreen on my Snapdragon 5G EU Model.
So it may be a software bug?
Annoys the hell out of me, especially at night or when waking up. I submitted a bug report.
Its because of the optic fingerprint scanner. Oneplus phones are the same
This is a side effect of using the optical fingerprint scanner.
Does the S10 use the same sensor, cuz the Blue Light filter works fine on the lock screen on my S10 which I will have to send in this week as my trade-in device.
When I try to submit a bug report, I choose GMAIL and it just creates an email with the bug report attached but its addressed to myself. What is the email address to send it to Samsung? Thanks.
Nevermind, I figured it out. Thanks.
el6006 said:
Does the S10 use the same sensor, cuz the Blue Light filter works fine on the lock screen on my S10 which I will have to send in this week as my trade-in device.
Click to expand...
Click to collapse
No. S10 uses an ultrasonic sensor while the S20 FE uses an optical sensor.
I turned off my fingerprint unlock and lo and behold, the blue light filter works on the lock screen. That means that the filter is disabled in order for the fingerprint scanner to function. Bummer. Guess it's either use the fingerprints scanner and be blinded in the dark with a bright lock screen or use pattern unlock and have a lock screen blue light filter. Sigh......
Sent from my SM-G781U1 using Tapatalk
Received a response from Samsung today regarding this issue. View attachment 5121709
Sent from my SM-G781U1 using Tapatalk
Has anyone problem with AOD? Even that I have the finger print sensor disabled, the blue light filter seems to not work on AOD. On lockscreen, it works properly.
el6006 said:
Received a response from Samsung today regarding this issue. View attachment 5121709
Sent from my SM-G781U1 using Tapatalk
Click to expand...
Click to collapse
Hi, I could not view the attachment. Could you please tell me what response it is that you got from Samsung? Can the blue screen filter be activated somehow even if I use the fingerprint scanner?
Basically, if you enable Blue light filter, it changes the screen lighting too much to use the finger prints scanner. So that's why it's disabled. If you turn it off finger prints unlock, your lock screen will stay yellow instead of momentarily disabling your blue light filter. So, it's either one or the other. I reattached the response they sent me.
el6006 said:
Basically, if you enable Blue light filter, it changes the screen lighting too much to use the finger prints scanner. So that's why it's disabled. If you turn it off finger prints unlock, your lock screen will stay yellow instead of momentarily disabling your blue light filter. So, it's either one or the other. I reattached the response they sent me.
Click to expand...
Click to collapse
Just turn on AoD. You can unlock straight from it, and it can be really dim for nights, the only part that lights up is the finger part itself.
Related
I multitask all the time on my Note 9. However when I try to use the screen when I'm talking on the speakerphone (for example, look up a phone number or web browser) the screen turns black immediately when my hand covers the proximity sensor. This is especially an issue since I hold my phone in landscape almost all the time (my left hand covers the proximity sensor). I'm baffled why Samsung would want the proximity sensor to turn off the screen when talking on the speakerphone... with no intuitive way to disable this.
Seems kind of odd considering this phone is meant for busy people who multitask. I've already spent a lot of time looking for a solution for this... but, haven't found a solution yet. I've already tried "Kinscreen" and "Keep screen on" on Google play. However, it doesnt work on the Note 9.
So... what's the trick to disable the proximity sensor on the Note 9?
Saw the below article by searching on Google... However, it seems to be a bogus website with false information:
https://gettechmedia.com/how-to-turn-proximity-sensor-on-off-samsung-galaxy-note-9/
PS: I have a Verizon phone.. so I can't root it either.
Sounds like a screen protector or similar may be causing an issue with the proximity sensor
The screen isn't supposed to turn off when on speakerphone, mine doesn't
Sent from my SM-N960U using Tapatalk
Thanks for the reply. I probably should have mentioned that the proximity sensor works correctly. If I move my finger over the sensor, it blacks out the screen. If my don't cover the sensor, the screen turns on immediately.
I think that's how the proximity sensor is supposed to work by design. This functionality is in place so that when you move your ear to the phone, it turns the screen off.
The problem I have is this that the proximity sensor turns off the screen if I accidentally move my finger over the sensor; even when I'm talking on the speakerphone (when my phone is not near my head). On older versions of android, there's a simple setting to turn this functionality off under Phone/Call Settings.
Could you please check to see what happens if you move your finger over the actual proximity sensor when the speakerphone is on?
harlenm said:
The screen isn't supposed to turn off when on speakerphone, mine doesn't
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
mkanet said:
Could you please check to see what happens if you move your finger over the actual proximity sensor when the speakerphone is on?
Click to expand...
Click to collapse
I just did, nothing
Sent from my SM-N960U using Tapatalk
Thanks for confirming this! So... my next question is how do I fix this issue. I wonder if there was some setting that I changed that causes this behavior.
PS: If I enable "Smart Stay", the screen will stay on (even if my move my finger over it), as long as I'm staring right at the screen and hold it the phone vertically.
harlenm said:
The screen isn't supposed to turn off when on speakerphone, mine doesn't
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
I'm almost too embarranssed to say what the real problem was. I guess I'm more tired than I realized. I just noticed I didn't actually have speakerphone turned on. I guess the phone speaker is so loud that I thought the speakerphone was enabled! Thanks for trying to answer my question anyway.
Lol, glad you sobered up ??
I noticed back in oreo speakerphone screen would go blank after a few seconds.
Sent from my SM-N960U1 using Tapatalk
Verizon N9. Screen goes black when on speakerphone after 10 seconds.
No screen protector. No proximity sensor issues. This is after I hit the speakerphone button (unlike OP that didnt know speakerphone wasn't truly engaged)
How do you get the screen to stay on when using speakerphone?
Again - this is NOT a prox sensor issue. The prox sensor works great when I am using it against my ear/face and not using speakerphone.
Same issue with the s10+, screen goes off after some time on speakerphone same as note 9.
Sent from my SM-G975U using Tapatalk
Is it possible to remove fingerprint from aod on p30 pro without removing fingerprint sign in? I can't find settings for it...
I don't know about yours, but mine isn't there until I pick up the phone or touch the screen?
If you want to completely remove it then you can't - the way the finger print sensor works requires the screen to light up at max brightness under your finger so it can capture the fingerprint with the optical sensor.
Watch the 'JerryRigEverything' YouTube teardown to find out more info on how it works, but when scanning for a fingerprint it needs the illumination
milosmeda said:
Is it possible to remove fingerprint from aod on p30 pro without removing fingerprint sign in? I can't find settings for it...
Click to expand...
Click to collapse
I was wondering this too as I'm starting to get slight screen burn from a combination of that and the intense light required to unlock. My S10+ has an option to turn it off, and muscle memory dictates that it isn't really necessary after a few days of use.
leoni1980 said:
I was wondering this too as I'm starting to get slight screen burn from a combination of that and the intense light required to unlock. My S10+ has an option to turn it off, and muscle memory dictates that it isn't really necessary after a few days of use.
Click to expand...
Click to collapse
As I said above, the reason for the intense light is that it uses and optical sensor rather than an ultrasonic sensor (as used in the S10+). Without the light it simply will not be able to see fingerprints.
NJ72 said:
As I said above, the reason for the intense light is that it uses and optical sensor rather than an ultrasonic sensor (as used in the S10+). Without the light it simply will not be able to see fingerprints.
Click to expand...
Click to collapse
I understand that but I'd like to at least be able to turn off the fingerprint indicator. I hold my phone in my hand most of the day so it's a bit annoying that it pops up every time you move the phone. You can switch off this indicator on the S10 and it has nothing to do with the technology - it's just a guide.
My Mi 9 display is starting to burn in the fingerprint image after just 2 months of usage. I'm going to turn off the fingerprint unlock to prevent it getting worse.
Does this sound normal?
Doesn't sound normal but AMOLED displays are know for burn in marks. For that to happen you need to have the fingerprint image always on display. I got a MI9 and the finger print image dissapear after some time and reappear if I lift the phone so its almost impossible in a normal usage to burn in the display.
What kind of burn-in is it? Is it the icon, or is it from the strong light that lights up the fingerprint at scanning? The fingerprint icon must show at the same place all the time unlike the rest of the AOD. I can se how keeeping the icon on at the exact same place all the time 24/7 may hurt an AMOLED display. I turned off, both AOD and fingerprint icon, after a day or so to save battery. Now it shows only on the lockscreen for a few seconds.
gerhard_wa said:
What kind of burn-in is it? Is it the icon, or is it from the strong light that lights up the fingerprint at scanning? The fingerprint icon must show at the same place all the time unlike the rest of the AOD. I can se how keeeping the icon on at the exact same place all the time 24/7 may hurt an AMOLED display. I turned off, both AOD and fingerprint icon, after a day or so to save battery. Now it shows only on the lockscreen for a few seconds.
Click to expand...
Click to collapse
So I had seen it as a sort of retention of the fingerprint image that appears on the lockscreen. I saw it when I was walking outside in full sun today. I quickly installed an app to check different colours full screen (dead pixel fix) and it clearly showed the burn in for several colours.
But now that I'm home, I tried again the screen check app and the burn in is gone!
So I wonder if it was either just temporary retention, or if I need to be outside in full sun to see the burn.
dvanders said:
So I had seen it as a sort of retention of the fingerprint image that appears on the lockscreen. I saw it when I was walking outside in full sun today. I quickly installed an app to check different colours full screen (dead pixel fix) and it clearly showed the burn in for several colours.
But now that I'm home, I tried again the screen check app and the burn in is gone!
So I wonder if it was either just temporary retention, or if I need to be outside in full sun to see the burn.
Click to expand...
Click to collapse
Please come back here and tell us if you see it again. It would be good to know if the display is this sensitive to permanent burn-in. Keeping the icon shut off at the AOD would probably be a good idea, I find it rather easy to hit the right spot after some time of practice in the blind.
That what you have seen on sun isnt burn in, that is normal see-through screen becase sensor is under display.
No need to panic, i seen it too but that is not a problem.
Same as marko378, it's totally normal to see this on bright daylight, it's not a bur in.
Its the finger print sensor and i see it at day one
No problem bro enjoy your phone
---------- Post added at 12:13 AM ---------- Previous post was at 12:05 AM ----------
Its the finger print sensor and i see it at day one
No problem bro enjoy your phone
Nice, today in full sun I confirmed what you're all saying. It's the sensor, the hole behind the screen, and it's only visible at certain angles in full sun.
Thanks to you all for helping
That's normal because the scanner is under the screen so it has to be a little transoarent there to work that's why In screen scanners are mainly used by oled displays. Enjoy the phone
dvanders said:
So I had seen it as a sort of retention of the fingerprint image that appears on the lockscreen. I saw it when I was walking outside in full sun today. I quickly installed an app to check different colours full screen (dead pixel fix) and it clearly showed the burn in for several colours.
But now that I'm home, I tried again the screen check app and the burn in is gone!
So I wonder if it was either just temporary retention, or if I need to be outside in full sun to see the burn.
Click to expand...
Click to collapse
It is not safe for the screen in my opinion to maintain the figerprint area always lighted. I use it as per default setting that dimly lights it when I take the phone and then in few seconds it disappeared even if I touch the screen. More than 1 year with the phone and no burning in the screen.
Hi
I'm in the UK and I recently bought an LG V40 128Gb Korean version - LM-V409N on Android 9/Pie.
There are a couple of things about it that are really annoying and I wanted to know if they are LG V40 features or bugs?
1. Screen goes black when making a phone call
When I use the phone dialler to make a call I type in the numbers and press the phone icon to make the call.
As soon as I press the phone icon the screen goes black and I have to press the physical unlock button on the right of the phone to be able to see the screen again and all the in-call options like 'dialpad', 'speaker' or 'end' call.
2. 'Always-On' display turns off in a dim light
I have the 'Always-On' (AO) display turned on in my settings, in my case it's just set to be the standard digital clock.
If I'm in a well lit area and lock the screen the AO display works as it should, however, if I'm in a dimly lit area and lock the screen the AO display does not come on.
Also, if I move between a well lit and dimly lit area the AO display comes on in the well lit area and turns off when I move into the dimly lit area.
Just to confirm, I'm not pressing anything on the phone during this time.
Finally, if I'm in a well lit area and cover the top of the phone with my hand (to mimick it going into my pocket) the AO display goes off when I cover the top of the phone and immediately comes back on when I uncover the top of the phone.
I can repeat both the above issues without there being a phone case on the phone potentially blocking a sensor and also the screen has been cleaned so I don't think any sensors are being affected by grease or dirt.
Both these issues are really annoying so could anyone confirm if these are intended features on all LG V40's or just bugs on mine?
Or any other info/ideas please?
Thanks
Yeah, the issue of the screen going black is a battery saving feature. There may be a work around utilizing the battery optimization exclusions in the Settings. There also is an app that I have seen suggested to alleviate this issue. As I don't use the AOD feature I can not advise a remedy.
Medevac1 said:
Yeah, the issue of the screen going black is a battery saving feature. There may be a work around utilizing the battery optimization exclusions in the Settings. There also is an app that I have seen suggested to alleviate this issue. As I don't use the AOD feature I can not advise a remedy.
Click to expand...
Click to collapse
Hi, thanks for the suggestion. I've turned off all the battery saving features/options but I still can't get rid of either of those features/bugs?
Can anyone else with an LG V40 confirm if they can reproduce either of these features/bugs?
After further digging around, I now think these issues are caused by faulty hardware on my V40.
I downloaded an app called 'Sensor Box for Android' from the Play Store which allowed me to test all the phone's sensors (accelerometer, light, proximity etc).
When I tested the proximity sensor it is not working/responding, so I believe that these issues are probably caused by the faulty proximity sensor.
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
jdock said:
I noticed the AOD stays on in my pocket as well. I thought maybe it was by design that way, even though it makes no sense.
Have not had a single pocket wakeup though.
It does seem that the proximity sensor (which is really the camera) doesn't work especially well though, from reports of people noticing it on phone calls. Hopefully something that can be fixed in software.
Click to expand...
Click to collapse
Thanks mate, appreciate your feedback. Proximity sensor works fine on my phone during calls. Can't think of any reason why Samsung would intend it this way...
Proximity sensor issue here as well
I have the same problem. I put phone into test mode and it was bad compared to my wife's s9 search proximity sensor s20fe on YouTube and see others with issue
There is no fix. This is apparently the way AOD works now. I can't remember if it started with the S10s or S20s.
uggies said:
I am having an issue where always on display is staying ON while in pocket/faced down on the table. Feels like the proximity sensor is not working while on the AOD.
Plus, the proximity sensor doesn't seem to work while in the pocket either. The setting 'prevent accidental touches' has been enabled, however it is still responding to 'double tap to wake' while in the pocket for whatever reason...
Is there any fix to this?
Click to expand...
Click to collapse
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
No problems with Verizon S20 FE 5G UW
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
I just purchased the Samsung S20 FE 5G UW (how about we shorten this to FE UW?) with all updates AND a glass screen protector and have no touch/proximity issues.
FYI I bought it at the Costco kiosk for a few dollars less per month, no activation charges and a 90 day return policy.
the Galaxy S20 FE (5G) has no physiscal proximity sensor.
Insted it uses a combination of the front camera, touch screen and gyroscope.
I have tested the proximity issues, luckily for me there were ok...turn green. The only thing that drive me crazy is the touch screen issues which never been fixed even after updates. Oh well at least its better than before.
Huberttus said:
I did some research on s20fe proximity sensor, because I desperately wanted flip case to open and close the screen.
Here is what I have noticed: there are two "proximity sensors" both sides of the front camera. These sensors close the screen during call if you touch them (I'm not sure if it's enough to touch just 1 or do you have to touch both of them). You need to touch these with your cheek or finger cause they need a electric field.
Phone also utilizes front camera light sensor during call: if there is no light, it turns off the screen but for this to happen phone needs to be on up right position. Screen won't close if the phone is on desk and you cover the camera.
So anyways, my point is that the proximity sensor is not able to detect if your phone is in the pocket or not. Only way for the phone to detect this is with the front camera light sensor, and I guess this would increase the battery consumption so much, there is no point.
You can test your "proximity sensors" by typing *#0*# in dialer numpad, select sensors and touch from the side of the front camera. If the screen turns green sensors are working.
Click to expand...
Click to collapse
Mate great information here, really appreciate this.
Tested the Proximity sensor using *#0*#, I agree with your analysis. The proximity must be using electric reaction to detect if my ears are touching it or not. Covering it with a book does not trigger a proximity sensor... This explain why my screen keeps waking up in the pocket.
As much as this is annoying, there appears to be no way out Just have to let the phone face outside rather than my legs.
I also have the same issue, while on a phone call, the phone's screen goes on and off constantly and I can see the notification bar moving. Very annoying.
This is a terrible design by Samsung. The punch hole usually goes in the "Empty" part of the ear, so the screen stays mostly on.
I might just return the phone because of this issue, I don't see it getting fixed by a software update.
I have the exact opposite issue with the proximity sensor on my Samsung S20 plus running Android 10 - i.e. it works well by turning the screen off when my ear/cheek/face is very close to the proximity sensor during phone calls; whereas, when the phone's screen is locked and turned off, the proximity sensor is turned off as well. Control by hardware? Software/firmware? Don't know?! To turn the screen on without using the Power hardware button, I had to enable the "Double Tap" feature in Settings.
On earlier/other Android mobile devices - Samsung included - the proximity sensor is always on - whether the screen is on, off, or currently locked. When it's always on, you can be innovative and build a widget, for instance, to turn the screen on by "waving" your hand above the proximity sensor to interrupt the laser. I suspect new(er) Samsung mobile devices like S20 and Note20 variants might be using a "virtual" proximity sensor setup/combo for controlling the device's screen - and that really sucks!
To test if the proximity sensor is always activated on Samsung S20 and Note20 variants, I type *#77692# - which displayed a hardware screen to test proximity and light sensors. Note: if you type *#0*#, the proximity and light sensor options are absent from the hardware test screen.
Has anyone found any method - via codes even - to permanently turn on the proximity sensor, even when the screen is locked and turned off?
I searched through AOSP framework vanilla codes and couldn't see anything out of the ordinary regarding control of the proximity sensor. Samsung might be doing something dubious with their firmwares/hardwares though - well, at least, the S20 and Note20 variants are having issues with the proximity sensor setup.
P.S: Not sure if you guys are aware, but Samsung mobile devices with odd designation tends to be more problematic than their even-designated counterparts, like screen's burn-ins/shadows on Samsung S3 devices, light sensor fluctuation (which affects screen brightness control) on Samsung S5s, and now proximity problems with the S20s and Note20. Samsung S20 variants are in fact "S11" variants renamed. So the trend continues with Samsung always stuffing up their odd-designated device releases.