Database Develop

Strange Adaptive Brightness issue

Off late I'm noticing that whenever I turn on the display, it goes completely bright for maybe 5 seconds before adaptive brightness kicks in. Today I completely reset my phone and reflashed the latest factory image (MRA58R, I was on MRA58N previously). It was fine for a while (for a few hours) and now it has started behaving the same way. It works fine if I turn off adaptive display. This happens 90% of the time.
Has anyone else faced this?
---
I have filed a bug report, please star it.
https://code.google.com/p/android/issues/detail?id=196048

I've got the same issue on 6.0 stock not rooted. I've been fiddling around with lux trying to get it to stop going to max bright in low light settings... And it seems that the light sensor is getting incorrect readings in low light and it takes a few seconds for the sensor to start showing accurate levels for the light conditions. I would love to have adaptive brightness work as it used to - don't know what changed.

Same issue here.

Woah. I'm not alone. So for all you guys, it started just recently?

yeah. I noticed it a little less than a week ago

Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.

foxnutz said:
yeah. I noticed it a little less than a week ago
Click to expand...
Click to collapse
Hmm. Same here. Started last week. Will have to dig out what the root cause is.
altimax98 said:
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
Click to expand...
Click to collapse
Nope. I'm running completely stock, no root, even locked bootloader (for device protection feature).

I am running completely stock marshmallow no root, boot loader is locked, no gravity box. Same problem.
Is there any program we can use to monitor the readings at the light sensor is receiving?

I have tried two apps but that doesn't seem to gather data while running in background; only works when the app is opened. Still trying to find one that does background logging.

I have the same issue.
And I thought it was Gravity Box.... now I wonder if it's the November patch? Since there is report from people who never root and using stock?

Ok, so I found an app that can log data while in background. It's called Androsensor. It also has a companion app (Androsensor Keep Awake) which helps to hold a wakelock to gather more data. I tried it and I feel it's definitely not the sensor or it's driver/binary malfunctioning, it seems to be reporting proper values. Maybe more people can try it and report back.

i just bought my phone (brand new) update it right away to 6.0 and used it and having thesame issue!
that means this is google firmware problem!

The reason I believed it to be the sensor was because I used lux to try and fix this and noticed when the bug was occurring, as the screen just turned on and went to max brightness, lux showed the values from the sensor above 20000. Oddly enough if I had lux update every 3 sec it would sometimes capture the actual light levels on the second update and adjust accordingly. I'll check out the app you mentioned and see what shakes out.

I'm having it too, also completely stock and unrooted, first noticed it a few days ago. A friend of mine also has it. He is also stock, I'm not sure about his root status though.

Ok got some interesting results this morning using androsensor. First of all I was unable to recreate the bug while using the keep awake helper app... Which leads me to believe that there may be some issue with the sensor values being calculated/averaged by the autobrightness code/program as the device wakes up from sleep. perhaps android is shutting off the light sensor when the device goes to sleep and this causes a reset? So it appears that it's not getting wrong values rather, that the data being drawn from the sensor is reset or perhaps recalculated as the device wakes back up. Almost as if it can't remember the last light level that was observed. I uninstalled the wake lock helper and was able to recreate the bug by letting the device "sleep" (leaving the screen off for maybe 5 seconds). So while the sensor showed readings of 2 lux the screen brightness was increased erroneously until the auto brightness refreshed and then after a few updates on the sensor the correct brightness was applied to the screen. Curious results. Can anyone else try to recreate the bug using androsensor and the wakelock helper program? I'm hoping I didn't run into some user error there.

I too tried without the wakelock helper and got the same result which made me believe it's not the sensor that's causing it. Will try the same with the helper app and report back.

Just tried Androsensor with the helper and I was unable to reproduce the bug, exactly what foxnutz faced.

Alright so we got some results! Just for the sake of being thorough, can anyone else replicate these results that andr0idfreak and myself saw? It seems holding a wakelock on the sensor stops this bug.
Now where do we go from here? It's been an awfully long time since I've done anything with logcat... But I think that may be our best bet to find out what's really going on here. I'll have to do some homework before proceeding. Will report back.

I think we should file a bug report here.
https://code.google.com/p/android/issues/list

I think a bug report is probably worthwhile. I thought it was some combo of xposed and gravitybox as well but I flashed my stock system back and it's doing the same thing.

Auto brightness not working correctly after 6.0.1 update

Several users (including myself) have pointed out that the automatic brightness doesn't work as before the 6.0.1 update.
Here are some of the reports:
kom-pakt said:
One of the few drawbacks I noticed just today is that the auto brightness seems a lot less responsive. For example it's very sunny today and most of the time when pulling the phone out of my pocket the display was still stuck on low brightness. It might just be a conflict with xposed or something else I'm running.
Click to expand...
Click to collapse
GFixx said:
I have a bug with automatic screen brightness, if I unlock the phone at the sun I do not see almost nothing
G800F ITV 1CQA1
Someone can confirm?
(GPS and Volume seems fine)
Click to expand...
Click to collapse
milad9896 said:
I also have this problem sometimes
Click to expand...
Click to collapse
So far I've tried running the phone without anything on it like Xposed or any apps beside the stock ones and it hasn't fixed the issue. What I do know is that it's definitely not a hardware issue since the light sensor works as it's supposed - you can test yours by entering the service menu by typing *#0*# from the dialer. I am currently running the German DBT firmware but I'm currently in the process of flashing the South East Europe SEE firmware which is different only in the security patch, so if the problem persists then I will know for sure it's not a DBT-only problem.
How many of you have this issue as well? Also, which version of the firmware are you running?

Me too. Also DBT FW with 6.01. Flashlight has also an issue in the dark.
Gesendet von meinem SM-G800F mit Tapatalk

I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "

Myke72 said:
Me too. Also DBT FW with 6.01. Flashlight has also an issue in the dark.
Gesendet von meinem SM-G800F mit Tapatalk
Click to expand...
Click to collapse
I am currently running the South East Europe (SEE) firmware but I haven't tested it extensively so I can't say if it's any better.
GFixx said:
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Click to expand...
Click to collapse
So Samsung's solution for this is to use manual brightness? Really Samsung?

I have the same after upgrade to 6.0.1, it's unbelievable such a bug in official release
any fix for this?
I installed Auto Brightness app, but it seems Samsung display goes above 100% in sun, third party apps can't do it

Does anyone have realy bad battery Problems too? (See my thread...)

GFixx said:
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Click to expand...
Click to collapse
I have the same problem - I made a video of it below. It's a serious usability problem - makes it very hard to use in sunlight.
As a kind of workaround you can put your thumb over the light sensor as you wake it up, then it will wake up dim but still visible. Eventually it will adjust and brighten to match the sunlight. But this is slow and awkward and needs two hands.
The reply you got from Samsung is ridiculous. For a start, the stronger the external light source, the stronger the brightness of the device - they have it the wrong way around. Anyway, it is obviously a major usability problem and I can't believe they are dismissing it. (And manual brightness is not an answer of course.)
Phone specification:
Model number: SM-G800F
Android version: 6.0.1
Baseband version: G800FXXU1CQA1
Kernel version: 3.4.39-10294723 [email protected]#1 Wed Jan 4 12:03:16 KST 2017
Build number: MMB29K.G800FXXU1CQA1
SE for Android status: Enforcing SEPF_SECMOBILE_6.0.1_0033 Wed Jan 04 12:28:05 2017

It works fine on my G800H with latest Polish stock ROM

I don't use to write in the forum, but I must say 'me too'. If someone knows a working Marshmallow ROM for the G800F. The thumb "workaaround" is the only one working for me..

I strongly encourage everyone facing this problem to write an e-mail to Samsung through their official website. In your e-mails make sure you note that this problem is definitely caused by a software issue and not a hardware issue - the auto brightness worked fine with KitKat and Lollipop, but not with Marshmallow. We need to bring this to their attention so they can fix it in a firmware update and the only way to do this is to send them as many reports as possible.

kom-pakt said:
I strongly encourage everyone facing this problem to write an e-mail to Samsung through their official website. In your e-mails make sure you note that this problem is definitely caused by a software issue and not a hardware issue - the auto brightness worked fine with KitKat and Lollipop, but not with Marshmallow. We need to bring this to their attention so they can fix it in a firmware update and the only way to do this is to send them as many reports as possible.
Click to expand...
Click to collapse
I'll do this. Do you know the best email address to use? Also I'll drop in at the nearby Samsung shop (hopefully on a sunny day) and see what they say.
I'm surprised that this bug isn't much more widely talked about given that it's a major usability problem, and given that the S5 mini is a popular phone (hundreds of thousands, maybe millions?, sold). So I wonder if it's possible that there is something special about our phones, and the bug doesn't happen on most people's devices. But I can't think what it would be. I've not done anything unusual with my phone - it's just a standard out-of-the box phone running the official operating system.

alex3453 said:
I'll do this. Do you know the best email address to use? Also I'll drop in at the nearby Samsung shop (hopefully on a sunny day) and see what they say.
I'm surprised that this bug isn't much more widely talked about given that it's a major usability problem, and given that the S5 mini is a popular phone (hundreds of thousands, maybe millions?, sold). So I wonder if it's possible that there is something special about our phones, and the bug doesn't happen on most people's devices. But I can't think what it would be. I've not done anything unusual with my phone - it's just a standard out-of-the box phone running the official operating system.
Click to expand...
Click to collapse
Use the official Samsung website (for your region) to report the issue. Browse a bit and you'll find the form.
It's strange that the number of people affected by this issue seems relatively small, keeping in mind that XDA is a forum where a typical user is usually a power user. Also it's not a region-specific issue or caused by an app or something else. For example I thought that maybe Xposed is causing a conflict so I did a complete wipe and flashed a fresh firmware, used the phone like that without any apps for a couple of days but the autobrightness issue was still there. Tried a different firmware version as well but nothing helps. Again, it's definitely not a hardware issue - test yours by typing *#0*# from the dialpad to enter the service menu and test the sensor yourself.

I solved the problem disabling the automatic brightness function and using Lux Lite as workaround instead

I have this issue too. Hungary (Telenor) G800FXXU1CQA1. The service does not find any problem. I refered severel minor issues (among autobrightness failure), but I did not managed to talk to them, and they wrote that there is not any hardware problem with the phone. They recalibrated the sensors, so that might help.
Lux Lite solved the problem, thanks!

Hello I have the brightness issue too (G800FXXU1CQD1) official french ROM, since I upgraded to 6.0.1.
I also had some strange charging issue.
I tried with different wall chargers. When I plug them, the charging led doesn't turn on. The battery charging icon in the status line on top doesn't indicate charging.
But if I leave the device for some time and reboot, the battery level increases. So it means that it charges !!
Once I tried removing battery and it recovered, but not every time...

ffoucault said:
I solved the problem disabling the automatic brightness function and using Lux Lite as workaround instead
Click to expand...
Click to collapse
bravur said:
I have this issue too. Hungary (Telenor) G800FXXU1CQA1. The service does not find any problem. I refered severel minor issues (among autobrightness failure), but I did not managed to talk to them, and they wrote that there is not any hardware problem with the phone. They recalibrated the sensors, so that might help.
Lux Lite solved the problem, thanks!
Click to expand...
Click to collapse
Lux Lite is only a workaround, but not an acceptable solution. That would be an official update from Samsung which solves the problem caused by their original update.
foulke said:
Hello I have the brightness issue too (G800FXXU1CQD1) official french ROM, since I upgraded to 6.0.1.
I also had some strange charging issue.
I tried with different wall chargers. When I plug them, the charging led doesn't turn on. The battery charging icon in the status line on top doesn't indicate charging.
But if I leave the device for some time and reboot, the battery level increases. So it means that it charges !!
Once I tried removing battery and it recovered, but not every time...
Click to expand...
Click to collapse
Did you try the basic stuff like reflashing the firmware and such?

kom-pakt said:
Lux Lite is only a workaround, but not an acceptable solution. That would be an official update from Samsung which solves the problem caused by their original update.
Did you try the basic stuff like reflashing the firmware and such?
Click to expand...
Click to collapse
No. I don't want to use Odin for the moment.
By the way I installed Lux, and it works fine.

I'm surprised you're happy with Lux, official Samsung can do much more brighter screen in strong sun then Lux

By the way, I removed Lux since. Because it requires too much app permission than I think it should (contacts...)
So I'm looking for an another solution

Good news!
Yesterday I jus tried to install the latest firmware available on sammobile (for G800F) - the one for nordic countries -.. and now the brightness control is working perfectly!
Seems that this 'not' problem was fixed in latests releases :good:

Outdoor Mode (hidden brightness menu, WHY?)

title says it all, why is this hidden and can only be accessed thru settings, and it's not a one time toggle, you'd have to go into settings every time you pull your phone out. just why? would be great for the brightness slider to just go to max instead. anyone know if theres any mods for this? or just what this is about, seems strange.

i dont have this mode
what android version u have
Sent from my SM-N950F using Tapatalk

I cannot find this mode on my Exynos Note 8! Have you flashed another rom?

soraxd said:
title says it all, why is this hidden and can only be accessed thru settings, and it's not a one time toggle, you'd have to go into settings every time you pull your phone out. just why? would be great for the brightness slider to just go to max instead. anyone know if theres any mods for this? or just what this is about, seems strange.
Click to expand...
Click to collapse
Mine always stays where ever put the slider. But then, I have auto brightness off.

Yeah what version you got? Wish we had outside mode.

I have a 950F exynos 128 GB, and It does not have such setting...

Because it's samsung. They will probably never make a good software. Just search for "automatic brightness bug". They just ignored this problem. No wonder they just hidding that option.
Outdoor mode can be enabled by editing something in system folder. Most of custom firmwares provides that function.

I've never seen that setting on mine. It's automatic for me.

GreyFox777 said:
Because it's samsung. They will probably never make a good software. Just search for "automatic brightness bug". They just ignored this problem. No wonder they just hidding that option.
Outdoor mode can be enabled by editing something in system folder. Most of custom firmwares provides that function.
Click to expand...
Click to collapse
IT is not a bug, and yes, there are ways to increase brightness beyond standard maximum, I remember from the days of my note 3, that many people posted very bad screen burn in and excesive batt drain when changing the lines to attain the most bright screen possible, same applies to speakers, might as well get blown, The auto brightness in note 8, in fact is very well implemented, because it learns your preferences, that is, if set to auto, and you move the slider, whenever the phone detects the same lux level, it will set the level you chose, infact, when in autobrightness, when sensing too much light, it will set an extra ammount of brightness

hi guys flahed s8+ and note 8 oreo(nougat no) flash twrp outdoor mode
https://drive.google.com/file/d/1bNVtkh9l6_rAAOubzLcwh8pE6lIiINDl/view
ENABLE OUTDOOR MODE OREO
https://drive.google.com/file/d/1bNVtkh9l6_rAAOubzLcwh8pE6lIiINDl/view

//

winol said:
IT is not a bug, and yes, there are ways to increase brightness beyond standard maximum, I remember from the days of my note 3, that many people posted very bad screen burn in and excesive batt drain when changing the lines to attain the most bright screen possible, same applies to speakers, might as well get blown, The auto brightness in note 8, in fact is very well implemented, because it learns your preferences, that is, if set to auto, and you move the slider, whenever the phone detects the same lux level, it will set the level you chose, infact, when in autobrightness, when sensing too much light, it will set an extra ammount of brightness
Click to expand...
Click to collapse
Agreed. Works very well. Was using GPS Google maps for the first time yesterday, screen was automatically too bright. I used slider to lower brightness, it learned my preference.
Sent from my SM-N950U using Tapatalk

Since long I haven't seen any Note device (at least International versions) have Outdoor mode enabled by default unless you are using custom ROM. But this mode i have seen available on low range samsung devices. Actually it is hidden and one minor change in settings app enough to enable outdoor mode.
I will try to make small app without making changes in setting app, though it might needed root access.

Thank you dr ketan! I have used your excellent roms and kernels in my note 3 and 4

As I said y'day, I have made and posted Outdoor mode Tool on my Facebook wall.

dr.ketan said:
As I said y'day, I have made and posted Outdoor mode Tool on my Facebook wall.
Click to expand...
Click to collapse
hey something cool came out of this post, awesome!
so the app acts like a toggle to turn on the outdoor mode, pretty cool!

Works perfectly. Thank you.

Have noticed this mod seems to time out after 15 minutes or so. Any workaround for this?

@ dr.Ketan: since updating to oreo your app does not work anymore... do you have a solution?
THX in advance!

I am on oreo too and working fine. Check you have granted su permission

[solved] Adaptive brightness broken in pie

Does anyone else have this issue? Every time you lock/unlock the brightness auto adjusts again (and it adjusts pretty low)
So even if I manually set it to 100% and lock/unlock it will be down to 25% again. Doesn't seem like it's learning at all

carloandreaguilar said:
Does anyone else have this issue? Every time you lock/unlock the brightness auto adjusts again (and it adjusts pretty low)
So even if I manually set it to 100% and lock/unlock it will be down to 25% again. Doesn't seem like it's learning at all
Click to expand...
Click to collapse
Seems like it takes a lot of time to learn. I don't use it anyway I prefer having control on it

carloandreaguilar said:
Does anyone else have this issue? Every time you lock/unlock the brightness auto adjusts again (and it adjusts pretty low)
So even if I manually set it to 100% and lock/unlock it will be down to 25% again. Doesn't seem like it's learning at all
Click to expand...
Click to collapse
Seems like a bug honestly, because it goes TOO LOW. I tried to lock the device several times to see if the "learning" of the slider improves, but it still goes back to the same spot... I'm gonna keep it deactivated until they fix it.

Android Pie has AI in basically everything and it learns for you, just keep adjusting the brightness manually and in a few days it'll know how you like your brightness and adjust it for you.

I care about to go low! And now I can't go below 19% with Adaptive ON, it's to high for a dark room.

jaycedam said:
Seems like a bug honestly, because it goes TOO LOW. I tried to lock the device several times to see if the "learning" of the slider improves, but it still goes back to the same spot... I'm gonna keep it deactivated until they fix it.
Click to expand...
Click to collapse
Actually I've been reading similar things about this on the pixel so it might just be the way it is. Might take long for it to learn. I read someone say it's always fun when he first unlocks it

And I found this link of people claiming it is like this the first few days until you train it better
https://www.reddit.com/r/GooglePixe...daptive_brightness_work_for/#thing_t1_e3yv49m

carloandreaguilar said:
And I found this link of people claiming it is like this the first few days until you train it better
https://www.reddit.com/r/GooglePixe...daptive_brightness_work_for/#thing_t1_e3yv49m
Click to expand...
Click to collapse
Yeah it could be the new implementation of the AI, I'm gonna use it for a few days to see if it gets better

This has started happening to me since yesterday. I've been using Pie for a month now (December update). What I've noticed is that it goes down to about 25% every time I cover the brightness sensor with my finger (usually when watching YT) and it stays there no matter what. It's pretty annoying having to always adjust it like that. Using "Sensors Monitor" app I see that the sensor is working correctly so it's a software "feature".
Any suggestions on how to mitigate it besides using "Velis Auto Brightness" app?

How do we know its 'AI'? Has it 'adapted' for anyone till now? That brings us tk the question, what was wrong with Auto Brightness in Oreo? Just because there's piece of code that's new, doesn't mean its versatile.

glasseffects said:
How do we know its 'AI'? Has it 'adapted' for anyone till now? That brings us tk the question, what was wrong with Auto Brightness in Oreo? Just because there's piece of code that's new, doesn't mean its versatile.
Click to expand...
Click to collapse
Three words.
Mar ket ing

Ashik_salim_ said:
Three words.
Mar ket ing
Click to expand...
Click to collapse
Yeah, and some of us would be fixing what was intentionally broke. Interesting, what would Android be without the community working as the underdog?
Oh, and AI (its Computational Intelligence) is the new cheaper, efficient corporate slave working to enslave the many.

Flickering dot under display in notification area

Hi all,
Been quite a few years since I posted anything here!
I have just received my pixel 5 and have noticed that dead center of the notification tray when in portrait, there is a flickering dot, especially in low light it flickers white or if not flickering leaves a faint grey dot over whatever is on the screen (stays in the same place even if I rotate the phone or watch a video)
If I reboot I can't see it for a minute or so until it then appears.
Factory reset doesn't solve it.
Has anyone else noticed this? I'm thinking it might be the ambient light sensor under the display but it is really irritating, possibly mine is faulty?
Cheers!

It's the underscreen proximity sensor.

I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?

Not showing on mine

I have it constantly when KinScreen is running, I saw someone having it with cpuz

I hadn't noticed until I saw this thread. I did wonder where the proximity sensor was. It's only visible when on a phone call for me.
Is the light sensor under the screen also? You can usually see that on a lot of devices when you tilt the screen slightly.

Joshhudsy said:
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Click to expand...
Click to collapse
Mine only shows when on a call

You probably have some apps using it. Possibly something like Tasker that happened to have proximity sensor based profiles configured, etc.

Mine went mental during Google Play downloading all my apps on initial phone setup. Then it went out and I've not seen it since.

Joshhudsy said:
I get that it is the proximity sensor but, It is flashing constantly - I spoke to google and they said that it should only show when in a call - it is flashing even while watching YouTube - does anyone else get this same behaviour?
Click to expand...
Click to collapse
It's a software bug. I read about it on reddit and twitter yesterday. Did you move your data from your old phone using the cable?
To fix it you should factory reset, then migrate your old data using WiFi, not cable, don't restore or restore your apps manually (at least until you make sure it's fixed).
If that still doesn't work, check if you have an app called HomeAssistant (HASSIO) installed. There's one report of that causing it. To fix that you need to disable the proximity sensor on the assistant app itself.
Sources: here, here, and here.

I got the same Problem after installing notifybuddy. There must be some Bug where the sensor gets started the moment an overlay is shown. I can reproduce the Bug over and over again. Install notifybuddy and Start the App give all permissions and than Pull down notificationscenter (its an overlay). To solve the Problem, uninstall notification Apps That are using overlays.

Mine is working fine. Only during a call or listening to voice messages.

akpe said:
It's a software bug. I read about it on reddit and twitter yesterday. Did you move your data from your old phone using the cable?
To fix it you should factory reset, then migrate your old data using WiFi, not cable, don't restore or restore your apps manually (at least until you make sure it's fixed).
If that still doesn't work, check if you have an app called HomeAssistant (HASSIO) installed. There's one report of that causing it. To fix that you need to disable the proximity sensor on the assistant app itself.
Sources: here, here, and here.
Click to expand...
Click to collapse
Hit the nail on the head there!
It was the Home assistant app causing it (even though it had installed after restoring from my backup, I had never opened it yet since having this phone). Uninstalled home assistant and it has stopped flashing!
Thanks so much for the replies all!

Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.

Anwar902 said:
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Click to expand...
Click to collapse
Go to the gestures options (don't know exactly where the specific one is located, it could also be at the Digital Wellbeing settings) and disable the Flip to Shh one. See if that helps.
Στάλθηκε από το Mi A2 μου χρησιμοποιώντας Tapatalk

Anwar902 said:
Have this issue on my one too...which is the home assistant app? Deleted the "Home" but that doesn't seem to have solved the problem.
Click to expand...
Click to collapse
The Home assistant is a 3rd party home automation app that I had previously installed - if you don't use it, I'd check for any other apps you have installed for something that might be using the proximity sensor.

Couldn't find that was causing the issue. After a restart it would be fine but once unlocked and apps started loading it would go crazy. Went through all my apps but couldn't find the cause so just reset my phone. Hopefully it doesn't show up again.
Seems to.be software issue so hopefully google will do something about it

Joshhudsy said:
The Home assistant is a 3rd party home automation app that I had previously installed - if you don't use it, I'd check for any other apps you have installed for something that might be using the proximity sensor.
Click to expand...
Click to collapse
It really shouldn't matter if something is using the proximity sensor. It shouldn't ever be visible.

jimv1983 said:
It really shouldn't matter if something is using the proximity sensor. It shouldn't ever be visible.
Click to expand...
Click to collapse
That's incorrect. A quick Google search for "S20 proximity sensor blinking" will yield results that show otherwise. Maybe go to YouTube instead as there's quite a few videos there on it. The Samsung subreddit has an influx of posts, it seems, for almost every device they've released over the past couple of years because folks aren't used to seeing it. It's visible under the display on my S20 Ultra and I had it on my S10 plus also.
Now of course there's bugs where it's blinking on the Pixel 5 when it shouldn't, but is it supposed to be visible when an app is using it legitimately? Yes.
Edit: It just dawned on me that YouTube vids wouldn't be the best example of this because they use cameras to video the proximity detector. Everything else stands though. Google searches and Samsung subreddits are ripe with examples though.

MasterBelch said:
That's incorrect. A quick Google search for "S20 proximity sensor blinking" will yield results that show otherwise. Maybe go to YouTube instead as there's quite a few videos there on it. The Samsung subreddit has an influx of posts, it seems, for almost every device they've released over the past couple of years because folks aren't used to seeing it. It's visible under the display on my S20 Ultra and I had it on my S10 plus also.
Now of course there's bugs where it's blinking on the Pixel 5 when it shouldn't, but is it supposed to be visible when an app is using it legitimately? Yes.
Edit: It just dawned on me that YouTube vids wouldn't be the best example of this because they use cameras to video the proximity detector. Everything else stands though. Google searches and Samsung subreddits are ripe with examples though.
Click to expand...
Click to collapse
If what you are saying is true then why can't you see the sensor flashing on any phone when in a phone call or when the "Flip To Shhh" feature is enabled with just your eyes?
And if that is true about the Pixel 5 then there will be no way to use the "Flip To Shhh" feature without always seeing the sensor flashing which I can do with my Pixel 2 XL.
Here is a video of my Pixel 2 XL taken with the camera on my tablet. You can see that the tablet picks up the flickering sensor when "Flip To Shhh" but the sensor goes off when I turn the feature off. That's because the feature uses the proximity sensor to work. However, the flickering is ONLY picked up by the camera on my other device. I can't see it with just my eyes looking at the phone even though the sensor is active.
https://streamable.com/z30mgx