The recording was discarded because the audio was completely silent. This device might not support recording calls associated with the 'com.android.phone' app.

[idklevi]

using qpr2 based aosp rom

[chenxiaolong]

Are you on a Google Pixel device? If not, there's probably not much you can do to make it work. On non-Pixel devices, call recording usually only works on ROMs that are based on the device's stock ROM.

[idklevi]

Are you on a Google Pixel device? If not, there's probably not much you can do to make it work. On non-Pixel devices, call recording usually only works on ROMs that are based on the device's stock ROM.

no.. I'm using a Xiaomi phone with project elixir custom rom installed in. Apparently BCR worked fine for me in multiple roms including elixir but as soon as I updated the aosp qpr2 update , this message shows up. The rom devs told me this issue is common for qpr2 update roms and the only way to fix this issue is to wait for the BCR release that supports qpr2. That's why I thought of mentioning this hoping there would be an update for BCR.

[chenxiaolong]

I'd suggest changing the output format to WAV/PCM and the sample rate to 48000 Hz. If that also doesn't work, then it's a ROM issue. With those settings, the recorded audio is byte-for-byte exactly what Android sent to BCR.

(BCR is already compatible with QPR2. QPR2 had a huge number of changes and is closer to Android 15 Beta than 14, but those changes don't impact BCR.)

[TomerGadol]

I also have this issues after updating ROM. On previous EvolutionX (which had BCR installed by default) recording was working fine. Now on latest Derpfest (qpr2) I get the same error. Tried the above settings of WAV/PCM at 48000Hz but still silent. My device is Xiaomi Mi 9T.

[TL431]

I'd suggest changing the output format to WAV/PCM and the sample rate to 48000 Hz. If that also doesn't work, then it's a ROM issue. With those settings, the recorded audio is byte-for-byte exactly what Android sent to BCR.

(BCR is already compatible with QPR2. QPR2 had a huge number of changes and is closer to Android 15 Beta than 14, but those changes don't impact BCR.)

Commenting to this issue because I had the same problem of OP on my Xperia 10 IV device with Android 14. Changing the output format to WAV/PCM at 48kHz worked.

[ask9027]

i am using AwakenOS , after installing BCR with KernelSU,
call recording is silent.
hiw to fix this?
20240428_160640.166+0530_out_198.log.txt

[heyitsj0n]

Are you on a Google Pixel device? If not, there's probably not much you can do to make it work. On non-Pixel devices, call recording usually only works on ROMs that are based on the device's stock ROM.

I am a Pixel 6 Pro user and have this issue for the 1st time after updating to latest release.

[Cheetoacidosis]

I'm having this issue on a Pixel 3 running LineageOS 21 (Android 14). I was able to get recordings working using the WAV/PCM at 48kHz workaround

EDIT: Now the default works too! No clue why

[Naushikha]

Yeah this was weird,

• first try (after installation); it failed
• searched through the issues and came up on this thread
• then I switched to WAV/PCM since it's a recommended solution
• awesome, recording works now! but the file size is too damn big
• out of curiosity, switched back to default OGG
• still works!

How though? o.O

btw my specs:

• Pixel 5 with LineageOS 21 + Magisk 27
• Flashed NikGapps Pixel Basic Package (which includes the Google Dialer: com.google.android.dialer v129.0.628891516)
• Flashed NikGapps Pixel Specifics Addon (Pixel Launcher + Other goodies)

[9vvk]

+1
essential ph-1, LineageOS 21, Magisk 27

20240521_181319.272+0300_in_tel_num.log.txt

[RunasSudo]

Had the same issue and very surprised to find I could reproduce the fix. After changing from WAV/PCM to OGG and recordings working correctly, changing to FLAC also works.

Specs:

• Pixel 8
• Stock Android 14, build AP1A.240405.002.B1
• Magisk 27.0 (27000)
• BCR 1.63 flashed as Magisk module

[ask9027]

install apk as normal install, then flash zip in magisk or KernelSU,
it will work.

[LuminarySage]

I'd suggest changing the output format to WAV/PCM and the sample rate to 48000 Hz. If that also doesn't work, then it's a ROM issue. With those settings, the recorded audio is byte-for-byte exactly what Android sent to BCR.

(BCR is already compatible with QPR2. QPR2 had a huge number of changes and is closer to Android 15 Beta than 14, but those changes don't impact BCR.)

I just installed qpr3 on my stock pixel and I'm getting the same error despite bcr working just fine before

[tommy1735]

just want to say thanks to chenxiaolong, change to WAV worked for me, phone is a xiaomi redmi note 9s with lineage OS 14 useing magisk

[Asunix666]

For me, neither above fixes worked. I'm on NUBIA REDMAGIC 9 Pro android 14 stock firmware. Since 2024.07.19 update, the app is broken. Please find a solution. I use this for years. Others don't have noise cancelation.

[Hellsingoff]

Same here. Redmi Note 10 Pro.
crDroid 9 (android 13), bcr 1.37 - worked fine.
Update to crDroid 10 (Android 14), bcr 1.66 - didnt work, "completely silent record" error
Rollback to crDroid 9 (Android 13), bcr 1.66 - same error
With wav/48khz settings - works.

Tomorrow i'll try update to crDroid 10 again and set same settings there

[mokurin000]

With Official LineageOS 21 on my kebab (oneplus 8T), switching to WAV/48kHz doesn't solve this problem.

20240728_015125.31+0800_out_10010.log.txt

[PKutok]

With official LineageOS 21, Android 14, without google on my Kebab (oneplus 8T) switching to WAV/48kHz does not solve this problem.
Version 1.57 saves the call recording, but there is only silence for 1-5 seconds.
Versions 1.60; 1.63; 1.65; 1.66; 1.67 do not save the call recording!

[mokurin000]

With official LineageOS 21, Android 14, without google on my Kebab (oneplus 8T) switching to WAV/48kHz does not solve this problem. Version 1.57 saves the call recording, but there is only silence for 1-5 seconds. Versions 1.60; 1.63; 1.65; 1.66; 1.67 do not save the call recording!

1.59 works fine
1.63 desn't works
so maybe the issue was introduced in 1.60

[PKutok]

Version 1.59 works poorly - saves, but does not play.
The problems began after the LineageOS update, July 19 and July 27.
Before that, BCR version 1.65 worked fine.

[PKutok]

After the August 2 update LineageOS 21, Android 14, OnePlus 8T and BCR update to version 1.69 - the call recording began to be saved. This happened after the second attempt.

[Asunix666]

Still nothing for me with NUBIA REDMAGIC 9 Pro android 14 stock firmware. 2024.07.19 update.

[mikelpr]

This happens to me on a Pixel 8 Pro on 14 AP2A.240605.024

EDIT: apparently in my case was happening because I was dialing a number which I have in my contacts and I had only set the Unknown numbers role, but then I don't know why I was getting the notification that it was recording and then the failure notification

[ztmzzz]

On my Pixel 8 Pro AP2A.240805 version, changing to WAV/48kHz works for me. After successfully recording a call, changing to FLAC also works.

[desson-ctrl]

Hey folks, I got it to work on my phone after trying several versions and several output formats. The fix for me was to turn off the "Record calls before connection" switch.

Now working with crDroid 9.18 android version 13 bcr ver 1.69 any of the output formats.

[robertio]

Still nothing for me with NUBIA REDMAGIC 9 Pro android 14 stock firmware. 2024.07.19 update.

Same here. Upgrade from EU 9.0.11 to REDMAGICOS9.0.13_NX769J_EEA BCR stopped working with this message.
None of the advises in this thread (changing output format, remove google assistant and so on) - helps.

@Asunix666 - do you also are on REDMAGICOS EU rom? or global? - i try to identify which version causes problem.

[Asunix666]

Still nothing for me with NUBIA REDMAGIC 9 Pro android 14 stock firmware. 2024.07.19 update.

Same here. Upgrade from EU 9.0.11 to REDMAGICOS9.0.13_NX769J_EEA BCR stopped working with this message. None of the advises in this thread (changing output format, remove google assistant and so on) - helps.

@Asunix666 - do you also are on REDMAGICOS EU rom? or global? - i try to identify which version causes problem.

EU rom OS9.0.13. Soon i'll downgrade using Official FOTA Packages Collection. Need to backup 400gb before that

[DoSpamu]

Same on Pixel 8 Pro AP2A.240605.024
I switched to WAV 48kHz - Working
And back to OGG but 48kHz not default 16kHz - working
On default settings was this error

[chenxiaolong]

Yep, the audio drivers on Pixel devices are a bit buggy. The first recording after a reboot will usually never work, but all subsequent ones will. There shouldn't be a need to change any settings. A quick workaround is to call voicemail and then hang up after a reboot.

[sspphheerraa]

LineageOS-21-20240912 (Android 14), Magisk 27.0, BCR-1.70
None of mentioned workarounds is helped.

[Ajax9039]

LineageOS-21-20240912 (Android 14), Magisk 27.0, BCR-1.70
None of mentioned workarounds is helped.

If you have to Google assistance or Gemini app installed try deactivateing the "hey Google" future.

[sspphheerraa]

LineageOS-21-20240912 (Android 14), Magisk 27.0, BCR-1.70
None of mentioned workarounds is helped.

If you have to Google assistance or Gemini app installed try deactivateing the "hey Google" future.

I didn't install Gemini, and I don't use Google assistant. Today update to BCR-1.71, no changes.

[sspphheerraa]

Clear Lineage-21.0-20241017 (Android 14), no gapps (!) installed, Magisk 28.0, BCR-1.72
Call recording is working.

Seems like gapps include something that broke call recordings.
I don't know is there way to fix it with gapps installed.

[zokky]

I noticed that recording is not working since I updated the "phone by google" apk. Somehow it seems to me this the apk is causing the problem.

I am using AwakenOS 4.5 on RN10PRO

[zokky]

just reverted "phone by google" apk to original version but it didn't help. There were some other Google apps for updating, but they didn't seem important to me. I will also return them to the original version.
I hope for the best

[zokky]

it turned out that the problem was only the google LLC app or a newer version. When I turn off the google app, call recording works normally

[zokky]

the problem is "hey google" voice control
hope someone will fix this soon

[MadhavMendpara]

I'd suggest changing the output format to WAV/PCM and the sample rate to 48000 Hz. If that also doesn't work, then it's a ROM issue. With those settings, the recorded audio is byte-for-byte exactly what Android sent to BCR.

(BCR is already compatible with QPR2. QPR2 had a huge number of changes and is closer to Android 15 Beta than 14, but those changes don't impact BCR.)

same issue i was facing failed to record call... audio was completely silent...

as @chenxiaolong suggest to use wav/pcm and 48000hz it does solved and now call is being recorded.

i think this is temp solution. i want to use ogg/opus as it is save storage space.

just for info i have used flash zip in recovery method and after that adb pm cmd to install as system app .

[MadhavMendpara]

little update

i have change back to default output format og/opus/48kbps/16khz. now it is working i dont know how but it was not working first time

[chenxiaolong]

i have change back to default output format og/opus/48kbps/16khz. now it is working i dont know how but it was not working first time

If you're on a Google Pixel, the first recording after a reboot will likely fail. It's a driver bug and there's no way I can fix it in BCR.

Other devices may have similar bugs too.

[bagarwa]

Yep, the audio drivers on Pixel devices are a bit buggy. The first recording after a reboot will usually never work, but all subsequent ones will. There shouldn't be a need to change any settings. A quick workaround is to call voicemail and then hang up after a reboot.

This seems to be the case for me too.
Pixel 9 Pro XL, running Android 15 QPR 2 Beta 1, Magisk 28.1.

[Asunix666]

Did recent updates fixed the problem? i'm on NUBIA REDMAGIC 9 Pro android 14 stock firmware. 2024.07.19 update