Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[MIUI 12/Android 10] No audio on incoming calls with visible number when screen is locked (Regression v1.11.1)

Abierto
  • ¿Algo no está bien?
#814 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
android, kotlin
Área
mobile

Línea de trabajo

The payload names no source files, tests, or entry points, so the starting point is the diff between v1.2.0 and v1.11.1 in the call-handling code. The reporter's hypothesis is a timing problem on a locked screen when a contact lookup runs before audio starts, but that is unconfirmed. Reproducing needs a MIUI or similar Android 10 device with a locked screen. Done means audio works on a locked screen for visible numbers, confirmed on that device.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug needs triage
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.11.1

Affected Android/Custom ROM version

Android 10 / MIUI 12.0.1

Affected device model

Xiaomi mi note 10 pro

How did you install the app?

GitHub releases

Steps to reproduce the bug
  1. Install Fossify Phone v1.11.1 on a Xiaomi device with MIUI 12 (Android 10).
  2. Ensure the phone screen is LOCKED.
  3. Receive an incoming call from a VISIBLE number (saved contact or displayed number).
  4. Answer the call.

Control Test Matrix (tested on v1.11.1):

  • Call from MASKED/PRIVATE number + Screen LOCKED -> Audio WORKS.
  • Call from MASKED/PRIVATE number + Screen UNLOCKED -> Audio WORKS.
  • Call from VISIBLE number + Screen UNLOCKED -> Audio WORKS.
  • Call from VISIBLE number + Screen LOCKED -> Audio FAILS (Muted). : BUG!
Expected behavior

Audio (microphone and speaker) should work immediately upon answering, in all four scenarios listed above. This is the standard behavior observed in version 1.2.0 (version i use for 2 years)

Actual behavior

In the specific scenario where the screen is LOCKED and the incoming number is VISIBLE, the call connects (timer runs) but the audio channel remains muted (no input, no output).
The other three scenarios function correctly.
Setting battery optimization to "No restrictions" reduces the frequency of the bug but does not eliminate it completely on v1.11.1.

Screenshots/Screen recordings

No response

Additional information
  • Device: Xiaomi Mi Note 10 Pro
  • OS: Android 10
  • UI: MIUI 12.0.1
  • Affected Version: 1.11.1
  • Last Working Version on my phone: 1.2.0 (Confirmed Regression)

Technical Hypothesis:
The bug appears to be a race condition involving "Wake Locks" on MIUI.

  • Visible numbers trigger a database lookup (contact name/photo) before audio initialization.
  • Masked numbers skip this lookup.
    The delay introduced by the lookup on a locked screen (deep sleep) seems to cause the audio initialization to fail or occur too late. Version 1.2.0 does not exhibit this timing sensitivity.
Lenguaje dominante
Kotlin
Estrellas
1.4k
Forks
213
Merge medio
2 d 21 h
PR fusionados (30 d)
9

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de FossifyOrg/Phone

Todos los issues de FossifyOrg/Phone

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.