android-emulator-m1-preview icon indicating copy to clipboard operation
android-emulator-m1-preview copied to clipboard

Is there a time-planning available yet?

Open florianmuetzel opened this issue 4 years ago • 16 comments

@Hey dev team,

do you habe a schedule for the development of the emulator? Are there any targets for RCs or final versions?

What about android studio native? The guys from JetBrains released IntelliJ as universal binary. Are they already working on a port of android studio?

Thank you so much...

florianmuetzel avatar Jan 08 '21 15:01 florianmuetzel

I hope to adapt Android studio Apple silicon as soon as possible

50kg avatar Jan 09 '21 06:01 50kg

And how soon is possible?:)

Lokni avatar Jan 10 '21 13:01 Lokni

Hi, we have a mechanism out in canary in Android Studio that should replace the downloaded emulator with this one once it tries to one. Then you create a Android R ARM64 AVD from there (need to go to Other Images tab).

We're working on adding architecture detection functionality to the SDK Manager which should make this more clean.

741g avatar Jan 14 '21 17:01 741g

Canary Android Studio + ARM64 image got the job done for me! Emulates very nicely - great work!

zholmes1 avatar Jan 20 '21 20:01 zholmes1

Hi, we have a mechanism out in canary in Android Studio that should replace the downloaded emulator with this one once it tries to one. Then you create a Android R ARM64 AVD from there (need to go to Other Images tab).

Hmm, should this work with 2020.3.1 Canary 4 ?

image

I see nothing which shows me a working image

image

Or how should it work ?

hannesa2 avatar Jan 21 '21 06:01 hannesa2

@hannesa2 Just use that first image under "Other Images". It gives a warning for VT-x but that doesn't affect us with arm64

zholmes1 avatar Jan 21 '21 06:01 zholmes1

I tried first image, but it's not able to start image

@zholmes1 How does your Emulator looks like ?

hannesa2 avatar Jan 21 '21 06:01 hannesa2

@hannesa2

Same as the one you have selected. Make sure you update your emulator in SDK Manager. Maybe you could try uninstalling the emulator and reinstalling it. The first thing I did after I opened Canary was updated the emulator.

zholmes1 avatar Jan 21 '21 07:01 zholmes1

I tested on command line ~/Library/Android/sdk/emulator/emulator -avd Pixel_5_API_30 to see error

image

And this works on your side ? -curious-

It looks like user lyang is somewhere hard coded In the avd directory of Emulator at least not

image

hannesa2 avatar Jan 21 '21 07:01 hannesa2

My system has no install-qt at all

image

But I found something here /Applications/Android Emulator.app/Contents/MacOS/emulator/lib64/qt/lib/libQt5GuiAndroidEmu.5.dylib

How to solve this ?

hannesa2 avatar Jan 21 '21 07:01 hannesa2

@hannesa2 You'll need to use the latest preview, that should be fixed since a rev to the V1 preview

741g avatar Jan 21 '21 09:01 741g

I used the latest v3 already. Anyway, I deleted Emulator form Android Studio 2020.3.1 Canary and reinstall v3 again. Then I created a new Emulator from "Android Device Manager" with "other image" R like before, now usage of hard coded path is gone, but I run into

image

From where should this QT plugin comes from ?

Emulator start from/Application works properly

hannesa2 avatar Jan 21 '21 11:01 hannesa2

Emulator is not working in cancary build after for the update for emulator.

premkumar5012002 avatar Feb 04 '21 17:02 premkumar5012002

@hannesa2 It's possible that the self-delete of the x86 download and redownload of the arm64 version was incomplete. Recommend using emulator from /Application for now as we'll soon introduce a way for SDK Manager to download the latest arm64 version directly.

@premkumar5012002 Can you try running from $ANDROID_SDK_ROOT/emulator command line?

741g avatar Feb 04 '21 17:02 741g

Also, check Studio's idea.log. What was the command line used there?

741g avatar Feb 04 '21 17:02 741g

image

I see now image

hannesa2 avatar Apr 16 '21 08:04 hannesa2