The Vita's Wi-Fi works, but Sony set it up for 2011:

• It sleeps between packets. Power save is on by default, so the first packet after any pause waits for the radio to wake up: ~100 ms, often 200+. You feel that in game streaming and remote shells.
• It uses half the channel. The radio handles 40 MHz channels, but the driver only ever asks for 20 MHz, which caps the link at 72 Mbps.
• It gives up at boot. If the auto-join misses your network once, the Vita just sits there offline until you open Settings and tap Connect.
• It gets dropped when idle. Many access points disconnect quiet clients after a few minutes, and the Vita doesn't always come back.

Wi-Fi Turbo fixes each of these, measured on real hardware.

Stock means Sony's defaults (power save on, 20 MHz). Turbo means the Max performance profile plus 40 MHz. Same Vita, same access point, modes interleaved so drifting radio conditions don't favour either side.

Throughput is the average of 4 interleaved runs per mode, 10 s each, received straight into RAM on the Vita (no memory card in the path). Wake-up latency is two runs of 30 pings sent 2 s apart, which gives the radio time to doze; that's the situation where power save hurts. See Measuring it yourself.

• 🚀 40 MHz channels (HT40). Unlocks the wide channel the radio already supports. The access point reports the Vita at 150 Mbps instead of 72. Best on a quiet channel; see the tips.
• ⚡ Power profiles. Max performance turns power save off (13× faster wake-up), Balanced is Sony's stock behaviour, and Battery saver sleeps through more beacons for longer battery life.
• 🔌 Auto-connect at boot. If the Vita's own auto-join gives up, Wi-Fi Turbo triggers the system's own "connect to my saved networks", so the Vita is online about 30 s after power-on with no input.
• 🔁 Auto-reconnect on drop. Lost the link? It comes back in about 3 s.
• 💓 Idle keep-alive. A tiny heartbeat to your router every 45 s, so access points don't disconnect a quiet Vita.
• 🔋 Keep Wi-Fi on. Stops the Vita dropping into standby (deep sleep), so downloads and remote sessions don't die. The screen still dims and turns off as normal, but while this is on the power button only turns the screen off: the Vita stays awake and connected. Turn it off when you want the Vita to sleep, or to save battery.
• 📡 Live HUD. An on-screen overlay with network, signal (dBm and %), SNR, channel, access point and active profile, read live from the driver.
• 🧭 Smart Mesh Roaming. For mesh and multi-AP setups: on a weak signal it rescans every channel and joins the strongest access point of the same network.
• 🎛️ Native Settings page. Everything lives in Settings → Network → Wi-Fi Turbo, in your system language.
• 🛡️ Safe by design. Every patch checks its target first, the driver is never hooked during boot, and any change is undone by switching it back in Settings, even with Wi-Fi down. See Safety.

Moving files onto the Vita over Wi-Fi (for example with VitaShell's FTP server) runs over TCP, which was about 20% faster with Turbo in our tests. How much you gain depends on the app's receive buffer, since the Vita's own TCP stack tops out around 40 Mbps. Keep Wi-Fi on also stops long transfers dying when the screen sleeps, and auto-reconnect picks up again after a drop.

Game streaming is all about steady latency. Power save adds 80–400 ms whenever traffic pauses; Max performance removes that, and 40 MHz halves the airtime of every frame. Pair it with vita-moonlight (my fork).

Building homebrew with vitacompanion (my fork), with its FTP uploads, remote launch, input injection and reboots, means your dev loop runs over Wi-Fi. Wi-Fi Turbo keeps that loop alive: it reconnects after reboots and drops on its own, keeps the console awake, and makes every round trip snappier.

Live HUD	Settings page

Power profiles	Built into Settings → Network

Network names and access point addresses are redacted in these screenshots.

Changing the profile or the 40 MHz option briefly reconnects Wi-Fi (about 5 s) so the new settings take effect. All settings are remembered and restored at boot, before the Vita first joins your network. To undo a change, just switch it back in Settings; that works even if Wi-Fi is down, so a setting your network doesn't like can never leave you stuck.

• Turn Bluetooth off when you don't need it. The Vita's Wi-Fi and Bluetooth share one 2.4 GHz radio and take turns on the air, so Bluetooth activity costs Wi-Fi airtime and adds latency. All the figures in this README were measured with Bluetooth off.
• Set your access point's 2.4 GHz radio to 40 MHz if you want the 40 MHz option to have any effect; the Vita can only use what the AP offers.
• In a congested 2.4 GHz area, 40 MHz can be slower. The band only has room for three non-overlapping 20 MHz channels, and a 40 MHz channel takes up two of them. With lots of neighbouring networks or other 2.4 GHz devices nearby, the wider channel picks up more interference, so throughput and latency can get worse instead of better. If that happens, turn 40 MHz off.
• Use Max performance for streaming and remote play, where steady latency matters more than battery life.

Turn on Developer mode (remote control), the last entry on the Wi-Fi Turbo page, and the plugin listens on TCP port 1339 on your LAN, handy for scripting and testing. It's off by default: with it off, nothing listens. It sits alongside vitacompanion (my fork), which uses ports 1337 and 1338. Send one command per connection, for example tools/bench/vcmd.py <vita-ip> status.

Profile and 40 MHz changes sent over port 1339 revert by themselves after 45 s unless you send confirm. A remote change that broke the link would otherwise leave you no way to reach the Vita and undo it. Changes made in Settings don't need confirming.

Port 1339 is unauthenticated, like vitacompanion's ports. Use it on networks you trust.

Wi-Fi Turbo's settings were measured on one Vita with the battery gauge's own average-current reading: screen off, connected 2 m from the access point, one pass of about 3 minutes per setting. "Load" is a continuous 100 Mbps UDP stream sent to the Vita.

• 40 MHz costs no battery. It draws the same current as 20 MHz, idle and under load, and moves about 40% more data while doing it.
• Max performance costs battery only when idle: about 19% more current, or roughly 2 hours of idle time with the screen off. Under load it costs nothing extra, because the radio is awake either way.
• Battery saver draws about the same as Balanced in these tests, but responds more slowly after a pause.
• Smart Mesh Roaming made no measurable difference (235 vs 236 mA).

In practice: use 40 MHz with Balanced day to day, and switch to Max performance for streaming, remote play or development, where its faster responses matter.

These are screen-off figures from a single run; differences under about 10 mA are within measurement noise. With the screen on, battery life is much shorter and Wi-Fi is a smaller share of the total.

The Settings page follows your system language. Supported:

Japanese, English (US), English (UK), French, Spanish, German, Italian, Dutch, Portuguese (Portugal), Portuguese (Brazil), Russian, Korean, Chinese (Traditional), Chinese (Simplified), Finnish, Swedish, Danish, Norwegian, Polish and Turkish.

The HUD uses a compact ASCII font, so it's translated for the Latin-script languages and shows English for the others.

This software is provided "as is", without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and non-infringement. It modifies how system software on your console behaves. You use it entirely at your own risk. The author is not responsible for any damage, data loss, bricked or unusable systems, lost warranty, or any other harm resulting from installing or using it. Keep backups, and make sure you know how to boot without plugins (hold L at boot) before you install. See the MIT License for the full terms.

Requirements: a PS Vita or PS TV with HENkaku or Ensō (taiHEN), on one of these firmware versions. Other versions are not supported. For the 40 MHz option you also need an access point with its 2.4 GHz radio set to 40 MHz channel width.

On 3.65 or 3.68 you need v0.2.0 or later: v0.1.0 does not load on those firmware versions.

1. Download wifiturbo_kernel.skprx and wifiturbo.suprx from the latest release.

2. Copy both files to ur0:tai/, for example with VitaShell over FTP or USB.

3. Find your config file. If ux0:tai/config.txt exists, edit that one: taiHEN reads it first and ignores ur0:tai/config.txt. This is the usual case on 3.65–3.68 with h-encore, which creates both files. Otherwise edit ur0:tai/config.txt. Keep the ur0:tai/... paths for the plugin files either way.

   Add one line under each of three sections:

   Section	Line to add
   *KERNEL	ur0:tai/wifiturbo_kernel.skprx
   *main	ur0:tai/wifiturbo.suprx
   *NPXS10015	ur0:tai/wifiturbo.suprx (adds the Settings page)

   HENkaku's default config already has these sections, so add the lines under the existing ones. A typical file afterwards looks like this:

   *KERNEL
   ur0:tai/wifiturbo_kernel.skprx
   *main
   ur0:tai/henkaku.suprx
   ur0:tai/wifiturbo.suprx
   *NPXS10015
   ur0:tai/henkaku.suprx
   ur0:tai/wifiturbo.suprx
   *NPXS10016
   ur0:tai/henkaku.suprx
   

4. Reboot the Vita (a "Refresh taiHEN config" from HENkaku Settings is not enough). Then open Settings → Network → Wi-Fi Turbo.

Not seeing the Settings entry? Check that ur0:tai/wifiturbo.suprx is listed under *NPXS10015 in the config file taiHEN actually reads (ux0:tai/config.txt if it exists, see step 3), then reboot.

To update: replace both files and reboot. To uninstall: remove the lines from config.txt, reboot, then delete the two files and ur0:data/wifiturbo/.

If anything goes wrong: hold L while the Vita boots to skip all plugins, then remove the lines from config.txt.

make                       # uses $VITASDK if set, otherwise a pinned VitaSDK Docker image
make deploy VITA_IP=<vita> # upload to ur0:tai/ over FTP and reboot (needs vitacompanion)
make log    VITA_IP=<vita> # fetch the plugin logs
make config                # print the config.txt lines

Output: build/wifiturbo_kernel.skprx and build/wifiturbo.suprx.

tools/bench/ has the scripts behind the numbers above. Run them from a computer on the same network:

export VITA_IP=<vita> HOST_IP=<this computer>
tools/bench/vcmd.py $VITA_IP "profile maxperf"   # link drops ~5 s, then:
tools/bench/vcmd.py $VITA_IP confirm
tools/bench/bench.sh turbo all                    # TCP, UDP and wake-up latency

• TCP: the Vita downloads from your computer into RAM for 10 s, with a 512 KB receive window. No memory card is involved.
• UDP: your computer sends a paced 100 Mbps stream; the Vita counts what arrives. That's the link's real capacity.
• Wake-up latency: 30 pings, 2 s apart. Pings 100 ms apart keep the radio awake and would hide power save.

Alternate stock and turbo runs to cancel out radio drift. The Vita's own TCP stack tops out around 40 Mbps, so UDP shows the 40 MHz gain best.

This plugin changes how a kernel driver behaves, so it's built to fail safe:

• Easy undo. Every change is undone by switching it back in Settings, which works with Wi-Fi down.
• Checked patches. Each driver patch verifies the original instructions first and refuses to apply on a mismatch, such as another firmware or a conflicting plugin. The one call into the system shell is located by a signature that must match exactly once. A feature whose check fails logs why and turns itself off.
• Gentle boot. At boot the plugin restores your settings with a few checked byte patches and a driver flag, before the first Wi-Fi join. It never hooks the driver while the console is starting up.
• Small hooks. The few driver hooks are tiny, only active when needed, and stay off the driver's busy command path.
• Escape hatch. Holding L at boot skips every plugin.

Bug reports, measurements from different access points, translations and code are welcome. See CONTRIBUTING.md. If you attach logs, redact your network name and access point MAC addresses first.

Built on taiHEN, VitaSDK and vitacompanion (my fork). Thanks to the PS Vita homebrew community.

MIT © 2026 Juan Garcia Alvite