Fix ringer mode being unneededly changed by setting ringer mode volume
to 0.

When having set the ringer mode to silent on a device with vibrator and
calling setStreamVolume() for the ringer stream again (e.g. in one of
the volume control dialogs in the settings app), the ringer mode is set
to vibrate, although there's no reason to do so.

Fix that by remembering the last non-normal (that is, either silent or
vibrate) ringer mode and using that when setting the stream volume to 0.

Change-Id: I27f1c75a0fef52bd63ac20f4101042808ce2c458
JIRA: CYAN-1403
Check and fail early if requested wallpaper size exceeds maximum texture size.

This fixes an issue where OpenGL initialization succeeds but buffer allocation fails because the requested wallpaper size
is too large (or otherwise unsupported) by the graphics hardware. This fixes an issue where SystemUI crashes constantly
on the PandaBoard when connected to a full HD display. Tested only on PandaBoard, no access to alternative hardware.
Signed-off-by: Wim Vander Schelden <wim.vander.schelden@philips.com>

Change-Id: I8d2e1ae9fd9772977c4e365f23f2f58bbca3787c
core: zh-rTW translations

Change-Id: I8301d7b0a07954cd52eec54739d2aa366c539992
Lockscreen : Fix widgets disabled

Currently, when keyguard widgets are disabled via the DevicePolicyManager,
a default widget if specified via widget_default_package_name/widget_default_class_name
is added on the main screen, and if not successful the default status widget is added.

However in its current state, each cycle of the lockscreen alternates between the two widgets.
Reason is, the default app widget is constantly recycled on screen power cycles, and in such events,
when checkAppWidgetConsistency() fails to add the widget (since the id is no longer valid), it toggles
back to the default status widget, and resets the stored id. Next cycle a new id is allocated and it works
and so on ...

This patchset addresses this issue by not removing the default status widget if not necessary, hence
preserving its id and fixing the toggling issue.

Change-Id: I6b21d18346fed5accc72141097939c92ee9aaa3c
SystemUI: zh-rTW translations

Change-Id: I69ae49bb775aa0cbc8ae1b66fd022a88cd73dcac
Fix mobile data button in power widget.

Change-Id: Ide0417768350081250af24518b6831d70196ba73
JIRA:CYAN-1189
Fix dock battery tile display.

Change-Id: I624663149da1161c2cd4f4b20b388bd711d9883c
Merge "Fix dock battery tile display." into cm-10.1
Merge branch 'cm-10.1' into martincz
HALO: Don't bring home to the front if we're opening a floating activity

Change-Id: I73900ee7c62f621c36e7364d83ac3afc9039509f
AssetRedirectionService: Check for permissions before running dump()

Fix android.security.cts.ServicePermissionsTest failure

Change-Id: I9d629d19f3ff231db477d156c8bf557d4b8ee861
Merge "Fix ringer mode being unneededly changed by setting ringer mode volume to 0." into cm-10.1
Merge "Lockscreen : Fix widgets disabled" into cm-10.1
Merge "Check and fail early if requested wallpaper size exceeds maximum texture size." into cm-10.1
Cleanup.

Change-Id: I4ee830f146529269be98d4b899a97e8e867fdb01
Close notification panel when swiping away the last clearable
notification.

Change-Id: I4e5114f66e799a7c80e18b38abce5678da460846
Hide navigation ring if no targets are configured.

Change-Id: Ieca5c700f628e9c990483999367aa48d153fd6a5
Give floating flag to previous activities in the stack

When launching stacked activities, only the last one is flagged as floating in sysui when tapping halo.
This causes the system to show the launcher when the first stacked activity is launched (this first intent gets the flag FLAG_ACTIVITY_TASK_ON_HOME
in TaskStackBuilder).
This change makes all the stacked activities get the floating flag if the last one has it.

Change-Id: Ia3d2a06c92bd1410585fa8c46364915405bd568b
Signed-off-by: martincz <martincz@mokeetek.com>
Merge branch 'cm-10.1' into martincz
Merge "Cleanup." into cm-10.1