systemui: turn off debugging

should be all of it

-VanirAOSP

Change-Id: Ia279a1be6968f67a4ad448cf51743f4c455af88a
Fix a fail from the backup transport fix

this file's name and this line init both lack any mention of backing things up...

Change-Id: I36ad254695d14e512e58c596228fe69a49c89dfd
Restore some fling parameters

one of the bugs I'm flailing on that are nagging at me is related to skippiness when flinging at high velocity

it's either related to constants in ViewConfiguration or(/and) animation stuff that could be handled more efficiently

MAXIMUM_FLING_VELOCITY:
stock     8000
ours was 15000

px = dp * (dpi / 160)
gsf = 430 dpi
15000 dp/s * (430 / 160) = 40312.5 px/s
on a 1080x1920 device, that's 21 screen-heights per second fling
I don't think we need to worry about flings being initiated with a 21 screen-height/second
so, returning MAXIMUM_FLING_VELOCITY to 8000 (stock val)

SCROLL_FRICTION:
stock    0.011
ours was 0.015
DADDY LIKES A SMOOTH RIDE, but this seems like it could lead to scroll inertia eventually
outrunning the scrolling cache. To prevent that, let's try the stock value.

Change-Id: I098399cf6f32661020d947eb27742bfda69161dd
Revert "Improve scrolling cache"

This reverts commit ea515cd5e01ff2a791171b44fa2ba19ff60414de.
Revert "frameworks/base: Fix for the race in Wallpaperservice"

debugging a ui deadlock... so this smells a bit funny.

This reverts commit 2166fd09e16e8bb9f82580e995b5dde533e6857e.
Make SkRect so skia doesn't need to know what an android::Rect is

Credit to David96 for the inspiration for the fix

Signed-off-by: nuclearmistake <nuclearmistake@gmail.com>
Change-Id: I3233728d8a0a44d085f20729b3c24f197d75741e

Conflicts:
	core/jni/Android.mk
Fix to NullPointerException on move back in ActivityStack.

In ActivityTask.moveTaskToBackLocked NullPointerException may occur
when moving back with only current Activity in stack. This due to a
condition that may trigger despite a TaskRecord being null and then
attempt accessing the TaskRecord.mOnTopOfHome variable.

TaskRecord task may be set to null when no resumed activity remain.

Resolved by assuring that flag mOnTopOfHome is instead set to false
for current TaskRecord in case where there are no remaining activities
above home.

The above bug has already been corrected in the following commit,
ada62fca51d314cefe2c5da4e007df5b9abf320d, but it does not set the
cottect value to mTopOfHome for the current taks, see below.

Variable mOnTopOfHome will not be set to false in situations where
stack is of size 1 or less and task is null, perhaps from already
having finished current activity.

To avoid current TaskRecord maintaining value mOnTopOfHome to true
after launching Home this variable is set to false.

Impact should not be major due to correction earlier that makes sure
that there is always a TaskRecord.mOnTopOfHome set to true above Home
activity but if not correctly set for current task still gives a
possibility of bad behavior.

Change-Id: Ie86ad99c188aaa05b0de9d58eaa16c42b6fc4341
Clean up native AlarmManagerService tabs/spaces and unused parameter warnings

Change-Id: I64da1437dd0ed30957b43450c72b9d3797112a2e
Signed-off-by: Greg Hackmann <ghackmann@google.com>
DO NOT MERGE - Fix improper declaration/use of pointer.

https://code.google.com/p/android/issues/detail?id=61547

This variable is shadowing the outer "ptr" declaration, resulting in a
potential NULL pointer being passed to the message API.

Change-Id: If96bfae8d5e874e12597182678a180ba137b78da
Port back LockScreen Music Control from 4.3 (1/2)