**** BEGIN LOGGING AT Sun Dec 20 02:59:57 2020
Dec 20 03:03:53 <ubptgbot> <Stellar_Eagle> @erfanoabdi [this isn't helping with his bug], Thank you. Let me see my old notes from old Linux backup if anything else I did apart from that. I'm not sure if I've copies of all previous defconfig files to look for changes that I made to get over that.
Dec 20 03:24:31 <ubptgbot> #K.D. was added by: #K.D.
**** BEGIN LOGGING AT Sun Dec 20 08:38:20 2020
Dec 20 09:45:43 <ubptgbot> ilhamisrar was added by: ilhamisrar
Dec 20 10:03:44 <ubptgbot> <Lukapanio> update about my error with karnak
Dec 20 10:04:21 <ubptgbot> <Lukapanio> Thanks @Herrie1982  for testing, it appears all arm32 devices have that error
Dec 20 10:04:22 <ubptgbot> <Lukapanio> https://bpa.st/W3AQ
Dec 20 11:37:25 <ubptgbot> <Lukapanio> @NotKit  how are ota updates implemented on pro 1?
Dec 20 11:37:32 <ubptgbot> <Lukapanio> there is no recovery partition
Dec 20 11:50:55 <ubptgbot> <just_carlod> @Lukapanio [@NotKit  how are ota updates implemented on pro 1?], recovery is integrated with boot image
Dec 20 11:52:11 <ubptgbot> <NotKit> yes, there recovery-ramdisk inside halium-boot which gets extracted if bootloader puts no "skip_initramfs" to cmdline
Dec 20 11:52:57 <ubptgbot> <Lukapanio> @NotKit [yes, there recovery-ramdisk inside halium-boot which gets extracted if bootloade …], oh lol sounds way too hacky
Dec 20 11:53:19 <ubptgbot> <NotKit> not too different from what Android 9 did
Dec 20 11:58:28 <ubptgbot> <just_carlod> @Lukapanio [oh lol sounds way too hacky], it's not hard you only need to apply a few commits and add device specific files
Dec 20 12:35:47 <ubptgbot> <Lukapanio> @just_carlod [it's not hard you only need to apply a few commits and add device specific files], ik that it is easy. But it is hack
Dec 20 12:51:17 <ubptgbot> <NotKit> whole Halium is a huge hack though
Dec 20 12:51:52 <ubptgbot> <Lukapanio> @NotKit [whole Halium is a huge hack though], but there is no alternative sadly
Dec 20 14:42:40 <nergzd723> kholk works on mainline for pro1 so there soon will be an alternative
Dec 20 16:01:16 <ubptgbot> <Lukapanio> @Venji10 [👍], You did that? as i have same problem now
Dec 20 16:01:38 <ubptgbot> <Lukapanio> @nergzd723 [kholk works on mainline for pro1 so there soon will be an alternative], pro 1 is not a popular device
Dec 20 16:03:59 <ubptgbot> <Lukapanio> @Venji10 [BOARD_BUILD_SYSTEM_ROOT_IMAGE := true], didnt chaned here
Dec 20 16:04:58 <ubptgbot> <Herrie1982> Well my notes from NotKit said: "For non-Treble devices workaround for ramdisk: … <NotKit> `BOARD_BUILD_SYSTEM_ROOT_IMAGE := true` in BoardConfig.mk or BoardConfigCommon.mk … "
Dec 20 16:05:07 <ubptgbot> <Herrie1982> Shouldn't that then come into halium-boot
Dec 20 16:06:07 <ubptgbot> <Lukapanio> @Herrie1982 [Shouldn't that then come into halium-boot], no
Dec 20 16:06:11 <ubptgbot> <Lukapanio> to systemimage
Dec 20 16:06:29 <ubptgbot> <Venji10> @Lukapanio [didnt chaned here], Fixed it
Dec 20 16:06:34 <ubptgbot> <Venji10> ?
Dec 20 16:06:39 <ubptgbot> <Lukapanio> @Herrie1982 [Well my notes from NotKit said: "For non-Treble devices workaround for ramdisk: …], you shure that you rebuilt and gave correct image me?
Dec 20 16:06:42 <ubptgbot> <Lukapanio> @Venji10 [Fixed it], no
Dec 20 16:16:21 <ubptgbot> <hacker12455> @Lukapanio [but there is no alternative sadly], mainline
Dec 20 16:17:42 <ubptgbot> <Lukapanio> @hacker12455 [mainline], on mtk
Dec 20 16:18:00 <ubptgbot> <hacker12455> mainline (torture) :)
Dec 20 18:27:07 <ubptgbot> <Lukapanio> https://paste.ubuntu.com/p/7KtNm7MFnv/
Dec 20 18:27:18 <ubptgbot> <Lukapanio> android failes in lxc
Dec 20 18:27:36 <ubptgbot> <Lukapanio> firstly evrything crashes
Dec 20 18:27:44 <ubptgbot> <Lukapanio> then: … ```[  174.782010]  (3)[7180:init]init: init first stage started! … [  174.782052]  (3)[7180:init]init: Skipped setting INIT_AVB_VERSION (not in recovery mode) … [  174.784897]  (3)[7180:init]init: init second stage started! … [  174.789675]  (3)[7180:init]init: Failed to initialize property area```
Dec 20 18:27:50 <ubptgbot> <NotKit> is it 32-bit device?
Dec 20 18:27:52 <ubptgbot> <Lukapanio> @Lukapanio [then: … [  174.782010]  (3)[7180:init]init: init first stage started! … [  174.78205 …], a lot of those
Dec 20 18:27:55 <ubptgbot> <Lukapanio> @NotKit [is it 32-bit device?], yep
Dec 20 18:28:06 <ubptgbot> <NotKit> in hybris-patches, there is LD_PRELOAD hardcoded with /system/lib64
Dec 20 18:28:07 <ubptgbot> <NotKit> fix it
Dec 20 18:28:21 <ubptgbot> <Lukapanio> @NotKit [in hybris-patches, there is LD_PRELOAD hardcoded with /system/lib64], oh lol, thanks
Dec 20 18:29:48 <ubptgbot> <Lukapanio> @NotKit [in hybris-patches, there is LD_PRELOAD hardcoded with /system/lib64], yep noticed in logcat
Dec 20 19:15:00 <ubptgbot> <Lukapanio> @NotKit [in hybris-patches, there is LD_PRELOAD hardcoded with /system/lib64], For now fixed local in init files
Dec 20 19:15:18 <ubptgbot> <Lukapanio> hwservicemanager and few others
Dec 20 19:15:26 <ubptgbot> <Lukapanio> lxc is up
Dec 20 19:20:34 <ubptgbot> <Lukapanio> Butw @NotKit what would be proper fix? To support both 64 and 32
Dec 20 20:09:13 <ubptgbot> <NotKit> not sure, maybe full path can be omitted altogether?
Dec 20 20:32:36 <ubptgbot> <Andeddokira> When I run source build/envsetup.sh && breakfast DEVICE_NAME I get an invalid parameters at the end but can still build successfully, how important is fixing these as currently I get stuck on the oem boot splash? The error is  … destroy_build_var_cache:unset:5: var_cache_ 2ND_TARGET_GCC_VERSION ANDROID_BUILD_PATHS OUT_DIR TARGET_2ND_A
Dec 20 20:32:37 <ubptgbot> RCH TARGET_ARCH TARGET_BUILD_VARIANT TARGET_DEVICE TARGET_GCC_VERSION TARGET_PLATFORM_VERSION TARGET_PRODUCT print report_config : invalid parameter name
Dec 20 20:34:15 <ubptgbot> <NotKit> unlikely to be related
Dec 20 20:35:00 <ubptgbot> <Andeddokira> Thought so but just trying to look at all the variables, don't seem to have usb whilst sitting at the oem splash so struggling to diagnose the issue
Dec 20 20:37:20 <ubptgbot> <Andeddokira> I have realized I didn't set do_skip_initramfs = 0; but I feel like I should at least have usb before that point anyway, giving the kernel a build with that set though. There is another variant of my device that shares the same kernel source, it was built with halium 7.1, I assume that this would not work for hallium 9?
Dec 20 20:40:36 <ubptgbot> <Andeddokira> Or would it be possible to take that kernel source, place it in my halium build dir and then build it for halium 9?
Dec 20 20:45:29 <ubptgbot> <NotKit> @Andeddokira [I have realized I didn't set do_skip_initramfs = 0; but I feel like I should at …], no, if it is Android 9 device
Dec 20 20:45:34 <ubptgbot> <NotKit> depends on your bootloader
Dec 20 21:41:27 <ubptgbot> <Andeddokira> Hmmm i'm at a bit of a loss now, I really can't seem to get the device to boot with halium, is there any other common things that can cause a device to not boot past the oem splash?
Dec 20 21:59:17 <ubptgbot> <Andeddokira> The kernel is motorola_msm8937 if that helps anyone point me in the right direction, pretty common chipset for porting UBT
Dec 20 22:32:38 <ubptgbot> Downhills_moirai was added by: Downhills_moirai
Dec 20 22:53:09 <ubptgbot> <Andeddokira> anyone know if there's anything like hybris-recovery for halium 9? Tried checking if telnet was up and that's not either
Dec 20 22:56:33 <ubptgbot> <just_carlod> @Andeddokira [anyone know if there's anything like hybris-recovery for halium 9? Tried checkin …], we don't use hybris-recovery for ubuntu touch
Dec 20 22:57:29 <ubptgbot> <Andeddokira> @just_carlod [we don't use hybris-recovery for ubuntu touch], I know, but i'm just trying to debug halium-boot and not getting very far with getting any usb to the device
Dec 21 00:31:51 <ubptgbot> <Andeddokira> (Document) https://irc.ubports.com/zdhgxp6r.txt
**** ENDING LOGGING AT Mon Dec 21 02:59:56 2020