Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/masagrator/Status-Monitor-Overlay
Monitor many stats of Nintendo Switch hardware
https://github.com/masagrator/Status-Monitor-Overlay
Last synced: 3 months ago
JSON representation
Monitor many stats of Nintendo Switch hardware
- Host: GitHub
- URL: https://github.com/masagrator/Status-Monitor-Overlay
- Owner: masagrator
- License: gpl-2.0
- Created: 2020-02-19T21:42:18.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2024-06-25T06:17:11.000Z (5 months ago)
- Last Synced: 2024-06-27T23:03:25.739Z (5 months ago)
- Language: C++
- Size: 1.16 MB
- Stars: 473
- Watchers: 14
- Forks: 31
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-switch-homebrew - Status Monitor Overlay - Monitor many stats of Nintendo Switch hardware (Homebrew / Tesla Overlays)
README
# Status Monitor Overlay
Monitor Your hardware in real time!This is an overlay homebrew dedicated to Nintendo Switch.
You need to have installed Tesla environment to use it.Tool contains six modes to choose, each one is explained [here](/docs/modes.md).
Overlay supports customizations through config file, more [here](/docs/config.md).If it's not working in dock, you need to first start Status Monitor, then put Nintendo Switch to dock.
# What is currently supported:
- CPU Usage for each core (Cores `#0`-`#2` are used by apps/games, Core `#3` is used by OS, background processes and also Tesla overlays)
- GPU Load
- CPU, GPU & RAM target frequencies (also real frequencies + RAM Load if [sys-clk 2.0.0_rc4+](https://github.com/retronx-team/sys-clk/releases) is installed, use only official RetroNX release for reliable results)
- Used RAM categorized to: (not supported by FWs <5.0.0)
- Total
- Application
- Applet
- System
- System Unsafe
- SoC, PCB & Skin temperatures (Skin temperature not supported by FWs <5.0.0)
- Fan Rotation Level
- PFPS and FPS (they don't work for 32-bit games, shows only if [my fork of SaltyNX](https://github.com/masagrator/SaltyNX/releases) is installed)
- Battery temperature, raw charge, age, average voltage, average current flow and average power flow
- Charger type, max voltage, and max current
- DSP usage (only for FW older than 17.0.0)
- NVDEC, NVENC and NVJPG clock rates
- Network type + Wi-fi password# Requirements:
- Tesla Menu at least version 1.2.3How to setup everything: [HERE](https://gist.github.com/masagrator/65fcbd5ad09243399268d145aaab899b)
---
# Thanks to:
- RetroNX channel for helping with coding stuff
- SunTheCourier for sys-clk-Overlay from which I learned how to make my own Tesla homebrew
- Herbaciarz for providing screenshots from HDMI Grabber
- KazushiMe for writing code to read registers from max17050 chip
- CTCaer for Hekate from which I took max17050.h and calculation formulas for reading battery stats from max17050 chip# FAQ:
Q: This homebrew has any impact on games?A: Negligible, you won't see any difference. Almost everything is done on Core `#3`, other cores usage is below 0.001%.
# Troubleshooting:
Q: When opening Full or Mini mode, overlay is showing that Core #3 usage is at 100% while everything else is showing 0, eventually leading to crash. Why this happens?
A: There are few possible explanations:
1. You're using nifm services connection test patches (in short `nifm ctest patches`) that are included in various packs. Those patches allow to connect to network that has no internet connection. But they cause nifm to randomly rampage when connected to network. Find any folder in `atmosphere/exefs_patches` that has in folder name `nifm`, `nfim` and/or `ctest`, delete this folder and restart Switch (if you are using `sys-patch`, turn off `nifm` patching). If you must use it, only solution is to use this overlay only in airplane mode.
2. You're using some untested custom sysmodule that has no proper thread sleeping implemented. Find out in atmosphere/contents any sysmodule that you don't need, delete it and restart Switch.
3. Your Switch is using sigpatches, is not a primary device, is using linked account, and is connected to network. Delete sigpatches, change your Switch to primary device, unlink account, or disable Wi-Fi.