Android Question AVD Manager - device definition not found

[Dave O]

The B4A SDK Manager works fine for me, but when I open the AVD manager, no devices are shown in the list.

When I try to create an AVD (regardless of the settings I choose), I get a "device definition not found" error.

(In Android Studio, I can open the AVD manager and start emulators just fine, but I'd really like to be able to do it directly from B4A.)

 

[Erel]

Please run the Sdk Manager from B4J: https://www.b4x.com/android/forum/t...-20-adds-support-for-google-based-avds.87832/ and check the logs.

Are you using the same SDK with B4A and Android Studio? It will cause problems.

 

[Dave O]

Yes, I'm using the same Android SDK for Android Studio and B4A. I was hoping they could co-exist so I wouldn't have to maintain separate SDKs, paths, environment variables, and so on.

For B4A, I'm using the SDK Manager from B4A 8.0. Is the B4J version (3.21) newer?

 

[Erel]

I was hoping they could co-exist so I wouldn't have to maintain separate SDKs, paths, environment variables, and so on.

B4A Sdk Manager doesn't require any of these. Just install it in a separate folder and let it update the SDK.

 

[juhacz]

I have the same issue "device definition not found". I have only installed sdk for b4a (i reinstalled sdk, 5 times). Some time ago I have installed AndroidStudio, but I unistalled it. I dont know how to resolve problem
b4a 8.0
avd manager 3.25

 

[Erel]

Hard to say. Installing a new SDK in a new folder usually solves this problem. However you shouldn't use the emulator as your first choice. Use a real device with B4A-Bridge instead.

 

[sunish]

I am using B4A 8.3 and getting the same message while trying to create a new AVD. AVD Manager shows version 3.27 and lists platform 24 and 27 (google_apis and google_apis_playstore) Irrespective of which ever platform and Screen Size I select I get Device Definition not found for the selected resolution. SDK is installed in a separate folder and Android Studio was uninstalled before updating using B4A SDK Manager.

 

[Erel]

Reinstall the SDK in a new folder might solve it. Note that currently it will only work with Intel CPU PCs.

 

[sunish]

This is a new install folder C:\dev\Android\android-sdk-b4a after I had problems running SDK manager with an AndroidStudio version. Now there is no Android Studio and SDK Manager updates fine. It's an Intel CPU machine with HAXM already installed. It's only AVD manager causing problems while creating AVD. I looked for updated source for SDK/AVD manager to run B4J but couldn't find it on the forums.

 

[Erel]

You can install Android Studio and run the emulator from Android Studio. B4A will find it if the emulator is already running.

 

[sunish]

I had uninstalled Android Studio, I will try after installing it.

 

[JohnC]

I too am getting this error and I just did a complete reinstall of the B4A SDK manager into a new directory.

The one thing that was confusing is that the SDK manager said "Intel x86 Emulator Accelerator (HAXM Installer)" was already installed, but when I run the AVD Manager, the top center of the app displays a button called "Download HAXM" - so I downloaded and did the silent install.bat and it didn't give any errors, and I still get the error in the OP.

I don't have Android Studio installed.

Any ideas?

 

[Erel]

You can try to run the manager from the B4J project and check the logs. There might be more information there.

 

[JohnC]

I don't have B4J installed on my PC - is there anything else I can try?

UPDATE: I uninstalled Java, reinstalled the latest version and reinstalled the B4A SDK Manager and all recommended items and the emulator is working now.

Except when I start it, it says that the ADB.exe is obsolete and has "serious performance problems" (the one from the sdk-tools-windows-3859397.zip link you have on https://www.b4x.com/b4a.html).

Any idea why it says this?

 

[Erel]

Except when I start it, it says that the ADB.exe is obsolete and has "serious performance problems" (the one from the sdk-tools-windows-3859397.zip link you have on https://www.b4x.com/b4a.html).

Any idea why it says this?

Use the search engine. It works very good: https://www.b4x.com/android/forum/pages/results/?query=ADB.exe+is+obsolete

If you are unable to find the answer then always start a new thread for a new question.

 

[Jaames]

Hi, just to say , when you do clean install (after fresh windows installation) and install B4A as it is suggested on B4A homepage , extract sdk (sdk-tools-windows-XXXXXX)
for example to the "D:\Android\sdk" point B4A SDK manager to the sdkmanager.bat , install Recommended , (intel HAXM installed) no matter which platform you download, the same error as the OP will occur .. No Android studio or any other android sdk except one mentioned in this post..

(If I find solution I'll post it here)

 

[Erel]

If you want to debug it then download the B4J source code: https://www.b4x.com/android/forum/threads/gui-avd-manager-emulator.80348/#post-555749

The error happens in AVDManager.btnCreateAVD_Action.
Add these lines before the For Each loop:

Log("************** devices *********************")
   Log(Devices)
   Log("*****************")
   Log(screen)

What is the output?

 

[Jaames]

It seams that "Devices" list is empty ..

************** devices *********************
(ArrayList) []
*****************
[IsInitialized=true, ScreenName=4" Phone (480 x 854, scale = 1.5), Skin=WVGA800
, Scale=240, DDName=4", EmulatorName=4in_Phone
]

 

[Jaames]

And there is complete log :

Spoiler: Log

DataFolder: C:\Users\james\AppData\Roaming\B4ASdkManager
Java Path: C:\Program Files\Java\jdk1.8.0_181\jre
Available Android Virtual Devices:
Parsing D:\Android\sdk\build-tools\27.0.1\package.xmlParsing D:\Android\sdk\emulator\package.xmlParsing D:\Android\sdk\extras\google\usb_driver\package.xmlParsing D:\Android\sdk\extras\intel\Hardware_Accelerated_Execution_Manager\package.xmlParsing D:\Android\sdk\patcher\v4\package.xmlParsing D:\Android\sdk\platform-tools\package.xmlParsing D:\Android\sdk\platforms\android-24\package.xmlParsing D:\Android\sdk\platforms\android-27\package.xmlParsing D:\Android\sdk\platforms\android-28\package.xmlParsing D:\Android\sdk\system-images\android-24\default\x86\package.xmlParsing D:\Android\sdk\system-images\android-27\google_apis_playstore\x86\package.xmlParsing D:\Android\sdk\system-images\android-28\default\x86\package.xmlParsing D:\Android\sdk\system-images\android-28\default\x86_64\package.xmlParsing D:\Android\sdk\system-images\android-28\google_apis_playstore\x86\package.xmlParsing D:\Android\sdk\system-images\android-28\google_apis_playstore\x86_64\package.xmlParsing D:\Android\sdk\too...
id: 0 or "tv_1080p"
Name: Android TV (1080p)
OEM : Google
Tag : android-tv
---------
id: 1 or "tv_720p"
Name: Android TV (720p)
OEM : Google
Tag : android-tv
---------
id: 2 or "wear_round"
Name: Android Wear Round
OEM : Google
Tag : android-wear
---------
id: 3 or "wear_round_chin_320_290"
Name: Android Wear Round Chin
OEM : Google
Tag : android-wear
---------
id: 4 or "wear_square"
Name: Android Wear Square
OEM : Google
Tag : android-wear
---------
id: 5 or "Galaxy Nexus"
Name: Galaxy Nexus
OEM : Google
---------
id: 6 or "Nexus 10"
Name: Nexus 10
OEM : Google
---------
id: 7 or "Nexus 4"
Name: Nexus 4
OEM : Google
---------
id: 8 or "Nexus 5"
Name: Nexus 5
OEM : Google
---------
id: 9 or "Nexus 5X"
Name: Nexus 5X
OEM : Google
---------
id: 10 or "Nexus 6"
Name: Nexus 6
OEM : Google
---------
id: 11 or "Nexus 6P"
Name: Nexus 6P
OEM : Google
---------
id: 12 or "Nexus 7 2013"
Name: Nexus 7
OEM : Google
---------
id: 13 or "Nexus 7"
Name: Nexus 7 (2012)
OEM : Google
---------
id: 14 or "Nexus 9"
Name: Nexus 9
OEM : Google
---------
id: 15 or "Nexus One"
Name: Nexus One
OEM : Google
---------
id: 16 or "Nexus S"
Name: Nexus S
OEM : Google
---------
id: 17 or "pixel"
Name: Pixel
OEM : Google
---------
id: 18 or "pixel_c"
Name: Pixel C
OEM : Google
---------
id: 19 or "pixel_xl"
Name: Pixel XL
OEM : Google
---------
id: 20 or "2.7in QVGA"
Name: 2.7" QVGA
OEM : Generic
---------
id: 21 or "2.7in QVGA slider"
Name: 2.7" QVGA slider
OEM : Generic
---------
id: 22 or "3.2in HVGA slider (ADP1)"
Name: 3.2" HVGA slider (ADP1)
OEM : Generic
---------
id: 23 or "3.2in QVGA (ADP2)"
Name: 3.2" QVGA (ADP2)
OEM : Generic
---------
id: 24 or "3.3in WQVGA"
Name: 3.3" WQVGA
OEM : Generic
---------
id: 25 or "3.4in WQVGA"
Name: 3.4" WQVGA
OEM : Generic
---------
id: 26 or "3.7 FWVGA slider"
Name: 3.7" FWVGA slider
OEM : Generic
---------
id: 27 or "3.7in WVGA (Nexus One)"
Name: 3.7" WVGA (Nexus One)
OEM : Generic
---------
id: 28 or "4in WVGA (Nexus S)"
Name: 4" WVGA (Nexus S)
OEM : Generic
---------
id: 29 or "4.65in 720p (Galaxy Nexus)"
Name: 4.65" 720p (Galaxy Nexus)
OEM : Generic
---------
id: 30 or "4.7in WXGA"
Name: 4.7" WXGA
OEM : Generic
---------
id: 31 or "5.1in WVGA"
Name: 5.1" WVGA
OEM : Generic
---------
id: 32 or "5.4in FWVGA"
Name: 5.4" FWVGA
OEM : Generic
---------
id: 33 or "7in WSVGA (Tablet)"
Name: 7" WSVGA (Tablet)
OEM : Generic
---------
id: 34 or "10.1in WXGA (Tablet)"
Name: 10.1" WXGA (Tablet)
OEM : Generic
************** devices *********************
(ArrayList) []
*****************
[IsInitialized=true, ScreenName=4" Phone (480 x 854, scale = 1.5), Skin=WVGA800
, Scale=240, DDName=4", EmulatorName=4in_Phone
]

 

[Erel]

Try it with the attached version.