[Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re] Maksvr:
Oke, strange issue. Something, I believe the audio driver, keeps crashing, causing any media (Youtube, Spotify, Shuttle+, etc.) to pause and resume again every 10 seconds.

I still have an RNS510 in my VW (very out dated but it still works). Problems started after I was messing with bluetooth in combination with Spotify. So it's probably an edge case but I'd like to share it in case you have the same problems. It could be related to your issue as well @Rapalax.

Logcat:

--------- beginning of crash
12-29 23:06:18.906 F/libc (21983): Fatal signal 31 (SIGSYS), code 1 (SYS_SECCOMP) in tid 21983 (dmesg), pid 21983 (dmesg)
12-29 23:06:18.933 F/DEBUG (21986): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-29 23:06:18.933 F/DEBUG (21986): LineageOS Version: '18.1-20201223-UNOFFICIAL-raphael'
12-29 23:06:18.933 F/DEBUG (21986): Build fingerprint: 'google/walleye/walleye:8.1.0/OPM1.171019.011/4448085:user/release-keys'
12-29 23:06:18.933 F/DEBUG (21986): Revision: '0'
12-29 23:06:18.933 F/DEBUG (21986): ABI: 'arm64'
12-29 23:06:18.934 F/DEBUG (21986): Timestamp: 2020-12-29 23:06:18+0100
12-29 23:06:18.934 F/DEBUG (21986): pid: 21983, tid: 21983, name: dmesg >>> dmesg <<<
12-29 23:06:18.934 F/DEBUG (21986): uid: 10301
12-29 23:06:18.934 F/DEBUG (21986): signal 31 (SIGSYS), code 1 (SYS_SECCOMP), fault addr --------
12-29 23:06:18.934 F/DEBUG (21986): Cause: seccomp prevented call to disallowed arm64 system call 116
12-29 23:06:18.934 F/DEBUG (21986): x0 <private info omitted>a x1 <private info omitted>0 x2 <private info omitted>0 x3 <private info omitted>0
12-29 23:06:18.934 F/DEBUG (21986): x4 0000007ffc0c3de1 x5 <private info omitted>4 x6 0000007e0ce49000 x7 0000007e0ce49000
12-29 23:06:18.934 F/DEBUG (21986): x8 <private info omitted>4 x9 c99fe129b14b5ade x10 0000007ffc0c1d40 x11 0000007ffc0c1d10
12-29 23:06:18.934 F/DEBUG (21986): x12 ffffff80ffffffd0 x13 0000007e0ce4b020 x14 <private info omitted>5 x15 <private info omitted>d
12-29 23:06:18.934 F/DEBUG (21986): x16 0000005d7b505c08 x17 0000007ecd2ae1d0 x18 0000007ecdb9a000 x19 <private info omitted>0
12-29 23:06:18.934 F/DEBUG (21986): x20 <private info omitted>0 x21 0000007ecd624000 x22 0000005d7b50b7c8 x23 0000005d7b5097a0
12-29 23:06:18.934 F/DEBUG (21986): x24 <private info omitted>0 x25 <private info omitted>0 x26 <private info omitted>0 x27 <private info omitted>0
12-29 23:06:18.934 F/DEBUG (21986): x28 <private info omitted>0 x29 0000007ffc0c3df0
12-29 23:06:18.934 F/DEBUG (21986): lr 0000005d7b4e386c sp 0000007ffc0c1de0 pc 0000007ecd2ae1d8 pst <private info omitted>0
12-29 23:06:18.939 F/DEBUG (21986): backtrace:
12-29 23:06:18.939 F/DEBUG (21986): #00 pc 000000000009d1d8 /apex/com.android.runtime/lib64/bionic/libc.so (klogctl+8) (BuildId: 15590a8fafc95809204f1f365f9bfec1)
12-29 23:06:18.939 F/DEBUG (21986): #01 pc 000000000004f868 /system/bin/toybox (dmesg_main+436) (BuildId: c51427283fe8c34d65e936e97f09a60b)
12-29 23:06:18.939 F/DEBUG (21986): #02 pc 0000000000033d50 /system/bin/toybox (toy_exec_which+84) (BuildId: c51427283fe8c34d65e936e97f09a60b)
12-29 23:06:18.939 F/DEBUG (21986): #03 pc 00000000000338d0 /system/bin/toybox (toybox_main+52) (BuildId: c51427283fe8c34d65e936e97f09a60b)
12-29 23:06:18.939 F/DEBUG (21986): #04 pc 0000000000033df4 /system/bin/toybox (main+112) (BuildId: c51427283fe8c34d65e936e97f09a60b)
12-29 23:06:18.939 F/DEBUG (21986): #05 pc <private info omitted>c /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: 15590a8fafc95809204f1f365f9bfec1)
--------- beginning of main
12-29 23:08:38.376 V/SysLog ( 2047): Path: /data/user/0/com.tortel.syslog/cache/logs/2020-12-29_23.08/
12-29 23:08:38.386 V/SysLog ( 2047): Done grabbing logs

It's seccomp preventing a process to do a certain kernel call. My request to @abhishek987 is to update the audio driver in the next release if that's possible :p. Thanks again for this great rom.

Edit\ Also I am a complete noob at debugging this, from the backtrace I can only see that it must be something low-level?? It would be nice if I can figure out what is actually making this call.

Edit2\ Found it and I feel stupid; I accidentally enabled Google Assistant/"Hey Google" together with the screen context. When I disabled this again everything worked OK for me.

The problem returned however so it's difficult to say if this really has got something to do with it.