Skip to main content
Version: 25.2

Android

The Android agent allows the inclusion of devices with this operating system in the service consoles, enabling complete visibility for the support teams for desktop computers and users' mobile devices.

Requirements​

To deploy FlexxAgent on Android devices, you need a mobile device management (MDM) platform, such as Google Admin or Microsoft Intune. These platforms allow centralized distribution and installation of the app.

Once the MDM solution is configured, FlexxAgent can be installed from Google Play.

Supported versions​

FlexxAgent runs on Android devices version 9.0 or later.

Limitations​

Due to the restrictions of this operating system, certain functionalities are not available for this type of device, such as the execution of power actions, remote assistance, user microservices, or microservices from Workspaces or flows. These include: execution of power actions, remote assistance, flows, user microservices, or execution of microservices from Workspaces.

Some devices, to save battery, stop services or cannot connect to the internet while their screen is locked. When this happens, the device may stop reporting for a while until its screen is unlocked. This behavior varies depending on the manufacturer and the version of the operating system.

Settings​

FlexxAgent configuration is managed through Managed Configurations to ensure correct operation.

This configuration will be provided by a Flexxible contact during the implementation process, according to the app distribution solution used. For example, for Microsoft Intune the configuration is provided in JSON format, but for Google Admin the configuration is provided with separate values.

Distribution​

Flexxible will grant access to FlexxAgent in the Managed Google Play console provided by the client's MDM solution during the implementation process, as well as the necessary data for its configuration.

For Flexxible to grant access to the app, the client must provide the Name and ID of their Managed Google Play.

manage-android-apps

Download and installation​

FlexxAgent is available as a private Android app on Google Play.

To ensure FlexxAgent configuration applies correctly, the app must be manually opened on each device at least once after installation. It is recommended to follow these steps:

  1. Go to Google Play and navigate to Manage apps and devices.

    android_install_1

  2. Go to the Manage tab and click on the FlexxAgent application.

    android_install_2

  3. On the app detail screen, click Open. Next, a window will appear confirming that the app has been successfully configured.

    android_install_3_1

    android_install_3_2

info

FlexxAgent requires some special permissions, such as access to device files. If this permission is not granted in the app's configuration in your MDM solution, the user will be prompted to provide it. When they do, a message will appear indicating that the app has been successfully configured.

  1. Close the window.

When running FlexxAgent on an Android device, the fixed notification indicates that the agent is installed and running.

android

Update​

FlexxAgent updates automatically from Google Play.

Information obtained from the device​

FlexxAgent obtains and sends the following general information to the consoles:

android_wks

  • Name: device model
  • Device Status: on or off
  • FlexxAgent version
  • FlexxAgent Status: running or stopped
  • Last FlexxAgent report: date and time of last report received
  • Connection: Wireless LAN, mobile network or unknown
  • Network signal: reception percentage
  • Subnet: device network segment
  • Network changes: last time the network changed
  • Sessions: number of user sessions
  • Last User: last user who logged in
  • Connected From: name of the device from which the user has logged in
  • Connection time: session start date and time
  • Disk List: total capacity and disk usage in percentage
  • Wireless Network: network name (SSID)
  • Network Signal: network signal reception percentage
  • Code: this field lets users identify the workspace with a personal code. This code must be manually filled in individually using the Edit option in the Operations menu of the workspace details.
  • RAM: total available RAM capacity
  • Cores: number of processor cores
  • IP address: device IP address on the local network
  • OS: operating system name
  • Operating system: operating system version
  • Uptime: time the device has been running since it was last started or rebooted.
  • Reboot Pending: shows if the device requires a reboot for updates.
  • Public IP and ISP: the ISP is obtained using the public IP. It might not be accurate if connected to a corporate network or using a VPN.
  • Region: obtained using the public IP. It might not be accurate if connected to a corporate network or using a VPN.
  • Report group: report group to which the device belongs

android_fa

General device data, as well as the installed applications and their versions, are sent to the Analyzer.