Wrong SIM storage
I maintainer di solito rispondono entro 4 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 25/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Kotlin
- Stelle
- 917
- Fork
- 73
- Merge medio
- 5g 8h
- PR unite (30g)
- 7
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di FossifyOrg/Contacts
-
feature request needs triage
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
FossifyOrg/Contacts#176 · 1 commento ·
I maintainer di solito rispondono entro 4 giorni
-
bug needs triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 64/100
FossifyOrg/Contacts#618 ·
I maintainer di solito rispondono entro 4 giorni
-
feature request needs triage
Difficoltà 3/5 1-2 giorni Idoneità per principianti 65/100
FossifyOrg/Contacts#614 · 1 commento ·
I maintainer di solito rispondono entro 4 giorni
-
New field: IBANApertafeature request needs triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
FossifyOrg/Contacts#613 ·
I maintainer di solito rispondono entro 4 giorni
-
bug needs triage
Difficoltà 4/5 3-5 giorni Idoneità per principianti 52/100
FossifyOrg/Contacts#612 · 5 commenti · 1 reazione ·
I maintainer di solito rispondono entro 4 giorni
Tutte le issue di FossifyOrg/Contacts
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 73/100
tortuvshin/open-apps#377 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
supabase-community/supabase-kt#1413 ·
I maintainer di solito rispondono entro 5 giorni
-
Type: Possible bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
spacecowboy/Feeder#1258 ·
I maintainer di solito rispondono entro 1 giorno
-
[Submission] 抖音火山版Apertasubmit-adaption submit-adaption-pre
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
BetterAndroid/android-notification-icon-project#744 · 1 commento ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
utopia-rise/godot-jvm#1004 ·
I maintainer di solito rispondono entro 1 giorno