I have a bunch of settings for mostly battery saving. I'll look into contributing them by next week. Been slammed with work.
The codebase has not been updated yet.@m4xw
I've compiled from source with libnx 2.1.0-1 / devkitARM r13-4 with msys2 on windows. I'm getting an error when I boot and I don't know why.
[2019-03-30 16:43:47] [!] ASSERT_RESULT_OK: pminfoGetTitleId
RC: [0x20f] 0015-0001
in C:/sys-clk/src/process_management.cpp:52
[2019-03-30 16:43:50] Ready
[2019-03-30 16:43:50] [!] ASSERT_RESULT_OK: pminfoGetTitleId
RC: [0x20f] 0015-0001
in C:/sys-clk/src/process_management.cpp:52
The codebase has not been updated yet.
Dunno why you compile from source.
Thanks, I'm just starting to look into this sysmodule and the 1st thing that came to my mind was to look for a list of good settings for battery saving and/or for overclocking.I have a bunch of settings for mostly battery saving. I'll look into contributing them by next week. Been slammed with work.
Thanks, I'm just starting to look into this sysmodule and the 1st thing that came to my mind was to look for a list of good settings for battery saving and/or for overclocking.
If I may suggest, maybe create a google sheet so that anyone can contribute?
Thanks, I'm just starting to look into this sysmodule and the 1st thing that came to my mind was to look for a list of good settings for battery saving and/or for overclocking.
If I may suggest, maybe create a google sheet so that anyone can contribute?
Before I forget, here is the one from on my device. It's mostly settings for handheld, not much in terms of charging profiles, yet. Also has some docked settings that provide lower clocks in most instances in order to keep the unit cooler. Thus, increase longevity of the unit (theoretically).
Some of it is copy and pasted, based on my memory of the title and my best guess of its needs.
There are a few instances (Dead Cells and Cities for example) where I pushed the GPU to 460, and reduced Mem and CPU clocks.
Now my educated guess is power consumption probably is in this order from most to least.
GPU - Using most power, thus I attempted to push that clock down when possible.
CPU - I pushed some clock rates down, no clue if this creates "race-to-idle" scenarios, which would be counter-productive.
Memory Clocks - Likely uses the least power consumption.
Feel free to correct me if I am wrong, or if anyone has any further info about what uses the most and if we encounter race-to-idle situations.
Also feel free to use this as a base for a spreadsheet, github, whatever. As I have limited time for a few weeks to put in the work.
It's not commented, as early on I was getting issues with the ini file being too big. Haven't attempted to see if that still happens.
Almost forgot! Homebrew and forwarders section, most of those NSPs I made myself, so you would need to edit the TitleID's accordingly!
Before I forget, here is the one from on my device. It's mostly settings for handheld, not much in terms of charging profiles, yet. Also has some docked settings that provide lower clocks in most instances in order to keep the unit cooler. Thus, increase longevity of the unit (theoretically).
Some of it is copy and pasted, based on my memory of the title and my best guess of its needs.
There are a few instances (Dead Cells and Cities for example) where I pushed the GPU to 460, and reduced Mem and CPU clocks.
Now my educated guess is power consumption probably is in this order from most to least.
GPU - Using most power, thus I attempted to push that clock down when possible.
CPU - I pushed some clock rates down, no clue if this creates "race-to-idle" scenarios, which would be counter-productive.
Memory Clocks - Likely uses the least power consumption.
Feel free to correct me if I am wrong, or if anyone has any further info about what uses the most and if we encounter race-to-idle situations.
Also feel free to use this as a base for a spreadsheet, github, whatever. As I have limited time for a few weeks to put in the work.
It's not commented, as early on I was getting issues with the ini file being too big. Haven't attempted to see if that still happens.
Almost forgot! Homebrew and forwarders section, most of those NSPs I made myself, so you would need to edit the TitleID's accordingly!
This is awesome, do you want somebody to add this to the official repo? I can make a pull request myself if you don't mind.
Yes, that's the method to use if you want to use OC for homebrew software like RetroArch.What if I overclock a certain game and use that game to launch homebrew menu, will the module still kick in?
Yes, that's the method to use if you want to use OC for homebrew software like RetroArch.
Only for CPU, not for the GPU and RAM. Those you can only overclock with sys-clk.RetroArch has overclocking builtin btw, but still yes
The devs hate GatewayAnyone bother getting this to work on SXOS yet? lol
You still need to configure your config.ini file for sys-clk to read. What this only mean, in my understanding, is that if you set a different clock rate on handheld vs on docked, it will automatically set the docked clock rates when you docked your switch and vice-versa even while you're in game.does this mean it over clocks automatically when docked or under clocks without me setting the config file per game or is it based on my config file per game. I believe I have this installed from Kosmos but I don’t think it’s active but I think I’m going to set it up.