Android 11 - Phone App crashes, phone freezes (Page 1 of 2)

I stopped using this app about a year ago since going to Android 11 because of this.  Pixel 4 XL.  Tried with and without fix module.

I have precisely the same problem:  the phone freezes at the conclusion of any call (in or out), requiring a hard reboot (and then the phone goes into a boot loop if I don't immediately reboot with Power button).  No recording results in the Call List (and I have specified SAF and a Clip Saving folder which exists).  As soon as I disable Rooted Options, the phone reverts to normal behavior (no freeze after calls), but no recording is made in any non-root Record Mode 1-14.  OnePlus 7Pro, Android 11, OOS v11.0.1.1, Magisk v23, BoldBeast v14.7 from the website, Alsa2, no CallFixModule installed, Google Assistant disabled, no Accessibility, no tweaks except Change Audio Controls (which is checked by default), no other recording apps installed (AFAIK).  Under Android 10 BoldBeast worked perfectly, with the same set of apps installed.  I am sending the hardware log to Administrator ...

I have powered off/on and restarted the phone dozens of times; the freezing problem is not solved.

> Instead please check other apps or other Magisk modules that may make your phone reboot or boot loop.

No Magisk modules are installed. I could delete all my apps and start from scratch (which would be very painful), but the fact is, the apps were the same under Android 10. It is difficult to escape the conclusion that Android 11/OOS 11 is the critical difference, and there is some element that v14.7 is unaware of.  Apart from Magisk itself, what app has the authority to "silently kill" the root process of Boldbeast?  According to Magisk, Boldbeast is a Superuser.

I'm emailing a list of installed, enabled third-party packages.  Do you see any conflicting recorder app in this list?

Just updated to new v14.8 (from your website).  Do you want logs before the call, or after the call and the freeze -- because BB is still freezing after every call.  At the moment of freeze, I also get the message "System UI isn't responding" with the choices "Close app" or "Wait".  If I do not respond, phone shuts down.

I've sent you logs after a call+freeze+hard reboot -- because immediately after a call I have no further operability ... so this is the same as "before a call"

About 1 minute after bootup, Magisk notifies "Boldbeast Recorder was granted Superuser rights" -- there is no request for root access, which has already been permanently granted -- i.e. no action for me to take -- I refused nothing.  See screenshots attached with hardware log. Root options are enabled, Alsa2 is enabled.  I make a 30 second call, then terminate that call.  Boldbeast does not turn off the big red button -- it stays lit (NOT the behavior under Android 10!), and the phone is frozen.  No hardware or software buttons respond, except Power+VolumeUp (which shuts down the phone after a long press).  Upon reboot, the "Call List" does not include this call.

Another peculiar thing is that Magisk repeats that "Boldbeast Recorder was granted Superuser rights" when I try to get New Parameters ...

The number I called shortly after 18:00 on 2021-06-11 was +1 805-637-7243.  If you see that call in the logs, then that was with phone freshly rebooted/root options fully enabled/Superuser granted/Alsa2 (per screenshots)/big red button fully lit. If you do not see that call, then we're spinning wheels ...

I followed your instructions to the letter. The phone freezes after the call, with all hard and soft buttons unresponsive (except long press of Power+VolumeUp). Upon reboot, no call is registered in either the Boldbeast Call List or the phone app's History (although the call certainly occurred and everything was normal until I terminated the call, at which point the big red button remained illuminated -- clearly Boldbeast had lost control over the process, reflecting the phone's suddenly frozen state).

The freeze seems to be entirely dependent on whether Rooted Options are enabled or not.  If I *disable* Rooted Options, leaving all other settings the same (Record Mode 12, Accessibility enabled), the phone does NOT freeze, the call is registered in both the Boldbeast Call List and the phone app History.  Played back, my local voice is crystal clear, but the remote voice is muffled and unintelligible.

It would be illuminating to learn the experience of other OOS 11 users under  v14.7 or v14.8 ...

My experience mirrors that of rjh.  The latest solution offered in post #14 does keep the phone from freezing up after the call for me, however it is not recording my side of the conversation either.  I have a rooted OnePlus 7 Pro, running Android 11, Lineage 18.1, Magisk v23, BoldBeast 14.8 (from your site, not the play store).

I did follow your instructions in #14.  Apart from the OnePlus 11/Alsa2 incompatibility, another area where I have been ignorant is Accessibility.  In Settings => System => Accessibility, I set Boldbeast "On".  But there are also additional options in this Accessibility menu, including display of a fourth soft button on the Home/Back/Background Programs row.  If I enable that button, I am then asked whether I want to assign Boldbeast to it (whatever that means).  I tried this, and found that each button press served as a toggle of basic Boldbeast Accessibility, from On to Off to On and et cetera -- a toggle.  So I disabled the button, which now seems to stabilize Boldbeast's basic Accessibility state as "On" (thus only manipulable in Settings), whereas before Bb Accessibility often turned Off seemingly by itself (obviously, I must have touched the soft button unintentionally).  I have no bloody idea what purpose Accessibility serves (and I've been an avid Android user for 10+ years), but anyway ... this instability of On|Off may have been an additional and fundamental problem.

In Record Mode 12, I am now getting listenable calls -- for 2 whole days.  The sound is unusually "spacious", as if recorded in a large room, but it is clear enough. Would other Record Modes work besides 12 and yield different results?  Because there is no description of the technical parameters/purposes of each Mode (or of things like Change Audio Controls or CallRecordingFix Module or Tune Audio Effect), trying each one individually is like shooting ducks in the dark -- and quite time-consuming, given the exponential number of variables.  (I could examine the code, but I don't know where to locate it.)

Thank you for sticking with this learning process to a satisfactory conclusion.  Frustrating for both of us.  I really appreciate it.

I choose for step 3 in post 20, Accessibility is enabled, callrecordingfix module installed and enabled after a reboot. in recording mode 12, tune audio route group 1 is selected and change audio controls is checked.  The phone is still not getting my side of the audio.  I made three phone calls to test.  On the third one, i turned off my bluetooth before the call, just to make sure it wasn't interfering.  I'll try the second option later today (using alsa, no ok google (which i don't use anyway) and let see if that works for me. I sent my log files too in case that helps.

Alaa works for me.