KVT49I
.1 becomes .2

Change-Id: Ib4208e24e66b05ff441302a817be22ea213eb1df
KVT49K
"KVT49L"
build: Prevent some auto-generated variables from being overridden

These variables are used by internal processes for build indexing
and identification, and those processes expect either specific patterns,
or uniqueness.
So prevent accidental overriding of these by device configurations:
BUILD_DISPLAY_ID, BUILD_NUMBER, PLATFORM_VERSION, PLATFORM_SDK_VERSION,
PLATFORM_VERSION_CODENAME, BUILD_VERSION_TAGS

Change-Id: I06252f2687a5e5fd97ee21a98f26c739fd0ef6e4
Store the path to the ota file generator where it can be reused

Change-Id: I8896713c79a751b79fbbcc75f6ba30dad4ea9fac
build: Add support for vendor product and device name

 * CM's build system assumes some convention-over-configuration which
   we might need to override in order to conform to vendor requirements.
 * Allow overriding of target and product names using these new
   variables. This allows for CM conventions to work, while generating
   the correct fingerprint dynamically without post processing the
   strings.

Change-Id: Ic5913e587400dd38c04aa05de3a7becced77a59e
For user builds, use a release build id in the description if one exists

Companion change to Ic5913e587400dd38c04aa05de3a7becced77a59e

Change-Id: If5edbf56d567701f96f0ba46af9a90ffa8310c24
Allow individual projects to enforce a property's value

Some projects require system properties to be set to a specific
value (for example, a shared library needing a property pointing
to its own path) in order to work correctly, but some device
configurations are mistakenly setting those properties with the
wrong value (usually inherited from the original OEM build).

"PRODUCT_PROPERTY_UBER_OVERRIDES += property=value" can (and
should) be used in that project's makefile to ensure the value
is the correct one. This variable is intended for software projects,
and should never be used in product makefiles (BoardConfig, cm.mk,
AndroidProduct)

Change-Id: I1986e7c444e51cce8b198e43fdc793fad16d6276
Store the value from TARGET_OTA_ASSERT_DEVICE to a file

This is needed so it can be read in when re-signing a package to
allow for the proper device asserts.

Change-Id: I8f3bb491bbbaa4d2b827a45ef83f12c6c83e6712
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 'kitkat-mr1.1-release' of https://android.googlesource.com/platform/build into kitkat

Change-Id: Ib8998aa3704758ab070d8bd97d6713c06fac4aba
Allow devices to specify certain ro. props via TARGET_UNIFIED_DEVICE

This modifies buildinfo.sh to not set model, name, description, and
fingerprint in build.prop. These can then be set via custom init
lib.
This also fixes ota_from_target_files to function without these
props being preset.

Change-Id: I945b2c38e60b207d2d0f82b34f4f230ac21b0657

Conflicts:
	core/Makefile
	tools/releasetools/ota_from_target_files
roomservice: Fix handling of devices with _ in their name

Currently, roomservice takes every _ in the device tree name and
replaces it with /

Instead, strip the device name (such as pollux_windy) from the repo
name before replacing _ with / and then append it again when we're done

Change-Id: Ieabe85ecd8829c959a7296e5cd73f577879c4ffc

Conflicts:
	tools/roomservice.py
gettop: fix symlink detection

Summary: We must use the -P flag for pwd to properly get $PWD from the environment *with* symlinks. Otherwise symlink
detection is broken and anything we do using $(gettop) at the top of a symlinked path won't work properly. I noticed this
issue while running on a system that has a SSD RAID symlinked to my android build home directory, which is ~/ssd_storage.
The top in this instance is a symlink, which means that gettop() returns my home path, or the path above the symlink
directory (but not the symlinked directory). This is a major issue in case developers choose to use $(gettop),
$ANDROID_BUILD_TOP, or $T (doesn't really matter either way).

Test Plan: Create a symlink and sync android source into the path. Open up the symlink, run envsetup.sh, and check
$(gettop) output.

While this isn't the best solution, it fixes an issue without creating new issues.

Change-Id: I65bc345753805e6161098d2af6e0bee0b07d37b1
Keep InCallUI in memory (3/3)

Build the dummy InCallUI apk

Change-Id: Idfb7fa760eacc8d6e46d50ce682fb06c0acfc8f4
Telephony(MSIM) : Add telephony-msim jar to build

Enable telephony-msim jar by adding it in PRODUCT_BOOT_JARS
 and PRODUCT_PACKAGES

Change-Id: Ibc80a19d3e0c39dfbe885916d61147055f3801a9
(cherry picked from commit b9ebc2172e9b646cb573fa5610f8a2829874b2a7)
(cherry picked from commit 2aff65e670639f07c0962f04b65f812618a181b9)
Store the value from BOARD_CUSTOM_BOOTIMG_MK to a file

This is needed so it can be read in when re-signing a package to
use the proper boot image.

Print notice when using a custom bootimage makefile

Change-Id: I6baab9f8964ce5d4fa9487f2859af9c385d7b21b
roomservice: fix derp breaking initial device sync

Change-Id: Iab4d40d2365d90a8070d5ca09776bfec0acc3eda
build: Add script to generate extra images

Change-Id: I53081c7a2b4f18bc8c8a27b04d311a6b078b2022