But Xas3d Halflife homebrew app has it..As far as I know, sysclk and popular overclocking tools have a limitation based on what's safe for the battery.
It's well known the Switch can go to higher clocks, but you would be quickly ruining your unit's battery by going above the set limits.
I don't really think they will add higher clocks, ever.
Why not let us users decide for ourselve what or what not to do.I see your point, but most devs are probably going to lean on the safe side and go with what's safe for the battery. They would rather have someone like you who doesn't use the Switch without charger slightly upset than someone who always or often uses their Switch with the battery extremely upset that their battery is messed up.
Well not sureAnd have you checked if it's working? Because 1785 is OS limitation, not overclock tools. 1912 shouldn't work, it would be changed to 1785.
I tried any overclocking in xash3d even lower ones but not sure how to apply. I choose via touchscreen and press Ok I guess? If I return to the screen it is still on the chosen speed. However Status monitor keep saying 1020 mhz cpu. So I guess the overclocking is not working at all for any speed in xash3d. (anymore)And have you checked if it's working? Because 1785 is OS limitation, not overclock tools. 1912 shouldn't work, it would be changed to 1785.
From 8.0.0 Horizon is using different service (clkrst). Before it was pcv. So if dev didn't update OC functions, then it will work only under 8.0.0.Why not let us users decide for ourselve what or what not to do.
--------------------- MERGED ---------------------------
Well not sure
I tried any overclocking in xash3d even lower ones but not sure how to apply. I choose via touchscreen and press Ok I guess? If I return to the screen it is still on the chosen speed. However Status monitor keep saying 1020 mhz cpu. So I guess the overclocking is not working at all for any speed in xash3d. (anymore)
Maybe it did use to work at different FW, who knows.
That must be it then. Though 1912 Probably worked at some point.. It is not there without reason I like to believe.From 8.0.0 Horizon is using different service (clkrst). Before it was pcv. So if dev didn't update OC functions, then it will work only under 8.0.0.
Maybe we can overlimit these OS limits of the overclock with CFW?.. 'cause in L4T for Switch there's also 3 new tiers of the CPU freq. available for the user:Because 1785 is OS limitation

It doesn't kill battery if you almost exclusively use the Switch in docked mode right? Why can't they just cap handheld to 1785MHz if that's the case?Maybe we can overlimit these OS limits of the overclock with CFW?.. 'cause in L4T for Switch there's also 3 new tiers of the CPU freq. available for the user:
- 1887 MHz,
- 1989 MHz, and
- 2091 MHz.
Maybe we can overlimit these OS limits of the overclock with CFW?.. 'cause in L4T for Switch there's also 3 new tiers of the CPU freq. available for the user:
- 1887 MHz,
- 1989 MHz, and
- 2091 MHz.

