N7.1 #40

Change-Id: I200730c58ee89fd4151f8e013d53023e098d8ce4

Change-Id: I11a48fb637b8b155c02c65500773aceb5d4bb376

* We can't depend on a $OUT variable with ninja Change-Id: I9ff050a986e7bb2774d1326f5b396d0afb7f33c1

Change-Id: If6f054f30cd76c48415e15cd06ef7433760bb76e

Change-Id: I34199aba9f6ec38d918c082def3298a3fa5c60f5 Signed-off-by: Brandon McAnsh <[email protected]>

* If the project doesn't have a revision specified, try to see if it's remote has one specified before falling back to the global default. Change-Id: I05129413b154e5d08d0fa9ef0ce853631b7e1562

AOSP split the media hal into msm8974 and msm8996, better to just add target named symlinks in the media hal than ifdefs here for the sake of cleanliness Change-Id: I87f06b9c1b8939a8a8868ff35fcf6e8f5ec48b51

Thou shalt not discriminate OS X. Change-Id: I9c993d44ca74cb15631ea25d6105a3398ea57e95

Change-Id: Icf29909e3df69832a58f3c654a6ed92251d817ca

* You wont find this in the build.prop on these devices and this is how we handled them in previous versions Change-Id: I56332c87916da1a1206980df0e7a6ca8a55f0e8e

Change-Id: Iaec955e1738cd644d879db0c38d66d250c24ce91

Change-Id: I9dea4605857741132b8d10143c20d4bd7829086a

Change-Id: I5c9599da2e68a17bafc73e8afabc06f6d54a77b6

Change-Id: I48aa4f0f231230f456645a9b36ab062cadf3dbb6

check the last 10 commits to HEAD for a dupe change id. Change-Id: Icfbf8b4eae165cf84ef4a82f54f792e9c9acd67b

Change-Id: Iff413c1ede334c8315a2082d9849e6c32d3aa8f7

* Broke bionic build on multiarch. This reverts commit 8a570fa. Change-Id: I1bc3aa90d584ac7985ce48aabe6f1ca63f065899

Change-Id: Ifb67c1269a738bf263f5caa56e963bb05cefbcb1

Change-Id: I3daa570db99b633d657ff60f2d0648124e5964ec

Change-Id: I6f7891a52fb1538e88f5a68dd28ef1c603ee7067

Change-Id: I81e6cb0e5e191f669bb665207d71f28f3fa19581

* OSX doesn't have an -r flag on date Change-Id: I04cb58366926418fb9b05482514800a5a72af0e1 Signed-off-by: Brandon McAnsh <[email protected]>

* This partially reverts commit c7d6cc2 * Move cmsdk check to checkapi-cm, android checkapi shouldn't be under this ifeq Change-Id: Ia7c9853cc5f978ed533f2879367428eb1d64bd46

Change-Id: Ifed887874b517ec335082f3eb7a4e079f4cac099

* workaround these being reset after BoardConfig.mk is run Change-Id: Ibe984d862df0e1a5910ea80a66c44d599c299f10

This reverts commit 7ffcafb. Change-Id: Ic79e954bb97f4b6748ecce874def97ce432099bc

Conflicts: tools/releasetools/build_image.py Change-Id: I04c4f7b4e978e4c0cd4928f3afd8243914d86f68

Change-Id: I284dc1df58ca33c0e4e029c152088cc19b8f2f56 Signed-off-by: Brandon McAnsh <[email protected]>

* Can be enabled on devices that need it with TARGET_USERIMAGES_USE_YAFFS This reverts commit 65d4186. Change-Id: I891f2e6a963178ffec92fedb25e7e28c60a768d1

Change-Id: I3abc22eea94293d1d0ebf0a81b396ebea0baf5a8 (cherry picked from commit 29357f5)

Change-Id: Icbd36b11659ced7764599c5d2e0e91be67a3e4bc

Change-Id: I6b785bbef48babac21aeb6c4d90999830ddad50d

Change-Id: I7726cb87da576d1fcc59a4a3108e5a7ca2bf5304

* Sometimes we want to put some private recovery resources there. Change-Id: I0cfa68ad92872cef654dbe1c71a536f7a950e53f

* kati & ninja create dotfiles (example: .ninja_log) in out/ Change-Id: I83ffd1c26a37f7ffef45fd4598435db93058ab67

On some devices the base address may need to be adjusted to prevent overlapping of memory. This will allow the adjustment to take place in the boardconfig.mk Change-Id: I17da0301960f1b0183db20b7b592eb1efd28343d

* Verify that the project has at least 10 commits to verify, if not check only the amount of existing commits Change-Id: Ic95212510d8f5b980c9a94af8d5ac1e0dfd94b3e

* Commits are identified by their last Change-Id, but the parser only considers the first one found * Reverse the list to find the last Change-Id and avoid multiple repopick attempts on the same commit Change-Id: Ie0204245a47799f8ead21148e0b4e9356cf271eb

The makefile now lives at the top and does platform selection Change-Id: I79255f8b98542f6298a74947fc91eeffca523e81

GCC 4.8 doesn't exist anymore in N. ** AICP: PS12 from CM Gerrit Change-Id: I5c83e7de97b75ece9a1306cb20b058d9fd30e288

Android 7.0.0 release 6

…CH" into n7.0

Change-Id: I8b0641eb107cd095079bb17f92e99730f532fda7

Operation not permitted using -d Needs to be looked into This reverts commit b4bf8ca. Change-Id: I54799e64d31ee6204523e3c51f2fb28ef10a3281

This reverts commit 03dccdf. Change-Id: I7b1ec73becbb8aadf2e34dce762e24ba98e5a9aa

This command does the normal brunch and just opens up the final zip directory in a file manager. Thanks Davor for helping make this work on all file managers. brunchopen : Don't change dir, only open zip dir. Change-Id: I3e77bc211b5c1179ea6603207f362d7d3a40a0b7 Change-Id: I564bd33afdd842dd409c6ac0a1744b7658cffd70

Change-Id: I9dc1c6a95c441829b5900ff9c83aa32540ddabf1 build: add maintainers for unified devices too Change-Id: I2a25b4b8c04f5c2624107d02b3489a6d154a0cd1

Change-Id: Ief6c7141303f8f431d95d330b87293d67bcc1386 Signed-off-by: Alexander Martinz <[email protected]>

* ccache gets updated semi-frequently and some builders would like to be able to take advantage of new features without having to rely on the prebuilt version getting updated * If a build system has ccache installed already, use that version instead of the prebuilt Change-Id: I8988c8a25fab3694d84633f957c2b92ce84cf69e

Conflicts: core/Makefile envsetup.sh target/product/security/aicp-devkey.x509.pem target/product/security/aicp.x509.pem tools/roomservice.py Change-Id: I39d3e711a6beab47e3284919a9a4fef15b0f40b9

This reverts commit 01ec68f. Change-Id: I8d3a0da869c1385e1e7b08fb7a56d2750b264975

* androidkernel is a set of toolchain symlinks for kernel builds that point to the regular toolchain binaries, except with ld pointing to bfd instead of gold. Change-Id: Id1e2d3b1c50db581bff13cfa00b5b35d5badb8ed

This reverts commit 3ef40be. Change-Id: Ie73d03be5ce72f9d6b1fe6854fbde35032d04703

This reverts commit bd59615. Change-Id: Ibb5a9606bf277173ca52432d4d2590415e4203bd

* For whatever reason mainline ninja improves my build significantly * Allow users to bust out of using whatever binary is provided with the build system and use their own copy if they have it installed Change-Id: I14dbb7b9d8a028d1b0f16e136a8310584df329be

AOSP split the media hal into msm8974 and msm8996, better to just add target named symlinks in the media hal than ifdefs here for the sake of cleanliness Change-Id: I87f06b9c1b8939a8a8868ff35fcf6e8f5ec48b51

Change-Id: Id05b92454c716cbed2faa26c24f2980a148464a0

Original change: df574f3 This part was missed during AICPfication of build repo... Change-Id: I38423e7094eb52949b9eadeea8ba388e6715713a

Change-Id: If483cbfd22aef29b46df9640e972427aa60064ee

Android 7.0.0 Release 14 (NBD90Z) Conflicts: core/build_id.mk Change-Id: I109a584d05fd9f4621034759284b851a734e5a19

When Difference.ComputePatch() failed for some reason, only the first part of the failed command was show with the error, not all arguments. old (simplified): WARNING: failure running ['imgdiff', '-b', '/tmp/recovery-resource.dat']: new: WARNING: failure running ['imgdiff', '-b', '/tmp/recovery-resource.dat', '/tmp/tmpSsy_kf', '/tmp/tmpOMCXSn', '/tmp/tmpA3FtZw']: Change-Id: Id8b498df3ed7934815430e4b4c2651ef4aa781c6

See: https://git.io/viAru Change-Id: I6f68e3e5cb09a8b64a8869396bb43c76e9bc181b

Allow modules to define custom AIDL flags Change-Id: I5609e6eb0a10d441cea2556179c8496293116dcf

Change-Id: If49f4340e1ae61a0fde4d1fb0a305c4eb937f099

HFS+ and ext4 both support filenames up to 255 characters in length. It should be ok to allow longer suffixes. This fixes mmp in places with long paths (where otherwise the build system defaults to using md5sum for the suffix) Change-Id: I93e39875470417ce1b0febe7a9e0da37b56b5b00

Change-Id: I9485b97fd0df6f8631f2f766ea347f625a6d9dc6

Change-Id: I062431f0a6ec1689d0538a44e02bfb3cd8915bae

This reverts commit a59d8a4. Change-Id: I2f1e7eb24797ff1398d12d22fbabb9e0afac4609

* Granted we should never not check the API, the flag was added so we need to account for it Change-Id: Iae58ab6484c5c72904cae30e74f5ea1e89a86618 Signed-off-by: Brandon McAnsh <[email protected]>

It is troublesome to create device makefile to vendor/aicp/products in each time... Change-Id: I413cb05b9e1dc609412d222e91dea4c4431ef61d

Change-Id: I131a81d174099660702fb1f256bfc12f1639ae4b

Change-Id: I03c704f6462330e7bb2e6a798f104a9077dfab9f Signed-off-by: Ralf Luther <[email protected]>

* Fix -caf and -caf-<platform> projects * Fix AOSP HALs that are synced in "/default" subfolder Change-Id: I33cc344a3234de6698676c32035622acbec03dd1

Change-Id: I1687b879e00918813886b2c9c54535376aa62d99 Signed-off-by: Marc K <[email protected]>

Change-Id: Icfab874abab64b0a3e5e63091cb6c25dd9630737 Signed-off-by: Marc K <[email protected]>

Change-Id: I27b4e62d08dcd2a6dc95519197c6284c8c44636d Signed-off-by: Marc K <[email protected]>

…m8226) RECOVERY_PATCH_INSTALL has a dependency on RECOVERY_FROM_BOOT_PATCH. This is correct, because RECOVERY_PATCH_INSTALL uses make_recovery_patch which needs the imgdiff tool. imgdiff on the other hand is a dependency of RECOVERY_FROM_BOOT_PATCH. This should ensure that all dependencies are met. However, RECOVERY_FROM_BOOT_PATCH is defined after RECOVERY_PATCH_INSTALL, making the dependency effectively non-existant. Moving RECOVERY_FROM_BOOT_PATCH before RECOVERY_PATCH_INSTALL fixes a race-condition where sometimes imgdiff was not build before RECOVERY_PATCH_INSTALL is called. Upstream is not affected by this bug, since it does not contain RECOVERY_PATCH_INSTALL anymore. The following error can be observed whenever someone hits this race condition (which is basically always reproducible when building with -j1): Installing recovery patch to system partition Warning: could not find SYSTEM/build.prop in <built-in function zip> using prebuilt recovery.img from BOOTABLE_IMAGES... using prebuilt boot.img from BOOTABLE_IMAGES... Traceback (most recent call last): File "./build/tools/releasetools/make_recovery_patch", line 55, in <module> main(sys.argv[1:]) File "./build/tools/releasetools/make_recovery_patch", line 51, in main common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img) File "build/tools/releasetools/common.py", line 1461, in MakeRecoveryPatch _, _, patch = d.ComputePatch() File "build/tools/releasetools/common.py", line 1146, in ComputePatch p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE) File "build/tools/releasetools/common.py", line 100, in Run return subprocess.Popen(args, **kwargs) File "/usr/lib/python2.7/subprocess.py", line 710, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory build/core/Makefile:1047: recipe for target 'out/target/product/t00n/system/bin/install-recovery.sh' failed Fixes: 3d1c612 ("Revert "Revert "core: Makefile: Build install-recovery into the system image""") Change-Id: I28e8c845ffc830553ca5177cbe22ae72b185b437

Change-Id: I702b0643edfd9cb2307b4c43c7f0e940abc37028

… for msm8226) RECOVERY_PATCH_INSTALL has a dependency on RECOVERY_FROM_BOOT_PATCH. This is correct, because RECOVERY_PATCH_INSTALL uses make_recovery_patch which needs the imgdiff tool. imgdiff on the other hand is a dependency of RECOVERY_FROM_BOOT_PATCH. This should ensure that all dependencies are met. However, RECOVERY_FROM_BOOT_PATCH is defined after RECOVERY_PATCH_INSTALL, making the dependency effectively non-existant. Moving RECOVERY_FROM_BOOT_PATCH before RECOVERY_PATCH_INSTALL fixes a race-condition where sometimes imgdiff was not build before RECOVERY_PATCH_INSTALL is called. Upstream is not affected by this bug, since it does not contain RECOVERY_PATCH_INSTALL anymore. The following error can be observed whenever someone hits this race condition (which is basically always reproducible when building with -j1): Installing recovery patch to system partition Warning: could not find SYSTEM/build.prop in <built-in function zip> using prebuilt recovery.img from BOOTABLE_IMAGES... using prebuilt boot.img from BOOTABLE_IMAGES... Traceback (most recent call last): File "./build/tools/releasetools/make_recovery_patch", line 55, in <module> main(sys.argv[1:]) File "./build/tools/releasetools/make_recovery_patch", line 51, in main common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img) File "build/tools/releasetools/common.py", line 1461, in MakeRecoveryPatch _, _, patch = d.ComputePatch() File "build/tools/releasetools/common.py", line 1146, in ComputePatch p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE) File "build/tools/releasetools/common.py", line 100, in Run return subprocess.Popen(args, **kwargs) File "/usr/lib/python2.7/subprocess.py", line 710, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory build/core/Makefile:1047: recipe for target 'out/target/product/t00n/system/bin/install-recovery.sh' failed Fixes: 3d1c612 ("Revert "Revert "core: Makefile: Build install-recovery into the system image""") Change-Id: I28e8c845ffc830553ca5177cbe22ae72b185b437

Change-Id: I3b96371883f84675df4ddaba54fb8a2ef7b0ae3e

…(needed for msm8226)" into n7.1

Change-Id: Iec38c313c9eb88a74c7bf7a5cf424131b568ac0a

Change-Id: Ia1a01f2e18ad6785d39f51b466a5d5a1b6d553be

* This code was refactored in 7.1 adjust accordingly. * This is used by projects like ril-caf where the proto-c generated sources dir might not match the project path. Change-Id: I7a7d0bb7a397b02deb5406a591059a877ac2c6da

* Make it inline with CM Change-Id: Ibacd11337fd028169a21beba22dedf82c858592c

This sometimes breaks packing on weak PCs Change-Id: I1f10ef8b046e06be865d9e5213095afae251a29d

It's just easier having it always built for you (and it really takes no time). Change-Id: If183cef50b1de0bf228e27bab77607df71350345

Needed for enabling proprietary Clang compiler Change-Id: I33a6a4c4c40722ce66dd7398ff647c33e5dfbdea

Currently, we always apply some flags to clang, which are actually not always available. Change-Id: Ia6404c36453cb10fc93624f1ae7d9f7aec587ebf

Prevent the warning for SDLLVM Change-Id: Ie44b6ea12fab6a6f198a00c360fee98980f0b40c

… LTO Change-Id: Ie71d09b0853954c44a37f708894eef68c2f6aafd

The lib indicated by LOCAL_HAL_STATIC_LIBRARIES(foo) currently gets appended to the end of the my_static_libraries list. As a result if foo is the only one to reference something from the static_libraries_list(bar) we die during linking since the linker would have stripped out bar. Fix this by prepending foo to the my_static_libraries list instead. Change-Id: Iefffcac65dd5f05d9be2d036b42729610d2394b3

* Only devices which see a measureable benefit should use this since it requires more resources to build. * Set TARGET_USE_SDCLANG to true in your BoardConfig if your device benefits from it. Change-Id: I12ee20b0627ff0ca121d653cde482e5449a768cc

…form/build into HEAD Android 7.1.0 release 7 Change-Id: I080763364ade3e76da95a9295fc355ea30ad9858

Newer QCOM HALs use this flag for libc2dcolorconvert, examples being msm8937 and msm8996 media HALs. Change-Id: I28e8a42b58b4f5f71126df7ad97c377724da5bab

KERNEL_ARCH specifies the kernel architecture, not TARGET_ARCH. Change-Id: I97407caa15cacf53489e8ebb31f5c059991a9493

* Will be used by the build servers Change-Id: I5d31a7c41adc283cb9336314e9d54412cc740e9e

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 <[email protected]>

* 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

Change-Id: I046d860127918858af98e9ab73bebc253502d08f

Change-Id: Idced60de644b4bb74cc160116180baf021304de1

Change-Id: Iafd416aaac81642c7ec736712b45ecbe05b0d55e

We call them already in TARGET_KERNEL_BINARIES Change-Id: I1a9cf89d59416fdb6c9c570d17fb490440d44159

* Make ccache great again Change-Id: I20da69f3f8ce695e7e5e4bdd06f7436cc5331003

ccache supports the compiler option -fprofile-use since v3.2. If the current wrapper is ccache v3.2 or newer, don't disable it when FDO is turned on. Change-Id: I506010173f60b791eae0d65afeac36995c57dbe6

(cherry picked from commit 202380f)

b/32949407 (cherry picked from commit 190129b)

Change-Id: Id48ce6b6fc07fc1fc7a824bacdf8997ac0bf3312

Uses authentication if $GITHUB_API_USERNAME and $GITHUB_API_TOKEN environmental vairables are set. Change-Id: I57acaaf1a7210691fc271d2a5cfe8a5d46232e1a

Android 7.1.1 release 4 Conflicts: core/Makefile core/binary.mk core/build_id.mk core/version_defaults.mk tools/droiddoc/templates-sdk-dev/assets/css/default.css tools/droiddoc/templates-sdk-dev/assets/js/docs.js tools/droiddoc/templates-sdk-dev/components/masthead.cs tools/droiddoc/templates-sdk-dev/customizations.cs tools/droiddoc/templates-sdk-dev/docpage.cs tools/droiddoc/templates-sdk-dev/head_tag.cs tools/droiddoc/templates-sdk-dev/header.cs tools/droiddoc/templates-sdk/assets/css/default.css tools/droiddoc/templates-sdk/assets/js/docs.js tools/droiddoc/templates-sdk/head_tag.cs tools/droiddoc/templates-sdk/jd_lists_unified.cs tools/releasetools/add_img_to_target_files.py tools/releasetools/check_target_files_signatures.py tools/releasetools/common.py tools/releasetools/ota_from_target_files.py tools/releasetools/sign_target_files_apks.py Change-Id: Id096bc159a727c17b55725cda1fe8656ed535166

Change-Id: I44b1e7b2725e781ea65209f1b26f521f12a67a00

Add a command to communicate with the OverlayManagerService for debugging purposes. This mirrors the am and pm commands. This commit restores the functionality after the Nougat rebase from Sony. Example use: $ adb shell om list com.android.systemui [ ] com.test.awesome-home-button $ adb shell om enable com.test.awesome-home-button $ adb shell om list com.android.systemui [x] com.test.awesome-home-button Co-authored-by: Martin Wallgren <[email protected]> Signed-off-by: Zoran Jovanovic <[email protected]> Change-Id: If424b8ef6052e4121902b630279c0ebaf416203c

* Add a flag that specifies which ramdisk(s) to compress with lzma * If not specified, fall back to gzip * Example: LZMA_RAMDISK_TARGETS := boot,recovery Change-Id: I9cce4da90343fb6dfb7039863649e37d78262726

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

* 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

Android 7.1.1 release 6 Change-Id: I6bca91229f411c624676b90dc8ccc273ecf7b12c

* Broken after ZSH v5.3 Change-Id: I99febebfa22efd702c2dea13369a9dd90f8e6120

In your device tree, add aicp.removal.dependencies in case some dependencies included in aicp.dependencies conflict with the current default manifest. Modified roomservice to call roomcleaner which does all the removals. Roomcleaner is in fact a modified copy of roomservice. Original commit-history of roomservice: commit d0419da Author: Koushik Dutta <[email protected]> Date: Sat Nov 26 18:51:42 2011 -0800 roomservice delivers you lunch combos from the CyanogenMod github. fix roomservice formatting support product names with _ in them fix roomservice to handle pagination Change-Id: I4923c2f768094dbad8e06a72d9f27d46414030ab roomservice: Add lightweight dependencies to repositories Roomservice can already fetch your cm_<device> without the need for a manifest entry. However, when working with common repositories, there is no way of actually fetching them without adding to the manifest. This patch introduces a lightweight dependency system. Each repository can have a cm.dependencies in the following json format: [ { "repository": "repository_name_on_cm_organization" "target_path": "target/path" }, ... ] For instance, for cm_anzu I need android_device_semc_msm7x30-common and android_device_semc_mogami-common. I would add both to cm.dependencies as follows: [ { "repository": "android_device_semc_msm7x30-common", "target_path": "device/semc/msm7x30-common" }, { "repository": "android_device_semc_mogami-common", "target_path": "device/semc/mogami-common" } ] Roomservice would then fetch the anzu repository, parse the dependency files and add/fetch/sync these additional repositories if they don't exist already. This also adds pretty printing to the output xml. Change-Id: I9cc847adfc717a06439bc6094213ed6492343158 roomservice: Add branch support to cm.dependencies Allow the cm.dependencies entries to provide an optional "branch" for the repository dependencies. Added to fully support http://wiki.cyanogenmod.com/wiki/Integrated_kernel_building Change-Id: I35b51920d296afa329411af6172c7bd9aeef4af8 roomservice: Fill in dependencies for already-deployed repositories Change-Id: I01fd408c9c4bfa78097c7f848b2556d2b2b180f3 roomservice: Extend dependency-checks to devices in main manifest CM currently keeps devices inherited from AOSP in the main manifest, so take that into account as well when checking device paths Change-Id: I9663f283617f237428b4eaa0cd60b5de2b86a7b9 make compatible with github v3 api Change-Id: Iff6f1f9099cdc5d2b49e04000b5fe3d04aa5d7e4 Fixed build for full-eng Previously Traceback (most recent call last): File "build/tools/roomservice.py", line 153, in <module> repo_path = get_from_manifest(device) NameError: name 'device' is not defined ** Don't have a product spec for: 'full' ** Do you have the right repo manifest? Now ============================================ PLATFORM_VERSION_CODENAME=REL PLATFORM_VERSION=4.0.4 TARGET_PRODUCT=full TARGET_BUILD_VARIANT=eng TARGET_BUILD_TYPE=release TARGET_BUILD_APPS= TARGET_ARCH=arm TARGET_ARCH_VARIANT=armv7-a HOST_ARCH=x86 HOST_OS=linux HOST_BUILD_TYPE=release BUILD_ID=IMM76L ============================================ Change-Id: Ib513705aba9a7a52a971ab64102ecbe9fddfb97a roomservice: Bump github request per_page to 100 Change the number of repos per page from the default 30 to 100. We seem to be hitting the rate limit on the jenkins server. Change-Id: Ie733feaa0414cbfebb7efcfc1e24d94e1e466d1b roomservice: Add support for netrc Change-Id: I1f5e11e40125abd0c4e4c8d8294d4fc09bfdc30a roomservice: Handle missing netrc file Change-Id: If981fe79dc3e2191434301239b0cd585be8b4730 roomservice.py: Verbose error when a branch is missing. Also add ROOMSERVICE_BRANCHES environment variable to use fallback branches. Change-Id: I3c2b1d79fc185c1f1e1d658e5ca4f78e688780e2 roomservice.py: Fixups around fallback branches not being used by dependencies when ROOMSERVICE_BRANCHES is defined. Change-Id: Ifb42a023cae5f62ac8f9cf7832125b91b431169c roomservice: Allow following up tag references This is now needed for release builds Change-Id: I8c5f87341059b3b15ee853312b71df73790ad0d8 build: local_manifest.xml deprecated, use local_manifests Patch Set 2:- Use roomservice.xml instead of cm.xml. Change-Id: I3d8a6ef3907b92808662cbba912cea5ed38d0bde Fix fallback branch search in roomservice If you provided a fallback branch to roomservice via the ROOMSERVICE_BRANCHES environment var the branch search would fail if the device repo had any tags. Fixed this by appending the tag search results to the branch search results instead of overwriting them Change-Id: I73a11af1500bd04e346f08ec3f83454502f3a169 roomservice: Fix wrong assumption about path of active manifest Change-Id: Id740ff4b848e6ccbfd658be4846197b8ca519237 roomservice: When validating the presence of a repo, check main manifest too Change-Id: If680536484074b473458723d93e783d074d7f669 roomservice: Bump devices per page to 200 Limit was reached again when attempting to lunch various projects, such as steelhead. Change-Id: I2f3b9705e07e1e47b86857aeb383cf7c99fcdbdc Signed-off-by: William Roberts <[email protected]> roomservice: Fix assumptions about the branch naming We can't just split from the last slash anymore, since we're using those to distinguish the stabilization branches Change-Id: Ia175dd317f508e99b275b56e9c83bd4729a75ddb roomservice: Add recursive dependencies Dependency repositories can now have dependencies themselves Change-Id: I33a28709170da52bc98f4a62387927e3a11b2450 roomservice: python3 support Change-Id: I7621818ba7ed997676728fe865f37a25b3a5b8b5 Signed-off-by: Chirayu Desai <[email protected]> roomservice: Improve new device retrieval Without credentials, GitHub's search API limits requests to 60/hr. The existing method to add a new device is to fetch JSON-formatted info for ALL CM repositories and then search for the device. In doing so, more than 10 pages of results are returned (i.e. more than 10 requests per device). This is clumsy, slow, and limits use of roomservice to only ~5 devices per hour. Instead, only return search results for repositories that have the device name in the repository name. Then, one device = one request. It's faster and allows closer to 60 device setups / hr. Additional bailouts are included to stop the script earlier than later if a device is not found. Change-Id: I7f914d7ede82da0f100d9fd6cf8b603177962e48 roomservice: Fix search of devices forked to CM Commit "roomservice: Improve new device retrieval" introduced a regression where repositories that were forked to CM were omitted from search results. This fixes that issue. Change-Id: I7bf54129b5da1749abe5b2b9a492cb93e6ee41a6 roomservice: Improve error handling on search Use the relevant forms of 'except' for urllib and parsing instead of a general except which was performed too late anyways. Change-Id: Ia1fc89dd5a8a703fc0175aef7b6dd013a44a2c8e roomservice: use force-sync when adding projects with roomservice This works around the error GitError: --force-sync not enabled; cannot overwrite a local work tree when using roomservice. Since this should only trigger when the device repos haven't been checked out yet, we can use force-sync to overwrite any roomservice device paths in the .repo directory. Change-Id: Iac54a8a2f2913f82f8ca6497b8785a9d5769640b Ticket: CYNGNOS-735 roomservice: check uniqueness by path, not name For repos such as hardware/qcom/media-caf we are using the same name with different branches for different paths. for eg. CyanogenMod/hardware_qcom_media-caf(branch:8994) - fetch to : /hardware/qcom/media-caf/8994 CyanogenMod/hardware_qcom_media-caf(branch:8960) - fetch to : /hardware/qcom/media-caf/8960 For such cases roomservice won't pick up a new path if one already exists. We should check for unique by target path instead. Change-Id: I89e561ca9a2d57ede8cf782f431a8e829ea47ee5 Signed-off-by: Arnav Gupta <[email protected]> commit 6cb0e68 Author: Anthony King <[email protected]> Date: Tue Nov 3 00:23:11 2015 +0000 py3: update all the things Change-Id: I5e11b46b7c2f7f8760d6c0e713ca99c1e88b7cd3 py3: update releasetools with proper print syntax Change-Id: I48534a72e6559f60af5f9b1c09040b34b7575b63 py3: ota_from_target_files.py: fix logic that broke Change-Id: I032097c463598d1246feb92c02567175a65f90fd commit 73f6887 Author: LorDClockaN <[email protected]> Date: Sat Aug 27 17:15:10 2016 +0200 AICPfy Change-Id: I5c9599da2e68a17bafc73e8afabc06f6d54a77b6 commit 8fe78df Author: Hashbang173 <[email protected]> Date: Fri Oct 28 18:28:50 2016 -0400 roomservice: update for n7.1 Change-Id: Ia1a01f2e18ad6785d39f51b466a5d5a1b6d553be commit b367c52 Author: Hashbang173 <[email protected]> Date: Sun Dec 4 14:20:48 2016 -0500 roomservice: Add support for authenticated GitHub API requests Uses authentication if $GITHUB_API_USERNAME and $GITHUB_API_TOKEN environmental vairables are set. Change-Id: I57acaaf1a7210691fc271d2a5cfe8a5d46232e1a Change-Id: I97e62956f76d7c6bc9aca73ab1453b65a3209780

We had all the files needed for this from an era long time ago (AOKP) lol. So I just added the persist command to be launched when Backup command is launched Change-Id: I54352e9485931c4c79bf144f58e355838d74ce67

Change-Id: I0e2dd0afcb6dd490dd81afb879890eeb41bf121d (cherry picked from commit 35901a7)

Change-Id: I761c90cd025b2862a3b6fe1cf12e6aebc5fa809f (cherry picked from commit af63566)

Conflicts: envsetup.sh Change-Id: I578cce73f20c86b82c0e0ae852cd0de02f0ed8a3

…VERY" * This macro was added for a reason, that reason being for devices without a dedicated recovery partition (marlin/sailfish for example?) * Use it Change-Id: Ieb08d498f1e201a01557b40aac8a30df26c97673

* ZSH breaks a lot of things. Conflicts: envsetup.sh Change-Id: Idee8485bee673bebf6fe5857253306b20aa92eb5

Android 7.1.1 release 9 Change-Id: Iaaeeefc65242dc7a765024289d60ed49c944b9fb

CAF recommends using https://source.codeaurora.org/quic/la now. Change-Id: Ic8d6451111f0e71bce044ffaae79f0acfc34caa1

Change-Id: I97f812412f94a0638e78eaf7e45112b6924120a9

Currently, in the media HAL, we're replacing the usage of this variable with a check for TARGET_BOARD_PLATFORM. Instead of having to do that every time a new branch is made, define the variable in qcom_target. Change-Id: Idd85b6f0b167bbc64833eb03335abcaa7b9de4a9

* These are now needed sooner than we had been importing them in android_build. This ensures they'll be imported before their macros are needed. Change-Id: Id7e31f36393414f6d51a8bc80686ceaebfe7cb28

* These (qcom specifically) are now needed sooner than we had previously been importing them. Move to vendor/cm and include them within their <platform>_target.mk makefiles. Change-Id: I06c6ab66446e2f0b54c245cf6c2cf665b649e0c9

With androidkernel (androideabi) toolchains, -fpic is enabled by default. At least on my 3.4 arm kernel, this causes an issue with kernel modules: "Unknown symbol _GLOBAL_OFFSET_TABLE_". On traditional armeabi toolchains, -fpic is not enabled, resulting in working kernel modules; let's follow that here. Change-Id: I3058b5213b34bdde9bb9d744563c7d55cd42d2a5

Developers can specify ccache parameters by sourcing a personal build environment script before envsetup. For example: CMHOME=$HOME/android/cm export USE_CCACHE=1 export CCACHE_DIR=$CMHOME/.ccache $CMHOME/prebuilts/misc/linux-x86/ccache/ccache -M50G # Maybe someday, currently not supported in ccache 3.1.x # echo "max_size = 50G" > "$CCACHE_DIR/ccache.conf" This reverts commit d99981e. Change-Id: Ic7b36a6d61269647aec022a86570cfa2068f65d7

* BOARD_USES_UBOOT is unused. * Same goes for BOARD_USES_UNCOMPRESSED_BOOT. Furthermore, it is superseded by TARGET_USES_UNCOMPRESSED_KERNEL. Change-Id: I9f0e2848fcd0cd212bccacf14df55ad03f821051

Currently, this script creates and leaves nearly 2GB in tmp per run. Clean up on exit. Change-Id: I4247dd2508e9d27de57c611c18e70800d7a47f33

…s set Currently devices that have TARGET_KERNEL_APPEND_DTB set also have to set BOARD_KERNEL_IMAGE_NAME to Image.gz-dtb (or zImage-dtb on arm32) in order to properly build the image with an appended DT. Automatially append -dtb if TARGET_KERNEL_APPEND_DTB is set so BOARD_KERNEL_IMAGE_NAME does not need to be set. Change-Id: I5464c67092a7b9f86669902e5c0e4a47836f7cbd

Change-Id: I9cbeb6edea79a7e9bb0fc692e53497b54058d67f

key passphrases may live in some sort of secure storage, support running an arbitrary command to retrieve them. Change-Id: I49862cf60f1b73a2356e0c492e1038beef28a95f

Change-Id: I4f31352139b2f38570f0370afff3901999082e48

These device-specific arguments are defined at build time and are necessary to generate the zip correctly. Don't use command line arguments to specify them, but write all the needed information in misc_info.txt when the target-files zip is generated. ota_from_target_files will then read misc_info.txt and set everything automatically. Change-Id: Ibdbca575b76eb07b53fccfcea52a351c7e333f91

If TARGET_OTA_ASSERT_DEVICE is not set, TARGET_DEVICE should be used for OTA_SCRIPT_OVERRIDE_DEVICE. Change-Id: If382dfa29dddb39498dec5f5eadc9895b7c47d88

The current check only checks for Linux, but many of us use GNU sed on darwin as well, which means the non-Linux command will fail, so read the sed version and use the GNU command if GNU is found in the version string. Change-Id: I7eefd0309751b069eef5e5e2b907d3d4f38f1638

This allows to update the property when signing the build content without the need of unpacking the boot images. Change-Id: I51c8ae757987fda1c34a6557a384f6c4dd428e03

…et files" sign_target_files_apks is currently dropping the content of BOOTABLE_IMAGES. As consequence, the images are re-generated without using custom mkbootimg makefiles, which can cause issues on some devices with specific formats or requirements. This reverts commit 71fbe14. Change-Id: If4c8c70ee32e21198859f594a2dc090abe2e13a1

Images placed in BOOTABLE_IMAGES/ are not re-generated when signing the target-files zip content. As of now, images are put into BOOTABLE_IMAGES/ only if BOARD_CUSTOM_BOOTIMG is set to true. Remove the flag and copy the images unconditionally since there's no need to re-generate them now that ro.bootimage.build.fingerprint is inside the build.prop. Change-Id: Idbb5329e0598c04c39fe7f1899b6af3dbdd4f0aa

* changes: Always copy bootable images in BOOTABLE_IMAGES/ Revert "releasetools: Don't extract BOOTABLE_IMAGES when signing target files" Move ro.bootimage.build.fingerprint to build.prop

@nathanchance

Pretty much identical to DirtyUnicorns/android_build@2871a7b Modified and updated for TWRP 3.0.3-x by @nathanchance Change-Id: Ic0cc0b6e96723a87298edb5cded9f6ef93c05b9d Signed-off-by: Nathan Chancellor <[email protected]>

If TARGET_NOT_USE_GZIP_RECOVERY_RAMDISK is true, we want to use bsdiff to create recovery-from-boot.p, otherwise there are high chances that imgdiff will fail. Currently this is done only when running make, but not when we re-create the patch from releasetools, so do it. Also, since recovery-resource.dat is used as bonus data for imgdiff, don't build it if we are going to use bsdiff. Change-Id: I93a662a358ee79f56b8acd4329eedd166a176c66

* Gotta save that space somehow. This is in the continuing effort to remove custom mkbootimg.mk files in device trees Change-Id: Ie8b3cedf6e37d1d11c2383dd3590f9908ad7818c

Change-Id: I39774eb49e0f093fff20b3583a0783ef4640ae2e

grep should be given the filename directly instead of using cat to pass the file contents. Change-Id: Ic5275ac0f057f3d134fe57f43672a73fa7e3d7de Signed-off-by: frk <[email protected]>

Android 7.1.1 release 21 Conflicts: core/build_id.mk core/version_defaults.mk Change-Id: Ie6b9c04dad6cd7ef5a7734a82736244d98d79a34

Change-Id: I1fb2f4c15644c61dc9d49b81d51067a6e86db6e9

This flag has been obsolete for a while now. Change-Id: Ib78a1b141ddd757d2546b2eff2158e6e0cc0d673

Android 7.1.1 release 25 Change-Id: I4d4a2cabff9cd0ae883e690f41bd2e14f8888236

Change-Id: I47d71f6f9f5f5c656b89b0ae9f4ec6ec2ff30915

The extra slash can create all kinds of problems throughout the makefiles. In particular, it caused a device to become unbootable because the ramdisk was incomplete due to mismatched filenames (some containing / and some containing //). Change-Id: I9dbb425aaf51e7ed2697dba0034f2ee92ab3c82b

@Cl3Kener

Thanks to @Cl3Kener for taking lots of his precious time to help me find these things that were driving me up the wall. I should have authored this commit as him but I didn't. Sorry buddy maybe next time.... Change-Id: I8d6cd504afe83954964f71eb7d8f802624d2e595 Signed-off-by: Chet Kener <[email protected]>

For Soong's build.ninja regeneration to work Bug: 32574042 Change-Id: Ie267ea33e8de88275e99330b2d0f147d1e58fa7b

This reverts commit 4aca571. Test: builds Change-Id: Iddb3517a4596e84404db1738fa95eb15f435a42d

bash doesn't kill children when it receives SIGTERM. Since makeparallel is the last command run by the shell, run it with exec to replace the shell with makeparallel so make can send the signal directly to makeparallel. Bug: 31907490 Test: m -j & killall make; pgrep -a makeparallel Change-Id: If8aeb51ec224234da5f05eae3382ce77f48a57e2

Set up a signal handler in makeparallel that will forward SIGHUP, SIGINT, SIGQUIT, and SIGTERM to the child process. Bug: 31907490 Test: m -j & killall make; pgrep -a ninja Test: make makeparallel_test Change-Id: I306e5335ed1b2c7056804d5da377a2f283877f30

Pruning $(OUT_DIR) can be overaggressive if $(OUT_DIR) matches the name of any directory in the source tree that contains Android.mk files. Pruning $(OUT_DIR) is no longer necessary, as one of the first things the build system does is put an empty Android.mk file in there to avoid recursing into it. Bug: 31941856 Test: m -j OUT_DIR=angler Change-Id: I7c5e95816f35bd5906845716d56cca76de7fa1ad

Remove assumptions about header side effects Test: compile Bug: 30465923 Change-Id: I117567b0f99814b9d9a955b39c56f43f7972cf62

Change-Id: I4f39e8d8cc22520cd36f83f8675a716cc1ade1d9

which throws an error if a binary is not found which breaks the build. Use command -v as it is safer. Change-Id: I2f08548e6559b9bd8ad7df19296f7bae960bad5c Signed-off-by: Nathan Chancellor <[email protected]>

When running makeparallel in non-ninja mode, which is used when running kati with USE_GOMA=true, convert -j to a reasonable parallelism value the same way ninja does. Bug: 34392351 Test: make -C build/make/tools/makeparallel makeparallel_test Change-Id: I9aee4dd2a3b0f2b1c2c10087be83f7b2b06f4368

Passing an empty argument in argv to ninja results in an error: ninja: error: empty path Don't add jarg to the argument list if it is empty. Bug: 34392351 Test: m -j Change-Id: I39c8998c79b09835650628e1413ae7625cdbc555

We never want Kati to see MAKEFLAGS, as forcefully overriding variables is terrible. The variables in MAKEFLAGS are still available in the environment, so if part of the build wants input from the user, it should be explicitly checking for an environment variable or using ?= This commit shouldn't actually change any behavior -- the version of Kati checked into our tree doesn't actually read MAKEFLAGS (the latest version does, which is why this change is necessary). We're also already clearing MAKEFLAGS during makeparallel, so the USE_GOMA case already doesn't pass through MAKEFLAGS. Test: Manual $(warnings $(origin MYTEST) $(MYTEST)) with old and new Kati Change-Id: I5e4ffa66b3539a539cc7a26da24645b11445c469

Build tools have been moved from prebuilts/sdk/tools to prebuilts/build-tools. Bug: 27857138 Change-Id: I60be42c197d420897dab77808c25818c9d2e81df

For acp, we've been using an old prebuilt in prebuilts/sdk, but it's not part of the SDK. Instead, we'll use a prebuilt in the build-tools repository. For ijar, we've been using the host libstdc++ to workaround the lack of libc++ on some unbundled branches. Instead, use a prebuilt that can use libc++. For ziptime, we've been disabling it on unbundled branches, due to the lack of libc++. Instead, use a prebuilt version of ziptime that can use the prebuilt libc++. Change-Id: If80f845ea06f76e3fe6765964e77c864eaf303d0

Test: SANITIZE_HOST=address m -j showcommands Change-Id: Ifdca98d5fa32867005ace99e1eb5188e22923ac6

Those libraries are already imported (or added to the classpath in the case of the check command) meaning that they were all duplicated. In addition to complicating the build this was also slowing down the compilation. Bug: 28307907 Change-Id: Ia8665e7c5ad8b567bd02de7839fa62e67a5668f7

Bootclasspath libraries are already added in LOCAL_JAVA_LIBRARIES by java.mk and host_dalvik_java_library.mk meaning that bootclasspath handling was just doing a duplicate work and adding duplicated entries to the classpath. Also fix order of bootclasspath libraries for host. Bug: 28307907 Change-Id: I6e98fc651a127435c029de65285dbf2cb04844af

* changes: Prevent Kati from seeing MAKEFLAGS Don't pass empty arguments to ninja Convert -j to a reasonable parallelism for kati Ccache configuration improvements Switch back to mksh as the default zipalign missing header Don't prune $(OUT_DIR) from findleaves.py Propagate signals through makeparallel exec makeparallel Revert "Remove -d keepdepfile from ninja command line" Update combined build.ninja to depend on Soong's build.ninja Kill some log spam

* changes: Remove bootclasspath handling for Jack Remove static libraries from Jack classpath Use ASAN prebuilts if SANITIZE_HOST includes address Use more prebuilt build-tools Update prebuilt build tools path

Change-Id: I51c3393dd359adc2834be1ef336da8ffedfff7a2

The easiest and best way to get openssl on darwin is using homebrew, however homebrew refuses to link openssl (and for good reason) in order to prevent conflicts with Apple's homegrown version. Include the openssl headers and dylibs from the dir that homebrew installs openssl to let 4.4 kernels compile. Change-Id: I06b66768fbdd4855fd57b88100d646ed6e311a59

Commit 7fb9251dfcc7a0876c8fb906338452204942144a modified the expansion in an illegal way. Fix the broken env variable. Change-Id: Ib3029fa995d6a4b0416887a2ef2e4792c9e6bb27

The zip file under $OUT/obj/PACKAGING/target_files_intermediate is used for final package creation, and it's being unzipped multiple times by releasetools. (Not to mention that it also takes an awful lot of time just to zip it initially.) Using 0 compression on it reduces the build time by several minutes. The final zip package is untouched by this change(remains compressed). Change-Id: Ic38b470f97f1e0ebb80da9d4f7750e4ccf53e05c Signed-off-by: Park Ju Hyung <[email protected]> Signed-off-by: Alex Naidis <[email protected]>

Android 7.1.2 Release 2 (N2G47E) Change-Id: Ie3d3e9ea5c8dd67f44e43b2ed5a97e844c19888d

Change-Id: Ib433b258f95b00a423affb7e892d387b7254b371

Change-Id: Id8a7d5cb62fc8e8b17e63f219138771ed634b741

…" into n7.1

…o n7.1

If old deprecated file based ota system, the zip file is too large because of 0 compression. Change-Id: Ia30aa921166ba1d6178108512aac356a37dc4ffe

This reverts commit f29352b. Change-Id: I7f2853e02b3408204a23b202444e5398e44cfabe

original commit: df574f3 This part was missed during AICPfication of build repo... Change-Id: I38423e7094eb52949b9eadeea8ba388e6715713a

export ENVSETUP_DEBUG=false to hide them Change-Id: I57ed1c89c6bb669597b8943aa4b290e9925b3398 Signed-off-by: Nathan Chancellor <[email protected]>

* Now build_verity_metadata.py takes an arg telling it what to do, in this case "build" is our intention, so update our custom runcmd array. * Ensure we cast all args to Popen as strings or picky python gets angry that we pass an int (image_size) to Popen Change-Id: I71c5e45e3155f470259f91f6f1a880e780aef369

use gio open Change-Id: If2fb9124ae81ca4da340c932ef5867d5022934a2

This reverts commit 68b5d4f. Change-Id: I29e57c1f9cc7f316fe8a53f759083860db6d297f

* This was only required for tomato kitkat 32bit to lollipop 64bit migration. This is no longer a supported upgrade case, so revert it to be inline with AOSP. * Users coming from stock should flash an updated 64bit recovery first This reverts commit b895106. Change-Id: Iccf37e5292c2068e9a1f8aeb370719cd9ced8c44

* Aosp browser is really old and insecure, we are replacing it with Jelly * Jelly is a simple webview-based browser, so it relies on installed webview, which makes it secure as long as webview is updated * Gello is still alive, it overrides Jelly instead of Browser target This reverts commit cf571f4. Change-Id: Ie5649cc213b3a5409d137d07bd6d1bfcdc789798

Android 7.1.2 release 8 Change-Id: Ied14553ee912d78e48ef7d427a307d4cea947703

And by default 'speed' compile those apps at build time. bug:33799337 Test: m -j32 (cherry picked from commit 9af4834) Change-Id: I66f1c675369fccc03b6529c08cb030264d15ba1c

bug:36532541 bug:33799337 Test: m -j32 && find out/target -name \*.odex (cherry picked from commit a2c6c0b) Change-Id: Ic4396bb6c543af1c05f56030495caafb245ea304

bug:33799337 bug:36534079 Test: m -j32 bullhead/angler/marlin/sailfish (cherry picked from commit e0848c8) Change-Id: I6d71bdca1d7b7afab8150a0b19a0e2235832d5e0

Change-Id: I9396d94f6fd37ce082b75259b5bf8a78b3591350

@dadi11

Thanks to @dadi11 for this find Change-Id: I03a0ba430c843893c26dc66a8f6e63616e306cba

Android 7.1.2 Release 17 (NJH47B) Change-Id: I1b66af6cb1b32284c9128b6d99cb70a7d6654ce9

This reverts commit 2b25066. Change-Id: I30f339cfe52ebe646a0b39a200140f538f6dafca

-Allow folks to see easily if the term session they are in has WITH_SU set to true -Also add a dumpvar rule for WITH_GMS for those that have it -Remove unused CYNGN dumpvar rules Change-Id: I9b3f7f729e31dee90caa366fe4798bbcea9e566f

Version string isn't shown while flashing. We are using prop ro.aicp.version to get version name and its value is 12.1-NIGHTLY So no sense to split the string Change-Id: I5509dafce302f9082007ebc543e048293854ee27

Change-Id: I773a092f44823b095cb4176a8647acef9519b870

Currently, in the display HAL, we're replacing the usage of this variable with a check for TARGET_BOARD_PLATFORM. Instead of having to do that every time a new branch is made, define the variable in qcom_target. Change-Id: Iddcc38c70adc52267e70c985b7a0ad3d8c4c8929

* Organize per family * Remove unsupported mpq8092 and msm_bronze * Add msm8998 Change-Id: I662a8e403045affa2a9b40511414ac6e8057f967

This flag enables user review of dangerous permissions pre-launch for apps targeting API < 23. Screenshot: https://i.imgur.com/o5HpaVu.jpg Change-Id: I98a68b3a20261cb7bded1ce5ca2fc9720cd4361c

Android 7.1.2 release 24 Change-Id: If7263d921e346390e33d8dc1558168554f1788f1

This reverts commit a3f0a4d. Causes disabling of custom WP setting, Wifi, Cellular qs tiles, BT keeps asking the same Permissions dialog everytime it's turned on. So, this is not ready to be merged. Change-Id: Ibdefd48d53fb0798bb1b96087255697f2bfb76e4

Change-Id: Iff693650db4b9423bc4bb16c12f592c2a74248af

* When using an ssh gerrit instance (-g) it is perfectly reasonable to pick a draft commit. Don't require force picking (-f) in order to do so. Change-Id: I420f566ee1bb1f0b0d2a2ef29d95e0545db70b89

* Add a build target to simply regenerate the kernel minimal defconfig and copy it to the kernel source Change-Id: I04be945eb6dae3042c236785328c7c9995d42e49

Stop calling `java -version`, remove HOST_JDK_IS_64BIT_VERSION All users of this variable have been removed. This command was adding 50-175ms to `lunch` (~15-30%), and was running at least twice (serially) in every build too. Test: cs/HOST_JDK_IS_64BIT_VERSION Test: prebuilts/jdk/jdk8/linux-x86/bin/java -version, is 64-bit. Change-Id: I0c0fe9f0c275ba64dfae4f9511318ea34edea963

Write into a temp file, then use `cmp` to determine whether to update the actual file. This means that we'll only run Kati twice on a clean build, since we'll omit the redundant write during the regeneration check. Simplify writing using $(file >) instead of $(shell), which doesn't have character count limitations. Bug: 35970961 Test: m clean; m -j nothing; m -j nothing; m -j nothing Test: Ensure clean_steps.mk is equivalent before/after Change-Id: Id574f416647434ab8d11ed3481da21b55e8797b7

This saves 20-50ms for `lunch` (~7-10%), and double that for every build execution. Test: Check HOST_OS_EXTRA on Linux & Mac Change-Id: Ifcd7dbdd0485ee2fcba9e81d8ae492be775c5fef

Currently, using project-set-path is blocking us from overriding the pathmap for the audio, display, and media HALs, so set them with set-device-specific-path to allow overriding the HALs with USE_DEVICE_SPECIFIC_* and DEVICE_SPECIFIC_*_PATH Change-Id: Iee3723cf251d0f485a77a17fd61cb62178833582

Android 7.1.2 Release 29 (NJH47F) Change-Id: I2249c6be18a8beb25e68c9205188d9aadb3e65cf

In case of conflict, reset to initial state by aborting the cherry-pick, leaving the working directory clean Change-Id: I2353b92254b67ea49835bc88b6fc9bc3910b5107

Change-Id: I90a44e040280bd43c40b06e14f658a5cf7e30297

Restore line that got accidentally deleted in f3d5525 Change-Id: Ied25f7670f11cddd5352148a043ecca8eb8cae09

* Use msm8996 HAL for 8953 & 8937 since they share the exact same git history sha1 in all 7.0+ released tags. Change-Id: I764a9a092b6d530de8a9b9e6e54f41c0b5d8a593

(cherry picked from commit 18be908) Change-Id: Ide74c0655eff5d24fcd7bf708b7e5ae5fe660d83

Building with LOCAL_STATIC_ANDROID_LIBARIES and LOCAL_USE_APPT2 causes a warning: build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets Only call find-subdir-assets if my_res_dir is not empty. Also improve the warning message to make it easier to find the module that caused it. Test: m -j Change-Id: I9a71162c7e2ed82f64d6844baca256968ac77317

Change-Id: Idc4602ad8c3067c9aeecc035783f52148bff2957 Signed-off-by: Ralf Luther <[email protected]>

Change-Id: I120a95fd261e09486a5293abecf4d0dea94fd234 Signed-off-by: Ralf Luther <[email protected]>

…ev Bug:64896113 (cherry picked from commit 73ab80d) Change-Id: I79c8696abc375a2c2cd77a2b12fec1558be70818

…ev Bug:64896113 (cherry picked from commit 1517f3d) Change-Id: Iaf69b105d57ab33dccde1b13be5271178269f82a

This patch prefixed bison with HOST_OUT_EXECUTABLES to ensure using our `bison` built from source. It also added bison to be a depencency of %.y and %.yy tasks so that it will be built if needed without any manual `mka bison`. Conflicts: core/config.mk Change-Id: Ic207124965c704b3f350e96b58d8e1f2683c2601

Change-Id: I9fd1b7832eee415ea2a6c718df419ea12ddfe620

KRACK vulnerability patches were shipped a while ago, so we can advertise a security patch level of 2017-11-06. Change-Id: I68300e296ae8fe10aecefd45cfa581d35d8086a8

Change-Id: I78682193de61e0119a634eed38277d044aa777cd

* changes: Bump Security String to 2017-11-06 Update Security String to 2017-11-05

Change-Id: Ib5a18e61ac99444b50538db122782c5830032396

Commits on Dec 6, 2016

NMF26S

gitbuildkicker committed Dec 6, 2016

Configuration menu

View commit details

Copy full SHA for 373adac

Browse repository at this point

Copy the full SHA

373adac View commit details

Browse the repository at this point in the history

N7.1 #40

Are you sure you want to change the base?

N7.1 #40

Commits on Aug 25, 2016

Commits on Aug 26, 2016

Commits on Aug 27, 2016

Commits on Aug 28, 2016

Commits on Aug 30, 2016

Commits on Aug 31, 2016

Commits on Sep 1, 2016

Commits on Sep 2, 2016

Commits on Sep 3, 2016

Commits on Sep 4, 2016

Commits on Sep 8, 2016

Commits on Sep 11, 2016

Commits on Sep 12, 2016

Commits on Sep 14, 2016

Commits on Sep 18, 2016

Commits on Sep 19, 2016

Commits on Sep 20, 2016

Commits on Sep 25, 2016

Commits on Sep 26, 2016

Commits on Sep 29, 2016

Commits on Oct 1, 2016

Commits on Oct 2, 2016

Commits on Oct 3, 2016

Commits on Oct 4, 2016

Commits on Oct 5, 2016

Commits on Oct 9, 2016

Commits on Oct 10, 2016

Commits on Oct 16, 2016

Commits on Oct 17, 2016

Commits on Oct 19, 2016

Commits on Oct 20, 2016

Commits on Oct 22, 2016

Commits on Oct 24, 2016

Commits on Oct 26, 2016

Commits on Oct 27, 2016

Commits on Oct 28, 2016

Commits on Oct 29, 2016

Commits on Nov 4, 2016

Commits on Nov 5, 2016

Commits on Nov 8, 2016

Commits on Nov 9, 2016

Commits on Nov 10, 2016

Commits on Nov 11, 2016

Commits on Nov 14, 2016

Commits on Nov 24, 2016

Commits on Nov 25, 2016

Commits on Nov 30, 2016

Commits on Dec 1, 2016

Commits on Dec 4, 2016

Commits on Dec 6, 2016

Commits on Dec 7, 2016

Commits on Dec 10, 2016

Commits on Dec 11, 2016

Commits on Dec 13, 2016

Commits on Dec 18, 2016

Commits on Dec 19, 2016

Commits on Dec 26, 2016

Commits on Dec 31, 2016

Commits on Jan 3, 2017

Commits on Jan 5, 2017

Commits on Jan 8, 2017

Commits on Jan 12, 2017

Commits on Jan 13, 2017

Commits on Jan 14, 2017

Commits on Jan 18, 2017

Commits on Jan 19, 2017

Commits on Jan 21, 2017

Commits on Jan 23, 2017

Commits on Jan 29, 2017

Commits on Jan 30, 2017

Commits on Feb 6, 2017

Commits on Feb 11, 2017

Commits on Feb 21, 2017

Commits on Feb 23, 2017

Commits on Feb 25, 2017

Commits on Mar 4, 2017

Commits on Mar 5, 2017