Cannot connect to android

Cannot connect device with Android Studio 3.3.2 and Android 8.1 #71

Comments

mikechy2005 commented Mar 14, 2019

After clicking Connect, android studio prompted «Unable to connect to device. Same network»
and on device, it prompted for permission.
After allowed on device, click «Connect» on android studio, looping the issue.

Please help. Thanks.

The text was updated successfully, but these errors were encountered:

francojohnc commented Mar 18, 2019

same to me its not working to latest android studio

dekzitfz commented Mar 19, 2019

same here with the latest android studio

bogdanzurac commented Mar 19, 2019

Can confirm this issue with the latest update of AS.

pedrovgs commented Mar 19, 2019

Can you provide information related to the device model you are using the OS version and the AS version?

bogdanzurac commented Mar 19, 2019

AS version: 3.3.2
Device model: OnePlus 6T
Device Android version: 9.0

pedrovgs commented Mar 19, 2019

@bogdanzurac what’s your computer OS version?

bogdanzurac commented Mar 19, 2019

Computer OS: MacOS Mojave
OS version: 10.14.3

mikechy2005 commented Mar 20, 2019

Computer OS: Win7 x64 and Win10 x64

kpradeepkumarreddy commented Mar 21, 2019 •

I’m also facing same problem.
Computer OS : Windows 10
Mobile device: oneplus3
Mobile OS: android 8.0.0, OxygenOS: 5.0.8
Android Studio version : 3.3.2

Even when both computer and mobile device are on same network. I’m getting the following message, «unable to connect to the device make sure both computer and mobile device are on same network.»

Marcosmaliki commented Mar 22, 2019

This was the ONLY working solution till android studio updated the IDE. It doesn’t work, sometimes when the disconnect button is clicked it «connects» but it doesn’t really work.

aniketrawat97 commented Mar 26, 2019 •

Same problem here
Android Studio Version — 3.3.2
Computer OS : Windows 10
Mobile device: MI 3s
Mobile OS: android 6.0.1

LEFrost commented Mar 31, 2019

Same problem here
Android studio version 3.3.2
adb version 28.0.2-5303910

littleylv commented Apr 12, 2019

pedrovgs commented Apr 14, 2019

Could you check if you can connect your device using the terminal? Right now I don’t understand if the issue is related to Android Studio or the plugin. You have to plug in your device and run these commands from your terminal:

littleylv commented Apr 14, 2019

@pedrovgs Here is what I got:

bogdanzurac commented Apr 15, 2019 •

Do you need some additional logs we can provide for you? It does seem strange that this started happening to a couple of us right after AS updated.

Mr-ARBN commented May 2, 2019 •

I’ve got the same problem.
after I try to connect to my device:
16:00 Android WiFi ADB: Unable to connect to device ‘G8142’. Make sure that your computer and your device are connected to the same WiFi network.

I tried the suggestions. but I got no answer.
OS: Windows 10
Android version: 9
Android Studio: 3.4.0

Could you check if you can connect your device using the terminal? Right now I don’t understand if the issue is related to Android Studio or the plugin. You have to plug in your device and run these commands from your terminal:

JoshuaHuangTW commented May 7, 2019

I got same issue here. I’m using Android Studio 3.4 and my phone is samsung s7 edge, it shows same error message(ask me to check same network connection).
However, same android studio version, same phone, my PC connect to my phone successfully.
Hope someone can solve this issue.

Источник

Solutions to Android Devices Cannot Connect to AirMore Web

If you meet problems when connecting Android Devices to AirMore Web, please try the solutions below.

Solutions to Android Devices Cannot Connect to AirMore Web

Things to Check

• Please make sure that your Android devices and the computer are connected to the same WiFi network.
• Please check if the internet is available, because scanning QR code and clicking your device in Radar won’t work when there is no internet. You may use IP address to get connected.
• Please check if your Android device is locked. If so, please activate it and reload the AirMore Web to try again.
• Please use Chrome, Firefox, Safari, Microsoft Edge or IE browser (Chrome browser is recommended).

Alternative Connecting Solutions

If the trouble you meet results from the QR code, for example, the QR code doesn’t load successfully, or there is no response after scanning the QR code, you may try to connect in Radar, use IP connection or Hotspot connection. Suppose that you have already tried them, you can skip this instruction and check the possible problem.

Connection via Radar

1. On web.airmore.com, choose “Radar” and wait for the loading of your mobile device.

Click the device icon in Radar. If there is a window pops up on your phone, hit “Accept”. Soon the connection is successfully built.

IP connection

1. Open AirMore app, tap the three dots on the top right hand of the interface. Select “Get IP”, then an IP address will be shown.

Enter this address into your browser to build connection.

Hotspot Connection

1. Open AirMore app, go to “More” and select “Hotspot” to build a hotspot with your phone.

Connect your PC to the hotspot and then enter the IP address in the PC browser (Chrome, IE, Edge, Firefox or Safari).

Possible Problem

If you have utilized the above ways, but your phone still cannot build the connection to AirMore Web, you can check out the following solutions.

Wrong IP address

One possible problem is that your Android device doesn’t get the right IP address of the network. Here is the guide to check it:

On your phone, go to “Settings” > “WiFi”, and tap your WiFi name. There you can see the IP Address.

On your computer, open the status of your network. Click “Details” and find the IP address.

Compare the two addresses to see if the first three groups of their figures are the same.

If they don’t match each other, the connection won’t be successfully established. In this case, there are two solutions for you:

1. Restart your phone.
2. Manually reset the IP address: keep the first three groups of figures of IP address the same on your phone and on your computer. If the IP address on your computer is 192.168.43.59, then you should set the first three groups of that on your phone as 192.168.43.

Browser/Computer Issue

Another possible problem results from the settings of your browser or computer. For example, your browser or other network adapters blocks the requirement of AirMore connection. Under this circumstance, you’d better change browser or computer to try again.

Provided that you still cannot connect Android devices to AirMore Web, don’t hesitate to contact us. Our technicians will get back to you as soon as possible.

Источник

Can’t connect to Android device from Linux

Can’t connect for remoteControl/Sharescreen from Linux to my Android Phone.

From Mac/Windows it works as expected.

1. Open TeamViewer on Ubuntu desktop.

2. OPen QuickSupport on Android device

3. Entering ID to Partner ID field on TeamViewer.

4. Press Connect

5. On Android device new dialog appearing: «Would you like to allow to remote support your Android device?». Press «Allow» button

6. On Android device showing spinner for 5-10 seconds

7. Android device show main screen with my ID and status at the bottom: «Ready to connect»

What is wrong? Need assist, Let me know if you need additional details

TeamViewer version: 13.0.9865

Date: Feb 12 2018 15:30:36

Device: Nexus 6P

QuickSupport version: 13.1.8602 QS

Host version: 13.1.8602 HM

Best Answer

Official Answer from Teamviewer:

Unfortunately there is no mobile device support for Linux at the moment. We can’t say when we will release it, but we are planning to do so.

If you have any further questions, please do not hesitate to contact us again.

Dennis [Personal information removed
Support Engineer

Answers

Had this problem as well.

OS: Ubuntu 16.04
TeamViewer version: latest as of 16/07/2018: 13.1.8286
Date: May 30 2018 15:56:29

Android: 8.0.0
Device: Samsung Galaxy Note 8
QuickSupport Samsung version: latest as of 16/07/2018: 11.0.4766 QS
Host version: latest as of 16/07/2018: 13.1.8752 HM

Tried using same network and different networks. (pc and phone on same wifi network, pc on cable or wifi, and phone on 4G.)

Please bear in mind that I can connect from my home to this ubuntu computer, and can connect from ubuntu to my home as well, and can connect on my home to my phone as well(over wifi on same network or 4g).

Using my Wifi and 4G:

Connecting through «HOST» app on phone(replaced possible private info with XXXXXXXXX):

When the connection ended suddenly (went from «Connection Accepted» to «Ready to Connect»):

Logs on my phone(also stripped of possibly identifying info):

Источник

Emulator is running but cannot connect to it #79

Comments

NoelOmo commented Dec 2, 2019 •

I have successfully ran the emulator, from the logs, it looks like its booting up just fine. However when, I connect to it via adb connect :5555 and then type adb devices, I get the following:
:5555 offline

Furthermore, when accessing the emulator through the react website, I can only see a black screen that that does not change to anything no matter how long I wait, see attached screenshot:

Anyone know what could be the issue here?

The text was updated successfully, but these errors were encountered:

NoelOmo commented Dec 2, 2019

Upon furher investigations on the logs, I see that the emulator is stuck on an endless loop of the following message
emulator_1 | kernel: [ 1372.050438] init: Could not find ‘android.hardware.graphics.composer@2.1::IComposer/default’ for ctl.interface_start emulator_1 | kernel: [ 1373.014064] init: Received control message ‘interface_start’ for ‘android.hardware.graphics.composer@2.1::IComposer/default’ from pid: 1664 (/system/bin/hwservicemanager)

Anyone who knows what this means?

NoelOmo commented Dec 2, 2019

@pokowaka Any insights on this issue?

dmarjanovic commented Dec 2, 2019 •

I am experiencing similar problem where adb cannot connect to emulator after using these 3 commands:

It starts all the 4 containers as expected ( docker_emulator_1 , docker_front-envoy_1 , docker_jwt_signer_1 , docker_nginx_1 ), I can see the UI in react website, there are adbkey and adbkey.pub both inside emulator container and on the host machine as expected but still cannot authorize emulator and it’s not possible to use any adb command such is adb logcat .

I’ve tried AVD/Emulator combos:

• google_apis_playstore-24-N-x86-29.2.11
• google_apis_playstore-27-O-x86-29.2.11
• google_apis_playstore-28-P-x86_64-29.2.11
• google_apis_playstore-28-P-x86_64-29.2.1

Linux CentOS 7.4 on MacBook Pro with NVidia drivers installed and KVM enabled.

NoelOmo commented Dec 4, 2019 •

I am experiencing similar problem where adb cannot connect to emulator after using these 3 commands:

It starts all the 4 containers as expected ( docker_emulator_1 , docker_front-envoy_1 , docker_jwt_signer_1 , docker_nginx_1 ), I can see the UI in react website, there are adbkey and adbkey.pub both inside emulator container and on the host machine as expected but still cannot authorize emulator and it’s not possible to use any adb command such is adb logcat .

I’ve tried AVD/Emulator combos:

• google_apis_playstore-24-N-x86-29.2.11
• google_apis_playstore-27-O-x86-29.2.11
• google_apis_playstore-28-P-x86_64-29.2.11
• google_apis_playstore-28-P-x86_64-29.2.1

Linux CentOS 7.4 on MacBook Pro with NVidia drivers installed and KVM enabled.

Have you had any luck with this?

pokowaka commented Dec 4, 2019

This happens due to a mismatch between the adb key used to authenticate to the container, versus the public key that is made available to the container.

Playstore images require ADB to authenticate, so the proper private and public key must be made available to the system image. The web container creation script tries to mount

/.android/adbkey.pub. Some things to try:

• Make sure to use the same user account for creation, as well as running the container.
• Make sure a private adb key exists in

/.android/adbkey). If non exists you can create one with adb keygen

I will look into automating this.

pokowaka commented Dec 4, 2019

@dmarjanovic could you make sure that the public/private key pairs inside the container match with the one you use to connect?

Things to try is setting $ADB_VENDOR_KEYS before launching adb (make sure to kill the server first), and have it pointed to the same keys used by the container as yours.

The container launched by js/docker/docker-compose-with-adb.yaml will mount the file

dmarjanovic commented Dec 4, 2019

@pokowaka I think the key pairs were matching when I was checking it the first time but will double check tomorrow again just to be sure. I will check the PR too, thank you.

What works just fine though is this combo:

I guess the docker compose approach does something more or differently to emu image.

pokowaka commented Dec 4, 2019

The main difference is that run.sh will pass the public adb key into the container via an environment variable, whereas the container will mount the file. More specifically:

Something with the mounting of the secret must not be working as expected. Which of the following do you see on the docker logs (after launching):

• Copying key from secret partition Using provided secret No adb key provided.. You might not be able to connect to the emulator.

pokowaka commented Dec 4, 2019

Sample output on my machine:

dmarjanovic commented Dec 4, 2019 •

1. When using ./run.sh docker_image_id method:

• Sample output on my machine -> Using provided secret
• both private and public keys match meaning adb devices works perfectly out of the box, I guess THIS worked nicely

1. When using web container ( docker-compose ) method:

• Sample output on my machine -> Copying key from secret partition
• private key mismatch (I guess because it copies only the public key HERE) meaning if I manually extract/copy private key from emulator image /root/.android/adbkey to my host

  /.android/adbkey then adb devices works perfect. Note that adbkey.pub is already the same as expected since it’s «copied from secret partition».

I guess above is enough to track the cause but answering to your previous questions below:

Make sure to use the same user account for creation, as well as running the container.

Make sure a private adb key exists in

/.android/adbkey). If non exists you can create one with adb keygen

The pair was already created prior any command here.

could you make sure that the public/private key pairs inside the container match with the one you use to connect?

Private key mismatch when using method 2. It’s the same when using method 1.

Things to try is setting $ADB_VENDOR_KEYS before launching adb

Not sure how to use this exactly.

The main difference is that run.sh will pass the public adb key into the container via an environment variable, whereas the container will mount the file

Can you try to month private key too in addition to public key? Somehow it looks like a possible solution since when I copy private key manually from emu image back to host then adb works perfectly on the host.

Please note I haven’t tried new PR yet since it’s really slow to rebuild all images from scratch.

pokowaka commented Dec 4, 2019

Can you try to month private key too in addition to public key? Somehow it looks like a possible solution since when I copy private key manually from emu image back to host then adb works perfectly on the host.

I’m not sure what happened here. There should not be a private key inside the image. Somehow the emulator must have decided to create a keypair on your behalf.

When the container was restarted it was still there. Likely resulting in a mismatch between the private key inside and outside the container, which in turn would explain the auth failures. Mounting the private key as a secret partition might be the best option to prevent these types of failures.

pokowaka commented Dec 4, 2019

Your case looks different. It is possible is that the video bridge is not pushing frames because the emulator window is not changing. The problem might go away by clicking on the black screen a few times.

This is something we will have to fix in the video bridge itself.

dmarjanovic commented Dec 4, 2019

Just small addition to above comments and answer to my question:

Can you try to month private key too in addition to public key?

I’ve tried and it didn’t work. Some unknown key pair ended up in emulator container in the end completely different that those on my host. I noticed that adbkey.pub in emulator container contains @unknown at the end.

pokowaka commented Dec 5, 2019

The @unknown and the end suggests that the emulator decided to create a public key. Normally the emulator:

• Creates a private key on first boot if it doesn’t exist.
• Derive the public key from the available private key if it doesn’t exist.

NoelOmo commented Dec 9, 2019

I have literally tried everything on this thread without any success, I have even tried using a non-google api image in order to start the emulator, but it looks like the device is still stuck on the boot screen. I have attached all my logs from my emulator from the moment I start it. If anyone could have a look and let me know what could possibly be wrong I would really appreciate it.[
thelogs.txt
](url)

dmarjanovic commented Dec 9, 2019

@NoelOmo where are you running this, some VM or some Linux on bare metal? Which distro/version? Does it run emu nicely when started from Android Studio? For me it wouldn’t boot any image (even from AS) with built-in Linux nouveau drivers for GPU until I installed NVidia drivers for CentOS for this MacBook Pro.

NoelOmo commented Dec 9, 2019

I am running this on a CentOS server that is running in a VM , I have not tried running emu with AS as the server does not have a GUI. Also I do not have Nvidia graphics card on the server so Im not sure whether I am supposed to install the drivers. Do you have a Nvidia graphics card on your MBP? Can you share the link to those drivers?

pokowaka commented Dec 9, 2019

@NoelOmo I looked at the logs, you are experiencing a Kernel crash, unfortunately this results in an emulator halt. Could you share the output from uname -a ? This might give us some guidance around possible kvm kernel issues on guest and host.

dmarjanovic commented Dec 9, 2019 •

@NoelOmo my setup is quite different. I do have NVidia graphic on MacBook Pro but I doubt installing random NVdia driver would help you on your server in VM. I had to install AS since stand alone tools were giving me wrong ANDROID_SDK_ROOT error I couldn’t solve so I had to install GUI (Gnome) too. In the end I had to go with NVidia drivers since emu wouldn’t boot even headless (I followed this tutorial). I do plan to take your approach with GUI-less server in VM in order to move all to cloud and am curious where this thread goes.

pokowaka commented Dec 9, 2019 •

One option we could pursue on our end is not to use the nvidia based base image if this is not explicitly requested. This will result in an image that will not enable hardware acceleration in most cloud environments.

If you wish to try this yourself you could replace the following lines in the generated Dockerfile or the templated Dockefile:

dmarjanovic commented Dec 9, 2019 •

One option we could pursue on our end is not to use the nvidia based base image if this is not explicitly requested

Making it optional or putting the snippet above in e.g. FAQ is welcome for transparency reasons. Not sure if disabling GPU acceleration fully is the best approach.

NoelOmo commented Dec 10, 2019

@NoelOmo I looked at the logs, you are experiencing a Kernel crash, unfortunately this results in an emulator halt. Could you share the output from uname -a ? This might give us some guidance around possible kvm kernel issues on guest and host.

Herr is the output from uname -a

Linux XXXXXXXXXXXX 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

NoelOmo commented Dec 10, 2019

One option we could pursue on our end is not to use the nvidia based base image if this is not explicitly requested. This will result in an image that will not enable hardware acceleration in most cloud environments.

If you wish to try this yourself you could replace the following lines in the generated Dockerfile or the templated Dockefile:

I tried this, now the emulator health status does not go past starting, it crashes very soon after starting it up, I have attached the new logs. The following lines are the last lines before it crashes:

logcat: 12-09 17:45:58.762 1600 1684 W DeviceHAL: Error from HAL Device in function get_master_volume: Function not implemented
logcat: 12-09 17:45:58.764 1600 1684 W DeviceHAL: Error from HAL Device in function get_master_mute: Function not implemented
logcat: 12-09 17:45:58.765 1600 1684 W DeviceHAL: Error from HAL Device in function set_master_volume: Function not implemented
logcat: 12-09 17:45:58.766 1600 1684 W DeviceHAL: Error from HAL Device in function set_master_mute: Function not implemented
logcat: 12-09 17:45:58.767 1623 1623 I AudioFlinger: loadHwModu

Источник