Related
Here's what I've found related to slow scrolling jitter and the touchscreen. When you first open an app, the very first couple slow scrolling swipes produce very smooth screen animation. It will then get jittery but if you exit the app, then reopen, the smoothness will return. Do this experiment in Contacts app to see what I mean.
Now I found this app called "Touch MultiTest" which reads out the touchscreen sample rate as you move your finger on the screen. When you first open it and do a swipe, you see smooth tracking and a solid sample rate reported greater than 120 Hz. However after a couple swipes the dot response becomes jittery and sample rate drops to something around 100 Hz. Closing and reopening the app gets you back to 120 Hz.
So I think this proves the hardware and software touch loop can produce smooth motion, and it's really sampling at 120 Hz. The big question is what exactly degrades after a couple swipes. In the best case it's some driver or software buffer / interrupt handling that degrades. In the worst case it's related to low level hardware issues. I'm hopeful it's software related. By the way somehow Chrome browser always scrolls smoothly with slow swipes. What is Chrome doing differently than all other apps? Just filtering?
Scrappy1 said:
Here's what I've found related to slow scrolling jitter and the touchscreen. When you first open an app, the very first couple slow scrolling swipes produce very smooth screen animation. It will then get jittery but if you exit the app, then reopen, the smoothness will return. Do this experiment in Contacts app to see what I mean.
Now I found this app called "Touch MultiTest" which reads out the touchscreen sample rate as you move your finger on the screen. When you first open it and do a swipe, you see smooth tracking and a solid sample rate reported greater than 120 Hz. However after a couple swipes the dot response becomes jittery and sample rate drops to something around 100 Hz. Closing and reopening the app gets you back to 120 Hz.
So I think this proves the hardware and software touch loop can produce smooth motion, and it's really sampling at 120 Hz. The big question is what exactly degrades after a couple swipes. In the best case it's some driver or software buffer / interrupt handling that degrades. In the worst case it's related to low level hardware issues. I'm hopeful it's software related. By the way somehow Chrome browser always scrolls smoothly with slow swipes. What is Chrome doing differently than all other apps? Just filtering?
Click to expand...
Click to collapse
Have you tried contacting Essential or possibly using their beta feedback form to tell them about your theory/findings?
Our screens sample at 60Hz. We already know this from the AMA's on Reddit. The test app you're using is inaccurate if it reads 120Hz or even 100Hz.
60Hz sampling in of itself shouldn't be a problem either since iPhones (except for the newest ones) sample at 60Hz and everyone knows how smooth they are.
Hopefully there's not some other hardware flaw and it's just Essential's software.
ChronoReverse said:
Our screens sample at 60Hz. We already know this from the AMA's on Reddit. The test app you're using is inaccurate if it reads 120Hz or even 100Hz.
60Hz sampling in of itself shouldn't be a problem either since iPhones (except for the newest ones) sample at 60Hz and everyone knows how smooth they are.
Hopefully there's not some other hardware flaw and it's just Essential's software.
Click to expand...
Click to collapse
I don't put much stock in the AMA response since its so vague and nonspecific and could be referring to screen refresh rate (60 Hz) either intentionally or accidentally.
If new iPads and iPhones sample at 120 Hz, it's entirely possible essential panel is sampling at 120 Hz.
Try using Touchscreen Benchmark to test and you'll be able to verify the actual samples per second. As a point of comparison, the Galaxy S4 samples at 90Hz and the Shield tablet does a whopping 180Hz!
In any case, it's easy to see that it's not refreshing at 100Hz or 120Hz simply by looking at the number of touch samples that actually appear on the screen. Try it on a faster phone and you can see the higher density of touch responses.
Furthermore, you can't reliably discern the sample rate in the first second so trusting the app saying it's 120Hz and dips to 100Hz is even less reliable than the AMA.
ChronoReverse said:
Try using Touchscreen Benchmark to test and you'll be able to verify the actual samples per second. As a point of comparison, the Galaxy S4 samples at 90Hz and the Shield tablet does a whopping 180Hz!
In any case, it's easy to see that it's not refreshing at 100Hz or 120Hz simply by looking at the number of touch samples that actually appear on the screen. Try it on a faster phone and you can see the higher density of touch responses.
Furthermore, you can't reliably discern the sample rate in the first second so trusting the app saying it's 120Hz and dips to 100Hz is even less reliable than the AMA.
Click to expand...
Click to collapse
I invite anyone to do my test and decide for themselves or measure and produce new data. That's what I'm going for here. Not regurgitation of bland statements.
Scrappy1 said:
I invite anyone to do my test and decide for themselves or measure and produce new data. That's what I'm going for here. Not regurgitation of bland statements.
Click to expand...
Click to collapse
I just invited you to use a different test instead of relying on one that doesn't spit out reasonable numbers.
Does it make more sense that the Essential potentially is using a 120Hz touchscreen which Essential won't confirm despite it being a feather in their caps (since even iPhones only got 120Hz recently) or does it make more sense that Essential is using a slower than average (for Android) panel which their software isn't filtering out as well as Apple's software does? Which is more likely to cause jitter and touch latency?
ChronoReverse said:
I just invited you to use a different test instead of relying on one that doesn't spit out reasonable numbers.
Does it make more sense that the Essential potentially is using a 120Hz touchscreen which Essential won't confirm despite it being a feather in their caps (since even iPhones only got 120Hz recently) or does it make more sense that Essential is using a slower than average (for Android) panel which their software isn't filtering out as well as Apple's software does? Which is more likely to cause jitter and touch latency?
Click to expand...
Click to collapse
It's actually that your misunderstanding terminology...
Your mistaking sample rate and refresh rate...
Refresh rate is how many times per second? the screen is redrawn...
Sample rate is how many times per second? the screen reads touches...
No way you can tell the difference between 120hz vs 100hz.
Sent from my PH-1 using Tapatalk
rignfool said:
It's actually that your misunderstanding terminology...
Your mistaking sample rate and refresh rate...
Refresh rate is how many times per second? the screen is redrawn...
Sample rate is how many times per second? the screen reads touches...
Click to expand...
Click to collapse
No, I'm referring to the touchscreen. Obviously the Essential LCD only refreshes at 60Hz (only the Razer and iPad Pro refreshes at 120Hz) but the touchscreen also samples at 60Hz which is common for lower end Androids (90Hz and 120Hz are the other common sampling rates found in Android devices).
The new iPhone X's OLED still refreshes at 60Hz but has a 120Hz sampling touchscreen which is higher than the 60Hz it used to be in other iOS devices (except for the iPad Pro). I also mentioned the Shield tablet sampling at 180Hz and there's no mobile device with a screen refresh that fast either.
LNJ said:
No way you can tell the difference between 120hz vs 100hz.
Click to expand...
Click to collapse
The drop to 100 Hz after a couple of seconds is "indicative of the problem", not that a 100 Hz rate would not be smooth in a properly designed device. Something comes unhinged at the point we see the drop to 100 Hz. Could be touch buffer / event que is not being serviced fast enough due to low level driver or hardware. Also could be some piece of software in critical path starts consuming more time than allowed, leading to non uniform response. Could be actual stuttering of hardware.
When you exit and then restart an app, the touch event pipleline is flushed, so things are fixed again for a couple of seconds.
YouTube app
Scrappy1 said:
Here's what I've found related to slow scrolling jitter and the touchscreen. When you first open an app, the very first couple slow scrolling swipes produce very smooth screen animation. It will then get jittery but if you exit the app, then reopen, the smoothness will return. Do this experiment in Contacts app to see what I mean.
Now I found this app called "Touch MultiTest" which reads out the touchscreen sample rate as you move your finger on the screen. When you first open it and do a swipe, you see smooth tracking and a solid sample rate reported greater than 120 Hz. However after a couple swipes the dot response becomes jittery and sample rate drops to something around 100 Hz. Closing and reopening the app gets you back to 120 Hz.
So I think this proves the hardware and software touch loop can produce smooth motion, and it's really sampling at 120 Hz. The big question is what exactly degrades after a couple swipes. In the best case it's some driver or software buffer / interrupt handling that degrades. In the worst case it's related to low level hardware issues. I'm hopeful it's software related. By the way somehow Chrome browser always scrolls smoothly with slow swipes. What is Chrome doing differently than all other apps? Just filtering?
Click to expand...
Click to collapse
I have noticed that if you launch the camera and then open the YouTube app or whatever you're using where you can see the touch scrolling jitters, the touch scrolling is nice and smooth. Then after some time it comes back. The touch scrolling in Chrome is perfect and I wish it was the same everywhere. For some reason the YouTube app performs the worst for me. Chrome must have received an update a while back since I used to get bad touch scrolling on that too. The thing that worries me is some claim touch scrolling is perfectly smooth on their device. Hopefully that's a case of them not noticing it and not a case of actual hardware differences.
mhajii210 said:
I have noticed that if you launch the camera and then open the YouTube app or whatever you're using where you can see the touch scrolling jitters, the touch scrolling is nice and smooth. Then after some time it comes back. The touch scrolling in Chrome is perfect and I wish it was the same everywhere. For some reason the YouTube app performs the worst for me. Chrome must have received an update a while back since I used to get bad touch scrolling on that too. The thing that worries me is some claim touch scrolling is perfectly smooth on their device. Hopefully that's a case of them not noticing it and not a case of actual hardware differences.
Click to expand...
Click to collapse
Cool tip! I hadn't noticed that. Opening camera then switching to contacts had me scrolling smooth for many minutes. However after a few rounds of tests it lost the magic. I could no longer use camera open first to produce the smooth scrolling. So there are several factors at play here and this could use more investigation. Most of all though this gives me hope the issue can be totally fixed in software.
I'm starting to think the thing that goes bad and causes choppiness is the rendering pipeline. I enabled "Profile GPU Rendering" and then did a screen capture after scrolling my battery stats in settings for both 1) good condition just after launching settings when scrolling is smooth and 2) bad condition that kicks in after a few seconds when things get choppy. The bad condition shows vastly inflated rendering time which blows the 60 FPS (green line) budget. The largest increase is in red (command issue), but EVERYTHING is inflated in the bad condition. What could cause this?
The captures of the good and bad conditions are attached.
Turns out the reason the rendering pipeline starts taking so long is due to the application thread moving from high performance CPU cluster to the low performance CPU cluster. Using the paid version of System Monitor I opened a floating window of CPU load and freq. I then again opened battery settings and scrolled around in the good and bad state. I can see the CPU load is on the high performance cluster right away (5-8) and those guys are running at 2.4 GHz. Hence everything is smooth. When the jitters set in, the load has moved to low performance cluster (1-4) and they are running much lower clock rate < 1 GHz. I do believe this is probably fairly normal android behavior, but it's obviously tied to the slow scrolling jitters for us. It could be a subtle governor or big.LITTLE thread scheduling issue somehow playing into touch screen weirdness I suppose.
The two captures attached show the issue. One was captured right after launching battery settings when things are smooth and CPUs 5-8 are screaming. Other was captured after things went jittery, and here you can see CPU load that was on 5-8 has moved to 1-4, and clock frequency is much lower. (Hovers between 300 - 1000 Mhz)
Scrappy1 said:
Turns out the reason the rendering pipeline starts taking so long is due to the application thread moving from high performance CPU cluster to the low performance CPU cluster. Using the paid version of System Monitor I opened a floating window of CPU load and freq. I then again opened battery settings and scrolled around in the good and bad state. I can see the CPU load is on the high performance cluster right away (5-8) and those guys are running at 2.4 GHz. Hence everything is smooth. When the jitters set in, the load has moved to low performance cluster (1-4) and they are running much lower clock rate < 1 GHz. I do believe this is probably fairly normal android behavior, but it's obviously tied to the slow scrolling jitters for us. It could be a subtle governor or big.LITTLE thread scheduling issue somehow playing into touch screen weirdness I suppose.
The two captures attached show the issue. One was captured right after launching battery settings when things are smooth and CPUs 5-8 are screaming. Other was captured after things went jittery, and here you can see CPU load that was on 5-8 has moved to 1-4, and clock frequency is much lower. (Hovers between 300 - 1000 Mhz)
Click to expand...
Click to collapse
Let's try this
@DespairFactor
GPU governor
rignfool said:
Let's try this
@DespairFactor
Click to expand...
Click to collapse
Well I can tell you it's not all because of the CPU performance since setting GPU governor to performance on Oreo beta 2 completely gets rid of the touch screen jitters for me. I'm running Oreo beta 2, Rey.R3 Kernel and Magisk 15.2. Using EX Kernel Manager to set GPU governor to performance, I have eliminated the touch scrolling microstutters. Try it out for yourself and see! I also set CPU governor to conservative to compensate for the slightly increased battery usage. Phone is blazing now. https://forum.xda-developers.com/essential-phone/development/kernel-rey-kernel-t3723601 is the link to the kernel.
mhajii210 said:
Well I can tell you it's not all because of the CPU performance since setting GPU governor to performance on Oreo beta 2 completely gets rid of the touch screen jitters for me. I'm running Oreo beta 2, Rey.R3 Kernel and Magisk 15.2. Using EX Kernel Manager to set GPU governor to performance, I have eliminated the touch scrolling microstutters. Try it out for yourself and see! I also set CPU governor to conservative to compensate for the slightly increased battery usage. Phone is blazing now. https://forum.xda-developers.com/essential-phone/development/kernel-rey-kernel-t3723601 is the link to the kernel.
Click to expand...
Click to collapse
Thanks for your input! I would go down the root and tweaks path if I didn't have to use my phone for work with the Google device policy and all. Hoping for some jitter improvement in next official stock update.
rignfool said:
Let's try this
@DespairFactor
Click to expand...
Click to collapse
I think we can move the touchscreen to it's own workqueue, but not sure if it'll handle this.
mhajii210 said:
Well I can tell you it's not all because of the CPU performance since setting GPU governor to performance on Oreo beta 2 completely gets rid of the touch screen jitters for me. I'm running Oreo beta 2, Rey.R3 Kernel and Magisk 15.2. Using EX Kernel Manager to set GPU governor to performance, I have eliminated the touch scrolling microstutters. Try it out for yourself and see! I also set CPU governor to conservative to compensate for the slightly increased battery usage. Phone is blazing now. https://forum.xda-developers.com/essential-phone/development/kernel-rey-kernel-t3723601 is the link to the kernel.
Click to expand...
Click to collapse
Post a video. In all likelihood, it's just placebo effect. I've heard time and time again people claiming that that the slow-scrolling stutter is gone. It's never once been proven. Here's a side-by-side comparison vs the Pixel XL.
Hi all, wondered if you could shed some light on this situation, I'm not sure if it's my device UK or a software issue. So when I select 120hz some apps are not silky smooth when scrolling like YouTube for example, it's not true 120hz it's as though it's on auto adjust, but it isn't, home screen and some apps are 120hz but some apps aren't is this a app issue or a phone issue? Has anyone else experienced this?
Not all applications support 120hz, Google Maps comes to mind, pretty sure that's capped at 60hz, I remember reading a article about YouTube not supporting 90hz on OnePlus devices, maybe the YouTube application is also called out at 60hz, I'd confidently say it's probably the app rather than the phone
Mat2k2020 said:
Hi all, wondered if you could shed some light on this situation, I'm not sure if it's my device UK or a software issue. So when I select 120hz some apps are not silky smooth when scrolling like YouTube for example, it's not true 120hz it's as though it's on auto adjust, but it isn't, home screen and some apps are 120hz but some apps aren't is this a app issue or a phone issue? Has anyone else experienced this?
Click to expand...
Click to collapse
Its app specific, some apps have no caps some do
I have this issue too.
It seems like whenever a video is playing in whatever app, it will switch to 60Hz.
In Reddit for example, scrolling is very laggy.
If your refresh rate mode is set to auto, ColorOS decides what refresh rate to run on based on a list found at /system/etc/refresh_rate_config.xml
If you set the refresh rate mode to 120Hz, though, it should run at that refresh rate in most apps.
Jordytjes said:
I have this issue too.
It seems like whenever a video is playing in whatever app, it will switch to 60Hz.
In Reddit for example, scrolling is very laggy.
Click to expand...
Click to collapse
Same here, is pretty annoying because takes away all the smoothness feeling, although sometimes it doesn't happen and keeps working at 120hz, so random... Just wondering did you find anyway to avoid this to happen?
Hi all,
I play Genshin Impact on Note 20 ultra and it's not smooth. Already try using lowest graphic and 30 fps but still laggy.
Is there any config to push the performance? I tried disable "game optimizing service" but still not smooth.
Please advice
mastermime said:
Hi all,
I play Genshin Impact on Note 20 ultra and it's not smooth. Already try using lowest graphic and 30 fps but still laggy.
Is there any config to push the performance? I tried disable "game optimizing service" but still not smooth.
Please advice
Click to expand...
Click to collapse
Reduce resolution
Enable "High Performance" power mode
My advice would be to not play at 30 FPS even if you set all the other settings to low.
mastermime said:
Hi all,
I play Genshin Impact on Note 20 ultra and it's not smooth. Already try using lowest graphic and 30 fps but still laggy.
Is there any config to push the performance? I tried disable "game optimizing service" but still not smooth.
Please advice
Click to expand...
Click to collapse
I'm on a UK Exynos device and this game runs very well. I'm on optimised power mode and have disabled the game optimisation service.
I've not measured fps but its close to 60 if not at 60 with everything in game set to maximum. There's the odd bit of stutter here and there but overall the game runs surprisingly very well.
paulrgod said:
I'm on a UK Exynos device and this game runs very well. I'm on optimised power mode and have disabled the game optimisation service.
I've not measured fps but its close to 60 if not at 60 with everything in game set to maximum. There's the odd bit of stutter here and there but overall the game runs surprisingly very well.
Click to expand...
Click to collapse
Hi, how did you disable to GOS?
Hi,
anyone noticing lag in the rotation animation? Most of the time the first time is pretty smooth. When changing rotation a few times thereafter the animations look more like 60 fps (although 120 is activated). Tried it in different apps. Always the same and really annoying and ugly.
Can anybody confirm this?
This issue goes way back. Even my 10+ does it.
Might have to do with the sensor refresh rate and/or degree of tilt/time at tilt/yaw.
If it takes more then a second there's definitely a fault issue.
Mmh. Actually I didn't recognize this when using my S20 with 120hz. At least not that much. So there's nothing that can improve the experience? I even thought the phone didn't have this behavior from the start which led to the question if I have something fishy installed. But there's nothing out of the ordinary. It's the same when using stock launcher or Ruthless launcher.
Be interested if there was a way to make it more responsive. This aspect of the device's behavior is slow by comparison to it's otherwise snappy performance. It is irritating... I hate waiting.
It's about .5-1 second on the N10+ in Brave browser and elsewhere.
I'm going to go through accessibility settings again. It's likely a user hidden setting though.
Have y'all dug into Developer Options & set the animation speeds to 0.5 (or 0)?
It might help some, if you haven't already done so. However, I've experienced it as well on occasion,getting "stuck", if you will.
KOLIOSIS said:
Have y'all dug into Developer Options & set the animation speeds to 0.5 (or 0)?
It might help some, if you haven't already done so. However, I've experienced it as well on occasion,getting "stuck", if you will.
Click to expand...
Click to collapse
Yeap, no joy
KOLIOSIS said:
Have y'all dug into Developer Options & set the animation speeds to 0.5 (or 0)?
It might help some, if you haven't already done so. However, I've experienced it as well on occasion,getting "stuck", if you will.
Click to expand...
Click to collapse
For me the problem is that it looks sluggish as if the phone struggles to display the 120 Hz. Setting the transition scale to 0.5 or 0 doesn't do it for me. Makes it even more unsatisfying.
Cris7ianO said:
For me the problem is that it looks sluggish as if the phone struggles to display the 120 Hz. Setting the transition scale to 0.5 or 0 doesn't do it for me. Makes it even more unsatisfying.
Click to expand...
Click to collapse
It has nothing to do with your refresh rate or does it? It so there may be some hope.
Like I said though both my N10+'s behave this way, it's normal... and irritating.
blackhawk said:
It has nothing to do with your refresh rate or does it? It so there may be some hope.
Like I said though both my N10+'s behave this way, it's normal... and irritating.
Click to expand...
Click to collapse
Honestly it looks like the phone is struggling to keep it on 120hz when rotating. When I choose 60hz and rotate the phone it looks the same way constantly. That's why I'm thinking it has something to do with the frame rate. So in my case it's not about a delay for the animation it's about the smoothness.
Cris7ianO said:
Honestly it looks like the phone is struggling to keep it on 120hz when rotating. When I choose 60hz and rotate the phone it looks the same way constantly. That's why I'm thinking it has something to do with the frame rate. So in my case it's not about a delay for the animation it's about the smoothness.
Click to expand...
Click to collapse
What I'm talking about is how long it takes to flip the screen to landscape once the phone's flipped. Close to 1 second.
I always disable all animations as it wastes resources plus I like the snap.
Lol, if it needs animations, it's too slow.
Cris7ianO said:
Hi,
anyone noticing lag in the rotation animation? Most of the time the first time is pretty smooth. When changing rotation a few times thereafter the animations look more like 60 fps (although 120 is activated). Tried it in different apps. Always the same and really annoying and ugly.
Can anybody confirm this?
Click to expand...
Click to collapse
Sounds like something might be bogging it down.
I have the obligatory delay when rotating (because you have a ton of redraws happening on top of the actual animation itself, not some accessibility setting), but it is minimal. That aside, the rotation is smooth with animation set to 0.5 and adaptive motion smoothness.
The difference between your previous S20, my previous Note 20, and the Z Flip 3 is the lost RAM. This is an 8GB device, compared to 12GB or 16GB from last year. After some time getting used to being able to launch a bunch of stuff, it is easy to forget that this one can't run quite as much at once.
The only sure way to stop that completely without having to keep tabs on how much is running would be Developer options -> Don't keep activities or setting Background process limit, both of which come with some downsides.
If it is happening with a single app running after multiple turns, that could indicate an issue with the GPU. It could be as simple as poor cache handling that will be resolved with an update or a clean start. It could also be a hardware issue.
twistedumbrella said:
Sounds like something might be bogging it down.
I have the obligatory delay when rotating (because you have a ton of redraws happening on top of the actual animation itself, not some accessibility setting), but it is minimal. That aside, the rotation is smooth with animation set to 0.5 and adaptive motion smoothness.
The difference between your previous S20, my previous Note 20, and the Z Flip 3 is the lost RAM. This is an 8GB device, compared to 12GB or 16GB from last year. After some time getting used to being able to launch a bunch of stuff, it is easy to forget that this one can't run quite as much at once.
The only sure way to stop that completely without having to keep tabs on how much is running would be Developer options -> Don't keep activities or setting Background process limit, both of which come with some downsides.
If it is happening with a single app running after multiple turns, that could indicate an issue with the GPU. It could be as simple as poor cache handling that will be resolved with an update or a clean start. It could also be a hardware issue.
Click to expand...
Click to collapse
This sounds like a reasonable explanation to me. The S20 with 12 GB indeed hadn't any of those issues, at least not to that extent. In addition I don't have that issue permanently. It only occurs from time to time. Haven't got an update since release. Hopefully it gets an improvement in the near future as it is disturbing. Nevertheless it is a joke that something like that happens even with 8 GB of RAM.
Cris7ianO said:
This sounds like a reasonable explanation to me. The S20 with 12 GB indeed hadn't any of those issues, at least not to that extent. In addition I don't have that issue permanently. It only occurs from time to time. Haven't got an update since release. Hopefully it gets an improvement in the near future as it is disturbing. Nevertheless it is a joke that something like that happens even with 8 GB of RAM.
Click to expand...
Click to collapse
Do you use split screen apps? The only time i've really come across the issue was trying to run both a game and the browser with a couple other apps still in the background.
I think an update will definitely help, though. It seems like the 8GB on this is a larger step down than it should be right now and it is supposed to be a much better GPU.
twistedumbrella said:
Do you use split screen apps? The only time i've really come across the issue was trying to run both a game and the browser with a couple other apps still in the background.
I think an update will definitely help, though. It seems like the 8GB on this is a larger step down than it should be right now and it is supposed to be a much better GPU.
Click to expand...
Click to collapse
No, I don't really use split screen apps. Hopefully an update will help. The device definitely has some obvious tradeoffs but in general it feels fresh and I really like it.
Just an update from my side: Indeed my inner feeling wasn't wrong. I just encountered the sluggish rotation again. Thereafter I went to developer settings and enabled show refresh rate. I went back and tried rotation again. The first time all is fine and it shows 120, but the times thereafter it jumped to 60 Hz when rotating. And if course my eyes will notice this behavior as they are used to 120. Hopefully this will get fixed. This has to be software related.
So this behavior is due to the adaptive refresh rate. It's there a way to force 120 all the time?
Cris7ianO said:
Just an update from my side: Indeed my inner feeling wasn't wrong. I just encountered the sluggish rotation again. Thereafter I went to developer settings and enabled show refresh rate. I went back and tried rotation again. The first time all is fine and it shows 120, but the times thereafter it jumped to 60 Hz when rotating. And if course my eyes will notice this behavior as they are used to 120. Hopefully this will get fixed. This has to be software related.
So this behavior is due to the adaptive refresh rate. It's there a way to force 120 all the time?
Click to expand...
Click to collapse
[App]Galaxy Max Hz (Refresh Rate Mods, Screen-off Mods, QS Tiles, Tasker Support and More)
About this app: Refresh Rate Control: Easily control the max refresh rate (Hz) of android devices with multiple refresh rates (e.g. note20 ultra, s20/S20+/S20Ultra, z fold 2, s21/s21+/s21Ultra, tab S7/S7+, z fold 3, z flip 3). This app can limit...
forum.xda-developers.com
Pretty sure that would be able to handle it for you.
twistedumbrella said:
[App]Galaxy Max Hz (Refresh Rate Mods, Screen-off Mods, QS Tiles, Tasker Support and More)
About this app: Refresh Rate Control: Easily control the max refresh rate (Hz) of android devices with multiple refresh rates (e.g. note20 ultra, s20/S20+/S20Ultra, z fold 2, s21/s21+/s21Ultra, tab S7/S7+, z fold 3, z flip 3). This app can limit...
forum.xda-developers.com
Pretty sure that would be able to handle it for you.
Click to expand...
Click to collapse
I tried this app and I am not fully satisfied with the outcome. Of course forcing 120hz will train the small battery even more and I don't want to be dependant on a 3rd party solution. Just to confirm the behavior is not only on my end, can you please test the following on your device?
1. Go to developer options and enable show refresh rate
2. Go in following apps: e.g. Whatsapp, Facebook, Google Play, Samsung Internet, Amazon Shopping (cause I don't face this issue on all apps)
3. In each app wait a few seconds four the refresh rate to go down to 60 and then rotate the screen (In my case the refresh rate stays at 60 when rotating in the mentioned apps and this looks horrible when the rest is running on 120hz)
If you could borrow a few minutes of your time to check that would be awesome and is very appreciated Thanks in advance!
Update: Just to be sure I did a factory reset. Still no improvement...
Further investigation gave me more information. There is something weird going on. When display brightness is low (around 10-15%) there is no issue for the phone keeping 120 while rotating. When I go up in brightness the 60hz rotation is back again. This is horrible. I've had a look on the new iPhone 13 pro and Apple doesn't have these issues with their adaptive screen. As I had the S20 before and skipped the s21 with the adaptive one this Flip is my first Samsung device with an adaptive screen. The experience is horrible. I just want a compact android device without such a compromise. This is ridiculous.
I have the version with Snapdragon, the first thing I did was "root" it and install these apps
+Package disabler Pro (To disable all GOS services, also disable all Bixby services since I don't use them)
+FDE.AI (To increase performance, highly recommended, although to force high hertz on the screen is not compatible and gives errors)
*GLTOOLS (To force 90 fps in CODM, although here I have problems with FPS losses and heating, I have an external fan cooler to avoid heating as much as possible, even so I still have low fps jerks)
+KILLAPPS PRO (To close any application that runs in the background, also those of the system, although at the same time they reactivate themselves)
I also lower the resolution to FHD+ and put the colors in natural, which by my logic I understand that I should force the processor less and heat less, the latter if it worked for me the temperature remains stable and the battery lasts much longer.
I have 15 days with the phone and in my little experience with it, I notice that it is not a cell phone to play for many hours CODM without external ventilation, since it gets very hot and you lose a lot of performance.
In general, I expected more from him, I thought that by forcing 90 fps and having external ventilation and lowering resolutions I was going to have a high and constant performance in CODM, which disappointed me.
Has anyone had other configurations so that the game is stable and without crashes?
CoDM just sucks on this phone. My OnePlus 8 Pro with a Snapdragon 865 was at least playable. I'm getting a lot of freezing even when not at mac settings