**** BEGIN LOGGING AT Fri Oct 18 02:59:58 2019 Oct 18 04:44:46 @ankaos [akatsu. my device not open ubports], what do you mean Oct 18 11:10:16 @NotKit what is better as base android 5 or android 7 Oct 18 11:41:38 @Luka [what do you mean], Because akatsu help me Oct 18 11:42:36 @ankaos [Because akatsu help me], i asked what do you mean by my device not open ubports Oct 18 11:42:36 Hey @JBBgameich … Kde backports repo on launchpad holds a kwin wayland version 5.16 for i386 - which fails to install because of missing dep for Qt 5.12. Oct 18 11:42:40 What are the patches for kernel 3.10 support and do you think I could just reapply those changes and rebuild the package. Or are there new „regressions“ regarding the new Qt version? Oct 18 11:42:55 @Luka [i asked what do you mean by my device not open ubports], I send paste link. Oct 18 11:43:09 @Luka [i asked what do you mean by my device not open ubports], But not answer me Oct 18 11:43:23 Maybe ı delete link 😔 Oct 18 11:43:51 Fwd from ankaos: https://paste.ubuntu.com/p/9jKqc2pjzf/ Oct 18 11:43:55 This link Oct 18 11:48:30 @ankaos [https://paste.ubuntu.com/p/9jKqc2pjzf/], cat: can't open '/android-system/boot/android-ramdisk.img': No such file or directory Oct 18 11:48:35 is it halium8? Oct 18 11:48:49 @Luka [is it halium8?], Yes Oct 18 11:49:11 @Luka [cat: can't open '/android-system/boot/android-ramdisk.img': No such file or dire …], Recovery-ramdisk.img have Oct 18 11:50:01 what ramdisk do you have in out folder (of build tree) Oct 18 11:58:00 @Luka [what ramdisk do you have in out folder (of build tree)], I look out folder. But not have Oct 18 11:58:21 no ramdisks at all? Oct 18 12:18:22 @ankaos [I look out folder. But not have], `find out/ -iname *ramdisk*` should yield something if nothing else Oct 18 14:08:37 @Deathmist1337 [find out/ -iname *ramdisk* should yield something if nothing else], anka@anka:~/lg_hal-8.1$ find out/ -iname *ramdisk* … out/target/product/d802/ramdisk-recovery.cpio … out/target/product/d802/ramdisk.img … out/target/product/d802/ramdisk-recovery.img Oct 18 14:10:40 @Deathmist1337 [find out/ -iname *ramdisk* should yield something if nothing else], ` BUILT_RAMDISK_TARGET := $(PRODUCT_OUT)/ramdisk.img ` maybe ramdisk.img new name android-ramdisk.img Oct 18 14:31:46 it is same Oct 18 14:32:06 rename ramdisk to android-ramdisk and put it to its place Oct 18 14:33:01 @Luka [rename ramdisk to android-ramdisk and put it to its place], now rebuild Oct 18 14:59:48 Hi where can i see devices list Oct 18 15:25:16 @Emanuel Tankovic [Hi where can i see devices list], https://github.com/Halium/projectmanagement/issues Oct 18 15:29:47 (Document) https://irc.ubports.com/a1EPgfnJ.png Oct 18 17:06:45 @Luka [rename ramdisk to android-ramdisk and put it to its place], https://paste.ubuntu.com/p/WwrBnq7NJz/ new dmesg output Oct 18 17:08:59 not there Oct 18 17:10:02 but ı have Oct 18 17:10:14 out/android-ramdisk.img have Oct 18 17:11:12 it must be in system/boot/android-ramdisk.img Oct 18 17:11:30 not ı have boot folder Oct 18 17:11:44 [Edit] ı have not boot folder Oct 18 17:12:34 create one Oct 18 17:12:40 inout/system Oct 18 17:12:48 in out/system* Oct 18 17:24:46 @Luka [in out/system*], out/system ı have Oct 18 17:26:22 create out/system/boot Oct 18 17:36:15 Okey Oct 18 17:36:44 @Luka [create out/system/boot], Than mv Android-ramdisk.img Oct 18 17:45:36 yep Oct 18 17:54:54 But it still fails. Oct 18 17:58:37 I think I found the problem. **** ENDING LOGGING AT Sat Oct 19 02:59:57 2019