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 device syncing

Change-Id: Id4a59d74531a4ea1744f845fbe65b43debf950dd
Signed-off-by: Evan Anderson <evan1124@gmail.com>
Merge tag 'android-4.4.2_r1' into update

Android 4.4.2 Release 1
Build Stk (Sim Toolkit)

Change-Id: I3a3406237e274b7272947f9b3e87475fffaf884c
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>
Slight changes in Makefile

- generate CUSTOM_TARGET_PACKAGE: this makes the rom name to appear and the zip not being copied to the root directory
- remove custom cache image generation: no needed anymore
- generate zip's md5

Change-Id: Ib055309ae70dc5e8e7b217463bbb880569ff1650
Makefile: use correct md5 extension

* our servers and OTA uses md5 extensions not md5sum

Change-Id: I404349a3d6b48d83f45776a749f6c5a84565a047
Signed-off-by: houst0nn <houstonn@gmail.com>
Merge branch 'google/kitkat-mr1.1-release'

Signed-off-by: Andre Saddler <dresadd09691@gmail.com>
Remove QuickSearchBox from build

* This thing is ancient, and apparently conflicts with Google Now.

Change-Id: I18548dd0b61cc8dedf6570562d073d0973120cba
TEMPORARY: Remove supersu backup script

Switched to superuser now so lets make sure supersu is completely gone.

Change-Id: Ice4bba005cf4bfc7d76b187f3622eeb712b84fde
Signed-off-by: Evan Anderson <evan@thelinuxman.us>
"KTU84M"
Colorize javac errors

You know those multi-line ones that are frequently interspersed with other buld output?
The ones that don't even have the word "error" in them to search for?

This makes them red.

ps2: fix jar_check failures cause by leaving empty stderr files in intermediates dirs
     this is probably not the best place to store stderr before colorizing it if javac
     exits non-zero, but it seems much lighter than mkdiring a bunch of temp directories
     or using sed to mangle the paths to point to per-intermediates directory unique
     temporary file names

Change-Id: I3b9b7d8a0c76958588ac1603b6742987d6dde54c
Signed-off-by: nuclearmistake <nuclearmistake@gmail.com>
Runtime resource overlay, iteration 2

Support any number of overlay packages. Support any target package.

UPDATED PACKAGE MATCHING
------------------------
In Runtime resource overlay, iteration 1, only a single overlay package
was considered. Package matching was based on file paths:
/vendor/overlay/system/framework-res.apk corresponded to
/system/framework-res.apk. Introduce a more flexible matching scheme
where any package is an overlay package if its manifest includes

    <overlay targetPackage="com.target.package"/>

For security reasons, an overlay package must fulfill certain criteria
to take effect: see below.

THE IDMAP TOOL AND IDMAP FILES
------------------------------
Idmap files are created by the 'idmap' binary; idmap files must be
present when loading packages. For the Android system, Zygote calls
'idmap' as part of the resource pre-loading. For application packages,
'idmap' is invoked via 'installd' during package installation (similar
to 'dexopt').

UPDATED FLOW
------------
The following is an outline of the start-up sequences for the Android
system and Android apps. Steps marked with '+' are introduced by this
commit.

Zygote initialization
   Initial AssetManager object created
+    idmap --scan creates idmaps for overlays targeting 'android', \
           stores list of overlays in /data/resource-cache/overlays.list
   AssetManager caches framework-res.apk
+  AssetManager caches overlay packages listed in overlays.list

Android boot
   New AssetManager's ResTable acquired
     AssetManager re-uses cached framework-res.apk
+    AssetManager re-uses cached 'android' overlays (if any)

App boot
   ActivityThread prepares AssetManager to load app.apk
+  ActivityThread prepares AssetManager to load app overlays (if any)
   New AssetManager's ResTable acquired as per Android boot

SECURITY
--------
Overlay packages are required to be pre-loaded (in /vendor/overlay).
These packages are trusted by definition. A future iteration of runtime
resource overlay may add support for downloaded overlays, which would
likely require target and overlay signatures match for the overlay to
be trusted.

LOOKUP PRIORITY
---------------
During resource lookup, packages are sequentially queried to provide a
best match, given the constraints of the current configuration. If any
package provide a better match than what has been found so far, it
replaces the previous match. The target package is always queried last.

When loading a package with more than one overlay, the order in which
the overlays are added become significant if several packages overlay
the same resource.

Had downloaded overlays been supported, the install time could have been
used to determine the load order. Regardless, for pre-installed
overlays, the install time is randomly determined by the order in which
the Package Manager locates the packages during initial boot. To support
a well-defined order, pre-installed overlay packages are expected to
define an additional 'priority' attribute in their <overlay> tags:

    <overlay targetPackage="com.target.package" priority="1234"/>

Pre-installed overlays are loaded in order of their priority attributes,
sorted in ascending order.

Assigning the same priority to several overlays targeting the same base
package leads to undefined behaviour. It is the responsibility of the
vendor to avoid this.

The following example shows the ResTable and PackageGroups after loading
an application and two overlays. The resource lookup framework will
query the packages in the order C, B, A.

        +------+------+-     -+------+------+
        | 0x01 |      |  ...  |      | 0x7f |
        +------+------+-     -+------+------+
            |                           |
        "android"                Target package A
                                        |
                       Pre-installed overlay B (priority 1)
                                        |
                       Pre-installed overlay C (priority 2)

Change-Id: If49c963149369b1957f7d2303b3dd27f669ed24e
Theme Engine [8/8]

Adds aapt for on device compiling of theme assets
Merge tag 'android-4.4.3_r1.1' into update

Android 4.4.3 release 1.1

Conflicts:
	CleanSpec.mk
	core/build_id.mk
	core/version_defaults.mk
	tools/releasetools/ota_from_target_files

Change-Id: I537e3be2401d98141a0f5837d07e57d73cbb8459
Merge remote-tracking branch 'AOSPA/kitkat' into 4.4.3

Conflicts:
	CleanSpec.mk
	core/Makefile
	core/build_id.mk
	core/version_defaults.mk
	target/product/telephony.mk
	tools/releasetools/ota_from_target_files
	tools/roomservice.py

Change-Id: I03045fe52db2813afda9c0e21aa30f3f18b46455
build: Disable mandatory recovery build

Some devices doesn't build recovery
fix: invalid syntax
Merge remote-tracking branch 'PA/kitkat' into kitkat-legacy-staging

Conflicts:
	core/Makefile
	core/build_id.mk
	tools/releasetools/ota_from_target_files