**** BEGIN LOGGING AT Thu Feb 08 03:00:02 2018 Feb 08 03:25:30 There's something weird with the 5X. I don't know if it's an interaction with halium-boot. The /vendor partition is mounted correctly in /android, but inside the container rootfs sits a link to /system/vendor Feb 08 03:26:02 Anyone know what would set that symlink up? I deleted the scripts provided by lxc-android already. Feb 08 05:10:58 @UniversalSuperBox, No one even have one of these... Happy for that one person who'll use it Feb 08 05:11:01 😂 Feb 08 05:32:44 @UniversalSuperBox, Is it unity desktop? Feb 08 05:52:18 @UniversalSuperBox, nice. can you get a shell also? I tried to get a shell in the past but it was just erroring out ... I suspected I was missing a kernel config Feb 08 06:06:48 @maharudra108, Budgie... And how the heck can you speculate DE from terminal? Feb 08 06:09:39 @NSA_AMERICA, ? Feb 08 06:30:54 OT Feb 08 06:33:19 Hi, is it possible to use halium-7.1 for Nexus5 (lge_hammerhead)? Feb 08 06:33:34 I m trying to compile aosp nd always getting dex2oat error Feb 08 06:35:05 @maharudra108, with halium-7.1 for nexus5 ? Feb 08 06:35:32 @itviewer, No bro pure aosp Feb 08 06:36:10 ok,thanks Feb 08 06:37:18 https://hastebin.com/vasoxageje.lua Feb 08 06:37:38 @itviewer, Yup bro Feb 08 06:38:05 If halium is already available for nexus5 Feb 08 06:57:10 @stefanomelchior, Yes I did Feb 08 07:54:39 @itviewer, Currently the Nexus 5 port uses halium-5.1, but updating it to 7.1 should be easier than porting a new device Feb 08 08:40:53 There are some source files missing what should I do? Feb 08 08:41:41 Running kati to generate build-lineage_jfltexx.ninja... … /root/halium/out/build-lineage_jfltexx.ninja is missing, regenerating... Feb 08 08:42:04 And Feb 08 08:42:07 device/samsung/qcom-common/doze/Android.mk:37: frameworks/base/packages/SettingsLib/common.mk: No such file or directory Feb 08 08:42:36 @Manu, you should remove all .apk mentions from your tree Feb 08 08:42:55 remove = comment out in make files Feb 08 08:43:09 How to do that? Feb 08 08:43:26 tell me please, how many free HDD GBs is required in order to build Hallium? Feb 08 08:43:41 @Progromizd, ~9 Feb 08 08:43:50 depends, but usually around that Feb 08 08:44:32 @Manu, https://github.com/Halium/android_device_htc_pme/commit/15d000575d043274b63da2d095b4a0ba10864ea3 Feb 08 08:44:38 refer to this commit Feb 08 08:44:51 go over /vendor and /device trees and look for .apk mentions in makefiles Feb 08 08:44:54 @Manu, there should be a vendor/bq//Android.mk Feb 08 08:45:45 look at my example https://github.com/Halium/projectmanagement/files/1696847/Android.mk.txt Feb 08 08:50:00 @vanyasem, why shouldn't those lines commented for all the devices, I mean in the main stream? Feb 08 08:50:33 .apks shouldn't be useful for halium purpose, shouldn't they? Feb 08 08:50:43 @stefanomelchior, forking /vendor tree might be considered illegal, that's why we don't do so. automatic excluding of apk files was proposed, but never got implemented Feb 08 08:51:05 that's less of an issue with halium and more of an issue of the muppets vendor tree and how android build system is designed Feb 08 08:53:49 @vanyasem, I don't understand why we don't just bring back the scripts that just adb pull things from a running AOSP build Feb 08 08:54:17 no idea either, ask bhushan :P Feb 08 08:54:42 We don't want to include java stuff and apks in the halium build Feb 08 08:55:12 oh wait you mean instead of using themuppets? Feb 08 08:55:28 yeah, way back when CM used to have a script that would just adb pull required blobs Feb 08 08:55:36 I don't think it has that anymore Feb 08 08:55:57 @vanyasem, neither create a script to "disable" while compiling? is it illegal too? Feb 08 08:56:10 @vanyasem, i wrote about that already Feb 08 08:56:32 it's not illegal, it's just that nobody has ever done that. PRs welcome Feb 08 08:57:01 @vanyasem, ok, got it Feb 08 08:57:53 Useful for arm64 device https://github.com/libhybris/libhybris/commit/21b90acbc580a1aab07adf1ed5a67db411259883 Feb 08 08:58:43 I realized my /system is 100% full and (I suppose for that reason) it is read-only. Is it possible to resize to have room to work? I can't read logs, neither work on test_* Feb 08 08:59:43 from mka systemimage, can I? Feb 08 09:00:54 it's supposed to be 100% full and read-only Feb 08 09:01:27 you can use resize2fs to resize it, in theory, and remount, but this is not related to your problems Feb 08 09:08:00 maybe I am wrong, but since it became full, I can exec a command like: echo 1 > /dev/wcnss_wlan to activate wifi Feb 08 10:01:47 root@localhost:~# EGL_PLATFORM=hwcomposer test_hwcomposer … library "libtinyxml.so" not found … width: 1080 height: 1920 … ?? Feb 08 10:30:14 @win8linux, can I be sure, that using this cmd with depth ==1, all necessary files will be downloaded? … (I mean, nothing will be lost for successful build.) Feb 08 11:48:05 I've been able to build Halium after the necessary modifications for my device, so yes. Feb 08 11:49:02 Do I need to flash the recovery image or can I just keep the one I had before? Feb 08 11:49:49 no.. just keep TWRP Feb 08 11:50:22 Great! :D Feb 08 12:29:50 @dohniks, Yes, by putting in /system/bin/sh Feb 08 14:34:11 Can someone merge PR#69 on docs, it's done Feb 08 14:37:38 @NSA_AMERICA, delete the old page that's incorrectly named Feb 08 14:37:49 why would you have 2 paged for the same device? Feb 08 14:37:57 I commented that on the issue Feb 08 14:40:56 @vanyasem, Already done, Feb 08 14:41:26 @vanyasem, Read the first message on PR#69 .. it was there whole time :) Feb 08 15:47:20 @maharudra108, That looks nothing like unity. Feb 08 15:49:43 @maharudra108, Budgie on Solus Feb 08 16:01:08 how much Budgie is touch optimized compared to GNOME Shell, btw? Feb 08 16:09:53 @vanyasem, Looks pretty shell Feb 08 17:30:08 @NotKit, Budgie is almost gnome and,,,, kde gnome and deepin and are very well optimized for touch Feb 08 19:02:29 Ho guys, someone has tried to port halium to a device with 3.4 kernel? Feb 08 19:02:58 Yeah, the Nexus 5 and Xperia Z port both use linux 3.4 Feb 08 19:04:00 @JBBgameich, Have you got some problems with lxc? Feb 08 19:06:32 Both kernels had to be patched Feb 08 19:06:54 https://github.com/Halium/android_kernel_sony_apq8064 Feb 08 19:08:44 @JBBgameich, From which commit? Feb 08 19:09:36 https://github.com/LineageOS/android_kernel_sony_apq8064/commit/b3bbbf6ce0bd76076e4e02bc7a2de90ea523535e … https://github.com/LineageOS/android_kernel_sony_apq8064/commit/7c9f141d37b833a99f2bf27f9793cd061c55c2e6 … https://github.com/LineageOS/android_kernel_sony_apq8064/commit/9e920c6371fb5aefd35b45cbb58d5c307db6ebda Feb 08 19:10:44 @JBBgameich, Thanks a lot! I Will try Feb 08 22:00:02 @NotKit, It's pretty good. The only problem is the lack of an iconified app list. Feb 08 22:07:46 (Photo, 681x800) https://irc.ubports.com/OVVAOewr/file_4132.jpg Feb 09 01:57:34 I'm working on bringing halium to the zte axon7. It has LineageOS 14.1 support. I get as far as 'mka mkbootimg' https://docs.halium.org/en/latest/porting/build-sources.html#building-the-system-img-and-hybris-boot-img but it cannot find SettingsLib. https://gist.github.com/rockybulwinkle/a875009fe2bfbc95d7d734d5ff0eede0 Feb 09 01:59:43 Initially I brought in the frameworks base from lineageos, which does have settingslib, but this doesn't seem like the right thing to do. Feb 09 02:10:41 Pablo Alejandro Mancera Salgado was added by: Pablo Alejandro Mancera Salgado Feb 09 02:18:23 Hi, I'm trying to port Halium to the LeEco Le Pro 3, however, I don't have experience porting, do you guys think I should even do the pull request of my manifest before getting a usable port? Is my first time porting anything and using GitHub for contribute to a project Feb 09 02:20:13 And sorry if I can't make myself understood, english is not my native language Feb 09 02:46:17 FiestyBurrito was added by: FiestyBurrito Feb 09 02:47:04 Hi, sorry if this is an stupid question, but executing "breakfast zl1" (I'm trying to port Halium to LeEco Le Pro 3) gives me this error: "** Don't have a product spec for: 'lineage_zl1' ** Do you have the right repo manifest?", I think I have configuted a right repo manifest, what should I do? **** ENDING LOGGING AT Fri Feb 09 03:00:01 2018