**** BEGIN LOGGING AT Fri Nov 08 02:59:57 2019 Nov 08 07:07:28 How likely am I to get something working that works on LineageOS, but people appearantly failed on before and my skills as a developer is basic technical googling? Nov 08 07:07:43 * How likely am I to get something working that works on LineageOS 16(17?), but people appearantly failed on before and my skills as a developer is basic technical googling? Nov 08 07:08:05 * How likely am I to get something working that works on LineageOS 16(17?), but people appearantly failed on before and my skills as a developer is limited to basic technical googling? Nov 08 07:09:35 jfltexx Nov 08 07:17:52 does it have LineageOS 14? Nov 08 07:17:59 no 15/16/17 support Nov 08 07:28:27 https://www.los-legacy.de/jfltexx this here appearantly also gets updates? Nov 08 07:28:28 I don't know. I'm pretty sure it did have official lineageOS 14 but I don't know where to get such old images Nov 08 07:29:10 you don't need to get that image, but need source device tree Nov 08 07:34:51 I can find 14.1 but cyanogenmod on lineageos github. Nov 08 07:34:51 The los-legacy 14.1 image seems to be made using https://github.com/lineageos-infra/updater Nov 08 07:35:07 * I can find 14.1 but it's actually cyanogenmod on github. Nov 08 07:35:08 The los-legacy 14.1 image seems to be made using https://github.com/lineageos-infra/updater Nov 08 07:36:21 I'm not sure about the kernel version Nov 08 07:37:16 * I can find 14.1 but it's actually cyanogenmod on github. Nov 08 07:37:16 The los-legacy 14.1 src seems to be made using https://github.com/lineageos-infra/updater Nov 08 07:37:39 * I'm not sure about the kernel version. 3.4 seems to be what samsung is shipping. Nov 08 07:38:32 cm-14.1 branch is fine Nov 08 09:07:19 So what are the chances I can get something like UBPorts working with halium on a usable level? again, I barely worked with android kernel or src Nov 08 09:09:01 does 14.1 support mean that most device functions will work fine out of the box? Nov 08 09:10:04 the 3.4 kernel seems to be sort of an issue, but somebody got plasma mobile working and it seems to be at least somewhat supported considering some things in the docs Nov 08 09:11:58 * does 14.1 support mean that most device functions will work fine out of the box? I definetly can't code drivers Nov 08 09:12:20 * does 14.1 support mean that most device functions will work fine out of the box? I definetly can't code/debug drivers Nov 08 09:14:25 Knowledge Graph Tutorial: How to Build a Knowledge Graph – IBM Developer … https://developer.ibm.com/patterns/build-a-domain-specific-knowledge-graph-from-given-set-of-documents/ Nov 08 09:18:25 things are very seldom to work fine out of the box Nov 08 09:19:18 if you're willing to search and investigate, it's often not rocket science, but will require some effort Nov 08 09:20:48 Basic knowledge of how a kernel is built for Linux also helps a lot Nov 08 09:21:45 @fajjida[m] [the 3.4 kernel seems to be sort of an issue, but somebody got plasma mobile work …], Hey, that brought a question from me! I have a 3.4 kernel too, could it affect LXC container from running? Nov 08 09:27:05 3.4 can work, just LXC and systemd will require a few patches to the kernel. Nothing too fancy though. Nov 08 09:27:33 We have a number of devices for LuneOS using Halium with 3.4 kernel (Mako, Hammerhead, Tenderloin for example) Nov 08 09:27:54 I tried to compile a custom kernel twice but failed? Nov 08 09:28:04 * I tried to compile a custom kernel on desktop twice but failed? Nov 08 09:33:54 things are very seldom "> yes, but would the issues be likely be more like config values or memory debugging? Nov 08 09:35:00 @Herrie|2 [3.4 can work, just LXC and systemd will require a few patches to the kernel. Not …], Hm, interesting. Could you send me or send me later some of those patches to try? Nov 08 09:37:00 would it be better to try using https://github.com/lineageos-infra/updater to get lineageos 14.1 (los-legacy builds?) or the cyanogenmod 14 branch? Nov 08 09:54:43 * would it be better to try using https://github.com/lineageos-infra/updater to get lineageos 14.1 (los-legacy?) or the cyanogenmod 14 branch? Nov 08 10:02:00 what if I use halium 5.1? Nov 08 11:33:19 @rixchy: See https://github.com/Halium/android_kernel_lge_hammerhead/commits/halium-5.1 (you can mostly ignore the GCC ones, these are for LuneOS because we use newer GCC and not Google's outdated 4.8/4.9) Nov 08 11:33:57 Okay. I have chagalllte, but I will check it out anyways. Nov 08 11:42:32 How do I know whether I need to adjust the config if mer-kernel-check complains? Nov 08 11:44:47 fajjida[m]: In general you should, that's why the check is there ;) Nov 08 11:46:39 Hm, suddenly I forgot.. where was the location of defconfigs? Nov 08 11:48:49 @rixchy: It's in your kernel repo: For example: https://github.com/Halium/android_kernel_lge_hammerhead/commit/533a628f03d4d0be2f1c4e969aa1c6d7a7e564bb Nov 08 11:49:13 @Herrie|2 [@rixchy: It's in your kernel repo: For example: https://github.com/Halium/androi …], Okay, thanks. the Nov 08 11:49:17 @Herrie|2 [@rixchy: It's in your kernel repo: For example: https://github.com/Halium/androi …], [Edit] Okay, thanks. Nov 08 12:01:56 Hey, so I ran mer-kernel-check, because I am recreating my device's port.. and I started wondering, what does value "m" mean in defconfig? Nov 08 12:06:17 m means that the feature is built as a module, not into the kernel image as far as I know Nov 08 12:06:45 Alright, could you explain it a little bit deeper? Nov 08 12:09:42 The system image has a directory containing .ko files, those are the kernel modules. They can be loaded and unloaded at runtime. In some cases you can build features as modules to make the kernel image contained in the boot image smaller. Nov 08 12:10:05 Okay, I understand it now. Thanks. :) Nov 08 12:17:21 I understand, that you need (recommended) to fix the errors that mer-kernel-check suggests. But, I am not sure about this one. Nov 08 12:17:28 "WARNING: CONFIG_UEVENT_HELPER_PATH is invalid … Value is: "/sbin/hotplug" … Allowed values : "", ! … Comment says: should be empty, if you want to use systemd without initramfs. Also systemd: http://cgit.freedesktop.org/systemd/systemd/commit/README?id=713bc0cfa477ca1df8769041cb3dbc83c10eace2 … " Nov 08 12:17:43 [Edit] "WARNING: CONFIG_UEVENT_HELPER_PATH is invalid … Value is: "/sbin/hotplug" … Allowed values : "", ! … Comment says: should be empty, if you want to use systemd without initramfs. … " Nov 08 12:24:15 @rixchy: hotplug is an old tool for managing uevents. if your system uses systemd, it won't use hotplug, most probably. Nov 08 12:24:39 So, what should I input in ther? Nov 08 12:24:46 [Edit] So, what should I input in there? Nov 08 12:24:54 The "", or "!"? Nov 08 12:25:20 "" Nov 08 12:25:28 Okay, thanks. :) Nov 08 12:30:46 20+ complaints about unset values, I set most of them to y. Nov 08 12:32:00 fajjida[m]: That number sounds about right.... Nov 08 12:33:25 Hm, suddenly I forgot.."> in my case, the directory for kernel config was in kernel/samsung/jf/arch/arm/configs/lineageos_jf_defconfig and I had to look through multiple files to find it, the docs advice didn't work because of an abstraction with include BKcommon from jf-common and stuff Nov 08 12:34:28 > <@freenode_ubptgbot:matrix.org> Hm, suddenly I forgot.. where was the location of defconfigs? Nov 08 12:34:29 * in my case, the directory for kernel config was in kernel/samsung/jf/arch/arm/configs/lineageos_jf_defconfig and I had to look through multiple files to find it, the docs advice using grep didn't work because of an abstraction with include BoardConfigCommon.mk from jf-common and stuff Nov 08 12:34:36 how do I apply the kernel patch needed for 3.4? Nov 08 12:42:05 the four letter addition https://github.com/ubports/android_kernel_google_msm/pull/5/commits/1ad88b041787d8ce8407a021271ef1031e95cba6 Nov 08 12:48:57 fajjida[m]: download https://github.com/ubports/android_kernel_google_msm/pull/5/commits/1ad88b041787d8ce8407a021271ef1031e95cba6.patch , apply it with "git am mypatch.patch" Nov 08 12:49:17 or do the change by hand Nov 08 13:07:21 @rixchy [Alright, could you explain it a little bit deeper?], Basically most Android kernels do not use modules, as the device´s kernel is not used on variants of hardware. On the desktop it makes perfect sense to not compile all network card drivers into the kernel to not bloat it. Instead ,load kernel modules on demand depending on lspc Nov 08 13:07:21 i etec Nov 08 13:07:35 But I have seen WiFi modules on our ports sometimes Nov 08 13:08:12 My recent port had modules turned off, some tools might throw errors then. Its safe to set CONFIG_MODULES=y but not more to enable an empty module ecosystem that makes userland happy ^^ Nov 08 13:08:42 Also, not all drivers that can be modules should be ones. Some might not work if not loaded with the kernel on boot Nov 08 13:16:43 @Flohack: and vice-versa, wifi module is a good example here: if firmware is in rootfs and not in initrd, initializing it too soon will just create problems Nov 08 13:24:09 @Tofe [@Flohack: and vice-versa, wifi module is a good example here: if firmware is in …], I agree. Nov 08 13:27:04 have anyone pb with selinux, phone boot only when i delete all selinux config from kernel, or set selinux as default Nov 08 14:35:50 Hm, "device/samsung/exynos5420-common/SamsungDoze/Android.mk:37: frameworks/base/packages/SettingsLib/common.mk: No such file or directory" Any idea where could I find that file? Nov 08 14:41:28 SettingsLib should not be needed and can be commented out. Nov 08 14:41:37 Alright, thank you. Nov 08 14:49:45 Hm, one more question. Should I be worried about this "build/core/base_rules.mk:316: warning: ignoring old commands for target `/home/rixchy/halium/out/target/product/chagalllte/system/lib/libexynoscamera.so' … "? I mean, the build itself completed successfully. Nov 08 14:51:43 Uhm, hm. "ninja: no work to do." Nov 08 15:04:10 @rixchy [Hm, one more question. Should I be worried about this "build/core/base_rules.mk: …], Probably there are two build rules for the same file. This is unfortunately quite common in the android world, so I guess its fine. Though you'd have to check this particular case to be sure. Nov 08 15:04:33 @rixchy [Uhm, hm. "ninja: no work to do."], Ok, but what about this one? Nov 08 16:35:43 Hi. I'm trying to build for asus Z00A. I'm getting out/host/linux-x86/bin/dx missing and no known rule to make it. Nov 08 16:37:29 during mka systemimage Nov 08 16:37:57 [69288.872075] 69288.872075 / 11-08 15:35:50.205] type=1400 audit(1573227350.205:39): apparmor="STATUS" operation="profile_load" name="/usr/lib/telepathy/telepathy-ofono" pid=18077 comm="apparmor_parser" Nov 08 16:38:02 not problem? Nov 08 16:47:51 Fernando BCF was added by: Fernando BCF Nov 08 19:57:21 Thinhx2 was added by: Thinhx2 **** BEGIN LOGGING AT Fri Nov 08 21:47:38 2019 Nov 09 00:49:08 Dunkle miles was added by: Dunkle miles Nov 09 00:49:38 KAREN HORN was added by: KAREN HORN **** ENDING LOGGING AT Sat Nov 09 02:59:57 2019