**** BEGIN LOGGING AT Mon Sep 23 02:59:57 2019 Sep 23 05:26:26 @Arch__ [?], Make modifications for lineage https://forum.xda-developers.com/showpost.php?s=1668d8ee982df9d47e36c7180a720815&p=54118852&postcount=9 Sep 23 05:33:31 @Arch__ [?], in practice, we don't know. Is that device tree for LOS-based ROM? Sep 23 11:08:53 status of halium 9 ? Sep 23 11:09:50 not started (I think Tofee had a tree for Android 8) Sep 23 11:12:00 what I personally want to try is to apply mer-hybris patches to phh-treble and bring UBPorts with it, then in theory only custom kernel is needed per device Sep 23 11:12:14 does your device in question have Android 9 native vendor? Sep 23 11:19:34 good idea Sep 23 11:20:26 treble stuff should unify hardware layer so we won;t have to deal with camera, sound and all this stuff Sep 23 11:21:01 we will stil have to deal with that since we're not Android, don't worry Sep 23 11:21:06 [Edit] we will still have to deal with that since we're not Android, don't worry Sep 23 11:21:17 give sad pepe sticker Sep 23 11:22:04 basically what it can unify is systemimage part of Halium, but all the middleware issues on rootfs level remain Sep 23 11:26:27 is there by any chance a way to define kernel cmdlines and/or properties only for the recovery images rather than for both recovery and boot? Sep 23 11:27:04 [Edit] is there by any chance a way to define kernel cmdline arguments and/or properties only for the recovery images rather than for both recovery and boot? Sep 23 11:30:59 @fredldotme [is there by any chance a way to define kernel cmdline arguments and/or propertie …], Well you can compile recovery with cmdline A, then flash then change to cmdline B and build/flash boot Sep 23 11:31:34 that's certainly not scalable in an automated environment Sep 23 11:33:29 NotKit: it's actually more Herrie who tried Halium a bit, but I don't know how far it actually went Sep 23 11:36:18 heh. sorry, I confused since he is also from LuneOS Sep 23 11:55:00 Well I got stuck at the point that I can build the minimal Halium 8.1 image, but it doesn't boot. Not really sure how to debug further, since my low level linux knowledge doesn't reach that far Sep 23 12:06:09 @NotKit [in practice, we don't know. Is that device tree for LOS-based ROM?], well there are a ton of ROMs like ASOP, ASOp-caf , LOS , and many more https://forum.xda-developers.com/oneplus-x/development Sep 23 12:06:38 if it is onyx, you have LOS, no? Sep 23 12:06:46 I just hope maybe any other rom source can solve my problem? Sep 23 12:07:37 the way Halium works it will bring more problems instead Sep 23 12:07:39 @NotKit [if it is onyx, you have LOS, no?], yes it does, even android 9.0 port of LOS works flawless Sep 23 12:08:19 @Arch__: We have Onyx running LuneOS using Halium 7.1 Sep 23 12:09:48 but i could find its source only the manifest file and issue mentioned about luneos Sep 23 12:09:55 @Herrie [Well I got stuck at the point that I can build the minimal Halium 8.1 image, but …], does it crash on LXC start? Sep 23 12:11:57 is there a way if halium is working fine, the rootfs shared in documentation doest even let me ssh into the system Sep 23 12:12:51 you can disable lxc-android container and check Sep 23 12:13:36 ssh is part of Linux system and does not depend on Android bits Sep 23 12:13:36 Fwd from Akatsu .: so how boot process looks like? … Kernel ->start linux->start LXC container->use container to talk to hardware? Sep 23 12:13:37 Fwd from fredldotme: kernel boots with halium-initramfs, which mounts your partitions and images -> pivot/chroot into the rootfs img -> lxc starts as a systemd/upstart service Sep 23 12:16:03 does it have 3.4 kernel? Sep 23 12:21:20 @NotKit [does it have 3.4 kernel?], yes Sep 23 12:21:44 are you trying UBPorts rootfs and have LuneOS kernel patches? Sep 23 12:24:35 3.4 kernel with required patches to keep systemd happy Sep 23 12:24:42 UBPorts might need some more patches though Sep 23 12:27:19 @NotKit [are you trying UBPorts rootfs and have LuneOS kernel patches?], i tried halium rootfs-> result no ssh but i can use telnet, i tried ubiports rootfs (both edge , non edge) tried all their error patches but Unity system compositor cannot start , only greeter . … Also I was searching for luneos /webos(?) git but there is nothing spec Sep 23 12:27:19 ific to my device. Should i be looking somewhere else? Sep 23 12:27:44 so you have SSH in UBPorts rootfs? Sep 23 12:29:38 yes Sep 23 12:33:06 it crashes after unity system compositor , i suspect this issue but it was already fixed/closed https://github.com/ubports/ubuntu-touch/issues/494 Sep 23 12:35:05 and this was my usc log https://pastebin.com/w4TzRikM Sep 23 12:36:12 Is there a different halium rootfs that has bare minimum (no fany OS only basic hardware drivers testing)? Sep 23 12:44:21 @Arch__ [Is there a different halium rootfs that has bare minimum (no fany OS only basic …], Halium rootfs but you need to build hybris-boot Sep 23 12:46:10 tried that already , i need a halium rootfs that is not the same one as mentioned in the halium docs Sep 23 12:54:37 for 3.4 kernels better to not use rootfs based on systemd, better use something like postmarketOS based on openrc, where it "just works" Sep 23 12:57:59 3.4 needs a few minor patches to get systemd 233 and higher to work, nothing too major really. Sep 23 12:58:25 @NotKit [does your device in question have Android 9 native vendor?], Do you make halium 8? Sep 23 12:59:51 Herrie: those "minor" did not help in my case :( each vendorkernel is unique it seems Sep 23 13:00:57 minlexx: Yeah they're not 100% foolproof, I agree Sep 23 13:01:04 @Herrie [3.4 needs a few minor patches to get systemd 233 and higher to work, nothing too …], only one was mentioned in the halium documentation, are there others? Sep 23 13:02:22 https://github.com/ubports/android_kernel_google_msm/pull/5/commits/1ad88b041787d8ce8407a021271ef1031e95cba6 Sep 23 13:03:16 which was already done , and i had no such issue Sep 23 13:03:18 Well you need various minor ones: https://github.com/shr-distribution/linux/commit/b840c1217fad4dd0db7e47aa671c5b0c848381a4, https://github.com/shr-distribution/linux/commit/c34cbea158fdce44085781a8318dcc4d3503239c, https://github.com/shr-distribution/linux/commit/f311986ee22b148876c327a9d9a29a240a62c5a5 and https://github.com/shr-distribution/linux/commit/01141a353241d545a2aaf9addaa32afe39a98562 Sep 23 13:03:30 The last one seems to vary quite a bit in the various 3.4.x revisions. Sep 23 13:08:11 @Arch__ [https://github.com/ubports/android_kernel_google_msm/pull/5/commits/1ad88b041787 …], this fix was already applied in lineage os , i think those minor pathes was also fixed but i will confirm again Sep 23 13:08:55 @Arch__: Those namespace ones are required for systemd too, though already for earlier systemd. The last commit is only for 233+ it seems Sep 23 13:22:48 will this help me get ssh https://github.com/Halium/projectmanagement/issues/96#issuecomment-434901900 Sep 23 13:35:51 @Arch__: We're a bit "lazy" on LuneOS side, since we only care about the created minimal Android rootfs, we never really cared about "Include your device in fixup-mountpoints", so you'd still need to add that for your device for Halium to work as a start Sep 23 13:44:47 Arch__ do you have SSH in UBPorts or not? Sep 23 13:45:05 because Halium reference rootfs is outdated and does not mean much now Sep 23 13:45:39 yes i have in ubiports but not in halium rootfs Sep 23 13:45:52 @NotKit [because Halium reference rootfs is outdated and does not mean much now], so its ok i think Sep 23 13:59:41 Ege was added by: Ege Sep 23 16:43:40 Nemraj Mundekar was added by: Nemraj Mundekar Sep 23 18:04:28 Hi Sep 23 18:06:06 hi Sep 23 18:06:18 I've been around the docs about the halium project and I have some questions. Sep 23 18:07:51 I really like the idea of having a linux distribution on my phone, especially for some old phone (galaxy trend, 7 years old) Sep 23 18:09:14 I checked the linux kernel version, it's 3.0.8. According to the documentation the 3.10 is required. That this means I can get this system to work on my phone ? Sep 23 18:09:59 your device is too old Sep 23 18:10:04 I haven't much experienced around phone development, is there a way to find the proper kernel corresponding to my phone architecture ? Sep 23 18:11:31 it depends on whatever original version of android your device shipped with. best for halium right now would be something that shipped with android 7. but oldest that could work would be 4.4 or 4.2 iirc, with kernel 3.4 Sep 23 18:12:04 Well ... I'm on 4.0.4. But I have another phone that's on 4.4 Sep 23 18:13:11 I will try with this one. Thank you for your answer Sep 23 18:28:45 Are there any halium ports for any of the many chromium projects for arm/arm64/armf and if so could whomever point me to the right XDA's and FAQ's please and thanks? Sep 23 18:31:33 probably not because ChromeOS/ChromiumOS are not Android Sep 23 18:33:28 @dohbee [probably not because ChromeOS/ChromiumOS are not Android], Do you even keep tabs and stay up to date with any of the chromuim projects? If you did you'd know you can use Android Apps + Linux .deb apps and Windows apps using Codeweavers/Crossover.... So I think that someone even me should start porting Chrome/Chromium t Sep 23 18:33:28 o halium for arm/arm64/armf... Sep 23 18:33:47 that has nothing to do with how the devices work Sep 23 18:34:23 and "porting chromium to halium" doesn't make sense in that context. there's no reason to run chromiumos on top of halium Sep 23 18:34:33 What branch do you think i need to choose? … https://github.com/LineageOS/android_kernel_xiaomi_msm8996/tree/cm-14.1 Sep 23 18:34:44 but thanks for your poor attempt at trying to be condescending Sep 23 18:35:24 @Mattia990 [What branch do you think i need to choose? … https://github.com/LineageOS/android …], i guess 14.1 would be the correct branch, as iirc it is the android 7 branch Sep 23 18:36:20 @dohbee [i guess 14.1 would be the correct branch, as iirc it is the android 7 branch], Yes but there are various cm-14.1 branch and i tried cm-14.1 and cm-14.1-caf and they have some various issues Sep 23 18:37:21 ok. i don't know if that device is caf or not, but if it is then you need the caf build. otherwise the standard build should do Sep 23 18:38:12 @dohbee [ok. i don't know if that device is caf or not, but if it is then you need the ca …], Ok, i'll retry with caf branch. thank you Sep 23 19:34:30 Any idea how can i find out why touchscreen isn;t working? Sep 23 19:35:02 Build based on Galaxy-MSM8916 repo Sep 23 19:43:32 probably libinput doesn't like something in kernel driver Sep 23 19:43:38 do you know which input node is it? Sep 23 19:45:16 ye Sep 23 19:45:31 its marked as sec_touchscreen Sep 23 19:45:35 or something like that Sep 23 19:47:02 what can i do if i know node number? Sep 23 19:55:19 flashed old build of halium boot with new android and i get cannot start user service Sep 23 19:56:22 old halium-boot shows inputs from my touchscreen presses Sep 23 20:15:28 X big D, there was parameter called touch_disabler at the end of defconfig, removed and touch works Sep 23 20:50:19 Lol, document this Sep 23 21:01:47 i havent found this anywhere in the internet Sep 23 21:02:53 CONFIG_TOUCH_DISABLER=y Sep 23 21:03:43 Now i have issue with Alsa on this new tree Sep 23 21:03:53 There is no devices. Sep 23 21:04:04 https://paste.ubuntu.com/p/2vMb5ht7cP/ **** ENDING LOGGING AT Tue Sep 24 02:59:59 2019