**** BEGIN LOGGING AT Wed Jul 17 02:59:57 2019 Jul 17 06:21:32 Can we maybe create a new branch halium-9.1 to start testing on lineage-16.1? https://github.com/Halium/android/blob/halium-7.1/default.xml Jul 17 06:21:37 what do you think? Jul 17 07:11:38 just creating a branch won't help much unless you understand how it was setup originally and willing to do same for los16 Jul 17 07:13:54 yeah, but we can start working on it, for now i'm going to try it locally Jul 17 07:14:34 which is your device? Jul 17 07:14:58 i have several, but i'm foing to test with oneplus 3 Jul 17 07:15:05 i know a can use 7.1 Jul 17 07:15:52 it would be best 5.1 and have working ofono, but if 7.1 is stacked on that point maybe we have to follow Jul 17 07:16:23 did oneplus 3 have 5.1 at all? Jul 17 07:16:24 and i don't see any changes since a lot of time on repos, except for mer projects Jul 17 07:16:47 no, minimum are cm-13.1 Jul 17 07:17:08 ofono is a distribution-side issue, generally not Halium one Jul 17 07:18:06 you can use those ported patches as reference for 9.0, but it doesn't have anything to minimize the build Jul 17 07:18:06 (Document) https://irc.ubports.com/iDG4a0cu.zip Jul 17 07:21:21 personally I would prefer target that is supported by Sailfish with 8/9 base so we can check what works for then and fix issues on rootfs side Jul 17 07:28:15 yeah i would be nice to Jul 17 07:28:22 are yours all that patches? Jul 17 07:34:22 @NotKit [personally I would prefer target that is supported by Sailfish with 8/9 base so …], targets like xperia xa2 or..? :) Jul 17 07:35:33 @hadrianweb [are yours all that patches?], they are ported from mer-hybris tree Jul 17 11:41:10 @minlexx [targets like xperia xa2 or..? :)], maybe something in-progress from porters channel, but I don't know personally Jul 17 14:54:04 (Photo, 1280x719) https://irc.ubports.com/z2M0Cvrp.png ı build ut. but this true or false? Jul 17 14:54:26 selinux disable? Jul 17 15:00:14 selinux should have replaced by apparmor Jul 17 15:01:27 ` CONFIG_DEFAULT_SECURITY="apparmor" ` not problem. Jul 17 15:01:29 @stefanomelchior [selinux should have replaced by apparmor], sorry, selinux should have BEEN replaced by apparmor Jul 17 15:01:55 been? Jul 17 15:03:10 `cmdlın:= selinux=0 ` false? Jul 17 15:03:22 [Edit] `cmdlıne:= selinux=0 ` false? Jul 17 15:03:58 @ankaos [], for ubports Jul 17 15:04:08 @ankaos [], Androidboot.selinux=0 Jul 17 15:04:17 It will set as permissive Jul 17 15:04:30 And =1 set as permissive Jul 17 15:06:06 @kumarayush2104 [It will set as permissive], https://paste.ubuntu.com/p/W7qkGX9MZM/ Jul 17 15:06:12 true or false? Jul 17 15:06:48 @ankaos [true or false?], 0 Jul 17 15:07:19 @kumarayush2104 [0], Is my editing correct? Jul 17 15:07:30 I told it wrong. Jul 17 15:10:18 Can you fix it if it's wrong? Jul 17 15:40:15 Is there any way to resize recovery partition? Jul 17 16:04:50 @everyhomeiswired [Is there any way to resize recovery partition?], Potentially yes, but potentially you gonna brick your device Jul 17 16:34:04 The halium-install script is pushing the rootfs tarball to recovery instead of data and then running out of space Jul 17 17:21:31 @nanu_c [Potentially yes, but potentially you gonna brick your device], https://paste.ubuntu.com/p/XK8HM8QdtV/ Jul 17 17:23:58 Safe to reduce userdata size, move the partitions down and then increase the size of recovery by the same amount that i reduce userdata Jul 17 17:25:57 Then you have to fix that recovery mounts userdata to /data because the halium-boot looks on userdata for the files to boot Jul 17 17:27:51 Which halium-install script are you using, and did you already try the alternative one? Jul 17 17:28:19 https://github.com/JBBgameich/halium-install/releases/download/continuous/halium-install-standalone.sh Jul 17 17:56:58 I didn’t check the alternate script I’ll try that first Jul 17 18:39:11 Running out of space on device even with the alternate script … It’s a 16gb device Jul 17 18:41:07 @nanu_c [Then you have to fix that recovery mounts userdata to /data because the halium-b …], Can i use adb pull on the partitions before resizing and then restore them with push after it’s done? Jul 17 18:49:55 https://paste.ubuntu.com/p/PkxMnw23Kq/ … Similar outputs as far up as i scroll Jul 17 19:04:11 kernel is not seandroid enforcing` Jul 17 19:04:24 [Edit] `kernel is not seandroid enforcing` say me Jul 17 19:23:21 @everyhomeiswired [Can i use adb pull on the partitions before resizing and then restore them with …], I would check why userdata isn't mounted to /data Jul 17 20:19:56 I checked and it is mounted to /data Jul 17 20:20:40 Well /data is on partition 48 and userdata is also on 48 Jul 18 02:32:12 Hey, trying to compile system image but gettng this error Jul 18 02:32:36 make: Leaving directory '/home/liam/halium/kernel/samsung/msm8974' … ninja: build stopped: subcommand failed. … make: *** [build/core/ninja.mk:152: ninja_wrapper] Error 1 … make: Leaving directory '/home/liam/halium' … #### make failed to build some targets (16 seconds) #### Jul 18 02:39:42 Anyone know what is happening? **** ENDING LOGGING AT Thu Jul 18 02:59:56 2019