Related
The TF101 suffers from reduced frame rate when you're using it in portrait orientation, this can be observed when you are on the launcher swiping left or right. Compare this to landscape mode where its a lot smoother.
This problem extends into running apps in portrait orientation.
Its my understanding that the Xoom does not suffer from this phenomena, does anything know why? They are both spec'ed exactly the same, this is a problem for me as some games are more suited to portrait play but the performance hit is significant.
Even the on-screen keyboard is slow to react.
Time to trade up?
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?
Has anyone checked this out closely.
I don't sense much better fluidity with Adapted Motion and FHD.
JUST ME?
I think it is just you.....
Set display to 120hz adaptive, load up a big web page or an app which has some scrolling room. Scroll up and down notice how fluid it is.
Then change display to regular standard 60hz and switch back to that web page or app and scroll up and down.
You will notice the difference.
Personally now I don't think I can go back to a 60hz panel on a phone.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About this app:
Refresh Rate Mods
Change default refresh rates
-Easily change the overall refresh rate settings of devices supporting multiple refresh rates.
-Set supported mid refresh rates as the maximum refresh rate limit for battery savings (e.g. 96hz instead of 120Hz).
-Quick settings shortcut
-Tasker plugin support
Motion smoothness mode switcher(Normal, Adaptive or High)***
-Set you device motion smoothness mode to stationary refresh rates (high mode) for better smoothness if so desired on Samsung devices with native Adaptive motion smoothness with a little trade-off to the battery.
-Apply adaptive mod on device that don't natively support adaptive mode [premium]
-Tasker plugin support
Per-app refresh rate settings:
Set different refresh rate settings for every app either adaptive or fixed(stationary) [premium].
Motion smoothness on power saving mode (not working to all devices with OneUI4.**+, test first). ***
-GMH will apply a workaround to bypass 60Hz limitation on Power Saving Mode (PSM) on supported Samsung smartphones.
-Automatically apply workaround when PSM is enabled [premium]
Note: Unfortunately this workaround is blocked and not working in OneUi5.0 on S22 Ultra
Please check this post and this post for other workaround(s).
Screen-off Mods:
Force to Lowest Hz
-Force the lowest refresh rate on screen-off or Always-On Display(AOD) to improve standby power consumption a bit.
-Select refresh rate to set for AOD/screen-off[premium]
-Tasker plugin support.
Auto apply power saving mode during screen-off ***
Auto disable Autosync***
Quick-doze mod***
-Quickly enter doze mode during screen-off that can not be interrupted by motion [premium]
-Tasker plugin support
Auto SENSORS OFF (experimental non-root workaround)
-Device sensors will automatically turn off while screen is off until the device is unlocked to help minimize battery-draining motion-triggered wakelocks while device is not being used [premium]
-Tasker plug-in support
- Supports up to OneUI4.* only
Others
Battery protection mod (Experimental)***
-Option to set maximum charge to 86%-95%(for OneUI4+)[premium]
Quick resolution switcher***
-Easily switch to any supported resolutions using the included quick setting tile
-Tasker plugin support
Customizable refresh rate monitor
-Use statusbar or overlay which you can place anywhere on screen.
-Tasker plugin support
Net speed statusbar indicator
OneUI inspired UI. Dynamic theme and Icon. Manual language selection
Note: The premium license is on a per device basis (not per user).
***these marked features require a one-time ADB procedure (this is not root)
Galaxy Max Hz background service is highly optimized. Background battery usage p is very negligible .
Info:
This app targets older android sdk in order to control refresh rates without ADB setup or root. Just tap OK the dialog that says "This app was built for an older version of Android...." when opened for the first time. If OK button is not visible, just tap the blank space on the lowest portion of the dialog.
If google play protect will prompt during install that the app is built for older version of android and doesn't include the latest privacy protections, you can ignore it and proceed to the installation. For privacy related concern, please refer to FAQ No. 3.
Download
v8.0.0
Changelogs
Github wiki
Localization/Translations Contributors
Italian: @Orlaf
German:devj3ns, drbeat
Russian: @a43 @Surghikov
Swedish:Steffe2
Turkish: osmanakar312
Greek: Nick
Spanish: @Sebastiansm
Czech: Chrono Leggionaire
Simplified Chinese: xiaolu7233123
French: Jaxom84
Polish: Pichulec
Korean: chicking86, 최운택
Lithuanian: @Klaudas
If you want to contribute on translations, please send me a message.
If you want to get GMH Premium features and/or support GMH development but paypal is not available in your place, you can use Google Play Store.
Just download GMH Donation app from Google Play Store.
Note: The price might be slightly higher due to the relatively higher tax imposed on play store.
--Reserved--
Just installed on my S22 Ultra
Will be returning/trading in my Z Flip 3.
android_htc said:
Just installed on my S22 Ultra
Will be returning/trading in my Z Flip 3.View attachment 5543277
Click to expand...
Click to collapse
Nice! How it's working?
tribalfs said:
Nice! How it's working?
Click to expand...
Click to collapse
All good, so far!
I noticed that the lowest refresh rate on stock was 24hz, and now with the app I am able to make it go to 10Hz, which is better
@tribalfs,
Unfortunately, when playing video in the background (i.e. Youtube Vanced in PIP mode) with 10Hz min adaptive refresh rate, the video starts lagging and gets choppy!
Also, Samsung TV Plus is not watchable with min 10Hz refresh rate, it is okay with 24Hz.
android_htc said:
@tribalfs,
Unfortunately, when playing video in the background (i.e. Youtube Vanced in PIP mode) with 10Hz min adaptive refresh rate, the video starts lagging and gets choppy!
Also, Samsung TV Plus is not watchable with min 10Hz refresh rate, it is okay with 24Hz.
Click to expand...
Click to collapse
I'll check. But this is only happening on PIP mode right?
tribalfs said:
I'll check. But this is only happening on PIP mode right?
Click to expand...
Click to collapse
Yes, on PiP mode.
But, on all modes, including full screen for "Samsung TV Plus"!
Edit: also affects Netflix, Disney+ and Prime in full screen mode...refresh rate drops to 10Hz and video gets laggy/choppy.
Youtube seems to be fine though.
First app I downloaded. Great work my n20u worked flawlessly. On my s22u and the improvement is small but significant. Not touching the screen whilst playing video it seems to hit 10hz and low framerate videos. There's a work around using bixby but not ideal. Can I add video playback to a whitelist?
android_htc said:
Yes, on PiP mode.
But, on all modes, including full screen for "Samsung TV Plus"!
Edit: also affects Netflix, Disney+ and Prime in full screen mode...refresh rate drops to 10Hz and video gets laggy/choppy.
Youtube seems to be fine though.
Click to expand...
Click to collapse
shopsdesire said:
First app I downloaded. Great work my n20u worked flawlessly. On my s22u and the improvement is small but significant. Not touching the screen whilst playing video it seems to hit 10hz and low framerate videos. There's a work around using bixby but not ideal. Can I add video playback to a whitelist?
Click to expand...
Click to collapse
I sent private message.
Thank you.
Still dropping to 10hz in fullscreen. The pip seems to be dropping to only 24hz which seems better. Is something different from the N20u?
shopsdesire said:
Still dropping to 10hz in fullscreen. The pip seems to be dropping to only 24hz which seems better. Is something different from the N20u?
Click to expand...
Click to collapse
It's working fine for me now.
Refresh rate drops to 24Hz now for Netflix, Disney+ and Prime.
Note: I cleared data then updated the settings again.
android_htc said:
@tribalfs,
Unfortunately, when playing video in the background (i.e. Youtube Vanced in PIP mode) with 10Hz min adaptive refresh rate, the video starts lagging and gets choppy!
Also, Samsung TV Plus is not watchable with min 10Hz refresh rate, it is okay with 24Hz.
Click to expand...
Click to collapse
Same thing. Also noticed choppy behaviour in simple animations such as loading circle in different apps. It's as if it wouldn't raise the frequency fast enough and got stuck in 10 Hz
xdocent said:
Same thing. Also noticed choppy behaviour in simple animations such as loading circle in different apps. It's as if it wouldn't raise the frequency fast enough and got stuck in 10 Hz
Click to expand...
Click to collapse
I've been given a updated version 7.1.4.33 but it's upto dev to release it. Seems to be cured.
v7.14.33 in-app update now available.
-Improved video player and PIP behavior on lowest min hz settings.-Fixed FC when disabling accessibility service on some localizations-Improved Greek translations-Other bug fixes
what's the show netspeed card option do?
edit
nm, i didnt see the new stuff at the bottom for it.
gonna buy you coffee for the premium after the trial is up, nice app
Been playing with this
When I have it in adaptive mode, and any videos are playing if it drops below 120 everything its choppy and laggy.
I'm using the latest version downloaded off the web page.
Plex is laggy at anything but 120 and it drops to 10 real fast.
Video in games gets choppy on adaptive and the rate drops to 10.
Do i have something configured wrong?
for rght now I set it to high with everything else going to power save/10 when the screen is in AOD.
The rate doesn't really seem to make a difference unless I'm watching stuff so far.
I'll see how the battery life is with it set to 120 all the time when the screen is on while I use it, and 10 when I lock it with the AOD on.
Something odd is going on, I have it set to adaptive with
max 120
max 10 for power saving
min 60 for adaptive
it wont go below 120 now. BUT, if i set min 10 for adaptive it either does 120 or 10, nothing in between.
Powering off still works though, it shows 60, then hits 10, then the notification goes away.
the little status icon never drops under 120 now unless i have min set to 10.
What did I mess up or what do I do to fix it?
ratchetrizzo said:
Been playing with this
When I have it in adaptive mode, and any videos are playing if it drops below 120 everything its choppy and laggy.
I'm using the latest version downloaded off the web page.
Plex is laggy at anything but 120 and it drops to 10 real fast.
Video in games gets choppy on adaptive and the rate drops to 10.
Do i have something configured wrong?
for rght now I set it to high with everything else going to power save/10 when the screen is in AOD.
The rate doesn't really seem to make a difference unless I'm watching stuff so far.
I'll see how the battery life is with it set to 120 all the time when the screen is on while I use it, and 10 when I lock it with the AOD on.
Click to expand...
Click to collapse
Are you using v7.14.33 ?
I can confirm that Netflix, Disney+, Amazon Prime, and Samsung TV are working fine, refresh rate drops to 24Hz lowest with 10Hz min adaptive.
However, just tested an mp4 video and can confirm that refresh rate drops to 10Hz and video gets laggy (do not use Plex, so can't test).
Edit: playing YouTube in the browser also gets laggy as refresh rate drops to 10Hz.
Maybe best to keep the min adaptive refresh rate at 24Hz for now until all apps are optimised.
android_htc said:
Are you v7.14.33 ?
I can confirm that Netflix, Disney+, Amazon Prime, and Samsung TV are working fine, refresh rate drops to 24Hz lowest with 10Hz min adaptive.
However, just tested an mp4 video and can confirm that refresh rate drops to 20Hz and video gets laggy (do not use Plex, so can't test).
Edit: playing YouTube in the browser also gets laggy as refresh rate drops to 10Hz.
Maybe best to keep the min adaptive refresh rate at 24Hz for now until all apps are optimised.
Click to expand...
Click to collapse
yep, 7.14.33. It also stopped changing rates except for 10hz and 120hz, it will not use anything inbetween unless that's the max setting.. So if I set the min at 24, it would only use 120 (or what ever I set the max to) and 24, nothing in between like it did when I first installed it. It's just strange. 60Hz standard is smooth too though, any lower is choppy with UHD and FHD streaming. So unless something is really screwed up with my apk install or the way it's configured I may use 60/120 adaptive then 10 for screen off.
I also cleared data/cache and reset everything with the same results.
*shrugs*