DeepManage

Features

Live Control and remote support for Android

Help a user in another city as if you were standing next to them. Live Control streams the device screen to your browser and lets you tap, swipe and navigate on it.

Live Control session in the console

What you can do

  1. Live screen in the browser

    The device screen streams straight to the console, with no plug-in or separate viewer to install on the administrator's computer.

  2. Remote input

    Tap, long press and swipe on the screen, and use Home, Back, Recents, Notifications, Quick Settings, Lock and Power buttons.

  3. Encrypted connection

    Screen video and commands are encrypted end to end between browser and device. Relay servers only forward encrypted packets.

  4. Your own relay servers

    Connections can use connection and relay servers in your own network with short-lived credentials, and can be forced through the relay. This also works in closed networks.

  5. Permission and consent

    Only roles with the Live Control permission can start a session, and the device user must accept Android's screen sharing prompt each time.

  6. Screenshots and bug reports

    Take a screenshot on request, and ask a fully managed device for an Android bug report that the user agrees to share. Reports can be downloaded from the console.

Why remote support matters

When a device fails in the field, the cost is rarely the device. It is the driver who cannot deliver, the sales rep who cannot take orders or the technician who has to drive two hours to change one setting. Live Control lets the help desk see exactly what the user sees and fix it on the spot. It is especially useful for field teams and for devices installed in places that are hard to reach.

How a session works

  1. On the device detail page, an administrator with the Live Control permission clicks Start.
  2. The DeepManage agent on the device receives the request over the live connection and asks Android to share the screen.
  3. The user sees Android’s screen sharing prompt and accepts it.
  4. Browser and device set up an encrypted connection. The DeepManage realtime service only helps them find each other and passes connection details.
  5. The screen appears in the console. The administrator can tap, swipe and use the navigation buttons, or take a screenshot.
  6. The session ends when the administrator clicks Stop, the user stops sharing, or the connection drops for too long.

Network and security

The connection tries a direct route first. When firewalls or mobile networks prevent that, traffic goes through a relay server. DeepManage lets you set:

Setting Purpose
Connection servers Help browser and device find a direct route
Relay servers Relay traffic when no direct route exists
Credential lifetime Relay credentials are generated per session and expire
Relay only Force all traffic through your relay server, so devices and operators never connect directly

For on-premises installations these servers can sit inside your own network, so a session never leaves it. In every case the screen stream is encrypted between browser and device.

Access is controlled in the console’s role and permission settings, as described on the identity and integrations page. A device’s live session is tied to one administrator at a time.

Beyond the live screen

Not every problem needs a live session. From the same device page you can:

  • request a screenshot to see what is on the screen right now,
  • request an Android bug report when an app or the system misbehaves. The user is asked to share it, and the console lists each request with its status and a download link,
  • lock, ring, sync or reboot the device, or send it a message with messaging.

Limits

  • Android requires the user’s approval for every screen sharing session, so Live Control cannot be used on an unattended device without someone to accept the prompt.
  • Remote input needs the DeepManage accessibility service to be enabled on the device.
  • Bug reports are available on fully managed devices and on company-owned devices with a work profile (Android 11 and later).

Frequently asked questions

Does the user have to approve each session?

Yes. Android shows its screen sharing prompt on the device at the start of every session, and the session starts only after the user accepts. This is an Android rule that keeps screen capture visible to the user.

Can someone else watch the session?

A session holds the device and one administrator. If a second authorized administrator starts Live Control, the session moves to them and the first one is disconnected. Starting a session is recorded in the administrator's activity log.

Does Live Control work on-premises and in closed networks?

Yes. The connection service runs as part of your DeepManage installation, and you can run your own relay servers inside the network. No traffic has to go through Infoline's servers.

Can the screen be seen by the server?

No. The video is encrypted between the browser and the device. The DeepManage connection service only passes connection details, and a relay server forwards encrypted packets that it cannot decode.

What do I need on the device?

The DeepManage agent with its accessibility service enabled, which is how remote taps and swipes are carried out. Bug reports need a fully managed device, or a company-owned device with a work profile on Android 11 or later.

See DeepManage on your own devices

Tell us about your fleet and we will prepare a demo environment for your team.