**** BEGIN LOGGING AT Sun Jul 15 03:00:02 2018
Jul 15 08:05:19 <ubptgbot> <Xessao> Hello everyone! I'm trying to port halium 7.1 to Xiaomi Mi Max 2. I'm faced with the problem of creating a manifest when I needed to add vendor blobs. I couldn't find my device in TheMuppets and Google Search. Where can I get vendor blobs or can I create them somehow?
Jul 15 08:08:02 <ubptgbot> <Lyokanthrope> @Xessao, https://github.com/ashwinr64/android_vendor_xiaomi_oxygen Try this
Jul 15 08:10:06 <ubptgbot> <Lyokanthrope> In case you're wondering where I found it: https://forum.xda-developers.com/mi-max-2/development/rom-lineageos-14-1-t3759587
Jul 15 08:10:31 <ubptgbot> <Xessao> @Lyokanthrope, I forgot about search on github. Thank you!
Jul 15 08:10:49 <ubptgbot> <Lyokanthrope> 👍
Jul 15 08:36:32 <ubptgbot> NitroFM was added by: NitroFM
Jul 15 08:40:04 <ubptgbot> <NitroFM> Hi I recently tried to Port halium 7.1 on my mi a1(Tissot) but I am always getting " *** There should be one and only one device entry for HYBRIS_BOOT_PART and HYBRIS_DATA_PART.  … I followed the guide here https://docs.halium.org/en/latest/porting/build-sources.html#breakfast-and-lunch … and I repeated it at least three times. Any
Jul 15 08:40:04 <ubptgbot> help would be appreciated :)
Jul 15 08:56:50 <ubptgbot> <NitroFM> [Edit] Hi I recently tried to Port halium 7.1 on my mi a1(Tissot) but I am always getting " *** There should be one and only one device entry for HYBRIS_BOOT_PART and  HYBRIS_DATA_PART.  … when I type "make -j4 mkbootimg" … I followed the guide here https://docs.halium.org/en/latest/porting/build-sources.html#breakfast-and-lunch … a
Jul 15 08:56:50 <ubptgbot> nd I repeated it at least three times. Any help would be appreciated :)
Jul 15 09:27:40 <ubptgbot> <superl2> This is just a guess, but I think it may be to do with a/b partitioning
Jul 15 09:29:24 <ubptgbot> <NitroFM> @superl2, Yeah, maybe it thinks that it's two devices due to the two boot partitions(boot.a boot.b)
Jul 15 09:30:58 <ubptgbot> <NitroFM> Although it's weird that it already had a manifest in halium source when it doesn't work :/
Jul 15 09:33:16 <ubptgbot> <NitroFM> now I deleted the error line in android.mk to see what will happen
Jul 15 10:00:11 <ubptgbot> <abhishek_01> So many device popping up for halium :')
Jul 15 10:01:35 <ubptgbot> <theimpulson> Halium is the new craze
Jul 15 10:03:35 <ubptgbot> <abhishek_01> Can't wait to see UT on these many devices... If it was not broken
Jul 15 10:03:39 <ubptgbot> <abhishek_01> 😛
Jul 15 10:19:26 <ubptgbot> <NitroFM> now after the first command (make mkbootimg(which succeeded ) I run "make hybris-boot" and after 30min it says "recipe for target 'ninja wrapper' failed
Jul 15 10:48:31 <ubptgbot> <abhishek_01> @NitroFM, Whats the error?
Jul 15 10:50:25 <ubptgbot> <NitroFM> I'm now trying to build system img so I can't see the log right now. I will tell ya in a while.
Jul 15 10:53:08 <ubptgbot> <NitroFM> But so far the error said "/build/core/ninja.mk 150: Recipe for Target 'ninja wrapper' failed
Jul 15 10:54:40 <ubptgbot> <abhishek_01> That's not the error paste the whole log
Jul 15 10:55:34 <ubptgbot> <NitroFM> Oh ok after I build system I will paste it.
Jul 15 10:57:19 <ubptgbot> <Walid> for halium-7.1 and caf device, there is any recommended ubuntu touch rootfs ?
Jul 15 11:11:57 <ubptgbot> <NitroFM> @abhishek_01, It seems that my PC has the problem because it couldn't allocate memory. I only have 2gb ram so that's why.
Jul 15 11:37:30 <ubptgbot> <Xessao> @NitroFM, Use swap?
Jul 15 11:40:24 <ubptgbot> <Xessao> @NitroFM, Same error with systemimage. :(
Jul 15 12:55:23 <ubptgbot> <Xessao> I'm trying to compile system.img, but I get error: https://hastebin.com/huvavisogo.coffeescript … Vendor blob: … https://github.com/ashwinr64/android_vendor_xiaomi_oxygen/tree/cm-14.1/proprietary/bin … What to do?
Jul 15 12:56:18 <ubptgbot> <superl2> I think that's a proprietary file you're missing
Jul 15 12:56:34 <ubptgbot> <Xessao> I understand it.
Jul 15 12:57:00 <ubptgbot> <superl2> You need to get the blog
Jul 15 12:57:10 <ubptgbot> <superl2> [Edit] You need to get the blob
Jul 15 12:57:18 <ubptgbot> <Xessao> I understand it.
Jul 15 12:58:42 <ubptgbot> <Xessao> But this blob isn't in the repository that I use.
Jul 15 12:59:05 <ubptgbot> <superl2> So pull it from your device
Jul 15 12:59:37 <ubptgbot> <Xessao> So it is possible?
Jul 15 12:59:42 <ubptgbot> <superl2> Yes
Jul 15 12:59:47 <ubptgbot> <Xessao> Hm...
Jul 15 12:59:57 <ubptgbot> <Xessao> I'm going to try now.
Jul 15 13:00:00 <ubptgbot> <Xessao> Thanks!
Jul 15 13:00:05 <ubptgbot> <superl2> Yw
Jul 15 16:46:33 <ubptgbot> <Dzmitry Sankouski> Hi everyone! … I have a problem with lxc@android container. It seems, that problem is with "wifiloader" program. I tried to delete this file and container started  normally.  … Any suggestions? … ksmg: https://pastebin.com/AsyrqC2H
Jul 15 18:37:32 <ubptgbot> <Dzmitry Sankouski> And if I start lxc@android service with wifiloader program present in a container, the phone reboots after a second
Jul 15 18:38:42 <ubptgbot> <Dzmitry Sankouski> As I said before, if I delete wifiloader from android container, lxc@android service starts normally
Jul 15 22:38:25 <futuretoast> Hello I'm stuck on the fixup-mountpoints part of
Jul 15 22:38:41 <futuretoast> Sorry accidentally pressed send too early
Jul 15 22:46:34 <ubptgbot> Mauri_9291 was added by: Mauri_9291
**** ENDING LOGGING AT Mon Jul 16 03:00:01 2018