Kadiska Tester deployment on Android¶
The Kadiska Android application (called Kadiska Tester) can run on any type of Android devices running the Android API Level 26 at a minimum. This API is supported as from Android version 8.
Please refer to https://apilevels.com for more information.
Before assigning a Fleet configuration to an Android device, make sure you have created Tracers and have assigned them to the newly created Fleet. Please refer to this section for more details. This will prevent you from having to wait for a first Android device configuration update when Tracers are created and applied after the Kadiska Tester deployment. This automatic update is scheduled every hour.
Manually installing the Kadiska Tester is a straightforward process.
From the Play Store on your Android device, search for the application "Kadiska" (1).
Click on install (2). Then open the application (3).
Once the initial installation is complete, you need to enroll it to the previously created Fleet.
To do this, click on the dots at the top right corner (4) and select "Enroll" (5).
During the enrollment process, you will be asked to enter the Fleet key, which you can retrieve from the corresponding Fleet configuration.
If your mobile device is equipped with a camera, the easiest way to proceed is by scanning the QR code. You can find the QR code by clicking on "Mobile Setup" from the Fleet configuration view (6). Then, click on "Open" to activate the Key (7).
Alternatively, if you can connect to the Kadiska platform from your mobile device, you can simply click on the magic URL provided.
If none of the previous methods work for you, you can manually fill in the Key.
After completing this enrollment process, you should see the following information displayed on the screen:
- Device ID
- Application version
- Server URL to which the application is connected
- Fleet name and ID to which the device is assigned
As shown in the screenshot above, there are still some settings that need to be configured in order to ensure optimal operation.
First, the Kadiska Tester requires access to the device's location. Follow these steps to activate it:
- Click on "Settings" (8).
- Click on "Grant" (9).
- Select the "While using the app" option (10).
This activation is necessary to identify Wi-Fi networks that the device is connected to, using their SSID and BSSID. It is not used for geolocating the user.
To perform Tracer tests without any user interaction, the Tester must be able to run in the background.
To activate it, navigate back to the settings menu and click on the corresponding "Grant" button (11). Then, select the "Allow all the time" option (12).
To prevent the device's system from snoozing the application, follow these steps from the settings menu:
- Click the corresponding "Grant" button (13).
- Activate the "Allow notifications" option (14).
To prevent the device's system from snoozing the Kadiska Tester for battery optimization purposes, follow these steps:
- Open the main settings menu.
- Click on the "Grant" button (15).
- Click on "Allow" (16).
Congratulations, you are all set!
You can check the proper operation of the Kadiska Tester at any time by navigating to the application settings menu.
The graph displays the evolution of the performed tests.
The screenshot above displays the results of the initial test. Please note that it may take several minutes after the initial setup to observe this first result.
Deployment through an Mobile Device Management (MDM) platform¶
Android MDM considers three use cases, excluding personal Android devices that are not managed by an organization:
- corporate devices that are exclusively used for professional purposes
- corporate devices that can be partially used for private purposes
- private devices that can be partially used for professional purposes (BYOD - Bring Your Own Device)
To address these use cases, Android provides a way to isolate the professional and personal environment called a "work profile".
We focus here on the model that relies on an enterprise MDM platform and assume that the devices are managed by your organization.
In this case, the scenario we are focusing on is the "fully managed devices" when the devices are not configured with a work profile.
Deployment technical requirements¶
As mentioned above, to operate properly, the Kadiska Tester requires:
- to run in the background
- to use the device's location service
These capabilities greatly depend on the MDM platform used, the deployment model, as well as the Android devices type and version.
To ensure the application constantly runs in the background, a mechanism that will periodically trigger the application is a must. Please refer to the Examples of deployments through MDM solutions section for a detailed example of VMware WorkspaceONE.
If you want to avoid the users to manually authorize permissions (background run and geolocation), you can configure your MDM to enforce the following permissions:
To identify a unique device from your fleets, the Kadiska Tester can use the IMEI (International Mobile Equipment Identity) as device ID.
This makes easy to find a specific device from the Kadiska dashboards, in your MDM.
Every device which has a SIM card slot, should have an IMEI.
To read the IMEI, the Kadiska Tester requires the enterprise policy
CERT_INSTALL (since Android 10), which must be activated in your MDM.
In your MDM, this policy can be found as example with a name like
Install certificates or
Certificate installation and management.
- The IMEI is not available on devices without a SIM card slot.
- Multiple SIM card slots can be found on a single device, only the first one will be used.
- If the policy is not granted, or if the IMEI is not available, the Kadiska Tester will use the Android ID as fallback.
Using a private store¶
Organizations may decide to import the Kadiska Tester in their applications private store.
In this case, we recommend creating a "Google Service Account" so that we can automatically deliver all application software updates and upgrades.
Please contact the Kadiska team if such a private store configuration is required.