Fix potential deadlock between LockScreen and WindowManagerService

If LockScreen is enhanced using SurfaceView/GLSurfaceView,
deadlock problem between LockScreen and WindowManagerService
can occur because of IWindow.resized() callback.
And it must lead to watchdog and reset.

IWindow.resized() callback is one-way function so calling resized()
callback of a remote IWindow object is never blocked.
However, calling resized() callback of a local IWindow object
(LockScreen is running on the same system_server process)
is always blocked until resized() callback returns.
Because resized() callback of SurfaceView/GLSurfaceView can lead to
WindowManagerService.relayoutWindow() call, deadlock can occur
between relayoutWindow() and performLayoutAndPlaceSurfacesLockedInner().
(Both functions need locking mWindowMap)

So this patch simulate one-way call when calling resized() callback
of a local IWindow object.

Change-Id: I2a6a5c74ed22d8e6b7a3bea3424ff2879d227105
Signed-off-by: Sangkyu Lee <sk82.lee@lge.com>
Remove the fixed-length buffer in DdmHandleNativeHeap.getLeakInfo.

It was possible to overrun this buffer, and even if you did fill
the buffer in a single read and exit the loop, the "string" still
wouldn't be terminated.

Bug: 8468088
Change-Id: Ia19f4d26dfd79e7b63807a7ec9540b932163d246
Restore gesture navigation and larger thumbnails

Change-Id: I04919fa58935c86f9269481c408276e3fb828063

Conflicts:

	core/res/res/values-sw600dp/dimens.xml
	packages/SystemUI/res/values-sw600dp/dimens.xml
Small cleanup for gesture navigation

Change-Id: Ife0c0b32af6e2d6bdec2b3462a891019d2ca8417
Only use gestures on main panel

Change-Id: I8f1e4402f84ce06275ef77978e0496db5d920f34
Move window manager calculation to first touch

Change-Id: Ie413002262cabe8f119c356306fb32ecd0e68537