Run multiple emulator android

How to run multiple Android instances with NoxPlayer on PC

Nox is an excellent Android emulator with full Android features. One of the most favored feature is running multiple Android instances at the same time.

Check this video out:

Or follow the below steps to learn how to do that:

1. You have two way to open the Multi-player management panel of Nox. One is by double clicking the Multi-drive shortcut on your desktop:

The other is to click the below icon on the side bar of a running Nox instance:

2. At the bottom of the multi-instance manager panel, Click on “Add emulator”, then select the Android version instance you want to create ( Android 4, 5 and 7 supported), and wait for a few seconds for it to download, then it is done.

3. In the Multi-instance manager, you can also duplicate an instance you already have. This will copy all the settings and data from an instance you are already using, to a new instance.

Click on the “Copy” icon from the instance you want to duplicate.

Wait for the copying process to complete. The time will varies depending on how heavy is the instance you are duplicating.

When it is completed, now you have two android instances with completely same settings, same games and same data.

4. You can rename an instance by clicking on the little pencil that appears when you fly the mouse over its name.

5. Click on the Start button to start running an instance from the multi instance manager.

Now you could play different games or different accounts of a same game concurrently. Please note that as long as your computer supports, you could run unlimited Nox Android instances.

Источник

15 best Android emulators for PC and Mac of 2021

There are a lot of valid reasons why someone would want to run Android emulators on their PC. App developers may be trying to test their application before shipping it out. Gamers may want to use a mouse and keyboard on their games. Maybe you just want it there to have it. In any case, Android emulation on PC is possible and it’s a lot easier than it used to be. Some old favorites either left the space or became unusable at some point (Andy, AmiduOS, and Leapdroid), but everything else here should work okay for most people. Here are the best Android emulators for PC and Mac.

It’s also worth noting that Windows 11 has native Android apps support. You can read a tutorial on how that works here and you can even use the Play Store if you want to go through the effort. Being able to run apps and games natively on Windows 11 may replace emulator use for a wide variety of use cases such as gaming or general productivity.

The best Android emulators for PC and Mac

The three main uses for Android emulators

There are three main uses for emulators. The first is the most common and it’s for gaming. Gamers can use emulators on their computers to make some games easier to play. They don’t have to rely on the battery life of their devices and the existence of macros and other tricks help the process. In most cases, these little tricks aren’t illegal (in most games) so nobody really has a problem with it. The best Android emulators for gaming include LDPlayer, BlueStacks, MeMu, KoPlayer, and Nox.

The second most common use case is development. Android app and game developers like to test apps and games on as many devices a possible before launch. Fortunately, Android Studio comes with the “Android Virtual Device” (AVD) which blows all other emulators out of the water in terms of performance and functionality. The only drawback for non-developers is that it comes with an installation of the space-hungry Android Studio and Android Software Development Kit (SDK). Of course, this is no problem for developers that already have all the necessary software on their machines.

The final main type is productivity. This isn’t nearly as common because Chromebooks are cheaper and better for using Android apps on something other than a phone and most productivity tools are cross-platform. Any gaming emulator works as a productivity emulator to an extent. However, those with hyper-specific use cases and a little knowledge can try ARChon and Bliss. Even so, in this day and age, we recommend going with a Chromebook (with reasonably decent specs) if you want to run Android apps in a laptop or computer environment. It’s better that way.

Finally, a bit of a disclaimer. At this time, no emulators run the latest versions of Android except for ones made for developers. Luckily, most apps and games still function on older versions of Android so this shouldn’t be a big deal. However, most emulators right now run anywhere between Android 7.0 Nougat and Android 9.0 Pie.

BlueStacks

Price: Free

BlueStacks is known by many users to be the most comprehensive Android app player in the market, and with good reason. Aside from running on both Windows and Mac, this emulator comes jam-packed with a ton of features to improve the gamer’s experience. Its most popular features include the Keymapping Tool to create customized control schemes, the Instance Manager through which you can create multiple instances of the emulator and run several games simultaneously, and quality-of-life features like Eco Mode, which help to reduce resource consumption while running the most demanding games. It’s also the safest emulator out there, with certified GDPR compliance — your data is always safe with them.

The most recent version, BlueStacks 5, is the lightest and fastest the emulator has ever been, delivering high-performance gaming even on low-end devices. The latest version addresses some of the most common complaints of the previous version — namely, the fact that it can feel bloated, especially when running on inferior hardware. Try it right now for yourself and discover why BlueStacks has a community of over 500-million gamers around the world!

LD Player

Price: Free

Android Studio emulator

Price: Free

Android Studio is the default development console (integrated development environment, or IDE) for Android. It comes with a bunch of tools to help developers make apps and games specifically for Android. As it turns out, there is also a built-in emulator that you can use to test out your app or game. The setup is rather complicated so it won’t appeal to everyone but it is by far the fastest and most feature-rich option on this list. You can run vanilla Android, download apps from the Google Play Store as you normally would, add custom launchers and keyboards, and emulate any size or form-factor device. You can even try out foldable devices!

ARChon

Price: Free

Bliss OS

Price: Free / Optional donations

Read more:

GameLoop

Price: Free

Genymotion

Price: Free with paid options

This Android emulator is mostly for developers. It lets you test your apps on a variety of devices without owning them. You can configure the emulator for a variety of devices with various versions of Android to help suit your needs. For instance, you can run a Nexus One with Android 4.2 or a Nexus 6 with Android 6.0. You can easily switch between virtual devices at will. It’s not great for consumer uses, but Genymotion does offer its services for free for personal use. Its most useful feature is its availability on both your desktop computer and the cloud. Those without powerful computers can make Genymotion’s servers do all the work for them.

MeMU emulator

Price: Free / $2.99 per month / $29.98 per year

Price: Free

Price: Free

Read more:

Phoenix OS

Price: Free

PrimeOS

Price: Free

Remix OS Player

Price: Free

Remix OS Player by Jide is one of the newer Android emulators for PC (comparatively speaking). It runs Android Marshmallow and that’s still relatively new compared to many of the others on the list. The installation process is pretty simple and using it also fairly easy. It caters mostly to gamers. There are a few gamer specific features along with a customizable toolbar. It boasts features like running multiple games at once. That said, it’s a fairly clean emulator so it’s still perfectly usable as a productivity tool. The site seems to be down and we’re relatively certain Remix OS Player isn’t in active development anymore. It should be okay for another year or two before it starts to feel really old. We’ll replace it when we find a good 15th option.

Xamarin

Price: Free / Enterprise options

Xamarin is an IDE similar to Android Studio. The difference is that it can plug into things like Microsoft Visual Studio for an even larger development environment (for better or for worse). Also, like the Android Studio, this comes with a built-in emulator for app or game testing. In case it wasn’t readily apparent, we only recommend this one to developers. The setup is simply too tedious for regular consumer use. Xamarin’s emulator is not as powerful as something like Genymotion, but it’ll get the job done if you intend on using this and it’s also configurable for your needs. It’s free for personal use. Companies and larger teams may have to negotiate a payment plan.

Make your own

Price: Free (usually)

As it turns out, you can build your own emulator. Here’s how it works in a nutshell. You need to download VirtualBox (linked above). You then have to download an image from Android-x86.org. From there, it’s just a matter of finding one of the many guides online and following the steps. This is easily one of the more difficult methods, but still not quite as tedious or difficult as setting up a whole IDE like Android Studio or Xamarin. We don’t recommend you try without a tutorial and a little prior knowledge. It won’t work well, it’ll be buggy, and unless you’re a coder, it’ll be difficult to fix. Still, it’ll be yours to customize as you please and who knows, maybe you’ll make and release an emulator that’ll adorn this list someday.

If we missed any of the best Android emulators for PC, tell us about them in the comments! You can also click here to check out our latest Android app and game lists! Here are what happened to some old classics from the list:

• Leapdroid was purchased by Google and no longer operates.
• AMIDuOS closed its doors officially on March 7th, 2018. You can still try it out, but you have to browse the official subreddit for download links.
• Andy began using some seriously not great development tactics, including suspected bitcoin mining without user permission. We don’t know if it’s from the third-party installer or from the Andy developers so until that whole situation resolves, we’re keeping it off of the list.
• Droid4x used to be one of the best options and its later builds are still available. However, it is no longer actively updated so we removed it from the list.
• KoPlayer is an outstanding Android emulator for gamers. However, the website appears to be down as of the time of this writing. If it comes back up by the time we update this piece again, we’ll gladly add it back to the list.
• YouWave, a once-popular option, has fallen out of favor because it runs much older versions of Android than most of its competitors. You can still get it at the link, but it’s not in active development so it won’t get any more updates.
• Most of the rest simply haven’t been updated or in active development in years and don’t really work well anymore with newer operating systems and hardware. If we missed any, let us know in the comments!

Thank you for reading! Try these out too:

Источник

mrk-han / emulator-install-using-avdmanager.md

Install and Create Emulators using AVDMANAGER and SDKMANAGER

For generic skin emulator with default apis (without google apis):

List All System Images Available for Download: sdkmanager —list | grep system-images

Download Image: sdkmanager —install «system-images;android-29;default;x86»

Create Emulator: echo «no» | avdmanager —verbose create avd —force —name «generic_10» —package «system-images;android-29;default;x86» —tag «default» —abi «x86»

Run Emulator: emulator @generic_10 &

• The goal of this gist is to quickly pre-install a range of system images to provide our project teams the ability to run emulators on a range of API levels, from API 19 to API 28.
  • These can be run locally or on the base build agent.
• Note: X86 is the fastest architecture for emulators, though x86_64 would probably be better to test against because most phones are 64 bit now.
• We create two sets of emulators here, one set with pixel hardware emulation and one set with default oem emulation.

1. Run the sdkmanager —install commands.
2. Run the avdmanager commands.

• Add aliases to run the emulators with parameters more easily. Or add these parameters to your build steps in TeamCity.
  • Instead of using emulator @ to run devices, you can use the aliases if they are added.
• If you run this locally, you can use the -read-only parameter to run multiple devices at the same time. You can then manually run automation against various APIs for added device coverage during regression.

Step 1 — Run the sdkmanager commands

KITKAT (4.4) API 19

sdkmanager —install «system-images;android-19;google_apis;x86»

LOLLIPOP (5.0) API 21

sdkmanager —install «system-images;android-21;google_apis;x86»

LOLLIPOP (5.1) API 22

sdkmanager —install «system-images;android-22;google_apis;x86»

MARSHMELLOW (6.0) API 23

sdkmanager —install «system-images;android-23;google_apis;x86»

NOUGAT (7.0) API 24

sdkmanager —install «system-images;android-24;google_apis;x86»

NOUGAT (7.1) API 25

sdkmanager —install «system-images;android-25;google_apis;x86»

sdkmanager —install «system-images;android-26;google_apis;x86»

sdkmanager —install «system-images;android-27;google_apis;x86»

sdkmanager —install «system-images;android-28;google_apis;x86»

Step 2 — Use AVDMANAGER to create emulators

Pixel Emulator with Google Apis and x86 architecture

echo «no» | avdmanager —verbose create avd —force —name «pixel_4.4» —device «pixel» —package «system-images;android-19;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «pixel_5.0» —device «pixel» —package «system-images;android-21;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «pixel_5.1» —device «pixel» —package «system-images;android-22;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «pixel_6.0» —device «pixel» —package «system-images;android-23;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «pixel_7.0» —device «pixel» —package «system-images;android-24;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «pixel_7.1» —device «pixel» —package «system-images;android-25;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «pixel_8.0» —device «pixel» —package «system-images;android-26;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «pixel_8.1» —device «pixel» —package «system-images;android-27;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «pixel_9.0» —device «pixel» —package «system-images;android-28;google_apis;x86» —tag «google_apis» —abi «x86»

Generic Emulator with Google Apis

echo «no» | avdmanager —verbose create avd —force —name «generic_4.4» —package «system-images;android-19;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «generic_5.0» —package «system-images;android-21;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «generic_5.1» —package «system-images;android-22;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «generic_6.0» —package «system-images;android-23;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «generic_7.0» —package «system-images;android-24;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «generic_7.1» —package «system-images;android-25;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «generic_8.0» —package «system-images;android-26;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «generic_8.1» —package «system-images;android-27;google_apis;x86» —tag «google_apis» —abi «x86»

echo «no» | avdmanager —verbose create avd —force —name «generic_9.0» —package «system-images;android-28;google_apis;x86» —tag «google_apis» —abi «x86»

Extra Steps — Aliases and notes on resolutions

Aliases to run emulators more optimally

Note: Add this alias to

/.zshrc , or just run using these parameters for best results. -skin 768×1280 is useful to run default emulators successfully because they have a very low resolution out-of-the-box.

alias generic_4.4=’emulator @generic_4.4 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 768×1280 &’

alias generic_5.0=’emulator @generic_5.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 768×1280 &’

alias generic_5.1=’emulator @generic_5.1 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 768×1280 &’

alias generic_6.0=’emulator @generic_6.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 768×1280 &’

alias generic_7.0=’emulator @generic_7.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 768×1280 &’

alias generic_7.1=’emulator @generic_7.1 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 768×1280 &’

alias generic_8.0=’emulator @generic_8.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 768×1280 &’

alias generic_8.1=’emulator @generic_8.1 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 768×1280 &’

alias generic_9.0=’emulator @generic_9.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 768×1280 &’

Note: Add this alias to

/.zshrc , or just run using these parameters for results. Pixel emulators should run at default resolution of 1080×1920 by default, but can specify this just in-case with the parameter: -skin 1080×1920

alias pixel_4.4 =’emulator @pixel_4.4 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 1080×1920 &’

alias pixel_5.0 =’emulator @pixel_5.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 1080×1920 &’

alias pixel_5.1 =’emulator @pixel_5.1 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 1080×1920 &’

alias pixel_6.0 =’emulator @pixel_6.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 1080×1920 &’

alias pixel_7.0 =’emulator @pixel_7.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 1080×1920 &’

alias pixel_7.1 =’emulator @pixel_7.1 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 1080×1920 &’

alias pixel_8.0 =’emulator @pixel_8.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 1080×1920 &’

alias pixel_8.1 =’emulator @pixel_8.1 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 1080×1920 &’

alias pixel_9.0 =’emulator @pixel_9.0 -no-boot-anim -netdelay none -no-snapshot -wipe-data -skin 1080×1920 &’

Note You can run all of the emulators above with a -read-only parameter to run multiple emulators at the same time, but this is an experimental feature right now.

1. Certain emulators, like Pixel, need to be started at a higher resolution than default oem emulators. Either define this in the

/.android/avd//config.ini file, or start emulator with -skin as seen above.

emulator -list-avds will print list of available devices

avdmanager list , avdmanager list target , avdmanager list devices , avdmanager list avd

This comment has been minimized.

Copy link Quote reply

mrk-han commented Apr 2, 2019

alias generic_9.0 =’emulator @generic_9.0 -noaudio -no-boot-anim -netdelay none -accel on -no-snapshot -skin 480×800 &

This comment has been minimized.

Copy link Quote reply

mrk-han commented Apr 2, 2019

This comment has been minimized.

Copy link Quote reply

wellavelino commented Nov 26, 2019

Really nice gist!

This comment has been minimized.

Copy link Quote reply

gitnepal commented Mar 17, 2020

nice gist, but not helping me , avd error . cannot create devices even downloaded the images from sdkmanager

This comment has been minimized.

Copy link Quote reply

kunalvshah commented Apr 12, 2020

Hi @mrk-han
I am having an issue and thought you might be able to help. I have searched forums for this error, and tried few tricks mentioned there but nothing worked. I am receiving an error
PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [/Users/kunalshah/android/sdk]!

Can you please help fixing it ?

Here are the details of my steps.

MacBook Air (13-inch, 2017) — macOS Catalina

1. No android studio
2. installed jdk 11 from oracle
3. downloaded commandlinetools-mac-6200805_latest.zip from https://developer.android.com/studio
4. Extraced it to

/android has following structure

added tools/bin directory to Path
export ANDROID_HOME=/Users/kunalshah/android
export PATH=$PATH:$ANDROID_HOME/tools/bin

Ran sdkmanager —sdk_root=/Users/kunalshah/android/sdk —install
this created a directory /Users/kunalshah/android/sdk

ran sdkmanager —sdk_root=/Users/kunalshah/android/sdk —licenses
accepted all licenses

Installed basic tools
sdkmanager —sdk_root=/Users/kunalshah/android/sdk —install «platforms;android-R» «platform-tools» «emulator» «cmdline-tools;latest» «system-images;android-R;google_apis_playstore;x86»

new directory structure

ANDROID_HOME=/Users/kunalshah/android
ANDROID_SDK_ROOT=/Users/kunalshah/android/sdk
ANDROID_AVD_HOME=/Users/kunalshah/android/sdk/.android/avd
ANDROID_SDK_HOME=/Users/kunalshah/android/sdk

kunalshah@Kunals-MacBook-Air emulator % ./emulator @testAVD
PANIC: Broken AVD system path. Check your ANDROID_SDK_ROOT value [/Users/kunalshah/android/sdk]!

This comment has been minimized.

Copy link Quote reply

matsp commented May 15, 2020

Thanks for this gist 💯 It helped me a lot building a flutter docker image with emulator!

This comment has been minimized.

Copy link Quote reply

nagdav853 commented May 16, 2020

do anyone know the linux equivalent for ‘/Users/markhan/Library/Android/sdk’? i’m looking for it, but can’t find the folder.

This comment has been minimized.

Copy link Quote reply

giansalex commented May 26, 2020

@kunalvshah install : sdkmanager «platform-tools» «platforms;android-28»

This comment has been minimized.

Copy link Quote reply

giansalex commented May 26, 2020

do anyone know the linux equivalent for ‘/Users/markhan/Library/Android/sdk’? i’m looking for it, but can’t find the folder.

@nagdav853 is where you uncompress comandline tools.

This comment has been minimized.

Copy link Quote reply

nitish-qa-automation commented Jun 16, 2020

Hi @mrk , i am installing emulator without android studio , from cmd able to install platform tools , image , however while creating emulator getting this error

:\Users\nitis>echo «no» | avdmanager —verbose create avd —force —name «android-28» —package «system-images;android-28;default;x86»
Warning: Observed package id ‘platform-tools’ in inconsistent location ‘C:\Users\nitis\Downloads\softwares\android-sdk\platform-tools’ (Expected ‘C:\Users\nitis\Downloads\softwares\platform-tools’)
Warning: Observed package id ‘platforms;android-28’ in inconsistent location ‘C:\Users\nitis\Downloads\softwares\android-sdk\platforms\android-28’ (Expected ‘C:\Users\nitis\Downloads\softwares\platforms\android-28’)
Warning: Observed package id ‘system-images;android-28;default;x86’ in inconsistent location ‘C:\Users\nitis\Downloads\softwares\android-sdk\system-images\android-28\default\x86’ (Expected ‘C:\Users\nitis\Downloads\softwares\system-images\android-28\default\x86’)
Warning: Observed package id ‘tools’ in inconsistent location ‘C:\Users\nitis\Downloads\softwares\android-sdk\tools’ (Expected ‘C:\Users\nitis\Downloads\softwares\tools’)
Auto-selecting single ABI x86===========] 100% Fetch remote repository.
Do you wish to create a custom hardware profile? [no] Error: «no» is not a valid reply
null

This comment has been minimized.

Copy link Quote reply

mrk-han commented Jun 18, 2020

@sharmaSelenium try just running it like this avdmanager —verbose create avd —force —name «android-28» —package «system-images;android-28;default;x86»

This comment has been minimized.

Copy link Quote reply

mrk-han commented Jun 18, 2020

@matsp so happy to hear this!

This comment has been minimized.

Copy link Quote reply

mrk-han commented Jun 18, 2020 •

@kunalvshah ANDROID_SDK_ROOT and ANDROID_HOME should be set to the same thing, but I think you only need to set one. Try setting one and make sure it is the true home, or path to your SDK installation. I see you have both of them set to different places which I think may be causing your problem. https://developer.android.com/studio/command-line/variables#envar

This comment has been minimized.

Copy link Quote reply

robotickamote commented Oct 20, 2020

I tried to create an avd using android-tv system images for android-29. Seems it can’t run the google playstore app. Is this the case for earlier versions of the platform (android-28/27/26)?

This comment has been minimized.

Copy link Quote reply

josevelasdev commented Dec 22, 2020

I created an avd but when i tried to run:



the problem is in wsl when write this command:

egrep -c ‘(vmx|svm)’ /proc/cpuinfo

launch 0 it means that my CPU doesn’t support hardware virtualization. any idea?

This comment has been minimized.

Copy link Quote reply

mahdizolqadr commented Jan 21, 2021

how install «arm64-v8a» ? :((

This comment has been minimized.

Copy link Quote reply

pen-pal commented Mar 1, 2021

is there a way you map your currently running emulator with avd ??

This comment has been minimized.

Copy link Quote reply

staff0rd commented Mar 19, 2021

After running this i see the following, what causes it to be offline?

This comment has been minimized.

Copy link Quote reply

sGuid commented Apr 9, 2021 •

For @Josevelasquez above — looks like latest android platform tools (like android 26+ when they started only allowing x86/x86_64 and not arm/arm64 emulators) automatically require hardware acceleration (which does not always work with docker and other vms). Use the emulator option «-no-accel» to start emulator without hardware acceleration.
ie. emulator @android-29-x86_64-test -no-audio -no-window -no-accel

@mahdizolqadr — you want to avdmanager create avd — and look for the abi option «x86_64» option for x86_v8a — and you’ll need to download the right system image for that
ie. sdkmanager —install «system-images;android-29;google_apis;x86_64»
ie. avdmanager create avd —name android29-x86_64-test —abi «x86_64» —package «system-images;android-29;google_apis;x86_64»
Basically use sdkmanager —list. to see all the available options. and can also use avdmanager —list will also show you all the available emulator options (that you’ve custom made or that are default profiles and can be made).

offline in a real device usually means not hitting the security popup approval when you plug in the device. In emulator, it might be that you are running newer emulator with old tools, so it’s not properly able to talk to the device (which is done via the android debugger bridge aka adb). try adb —version to see what tool version is using to talk to device, and then restart adb connection with adb kill-server and then adb start-server. (ie. if your adb version is 1.0.36, which is like andorid 5, then you can’t talk to an android 29 device that’s has adb 1.0.41 or something like that). adb is located in platform-tools (to update check options in sdkmanager —list, but will probably want sdmanager «platform-tools»)

I currently have the problem with the emulator is up and running, but my unit tests run via gradlew won’t run on the device, «Found 1 connected device(s), 0 of which were compatible. . Skipping device ‘android-29-x86_64-test(AVD)’ for ‘test:’: Unknown API Level». I am using —abi «x86_64» when i create the emulator so the API level should be known. I’m sure I’m using an older version tool on newer device issue, but I can’t tell what’s not updated as I thought I updated everything, if anyone has ideas I would love to hear them. (I always wish android would give less vague error logs).

@mrk-han — your gist was really good and clear — thanks!

Источник

Читайте также:  Контроль разрешений для андроид