Framework: Custom Tiles (1/2)

PS1: Reinvent logic from initial
	implementation
PS3: Clean-up and unlock/collapse
	options.
PS4: Small fix.
PS5: Remove unlock option.
	Too complex for average usage.
PS6: Allow reset button to reset last
	drawable/label.
PS11: Fix "user deleted index while
	above index 0" which would
        display the old drawable
	until the tile was manually
	updated by user.  Small fix.
PSX: Create Dependancy

Change-Id: Ifdfa60b8257290c07e1861903e26c5dea715d036
QS: no need to rebuild the complete QS on orientationchange

to update just the layout parameter from the container view
is more then enough

As well after theme change we can directly return due that
all gets rebuilded

Change-Id: I93662d611bb79c9bb294707fb2b4e204c060ce0c
SystemUI: Always show translucent decor on recents panel

Change-Id: Id3e371f841b065ba6ac7693d96b38504354b4fd9
fb: make QS again rtl aware

we removed on first version the possibility to respect rtl
add it back to be aware.

As well remove the try to fix the tablet on first boot landscape problem
It actually did not fix the problem.

Change-Id: Id71e1d4865bb84831a58813a9efdf47a2f96a1f8
QS: fix wrong measurement on 4 or 5 tiles per row on settingspanelview

Issue was only visible on devices which have settingspanelview (tablets - not flippable)
on boot up on landscape and had 4 or 5 tiles per row set. Problem is that due we have
the same layout situation like in portrait on this devices that the layoutparameter
height needs to be calculated in landscape as well.

Solve it with forcing (on only settingspanelview devices) the calculation on landscape
as well

Change-Id: Ib87485e0892abe798006ba5ffaaf5061d560afd6
Fix fatal exception due to missing looper for current thread.

While creating handler for the thread, there was fatal exception getting
thrown because the present thread does not have a looper. So passing the
applications looper to be used , while creating the handler to avoid this
exception.

Change-Id: Id2e3ed61f5691c8319eb7bc20ad970eb6758e765
(cherry picked from commit f5d1769b4357fb8d86fc31f7115b55b567a20ed1)
(cherry picked from commit d0a7c5833b90fe4d8fe8f968b53a7028720ffd8c)
Cursor leakage due to cancellation signal

If a query call was cancelled, the cursor adaptor might leak. The
adaptor is now closed if any exception is thrown during query.

Change-Id: Ic4c2edeaf2fcef56b4ef59484a36d3233aa12dbc
Fix visibility of multiple non-fullscreen activities.

Issue detail:
Assume X, Y are non-fullscreen activities.
 a.Home starts an activity X in task A in application stack.
 b.X starts an activity Y in <task A> or <new task B>
 c.Activity X will be invisible.

How to fix:
Because the function "isActivityOverHome" means an activity is able to see home.
But there may have many non-fullscreen activities between the top non-fullscreen activity and home.
If flag "behindFullscreen" is set, those middle activities will be invisible.
So it should only take care from who is adjacent to home.
Then check two flags frontOfTask(task root) and mOnTopOfHome for constraining the condition.

Change-Id: I60bcea304976414e44835a0a38675aae365e9e19
Fix a JNI local reference leak in MediaDrm

A reference leak was found in the subtitle usecase that also
applies to android_media_MediaDrm.cpp
(Code taken from the similar fix in android_media_MediaPlayer.cpp)

Change-Id: Icc4b25e4adc9a600ff4ac99a7a8478bb55a6e348