Juggluco function inhibited by AAPS 4.0.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- accessibility, mobile
Research direction
The payload names no source files, so start by reproducing: install a Juggluco build alongside AAPS 4.0.0 and AAPS RC-1, then open the AAPS screen to confirm the floating glucose overlay disappears only in 4.0.0. The screenshot in the issue is the reference for the symptom. Work out what changed between RC-1 and 4.0.0 in how the AAPS main activity handles windows or overlays. Done means the floating overlay stays visible while the AAPS screen is open, verified on a device. Comments on the thread are the best source for which screen or component to look at.
Written by the indexing model from the issue text.
Description
The floating glucose function available to visually impaired users of Juggluco no longer functions when the AAPS screen is displayed on the user device following the installation of AAPS 4.0.0.
The function continues to be available to visually impaired users when other screens are open on the device, email, browser etc, but disappears when the AAPS screen is opened.
The function was available to users of AAPS 3x, 4 beta or 4 RC-1 when the AAPS screen is displayed.
Visually impaired users can restore the function by reinstalling AAPS 4 beta or RC-1 or AAPS 3x.
- Dominant language
- Kotlin
- Stars
- 1.2k
- Forks
- 7.4k
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 93
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from nightscout/AndroidAPS
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nightscout/AndroidAPS#5481 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nightscout/AndroidAPS#5478 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
nightscout/AndroidAPS#5475 ·
Maintainers usually reply within 1 day
-
enhancement for_discussion minor
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
nightscout/AndroidAPS#5422 ·
Maintainers usually reply within 1 day
-
enhancement for_discussion
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nightscout/AndroidAPS#5057 · 2 comments ·
Maintainers usually reply within 1 day
All issues in nightscout/AndroidAPS
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
AChep/keyguard-app#1665 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openai/openai-java#1337 ·
Maintainers usually reply within 1 day
-
enhancement impact:U1 P3 reach:R2 size:S
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
thtbee/nectarlink#196 · 1 comment ·
Maintainers usually reply within 1 day
-
sentry-loop
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
paritytech/trinity-user-agents#1890 ·
Maintainers usually reply within 1 day