A Supervisor Plugin enables features that otherwise wouldn’t be available on devices, such as Remote Control. Customers can work with their device manufacturers to automate Esper’s Remote Control setup and enable remote access right out of the box.
In this article:
Preparing the Requirements
You will need the following details to request a supervisor plugin:
- Manufacturer
- Model
Manufacturer and model information may not be the same as those displayed in the device’s advertisements and packaging. You can find this information using the following methods:
On Provisioned Devices
For devices that are already provisioned with Esper, search for the device in Devices & Groups. Then click on the device’s ID, and navigate to the Overview > Hardware section.
On Unprovisioned Devices
Adb
Use the adb shell to find device information.
Find the manufacturer
adb shell getprop ro.product.manufacturerFind the model
adb shell getprop ro.product.modelSee Installing the Android Debug Bridget (ADB) Tool for more information.
AOSP Builds
By default, this information is typically defined in the Product Directory > build.prop file in your AOSP source. Occasionally, this can also be defined under the system, system_etc, vendor, or odm directories.
Android Settings
On some devices, this information can be found in Android Settings > About.
Requesting and Sharing the Plugin
In order to do so, customers will have to:
- Request a plugin for each device model from Esper.
- Share the plugin with the device manufacturer. The manufacturer will then sign these plugins with specified platform model keys.
- Then share the signed plugin with Esper.
Device manufacturers must use the latest version of the APK signer tool to sign the plugin.
Ensure that the plugin is signed with the same platform key as the device image. Values that don't match won't be granted sufficient permissions.
After the plugin is signed, run the following commands to verify the matching signatures. First, pull the following file from the device through adb:
adb pull /system/framework/framework-res.apkNext, match the outputs of the following two commands:
apksigner verify -prints-certs supervisor.apkapksigner verify -prints-certs framework-res.apkMatching signatures ensure that the plugin will have sufficient permissions to use Esper features.