USB HID Client

about

description

<p>This Android app allows you your phone to present itself to a connected device as a keyboard and mouse. Since this happens at a very low level, the connected device sees it exactly as a normal keyboard and mouse, meaning you don't need to install any software on the connected computer! For this reason, it will even work if the connected device is in its BIOS/UEFI. Even multimedia keys are supported, meaning you can send volume up/down keys to the connected computer to control media. <b>I strongly recommend using <a href="https://github.com/Julow/Unexpected-Keyboard">Unexpected Keyboard</a> to use special keys such as modifier and function keys</b>, but most functionality will work with any standard Android keyboard.</p><p>Bonus description for nerds: This app adds (and provides a simple UI for you to communicate with) two character devices (<code>/dev/hidg0</code> and <code>/dev/hidg1</code> respectively) by adding HID functions to the default Android USB gadget. If you wanted to, you could just use this app to create the character devices, then communicate solely through some C program, shell script, or whatever else you wanted as long as it had the right permissions to access the character devices and knew how to send proper reports to them. Beware of SELinux policies if you do that though. If anyone is actually doing that, let me know, I'd be glad to help if necessary.</p><p>For more details on setup and usage, please consult the project's Readme.</p>

publisher

78ce6faa72264387284e647ba6938995735ec8c7d5c5a65737e55130f026307d

first seen

2026-10-08T08:04:10.657759+00:00

last event

2026-10-08 08:04 UTC

install

zapstore.dev or any Zapstore-compatible client

source & build

repository

https://github.com/arian04/android-hid-client

arch flags

android-arm64-v8a android-armeabi-v7a android-x86 android-x86_64

manifest

missing

releases (kind 30063)

1 release indexed; latest 3.1.0.

assets & verification

Every app, release and asset event is schnorr-verified (NIP-01 id + signature) before it enters the catalog, and assets are content-addressed by sha256. We subscribe read-only to the catalog relay — never write to it.

Showing the newest 0 asset descriptors; the full set is in /api/apps/78ce6faa…