Clock 2.0

[BlackyHawky]

Fixes

• Fix alarm triggering for Android 14;
• Fix stopwatch and timer notifications;
• Fix force close for bedtime when no alarm is set or when the device is rotated;
• Fix some malfunctions for the Bedtime mode;
• Fix screensaver launch for Android 13+;
• Fix display and update of digital widget for Android 12+;
• Fix setting alarm volume in settings;
• Fix background color of bottom navigation bar (tablets are the most affected);

Improvements

• Implement material design (switches, time picker, rounded icons, card background,...);
• Add dynamic colors;
• Add AMOLED mode for dark theme;
• Add new permission management;
• Add monochrome icon;
• Add collapsing toolbar;
• Add Material You analog and digital widgets;
• Add "Bedtime" mode (by @Nilsu11);
• Replace icons with more rounded ones;
• When the application is launched for the first time, a presentation of the main features as well as the possibility of managing permissions is included;
• Add verification that essential permissions are granted at app launch to ensure the app is working properly;
• Allow debug version to be installed along with release version;
• Set default ringtone for alarms in settings;
• Add screensaver display options;
• Activate screensaver with a long press on the clock;
• Reduce screensaver animation to 30 seconds;
• Menus are displayed by icons;
• Modernize the appearance of settings;
• Add "About" section in settings;
• Animate the bedtime icon;
• Displays keyboard automatically when editing an alarm;
• Add a delete icon and the text "Delete" when swiping to delete an alarm;
• Add a button to duplicate an alarm (except for the bedtime alarm, which is useless);
• The vibrator is not activated when an alarm is created and on alarms initially created;
• Increase vibrator duration when activating an alarm;
• Allow display of analog clock in the alarm trigger view;
• Update Fragment related code to use AndroidX;
• Update license headers;
• Delete unnecessary files and code;

---

This discussion was created from the release Clock 2.0.

[qw123wh]

Perfect, thank you.

I noticed that you removed do not disturb for bedtime, you did well; actually not even the google clock activates do not disturb. At this point you could also remove the do not disturb permission also because that permission was only needed for bedtime

Add topic in the about section, you can use the same ones I put in the old reposity.
Without the topics, this repository is impossible to find for a user searching for an Android clock app on github.

[BlackyHawky]

At this point you could also remove the do not disturb permission also because that permission was only needed for bedtime

As I didn't have many devices to test, I preferred to leave this permission; moreover, I realized that it is present and necessary in other alarm applications. Surely this can be removed in a future release.

Add topic in the about section...

Done. Thanks for the tip. 😉

[Nilsu11]

Since I added the permission I also can confirm that it only was used in the bedtime service, so it can be removed safely. If you want notifications to ignore DND you would have to regulate this at the notification channel mangement in NotificationUtils which I haven't touched. Also google clock doesn't require it, which this clock app is closely related to. Since you removed all bedtime mode features you could also go ahead and remove it.

[BlackyHawky]

I hadn't realized that this authorization was added at the same time as the bedtime mode. So I'm going to remove it without worry.
(If I'd known, I'd have released it right after this change... Too bad.)

[BlackyHawky]

I'm not sure that the update will be done on F-Droid; indeed, if you look here, you can see that the old repository is still referenced (but the version has been updated correctly).
Perhaps I need to open a ticket?

[BlackyHawky]

That's what I thought. 😅

From what I've read on Gitlab, it can take several days for the version to be compiled on F-Droid.
So I'll see next weekend whether I'll open a ticket or not.

[BlackyHawky]

@IzzySoft: I've seen you intervene in the past to make this application available on F-Droid so I'd like to ask for your help and explanations, please.

I've made a few modifications, published a release version on GitHub available here) and it would be great if the application could also be updated on F-Droid.

I can see that the com.best.deskclock.yml file (available here) is updated, but only partially.
Indeed, the SourceCode:, IssueTracker: and Repo: fields are not updated and I have the impression that this will prevent the application from being updated on F-Droid.
(FYI: these fields refer to the old repository that @qw123wh transferred to me a few days ago.)

Can you tell me if I'm right or not? If so, do you know how to update these fields? Maybe it's automatic after a few days?

Thank you in advance.

Edit: I've opened an issue on GitLab (here) in case this is necessary.

[IzzySoft]

I'm currently not active at F-Droid, so it won't be me to intervene there this time. Also with so many apps I've worked on, I don't remember the reasons for each of them. I'd suggest you to report that there. With the original repo transferred to you, there should be no conflicts when it comes to "take over the packageName" etc.

for updating the mentioned fields, it will need a merge request at fdroiddata.

[BlackyHawky]

I didn't know there were any disputes within the F-Droid team...

Finally, we've already requested the changes in the metadata file; these changes have been validated, so let's wait and see if the update is done correctly.

@IzzySoft Thank you for taking the time to reply.

[IzzySoft]

I didn't know there were any disputes within the F-Droid team...

Disputes? Eh. Just a few (core) contributors (including their RB specialist) left, so what </s>

Nevertheless, best luck and good progress for you!

[qw123wh]

@BlackyHawky I tried to create a PR where I change the route maybe this can help. Let's wait a few more days.

https://gitlab.com/fdroid/fdroiddata/-/merge_requests/14985

[BlackyHawky]

The screenshots won't fix themselves. It's a long-standing bug with fdroidserver. A work-around is to replace the unwanted ones by 1x1 px images, and once those have overwritten the old screenshots remove them again from fastlane.

@IzzySoft

• Screenshots replaced for version 2.2 with commit 7e5df63;
• Screenshots removed for version 2.3 with commit b4a9ae4;

but screenshots are still available in F-Droid 😭😭

[IzzySoft]

As outlined: long-standing bug with F-Droid which I doubt they'll fix anytime soon. Just add 1x1px pictures to replace the old ones so they become invisible. Once the next release was pulled and the 1x1px replacements reached F-Droid, you can remove them again from your fastlane (which will automatically remove them from IzzyOnDroid with the release after that).

Pointer: Never rename screenshots if your app is listed at F-Droid.org, their updater does not handle that.

[IzzySoft]

@BlackyHawky as those 1x1 px screenshots now served their purpose (they've reached F-Droid), maybe it's time to remove them here again to not "pollute" other places using the structure (e.g. IzzyOnDroid, where inclusion was requested and your app added meanwhile, too)? Thanks in advance!

[BlackyHawky]

@IzzySoft
The last 1x1 px screenshots added have been removed for version 2.10.1

[IzzySoft]

Thanks! I've now updated the config here to pull screenshots along with the other fastlane data on updates.