# Mouse Several mouse input modes are available: - `--mouse=sdk` (default) - `--mouse=uhid` (or `-M`): simulates a physical HID mouse using the UHID kernel module on the device - `--mouse=aoa`: simulates a physical HID mouse using the AOAv2 protocol - `--mouse=disabled` ## SDK mouse In this mode (`--mouse=sdk`, or if the parameter is omitted), mouse input events are injected at the Android API level with absolute coordinates. Note that on some devices, an additional option must be enabled in developer options for this mouse mode to work. See [prerequisites](/README.md#prerequisites). ## Physical mouse simulation Two modes allow to simulate a physical HID mouse on the device. In these modes, the computer mouse is "captured": the mouse pointer disappears from the computer and appears on the Android device instead. Special capture keys, either Alt or Super, toggle (disable or enable) the mouse capture. Use one of them to give the control of the mouse back to the computer. ### UHID This mode simulates a physical HID mouse using the [UHID] kernel module on the device. [UHID]: https://kernel.org/doc/Documentation/hid/uhid.txt To enable UHID mouse, use: ```bash scrcpy --mouse=uhid scrcpy -M # short version ``` ### AOA This mode simulates a physical HID mouse using the [AOAv2] protocol. [AOAv2]: https://source.android.com/devices/accessories/aoa2#hid-support To enable AOA mouse, use: ```bash scrcpy --mouse=aoa ``` Contrary to the other modes, it works at the USB level directly (so it only works over USB). It does not use the scrcpy server, and does not require `adb` (USB debugging). Therefore, it is possible to control the device (but not mirror) even with USB debugging disabled (see [OTG](otg.md)). Note: On Windows, it may only work in [OTG mode](otg.md), not while mirroring (it is not possible to open a USB device if it is already open by another process like the _adb daemon_).