I'm having trouble getting my emulator to work on my m1 mac. Currently, I am waiting on my physical android phone to arrive so I have to use an emulator for the moment. I have looked at the official google repo (https://github.com/google/android-emulator-m1-preview) for the m1 preview and I noticed it said "Support for downloading the M1-based emulator was added to SDK Manager, so it's not necessary to go to the Github releases page to download a standalone .app anymore. In AVD Manager go to the Other Images tab as by default it doesn't show the ARM64 images." However, I can't seem to find which SDK to download in the SDK manager as every time I attempt to cold boot a virtual device it simply returns the error "Could Not Start AVD".
Sorry if this has been asked before. Couldn't seem to find any posts about it.
So it took some time but I figured it out. In the updated Android Studio you have to create a new virtual device for ARM based machines. Once you select your new device and you get to what android release you would like to run, hit the "other" column. Now you have a list of some of the ARM based Virtual Devices.
Here is a link to a post I found that helped:
Android Studio - How Can I Make an AVD With ARM Instead of HAXM?
Android Studio Dolphin, Virtual Device Manager, now includes arm64a-v8a for Tiramisu API level 33, which works well for M1 mac.
Problem Picture
Hey guys. I just installed to flutter and android studio. So, I new installed to emulator. I started to follow a tutorial and in there, instructor's emulator's name was in the devices label but mine is not like it(it says no devices.As i show in picture). Also, when i was click over devices button I can open my emulator. My question is, can my emulator work as manuel, with my manuel click or do you have any advices for me about this? Thanks in advance.
When you start your emulator for the first time, you must authorize your computer to access it by enabling the USB debugging on it in the Phone Settings and by changing the Use USB for to Transferring files
First post--be gentle. Can't find any posts on Android Studio 4.0, so I hope this isn't a repeat. I updated Android Studio from 3.6.3 to 4.0 on Windows 10 (1909). Had created a couple of virtual devices in 3.6.3 (a Pixel 2 running API 28 and a Pixel 3 running API 29)--both worked great in AS-3.6.3 and I could develop apps, compile, load, and run them with no problem.
After the update to AS-4.0, the virtual devices no longer appear in the devices box at the top of the GUI--it just says "No Devices". When I open the AVD Manager, I can see them, and I can start them (although when I start them I get a pop-up saying "AVD Manager: Unable to locate adb"), but I can't get any code to download and execute on it. On the Pixel 3 emulator, I also get another pop-up saying "Detected ADB: Could not automatically detect an ADB binary.", and it gives instructions to resolve it, which don't make any difference (jump into extended controls and toggle "Use detected ADB location").
When I try to open a past project and run it, I get the same behavior--no devices found.
I've also tried making new emulators, hoping the new setup would recognize them, but to no avail. Tried starting and restarting AS, as well as the computer, also to no avail. I have Android SDK Build-Tools 30-rc4, the latest Android SDK Command-line Tools, Android Emulator 30.0.12 Android SDK Platform-Tools 30.0.1, and the Intel x86 Emulator Accelerator all installed.
I've Googled and spoken words of fierce power over this for several days now. Any suggestions for how to get AS-4.0 to recognize the emulators? I've resisted uninstalling everything and starting over--was hoping it was just a configuration thing.
Thanks in advance,
Uber
After some more Googling, I found the answer here (I think my constraint of wanting an answer for AS-4.0 specifically kept me from finding it):
Could not automatically detect an ADB binary - Android Studio
I had to redownload the SDK platform-tools zip file and reinstall it. I don't know why the old one got messed up with the migration from AS-3.6.3 to 4.0, but there you go--such is life with complicated software.
As soon as I replaced the old platform-tools directory with the new one, all my old emulators showed up and I was back in business.
Thanks anyway!
Uber
A young friend of mine would like to push a game created using www.buildbox.com to his Samsung Android Tablet. He is using Windows 10 and Android Studio 3.6.1.
But the Device Drop Down is greyed out and for some reason the AVD Manager, the SDK Manager and the Connection Assistant are missing from this tools menu.
On my Android Studio 3.4 I can still see the Connection Assistant
I checked the Release notes but could not find anything.
https://developer.android.com/studio/releases
I checked that Windows can see the tablet as a USB device and the friend told me that developer mode is enabled.
Any ideas what is going on ?
So I got a chance to look further into the problem.
It turned out, that the problem seems to be with Buildbox not generating a proper Android project. In particular the generated project is missing a proper module and a proper app configuration. Once I added those the missing connection tool reappeared.
However I still got an error.
This question already has answers here:
Cannot see Nexus 6P for debugging
(5 answers)
Closed 4 years ago.
I am struggling to figure out the problem with my device not being recognized in Android Studio. However I do see it from file explorer and can browse the device files.
OS: Windows 10
Device: Nexus 6P
Yes, I did some research before posting this question, so I'll enumerate what I tried:
Enabled USB Debugging
Installed Google USB drivers from the SDK manager
Intalled HiSuite(apparently including some device drivers)
Switching between MTP/PTP
Restarting Android Studio several times
Restarting my computer several times
Every USB 2/3 ports of my computer
Tried updating drivers from device manager(however it did not suggest anything)
adb kill-server / start-server
Any suggestions would be greatly welcome!
Thanks in advance!
Apparently, installing 'Google USB Drivers' from the SDK Manager doesn't actually install them!
You have to go to:
'C:\Users\your_user\AppData\Local\Android\sdk\extras\google\usb_driver\'
right-click on 'android_winusb.inf' and install.
Try to use ADB over Network but it depends what Android version you have.
In Developer options you should see ADB over network section if not then sorry for this unhelpful advice.
check for SDK platforms in Android Studio whether you have installed the Android 6.x(N), Because Nexus got Android N updates, so it may be one of the issue you faced...
When I had this problem what I did was install the drivers manually. What you do is download the drivers from the google website NOT with Android Studio then you go into device manager and right click on your nexus. Then go to drivers tab and hit the update then manually find drivers on computer. Navigate to the downloaded drivers and click on them. Device manager will install your drivers and should fix the problem. Also for drivers you may want to try this or this driver Also please post these kinds of questions on the Android Stack Exchange Thanks!
If you have already tried all those steps , i would like you to install pdaNet software . This will automatically detect and repair the driver and you can find device in Android Studio.
This has worked for me
SO references :
Android studio doesn't list my phone under "Choose Device"
eclipse or android studio not recognize my phone on usb debugging mode
References for installing the drivers and enabling USB debugging is available here for reference , you could cross check with as well.
Reference 2 : Installing pdaNet
First of all I make sure that I've installed google's usb_driver. Either through the SDK or what SlashJ said:
Apparently, installing 'Google USB Drivers' from the SDK Manager doesn't actually install them!
You have to go to:
'C:\Users\your_user\AppData\Local\Android\sdk\extras\google\usb_driver\'
right-click on 'android_winusb.inf' and install.
- SlashJ
After that's done:
Insert your device into your PC
Open device management
Click start > run devmgmt.msc
Right click my PC > manage > devices in left panel
Check if there's a tab android device and look for your device or an ADB Interface, Otherwise just search for your device
Right click your device and Update Driver Software
Browse my computer for driver software
Let me pick from a list
Search for google or android in the left pane.
And select ADB Interface in the right.
Continue installation and it should work now.
You can try to unplug and re-plug your android device.
Maybe you also have to enable developer mode on the device.
Here's a walkthrough
I have a similar problem with my Wiko phone, I had installed the wrong usb driver and I could not do it manualy.
In developer mode, enable the usb debuging
Try to update your driver with apk installer for Windows 10 even if it is already installed:
APK DRIVER
This tool permits to install automaticaly the right driver.
Have a look to my previous question fo further details:
How can I run my ionic app on a physical device (Wiko phone) on Windows?
i just have that problem and anything works for me
what help me is to click a lot of time on the build number (setting-about phone-build number) and magic happens :)
Did you check in Android Studio Run tab->Edit Configurations->Target set to USB device.
if that doesn't work, try updating Android Studio, and/or device's firmware, also here is a similar question, involves a nexus and windows 10: https://stackoverflow.com/a/31938193/3817308
I hope this help.
I'm not sure how you installed adb driver. If your device is displayed in device manager but not as a ADB device, try these steps
Go to Control Panel and open Device Manager.
Find the device
Right click the device and select properties.
Select Driver tab, then click the Update Driver button.
Choose Browse my computer for driver software.
Let me pick from a list of device drivers on my computer
Browse for the .inf driver file. Open and Next.
Select ADB interface from device list (i can't remember the exact name)
Install
There's another another Stack post (Cannot see Nexus 6P for debugging) you might want to try.
You need to manually download the driver here (http://developer.android.com/sdk/win-usb.html)
Go to "Devices and Printers", right-click on "MTP", and choose properties.
Click "ADB interface", then click "Properties"
Go to "Driver" tab and update driver with the file you just downloaded. (Make sure you unzip them first)