Updated on 2024-04-19 GMT+08:00

ADB (Recommended)

You can use ADB to access your cloud phones on the CPH console. This method is similar to the ADB (Internet) method. The access principles are the same.

Prerequisites

The cloud phone must be in the Running state.

Procedure

  1. Log in to the management console.
  2. On the Service List page, choose Compute > Cloud Phone Host.

    The CPH console is displayed.

  3. In the navigation pane on the left, choose Instances.
  4. On the Instances page, locate the target cloud phone, and choose More > Access Through ADB in the Operation column.

    The right pane is displayed.

  5. Enter the local path for storing the private key file of the server, for example, C:\Users\Administrator\Downloads\KeyPair-a49c.pem.
  6. Enter the platform-tools directory. To obtain the directory,

    download the ADB tool and decompress the tool package to a specified directory, for example, C:\Users\Administrator\Downloads\platform-tools.

    If you cannot access the ADB download address on the console, click the following link to download ADB:

    https://dl.google.com/android/repository/platform-tools-latest-windows.zip

  7. Enter a local idle port number.

    Run the netstat -an command to check whether the port is idle.

    As shown in the following figure, port 6667 is occupied by another program, and port 1234 is idle.

  8. After you performed 5, 6, 7 in the lower part of the right panel, the command is automatically filled in the blank area. Perform operations as prompted to access the cloud phone.

    For details about the parameters in the command for establishing an SSH tunnel, see ADB (Internet).

    If you select Automatically-assigned IPv6 address when purchasing a cloud phone server, you can use the IPv6 address of the server to establish a tunnel to connect to the cloud phone. The command structure is the same as that for an IPv4 address. The following is an example:

    ssh -L 1234:[fd00::aed:96]:5555 05e1aexxx@ xxx:xxx:xxx:xxx -i C:\Users\Administrator\Downloads\KeyPair-a49c.pem -o ServerAliveInterval=30 -Nf

    For details about how to troubleshoot SSH tunnel establishment faults, visit the following links: