fix floating window derp
just not as default

This reverts commit 722e054b8123373dc03a17db76aebf0e35c34991.
Frameworks: activate PIE on Lockscreen

completly activate it now if navbar is disabled, expanded desktop or
whatever. The bottom trigger can be used on Lockscreen
if the user want (left and right does not make sense due the wigets.
If navigationbar hints are disabled it show instead
the home button the tinny circle which opens search/gnow. Longpress
action is the same like the one which was bind to the homebutton

slight adjust of default values trigger height and overall size

as well colorize and set alpha  on navbar for the tinny keyguard circle
like the other navbar buttons to be consistent

Change-Id: Ia721d02ae44ef0f9886224414c2932f5c24c0de6
Framworks: clean up trigger code

+ small fix

how to reproduce the bug
activate hide trigger on ime.....open ime...pull down notification drawer
close it again.....pie trigger left and right do not change back again

Change-Id: Ibbc1ba8731046b7214f8019f77491c9d2da776b8
Framewors: do not call every time setupTriggers

if pie is disabled

Change-Id: Iecfe5a074aa11a2f773ba176a51a4ccad121f1de
Fix: lockscreen bottom trigger on expanded desktop mode

did not show up in expanded mode before. Only on navigation bar disabled
or 0 values

Change-Id: I8a7215438b7205575bfeea99778c6203da47d82f
another cleanup

why complicated when it is easy. I will stop for today lol
just a small code cleanup

cheers

Change-Id: I3a17555fcc613c1466578758446f62b8aba0561f
Frameworks: remove always transparency mode navbar/statusbar 2/2

problem is that the transparency on most app totally break due
that a lot apps do not draw behind navbar and statusbar. Nearly
all user never use always mode and just use it on launcher
and lockcreen. So let us remove it
as well a bit cleanup

Change-Id: Ia5ee97f99102aa2b3833a33eb93b5e428a80b867
Frameworks: simplify custom lockscreen background code

- remove observer for transparency and handle it better
- add multisuser handles
- smaller fixes and code cleanup
- simpfliy custom background handling and change to our needs (thanks Danish)

Change-Id: Idf0bbb7bf9e132a3a68d567e3863cce1b6d99742
Frameworks: use a layer drawable for the keyguard

in preperation to the new navbar and statusbar transparency
managment which will come it is more consistent on custom image
and color fill on lockcreen to use a layerdrawable to add the
shadow on top of the image to keep on transparency of the background
the shadow like it is suggested by google

Change-Id: I22df7652b8be42cab1c9d1f0a13797da40a75dd9
Frameworks: rework navbar and statusbar transparency/color handling (1/2)

All current implemented versions of nav and statusbar transparency
which are around are not really perfect and all have downsides. After I saw the
implementation from Romanb (thanks) I got an idea to solve especially
the problem on keyguard without forcing the user to set for keyguard
seperatly a transparency to have a good result. Main problem is that
aosp does not allow to overlay the navbar with a shadow.

This commit does:

- introduce central TransparencyManager (thanks Roman)
- introduce a layerDrawable with a ColorDrawable as overlay and underlay
  to get consistent results on keyguard to show the shadow
- introduce a overlay to animate the navbar shadow like the PIE background shadow
  when the user is not in expanded mode. So the user get the whole screen darken (or colored).
- get complete rid of backgroundalphadrawable class
- allow colorize of theme (theme engine) navbar/status bar background changes
  reset to default shows as usual the theme without manipulation
- expand the custom background area on lockscreen behind the statusbar
  (navbar AOSP does not allow)

- default wallpaper and full transparent mode is now completly consistent and nice
  looking on every possible setting.
- full color lockscreen reflects the color now behind the navbar
  to imitate same behaviour like the default wallpaper on lockscreen. As well
  now consistent and nice looking on every possible setting.
- lockscreen background image mode is the only one where a 100% consistent solution
  is not possible due that the image is always smaller on lockscreen (not expandable behind
  navbar) and I do not see a good way to put in the underlay a partly image in a nice way
  ...to avoid weird transparency draws the transparency on navbar
  is set to the chosen lockscreen background transparency as long the lockscreen transparency
  is smaller then the navbar/statusbar transparency. Todo: notify in settings the user about
  the behaviour change so that it is no surprise.
- add multiuser compatibility to serveral vars
- margin fix on lockscreen
- hide statusbar on lockscreen on expanded or autohide statusbar mode
- add option to unlink colorizing on apps
- optimizing and a memory leak fix
- cleanup

Change-Id: I22ccfc5d3fff58b266848b2e0983435094ba6847

Conflicts:

	packages/SystemUI/res/values/config.xml
	packages/SystemUI/src/com/android/systemui/statusbar/BaseStatusBar.java
	policy/src/com/android/internal/policy/impl/PhoneWindowManager.java
Frameworks: move complete keyevents into SlimActions

still to lazy to doe the HW key rebinding revamp but we need
this move as well for that and it is from codeview much cleaner

This commit does:
- move all key event actions into SlimActions
- get rid off ExtensableKeyViewButton class and handle all over
  the AOSP KeyViewButton class which is now reverted nearly to the aosp
  one with slight modifications for the key handling
- fix the double vibrations on home, back and recents
- fix double sound on menu action on PIE and navbar permanent menu buttons
  due that the click sound is played by PhoneWindow.java for ActionBar events
  we do not play our sound for this action
- cleanup a lot unused imports

Change-Id: I7f1862e0e43654837fce4f4085d1ab9aef0558df
Frameworks: add Accessibility events to navbar, pie and navring

for click and longpress actions

Change-Id: Iea536ec43cbad9f2c26e0ab52a89f7d2c700f149
Framewors: add expanded dektop to SlimActions (1/2)

which is then available for PIE, navbar and navring and later
for HW keys

Change-Id: I00ebf30c75aa1b2980c2e41ce1464ee5b63e6f83
Frameworks: seperate core strings, arrays and symbols.xml

into slim seperat files. Ppl will ask my why symbols....just
because it is easier for me when I search something. Always
a mess with our old symbols.xml

Change-Id: I76976ca496b6f097e24f47b428c0273b34ce47cf
Frameworks SytemUI: seperate strings and arrays.xml

Change-Id: I588917efea63d7efa00bd28ec37a1bd03246f037

Conflicts:

	packages/SystemUI/res/values/strings.xml
Frameworks: add power menu to SlimActions (1/2)

like the feature before we can see now how easy the util
class and the dlsv is for us to use....just 8 lines + drawables
and we have a new feature available on all navigations

Change-Id: I88b5d5ded06294824679b0850725f14240c2ef92
Frameworks: bring navring/pie/navbar vibrate/sound inline with AOSP

currently all 3 features are doing it a bit different. For navigation
AOSP has for normal click:

 short soft vibrate + click sound

for longpress

 no sound but more intensive vibrate

This commit does:
- seperate keyevents haptic and sound from the other actions and call them
- add vibrate and sound to navring
- navbar only vibrate when the action is performing
- do not use custom vibrate on keycodes
- bring all inline with AOSP like described above
- fix a possible NPE on lockcreen

not solveable (do not ask me...google is not always consistent especially
on keyevents) due the change will break other global behaviours:
- menu button always have a click sound even on longpress.
- powermenu always have a second vibrate due of GlobalManager

all other works inline like described

Change-Id: I90fae2393c5c654055014556b0772447313d28b4
Frameworks: add DeviceSupportUtils helper class

adapted partly from cm (thanks) + own modification for our needs.
Currently unused but there will follow a bunch of commits which will
use it next days

Change-Id: Ifc0c1353e1d65ead000d07e2eab2ed7d8eaa1894
Bluetooth: Add trust device feature.

Add set trust feature where the remote device is marked
as a trusted device for subsequent connection.

CRs-fixed: 523135

Change-Id: I9bde4d7dfe07d9d63b58a661ed2413f45501bd7b