Wrong SIM storage
Los mantenedores suelen responder en 4 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
The payload names no source files, so start from the app's SIM contact source selection in the Kotlin code and find where the SIM storage entry for a second SIM slot is chosen. The bug is that the SDN2 service-number storage is shown instead of the SIM's own contacts, which the reporter reproduces on Android 15 with a moto g15 power. Done means the SIM filter lists the card's contacts on that device, which needs a device or emulator with a second SIM slot to confirm, and the thread has no maintainer reply after 395 days.
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.2.5
Affected Android/Custom ROM version
Android 15 (stock, no root, etc.)
Affected device model
moto g15 power
How did you install the app?
GitHub releases
Steps to reproduce the bug
- Have a phone with this issue.
- In Contacts (or Phone), tap the filter icon and select SIM contacts (SDN2 here).
Expected behavior
My contacts from SIM card should be displayed.
Actual behavior
My carrier's service numbers from SIM card are displayed.
Screenshots/Screen recordings
No response
Additional information
Just noticed that when I select SDN2 (Service Dialing Numbers?) - for the primary SIM slot and it's the only choice for SIM - I don't get my contacts from SIM card displayed, but "service numbers" instead, which is a separate, read-only storage, I think.
On Galaxy A12 everything works fine. SIM storage names are "primary.sim.account_name" (SIM1) & "primary2.sim.account_name" (SIM2).
Interestingly, Google Contacts also shows those service numbers from SIM, mixed with phone storage contacts.
However, under "Organize -> Manage SIM (Import or delete contacts from SIM)" it shows my SIM contacts instead.
I also installed "SIM Contacts" (com.midi.simcontacts) app and it correctly shows my SIM contacts on "SIM CONTACTS" tab, but both phone storage contacts + service numbers on "ALL CONTACTS" tab, just like Google Contacts.
"SIM Card Info" (me.harrygonzalez.simcardinfo) shows the correct entries, too.
Even *#*#4636#*#* -> Phone Information -> <three dots menu> -> View SIM Address Book = correct list.
So, it seems to be fixable, I hope.
- Lenguaje dominante
- Kotlin
- Estrellas
- 917
- Forks
- 73
- Merge medio
- 5 d 8 h
- 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/Contacts
-
feature request needs triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
FossifyOrg/Contacts#176 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
bug needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 64/100
FossifyOrg/Contacts#618 ·
Los mantenedores suelen responder en 4 días
-
feature request needs triage
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
FossifyOrg/Contacts#614 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
New field: IBANAbiertofeature request needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
FossifyOrg/Contacts#613 ·
Los mantenedores suelen responder en 4 días
-
bug needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
FossifyOrg/Contacts#612 · 5 comentarios · 1 reacción ·
Los mantenedores suelen responder en 4 días
Todos los issues de FossifyOrg/Contacts
Issues similares
-
Default book icon displayed while loadingPosiblemente ocupada @Bhaskar-Guthula-137 la tomó hoy. Abiertobug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
kiwix/kiwix-android#5194 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
jellyfin/jellyfin-androidtv#5885 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 73/100
tortuvshin/open-apps#377 ·
Los mantenedores suelen responder en 1 día
-
contributor: external needs review
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
supabase-community/supabase-kt#1413 ·
Los mantenedores suelen responder en 5 días