**** BEGIN LOGGING AT Sun Apr 01 03:00:02 2018 Apr 01 06:12:00 @Ismaelbonato, Yes Apr 01 06:32:59 dansk was added by: dansk Apr 01 14:18:41 takaturgut was added by: takaturgut Apr 01 14:19:22 "guys i was tryin to build boot image but icouldnt edit fstab thing" Apr 01 14:20:09 i guess it's about "fix mounts" on port guide but i couldn't understand exactly Apr 01 14:21:27 https://hastebin.com/neduvarego.md here is my error btw Apr 01 14:28:19 K31j0 was added by: K31j0 Apr 01 14:28:29 Hey there Apr 01 14:32:12 👋 Apr 01 14:32:50 Anyone tried to build any Xperia 2012 series device on 7.1? Trying to build lineage for z2 now, but I'm skeptical about it, because I had to comment out one blob repository, because no archive had those blobs so I think they shouldn't be a problem, but we'll see Apr 01 14:33:40 I'm trying to build for xperia m but it only has 4gigs of internal and countless problems with compiling 😆 Apr 01 14:34:43 My god, you own one of couple legends Apr 01 14:36:10 I have a working x8 😉 Apr 01 14:37:19 nice, miniC … , Apr 01 14:37:23 miniCM* Apr 01 14:37:31 Flashed couple of them Apr 01 14:38:01 I own N900 woth wrecked usb port, sending it to my friend after holidays and he'll try to repair it Apr 01 15:14:02 @VeryOriginalUsername, Unfortunately locked bootloader Apr 01 15:14:11 Too new to unlock with a free method Apr 01 15:18:46 @K31j0, 👋🏻 Apr 01 15:19:13 btw i found my solution thanks again Apr 01 15:43:22 During boot, what does halium mount on /? Apr 01 15:47:59 Or well, what is usually provided via `root=` cmdline parameter? Apr 01 15:48:13 Nothing? Apr 01 15:48:32 The image gets mounted from the data partition Apr 01 15:48:45 Yeah, I know that Apr 01 15:49:16 But with dm-verity turned on, bootloader adds dm= and root= parameters Apr 01 15:49:45 It should ignore those Apr 01 15:49:46 And I don't think it'll activate verity Apr 01 15:50:23 It does, apparently Apr 01 15:50:24 dm=system none ro,0 1 android-verity /dev/sda34 Apr 01 15:50:49 Does it break something? Apr 01 15:51:32 Yep Apr 01 15:51:37 [ 2.672585] c3 1 init: SELinux: Could not mkdir: Read-only file system Apr 01 15:51:52 SELinux is disabled in defconfig Apr 01 15:53:13 I tried enabling it and turling off via `audit=0 selinux=0` but the error persists Apr 01 15:55:57 Fix: remove selinux Apr 01 15:55:58 Xd Apr 01 15:57:29 Yeah, but it was not present in the first place... Apr 01 16:32:51 @Sergobot, Ah, also, if I replace `ro` to `rw` in `obsolete_checksetup()` in init/main.c, it gets further … So, I'd like to avoid such hacks Apr 01 16:40:56 flashed frankenlineage, how long is the typical first boot of lineage14.1? Apr 01 16:41:05 oh, it booted Apr 01 16:41:43 ...without touch Apr 01 16:43:56 weird, after rebooting it works Apr 01 20:06:23 which devices *with device tree on github* works their hwcomposer? Apr 01 21:10:43 is there a problem building to xiaomi devices? it keeps giving me that android.mk:70 Apr 01 21:10:57 which one is about partitions Apr 01 21:11:34 https://github.com/Halium/hybris-boot/pull/28/files/160405518d573aee72edfa1b593ebf1a17bd2ddb and i found this soo, any idea? Apr 02 02:04:14 i've applied the kernel patches, disabled the paranoid network, tried some crappy fix from stackoverflow (groups) and nothing worked to get the "ping" command working Apr 02 02:04:19 https://github.com/Lyudmila17/android_kernel_motorola_msm8952/commits/halium-7.1 Apr 02 02:04:45 when I do a chroot while i'm on the adb shell i get some commands unknown **** ENDING LOGGING AT Mon Apr 02 03:00:02 2018