Emittr turns a rooted Android phone into a USB keyboard without a PC-side app
The open-source project uses the phone’s gadget interface, with a direct mode and an optional local browser relay.

The spare Android phone has found another job. It can become the keyboard plugged into a computer, instead of asking that computer to install a remote-control app first.
Emittr uses the Linux USB gadget interface to present keyboard and mouse functions from a rooted phone. The project’s documentation describes configuring this through configfs and sending standard HID reports. The receiving machine sees input from a USB peripheral, while the phone supplies the controls on its screen.
That arrangement changes where the software needs to run. A conventional remote-control setup usually needs something on both ends. The README calls this “no host software”: the target doesn’t need the project’s client app. The phone carries the implementation, which is a useful distinction when the target’s operating system isn’t ready to cooperate.
The maker describes support for firmware and boot-menu input using USB Boot Protocol keyboard reports. Its field-demo panels are labeled as placeholders, so the advertised firmware compatibility still needs verification on the intended motherboard before depending on it for recovery.
There are two ways to drive it. Direct mode uses the connected phone itself. Relay mode leaves that phone plugged into the target, while a browser on the local network talks to the phone’s interface. The phone then sends the resulting keystrokes over USB. The second mode is convenient, but the Wi-Fi-facing phone is now part of the input path.
That is a real connection even though the target has no ordinary network session with the browser. Describing the arrangement as magically isolated would miss the entire point of the bridge. A phone that can type commands has been given meaningful control of the target, one keystroke at a time.
The project supplies typing speed controls, a countdown and an abort option for bulk text. Those are useful because typing quickly into the wrong window remains typing into the wrong window. Automation can make a mistake impressively punctual.
Its no-clipboard claim has a narrower meaning than some of the promotional language suggests. Sending keystrokes avoids placing the text in the target’s clipboard, but the target still receives it. That does not establish an absence of logs, monitoring or other records. The README’s sweeping claims about leaving no forensic footprint should not be mistaken for a guarantee.
The kernel requirements also make this a project for an already compatible rooted phone. Root alone doesn’t manufacture missing gadget support. The useful next step is checking that hardware boundary, without turning a straightforward spare-phone experiment into a promise that every Android handset can do the job.
The phone has entered the chat field.