Help Center/ Cloud Phone Host/ FAQs/ ADB Connection Faults/ What Can I Do If Message "unable to connect to :5555" Is Displayed When I Am Using ADB to Access a Cloud Phone?

Updated on 2022-11-29 GMT+08:00

View PDF

What Can I Do If Message "unable to connect to :5555" Is Displayed When I Am Using ADB to Access a Cloud Phone?

Description

After successful establishment of the SSH channel, I ran the ADB command to access a cloud phone, and message "unable to connect to :5555" is displayed.

Figure 1 unable to connect to :5555

Causes

The ADB is connected to the cloud phone over USB instead of over Wi-Fi.

Handling Method

Run the adb tcpip Local idle port command in the CLI, and then run the adb connect 127.0.0.1: Local idle port command to reconnect to the cloud phone.

Parent topic: ADB Connection Faults

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot