My phone number is appended at the post of the caller's phone number when VoLTE is on (I found the solution and fixed it)

[colorlit]

Build date

PixelExperience_Plus_alioth-12.1-20220920-0633-OFFICIAL and PixelExperience_Plus_alioth-13.0-20221113-2000-OFFICIAL

Expected Behavior

Only a caller's phone number (or a name saved on contacts) is displayed on call logs and receiving phone call UIs

Current Behavior

Two phone numbers are displayed in this format : _caller_phone_number&_receiver_phone_number and logged as _caller_phone_number_receiver_phone_number (without a character &)
(ex : 0123456789&0987654321)
Even if I saved the caller's phone number on contact(in this case 0123456789 as the number for sure), the call information is displayed and logged as above instead of the name saved.

I'm using physical dual SIM cards but it seems like an irrelevant case because I can reproduce the issue with only one SIM card inserted.

Possible Solution

1. from build.prop, set an entity 'persist.vendor.radio.redir_party_num=0'
2. Back port POCO F4's stock NON-HLOS.bin file to POCO F3's NON-HLOS.bin (a.k.a. modem.img) file.
   I used two files to create altered modem image:
   F3 | A13 | beta | china region firmware 'alioth_images_V14.0.22.12.5.DEV_13.0_cn_chinatelecom',
   F4 | A12 | stable | global firmware 'V13.0.5.0.SLMMIXM'
   1. Locate original NON-HLOS.bin in fastboot rom file/images/NON-HLOS.bin
   2. Mount bin files(I used OSFMount) as R/W, go to ./image/modem_pr/mcfg/configs/mcfg_sw/generic/
   3. Copy mbn files from F4's to F3's in same directory. I just copied folders(In my case, 'Korea' folder) from F4 and replaced F3's original files with it.
   4. Dismount
   5. Replace the modem img with the modified one. I done it by hit 'fastboot flash modem_ab NON-HLOS.bin'.

• update : firmware version mismatch may lead to not working biometric services(fingerprint scanner). I replaced above modem img(NON-HLOS.bin) with another one based F3's 13.0.8 stock global firmware and fingerprint bug has been addressed. You may know better than me as you are who chose the vender things to be used.

Set an entity on build.prop 'persist.vendor.radio.redir_party_num=0' addressed the issue on Android 12.
The maintenancer of LineageOS POCO F3 build resolved this issue by porting POCO F4's modem firmware image. I heard it addressed the problem as F4 has same SDM870 SoC logic board and has more VoLTE profiles included in modem firmware than F3's stock image. So I had followed same steps and the problem has disappered.

Steps to Reproduce

1. Set the VoLTE option ON on the cellular setting menu.
2. Receive an incoming call. ( outgoing call is logged properly )
3. I did not touch any of settings regarding call, so it should be reproduced at this level.
4. This behavior has persisted since 12.1-20220920 build. As that was the first install of this ROM I don't know if the problem was there in previous builds.

/device alioth
/version thirteen_plus

[pixelexperiencebot]

Issue created! You can close at any time by commenting /close

[colorlit]

The number exchanged several calls as below is saved like this.
Note that I masked the numbers for privacy reasons.

Outgoing calls are displayed and logged properly.

In case of incoming calls, two numbers; caller&receiver(my number) are displayed in this order.

Another screen capture.

Incoming calls are logged in call log as above. '&' character has been omitted.

Redialing to last number. Note that '&' character has been omitted as same. The system does not recognize this as the same number with one I saved above, but the call is connected to the other ends btw.


Call logs of each format. It also shows that the system regards these as different numbers.

[colorlit]

Update : I found it's probably related with the VoLTE(after I disable VoLTE the issue got disappeared) and
'persist.vendor.radio.redir_party_num=1' entity on build.prop causes this problem.

It seems that overriding that option persist.vendor.radio.redir_party_num=0 resolves the problem on Android 12 but does not work on Android 13.

I'm not sure but not compatible VoLTE profile may be the cause of the issue. (The stock modem firmware does not contain my carrier's VoLTE mbn profile but the VoLTE option is enabled by default on this ROM. I can not confirm it as I currently have no access to modify the modem file on Android 13.)

Another update : I managed to add a VoLTE support and checked its functionality(both a call circuit and a lte data connection are live during the call) but the issue has persisted.

[colorlit]

It seems that the maintenancer of LineageOS ROM addressed this issue by porting POCO F4(SDM870)'s modem firmware image to the ROM as two sibling devices use same SDM870 SoC and F4's modem firmware has much wider carrier compatibility with more VoLTE profiles included.

[colorlit]

I had addressed the problem by setting the build prop thing and porting POCO F4's modem image.

[colorlit]

https://gitlab.com/LineageOS/issues/android/-/issues/4946
https://review.lineageos.org/c/LineageOS/android_device_xiaomi_sm8250-common/+/334528