| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| | |
'entry' type enumerates values that are allowed for the given type name.
Change-Id: Ic0f4021f761dfd78ff4dd9d2b58a2d811109b3c6
|
|/
|
| |
This reverts commit 1d57949ea5bae66b27febc2edcfc7ae0f10be716
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL adds new 'enum' type to the types supported by the script.
Enumerated types should be formatted as such:
enum(type: val1[, val2[, ..., valN])
where:
- 'type' defines type of enumerated values, and must be one of the types
listed in typesToMacros
- 'val1'... 'valN' lists enumerated values, separated with a comma.
- '...' is a special value indicating that AVD editor may set property
value that doesn't match values enumerated in the .ini file. However,
default value set for the property must match one of the enumerated
values.
Change-Id: Id5c1c2940a956002e9e01a2d2456b6218f1f3742
|
|
|
|
|
|
| |
This CL provides proper handling for event socket async I/O initialization.
Change-Id: If02894a63e943c7f3db8efbab0713ed2861ecb38
|
|
|
|
|
|
|
|
|
|
| |
This is a continuation of an effort to simplify HW config, and make the UI for it clearer.
This CL gets rid of multiple camera emulation properties, combining everything into just
two properties:
- hw.camera_back that controls emulation of a camera facing back, and
- hw.camera_front that controls emulation of a camera facing front.
Change-Id: Ia114ae4caf2053685cbff00f39088e5b5be2952c
|
|
|
|
|
|
|
| |
1. Remove unused hw.camera.maxHorizontalPixels, and hw.camera.maxVerticalPixels parameters.
2. Combine hw.touchScreen, and hw.multiTouch under one property: hw.screen
Change-Id: I3cdf64f7d7e46486110cbc0769f9d98a61f0bea5
|
|
|
|
|
|
|
|
| |
The issue was that on Mac there is a bug in select() implementation, that caused select()
to fail with EINVAL on condition that timeout exceeds 100000000 secods. So the real fix
was to clamp timout value to that limit when select() is called on Mac.
Change-Id: Icb9ead00a0060028957af1e6e22911d5e8e231c6
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Patch to allow emulator searches for emulator64-${ARCH} first on
64-bit OS. If none is found, the original behavior which searchs
for 32-bit emulator-${ARCH} is performed as usual.
64-bit emulator (which still emulates Android built in 32-bit) offers
up to 20% speedup compared to its 32-bit counterpart.
Details:
android/main-emulator.c
1) search emulator64 based on the OS
2) dlopen lib64OpenglRender in 64-bit
Makefile.*
1) Rules to build 64-bit executable emulator64-{x86,arm} and libraries
emulator64-{libui,libqemu,target-i386,target-arm,libelff,common}
2) remove -Wa,-32
3) Changes prebuit toolchain path
android-configure.h
android/build/common.h
1) no longer force 32-bit build (because now prebuilts/tools/gcc-sdk/gcc
can now handle 64-bit
2) set ANDROID_PREBUILTS to correctly locate ccache
android/config/*/config-host.h
1) Detect HOST_X86_64 and HOST_X86_64/HOST_I386
Misc 64-bit porting clean-up
1) use %zx to print variable of type size_t in hex
2) use %zu to print variable of type size_t in dec
3) Initialize query_parm to NULL
4) use PRIu64 to replace PDUd64
5) use PRId64/PRIu64/PRIX64 to print 64-bit
6) drop PRUx64 because PRIx64 does the same
7) cast pointer arith to intptr_t before casting to int
8) fixed 1ULL<<63
Change-Id: Ife62a20063a6ec38d4a9b23977e840af1fce149a
|
| |
| |
| |
| |
| |
| |
| | |
The reason for crash is that event socket's I/O looper has been used without
being properly initialized.
Change-Id: I4f6372a4c2e54d5ea80313eda5208da17fc84d1d
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This CL should fix external issue 26839, where system gets loaded from a snapshot
even it is explicitly disabled in config.ini.
The reason for that was a bug in autoconfig generator that didn't respect config.ini
settings for snapshot.
Change-Id: I617e9de7f7472f8d5b75d544f81c5b160f81c2f8
|
|/
|
|
|
|
|
|
|
|
|
| |
There is a (reasonable) demand from android development comunity to increase default
data partition size. It seems that 66MB doesn't match anymore user needs. So, with this
CL default data partition size will be increased to 12MB.
This CL also fixes a bug where data partition size set by the AVD manager has been wrongly
treated as an MB value, while it was a byte value.
Change-Id: I27c456a71299aff42bd4ca573d3660292a7d1d44
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I311dc55fe10f41637775baa330a7c732ff317f51
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Commit for discuss at
https://groups.google.com/forum/?fromgroups#!topic/android-contrib/H_oodJPngHo
Because default value of hw.keyboard is "yes", emulator doesn't display
soft keyboard although text input widget has focus.
Developers can change value easily;
But users who doesn't know about property setting such as non-developer
can be confused a lot.
And, most devices has no H/W keyboard(Galaxy Nexus too).
So, set default value of hw.keyboard to "no".
Change-Id: Id3a6af23fe0525e4b8f6ccd8bbde2d6dd26e5d7d
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
When running inside the emulator, guest's adbd can connect to 'adb-debug' qemud
service that can display adb trace messages on condition that emulator has been
started with '-debug adb' option.
This CL contains emulator code that enables that.
Change-Id: I6720deef0833fd02e2fe80deeaafbcf517de0c33
|
|
|
|
|
|
|
|
|
| |
The root of the issue was that some cameras / camera drivers don't set
compression type in the bitmap header explicitly to a V4L2_XXX, but set
it to BI_RGB, which is unknown value for frame converters. To fix this,
this CL converts BI_RGB to an appropriate V4L2_XXX value.
Change-Id: Ifd70aa44138ab38fe66e8c80806a7dbb91725cf2
|
|
|
|
|
|
|
| |
This is a temporary solution fixing emulator crash due to the difficulties in
implementing GPU state save to and reload from snapshot.
Change-Id: Id62830d3447538472d3c7a83ade97f4f09dfaa06
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a fix for a user reported issue #24794. In the nutshell, when emulator grabs
a frame from webcam it leaves its bitmap in the clipboard (which is global). So, when
user does a 'paste' somewhere else, that bitmap will be pasted there. Being bad by
itself, it gets worst, because 'copy / paste' will be globally broken while camera
application is running in the emulator. I.e, if you have camera app running in the
emulator, and at the same time you're editing a Word file (for example), copy / paste
will not work in Word.
This CL contains a fix such as when possible, camera emulator on windows will not use
clipboard to grab video frames, but will grab video frames using frame callback.
Change-Id: I115a9c653b252620cf5407173c1e1eec69b4a2ee
|
|
|
|
| |
Change-Id: Ifce399aec98540fca4e1cca8c3599142d9ff6887
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Contains new routines that allow sending multiple blocks of data within a single
query. Also, these routines allow to avoid restriction on queries as zero-terminated
strings.
Change-Id: Ia5789a01a7eadbae5b1f5014a67864eea463af43
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
QEMU emulator interacts with the HAX kernel module. A HAX (Hardware-based Accelerated eXecution)
kernel module is required to use HAX support. Most guest instructions run in VMX non-root
(i.e. in hardware) mode and achieve near-native (relative to the host) performance.
QEMU still emulates PIO/MMIO instructions and non-PG (paging) mode operations.
HAX is supported only on Mac OS X and Windows hosts when Intel VT is present.
Change-Id: I8dd52a35e315437dc568f555742bb8ab7e9d8ab2
Signed-off-by: Zhang, Xiantao <xiantao.zhang@intel.com>
Signed-off-by: Xin, Xiaohui <xiaohui.xin@intel.com>
Signed-off-by: Jiang Yunhong <yunhong.jiang@intel.com>
Signed-off-by: Nakajima, Jun <jun.nakajima@intel.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Move routines that pulls values out of the parameter string from camera-service.c
to misc.c
Those are general purpose routines that are also used in multitouch emulation, so
it's better to keep it an an general utility file.
Change-Id: I02978075b64b42ff07f5042cda770bbef8939e24
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Makes sure that snapshots are not loaded if data partition for which the snapshot
has been saved is overwritten (with -wipe-data option for example). We want the
loaded snapshot to be consistent with the data underneath it.
Change-Id: I605c9b5a66870aad76ffd97d641a08c75730de7f
|
|/
|
|
|
|
|
| |
1. "<build-root>/prebuilt/android-arm/kernel/" -> "<build-root>/prebuilts/qemu-kernel/"
2. "<build-root>/sdk/emulator/skins/" -> "<build-root>/development/tools/emulator/skins/"
Change-Id: I46cf9f805506753271bf4b88cebd47faa3775f45
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changing HW configuration properties may cause emulator / guest system crash on
condition that VM has been loaded from a snapshot. This CL addresses this issue
in the following way:
1. Each time a snapshot is saved, a backup copy of HW config is saved with it.
2. Each time a snapshot is loaded, emulator finds an appropriate HW config
backup, and compares current HW config with the one that was saved in the
backup, and if configs are different, emulator exits with an appropriate
error.
Change-Id: I730bec0afbe166e88189fdcc4804b76e109e4422
|
|
|
|
|
|
|
|
|
|
| |
Warning that is displayed when "realisting sensors emulation" component in emulator
is not able to connect to an application streaming sensor changes from an actual
device, that warning confuses users, making them think that emulator didn't
initialize properly. To avoid that confusion, hide that warning under -verbose,
displaying it only if -verbose option has been specified on emulator start.
Change-Id: If40cc726db9bec4ab631dcbdcd02fb98cc30d93a
|
|\
| |
| |
| |
| | |
* commit 'd3ed299f15c993bda873cbd56648eedabc7f45c9':
Reference kernels from their new location
|
| |\
| | |
| | |
| | |
| | | |
* commit '8edd3e9e2959868ec221a1f3c1d4f9f16eb91177':
Reference kernels from their new location
|
| | | |
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Turns of webcam emulation on condition that 'camera' AVD property is set to 'false'.
Note that command line options (-webcam) will enable webcam emulation even if
'camera' AVD property is set to 'false'
Change-Id: I493446f1d12b732ed49f9a5a9967b87b31b180f6
|
|\ \
| |/
|/| |
|
| |
| |
| |
| | |
Change-Id: Idb86b2e8bbb396ee1bca606a32569b9b6b46dcb8
|
|/
|
|
|
|
|
|
| |
This way, we don't rely on the relative position of the source
directory and the out directory, and the emulator works when
using OUT_DIR_COMMON_BASE
Change-Id: I319f4fffc9ffee676d8040ebbb017831db08f6b6
|
|
|
|
|
| |
This goes invisible on case-insensitive filesystems, but fails
when XCode is installed on a case-sensitive filesystem.
|
|
|
|
| |
Change-Id: I62ff5898c7a955aaaa8af8f7ee7ed018af860f80
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Id2dbb227280f0c0e1b5708ef78b9f19b087f92d5
|
| |
| |
| |
| |
| |
| |
| | |
This is part of a bigger CL (coming later this week) that uses qemu pipes to
hook up host ADB with ADBD daemon running on the guest system.
Change-Id: I625b020531af636b9b9fa4e4aa52b7586749c693
|
|/
|
|
|
|
|
|
|
| |
The pipe client should really be closed (and destructed) only when the guest closes
its handle to the pipe. When pipe client is closed from within the emulator, it
should only notify the guest about disconnection, and wait for the guest to
explicitly close the pipe handle.
Change-Id: I6bde3ae1e05ff5dc40e9903282c3fc46df0b9b57
|
|
|
|
|
|
|
|
|
|
| |
This fixes the 64-bit Linux build (i.e. ./android-rebuild.sh --try-64).
You can't really call _mm_empty() when your target CPU doesn't support MMX.
We should probably try to use XMM registers instead of MMX for this in
the future, but this should be good enough for now.
Change-Id: If5abf747939022ef47daf7eb4badf1798e22bf95
|
|
|
|
| |
Change-Id: I54897ca86b372d98c7a30a47ecf88a4df8ee0fe9
|
|
|
|
|
|
|
|
|
|
| |
Camera framework requires that certain frame dimensions must be supported by the
camera devices. Since on Windows and Mac we have no way of knowing the real
webcam capabilities, but camera API there pretty much allows us to choose any
frame dimensions that we want, we will hard-code those that are required by
the camera framework.
Change-Id: I625381776f374103d2ac1c62fabae23b1c5afa88
|
|
|
|
| |
Change-Id: I554de3610bbd28cc299fecae4bf0199f044edb5a
|
|
|
|
| |
Change-Id: Ia2c29d890695186b04dd5d306c88aadfe084318f
|