Database Develop

[Q] Ambient Display Randomly Turns On

What is everyone experiencing? I have a T-Mobile Nexus 6. I am running stock and not rooted. Apologies if this has already been covered, but I searched a couple of different ways and did not see anything.
Not sure what others are experiencing, but my Nexus 6 display will randomly wake into ambient mode even when I just have it sitting still on my desk or couch. There are no alerts that are driving it, so I am just wondering if others are seeing the same thing or if they have done anything with the settings to clear this issue.
I can't imagine that ambient display is a huge drain on the battery or anything, but it's not nothing. Plus it's distracting when it happens.

I've noticed mine coming on due to vibrations. I had it sitting on a minifridge next to my desk. I thought it was random too, but it turns out I was either knocking the side of my desk with my knee, or the fridge was kicking on/off.

Mine does it all the time. No movement to the phone or even around the phone. Hands no where near it. Just decides to wake up. I find the whole ambient display to be pretty annoying altogether honestly. Hoping devs can disable it and find a way to use the LED.

I saw a weird error message from LightFlow (which I installed and enabled to see what it would do). I wonder if this or other apps that are running in the background and potentially causing the screen wakes.
I will try uninstalling LighFlow to see if it improves the situation and report back with any news.

I think you might be right. I have the same problem but I didn't notice it when I first got the phone. I have installed lightflow and now that you mention it, this problem started soon after. So I just uninstalled lightflow and it already seems better.

When I installed that double tap to wake app it messed with ambient display and would turn it on, especially when the battery was low. I removed that app.
Since then I have also turned off ambient display because I found it fairly useless and feel it is using battery for very little benefit. If it flashed faster or kept flashing until I checked it I think I'd use it.

I turned it off because I had it sitting on a table with nobody touching the table and it kept coming on. I couldn't get light flow to get the light working unfortunately, hopefully there is a fix coming.

Moostafa29 said:
Mine does it all the time. No movement to the phone or even around the phone. Hands no where near it. Just decides to wake up. I find the whole ambient display to be pretty annoying altogether honestly. Hoping devs can disable it and find a way to use the LED.
Click to expand...
Click to collapse
root phone, install light flow, disable ambient display.
it's already been done.
i use light flow and it works perfectly, sans flashing LED but that seems hardware/kernel blocked.

It seems that LightFlow is what was causing the issue as I haven't noticed the screen waking since uninstalling it yesterday.
Sent from my Nexus 6 using XDA Premium HD app

I'm definitely looking forward to getting the LED indicator working.
Sent from my Nexus 6 using XDA Premium HD app

Auto brightness issue

Has anyone noticed an issue with the auto brightness of the note 8 ? It seems it doesn't get adjusted efficiently! Sometimes it's too dim and sometimes too bright, that's so disturbing

It's really funny, it worked after I installed an application called lux lite, that's unbelievable.. I need to install a third party application on a 1000$ cellphone to get such a basic function working. Thanks Samsung !

ghassan haddad said:
It's really funny, it worked after I installed an application called lux lite, that's unbelievable.. I need to install a third party application on a 1000$ cellphone to get such a basic function working. Thanks Samsung !
Click to expand...
Click to collapse
I believe you are wrong about this. The auto brightness is adaptable, in the sense that you can set it manually wherever you want in different comditions and it will learn your preferences and interpolate. I actually find it very flexible.

pedmond said:
I believe you are wrong about this. The auto brightness is adaptable, in the sense that you can set it manually wherever you want in different comditions and it will learn your preferences and interpolate. I actually find it very flexible.
Click to expand...
Click to collapse
I find that is not doing such a hot job at learning my preferences. I keep having to manually adjust because my phone thinks it knows what I want. It's annoying.

pedmond said:
I believe you are wrong about this. The auto brightness is adaptable, in the sense that you can set it manually wherever you want in different comditions and it will learn your preferences and interpolate. I actually find it very flexible.
Click to expand...
Click to collapse
do you mean that it has a new functionality that has not been in old phones? I have the Note 4 and it works like a charm, but the note 8 auto brightness works strangely, when I'm in a room with low brightness the screen light goes so dim that I can barely see anything!

Ive experienced the same thing, I have to do a screen lock for its auto brightness to work correctly

Hi,
(sorry for my English)
Your message was one month ago but I reply just in case some people have the same issue.
You have to call samsung about your issue. I have done that there are 2 months ago and Samsung are going to change the settings only if they have lot of complaint about this weird behaviour of the note 8, S8 and S8+.
The new settings of the auto brightness is "smart" but often it's more like "lost" than "smart"... :/
I adked to Samsung to give 3 choices for the settings of the auto brightness for the user instead of 2:
1) manually
2) auto "smart"
3) auto "not smart" => so the phone adjust the brightness depending only of the light sensor.
They told me that my proposition can be integrate only if they received lot of complaint.

Seems to come with last update
I can confirm am having the exact issue..
Brightness doesn't seem to auto adjust. Even after a reboot. The issue seems to come during the last update - the update where now we can have video lockscreen and animated AODs.
Hope this is resolved soon.

N1T15H said:
I can confirm am having the exact issue..
Brightness doesn't seem to auto adjust. Even after a reboot. The issue seems to come during the last update - the update where now we can have video lockscreen and animated AODs.
Hope this is resolved soon.
Click to expand...
Click to collapse
I don't recall having issues on the last update, but I am on the latest CRG1 now and it's working fine on my N950F.

N1T15H said:
I can confirm am having the exact issue..
Brightness doesn't seem to auto adjust. Even after a reboot. The issue seems to come during the last update - the update where now we can have video lockscreen and animated AODs.
Hope this is resolved soon.
Click to expand...
Click to collapse
same here. Auto brightness not working after update. Hope they will release fix soon
Sent from my SM-N950F using Tapatalk

I ran the sensor tests, and it seems that more than the lux sensor is not responding ...
My heart rate sensor seems to work on a hit-or-miss basis..
SpO2 working fine though.

ghassan haddad said:
do you mean that it has a new functionality that has not been in old phones? I have the Note 4 and it works like a charm, but the note 8 auto brightness works strangely, when I'm in a room with low brightness the screen light goes so dim that I can barely see anything!
Click to expand...
Click to collapse
Try and reset your usage pattern and give it time to learn your usage. You will have to adjust the slider for your preference while its learning. I'm on the latest oreo and have no issues with it.

Reset phone to factory settings..
Issue persists!!

Hello Guys,
Yesterday I received the August 1 Update on my note 8.
After the update, I confirm the matter has been tackled
Screen rotation, auto brightness all working fine now.

N1T15H said:
Hello Guys,
Yesterday I received the August 1 Update on my note 8.
After the update, I confirm the matter has been tackled
Screen rotation, auto brightness all working fine now.
Click to expand...
Click to collapse
That's strange. My auto brightness worked fine up until the latest update. It is the August update that caused the problem for me.

Actually, providinf an update on the matter.
Some days later, situation came back to square one!
Not working:
Light sensor
Heart Rate sensor
Proximity sensor
Gyro sensor
Magnet sensor
Accelerometer
Just fingerprint sensor seems to be working fine.
I was on a trip in Malaysia and was at a Samsung store. They told me this is a very common issue and easily solved by 'software update' but when I went on to the service centre, they denied me since my phone was bought in different country. Phff

If the next OS update doesn't resolve this then I would recommend that you take your device to a Samsung Service Center

Anyone got their unresponsive device working back again ?

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

Question Cameraservice_worker partial wakelock

Hi everyone, I recently bought a S21 Ultra Exynos version. I previously installed BetterBatteryStats app to monitor for any battery drain.
There's an issue that from what I have searched, a few users are having. When my phone is on standby on a flat surface the battery drain is minimal or roughly 1-2% overnight
However, when my phone is in my pocket and when I'm walking, something is activating (possilby the proximity sensor?) the wakelock "cameraservice_worker" that causes the phone to drain battery even without touching it. I also did some testing and this process also runs in the background whenever I'm shaking my phone around instead of letting it lie still on a table top.
I have tried factory resetting and disabling multiple settings, but none seem to be able to work.
Below is a screenshot of BBS to show what I mean under partial wakelocks
This is causing my phone's battery to drain much faster than normal when in my pocket compared to when lying still on a table. Anyone here has similar issues?
These links also show a similar problem, but no one seems to be able to find a solution.
Standby battery drain when active
I've noticed since owning my phone that when I'm walking around in the day, my phone dies quicker than when I have a day where I'm more static. I've tried deleting apps and did a full reset but the problem still existed. I did some research and tried turning off loads of different settings and...
eu.community.samsung.com
Are Exynos Users Getting Bad Standby Drain?
Hi All, Is anyone getting really bad standby drain on the Exynos version? Soon as I take the phone off 100% charge within minutes of checking it again it falls down to 98% with nothing running or in the background. Last night while I slept for 8...
forum.xda-developers.com

So I have seen this as well, I think it's driven by how doze works - basically there is light and deep doze, and apps will be restricted from accessing data etc. until scheduled maintenance windows.
If you are moving, then the phone will only ever be in light doze (less restrictions, more maintenance windows, more drain). Without knowing what it does, I would hazard a guess that it's something that is blocked in 'deep doze.'
Worth giving Naptime a shot - it forces your phone to doze almost immediately, and you can turn off motion detection to stop your phone waking up.
That said I haven't tested it whilst out and about (turning off motion detection basically does light doze with all the rules of deep doze), so not sure if it will help with that particular wakelock.

Okay I'll try naptime out. Thanks!
Does your phone also have the same problem?

Yea same 'problem' - as in I think it's by design, your phone assumes it's in use so pings for more location updates etc. when moving, and I have cameraservice_worker as my biggest wakelock (haven't checked it overnight when phone is stationary, so will give that a go). I lose about 0.5% an hour without AOD overnight.
What I j haven't really looked at is 4g moving around drain vs WiFi moving around. Obviously stuck in the house atm battery is great, but phone is stationary a lot more than usual. Likely that moving around and on mobile data will make a big difference.
You'll need ADB to use naptime but it's easy enough to do (assuming you used it for BBS)

Did a quick experiment, looks like naptime doesn't stop the wakelock, even with motion detection turned off. Moving the phone I got the wakelock, leaving it still I didn't. (Turning motion detection off in naptime requires it to stay in light doze, but with the parameters of deep doze).
I'll keep it on just to see if it works but otherwise not to sure what you can do about it.
Still worth having as it's near instant doze as soon as you turn off your screen

Yeah same here.. having naptime with motion detection disabled still triggers the wakelock. It's annoying how my standby can be so great when it's on the table, but the moments it's in my pocket the standby drain is noticeably faster.
Hope it gets fixed in those newer updates

hsienjuen said:
Yeah same here.. having naptime with motion detection disabled still triggers the wakelock. It's annoying how my standby can be so great when it's on the table, but the moments it's in my pocket the standby drain is noticeably faster.
Hope it gets fixed in those newer updates
Click to expand...
Click to collapse
Have you tried turning off tap to wake or anything like that? That's the only other logical thing I can think of?

mtm1401 said:
Have you tried turning off tap to wake or anything like that? That's the only other logical thing I can think of?
Click to expand...
Click to collapse
I haven't tried turning off tap to wake yet.. will try it and see
Other options I have disabled like turning off lift to wake, pocket detection, fingerprint scanner off when display off. But still the wakelock is there

Had a quick flick through reddit, looks like it might be something to do with proximity sensor and how it uses the camera, which I guess makes some sense, although might have expected pocket detection to stop it.
I wonder if it is misbehaving or if it's a 'normal' service.
On a side note, any noticeable battery improvements from having the scanner off when screen is off? don't really use it

I noticed this last week too and have been trying to find more reports about it. It's also happening to the Note 20 Ultra, seems to be related to the variable refresh rate.
FWIW - i disabled sensors (Dev options > dev quick tiles > sensors off) the wakelocks stop. Just hoping someonee can figure out if there's a service we can disable without causing any issues.

mtm1401 said:
Had a quick flick through reddit, looks like it might be something to do with proximity sensor and how it uses the camera, which I guess makes some sense, although might have expected pocket detection to stop it.
I wonder if it is misbehaving or if it's a 'normal' service.
On a side note, any noticeable battery improvements from having the scanner off when screen is off? don't really use it
Click to expand...
Click to collapse
Hmm unfortunately turning off pocket detection also doesn't stop the wakelock from triggering. I've tried just about everything but no success.. hopefully it'll get better in the newer updates. I'm still on January update
Oh I think leaving the fingerprint scanner always on/off doesn't seem to have a noticeable impact
jigna said:
I noticed this last week too and have been trying to find more reports about it. It's also happening to the Note 20 Ultra, seems to be related to the variable refresh rate.
FWIW - i disabled sensors (Dev options > dev quick tiles > sensors off) the wakelocks stop. Just hoping someonee can figure out if there's a service we can disable without causing any issues.
Click to expand...
Click to collapse
Yeah I came across some of the note 20 ultra threads... no one can seem to find a solution there either.
Haha I tried the disabling sensors workaround.. I'll report back and see if that helps. But at the moment feels weird not having the camera work without having to re-enable sensors first

hsienjuen said:
But at the moment feels weird not having the camera work without having to re-enable sensors first
Click to expand...
Click to collapse
haha I'd be curious how you go with all the other stuff like proximity, ambient light sensors etc are off. Camera was my only test with it, it failed, so turned sensors straight back on.

So I was having a think, if it is a bug rather than normal operation, wondered if it could be the OIS moving around and triggering something when the device is moving? Will do adb permissions for GSAM on my S10 and see if the same thing happens

I installed GSAM on my partner's S20+ and no sign of this wakelock anywhere. Definitely seems limited to the later models Note20 ultra and S21 ultra. Not even sure if the S21 or S21+ are experiencing it.

hsienjuen said:
Hmm unfortunately turning off pocket detection also doesn't stop the wakelock from triggering. I've tried just about everything but no success.. hopefully it'll get better in the newer updates. I'm still on January update
Oh I think leaving the fingerprint scanner always on/off doesn't seem to have a noticeable impact
Yeah I came across some of the note 20 ultra threads... no one can seem to find a solution there either.
Haha I tried the disabling sensors workaround.. I'll report back and see if that helps. But at the moment feels weird not having the camera work without having to re-enable sensors first
Click to expand...
Click to collapse
Have you raised it with the support team on samsung members? going to submit a bug report tonight after using the phone all day so they can see some usage.
It's the sort of thing that average users wouldn't be able to report because they just wouldn't be aware

Just when I was thinking I'm one of the lucky ones, I see this wakelock under BBS...oh rats! I don't think samsung members would be of much help and if I do post BBS screenshots there, I'm sure there will be a load of crackpots saying that this app could be causing this issue yadi yadi yaa...

mtm1401 said:
Have you raised it with the support team on samsung members? going to submit a bug report tonight after using the phone all day so they can see some usage.
It's the sort of thing that average users wouldn't be able to report because they just wouldn't be aware
Click to expand...
Click to collapse
No I haven't.. I'm wasn't really sure where to report this because it doesn't seem like a widespread issue.
But hmm you're right maybe it's because the average user isn't even aware that their phones are draining battery more in their pockets, and probably even less aware that this wakelock even exists

hsienjuen said:
No I haven't.. I'm wasn't really sure where to report this because it doesn't seem like a widespread issue.
But hmm you're right maybe it's because the average user isn't even aware that their phones are draining battery more in their pockets, and probably even less aware that this wakelock even exists
Click to expand...
Click to collapse
Yea exactly, I think you'd need to be using ADB commands (BBS, GSAM etc.) to even see that level of detail, and I reckon 95% of users don't know what they are
FYI - no such wakelock on my S10 running OneUI 3.1

Comrades, this issue a grave issue and will surely wreak havoc on the battery...This issue has to go global. It wasn't present on AUB6 and I have every mind to downgrade to AUB6 until this issue is fixed in the next update

amirage said:
Comrades, this issue a grave issue and will surely wreak havoc on the battery...This issue has to go global. It wasn't present on AUB6 and I have every mind to downgrade to AUB6 until this issue is fixed in the next update
Click to expand...
Click to collapse
Pretty sure I had it in aub6 tbh

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.