Change-Id: I12ea4416a8b0008bf98d32e777a0671c15b5b82b

Q 1922

See merge request !13

Change-Id: Iffb5f006b32465384feedaea3a3f84739e8271f6

Change-Id: I3ea406bf3e26f65445727949b68ff250e2b3e9e4

Change-Id: Ib88d9d080e532628a85319966d99abee0aba7bb7

Change-Id: Ic2e3cdea67d0d12f13afe8b049a8128cf30de31f

Change-Id: I4588105ffc653f97f09b98923acc573298b08748

Nihar Thakkar authored Jul 08, 2019 and Alexandre Roux committed Sep 07, 2020

(cherry picked from commit 9cd40658)

Root cause: API ActivityTaskManagerService.notifyKeyguardFlagsChanged is called multiple times,
which causes the activity status abnormal.

Solution: Add 'android:showWhenLocked = true' to
ensure activity show on the top even  when screen locked.

BUG: 156311117

Test: manual - Tested the DeskClock UI manually and tested the alarm.

$ make -j 40
$ ls -l  out/target/product/bonito/product/app/DeskClock/DeskClock.apk
  -rw-r----- 1 rtenneti primarygroup 6117353 Jul 13 11:35 out/target/product/bonito/product/app/DeskClock/DeskClock.apk

$ adb install -r out/target/product/bonito/product/app/DeskClock/DeskClock.apk

+ Verified by setting up the alaram, lock the screen and waiting for the alarm to go off.

Change-Id: I69c44571cd86c21203311c89081c8935d5ed1450

AOSP/DeskClock - Call executePendingTransactions only if mFragmentManager is not destroyed. Fixes the crash bug. Code matches internal code.

BUG: 153590150

Test: manual - Tested the DeskClock UI manually and tested the timer.

$ make -j 40

... 6117353 Jul  7 15:27 out/target/product/bonito/product/app/DeskClock/DeskClock.apk

$ adb install -r -d -t out/target/product/bonito/product/app/DeskClock/DeskClock.apk

Change-Id: I582013ebffef2c8d1ec16255ea531d874d14a968

* Otherwise onStart() in StopwatchFragment will be called
  when app still believes it's running in the background and
  thus will remove FLAG_KEEP_SCREEN_ON window flag.

Fixes: https://gitlab.com/LineageOS/issues/android/-/issues/2258
Change-Id: I196051d0d03f479c7ee3d0f7735cf8e64b70d70d

* The getTimer() method returns null when we call getFabTargetVisibility()
  before the onCreateView method gets called, resulting in the FAB not
  being shown
* A video how to reproduce the issue can be found on the bug report linked
  below
* Fix: Always return the first timer (if one exists) so we can properly
  decide if the FAB needs to be shown

Fixes: https://gitlab.com/LineageOS/issues/android/-/issues/2250
Change-Id: Id16686c729ee41d14c890827dc441e81511c8405

Change-Id: I421928b0dae80290bf318a117037c8044a1c7b3b

* We can build with sdk_version = current after latest changes

Change-Id: Ie424ffd156e9595082dc8ad935fb1c9e8e22bd87

* Was used for a feature that isn't used anymore
* We need to create new tables because dropping columns isn't supported
  -> create temp tables, copy over values, remove old tables, rename temp
     tables
* Also fixes alarm inserts, which partially failed due to increasing
  volume and profile being indexed wrong:
"CursorWindow: Failed to read row 0, column 11 from a CursorWindow which
has 1 rows, 11 columns."
* Above fix is required for "new Alarms(cursor)" to not fail so we can
  actually get a valid Alarms object to insert into our (temp) database

Change-Id: I80e495792dcb65955de09268c7df9c6846cee559

* Building within an AOSP environment sets sdk_version: "current"
  which makes the build fail here due to usage of "com.android.internal"
  stuff
* Set local ids instead where required and use PreferenceImageView
  from androidx instead of com.android.internal

Change-Id: I5b50531720840ae81559c8fd958166154098b782

Change-Id: If5872d2adf67da2649eac2c03f195f2eec8547db

* Firing alarms and timers needs high priority but we don't need a
  notification sound, as the alarm / timer already bring their own sound
* This has been lost in the rework of notification channels
  -> Needs another channel recreation

* Snoozing was lowered in priority in commit
  22b6cf2f
  but I didn't give it a new id, so existing installations are left with
  notification sound when snoozing - who would want that?

Change-Id: I5c7fc96b657e966950414b40fb61c829040ece9f

* Convert to using androidx Fragments
* Group imports properly

Change-Id: Iaadfb417f0ca8638936875113ec2f39853f2a39c

* Currently the snackbar says
  "Der Wecker klingelt in 5 Tage, 3 Stunden  und 47 Minuten"
* It must be "Der Wecker klingelt in 5 Tagen, 3 Stunden und 47 Minuten"
* Also checked if these plurals aren't used elsewhere so other strings
  wouldn't make sense anymore - no more usages found

Change-Id: Iabadaa254afc7a04cb00d79753be1443719fce2c

* The alarm volume setting doesn't look as it should
* Copied "preference_volume_slider" from Settings (used in Settings->
  Sound) and stripped by stuff we don't need (suppression_text,
  widget_frame)
* Looks like without providing an initial icon, the layout would not
  inflate the space for it properly, so provide the default one

Change-Id: I31d103cd0b0a6f096d376af2026702a0a4754671

* Wrap the desk_clock layout into a LinearLayout so the Snackbar
  appears above the BottomNavigationView
* Change the icon tint and text color to reflect the changes for the dark
  layout
* Use a BottomNavigationView instead of a TabLayout
* Reorder imports - looks like someone didn't care before
Co-authored-by: Arian <arian.kulmer@web.de>
Co-authored-by: Jesse Chan <jc@lineageos.org>
Signed-off-by: Jesse Chan <jc@lineageos.org>
Change-Id: I780713dcbeb58256b2660a9631d48e5f7259fb11

Change-Id: Ia2c7e28e161f1a0f01de13deff4d02a78c34f8d5

... we have cookies

* Move minSdkVersion to 24 so the notification actions don't use the
  icons anymore and we can just tint the icons black to fit onto the new
  accent color used e.g. for the FABs
* Move accent color to an own color name which is defined differently
  for values and values-night
* Background: Keep blue for light theme but use grey for night one

Change-Id: Ib14044fc9c6de15453891638581a7e3f4d10c6c5

* Alarm notifications etc. are important and should be on high
  importance level.
* On contrast, upcoming alarms etc. should not have sounds or vibrations
  attached to them.
* In addition, we need to fix strings for notification channel.
* In order to achieve this, we need to create some new channels because
  you can't change the priority for existing channels
* Delete old channels on boot and update the names of existing channels if
  they already exist (they get created with the first notification
  requiring them)
* Move creation of upcoming alarm notifications into one place
Co-authored-by: Wang Han <416810799@qq.com>
Change-Id: I6d2e9abd6a822a62b3313c62b0617d8d9211948e

Change-Id: I6ba715acbcdfcbd7472d5f7bf2008efa6027139a