AOSP 构建成功但相机的视频捕获故障

如何解决AOSP 构建成功但相机的视频捕获故障

我刚刚使用分支 android-11.0.0_r17 在我的 macbook 上构建了 AOSP，午餐目标是 aosp_blueline-user。我遵循了所有官方说明并获得了成功的构建输出。但是，当我将构建闪存到我的像素 3 手机并试用时。相机视频捕获功能不起作用。当我按下视频捕获按钮时，应用程序冻结并且 ANR 对话框提示出来，同时 logcat 打印一些错误消息：

2021-06-17 11:33:58.224 26596-26596/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2021-06-17 11:33:58.224 26596-26596/? A/DEBUG: Build fingerprint: 'Android/aosp_blueline/blueline:11/RP1A.201105.002/eng.liulif.20210616.170506:user/test-keys'
2021-06-17 11:33:58.224 26596-26596/? A/DEBUG: Revision: 'MP1.0'
2021-06-17 11:33:58.224 26596-26596/? A/DEBUG: ABI: 'arm64'
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG: Timestamp: 2021-06-17 11:33:58+0800
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG: pid: 26584,tid: 26584,name: mediaextractor  >>> /system/bin/mediaextractor <<<
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG: uid: 1040
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG: signal 6 (SIGABRT),code -1 (SI_QUEUE),fault addr --------
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG:     x0  0000000000000000  x1  00000000000067d8  x2  0000000000000006  x3  0000007fd9143d40
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG:     x4  0000000000000034  x5  0000000000000034  x6  0000000000000034  x7  0000000000000034
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG:     x8  00000000000000f0  x9  f414f4897a41b472  x10 0000000000000000  x11 ffffffc0ffffffdf
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG:     x12 0000000000000001  x13 206466206d6f7266  x14 00000075ff17ed22  x15 000a7c801a850154
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG:     x16 00000075ff17bc80  x17 00000075ff15d3b0  x18 0000007602aae000  x19 00000000000067d8
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG:     x20 00000000000067d8  x21 00000000ffffffff  x22 0000000000000000  x23 0000007601ff3000
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG:     x24 0000007601ff3000  x25 000000738ed9b0e8  x26 0000000000000002  x27 0000000000000000
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG:     x28 0000000000000000  x29 0000007fd9143dc0
2021-06-17 11:33:58.225 26596-26596/? A/DEBUG:     lr  00000075ff110e20  sp  0000007fd9143d20  pc  00000075ff110e4c  pst 0000000000000000
2021-06-17 11:33:58.228 26596-26596/? A/DEBUG: backtrace:
2021-06-17 11:33:58.228 26596-26596/? A/DEBUG:       #00 pc 000000000004de4c  /apex/com.android.runtime/lib64/bionic/libc.so (abort+164) (BuildId: 0d88bf62691b14ff4287d2637426385f)
2021-06-17 11:33:58.228 26596-26596/? A/DEBUG:       #01 pc 0000000000012138  /system/lib64/libminijail.so (do_fatal_log+288) (BuildId: 34e38a0ea0fc0c28600c8a331880f42b)
2021-06-17 11:33:58.228 26596-26596/? A/DEBUG:       #02 pc 000000000000b958  /system/lib64/libminijail.so (minijail_parse_seccomp_filters_from_fd+276) (BuildId: 34e38a0ea0fc0c28600c8a331880f42b)
2021-06-17 11:33:58.228 26596-26596/? A/DEBUG:       #03 pc 0000000000002984  /system/lib64/libavservices_minijail.so (android::SetUpMinijailList(std::__1::basic_string<char,std::__1::char_traits<char>,std::__1::allocator<char> > const&,std::__1::vector<std::__1::basic_string<char,std::__1::allocator<char> >,std::__1::allocator<std::__1::basic_string<char,std::__1::allocator<char> > > > const&) (.cfi)+616) (BuildId: f50e473049ba38a9d60df9d1dfcce80b)
2021-06-17 11:33:58.228 26596-26596/? A/DEBUG:       #04 pc 00000000000026c4  /system/lib64/libavservices_minijail.so (android::SetUpMinijail(std::__1::basic_string<char,std::__1::basic_string<char,std::__1::allocator<char> > const&) (.cfi)+88) (BuildId: f50e473049ba38a9d60df9d1dfcce80b)
2021-06-17 11:33:58.228 26596-26596/? A/DEBUG:       #05 pc 000000000000112c  /system/bin/mediaextractor (main.cfi+192) (BuildId: edd83fdd4235a0ef3eafcf5937896835)
2021-06-17 11:33:58.228 26596-26596/? A/DEBUG:       #06 pc 0000000000049418  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: 0d88bf62691b14ff4287d2637426385f)

有人知道如何解决这个问题吗？谢谢。