I’m always wary of reporting any issue I have as a “bug,” because more likely than not, it might be something I’m doing wrong or overlooking. But, for the life of me, I can’t figure this out:
According to KWGT, I have an alarm set (i.e., $si(alarmon)$ returns 1, and $df(“EEE hh:mma”, si(alarmd))$ returns the current, actual time). However, I do not have an alarm set on my phone. And the weirdest thing is that the supposed alarm’s time keeps changing to the current time.
If it matters, I’m running a pixel 9 under android 16.
Check whether your system actually reports any alarm info. For example, on my Xiaomi the system only exposes one alarm the one set within the next 12 hours and KWGT can’t see the rest, so it shows weird data. This started happening after some Android/HyperOS updates. It might be the same on Pixel. Try setting an alarm for a couple of hours and see if KWGT detects the correct time.
Huh, the results left me even more perplexed. I created an alarm for a few hours from now but, because KWGT reports the next inmediate alarm, it still only shows the current time as the “next alarm time”. And, because this ghost alarm is supposed to be “now’” there is no way for me to set a real alarm in between.