yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] boldbeast:
1. Please confirm you have installed the CallRecordingFix module that is provided in the app.

2. Please use these settings to record calls:

- Record Mode: 1

- Fix Recording Issues - Tune Audio Route: Group1

- Fix Recording Issues - Change Audio Controls: Yes

- Fix Recording Issues - Start Input Stream: Yes

Or use these settings to record calls:

- Record Mode: Alsa

- File Sampling Rate: Auto

- Alsa Device: Device0

- Alsa Bits: 16 Bits

- Alsa Channels: Auto

- Alsa Sampling Rate: Auto

- Fix Recording Issues - Change Audio Controls: Yes

- Fix Recording Issues - Start Input Stream: Yes
[Android Apps and Games] drjat:
Hi [MENTION=6106307]boldbeast[/MENTION] I have Pro version of this app on my Oneplus 5 running Oxygen OS Pie 9.0.5 with Magisk Root (and xXx CUSTOM Magisk ROM). My ROM has the option of systemizing apps - so Boldbeast app can be converted into a system app.

My question: If Boldbeast was a system app:

1. Will there be any problems?

2. Will it still require persistent notification?
[Android Apps and Games] boldbeast:
When Boldbeast Recorder starts up it needs to load several native library files inside the app. If you systemizing the app, the app may fail to load the library files. In this case please copy the 3 library files libboldbeast.so, libboldbeast_helper.so and libbbmonserver.so

- from the folder apk/lib/armeabi-v7a into the folder /system/lib

- from the folder apk/lib/arm64-v8a into the folder /system/lib64

In theory this will make it working. If it works, in most phones persistent notification is unnecessary.
[Android Apps and Games] vip5912:
I found the solution for the incoming call numbers.

I saw the incoming call as 000000 despite the fact that CR app had call log read permission on.

I started Setup - Privacy - Trust - Privacy Protection and change BoldBeast Call log read right (not used) from Ask to Allow.

And now I can see the call number in the CR app. :good:
[Android Apps and Games] boldbeast:
About the telephone number and contact name problem please see [007] in this page http://www.boldbeast.com/android/call_recorder_troubleshooting.html to know more details.
[Android Apps and Games] vip5912:
I installed the app from the official website.

The app has the permissions:

android.permission.PROCESS_OUTGOING_CALLS

android.permission.READ_CALL_LOG

The both permissions are on in app info.

But in the Privacy Protection I can see:

PROCESS_OUTGOING_CALLS allow

READ_CALL_LOG ask

I changed last to allow and now I have the call records with right call number and name!
[Android Apps and Games] sjamie:
I am running a custom Pie AOSP Rom (Codename Phoenix) on my OnePlus 5. I am able to get both sides of bluetooth calls recorded using the Call Recording Fix magisk module but there is a crackling sound in my recordings. I've been trying different recording modes but haven't found one that eliminates that crackling sound. Any suggestions?
[Android Apps and Games] boldbeast:
What kind of crackling sound? Please try to change "Call Settings - File Sampling Rate" to 16000 and 8000 and test again. Is there any difference?
[Android Apps and Games] str8str:
Just to advise I'm on newest firmware and Android 9 on a one plus 5, custom rom. Using stock settings with root enabled, record mode 14, no magisk module tho I do have magisk installed. And everything works great. Thanks
[Android Apps and Games] drjat:
What Magisk module?
[Android Apps and Games] sjamie:
Which OP5 custom ROM are you using? Is your voice and the caller's voice recorded at the same volume?
[Android Apps and Games] boldbeast:
Thanks for sharing.
[Android Apps and Games] boldbeast:
The CallRecordingFix module inside Boldbeast Recorder.

Click "Call Settings - Fix Recording Issues - Install CallRecordingFix Module" inside the app to show the folder in which the module is saved, then use Magisk Manager to install it.

Some third-party ROMs can't record the caller's voice even if you grant root access to a popular recorder, the CallRecordingFix module can fix them perfectly. This module can fix call recording problems for almost all phones in the market.
[Android Apps and Games] cimdrap:
I'm on whyred (redmi note 5) with Havoc Rom (aosp custom rom). I purchased Boldbeast and never regret.

I use root option, everything works, but since i use Bluetooth earbuds it's happening strange and random things:

- i can't get the call recorder working at all

- sometimes works but the records are metallic and very slow (not understandable)

- Google assistant doesn't hear commands (i don't use voice match)

- it keeps not working even after unpairing my bluetooth devices untill some time when it works again, but i never got when and why precisely.

I'm ready to pass to miui again if it would help... Could it be Rom related or changing Rom is useless?
[Android Apps and Games] peterlee928:
hi all, big fan of this app! one question - does it work on android q beta v4? i used it regularly on 9.0.0 june update, but doesnt seem to work on q. much thanks in advance!
[Android Apps and Games] boldbeast:
i can't get the call recorder working at all

=> From you log files, I saw your calls were saved successfully, for example the call at 2019-07-04 10:11:18.

sometimes works but the records are metallic and very slow (not understandable)

=> This is because you were using wrong sampling rate to record calls. Please change following settings in Boldbeast Recorder to make recordings crystal clear:

Call Settings - Alsa Sampling Rate: test 8000 and 16000

Call Settings - File Sampling Rate: Auto

Google assistant doesn't hear commands (i don't use voice match)

=> This has nothing to do with Boldbeast Recorder. This is related to the ROM, or Google assistant settings maybe.

it keeps not working even after unpairing my bluetooth devices untill some time when it works again, but i never got when and why precisely.

=> You should uninstall all other recorders in your phone. And you should disable OK Google. Why? Please see [001] in this page http://www.boldbeast.com/android/call_recorder_troubleshooting.html to know the reason.

I'm ready to pass to miui again if it would help... Could it be Rom related or changing Rom is useless?

=> ROM matters.
[Android Apps and Games] boldbeast:
The new version of Android changed something inside. We need to change Boldbeast Recorder accordingly.

At this moment we are changing the app. Android Q will be supported soon.

UPDATE

We have just released the new version of Boldbeast Recorder V12.5, now Android Q is supported.

Google Play may need time to publish it. If at this moment the new version is unavailable in your area please download it from our web site: https://www.boldbeast.com/android/call_recorder.html
[Android Apps and Games] peterlee928:
fantastic, thanks! will i need to be rooted to use boldbeast on android q?
[Android Apps and Games] boldbeast:
In some countries in some phones the call recording feature is enabled, no root needed, Boldbeast Recorder works good. However if the call recording feature is disabled by the manufacturer, you'll find all recorders in the market work bad. In this case you should root the phone, then Boldbeast Recorder can fix it perfectly.
[Android Apps and Games] sjamie:
For me, the settings above work great for recording calls when not using Bluetooth.

Is anyone using OxygenOS 9.0.7 (pie) on a OnePlus 5 and is able to record calls over Bluetooth successfully? If so, please share your specific settings. Thanks!
[Android Apps and Games] boldbeast:
If you have rooted the phone, please enable the option "Call Settings - Fix Recording Issues - Change Audio Controls" in Boldbeast Recorder, it can fix the bluetooth problem at once.

At first please confirm you are using the latest version (currently V12.6) of Boldbeast Recorder.
[Android Apps and Games] sjamie:
Yes, I did all of that and was using V12.6 from the Play Store. Once I uninstalled that version and installed the version on the Boldbeast website, it is now recording both sides of Bluetooth calls. My voice is a bit louder than the other person's voice but I can live with that. Thanks for creating this awesome app!

Device: OnePlus 5

ROM: OxygenOS 9.0.7 (powered by xXx NoLimits Magisk Mod)

Here are my current Boldbeast settings:

- Record Mode 1

- Fix Recording Issues

- Tune Audio Route: Group 3

- Enabled Root Options

- Change Audio Controls

- Installed CallRecordingFix Module
[Android Apps and Games] drjat:
Where can I find recommended settings for Oneplus 5 running Oxygen OS Pie with Magisk and Boldbeast PRO version.

I want to record in Automatic mode.

I currently have default settings with ASLA mode and the Magisk Module - but I get failed recording messages on Car Bluetooth. Also - sometimes when the call is very short (1-2 seconds) - my phone hangs (screen unresponsive) and I have to press/hold power button for a long time to reboot. This does not happen when Auto call recording is off
[Android Apps and Games] boldbeast:
1. Please use these settings to record calls:

- Record Mode: Alsa

- File Sampling Rate: Auto

- Alsa Device: Alsa Device0

- Alsa Bits: 16 Bits

- Alsa Channels: Auto

- Alsa Sampling Rate: Auto

- Fix Recording Issues - Change Audio Controls: Yes

- Fix Recording Issues - Start Input Stream: No (Yes, some third-party ROMs)

2. If you get failed recording messages, most possibly you are using OK Google that blocks Boldbeast Recorder working. Please disable OK Google. See [001] in this page http://www.boldbeast.com/android/call_recorder_troubleshooting.html to know how to do it.

3. You said your phone hangs (screen unresponsive), other Oneplus 5 users don't have this problem. Please check other apps in your phone that may be related. Send log files to me if needed, let me help you find the reason.
[Android Apps and Games] sjamie:
I experienced all of the above when I used the same settings. Below are the settings which ultimately worked for me.

Device: OnePlus 5

ROM: OxygenOS 9.0.7 (powered by xXx NoLimits Magisk Mod)

Here are my current Boldbeast settings:

- Record Mode 1

- Fix Recording Issues

- Tune Audio Route: Group 3

- Enabled Root Options

- Change Audio Controls

- Installed CallRecordingFix Module
[Android Apps and Games] JDubbed:
I tried your first method and even though the voices were clear on both ends there was loud popping sounds and I had echoing from my voice. This was same problem with phone and Bluetooth headset.

I tried the Alsa method and it works almost perfectly with the phone with minor static but with Bluetooth headset the guests and my voice are sped up 2x with a lot of missed words.

I am needing to record both directions on handset and Bluetooth. Based on the information above can you recommend I try another method?

Thank you!
[Android Apps and Games] boldbeast:
Please try to change following settings:

Alsa Channels: 2 Channels

Alsa Sampling Rate: test 8000 and 16000

How about it now?
[Android Apps and Games] drjat:
These settings are working well for me as well. [MENTION=4204995]sjamie[/MENTION] what happens when you hang up within 1-2 seconds of call answering? (in auto record mode). My phone gets snail slow to unresponsive and I have to reboot. We both have same device, ROM and setup etc - hence asking you directly. Thanks
[Android Apps and Games] sjamie:
I have also experienced that exact behavior when I was testing different settings. I have my device set to manually record calls so I currently do not experience the situation you described.
[Android Apps and Games] JDubbed:
With those two settings on both handset and Bluetooth both my voice and guest voice keep tripping over ourselves like a computer going hay wire. What else you got? ?
[Android Apps and Games] boldbeast:
Obviously your ROM has bugs inside. It can't resample audio correctly.

Please try to change "Alsa Channels" and "Alsa Sampling Rate" to other combinations, until you find one of them crystal clear.
[Android Apps and Games] JDubbed:
The ROM on the Razer Phone 2 is factory. So if your saying the Razer Phone 2 ROM is buggy then I guess that applies to all Razer Phone 2's. I'll keep playing around with it. I cannot imagine I am the only one using Boldbeast on a Razer Phone 2. Has anyone else reported any feedback on their settings?

Oh and btw I did get a prompt today from Boldbeast that the call recorder fix was outdated. It was v1230 and I updated to v1260. Maybe that will fix it. I remember updating Boldbeast maybe a month ago and am just now getting a prompt that the module is outdated. If you think of anything else please let me know. Otherwise I'll just keep trying different settings until my ears bleed.
[Android Apps and Games] JDubbed:
I have a near perfect setup. I added the file sampling rate of 1600 to the below setup you sent me and that seems to support both headset and Bluetooth with very little popping or static sounds.

However I have found a very odd reoccurring issue that I can replicate every time. If I make a call using the headset and end it, then connect my Bluetooth and make another call and then end it, and then make a another phone call on my headset that recording will be 2x slow and will sound like a robot. But then if I make a 4th phone call using the headset the recording goes back to normal and sounds great. So for some reason when I make a phone call after switching from Bluetooth to headset, the next phone call will have a 2x slower recording and then will fix itself by making another call. It's as if something isn't switching back to normal operation after switching from Bluetooth to headset but then it gets fixed after making a phone call. And since I am constantly switching from headset to Bluetooth that can be a problem. Any suggestions on why this might occur? Or maybe now that I have a practically flawless setup and got the configuration down right, now all we got to do is solve for this weird problem. Any advice to fix this would be appreciated.

2. Please use these settings to record calls:

- Record Mode: 1

- Fix Recording Issues - Tune Audio Route: Group1

- Fix Recording Issues - Change Audio Controls: Yes

- Fix Recording Issues - Start Input Stream: Yes

Added: File sampling rate 1600
[Android Apps and Games] sjamie:
On my OnePlus 5 running OOS 9.0.7, I was using the following settings which works successfully:

- Record Mode 1

- Fix Recording Issues - Tune Audio Route: Group 3

- Fix Recording Issues - Enabled Root Options

- Fix Recording Issues - Change Audio Controls (yes)

- Installed CallRecordingFix Module

Just out of curiosity, I tried your settings mentioned above which also works successfully:

- Record Mode: 1

- Fix Recording Issues - Tune Audio Route: Group1

- Fix Recording Issues - Change Audio Controls: Yes

- Fix Recording Issues - Start Input Stream: Yes

I could NOT get these settings below to record at all. I received error messages to change Alsa Device and/or to change the record mode:

- Record Mode: Alsa

- File Sampling Rate: Auto

- Alsa Device: Device0

- Alsa Bits: 16 Bits

- Alsa Channels: Auto

- Alsa Sampling Rate: Auto

- Fix Recording Issues - Change Audio Controls: Yes

- Fix Recording Issues - Start Input Stream: Yes

Hopefully, this post will help other OnePlus 5 users.
[Android Apps and Games] boldbeast:
You described the situation very clear. Yes, I also believe the ROM forgot "switching back to normal operation after switching from Bluetooth to headset" that it should do. Next time when you make a new call the ROM will "initialize" the related states so the problem will be fixed. Because the problem is in the ROM, I'm afraid there is no good solution from third-parties.

You said "I guess the problem applies to all Razer Phone 2 users." Undoubtedly it does.
[Android Apps and Games] boldbeast:
This is because you enabled OK Google that blocked Boldbeast Recorder working.

If you disable OK Google these settings work at once. Please see [001] in this page http://www.boldbeast.com/android/call_recorder_troubleshooting.html to know how to disable OK Google.
[Android Apps and Games] sjamie:
Oh... but I like using OK Google and it works with the settings I posted. :laugh:

Do you think using the Alsa settings you posted creates a better sounding recording?
[Android Apps and Games] boldbeast:
I don't think the Alsa settings have a better sounding recording.

Some phones have bugs in the ROM (specially in AudioServer). The Alsa engine doesn't depend on AudioServer, so it can bypass many bugs in the ROM. By providing the Alsa engine Boldbeast Recorder supports more phones. If your phone doesn't have bugs in AudioServer you can use any settings that work good.

The latest OK Google is very smart. When Boldbeast Recorder starts recording via AudioServer, OK Google will stop working itself to release occupied resources to allow the recorder doing its job. When the recorder stops recording OK Google will work again. However if the recorder starts recording via the Alsa engine OK Google will not stop working itself to release occupied resources, as a result the recorder fails to start recording. This is the reason why you should disable OK Google when you are using the Alsa record mode.
[Android Apps and Games] TogoFire:
bug camera

All cameras on my Mi A2 lite (daisy) device stop working when installing the "CallRecordingFix_Magisk_Install" module.
[Android Apps and Games] boldbeast:
In your log file:

F/DEBUG (11421): SuperiorOS Version: 'SuperiorOS-Nemesis-daisy-OFFICIAL-20190808-1620'

F/DEBUG (11421): Build fingerprint: 'google/walleye/walleye:9/PQ3A.190605.003/5524043:user/release-keys'

F/DEBUG (11421): Revision: '0'

F/DEBUG (11421): ABI: 'arm'

F/DEBUG (11421): pid: 10949, tid: 11403, name: C3Dev-0-ReqQueu >>> /system/bin/cameraserver <<<

F/DEBUG (11421): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------

F/DEBUG (11421): Abort message: 'gralloc-mapper is missing'

F/DEBUG (11421): r0 00000000 r1 00002c8b r2 00000006 r3 00000008

F/DEBUG (11421): r4 00002ac5 r5 00002c8b r6 f0c7f184 r7 0000010c

F/DEBUG (11421): r8 f1024078 r9 00000001 r10 f0c7f7a0 r11 00000023

F/DEBUG (11421): ip f2e75149 sp f0c7f170 lr f26e7089 pc f26def2a

F/DEBUG (11421):

F/DEBUG (11421): backtrace:

F/DEBUG (11421): #00 pc 0001cf2a /system/lib/libc.so (abort+58)

F/DEBUG (11421): #01 pc 00006ccd /system/lib/liblog.so (__android_log_assert+156)

F/DEBUG (11421): #02 pc 00011211 /system/lib/libui.so (android::Gralloc2::Mapper::Mapper()+280)

F/DEBUG (11421): #03 pc 000139bf /system/lib/libui.so (android::GraphicBufferMapper::GraphicBufferMapper()+10)

F/DEBUG (11421): #04 pc 00011f97 /system/lib/libui.so (android::GraphicBuffer::GraphicBuffer()+98)

F/DEBUG (11421): #05 pc 0004c5d5 /system/lib/libgui.so (android::BpGraphicBufferProducer::requestBuffer(int, android::sp<android::GraphicBuffer>*)+96)

F/DEBUG (11421): #06 pc 00058445 /system/lib/libgui.so (android::Surface::dequeueBuffer(ANativeWindowBuffer**, int*)+548)

F/DEBUG (11421): #07 pc 000cf19b /system/lib/libcameraservice.so (android::camera3::Camera3OutputStream::getBufferLockedCommon(ANativeWindowBuffer**, int*)+370)

F/DEBUG (11421): #08 pc 000cef9b /system/lib/libcameraservice.so (android::camera3::Camera3OutputStream::getBufferLocked(camera3_stream_buffer*, std::__1::vector<unsigned int, std::__1::allocator<unsigned int>> const&)+58)

F/DEBUG (11421): #09 pc 000cc287 /system/lib/libcameraservice.so (android::camera3::Camera3Stream::getBuffer(camera3_stream_buffer*, long long, std::__1::vector<unsigned int, std::__1::allocator<unsigned int>> const&)+394)

F/DEBUG (11421): #10 pc 000c7057 /system/lib/libcameraservice.so (android::Camera3Device::RequestThread::prepareHalRequests()+974)

F/DEBUG (11421): #11 pc 000c6799 /system/lib/libcameraservice.so (android::Camera3Device::RequestThread::threadLoop()+424)

F/DEBUG (11421): #12 pc 0000c087 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+166)

F/DEBUG (11421): #13 pc 000641e9 /system/lib/libc.so (__pthread_start(void*)+22)

F/DEBUG (11421): #14 pc 0001e0ed /system/lib/libc.so (__start_thread+24)

It's very clear the "cameraserver" in your phone crashed itself. It has nothing to do with the "CallRecordingFix_Magisk_Install" module.

Even if you uninstall the "CallRecordingFix_Magisk_Install" module, you'll find the problem is still there.
[Android Apps and Games] TogoFire:
Okay. Thx

Boldbeast work good in root mod no need module. I just find it strange that the module bugs cameras lol. This happens in any ROM that exists for daisy.

One thing I miss so much is that this recorder does not display the recorded number or the person's name according to the contacts.
[Android Apps and Games] boldbeast:
Please see [007] in this page http://www.boldbeast.com/android/call_recorder_troubleshooting.html to know the reason and the solution.
[Android Apps and Games] mumfordfan:
Anyone know the settings for the Mi 9t pro, recorder starts but won't record the other side of the line.
[Android Apps and Games] boldbeast:
Please click "Set Default Settings" in Boldbeast Recorder. If it works good that's OK. If it doesn't work you should root the phone to fix it, because all recorders in the market surely don't work either in this case.
[Android Apps and Games] lymbra:
Hey

I were using this app for a long time without any problems. But since a rom update, it tells me to change the alsa-device.

I tried all of them, without any success

phone: Mi Mix 3 with EvoX 2.1 Rom, rooted.

which further information do you need for assistant?

thanks a lot!
[Android Apps and Games] boldbeast:
Please set "Alsa Device" to Device0, then test again.

At first please confirm you have disabled OK Google. See [001] in this page http://www.boldbeast.com/android/call_recorder_troubleshooting.html to know how to disable it.

If the problem is still there, please click "Call Settings - Fix Recording Issues - Ask New Parameters" in Boldbeast Recorder to send log files to me, let me have a look at them and see what happened in your phone.
[Android Apps and Games] Dany XP:
Does anybody know right parameters for Moto Z2 Force in Lineage 16?
[Android Apps and Games] boldbeast:
In Boldbeast Recorder please use these settings to record calls:

- Record Mode: 1

- Fix Recording Issues - Tune Audio Route: Group1

- Fix Recording Issues - Change Audio Controls: Yes

- Fix Recording Issues - Start Input Stream: Yes

If it can't record the caller's voice, please

- Open Boldbeast Recorder, tap the item "Call Settings - Fix Recording Issues - Install CallRecordingFix Module", it will display the folder name in which the CallRecordingFix module is saved.

- Open Magisk Manager, tap the top-left icon, tap Modules, tap the bottom-center "+" icon to install the CallRecordingFix module.

- Power off then power on the phone.

Now you should get crystal clear call recordings.
[Android Apps and Games] Dany XP:
Thank u, it worked! All I needed was just:

Record Mode: 1

- Fix Recording Issues - Tune Audio Route: Group1

- Fix Recording Issues - Change Audio Controls: Yes

- Fix Recording Issues - Start Input Stream: Yes

No need for magisk modules (had it installed anyway...)

Thank u!

EDIT: i spoke too soon.

After the first test call successful recorded, now all recordings are in "slow motion".... What can I do?

EDIT 2: I had to install Magisk module for fixin the " slow mode" recordings, after all...all good now
[Android Apps and Games] ranaxda200:
I'm on android Q OnePlus 3t on msm extended custom rom. Built-in recorder saved files won't play at all. Using rooted option boldbeast showing error that I'm using double recording apps. How to fix this issue!??
[Android Apps and Games] boldbeast:
Please confirm you have uninstalled all other recorders at first, then test again.
[Android Apps and Games] DHorseman:
I'm using HTC u11 with Magisk v20.1. When I press Enable Rooted Options, the grand popup doesn't show, so I can't grant root permission
[Android Apps and Games] boldbeast:
Please confirm you are using the latest version of Boldbeast Recorder, and try again. It should work.
[Android Apps and Games] DHorseman:
I think problems come from my phone. I trying to reset my phone and try again. Thanks you ?
[Android Apps and Games] psvod:
Hello! What settings do you recommend for the smartphone Huawei Mate 30 Pro? Thanks!