platform_build/target/board/vbox_x86
Keun young Park 53ba6b22f9 am 15d15136: Merge "change location of apns-conf.xml and vold.conf" into jb-dev
* commit '15d151367482b6ed47cecf1a578b365b7c6ccab3':
  change location of apns-conf.xml and vold.conf
2012-05-30 20:34:00 -07:00
..
AndroidBoard.mk Fix build scripts for vbox_x86 target 2011-04-01 08:24:25 -07:00
BoardConfig.mk am a2bfde63: am fed2587c: Merge "dalvik heapsize: Remove obsolete flag, set porperty" 2012-05-25 07:19:55 -07:00
device.mk change location of apns-conf.xml and vold.conf 2012-05-30 16:32:30 -07:00
disk_layout.conf x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00
init.vbox_x86.rc init.vbox_x86.rc: mount data & cache partitions from /dev/sdb 2012-04-06 11:04:53 -07:00
README.txt x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00
system.prop x86: Add in the VirtualBox emulator as a separate build target 2011-03-01 13:04:21 -08:00

The "vbox_x86" product defines a non-hardware-specific target intended
to run on the VirtualBox emulator.

Most of the Android devices (networking, phones, sound, etc) do not work.

ADB via ethernet works with this target. You can use 'adb install' to
test applications that do not require network, phone or sound support.
This emulation is useful because VirtualBox runs much faster then does the
QEMU emulators (at least until a KVM enabled QEMU emulator is available).