Since the locksettings database is not backed by a provider, we cannot
use a ContentObserver to know when a change to the third party keyguard
component has occurred. Instead we broadcast that it has changed.
Change-Id: I1384b8ba445dcb8d0c571ded1c68b297182f086a
TICKET: CYNGNOS-1481
For CM13, the third party keyguard permission is being added to
the cmsdk rather than frameworks/base. This patch also introduces
CmLockPatternUtils, a subclass of LockPatternUtils, which allows us
to make use of the new third party keyguard permissions in cmsdk.
Change-Id: I91fadfaae79e3f146e9ae73929cea91294ef8d87
Create a simple CustomTile object with builder which lets a 3rd party
application publish a quick settings tile to the status bar panel.
An example CustomTile build:
CustomTile customTile = new CustomTile.Builder(mContext)
.setLabel("custom label")
.setContentDescription("custom description")
.setOnClickIntent(pendingIntent)
.setOnClickUri(Uri.parse("custom uri"))
.setIcon(R.drawable.ic_launcher)
.build();
Which can be published to the status bar panel via CMStatusBarManager#publishTile.
The CustomTile contains a click intent and click uri which can be
sent or broadcasted when the CustomQSTile's handleClick is fired.
This implementation closely mirrors that of NotificationManager#notify for
notifications. In that each CMStatusBarManager#publishTile can have an appended
id which can be kept by the 3rd party application to either update the tile with,
or to remove the tile via CMStatusBarManager#removeTile.
Change-Id: I4b8a50e4e53ef2ececc9c7fc9c8d0ec6acfd0c0e
