Android Question Emulator

Erel

B4X founder

Staff member

Licensed User

Longtime User

• Jan 29, 2014

• #2

I recommend you to use a real device or one of the Android virtual machines instead of the SDK emulator. The Android emulator is very slow.

 

Upvote 0

andymc

Well-Known Member

Licensed User

Longtime User

• Jan 29, 2014

• #3

You could also try instaling the HAXM plugin for the emulator to speed it up
http://software.intel.com/en-us/and...up-the-android-emulator-on-intel-architecture

 

Upvote 0

S

sorex

Expert

Licensed User

Longtime User

• Jan 29, 2014

• #4

I wasted some time with that AVD emulator yesterday as I couldn't get the others to work since they rely on OpenGL2 which my card supports but no decent driver exists for the Win8.1 I have here.

In my case the emulator configured with Intel Atom is in a loop and didn't get past the Android Boot logo.

When swithing it to ARM it booted after a few minutes and I am able to compile to it aswell.
The application install/start takes a bit longer than my slow phone but then I can test different resolution behaviours.

 

Upvote 0

E

ernschd

Active Member

Licensed User

Longtime User

• Jan 29, 2014

• #5

I recommend to use Genymotion. Its simple to install, very fast and works fine with B4A.

 

Upvote 0

S

sorex

Expert

Licensed User

Longtime User

• Jan 29, 2014

• #6

@Andy: I enabled virtualizing in the bios and installed (and ran the setup) that haxm thing. It's still stuck at the bootscreen tho.

@Ern: it installs but won't run the virtual machine due to the previous mentioned OpenGL2 issue

 

Upvote 0

S

sorex

Expert

Licensed User

Longtime User

• Jan 29, 2014

• #7

wow, seems that enabling virtualization solved the genymotion issue

seems to work more smooth but I can't compile to it, it gives this error:

Installing file to device. Error
failed to copy 'test.apk' to '/data/local/tmp/test.apk': No such file or directory

Restarting ADB Server may solve this problem.
Tools - Restart ADB Server. Device serial: emulator-5554

 

Upvote 0

S

sorex

Expert

Licensed User

Longtime User

• Jan 29, 2014

• #8

with another virtual device (S2 at 480x800 I believe) compiling works fine and very fast.

 

Upvote 0

andymc

Well-Known Member

Licensed User

Longtime User

• Jan 29, 2014

• #9

You have to install the intel image for the emulator and the "Intel x86 Emulator Accelerator (HAXM)" in the extras section of the Android SDK manager
Once installed, run the "IntelHaxm.exe" app in the folder "C:\adt-bundle-windows-x86-20130522\sdk\extras\intel\Hardware_Accelerated_Execution_Manager" your folder will probably be different but you can find your android sdk path int he paths section of the B4A tools menu

 

Upvote 0

G

ggkuwait

Member

Licensed User

Longtime User

• Jan 30, 2014

• #10

andymc said:

You have to install the intel image for the emulator and the "Intel x86 Emulator Accelerator (HAXM)" in the extras section of the Android SDK manager
Once installed, run the "IntelHaxm.exe" app in the folder "C:\adt-bundle-windows-x86-20130522\sdk\extras\intel\Hardware_Accelerated_Execution_Manager" your folder will probably be different but you can find your android sdk path int he paths section of the B4A tools menu

Click to expand...

 

Upvote 0

G

ggkuwait

Member

Licensed User

Longtime User

• Jan 30, 2014

• #11

Once agin you have all been brilliant so thank you very much. Will have a fun weekend trying all the above out and seeing which one works.
Thanks.

 

Upvote 0