will be used later
[2/2] Add network stats to statusbar

Change-Id: I81b59fb7e19dc14b97c53d69291e54a479137bc5
Signed-off-by: kecinzer <kecinzer@gmail.com>

Conflicts:

	res/values/arrays.xml
	res/values/slim_strings.xml
	res/xml/profile_config.xml
	src/com/android/settings/slim/StatusBar.java

Conflicts:
	res/values/spirit_arrays.xml
	res/values/spirit_strings.xml
	src/com/android/settings/cyanogenmod/StatusBar.java
navbar experiment

Finish experiment

Conflicts:
	res/values/cm_arrays.xml
	res/values/cm_dimens.xml

navbar switch fixup
Settings: SlimPie (2/2)

Well first I want to thanks again for the ideas Jens Doll, Kyrylo Mikos and PA gave us
on 4.3 allready to make our own SlimPie possible. We used partly code from them and added
and changed it in our Slim way to have it for us most usefull.

Well as known SlimPie advantage to other PIEs is that it can bind on every button
press and longpress action like the user want. All SlimActions are available for
every button (so all possible shortcuts we have + apps etc). Of course as well
available are custom icon images or system icons. Other unique thing of SlimPie
is that 2 rows are available. First row user can setup up to 5 buttons. On the second
row up to 7 Buttons.
Of course the user can setup the style to their like and still theme engine related
things are respected.
Pie is activated present on non expanded Desktop as well

For 4.4 we reworked a lot of the frameworks base code mainly. Changes compared to 4.3

- We use now a edge detection service (thanks a ton to Jens and Kyrylo). We tweaked it only
  very minor due that it works allready out of the box. Two reasons why we want to use it.

  1. We do not have detection overlays on the borders anymore. Means the user is not disturbed
     by it and we do not need to add workarounds like we did before to avoid accidental swipe ups
     (eg old IME reduce triggers). As well it is not needed anymore that the user can setup
     thikness etc. The default values are allready quiet good. If a device has detection problems
     the dm can adjust them via overlay. As said main main main advantage  that no dead zones are present
     anymore.

  2. we will use this service for other upcomming features as well (eg new Recents)

- Centralized and adapted the code to 4.4 and some changes we did in our central classes
- reduced observer to an absolutly minimum. If PIE is disabled it does not observe any value
- A lot small fixes and tweaks
- Change default colors to KK style
- If navbar is present the navbar gets animated with the background to give a full screen overlay
  feeling to the user. Especially now with kk transparency way better.
- Full keyguard support
- complete reworked edge disable detection
- and a lot more

PS:
- better disable message for second layer
PS:
- fix wrong initialize from pie control settings
PS
- changed to Jubas suggestions

Change-Id: Ia861e06758a6dadcb5a6b52689e574308b2dcc02

Conflicts:
	res/values/cm_arrays.xml
	res/values/cm_strings.xml

Conflicts:
	res/values/cm_arrays.xml
	res/values/cm_strings.xml
Settings: notification drawer background (1/2)

    so after keyguard is mostly done let us start notification drawer
    and QS. First one custom background.....either color or picture
    with custom alpha and ability to set a landscape picture seperatly
     if the user want. (lanscape phone only)

    Compared to the 4.3 included version completly recoded and better
    integrated. No idea what I thought 1 year ago on the old implementation

    cheeers

Change-Id: I23f4502e3d9e97f52245bbf3b41900939bb5c4ce

Conflicts:

	res/values/slim_arrays.xml
	res/values/slim_strings.xml
	res/xml/notification_drawer_settings.xml

Conflicts:
	AndroidManifest.xml
	res/values/spirit_arrays.xml
	res/values/spirit_strings.xml
settings: notification transparency (2/2)

this add back notification transparency...compared to 4.3
it controlls as well the notification icon backgound transparency
which felt in the past dissplaced. As well codecleanup of the old
implementation.

largeIcon support I did not add due that google does not support it
as well at current status...it is only a placeholder in
NotificationData

Change-Id: Iacefd9d02919990517823e5d800c6e018c3c68a1

Conflicts:

	res/values/slim_strings.xml

Conflicts:
	res/values/spirit_strings.xml