Wrong SIM storage
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 3/5
- Geschätzter Aufwand
- 1-2 Tage
- Anfängerfreundlichkeit
- 25/100
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
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.
- Vorherrschende Sprache
- Kotlin
- Sterne
- 917
- Forks
- 73
- Ø Merge
- 2 T. 2 Std.
- Gemergte PRs (30 T.)
- 9
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus FossifyOrg/Contacts
-
feature request needs triage
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 72/100
FossifyOrg/Contacts#176 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug needs triage
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 64/100
FossifyOrg/Contacts#618 ·
Maintainer antworten meist innerhalb von 1 Tag
-
feature request needs triage
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 65/100
FossifyOrg/Contacts#614 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
New field: IBANOffenfeature request needs triage
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 48/100
FossifyOrg/Contacts#613 ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug needs triage
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 52/100
FossifyOrg/Contacts#612 · 5 Kommentare · 1 Reaktion ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in FossifyOrg/Contacts
Ähnliche Issues
-
[Submission] WeChat KidsOffensubmit-adaption submit-adaption-pre
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 82/100
BetterAndroid/android-notification-icon-project#750 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
openbase/planetsudo.engine#107 ·
Maintainer antworten meist innerhalb von 1 Tag
-
native-cpu: -Wreturn-type in skainet_row_threads.c:150 (worker fn has no return)Evtl. vergeben @Doomguy-BFG9000 hat das heute übernommen. Offengood first issue size:xs skill:native
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 78/100
SKaiNET-developers/SKaiNET#1358 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 63/100
IBRAHIMDANS/i18nSupportPlus#577 · 3 Kommentare ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
PostHog/posthog-kmp#100 ·
Maintainer antworten meist innerhalb von 2 Tagen