search

BlackyHawky / Clock

Privacy-conscious open-source clock, based on AOSP Clock
Apache License 2.0
284 stars 17 forks source link

Specify "USE_EXACT_ALARM" permission in manifest? #151

Open secretmango opened 4 days ago

secretmango commented 4 days ago

Android has a permission for apps to set alarms and events or something.

If that is used, the time when the next alarm will ring, is displayed on the lockscreen.

Also, alarms always work.

This is not the case for this clock, and I am pretty certain that alarms dont ring reliably.

I think the permission is USE_EXACT_ALARM

https://developer.android.com/about/versions/14/changes/schedule-exact-alarms

BlackyHawky commented 4 days ago

Hi,

Do not indicate the Bug label if you have not encountered a bug on your device; it can mislead users. Especially since the title you had written clearly indicated that the alarm does not sound in general when this is not the case.

Also, it is better to use the template in case of a bug.

I'll take a look later because until proven otherwise, it works fine on my device with Android 14.

secretmango commented 4 days ago

The bug is that the alarm does not register as an alarm and doesnt reliably go off.

This is how it should look like on the lockscreen.

I am using Android 15, which may be a difference here. I am not sure if the bug goes further than the missing display, I will check.

BlackyHawky commented 4 days ago

@secretmango When you say "doesnt reliably go off", does that mean that no alarm goes off?

Moreover, you mean you can display this app's widget on lock screen?

What model is your device? Do you use an alternative ROM?

Note: Currently, the maximum SDK for this application is 34, so perhaps some adjustments need to be made for Android 15.