FossifyOrg
tomorrow never comes :-)
Checklist
- [x] I can reproduce the bug with the latest version given here.
- [x] I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- [x] I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- [x] I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- [x] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- [x] This issue contains only one bug.
- [x] I have read and understood the contribution guidelines.
Affected app version
1.3.1
Affected Android/Custom ROM version
Android 15
Affected device model
Samsung Galaxy A16 5G
How did you install the app?
GitHub releases
Steps to reproduce the bug
I create an alarm that doesn't specify a date for tomorrow.
Expected behavior
I created an alarm on Thu for 10am tomorrow.
Actual behavior
The alarm should have gone off Fri but it changed to Sat.
Screenshots/Screen recordings
Please see https://github.com/orgs/FossifyOrg/discussions/719 for screenshots.
Additional information
No response
I have the same issue.
App version 1.3.1. Android 15. (Nothing OS 3.5 - Build: Metroid-V3.5-250911-2112) Nothing Phone 3 (A024). Installed from F-Droid.
My alarm settings are: Max reminder duration - 5 minutes Increase volume gradually - On Always use same snooze time - On Snooze time - 5 minutes
The alarm itself: Time 4:30 (tomorrow) No days selected Vibrate - On Sound - Custom (Present on phone and working) Label - None
Even with "Allow background usage" turned on and "Sleep standby optimization" turned off, alarms set for the early morning never sound. Do Not Disturb mode is scheduled overnight. "Alarms can override end time" is on. Alarms in Do Not Disturb is on. The alarm is registered with the system and used to set the end time for Do Not Disturb and Smart Charging Mode. The phone locks itself overnight and requires the daily password re-entry in the morning. (It does not reboot, but locks as if it did.)
After unlocking the phone and opening the Fossify Clock app, the alarm is still turned on, but now rescheduled for the new "tomorrow". There is no "missed alarm" notification - like what I got on a previous phone when the alarm failed to run due to a dead battery.
I don't know if the fault lies with the app or the OS. If the OS is somehow interfering with the app, I'd rather get notified late than never: e.g. Try to schedule the app to launch multiple times after the scheduled alarm time and run the alarm immediately if the app successfully launches within 30 minutes of an alarm that failed to run. If a one-time alarm was missed by more than 30 minutes, deactivate it and and issue a notification of a missed alarm instead of silently carrying it over to the next day.
I really don't want to have to use the Google Clock (spyware) app, but I need a reliable alarm.
Further testing suggests that this combination of phone and app may be prone to failure:
- Another alarm app did work with the same settings under the same conditions on my Nothing Phone 3. [1 attempt]
- The Fossify alarm did work on my OnePlus 8 (IN2015) running Android 15 (CrDroid 11.6 - custom rom). [1 attempt]
- The Fossify alarm did work with Fossify Clock installed as a system app on my rooted Nothing Phone 3. [1 attempt] (More testing may be needed to confirm the consistency of these results.)
The other clock app I tried also requested the "Power Off Alarm" permission. Fossify Clock currently does not request this permission. That app was able to boot my phone 2 minutes prior to the alarm and activate the alarm while the phone was still fully locked (encrypted) after a cold boot. The only difference being that my alarm sound is replaced with generic beeps when the device is locked.
For now, I think I'll use the other clock app. Power off alarm is a valuable feature to further increase the reliability of the alarm.
The other clock app I tried also requested the "Power Off Alarm" permission. Fossify Clock currently does not request this permission. That app was able to boot my phone 2 minutes prior to the alarm and activate the alarm while the phone was still fully locked (encrypted) after a cold boot. The only difference being that my alarm sound is replaced with generic beeps when the device is locked.
For reference, that is tracked here: https://github.com/FossifyOrg/Clock/issues/92
I've run into the same issue on 1.4.0. To reproduce:
- Set a non-repeating alarm with time set to a time that's already passed (i.e., if it's currently 12:00, set to 11:00); this will schedule the alarm for tomorrow, as expected.
- Wait for tomorrow to come; the alarm widget will still show the alarm scheduled correctly.
- Restart the device; the alarm widget will now show the alarm scheduled for the next day.
My guess is that the alarm gets stored specifically as "tomorrow at <time>" instead of "on <date> at <time>", and gets reinitialized from storage as such when the app restarts, pushing it to the new date if the day rolled over since it was set.
My guess is that the alarm gets stored specifically as "tomorrow at
That is correct. I'll start work on this soon.