Related
Hi everyone,
Got my Pixel 4 XL on the 23rd and been playing around with it since then. I am now settling into a rhythm and noticed a very concerning glitch with the display when the phone is in dark mode. Basically, when the phone is in dark mode I noticed that typing in Gboard or tapping anywhere on screen in apps that are not pure black (such as Messages, Phone, etc.) will shift the screen colour from blueish-black to greenish-black. This happens every time, even after rebooting the device. There is no visible colour shifting in apps that use pure-black such as Settings (however, parts of Settings like the search bar that are the "gray" dark colour also shift). Once I noticed this happening now I cannot stop noticing it everywhere. I am looking to find out from you whether you are seeing the same thing or whether this may be a device problem. Note that the same issue shows up in dark apps even if dark mode is not enabled. It also has nothing to do with Ambient EQ, Automatic Brightness, or anything else of similar nature. Occasionally the problem stops, but if I pull up Gboard and start typing (say to search in the Recent section of the phone app) the problem immediately comes back.
I am looking for serious feedback here from those willing to look closely. This does seem like a software glitch to me, rather than hardware, especially since I am not seeing this behaviour with any other colours and so far it definitely has something to do with physical interaction with the screen when tapping on it. As I said, it also seems to be universally triggered by Gboard when in apps running in dark mode.
I appreciate any feedback you can provide.
Edit: Looks like what I'm observing is related to the switching colour profiles when the display is going back and forth between 60Hz and 90Hz. Turning off the smooth display function or forcing the display into permanent 90Hz mode appears to stop the problem from happening. Google really messed this one up. I hope their 90Hz fix they promised clears up this issue. Very annoyed ?
Thanks,
Dejan
Btw, since you are using forced 90hz display make sure to have always on display on. If you don't your greys will be purple and lower brightness as well as lots of black smear/crush. I don't know how turning on always on display solved that issue (someone posted this fix in another thread). So it indeed doesn't seem to be hardware but software related and hopefully they will tune this over time.
zetsumeikuro said:
Btw, since you are using forced 90hz display make sure to have always on display on. If you don't your greys will be purple and lower brightness as well as lots of black smear/crush. I don't know how turning on always on display solved that issue (someone posted this fix in another thread). So it indeed doesn't seem to be hardware but software related and hopefully they will tune this over time.
Click to expand...
Click to collapse
Yeah, I saw that thread. Some funky stuff going on with display calibration and 90Hz. Since I know that the HW is not defective and the SW is the source of the issue I am less bothered now (I cannot stand exchanging HW). I haven't specifically observed that effect on my phone and while I did try forcing 90Hz, I actually went back to the stock setting since I noticed that forced 90Hz further sucked down the battery that already is not particularly stellar despite this being the XL version. I presume Google will refine the 90Hz calibration and function over the next few months. I will say though that I am a bit confused why they need to have different calibration at different refresh rates. I calibrate all of my desktop monitors and despite the fact that I have a 100Hz monitor I never have to change calibration with refresh rate. Maybe an OLED thing :shrug:
dhorgas said:
Hi everyone,
Got my Pixel 4 XL on the 23rd and been playing around with it since then. I am now settling into a rhythm and noticed a very concerning glitch with the display when the phone is in dark mode. Basically, when the phone is in dark mode I noticed that typing in Gboard or tapping anywhere on screen in apps that are not pure black (such as Messages, Phone, etc.) will shift the screen colour from blueish-black to greenish-black. This happens every time, even after rebooting the device. There is no visible colour shifting in apps that use pure-black such as Settings (however, parts of Settings like the search bar that are the "gray" dark colour also shift). Once I noticed this happening now I cannot stop noticing it everywhere. I am looking to find out from you whether you are seeing the same thing or whether this may be a device problem. Note that the same issue shows up in dark apps even if dark mode is not enabled. It also has nothing to do with Ambient EQ, Automatic Brightness, or anything else of similar nature. Occasionally the problem stops, but if I pull up Gboard and start typing (say to search in the Recent section of the phone app) the problem immediately comes back.
I am looking for serious feedback here from those willing to look closely. This does seem like a software glitch to me, rather than hardware, especially since I am not seeing this behaviour with any other colours and so far it definitely has something to do with physical interaction with the screen when tapping on it. As I said, it also seems to be universally triggered by Gboard when in apps running in dark mode.
I appreciate any feedback you can provide.
Edit: Looks like what I'm observing is related to the switching colour profiles when the display is going back and forth between 60Hz and 90Hz. Turning off the smooth display function or forcing the display into permanent 90Hz mode appears to stop the problem from happening. Google really messed this one up. I hope their 90Hz fix they promised clears up this issue. Very annoyed ?
Thanks,
Dejan
Click to expand...
Click to collapse
I just noticed this on my pixel 4 xl tonight. But It only happens when the proximity sensor is triggered. Ex: like after making a phone call except it made everything on the screen seem over saturated on the screen and well as the same color shift you had stated. It seems to go away once I lock the device and unlock it again. It did it with smooth display on and off as well as force 90hz on and off.
There are a couple threads discussing this. Here's one of them:
https://forum.xda-developers.com/pixel-4-xl/how-to/smooth-display-colour-issues-t4000087
And another:
https://forum.xda-developers.com/showthread.php?t=3998907
Sent from my Pixel 4 XL using Tapatalk
I noticed at bedtime that this phone's panel didn't get those deep blacks we come to expect from samsung panels, i remeber in 2012 i had the same issue with my galaxy S2, i can see the black being lit like it was an LCD panel.
black image 0% brightness at 60hz = i can clearly see the display back-light.
black image 0% brightness at 120hz = it behaves like an amoled panel should, i can't see a thing.
The phone is running the latest software, oneui 3.1 + May patch.
Is this a known software bug? I think i'll return this phone because of this.
There is no backlight in a AMOLED display.
Firmware or hardware issue.
Or your eyes.
blackhawk said:
There is no backlight in a AMOLED display.
Firmware or hardware issue.
Or your eyes.
Click to expand...
Click to collapse
Definitely not my eyes unfortunately.
Try clearing the system cache
Try a hard reboot
Doesn't it have variable display frequency depending on what you're viewing ie static picture vs scrolling?
Could that be coming into play?
A glitch. You can't clear the graphic driver data but maybe the apk that controls the variable rate if separate from that.
You haven't done any major firmware upgrades, right?
I haven't play with the higher refresh rate displays, pretty much love my 10+/Pie.
Otherwise...
If you're within your return window, do so.
blackhawk said:
Try clearing the system cache
Try a hard reboot
Doesn't it have variable display frequency depending on what you're viewing ie static picture vs scrolling?
Could that be coming into play?
A glitch. You can't clear the graphic driver data but maybe the apk that controls the variable rate if separate from that.
You haven't done any major firmware upgrades, right?
I haven't play with the higher refresh rate displays, pretty much love my 10+/Pie.
Otherwise...
If you're within your return window, do so.
Click to expand...
Click to collapse
phone came already running latest software, i got it 3 days ago.
either you bought some cheap a$$ black market fakes or its some software fu*k up in the brightness department.
sivasankarpnair1998 said:
either you bought some cheap a$$ black market fakes or its some software fu*k up in the brightness department.
Click to expand...
Click to collapse
big retail store.
maybe some calibration issue? however someone tested on his device and had pitch black on both refresh rate so i think thats a faulty panel.
williamtavares said:
big retail store.
maybe some calibration issue? however someone tested on his device and had pitch black on both refresh rate so i think thats a faulty panel.
Click to expand...
Click to collapse
I've not personally used an S20 FE , but am a samsung user myself.
it should be pitch black.
are you sure the picture was absolute black and not slightly gray ?
if it was an absolute black image , the screen should not emit no light at all irrespective of what brightness you put it in , since it is black.
sivasankarpnair1998 said:
I've not personally used an S20 FE , but am a samsung user myself.
it should be pitch black.
are you sure the picture was absolute black and not slightly gray ?
if it was an absolute black image , the screen should not emit no light at all irrespective of what brightness you put it in , since it is black.
Click to expand...
Click to collapse
yeah i used different sources for this, including some apps.
i had many amoled display phones before, this was my first samsung phone since the s2 i had in 2012, bummer.
williamtavares said:
yeah i used different sources for this, including some apps.
i had many amoled display phones before, this was my first samsung phone since the s2 i had in 2012, bummer.
Click to expand...
Click to collapse
You're within your return window. Do it tomorrow. It should be black as night.
I have the same issue. 120hz is black but 60hz is not.
sonof said:
I have the same issue. 120hz is black but 60hz is not.
Click to expand...
Click to collapse
This affects all units, but some users doesn't even know what we are talking about.
Tested in 3 different units, same results, all returned.
williamtavares said:
This affects all units, but some users doesn't even know what we are talking about.
Tested in 3 different models, same results.
Click to expand...
Click to collapse
Thanks. That's what I was thinking about. No need to send for replacement since the same is with all units. Not a big problem for me since I like to use 120hz even if it drains more battery.
I got the same issue. It seems to be a software issue, because it only happens in always on display. If I open a black image the screen comes completely black. Weird bug.
There is a setting for variable current verses pulse modulation for brightness, I can't recall what they call it. Try using the variable current setting.
ivan290 said:
I got the same issue. It seems to be a software issue, because it only happens in always on display. If I open a black image the screen comes completely black. Weird bug.
Click to expand...
Click to collapse
Try to turn off Auto brightness in AOD settings, that fixed it for me.
froki said:
Try to turn off Auto brightness in AOD settings, that fixed it for me.
Click to expand...
Click to collapse
I have auto brightness in AOD disabled (and the normal auto brightness too) but the bug is still there. I configured it to max brightness so I notice it a little less
I am using the samsung galaxy A 52s 5g.
It has the exact same issue, the AOD and lockscreen behave like a LCD panel with a yellowish tint when the refresh rate is set on 60Hz.
Though everything else is fine, other screens and apps.
If set at 120Hz then AOD and lockscreen behave normally.
I don't what this is.. maybe samsung did not optimise their 60Hz setting properly.
prc001 said:
I am using the samsung galaxy A 52s 5g.
It has the exact same issue, the AOD and lockscreen behave like a LCD panel with a yellowish tint when the refresh rate is set on 60Hz.
Though everything else is fine, other screens and apps.
If set at 120Hz then AOD and lockscreen behave normally.
I don't what this is.. maybe samsung did not optimise their 60Hz setting properly.
Click to expand...
Click to collapse
There are color calibration/display issues on all the variable rate AMOLED displays it seems to some degree.
Lol, set to 120hz and be happy.
Who the hell buy 120hz phone and using 60hz
Hi. I don't have any way to show this but my unit has what I think is backlight bleed when displaying a fully black (#000000) picture.
This bleeding is somehow especially visible at 35% (don't ask me why) and 100% brightness.
Now, it's only really visible when in the dark and when my eyes are used to it so it's not a big deal for daily use. However, this screen is supposed to be AMOLED which presumably works on the same principle of OLED displays.
My OnePlus 3T, with the same picture of a plain black background and with the brightness turned to the max shows no sign of any light whatsoever, as any true OLED display should.
My Zenfone 8 however has a weird pattern of tiny scattered dots and a few vertical lines you can barely make out all around the display and especially along the left edge of the display.
Can anyone with a Zenfone 8 check if they observe the same effect ? Like I said, it's only visible when your eyes are well accustomed to obscurity. I tried repeating the experiment yesterday when going to sleep and didn't see anything at first but I woke up later that night and sure enough, the same pattern was visible again.
In case you're doubting the file I used to test it out, here it is. A fully black pic. Of course you have to watch it in fullscreen so that no UI element can pollute your vision.
Any insight on what might be happening would be greatly appreciated.
Used your file and checked it in a pitch black place. Can't see nothing on full brightness. I still had the home-recent apps slider on the bottom but covered it with my finger. I couldn't tell where the screen is at all.
Maybe yours has some defect but if you cannot see it without hours of eyes adjustment than I think you are exaggerating quite a bit.
I've been using the LG V30 which also has OLED but it had a grey lighting always. Don't know why. This screen is much much better.
Kemez said:
Maybe yours has some defect but if you cannot see it without hours of eyes adjustment than I think you are exaggerating quite a bit.
Click to expand...
Click to collapse
It's not like I was purposely trying to find flaws in the display. I was looking for a wallpaper while in bed and as I was zooming in a picture, I noticed as if what I initially thought were color variations in the image remained static on the screen. It wasn't due to a dirty screen. In doubt, I tested with the black picture and cranked the brightness to emphasize the issue and it was clear something was up.
So even if this issue can't be seen during the day, it's still something that can be seen in normal use when using the phone in the dark.
I just went from the my PC to a dark room and tried to reproduce it with brightness at 35% and I could see it in a matter of seconds.
One of the key factors that made me buy this phone in the first place is the AMOLED display. If it's actually defective, I might as well get it replaced. I would just like to know if it's worth the hassle or if every unit has that defect maybe due to something in the manufacturing process.
Can't see anything like that on mine. Totally black everywhere. Try exchanging the phone. Or just give it back and get another so they will not try to repair it.
Thank you very much for your feedback.
The only way the pixels can light is if they have current. Otherwise they are black as night.
Bad firmware or defective hardware.
Try clearing the system cache.
My display has that too, but only at 60 and 120 hz. At 90 Hz, the Dysplay is without lighting, so black as it should.
blackhawk said:
Try clearing the system cache.
Click to expand...
Click to collapse
I don't have the option in the bootloader to reset the system cache, only "wipe data/factory reset".
I selected it thinking it would let me choose what to wipe but then it warned me about permanently deleting everything so I nope out of there.
Any other way I can do that ?
Mr.GSpecial said:
My display has that too, but only at 60 and 120 hz. At 90 Hz, the Dysplay is without lighting, so black as it should.
Click to expand...
Click to collapse
Uh, interesting. I'll give this a try as well.
Nekrozys said:
I don't have the option in the bootloader to reset the system cache, only "wipe data/factory reset".
I selected it thinking it would let me choose what to wipe but then it warned me about permanently deleting everything so I nope out of there.
Any other way I can do that ?
Click to expand...
Click to collapse
It's in Settings somewhere under storage or memory.
On Samsung's it's on the boot menu.
Lol, a factory reset will definitely clear it
Mr.GSpecial said:
My display has that too, but only at 60 and 120 hz. At 90 Hz, the Dysplay is without lighting, so black as it should.
Click to expand...
Click to collapse
That's it! I got the same behavior. Perfect black at 90hz, grey goo at 60 and 120. Since I'm not the only one, I suppose this is "normal". I guess that must be some sort of compromise they had to make for the display and they hoped people wouldn't notice.
It's a shame but at least I'm relieved knowing the screen works well at 90Hz. Since the 120Hz was not one of the key features I was looking for, this doesn't feel too bad a compromise to deal with.
Thank you everyone for your time and replies.
Interesting, I hope this is a software issue that can be fixed with an update...
Same.. When viewing black wallpaper @60/120 hz, it got scattered gray all over the place with a vertical line in the middle. Noticeable if you're in a dark room. Glad i'm not the only one
Alright, so I was able to capture a long exposure photo of the phone on a black screen. The issue appears on 60 and 120Hz like mentionned above. I found that it is more apparent on the 120Hz mode than 60Hz. 90Hz is flawless. The effect is kind of exagerrated, but it was the only way to visibly capture it.
Adaoh said:
Alright, so I was able to capture a long exposure photo of the phone on a black screen. The issue appears on 60 and 120Hz like mentionned above. I found that it is more apparent on the 120Hz mode than 60Hz. 90Hz is flawless. The effect is kind of exagerrated, but it was the only way to visibly capture it.View attachment 5350315
Click to expand...
Click to collapse
Also during restart, the "Zenfone" loading screen appears like that in dark room.
Same behavior here, 120 and 60Hz are not truly black. 90Hz is.
Quick reply to add here that for those that use the phone at 60Hz, you can enable DC Dimming, that solved the issue for my device. 120Hz still needs to be figured out though...
Adaoh said:
Quick reply to add here that for those that use the phone at 60Hz, you can enable DC Dimming, that solved the issue for my device. 120Hz still needs to be figured out though...
Click to expand...
Click to collapse
Interesting.
DC dimming can reportedly have its own drawbacks as well like skewing color rendering.
What is DC Dimming & Why it's Important for AMOLED Smartphones? - Gizmochina
OLED panels have a lot of advantages. They have better color accuracy and contrasts (including better blacks) and are thinner and brighter than traditional LCD panels. So, it’s no surprise that smartphone manufacturers are shifting to OLED panels for their smartphones. Even the mid-range ones...
www.gizmochina.com
after further investigation and trying to replicate on several ZF8's, it seems that this is a normal behavior. The questions is: is it hardware or software?
Many users of this device (including myself) have noticed bad touch input sensitivity when using the 144Hz mode, but not in 60Hz or Auto. I have found quite an odd solution that at least fixes the issue on my end, and I'd like more people to test this, so please, comment down below.
Okay, for this I don't believe you need root. Go to settings and enable USB debugging, find the Motorola Edge 20 USB drivers online and ADB & Fastboot of you choice.
Once you have done all of that, open ADB & Fastboot in a terminal and write the following without the quote marks and the comments that start with a dash (make sure your display is on and the phone is connected to the computer):
"adb devices"
-this command will make a message pop up on your phone asking you if you allow the current computer to access your phone, press allow
"adb shell settings put system peak_refresh_rate 120"
-this will make it so that your max refresh rate can be 120Hz. Keep in mind you can set this to either 48, 60, 90, 120 or 144.
"adb shell settings put system min_refresh_rate 120"
-this will set your minimum refresh rate that the phone will default to when it thinks that it doesn't need the maximum refresh rate. Again it can be set to 48, 60, 90, 120 or 144.
Note: You do not need to reboot, the changes are instant. You can freely use the power saving feature (it sets the refresh rate to 60 when enabled) as turning it off retains the parameters set. The parameters also remain after rebooting. You will have to re-introduce these commands only if you switch the refresh rate option in the settings. This is for the most part a one-time fix.
What this basically does is set the refresh rate parameters for your phone. Android has adaptive refresh rate that oscillates based on the content you watch. The "min_refresh_rate" is the lowest refresh rate your phone will use when conserving power (e.g sitting idle on a .pdf file or watching a 60fps video) and the "peak_refresh_rate" is the highest refresh rate the phone will reach when doing tasks it deems appropriate for 120fps. At least in theory. The reality is that setting any sort of parameters that aren't a fixed refresh rate (e.g 144Hz peak with 90Hz min) will be refused by your device, and it will choose to switch to 60Hz when it feels like it even if you have specifically set it to not do that.
I have used the phone for about a week now with these settings, and I'm positive it is better with 120Hz min and peak. You do not get touch issues at this refresh rate and your phone also doesn't annoyingly switch to 60Hz when scrolling through a web browser or Instagram. It is pinned to 120Hz. Although it sucks that the device is not usable at 144Hz, this is the best solution at the moment until Motorola decides to fix their device.
I unfortunately doubt this fixes the issues with the Indian release of the phone. From my understanding, the Indian market has received a varient that has an AMOLED display that comes with issues far more severe than what I've experienced on my unit. Hopefully it is a software issue rather than a hardware one.
-Username: Required
I'll try this later tonight. Thanks for the tip.
Also, Motorola has announced in their forum that there is a fix coming for the touch issue in a software update.
dannejanne said:
I'll try this later tonight. Thanks for the tip.
Also, Motorola has announced in their forum that there is a fix coming for the touch issue in a software update.
Click to expand...
Click to collapse
Yes, I know this. But we all know Motorola is very slow with updates. If we get that fix by the end of the year we'll be very lucky. Set the refresh to 120 and 120 respectively. I feel that the phone is way more usable this way. I'll update the guide too.
Username: Required said:
Yes, I know this. But we all know Motorola is very slow with updates. If we get that fix by the end of the year we'll be very lucky. Set the refresh to 120 and 120 respectively. I feel that the phone is way more usable this way. I'll update the guide too.
Click to expand...
Click to collapse
My touch still had problems in 144Hz mode after doing this. In auto I never really had an issue. However it is useful to let the phone run at 120Hz all the time.
dannejanne said:
My touch still had problems in 144Hz mode after doing this. In auto I never really had an issue. However it is useful to let the phone run at 120Hz all the time.
Click to expand...
Click to collapse
You shouldn't have touch problems with 120Hz fixed.
Username: Required said:
You shouldn't have touch problems with 120Hz fixed.
Click to expand...
Click to collapse
No I don't, only in 144Hz mode. Didn't have issue in auto mode before fixing the refresh rate either. Anyway let's hope the future update will fix 144Hz mode.
dannejanne said:
No I don't, only in 144Hz mode. Didn't have issue in auto mode before fixing the refresh rate either. Anyway let's hope the future update will fix 144Hz mode.
Click to expand...
Click to collapse
Yeah. Let's hope that it's at least not hardware related and can actually be fixed.
Running 144hz no touch issues hear Smooth as butter ,
Hi there, I'd not noticed this before the Android 12 update, but refresh rate appears to drop from 120Hz to 60Hz when using Picture in Picture or Split Screen views. Can anyone else reproduce this please?
You can confirm this by going into developer mode and toggling to always display the refresh rate.
Try a factory reset if you haven't already and it was a OTA upgrade...
I'd rather see if others can reproduce this first - would have thought it's a simple enough thing to test and post your results here, thanks!
Hi SSJ100, I just tested this to confirm for you, it does drop to 60hz immediately and I cannot prompt it to 120hz until I return to full screen view
Further testing, if i have video running in the background, Amazon, netflix or YouTube it stays at 120 with windowed mode on
DS1000RR said:
Hi SSJ100, I just tested this to confirm for you, it does drop to 60hz immediately and I cannot prompt it to 120hz until I return to full screen view
Click to expand...
Click to collapse
Thanks for checking! Again though, I'm quite amazed (okay, maybe not quite the word hehe) at how no one has reported this issue in this forum (and at least one other "major" forum). If they have, please excuse my ignorance and I'd appreciate a link to the thread.
I can also confirm that this issue persists even after updating to the so-called bug fixing patch "BUKG".
DS1000RR said:
Further testing, if i have video running in the background, Amazon, netflix or YouTube it stays at 120 with windowed mode on
Click to expand...
Click to collapse
Interesting how bugs like this manifest sometimes huh hehe. I first noticed this issue with Google Maps when I was navigating with it and switching to another app (which automatically forces Google Maps app to become picture in picture mode). Scrolling looks quite different and jittery - it's amazing how one gets used to 120Hz!
Have you tried the tiles app developed by a user on here? It can force refresh rates very easily and just requires an adb permission.....there was a thread the other day
ssj100 said:
Scrolling looks quite different and jittery - it's amazing how one gets used to 120Hz!
Click to expand...
Click to collapse
There is some black magic going on with these 120Hz panels. 60 Hz never seemed to be a problem before these high refresh rate displays started popping up. I remember smooth as butter 60Hz phones (both iphones and android). But now when i use a 120Hz panel at a 60Hz refresh rate, it feels like something inside the phone is in it's death throes, coughing and spluttering - the stutter is jarring! But if I use my wife's OnePlus 6 (which has a fixed 60Hz screen), it doesn't feel so bad. It's definitely not as smooth as 120Hz but the 60Hz on a 60Hz panel feels smoother than 60Hz on a 120Hz panel. Is it only me or has anyone else had a similar experience?
I have the same issue as well..so pissed..using latest BUKG
I'm on Android 11, One UI 3 still, and when my phone displays split screen apps the refresh rate drops from 120 down to 60.
This must be some battery saving feature, because If I toggle performance mode (processing speed) from the drop down quick menu, the fps shoots back up to 120 in split screen.
So an easy fix if you need 120 in split screen.
Gasman said:
I'm on Android 11, One UI 3 still, and when my phone displays split screen apps the refresh rate drops from 120 down to 60.
This must be some battery saving feature, because If I toggle performance mode (processing speed) from the drop down quick menu, the fps shoots back up to 120 in split screen.
So an easy fix if you need 120 in split screen.
Click to expand...
Click to collapse
Yes, that seems to "fix" it for split screen. However, it doesn't resolve picture in picture fps drop to 60Hz.
Hmm must be an Android 12 thing. I'm sat here typing this with YouTube playing pip and the screen is holding 120fps even with my finger removed from the screen.
I did try Android 12 when the public version was released, but didn't like it, so downgraded back to the last version of 11, with a clean wipe.
Ok something odd going off, my screen seems to be stuck at 120!
Forcing it back to 60 in display options, works. Putting it back to adaptive, keeps the screen at 120. Even on the lock screen, and AOD!
I might try a reboot.
Gasman said:
Ok something odd going off, my screen seems to be stuck at 120!
Forcing it back to 60 in display options, works. Putting it back to adaptive, keeps the screen at 120. Even on the lock screen, and AOD!
I might try a reboot.
Click to expand...
Click to collapse
If you're in low ambient light, screen at low brightness, panel will be locked at 120Hz even with adaptive selected. Move to bright area or increase screen brightness and check if you are able to get to 60Hz
Gasman said:
Hmm must be an Android 12 thing. I'm sat here typing this with YouTube playing pip and the screen is holding 120fps even with my finger removed from the screen.
I did try Android 12 when the public version was released, but didn't like it, so downgraded back to the last version of 11, with a clean wipe.
Click to expand...
Click to collapse
Yes, I've only noticed this issue since Android 12 with the picture-in-picture scenario. Hopefully Samsung fixes this soon.
Gasman said:
Ok something odd going off, my screen seems to be stuck at 120!
Forcing it back to 60 in display options, works. Putting it back to adaptive, keeps the screen at 120. Even on the lock screen, and AOD!
I might try a reboot.
Click to expand...
Click to collapse
Nothing odd there - as previous poster mentioned, it's always behaved that way when the ambient lighting is low enough. And yes, has always been that way for AOD too. I never understood why 120Hz is required particularly for that!
I think that after android 12, my unlock animation is rendered at 60hz because it is sometimes sluggish. Did a full factory reset and i have the last update. Do you guys experience the same? other than that the phone is perfectly smooth
Still the same issue with BULC December update. Somewhat disappointing, as you'd think this should be quite an easy fix.
Still same issue after BULG update with PIP. As a previous person has noted, split-screen mode appears to be auto-throttled to 60Hz by default, and the only way to change this so it remains at 120Hz is by toggling "High" or "Maximum" "Processing speed".