vendor services (to arrays.xml)

Conflicts:

	core/res/res/values/arrays.xml
	services/java/com/android/server/SystemServer.java
Add vendor_service resource to public.xml
hwui: Allow to blacklist android applications

Add support for a local config folder with blacklisted process names
/data/local/hwui.deny/<package name>

Only enabled with "hwui.use.blacklist=true"

This system can be used easily from adb shell, without reboot
or with a setting app, like the one i use, HwaSettings

Change-Id: I436b5dd7d6bf9fd36be7e86fc9d2a174a66701ff
re-implement of ro.usb.use_custom_service (notification mass storage)
1% battery

Change-Id: Ib2074c1d709cd386d53b56d4bb4fb1d937cb31ba
Some devices need light sensor enabled for kb and button backlight

Change-Id: Ic883779856cb19fb20c46a6896dbbf03855b4b0d
enable bandwidth control: ignore the iptables errors
Add LegacyUsbDeviceManager::setCurrentFunction method. (from ics, adapted to jb)
Debug: fix reversed brightness for buttons and keyboard

Change-Id: I64f751496e1ceb344368f28c6c5e1fc635a554d9
Force the screen-on after phone calls, ignore proximity sensor

Proximity workaround for device specific settings, this is required
on phone with a case hiding the proximity sensor, or buggy sensors.

Change-Id: I5b6174d5f19ef601dd503b4dadafb3defbf2bb00
disable debug of light sensor
PowerManagerService: fix getAutoBrightnessValue for btn/kbd

getAutoBrightnessValue calculations are correct only for LCD
backlight brightness values increasing with higher light values.
Skip the calculation for the reversed button/keyboard backlight
arrays, where the backlight brightness decreases with increasing
light values.

Change-Id: Ib72b8325fe2b0f83780e91dc94eea2e38061224b
allow define mtp device
Make button brightness override actually work. (from gb by maniac103)
Add support for USB tethering interfaces that are always present.

Previously, the state machine assumed that the USB tethering interfaces
appear/disappear when reconfiguring USB or changing the USB status. Add
some fallback handling for devices where this isn't the case.
Keep track of tetherable USB interfaces in both up and down link states.

USB network interfaces that are present-since-boot are never issued "added"
(or "removed", for that matter) notifications from netd, and thus, are only
discovered by Tethering when their link state changes.  Prior to this
commit, such interfaces were only tracked on change to "up" link state,
even though the interfaces were _not_ removed on changes to "down" state.

On some devices (e.g., epicmtd) a change to "up" state only occurs after
(i) IFF_UP is set on the interface, (ii) the rndis USB gadget function is
enabled, and (iii) a USB cable is connected to another machine.  Since
rndis is enabled immediately before the start of USB tethering, the "up"
state is achieved asynchronously, and often _after_ Tethering looks for a
tetherable interface.  However, "down" state is synchronously reported when
IFF_UP is set, and thus, serves as an effective mechanism to notify
Tethering about the existence of the interface.
fix interface name for stop wifi tethering
Disable report bad bounds
hack to get data connection up again (thanks to XDA User: SlugZero)
add STREAM_FM