We no longer sync Launcher3. This entry never did anything anyway,
since we build Trebuchet instead, which overrides Launcher3.
Change-Id: Ia2c56c9f819025ba34cbff1daf8d3380a924a8a5
Chrome Stable and Google Webview had incorrect
signatures. That was due to an incorrect method
of determining the right signature.
That mistake wasn't noticed because Android
disables the signature check on "userdebug" and
"eng" builds. It is only enabled on "user" builds.
So this commit replaces the wrong signatures
of Chrome Stable and Google Webview by the
correct ones and thus makes them avaliable
webview providers on "user" builds.
Main credits go to @KreAch3R for his
extensive research on the issue.
Change-Id: I081783b59254bfed0b2e3568ba8ae2801d86efea
Signed-off-by: Alex Naidis <alex.naidis@linux.com>
* Some projects with multiple merges and
discountinuous histories could trigger
an error here when the HEAD~{?} does
not exist, hence avoid this by ignoring
the commit and continue the search
Change-Id: Ice28c87d1bf8897da52236b637bbb0c5d349f848
It doesn't make sense to have:
1. mm and mmp
2. mma and mmap
3. mmm and mmmp
4. mmma BUT NO mmmap
Add the mmmap command for consistency.
Change-Id: I8cb1041113e6d56a0ac1d34898b07615da22b459
The framework disables aggressive power-save modes when appropriate,
such as when the device lacks a significant motion detector.
Thus, instead of enabling it in each device tree,
enable it by default for all devices.
Change-Id: I1999b04876f1ddce1574c050b6bc582e9a9a96da
Trusted Face depends on libprotobuf-cpp-full.
Some devices already ship it (eg RIL needs it).
Include it here to build it for every device.
Link to OpenGapps issue:
https://github.com/opengapps/opengapps/issues/390
Change-Id: Iffee0aa6218dfef45f5cd728a999fa1114c0dd57
Signed-off-by: Alexander Martinz <eviscerationls@gmail.com>
The servers do not have ImageMagick installed right now,
breaking the automated builds.
Revert this for now.
This reverts the following commits:
840e781408 bootanim: Use a for loop to make part# folders
ce5405d1f7 Fix wrong bootanimation.zip from mkdir .../part{0..2}
6179d9494f cm: Build bootanimation.zip
67ddf37281 cm: Rework boot animation generation
Change-Id: I63fc43da9b1a6afea5f791e879f0bfc9a385d98d
* In a situation where the Android tree is already
fetched and entirely set for a device tree,
all additions to cm.dependencies in a common
project were ignored due to being already fetched
* Add a new array of projects to verify but not
necessarily fetch, and fill it upon fetch request
or if the project starts with "android_device_",
to let the iterations follow the common trees
Change-Id: I9eea0ab9c46a4bed8366baa37a4e7e8696481504
Signed-off-by: Adrian DC <radian.dc@gmail.com>
For some reason the mkdir command:
mkdir -p $ANDROID_PRODUCT_OUT/obj/BOOTANIMATION/bootanimation/part{0..2}
creates a directory part{0..2} instead of three separate directories.
Non-fatal build errors and a 386 byte bootanimation.zip file result.
This explicitly creates each directory.
Change-Id: Ia6ae0e4f64521992de8cc34a376af3eaac5c8819
* In init.rc, this prop will be used to set DOWNLOAD_CACHE
* If a device specifies having a dedicated /cache partition, by setting
BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE, use it!
* Default to /data/cache per AOSP
Change-Id: I838672ca4638c9665333c1a67257fc435f33f388
This was used for the HCE implementation by SimplyTapp in CM 9 - 10.2.
Since then, Android has an HCE implementation and this is no longer used.
Change-Id: Icd9db39829c1863c4962aab53959ad527da28bcd
RomManager hasn't been properly updated in years.
Is this still even a reliable ROM updater anymore?
Change-Id: I3ea57ec0121e6d6f933dd80031bb53514a44e362
* This code was introduced to support building from Qualcomm hardware
manifests, placing the appropriate Qualcomm HALs at the AOSP
hardware/qcom/$(HAL_TYPE) location. This isn't a supported use case
anymore, so remove the dead code.
Change-Id: Id7d53b33f53289bc1ead8eb983d7e252940b0387
Newer QCOM HALs use this flag for libc2dcolorconvert,
examples being msm8937 and msm8996 media HALs.
Change-Id: I28e8a42b58b4f5f71126df7ad97c377724da5bab
* Honestly, I have no idea why this works. Or, to put it more
precisely, why it works without this on _some_ devices and not
others. All of a sudden?
* Without this patch I'm getting:
/opt/out/14.1/build-cm_d2vzw-clobber.ninja is missing, regenerating...
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_string::erase
make: *** [build/core/ninja.mk:167: /opt/out/14.1/build-cm_d2vzw-clobber.ninja] Aborted (core dumped)
#### make failed to build some targets (5 seconds) ####
Change-Id: I4bf43868bf7dfe13df57151ae3597246164cbebc
Snapdragon LLVM is not supported on Darwin yet.
There might be the case where the directory structure is set up
by default and the build system will try to execute the linux binaries.
This will fail obviously:
/bin/bash: /Volumes/Android/build/prebuilts/snapdragon-llvm/toolchains/llvm-Snapdragon_LLVM_for_Android_3.8/prebuilt/linux-x86_64/bin/clang: cannot execute binary file
Change-Id: I1f4d0bbda88b540b7ac3159f8e83de4501b9073b
Signed-off-by: Alexander Martinz <eviscerationls@gmail.com>
