New My voice shouldn't be absent in a call recording. Voice of the other side of the call is recorded only. Android 11.

[usernamexiaomieu]

There is an issue with call recording after upgrade to Android 11 MIUI by xiaomi.eu 12.0.2 MIUI 12 | V12.0.2.0.RCXMIXM | (stable). My voice is not recorded. The voice of the person on the other end is recorded only. My Redmi Note 8T model: M1908C3XG. The issue is reproducible every time (100%). The bug didn't occur in the previous versions of the ROM. Will you fix it so that both sides of the call are recorder, please?

 

[Igor Eisberg]

We don't have that device and you didn't even provide a log.

 

[ascenda]

I have this same issue. My voice isn't recorded.

 

[usernamexiaomieu]

The call recording stopped working entirely in the newer version (published yesterday, SHA 7419b76c53b0fca55e9ba7568dab3f23f1684572, xiaomi.eu_multi_HMNote8T_V12.5.2.0.RCXMIXM_v12-11.zip, https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/): MIUI 12.5 | V12.5.2.0.RCXMIXM | (stable) on Redmi Note 8T model: M1908C3XG. There is the UI loop (views/screens changing back and forth repeatedly automatically) reproducible every time I start a call and automatic call recording is enabled, unfortunately. It is not possible to use a smartphone until the call is ended on the other end. There isn't any file with the call recording created in the end.

 

[Kacper Skrzypek]

Like Igor said, we don't have that device, so would be nice if you provide the logcat.

[GUIDE] Logging with ADB Logcat

Many of the issues encountered by users can be tracked down by the team using a log produced by ADB (Android Debug Bridge) Logcat. Whenever encountering obvious failures like app crashes, background services crashes, etc. you should always attach a log to your bug report. Bug reports for such...

xiaomi.eu

 

[usernamexiaomieu]

Like Igor said, we don't have that device, so would be nice if you provide the logcat.

[GUIDE] Logging with ADB Logcat

Many of the issues encountered by users can be tracked down by the team using a log produced by ADB (Android Debug Bridge) Logcat. Whenever encountering obvious failures like app crashes, background services crashes, etc. you should always attach a log to your bug report. Bug reports for such...

xiaomi.eu

Reproduction steps video: "https://streamable.com/tehdrt". There are logs from another (later) attempt attached.

 

[Igor Eisberg]

V12.5.2.0.RCXMIXM for Redmi Note 8T has been reuploaded, this issue should now be fixed. Let me know if it's working.

 

[usernamexiaomieu]

V12.5.2.0.RCXMIXM for Redmi Note 8T has been reuploaded, this issue should now be fixed. Let me know if it's working.

I verified that the latter issue (UI loop bug) has been fixed in the newest version. The original issue of my voice not being recorded has not been fixed. I will upload logs soon.

 

[usernamexiaomieu]

The post has been marked as resolved incorrectly because the original issue is not fixed. I'm attaching logs and the .mp3 of a call recording where my voice is absent. The logs were generated using the command:
.\adb.exe bugreport

Pre-requisites:
1) Automatic call recording turned on

Steps:
1) Callers starts a phone call
2) Callee answers the phone
3) Both sides of the conversation speak
4) Caller or callee hangs up.
5) Play call recording (.mp3 file).

Expected result:
A call recording .mp3 file includes both voices of a caller and callee

Actual result:
A call recording .mp3 file includes voice of a callee only. The voice of a caller is absent in the .mp3 file.

Can I ask you to fix the bug and update the status of the issue so it is not marked as "resolved", please?

 

[Igor Eisberg]

The post has been marked as resolved incorrectly because the original issue is not fixed. I'm attaching logs and the .mp3 of a call recording where my voice is absent. Can I ask you to fix the bug and update the status of the issue so it is not marked as "resolved", please?

The files you included are not logs made with logcat. Read the sticky post on how to record proper logs...

 

[usernamexiaomieu]

New logs generated with the command:
.\adb.exe logcat -d > "20220109 logcat voice absent from a call recording file.txt"

 

[DrBrod]

I have the same problem on xiaomi.eu_multi_HMNote8T_V12.5.2.0.RCXMIXM_v12-11. Only the voice of the interlocutor is recorded when making a call.

 

[DrBrod]

Interestingly, does anyone read our messages?

 

[JiaiJ]

Interestingly, does anyone read our messages?

Yes, I believe the forum works correctly.

 

[maxi-hard]

I approve that problem exists. My phone is Redmi Note 8T. MIUI 12, V12.0.2.0.RCXMIXM stable by xiaomi.eu. Only person's voice is recorded. My voice is not recorded. Please fix this bug, or write instruction how to fix it (my device has root). I use standart built-in recorder, and don't want to use any third-party recorder. Thanks a lot!

 

[DrBrod]

Yes, I believe the forum works correctly.

Just don't wait for an answer.

 

[Igor Eisberg]

I approve that problem exists. My phone is Redmi Note 8T. MIUI 12, V12.0.2.0.RCXMIXM stable by xiaomi.eu. Only person's voice is recorded. My voice is not recorded. Please fix this bug, or write instruction how to fix it (my device has root). I use standart built-in recorder, and don't want to use any third-party recorder. Thanks a lot!

We don't have that device, no way to debug it properly.

 

[usernamexiaomieu]

We don't have that device, no way to debug it properly.

Let me support you in debugging. I have the device and can test fix candidates etc. What do you think?

 

[Igor Eisberg]

Let me support you in debugging. I have the device and can test fix candidates etc. What do you think?

I didn't say that we had any fix candidates, that's why we need to debug. Don't even know where to start.

 

[usernamexiaomieu]

I didn't say that we had any fix candidates, that's why we need to debug. Don't even know where to start.

Do you know how are bugfixes prepared and incorporated in new releases of MIUI? Is there maybe an official way to report bugs and have them fixed (by Xiaomi or others)?

 

[Igor Eisberg]

Do you know how are bugfixes prepared and incorporated in new releases of MIUI? Is there maybe an official way to report bugs and have them fixed (by Xiaomi or others)?

Official ROMs for Redmi Note 8T don't even have call recording support, so official Xiaomi support won't be able to help you with a custom ROM...

 

[ascenda]

So, how can we help to fix this bug?

 

[Igor Eisberg]

So, how can we help to fix this bug?

You could start my making a clean log starting from the moment the recording is starting.
1) Make sure automatic call recording is disabled.
2) Start a phone call and wait like 10 seconds.
3) Enter the commands quickly one after the other:

adb logcat -c
adb logcat > log.txt

4) Quickly start the call recording for about 10-15 seconds, then stop the call recording.
5) In the ADB window, press Ctrl+C to stop logging, or just close the window.

Such a log will be relatively short and only hold relevant information, not a 10MB log that can take days to analyze.

 

[usernamexiaomieu]

There may be relevant fragments:

01-17 17:40:01.399  2525  2525 E ndroid.systemu: Invalid ID 0x00000000.
01-17 17:40:01.399   809   809 D AudioPolicyManagerCustom: setForceUse() usage 0, config 0, mPhoneState 2
01-17 17:40:01.399  2525  2525 E VolumeDialogControllerCompat: Can't find translation for stream com.android.systemui.plugins.VolumeDialogController$StreamState@2502af9
01-17 17:40:01.400  2525  2525 I RingerModeLayout: Zenmode changed false,false -> false,false doAnimation:false
01-17 17:40:01.400  2525  2525 E ndroid.systemu: Invalid ID 0x00000000.
01-17 17:40:01.401  2525  2525 E VolumeDialogControllerCompat: Can't find translation for stream com.android.systemui.plugins.VolumeDialogController$StreamState@ed05a3e
01-17 17:40:01.401  2525  2525 I RingerModeLayout: Zenmode changed false,false -> false,false doAnimation:false
01-17 17:40:01.404 27965 27965 D DecorView[]: getWindowModeFromSystem  windowmode is 1
01-17 17:40:01.404 27965 27965 D DecorView: createDecorCaptionView windowingMode:1 mWindowMode 1 isFullscreen: true
01-17 17:40:01.406  2095  3054 I AS.AudioDeviceBroker: In isBluetoothScoOnForApp(), mForcedUseForCommExt: 0
01-17 17:40:01.406  2095  3054 I AS.AudioDeviceBroker: In isSpeakerphoneOn(), mForcedUseForCommExt: 0
01-17 17:40:01.406  2095  3054 W AudioService: None thiing for handleSpeakerChanged:2095/false
01-17 17:40:01.406  2095  3054 E TipCloseScreen: isFrontReceiver e=java.lang.NullPointerException: Attempt to invoke virtual method 'int android.media.AudioManager.getMode()' on a null object reference
01-17 17:40:01.407  2095  3054 W System.err: java.lang.NullPointerException: Attempt to invoke virtual method 'int android.media.AudioManager.getMode()' on a null object reference
01-17 17:40:01.407  2095  3054 W System.err:     at miui.util.TipCloseScreen.isFrontReceiver(Unknown Source:3)
01-17 17:40:01.407  2095  3054 W System.err:     at miui.util.TipCloseScreen.showToastForPhone(Unknown Source:27)
01-17 17:40:01.407  2095  3054 W System.err:     at android.media.AudioServiceInjector.handleSpeakerChanged(Unknown Source:36)
01-17 17:40:01.407  2095  3054 W System.err:     at com.android.server.audio.AudioService.setSpeakerphoneOn(Unknown Source:265)
01-17 17:40:01.407  2095  3054 W System.err:     at android.media.AudioManager.setSpeakerphoneOn(Unknown Source:42)
01-17 17:40:01.407  2095  3054 W System.err:     at com.android.server.telecom.CallAudioRouteStateMachine.setSpeakerphoneOn(Unknown Source:17)
01-17 17:40:01.407  2095  3054 W System.err:     at com.android.server.telecom.CallAudioRouteStateMachine.access$1100(Unknown Source:0)
01-17 17:40:01.407  2095  3054 W System.err:     at com.android.server.telecom.CallAudioRouteStateMachine$ActiveEarpieceRoute.enter(Unknown Source:6)
01-17 17:40:01.407  2095  3054 W System.err:     at com.android.internal.util.StateMachine$SmHandler.invokeEnterMethods(Unknown Source:52)
01-17 17:40:01.407  2095  3054 W System.err:     at com.android.internal.util.StateMachine$SmHandler.performTransitions(Unknown Source:106)
01-17 17:40:01.407  2095  3054 W System.err:     at com.android.internal.util.StateMachine$SmHandler.handleMessage(Unknown Source:116)
01-17 17:40:01.407  2095  3054 W System.err:     at android.os.Handler.dispatchMessage(Unknown Source:19)
01-17 17:40:01.407  2095  3054 W System.err:     at android.os.Looper.loop(Unknown Source:249)
01-17 17:40:01.407  2095  3054 W System.err:     at android.os.HandlerThread.run(Unknown Source:28)

or maybe

01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> send_voice_cal, acdb_rx = 7, acdb_tx = 41, feature_set = 0
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> send_voice_rx_topology
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_VOCPROC_COMMON_TOPOLOGY_ID
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_TARGET_SPECIFIC_DEVICE_INFO
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> ACDB_CHANNEL_MAPPING_CONFIG_V2: GET_DEVICE_PROPERTY
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> send_voice_tx_topology
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_VOCPROC_COMMON_TOPOLOGY_ID
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_TARGET_SPECIFIC_DEVICE_INFO
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> ACDB_CHANNEL_MAPPING_CONFIG_V2: GET_DEVICE_PROPERTY
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> AUDIO_SET_SIDETONE_IIR_CAL
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_AFE_DATA
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> AUDIO_SET_SIDETONE_CAL
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> send_voice_columns, rxacdb_id 7, txacdb_id 41, table 8
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_VOC_COLUMNS_INFO_V2
01-17 17:40:01.811   713  2206 D ACDB-LOADER: ACDB -> ACDB_CMD_GET_VOC_PROC_STATIC_TABLE_SIZE
01-17 17:40:01.811   713  2206 D android.hardware.audio.service: ACDBFILE_MGR: Property for the pid 000133B7 not found
01-17 17:40:01.811   713  2206 D android.hardware.audio.service: [Data Manager] -> Failed to fetch the property info for pid 000133B7

 

[usernamexiaomieu]

There is another logcat log .txt with a screenrecord video .mp4 and a call recording .mp3. This time call recording is started manually by tapping the option during the call.