Refactoring for UberHand 2.3.1

Sources/NXVenom/switch/.packages/SC Wizard/Guides/Test Stability/config.ini

@@ -0,0 +1,8 @@
+[*CPU]
+text_source '/switch/.packages/SC Wizard/Guides/txt/stability/cpu.txt'
+
+[*GPU]
+text_source '/switch/.packages/SC Wizard/Guides/txt/stability/gpu.txt'
+
+[*RAM]
+text_source '/switch/.packages/SC Wizard/Guides/txt/stability/ram.txt'

Sources/NXVenom/switch/.packages/SC Wizard/Guides/config.ini

@@ -0,0 +1,28 @@
+[*Safety Disclaimer]
+text_source '/switch/.packages/SC Wizard/Guides/txt/safety.txt'
+
+[*Switch Limits]
+; Mariko
+text_source '/switch/.packages/SC Wizard/Guides/txt/mariko/limits.txt'
+
+[*Switch Limits]
+; Erista
+text_source '/switch/.packages/SC Wizard/Guides/txt/erista/limits.txt'
+
+[*OC Settings]
+; Mariko
+text_source '/switch/.packages/SC Wizard/Guides/txt/mariko/oc_settings.txt'
+
+[*OC Settings]
+; Erista
+text_source '/switch/.packages/SC Wizard/Guides/txt/erista/oc_settings.txt'
+
+[*Clock Settings]
+; Mariko
+text_source '/switch/.packages/SC Wizard/Guides/txt/mariko/clock_settings.txt'
+
+[*Clock Settings]
+; Erista
+text_source '/switch/.packages/SC Wizard/Guides/txt/erista/clock_settings.txt'
+
+[>Test Stability]

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/erista/clock_settings.txt

@@ -0,0 +1,21 @@
+Erista Max Plugged [HAC-001(-01), HEG-001]
+
+- CPU: 2295MHz (Use only with UV5 on good speedo), 2091MHz (Use only with UV3-5), 1785MHz (UV is recommended)
+- GPU: 998MHz (Use it only with UV2, try to avoid going over 1000mv), 921MHz (safe, use it with undervolt)
+- RAM: 1862MHz-2133MHz+ (whatever is stable and within 1175mv VDD2) (HEAVILY DEPENDENT ON RAM TYPE)
+
+---------------------------------------------------------------
+
+Erista Max Safe Clocks on Battery [HDH-001]
+
+- CPU: 1785MHz
+- GPU: 460MHz
+- RAM: 1862MHz-2133MHz+ (whatever is stable and within 1175mv VDD2) (HEAVILY DEPENDENT ON RAM TYPE)
+
+Note: Drawing over 8W on battery will cause battery issues. Please avoid doing that for extended periods!
+
+---------------------------------------------------------------
+
+# Troubleshooting
+
+If Switch won't boot into EMUNAND CPU UV level is too high, lower it or set it to 0.

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/erista/limits.txt

@@ -0,0 +1,51 @@
+Erista CPU Limits:
+
+- The Erista CPU limit of 15A is reached at 1785MHz without any UV or 2091MHz with CPU UV1.
+
+---------------------------------------------------------------
+
+Erista GPU Limits:
+
+- The Erista GPU limit of 15A is reached at 921MHz without GPU UV with moderate speedos.
+
+Be extremely careful if you disable GPU scheduling. This will hit the PMIC limit very hard!
+
+---------------------------------------------------------------
+
+GPU Scheduling:
+
+- On: ~96.7%
+- Off: ~99.7%
+
+---------------------------------------------------------------
+
+Charger IC Limit:
+
+- 18W limit restricts overclocking for Erista units. This is the main limiting factor, but the PMIC current limits for CPU and GPU will be reached first.
+
+---------------------------------------------------------------
+
+# Monitoring Your Switch
+
+- Use status monitor overlay to indicate if you've bypassed the charger IC limit (e.g., -1W displayed while charging).
+- To get the best results, be sure your battery is 10-90% to display the real charging
+
+---------------------------------------------------------------
+
+# Checking Speedo and RAM Type
+
+1. Boot Hekate.
+2. Go to Console Info > HW & Fuses.
+3. Note your DRAM ID, CPU Speedo 0, CPU Speedo 2, and SoC Speedo.
+
+Speedos range from approximately 1980 to 2200, with SoC speedos ranging from approximately 1899 to 2050. An Erista with a higher speedo requires less voltage to meet the same clock speed compared to another Switch with a lower speedo. A speedo of 2100 is generally considered good.
+
+---------------------------------------------------------------
+
+# RAM Types
+
+There are various RAM types for Erista, and better types can reach higher clocks, require lower voltages, and support tighter timings at the same clocks compared to worse types. Not only do RAM types matter, but RAM bin matters, meaning that worse RAM types can outperform higher RAM types. Here are some RAM types:
+
+- Samsung MGCH
+- Hynix NLE
+- Micron WT:C

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/erista/oc_settings.txt

@@ -0,0 +1,25 @@
+CPU Settings
+
+- Boost Clock: 2091MHz if you use UV3, otherwise use 1785MHz
+- Undervolt Mode: 1-5 (use the max that is stable)
+- Vmin: 800
+- Voltage Limit: 1225mv
+
+---------------------------------------------------------------
+
+GPU Settings
+
+- Undervolt Mode: 2
+- Vmin: 740-780mv
+- Voltage Offset: 0-30
+
+If you want to safely use 998Mhz gpu, you need to keep gpu volt under 950 (slightly differs depending on iddq and temperature)
+
+---------------------------------------------------------------
+
+RAM Settings
+
+- DRAM Timing:
+AUTO_ADJ: Auto adjust mtc table with LPDDR4 3733 Mbps specs, 16Gb density. Change timing with Advanced Config (Default)
+NO_ADJ: Use 1600 mtc table without adjusting (Timing becomes tighter if you raise dram clock)
+- DVB Shift: 1-4 (Boosting the SoC voltage helps stabilize RAM, especially at high frequencies like 1996MHz+)

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/mariko/clock_settings.txt

@@ -0,0 +1,43 @@
+Mariko Max Safe on Battery [HAC-001(-01), HEG-001]
+
+- CPU: 1963MHz
+- GPU: 998MHz
+- RAM: 2133MHz-2500MHz+ (whatever is stable and within 1175mv VDD2)
+
+Note: Drawing over 8W on battery will cause battery issues. Please avoid doing that for extended periods!
+
+---------------------------------------------------------------
+
+Switch Lite Max Safe Clocks on Battery [HDH-001]
+
+- CPU: 1785MHz
+- GPU: 921MHz
+- RAM: 2133MHz-2500MHz+ (whatever is stable and within 1175mv VDD2)
+
+Note: Drawing over 6.5W on battery will cause battery issues. Please avoid doing that for extended periods!
+
+Switch Lite limits are lower due to the 12W board power limit, but counts as Mariko for all other purposes.
+
+---------------------------------------------------------------
+
+Mariko Max Clocks Docked and Plugged [HAC-001(-01), HEG-001]
+
+- CPU: 2295MHz on CPU speedo < 1650, 2601MHz on CPU speedo ≥ 1650 with undervolt
+- GPU: 1152MHz (1228MHz and above on GPU speedo ≥ 1650 with undervolt, otherwise lower)
+- RAM: 2133MHz-2500MHz+ (whatever is stable and within 1175mv VDD2)
+
+---------------------------------------------------------------
+
+Switch Lite Max Clocks Plugged [HDH-001]
+
+- CPU: 1963MHz (2295MHz on CPU speedo < 1650, 2397 on CPU speedo ≥ 1650 with undervolt)
+- GPU: 998MHz (1228MHz on GPU speedo ≥ 1650 with undervolt, otherwise lower)
+- RAM: 2133MHz-2500MHz+ (whatever is stable and within 1175mv VDD2)
+
+Switch Lite limits are lower due to the 12W board power limit, but counts as Mariko for all other purposes.
+
+---------------------------------------------------------------
+
+Troubleshooting
+
+If Switch won't boot into EMUNAND CPU UV level is too high, lower it or set it to 0.

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/mariko/limits.txt

@@ -0,0 +1,53 @@
+Mariko CPU Limits:
+
+- 5A limit reached at 2397MHz (CPU UV1) or 2295MHz (< 1650 CPU speedo).
+- Use higher UV levels to avoid exceeding the PMIC limit.
+
+---------------------------------------------------------------
+
+Mariko GPU Limits:
+
+- 10A limit reached at 1228MHz (GPU UV1) with moderate speedos (1650 GPU clock).
+- Disabling GPU scheduling overloads the PMIC, potentially causing damage.
+
+---------------------------------------------------------------
+
+GPU Scheduling:
+
+- On: ~96.7%
+- Off: ~99.7%
+
+Warning: Disabling GPU Scheduling will significantly increase power draw. Use it with caution.
+
+---------------------------------------------------------------
+
+Charger IC Limit:
+
+18W limit restricts overclocking for both Erista and Mariko units (12W on Switch Lite). This is the main limiting factor, but the PMIC current limits for CPU and GPU will be reached first.
+
+---------------------------------------------------------------
+
+Monitoring Your Switch
+
+- Use status monitor overlay to indicate if you've bypassed the charger IC limit (e.g., -1W displayed while charging).
+- To get the best results, be sure your battery is 10-90% to display the real charging
+
+---------------------------------------------------------------
+
+# Checking Speedo and RAM Type
+
+1. Boot Hekate.
+2. Go to Console Info > HW & Fuses.
+3. Note your DRAM ID, CPU Speedo 0, CPU Speedo 2, and SoC Speedo.
+4. Speedos typically range from 1450 to 1750. A higher speedo means less voltage is needed for the same clock speed. A speedo of 1650 is generally considered good.
+
+---------------------------------------------------------------
+
+RAM Tiers (Higher is better)
+
+GOD-tier - NEI/NEE, WT:B
+S-tier - AA-MGCR, AA-MGCL
+A-tier - WT:F
+B-tier - AM-MGCJ, WT:E
+C-tier - AB-MGCL
+D-tier - NME

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/mariko/oc_settings.txt

@@ -0,0 +1,41 @@
+CPU Settings:
+
+- Boost Clock:
+2400 MHz (Low Speedo or High Freq UV 1-5)
+2600 MHz (Speedo > 1650 or High Freq UV 6+)
+
+- Undervolt Mode: 1-4 (Increase if stable, find your highest stable value)
+
+- High Freq UV: 6-10 (Find your highest stable value). Just a few units can do 11-12, test carefully.
+
+- Low Freq Vmin: 590mv
+
+- High Freq Vmin: 720-750mv (Test for lower values if your CPU bin is good)
+
+- Voltage Limit: 1120mv (safe), 1160mv (use with caution), 1235 (unsafe for high clocks)
+
+---------------------------------------------------------------
+
+GPU Settings:
+
+- Undervolt Mode: 2
+
+- Vmin: AUTO
+
+- Vmax: 800mv
+
+- Speedo: (Input your value from HW & Fuses in Hekate)
+
+- Voltage Offset: 0 (Test 5, 10, or 15 with UV2, but check stability first)
+
+---------------------------------------------------------------
+
+RAM Settings:
+
+- DRAM Timing:
+AUTO_ADJ: Auto adjust mtc table with LPDDR4 3733 Mbps specs, 16Gb density. Change timing with Advanced Config (Default)
+NO_ADJ: Use 1600 mtc table without adjusting (Timing becomes tighter if you raise dram clock)
+
+- DVB Shift: 1-4 (Boosting the SoC voltage helps stabilize RAM, especially at high frequencies like 2400MHz+).
+
+- HP mode: 1

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/safety.txt

@@ -0,0 +1,5 @@
+!! WARNING !!
+
+Overclocking is inherently risky as it pushes the system beyond its original design. The risk level depends on how much you overclock and whether you stay within the limits of the chip and hardware.
+
+Unstable RAM overclocking can cause SYSNAND/EMUNAND corruption and SD card corruption, particularly if done on SYSNAND. Test the overclock settings on EMUNAND and back it up before using Switchcraft.

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/stability/cpu.txt

@@ -0,0 +1,15 @@
+Recommended Games for Testing CPU Undervolting (UV):
+
+Need for Speed: Hot Pursuit
+
+- Scenario:
+If the CPU undervolt is unstable, the game will crash in the main menu on the map at 1963 MHz and 60 fps (credits to B3711).
+- Testing Procedure:
+Leave the game running on the desired frequency for 15-30 seconds while on the map screen. Test every frequency carefully to ensure stability.
+
+Kirby and the Forgotten Land
+
+- Scenario:
+This game is suitable for testing low CPU Vmin using stock clock speed (1020mhz).
+- Testing Procedure:
+Run the game docked at 60 fps to observe for crashes or instability. Let it run for hours, it will crash after a few hours.

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/stability/gpu.txt

@@ -0,0 +1,21 @@
+Testing GPU stability using GPU voltage offsets or undervolting (UV3) can be challenging, as there are no good artificial stress tests available on the Homebrew Operating System (HOS). Therefore, we rely on games known to be more sensitive to unstable GPU voltages.
+
+---------------------------------------------------------------
+
+Signs of GPU Voltage Instability
+
+- GPU Voltage Glitches:
+Look for "disco lights," white flashes, or color distortions. These artifacts indicate that the GPU voltage is too low.
+- Crash and Hangs:
+If the GPU voltage is too low, games might crash or hang without showing any visual glitches.
+
+---------------------------------------------------------------
+
+Examples of GPU Voltage Instability
+
+Recommended Games for Testing GPU:
+
+- ANNO: Mutationem
+- Convergence: A League of Legends Story
+- SIFU
+- Pikmin 3 Deluxe

Sources/NXVenom/switch/.packages/SC Wizard/Guides/txt/stability/ram.txt

@@ -0,0 +1,44 @@
+A good application to test the ram is MemToolkitNX.
+
+Set the cpu and the ram to max to gather the highest bandwidth possible.
+Set the test type using DPAD right to 2x Memtester + BW Burn-in.
+Press A to start the test.
+Run the test 200-500 loops.
+
+This is good to find some errors, test the stability in game!
+
+---------------------------------------------------------------
+
+# Recommended Games for Testing RAM Stability
+
+Do those tests in docked mode for higher resource usage.
+
+- Game: Monster Hunter Stories 2: Wings of Ruin
+- Scenario: To test for unstable RAM, start the game and let the first 2 cutscenes to run. Look for artifacts.
+- Signs of Instability: Freezing, crashes, or unexpected restarts.
+
+- Game: The Legend of Zelda: Tears of the Kingdom (TOTK)
+- Scenario: To test for unstable RAM, leave your Switch running for approximately one hour on this game, it will crash, hang, or freeze when using unstable RAM. These games typically use a large amount of system resources.
+- Signs of Instability: Crashes, freezes, or hangs.
+
+- Game: Red Dead Redemption
+- Scenario: To test for unstable RAM, leave your Switch running for approximately one hour on this game, it will crash, hang, or freeze when using unstable RAM. These games typically use a large amount of system resources.
+- Signs of Instability: Crashes, hangs, or graphical corruption.
+
+- Game: Borderlands 3
+- Scenario: To test for unstable RAM, leave your Switch running for approximately one hour on this game, it will crash, hang, or freeze when using unstable RAM. These games typically use a large amount of system resources.
+- Signs of Instability: Pixel corruption, crashes, or system hangs.
+
+- Game: Borderlands: The Pre-Sequel
+- Scenario: Similar to Borderlands 3, it uses substantial resources, which can trigger instability in RAM.
+- Signs of Instability: Crashes, graphical corruption, or system hangs.
+
+- Game: Nier Automata
+- Scenario: Especially effective with 60 FPS cheats or graphical modifications that increase load.
+- Signs of Instability: Crashes, hangs, or visual glitches during high-stress scenes.
+
+- Game: Kirby and the Forgotten Land
+- Scenario: To test for unstable RAM, leave your Switch running for approximately one hour on this game, it will crash, hang, or freeze when using unstable RAM. These games typically use a large amount of system resources.
+- Signs of Instability: Crashes, hangs, or graphical corruption.
+
+Unstable RAM can cause graphical glitches, but more often leads to crashes or hangs.