blue-common: use custom RIL header

Change-Id: I6f0c154d737666079b821c68d644cd3a56c36e05
RIL: update SIM_IO struct

The libril-qc-qmi-1.so blob expects an additional int32 member
at the beginning of the struct.  It's for RIL_REQUEST_SIM_TRANSMIT_BASIC
and RIL_REQUEST_SIM_TRANSMIT_CHANNEL (not implemented in CM)

Change-Id: I3f346a054c53652db58a1eba93e9d5574157d2cd
Revert "RIL: update SIM_IO struct"

SEEK is supported.
This reverts commit 0871664f8b25cad80b3a8c9f3f746b9900cf7eb0.
Revert "blue-common: use custom RIL header"

SEEK is supported
This reverts commit a669a4e4f654880a53730afce2fb44af745f411a.
blue: remove twrp flags

* These aren't maintained / kept in sync with TWRP.

Change-Id: Ie6d70be03f51cff0495ada7c090f1b2f9f958dfb
move bootrec-device so that it is automatically copied

* And cleanup the makefile a little bit

Change-Id: I12bc2c8ce0e4c3b517abdc666960bb34113a422b
releasetools: use set_metadata instead of set_perm

Change-Id: I1eda9dd7c1b1497fde1ae57596329193901947a2
script: fix traditional sort

Change-Id: If71cb15853702b441c93880d34c214e419918c84
Inherit from msm8960-common

* msm8960-common then inherits from qcom-common.
* This doesn't change anything currently, just adds one more
  common tree in between - however, later on, we can start moving
  things to this new tree as needed, from both blue-common
  and qcom-common

Change-Id: Ib0a5bca4569501e8504ae18b04c98f59130fe4be
script: make osx devs happy

Change-Id: I1e4a6be6d9c9da589a147f87f0164de65df2fc5f
blue: remove twrp flags

* These aren't maintained / kept in sync with TWRP.

Change-Id: Ie6d70be03f51cff0495ada7c090f1b2f9f958dfb
move bootrec-device so that it is automatically copied

* And cleanup the makefile a little bit

Change-Id: I12bc2c8ce0e4c3b517abdc666960bb34113a422b
blue-common: disable some unimplemented overlays

...to fix build

Change-Id: Idbddf4e6c78af24fad4ccc35b89affac9d7fc5e1
blue-common: use qcom sepolicy

Change-Id: I9d6e798468e58763d00066cff289aed634c7d4dc
fstab: mount FOTAKernel partition to /recovery

Change-Id: Id6f6f1a53d178ab7ca48550da5c6f62f0fb1c7e0
blue-common: use specific sepolicy, based on qcom's

Change-Id: Ib4a925ca0c80262aefab352f0f302163df05ce0f
blue-common: remove NFC HCE permission

This will cause Nfc Service FC. Remove for now.

Change-Id: I4021fddd08eaedc6541cee1a0591116b6bc166d2
blue-common: remove voip device and QCOM-specific flag from audio_policy

The non-extistent flag AUDIO_DEVICE_OUT_COMMUNICATION will cause
AudioPolicyManager to ignore the "primary" device, leading to
broken audio system.
voip_tx has only one COMMUNICATION device defined, so I removed it
with voip_rx altogether.

Change-Id: Ie3470fff7a88bca77e79070d38988dd84f3aceca
remove NFC HCE permission

* This isn't currently supported in AOSP/CM12

Change-Id: I4021fddd08eaedc6541cee1a0591116b6bc166d2
blue-common: remove redunant QCOM flags, use minikin, include more fonts

Sorry to squash all into one..

Change-Id: I2be84b4dbf51680e1a16944926d945586b4b9bc6