**** BEGIN LOGGING AT Sat Jun 12 02:59:56 2021 Jun 12 11:33:50 ItoRimai was added by: ItoRimai Jun 12 11:34:27 halium is a driver? Jun 12 12:04:54 no Jun 12 12:05:53 kernel? Jun 12 13:32:26 @ItoRimai [halium is a driver?], halium is a compatibility layer Jun 12 13:59:41 Is it only needed by some devices? (such as Samsung) Jun 12 14:04:35 https://gitlab.com/ubports/community-ports/android10/xiaomi-poco-m3/xiaomi-citrus … Where's the upstream repo for the scripts here? Jun 12 14:20:08 @NotKit is it your Volla Phone X repo? Jun 12 14:24:02 And how can I find a value for `deviceinfo_flash_offset_dtb`? `mkbootimg` doesn't list it. Jun 12 14:54:56 @hacker1024 [And how can I find a value for deviceinfo_flash_offset_dtb? mkbootimg doesn't li …], does your phone use boot 2.0 header image? otherwise you don't have it Jun 12 14:55:19 and no real upstream yet, but thinking of doing something like that Jun 12 14:55:23 @NotKit [does your phone use boot 2.0 header image? otherwise you don't have it], I'll check. I think it does; it launched with Pie. Jun 12 14:55:35 that started with 10 Jun 12 14:55:38 Oh Jun 12 14:56:48 Ah yes it's version 1 Jun 12 14:58:31 Thanks Jun 12 14:58:44 @NotKit [and no real upstream yet, but thinking of doing something like that], That would be very much appreciated Jun 12 15:15:09 @NotKit [and no real upstream yet, but thinking of doing something like that], [Edit] That would be very much appreciated if you do Jun 12 15:55:07 It looks like the kernel image generated by the script is missing embedded DTBs. Is there a way to fix this? Jun 12 15:55:32 does Image.gz-dtb get build? Jun 12 15:55:41 and you changed version to 1? Jun 12 15:56:04 I changed to 1, I'll investigate Image.gz-ftb Jun 12 15:56:07 (Sticker, 512x512) https://irc.ubports.com/RBfNbL0M.webp Jun 12 15:56:16 [Edit] I changed to 1, I'll investigate Image.gz-dtb Jun 12 15:58:47 Looks like the built images got deleted Jun 12 15:59:09 I'll check that my config is set up to build it Jun 12 16:03:57 It is indeed being built, but I just notices this a few lines above where the image list is declared on line 32 of `make-bootimage.sh`: `cpio: command not found`. I missed it in all the noise. Jun 12 16:04:09 I'll install `cpio` and try again Jun 12 16:07:04 Nope, there still are no DTBs being put in the kernel image Jun 12 16:07:15 There are 32 in the generated Image-dtb Jun 12 16:07:26 Oh Jun 12 16:07:38 The generated image isn't gzipped Jun 12 16:08:01 I don't think the script handles that situation Jun 12 16:13:26 @NotKit I assume you still maintain this script - you may want to add `Image-dtb` to the image list Jun 12 16:33:08 @ItoRimai [Is it only needed by some devices? (such as Samsung)], it is need for all android devices Jun 12 16:33:38 Sarabpal was added by: Sarabpal Jun 12 16:35:57 @Fuseteam [it is need for all android devices], When can the bottom be independent Jun 12 16:36:11 maybe 5 years later😄 Jun 12 16:38:32 @ItoRimai [When can the bottom be independent], when someone reversed engineerd all drivers and upstreamed all the out of tree code of all the devices upstream :p Jun 12 16:40:18 I trust ,someone will be Jun 12 16:40:31 Or when the FSF buy Qualcomm Jun 12 16:41:56 lol Jun 12 16:42:13 @ItoRimai [I trust ,someone will be], postmarketos i guess hehe Jun 12 16:53:24 most stuff in our phones is pretty generic Jun 12 16:59:53 hi, wanted to ask something … how do i port halium to a certain device? … is there a way to learn how? … my phone is a samsung galaxy a51 and i would like to learn how to port halium to it Jun 12 17:01:10 @Sulu1415 [hi, wanted to ask something … how do i port halium to a certain device? … is there a …], https://github.com/ubports/porting-notes/wiki/Halium-9 Jun 12 17:01:18 this device would probably require Halium 10 though Jun 12 17:01:32 hmmmm Jun 12 17:01:34 thanks Jun 12 17:01:54 so basically steps for recent devices Jun 12 17:02:09 1. you need to compile kernel with few defconfig changes and make sure it boots Jun 12 17:02:26 2. make boot.img or flash halium-ramdisk and boot to telnet Jun 12 17:02:46 3. install Ubuntu Touch (or the project you're interested in) rootfs and debug things from there Jun 12 17:03:41 does it specifically have to be stuff like ubuntu touch or can i install any other linux distro that's aarch64/arm64 compatible? Jun 12 17:04:06 Ubuntu Touch, LuneOS, Droidian so far Jun 12 17:04:23 fair enough Jun 12 18:48:28 Greetings, I'm having a little trouble compiling .img files using Halium 5 for LG G4 H815 Jun 12 18:50:03 My errors currently are: No rule to make target 'halium-boot', 'mkbootimg' and 'systemimage' Jun 12 18:50:10 I must have made a mistake somewhere Jun 12 18:50:51 The only other line that I'm concerned about is 'Trying dependencies-only mode on a non-existing device tree?' when using lunch Jun 12 22:14:59 https://paste.ubuntu.com/p/Kv2zdqHgHf/ … please help can't run the "lunch" command Jun 12 22:22:09 You use breakfast with Halium 7+ with the device name. If you're running Halium 5, you just use "lunch" without the device name Jun 12 22:23:21 Lunch will display the list of software devices to use with your Halium setup. https://docs.halium.org/en/latest/porting/build-sources.html#for-halium-5-1 Jun 12 22:25:01 You also need to run the command "source build/envsetup.sh" in the same terminal before using Lunch or the device information won't show up properly. Jun 13 00:27:04 I just blank slate and restarted. Seems like someone else recently added a LG G4 manufest on Halium 7... I was running Halium 5 so... Let's see if it works out Jun 13 01:06:41 I failed at `mka mkbootimg` with the QA "HYBRIS_BOOT_PART and HYBRIS_DATA_PART". After following instructions, it's still not working **** ENDING LOGGING AT Sun Jun 13 02:59:57 2021