Develop Bugs

How to maximize battery life without affecting functionality

How to maximize battery life without affecting functionality? I think the answer for this question is different for most of you. It depends on how you plan to use your device, even when it’s not turned on. Keynote is that you have to get the right tools and be creative. To give you a head start, I will dump my configuration in this thread. I am able to get up to 48 hours on one charge using this configuration. If used more intensive, your results may differ from mine though.
My configuration
HTC Desire
DeFroST 2.4d
DeFroST 2.4d"]DeFroST 2.4 SVS 1267Mhz kernel
SetCPU
Setting Profiles
DeFroST 2.4d
I will stick to this ROM for this guide but I’m sure the following applies to your custom ROM as well. DeFroST is my personal favorite and I would like to use this opportunity to thank RichardTrip for all the time he puts into this ROM.
DeFroST 2.4 SVS 1267Mhz kernel
DeFroST 2.4 HAVS max 998MHz 800mV (max 998MHz) might be better at saving more energy. But my decision to pick the SVS 1267Mhz has couple of causes.
I don’t have a CPU that can run at 800mV
I’m not patient, I love to go to max speed when it’s available
I found that with my current settings, battery life is good even with the SVS kernel
As I said, it’s totally up to personal preference. If you feel you need it, flash it! There’s a 925mV kernel out there as well if you have the same issue I do with 800mV (running unstable).
SetCPU
Freely available to any XDA user. A lightweight tool that offers all the functionality we need. Other then setting the default speed, it allows us to use profiles based on things like battery charge and temperature.
Main
Profiles
In my configuration, the phone runs at full speed when the battery capacity >= 75% or if it’s charging. Then when the phone discharges, it gradually scales down the max CPU speed. More important though, I found that I don’t need to have the device running at max speed, seeping energy, when I’m not actively using it. When my display turns of, my max CPU speed will be set to 245Mhz. This is perhaps the most important setting in this configuration.
Setting Profiles
No, not Juice Defender. I don’t know why so many seem to prefer Juice Defender. It cannot be customised the way I like it and the UI gives me a headache. But then again, that’s my opinion, maybe I’m wrong
Setting profiles is once again a lightweight tool that lets you define rules by means of logic. It works like this (example):
Create a profile that enables WiFi
Create a rule Activate WiFi when the condition battery is plugged to any charger is met
I figured that I do not want to receive mail, connect to bluetooth or WiFi when I’m asleep. Also, I don’t need a constant e-mail sync at daytime. 50% sync activity is enough for me. For now, that’ll do.
Profiles
Rules
I have a lot of ideas that can still be implemented. The devs at probeez.com are working hard to implement new functionality into their app. One idea I had was to revert to 2G when the display is turned off. However, the condition display off and the action revert to 2G are not available yet.
If you agree, please let the devs know what functionality needs to be added to make their software even better. Vote on this site.
The 2G functionality has already been planned. My other suggestion, the display state, doesn’t have enough votes yet. You can find it here.
The good thing about this tool is that it will be highly customisable when more and more options are added. This fits the idea of choosing your own energy efficient settings I’m trying to promote with this topic.
Conclusion
I could elaborate my choices, but my point is to give you tips about how to address energy saving. Read this manual and be creative. Copy some of the ideas, change others. Maybe come up with new ideas so brilliant that I should add them to this post .
I’ll try to keep updating this topic with the input from you and the newly available functions in the apps.

Other Recommendations
Manual control of brightness
How could I forget? My own brightness setting is always at the lowest. Unless I'm in a very bright environment (like in the sun) and I cannot see anything on my screen. Auto brightness tends to be to bright in general. The Power Control widget can assist you in quickly switching brightness.
-prove
Use a plain black wallpaper
Although this goes further them some of you want to go, using a plain black wallpaper can save battery usage.
AMOLED: Black wallpaper = Battery saving (experiment result)
-b3ndik

great guide, will try this after I get some sleep!

I would recomend using manual control of display brightness!

prove said:
I would recomend using manual control of display brightness!
Click to expand...
Click to collapse
Added. Thank you.

Although there is not a huge improvement, I'd recommend you to have a plain black wallpaper. It actually saves a few percentages, if you do a quick search around the forum you will find the thread.

b3ndik said:
Although there is not a huge improvement, I'd recommend you to have a plain black wallpaper. It actually saves a few percentages, if you do a quick search around the forum you will find the thread.
Click to expand...
Click to collapse
Added to recommendations, thank you.
Personally I think this goes a bit to far for me. I like active backgrounds, like the one that reflects weather and daytime. However, it's a good idea. If someone can find the link to the detailed topic, I'll add it.

here is the link to the topic. The thread includes tests and results.
http://forum.xda-developers.com/showthread.php?t=660853

is it safe to assume that the profiles that let you enable or disable wifi are in the full paid version ?
*edit*
scratch that, just found 'setting profiles' on the market.

i did lose 2% battery life with just 5 minutes surfing ealier on ..

I have never used any additional program to control power apart from the default Android power widget. I would normally do this to preserve energy no matter which ROM or even which phone I have. It's all common sense:
- turn "2G only mode" and switch on 3G hen I actually need it (e.g. browsing heavy webpages). If you turn off the images in websites even GPRS usually does the job well.
- NEVER use 3G for regular voicecalls. It's a completely senseless way of draining battery fast.
- completely switch off any automatic syncronizations (Gmail, Facebook, Weather, etc.) and syncronize individual accounts only when I actually need it. Simply untick the "automatic synchronization" in the accounts and sync settings.
- of course wi-fi, gps are permanently off and I turn them on manually only when I need them.
- keep the display as dark as possible and no brighter than needed.
- use a solid black wallpaper which saves energy on AMOLED screens (won't make difference on regular TFT LCD). A bright wallpaper may significantly increase energy consumptions.
- forget any "Live" wallpapers.
I have read that killing tasks does not make much difference on Android 2.1 onwards. I still keep killing tasks just as a habit.
This way it adds up a bit of extra manual job but I think it's better than any of those "power control" programs that do the same thing just not as accurately as one can do manually.

well i left my phone on charge overnight and unplugged it at 8am this morning on 100% battery.
6 hours later and it's on 96% - although to be fair that's with near zero usage.

thanks for this topic, very helpfull
on this screenshot, what contains the first line with priority of 100?
http://forum.xda-developers.com/attachment.php?attachmentid=365973&stc=1&d=1279958467
thanks !

I have just implemented everything you recommended, so lets see how tomorrow goes (I can't be bothered to go drive out of my local cell towers ranges right now to see if my WiFi turns off ).
With regards to Disabling Sync, if I set it for 4 minutes out of 5 minutes (4/5) then Sync is only enabled for 1 minute out of every 5 minutes, right?

Having previously used JuiceDefender, I thought I'd give Setting Profiles a bash. First stumbling block is lack of toggling for mobile data - is that right, or have I missed something?

Hidden Powersaver Options: Use single CPU core

Hey all,
I wasn't able to find any conclusive details regarding this topic, maybe you guys can shed some light for me:
In the hidden HTC powersaver options for the HOX, we have the option to use "Reduce CPU speed"- which is set to 'on' by default and its function being explained as then only using a single cpu core and reducing the speed to 1Ghz.
Even though the explanation is rather straight forward I'd like to know exactly what this option does.
Does that mean the CPU is throttled for 'normal use' like browsing, using simple apps, (...) only and is being reverted to its full capacity when (eg) playing games? Or in other words, where exactly is the threshold here?
I find my HOX a lot smoother in response (ie scrolling, surfing) when de-activating this option but battery drain also seems to go way up.
Thanks guys.

Murdock80 said:
Hey all,
I wasn't able to find any conclusive details regarding this topic, maybe you guys can shed some light for me:
In the hidden HTC powersaver options for the HOX, we have the option to use "Reduce CPU speed"- which is set to 'on' by default and its function being explained as then only using a single cpu core and reducing the speed to 1Ghz.
Even though the explanation is rather straight forward I'd like to know exactly what this option does.
Does that mean the CPU is throttled for 'normal use' like browsing, using simple apps, (...) only and is being reverted to its full capacity when (eg) playing games? Or in other words, where exactly is the threshold here?
I find my HOX a lot smoother in response (ie scrolling, surfing) when de-activating this option but battery drain also seems to go way up.
Thanks guys.
Click to expand...
Click to collapse
When battery is below 30%, speed is capped to 1Ghz single core with UI at 30fps

kryptoner said:
When battery is below 30%, speed is capped to 1Ghz single core with UI at 30fps
Click to expand...
Click to collapse
Alright, did not realise those options only applied to the system when battery is below 30%.
Thanks for the quick reply mate!

Murdock80 said:
Hey all,
I wasn't able to find any conclusive details regarding this topic, maybe you guys can shed some light for me:
In the hidden HTC powersaver options for the HOX, we have the option to use "Reduce CPU speed"- which is set to 'on' by default and its function being explained as then only using a single cpu core and reducing the speed to 1Ghz.
Even though the explanation is rather straight forward I'd like to know exactly what this option does.
Does that mean the CPU is throttled for 'normal use' like browsing, using simple apps, (...) only and is being reverted to its full capacity when (eg) playing games? Or in other words, where exactly is the threshold here?
I find my HOX a lot smoother in response (ie scrolling, surfing) when de-activating this option but battery drain also seems to go way up.
Thanks guys.
Click to expand...
Click to collapse
where is this option in HOX?
Best regards,
Deependra

dtandukar said:
where is this option in HOX?
Best regards,
Deependra
Click to expand...
Click to collapse
Its hidden in the settings, you can access it through downloading Minimalistic Text in the play store then set up a temporary widget that leads to settings under activities and search for power saver settings. Then just tap on the widget and it should lead you directly there/

leking19 said:
Its hidden in the settings, you can access it through downloading Minimalistic Text in the play store then set up a temporary widget that leads to settings under activities and search for power saver settings. Then just tap on the widget and it should lead you directly there/
Click to expand...
Click to collapse
simpler way is to download an app called 'hidden settings' from play store

kryptoner said:
simpler way is to download an app called 'hidden settings' from play store
Click to expand...
Click to collapse
^^ thanks!

Are all of these options on this tab only effective on a battery lower than 30% because some of them say that the data conection is only on with the screen on..
And If it's only on a lower 30% battery I will leave them on otherwise I will just turn them of.

Thermal Daemon Mitigation OFF with CM?

Dear All,
I´ve managed to build a CM 12.1 with nfs support. Why 12.1? Well, for my D855, that was the only branch I could get working when building a kernel in Ubuntu, using the downloadable snapshot at CM´s site. The nighty´s would give me errors of different kinds during the building process, so the files on the phone needed when building are probably not the exact required version that match with the repo you can download in terminal mode.
Anyway, my experience with marshmellow is that the phone gets so hot that it turns itself off - another good reason to stay with 12.1.
My phone however still gets hot, which happens when using it with my VR headset to watch UHD clips. After 5 mins of watching, it dims down a bit. Then a few mins later a bit more, and so on until it looks like I´m staring at the screen through old cheap shades.
I´ve already disabled automatic brightness control, tried apps which claim to keep the brightness at the desired strength (Lux, the app is called), an app that´s ment to keep the screen always on (Always Awake), an app claiming to patch this exact bug, flashed a hack that´ll throttle only above 70 C. None of this helped. What I do know is that in the secret menu of stock firmware, there´s an option called Thermal Daemon Mitigation OFF, but I can´t access the secret menu through CM - only CM´s secret menu, that doesn´t have this option. Enabling this is said to cope with the problem.
There´s also a file named thermanager.xml in system/etc, which looks like something which can be modified to meet my requirements, but I´m not sure.
Finally, my least prefered option is to install a thermal pad on the SoC, but although I´m experienced with hardware, it´s on desktop level - not with such tiny things as a mobile.
So please, could someone help out here? Is there a way to rebuild the kernel with the stock secret menu or amendments to the throttling? Is there a way for me to get into the stock secret menu in CM?
Other ideas?
PS: I´m posting here because if there´s a way to get Thermal Daemon Mitigation OFF option related parameters set when building kernel in menuconfig, then it´s related to this sub forum.
PPS: Edited thermanager so all brightness values are 255, this seems to fix the problem!

Research - XZP SHARP Panel @ 120Hz

XZP 120Hz QUEST​
First i would like to push this thread forward cause i thing phone has some potential still to unlock. There is much writen about XZP - 120hz but nothing concrete or usable in stock, before i write something of mine i would like to credit a developer which inspired me to snoof around a bit:
thanks to "kholk @ Github" and here is kholk,s work:
https://github.com/sonyxperiadev/ke...si-panel-somc-synaptics-sharp-4k-cmd-ID6.dtsi
https://forum.xda-developers.com/newthread.php?do=newthread&f=6237
thanks to Paranoid Team for developing a great rom for XZP
http://paranoidandroid.co/downloads/maple
So lots of us have rooted device and in root explorer i triggered search for "SHARP" word just from curiosity, after minutes of waiting search completed and 4 folders stand out:
qcom,mdss_dsi_sharp_4k_dsc_cmd
qcom,mdss_dsi_sharp_4k_dsc_video
qcom,mdss_dual_sharp_1080p_120hz_cmd
qcom,mdss_dsi_sharp_1080p_cmd
Is it possible to enable this mode from this folders and sub files in stock rom? And how would i an amateur user switch this modes?
I will make backups in twrp and then myself try to mess up with files or at least go through them if something punches me in the eye i will report, what i meant to say it would be nice if above links could be used to inject it into our stock roms?
Oh, i recently installed paranoid android and there are settings to enable 120hz but are not yet working, you can google it, so xzp is at least in good hands and path, hope we wount wait too long for this goodies
If annyone has some succes or ideas, observations please write it down maybe some devs will look into them

stipi69 said:
XZP 120Hz QUEST
First i would like to push this thread forward cause i thing phone has some potential still to unlock. There is much writen about XZP - 120hz but nothing concrete or usable in stock, before i write something of mine i would like to credit a developer which inspired me to snoof around a bit:
thanks to "kholk @ Github" and here is kholk,s work:
https://github.com/sonyxperiadev/ke...si-panel-somc-synaptics-sharp-4k-cmd-ID6.dtsi
https://forum.xda-developers.com/newthread.php?do=newthread&f=6237
thanks to Paranoid Team for developing a great rom for XZP
http://paranoidandroid.co/downloads/maple
So lots of us have rooted device and in root explorer i triggered search for "SHARP" word just from curiosity, after minutes of waiting search completed and 4 folders stand out:
qcom,mdss_dsi_sharp_4k_dsc_cmd
qcom,mdss_dsi_sharp_4k_dsc_video
qcom,mdss_dual_sharp_1080p_120hz_cmd
qcom,mdss_dsi_sharp_1080p_cmd
Is it possible to enable this mode from this folders and sub files in stock rom? And how would i an amateur user switch this modes?
I will make backups in twrp and then myself try to mess up with files or at least go through them if something punches me in the eye i will report, what i meant to say it would be nice if above links could be used to inject it into our stock roms?
Oh, i recently installed paranoid android and there are settings to enable 120hz but are not yet working, you can google it, so xzp is at least in good hands and path, hope we wount wait too long for this goodies
If annyone has some succes or ideas, observations please write it down maybe some devs will look into them
Click to expand...
Click to collapse
I wish to have it in Android pie coz of this I really like this phone

I'm building Zest Kernel got this device soon and that surely seems like a great idea. I'm personally thinking of trying to force 120Hz as I forced 90Hz on the Essential phone with celtaire. The only problem is it seems the userland side of things may have limitations to 60fps which would need a bypass somehow, as Razer did.
PA seems interesting that they have a switch so I'll try look at they code to see (if they have the piece of the puzzle I was missing that would be amazing).

Great this would be awesome :fingers-crossed:

can't wait, 60 hz really hurts my eyes.

amakuramio said:
can't wait, 60 hz really hurts my eyes.
Click to expand...
Click to collapse
Lol, as in its pretty smooth anyways. But 120Hz is likely darn water flowing.

Any update on this lol went back to my xz premium

I've been thinking about how to get this working, but it seems tweaking the qcom,mdss-dsi-panel-framerate value on the default configuration (1080p) alone is not enough, although from an initial diff between the original 60Hz configuration and kholk's newly added 120Hz configuration on SonyOpenDevices kernel showed only the framerate value was changed (there are probably things I didn't find).
I've tried changing it from 60 to 90 and 120. Changing to 90 has no apparent effect (the system still renders at 60 FPS), while changing to 120 caused everything to be rendered at 24 FPS (very sluggish). Still, it seems the refresh rate change is indeed set to the value, as this app (which looked rather dated and unreliable) did show the system's refresh rate (rr) is configured to the value written in the dtsi.
From the looks of it, it seems the dtsi file controls what refresh rate be configured at kernel level, but something's probably needed in the userland to get it function properly. But still, it's interesting that setting the value to 120 would cause the system to render everything at 24 FPS, while setting the value to 90 doesn't have any impact.
I posted some details here yesterday as I was mainly building my own CarbonROM zips with some own configurations. For CarbonROM, the dtsi file is located in arch/arm/boot/dts/qcom/dsi-panel-maple.dtsi.
Back to the OP... I've found the entries as well. However, even after I modify the dsi-panel-maple.dtsi and that the modified value is registered somewhere, the value in /sys/firmware/devicetree/base/soc/qcom,[email protected]/qcom,mdss_dsi_sharp_1080p_cmd is still 60 (003c). This file is probably the one representing the original 60Hz command:
https://github.com/CarbonROM/androi.../boot/dts/qcom/dsi-panel-sharp-1080p-cmd.dtsi.
And there's the 120Hz configurations placed in /sys/firmware/devicetree/base/soc/qcom,[email protected]/qcom,mdss_dual_sharp_1080p_120hz_cmd.
This file might be related to it. However, this file is significantly different from the 1080p (60Hz) one and I'm wondering if this is indeed for the same panel our device is using.
https://github.com/CarbonROM/androi...com/dsi-panel-sharp-dualmipi-1080p-120hz.dtsi
Not sure if there are any hope on getting 120Hz working on existing Oreo custom ROMs as SonyOpenDevices is now working on 4.9 kernel (which is used by Pie), and I'm yet to be able to build a working AOSP ROM for it. The last time I built an AOSP Pie ROM and flashed the generated images resulted in a lot of crashes and then the phone powered off by itself... it was completely unusable.
EDIT: It seems the value I previously changed was reflected in /sys/devices/mdss_dsi_panel/change_fps (which can be viewed via cat). As I set it to 90 in the dtsi, the value here is also 90.

raven213 said:
Any update on this lol went back to my xz premium
Click to expand...
Click to collapse
I haven't got round to modding the display on my kernel yet, I'm firstly trying to fix WiFi lol.
---------- Post added at 09:10 PM ---------- Previous post was at 08:56 PM ----------
LSS4181 said:
I've been thinking about how to get this working, but it seems tweaking the qcom,mdss-dsi-panel-framerate value on the default configuration (1080p) alone is not enough, although from an initial diff between the original 60Hz configuration and kholk's newly added 120Hz configuration on SonyOpenDevices kernel showed only the framerate value was changed (there are probably things I didn't find).
I've tried changing it from 60 to 90 and 120. Changing to 90 has no apparent effect (the system still renders at 60 FPS), while changing to 120 caused everything to be rendered at 24 FPS (very sluggish). Still, it seems the refresh rate change is indeed set to the value, as this app (which looked rather dated and unreliable) did show the system's refresh rate (rr) is configured to the value written in the dtsi.
From the looks of it, it seems the dtsi file controls what refresh rate be configured at kernel level, but something's probably needed in the userland to get it function properly. But still, it's interesting that setting the value to 120 would cause the system to render everything at 24 FPS, while setting the value to 90 doesn't have any impact.
I posted some details here yesterday as I was mainly building my own CarbonROM zips with some own configurations. For CarbonROM, the dtsi file is located in arch/arm/boot/dts/qcom/dsi-panel-maple.dtsi.
Back to the OP... I've found the entries as well. However, even after I modify the dsi-panel-maple.dtsi and that the modified value is registered somewhere, the value in /sys/firmware/devicetree/base/soc/qcom,[email protected]/qcom,mdss_dsi_sharp_1080p_cmd is still 60 (003c). This file is probably the one representing the original 60Hz command:
https://github.com/CarbonROM/androi...boot/dts/qcom/dsi-panel-sharp-1080p-cmd.dtsi.
And there's the 120Hz configurations placed in /sys/firmware/devicetree/base/soc/qcom,[email protected]/qcom,mdss_dual_sharp_1080p_120hz_cmd.
This file might be related to it. However, this file is significantly different from the 1080p (60Hz) one and I'm wondering if this is indeed for the same panel our device is using.
https://github.com/CarbonROM/androi...com/dsi-panel-sharp-dualmipi-1080p-120hz.dtsi
Not sure if there are any hope on getting 120Hz working on existing Oreo custom ROMs as SonyOpenDevices is now working on 4.9 kernel (which is used by Pie), and I'm yet to be able to build a working AOSP ROM for it. The last time I built an AOSP Pie ROM and flashed the generated images resulted in a lot of crashes and then the phone powered off by itself... it was completely unusable.
EDIT: It seems the value I previously changed was reflected in /sys/devices/mdss_dsi_panel/change_fps (which can be viewed via cat). As I set it to 90 in the dtsi, the value here is also 90.
Click to expand...
Click to collapse
Okay so I've been looking into this for quite some time and have even got a 90Hz Essential PH-1. But the thing is while we CAN force the display Hz, we aren't telling the display/graphics HAL to run at that frequency. So we need to find a way (or just find the way) to tell HAL to support by default this FPS. Razer clearly does this and that's why even on GSIs the display HAL in its /vendor position loads it up to normal.
Sony's SOMC kernel seems to have the display driver a bit wonky to the AOSP standards as you've seen. It seems this way for their method of HAL switching to 4K. Little OT tip: wm set doesn't change the resolution you see, only changes the resolution that's processed ?.
TL;DR it's pretty obvious (if you spend some time) to see the display references in the kernel where the Hz of the panel is displayed HOWEVER we need to rather focus on finding a way to force/tell the display/graphics HAL to process those 90 or 120 fps otherwise you'll have 60fps on your 120Hz panel .
There is the monitor (Hz) and the processed refresh rate (FPS) and one can usually get used the both being the same when using a desktop system however this is incorrect. They are 99% of the time aligned but it IS possible to have them not aligned (which is what happens when we're changing the kernel here).

LazerL0rd said:
Okay so I've been looking into this for quite some time and have even got a 90Hz Essential PH-1. But the thing is while we CAN force the display Hz, we aren't telling the display/graphics HAL to run at that frequency. So we need to find a way (or just find the way) to tell HAL to support by default this FPS. Razer clearly does this and that's why even on GSIs the display HAL in its /vendor position loads it up to normal.
Sony's SOMC kernel seems to have the display driver a bit wonky to the AOSP standards as you've seen. It seems this way for their method of HAL switching to 4K. Little OT tip: wm set doesn't change the resolution you see, only changes the resolution that's processed .
TL;DR it's pretty obvious (if you spend some time) to see the display references in the kernel where the Hz of the panel is displayed HOWEVER we need to rather focus on finding a way to force/tell the display/graphics HAL to process those 90 or 120 fps otherwise you'll have 60fps on your 120Hz panel .
There is the monitor (Hz) and the processed refresh rate (FPS) and one can usually get used the both being the same when using a desktop system however this is incorrect. They are 99% of the time aligned but it IS possible to have them not aligned (which is what happens when we're changing the kernel here).
Click to expand...
Click to collapse
So it seems we need to also alter the HAL to get the correct FPS. But the interesting phenomenon is, altering the kernel to use 120Hz, without touching any other code, triggers the HAL to render at 24 FPS instead of 60 FPS. This might be a hint on where we need to look at in the HAL code, if possible. I haven't tried other combinations, only 90 and 120, with the former having no impact (60 FPS).
As for you saying the SOMC kernel using a driver wonky to the AOSP standard might explain why it's been so complicated to get DRS (Dynamic Resolution Switching) to actually work despite the functionality's already been implemented in the SonyOpenDevices project (which is NOT what current CarbonROM is based on). Not sure about the functionality in AOSP now, but it's been non-working for quite a while (at least up to the point of switching to the 4.9 kernel as it wasn't complete on 4.4 kernel). At that time, the functionality itself existed, but it did nothing.
And as for the wm not changing the resolution we see... does it mean the panel is still outputting at 1080p even when instructed to change to 4K? If so, the "4K" is actually achieved via GPU scaling (which is also possible on desktop video cards, to attain a virtual 4K resolution on a 1080p-only monitor). This makes the 4K support claim fake, as it's not a real 4K resolution, but rather 4K rendered in background then downscaled to 1080p when outputting to the panel as the panel is operating at 1080p.

LSS4181 said:
So it seems we need to also alter the HAL to get the correct FPS. But the interesting phenomenon is, altering the kernel to use 120Hz, without touching any other code, triggers the HAL to render at 24 FPS instead of 60 FPS. This might be a hint on where we need to look at in the HAL code, if possible. I haven't tried other combinations, only 90 and 120, with the former having no impact (60 FPS).
As for you saying the SOMC kernel using a driver wonky to the AOSP standard might explain why it's been so complicated to get DRS (Dynamic Resolution Switching) to actually work despite the functionality's already been implemented in the SonyOpenDevices project (which is NOT what current CarbonROM is based on). Not sure about the functionality in AOSP now, but it's been non-working for quite a while (at least up to the point of switching to the 4.9 kernel as it wasn't complete on 4.4 kernel). At that time, the functionality itself existed, but it did nothing.
And as for the wm not changing the resolution we see... does it mean the panel is still outputting at 1080p even when instructed to change to 4K? If so, the "4K" is actually achieved via GPU scaling (which is also possible on desktop video cards, to attain a virtual 4K resolution on a 1080p-only monitor). This makes the 4K support claim fake, as it's not a real 4K resolution, but rather 4K rendered in background then downscaled to 1080p when outputting to the panel as the panel is operating at 1080p.
Click to expand...
Click to collapse
The 24 thing seems more like a glitch to me, personally. Since Android was never designed to support high refresh rates. Maybe in Android Q, hey?
By wonky I meant they use a different.. unusual method of seemingly having a display for each resolution (and one for 120hz) which are switched between or something like that. An interesting fact is if you're watching 4k and screenshot you get a black screen. I've noticed Windows 10 doing a similar thing in their recent closed Insider beta.
Yes the panel outputs 1080p even with a 4k resolution as the window manager (wm) only controls how much it processes not the output, without the HALs allowance. Yupp is 4k rendered them down to 1080p and breaks screenshots. You can easily tell by looking at a 4k picture in any app and then album with the stock wm.

Is 120Hz still being worked on? its been nearly a year since it was discovered and i thought it would be working by the end of the year at least. coming from the XZ

XxperexX said:
Is 120Hz still being worked on? its been nearly a year since it was discovered and i thought it would be working by the end of the year at least. coming from the XZ
Click to expand...
Click to collapse
Thanks to Bartcubbins/Pavel we're pretty close to getting it on stock on my kernel.
For custom ROMs they've had it for ages.

LazerL0rd said:
Thanks to Bartcubbins/Pavel we're pretty close to getting it on stock on my kernel.
For custom ROMs they've had it for ages.
Click to expand...
Click to collapse
I follow your project[emoji6]
Envoyé de mon G8141 en utilisant Tapatalk

LazerL0rd said:
Thanks to Bartcubbins/Pavel we're pretty close to getting it on stock on my kernel.
For custom ROMs they've had it for ages.
Click to expand...
Click to collapse
im running omni 8.1.0 custom rom on my XZ and it has the toggle for it, but it doesnt work i understand that u probs only work on the XZP, but at least work is being done on it

Any new updates? or is it still WiP?

LazerL0rd said:
Thanks to Bartcubbins/Pavel we're pretty close to getting it on stock on my kernel.
For custom ROMs they've had it for ages.
Click to expand...
Click to collapse
Which roms?

razerphynx said:
Which roms?
Click to expand...
Click to collapse
Idk but it's been available to all SODP for some time.

How To Guide Force 120Hz Guide (S22)

[Tested. Works as of One UI 4.1 September, 2022 Patch AVHH Build]
Hello again! A handful of you may have seen my S21 guide for forcing 120Hz through pretty much every app and while the camera is active (looking at you, Snapchat!!). The previous guide doesn't apply to the S22 series because Samsung changed the range of valid refresh rate values all the way down to 1Hz.. WELL I still managed to break it... 0.1Hz as a value apparently works.
A kind user made a video based on my guide: Linked;
I also want to say that the August update seems to have broken something for some users, but I've re-applied this on said update and it still works fine on my end.
This is also for allowing 120Hz when the camera is active; not so much forcing 120Hz (some users got confused because of my poor choice of wording).
Before you start, make sure your refresh rate is set to Adaptive.
1. Download SetEdit from the google play store.
2. Open up to the system table.
3. At the very top, you'll see an option to add a new setting. Go ahead and tap.
4. enter this: min_refresh_rate
5. Save changes. For the second value, enter: 0.1
6. Do this again but instead start with: peak_refresh_rate
7. Save changes
8. enter again, : 0.1
9. Save changes.
That's it! You'll still benefit from adaptive refresh rates when the screen is still and most apps will run in 120Hz regardless of their manifest. Enjoy a smooth Snapchat and everything else!
No.. Google Maps still runs at 60Hz; but rightfully so! It uses a lot of battery as-is.
If you want to undo this, carefully delete the lines we added and reboot the phone.
Screenshot 1: Snapchat 120Hz
Screenshot 2: Native Camera 120Hz

Thanks bossman. On it.

Will this force games like COD Mobile to run in 120pfs?

Kris_b1104 said:
Will this force games like COD Mobile to run in 120pfs?
Click to expand...
Click to collapse
It won't 'force' games to run any higher than they are programmed to. It just allows the screen to go up to 120Hz in most applications that normally wouldn't.

MochaVex said:
It won't 'force' games to run any higher than they are programmed to. It just allows the screen to go up to 120Hz in most applications that normally wouldn't.
Click to expand...
Click to collapse
Thanks, makes sense.

What FPS counter app do you use?

Thank you for this! Does this tweak have an impact on battery life?

Kris_b1104 said:
Will this force games like COD Mobile to run in 120pfs?
Click to expand...
Click to collapse
if you want play COD with 120hz just use [App]Galaxy Max Hz ,
i play on mine s22 with very high graphic quality and force 120hz with this app

herothezero90 said:
Thank you for this! Does this tweak have an impact on battery life?
Click to expand...
Click to collapse
Nothing too noticeable in my experience between stock and forced.

skura91 said:
if you want play COD with 120hz just use [App]Galaxy Max Hz ,
i play on mine s22 with very high graphic quality and force 120hz with this app
Click to expand...
Click to collapse
That's still not 120FPS though, alls it is doing os putting out 120Hz.

Thank you for good article.
Is there any way to fix 90 or 96Hz not 120Hz?

Doesn't work anymore on August update

leonbarroso said:
Doesn't work anymore on August update
Click to expand...
Click to collapse
For my Tab 8, on newest firmware I had to change the min_refresh_rate value to 120. Leaving the peak_refresh_rate at 0.1 Instantly locked to 120.

Actually tested this on my s22+ and the result was me having "grey" screen instead of black in 24hz, just deleted the "peak" and "min" values and restarted and was solved! If anyone getting this, that is the solution.

does it work on s22 ultra in agust 2022 update?

safereg said:
does it work on s22 ultra in agust 2022 update?
Click to expand...
Click to collapse
Re-applied just now and it seems to without any issues.

Any way to use system table or other means to allow adaptive refresh when battery saver is enabled? Even if peak is still 60 fps with battery saver on, seems like it would still improve battery life to have it drop down to 24 or whatever it normally does when there is no motion, though I may be completely wrong.

Why can't Samsung give what we want in the first place? Why don't we have the freedom of choosing what refresh rate our phones runs on, like for ffs

pschoolmeester said:
Any way to use system table or other means to allow adaptive refresh when battery saver is enabled? Even if peak is still 60 fps with battery saver on, seems like it would still improve battery life to have it drop down to 24 or whatever it normally does when there is no motion, though I may be completely wrong.
Click to expand...
Click to collapse
Not that I could find.. They fixed system table modifications for what you're asking for with One UI 4.0's release. Galaxy Max Hz App *might* be able to accomplish this but I'm not entirely sure.

AmmarHaseeb said:
Why can't Samsung give what we want in the first place? Why don't we have the freedom of choosing what refresh rate our phones runs on, like for ffs
Click to expand...
Click to collapse
The Beta Moderator's reasoning was that the phone's hardware couldn't handle the screen running up to 120Hz in every single activity.. part of that is proven incorrect and the rest I can't vouch for because no matter what I do some apps just refuse to go higher than 60Hz.