[Android Apps and Games] boldbeast:
A user said he met exactly the same problem, and he said this problem was made by the Boldbeast Recorder CallRecordingFix module.. Actually, his claim is not right.

Here is his log file:

09-14 08:08:54.560 8089 8089 I crash_dump32: performing dump of process 7169 (target tid = 8074)

09-14 08:08:54.563 8089 8089 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

09-14 08:08:54.563 8089 8089 F DEBUG : Build fingerprint: 'ZUK/z2_plus/z2_plus:7.0/NRD90M/3.1.117_171110:user/release-keys'

09-14 08:08:54.563 8089 8089 F DEBUG : Revision: '0'

09-14 08:08:54.563 8089 8089 F DEBUG : ABI: 'arm'

09-14 08:08:54.563 8089 8089 F DEBUG : pid: 7169, tid: 8074, name: C3Dev-0-ReqQueu >>> /system/bin/cameraserver <<<

09-14 08:08:54.563 8089 8089 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------

09-14 08:08:54.563 8089 8089 F DEBUG : Abort message: 'gralloc-mapper is missing'

09-14 08:08:54.563 8089 8089 F DEBUG : r0 00000000 r1 00001f8a r2 00000006 r3 00000008

09-14 08:08:54.563 8089 8089 F DEBUG : r4 00001c01 r5 00001f8a r6 e837f19c r7 0000010c

09-14 08:08:54.563 8089 8089 F DEBUG : r8 e8bff078 r9 00000001 r10 e837f7b8 r11 00000023

09-14 08:08:54.563 8089 8089 F DEBUG : ip e99bb149 sp e837f188 lr e9beaf99 pc e9be2e3a

09-14 08:08:54.580 8089 8089 F DEBUG :

09-14 08:08:54.580 8089 8089 F DEBUG : backtrace:

09-14 08:08:54.580 8089 8089 F DEBUG : #00 pc 0001ce3a /system/lib/libc.so (abort+58)

09-14 08:08:54.580 8089 8089 F DEBUG : #01 pc 00006ccd /system/lib/liblog.so (__android_log_assert+156)

09-14 08:08:54.580 8089 8089 F DEBUG : #02 pc 00011211 /system/lib/libui.so (android::Gralloc2::Mapper::Mapper()+280)

09-14 08:08:54.580 8089 8089 F DEBUG : #03 pc 000139eb /system/lib/libui.so (android::GraphicBufferMapper::GraphicBufferMapper()+10)

09-14 08:08:54.580 8089 8089 F DEBUG : #04 pc 00011f7f /system/lib/libui.so (android::GraphicBuffer::GraphicBuffer()+98)

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

09-14 08:08:54.580 8089 8089 F DEBUG : #06 pc 00058455 /system/lib/libgui.so (android::Surface::dequeueBuffer(ANativeWindowBuffer**, int*)+548)

09-14 08:08:54.581 8089 8089 F DEBUG : #07 pc 000cd0af /system/lib/libcameraservice.so (android::camera3::Camera3OutputStream::getBufferLockedCommon(ANativeWindowBuffer**, int*)+370)

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

09-14 08:08:54.581 8089 8089 F DEBUG : #09 pc 000ca19d /system/lib/libcameraservice.so (android::camera3::Camera3Stream::getBuffer(camera3_stream_buffer*, std::__1::vector<unsigned int, std::__1::allocator<unsigned int>> const&)+328)

09-14 08:08:54.581 8089 8089 F DEBUG : #10 pc 000c5049 /system/lib/libcameraservice.so (android::Camera3Device::RequestThread::prepareHalRequests()+904)

09-14 08:08:54.581 8089 8089 F DEBUG : #11 pc 000c47d1 /system/lib/libcameraservice.so (android::Camera3Device::RequestThread::threadLoop()+424)

09-14 08:08:54.581 8089 8089 F DEBUG : #12 pc 0000c103 /system/lib/libutils.so (android::Thread::_threadLoop(void*)+290)

09-14 08:08:54.581 8089 8089 F DEBUG : #13 pc 00064219 /system/lib/libc.so (__pthread_start(void*)+22)

09-14 08:08:54.581 8089 8089 F DEBUG : #14 pc 0001dffd /system/lib/libc.so (__start_thread+24)

It's obvious his cameraserver crashed itself. This has nothing to do with the Boldbeast Recorder module.

Even if he uninstall the Boldbeast Recorder module, his cameraserver will still crash without doubt.

And from the log file:

09-14 08:08:54.526 7169 7169 W C3Dev-0-ReqQueu: type=1400 audit(0.0:63): avc: denied { read } for name="/" dev="tmpfs" ino=17050 scontext=u:r:cameraserver:s0 tcontext=u:object_r:vendor_file:s0 tclass=dir permissive=0

Now the real reason of the problem is very clear:

His phone has wrong SELinux policies inside that blocks the cameraserver to do its jobs, therefore the cameraserver "abort" itself.

The Boldbeast Recorder CallRecordingFix module doesn't change any SELinux policies. Maybe other apps wrongly changed it, maybe the ROM wrongly set it. Anyway, after changing SELinux to "Permissive" the problem disappeared at once.

The phone of this user is Lenovo ZUK Z2 Plus. I also checked the log file of a Xiaomi phone used by another user who said he had the same problem. The problem is mode by wrong SELinux policies. Please check your phone, most possibly your phone is the same.