Android Question Error creating new AVD

Erel said:

Not sure, however if the emulator is critical for you then you can use Android Studio to create the AVD and it will work fine with B4A.

Click to expand...

AnandGupta said:

Is there any command line to create the avd from the existing android tools in B4X, instead of installing full Android Studio ?

Click to expand...

teddybear said:

Yes, you can use the sdkmanager and avdmanager do that without Android Studio .

Click to expand...

AnandGupta said:

Original error is from avd manager.

Click to expand...

AnandGupta said:

These are commands I used in the command line.

Click to expand...

sdkmanager --sdk_root=D:\android --install "emulator"
sdkmanager --sdk_root=D:\android "system-images;android-36;google_apis;x86_64"
avdmanager create avd --force --name MyEmu36 --package "system-images;android-36;google_apis;x86_64"
emulator -avd MyEmu36

teddybear said:

B4X:

sdkmanager --sdk_root=D:\android --install "emulator"
sdkmanager --sdk_root=D:\android "system-images;android-36;google_apis;x86_64"
avdmanager create avd --force --name MyEmu36 --package "system-images;android-36;google_apis;x86_64"
emulator -avd MyEmu36

It works for me.

View attachment 172626

Click to expand...

Microsoft Windows [Version 10.0.26200.8875]
(c) Microsoft Corporation. All rights reserved.

e:\Android\emulator>emulator -avd MyEmu36
INFO         | Android emulator version 36.6.11.0 (build_id 15507667) (CL:N/A)
INFO         | Graphics backend: gfxstream
INFO         | AVD MyEmu36 has path C:\Users\Anand\.android\avd\..\avd\MyEmu36.avd
INFO         | trying to check whether e:\Android is a valid sdk root
WARNING      | e:\Android\Android-old\system-images\android-36\google_apis\x86_64\ is not a valid directory.
WARNING      | emulator has searched the above paths but found no valid sdk root directory.
FATAL        | Cannot find AVD system path. Please define ANDROID_SDK_ROOT

teddybear said:

Enter the folder C:\Users\Anand\.android\avd\MyEmu36.avd.
Edit the config.ini file, and find and replace the entry image.sysdir.1 as below

B4X:

'Change this-- remove Android-old\
image.sysdir.1 = Android-old\system-images\android-36\google_apis\x86_64\
'To
image.sysdir.1 = system-images\android-36\google_apis\x86_64\

and then try

B4X:

emulator -avd MyEmu36

Click to expand...

Detected ADB
---------------------------
Could not automatically detect an ADB binary. Some emulator functionality will not work until a custom path to ADB  is added. This can be done in Extended Controls (...) > Settings > General tab > 'Use detected ADB location'

WARNING      | Failed to process .ini file C:\Users\Anand\.android\avd\..\avd\MyEmu36.avd\quickbootChoice.ini for reading.
WARNING      | The emulator now requires a signed jwt token for gRPC access! Use the -grpc flag if you really want an open unprotected grpc port
WARNING      | Device 'cache' does not have the requested snapshot 'default_boot'
WARNING      | Failed to load snapshot 'default_boot'