Category filter
How to remotely launch app on your Android devices
The Remote App Launch action allows IT administrators to trigger the opening of specific applications on managed Android devices over-the-air, ensuring critical tools are active and accessible to end-users.
Why Use Remote App Launch?
Remote app launching simplifies device management by allowing admins to push specific software to the foreground. This is particularly effective for troubleshooting, ensuring persistent app uptime in kiosk environments, or guiding users to mandatory corporate applications.
- App Persistence: Keeps critical background apps alive during kiosk sessions.
- Operational Control: Opens and maintains specific apps for a defined duration.
- Remote Assistance: Assists users by opening necessary diagnostic or communication tools.
Prerequisites and Support Constraints
Before initiating a remote launch, ensure the device environment meets the following technical criteria:
| Requirement | Specification |
|---|---|
| Installation | The target application must be pre-installed on the device. |
| Agent App | Latest version of Hexnode UEM or Hexnode for Work is required. |
| Android Enterprise | Profile Owner mode only supports “Keep app open until user exits manually”. |
| Kiosk Mode | Apps must be added as Kiosk Apps or Background Apps to bypass blocks. |
| Xiaomi Devices | Must enable “Display pop-up windows while running in the background” and MIUI Optimization. |
Remote App Launch is not supported for devices currently in Lost Mode.
Step-by-Step Guide: Executing Remote App Launch
Administrators can initiate this action for individual devices or execute it as a bulk command for a fleet.
1. Launch an App on a Single Device
- Log in to the Hexnode portal.
- Navigate to Manage > Devices.
- Click on the specific device name to open the device summary.
- Navigate to Actions > Applications > Remote App Launch.
- Select the desired application from the drop-down list.
- Configure the launch behavior:
- Keep app open for _ seconds: Set a specific duration for the app to remain in the foreground.
- Never keep the app open: The app opens and immediately closes.
- Keep app open until user exits manually: (Enabled by default) The app stays open until closed by the user.
- Click Done.
2. Launch an App in Bulk
- In the Hexnode portal, navigate to Manage > Devices.
- Select the checkboxes for all target devices.
- Navigate to Actions > Applications > Remote App Launch.
- Select the application, choose the configuration setting, and click Done.
Troubleshooting Guides
| Problem | Resolution |
|---|---|
| App is blocked in Kiosk Mode | The app was likely not added to the Kiosk policy. Ensure the app is listed under Kiosk Apps or as a Background App in the policy settings. |
| Action fails on Xiaomi devices | Navigate to App Info > Other Permissions and enable “Display pop-up windows while running in the background.” Also, ensure MIUI Optimization is turned ON. |
| App fails to launch in Profile Owner mode | Ensure the application is part of the Work Profile. Only apps within the work container can be remotely launched in this mode. |
| Action remains in “Pending” status | Verify the device has an active internet connection. If the device is in Lost Mode, the action will be ignored by the system. |
Frequently Asked Questions (FAQs)
What happens if the app is already open?
If the application is already running in the background, the Remote App Launch action will bring it to the foreground based on the specified configuration.
Can an app that is not installed be launched?
No. The application must be present on the device. If it is a managed app, ensure the installation was successful before attempting a remote launch.
Does “Never keep the app open” actually do anything?
This setting is typically used for specific background triggers where the app needs to initialize a process but does not need to remain visible to the user.
Why is the Work Profile restricted?
In Android Enterprise Profile Owner mode, the MDM only has authority over the work container. Therefore, it cannot trigger the launch of personal apps outside of that container.
