[2/3] mediaeditor: Allow custom DOMX source instead of Google DOMX default

Part 2 of 3 patches: To allow omap4 devices to use custom "domx" source
via a new BoardConfig.mk item:
TI_CUSTOM_DOMX_PATH := device/<manufacturer>/<device-name>/domx

This setting provides for 3 changes during the build:
1. In hardware/ti/omap4xxx this settings stops standard Google domx
source from being built and changes the domx reference for tiutils.
2. In frameworks/base it changes the default openmax references for
frameworks/base/media/jni/mediaeditor/Android.mk to the new location
3. In frameworks/av changes the openmax references in 5 places, and adds
new includes in ACodec.cpp, CameraSource.cpp and OMXCodec.cpp

This commit is based on cherry-pick from omapzoom (with a more descriptive
BoardConfig setting name):
http://www.omapzoom.org/?p=platform/frameworks/base.git;a=commit;h=f7f929ff477955333bf7e7413a81a66d683d1f3f

Change-Id: I7ba8052a6144597bf961b78723186c58b7e12e48
Re-add BOARD_USE_LEGACY_TOUCHSCREEN flag for the devices that needs it

Change-Id: I24ed882348ec5463910b5e49f849af2deac240a3
Frameworks: QS performance profiles tile

Patchset 2: Fix not null comparation
Patchset 3: xxhdpi drawables
Patchset 4: Fix xxhdpi drawables (thx blunden)
            Rebased
Patchset 5: Add suggestions
            Sync on boot the system property with the setting
Patchset 6: Rebased

Conflicts:
	core/java/com/android/internal/util/cm/QSUtils.java
	core/res/res/values-cs/cm_strings.xml
	core/res/res/values-el/cm_strings.xml
	core/res/res/values-hu/cm_strings.xml
	core/res/res/values/cm_strings.xml
	core/res/res/values/config.xml
	core/res/res/values/symbols.xml
	packages/SystemUI/res/drawable-hdpi/ic_qs_perf_profile.png
	packages/SystemUI/res/drawable-hdpi/ic_qs_perf_profile_bal.png
	packages/SystemUI/res/drawable-hdpi/ic_qs_perf_profile_perf.png
	packages/SystemUI/res/drawable-hdpi/ic_qs_perf_profile_pwrsv.png
	packages/SystemUI/res/drawable-mdpi/ic_qs_perf_profile.png
	packages/SystemUI/res/drawable-mdpi/ic_qs_perf_profile_bal.png
	packages/SystemUI/res/drawable-mdpi/ic_qs_perf_profile_perf.png
	packages/SystemUI/res/drawable-mdpi/ic_qs_perf_profile_pwrsv.png
	packages/SystemUI/res/drawable-xhdpi/ic_qs_perf_profile.png
	packages/SystemUI/res/drawable-xhdpi/ic_qs_perf_profile_bal.png
	packages/SystemUI/res/drawable-xhdpi/ic_qs_perf_profile_perf.png
	packages/SystemUI/res/drawable-xhdpi/ic_qs_perf_profile_pwrsv.png
	packages/SystemUI/res/drawable-xxhdpi/ic_qs_perf_profile.png
	packages/SystemUI/res/drawable-xxhdpi/ic_qs_perf_profile_bal.png
	packages/SystemUI/res/drawable-xxhdpi/ic_qs_perf_profile_perf.png
	packages/SystemUI/res/drawable-xxhdpi/ic_qs_perf_profile_pwrsv.png
	packages/SystemUI/src/com/android/systemui/statusbar/phone/QuickSettingsController.java
	services/java/com/android/server/SystemServer.java

Change-Id: Ib32d3734b63f88a3473e0ab10d8edf30dae9ceb6
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
Turn off carrier provisioning by default

Whether or not to use carrier provisioning is a setting hidden to the
end user that is currently not set. Unfortunately, on some carriers that
may result in it being set to yes, or effectively set to yes, without
other accompanying changes that must occur, such as setting a tethering
apn and possibly having a carrier provisioning app, resulting in hitting
a paywall when a tethering plan exists, or, worse having nothing happen
at all when you try to tether since the data doesn't have an apn set.

Change-Id: I3b5b3cc86e3325302411f46e3fd5f7a7c1b9f57e