Calling wit preferred SIM in 2nd profile

[flang3]

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.6.0

Affected Android/Custom ROM version

GrapheneOS

Affected device model

Pixel 9 Pro Fold

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

When using the preferred SIM feature (per contact) in a secondary profile the call process hangs/stalls indefinitely.

Main profile works fine. Using the three dots menu to specify SIM works too.

Expected behavior

Calling should work.

Actual behavior

No calls possible for contacts that have a preferred SIM specified.

Screenshots/Screen recordings

Additional information

No response

[naveensingh]

1. Did you have this problem before you updated to 1.6.0?

preferred SIM feature (per contact)

2. Do you mean the Always use this SIM for this number option?

[flang3]

1. I also had the problem with 1.5.1 I didn't use any versions prior because I hadn't dual SIM back then.
2. Yes!

[dvino]

I have the same problem. To make a call, I have to tap the call notification, only then will the call start.
App version 1.11.1

[dvino]

I'm not a developer, but here's what Gemini says about this bug:

Root cause of the issue:

1. When recreating PhoneAccountHandle from saved strings for the preferred SIM, the constructor assigns Process.myUserHandle(). In a secondary profile, this attaches the Work Profile's user ID instead of the system's (0).
2. TelecomManager fails to find the SIM associated with this wrong UserHandle and puts the call into the STATE_SELECT_PHONE_ACCOUNT state.
3. InCallService receives this state and attempts to launch InCallActivity to show the SIM chooser.
4. Due to Android 10+ Background Activity Start restrictions, the startActivity() request is silently blocked by the OS. The call stalls indefinitely waiting for UI.
5. Tapping the notification acts as a user interaction, bypassing the background restriction, opening InCallActivity, and allowing the call to proceed.

Fix:
Do not recreate PhoneAccountHandle manually. Instead, query telecomManager.callCapablePhoneAccounts, find the matching account by its Id and ComponentName, and use the system-provided PhoneAccountHandle (which contains the correct UserHandle).

These are Gemini's suggestions for fixing getCustomSIM function.

    import android.annotation.SuppressLint

    // ... 

    fun getCustomSIM(number: String): PhoneAccountHandle? {
        
        // --- ADDED BLOCK (FIX) ---
        // Вспомогательная функция, которая ищет системный хэндл с правильным UserHandle(0)
        fun getValidSystemHandle(savedHandle: PhoneAccountHandle): PhoneAccountHandle {
            try {
                val telecomManager = context.getSystemService(android.content.Context.TELECOM_SERVICE) as android.telecom.TelecomManager
                
                @SuppressLint("MissingPermission")
                val availableAccounts = telecomManager.callCapablePhoneAccounts
                
                val correctSystemHandle = availableAccounts.firstOrNull {
                    it.id == savedHandle.id && it.componentName == savedHandle.componentName
                }
                
                // If we find a real SIM card in the system, we return it.
                if (correctSystemHandle != null) {
                    return correctSystemHandle
                }
            } catch (ignored: Exception) {
                // If there are no permissions or another error — we ignore it.
            }
            // Fallback: возвращаем то, что собрали из БД
            return savedHandle
        }
        // --------------------------------

        val key = getKeyForCustomSIM(number)
        prefs.getPhoneAccountHandleModel(key, null)?.let {
            // WE PASS THE CREATED HANDLE THROUGH OUR FIX
            return getValidSystemHandle(it.toPhoneAccountHandle())
        }

        // fallback for old unstable keys. should be removed in future versions
        val migratedHandle = prefs.all.keys
            .filterIsInstance<String>()
            .filter { it.startsWith(REMEMBER_SIM_PREFIX) }
            .firstOrNull {
                @Suppress("DEPRECATION")
                PhoneNumberUtils.compare(
                    it.removePrefix(REMEMBER_SIM_PREFIX),
                    normalizeCustomSIMNumber(number)
                )
            }?.let { legacyKey ->
                prefs.getPhoneAccountHandleModel(legacyKey, null)?.let {
                    val handle = it.toPhoneAccountHandle()
                    prefs.edit {
                        remove(legacyKey)
                        putPhoneAccountHandle(key, handle)
                    }
                    // WE PASS THE MIGRATED HANDLE THROUGH OUR FIX
                    getValidSystemHandle(handle)
                }
            }

        return migratedHandle
    }

Since I don't fully understand the proposed code, I'm not planning on opening a PR. But perhaps this information will help fix the bug.