- What's New
- Service Overview
- Billing
- Getting Started
-
User Guide
- Buying a Cloud Phone Server
- Accessing the Cloud Phone
- Cloud Phone Management
- Cloud Phone Server Management
-
Using AOSP
- Overview
- Automatic Application Authorization
- Loading Pictures
- Rooting
- Startup Script
- Automatic Installation of Applications
- Hiding Virtual Keys
- Hiding the Status Bar
- Disabling the Notification System
- Disabling Screenshot Protection
- Simulating Location Information
- App Installation Whitelist
- App Installation Blacklist
- Forcibly Installing a 32-Bit Application
- Dynamically Changing the System Language
- Background Process Management
- Texture Compression
- Restarting a Cloud Phone
- Device Emulation
- Cloud Phone Audio and Video
- Configuring a Route
- Permission Management
- Adjusting Resource Quotas
- Monitoring
- CTS
- Appendix
-
Best Practices
- Best Practices of Connecting to General-Purpose Cloud Phones
-
Best Practices of Cloud Phone Application Sharing
- Overview of Application Sharing
-
Usage Guide to Application Sharing
- Purchasing a Cloud Phone Server That Supports Application Sharing
- Preparing the TAR Package of an Application
- Pushing the TAR Package of an Application to a Cloud Phone Server
- Using the appctrl Command to Manage Shared Applications
- Deleting an Application
- Presetting Configuration Files by Sharing Applications
- appctrl Commands
- Installing an Application on Cloud Phones in Batches
- Modifying the Cloud Phone GPS Location
- Using the Cloud Phone Camera
- Using STF to Manage Cloud Phones in Batches
- Allowing a Cloud Phone Server to Access a Public Network Outside the Chinese Mainland
- Delegating CPH to Operate OBS Buckets
- Changing the AOSP Version of a Cloud Phone
- Change History
-
API Reference
- Before You Start
- API Overview
- Calling APIs
- Getting Started
-
Cloud Phone Server APIs
-
Cloud Phone Servers
- Querying cloud phone servers
- Querying the Details of a Cloud Phone Server
- Querying Flavors of Cloud Phone Servers
- Purchasing a Cloud Phone Server
- Restarting Cloud Phone Servers
- Changing the Cloud Phone Server for a Cloud Phone
- Pushing Shared Storage Files
- Querying Shared Storage Files
- Deleting Shared Storage Files
- Pushing Shared Applications
- Deleting a Shared Application
- Changing the Flavor of a Cloud Phone Server
- Modifying the Name of a Cloud Phone Server
- Bandwidth
-
Cloud Phones
- Querying Cloud Phones
- Querying Cloud Phone Details
- Obtaining the Cloud Phone Access Information
- Querying Cloud Phone Flavors
- Querying the Image of a Cloud Phone
- Resetting Cloud Phones
- Restarting Cloud Phones
- Stopping Cloud Phones
- Editing the Name of a Cloud Phone
- Updating Properties of Cloud Phones
- Exporting Data from Cloud Phones
- Restoring Data of Cloud Phones
- Diverting Cloud Phone Traffic
- Expanding the Data Disk of a Cloud Phone
- Tasks
- Keys
- Encoding Services
- ADB Commands
- Tags
- Images
-
Cloud Phone Servers
- Permissions Policies and Supported Actions
- Common Parameters
- Appendix
-
FAQs
-
Consulting
- What Are the Advantages of Huawei Cloud Phone Compared with Other Similar Solutions?
- Does Cloud Phone Support iOS?
- Are There Cloud Phone Root Permissions?
- Does Each Cloud Phone Has an Independent Public IP Address?
- How Is CPH Billed?
- How Do I Obtain the Project ID?
- How Do I Install Applications on a Cloud Phone?
- How Long Does It Take to Activate a Server After I Purchase It?
- What Should I Do If I Can't Find My Cloud Phone Server on the CPH Console?
- How Long Will Resources Be Released After My Cloud Phone Server Expires?
- What Can I Do If the Private Key File Is Lost?
- How Can I Know Whether the SSH Service Has Been Installed on My Local Device?
- What Are Common ADB Commands?
- Does the Cloud Phone Support Cameras?
- Does the Cloud Phone Support Facial Recognition?
- What Are the Security Group Authorization Rules for Cloud Phones Using Custom Networks?
-
SSH Tunnel Faults
- What Can I Do If the SSH Tunnel Fails to Be Established When I Access the Cloud Phone over the Public Network?
- What Does Message "Authorized users only. All activities may be monitored and reported." Indicate?
- What Can I Do If Message "too open" Is Displayed When I Am Establishing the SSH Tunnel?
- What Can I Do If Message "Permission denied" Is Displayed When I Am Establishing the SSH Tunnel?
- What Can I Do If Message "no match mac found" Is Displayed When I Am Establishing the SSH Tunnel?
- What Can I Do If Message "no matching key exchange method found" Is Displayed When I Am Establishing the SSH Tunnel?
- How Do I Keep an SSH Session Uninterrupted?
- What Can I Do If I Failed to Establish an SSH Tunnel?
- What Can I Do If an Error Occurs When I Invoke the Cloud Phone Query API?
- ADB Connection Faults
-
Consulting
- General Reference
Copied.
ADB (Intranet)
When you connect to a cloud phone through a private network, create an ECS in your VPC as the jump server for connecting to the cloud phone. If you do not customize the network when buying a cloud phone server, create a VPC peering connection between your existing VPC and the VPC where the cloud phone server is located, as shown in Figure 1. The ECS can run either the Windows or Linux. This topic uses the Windows as an example.
Constraints and Limitations
- You cannot establish a peering connection between the VPC of a tenant who has not purchased a server with the VPC where a purchased server is located. For example, in Figure 1, the tenant VPC and the VPC where the server resides belong to account A. A VPC peering connection across accounts cannot be created.
- The CIDR block of your VPC cannot overlap with 172.31.0.0/16 and 10.237.0.0/16. Otherwise, the VPC peering connection may be invalid.
- If multiple VPC peering connections are established between your VPC and the VPC where the cloud phone server resides, only one of the peering connections is automatically accepted.
Prerequisites
- The cloud phone must be in the Running state.
- The inbound rules configured for your VPC allow traffic from the IP address and port of the cloud phone to be accessed.
To obtain the IP address and port number of a cloud phone, go to its details page and obtain the server listening address in the Application Port area.
Figure 2 Application Port - A Windows ECS is available in your VPC.
- If you want to use an IPv6 address to connect to a dual-stack cloud phone, ensure that your environment, such as your ECS, supports IPv6 addresses.
Step 1: Create a VPC Peering Connection (Only When the Jump Server and the Cloud Phone Are in Different VPCs)
- Log in to the management console.
- On the Service List page, choose Compute > Cloud Phone Host.
The CPH console is displayed.
- In the navigation pane on the left, choose Servers. In the upper part of the server list, click Configure Route.
- In the right pane, record the project ID, VPC ID, and CIDR Block that will be required for creating a VPC peering connection.
Figure 3 Information collection
- If there is no Accepted peering connection available, click VPC console to create a VPC peering connection.
The VPC Peering page is displayed.
NOTE:
If a VPC peering connection in the Accepted state exists, perform the following operations to go to the VPC Peering page:
- Choose Service List > Network > Virtual Private Cloud.
- In the navigation pane on the left, click VPC Peering.
- In the upper right corner, click Create VPC Peering Connection.
- Set parameters as prompted. Set Account to Another account, Peer Project ID to the project ID recorded in 4, and Peer VPC ID to the VPC ID recorded in 4. Click OK.
Figure 4 Create VPC Peering Connection
- Wait for about 5 minutes until the VPC peering connection state changes to Accepted.
- Add routes for the VPC peering connection. For details, see Step 3: Add Routes for the VPC Peering Connection. In some regions, you cannot visit the route table module directly from the navigation pane on the left of the network console. In this case, add routes for the VPC peering connection by referring to Step 3: Add Routes for the VPC Peering Connection.
When adding a route, set Destination to the CIDR block recorded in 4. After the route is added, the two VPCs can communicate with each other.
- (Optional) If you want to forward all outbound traffic of all of your cloud phones to the created VPC peering connection, perform operations by referring to Configuring a Route.
Step 2 Access the Cloud Phone Through ADB
- Log in to the ECS.
- Download ADB from the local PC and upload it to the ECS.
Visit https://developer.android.com/studio/releases/platform-tools, switch the language to English in the upper right corner, and choose Download SDK Platform-Tools for Windows.
Figure 5 Downloading ADBIn the displayed dialog box, select the I have read and agree with the above terms and conditions check box, and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS.
- Decompress the ADB installation package (for example, platform-tools_r29.0.5-windows.zip) to the specified directory (PATH) on the ECS.
- Go to the PATH\platform-tools directory.
- Run the following ADB command to access the cloud phone:
adb connect Listening IP address of the server: Listening port number of the server
To obtain the listening IP address and port number of the server, perform the following steps:
- On the Instances page, click the name of the target cloud phone.
- In the Application Port area, obtain the listening IP address of the cloud phone server.
Take the information in Figure 6 as an example. Run the following ADB command:
adb connect 172.31.248.213:4673
If you select Automatically-assigned IPv6 address when purchasing a cloud phone server, the system will allocate an IPv4 address and an IPv6 address to both the cloud phone and the server, as shown in Figure 7. The listening ports of the cloud phone's IPv4 and IPv6 addresses are the same, so are the listening ports of the cloud phone server.
To use the IPv6 address to connect to the cloud phone, run the following ADB command:
adb connect [2409:8c85:80:32:cb7e:97e3:e424:1286]:4615
(Make sure you use square brackets to enclose the IPv6 address.)
- Run the adb devices command to check whether the current port is connected.
If information similar to the following is displayed, the connection is successful:
List of devices attached 172.31.248.213:4673 device
- Run other ADB commands to operate the cloud phone.
For details about how to troubleshoot the ADB connection faults, visit the following links:
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot