**** BEGIN LOGGING AT Thu Dec 06 03:00:01 2018 Dec 06 04:20:39 @Ben Mayo, Hi! Have you seen the discussion above about A/B devices? Dec 06 04:20:48 @Ben Mayo, [Edit] Hello! Have you seen the discussion above about A/B devices? Dec 06 04:22:30 @ilyaishere, I have not. I scrolled through some of the message history but I didn't see anything. Dec 06 04:23:36 @johanneswk00, Starts here ^ Dec 06 06:05:06 So, compiled successfully but I can't get halium-boot to boot properly. Looked throught the logs and it appears device-mapper is trying to map android-verity. I have removed the verity pieces from my device.mk file and disabled the references to verity in my kernel config. Any ideas as to how to get around this? Log: https://paste. Dec 06 06:05:06 ubuntu.com/p/kJzm8DWVZt/ Dec 06 06:36:23 @f171pp0, What is the device code name? Dec 06 08:00:33 @abhishek_0, Xiaomi redmi 4 Prime, codename markw Dec 06 08:58:21 @f171pp0, Have you tried asking any of the device maintainers? Dec 06 09:02:48 device is pretty active on xda Dec 06 09:27:32 Haven't tried yet, I will now Dec 06 09:34:27 Thanks Dec 06 10:03:35 I'm considering porting halium to the Samsung Galaxy Nexus but the kernel is quite old (3.0.x) and I can't find any newer port. Do you see any problem with that? Dec 06 10:17:19 Hi, I still don't know how to fixup-mountpoints for Mocha. … I have for example the following line in fstab: … /dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait … How do I know what to put for this line and what mmcblkMpN corresponds? Dec 06 10:17:46 [Edit] Hi, I still don't know how to make the fixup-mountpoints file for Mocha. … I have for example the following line in fstab: … /dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait … How do I know what to put for this line and what mmcblkMpN corresponds? Dec 06 10:18:37 @Dargons10, `readlink /dev/block/platform/sdhci-tegra.3/by-name/APP` on device? Dec 06 10:21:55 i saw that in others devices the lines are block/platform/msm_sdcc.1/by-name/system mmcblk0p21 Dec 06 10:31:32 @minlexx, I have to write that in adb with device connect, havent you? Dec 06 10:33:20 @Dargons10, connected device in recovery mode (twrp), yes … and on host, `adb shell` Dec 06 10:34:22 @minlexx, Ok thanks a lot Dec 06 10:47:27 @minlexx, This three too? … /devices/platform/sdhci-tegra.2/mmc_host* auto auto defaults voldmanaged=sdcard1:auto,encryptable=userdata … /devices/platform/tegra-ehci.*/usb* auto auto defaults Dec 06 10:47:27 voldmanaged=usb:auto … /dev/block/platform/sdhci-tegra.2/by-num/p1 /sdcard vfat defaults recoveryonly Dec 06 10:49:43 @Dargons10, I think halium docs explicitly say which ones are needed, in https://docs.halium.org/en/latest/porting/build-sources.html#include-your-device-in-fixup-mountpoints Dec 06 10:50:08 For every line in fstab where the type is not auto, emmc or swap Dec 06 10:50:34 @minlexx, i dont get anything in that tree lines Dec 06 10:51:20 @Dargons10, [Edit] `readlink -f /dev/block/platform/sdhci-tegra.3/by-name/APP` on device? Dec 06 12:02:11 i get this errors in mka hybrys-boot … https://paste.ubuntu.com/p/Jc2HnyYMqC/ Dec 06 12:04:06 @Dargons10, you have some error in your block in fixup-mountpoints Dec 06 12:04:49 (Document) https://irc.ubports.com/d3yqNFH1.null Dec 06 12:05:06 this is my file with mocha lines Dec 06 12:06:05 (Document) https://irc.ubports.com/zYwJE4m9.txt Dec 06 12:06:34 and this is the file where i look at the fstab Dec 06 12:07:19 (Photo, 669x168) https://irc.ubports.com/2fk21kTt.png there is a TAB instead of spaces that probably breaks everything Dec 06 12:13:36 @minlexx, Everything else is okay? Dec 06 12:14:44 seems so Dec 06 12:21:10 I'm downloading Halium sources .. … Can I reuse them to build LineageOS as well? (To save data - the downloads are huge😅) Dec 06 12:39:23 @minlexx, after fix it now i get a different error … https://paste.ubuntu.com/p/vpbFvP4z7t/ Dec 06 12:40:38 @Dargons10, there is no error message in this paste Dec 06 12:43:42 @minlexx, i dont find othe fail Dec 06 12:43:55 (Document) https://irc.ubports.com/3Jg2ouJB.txt Dec 06 12:44:20 this is the log from my compiling. Could you look at, please? Dec 06 12:49:37 looks like your device kernel is being compiled with warnings, and warnings are treated as errors (line 2900: `cc1: all warnings being treated as errors`) Dec 06 12:50:32 @minlexx, this kernel works in ubuntu for mocha. Ill try the kernel for lineage Dec 06 12:54:23 @Waseem Alkurdi, Anybody?😂 Dec 06 12:55:45 @Waseem Alkurdi, are different sources Dec 06 12:57:55 Hi, I have found vendor blobs for my devices, when here https://docs.halium.org/en/latest/porting/get-sources.html#vendor-blobs the documentation says that I have to add blobs to ```vendor``` do they mean that I just have to copy all files that I've found to ```vendor/```? Dec 06 12:58:33 @f171pp0, Copy no. You have to clone it. Dec 06 12:59:13 just clone the repo containing the files into vendor/? Dec 06 12:59:37 What is your device? Dec 06 12:59:53 @f171pp0, add a manifest line for it Dec 06 13:00:19 @Dargons10, Xiaomi redmi 4 Prime codename markw Dec 06 13:00:44 In vendor/xiaomi/markw Dec 06 13:00:51 like here https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/xiaomi_mido.xml#L7 Dec 06 13:02:33 @f171pp0, are they on github? in what repo? Dec 06 13:04:07 @minlexx, this helped Dec 06 13:04:37 you will probaby have different `remote` if not on TheMuppets Dec 06 13:04:41 @minlexx with lineage kernel now is succesfully the compilation!! Dec 06 13:04:48 sorry for dumb questions, but I'm really new to this Dec 06 13:05:47 Now im in mka systemimage Dec 06 13:07:10 @minlexx, I've forked some repo from a guy that did some custom rom for my device and there is also one with vendor blobs Dec 06 13:22:25 @Dargons10, How? Aren't we essentially cloning LineageOS' 14.1 branch when we clone Halium's source? Dec 06 13:23:19 @Waseem Alkurdi, some repos are the same, yes, you can probably copy manually, dunno Dec 06 13:25:19 @Waseem Alkurdi, Yes essentially Dec 06 13:37:37 @Dargons10, That's what I'm thinking Dec 06 13:37:45 So can't we use the resulting repo Dec 06 13:37:56 To build plain ol' LineageOS? Dec 06 13:38:16 Or is it different? Dec 06 18:05:19 I'm at the Document section https://docs.halium.org/en/latest/porting/get-sources.html#document to create a pull request do I need to fork the repo, create the manifest for my device and then create a pull request? Dec 06 18:44:46 Hi, when I run ```./mer_verify_kernel_config ``` I get lots of errors and warnings, do I have to edit the kernel configuration file according to what the output of this command says till I get no error? Dec 06 20:20:05 Fwd from abhishek_01: no , For eg. if error says ```CONFIG_NLS_UTF8 is invalid``` like in line 2 … check for allowed values … in line 4 it is ```y``` … now go to your defconfig which is `msm8916_sec_j5lte_eur_defconfig` … in that file search for "CONFIG_NLS_UTF8" … change it from ```# CONFIG_NLS_UTF8 is not set``` to ``` Dec 06 20:20:05 CONFIG_NLS_UTF8=y``` Dec 06 20:20:05 Fwd from abhishek_01: and repeat the steps untill you fixed all the errors Dec 06 20:20:08 @f171pp0 Dec 06 20:33:52 @minlexx hi i get some errors at 99% in hardware_broadcom whe i make mka systemimage Dec 06 20:36:39 in libbt folder … https://paste.ubuntu.com/p/3psBQX5PHk/ Dec 06 20:38:38 is this folder for BT? Dec 06 20:39:57 yes Dec 06 20:40:10 Could i delete? Dec 06 20:41:10 uhm yes but the error is weird. it's not catching that line 3 is a comment Dec 06 20:41:15 did you touch that file? Dec 06 20:42:14 yes, i changed from lineageOS because always i got errors. Dec 06 20:42:49 I'm pretty sure bcm libbt compiles just fine Dec 06 20:43:41 Did you delete line 1 on src/bt_vendor_brcm.c or something Dec 06 20:43:56 @aleasto, Not to me, always it told me thar somes files not found like userial.h Dec 06 20:44:43 @aleasto, I changed all Dec 06 20:44:43 Idk, I built whatever ships with halium's manifest some weeks ago Dec 06 20:44:48 Anyways you can delete Dec 06 20:45:00 Unless you want BT ofc lel Dec 06 20:45:52 ok i deleted to prove that it's the only thing that failed me. Dec 06 20:46:14 @abhishek_0, Thankss Dec 06 20:49:22 ok, now is all compile but i get this … failed to reconstruct target deflate chunk 1 [(null)]; treating as normal Dec 06 20:49:29 is this a problem? Dec 06 21:39:57 ok mka bootimg, mka kybrid-root and mka systemimage is succesfully now next step! Dec 06 21:56:23 I would like to try KDE Plasma Mobile, The steps would be as follows? … 1. fastboot flash boot [path/to/]hybris-boot.img … 2. Download Plasma mobile rootfs from here: … https://images.plasma-mobile.org/rootfs/ … 3. use the halium-install script … halium-install … Is all ok? Dec 06 22:17:45 Guys, where i can find the latest version of halium rootfs (caf) ? Dec 07 00:45:51 Is the file ```fixup-mountpoints``` correct like this? Or have I to remove /dev/ in front of [src] and /dev/block/ before the output of ```readlink -f [src]``` https://paste.ubuntu.com/p/bXgq5Z6yqy/ Dec 07 00:48:27 @f171pp0, remove /dev and /dev/block Dec 07 00:48:50 (Sticker, 512x512) https://irc.ubports.com/Ntb2nUSt.webp Dec 07 00:48:57 👍 Dec 07 01:02:54 @Dargons10, 2. probably from there - https://images.plasma-mobile.org/caf-rootfs/ … 3. `halium-install -p pm -v ` Dec 07 01:03:09 @Dargons10, [Edit] 2. probably from there - https://images.plasma-mobile.org/caf-rootfs/ (depends on device) … 3. `halium-install -p pm -v ` Dec 07 01:37:00 @Dargons10, where can I see the whole source file with errors? `hardware/broadcom/libbt/src/bt_vendor_brcm.c` Dec 07 02:20:15 @minlexx, Ok thanks. Dec 07 02:21:23 @minlexx, When i compiled i used the next command … Mka systemimage | tee log.txt Dec 07 02:22:38 But when my compile was successfully i used that command too, then my log.txt is successfully too. Dec 07 02:47:24 @Mattia990, There isn't, we are using that old reference rootfs **** ENDING LOGGING AT Fri Dec 07 03:00:01 2018