{
"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 the app
PixelParts began as a simple High Brightness Mode (HBM) tool. Since then, it has evolved to include a detailed battery information panel, a display saturation level adjuster, charging limiter and more. The app now offers a wide range of features, transitioning from its original function as an HBM tool to a hub for device tweaks and stats on customs, with a lot more planned going forward. The application needs to be included at build time, so this is a project for device maintainers from other ROMS to use if they'd like.
Current features
CategoryFeatureDescriptionQS TileRequired kernel changesBatteryBattery infoView various battery informationN/AN/AStart/Stop chargingStart/stop charging at specific percentagesN/AN/ADisplayHigh brightness mode (HBM)Directly enable high brightness modeYesN/AAutomatic HBMAutomatically enable high brightness mode based on sunlight intensity (lux)YesN/ASaturationControl the saturation level of the displayN/AN/ALEDsTorch strengthAdjust the brightness of the Pixel Torch flashlight QS-TilePixel TorchN/AUi-BenchJitterCalculate rendering jitter.N/AN/AUSBUSB 2.0 fast chargeEnable CDP mode for faster charging on USB 2.0 ports.YesCommit 1/1
Including PixelParts in your AOSP build
1. Remove HbmSVManager
Commit 1/2 (vendor)
Commit 2/2 (device tree)
2. Clone PixelParts to packages/apps/PixelParts in your AOSP source tree
Run the following cmd at the root of your source tree:
Code:
git clone https://github.com/Evolution-X-Devices/packages_apps_PixelParts packages/apps/PixelParts
3. Include the app at build time
Commit 1/1 (device tree)
This includes the device.mk file from the PixelParts repository, which will add the PixelParts application, its initialization script (init.rc), and the necessary security policies (sepolicies) to your AOSP build during compilation.
Testing new changes
When testing new changes, it is much faster to compile the application standalone and update it manually rather than running a full AOSP build. Please note that some changes may require you to chmod 0666 sysfs nodes and set selinux to permissive. When compiling a full AOSP build, this is not needed assuming the init cmds and sepolicies have been properly configured.
Lunch your device and run the following cmd:
Code:
m PixelParts
This also assumes you are already running an AOSP build including PixelParts as a priv-app in /system_ext.
Screenshots
Source code
GitHub - Evolution-X-Devices/packages_apps_PixelParts: Parts application for pixel 6/7 series
Parts application for pixel 6/7 series. Contribute to Evolution-X-Devices/packages_apps_PixelParts development by creating an account on GitHub.
github.com
Translations
Crowdin
crowdin.com
Credits
WorkAuthorBase preference fragment & CustomSeekBar preferenceNeobuddy89Original AutoHBMServiceHikari no Tenshi & maxwenShakeUtilsAmeChanRainFirst launch warning dialogRamyskiLeonids particle systemPlattysoftRandomized color particle effectLorD ClockaNUSB 2.0 Force CDP kernel changeeng.stk
Reserved
Thanks! this app helps so much!
Thanks. I guess it is not possible to use it on stock rom? Could not find a reason to test custom roms on this device tbh
Automatic HBM is someting I would like a lot Will be available on OP9 Pro also?
I've just checked the code and it seams to me that it could be improved in that way:
1) set HBM on immediatelly when lux > luxThreshold and hold it in time KEY_HBM_ENABLE_TIME + start timer to be sure that HBM goes off after the amount of time)
2) set HBM off when lux < luxThreshold or time KEY_HBM_ENABLE_TIME finished. Hold HBM off in the KEY_HBM_DISABLE_TIME (to release and cool a display)
This helps to protect the display - typical use case: I have turn-by-turn navigation on, the sun is shining so I want to switch HBM off after a while to protect my screen. It would be great if HBM can go off when temperature is high also (at least battery temperature, better phone temperature)
thuryn said:
I've just checked the code and it seams to me that it could be improved in that way:
1) set HBM on immediatelly when lux > luxThreshold and hold it in time KEY_HBM_ENABLE_TIME + start timer to be sure that HBM goes off after the amount of time)
2) set HBM off when lux < luxThreshold or time KEY_HBM_ENABLE_TIME finished. Hold HBM off in the KEY_HBM_DISABLE_TIME (to release and cool a display)
This helps to protect the display - typical use case: I have turn-by-turn navigation on, the sun is shining so I want to switch HBM off after a while to protect my screen. It would be great if HBM can go off when temperature is high also (at least battery temperature, better phone temperature)
Click to expand...
Click to collapse
There are some major improvements coming to the HBM aspect of the app. One of them being the ability to define a temp threshold. The entire autohbm service is being rewritten, and it's preference and sub preferences will be relocated to their own fragment/activity soon.
AnierinB said:
There are some major improvements coming to the HBM aspect of the app. One of them being the ability to define a temp threshold. The entire autohbm service is being rewritten, and it's preference and sub preferences will be relocated to their own fragment/activity soon.
Click to expand...
Click to collapse
really, really cool, thank you a lot fot this
Moved autohbm preferences into their own fragment. Finishing the AutoHBMService rewrite and adding a temperature threshold now.
PixelParts: Move autohbm preferences into their own fragment · Evolution-X-Devices/[email protected]
Signed-off-by: AnierinB <[email protected]>
github.com
PixelParts: Display the current lux level in AutoHBM fragment · Evolution-X-Devices/[email protected]
During onSensorChanged, the lux level is set as the summary for the current_lux_level preference. Listener is registered when enabling the main switch and when the fragment is resumed (only if the...
github.com
That's great. Just my experience today with my OP9Pro. I was reading PDF file outside, on the sun, HBM off and event thought, battery temperature (other sensor is not present) shows 53 °C. I don't know what makes the hear - CPU or display, but it could be good if CPU frequency goes down for a while or display goes to lower brightness. Or 53 °C is OK, I don't know.
One more experience with heating - I've found that when I ride a motorbike, turn-by-turn navigation on, even if display is on low brithness the phone heats a lot and battery is not charged because of that. So some CPU throttling is needed
thuryn said:
One more experience with heating - I've found that when I ride a motorbike, turn-by-turn navigation on, even if display is on low brithness the phone heats a lot and battery is not charged because of that. So some CPU throttling is needed
Click to expand...
Click to collapse
Most definitely not a result of the app.
AnierinB said:
Most definitely not a result of the app.
Click to expand...
Click to collapse
Of course not, it's like an advice for the next feature ;-)
thuryn said:
One more experience with heating - I've found that when I ride a motorbike, turn-by-turn navigation on, even if display is on low brithness the phone heats a lot and battery is not charged because of that. So some CPU throttling is needed
Click to expand...
Click to collapse
The problem with heat, overall, in my experience is related to one thing; the sun. If the phone is charging on my Dash and I'm in a position where the phone is in the sun, the heat goes up quickly. Otherwise, usage has never caused heat with this phone as it did with the P6P
HipKat said:
The problem with heat, overall, in my experience is related to one thing; the sun. If the phone is charging on my Dash and I'm in a position where the phone is in the sun, the heat goes up quickly. Otherwise, usage has never caused heat with this phone as it did with the P6P
Click to expand...
Click to collapse
Interesting. I've found that also - the sun. But the CPU is also the source of heat (because I ride after sunset). Anyway, I've found a solution - slow down the CPUs by Tasker.
Great app. Just curious, will adaptive charging work together with stop charging in pixel parts? (Assuming i set the stop charging at 100%) or it will disregard the adaptive charging and charge it to 100% and stop there
Related
Hi,
I was not satisfied with how Android system auto-brightness work. It just don't allow me, nor us to setup maximum screen brightness level for auto-brightness just like iOS did. This problem is really bugging me about my Nexus S battery usage which is bad because of screen is just too bright while i just need maybe just half of it since i spend most of days indoor.
Then i started to learn Android development (this is my first Android app) and here is my simple app to configure my Nexus S auto-brightness. Currently app feature are:
Save battery! Service implementation is really battery friendly (not even shown on Android battery stats)
Custom maximum screen brightness level (in %) (require modify system settings permission)
Custom screen brightness threshold to apply new brightness level (in %)
Allow to use smooth screen brightness level transition
Custom ambiance level pool interval (in seconds). But when screen is awake, brightness level is calculated as soon as possible
Auto-start service on boot completed (require run at startup permission)
Auto-start service when destroyed by Android OS because of system low memory
Display live current screen brightness level (in %)
Display live current light sensor levels (in lx)
FREE!
Screenshots
{
"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"
}
Known issues:
On my Nexus S (CyanogenMod 10.1 nightly) maximum light sensor value is 3.6 million (wow!). Each device could provide different sensor value and steps. Example, Nexus 4 Stock would provide 10.000 for maximum sensor value.
Currently using this and this as calculation method
Because of above issues, i still looking for best implementation to normalize light sensor values. Maybe anyone can help about this?
Download and try it from here
UPDATE
20120212 - Check if device has any Light Sensors
Hey! I like the idea of your app. However, I haven't found the issue of auto brightness being set at too high of a maximum value in my usage. What I have found is that auto brightness does not kick it down enough when in low light/dark situations. Are you planning on adding the feature of setting a minimum screen brightness level as well?
crashed when i start the service on my xperia active ics
kino1122 said:
Hey! I like the idea of your app. However, I haven't found the issue of auto brightness being set at too high of a maximum value in my usage.
Click to expand...
Click to collapse
Hi, sorry for my bad english, the issue is not the screen auto brightness being too high above Android maximum brightness setting (on manual brightness). But, its the same as the problem you described below
kino1122 said:
What I have found is that auto brightness does not kick it down enough when in low light/dark situations. Are you planning on adding the feature of setting a minimum screen brightness level as well?
Click to expand...
Click to collapse
To tackle this problem, auto brightness setting is mimicking how iOS implementing its auto-brightness.
By configuring maximum brightness allowed to certain amount (by %). For example, in dim indoors (light sensor lux values ranging from 201 to 400), the default Android auto-brightness will be 30% to 40% (based on this formula, which is log10(lux)/5), then in this app, I configure maximum brightness to 50%, then screen brightness will be 50% of this Android default 30%-40%, which is 15% to 20%. Exactly how iOS device did with its screen auto-brightness.
About minimum screen brightness, it always will be 0%-3%. Android system use 0 to 255 brightness value. By configuring maximum brightness to 50% (it will be 127), then your device screen brightness will be half lower than standard Android auto-brightness. Since the most battery draining items is screen, by cutting its brightness to half or more, i think it will be longer my battery cycle, as i posted above.
oldsap said:
crashed when i start the service on my xperia active ics
Click to expand...
Click to collapse
Oops sorry for that, i did not test it on other device than my Nexus S with CM 10.1 yet, would you send me your logcat? This link will show you how to get logcat
oldsap said:
crashed when i start the service on my xperia active ics
Click to expand...
Click to collapse
i just updated apk with light sensor checking. i suspect Android could not find any light sensor on your device.
the service was trying to start, check if there is no any light sensor, since it found no light sensor, service is not registering screen on/off broadcast. then when service stopped, service try to un-register a never registered screen on/off broadcast resulting a Force Close/crash.
please try to update it. thanks
Just what I was looking for. Thanks!
Summary:
A simple application that uses a transparent overlay to dim the device brightness, effectively removing PWM.
Download PWMfree
More Information:
Why PWM is such a headache
Brief explanation about PWM
Default brightness control:
{
"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"
}
PWMfree brightness control:
Thanks, runs on my S9 on AOSP 8.1. Affects auto-brightness a bit but seems to work as intended. Great work!
Wrong section man
Can someone explain to me what this app on s9 does?
Its suspicious
@amakuramio
Not sure why the installation is prevented.
The application itself just creates an accessibility overlay and changes the permission for /sys/class/backlight/panel/brightness to prevent access from liblights.
Edit:
Seems like this is the common behaviour for non-playstore apps: disable Google Play Protect
The brightness does not change while sliding the slider, only after releasing the slider. Please fix, thx.
Can this work on other models (like my Galaxy A3 2017 AMOLED) ?
vratnik said:
The brightness does not change while sliding the slider, only after releasing the slider. Please fix, thx.
Click to expand...
Click to collapse
Unfortunately not possible.
victo24dord said:
Can this work on other models (like my Galaxy A3 2017 AMOLED) ?
Click to expand...
Click to collapse
The overlay itself should work on every device, only the brightness slider override that requires root is device dependent.
But this isn't particularly well-working, i will probably ditch this override and just add a widget slider so it can be used without root.
So is this root only? Cause I saw my screen change brightness immediately after turning accessibility access on, and I'm not rooted, stock rom.
@qb74
Root permission is used to prevent liblights (android system brightness handler) from accessing the kernel brightness path (/sys/class/backlight/panel/brightness).
The brightness slider on the notification bar then only modifies the transparency of the accessibility overlay, not the display (kernel) brightness.
Without root permission it controls both the overlay and kernel brightness, but this prevents the pwmfree usage as the kernel brightness needs to be at 100% to avoid pwm dimming.
Trying out on s8+. But weird thing is, when enabled, if you lower the brightness to 0% the screen becomes completely dark. It should not happen like this, I presume. The app has root access too.
@parser
The lights service might be different on the S8 and is not correctly halted by the application.
Here is a first version that works without root and only relies on the accessibility service: (link in the original post)
It locks the device brightness at 100% and uses it's own slider to control it.
Wootever said:
@parser
The lights service might be different on the S8 and is not correctly halted by the application.
Here is a first version that works without root and only relies on the accessibility service: pwmfree.apk
It locks the device brightness at 100% and uses it's own slider to control it.
Click to expand...
Click to collapse
So this version works with non-root? Great! Why does the brightness need to be 100%? From the looks of your graph, all brightness levels seem more consistent?
Wootever said:
@parser
The lights service might be different on the S8 and is not correctly halted by the application.
Here is a first version that works without root and only relies on the accessibility service: pwmfree.apk
It locks the device brightness at 100% and uses it's own slider to control it.
Click to expand...
Click to collapse
Hmm, well than I hope you make this wonderful app s8/+ compatible too
Thanks for your work mate. Would love to use it :good:
qb74 said:
So this version works with non-root? Great! Why does the brightness need to be 100%? From the looks of your graph, all brightness levels seem more consistent?
Click to expand...
Click to collapse
Only the device (kernel) brightness needs to be set at 100%, at this stage the amoled panel only uses a short 59hz vsync signal (this is the small amplitude on the graph).
Anything below ~95% uses the amoled typical 240hz pwm dimming.
The pwmfree overlay now dims the full kernel brightness by decreasing it's transparency, this is somehow similar to lcd contrast dimming.
@parser
The new version should work on all amoled devices, although the widget type brightness slider is a bit less comfortable than the android system one.
Wootever said:
Only the device (kernel) brightness needs to be set at 100%, at this stage the amoled panel only uses a short 59hz vsync signal (this is the small amplitude on the graph).
Anything below ~95% uses the amoled typical 240hz pwm dimming.
The pwmfree overlay now dims the full kernel brightness by decreasing it's transparency, this is somehow similar to lcd contrast dimming.
@parser
The new version should work on all amoled devices, although the widget type brightness slider is a bit less comfortable than the android system one.
Click to expand...
Click to collapse
Trying it atm, the only down side is, as u said, adjusting the brightness by hand. If I am in a game and need brighter screen, have to go desktop and adjust it :/
Would it have an effect on battery efficiency too?
@parser
The overlay is managed by SurfaceFlinger and shouldn't cause any impact. The amoled panel seems to work identical with the contrast dimming and i would guess the battery usage is similar, but i can't tell for sure yet.
As for the brightness slider, i think this can be placed on the notification bar instead, which should increase the usability.
Wootever, you're BEST!
P.S. I sold my Note 8
I installed it but it won't run, s7 stock rooted.
{
"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"
}
Cometin
What is Cometin
Cometin is a free*, growing collection of tweaks and tricks to optimize your productivity and improve the Android experience.
More information
I can create a separate app for every idea I have. But why shouldn't I put everything in 1 app?
Google announced Dynamic Modules at the IO in 2019
With dynamic features you can split an app into several parts. This is exactly what Cometin is.
Cometin is a growing collection of tricks and tweaks for your Android device, split into modules.
This way you only download the features that you want to use and save your storage space.
Available modules (with some small descriptions)
• Ambient display
bring a customized Ambient display, Always-on-display and wave to wake to your device
• App locker
Lock apps behind a passcode or pattern
• Better rotation
Forces every app to be compatible with every orientation including 180 degrees
• Caffeine
Keep your screen on for a certain amount of time
• Cometin Sync
Sync notifications, and notes between phones and desktops
• Darker brightness
Go below the minimum brightness by applying a dark overlay on top of your screen
• Flip to shhh (beta)
Flip your phone face down to silent notifications (except alarms)
• Heads-up
Hide head-up notifications
• Immersive
Hide statusbar, navigationbar or both
• Parallel
Create a work profile to seperate personal and work
• Remap assistant
Execute a different action when opening the assistant
Is this safe?
Yes! All modules are only served from the Google Play Store, all modules are scanned by Google Play Protect so nothing to worry about!
Installing modules:
The installation of modules is done immediately, and you can use the module immediately after installation.
Updating modules:
Installed modules are automatically updated together with Cometin. No hassle with separate files!
Removing modules:
Module uninstalls do not occur immediately. That is, the device uninstalls them in the background in the next 24 hours.
Request for new features:
Requests for new features are always welcome! However, I cannot promise anything about the actual arrival of these features.
Request your features via my support ticket system. This way you can keep track of the status of features.
Need help or got problems?
If you are stuck or need more information, don't hesitate and contact me via Telegram, XDA or my support ticket system. That way I can best help you.
Did I got your attention?
For the latest list of available modules, screenshots and more information please visit the Play Store listing
Play store
Downloads:
Play store
Support:
Telegram group
Note for MIUI users:
MIUI is known for breaking core functionalities in Android. If you want to use Cometin on a MIUI or Xiaomi device please read this: https://helpdesk.stjin.host/kb/faq.php?id=7
You can also join the Telegram group: https://t.me/joinchat/C_IJXEn6Nowh7t5mJ3kfxQ
XDA:DevDB Information
Cometin, App for the Android General
Contributors
Stjin, JustPlayingHard, HrX,RKBDI
Version Information
Status: Beta
Beta Release Date: 2019-10-10
Created 2019-10-13
Last Updated 2020-03-14
I have enabled Better rotation & Caffeine modules. Both are working fine. Thanks to developer for this great app.
Will test other modules too and provide feedback for any improvements.
gvamsi_krish said:
I have enabled Better rotation & Caffeine modules. Both are working fine. Thanks to developer for this great app.
Will test other modules too and provide feedback for any improvements.
Click to expand...
Click to collapse
That's wonderful to hear!
Stjin said:
That's wonderful to hear!
Click to expand...
Click to collapse
Thanks for the app.
I've enabled Ambient Display module. When I receive a notification, screen wakes up showing the stock lockscreen and after a second lag, the Ambient Display shows up.
Using on Moto g4 play with Pixel Experience ROM 9.0
midhun.ko said:
Thanks for the app.
I've enabled Ambient Display module. When I receive a notification, screen wakes up showing the stock lockscreen and after a second lag, the Ambient Display shows up.
Using on Moto g4 play with Pixel Experience ROM 9.0
Click to expand...
Click to collapse
Issue acknowledged. Working on a fix!
Stjin said:
Issue acknowledged. Working on a fix!
Click to expand...
Click to collapse
I enabled it too on my pixel 2 xl and disabled the built in ambient display but when i get a notification there's also a 1 sec lag and shows my stock and then the actual ambient display you have made :/ thanks for working on a fix
this app required root or not, bro? thanks your app!
oldman20 said:
this app required root or not, bro? thanks your app!
Click to expand...
Click to collapse
Root not required.
Always on display
this app is awesome! i turned on Ambient Display on my Pixel 3xl; is there any way i can have always on display with the new customized display? Right now, i only see it whenever i get a notification.
Nice app OP. Is there network speed indicator that show download and upload speed in notification in future? Mine using mia1 stock rom, if this app can achieve that i would be happier coz no need to use edexposed anymore
When I remapped assistant, it broke calling up the Google Assistant
When I remapped Google Assistant, it broke it. Google Assistant can no longer be summoned by my voice. Is this a bug? Pixel 3 Android 10.
Nice idea! For now just testing ambient display.
Would you consider adding the option to unlink ring and notification volumes? Linked behaviour is very annoying.
Thanks again for you work!
I'm trying out Ambient display on my tablet and I'm not sure I'm using it right. It's enabled, and I've customized it, but the ambient display doesn't turn on my screen when I get a notification. Is it also possible for me to make the ambient display show when I open the cover of my tablet (my case is one of those kinds that have a flap to cover to the front).
Like the app lots - do you think adding an always on to the ambient display might be a good idea for anyone with an amoled screen but no native option?
Like oneplus owners?
Like me... ?
Hello
First of all thank this application.It is essential for me.
I've enabled Ambient Display module. I need when I'm studying to get notifications on the lock screen and see a header of them.
Now when a notification arrives there is a small lag when you press on the screen to enter.
It would be great to be able to configure the time that these notifications are on the screen, as well as the position in the same and the amount of notifications that one needs.
Best regards and thanks again!
Reporting after a couple of days of testing.
Just used the ambient display and it looks fantastic.
Works everytime too.
Apart from the lag that others have noted, i noticed 2 other issues:
a) when this is enabled, screen dimming & screen off seems to be forced. I've noticed the default time reverting to 15 seconds. Even if there is activity on the screen, it still forces the screen dimming and turning off.
b) there seems to be a noticeable increase in battery drain.
If I uninstall the app will it uninstall all modules right then?
letmedanz said:
Reporting after a couple of days of testing.
Just used the ambient display and it looks fantastic.
Works everytime too.
Apart from the lag that others have noted, i noticed 2 other issues:
a) when this is enabled, screen dimming & screen off seems to be forced. I've noticed the default time reverting to 15 seconds. Even if there is activity on the screen, it still forces the screen dimming and turning off.
b) there seems to be a noticeable increase in battery drain.
Click to expand...
Click to collapse
I've also noticed screen off time reverting to 15 seconds. Is Ambient Display working fine?
Using the Cloud Dashboard and I noticed Microsoft's "Your Phone" application which connects my Windows computer with my phone no longer connects. Does the Cloud Dashboard preempt this connection? Both applications show my phone's (Pro 7) notifications. Your Phone also gives easy access to photos, allows for SMS messaging from a Windows computer and, with the next Windows feature update, will allow for calling from a computer via a phone. I'd like to keep both application up and running.
midhun.ko said:
I've also noticed screen off time reverting to 15 seconds. Is Ambient Display working fine?
Click to expand...
Click to collapse
The display of ambient display works well. The lag issue that others have mentioned, exists. Due to ambient display however, i see some quirks with forced screen locking etc
{
"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)***
-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: Stopped working (blocked by system) on S20 series updated to OneUI4.*.
Update: Google maps workaround implemented in v7.14.51
Update: OneUi5.0 completely fixed the bug on Google maps that allows the app bypass 60Hz limit. Check app for possible extra steps that are reportedly remains working
Screen-off Mods:
Force to Lowest Hz: Force the lowest refresh rate on screen-off or Always-On Display(AOD). This overrides Samsung's strange stock behavior which sets the refresh rate to the highest on screen off (update: it is now at 60hz since OneUI3.0) to improve standby power consumption a bit.
-Tasker plugin support
Auto apply power saving mode during screen-off (after ~ 10 secs)***
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.
-Tasker plug-in support
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.
Download
v8.0.0
Changelogs
Github wiki
Hi, I've tried this on S20 FE 5G however 96hz doesnt seem to work, when enabling it the built in monitor still shows 60hz
Sadly...96Hz option doesnt work. It shows 60Hz instead.
S20 fe 5g.
Sent from my S20 FE 5G
Will continue to wait on a solution for this til it finally happens...
Please don't mind my sig, its been there for a while and I'm too lazy to change it, lol
Any update on the app?
Still waiting for screen resolution changer app any update guys ?
shiva255 said:
Still waiting for screen resolution changer app any update guys ?
Click to expand...
Click to collapse
in the meantime try playing around with the Minimum Width setting in developer options under drawing. raising the value makes things smaller putting more onscreen, lowering must do the opposite. don't forget the default of 411
3mel said:
in the meantime try playing around with the Minimum Width setting in developer options under drawing. raising the value makes things smaller putting more onscreen, lowering must do the opposite. don't forget the default of 411
Click to expand...
Click to collapse
thank you sure will try that also anyone facing heating issues with Exynos version still?
shiva255 said:
thank you sure will try that also anyone facing heating issues with Exynos version still?
Click to expand...
Click to collapse
I don't know, I have the Qualcomm
v6.60 is now up! - you can check this update in the app.
Includes a working adaptive refresh rate mod for S20 series, S20FE and other Samsung devices with multiple refresh rates.
I hope you'll understand if it's only for ad-free for now.
You can test it using the 7-day ad-free trial!
tribalfs said:
v6.60
Experimental Adaptive refresh rate mod working for Samsung devices supporting multiple refresh rates (e.g. S20/S20+/S20Ultra,S20FE) (only available for Ad-free)
Quick power-doze mod: Automatic power saving mode and quick doze mode on screen-off (only available for Ad-free)
7-day ad-free trial is available for you to test. Just click "Activate Ad-free" button and click "More info" on the snackbar prompt that will appear.
Click to expand...
Click to collapse
Hello @tribalfs ,
First, thanks for your work and thanks for the trial, while i don't mind paying for app i like, it's nice to be able to test everything before buying.
Everything seems to work fine on my Galaxy S20 FE 5G (android 11/One UI 3.1), so i will probably buy it after the trial.
One thing to note, though i guess it's due to how the power saving mode work, is that the Quick power-doze mod is not very AOD friendly. It tend to disable and reenable it everytime, and if the power saving mode is on when putting my phone on charge, the bixby routine i use to switch the AOD from "tap to show" to "always on" get stuck.
Hello,
strongly adapting to s20fe 5g
cara76190 said:
Hello,
strongly adapting to s20fe 5g adaptative mod without adb
Click to expand...
Click to collapse
tribalfs said:
v6.60 is now up! - you can check this update in the app.
Includes a working adaptive refresh rate mod for S20 series, S20FE and other Samsung devices with multiple refresh rates.
I hope you'll understand if it's only for ad-free for now.
You can test it using the 7-day ad-free trial!
Click to expand...
Click to collapse
Great app, purchased the ad-free version. Thanks
Hello. Does the application work on s20 fe 4g in android 11. More importantly, does s20 fe display support 96hz ?
Okan94 said:
Hello. Does the application work on s20 fe 4g in android 11. More importantly, does s20 fe display support 96hz ?
Click to expand...
Click to collapse
I think so. But no 96hz in S20FE as far as I know.
Hello everyone! Pls. check update on the app now. v6.61 now up. See changes below.
tribalfs said:
Changelogs
v6.61
- Improvements on adaptive mod behavior for multi-refresh rates devices not natively supporting adaptive refresh rates (fixed issues on prolonged scroll, mouse scroll, not working on settings, etc.)- Set minimum refresh rate for adaptive mode to 60hz or lower (if available)- Net speed indicator now autohides when not connected to internet- More optimizations- Other improvements and bug fixes
Click to expand...
Click to collapse
Hello, love your app.
I think I somehow broke the adaptive refresh rate:
If i set it as 96Hz adaptive, the screen stays at 96Hz when scrolling and goes to 120Hz when idling.
How can i fix this?
Hello everyone.
v6.61.10 build is now up - should fix bug on refresh rate profiles not properly loading introduced in v6.61.0*.
v6.61.10
- Fixed bug on refresh rate profiles not properly loading(bug inroduced in v6.61)Clearing app data is highly recommended after this update
tribalfs said:
I think so. But no 96hz in S20FE as far as I know.
Click to expand...
Click to collapse
Works very well on the S20 Fe thank you.How will it be purchased after the 7-day trial period?
{
"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 ap:
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]
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]
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
***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
Swedish:Steffe2
Turkish: osmanakar312
Greek: Nick
Spanish: @Sebastiansm
Czech: @Chrono Leggionaire
Simplified Chinese: @xiaolu7233123
French: @Jaxom84
Polish: @Pichulec
Korean: chicking86, 최운택
Lithuanian: @Klaudas
Arabic: Sebastian S.
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.
As stated in the "wrong" thread I can set 96 hz in normal energy mode and it works but it doesn´t work in power saving mode though 96 hz is set.
Is it technically possible to fix this or do I have to tolerate this?
Thanks!
Rasti19642 said:
As stated in the "wrong" thread I can set 96 hz in normal energy mode and it works but it doesn´t work in power saving mode though 96 hz is set.
Is it technically possible to fix this or do I have to tolerate this?
Thanks!
Click to expand...
Click to collapse
Existing workaround to bypass 60hz limit on PSM does not work on Z Flip4.
What is recommended the lowest value, if lower then 24 Hz could be set?
Is there any way to set a different minimum refresh rate for the Coversceen on the Flip 4?
Also I've set my app to be on the Beta track but no matter how many times I click Update it never changes to download the Beta.
Great app though!
stejc said:
Is there any way to set a different minimum refresh rate for the Coversceen on the Flip 4?
Also I've set my app to be on the Beta track but no matter how many times I click Update it never changes to download the Beta.
Great app though!
Click to expand...
Click to collapse
Sorry, it's not possible.
Thank you.
V8.0.0.2 in-app update:
-Fixed bug on per-app settings not being restored after turning off and turning on the screen.
tribalfs said:
Sorry, it's not possible.
Thank you.
Click to expand...
Click to collapse
OK no probs, thanks for coming back to me anyway.
Also one thing I've noticed is my phone keeps going back to Standard even though I've set it to adaptive. Ive been trying to work out if it's related to adaptive power saving or Android Auto but it just seems to be random!
i didn't understand if it works on galaxy flip4
stejc said:
OK no probs, thanks for coming back to me anyway.
Also one thing I've noticed is my phone keeps going back to Standard even though I've set it to adaptive. Ive been trying to work out if it's related to adaptive power saving or Android Auto but it just seems to be random!
Click to expand...
Click to collapse
Probably adaptive power saving.
yuri76 said:
i didn't understand if it works on galaxy flip4
Click to expand...
Click to collapse
It should work but you can test it.
On Beta 2 of OneUI 5 (Android 13) every morning after being on charge all night, the refresh rate seems to default to 24hz, if I open up Galaxy Max Hz and change to Standard and Back to Adoptive then its fine again.
Only happened on Beta 2 so hopefully when the final version is out in a few weeks it will be fine.
I have the version of One UI 5.0 and Android 13, I used the app for a few days in test mode and it worked well, after some time I decided to buy the license, unfortunately the 120hz frequency in energy saving mode does not work more, can you tell me why? I repeat, it worked for the first few days, I also repeated the enabling in ADB but nothing, it doesn't work anymore
Peppespa said:
I have the version of One UI 5.0 and Android 13, I used the app for a few days in test mode and it worked well, after some time I decided to buy the license, unfortunately the 120hz frequency in energy saving mode does not work more, can you tell me why? I repeat, it worked for the first few days, I also repeated the enabling in ADB but nothing, it doesn't work anymore
Click to expand...
Click to collapse
120Hz on PSM does not work on Z Flip 4 since launched (except if you do the extra steps). Please check opening post.
v8.1.0 update
-New setting: refresh rate for low battery state.
tribalfs said:
v8.1.0 update
-New setting: refresh rate for low battery state.
Click to expand...
Click to collapse
Does low battery state has tasker params?
tanapak1 said:
Does low battery state has tasker params?
Click to expand...
Click to collapse
Not yet. Will add that in the next update. Thank you.
tanapak1 said:
Does low battery state has tasker params?
Click to expand...
Click to collapse
Update:
You can manually install this update. This is not yet available in in-app update.
v8.1.8 in-app update:
-Added menu to disable mods (reset to stock settings)
-Protect battery mod: Added option to show notification when plugged
-Per-app settings: Added option to show non-launcher apps, added filter and sort options
Just installed on Flip 4 setting max refresh rate to 96hz. In normal mode, it works for about 30 mins then stay maxed out at 60hz. Is it because I'm using a trial version or is this a flip 4 bug?