init.rc: mount pstore fs, set console-ramoops permissions

Change-Id: I44cb00f9123c6044a03de926b6a616da753bb549
Fix overflow in adb_client

Change-Id: I7f8582bd8a69d61ce47d11a9ffd0e901fc371037
Credit: Joshua Drake
Bug: 12060953
am e89e09dd: Fix overflow in adb_client

* commit 'e89e09dd2b9b42184973e3ade291186a2737bced':
  Fix overflow in adb_client
am d63fb078: am e89e09dd: Fix overflow in adb_client

* commit 'd63fb078aea697c536b19c03d29d4dde4ac087fc':
  Fix overflow in adb_client
am 03d4eb29: am d63fb078: am e89e09dd: Fix overflow in adb_client

* commit '03d4eb29003a712c28733646588fafc8939fc1fe':
  Fix overflow in adb_client
am e975716e: am 03d4eb29: am d63fb078: am e89e09dd: Fix overflow in adb_client

* commit 'e975716e36c9ad6aa80be2b54ee2cc63eadbdc44':
  Fix overflow in adb_client
am ba104fb7: am e975716e: am 03d4eb29: am d63fb078: am e89e09dd: Fix overflow in adb_client

* commit 'ba104fb7f1f0acad99a0d3a1cf7153aab57ea450':
  Fix overflow in adb_client
am cd072e94: am ba104fb7: am e975716e: am 03d4eb29: am d63fb078: am e89e09dd: Fix overflow in adb_client

* commit 'cd072e94cf7e546cd6d333cd65641edcd69402b7':
  Fix overflow in adb_client
am 54a80bcf: am cd072e94: am ba104fb7: am e975716e: am 03d4eb29: am d63fb078: am e89e09dd: Fix overflow in adb_client

* commit '54a80bcf88060b21f527c631c7ec911171bdb13f':
  Fix overflow in adb_client
am 33e7f915: am 54a80bcf: am cd072e94: am ba104fb7: am e975716e: am 03d4eb29: am d63fb078: am e89e09dd: Fix overflow in adb_client

* commit '33e7f915d6a27880dd4c4c0709dcc921f549eea2':
  Fix overflow in adb_client
am 02d90b92: am 33e7f915: am 54a80bcf: am cd072e94: am ba104fb7: am e975716e: am 03d4eb29: am d63fb078: am e89e09dd: Fix overflow in adb_client

* commit '02d90b92ce65ad4e7f49565f0e97373e1d8b0fbf':
  Fix overflow in adb_client
Remove obsolete vdc call.

Since ca8e66a8b0f843812014a28d49208f9f6f64ecbc, init has
been handling reboots and filesystem unmounts. Remove obsolete
call to vdc.

Bug: 12504045
Change-Id: If8704ca042cb3a68857743b9973e48c52e7eb881
(cherry picked from commit 225459a5da21e9397ca49b0d9af7d5fe3462706b)
don't load property_contexts from /data

Bug: 12613118
Change-Id: I5a84b13d2151075d5136e3682431fbcc9307df13
(cherry picked from commit dc3a42bb11dc2aefee37f799b5a1cce87cf35aaf)
init.rc: prep tcp_default_init_rwnd, set the default to 60

The kernel's default is between 4~20.

Prepare for javaland to modify the value at runtime.

It can be done via
  setprop sys.sysctl.tcp_def_init_rwnd  <value>


Bug: 12020135
Change-Id: Id34194b085206fd02e316401c0fbbb9eb52522d2
(cherry picked from commit 7c862c8b5e59cbe216a5bc092c01f1ecba8e9de4)
toolbox: Avoid issues with non-regular files

Toolbox uses open() in order to check for existence of a file, instead
of using stat(). This breaks when using non-regular files such as FIFO,
because opening a FIFO for reading blocks until a writer is available.

Change-Id: I008d246d68f7ce56040f4b4c36e5ff4f9c34f4dc
init: update recovery when enabled in settings

Update the recovery image only if the option is enabled
under Developer options

This reverts commit 231e0a9e6a1da6fa4a188840f68af649669e417f.

Change-Id: I928f7ee8bb3eaf5581bb8225661d253ecca0c4ef
Change CM recovery install script filename [2/2]

This is part 2/2 to maintain backwards compatibility with CWM's
verify_root_and_recovery() function. CWM checks if install-recovery.sh
exists and has an executable flag set, then offers to disable the script
for the user. CM now controls this with the persist.sys.recovery_update
property which is configurable via settings, so we don't need to
double-check this.

This changes the name of the recovery install script to
install-cm-recovery.sh.

Change-Id: I275dd358b46c626dfcb8fe02c583a308d5a89c56
Merge tag 'android-4.4.3_r1' into HEAD

Android 4.4.3 release 1
audio: Add support for FLAC in compress offload path

- Add new audio format for FLAC
- Add FLAC in valid formats list
- Add bitWidth in offload info

Change-Id: Ic716aff8b7cdb28b03f32f686eca33ff0beb981c
Revert "charger: Draw battery percentage over charger screen"

This reverts commit f7e1ef2461121c1ebe7f1ef3ea25cca397e4c5ab.

Rationale:
The tiny (blue) number drawn on top of the otherwise black-and-white
battery symbol looks pretty out of place and gives the perception of
being a debugging leftover that just was forgotten to be removed.
Additionally it's very unlikely the user is interested in the exact
value of battery charge in offmode charging. It's much more likely he's
interested in rough state information only ('is my battery fully charged
now?').

Change-Id: I2b4f881faa4a254d03e07d5d46b6870a2fe9ec4a