Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Marvis Android Client

Complete the preinstallation tasks, and then choose the method that you want to use to install the Marvis Client on your device.

The Marvis client for Android provides detailed visibility into how your Android device interacts with the wireless network. It helps optimize network performance, streamline troubleshooting, and enhance overall user experience by providing insights into device connectivity and performance.

The Marvis Android client is supported on the following devices:

  • Android handheld devices and smartphones that run Android 8.0 and later versions

  • Zebra devices that run Android 8.0 and later versions

Marvis Android Client Installation Overview

You can use any one of the following methods to install the app:

  • Manual—Download and install the Marvis client app directly from the Google Play Store or the Juniper Mist portal.

    To download the client from the Juniper Mist portal:

    1. Select Organization > Admin > Mobile SDK from the left menu.

    2. Click Marvis Client at the top of the Mobile SDK page.

    3. Select the app version under Android, and then click Download Installer.

  • Android Debug Bridge (ADB)—Install the app using ADB, a command-line tool that developers can use to communicate with Android devices to debug issues and install/uninstall apps.

  • Mobile device management (MDM)—Use any of the following MDM solutions to install the app:

    • AirWatch or VMware Workspace ONE

    • SOTI

    Note:

    We've tested interoperability only with the MDMs listed above.

Requirements

Before you start the installation:

  • Enable the mandatory permissions listed in Table 1 for the app.

    Table 1: Permissions Required for the Marvis Client App for Android

    Permission

    Description

    Mandatory or Optional

    Location—Set as Allow all the time

    Enables the Marvis client app to obtain the Wi-Fi roam data and function as expected.

    Mandatory

    Bluetooth

    Allows the app to obtain the x and y coordinates of the location.

    Mandatory

    Nearby devices

    Enables the app to determine the relative location of nearby devices. Android 12 needs this permission enabled to run the location service on mobile devices.

    Mandatory

    Notifications

    Enables notifications if you want to be notified when the Marvis client is running actively in the background.

    Optional

    Camera—Set as Allow Once

    Enables you to scan the QR code during enrollment. You need not enable this permission if you are installing the app through ADB or MDM.

    Optional

  • Configure your network firewall settings to allow the Marvis client to connect to your organization.

    If your organization resides in the Amazon Web Services (AWS) cloud (default), use the following settings:

    • wss://client-terminator.mistsys.net:443/ws or protocol WSS (websocket) port 443 for domain/path

    • https://api.mist.com or the HTTPS protocol port 443 for domain

    If your organization resides in the Google Cloud Platform (GCP) cloud, use the following settings:

    • wss://client-terminator.gc1.mist.com/ws or protocol WSS (websocket) port 443 for domain/path

    • https://api.gc1.mist.com/ or the HTTPS protocol port 443 for domain

    Note:

    If your organization resides in a cloud other than AWS or GCP, contact the support team for the appropriate URLs to configure the firewall settings.

  • Obtain your secret token or QR code to onboard the Marvis client.

    1. Select Organization > Admin > Mobile SDK from the left menu.

    2. Click Token at the top of the Mobile SDK page.

    3. Create a new token, or use an existing token:

      • For a new token—Click Create Invitation. Enter a name for this invitation, and then click Create. When the token appears on the page, click View to see the QR code.

      • For an existing token—Refer to the token names to find the one that you want to use. Click the View link on the right side of the page to see the QR code.

    Note: To obtain the secret token using API, see https://api.mist.com/api/v1/docs/Org#sdk-invite.

As a best practice, we recommend that you disable the random MAC address. This avoids the need to re-register your device every time it connects to the network. To disable the random MAC address:

  1. Navigate to the Settings page on your device.

  2. Tap Network & Internet or Connections and then tap Wi-Fi.

  3. Tap the gear (settings) icon next to the wireless connection.

  4. Tap MAC Address Type and then tap Phone MAC.

Operational Modes

The Marvis client operates in the following modes:

  • Production mode—Standard operational mode for live environments that you can set using command-line parameters during installation.

  • Proof of Concept (POC) mode—Operational mode for testing and evaluation purposes and is also the default mode.

  • GUI or Non-GUI mode—Mode that enables or restricts visual access to the Marvis client. In non-GUI mode, you cannot access the UI or the Marvis client icon in the taskbar.

  • Debug mode—Mode to access the logs. You cannot edit the configuration in this mode.

Note:

  • If you want to view the configuration settings when you're in Production mode, you'll need to switch to the debug mode. However, the settings are not editable.

  • In POC mode, you can view and edit the configuration settings without any dependency on the debug mode.

Connection States

The Marvis client status is indicated by visual indicators and the following connection states :

  •  Disconnected—Client is not connected to the Juniper Mist cloud.

  •  Connected—Client is connected to the Juniper Mist cloud.

  •  Connecting—Client is requesting to connect to the Juniper Mist cloud.

  •  Sleeping —Client is connected to the Juniper Mist cloud through a non-Juniper AP.

Deploy the Marvis Client Using the SOTI MDM

To deploy the Marvis client using a mobile device management (MDM) solution, you must customize the Android package kit (APK) package deployment. You customize the APK deployment with the intent action to set the secret software development kit (SDK) token upon installation. When you launch the customized application package, the client is fully preconfigured and onboarded for operation.

You can onboard the Marvis client using the SOTI MDM.

Note:

We do not present the overall generic Android application deployment process with SOTI. We present only the information necessary to customize the Android application to complete the Marvis client deployment.

Before you begin:

  1. Ensure that you have a Windows device or a virtual machine (VM). You will run Package Studio, which runs only on Windows devices.

  2. Download SOTI’s MobiControl Package Studio (McStudio.exe).

To deploy the Marvis client using the SOTI MDM:

  1. On your Windows device or VM, launch Package Studio and create a package project with the following settings:

    • Processor—All (unless you're targeting specific CPU or device types)

    • Platform—Android

    • OS Version—8 or later

    • Version String—Same as the APK version

    • Vendor—Juniper Networks

    • Optional space requirement specifications

  2. Add the Marvis client APK.
  3. Add the following script file:

    • Script Engine—Legacy

    • Script Type—Post-Install

  4. Import the script file. The script file must have the following content:

    If you have configured a specific port on a Zebra device for voice calls, then the script file must have the following content:

  5. Build the package.

When you deploy the customized package with SOTI, the Marvis client is preconfigured and onboarded.

Deploy the Marvis Client Using AirWatch or VMware Workspace ONE

We do not cover the overall generic Android app deployment process with AirWatch. We cover only the specific steps needed to complete the Marvis client deployment.

Use the following intent command to deploy the client:

If you have configured a specific port on a Zebra device for voice calls, then use the following intent command:

You can use the following references to deploy the intent command:

Deploy Marvis Client Using Other MDMs

If you're using any other MDM, verify that the MDM supports intent execution. Here is a sample for Android Debug Bridge (ADB)-based (developer/debug) deployment that you can use to adapt to an MDM of your choice:

If the MDM solution does not support execution of Android intents, you might need to onboard each deployed client device manually. See Onboard and Configure the Marvis Client.

Verify the Installation

After you install and onboard the Marvis client, verify that those processes have run correctly. Ensure that your device is connected to the Mist Wi-Fi network.

To verify the installation:

  • Confirm that the secret token value is applied correctly. Navigate to the About or Configuration (if you're in the non-production mode) page on the Marvis client app and verify that the secret token value is still stored in the field.

    If the data does not persist and the secret token field is empty, enter the secret token value manually. You might need to also configure the application deployment to retain the application data.

  • About 15 minutes after you onboard the Marvis client, confirm that the Marvis client data is available on the Juniper Mist portal. You need to wait for a minimum of 10 to 15 minutes after onboarding the Marvis client for the data to propagate to the Juniper Mist cloud.

    The client data is not available on the Juniper Mist portal when a problem occurs in the client workflow of collecting and sending data to the Juniper Mist cloud. Contact the support team. You can access the logs in the Marvis client app. See View Logs in the Marvis Android Client. Alternatively, you can also use tools such as Logcat or Android Debug Bridge (ADB) to collect the Marvis client logs and share the logs with the support team.

    For Zebra devices, you can use the RxLogger tool as an alternative method to collect logs.

    When you contact the support team, you must share the Marvis client UUID. You can find the UUID on the About page of the Marvis client app. The UUID is used to track the data flow from the Marvis client to the Juniper Mist cloud.

Onboard and Configure the Marvis Client

After you install the app, you'll need to onboard and configure the app.
  1. Go to the Organization > Mobile SDK page in the Juniper Mist portal and select the Token tab to locate your secret token or QR code. Click View to display the QR code.
  2. Open the Marvis Client app.
  3. Tap the hamburger icon and then tap Configuration.
    The Configuration page appears.

  4. Tap the QR code icon next to Mobile SDK Secret field. Focus your device camera on the QR code that appears on the Juniper Mist portal.
    The app scans the QR code and inserts the matching secret token value in the Mobile SDK Secret field.
  5. Enter the values for the following parameters:

    • Location Visibility

      By default, Location Visibility is set to Off. If you enable Location Visibility, the device is listed as an app client in the Clients > App Clients page in the Juniper Mist portal for 5 seconds. You can set the display frequency as:

      • Low—Displayed after every 10 minutes.

      • Standard (recommended)—Displayed after every 5 minutes.

      • High—Displayed after every minute.

      Note:

      You'll need to have vBLE enabled on your access point (AP) if you want to enable Location Visibility. You can activate vBLE by purchasing the user engagement or asset visibility subscription or both the subscriptions (in addition to the Wireless Assurance base subscription).

    • Mobile Client Name

    • Mobile Voice Call Port (applicable only for Zebra devices)

  6. Tap Apply to save the configuration.

    If you haven't set the permissions already, you'll see permission requests. Enable the permissions as listed in Table 1. Ensure that you set the Location permission to Allow all the time.

  7. Tap the hamburger icon and tap Connection Status to view the Connection status page.

    Verify that the status shows as Connected.

    The Marvis Client is all set now to send data to the Juniper Mist portal. You'll need to wait for about 15 minutes for the data to appear on the Juniper Mist portal.

View Logs in the Marvis Android Client

The Marvis client classifies the logs as:

  • Info—General information

  • Error—Critical issues

  • Debug—Detailed data that you can use to debug issues

To view the logs in the app, you'll need to enable debug mode on the app:
  1. Tap the hamburger icon and then tap the Marvis Client icon 7 times.
    You'll be prompted for a password.
  2. Enter the password as AIDriven.

    You'll see the Logs option listed in the menu.

  3. Tap Logs.
  4. Enable View Logs to view the logs captured by the Marvis client. You can select the type of information you want to view from the Log Level drop-down list.
    You can click the Copy button to copy and send the log details to the support team for troubleshooting.
    Note:

    If you contact the Juniper Mist support team to resolve any issue, you might be asked to provide the organization ID, UUID, and organization name. You can find these details in the About page, which you can access from the hamburger menu.