Intermittent loss of navigation buttons after screen unlock
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
No source files or tests are named. First try to reproduce the intermittent behavior on the reported setup: Fossify Launcher 1.10.0 on LineageOS 23.2, OnePlus 13, following the screen lock and unlock steps. Done means the navigation buttons are present every time the screen is unlocked.
Written by the indexing model from the issue text.
Description
Checklist
- I can reproduce the bug with the latest version given here.
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- This issue contains only one bug.
- I have read and understood the contribution guidelines.
Affected app version
1.10.0
Affected Android/Custom ROM version
LineageOS 23.2 (20250929 build)
Affected device model
OnePlus 13
How did you install the app?
GitHub releases
Steps to reproduce the bug
- Unlock the screen
- The navigation buttons may or may not be there
- Turn the screen off / lock the screen again if the problem occurs
- Unlock the screen
- Lather, rinse, repeat
Expected behavior
The navigation button should be present any time the screen is unlocked.
Actual behavior
Intermittently, the navigation buttons are not present leaving it impossible to do anything without turning the screen off / locking the screen and subsequently trying to unlock it again.
Screenshots/Screen recordings
No response
Additional information
I thought this could potentially be some other problem, but if I go back to the LineageOS stock launcher (Trebuchet), I can't reproduce the problem. I don't personally like the stock launcher, so I would much rather stay with Fossify Launcher.
Please let me know what further details I can provide to help troubleshoot.
- Dominant language
- Kotlin
- Stars
- 703
- Forks
- 85
- Avg merge
- 4d 39m
- Merged PRs (30d)
- 7
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 FossifyOrg/Launcher
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FossifyOrg/Launcher#453 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FossifyOrg/Launcher#447 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
FossifyOrg/Launcher#446 ·
Maintainers usually reply within 3 days
-
feature request needs triage
Difficulty 3/5 1-2 days Newbie friendliness 40/100
FossifyOrg/Launcher#461 ·
Maintainers usually reply within 3 days
-
bug needs triage
Difficulty 3/5 1-2 days Newbie friendliness 64/100
FossifyOrg/Launcher#452 ·
Maintainers usually reply within 3 days
All issues in FossifyOrg/Launcher
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
partiql/partiql-lang-kotlin#1972 ·
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
enorm-labs/event-junkie#3027 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
libre-tube/LibreTube#8854 ·
Maintainers usually reply within 1 day