Solve three memory leaks related to PatchCache

A Patch can be fairly large, holding bitmap data, but
is also frequently leaked which adds to the severity.
The feature is used in many important processes such
as Home, SystemUI and Chrome.

The following leaks are solved:

1. The Patch itself was not always freed.
PatchCache::removeDeferred() can mark patches to be
cared for by PatchCache::clearGarbage(). But
mCache.remove() would only destroy the container
and the pointer, not the Patch object itself.

2. The vertices stored in the Patch at Patch::createMesh()
would always leak. The empty/default destructor in Patch
would not properly destroy "vertices" since it's just a
pointer.

3. A BufferBlock that's added to the mFreeBlocks
in PatchCache could leak. The leak happened when a
patch later needed the entire free block, because the
object was removed from the list but never deleted
in PatchCache::setupMesh().

Change-Id: I41e60824479230b67426fc546d3dbff294c8891f
frameworks/base: cleaning translations for es and hu languages

Change-Id: Idbf779cac4bc9444febadb1ca4e9ecff178396fa

Conflicts:
	packages/SystemUI/res/values-es/slim_strings.xml
	packages/SystemUI/res/values-hu/slim_strings.xml
frameworks/base: added missing line

Change-Id: I614ede7f178ab49d74d26349054d36a88cbd713d

Conflicts:
	packages/SystemUI/res/values-ru/slim_strings.xml
SystemUI: Add DE-Translation

Change-Id: Ie7a1bcad90ee127376d9f8c64cada736e332743d
Frameworks: Notification Reminders (1/2)

Click notification header to set a reminder
Long-click to dismiss current

Change-Id: I68d6eab8893419e8ec192d45f1e6b42ddff3e62b

Conflicts:
	core/java/android/provider/Settings.java
	packages/SystemUI/res/layout/status_bar_expanded_header.xml
	packages/SystemUI/res/values/slim_strings.xml
	packages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java
Fix Build