Homebrew RELEASE sys-clk under/overclocking sysmodule

  • Thread starter Thread starter m4xw
  • Start date Start date
  • Views Views 592,508
  • Replies Replies 1,390
  • Likes Likes 90
Could someone test some tweaks for Travis Strikes Again ?

Tweak as you see fit, this here is to save some battery VIA the gpu at lowest official clock versus 384.

Code:
#Travis Strikes Again
[010011600c946000]
handheld_charging_cpu=1122
handheld_cpu=1122
handheld_gpu=307
 
  • Like
Reactions: Mambila2001
What???


This is my log, with no over/underclocking done (no config.ini), launching Breath of the Wild (01007EF00011E000).

Code:
=== sys-clk boot ===
Ready
* ApplicationTid changed to: 0100000000001000
* cpu clock is now 1020000000
* gpu clock is now 307200000
* mem clock is now 1331200000
[cfg] reading /config/sys-clk/config.ini
[cfg] Warning: File loading error while reading /config/sys-clk/config.ini
* ApplicationTid changed to: 01007EF00011E000
* gpu clock is now 460800000
* ApplicationTid changed to: 0100000000001000
* gpu clock is now 307200000
* Console profile changed to: handheld_charging_official
* ApplicationTid changed to: 01007EF00011E000
* gpu clock is now 460800000
* ApplicationTid changed to: 0100000000001000
* gpu clock is now 307200000

Booted, launched Zelda, quit out, put on charger, launched Zelda again, quit out.


I mean, technically it uses 460.8 MHz instead of 460 MHz, but i mean, come the fuck on.


I don't look forward to testing every single title's stock frequencies to hard set them, just to be able to underclock effectively.

This is something I'm willing to change, but I gave you the temp solution until sys-clk is updated
 
can someone make presets for these games :
- Fate Extella/Link : the graphic is awful on handheld but docked isn't so bad
- Fairy Fencer Advent : framerate is totally awful on handheld
- Warriors Orochi 4 : same as above

thanks in advance :))))
 
can someone make presets for these games :
- Fate Extella/Link : the graphic is awful on handheld but docked isn't so bad
- Fairy Fencer Advent : framerate is totally awful on handheld
- Warriors Orochi 4 : same as above

thanks in advance :))))
It's probably the easiest way to try doing it yourself. If you have sys-ftpd running in the background it's really easy to adjust the values while you are playing the game and see how the performance changes right away. Graphics might be hardcoded for the portable profile, so overclocking won't do anything in that case. Bad framerate might be fixable though. Once you're satisfied with it you can submit it, so it can be used by other people as well. ^^
 
Last edited by Trice,
It's probably the easiest way to try doing it yourself. If you have sys-ftpd running in the background it's really easy to adjust the values while you are playing the game and see how the performance changes right away. Graphics might be hardcoded for the portable profile, so overclocking won't do anything in that case. Bad framerate might be fixable though. Once you're satisfied with it you can submit it, so it can be used by other people as well. ^^
alright.. so with this sys-ftpd i can change value in config.ini ? or i just copy paste replace or something ?
 
alright.. so with this sys-ftpd i can change value in config.ini ? or i just copy paste replace or something ?
Yeah, you connect to your Switch via an FTP client from your PC and from there you can just change the config.ini and it will reload it on the fly. In the log you can also check what the title id of the game that you're launching is and that it applies the new values correctly after you added a config for it. It's usually best to start from the base configuration and then just increase the values step by step until you're satisfied with the result or don't see any noticeable improvements.
 
Yeah, you connect to your Switch via an FTP client from your PC and from there you can just change the config.ini and it will reload it on the fly. In the log you can also check what the title id of the game that you're launching is and that it applies the new values correctly after you added a config for it. It's usually best to start from the base configuration and then just increase the values step by step until you're satisfied with the result or don't see any noticeable improvements.
got it. thanks for the explanation, gotta try this soon
 
This is something I'm willing to change, but I gave you the temp solution until sys-clk is updated
I didn't want to come across as entitled or something, and i'm sorry if i did. I guess i just wasn't sure if my point came across. I'm really happy to have this app.


I also noticed that problem that a poster earlier in the thread spoke of:
Been working on setting up values for a few games. One thing I think I noticed is the QLaunch settings for underclocking. Its nice to have the unit running cooler when not in use. However I think when you start a new game without specific values, instead of going back to default, it appears to remain at whatever last clock was set.
If I have a game not listed, it'll stay at whatever QLaunch was set at.

I noticed this because I had the QLaunch lower for docked mode, since I have the unit sitting around for hours, especially if using FTP, etc... Loaded up some games and they were running horribly, checked logs and saw that unless specified, the clocks were not returning to default values.

I also underclocked QLaunch in handheld and started Aragami: Shadow Edition and it ran TERRIBLY. Like, sub-10 FPS in the main menu. So i checked the log and lo and behold, the system underclocked in the home menu, but then didn't adjust the clocks to normal levels when i started the game.
Strangely, it doesn't happen for all games. I started Okami afterwards, and that game DID adjust to proper clocks ater starting from the underclocked home menu. I then switched over to Aragami from Okami, and Aragami used the QLaunch clocks again.

Code:
=== sys-clk boot ===
Ready
* ApplicationTid changed to: 0100000000001000
* cpu clock is now 1020000000
* gpu clock is now 307200000
* mem clock is now 1331200000
[cfg] reading /config/sys-clk/config.ini
* Setting cpu clock to 816000000
* Setting gpu clock to 230400000
* Setting mem clock to 800000000
* cpu clock is now 816000000
* gpu clock is now 230400000
* mem clock is now 800000000
* ApplicationTid changed to: 010071800BA74000 (<- Aragami)
* ApplicationTid changed to: 0100000000001000
* ApplicationTid changed to: 0100276009872000 (<- Okami)
* cpu clock is now 1020000000
* gpu clock is now 384000000
* mem clock is now 1331200000
* ApplicationTid changed to: 0100000000001000
* gpu clock is now 307200000
* Setting cpu clock to 816000000
* Setting gpu clock to 230400000
* Setting mem clock to 800000000
* ApplicationTid changed to: 010071800BA74000 (-< Aragami)
* cpu clock is now 816000000
* gpu clock is now 230400000
* mem clock is now 800000000

Note that i have no config entries for either Okami or Aragami, only for QLaunch.
 
I notice some apps have periodic requests for default clocks, others do not.
So if you play some games for a bit, you might see the clocks keep getting reset, then sys-clk changes them back. (QLaunch does this too while docked and charging).

Not sure if this is okay to leave, or if its counter-productive (clocks going back and forth)?

Other titles the clocks get changed, and never "reset" again.

I find it's best to add every title as you install them, if using a modified QLaunch to ensure desired performance. But does end up making the config bigger... I found configs bigger than 25KB can error out.
 
so except for apparently something with retroarch, is there anything to look out for while using this?
is there an on/off homebrew?
 
I didn't want to come across as entitled or something, and i'm sorry if i did. I guess i just wasn't sure if my point came across. I'm really happy to have this app.


I also noticed that problem that a poster earlier in the thread spoke of:


I also underclocked QLaunch in handheld and started Aragami: Shadow Edition and it ran TERRIBLY. Like, sub-10 FPS in the main menu. So i checked the log and lo and behold, the system underclocked in the home menu, but then didn't adjust the clocks to normal levels when i started the game.
Strangely, it doesn't happen for all games. I started Okami afterwards, and that game DID adjust to proper clocks ater starting from the underclocked home menu. I then switched over to Aragami from Okami, and Aragami used the QLaunch clocks again.

Code:
=== sys-clk boot ===
Ready
* ApplicationTid changed to: 0100000000001000
* cpu clock is now 1020000000
* gpu clock is now 307200000
* mem clock is now 1331200000
[cfg] reading /config/sys-clk/config.ini
* Setting cpu clock to 816000000
* Setting gpu clock to 230400000
* Setting mem clock to 800000000
* cpu clock is now 816000000
* gpu clock is now 230400000
* mem clock is now 800000000
* ApplicationTid changed to: 010071800BA74000 (<- Aragami)
* ApplicationTid changed to: 0100000000001000
* ApplicationTid changed to: 0100276009872000 (<- Okami)
* cpu clock is now 1020000000
* gpu clock is now 384000000
* mem clock is now 1331200000
* ApplicationTid changed to: 0100000000001000
* gpu clock is now 307200000
* Setting cpu clock to 816000000
* Setting gpu clock to 230400000
* Setting mem clock to 800000000
* ApplicationTid changed to: 010071800BA74000 (-< Aragami)
* cpu clock is now 816000000
* gpu clock is now 230400000
* mem clock is now 800000000

Note that i have no config entries for either Okami or Aragami, only for QLaunch.

No worries.
Yea this is what is happening the "do not change" behavior that is currently in makes your underclocked configuration stay
 
How do I use this? I just renamed the folder and copied/moved the files.
After that it will turn automatically using the configuration?
How do I know that game's title to be used in the configuration?
 
How do I use this? I just renamed the folder and copied/moved the files.
After that it will turn automatically using the configuration?
How do I know that game's title to be used in the configuration?
Use ftp to view the log after running the game. Sys-clk will tell you the title ID. You can make changes to the ini and sys-clk will apply the clocks on the fly.
 
  • Like
Reactions: p-sam
I didn't want to come across as entitled or something, and i'm sorry if i did. I guess i just wasn't sure if my point came across. I'm really happy to have this app.


I also noticed that problem that a poster earlier in the thread spoke of:


I also underclocked QLaunch in handheld and started Aragami: Shadow Edition and it ran TERRIBLY. Like, sub-10 FPS in the main menu. So i checked the log and lo and behold, the system underclocked in the home menu, but then didn't adjust the clocks to normal levels when i started the game.
Strangely, it doesn't happen for all games. I started Okami afterwards, and that game DID adjust to proper clocks ater starting from the underclocked home menu. I then switched over to Aragami from Okami, and Aragami used the QLaunch clocks again.

Code:
=== sys-clk boot ===
Ready
* ApplicationTid changed to: 0100000000001000
* cpu clock is now 1020000000
* gpu clock is now 307200000
* mem clock is now 1331200000
[cfg] reading /config/sys-clk/config.ini
* Setting cpu clock to 816000000
* Setting gpu clock to 230400000
* Setting mem clock to 800000000
* cpu clock is now 816000000
* gpu clock is now 230400000
* mem clock is now 800000000
* ApplicationTid changed to: 010071800BA74000 (<- Aragami)
* ApplicationTid changed to: 0100000000001000
* ApplicationTid changed to: 0100276009872000 (<- Okami)
* cpu clock is now 1020000000
* gpu clock is now 384000000
* mem clock is now 1331200000
* ApplicationTid changed to: 0100000000001000
* gpu clock is now 307200000
* Setting cpu clock to 816000000
* Setting gpu clock to 230400000
* Setting mem clock to 800000000
* ApplicationTid changed to: 010071800BA74000 (-< Aragami)
* cpu clock is now 816000000
* gpu clock is now 230400000
* mem clock is now 800000000

Note that i have no config entries for either Okami or Aragami, only for QLaunch.

Next release will accomodate for those lazy games, be sure to also remove the game stock freqs you temporarily added
 

Site & Scene News

Popular threads in this forum