[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: I76e558ce840ea45eec14194f2e9107fb83cebf8f
Signed-off-by: Hashcode <hashcode0f@gmail.com>
implement 1% battery on select devices

via ro.product.use_charge_counter=1
Change-Id: Iaed07e682463a6467b1903ab40cf41440334b64b

Conflicts:

	services/jni/com_android_server_BatteryService.cpp
Merge "[2/3] mediaeditor: Allow custom DOMX source instead of Google DOMX default" into jb-mr1
Merge "implement 1% battery on select devices" into jb-mr1
Merge branch 'jb-mr1' of git://github.com/AOKP/frameworks_base into AOKP

Conflicts:
	services/jni/com_android_server_BatteryService.cpp