platform_build

History

Vladimir Chtchetkine e6b969f3bc Add boot property enabling ADBD over QEMU Emulator and system image now support ADBD communication over QEMUD pipe rather than over a TCP port forwarding. However, emulator has to know ahead of time (before system starts booting) whether or not the system image supports ADBD over pipe to properly setup the communication. For that, we introduce a boot property "ro.adb.qemu" that is readable by the emulator early enough for the proper ADB communication setup. Change-Id: I978489c5acf46177b520e775d745bcc78f469837		2011-12-13 11:31:54 -08:00
..
AndroidBoard.mk	Fix build scripts for vbox_x86 target	2011-04-01 08:24:25 -07:00
BoardConfig.mk	Fix ADB, and a typo in BoardConfig.mk	2011-04-05 17:28:43 -07:00
README.txt	x86: Add in the VirtualBox emulator as a separate build target	2011-03-01 13:04:21 -08:00
device.mk	Add boot property enabling ADBD over QEMU	2011-12-13 11:31:54 -08:00
disk_layout.conf	x86: Add in the VirtualBox emulator as a separate build target	2011-03-01 13:04:21 -08:00
init.rc	x86: Add in the VirtualBox emulator as a separate build target	2011-03-01 13:04:21 -08:00
init.vbox_x86.rc	Fix ADB, and a typo in BoardConfig.mk	2011-04-05 17:28:43 -07:00
system.prop	x86: Add in the VirtualBox emulator as a separate build target	2011-03-01 13:04:21 -08:00

README.txt

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).