-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
目覚め時計 #3906
目覚め時計 #3906
Conversation
Compiled f7 firmware for commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The basic alarm function works well, incl. waking up the Flipper when it was shut down.
A few notes/ideas, knowing full well that this PR is WIP so I'm aware that some of those may already be planned:
- A "bell" icon, like the Bluetooth/SD card icons are placed currently
- Perhaps allow applications to use ALMB while ALMA is "reserved" for the inbuilt Clock app. Make it possible for the app to choose if it wants to get the default "wake up!" screen and wake the Flipper up, or if it wants to control that by itself
- Allow applications to subscribe to the alarm ISR at least for ALMB, right now it seems to be dominated by the Clock app
- If ALMA and ALMB get exposed to apps, reset them when resetting Flipper settings, and maybe also offer a "Reset alarms" option in the Clock app, if some app leaves alarms configured in a weird state
- One shot timers? Both in furi rtc, and in the Clock app
Co-authored-by: Silent <[email protected]>
Co-authored-by: Silent <[email protected]>
Co-authored-by: Silent <[email protected]>
Regarding your previous message: despite of the fact that there are 2 alarm slots, having both of them working in a same way is impossible. Alarm output can only be configured to work with one source. Also since we don't have way to start app on alarm, I'll hide this API from public use. PS: I'm open to new creative ideas on how to make this thing usable, but super busy and don't have time to polish this PR further |
Indeed, tricky. I think this could be solved by not treating the alarm callback as an ISR (from the API standpoint), but rather |
What's new
Verification
Checklist (For Reviewer)