- 11 Jul, 2015 3 commits
-
-
Corey Edwards authored
This reverts commit 56d96ae8. Conflicts: core/Makefile
-
Corey Edwards authored
This reverts commit 513f7930.
-
Corey Edwards authored
This reverts commit 1cbbd46c.
-
- 13 Mar, 2015 1 commit
-
-
MrApocalypse authored
Android 5.1.0 release 1 Conflicts: CleanSpec.mk core/Makefile core/apicheck_msg_current.txt core/build_id.mk core/tasks/apicheck.mk core/version_defaults.mk tools/releasetools/ota_from_target_files
-
- 05 Dec, 2014 1 commit
-
-
houst0nn authored
Needs: 1 - a build 2 - a connected device Change-Id: I24820b984e79430b7af7ccedc171fc69269c0a32 envsetup: eat safely Change-Id: I2d8b52206213d8f4d8dcce3518cadb2be59e78d8 eat more safely, if there is something to eat Check for zip file presence before trying to eat Change-Id: I7913be619d189bbd723263edad878d6d05b8a5a7 Fixed eat not waiting for device if adb server was not started $(adb get-state) returned unexpected starting server message causing the if statement to fail. Calling "adb start-server" beforehand remedies that. Patch Set 2: $(adb get-state) returns 'unknown' if Clockwork recovery is running on the device look for /sbin/recovery and 'pass' the state test also adb wait-for-device will result in endless loop, replace with until loop using with get-state OR 'recovery' tests Patch Set 3: fix the initial adb state test, use AND instead of OR Patch Set 4: Rebased and prevent "device not found" message from spamming the screen by redirecting error output to null Change-Id: I2d41b8853567cde80bf7fc08b5e4f0ad5ba1fdf5 Signed-off-by:
Firerat <firer4t@googlemail.com> Updated for CM9 variables eat: Adapt to new file naming scheme Change-Id: I101e333918bc215bebcc594c97bdd68307c90aaa eat: Adapt to new storage paths Change-Id: Ic060304275c2d19858636c84740b3f60dfdc6193 envsetup: Make eat restart adbd as root before pushing the recovery command Without adbd running as root we can't write to /cache/recovery and eat fails with a permission denied. Change-Id: I015b50f29c001605cdc1a0088f68296b62809b56 Eat: Option to specify directory of zip in recovery mode It pushes to /mnt/sdcard0, which may be /emmc/ in recovery. Now the user can specify another path other than /sdcard/ where the zip is Change-Id: Ie39615132ae39d9f6b304a3049b2395b2a2af182 fix "eat" Assume user 0 is the active one when flashing... Change-Id: Ibdc28ef49f8023e786ee82c9e42c221409dfd6bb eat: Use /cache if possible * Check the size of /cache and use it if possible. Change-Id: I72fecf3f8d2311c04e63fe81a7ca9a8a6a40419d
-
- 04 Dec, 2014 1 commit
-
-
ayysir authored
Change-Id: I1063dc744f7f6ab618e10c9e3b5132af1cbab490
-
- 21 Nov, 2014 12 commits
-
-
MrApocalypse authored
-
bryan2894 authored
Prebuilt chromium: update for lollipop Change-Id: I4e34feb26c1b4bec10fb751a10dbc52579d7cd07 Prebuilt chromium: Run a check for target device directory this should fix the issue that arises if device fails and device is built again, chromium will error out because it thinks the prebuilt files exist (which they are not, directories are just created). Signed-off-by:
Ayysir <ayysir@aospal.com> Change-Id: I595cab268e66c738ccae9900150b36d7f9626a6e
-
Jiangyi authored
This adds a chromium_prebuilt function to envsetup.sh that is invoked by lunch to check whether the chromium prebuilts are up-to-date or not. If not, it will be built from source and then the new source built version will be pulled during brunch/mka bacon to become the new prebuilts for future builds. This is all opt-in through the USE_PREBUILT_CHROMIUM flag. Without it being set to 1, none of this would be ran, and regular operations will go on. PS13: -use export TARGET_DEVICE -replace git -C with params compatible to old git versions (vendor repository for script) Change-Id: I40f8c8dbd2a8a84a5c1b9f47ee04180a71ef4e07 Conflicts: core/Makefile
-
ayysir authored
- Build CellBroadcastReceiver - Replace Launcher2 w/ Launcher3 & remove QuickSearchBox - add PRODUCT_BUILD_PROP_OVERRIDES - Remove deprecated Music package - Remove optional "Home Sample" Launcher and more... Change-Id: Ic8f707e7c2f492812648a4a5c3cc0b22af5fbb08
-
Brint E. Kriebel authored
Even if we are doing TARGET_BUILD_APPS, we may want to use a pa target for building. Change-Id: Ic8053bc679fa8b726be90e611aeaacdf1850cabc Conflicts: core/product_config.mk
-
Ricardo Cerqueira authored
SDK-readable via android.os.Build.INCREMENTAL Change-Id: If9885adebe12a56b2b2e353285721be695bc411b Fix exporting the unique build identifier Change-Id: Ie58e981b7e83a4351d137dfd8995dce7d365d950 Fix incremental build number on Darwin Darwin does not include sha1sum, but it should have openssl. Change-Id: If2b685c1478f9486bed21dfba0c655d9e02db72b Use openssl instead of sha1sum Change-Id: Iab8a74d4af6646104cb23312853f811a38bdec0d Conflicts: envsetup.sh
-
Chirayu Desai authored
* out/target/common isn't really common, and if you do back to back builds for multiple devices, that is noticable. * Use out/target/common-$device instead, and link the appropriate dir to out/target/common every time lunch() is run, if CM_FIXUP_COMMON_OUT is set. * Refer https://groups.google.com/forum/#!topic/android-building/ispbOgzoyg8 for more info. Change-Id: I11e7df0e68e2a60ce32576f06397d60fc9465b60
-
cybojenix authored
It's very simple, but with more and more devices coming in, a long list won't cut it There are probably better ways of doing this, feel free to comment Change-Id: I9bd1fef920f985a133c882df9987b6be29dbc7b8
-
nebkat authored
Change-Id: I3b5bf8a5f62dcdf267662bb97a2073150152cfa6
-
Chirayu Desai authored
Change-Id: Id90d84748df41d6626dfd46befabe0054c6d14e7
-
Steve Kondik authored
* I want my own PROMPT_COMMAND to coexist with Android's, so stash it in the environment and add it to the new command. Change-Id: I200902f135d0c5c620a8eb3ce9cefdba318cf9d3 envsetup: Fix $PROMPT_COMMAND Change I200902f135d0c5c620a8eb3ce9cefdba318cf9d3 broke the android PROMPT_COMMAND on scenarios where the existing prompt already had a hardstatus adjustment, since appending it to Android's just clobbered Android's in favor of the original. So instead of appending them, inject android's at the beggining of the existing one (and create a default if none exists) Change-Id: I1fbcbfdb6220d886dda3662da498d1759a4c195b envsetup: Really fix PROMPT_COMMAND handling * Add ANDROID_NO_PROMPT_COMMAND to not change it at all. * Export ANDROID_PROMPT_PREFIX so it can be used elsewhere. Change-Id: Ib2a487404d3b8a367a21582e8a0ce69c2d212a9a envsetup: More PROMPT_COMMAND * Get rid of ANDROID_NO_PROMPT_COMMAND, the pre-existing STAY_OFF_MY_LAWN does the same thing * Remove any pre-existing android prefixes to avoid accumulation scenarios in consecutive builds (i.e., multiple build identification strings in hardstatus) Change-Id: I86661e066e18ea6ad0c742fa1dc6555780fa5441 envsetup: add quotes around PROMPT_COMMAND Better compatibility for zsh. Change-Id: Ie010c30580e67e3b5357e3cc869114a525762677
-
houst0nn authored
If building a pa_* product, skip crawling the filesystem for AndroidProduct makefiles (and, of course, parsing their contents) and aim directly for the device/pa/<product> device configuration Change-Id: I2a5e70dda973a6fcdbba0d5e26b35b99d3f1aea2 Change how we search for PA makefiles. build: Fix fastpath code for PA_BUILD * We need to adjust to the new validations Change-Id: I9066d4f437beb9597027ee6bbb52504b5e7e84c5 build: Fix pa builds the setup variable wasn't exported, and was being missed by part of the scripts
-
- 19 Nov, 2014 4 commits
-
-
ayysir authored
History === [*]roomservice: Auto-remove duplicated projects roomservice has improved in the sense that once a duplicate path is found, a <remove-project> tag will be added into roomservice.xml Change-Id: If3e1dc672d25996a0cd19628ece24c010e213adf [*]roomservice: Include forked repositories in device search The github api defaults to not including forked repos in search results. This causes roomservice to fail to find a device repo if it is a fork (I.E. maguro). This commit adds the necessary argument to include forked repositories in the results and fixes maguro syncing. Change-Id: I50ec96316c3208e977d659a1dd90205a2b3d85b3 Signed-off-by:
Evan Anderson <evan1124@gmail.com> [*]roomservice: Fix device syncing Change-Id: Id4a59d74531a4ea1744f845fbe65b43debf950dd Signed-off-by:
Evan Anderson <evan1124@gmail.com> [*]Switch to OmniRom's roomservice All credit goes to Omni for this. PS2: Update defaults to use with PA PS3: Give proper authorship PS4: Update dependency file name PS5: Set default_team_rem to github PS6: Revert PS5. Depends on manifest change Change-Id: I77fe0e958a3da5a3d65d0bf8c929fed2b13115bd Signed-off-by:
Evan Anderson <evan1124@gmail.com> [*]roomservice: fix missing revision line Change-Id: I727f3a6ab1345b32b61b1c1bda31f03008082c96 Signed-off-by:
Evan Anderson <evan1124@gmail.com> [*]roomservice: Fix adding to manifest Python is indent-sensitive, so needed to indent some lines. Change-Id: Iaa360754038e4966fb76eb264e7c3195209735a1 Signed-off-by:
Evan Anderson <evan1124@gmail.com> Contributers: @Ryuinferno @Cybojenix Change-Id: I91ee64727edf80cbe2cce7934de0adcf813b55a6
-
Emilio López authored
Basic functionality has been tested on zsh 5.0.2 and has been found to work correctly. Change-Id: I02e5e3bedf56b43104c280d9737ae7b334357643
-
Emilio López authored
complete is a bashism; so it will fail on other shells. Avoid printing an error if that is the case. Change-Id: Id6d6311792f409cc3a697c7a2bb003863f1afe60
-
Ayysir authored
Change-Id: Idc30394631a5cf20038784ffb381f419966505b7 Conflicts: envsetup.sh
-
- 05 Nov, 2014 2 commits
-
-
Nick Kralevich authored
Proper selinux labeling support for files on rootfs was never completely implemented. Instead of putting coredump files on rootfs, put them on tmpfs instead. See: http://www.mail-archive.com/seandroid-list@tycho.nsa.gov/msg01815.html Bug: 18227650 Change-Id: I2eeabee4fe1a14bfbf990a4a518d538d6b4b6e87
-
Iliyan Malchev authored
b/18229600 shamu kernel is failing to build on build machine Change-Id: Ia67443853443e4d7db9311bf8da69a5dc0da8e5e Signed-off-by:
Iliyan Malchev <malchev@google.com>
-
- 04 Nov, 2014 1 commit
-
-
Justin Morey authored
If no density value is specified when invoking tapas, we now export a default value of 'alldpi' Change-Id: I12b22a4cbd0ef604826aad66c5f7ab9271eb6d57
-
- 03 Nov, 2014 1 commit
-
-
Iliyan Malchev authored
b/18229600 shamu kernel is failing to build on build machine Change-Id: I1b7e6d0ebf3e966a89ae4c7fed0cfd2db3f0a6a9 Signed-off-by:
Iliyan Malchev <malchev@google.com>
-
- 31 Oct, 2014 2 commits
-
-
Dmitriy Ivanov authored
Differences between this implementation and the old one: 1. Resolves symbols/gdb based on device information (lunch target is irrelevant) 2. Works with downloaded from build-server symbols 3. Does not require user to specify exe file - detects it automatically Bug: 18208329 (cherry picked from commit 9b8e4b37) Change-Id: I13ae2debb6e2d827b9aa55e93864b5d60c2bd32e
-
Iliyan Malchev authored
The shell functions in this patch enable crashing processes with the core limit set correctly to dump core in directory /cores. They do so by remounting the root partition, which is RAM-backed, and by creating the 0777-chmodded /cores under it. They also set the core file pattern in /proc/sys/kernel/core_pattern to be /cores/core.%p, such that a core dump will have the crashing process' PID appended to it. You enable core-dump generation once per boot, as follows: coredump-setup If a process does not have its core-size rlimit set (as most do not), you can either set it manually by typing "adb shell prlimit <pid> 4 -1 -1", or by typing coredump-enable <name>, e.g. coredump-enable $(pid mediaserver) Alternatively, you can cause a running process to dump core by sending it a SIGSEGV via the shell function core <name>, e.g.: core $(pid mediaserver) Change-Id: Ib174e7ee95515fb9866fa6bf0d5b5bf23f3ec61b Signed-off-by:
Iliyan Malchev <malchev@google.com>
-
- 23 Oct, 2014 1 commit
-
-
Jeff Hamilton authored
It allows overriding the density the app is built for. Currently only used in the GMS core APK's gradle file. Change-Id: I3606df313a3110208cd8e6acade5f558261c921f (cherry picked from commit 7e3d2341570681e566872216796dc4f79c8695ef)
-
- 05 Oct, 2014 1 commit
-
-
Christopher Ferris authored
If you are debugging a native process, SIGSEGV gets ignored by default. Make it so that the special ART gdb macro is only called when debugging app_processXX. Bug: 17815162 Change-Id: Idba86860dfd94e7483f2668beeb76b3e6032fb34
-
- 16 Sep, 2014 1 commit
-
-
David 'Digit' Turner authored
Due to a bad previous merge, everytime 'lunch' is called, a new instance of prebuilts/android-emulator/<system>/ will be added to your PATH. This patch fixes the issue by removing the duplicate code that should have been removed during the merge. Note that android-emulator is still being added once to the PATH by code that appears before in the script. BUG=17524154 Change-Id: Iaa03159b0c81b15ef4c7c420e2f76e0a48aba789
-
- 12 Sep, 2014 1 commit
-
-
Brian Carlstrom authored
Bug: 17253957 Change-Id: Ifd6d5984f63981e1f99b6ae6f9459c2801588459
-
- 11 Sep, 2014 1 commit
-
-
Dan Albert authored
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 de21059a)
-
- 25 Aug, 2014 1 commit
-
-
Ying Wang authored
To override define function get_make_command() in vendor's vendor-envsetup.sh. Change-Id: I553e60816eb789750ccd16110f2e82a5087587e8
-
- 05 Aug, 2014 1 commit
-
-
Duane Sand authored
Use 4.9 mips64el toolchain for both 64- and 32-bit builds. Tell ld when 32-bit links are required. Override 4.9's changed defaults for mips floating point register use, to get same assembler rules as 4.8 and earlier. Also: drop unused soft-fp build targets, cleanout redundant compiler options, and remove extraneous Android.mk file. (cherry picked from commit 6670e24a) Change-Id: I34d2f8fc6113c9d1670e3acff1aff48634b9fe1b
-
- 26 Jul, 2014 1 commit
-
-
Jeff Brown authored
Also add it to the help list since it was missing. Change-Id: I11403e63bc421fd146ad88452eac05043eacabc3
-
- 18 Jul, 2014 2 commits
-
-
Ed Heyl authored
Bug: 16368823 | Lunch sets $out with extra text Change-Id: I2a1d422865a073cd30e86f1e20b4d99a3747cc0b
-
Nick Kralevich authored
Use /data/local/tmp for runhat reports, instead of the sdcard. system_server isn't allowed to handle sdcard file descriptors, since the sdcard could be ejected at any time, causing the kernel to kill the system process. This addresses the following SELinux denial: W/main ( 9906): type=1400 audit(0.0:16): avc: denied { read write } for path="/mnt/shell/emulated/0/hprof-600" dev="fuse" ino=3077890536 scontext=u:r:system_server:s0 tcontext=u:object_r:fuse:s0 tclass=file Bug: 16375996 Change-Id: I4c2053c327526c2f8e6812f4ed911a712ae9a9b8
-
- 09 Jul, 2014 1 commit
-
-
Ying Wang authored
Change-Id: I1190a0b1c84fa17b3692427eb6071ffbe84bc529
-
- 01 Jul, 2014 1 commit
-
-
Ying Wang authored
This fixes mmma broken due to quotes stripped in the argument passing. Change-Id: I6095c7ccf0660ba7b17a659f5df29b05e50e6303
-