AndroMouse turns an Android phone or tablet into an input and remote-control surface for a computer. The mobile app sends pointer movement, clicks, keyboard input, media commands, and other controls through either Bluetooth or Wi-Fi. Bluetooth mode connects without the AndroMouse desktop server. Wi-Fi mode requires the matching server on the computer, and some advanced remotes depend on that server even when basic Bluetooth input is available.
Phone and server
In Wi-Fi mode, the desktop server receives commands from the Android app over the local network. The phone and computer need to share a reachable network, and the computer firewall must allow the server. Guest Wi-Fi often isolates wireless devices from one another even though both show the same access-point name. In that case AndroMouse cannot find the server until the network permits local communication. Bluetooth mode avoids this discovery step, but it does not expose every server-backed feature.
Manual connection uses the computer’s local address when discovery does not find it. That address can change after a router restart unless the network reserves it. Entering a public address or forwarding the server port exposes remote-control traffic beyond the local network and should not replace a secured remote-access method.
Input modes
The touchpad mode maps finger movement to the desktop pointer and assigns taps or on-screen buttons to mouse actions. The keyboard sends typed characters and command keys to the active computer window. Keyboard layouts, operating-system shortcuts, and application-specific keys can produce different results from the labels shown on the phone.
AndroMouse also has media and presentation controls. These send common play, pause, volume, slide, and navigation commands rather than reading the exact state of every desktop application. A media player that ignores standard media keys may not respond. Presentation controls also depend on the slide program holding keyboard focus.
Specialized remotes can expose file browsing, number pads, game controls, or configurable commands. Opening a desktop file through the phone still runs it on the computer. The file does not move to Android unless a separate transfer function copies it.
Connection limits
Pointer quality depends on the selected connection, phone sensors, and the computer’s responsiveness. A busy Wi-Fi network can cause delayed clicks or uneven motion, while Bluetooth range and interference can interrupt direct input. Either connection can fail in the middle of a drag or presentation and leave the desktop at its last received input state.
The desktop server grants the phone the ability to generate user input in Wi-Fi mode. Anyone who can connect under the same server settings may gain that control, so the server should run only on trusted networks and use the available access protection. Closing the Android screen does not necessarily stop the desktop component. The user must exit or disable the server when Wi-Fi remote input is no longer needed.
AndroMouse supplements a physical keyboard and mouse rather than replacing them during login failures, connection outages, or server setup. Keep local input available while changing Wi-Fi or Bluetooth settings because a mistake can cut off the phone before it can correct the configuration.
