Build of sdk_google_phone_x86_64-sdk_addon product was failing with
the following error message:
error: ext4_allocate_best_fit_partial: failed to allocate 2420 blocks,
out of space?
Change-Id: Ib9e2d21bac86b12b6f8f75d4f30806dd20abcb90
Prebuilts are now preopted. This requires a bump in system image
size. Technically a 13M bump would have been fine, but round up
to 50M for a little bit of future breathing space.
Bug: 17772057
Change-Id: Ib10dc24960c0b2e03ef28c55c3c199382802d4e1
goldfish-setup, goldfish-logcat, and qemu-props are goldfish-specific
oneshot services that lacked domain definitions and thus were left in init's
domain.
This depends on a change to external/sepolicy with the same Change-Id
to define non-goldfish-specific types for properties and logcat.
Change-Id: Idce1fb5ed9680af84788ae69a5ace684c6663974
Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
I've been told this is no longer in use, and it's the only user of
external/grub, which is distressingly out of date.
Change-Id: I434a55e0d68f6db97fa71e294e983ff1802e9ba6
(cherry picked from commit de21059acf)
I've been told this is no longer in use, and it's the only user of
external/grub, which is distressingly out of date.
Change-Id: I434a55e0d68f6db97fa71e294e983ff1802e9ba6
This ensures that the property is always set by init
prior to starting any other process, which avoids the need
for the bionic systrace code to try to set the property
if it has not already been set to avoid the full cost of
searching for an undefined property each time. See
change I30ed5b377c91ca4c36568a0e647ddf95d4e4a61a for
the relevant bionic code.
The problem with the current bionic code is that it can
trigger an attempt to set this property from any random
process, which will be denied unless the process is already
authorized to set debug properties. This is visible in the
form of various SELinux avc: denied messages and
init sys_prop: permission denied messages in dmesg output.
Allowing all domains to set such properties is undesirable.
Change-Id: I6d953c0c281fd72ad3eba8a479fd258023579b5b
Signed-off-by: Stephen Smalley <sds@tycho.nsa.gov>
The WebView Java code is now loaded by WebViewFactory from an APK
when an app needs it, so remove the old jar from the boot classpath.
The previous change removed the webview from core_minimal.mk but
not from core_base.mk, which is what this change addresses.
Change-Id: I6f4bcd427a7e65f3a20372c3c177e9342a953290
The WebView Java code is now loaded by WebViewFactory from an APK
when an app needs it, so remove the old jar from the boot classpath.
Bug: 16329371
Change-Id: Ibed49641d04fd5e93e26ab12e203e4596e0b3bb6
A value of "0" means that native bridge is disabled.
Bug: 17104449
(cherry picked from commit 4f703a7f9f)
Change-Id: I4ca379923996ea08828dea4b2cd2da045e3f8031
This patch fixes the sdk_arm64 system images to boot properly when run
under emulation with the new qemu-android binaries.
BUG=17154406
Change-Id: I152eb09086ce4abc4b623e54de78cdaaac6b90a1
This patch ensures that the system image produced for the 'aosp_arm64'
build products can actually run under emulation with the new qemu-android
binaries [1]
The main issue is that the virtual board is named 'ranchu' instead of
'goldfish' (because the virtual hardware is _very_ different), and thus
requires specific files for the boot to start properly
(in particular fstab.ranchu is required to mount the system, data and
cache partitions, otherwise init will fail badly because /system/bin/
and /data/ are missing important files).
IMPORTANT: This requires the files under device/generic/goldfish/ from:
https://android-review.googlesource.com/#/c/105020/
[1] Binaries built from https://qemu-android.googlesource.com/qemu-android
BUG=17154406
Change-Id: Ic40360bf56e32aab708551c810000467d23793d4
