Intermittent loss of navigation buttons after screen unlock
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Kotlin
- Estrellas
- 703
- Forks
- 85
- Merge medio
- 4 d 39 min
- PR fusionados (30 d)
- 7
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FossifyOrg/Launcher
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
FossifyOrg/Launcher#453 ·
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
FossifyOrg/Launcher#447 ·
-
bug needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
FossifyOrg/Launcher#446 ·
-
bug needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 64/100
FossifyOrg/Launcher#452 ·
-
bug needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
FossifyOrg/Launcher#451 ·
Todos los issues de FossifyOrg/Launcher
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 64/100
maplibre/maplibre-native-ffi#792 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
-
an:enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100