Touchpad compatibility mode requires Network debugging to remain enabled so the app can restore USB permission and the virtual gamepad after a restart or controller reconnect. On the tested SHIELD firmware, Network debugging exposes ADB port 5555 to the local network. Use the app only on a trusted home network, review every ADB authorization prompt, and never approve a computer you do not recognize.
Turning Network debugging off removes that network exposure. The running mouse may continue until the next restart or controller reconnect, but automatic recovery will no longer work.
V2.1 Public R4 is signed with the standard Android debug certificate, not a protected production key. Its certificate SHA-256 fingerprint is:
BC29009E9249E2B3B1532BF63F6579CBFD35B3B9777E3681A071C6305E77EDAE
Because it is sideloaded and debug-signed, Google Play Protect may warn about the APK. Verify the release checksum and install only if you trust the source. Do not disable security scanning permanently just to install this app.
- The native helper binds only to
127.0.0.1:47210, not all network interfaces. - The helper requires a fixed protocol token before accepting commands.
- It accepts only create, input, and destroy frames for one UHID device.
- Packaged helper files are SHA-256 checked before installation or replacement.
- The USB permission helper grants access only to NVIDIA USB device
0955:7210and only to this app's UID.
The fixed loopback token is not a substitute for an operating-system security boundary. The main boundaries are loopback-only binding plus Android's process and ADB authorization model.
Do not publish device identifiers, ADB keys, private network addresses, or working exploit details in a public issue. Open a GitHub issue with a minimal description and request a private contact channel.