Add Android device

Before you start

  • Follow this guide to prepare the device before continuing.

  • Find the UDID of the device and note it down.

Connect Cambrionix hub to the host

Skip this step if the Mac mini host or GEM already has a Cambrionix hub connected.

Make sure you use a supported model of Cambrionix hub.

Connect the Cambrionix hub to a power source. The power LED indicator of the Cambrionix hub should turn on.

For Standard mode, connect the Mac mini to the host port of the hub.

For Lightning mode, connect the Graphic Extension Manager (GEM) to the host port of the hub. Make sure you connect the Cambrionix hub to the blue USB 3.0 port on the GEM.

Refer to the hub model’s user manual from Cambrionix for the exact host port location.

See below for an example of the SuperSync15 with the Host port visible.

SuperSync15 with the Host port visible

Connect the device to the host

Make sure you have properly prepared the device for hosting on Kobiton.

For Standard mode, connect the mobile device to the Cambrionix hub that is attached to the Mac mini host.

For Lightning mode, connect the mobile device to the Cambrionix hub that is attached to the GEM.

Check the device to see if it is charging after connecting. If it is not charging, the USB cable might be malfunctioning, or the Cambrionix hub is not connected to a power source.

Establish trust pairing between the device and the host

Access the Mac mini host directly, or via screen sharing.

Follow the appropriate steps based on whether you are using Standard or Lightning mode.

  • Standard mode

  • Lightning mode

  • Open Terminal and enter the following command. This must be run at least once after deviceConnect is installed:

    /usr/local/deviceconnect/bin/adb devices
  • The UDID of the device should show up in the output.

  • Make sure that adb is not running on the Mac mini by opening Terminal and enter the below command:

    /usr/local/deviceconnect/bin/adb kill-server
  • Still in Terminal, SSH to the GEM using the customerAdmin account:

    ssh customerAdmin@1.1.1.1
    • Replace 1.1.1.1 with the actual IP address of the GEM

  • Run the below command to check if the GEM can recognize the plugged in device:

    adb devices
  • The UDID of the device should show up in the output.

Check the device screen. Tap Always allow from this computer in the Allow USB debugging popup on the device screen, then tap Allow.

Allow USB debugging popup on the device screen

On some device models (such as Xiaomi or Oppo), the Use USB for popup displays as below:

Alternate Allow USB debugging popup on the similar device screens

Choose the File Transfer option.

Wait until the device screen changes to the below before continuing:

device screen changes and shows Kobiton name and logo

Set up OPPO devices

ColorOS on OPPO devices can block Kobiton software in two ways:

  • On newer ColorOS versions, the preinstalled system app com.heytap.accessory system app can occupy a network port required by Kobiton software.

  • Battery management can restrict background activity and stop Kobiton apps.

These settings can prevent a device from connecting to Kobiton or cause it to disconnect or become unresponsive.

Disable the conflicting system app

On each OPPO device, disable com.heytap.accessory to prevent it from using a network port required by Kobiton software.

If the first command returns an error that contains Unknown package: com.heytap.accessory, the app isn’t installed. Skip the second command and continue to Allow Kobiton apps to run in the background.

Disabling com.heytap.accessory turns off quick pairing with OPPO accessories, such as Enco earbuds. Standard Bluetooth pairing remains available.

Mac mini

On the Mac mini, open Terminal and run:

/usr/local/deviceconnect/bin/adb -s <device-serial> shell pm disable-user --user 0 com.heytap.accessory
/usr/local/deviceconnect/bin/adb -s <device-serial> shell am force-stop com.mobilelabsinc.deviceControl

Lightning mode (Linux server)

Configure adb on the Linux server as described in Establish trust pairing between the device and the host, then run:

adb -s <device-serial> shell pm disable-user --user 0 com.heytap.accessory
adb -s <device-serial> shell am force-stop com.mobilelabsinc.deviceControl

Replace <device-serial> with the serial number of the device.

The first command disables com.heytap.accessory. The second command stops deviceControl, which Kobiton software then restarts using the available port.

Allow Kobiton apps to run in the background

On the OPPO device, enable background activity for both apps:

  • deviceControl (com.mobilelabsinc.deviceControl)

  • Kobiton Agent Launcher (com.mobilelabsinc.trust.agent.stub)

    1. Open Settings and select Apps → App management.

    2. Select the app.

    3. Select Battery usage.

    4. Select Allow background activity.

The Apps screen in OPPO Settings with App management at the top → The App management list on an OPPO device showing the deviceControl app → The App info screen for deviceControl with the Battery usage option → Power consumption controls for deviceControl with the Allow background activity option

On older ColorOS versions, such as ColorOS 6, open Settings, select App Management, select the app, and select Power Saver. Then select Allow Background Running.

After restarting an OPPO device

When an OPPO device restarts, com.heytap.accessory is re-enabled. Run the commands in Disable the conflicting system app again from the host.

Use the host terminal rather than the ADB shell in a manual session to stop deviceControl.

Verify device is available in Kobiton

Open Chrome on the Mac mini, then open localhost and login.

Navigate to Devices. The connected device displays as Available.

The connected device displays as Available in the Devices section

Still in Chrome, open the Kobiton web portal and log in using an account with ADMIN role.

Select the profile picture and choose Settings, then choose Device Management.

In the search bar, enter the device’s UDID and hit Enter to filter.

The device should appear in the filter result. If the state of the device is Utilizing, it is being cleaned up. Wait about 2-3 minutes for the cleanup to complete.

When the cleanup is done, the device state becomes Online and the Launch button is available. Select it to launch a Manual session on the device.

Device state is Online and the Launch button is now available

In the Manual session, try the following to verify if the device is working properly:

If all the above works, you have successfully added the device.