Database Develop

ghosting

i haven't seen any complaints about ghosting so it may just be my phone but i have it really bad.
it's very visible when i scroll through my home screens because i have a near black background and use the red and white data widget.
it also makes text and such look horrid when i scroll through menus or web pages

deyna said:
i haven't seen any complaints about ghosting so it may just be my phone but i have it really bad.
it's very visible when i scroll through my home screens because i have a near black background and use the red and white data widget.
it also makes text and such look horrid when i scroll through menus or web pages
Click to expand...
Click to collapse
You probably have the brightness set extremely high or extremely low.
Whenever CM7 comes out for the D3, you can try adjusting render settings to improve the overall gamma of the screen. I'm guessing you're just more sensitive than most to a high-persistence screen, unless you have found a way to monkey with your refresh rate

rynosaur said:
You probably have the brightness set extremely high or extremely low.
Whenever CM7 comes out for the D3, you can try adjusting render settings to improve the overall gamma of the screen. I'm guessing you're just more sensitive than most to a high-persistence screen, unless you have found a way to monkey with your refresh rate
Click to expand...
Click to collapse
i've got a friend who has the same phone so i'll see if his is the same.
i haven't messed with the screen settings at all and have it set to auto brightness.
my last phone was the Nexus S with it's s-amoled screen. does this screen have a lower refresh rate then it did?
i know normal monitors have about a 60hz refresh rate but i know nothing about smart phone screens.

deyna said:
i've got a friend who has the same phone so i'll see if his is the same.
i haven't messed with the screen settings at all and have it set to auto brightness.
my last phone was the Nexus S with it's s-amoled screen. does this screen have a lower refresh rate then it did?
i know normal monitors have about a 60hz refresh rate but i know nothing about smart phone screens.
Click to expand...
Click to collapse
You've got me on the specs. I know desktop LCDs/LEDs are capable of higher refresh rates, but those aren't necessary for regular applications (read: non-bluray, non/gaming). Not sure where a smartphone like the D3 would land in the gamut between 29mhz and 120mhz.

deyna said:
i haven't seen any complaints about ghosting so it may just be my phone but i have it really bad.
it's very visible when i scroll through my home screens because i have a near black background and use the red and white data widget.
it also makes text and such look horrid when i scroll through menus or web pages
Click to expand...
Click to collapse
I've got a little...not exactly ghosting, but similar...on mine. It seems to me that the display controller for the pentile screen isn't outputting all of the color channels at the same time, so i end up with a red fringe or bloom around objects scrolling across the screen. Hopefully, a firmware update for the chip can fine-tune things.

rynosaur said:
You've got me on the specs. I know desktop LCDs/LEDs are capable of higher refresh rates, but those aren't necessary for regular applications (read: non-bluray, non/gaming). Not sure where a smartphone like the D3 would land in the gamut between 29mhz and 120mhz.
Click to expand...
Click to collapse
hmh i wish.
29mhz would be 29,000,000 refreshes per second XD
on computer monitors 60hz has been the norm for a long time. all my old CRTs use it. the newer 3d tvs and such generally need a 120hz refresh rate at the least.
even my dell inspiron 1420 has an lcd with a 60hz refresh rate and it can play bluray.
i remember there being one phone not too long ago that was limited to 30hz and most didn't like that one bit.

Xenoproctologist said:
I've got a little...not exactly ghosting, but similar...on mine. It seems to me that the display controller for the pentile screen isn't outputting all of the color channels at the same time, so i end up with a red fringe or bloom around objects scrolling across the screen. Hopefully, a firmware update for the chip can fine-tune things.
Click to expand...
Click to collapse
you may be right. i'll check another phone or two and if they have the same problems i'll just hope that an update or rom can fix it.

FYI: this has not that much to do with refresh rate, but more with response time. Response times are displayed in milliseconds most of the time.
For example, my uber-gaming-tft-display has a 2 milliseconds response time, which is very low and has almost no ghosting.
So, the question is: what is the response time of the qHD display in the droid 3.
I noticed the ghosting is way more visible on black backgrounds than on white. Good thing motorola changed the background in the android menu's from the default black to white.

I have noticed the ghosting too but have to admit that I actually like it. Especially while playing Emulators like FPSE and Gameboid it brings back the real PSP feeling. I know, its a weird oppinion.

rvschuil said:
FYI: this has not that much to do with refresh rate, but more with response time. Response times are displayed in milliseconds most of the time.
For example, my uber-gaming-tft-display has a 2 milliseconds response time, which is very low and has almost no ghosting.
So, the question is: what is the response time of the qHD display in the droid 3.
I noticed the ghosting is way more visible on black backgrounds than on white. Good thing motorola changed the background in the android menu's from the default black to white.
Click to expand...
Click to collapse
It's definitely got a slower rise-time than fall-time. You can see it on monochromatic icons when scrolling the app drawer in a launcher that uses a black background -- the leading edge is a blurry mess, while the trailing edge is fairly crisp. I'm guessing that the display controller simply isn't using any kind of overdriving to improve response time.
Also, to clarify my previous characterization of the blurring, it appears not so much that the red channel specifically is updating faster, as it is that the white channel is updating slower than all of the RGB channels.

Refresh rate has nothing to do with ghosting. Nearly every TV is actually 60, but they are falsely advertised at 600(plasmas) or use frame interpolation to achieve refresh rates above 60hz(LCD.) The only exceptions are 3D TVs. They actually refresh at 120 hz in 3D mode. Each eye sees 60hz. If they stayed at 60hz, each eye would see 30hz, and there would be noticeable flickering.
What effects ghosting is response time-the amount of time it takes a pixel to respond to a change in state. In layman's terms, how quickly it can go from one color to the next.
Plasmas and CRTs have near instant response times-it takes just nanoseconds for a pixel to change(actually, green phosphors take about 1 millisecond to change, blue and red phosphors change in nanoseconds). Nonetheless, plasmas and CRTs simply don't ghost(which is one reason why I prefer Plasma TVs). Part of this is because the pixels produce their own light. There is no backlight like an LCD.
But on LCDs, it takes the pixels many milliseconds to change. Though they are advertised between 2-6ms, the true response time of an LCD is usually at least 20 milliseconds. The Retina Display and qHD displays ghost because they have response times of 25-30ms. I can't recall why right now, but when you pack in a ton of pixels on a small screen, the response time is extremely high.
The refresh rate on phone screens is 60hz, which is actually why most are capped at 60fps, or you would probably see screen tearing.

GoogleAndroid said:
Refresh rate has nothing to do with ghosting. Nearly every TV is actually 60, but they are falsely advertised at 600(plasmas) or use frame interpolation to achieve refresh rates above 60hz(LCD.) The only exceptions are 3D TVs. They actually refresh at 120 hz in 3D mode. Each eye sees 60hz. If they stayed at 60hz, each eye would see 30hz, and there would be noticeable flickering.
What effects ghosting is response time-the amount of time it takes a pixel to respond to a change in state. In layman's terms, how quickly it can go from one color to the next.
Plasmas and CRTs have near instant response times-it takes just nanoseconds for a pixel to change(actually, green phosphors take about 1 millisecond to change, blue and red phosphors change in nanoseconds). Nonetheless, plasmas and CRTs simply don't ghost(which is one reason why I prefer Plasma TVs). Part of this is because the pixels produce their own light. There is no backlight like an LCD.
But on LCDs, it takes the pixels many milliseconds to change. Though they are advertised between 2-6ms, the true response time of an LCD is usually at least 20 milliseconds. The Retina Display and qHD displays ghost because they have response times of 25-30ms. I can't recall why right now, but when you pack in a ton of pixels on a small screen, the response time is extremely high.
The refresh rate on phone screens is 60hz, which is actually why most are capped at 60fps, or you would probably see screen tearing.
Click to expand...
Click to collapse
very informative, thank you! i knew what response times are but for some reason didn't draw the line between that knowledge and ghosting.
that would also explain why it's so noticeable to me after using the Nexus S for 9 months. hopefully (though unlikely) a new phone will come out here soon with a keyboard and high res screen with good response time.

Screen changing brightness when not on Auto and no power saving...

I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.

dbozam said:
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
Click to expand...
Click to collapse
I don't have the flickering when not on auto and lowest setting.
However some apps can dimm the screen while loading.
On the TF700 the stock browser did that when loading a page but on the TF701 the brightness doesn't do that.

You have an ambient light sensor built into the device. It adjusts the brightness based on the lighting in your environment. It can't be turned off either.
Sent from my Transformer Infinity TF701T using Tapatalk HD

xRevilatioNx said:
You have an ambient light sensor built into the device. It adjusts the brightness based on the lighting in your environment. It can't be turned off either.
Click to expand...
Click to collapse
It can't be turned off? So when you turn on automatic brightness it just changes the brightness more drastically? This doesn't sound right.
Based on the other poster's response, I think I need to return this unit. The screen dimming/brightening happens to often and randomly to be part of my apps and I even noticed, in some apps, that just touching the screen causes a brightness change.
Even if this is by design, it is far too distracting.

dbozam said:
It can't be turned off? So when you turn on automatic brightness it just changes the brightness more drastically? This doesn't sound right.
Based on the other poster's response, I think I need to return this unit. The screen dimming/brightening happens to often and randomly to be part of my apps and I even noticed, in some apps, that just touching the screen causes a brightness change.
Even if this is by design, it is far too distracting.
Click to expand...
Click to collapse
Read it and weep my friend. Proof is in the pudding..
Sent from my Transformer Infinity TF701T using Tapatalk HD

dbozam said:
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
Click to expand...
Click to collapse
My 701 is doing this as well. Turned off auto brightness, turned off power saver, rebooted. When it comes back up the device acts like auto brightness is on, with screen brightness fluctuaating randomly. Turning power saver on and off again seems to solve it, but that behavior is very annoying - it's why I turn auto brightness off in the first place.
US SKU running 4.3 installed via ota, no root or unlock or anything - straight stock. Its also my second device, my original had a bad cable and wouldn't charge. Serial number ends in 072259.
Sent from my K00C using Tapatalk 4

Aaroneious said:
My 701 is doing this as well. Turned off auto brightness, turned off power saver, rebooted. When it comes back up the device acts like auto brightness is on, with screen brightness fluctuaating randomly. Turning power saver on and off again seems to solve it, but that behavior is very annoying - it's why I turn auto brightness off in the first place.
US SKU running 4.3 installed via ota, no root or unlock or anything - straight stock. Its also my second device, my original had a bad cable and wouldn't charge. Serial number ends in 072259.
Sent from my K00C using Tapatalk 4
Click to expand...
Click to collapse
I also tried turning power saver mode on and off and for me it seemed to improve the situation but not eliminate it. I am going to return the tablet and wait for the nexus 10.

Ugh, mine has been doing this, too. Can't believe there isn't a setting somewhere...

Mine is doing the same thing... glad that it's not just me, but this flickering is very annoying

Driving me nuts
I'm having the same problem and it's driving me nuts!
I'm quite convinced it's a software "feature" but currently there seems to be no way to turn it off?
It's one of those "Adjust brightness of the screen based on content" or "Changing LCD refresh rate and colors for power saving" but sadly it does it the wrong way around (This has been going on for a while now, manufacturers don't really get it). When there is a lot of bright content the brightness will rise and when there is mostly a dark screen it will fall.
Of course, this should happen exactly the other way around. When there is a lot of bright/white on my screen it should lower and when there is mostly black it should become brighter thus giving you more contrast but keeping the overall lux that comes off your screen the same...... My Intel graphics notebook does this too and it's very irritating. There they do it by manipulating the LCD screen and lowering the refresh rate and other tricks to save battery. First thing I turned off.
However way it goes though, you should be able to turn it off!

Quindor said:
I'm having the same problem and it's driving me nuts!
I'm quite convinced it's a software "feature" but currently there seems to be no way to turn it off?
It's one of those "Adjust brightness of the screen based on content" or "Changing LCD refresh rate and colors for power saving" but sadly it does it the wrong way around (This has been going on for a while now, manufacturers don't really get it). When there is a lot of bright content the brightness will rise and when there is mostly a dark screen it will fall.
Of course, this should happen exactly the other way around. When there is a lot of bright/white on my screen it should lower and when there is mostly black it should become brighter thus giving you more contrast but keeping the overall lux that comes off your screen the same...... My Intel graphics notebook does this too and it's very irritating. There they do it by manipulating the LCD screen and lowering the refresh rate and other tricks to save battery. First thing I turned off.
However way it goes though, you should be able to turn it off!
Click to expand...
Click to collapse
I'm having the same issue. I think it's the smart dimmer option Asus have used before but they forgot to include it in the Asus customised options. I'll have a dig through the ROM to see where it is stored.

I'm having this problem as well.
I have my brightness set to about 80%, Auto-Brightness Off, Power Save Off.
It is very annoying when reading magazines that have a lot of white background. My screen will be stable for minutes then, often on a touch, will change the screen brightness, seemingly by 5-20%.
I was just getting ready to return it, and thought I would check here to see of anyone else has this problem. Has any actually called Asus with this complaint? I would be interested to know if they see this as a hardware defect, software bug, or working as designed.
PS - I just placed a technical support request about this on the Asus Website. Here is my problem description:
Even with automatic brightness & power saving turned off, the brightness of the screen will change over time, often seemingly in response to a touch. (Reading Mode is Off as well.)
The period between changes can vary from several minutes to 30 seconds. It happens both while docked and undocked. It happens with apps and just at the launcher.
The amount of brightness change is 5-20% and it will often seem to step through some values before it stops at a particular one.
Given how fantastic looking the screen is, this unwanted fluctuation is particularly annoying.
I also own a TF201 and have not experienced this problem on that product.
Click to expand...
Click to collapse

sschlosnagle said:
I'm having this problem as well.
I have my brightness set to about 80%, Auto-Brightness Off, Power Save Off.
It is very annoying when reading magazines that have a lot of white background. My screen will be stable for minutes then, often on a touch, will change the screen brightness, seemingly by 5-20%.
I was just getting ready to return it, and thought I would check here to see of anyone else has this problem. Has any actually called Asus with this complaint? I would be interested to know if they see this as a hardware defect, software bug, or working as designed.
PS - I just placed a technical support request about this on the Asus Website. Here is my problem description:
Click to expand...
Click to collapse
I have this issue too but not a real biggie as the connection problems between dock and tablet.

Same problem!
dbozam said:
I just got my Asus tf701t and, while first using it, the home and back buttons did not work in portrait mode and the screen would change brightness at varying time intervals (usually a few seconds) when the brightness was set very low. an update to 4.3 cured the back and home button issue but the screen still can't stay at one brightness level when I set it to very dim. It's not changing dramatically, more like a few percent, but enough to be distracting.
The odd part is that the dimming/brightening issue almost seems application dependent. It occurs far more often in the home screen or skout but almost never when playing shadowgun dead zone or when using naked browser.
Does anyone else have similar issues?
The only posts about flickering on other people's tf701t seem to be related to power saving and I need to know if this needs to be exchanged or if this is a common problem.
Click to expand...
Click to collapse
Thank you very much for creating this topic, because I was worried for my tablet too!
---------- Post added at 11:55 AM ---------- Previous post was at 11:52 AM ----------
Snah001 said:
I have this issue too but not a real biggie as the connection problems between dock and tablet.
Click to expand...
Click to collapse
I heared a lot of people say I about this, but happily I seem to don't have it or I don't detect it. What is this dock problem about?

I suspect this is the same "smart dimming" feature that the 700 had.

improvius said:
I suspect this is the same "smart dimming" feature that the 700 had.
Click to expand...
Click to collapse
Yep me too and as soon as I root I'm going to see if the same fix will turn it off

There seems to be no way to disable this. Some believe it's the light sensor, but I've taped over mine with black electrical tape and tested and I don't see any difference in the behavior. Check our my Youtube video if you are a user who doesn't see the issue (look for threads in this same XDA forum).
I've finally been able to get someone at Asus to look into this and it's been sent to TW for review. I haven't heard anything back yet. I strongly recommend that other people who are annoyed by this (I find it tremendously distracting) to search on "asus escalation" which will bring up a special mailbox. Here is the link (although I do not know if the link will work for you). This should get looked at by someone with at least some ability beyond reading a script. If enough people do this, I think that they will fix it. Since you can temporarily override it by toggling smart saver on/off, it has to be fixable by software.
http://www.service.asus.com/#!escalation-mailbox/c1scx

derekk1 said:
There seems to be no way to disable this. Some believe it's the light sensor, but I've taped over mine with black electrical tape and tested and I don't see any difference in the behavior. Check our my Youtube video if you are a user who doesn't see the issue (look for threads in this same XDA forum).
I've finally been able to get someone at Asus to look into this and it's been sent to TW for review. I haven't heard anything back yet. I strongly recommend that other people who are annoyed by this (I find it tremendously distracting) to search on "asus escalation" which will bring up a special mailbox. Here is the link (although I do not know if the link will work for you). This should get looked at by someone with at least some ability beyond reading a script. If enough people do this, I think that they will fix it. Since you can temporarily override it by toggling smart saver on/off, it has to be fixable by software.
http://www.service.asus.com/#!escalation-mailbox/c1scx
Click to expand...
Click to collapse
I returned my tf701, waited for cyber Monday, and bought the Samsung note 2014 since the nexus 10 2 is so elusive. I put in an escalation request anyway and included a link to this thread in my complaint.

improvius said:
I suspect this is the same "smart dimming" feature that the 700 had.
Click to expand...
Click to collapse
I also saw this issue on my TF701. This seems a "feature" of Tegra SoC

CameraLightSensor

Anyone having CameraLightSensor battery drain?
Edit: it is 4g Exynos model, latest firmware

I just checked and I do not see it on mine at all. T-mobile version.

No battery drain on mine either.

Possibly disable the face unlock, its going to save alot of battery for you.

coolmaster121 said:
Possibly disable the face unlock, its going to save alot of battery for you.
Click to expand...
Click to collapse
Don't have it enabled, it seems it is auto brightness

Off topic: could you tell me what kind of SoT you're getting? There are no replies yet in the official thread and I'm interested in the Exynos version.

Pufanu said:
Off topic: could you tell me what kind of SoT you're getting? There are no replies yet in the official thread and I'm interested in the Exynos version.
Click to expand...
Click to collapse
4 hours sot max

dzontra83 said:
4 hours sot max
Click to expand...
Click to collapse
Ouch! That's on 120hz, I assume. I was half-expecting that. Thanks.

Pufanu said:
Ouch! That's on 120hz, I assume. I was half-expecting that. Thanks.
Click to expand...
Click to collapse
Yup, will report tomorrow with auto brightness turned off, because today CameraLightSensor was running in the background for almost 9 hours.

dzontra83 said:
Yup, will report tomorrow with auto brightness turned off, because today CameraLightSensor was running in the background for almost 9 hours.
Click to expand...
Click to collapse
That's definitely not right. Hope you get it sorted out.

Pufanu said:
That's definitely not right. Hope you get it sorted out.
Click to expand...
Click to collapse
I know, don't know where to start, so first step is to disable auto brightness....

dzontra83 said:
I know, don't know where to start, so first step is to disable auto brightness....
Click to expand...
Click to collapse
It definitely seems to be auto brightness, I turned it off, charged the phone to 100%, and today CameraLightSensor it not showing in the battery usage at all.

dzontra83 said:
Yup, will report tomorrow with auto brightness turned off, because today CameraLightSensor was running in the background for almost 9 hours.
Click to expand...
Click to collapse
Same thing on my T-Mobile model - 3.1% over 9 hours. I have not checked my unlocked model, as its still in the box.
Have you noticed the 'ring" of pixels around the camera changing color to black when using the phone? I notice it mostly when browsing the web, or on a phone call.
Hard to describe what it is, but a "ring" about 5 px wide turns black or dark grey around the front camera just for a second. Is that the light sensor thing?
---------- Post added at 12:37 PM ---------- Previous post was at 12:27 PM ----------
Interesting - I read an article about samsung using the camera instead of a sensor in new phones to detect the ambient brightness. The phone will take a picture, adjust the brightness, then the picture is permanently deleted. I guess that flash of the ring around the camera is the phone doing that to see what the light levels are in the room.
I turned off auto brightness and that ring flashing has stopped.

fncd said:
Same thing on my T-Mobile model - 3.1% over 9 hours. I have not checked my unlocked model, as its still in the box.
Have you noticed the 'ring" of pixels around the camera changing color to black when using the phone? I notice it mostly when browsing the web, or on a phone call.
Hard to describe what it is, but a "ring" about 5 px wide turns black or dark grey around the front camera just for a second. Is that the light sensor thing?
---------- Post added at 12:37 PM ---------- Previous post was at 12:27 PM ----------
Interesting - I read an article about samsung using the camera instead of a sensor in new phones to detect the ambient brightness. The phone will take a picture, adjust the brightness, then the picture is permanently deleted. I guess that flash of the ring around the camera is the phone doing that to see what the light levels are in the room.
I turned off auto brightness and that ring flashing has stopped.
Click to expand...
Click to collapse
Definitely when you turn off auto brightness, the CameraLightSensor is not working in the background. But it must be a software glitch, it should be active only when the screen is on, it shouldn't be active while the device is in sleep.

dzontra83 said:
Definitely when you turn off auto brightness, the CameraLightSensor is not working in the background. But it must be a software glitch, it should be active only when the screen is on, it shouldn't be active while the device is in sleep.
Click to expand...
Click to collapse
I spoke too soon. Even with auto brightness turned off, the flashing ring of pixels around the camera still persist. ?
Edit: Sent in an error report along with two of them about the screen sensitivity issues.

Just checked my S20 FE 5G variant and it too has the CameraLightSensor draining at 2.8% for a total background usage of 8hrs and 28 minutes
(Snapdragon)

dzontra83 said:
It definitely seems to be auto brightness, I turned it off, charged the phone to 100%, and today CameraLightSensor it not showing in the battery usage at all.
Click to expand...
Click to collapse
How many hours SOT after auto-brightness is turned off please?
My country will only have the 4G Exynos type too.

fncd said:
I spoke too soon. Even with auto brightness turned off, the flashing ring of pixels around the camera still persist.
Edit: Sent in an error report along with two of them about the screen sensitivity issues.
Click to expand...
Click to collapse
Flashing ring of pixels around the camera???

ChildishSmef said:
Flashing ring of pixels around the camera???
Click to expand...
Click to collapse
Yes - Whether on the home screen, in a call, or in an app, there is a perfect "ring" (if you will) about 3-5 pixels wide around the camera that goes black for a split second or so and then changes back to the color of whatever it was displaying (think background color of a chrome tab, phone call, etc). It's impossible to catch as it happens so quickly. It's almost as if a perfect circle is turning off and then back on. And it has happened on both of my S20 FE, with or without adaptive brightness turned on.
I don't think it's something that screen recorder will even capture since that doesn't show the camera cutout, but I'll try!
EDIT: So I made a screen recording - and I think it was just the troubleshooting I needed to figure out what the problem is (was). . . When recording, the screen never shuts off, so there is no need for Smart Stay to activate (the camera checks to see if you're looking @ the phone to stay on). . . As soon as I stopped screen recording, that ring of pixels turned off and back on as it has been doing. I turned off Smart Stay, and it hasn't happened in the past 10 minutes or so. . .
I wonder if those that are seeing the high CameraLightSensor usage have Smart Stay turned on? It's not on by default - you have to look for it in settings.

fncd said:
Yes - Whether on the home screen, in a call, or in an app, there is a perfect "ring" (if you will) about 3-5 pixels wide around the camera that goes black for a split second or so and then changes back to the color of whatever it was displaying (think background color of a chrome tab, phone call, etc). It's impossible to catch as it happens so quickly. It's almost as if a perfect circle is turning off and then back on. And it has happened on both of my S20 FE, with or without adaptive brightness turned on.
I don't think it's something that screen recorder will even capture since that doesn't show the camera cutout, but I'll try!
EDIT: So I made a screen recording - and I think it was just the troubleshooting I needed to figure out what the problem is (was). . . When recording, the screen never shuts off, so there is no need for Smart Stay to activate (the camera checks to see if you're looking @ the phone to stay on). . . As soon as I stopped screen recording, that ring of pixels turned off and back on as it has been doing. I turned off Smart Stay, and it hasn't happened in the past 10 minutes or so. . .
I wonder if those that are seeing the high CameraLightSensor usage have Smart Stay turned on? It's not on by default - you have to look for it in settings.
Click to expand...
Click to collapse
I have smart stay off, accidentall touch protection off, face unlock off, and from today adaptive brightness off, and my CameraLightSensor is not working in the background when I turned it off. Auto brightness was definitely the culprit for me.

Question Screen dimming randomly

Hello,
Recently got this phone and very happy with it. Only issue I have found is that the screen occasionally dims randomly, not by a lot, but noticeable when it happens.
Adaptive brightness is off. System mode is set to dynamic.
Is dynamic system mode the issue? If so which is a good adaptive battery setting which won't affect the screen brightness.
Thanks in advance

I assume its due to the changes in refresh rate. Try setting the refresh rate to a single value (120 90 or 60) and i think you wont see the transition.

Same issue and I have adaptive brightness on. You will open an app and suddenly brightness will turn all the way down. Definitely a bug.

hirshr said:
I assume its due to the changes in refresh rate. Try setting the refresh rate to a single value (120 90 or 60) and i think you wont see the transition.
Click to expand...
Click to collapse
Thanks for the suggestion. I've tried this at 90hz, for reasonable battery, but it still does it.

Same here! Locked at 90hz, so that's not the problem.

I'm having the same issue. Adaptive brightness off, fixed refresh rate. I've only noticed it when I'm outside in bright light.

same problem.
have zenfone 7 rooted. locked to 90hz. adaptive brightness switched off.
anyone found a solution or cause?
I've noticed it happens when i tilt the phone.
and also when i have an app overlaid over main screen. like YouTube vanced minimised etc.
i think phone somehow might be switching brightness between the small app at the front and the main app on the back and doing it back and forth.

Find X5 pro, Screen stuck 120hz

I turn on show screen refresh rate in Developer mode.
Then it only show 120 hz in almost state, almost app, while am not touch it, and in stactic display.
Only drop to 60hz in game or full screen youtube.
Never down to 1hz.
How to fix that ?