I've had this up n running over the last 3 - 4 days with livecode.
Rebooted pc this morning and can't get consistant results anymore.
Emulator does show up in target test devices but won't install anymore with an error.
Gotta put this on hold for now.
This alternative to the Google Emulator is actually faster than testing on my device.
1. Setup Android guest OS on VirtualBox.
2. How to run the Android guest OS on VirtualBox in portriate mode.
3. How to mount an SD card.
http://software.intel.com/en-us/blogs/2 ... irtualbox/
http://www.basic4ppc.com/forum/basic4an ... droid.html
(Note: At STEP 5 you can go straight for the Live CD option for initial testing)
http://androidspin.com/2011/01/24/howto ... virtualbox
I am enjoying B4A even more so now after installing a super-fast Android on my Windows PC. The install is actually a virtual Android (Froyo 2.2 build) and is MUCH faster than the emulator!
First of all, follow this excellent guide for setting up and installing
How to install Android x86 2.2 (with Virtual Box)
At STEP 5 you can go straight for the Live CD option for initial testing
BEFORE LAUNCHING THE VIRTUAL ANDROID
set the VirtualBox machine's network mode (under Settings > Network) to Bridged Adapter and accept the defaults. Your PC and emulated PC will now have IP addresses in the same range
Double-Click the virtual Android entry to launch the virtual x86 Android
Once the emulator is running, press Alt + F1
Type netcfg then note the IP address ** (usually starting with 192.168.x.xxx) (mine return 192.168.1.3)
Return to the emulator by pressing Alt + F7
Getting B4A to communicate with Android
Open the Windows command prompt (Start > Run > CMD)
Navigate to wherever Android\platform-tools folder is
Type adb connect 192.168.x.xxx (the address noted at ** above) (18.104.22.168)
Try compiling a B4A project. If everything is good your app/game should appear (very quickly) in the virtual Android
TIP -- You can create a *.bat file to aid in establishing the connection. This is something you can simply double-click to carry out command line instructions. My own "Android-Connect.bat" file contains the following. Change the directory and IP address as necessary
Code:(Note: you can download and install the windows utility "Command Prompt Here".
Code: Select all
m: cd android cd platform-tools adb connect 192.168.1.3 exit
Then navigate to the android-sdk-windows folder via windows explorer,
Right click on platform-toosl and select Command prompt Here.
a dos cmd window should open and you type: adb connect 192.168.1.3
Leave this dos cmd window open so you can execute the connect command again when the connecting is lost.)
Happy coding, and enjoy WARP SPEED!
Windows keys and their Android actions
Right Control (only) = Default HOST key (break out of virtual Android)
Escape key (or right-mouse button) = Android BACK key
HOME or Windows Key = Android HOME key
MENU key or middle mouse button = Android MENU key
END = Android POWER button
Right Control = Default HOST key (break out of virtual Android)