Hello
I have been having On and off problems with the call recording feature. Unfortunately, sometimes the call recording crashes.
I have Pixel 9 Pro version: 2025110800
I have the logs of the crash.
`type: crash
osVersion: google/caiman/caiman:16/BP2A.250805.005/2025110801:user/release-keys
uid: 1041 (u:r:hal_audio_default:s0)
cmdline: /vendor/bin/hw/android.hardware.audio.service-aidl.aoc
processUptime: 0s
signal: 35 (<debuggerd signal>), code -1 (SI_QUEUE), senderUid 1041
threadName: binder:811_2
MTE: enabled
backtrace:
/apex/com.android.runtime/lib64/bionic/libc.so (ioctl+12, pc e980c)
/apex/com.android.runtime/lib64/bionic/libc.so (ioctl+160, pc 885d0)
/system/lib64/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+216, pc 51248)
/system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+152, pc 557c8)
/vendor/bin/hw/android.hardware.audio.service-aidl.aoc (main+1772, pc 9156c)
/apex/com.android.runtime/lib64/bionic/libc.so (libc_init+124, pc 7450c)`
And
`type: crash
osVersion: google/caiman/caiman:16/BP2A.250805.005/2025110801:user/release-keys
uid: 1041 (u:r:audioserver:s0)
cmdline: /system/bin/audioserver
processUptime: 0s
abortMessage: TimeCheck timeout for IAudioFlinger::getInputFramesLost scheduled 09:56:22.735 on thread 12796
Timeout ms 5000.00 (3000.00 + 2000.00) elapsed steady ms 5000.7314 elapsed system ms 5000.7412
HAL pids [ 811 ]
now 09:56:28.824
secondChanceCount 2
analysis [ ]
timeout [ { IAudioFlinger::getInputFramesLost scheduled 09:56:22.735 deadline :25.735 tid 12796 } ]
pending [ ]
retired [ { IAudioFlinger::getInputFramesLost scheduled 09:56:22.649 deadline :25.649 tid 28716 } { IAudioFlinger::getInputFramesLost scheduled 09:56:22.670 deadline :25.670 tid 28716 } { IAudioFlinger::getInputFramesLost scheduled 09:56:22.692 deadline :25.692 tid 28716 } { IAudioFlinger::getInputFramesLost scheduled 09:56:22.692 deadline :25.692 tid 12796 } ]
timeout(12796) callstack [
#00 pc 00000000000e980c /apex/com.android.runtime/lib64/bionic/libc.so (ioctl+12) (BuildId: e688446b48f00a577c82f6e36cac2c6e)
#01 pc 00000000000885d0 /apex/com.android.runtime/lib64/bionic/libc.so (ioctl+160) (BuildId: e688446b48f00a577c82f6e36cac2c6e)
#02 pc 0000000000051248 /system/lib64/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+216) (BuildId: 389ab2ccdbc4169d4345c969fa63955c)
#03 pc 00000000000557c8 /system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+152) (BuildId: 389ab2ccdbc4169d4345c969fa63955c)
#04 pc 0000000000082cec /system/lib64/libbinder.so (android::PoolThread::threadLoop()+28) (BuildId: 389ab2ccdbc4169d4345c969fa63955c)
#05 pc 000000000001956c /system/lib64/libutils.so (android::Thread::_threadLoop(void)+252) (BuildId: 8708332b97701f7d01a4f87d703335f7)
#06 pc 000000000001bdb8 /system/lib64/libutils.so (libutil_thread_trampoline(void) (.uniq.226528677032898775202282855395389835431)+24) (BuildId: 8708332b97701f7d01a4f87d703335f7)
#07 pc 000000000008e254 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_start(void*)+180) (BuildId: e688446b48f00a577c82f6e36cac2c6e)
#08 pc 000000000007f9f4 /apex/com.android.runtime/lib64/bionic/libc.so (start_thread+68) (BuildId: e688446b48f00a577c82f6e36cac2c6e)
]
signal: 6 (SIGABRT), code -1 (SI_QUEUE)
threadName: binder:871_7
MTE: enabled
backtrace:
/apex/com.android.runtime/lib64/bionic/libc.so (ioctl+12, pc e980c)
/apex/com.android.runtime/lib64/bionic/libc.so (ioctl+160, pc 885d0)
/system/lib64/libbinder.so (android::IPCThreadState::talkWithDriver(bool)+216, pc 51248)
/system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+152, pc 557c8)
/system/lib64/libbinder.so (android::PoolThread::threadLoop()+28, pc 82cec)
/system/lib64/libutils.so (android::Thread::_threadLoop(void)+252, pc 1956c)
/system/lib64/libutils.so (libutil_thread_trampoline(void) (.uniq.226528677032898775202282855395389835431)+24, pc 1bdb8)
/apex/com.android.runtime/lib64/bionic/libc.so (pthread_start(void*)+180, pc 8e254)
/apex/com.android.runtime/lib64/bionic/libc.so (start_thread+68, pc 7f9f4)`
Let me know if there is any recent fix for that.
Apologies for pasting the logs directly. I am on mobile and when I use the code feature it does not include the logs in the code box correctly for some reason.