Toggle sidebar

Homebrew RELEASE sys-clk under/overclocking sysmodule

  • Thread starter Thread starter m4xw
  • Start date Start date
  • Views Views 592,555
  • Replies Replies 1,390
  • Likes Likes 90
I made a test config of just QLaunch
Code: 
#QLaunch cooling profile
[0100000000001000]
handheld_cpu=816
handheld_gpu=230
handheld_mem=800
handheld_charging_cpu=816
handheld_charging_gpu=230
handheld_charging_mem=800
handheld_charging_usb_cpu=816
handheld_charging_usb_gpu=230
handheld_charging_usb_mem=800
handheld_charging_official_cpu=816
handheld_charging_official_gpu=230
handheld_charging_official_mem=800
docked_cpu=918
docked_gpu=460
docked_mem=1065

Same error, and sys-clk stops. So then another test...
Code: 
#QLaunch cooling profile
[0100000000001000]
docked_cpu=918
docked_gpu=460
docked_mem=1065
handheld_charging_cpu=816
handheld_charging_gpu=230
handheld_charging_mem=800
handheld_charging_usb_cpu=816
handheld_charging_usb_gpu=230
handheld_charging_usb_mem=800
handheld_charging_official_cpu=816
handheld_charging_official_gpu=230
handheld_charging_official_mem=800
handheld_cpu=816
handheld_gpu=230
handheld_mem=800

Worked fine, so I went in and redid the bigger list in the correct formatting...
No dice, so memory? File was 29KB or so.

Then went ahead and removed all
Code: 
handheld_charging_cpu=
handheld_charging_gpu=
handheld_charging_mem=
handheld_charging_usb_cpu=
handheld_charging_usb_gpu=
handheld_charging_usb_mem=
handheld_charging_official_cpu=
handheld_charging_official_gpu=
handheld_charging_official_mem=

So back to just the docked and handheld configs, file is roughly 10KB, works fine...
 
mdmachine said:
I made a test config of just QLaunch
Code: 
#QLaunch cooling profile
[0100000000001000]
handheld_cpu=816
handheld_gpu=230
handheld_mem=800
handheld_charging_cpu=816
handheld_charging_gpu=230
handheld_charging_mem=800
handheld_charging_usb_cpu=816
handheld_charging_usb_gpu=230
handheld_charging_usb_mem=800
handheld_charging_official_cpu=816
handheld_charging_official_gpu=230
handheld_charging_official_mem=800
docked_cpu=918
docked_gpu=460
docked_mem=1065

Same error, and sys-clk stops. So then another test...
Code: 
#QLaunch cooling profile
[0100000000001000]
docked_cpu=918
docked_gpu=460
docked_mem=1065
handheld_charging_cpu=816
handheld_charging_gpu=230
handheld_charging_mem=800
handheld_charging_usb_cpu=816
handheld_charging_usb_gpu=230
handheld_charging_usb_mem=800
handheld_charging_official_cpu=816
handheld_charging_official_gpu=230
handheld_charging_official_mem=800
handheld_cpu=816
handheld_gpu=230
handheld_mem=800

Worked fine, so I went in and redid the bigger list in the correct formatting...
No dice, so memory? File was 29KB or so.

Then went ahead and removed all
Code: 
handheld_charging_cpu=
handheld_charging_gpu=
handheld_charging_mem=
handheld_charging_usb_cpu=
handheld_charging_usb_gpu=
handheld_charging_usb_mem=
handheld_charging_official_cpu=
handheld_charging_official_gpu=
handheld_charging_official_mem=

So back to just the docked and handheld configs, file is roughly 10KB, works fine...
Click to expand...

You're not forced to duplicate all the handheld configs anyway, because yours dont change, check the readme for more info.
 
Code: 
If charging, sys-clk will look for the frequencies in that order, picking the first found:

   *Charger specific config (USB or Official): handheld_charging_usb_X or handheld_charging_official_X
Shouldn't it be the other way around and check for official charger first, since it has the highest limit?

Now that i think about it, what IS usb charging? How is USB charging different from "normal" charging, and how is it determined whether the charger is an official one or not?

--------------------- MERGED ---------------------------

Wait, i think i might get it now? Charging is the catch-all for charged gameplay for both normal USB and official charger, so if you specifically set USB and official, normal charging never applies. It's a fall-back for "no specific charging profile is defined, but we're on some kind of charger".

So,let me get this straight: if i defined an overclock only for USB charging, and hooked the console up to an official charger, the console will NOT overclock because:
* specific official clock doesn't exist ->
* fall-back charging clock doesn't exist ->
* hand-held clock doesn't exist ->
* use stock clock

Or is there still some kind of priority where official charging will at least use the lower-tier "usb" one if no other are defined?
 
p-sam said:
You're not forced to duplicate all the handheld configs anyway, because yours dont change, check the readme for more info.
Click to expand...

Maybe that was bad example, the only reason the QLaunch is all the same, is that's the clock rates I want when going back home. So what if I am on a charger and I have a active profile that changes all the clocks while charging? When I go back home, I need that specific setting in QLaunch to "reset".

I can leave alone any game settings that are equal to my QLaunch settings, but when your adding allot it just seemed easier.

I am going to try adding just the
Code: 
handheld_charging_cpu=
handheld_charging_gpu=
handheld_charging_mem=

To all my profiles so its like so:
Code: 
docked_cpu=
docked_gpu=
docked_mem=
handheld_charging_cpu=
handheld_charging_gpu=
handheld_charging_mem=
handheld_cpu=
handheld_gpu=
handheld_mem=
Then remove any = stuff, and see if it'll parse it.
 
Has someone messed around with Warframe? It's free game, also it use heavy dynamic resolution :)
 
Still not sur eon the priority of the charging profiles. Also is it possible to underclock a title in handheld, but go back to stock clocks when charging? Stock can differ between games apparently (only gpu?), so making a profile =0 to mean stock frequency would be great. Something like this:

handheld_charging_gpu=0
handheld_gpu=230

I'm assuming this doesn't work right now since =0 just means "ignore this" and it would use the handheld underclock when charging.
 
Krude said:
Still not sur eon the priority of the charging profiles. Also is it possible to underclock a title in handheld, but go back to stock clocks when charging? Stock can differ between games apparently (only gpu?), so making a profile =0 to mean stock frequency would be great. Something like this:

handheld_charging_gpu=0
handheld_gpu=230

I'm assuming this doesn't work right now since =0 just means "ignore this" and it would use the handheld underclock when charging.
Click to expand...
Indeed, but the readme contains the stock clock for GPU (either 307 or 384) so you can just put that
 
p-sam said:
Indeed, but the readme contains the stock clock for GPU (either 307 or 384) so you can just put that
Click to expand...
The idea is NOT having to manually find out the stock clock for every single game (BOTW seems to use 460 btw not 307 or 384) and to allow differentiation between a general "charging/not charging" in handheld.
 
Krude said:
The idea is NOT having to manually find out the stock clock for every single game (BOTW seems to use 460 btw not 307 or 384) and to allow differentiation between a general "charging/not charging" in handheld.
Click to expand...

Your message got thru the first time
 
Does main launcher have a title id, for which I can change clock speeds? It would be awesome to downclock everything to minimum when browsing games and settings.

[edit] Oh wait, it's called QLaunch and it is posted just on top of this page, right?
 
Last edited by dreambottle,
dreambottle said:
Does main launcher have a title id, for which I can change clock speeds? It would be awesome to downclock everything to minimum when browsing games and settings.

[edit] Oh wait, it's called QLaunch and it is posted just on top of this page, right?
Click to expand...

that's what I attempted to do. And noticed checking logs later that periodically the clocks were being set back to default. Sometimes all 3, sometimes just one random one here and there. They always get set back to what I defined by the module though.

Im not sure how long it is between these changes, when I sit around and try and watch, I didn't see the log change. But when I noticed it, the log was quite large. I noticed the most action in docked and charging. It happens much less, when in handheld mode.

I dont have any idea how long until/if the clocks "reset"? Or, if it changing the clocks sometimes is counter-productive?
 
ZachyCatGames said:
there aren’t any retail titles that use 460mhz
Click to expand...
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.
 
Last edited by Krude,
Krude said:
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.
Click to expand...
hmm? Maybe they changed it in a update or something then ¯\_(ツ)_/¯
 

Site & Scene News

Go to forum More news

Popular threads in this forum

Dusk for switch (TLoZ Twilight Princess port)

Homebrew  New Homebrew "Foil Server"?

Homebrew  Full List of N64 Recompilation Switch ports

Hacking  WiFi chip failing and can't boot. is it possible to enable Airplane Mode by editing system save files directly?

Homebrew Tutorial Translation Project  CS2SX — Write Nintendo Switch Homebrew in C#

Is it fixable

Homebrew  Sonic Unleashed Recompiled (Homebrew Port)

Hacking Emulation  Switch Prod Keys downloading from sites okay?