| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
Bug: 24875598
Use ExactCalculator for AOSP builds.
This is a manual (due to intervening commits) cherrypick of
commit 53c5891460408ffe37f2aecc2044320d49cef801 (ag/748830).
Change-Id: I6c0acef640e62f8a70b7b2832b7eea662a0d301b
|
|\
| |
| |
| |
| | |
* commit '393c62549a6340b3473f14b71d583e118d7e6a6d':
Really include drawables for all densities.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Previously with "PRODUCT_AAPT_CONFIG := normal" resource with modifier
"small" isn't included.
Bug: 21643610
Change-Id: I53940d716fb9705462b1abb882e04103e211f8af
|
|\ \
| |/
| |
| |
| | |
* commit '2ad5c0cca46b7f0a159dbc90243756c84a93b093':
emulator.mk: Add ethernet permission
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Networking on old emulator device(a.k.a. goldfish) relies on RIL;
However, RIL is not available on ranchu device yet. For ranchu device
to have a functional networking, we need to add ethernet permission
and start dhcpcd_eth0 service on ranchu device. This CL adds ethernet
permission to both goldfish (which is harmless) and ranchu devices.
This addition was originally proposed by miroslav.tisma@imgtec.com
and the ethernet permission was only added to arm64 and mips64 after
discussion. With the ranchu device supporting more architectures,
it makes sense to allow this permission on all devices and all CPU
architectures.
related CL by miroslav.tisma@imgtec.com on AOSP:
b09fb84becf73bf2bc578ebf27910d75b79d668a
bug: 24070972
Change-Id: I81ac5d8901adee43784fe9dd45a170fb90bb824a
|
| |
| |
| |
| |
| |
| | |
Bug=23633457
Change-Id: I26bbc5ff597138b2ccac1de72117753739b31554
|
|\ \
| |/
| |
| |
| | |
* commit '956e469327b1da4b635f20795ed48f6c36ba10d6':
Increasing MIPS emulator system image size and user-data image size
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Size increase taken as a precaution against recent built breakage
due to lack of space on a number of targets (e.g. x86, ARM64).
System and user-data image sizes set to match currently most common
setup for the emulator: system image: 1.25gb, user-data image 700mb.
Change-Id: I7118eb26dd78f5fa9e4f0006e15c8d47dee8e28c
|
|\ \
| |/
| |
| |
| |
| |
| | |
builds." into mnc-dev
* commit '5bf35d0685ba62ded55cc63f3dd2f23b82cc645d':
Include new AOSP messaging app in base AOSP telephony builds.
|
| |
| |
| |
| |
| |
| | |
b/23110861
Change-Id: I31ba32f3341c77ba6eb083a189dffa1a08c6c8d4
|
|\ \
| |/
| |
| |
| |
| |
| | |
with API 23 rules" into mnc-dev
* commit 'a0372e20a24283002c2d27b372194d88e1983a3f':
Removing VisualizationWallpapers as it does not comply with API 23 rules
|
| |\
| | |
| | |
| | | |
rules" into mnc-dev
|
| | |
| | |
| | |
| | |
| | | |
Bug: 23021372
Change-Id: Ib985ac99bd9068c21f8a1c48e77c72426f69ea79
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
into mnc-dev
* commit '745d11ccd077060b5d3b0e3e53682e8c1f85dd66':
Revert "Include new AOSP messaging app in base builds."
|
| |\ \
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit a8b0905e165448857ad45d1633c545c53bd53a5e.
Change-Id: Ia8b8eaf6576937907b073ad97593440e114c0b6f
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit '02389bf940f751ffb85c8c2187a7039f0c18dad1':
Include new AOSP messaging app in base builds.
|
| |\ \
| | |/ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
b/23110861
Change-Id: I365bedc809425c901982f867e671070344d1112b
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | | |
into mnc-dev
* commit 'e5a631585a7b07c329f9ada04c99ed04b6c16b62':
Increasing arm(64)? emulator partition sizes to 1.5GB
|
| | |
| | |
| | |
| | |
| | | |
Bug: 23093319
Change-Id: I5e493ef4715cee96ae6ab40d6415f5330075fad6
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* commit '073f74d90853b39de32308fa3eeab9aa8998bd69':
Increasing x86 emulator system partition size
|
| |/
| |
| |
| |
| |
| |
| | |
Seems sdk_google_phone_x86 is building larger than 750MB
Bug: 23093319
Change-Id: Ib3ddbbb96a9dcea02eb6da7362ac0142bdfae4de
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Currently, the keyblock was being generated using
data_key.vbprivk. However, we need to use kernel_subkey.vbprivk for
kernel keyblock generation. This did not create any issues until now
because dev-mode just throws a message saying that keyblock is
invalid. But, normal-mode does not boot if keyblock is
invalid. Add extra parameter for passing in kernel subkey to
vboot_signer script.
TEST="make bootimage-nodeps" generates correctly signed
boot.img. Verified that the image boots fine in normal mode.
Change-Id: I0fc2183b466e34ddf1d98c9532072548504fcec4
Signed-off-by: Furquan Shaikh <furquan@google.com>
|
|\ \
| |/
|/|
| | |
into mnc-dr-dev
|
| |
| |
| |
| |
| |
| | |
Bug: 19706593
Change-Id: I073b7b39f25b054abdf2b983a63d029d690970a9
(cherry picked from commit 54a28654e605c73d42c66a552b8fc9c6255529cf)
|
| |
| |
| |
| |
| |
| |
| |
| | |
Addresses the following denial:
avc: denied { create } for pid=1 comm="init" name="sdcard" scontext=u:r:init:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=0
Bug: 22084499
Change-Id: Icffef8330d07b00f36fda11374e39e0df7181ca3
|
|/
|
|
|
| |
Bug: 21662862
Change-Id: I11ed67b8f0efd1232ddfbb6e0a5f4bdbb065397e
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I193b54dd9f4511eb7959c5dbbf38f90267b8fcc9
|
| |
| |
| |
| |
| |
| |
| | |
(cherrypicked from commit fd8c30177c472fe1cbff30312144b2a0b231bd35)
Bug: 19608716
Change-Id: I5c76648a4bcbbb15a033465e8af66b12af6e0a18
|
|/
|
|
|
|
|
|
|
| |
Deal with a build failure in conflict with cl/152105
(cherrypicked from commit 1cc7735ffa5194b9651429b2a96d6f6f319ca5eb)
Bug: 19608716
Change-Id: I1078046db3b159c1baf0a22435c3e777424453a1
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
New adoptable storage feature can format media as either ext4 or
f2fs, so bring in both sets of binaries for typical products.
Bug: 20275581
Change-Id: I85380cbc8c06c958b66db879f63447ddac124cbf
|
|/
|
|
| |
Change-Id: I453d7d3fa3844bdb26c8279982b8b5b246032926
|
|
|
|
|
|
| |
Bumped from 1G to 1.25G
Change-Id: I8d04166c43c792030f346cbe6ba9d6889b31359b
|
|
|
|
|
|
|
|
|
| |
The SDK system images does not have some features such as bluetooth;
From now on, it will use its own feature list from
device/generic/goldfish/data/etc/handheld_core_hardware.xml
bug: 21159206
Change-Id: If566d4d190dc307c6d16844dba0d17570f0ceebf
|
|
|
|
|
|
|
| |
Launcher2 is deprecated and should use Launcher3, as the latter
can handle higher resolution devices (such as Nexus 6).
Change-Id: I5215d87f8536869486bb0b6317ae382a21099925
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Bug: 21164174
This reverts commit d79778faf3180ec0db67e7a12e0871d39867565a.
Change-Id: Ide6b2dc4c511a60bcdf22dd44369e3a9fa08d1af
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| | |
now implemented directly in gatekeeperd binary
Change-Id: Iaeb8e97427dbcffd1356fa955d61af55e3e330ec
|
| |
| |
| |
| |
| |
| |
| |
| | |
Launcher2 is deprecated and should use Launcher3, as the latter
can handle higher resolution devices (such as Nexus 6).
Most importantly, Launcher3 is maintained.
Change-Id: I3a80f242af2baaebe90af93794b0ba5e249dbc7d
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The goldfish-setup service (essentially /system/etc/init.goldfish.sh)
executes the following commands when certain conditions are met:
setprop ro.radio.noril yes
stop ril-daemon
so as to stop the RIL daemon and emulate a WiFi-only device. Both would
fail, though, because goldfish-setup does not have the permissions to
set relevant properties.
This CL modifies the emulator's SELinux policy to grant the necessary
permissions. It is a step towards fixing the ril-daemon-keeps-getting-
killed-and-restarted problem with the new ("ranchu") emulator, which
does not support telephony emulation yet. (The other step is to have
init start goldfish-setup, which will be done in a seperate CL.)
(cherrypicked from commit 33dca8090f8eb1be27e6c6426b7a13a73314e464)
Change-Id: Ice7e7898804b7353ac4a8c49d871b1b2571d7a5f
Signed-off-by: Yu Ning <yu.ning@intel.com>
|
| |
| |
| |
| |
| |
| |
| | |
(cherrypicked from commit cccc90163946c0273a165a1ea50f2a87756610c7)
Change-Id: I630ba0178439c935d08062892990d43a3cc1239e
Signed-off-by: William Roberts <william.c.roberts@linux.intel.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In goldfish kernel 3.10, the goldfish_tty device instantiates virtual
serial ports as /dev/ttyGF* (e.g. /dev/ttyGF0), not as /dev/ttyS* as in
goldfish kernel 3.4. However, in the emulator's SELinux security policy,
there is no specific security context assigned to /dev/ttyGF*, and the
one inherited from /dev (u:object_r:device:s0) prevents services such as
qemud and goldfish-logcat from reading and writing ttyGF*. Consequently,
qemud terminates abnormally on the classic x86_64 emulator:
init: Service 'qemud' (pid XXX) exited with status 1
Fix this issue by assigning /dev/ttyGF* the same security context as
/dev/ttyS*.
(cherrypicked from commit 478346792282aba990111d736ba9928c616f9eb6)
Change-Id: Ia7394dc217bd82f566c4d1b7eda3cc8ce3ac612f
Signed-off-by: Yu Ning <yu.ning@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In goldfish kernel 3.10, qemu_pipe has been renamed to goldfish_pipe.
However, in the emulator's SELinux policy, there is no specific security
context assigned to /dev/goldfish_pipe, and the one inherited from /dev
(u:object_r:device:s0) prevents various processes (qemud, qemu-props,
etc.) from reading and writing goldfish_pipe. Consequently, the classic
x86_64 emulator will not boot if GPU emulation is enabled ("-gpu host"),
and does not render the UI correctly if launched with "-gpu off".
Fix this issue by assigning /dev/goldfish_pipe the same security context
as /dev/qemu_pipe.
This CL also benefits the new ("ranchu") emulator, where all supported
ABIs (arm64, mips64, x86 and x86_64) use 3.10-based kernels. Without
this fix, the new emulator boots and works, but there are avc denials
related to goldfish_pipe.
Last but not least, it is now possible to boot the classic x86 emulator
with a 3.10-based kernel instead of the current 3.4-based one, without
disabling SELinux.
(cherry-pick of commit: a5053e6b35fa1188d94a851a3032126141e5c87f)
Change-Id: I52e75c94d3ae3758cbbf5bc0e1d84254fdf5c6cb
Signed-off-by: Yu Ning <yu.ning@intel.com>
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Bug: 21110439
Bug: 19941636
Change-Id: I743236d9c7b433968865648ffae25451c6012a5f
|
|/
|
|
| |
Bug: 21095280
|