Install and start Porter

Download Porter from GitHub Releases, then follow the steps below.

Install

1. Download the Porter APK from the release’s Assets section. Source-code ZIP and TAR files are not Android apps.
2. Open the APK on your device. If Android asks, allow your browser or file manager to install apps from this source.
3. Open Porter.

For apps that support Porter directly, Porter alone is enough. If an app only supports Shizuku, open Shizuku compatibility in the FOSS build to install the included companion and review a replacement/import before removing Shizuku. The separate Porter Compatibility APK from the same release is also available. For manual installation, uninstall Shizuku first: the companion cannot be installed alongside it. Keep the companion installed while using those apps with Porter. See the compatibility guide for more details.

Choose how to start

Startup methods appear directly on the home screen while the service is stopped.

Wireless debugging

You need a Wi-Fi connection and Android 11 or newer. Some device manufacturers restrict wireless debugging; if it is unavailable, use a computer.

1. Enable Developer options in Android Settings. Usually this means opening About phone and tapping Build number seven times. The location varies by device.
2. In Developer options, enable USB debugging and Wireless debugging. Accept Android’s network authorization prompt if it appears.
3. In Porter, tap Pairing under Start via Wireless debugging. Allow notifications and, if requested, nearby-device or local-network access.
4. Open Android’s Wireless debugging settings and tap Pair device with pairing code. Keep that dialog open.
5. Expand Porter’s pairing notification and enter the code shown by Android. Wait for pairing to succeed.
6. Return to Porter and tap Start under Start via Wireless debugging.
7. Check that Porter says Porter is running.

Porter leaves Android’s debugging settings enabled when it stops. You can turn them off in Developer options when you no longer need debugging access.

Pairing normally only needs to be done once. Starting the service is a separate step and is needed again after a device restart. If Android forgets the pairing, repeat these steps.

If you selected In-app dialog under Settings, Startup, Pairing method, wait for Porter’s dialog to discover the pairing service, then enter the code there. If it asks for a port, use the pairing port from Android’s pairing-code dialog, not the connection port on the main Wireless debugging screen.

Android TV

On a TV with wireless debugging, choose Pairing in Porter and follow the instructions to enable its pairing accessibility service. Within one minute, open Developer options, Wireless debugging, then Pair device with pairing code. Keep that dialog open while Porter reads the code and completes pairing.

Porter displays a progress panel over the pairing-code screen. Leave that screen open until the pairing result appears. Porter then opens its result screen and turns off its pairing accessibility service. The result screen confirms when the service is off, separately from whether pairing worked. Choose Start after success, or Retry after a failure or timeout. If Porter does not open automatically, open it to see the result. For installation controls that cannot be selected with a remote, see TV installation warnings.

With a computer

1. Install Google’s Android SDK Platform-Tools on your computer.
2. Enable Developer options and USB debugging on the Android device.
3. Connect the device with a USB data cable. Unlock it and approve the debugging connection. Only authorize a computer you trust.
4. Open a terminal in the Platform-Tools folder and run adb devices. On Windows PowerShell, use ./adb.exe devices; on macOS or Linux, use ./adb devices if ADB is not on your PATH.
5. In Porter, find Start by connecting to a computer and tap View command. Run that exact command on your computer, adjusting the adb executable prefix as above if needed.
6. Check that Porter says Porter is running. You can disconnect the cable afterward.

If more than one device is connected, insert -s DEVICE_SERIAL immediately after adb in the displayed command. Use the serial shown by adb devices for the device running Porter.

Get a new command from Porter after updating or reinstalling it. The path can change. Do not use a startup command copied from Shizuku or another installation.

Root

This method is for devices that already have working root access. Installing Porter does not root your device.

1. Open Porter and tap Start in its root startup section.
2. Approve Porter’s request in your root manager.
3. Check that Porter says Porter is running and shows root as the startup mode.

Stop the current Porter service before switching between root and debugging access.

Allow an app

Open the app you want to use, enable its Porter or Shizuku integration, then approve Porter’s access prompt. Only approve apps you trust: they can perform tasks with Porter’s debugging or root access.

To remove access, tap Applications in Porter and turn off the app’s authorization. Porter and Shizuku keep separate approvals.

To pause access for all apps, turn off Allow app access at the top of that screen. Individual approvals are preserved. Turn it back on to resume access. Already-started shell commands may continue while access is paused.

If the app has a service selector, choose Porter there. Follow the app’s own setup instructions. If changing the selection requires restarting the app, use Force stop in Android’s app settings and reopen it.

Stop Porter

Tap Porter is running on the dashboard, then choose Stop Porter. Connected apps lose access until you start Porter again.

Update Porter

Install the newer APK over the existing app and start Porter again. If you use Porter Compatibility, update it from the same release. Android requires matching signatures for updates; see installation problems if it refuses.