1. Linux Features

The Switch contains a unique combination of hardware allowing for a vast featureset not seen on many other devices. Commonly used programs/apps are listed and documented here for reference.

L4T Switch Features

General Features Supported

  • Switch 2017, Switch 2019, Switch Lite, Switch OLED support (Erista and Mariko)
  • Full USB-C support Power Delivery, On-The-Go, DisplayPort/HDMI on any adapters/dock
  • Bluetooth and Wifi BT controllers and audio SBC/AAC/AptX/Aptx HD support WiFi with all channels except 2.4GHz 14 and 5GHz 144.
  • Full Joy-Con Support (Excluding NFC, and IR camera)
  • Nvidia Tegra GPU drivers - Vulkan, OpenGL, OpenGLES, EGL, CUDA
  • Audio - Headphones, Speakers, HDMI (up to 5.1) when docked, and Microphone (version 3.4.2+)
  • Touchscreen
  • Handheld (720p @ 60) and Docked Display Docked up to 4k30 or 1440p60 on Switch 2017/2019, and up to 4k60 on Switch OLED with OLED dock or 4k60 capable adapter
  • CPU/GPU/RAM frequency scaling Frequency depends on the Nvidia Applet Power Mode, automatic Console and Handheld Profiles
  • Automatic Overclocking through the Nvidia (Blue/Red Joy-Con) Indicator Applet (select an OC mode)
  • Full eMMC/SD speed. For SD, proprietary UHS DDR200 is also supported. DDR200 support makes Switch the first device in the world to even support it.
  • Hardware Video acceleration Support in new SMPV Player app (smpv), ffmpeg-l4t, mpv-l4t, system ffmpeg and the chromium-browser Watch videos without massive battery draining and convert videos really fast
  • Deep Sleep
  • IMU/Ambient Light sensor support
  • R2P and R2C (Reboot to any hekate boot entry configuration)
  • Support for Moonlight-QT Stream games/desktop from your Nvidia (nvidia gamestream) or AMD (sunshine moonlight host) GPU to your Switch HW video accelerated up to 4k
  • Widevine DRM support for Streaming platforms via Chromium
  • Updates distributed through APT package manager
  • Basically everything the hardware supports even if Switch OS doesn't support. Except NFC and IR.

JoyCon and Switch Pro Controller native support

JoyCon may be paired through Linux blutooth settings or through hekate to allow for use in HOS, Linux, and Android without the need to repair.
JoyCon function via Bluetooth, railed on Switch, and connected via USB through the JoyCon charging grip. Multiple pairs can be connected and be registered by pressing L+R or ZL+ZR. Otherwise if SL+SR is used, it will pair them in sideways orientation.
Switch Pro Controller functions via Bluetooth and via USB. You may pair through the Linux/Android Bluetooth settings but the pairing will not match HOS.
To dump the pairing info for use on HOS and Linux without the need to re-pair follow these instructions:
  1. 1.
    Pair procon in HOS if you haven't already done that
  2. 2.
    Boot L4T on your Switch and connect procon via USB
  3. 3.
    Run jc-dump-ltk in the terminal to get the HOS LTK
  4. 4.
    Go to your sd card via the file manager at sd:/switchroot/ and edit or create joycon_mac.ini
  5. 5.
    If existing entries then add a [joycon_02] entry. Otherwise [joycon_00].
  6. 6.
    It should look something like this: [joycon_01] type=3 mac=00:00:00:00:00:00 host=00:00:00:00:00:00 ltk=00000000000000000000000000000000 Description of the above keys: type is 3 for Pro-Con mac is the MAC from jc-dump-ltk ltk is the LTK from jc-dump-ltk host is your Switch Bluetooth MAC. Either copy it from existing entry or read it from hekate -> Console Info -> Hw Info -> Cal0
  7. 7.
    Save and Reboot Linux. Now procon will be able to auto connect in both HOS and Linux.
Both JoyCons and Switch Pro Controllers have their IMU (accelerometer/gyro) exposed as udev inputs in Linux and can be used in games/programs with support (Dolphin-Emulator is a good example)

Switch Docked Displayport/HDMI Output Support

Support for Official Nintendo Switch Dock as well as 3rd party Displayport/HDMI adapters/docks/hubs exists in Linux/Android. Official Dock requires power input from the official power adapter or better (15V 2.6A+ and 5V 1.5A+ PD profiles required from the charger). Many 3rd party adapters/docks/hubs can be used without supplemental power or with power from a USB-C PD Power adapter.
Official Original Nintendo Switch Dock is capable of resolutions up to 4k 30hz or 1440p 60hz. OLED dock supports up to 4k 60hz. Some 3rd party adapters can also achieve these resolutions. (note, any non-OLED Switch hardware is INCAPABLE of outputting 4k 60hz)
To specify a custom resolution for docked mode (useful for using 1920x1080 60hz on a 4K display): echo "1920x1080" | sudo tee /etc/dock-hotplug.conf
The syntax is basically WIDTHxHEIGHT {optional xrandr settings}. For example 1920x1080 --rate 120 will select 1080p at 120hz.

Switch USB-C OTG Support

OTG via USB-C is enabled and devices can pull up to 1.3A when unpowered. Powered OTG adapters are not supported, it is advised to use a hub/dock (which usually contains HDMI/Displayport) if USB and powering is desired.

Switch Accelerometer/Gyro and Rotation

Automatic rotation is supported in DE that have it enabled. The built in accelerometer/gyro is NOT exposed in userspace as a udev input. Instead, it is mapped as an iio device along with the ambient light sensor and fan tachometer.
/sys/bus/iio/devices/iio\:device0/ -> Accelerometer
/sys/bus/iio/devices/iio\:device1/ -> Rotation/IMU

Common Features and Applications

JoyCon Mouse/Keyboard mapping

Many users find it handy to map their JoyCons/Pro Controllers as a mouse/keyboard within Linux. There are profiles pre-installed for Official Joy-Cons, Switch Pro Controller, GameCube Controller (Wii-U/Switch Gamecube adapter with ToadKing Driver), Dualshock 4 Controllers (wired only, for now), X-Box One Controller (Wireless Only).
The current JoyCon/ProCon mapping is\
If you are used to other mappings, give the above a try for a full week. It's based on the most common and intuitive gamepad mappings. If you still can't get used to it, view the /usr/share/X11/xorg.conf.d/50-joystick.conf file for instructions on editing/writing/customizing the configuration to your own needs.

Reboot 2 Config

An app called Reboot 2 Config was added in 5.1.0 in the Switch tray icon. It allows you to reboot into your existing hekate boot entries with 2-3 taps.

Widevine Streaming

Widevine L3 is supported for Streaming Movie and TV series platforms.
  • For most platforms you can use the existing Chromium Web Browser.
  • For others like Netflix, you use the Chromium Streaming one.

CPU and GPU Overclocking:

Multiple custom CPU/GPU power profiles are included with the switchroot bionic. These are selectable by the Profile name at the taskbar near the Switch Icon.
Current L4T releases include these profiles by default:
Switch 2017 (v1):
Profile Name:
CPU/GPU: Min MHz - Max MHz
CPU: 0 - 1785
GPU: 0 - 768
CPU: 0 - 1428
GPU: 0 - 460
CPU: 0 - 2091
GPU: 0 - 768
CPU: 0 - 1785
GPU: 0 - 921
OC All:
CPU: 0 - 2091
GPU: 0 - 921
Perf All:
CPU: 1020 - 1785
GPU: 384 - 768
Perf OC All:
CPU: 1020 - 2091
GPU: 384 - 921
Switch 2019 (v2) / Lite / OLED:
Profile Name:
CPU/GPU: Minimum Frequency (MHz) - Max Frequency (MHz)
CPU: 0 - 1963
GPU: 0 - 844 (Lite: 768 or 844)
CPU: 0 - 1581
GPU: 0 - 537
CPU: 0 - 2295 or 2397 (Lite: 1963 or 2091)
GPU: 0 - 844 (Lite: 768 or 844)
CPU: 0 - 1963
GPU: 0 - up to 1228 (Lite: 768 or 844)
OC All:
CPU: 0 - 2295 or 2397 (Lite: 1963 or 2091)
GPU: 0 - up to 1228 (Lite: 768 or 844)
Perf All:
CPU: 1224 - 1963
GPU: 384 - 844 (Lite: 768 or 844)
Perf OC All:
CPU: 1224 - 2295 or 2397 (Lite: 1963 or 2091)
GPU: 384 - up to 1228 (Lite: 768 or 844)
More configs can be added by following the examples. Documentation for nvpmodel config can be found at the link. The nvpmodel config can be found here by default at /etc/nvpmodel/nvpmodel_t210.conf for Erista and /etc/nvpmodel/nvpmodel_t210b01.conf for Mariko devices.

RAM Overclocking

RAM overclocking was significantly improved. Now max frequencies allowed are 2366MHz for T210 and 3200 MHz for T210B01. Can be set in ini.
RAM is automatically scaled and can reach max 1600 MHz.


Set RAM Overclock frequency in KHz.
If you hang or get corruption or artifacts, try to reduce it. Unlike HOS which uses encryption for storage, such situations are safer when they are happening in L4T, so just set power profile to handheld and reboot. mem-bench command can use almost all of the available bandwidth so it can be used for a quick testing. Actual stability can only be confirmed by memtester command on as high as possible RAM temperature for several hours and with a big test size. Running 2-4 instances of 128-256MB can help on running it on all RAM banks. Running a secondary GPU benchmark can help raise temperature.
Creating more L4T boot entries in the ini with different RAM clocks can help with fast testing. Especially when Reboot 2 Config from Switch tray icon is used.
Any clock increase will also increase RAM power consumption like a CPU/GPU OC. For example on T210B01, with 1z-nm ram, going from 1866 to 2133 causes a 146 mW increase on active reads/writes which is 19.8%. Any other state is affected only with a voltage change.
Warning (T210B01): On T210B01, high RAM frequency might require the GPU minimum voltage to increase. That depends on GPU Speedo binning. Since RAM OC can raise GPU voltages, again depends on GPU binning, consideration must be given based on needed workloads. The DVFS that manages that is dynamic. On idle or if ram bandwidth requirement and frequency drops, it switches back to stock minimum. That allows for more fine tuned power draws, without the need to have GPU min voltage raised all the time.
T210 (Erista max 2366 MHz): List of supported frequencies: 1733000, 1800000, 1866000, 1900000, 1933000, 1966000, 2000000, 2033000, 2066000, 2100000, 2133000, 2166000, 2200000, 2233000, 2266000, 2300000, 2333000, 2366000.
Input frequency is generally normalized to one of the above. Actual frequency will differ a bit.
Suggested Jedec Frequencies:
  • 1866000
  • 2133000
Suggested Custom:
  • Any, if it works.
T210B01 (Mariko max 3200 MHz): List of supported frequencies: 1866000, 2133000, 2166000, 2200000, 2233000, 2266000, 2300000, 2333000, 2366000, 2400000, 2433000, 2466000, 2500000, 2533000, 2566000, 2600000, 2633000, 2666000, 2700000, 2733000, 2766000, 2800000, 2833000, 2866000, 2900000, 2933000, 2966000, 3000000, 3033000, 3066000, 3100000, 3133000, 3166000, 3200000.
Input frequency is generally normalized to one of the above. Actual frequency will be exactly one of these.
Suggested Jedec Frequencies:
  • 1866000
  • 2133000
Suggested Custom Frequencies:
  • Any, if it works. Very high ram frequencies might raise GPU power draw on some GPU frequencies if GPU binning is low.
Timing based overclocking: To enable that, edit the last 2 (T210) or 3 (T210B01) digits of the frequency.
It's generally better to find a good base frequency before touching these.
Do not touch them at all for guaranteed stability on max possible frequency, since without these, the whole configuration is exactly per Nvidia's and RAM vendor's specifications.
Syntax: T210: Freq MHz + BA. FFFFFBA. (1862400 -> 1862452) T210B01: Freq MHz + CBA. FFFFCBA. (2133000 -> 2133252)
Description of F, A, B and C timing overclocking options: [F]: Actual clock frequency. Exceeding chip's real max is actual OC.
  • Range: check above for T210 and T210B01 lists.
[A]: Base Latency reduction. Base latency decreases based on selected frequency bracket. Brackets: 1333/1600/1866/2133.
  • Range: 0 - 3. 0 to -3 bracket change. Example 1: 1866 with 2 is 1333 base latency. Originally 1866 bracket. Example 1: 1866 with 3 is 1333 base latency. Originally 1866 bracket. Example 2: 1996 with 3 is 1333 base latency. Originally 2133 bracket. Example 3: 2133 with 2 is 1600 base latency. Originally 2133 bracket. Example 4: 2400 with 0 is 2133 base latency. Originally 2133 bracket.
[B]: Core Timings reduction. Timings that massively get affected by temperatures are not touched.
  • Range: 0 - 9. 0% to 45% reduction.
[C]: BW Increase. T210B01/LPDDR4x only. RAM Temperature limited timings. Can cause significant ram data corruption if ram temperature exceeds max. Reason is not allowed on T210 and LPDDR4.
  • 0/1/2/3/4: for max 85/75/65/55/45 oC RAM temperature
RAM Temperature is only related to MEM/PLL sensors and not to Tdiode or Tboard. 45oC is 50/51 oC MEM/PLL (around 43 oC Tdiode, depends on temp equilibrium). 65oC is 68/69 oC MEM/PLL (around 60 oC Tdiode, depends on temp equilibrium).
Full Examples:
Old (no timing adjustments) OC equivalents:
  • 1862 Old OC: 15% -> [A1,B3,C0] - 1866031
  • 1996 Old OC: 25% -> [A2,B5,C0] - 2000052
  • 1996800 -> 1996800: 1996 MHz with read/write base latency of 2133 MHz and proper 1996 MHz core timings.
  • 1996800 -> 1996852: 1996 MHz with read/write base latency of 1600 MHz and reduced core timings by 25%.
  • 2666000 -> 2666000: 2666 MHz with read/write base latency of 2133 MHz and proper 2666 MHz core timings.
  • 2666000 -> 2666252: 2666 MHz with read/write base latency of 1600 MHz, reduced core timings by 25% and up to 65C operation.
Again, do not use them if you want the ram running like Nvidia and RAM vendor made the tables, and write the frequency as is in that case.


Changes VDDIO/VDDQ voltage for T210. VDDIO only for T210B01. Can stabilize timing reduction or if at frequency limit. Do not use for zero reason. Limits are fully safe (official Jedec).
  • Range: 1100 - 1175. (Unit in mV).


Changes VDDQ voltage for T210B01. Can stabilize timing reduction or if at frequency limit. Do not use for zero reason. Limits are fully safe (official Jedec).
  • Range: 600 - 650. (Unit in mV).