InfiniTimeOrg / InfiniTimeOrg/InfiniTime
It's still possible to accidentally change/switch off the alarm while asleep
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
Verification
- I searched for similar issues (including closed issues) and found none was relevant.
Introduce the issue
The recent 1.16 release fixed some important alarm issues - crashes and accidental alarm settings change - which is great.
So now when the alarm is ringing it's only possible to turn it off, other buttons have been hidden.
But just right after turning off the alarm, the alarm configuration screen appears for a few seconds which again enables the possibility of accidentally changing the alarm time or disabling it completely.
Preferred solution
I think that after turning the alarm off, it would be better to skip the alarm config screen and go back directly to any previous screen the watch was in , e.g. main/watchface screen.
Version
1.16
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the alarm-off flow from the ringing alarm into the alarm configuration screen, then identify how the previous watch screen is restored. Confirm the behavior on a device or emulator: turning off a ringing alarm should return directly to the prior screen without briefly exposing alarm configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100