SystemUI: unregister ContentObserver

We were leaking memory.

PS2: move instanciating to the SearchPanelView constructor
PS3: more possible memory leaks

Change-Id: Ie9ddf00c698692f418cb8ef473dff2b1aa05135d
Signed-off-by: Dirk Rettschlag <dirk.rettschlag@gmail.com>

Conflicts:
	packages/SystemUI/src/com/android/systemui/SearchPanelView.java
	packages/SystemUI/src/com/android/systemui/statusbar/GestureCatcherView.java
	packages/SystemUI/src/com/android/systemui/statusbar/NavigationBarView.java
SystemUI: fix memory leaks

ContentObservers are being registered without being unregistered,
causing old objects not to be garbage collected. This causes memory
leak if the classes are destroyed and recreated throughout the
device's uptime.

SearchPanelView is recreated every time the screen is turned on.
StatusBarIconView is created every time a notification is triggered.

JIRA: CYAN-650
Change-Id: Iabd3221fc2b0c848396af1790fd09424be602e7e

Conflicts:
	packages/SystemUI/src/com/android/systemui/SearchPanelView.java
	packages/SystemUI/src/com/android/systemui/statusbar/StatusBarIconView.java

Conflicts:
	packages/SystemUI/src/com/android/systemui/SearchPanelView.java
SystemUI: partial revert of 3f72751c, we already had the fix in SearchPanelView

Signed-off-by: Gergely Szell (sethyx) <szell@hu.ibm.com>

Change-Id: I05d9b000638c9ea0083a8a95cb199811a89164b4
SystemUI: RAM bar view optimizations

findViewById() was being called every time updateSettings()
was being called. Instead, let's instantiate them once, and
remove calls to updateSettings() since it will be called
on its own when the setting values change.

Change-Id: Iaa02343caccb615921219be2a56b3bac4f3263b9
Signed-off-by: Roman Birg <romanbirg@gmail.com>
Fix PowerMenu Navigation Bar Layout

Change-Id: I4741efceb01da7830bcd7457b274b051c5e2b197
SystemUI: fix recents minimization animation

Splitting up the buttons into each class is cute,
but it only seemed to complicate its interactions.
The instantiation was wrong before anyways and
onTouchListener was never being registered
(which is why the animation was wonky).

Change-Id: I4194569aaf0099754852d5cfb83f308f3271008b
Signed-off-by: Roman Birg <romanbirg@gmail.com>
Fix NavBar & SystemBar sizing issues

PhoneWindowManager makes some decisions regarding
portrait & landscape based on screen sizes.  Since we poke
this routine everytime we change something on the NavBar, this
can result in PWN changing the orientation of the device.  This
was causing strange behavior in resizing of the NavBar & SystemBar.
It might also have been causing other strange orientation issues.

PS2:  Attempts to decode the actual device type based on the screen
   dimensions and the rotation at time of setInitialDisplaySize.
   This is needed because large tablets (that default to a landscape
   orientation, need to have the dimensions swapped)

PS3: Whitespace

ps 4: Restore the stock calculations for orientation, but restrict
    them to running only one time (at initial boot).  This will allow
    the normal detection routines to set up the proper rotation variables,
    but will not reset (and change them incorrectly) everytime we poke
   setInitialDisplaySize.

Signed-off-by: Zaphod <mwilson@acesappraisal.com>
Change-Id: Iaec0e8ba623f10bd0d4118b4d5a99a42ab0564f6
Dynamic glowScale adjustment and spacing of NavBar.

This adjust the Glowscale for the NavBar buttons based on
the number of buttons on the bar.  I also added spacer
views to the outer edges of the NavBar.  This helps alleviate
conditions where the glow was cut off on outer buttons (especially
in tablet UI).  It also makes the Glow more appropriately sized
as the number of buttons increase.

There are still some cases where an excess number of buttons,
and a small navbar percentage (TabUI) is going to create some
glow cut-off conditions.  That's just going to be unavoidable when
the user tries to squeeze it down that small.

ps 2: Adding the spacers now only occurs on TabUI.  This prevents
    major changes to the look/layout of buttons on Phone/Phablet,
    but still provides glow cutoff release for tablets, as they
    were the worst effected.

Change-Id: Ic6d9deb4ae49c87251b8b258ff0f42da46910986
Signed-off-by: Zaphod <mwilson@acesappraisal.com>

Conflicts:
	packages/SystemUI/src/com/android/systemui/statusbar/NavigationBarView.java
	packages/SystemUI/src/com/android/systemui/statusbar/policy/KeyButtonView.java
fix screen skip

Change-Id: I1a01cf1353a6a2f41712ab0ff07fbb6f581249c3

Conflicts:
	packages/SystemUI/src/com/android/systemui/recent/RecentsPanelView.java
Correct executable bit for source files [Take 2]

Change Ieb51bafb46c895a21d2e83696f5a901ba752b2c5 left out some
files, this fixes them.

Change-Id: Ia949a8581668836ea0251602e048f09c852f5169
Action before broadcast

Change-Id: Ie79b730935217031929fcb0067c20e11c88efe70
SystemUI: StayAwake Toggle

* Icon is in the works (Interim icon is AOKP cog)

Instead of overcomplicating toggle, onLongClick simply takes the user to
Settings$DisplaySettingsActivity instead. onClick (on) sets screen timeout to
int MAX_VALUE(approx 24 days), and restores user value onClick (off).

Change-Id: Ifd2051b2a6e8235160713cad3b4385dbb6d66b8f
Signed-off-by: bmc08gt <bmc08gt.teamb00sted@gmail.com>

Conflicts:
	packages/SystemUI/res/values/strings.xml