**** BEGIN LOGGING AT Sat Nov 14 02:59:56 2020
Nov 14 05:47:56 <ubptgbot> <Hulisen Mickey> (Photo, 1280x568) https://irc.ubports.com/BNnaifVY.png Why does EGL_BAD_DISPLAY appear?
Nov 14 05:48:37 <ubptgbot> <Hulisen Mickey> (Photo, 1280x309) https://irc.ubports.com/1yiL2xp5.png opencl has passed the test
Nov 14 06:04:47 <ubptgbot> <Hulisen Mickey> @NotKit The screen will light up but nothing is displayed
Nov 14 06:05:01 <ubptgbot> <NotKit> @Hulisen Mickey [<reply to media>], something is wrong from libEGL point
Nov 14 06:05:10 <ubptgbot> <NotKit> @Hulisen Mickey [@NotKit The screen will light up but nothing is displayed], which test?
Nov 14 06:05:45 <ubptgbot> <Hulisen Mickey> test_hwcomposer
Nov 14 06:06:48 <ubptgbot> <Hulisen Mickey> @NotKit [which test?], The same is true for test_glesv2 and test_glesv3
Nov 14 06:10:48 <ubptgbot> <NotKit> have you done something about HWComposer HAL?
Nov 14 06:12:16 <ubptgbot> <Hulisen Mickey> I did not make any changes to HWComposer HAL
Nov 14 06:12:39 <ubptgbot> <Hulisen Mickey> test_hwcomposer in Halium reference rootfs, it doesn't work, I recompile the latest libhybris, it will light up the screen, but nothing more
Nov 14 06:14:33 <ubptgbot> <NotKit> I do not understand how does it even load and not crash since we couldn't find HWComposer HAL on your device
Nov 14 06:14:42 <ubptgbot> <NotKit> strace it please
Nov 14 06:16:38 <ubptgbot> <Hulisen Mickey> (Photo, 1193x858) https://irc.ubports.com/LBAs4Fdg.png Information that appears in strace test_hwcomposer
Nov 14 06:16:58 <ubptgbot> <NotKit> no, no photo, please upload full log to pastebin
Nov 14 06:18:13 <ubptgbot> <Hulisen Mickey> Ok please wait...Thank you😄
Nov 14 06:18:43 <ubptgbot> <NotKit> [Edit] no, not a screenshot, please upload full log to pastebin
Nov 14 06:21:00 <ubptgbot> <Hulisen Mickey> https://paste.ubuntu.com/p/qPhDDpw3Pd/
Nov 14 06:21:22 <ubptgbot> <Hulisen Mickey> It contains too much duplicate content
Nov 14 06:22:32 <ubptgbot> <NotKit> that's expected
Nov 14 06:22:58 <ubptgbot> <NotKit> Hulisen it loads open("/vendor/lib/hw/hwcomposer.hi3650.so", O_RDONLY|O_CLOEXEC) = 3
Nov 14 06:25:15 <ubptgbot> <Hulisen Mickey> This file is from LineageOS
Nov 14 06:25:53 <ubptgbot> <Hulisen Mickey> I copied it manually, there was no such file originally
Nov 14 06:29:17 <ubptgbot> <NotKit> do you know if it accepts standard AOSP structs like hwc_display_contents_1_t?
Nov 14 06:30:35 <ubptgbot> <Hulisen Mickey> I do not know
Nov 14 06:31:17 <ubptgbot> <NotKit> it's not even in https://github.com/OpenKirin/android_vendor_huawei_eva/tree/7.x/proprietary/lib64/hw, so it feels like the dev for custom firmware had some issues with it
Nov 14 06:33:51 <ubptgbot> <Hulisen Mickey> hwcomposer.hi3650.so is compiled from halium/hardware/libhardware/modules/hwcomposer
Nov 14 06:34:37 <ubptgbot> <NotKit> em... how is it hwcomposer.hi3650.so and not hwcomposer.default.so then?
Nov 14 06:36:03 <ubptgbot> <Hulisen Mickey> Do you mean it is hwcomposer.default.so itself?
Nov 14 06:38:12 <ubptgbot> <NotKit> @Hulisen Mickey [hwcomposer.hi3650.so is compiled from halium/hardware/libhardware/modules/hwcomp …], if you check https://github.com/Halium/android_hardware_libhardware/blob/halium-7.1/modules/hwcomposer/hwcomposer.cpp is just a sample skeleton and does not have any code to output graphic buffers to display
Nov 14 06:39:21 <ubptgbot> <Hulisen Mickey> indeed it is...😆
Nov 14 06:42:20 <ubptgbot> <NotKit> if I understand correctly, since it presents itself as version 1.0 HWComposer HAL, SurfaceFlinger will use fbdev/gralloc HAL to output instead: https://github.com/LineageOS/android_frameworks_native/blob/cm-14.1/services/surfaceflinger/DisplayHardware/HWComposer_hwc1.cpp#L181
Nov 14 06:43:09 <ubptgbot> <Hulisen Mickey> 👍
Nov 14 06:45:04 <ubptgbot> <NotKit> I don't know if it may really help, but try building libhybris before https://github.com/libhybris/libhybris/commit/bd08484162d4c5ab9906cfa573105635c9eb8884 this commit
Nov 14 06:45:14 <ubptgbot> <NotKit> [Edit] I don't know if it may really help, but try building libhybris before https://github.com/libhybris/libhybris/commit/bd08484162d4c5ab9906cfa573105635c9eb8884 this commit or revert it
Nov 14 06:45:38 <ubptgbot> <NotKit> I wonder if EGL_PLATFORM=fbdev test_glesv2 will render anything on screen
Nov 14 06:47:03 <ubptgbot> <Hulisen Mickey> test_glesv2: test_common.cpp:370: HWComposer* create_hwcomposer_window(): Assertion `err == 0' failed. … Aborted
Nov 14 06:47:05 <ubptgbot> <Hulisen Mickey> It just outputs this
Nov 14 06:49:43 <ubptgbot> <NotKit> see above ^
Nov 14 06:49:59 <ubptgbot> Penelopeу ADA was added by: Penelopeу ADA
Nov 14 06:50:28 <ubptgbot> <Hulisen Mickey> ok
Nov 14 07:00:45 <ubptgbot> <Hulisen Mickey> em...There was a problem compiling
Nov 14 07:01:22 <ubptgbot> <Hulisen Mickey> (Photo, 1280x370) https://irc.ubports.com/XDak202l.png
Nov 14 07:05:44 <ubptgbot> <NotKit> you didn't revert it fully or did not clean from previous build
Nov 14 07:06:02 <ubptgbot> <NotKit> notice it still tries to build test_common
Nov 14 07:07:07 <ubptgbot> <Hulisen Mickey> Ok i try again
Nov 14 07:39:28 <ubptgbot> <Hulisen Mickey> Has been compiled successfully
Nov 14 07:40:22 <ubptgbot> <Hulisen Mickey> (Photo, 856x155) https://irc.ubports.com/Q4cTlmuK.png EGL_PLATFORM=fbdev ./test_glesv2
Nov 14 07:58:59 <ubptgbot> <NotKit> https://github.com/libhybris/libhybris/blob/d2c23a6c537b750f9227b9b08f3d8c212a6afb1c/hybris/tests/test_glesv2.c#L116 - this fails
Nov 14 08:00:22 <ubptgbot> <NotKit> it seems to be hard to do something without understanding how does LineageOS 14.1 render on this device and maybe comparing it with hybris code step-by-step
Nov 14 08:02:04 <ubptgbot> <Hulisen Mickey> @NotKit [it seems to be hard to do something without understanding how does LineageOS 14. …], It's too difficult for me, I'm a novice...😆
Nov 14 08:02:29 <ubptgbot> <NotKit> I personally think the choice of target device in unfortunate - will be lot of work to make something work, but little to gain in result
Nov 14 08:03:07 <ubptgbot> <NotKit> Snapdragon Xiaomi or Moto should be much easier to deal with
Nov 14 08:08:35 <ubptgbot> <Hulisen Mickey> Huawei's equipment is too weird...
Nov 14 09:48:52 <ubptgbot> <aribk> How/where does one specify settings that ensure that a Halium build finds the vendor blobs and places them correctly in the final build, including setting necessary environment variables that ensure that they are found by the parts of the system that need them? I ask because my build ends up with blind links in  / that can be fixed by symli
Nov 14 09:48:52 <ubptgbot> nking. But this should be avoidable.
Nov 14 10:27:02 <ubptgbot> <Deathmist1337> @erfanoabdi do you happen to know if pre-Oreo Android rootfs' ever contained a `/vendor` (e.g. it being a symlink to `/system/vendor`)? I'm trying to figure out a way to detect A-only Treble devices during early halium-boot init: https://github.com/Halium/initramfs-tools-halium/pull/22
Nov 14 10:27:50 <ubptgbot> <erfanoabdi> @Deathmist1337 [@erfanoabdi do you happen to know if pre-Oreo Android rootfs' ever contained a / …], Yeah pixel 1gen … And nexus 5,6p have separate vendor partition
Nov 14 10:28:29 <ubptgbot> <erfanoabdi> @Deathmist1337 [@erfanoabdi do you happen to know if pre-Oreo Android rootfs' ever contained a / …], Just detecting A-only? … Grep slot on /proc/cmdline
Nov 14 10:29:01 <ubptgbot> <erfanoabdi> AB devices have slot parameter coming from bootloader
Nov 14 10:32:39 <ubptgbot> <Deathmist1337> @erfanoabdi [Just detecting A-only? … Grep slot on /proc/cmdline], well I know this, but it needs to not break older (e.g. Halium 7) devices, and we don't have any Android stuff mounted at that point in init so can't really check `build.prop` either
Nov 14 10:33:26 <ubptgbot> <Deathmist1337> checking for a vendor partition could cause false positives for A-only A9 device detection, as you can still downgrade firmware (I can go all the way back to 7.x from 10.x) and people can create unofficial vendor partitions for testing treble roms or whatnot
Nov 14 10:33:34 <ubptgbot> <erfanoabdi> @Deathmist1337 [well I know this, but it needs to not break older (e.g. Halium 7) devices, and w …], Halium 7 devices have fstab on ramdisk
Nov 14 10:33:55 <ubptgbot> <erfanoabdi> That's enough for checking
Nov 14 10:35:16 <ubptgbot> <Deathmist1337> huh, does this apply to halium-boot as well?
Nov 14 10:35:34 <ubptgbot> <erfanoabdi> @Deathmist1337 [huh, does this apply to halium-boot as well?], Yeah
Nov 14 10:37:28 <ubptgbot> <erfanoabdi> @Deathmist1337 [huh, does this apply to halium-boot as well?], Can u add udev rules generation on halium boot while you are at it?
Nov 14 10:41:08 <ubptgbot> <Deathmist1337> maybe when I'm done with this :p once again it shouldn't affect already ported devices so it could be a bit of a challange
Nov 14 10:43:24 <ubptgbot> <erfanoabdi> I think it's fine to have a new branch for halium9+
Nov 14 10:43:30 <ubptgbot> <erfanoabdi> Cc @NotKit
Nov 14 11:10:51 <ubptgbot> <NotKit> or just check Android version in build.prop
Nov 14 11:11:28 <ubptgbot> <NotKit> we're trying to minimize Android 9 specific branches actually
Nov 14 11:28:48 <ubptgbot> <Deathmist1337> @NotKit Android stuff gets mounted way later, should we now begin to mount it before boot mode detection (or mount it temporarily just to read it and then unmount again as needed)?
Nov 14 11:29:30 <ubptgbot> <Deathmist1337> [Edit] @NotKit Android stuff gets mounted way later, should we now begin to mount the system partition before boot mode detection (or mount it temporarily just to read it and then unmount again as needed)?
Nov 14 12:09:09 <filkatron> Hi everyone,while building the system image for motorola surnia I get the following error: ninja: error: 'vendor/motorola/msm8916-common/proprietary/bin/stml0xx', needed by '/home/filkatron/Projects/halium/out/target/product/surnia/system/bin/stml0xx', missing and no known rule to make itmake: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1
Nov 14 12:10:19 <filkatron> Could someone give me a hint of what I'm missing?
Nov 14 12:43:16 <ubptgbot> FABIEN Urho was added by: FABIEN Urho
Nov 14 12:43:51 <ubptgbot> DUNKLE french was added by: DUNKLE french
Nov 14 14:36:02 <ubptgbot> I_detonate_your_pride was added by: I_detonate_your_pride
Nov 14 14:37:15 <ubptgbot> <UniversalSuperBox> @I_detonate_your_pride [/rules], There is no rules robot in this room, nor a notes robot. … Read the pin.
Nov 14 14:37:38 <ubptgbot> <I_detonate_your_pride> Understood, sorry
Nov 14 14:51:46 <ubptgbot> <I_detonate_your_pride> [[[So I am att](https://github.com/NaramonRhino/vendor_amazon_karnak)[[So I am att](https://github.com/NaramonRhino/kernel_amazon_karnak)[So I am atte](https://github.com/NaramonRhino/device_amazon_mt8163-common)So I am attempting to port Halium-7.0 for the Amazon Fire HD 8 (2018 model, Codename: karnak).  I am keeping track
Nov 14 14:51:46 <ubptgbot>  of all the changes I made to the trees over on my own github in the following repositories: … [Device Tree … ](https://github.com/NaramonRhino/device_amazon_karnak)Common Tree … Kernel Tree … Vendor Tree … The error: https://paste.ubuntu.com/p/ZWG8bgmPtn/ … Any help would be appreciated, TIA!
Nov 14 15:25:10 <ubptgbot> <NotKit> @I_detonate_your_pride https://github.com/NaramonRhino/device_amazon_mt8163-common/blob/halium-7.0/BoardConfigCommon.mk#L56 comment out Wi-Fi section
Nov 14 15:25:22 <ubptgbot> <NotKit> we use host wpa_supplicant anyway
Nov 14 15:25:31 <ubptgbot> <NotKit> [Edit] we use Linux version of wpa_supplicant anyway
Nov 14 15:26:30 <ubptgbot> <Lukapanio> @I_detonate_your_pride [So I am attempting to port Halium-7.0 for the Amazon Fire HD 8 (2018 model, Code …], i did ported before to karnak, tho my trees are not public bcz of bugs
Nov 14 15:27:08 <ubptgbot> <NotKit> maybe you can push them as reference at least then?
Nov 14 15:29:24 <ubptgbot> <Lukapanio> @NotKit [maybe you can push them as reference at least then?], mb, but i am going to start new port based on new blbs and new kernel. Halium 9
Nov 14 15:29:48 <ubptgbot> <NotKit> what were your problems with it?
Nov 14 15:30:07 <ubptgbot> <Lukapanio> as amazon did updated to android 9, changing all blobs moving to sar and updating  … kernel to 4.9
Nov 14 15:30:11 <ubptgbot> <Lukapanio> @NotKit [what were your problems with it?], audio
Nov 14 15:30:47 <ubptgbot> <NotKit> @Lukapanio [as amazon did updated to android 9, changing all blobs moving to sar and updatin …], wow, that's pretty rare to happen for MTK device
Nov 14 15:31:14 <ubptgbot> <Lukapanio> @NotKit [wow, that's pretty rare to happen for MTK device], It is amazon, and it is "another" mtk
Nov 14 15:33:08 <ubptgbot> <X YZ> @Lukapanio [mb, but i am going to start new port based on new blbs and new kernel. Halium 9], Is that also for the Fire 8 only? I wish somebody would tackle the HD 10 (2019) ... 🎄
Nov 14 15:33:55 <ubptgbot> <Lukapanio> @X YZ [Is that also for the Fire 8 only? I wish somebody would tackle the HD 10 (2019) …], hd 10 2019 wount get anything before amonet or other exploit
Nov 14 15:37:29 <ubptgbot> <X YZ> @Lukapanio [hd 10 2019 wount get anything before amonet or other exploit], Yeah, that's what I figured: Long way to go. Since I am not a programmer, the only things I was able to achieve was install F-Droid /Aurora for apps and use Netguard to keep the chatty Amazon apps in check. Makes for a useful tablet then. 👍
Nov 14 19:50:54 <Kaderohr> Hi. Halium 9 can be compiled with lineageos 17.1??Thanks.
Nov 14 19:53:23 <ubptgbot> <NotKit> @Kaderohr [Hi. Halium 9 can be compiled with lineageos 17.1??Thanks.], Hi. No, that will require Halium 10
Nov 14 19:53:39 <ubptgbot> <NotKit> did your device launch with Android 10?
Nov 14 19:54:15 <Kaderohr> my device was launched with Android 8.1
Nov 14 19:54:47 <Kaderohr> how i can get halium 10??
Nov 14 19:55:44 <Kaderohr> I didn't know it existed
Nov 14 20:15:44 <ubptgbot> <NotKit> Halium 10 doesn't exist, but if your device started with 8.1, you don't need it
Nov 14 20:16:03 <ubptgbot> <NotKit> see https://github.com/ubports/porting-notes/wiki/Generic-system-image-(GSI)
Nov 14 20:28:23 <Kaderohr> ok thanks :]  :] . I have read the documentation before and I have tried to compile a halim-boot.img following the steps, but using the 17.1 lineage sources that are officially supported for my device. For android 9 or lineageos 16.0 I have not been able to find sources and I don't know how to do it.
Nov 14 20:34:43 <Kaderohr> My device is the Galaxy Note 9 (crownlte). I have seen that in Erfanoabdi's git there is a repository for exynos9810 with a branch called halium-9 (I don't know if it is based on 17.1 lineages).I have downloaded the sources, I have compiled them but when I flash the boot.img by TWRP and the other files that the guide specifies, the device does not
Nov 14 20:34:43 <Kaderohr> start and the screen remains black;( ;( ;(
Nov 14 20:36:29 <ubptgbot> <NotKit> @erfanoabdi do you have information for crownlte?
Nov 14 20:36:39 <ubptgbot> <NotKit> [Edit] @erfanoabdi do you have any information for crownlte?
Nov 14 20:52:35 <ubptgbot> <Ern_st> Is there any interest in forcing camera HAL3 or camera HAL1, for halium 9 ?
Nov 14 20:54:27 <ubptgbot> <Ern_st> Better compatibility, etc...?
Nov 14 22:37:21 <ubptgbot> <erfanoabdi> @NotKit [@erfanoabdi do you have any information for crownlte?], Need to build lineage16 with special patches first (init scripts should be moved to vendor and a few audio xml workings) … Kernel need halium patches too
Nov 14 22:38:07 <ubptgbot> <erfanoabdi> Btw i couldn't even boot starlte on arm64 rootfs … Screen goes black … Ssh/rndis is broken … So very hard to debug
Nov 15 00:46:57 <ubptgbot> maXp29 was added by: maXp29
Nov 15 01:16:42 <ubptgbot> Jefferson was added by: Jefferson
Nov 15 01:17:13 <ubptgbot> <Jefferson> Hi … i use a Redmi 7A … i will like install Ubuntu Touch … who can help me … please
Nov 15 01:17:39 <ubptgbot> <Jefferson> https://www.youtube.com/watch?v=kV3SAWdxhwU&t=1103s
Nov 15 01:17:48 <ubptgbot> <Jefferson> a guy uploaded this video installing on Redmi 7A
**** ENDING LOGGING AT Sun Nov 15 02:59:56 2020