nightscout / nightscout/AndroidAPS
Feature Request: option "Force Speaker" for alarms
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 6.4k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 19
Description
In xDrip+ there is the possibility to select a "Force Speaker" option for a "Glucose Level Alarm".
Even if a headset is connected, the alarm then comes through the speaker of the cell phone.
Background:
If I listened to music or made a phone call using a headset and then put the headset down, then an alarm from AAPS is only heard through the headset. But because I have already put down the headset, I sometimes cannot hear an alarm.
In short:
It would be nice to be able to define the alarms from AAPS with the "Force Speaker" option as well.
Edit:
Observed with AAPS [ 3.1.0.3] with Google Pixel 4.
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 locating the alarm settings and alarm playback entry points in AndroidAPS, then reproduce the reported behavior with a connected headset on the stated Google Pixel 4 setup. Done means users can configure a Force Speaker option for alarms and hear those alarms from the phone speaker when a headset is connected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100