As to the emulator issue not working, it should work fine even on Windows 7. As
@KMatle said, myabe it is an Antivirus and Firewall issue and which may be blocking adb. Try to turn them off.
PS: I am very happy with the latest android-emulators (with hardware acceleration -x86 - enabled). They run fine and fast and are much improved.
I should have mentioned yesterday I and deactivated the AV and Firewall and it did not make a difference.
I had also installed the Intel Hardware Accelerated Execution Manager (HAXM) for the standard Android emulator but of course that did not make a difference.
I installed GenyMotion and that did not make a difference.
Re-installing B4A and Android SDK did not solve the problem.
I elevated the security for adb.exe, b4a and even the emulator.
Today I created a virtual box (Win7) and started all over again, installing Java, Android SDK and B4A. I see installing the Android SDK is as fast as ever. ;-)
B4A simply would not connect to the emulator, regardless of what emulator I was using.
But I found out what the problem was. I was using the install instructions at
www.b4x.com/b4a.html.
I thought since it was on the b4x website it would be the most up to date reference for installing the software.
Well, I was wrong.
I should have been reading the B4ABeginnersGuidev3_2.pdf where it clearly states:
Installation instructions:
The first step should be to install the Java JDK, as Android SDK requires it as well.
Note that there is no problem with having several versions of Java installed on the same computer.
- Open the Java 8 JDK download link.
- Check the Accept License Agreement radio button.
- Select "Windows x86" in the platforms list (for 64 bit machines as well).
Android SDK doesn't work with Java 64bit JDK.
You should install the regular JDK for 64-bit computers as well.
Since I have Win 7 64bit, I had naturally installed the 64 bit version of Java. And the PDF file explicitly states the Android SDK does not work with Java 64bit. So I installed Java for Windows x86 (32bit) and presto-chango, B4A can now communicate with the emulator.
The web page at
www.b4x.com/b4a.html doesn't mention to use only the 32bit Java version. In fact, in the previous section for remote compilation, it said to download either 32bit/64bit version of Java. So naturally I thought this applied to Local Compilation as well.
I'm only reporting this in hopes it may eliminate someone else spending a day trying to solve the same problem.
I wonder if the pubs are open yet? Who's buying??