remote-android
No controlling tty: open /dev/tty: No such device or address
我是用的win10开虚拟机运行的ubuntu20.04，内核版本5.4.0-172-generic，看了之前那些问题，始终出现在binder上，输出了日志，目前不知道该怎么解决问题了，麻烦帮助一下谢谢。
According to ps.txt, your redroid container boot succeeded. Try adb shell or docker exec -it <container-id> sh again (may need wait a few seconds to make sure critical process started in container).
BTW, there is a fatal system crash during boot up. May need inspect further if constantly crashed.
Build fingerprint: 'redroid/redroid_x86_64/redroid_x86_64:11/RD2A.211001.002/eng.frank.20231013.063253:userdebug/test-keys'
Revision: '0'
ABI: 'x86_64'
Timestamp: 2024-02-23 03:24:55+0000
pid: 251, tid: 276, name: android.bg >>> system_server <<<
uid: 1000
signal 11 (SIGSEGV), code 128 (SI_KERNEL), fault addr 0x0
rax 00007f23896fcf58 rbx 0000000000000060 rcx 0000000000000100 rdx 00007f26283c0e30
r8 ffffffffffffff00 r9 0000000000000001 r10 0000000000000007 r11 0000000000000000
r12 0000000000000000 r13 00007f2453fcb3f0 r14 000000000003cee2 r15 00007f23347396d0
rdi 00007f23347390d0 rsi 0000000000000001
rbp 0000000000000060 rsp 00007f2334739590 rip 00007f26272af15e
backtrace:
#00 pc 000000000000215e /system/lib64/libmemtrack.so (memtrack_proc_new+14) (BuildId: 4badf617a2d83ba759f11339dd902101)
#01 pc 0000000000111d6e /system/lib64/libandroid_runtime.so (android::read_memtrack_memory(int, android::graphics_memory_
#02 pc 0000000000110e22 /system/lib64/libandroid_runtime.so (android::android_os_Debug_getPssPid(_JNIEnv*, _jobject*, int
#03 pc 000000000023403b /system/framework/x86_64/boot-framework.oat (art_jni_trampoline+267) (BuildId: 486e7e1c0e08904fd2
#04 pc 000000000121c814 /system/framework/oat/x86_64/services.odex (com.android.server.am.ActivityManagerService$5.handle
#05 pc 000000000066d0c7 /system/framework/x86_64/boot-framework.oat (android.os.Handler.dispatchMessage+183) (BuildId: 48
According to
ps.txt, your redroid container boot succeeded. Tryadb shellordocker exec -it <container-id> shagain (may need wait a few seconds to make sure critical process started in container).BTW, there is a fatal system crash during boot up. May need inspect further if constantly crashed.
Build fingerprint: 'redroid/redroid_x86_64/redroid_x86_64:11/RD2A.211001.002/eng.frank.20231013.063253:userdebug/test-keys' Revision: '0' ABI: 'x86_64' Timestamp: 2024-02-23 03:24:55+0000 pid: 251, tid: 276, name: android.bg >>> system_server <<< uid: 1000 signal 11 (SIGSEGV), code 128 (SI_KERNEL), fault addr 0x0 rax 00007f23896fcf58 rbx 0000000000000060 rcx 0000000000000100 rdx 00007f26283c0e30 r8 ffffffffffffff00 r9 0000000000000001 r10 0000000000000007 r11 0000000000000000 r12 0000000000000000 r13 00007f2453fcb3f0 r14 000000000003cee2 r15 00007f23347396d0 rdi 00007f23347390d0 rsi 0000000000000001 rbp 0000000000000060 rsp 00007f2334739590 rip 00007f26272af15e backtrace: #00 pc 000000000000215e /system/lib64/libmemtrack.so (memtrack_proc_new+14) (BuildId: 4badf617a2d83ba759f11339dd902101) #01 pc 0000000000111d6e /system/lib64/libandroid_runtime.so (android::read_memtrack_memory(int, android::graphics_memory_ #02 pc 0000000000110e22 /system/lib64/libandroid_runtime.so (android::android_os_Debug_getPssPid(_JNIEnv*, _jobject*, int #03 pc 000000000023403b /system/framework/x86_64/boot-framework.oat (art_jni_trampoline+267) (BuildId: 486e7e1c0e08904fd2 #04 pc 000000000121c814 /system/framework/oat/x86_64/services.odex (com.android.server.am.ActivityManagerService$5.handle #05 pc 000000000066d0c7 /system/framework/x86_64/boot-framework.oat (android.os.Handler.dispatchMessage+183) (BuildId: 48
我又重新连接试了一下，好像确实又可以连上了，感谢