**** BEGIN LOGGING AT Sat May 11 02:59:57 2019 May 11 07:33:43 is the xenial hyrbis rootfs is for use with hybris-boot? May 11 07:40:14 @austenite [is the xenial hyrbis rootfs is for use with hybris-boot?], you mean the ubports one? both hybris- and halium-boot May 11 07:41:10 @fredldotme [you mean the ubports one? both hybris- and halium-boot], with halium-boot, it gets stuck on splash, with hybris-boot , device goes into boot loop, mine is a 64bit device, should i use 64bit hybris rootfs? May 11 07:42:24 with hybris-boot you might have gotten somewhere, have you tried opening a telnet connection? May 11 07:42:44 @fredldotme yes, ran some tests too, all are failing May 11 07:43:03 @fredldotme meanwhile plasma mobile works with 64bit rootfs and hybris-boot May 11 07:44:01 so far with halium-boot i can see the display is working and ubuntu loading screen shows up May 11 07:45:42 does dmesg note any crashes? May 11 07:45:44 and dmesg is spammed wih this https://del.dog/garlic-ubports1.css May 11 07:48:17 uh oh, dash crashing is not good. the ubports porting group might be more helpful in that case. May 11 07:48:47 you could theoretically try the edge rootfs as it doesn't ship the dash May 11 07:49:27 ok, downloading the xenial-hybris-edge-rootfs-arm64? what is the mainline one? May 11 07:49:45 I'd suggest staying at armhf, the arm64 is discouraged atm May 11 07:50:14 @austenite [ok, downloading the xenial-hybris-edge-rootfs-arm64? what is the mainline one?], mainline ships mesa drivers instead of libhybris-based wrappers May 11 09:38:56 Hey guys May 11 09:39:30 Anyone want to work on halium 15.1 with @ankaos or 16.0 with me? I know I keep asking but yeah... I'm still asking May 11 09:39:53 I'm gonna start working on both since 90% of the work is basically the same for both May 11 09:46:58 I think he needs help with 15.1 too, I dunno if he's capable of pulling off the task alone, very few people are able to do something like this... I mean look at 7.1.... zero stable devices with proper kernels that can run stable software as stable software May 11 09:48:57 I have 97 known bugs in herolte and it's a device with a manifest in halium-devices repo, and 97 are KNOWN... there's probably 1000+ that are unknown May 11 09:49:56 I'm gonna use my J3 2018, but the only kernel is from samsung opensource center and is not ready to roll like a lineageos kernel May 11 09:50:08 *shrug* May 11 10:08:12 @powderedtoastman9000 [Anyone want to work on halium 15.1 with @ankaos or 16.0 with me? I know I keep a …], If u can tell me, how I can help? May 11 10:09:44 @Venji10 [If u can tell me, how I can help?], Well, basically you need to figure out all the hardware changes in 9.0 and backport the supporting code into hybris/libhybris/libnativehelper May 11 10:10:48 I mean... to me it seems simple and logical, I don't know how to explain it other than keep trying obvious ideas until one works, but having an 8.0/8.1 or 9.0 device is a requirement... for halium 16.0 I am using S8 and S9 as my development devices May 11 10:11:03 and for 15.1 I am going to use J3 2018 international version May 11 10:11:13 Is Halium 16 available on github, that I can download your source? May 11 10:11:44 not really... I mean I forked all the repos I've made major changes to, but those "major changes" are actually pretty small, github.com/zerorax May 11 10:12:11 All my public repos except 2 are halium/ut repos May 11 10:13:28 I mean, if you don't already know how to do it... explaining is basically you trying to do it and asking me what to do next every time you get stuck... I'm just removing everything from Lineage that isn't needed, fixing bugs in kernels, fixing device trees, I still need to update the android_hardware repo which is LOS 15.1 ba May 11 10:13:28 sed since there is no public 16.0 fork in LOS May 11 10:13:56 and defintely you want to use the hybris 9.0 patch repo that I have... someone linked me a download link to the patches, I didn't make them May 11 10:17:32 Were you able to build a working version of Halium 16? May 11 10:19:15 Nope... I have halium-boot booting, but only adbd with busybox booting and nothing useful in the running kernel, not even a USB connection May 11 10:19:32 I'm not done the initial work to make it at a point where I can debug or use it May 11 10:20:04 I only spent 3 days working on it, then I was sick for two days, before 5 days ago 16.0 didn't exist May 11 10:52:18 I have j3 prime 2018... maybe I can help you with 15.1 May 11 10:52:59 If that is the development device I have it already May 11 11:25:40 Hello, do you have experience with the hardware adaption for Mediatek chipsets? I know estimations of about 10 man month for devices with Qualcomm chipsets, bot not for devices with Mediatek. Our potential device uses a Mediatek MTK Hello P23 (MT6763) Octa-Core 2.0 GHz chipset. May 11 11:29:24 Does anybody know, how the first versions of Halium were developed? Are they based on the CM/LOS Repo? May 11 21:46:32 Any news about 8.1 or 9.0 compatibility? May 11 22:10:19 @Nebrassy [Any news about 8.1 or 9.0 compatibility?], No May 11 22:11:07 I sleep May 11 22:11:17 Some people are working on it but not much results until now May 11 22:11:38 Then turn off your phone ;) **** ENDING LOGGING AT Sun May 12 03:00:31 2019