**** BEGIN LOGGING AT Thu Jan 14 02:59:57 2021
Jan 14 06:41:24 <ubptgbot> <ArunSojanParolikkal> @Herrie1982 [Got a quick builder here, so can easily test :P], Could you tell me where the halium.mk file originates from?
Jan 14 06:53:09 <ubptgbot> <Daniel K> When building the system image, I get an error  for one of the files missing: stml0xx I had a look in the muppets github and the file doesn't exist for cm-14.1.
Jan 14 06:53:48 <ubptgbot> <Daniel K> Do i get it from another version of lineage, do I need it at all?
Jan 14 06:54:13 <ubptgbot> <Daniel K> Error: ninja: error: 'vendor/motorola/msm8916-common/proprietary/bin/stml0xx', needed by '/home/daniel/halium/out/target/product/osprey/system/bin/stml0xx', missing and no known rule to make it
Jan 14 06:55:25 <ubptgbot> <Herrie1982> @ArunSojanParolikkal [Could you tell me where the halium.mk file originates from?], From hybris-patches: https://github.com/Halium/hybris-patches/blob/halium-9.0/build/make/0003-halium-add-basic-Halium-build-configuration-based-on.patch
Jan 14 06:55:42 <ubptgbot> <Herrie1982> But if you follow the build instructions properly that shouldn't be of your concern
Jan 14 06:59:07 <ubptgbot> <Daniel K> Anyone able to help?
Jan 14 07:01:26 <ubptgbot> <Herrie1982> @Daniel K [Anyone able to help?], You're building 7.1 right?
Jan 14 07:01:41 <ubptgbot> <Daniel K> Yes sir.
Jan 14 07:02:06 <ubptgbot> <Herrie1982> Where do you have your motorola_osprey.xml
Jan 14 07:02:07 <ubptgbot> <Herrie1982> ?
Jan 14 07:04:58 <ubptgbot> <Herrie1982> Can you paste the contents somewhere?
Jan 14 07:05:09 <ubptgbot> <Herrie1982> Or you have it on a github repo maybe?
Jan 14 07:05:40 <ubptgbot> <Daniel K> https://pastebin.com/47D3etLC
Jan 14 07:10:58 <ubptgbot> <Daniel K> I have previously used the file from cm14.0 to get around this. I don't know what the file is so I want to do a clean make this time.
Jan 14 07:16:57 <ubptgbot> <ArunSojanParolikkal> @Herrie1982 [But if you follow the build instructions properly that shouldn't be of your conc …], I did follow the instructions. For Halium 9 and the general instructions. And I did the same thing four times to be sure.
Jan 14 07:18:56 <ubptgbot> <Herrie1982> @Daniel K [I have previously used the file from cm14.0 to get around this. I don't know wha …], I'm building at my end, give me a few minutes
Jan 14 07:19:21 <ubptgbot> <Daniel K> Thank you
Jan 14 07:24:06 <ubptgbot> <Herrie1982> Seems it was removed with this commit: https://github.com/TheMuppets/proprietary_vendor_motorola/commit/a4cfd5bd2147cba254e986d109063ec712070a99#diff-18cbc9c3312c0a3bcf7fe7d65864d5e51fae3c3d4c379015fa31ebb108002627
Jan 14 07:24:22 <ubptgbot> <Herrie1982> I suggest you fork TheMuppets and simply add the file back from an earlier commit
Jan 14 07:24:52 <ubptgbot> <Daniel K> ok.
Jan 14 07:25:04 <ubptgbot> <Herrie1982> I.e.: https://github.com/TheMuppets/proprietary_vendor_motorola/blob/a017e7a4014940f3ae7027b8c710bd14591ffb67/msm8916-common/proprietary/bin/stml0xx
Jan 14 07:25:20 <ubptgbot> <Herrie1982> Not sure why they removed it, looks like a mistake to be honest
Jan 14 07:25:59 <ubptgbot> <Daniel K> I can extract it from my phone, it is running Linage 14.1 then fork it.
Jan 14 07:27:04 <ubptgbot> <Daniel K> Would this file be the one?
Jan 14 07:29:03 <ubptgbot> <Herrie1982> You can simply download it from above link
Jan 14 07:29:51 <ubptgbot> <Daniel K> Thank you for your help
Jan 14 07:34:35 <ubptgbot> <Daniel K> There is more files missing for cm14.1 vendor/motorola/msm8916-common/proprietary/lib/hw/sensorhub.msm8916.so
Jan 14 07:37:03 <ubptgbot> <Daniel K> How did you find the delete files on github?
Jan 14 07:38:48 <ubptgbot> <Daniel K> ok worked it out
Jan 14 08:03:05 <ubptgbot> <Herrie1982> Sometimes they update and remove things
Jan 14 08:03:33 <ubptgbot> <Herrie1982> It's a bit of a shame we cannot pin a specific commit in the device manifests in halium-devices
Jan 14 09:07:50 <ubptgbot> <Max> so is there maybe an older version of halium-install available or not?
Jan 14 09:07:57 <ubptgbot> <Max> thanks
Jan 14 11:12:53 <ubptgbot> <Deathmist1337> @Max [so is there maybe an older version of halium-install available or not?], why not share the error you have? no one can help if they don't know what is going wrong. does the problem you have happen with https://gitlab.com/JBBgameich/halium-install?
Jan 14 12:32:16 <ubptgbot> <H@ñß9ñ> What operating system you guys used to build halium
Jan 14 12:32:29 <Tofe> Herrie: well, it's possible to try: "Tags and/or explicit SHA-1s should work in theory, but have not been extensively tested"
Jan 14 12:47:04 <ubptgbot> <Herrie1982> @H@ñß9ñ [What operating system you guys used to build halium], Used Ubuntu 16.04 in the past as well as KUbuntu 18.04, now on KUbuntu 18.04 at my end
Jan 14 12:49:11 <ubptgbot> <H@ñß9ñ> @Herrie1982 [Used Ubuntu 16.04 in the past as well as KUbuntu 18.04, now on KUbuntu 18.04 at …], Can I use windows 10
Jan 14 12:49:29 <ubptgbot> <Herrie1982> @H@ñß9ñ [Can I use windows 10], Maybe, never tried
Jan 14 12:49:39 <ubptgbot> <H@ñß9ñ> On the documentation ubports it's used Linux command
Jan 14 12:49:54 <ubptgbot> <H@ñß9ñ> Ok I'll try thanks
Jan 14 12:50:44 <ubptgbot> <Herrie1982> Well you have WSL on Win10 now
Jan 14 12:50:57 <ubptgbot> <Herrie1982> So theoretically it could work
Jan 14 12:51:21 <ubptgbot> <Herrie1982> Otherwise you could run Ubuntu in a VirtualBox for example
Jan 14 13:47:56 <ubptgbot> <Abdullah AL Shohag> Can anyone look at this problem? https://stackoverflow.com/questions/65719101/error-on-building-lineageos-for-nokia-2-dynamo-e1m
Jan 14 13:50:12 <ubptgbot> <Herrie1982> This is for Halium, not for LineageOS
Jan 14 14:04:13 <ubptgbot> <H@ñß9ñ> Halium need lineage os too
Jan 14 14:04:22 <Herrie> That is true
Jan 14 14:04:39 <Herrie> But if you have LOS specific issues better to check LOS channels
Jan 14 14:10:08 <ubptgbot> <NotKit> Abdullah AL I had a look at https://github.com/AndroidBlobs/device_nokia_Dynamo and it's not useful for Halium (kernel compilation is not set up at all, it just copies blobs to vendor and configuration files)
Jan 14 14:11:29 <ubptgbot> <ArunSojanParolikkal> Does anyone know what this indicates when running "make halium-boot"? ninja: error: '/home/actuday/dev/hallium3/out/target/product/a10/kernel', needed by '/home/actuday/dev/hallium3/out/target/product/a10/obj/ROOT/halium-boot_intermediates/halium-boot.img', missing and no known rule to make it
Jan 14 14:25:13 <ubptgbot> <ankaos> hı. ı build vendor.img and read me `ninja: error: 'fstab.qcom', needed by '/home/enes/oxygen-9/out/target/product/oxygen/vendor.img', missing and no known rule to make it`
Jan 14 14:26:28 <ubptgbot> <ArunSojanParolikkal> @ArunSojanParolikkal [Does anyone know what this indicates when running "make halium-boot"? ninja: err …], The entire output from make: https://pastebin.com/aznxR9rW
Jan 14 15:30:45 <ubptgbot> <arpio1> You using prebuild kernel? … vendor/lineage/build/tasks/kernel.mk:108: warning: * Using prebuilt kernel binary instead of source
Jan 14 16:42:33 <ubptgbot> prohackerbro was added by: prohackerbro
Jan 14 17:22:01 <ubptgbot> Fuji_Sleepy was added by: Fuji_Sleepy
Jan 14 17:23:00 <ubptgbot> <ArunSojanParolikkal> @arpio1 [You using prebuild kernel? … vendor/lineage/build/tasks/kernel.mk:108: warning: * …], Isn't this the kernel source for the a10? https://github.com/geckyn/android_kernel_samsung_exynos7885
Jan 14 17:23:14 <ubptgbot> <ArunSojanParolikkal> I have this in my manifest.xml
Jan 14 17:23:35 <ubptgbot> <Max> need help always getting rror: system/bt/types/Android.bp:9:1: module "libbluetooth-types" variant "linux_glibc_x86_64_static": source path hardware/samsung_slsi/libbt/include does not exist … error: system/bt/types/Android.bp:9:1: module "libbluetooth-types" variant "linux_glibc_x86_64_static": source path hardware/samsung_slsi/libbt/include
Jan 14 17:23:35 <ubptgbot>  does not exist … error: system/bt/include/Android.bp:1:1: module "avrcp_headers" variant "linux_glibc_x86_64": source path hardware/samsung_slsi/libbt/include does not exist … error: system/bt/packet/base/Android.bp:1:1: module "lib-bt-packets-base" variant "linux_glibc_x86_64_static": source path hardware/samsung_slsi/libbt/include does not exist
Jan 14 17:23:35 <ubptgbot>  … ninja: build stopped: subcommand failed. … 17:21:35 soong bootstrap failed with: exit status 1
Jan 14 17:39:36 <ubptgbot> <arpio1> @ArunSojanParolikkal [Isn't this the kernel source for the a10? https://github.com/geckyn/android_kern …], Yes, did you try a clean built?  In your logs it looks like you rebuilding after some changes.
Jan 14 17:41:35 <ubptgbot> <ArunSojanParolikkal> @arpio1 [Yes, did you try a clean built?  In your logs it looks like you rebuilding after …], To the kernel configs?
Jan 14 17:42:32 <ubptgbot> <ArunSojanParolikkal> Yes, I did change the kernel configs that were causing errors when checked using the 'mer-something' tool mentioned in the porting guide.
Jan 14 17:43:21 <ubptgbot> <ArunSojanParolikkal> @arpio1 [Yes, did you try a clean built?  In your logs it looks like you rebuilding after …], I'll try skipping that step then.
Jan 14 17:45:11 <ubptgbot> <ArunSojanParolikkal> (Photo, 606x1280) https://irc.ubports.com/vVuedq6i.png
Jan 14 17:45:25 <ubptgbot> <ArunSojanParolikkal> @ArunSojanParolikkal [<reply to media>], This is the step I mentioned
Jan 14 18:00:18 <ubptgbot> <antoine_62> Is halium9 compatible with devices with no vendor partitions?
Jan 14 18:02:07 <ubptgbot> <NotKit> kind of possible, but not well tested and there are known issues (though some of them resolved very recently in hybris-patches)
Jan 14 18:02:36 <ubptgbot> <Herrie1982> Which device you have?
Jan 14 18:03:12 <ubptgbot> <antoine_62> Galaxy tab a6, i have to use halium9, samsung broke los14.1 with the orea update
Jan 14 18:03:44 <ubptgbot> <antoine_62> @NotKit [kind of possible, but not well tested and there are known issues (though some of …], I currently have a too many level of symbolic links error whrn starti-g the container.
Jan 14 18:03:55 <ubptgbot> <antoine_62> [Edit] Galaxy tab a6, i have to use halium9, samsung broke los14.1 with the oreo update
Jan 14 18:04:09 <ubptgbot> <Herrie1982> @antoine_62 [I currently have a too many level of symbolic links error whrn starti-g the cont …], That's a known issue with certain kernels
Jan 14 18:04:17 <ubptgbot> <Herrie1982> Which kernel version you have?
Jan 14 18:04:26 <ubptgbot> <antoine_62> @Herrie1982 [Which kernel version you have?], 3.18, its not in /proc.
Jan 14 18:04:49 <ubptgbot> <antoine_62> It never happened with the broken gsi port
Jan 14 18:05:11 <ubptgbot> <NotKit> @antoine_62 maybe you need to modify /vendor symlink to point to /system/vendor?
Jan 14 18:05:21 <ubptgbot> <NotKit> in rootfs
Jan 14 18:05:55 <ubptgbot> <antoine_62> Its the container that doesnt start
Jan 14 18:06:27 <ubptgbot> <NotKit> send ls -la / /vendor and full LXC logs
Jan 14 18:07:46 <ubptgbot> <antoine_62> Will do tomorrow, im not on my pc, but i remember that ls -la / sjow that vendor is mounted to /android/vendor (and is mounted correctly), vendor is not also not empty
Jan 14 18:08:52 <ubptgbot> <antoine_62> "Too many level of symbolic links - vendor in /usr/lib/aarch64-linux-gnu/lxc/vendor was a symbolic link!"
Jan 14 18:09:08 <ubptgbot> <antoine_62> And that's the error in lxc logs
Jan 14 18:36:41 <ubptgbot> <antoine_62> Any idea, or those arent enough?
Jan 14 18:39:11 <ubptgbot> <NotKit> not enough, but feels like something is still off with symlinks and not
Jan 14 18:39:23 <ubptgbot> <NotKit> LXC is configured to bind-mount /vendor to /var/lib/lxc/android/rootfs/vendor
Jan 14 18:39:56 <ubptgbot> <NotKit> so if /var/lib/lxc/android/rootfs/vendor is symlink, this will also fail
Jan 14 18:41:19 <ubptgbot> <antoine_62> Alright, i will give you that tomorrow
Jan 14 23:44:05 <ubptgbot> <Daniel K> I did another clean build for Moto G  2015 Osprey again after 6 months or so. Still in reboot loop and able to connect to SSH but but not long enough to stop lightdm from rebooting the system (if that is causing it) any ideas guys?
Jan 14 23:44:27 <ubptgbot> <Daniel K> I never worked this out back 6 months ago so I quit.
Jan 15 01:57:56 <ubptgbot> <Fuseteam> uh do you mean you quit back then but are looking to tackle it again or......
Jan 15 01:58:12 <ubptgbot> <Fuseteam> [Edit] uh do you mean you quit back then and are looking to tackle it again now or......
Jan 15 02:15:38 <ubptgbot> <arpio1> @Daniel K [I did another clean build for Moto G  2015 Osprey again after 6 months or so. St …], You should be able to mount rootfs in twrp and disable autostart. But I don't know exactly which file it is.
**** ENDING LOGGING AT Fri Jan 15 02:59:57 2021