BoardConfig: remove fstab version
libaudio: complete overhaul for mr2

Change-Id: I5fbec0a6b052512d2c74c6a195aefd78f2c0267b

Conflicts:
	audio/AudioPolicyManager.cpp
	audio/AudioPolicyManager.h
BoardConfig: enable qcom av enhancements
BoardConfig: make display-legacy do what I want it to do

wow I can't believe this has been broken for so long
media_codecs: update for mr2
Revert "Recovery Touch: Update recovery key layout"

This reverts commit 5f2e724b0b31a0782331d848b4d88e93c77167ef.
recovery: remove custom graphics and update init.rc
hardware tunables: vibrator support
BoardConfig: add TLS register

This isn't in CM's android_build and androidarmv6's GL ES needs it or rip boot
BoardConfig: remove ancient flag
BoardConfig: enable lowmem
Revert "system.prop: update max background apps key"

We're back to this one again.

This reverts commit 6c723791ccc25049c049539e9cd169d009617016.
BoardConfig: use cortex-a5 cpu variant
init.rc: merge recent updates

Ignoring https://github.com/CyanogenMod/android_bootable_recovery/commit/ad054c684524962eae3269c1d807dc60e8bca1ec because it breaks adb completely.
setbtmac: get the bdaddr from the radio instead of cheating

Cheating worked unless you were on the Gingerbread bootloader, as
the serialno was not set to the bdaddr but some other weird string.

This is pretty much the same method that brcm_patchram_plus uses, without
all of the fancy structs and enums... and error checking, but it's hard to do
that without having the code for this stuff, and probably not really necessary
anyway. :D

Also clean up setwifimac
Make internal SD (emmc) the primary storage

Necessary to fix the CMUpdater/recovery disaster post 4.3 without hacking
away at recovery code as everything assumes this kind of setup.
It's also "mandatory for CM10", so maybe we're a little late here. :D

When (if) the vold switchable pair stuff gets merged this shouldn't be much of
a problem, but I'm sure there are going to be "vocal" users following this change. :(