derp

Change-Id: Ieab55a5f40138d313b704623652ccba93487b371
Add network usage stats to status bar: Re-implement for 4.4 [1/2]

Conflicts:

	packages/SystemUI/res/layout/status_bar_center_clock.xml
	packages/SystemUI/res/values/vendor_dimens.xml
	packages/SystemUI/res/values/vendor_styles.xml

Change-Id: I7c64a81167d0fea1ccd0adc9ed41e38fc07a79b7
Frameworks: Port BatteryBar (1/2)

{x} Adds Battery bar with following features:
{x} location set
{x} color
{x} aligment
{x} thickness
{x} charging animation

Change-Id: I4fc0b51abb29ac0a9f0b86e4d0ad3519f697b0f6
Navigation Bar: Landscape Height [1/2]

Change-Id: I2ed212cc95edd9a72bc8dae540e9fcae2897cc99
Signed-off-by: Lokesh Chamane <lokesh.c703@gmail.com>
Frameworks: 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
(landscape 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: Ia823856b755a129ea1fcddc2e24cb043ac37d621
fb: notification transparency (1/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: Ia2c6761575dcf62adc5eae248125d4e0ad67be5e
Force Expanded Notifications [1/2]

Change-Id: I0c8d8315ea046809fe6864ca8a9f21da8cdf953a
[1/3] base: allow disabling non intrusive incall ui

Change-Id: Ibe9c65f1fe024a859d98d96fd86199607a1060de
[1/3] Base: Flip to Mute/Reject Call

Saving flip action value to settings container

Telephony: https://gerrit.omnirom.org/#/c/4670/
InCallUI: https://gerrit.omnirom.org/#/c/4669/

Change-Id: Ie72dda49d78b23b9bc7d8a886f6916f678c918d1
[1/2] base: allow disabling call end sound

Change-Id: I4e5942de5c61dab9ee59cbf3b6599af32edb1d47
Revert HeadsUp

Revert "HeadsUp: Fix dismiss on back key press."

This reverts commit d84e336fdcf5db5ab7116297732c316416845e3d.

Revert "SystemUI: Improve HeadsUp expanding performance."

This reverts commit 0d107ce038e322d251316c818f9a25f3ab24d934.

Revert "HeadsUp: Fix resetHeadsUpDecayTimer."

This reverts commit 802d3e7d2a6c0d7c29fa4f4a652615836bb6a3e5.

Revert "HeadsUp: Add heads up blacklist options. (1/2)"

This reverts commit cb85a9086a32906d4b65f19a7609870ce0d9836e.

Revert "HeadsUp: Clean up."

This reverts commit 6551a47c998c6892260dc45e9db7f1c66832cd33.

Change-Id: Ia93332125d670fd95172021f1b89a3f1c3e8d2e9

Revert "HeadsUp: Only remove heads up if attached to window"

This reverts commit 6a7eb48b34ef03d7eafa88921a51b2c364b1baee.

Revert "HeadsUp: Respect system decorations when adding view."

This reverts commit 9c16fe048747cf7e1249458a5bc1c8265024f015.

Revert "SystemUI: Expose heads up."

This reverts commit 6c65b35e061409b15ccccacf86d58dadbf655e26.

Change-Id: I0b624af16a081fc792b36ab0be9ad565de0005d7
Frameworks: Heads up meets SlimKat....SlimKat meets Google IO [1/4]

First introduced from apple, showed as android version on PA as hover and now found
in android code as native implementation we want to do our interpretation of this feature.
Especially thanks PA and CM for some of the UX ideas.

We have basically split this feature in two parts.

1. Googles native integration. We keep it as is and use the native flags for it. Apps
   (in our case Dialer, Mms, Email per account) can force show a heads up notification
   if the notification is important. So basically same what was shown on Google IO the first
   time to the public. Eg the dialer on SlimKat is doing exactly the same now like google want it.
   Due that we use same flags like google every future app with heads up support will automatically
   show as heads up.

2. Give the user an ability to enable heads up mode for third party apps which do not have a native
   integration. Well first thought was on which apps a user would usally use it (keeping in minde the idea from google....heads up
   is for important notifications and for nothing more)? Right on chat, email
   or social apps. On all other apps it simply does not make sense at all. Which leads into the question why the
   current integrations are handling blacklists or whitelists and enable it per default for all apps. This
   is from UX point of view an absolutely no go (just imagine the user blacklists half of the 200 apps installed lol).
   Aside that parsing long lists is a peformance problem.

   So our attempt goes into another direction. Headsup for (native integration is another story) apps is disabled
   by default. We bind the information directly to the application package. So each app carries the information itself.
   The user can either enable it with a longlick in the notification drawer on the notification or in Settings->app->App info
   as well via a check box. As soon it is enabled for this app every notification from this app will show as heads up as long
   it is not an ongoing notification.

   In general on system signed apps the user is not allowed to change the heads up state. Thats nothing the user should
   decide....the system should do. Aside that it prevends user to enable heads up for eg IME selector etc etc.

Thats the basic concept behind. In addition to this concept following things were done.

- Introduce a new expanded notification flag. Apps can send it via extra metadata to force
  a expanded heads up notification is it is needed (eg dialer).
- Add a user option to enable always expanded on heads up notification
- Add a user option to set the timeout for the heads up view.
- Introduce a snooze button. Every heads up notification has a snooze button on the top right. If the user press it
  heads up is disabled for a certain time (like a do not disturb mode). The time length is user configurable in settings.
- We had a bunch of user which want to use heads up in a more intrusive way. Current default behaviour is that a heads up
  shows up if the user did not push the heads up of this app into background. This is due that the system assumes if the user
  put it into background he or she do not want to be disturbed by notifications of this app at the moment. Of course in the moment
  the user interacted with the background notification heads up is activated again. This leads like google suggested in a very
  good non intrusive way. Well but some user use it in another way (especially on immversive mode) and want to be notified on every
  notification update of this app via heads up. Due of this understandable other user behaviour we add an option for it to allow
  this scenario.
- Detect direction of the swipe. Left swipe will dismiss the notification (if it is not a non clearable). Right swipe will just
  hide the heads up and the notification is still in background accessable in the notification drawer.

Other then that some fixes were done as well (eg utilize the back button, correctly handle the hiding of the heads up,
handle action buttons on heads up view correctly, fix several expanded desktop and immersive issues
and some other issues the AOSP implementation currently has)

To summarize...heads up this way is very non intrusive and especially we do not need a bunch of settings or blacklists.
So it is pretty straight forward, fast, clean and user friendly.

Some visual examples:

https://plus.google.com/107859134357373490612/posts/bJABHs1aNMj

Change-Id: I81a7473ca48eb5fd91263ec63c82957d8b3ad17b
Slim Heads up: change behaviour of back key

Currently back key hides the heads up. We change it that the back key is still
working for the app which has focus and not for the heads up at all.

Reasons:

1. A lot user requested this due that they often hide the heads up during they work
   on the phone, simply due that the back button is often pressed on a normal workflow.
   The results is indeed that a lot heads up windows are missed excidentaly.

2. First I thought to make it optional. But there is another big reason to do it this way. Current
   behaviour is that the heads up view gets focus...and that we dispatch the back key only. Thing is
   that other key events are still rooted to the heads up window. Well most things a user will not see.
   But eg on apps with input field some keys on the IME keyboard do not work during the heads up is showing
   which is a big no go when we assume that heads up needs to be as much non intrusive as possible.

That being said we remove the dispatch override and give the heads up window FLAG_NOT_FOCUSABLE flag
which will bypass any key events to the window behind which had focus before the heads up showed up.

FLAG_NOT_TOUCH_MODAL we can remove due that FLAG_NOT_FOCUSABLE automatically enables the FLAG_NOT_TOUCH_MODAL flag.

Change-Id: Ied4c7d2dd5b99f89af958f01db980a36d431bbc3
HeadsUp: Only remove heads up if attached to window

Attempting to remove mHeadsUpNoficiationView from the window manager
when it is not currently attached will throw an IllegalArgumentException
so we check if it is attached and if so remove it, otherwise carry on.

As well remove possible left children in statusbarview

Change-Id: Ida916eba496c4183e47288ef24a8a93c46a7eddf
HeadsUp: Correctly add and remove the window

isAttachedToWindow() basically works to determine if the view was attached or not.

But on the boot up process when already addHeadsUpView is called but the system is not
fully up and a recreation happens (eg on TRDS...due that the UIModeManager is doing its work as soon as system is ready)
the view gets attached....but not removed on the recreation due that at this time isAttachedToWindow() will return false even though the
window was added.

To solve simply use a boolean instead of isAttachedToWindow()

Change-Id: Ib576a83cadc581683f2a5b0afc922c53b01888b7
fb: Show heads up at the bottom of the screen (1/2)

Due of user requests and indeed especially on hw key devices for a better
workflow we add an option to show heads up notifications on the bottom instead
of the top.

Animation we leave as is due that if it slide from the bottom into the screen it happens
to often that the user accidentaly interacts with it. If it comes from the top of the
container we add, the user has enough time to realize it. Sometimes a ms can make a big difference.

As well this commit fixes the wrong gap on the top if user boots up directly
into immersive mode.

PS:
- if IME keyboard is showing show the heads up on the top to do not disturb the typing.
PS:
- NPE if updatePosition is called to early from the system.

Change-Id: I5ec2ab97f3309e9e690bc60c9f5cfd19d4dab516
Floating Window: Welcome back

* Port squashed jellybean floating window to kitkat.

Floating window contributors:
@drcmda
@beerbong
@D4rKn3sSyS

Signed-off-by: Carlo Savignano <stevewatersy@gmail.com>

Merge notification manager service changes.

Signed-off-by: Carlo Savignano <stevewatersy@gmail.com>

Change-Id: If3d6338f657915754bd6cb9cb987df62c17aa6d0
Kill floating activities running in the same thread when tapping outside

This change makes all activities from the same app to be finished when we tap outside the halo window. Other apps running in different threads
(floating or not) won't be finished.

Port from here: https://github.com/ParanoidAndroid/android_frameworks_base/commit/f489f45ab2ba5dd4991c241917f7f4b0fd74b884

Change-Id: Ie6d6f46b2e23be60f991520ed480c2866fb2d0e3
Hide netstats on light out (this was annoying as fuck)

Change-Id: I8cd74411e72012f7a8f7a8d7fa6dc85e4313e693
Don't show Netstats when there's no traffic

Change-Id: Ie90caabd52dcfb6889cf26da37d7c57974993ffb