Since everyone else is having problems getting their device recognized by ADB and Android Studio, I want to use this opportunity to breathe fresh air into this topic by having the exact opposite problem.
My Android Studio is randomly detecting a "unknown device" in the list of devices. If I run the connection troubleshooter it sometimes list an "emulator-5554" device.
emulator-5554
- Device was detected by ADB but not Android Studio
The only problem is I have no physical or virtual device running on my PC. The issue started recently and it's appearing and disappearing in like a few seconds interval. I'm going crazy because I can't find the cause of the issue, and when I have my phone connected, if I click "Run" at the moment the random device appears, it will try to install it there, but it disappears again and then it just fails to install instead to install it onto my phone.
My Android Studio:
Android Studio 3.5.1
Build #AI-191.8026.42.35.5900203, built on September 25, 2019
JRE: 1.8.0_202-release-1483-b03 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0
Related
I'm using Android Studio 3.4 on Linux Debian 9 x64 and phone Samsung SM-A10 with Android 9 Pie.
Phone is completely new and clean with latest security patch.
Every time I'm installing apk directly from Android Studio to the phone, I have to re-plug USB cable, otherwise installation stucks with "Installing..." message in status bar of the Studio. No any error messages.
What is weird - my other phones with Android 7, 8 works well - Android Studio installs the same project well, every time I click "Run" icon.
But with Samsung A10 (Android 9), the situation always looks like:
The phone connected with a USB cable
I click the "Run" icon in the Studio
Installation gets stuck with "Install..." status
I re-plug USB cable and click "Run" again.
Apk installs well.
...
I click "Run" again (does not matter if the previous app removed from the phone or not)
Installation gets stuck
I have to re-plug cable again
Also, when I download big (>100mb) file from this phone (with "adb pull ...") it gets stuck too and was solved with cable reconnect for few attempts.
What I've tried:
reboot phone
reboot PC
re-enable USB debugging in Android developer menu
enable "Instant Run" (usually I'm not using it)
run other apps
run debugging in Android Studio - does not start at all, gets stuck on different steps (loading some library, mostly); No error messages too
I am trying to run my app on canary build of the android emulator from android studio on AMD processor but I am getting the following error
1:47 PM Emulator: [2440]:INFO:android/android-emu/android/verified-
boot/load_config.cpp:236:Verified boot params were not found.
1:47 PM Emulator: **
1:47 PM Emulator: ERROR:/usr/local/google/buildbot/src/android/emu-master-
dev/external/qemu/fpu/softfloat.c:486:round_canonical: code should not be
reached
1:47 PM Emulator: Process finished with exit code 3
I got to know about the canary build of the android emulator for AMD processor from here. My virtual device' CPU/ABI is armeabi-v7a. I searched for what the 'exit code 3' for the emulator mean but I didn't get any solution.
Can someone help me please!
I got the android emulator working today.
I have done the instalation process for canary build of android studio from the beginning:
1. Enabled "Hyper-V" and "Windows Hypervisor Platform" in "Turn Windows features on or off" settings of Windows. This has been explained in here.
2. Downloaded the latest Canary build of Android studio from here.
3. After downloading the zip file I followed the guidelines in here under "Install alongside your stable version" heading. The guide lines are:
a. Unpack the ZIP file.
b. Rename the resulting folder to something unique like "Android Studio Preview."
c. Move it to a permanent location, such as next to your existing Android Studio install in C:\Program Files\Android.
d. Inside C:\Program Files\Android\Android Studio Preview\bin\, launch studio64.exe (or if you're on a 32-bit machine, launch studio.exe).
4. After launching studio64.exe I got a pop-up message to update Android emulator. After the update I created a new virtual device with an image of x86 with android 9.0. I started the android emulator to test my app. Though I got the
Verified boot params were not found
popup error message initially, the emulator started functioning well.
I am a very new Android developer and was until today having the same issue as yourself. Here is how I got it to work (Please note I am also on an AMD system).
Make sure you have enabled Hyper-V and Windows Hypervisor Platform. If you type "turn windows features on" in your run bar you should be able to locate it. Also enable virtualisation in the Bios. Mine comes under "SVD".
(Please note after this step I was still experiencing the problem but this is a pre-requisite).
Delete all devices from the AVD manager.
Install a new x86 device from the AVD manager. What I did here was select a version down from the one I was previously getting issues on so Oreo from Pie. When it asks to confirm if you want to wipe the user data please confirm positive.
Once setup, run the device from the AVD manager. It may ask you if you wish to enable Instant Run. I elected to disable this. (I had enabled it when I first was trying to run a device).
You will still receive the 1st error regarding no boot parameters but the emulated environment should load. You can now run the APP and it should install the APK. Previously due to the device not coming online properly, the APK would not install. I can also now setup a device on Pie without experiencing the issue so I think it may have been the wiping of the previous data that helped.
I wish I could tell you WHY this worked for certain and previously it would not work, sadly I cannot but hopefully this will get you working.
I have a fresh Windows 10 installation on my MacBook Pro (Late 2016) along with the newest Bootcamp drivers. Everything is working and shiny up until now.
When I install Visual Studio 2017 Enterprise it works up to a point where the reboot takes place. This takes really long, but windows is starting again, for about 7 minutes windows boots while showing the loading indicator. When I'm finally prompted for Login, the MacBooks keyboard and trackpad doesn't work anymore, as we'll as I don't have a wifi connection or audio (having the x sign in taskbar).
I tried the whole painfull process three times now while ending up with the same problem. Windows is broken, which means I can't reinstall the bootcamp drivers (crashes system), no system restore points can be restored (failing), I can't reset windows (breaks the boot process and results in a blank screen). I guess this is somehow related to an intercompatibility between bootcamp and Visual Studio 2017.
I'm not sure if this is related to any specific components of VisualStudio which I install. I'll try a minimal install next...
It was the same for me, Windows 10 was loading 5-8 minutes and no keyboard and touchpad support. After 3-5 re-installs(windows and VS2017), found that issue caused by Hyper-V virtualization. It is disabled by default, but as soon as you installed VS 2017 with at least one component which require Hyper-V, you will never be able to login to you windows on macbook pro.
Just DO NOT install any emulators:
Google Android emulator,
Intel hardware accelerated execution manager(HAXM),
Visual Studio emulator for Android,
Windows 10 Mobile Emulator
And Windows will work fine.
Yesterday, I installed Android Studio's latest version on Ubuntu. Everything ran fine, until I ran the "Hello World!" program. It asked me to create a virtual device. While creating the device, it shows me an error that the AVD manager cannot find a system image. This makes no sense since I have already installed the latest SDK (API level 25, Android 7.1.1). I downloaded the system image from the AVD manager itself, but to no avail.
Can someone help me sort the damn thing out? I switched from Windows to Linux due to the plethora of problems with Android Studio on Windows. But the thing's bugging once again. Here is a screen shot:
Running windows 7 and I have just downloaded the latest android studio version and started a project and now I'd like to test the application on my device but Android Studio says on the bottom left "No devices connected". I've tried a couple of things such as:
updating my Samsung S6 edge drivers through device manager, which were updated now.
have debugging mode turned on and USB debugging mode on.
ran 'adb devices' command to list devices but none show up.
downloaded new universal adb drivers.
toggled between MTP and PTP modes.
restarted computer/phone/android studio/ adb tens of times.
deleted phones drivers from device manager and installed again.
re-installed android studio.
probably some other small things too that I can't remember right now.
I'm at a loss as of right now, if someone can help me out I would really appreciate it!