AOSP Android TV (atv_x86 or sdk_atv_x86) build issue Android Oreo OPR2.170623.027 / OPR6.170623.021
985 views
Skip to first unread message
Shashank Raghunath
Jun 4, 2019, 12:01:25 PM6/4/19
to Android Building
Hi,
I am trying to build AOSP and deploy it on an Android TV emulator. Following are the steps I have taken so far:
repo init -u https://android.googlesource.com/platform/manifest -b android-8.0.0_r29 --depth=1
ran the sh command for the binaries for OPR2.170623.027
added to /device/google/atv/products/AndroidProducts.mk the following:
added to /device/google/atv/products/vendorsetup.sh the following:
add_lunch_combo atv_x86-userdebug
add_lunch_combo sdk_atv_x86-userdebug
ran the following commands from the aosp source folder:
source build/envsetup.sh
lunch atv_x86-userdebug
make.
I get no errors in building the aosp. But I am getting a black screen on the emulator and nothing happens.
Following is error i get when i run $ emulator -use-system-libs from AOSP source directory.
2019-06-03 17:35:06.945 4114-4114/? W/ProcessState: Opening '/dev/vndbinder' failed: No such file or directory
2019-06-03 17:35:06.945 4114-4114/? A/ProcessState: Binder driver could not be opened. Terminating.
2019-06-03 17:35:06.945 4114-4114/? A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 4114 (android.hardwar)
2019-06-03 17:35:06.962 4159-4159/? I/crash_dump32: obtaining output fd from tombstoned
2019-06-03 17:35:06.962 4159-4159/? E/libc: failed to connect to tombstoned: No such file or directory
2019-06-03 17:35:06.963 4159-4159/? I/crash_dump32: performing dump of process 4114 (target tid = 4114)
2019-06-03 17:35:06.963 4159-4159/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2019-06-03 17:35:06.963 4159-4159/? A/DEBUG: Build fingerprint: 'Android/atv_x86/generic_x86:8.0.0/OPR2.170623.027/shasha06031122:userdebug/test-keys'
2019-06-03 17:35:06.967 4159-4159/? A/DEBUG: Revision: '0'
2019-06-03 17:35:06.967 4159-4159/? A/DEBUG: ABI: 'x86'
2019-06-03 17:35:06.967 4159-4159/? A/DEBUG: pid: 4114, tid: 4114, name: android.hardwar >>> /vendor/bin/hw/android.hardw...@1.0-service <<<
2019-06-03 17:35:06.967 4159-4159/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
2019-06-03 17:35:06.968 4159-4159/? A/DEBUG: Abort message: 'Binder driver could not be opened. Terminating.'
2019-06-03 17:35:06.968 4159-4159/? A/DEBUG: eax 00000000 ebx 00001012 ecx 00001012 edx 00000006
2019-06-03 17:35:06.968 4159-4159/? A/DEBUG: esi 00001012 edi bff2c9c8
2019-06-03 17:35:06.968 4159-4159/? A/DEBUG: xcs 00000073 xds 0000007b xes 0000007b xfs 00000000 xss 0000007b
2019-06-03 17:35:06.968 4159-4159/? A/DEBUG: eip b0118424 ebp bff2c9e8 esp bff2c97c flags 00000296
2019-06-03 17:35:06.971 4123-4123/? E/crash_dump32: unable to connect to activity manager: No such file or directory
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: backtrace:
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: #00 pc ffffe424 [vdso:b0118000] (__kernel_vsyscall+16)
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: #01 pc 00075b3c /system/lib/libc.so (tgkill+28)
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: #02 pc 0001f04e /system/lib/libc.so (abort+110)
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: #03 pc 00006a06 /system/lib/liblog.so (__android_log_assert+294)
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: #04 pc 0007d2bb /system/lib/libbinder.so (_ZN7android12ProcessStateC1EPKc+427)
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: #05 pc 0007d395 /system/lib/libbinder.so (_ZN7android12ProcessState14initWithDriverEPKc+197)
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: #06 pc 0000129c /system/vendor/bin/hw/android.hardw...@1.0-service (main+108)
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: #07 pc 00015f34 /system/lib/libc.so (__libc_init+100)
2019-06-03 17:35:06.982 4159-4159/? A/DEBUG: #08 pc 00001181 /system/vendor/bin/hw/android.hardw...@1.0-service (_start+97)
Please let me know if I am missing something here. Is it even possible to run AOSP on a TV emulator. If so please let me know the correct steps.
Reply all
Reply to author
Forward
0 new messages