← All news

Remote control of Android devices from the session

Android debugging through the session is complete: what started with files and Logcat ends with remote control of the device.

Remote control

  • Screen of phone, tablet and Android TV inside the session, picture through the sandboxed decoder, mouse, keyboard and text input.
  • Key bar with hold, rotate and “auto-rotate”, “view only” with full-resolution screenshots, quality levels, clipboard sync.
  • Android TV with a remote-control panel (profiles for Fire TV, SHIELD and generic devices, live TV, app keys); settings per device; history on the partner side.
  • Verified live on Samsung S26, Nvidia Shield and Fire TV Cube.

Logcat viewer

  • Separate window with a filter language (tags, levels, processes, time, crashes, AND/OR/NOT), search, bookmarks, crash card and memory limits.
  • Devices over Wi-Fi report “not responding” quickly and reconnect on their own; after re-plugging via USB, the viewer finds the device again by its real serial number.

Files and shell

  • Device files (storage and app data of debuggable apps) in the file browser; install APKs from the device or after download.
  • ADB shell in the shell module; remembered devices on the partner side with names, in service mode too.

Pairing works over Wi-Fi (mDNS, QR or code pairing on the partner side) or via the USB bridge; the supporter needs neither an Android SDK nor drivers on their own machine.