Clock updated launcher icon

See merge request !4

Change-Id: I9a3adcfde5951751b56254c652037354d6825197

Change-Id: I56614d12fa1415007f4929451cf3805677159943

Change-Id: If565c00a9f5b43cf6cd22564560a5d530f79c50f

Change-Id: Ica00b9aee3e7b87c55e30914e60a7c3c93e1eeb8

Change-Id: Iae6a35eaab3b8c3c346bdbe878510a5d7125a118

Change-Id: I568ce075e8f9594effebc8a6670a46f74cc3c67e

Change-Id: I0c22011049ef8c16f9d94ffba22a1a03ddd40b31

Change-Id: I6a1dd4b05a08131664f00f02351052403346ee21

BUGBASH-1720

Change-Id: I9ba3488a4138d4764d642dbc4dd71054c0163a62

 * Platform apps that depend on the SDK must only link
   against org.lineageos.platform.internal

Change-Id: Ibf63433f0961572d118361f984270f56accf8409

Change-Id: Idf58f3b46d58efb0a85bd588c99f0b11bd5c4485

Change-Id: I736a00f145b7e03265aee7bf2b998e973725790d

* This is apparently causing issues for many users,
  while using plain old notifications doesn't.
  Setting API to 27 is also not helping, so just
  roll back to what AOSP shipped.

This reverts commit 3d59c126.

Change-Id: I4b6914f7fd1a1afc13cc38241ae8e5677e6620ea

Update the alarm instance status when the power off alarm is handled
in min framework mode.

CRs-Fixed: 2113033
Change-Id: I5f10d80fa17c6d89fca990a5d3ccc90a41fa3d5f

Change-Id: I7e83d64ff6cc6e01f8a703edbaade681df834c17

Change-Id: I452f1d2b2e9dfe54d9de4df87b39634dc379758f

Change-Id: I54868f572453665a56797f8fb37171594e108e11

Java exception occurs when notification is posted by DeskClock
because Notification channel is not implemented.
To fix, Notification channel needs to implement and used
when notification is posted.

Change-Id: Ie4b2b46685fd150f5a0f7e6434ff487a56570107
Test: Manual and cts, passed always tried more than 100 times

Change-Id: I06a94c0cad96df772ed631bf1377eb5d5c8effa1

Change-Id: I488492c7dc57d22a4e4cd97c4abdb8c9b946ae4e

Change-Id: I673d1463bb9bd9e7cbad0ec36dd92012be018f39

Change-Id: Ib6c7c2ec1a8d988839e33293dc459f0523a0e51f

This reverts commit c86ad54e.

Change-Id: Ic4442eb2b0bf752fa850c51e3ebe81c2425331de

This reverts commit dcb41bc4.

Change-Id: Id0cbee9c0fbec3800f34dffbee1bf47f3637287e

This reverts commit c0552a2b.

Change-Id: I50305980aaeb6c888749aa45e591d53a830c57ca

This reverts commit b4d1b477.

Change-Id: I6dd1cf4e6a3b77c68d29d9855dc61415f39bc7c0

Change-Id: I1c0bd5ba0aead67cb0f6d9878792b4ebf0004893

I have two different devices, both of which are experiencing issues
with randomly missed alarms in N. I can see in the logs that the
device wakes up in time, and it's aware that it has to fire an
alarm. So it gives the order to fire, but the order never reaches the
firing squad.

Testing this revert, both by myself and users, shows that not a single
alarm is missed. It wakes up and fires the alarm as it should every
time.

Note: CAF hijacked some of the code that Google removed in the patch,
and modified it for their own use, so I had to slightly adapt the
revert to that.

This reverts commit b76aa50f.

Change-Id: I3eeb85dec208cd0022c3d037a403bbe1a5d86e28

1. Add alarm will prompt error tips because it does NOT use
Notification Channel while NotificationCompat.Builder.build

2. Failed to start Alarm notification because it can NOT start
background service in Andorid O while APP is in Idle mode

Set targetSdkVersion as 25 so the AlarmManager/Notification
API will keep behavior as Android N

Change-Id: I79e058bf091c60ba89dc77b475eccf7a25212006
CRs-Fixed:

Change-Id: I3274bff4f070207951f4e43f145f95346fb6c8f3

Change-Id: I772f0a697b48d2d1752aa08d517bb09050f96836
Signed-off-by: Joey <joey@lineageos.org>