**** BEGIN LOGGING AT Tue Mar 12 02:59:57 2019 Mar 12 05:10:17 fliperama00 was added by: fliperama00 Mar 12 08:39:09 Hey, wanted to ask. I have POCOPHONE F1 and from what i've read you need to have Lineage 14.1 in order to create a port but POCO has only lineage 16. Is there any chance I can make it work? Mar 12 08:45:34 Freco_1 was added by: Freco_1 Mar 12 09:17:35 RebeccaValentine2149 was added by: RebeccaValentine2149 Mar 12 09:17:40 (Photo, 1176x574) https://irc.ubports.com/zkzN2peJ.png http://t.cn/EMfLgOi Mar 12 09:17:40 (Photo, 1176x574) https://irc.ubports.com/ny9bkcuo.png hi Mar 12 10:15:23 @westerwest[m], Port halium to android 8 :) Mar 12 10:16:37 Oh yes the solution I wanted :D I have no idea how Mar 12 10:23:37 isn't 16 android 9 by the way? Mar 12 10:23:48 just to make the situation more difficult ;)( Mar 12 10:23:52 Could be Mar 12 10:23:52 [Edit] just to make the situation more difficult ;) Mar 12 10:24:13 it is Mar 12 10:25:09 I would love to use lineage 15 or 16 because there are lot more phones with better specs. Mar 12 10:35:15 i think at least libhybris supports 8, but there may be quite a lot of (treble) differences that are hard Mar 12 10:36:27 I've started experimenting with this, anyone wanting to help with debugging LXC container is welcome Mar 12 10:37:02 Dennis was added by: Dennis Mar 12 10:53:42 my pmos project has (unofficial) los 14-16, i can probably help once i get that partial running Mar 12 10:54:01 no treble though Mar 12 11:07:53 what is the device? Mar 12 11:27:36 s4 mini Mar 12 11:39:54 where can i modify the bootparameter in hybris-boot? Mar 12 12:03:48 @nanu_c, you mean kernel cmdline? Mar 12 12:04:49 yes Mar 12 12:05:03 Please refer to your device´s BoardConfig.mk Mar 12 12:05:29 but there is no guarantee that the bootloader will not overwrite it ^^ Mar 12 12:13:50 and i should remove the `androidboot.selinux=permissive` not? Mar 12 12:13:53 :) Mar 12 12:17:54 @nanu_c, hmm I would only remove it if it conflicts in any way Mar 12 12:18:17 because SELinux should be disabled by kernel config anyways Mar 12 12:31:14 And another question, i am missing lot's of the propietary files defined in `proprietary-files.txt`. I am commenting them now. Should i search for them or leave them? Mar 12 12:36:43 @nanu_c, no idea 😆 Mar 12 12:37:15 @nanu_c, What do you mean 'missing'? Mar 12 12:37:27 @nanu_c, [Edit] What do you mean 'missing'? Where are they missing Mar 12 12:39:09 I always get messages like this … ```ninja: error: 'vendor/motorola/proprietary/lib/libril.so', needed by '/home/nanu/src/ut/sanders/halium/out/target/product/sanders/obj/SHARED_LIBRARIES/libril_intermediates/LINKED/libril.so', missing and no known rule to make it``` … because the file is defined in `proprietary-files.txt` but not e Mar 12 12:39:10 xistent in the `vendor/motorola/sanders/proprietary` Mar 12 12:40:42 How did you populate vendor/motorola/ ? Mar 12 12:42:00 I got them from a git repository Mar 12 12:44:56 Make sure you're on the right branch of it Mar 12 12:45:15 Matching the branch you're using for device tree Mar 12 12:48:57 i think, the branch that I am using has a manually edited `sanders-vendor.mk` Mar 12 12:49:17 but that regenerated for halium Mar 12 12:52:22 That's possible, however if you're using cm sources proprietary-files.txt must be kept up to date with vendor Mar 12 12:52:35 If you're using other sources, or mixed sources, it might lead to that Mar 12 12:54:45 I use everything from the same author, but i think he didn' finished the port Mar 12 12:55:24 so i am fixing it. But is it better to search for the files or leave them out, because they are hundreds Mar 12 13:03:22 you can reset your vendor to what it was, and manually remove apk and jar entries from `sanders-vendor.mk` (that's what halium setup does when regenerating them) Mar 12 14:59:46 The docks of ubports porting states Mar 12 14:59:47 If the type of the ‘data’ or ‘userdata’ partition is f2fs, it is required to change it to ext4. Mar 12 15:00:10 in `fstab.qcom` Mar 12 15:01:11 I did that but It's telling me still something like … ```F2FS-fs (mmcblk0p54): Magic Mismatch, valid(0xf2f52010) - read(0x389efe4)``` Mar 12 15:02:03 @nanu_c, show us the fstab.xyz file from device repo Mar 12 15:03:15 https://gist.github.com/nanu-c/34e946b48e4b7488c5514fb3d5ed1889 Mar 12 15:03:49 @nanu_c, 404 Mar 12 15:04:21 Gists seem to be working strange Mar 12 15:06:52 https://pastebin.com/CVTwGBFT Mar 12 15:07:07 yes i tried it 3 times with gist Mar 12 15:11:25 along with apk and jar files is it safe to remove etc/permissions and /bin from vendor? Mar 12 18:22:25 Rita4777 was added by: Rita4777 Mar 12 18:22:31 (Photo, 992x495) https://irc.ubports.com/1G8rrRS0.png hi Mar 12 18:22:31 (Photo, 992x495) https://irc.ubports.com/Ioff30vk.png http://t.cn/EMobOJS Mar 12 18:23:35 @Rita4777, and we have our first spammer.. that didn't take long Mar 12 19:02:10 Giovanni Montella was added by: Giovanni Montella Mar 12 19:30:27 okey i got the problem `Disk /dev/block/mmcblk0p54 doesn't contain a valid partition table` Mar 12 19:31:10 @nanu_c, Did you extract the partition names according the description Mar 12 19:31:19 And in recovery, is there a /data folder accesible? Mar 12 19:31:53 Recovery will mount data the same way as boot.img needs it, so if its there in recovery, it must be there in normal boot too Mar 12 19:32:18 was it encrypted before or such? Mar 12 19:34:24 in twrp there is a data folder Mar 12 19:38:05 ```readlink -f /dev/block/bootdevice/by-name/userdata … /dev/block/mmcblk0p54 … ``` … i converted to … ``` -e 's block/bootdevice/by-name/userdata mmcblk0p54 '\``` Mar 12 19:38:44 but it says also … ```df -h /data … Filesystem Size Used Available Use% Mounted on … /dev/block/dm-0 23.9G 4.5G 19.1G 19% /data``` Mar 12 19:39:07 hmmm Mar 12 19:39:17 Maybe it's encrypted Mar 12 19:39:31 yeah but then you could not install Halium Mar 12 19:39:43 and recovery wont show or show the same error Mar 12 19:40:33 in fstab it has `encryptable=/dev/block/bootdevice/by-name/metadata` Mar 12 19:41:52 But only at userdata Mar 12 19:42:30 Can i create a partition table with no problem? Mar 12 19:51:31 here is dmesg log for twrp while mounting https://pastebin.com/yHvzKzcc Mar 12 19:52:36 @nanu_c, I would not bet on this. Android is not like a PC, everything can go wrong there ^^ The bootloaders have their own mind. Is this from a Lineage port? Mar 12 19:53:27 there is a port for andoid 8 and 9 but it was deliverd with 7 and that port wasn't finished Mar 12 19:55:10 it's funny. the data is fully encrypted and the key is in `/dev/block/mmcblk0p35` Mar 12 19:55:27 but if i try to munt it i get permission denied Mar 12 20:14:29 why the docs say i have to use ext4 and not f2fs? Mar 12 20:19:27 @nanu_c, does it work with f2fs? I assume not Mar 12 20:19:53 @nanu_c, Then just reformat it with ext4 probably Mar 12 20:56:43 velitasali was added by: velitasali Mar 12 21:55:17 I got sony honami (z1) to boot, expect some PRs later this week Mar 12 21:55:51 Also why and how could rootfs refuse to mount with reference but work fine with PlaMo? Perhaps I have a corrupted file or smth Mar 12 23:15:07 You want to unify everything,right? Mar 12 23:18:18 Ive worked with halium for 2 years and they want to teach me how it works :/ Mar 12 23:45:27 steevie, Halium hasn't quite existed for two years. ;) Mar 12 23:45:32 But what's up? Mar 12 23:49:19 Almost two years!!!! Mar 12 23:49:36 April 2017 **** ENDING LOGGING AT Wed Mar 13 02:59:57 2019