Revert "Frameworks: Add support for variable size pattern lockscreen (Part 1/2)"

This reverts commit 42b6edc0e5976920f4dedc6f10792538ac73a888.
Forward port CM Screen Security settings (1/2)

* Lockscreen Vibrate
* Slide Lock Delay
* Menu Unlock
* Home Unlock
* Toggle dots/error pattern visibility

Forward port from cm-10.2, adjusted for 4.4

Change-Id: Ie1ccaec43ca75474e92f96c60e15d7b75796ac5f

Conflicts:

	core/java/android/provider/Settings.java
	packages/Keyguard/src/com/android/keyguard/KeyguardHostView.java
Framework: Change stock Clock-Click Actions

Separate into two views and add:
	Date: View Today Calendar
	DateLong: New Event Today
	Clock: View Alarms
	ClockLong: New Alarm

PS2: Catch Missing Intent

Change-Id: I578df64691c0d957cc3923958abae9a0f9d02b88
systemUI: fix date and clock layout

in notification drawer after clickable actions change

Change-Id: I5979d5537e5fe3347fe7cd2bdf68786c63dc812d
Keyguard: let the user drag the challenge down if widgets are disabled

for the system clock widget this does not make much sense but due
that our system default is DashClock it makes a lot sense to
allow it to see more content of DashClock extensions

So allow it for overlay added app widgets if the binding was
sucessfull.

Change-Id: I0365573c6fa88117a47b01ced81eb36f75324342
Fix one and hide the other warnings from core/jni

Most of the warnings are unused parameter from skia functions.

Change-Id: I9df57718d117c26b96163f751ccb056ca86ac072
Don't try to set service.bootanim.exit

init has never allowed the bootanimation code to
set service.bootanim.exit, and has always generated the
dmesg error message

  <3>[   17.644615] init: sys_prop: permission denied uid:1003  name:service.bootanim.exit

Since setting this property has no effect and never worked, delete
the code which tries to do it.

Change-Id: Idacc5467d85479a8cf974702af8895011be585ea
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
Use java.util.Objects instead on internal API

Not needed since java.util.Objects implements all the needed
functionality.

Change-Id: Icd31d49a9801d1705427f028e9ac927d58e7d34c

Conflicts:

	services/java/com/android/server/am/ActivityStack.java
Clean up native AlarmManagerService tabs/spaces and unused parameter warnings

Change-Id: I64da1437dd0ed30957b43450c72b9d3797112a2e
Signed-off-by: Greg Hackmann <ghackmann@google.com>
Don't pseudolocalize untranslatable strings.

bug: https://code.google.com/p/android/issues/detail?id=63004
Change-Id: I8e47a53d887144dc867111e42313d0e113b83ea1
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
Keydispatching timeout while finish Activity

If there is input to be handled during finish activity we can get a
keydispatching timeout ANR. The reason is that finish activity is some
times not possible, and the activity is instead put on a finish queue.
The activity will then be finished sometime in the future. When we add
the activity to the finish queue, key dispatching is paused, and there
is an ANR timer waiting for it to be resumed again. Since it can take a
long time before the activity is actually finished, we need to resume
the key dispatching to avoid the ANR.

Change-Id: Icea4ab3b5ad05c8bfbadf8f5cece1a59ec621469
Keyguard: disable menu unlock
Frameworks: Slims ElectronBeam get some love (1/2)

Features:
- You can select different crt off animation modes if device overlay does not disable it at all
- disabled
- always horizontal (stock behaviour)
- always vertical (screen collapse from left and right to the middle)
- orientation dependent (means portrait = horizontal animation, landscape = vertical animation)
- some minor fixes/code style improvements to 4.3 implementation

Change-Id: I02543a242f8f570438f2ab97a19b6ffe1b4dba1c
fb: add scale down crt animation - thanks a ton to xploidwild

really nice idea...fits perfectly into our animation options
for CRT

Change-Id: I562ed272e7106482ef8d6b477a46eb5d81569dbb