Database Develop

Smart Display with Android L not working

Hey,
So after updating to 22.21.19 retde, I found the smart display feature, that is meant to keep the screen on when you look at the display, is no longer working. It is enabled and the test that is accessible from the options works and can successfully determine whether I look at the screen or not.
Can anyone confirm this behaviour under android L? It would be remotely possible this is an isolated case since I had to completely factory reset my phone for the update, to remove root. I am also rooted on the new build.
So, if you run the same version of Android L, I'd like to hear whether smart display works for you or not. Thanks in advance.

Yes it seems to be broken for now
Sent from my XT1095 using Tapatalk

You're not the only one.

It does work sometimes, others it simply ignore your face and dimm the brightness too fast.

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.

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

S10 plus touch sensitivity not working

I have a stock s10 plus. at first, the issue happened when I tried to pull my notification panel down but realized touch screen isnt working but its localized toward the top. Over the next few days, the area spread from top of the notifications bar to half of the screen and finally to my fingerprint scanner. I though the display is damaged but testing it with *#0*# test prove its working. locking the screen and unlocking it seems to fix it temporarily but it happened after a minute or two. my device feels laggy when the display is working normally. No visual damage nor did I damage it in any way

Arizzrn said:
I have a stock s10 plus. at first, the issue happened when I tried to pull my notification panel down but realized touch screen isnt working but its localized toward the top. Over the next few days, the area spread from top of the notifications bar to half of the screen and finally to my fingerprint scanner. I though the display is damaged but testing it with *#0*# test prove its working. locking the screen and unlocking it seems to fix it temporarily but it happened after a minute or two. my device feels laggy when the display is working normally. No visual damage nor did I damage it in any way
Click to expand...
Click to collapse
Maybe try to factory reset to see if it resolves the issue.

Keno_I said:
Maybe try to factory reset to see if it resolves the issue.
Click to expand...
Click to collapse
doesn't work. i even tried using the firmware that worked before and had no issue but it doesn't work now

Saeremi said:
doesn't work. i even tried using the firmware that worked before and had no issue but it doesn't work now
Click to expand...
Click to collapse
Possible water damage?
It sounds like mobo issue... as the display tests normally and firmware doesn't fix it.
Try a hard reboot.

MOD ACTION:
Thread closed at the request of the OP.

Question Display dims for a few secs after screen unlock

This has been an age-old issue on multiple devices and still can't find a solution.
When the screen is unlocked the display is dim to a very low brightness hardly enough to use for a few seconds, roughly about 5s, and it turns on to the normal brightness. I find this issue reported to have been occurring since 2105? or earlier on phones from OnePlus and others.
I have Nova launcher as default, altered it's settings, just in case, in vain. After tinkering with many options in the settings i couldn't find a proper solution. Then I found that after the phone is booted, the problem didn't occur for some time, under a minute. So i Disabled multiple apps from startup, yet, nothing changed. It was also noted that the display was not fully dim though, whilst the home screen was dim, the status and the notification drop down stayed lit with normal brightness. Afterall, it seems the fingerprint might the thing causing the issue that the phone doesn't show a problem when screen unlock is performed via other methods like pin. Apparently, it's all BBK phones that's having this issue? Even though this is not a big problem, the experience is pretty annoying. And, it wasn't there when i first used the phone.
So, is there a workaround for this issue other than disabling fingerprint or using other login methods? Or could it be a bug that's to be resolved in an OS update? Any help is appreciated.
Edit: vivo pushed an OTA update today, and after installing that, it seems the issue has been resolved. There's no mention of such an issue in the bugs fix list, let's still assume it was a bug.
Edit 2: Well, the problem persists (also deleted attached image of update which did not help resolve the issue).

daftdrift said:
This has been an age-old issue on multiple devices and still can't find a solution.
When the screen is unlocked the display is dim to a very low brightness hardly enough to use for a few seconds, roughly about 5s, and it turns on to the normal brightness. I find this issue reported to have been occurring since 2105? or earlier on phones from OnePlus and others.
I have Nova launcher as default, altered it's settings, just in case, in vain. After tinkering with many options in the settings i couldn't find a proper solution. Then I found that after the phone is booted, the problem didn't occur for some time, under a minute. So i Disabled multiple apps from startup, yet, nothing changed. It was also noted that the display was not fully dim though, whilst the home screen was dim, the status and the notification drop down stayed lit with normal brightness. Afterall, it seems the fingerprint might the thing causing the issue that the phone doesn't show a problem when screen unlock is performed via other methods like pin. Apparently, it's all BBK phones that's having this issue? Even though this is not a big problem, the experience is pretty annoying. And, it wasn't there when i first used the phone.
So, is there a workaround for this issue other than disabling fingerprint or using other login methods? Or could it be a bug that's to be resolved in an OS update? Any help is appreciated.
Click to expand...
Click to collapse
Just try NOT to set auto brightness ON and see things can improve.

rnjsx100 said:
Just try NOT to set auto brightness ON and see things can improve.
Click to expand...
Click to collapse
Sorry i did not mention I did try that method in the first place of all. We could tell it isn't the auto brightness causing the issue if the status bar and notifications are displaying in normal brightness.

The issue was resolved with an update.
Edit: not really. Sick.