**** BEGIN LOGGING AT Sun Aug 19 03:00:01 2018 Aug 19 07:17:43 @Marc Aurel, [SoCs manufacture](https://puri.sm/contact/)SoCs manufacturers actually don't need unified HAL. They just use their own closed-source kernel sources with binary blobs and it's doing fine on Android with Google vendor lock-in. … Purism Librem 5 uses pure GNU/Linux with its own Phosh phone shell based on GTK+ (afaik Aug 19 07:17:43 there is no such thing as GNOME Mobile. Phosh is planned to be pushed upstream to become an official GNOME mobile shell). UBports, Plasma Mobile, and Replicant are planned to be supported too. But again, it's a pure GNU/Linux and you can use whatever you need. … Drivers are already implemented, however some of them still require further work. Puris Aug 19 07:17:43 m Librem development board is going to be released in September. If you want to ask them something directly, you should contact Purism at [matrix chatroom](https://matrix.to/#/!BSqRHgvCtIsGittkBG:talk.puri.sm) or at their website. Aug 19 07:43:14 Hello! … When following the docs to build bcmdhd as a module, I get this build error: https://pastebin.com/Qmz7ULTq … Has anyone solved this before? Aug 19 08:32:30 @Marc Aurel, I strongly disagree that Ubuntu Touch is in early stage. A few thousand people probbaly are using the phone as daily driver. We have a growing App ecosystem. We work hard to getting the core OS up2date and will release our 4th OTA this month. The investment by Canonical was huge, and therefore we are some man-year Aug 19 08:32:31 s ahead of other alternatives. Aug 19 08:51:52 @Artem they can do that because they have what they need. A hardware abstraction. Aug 19 08:56:10 @Flohack, Yes. UBPorts is a very mature system. But Plasma Mobile is in a very early stage. I tested the recent release on the reference device Nexus 5x yesterday and no basic phone features are supported. PostmarketOS seems in a very early stage either. So UBPorts could be indeed a got choice, but the optione to modify the Aug 19 08:56:11 UI are limited and the concept of scopes will de dropped. Look at this thread: https://forums.ubports.com/topic/834/ui-design-concepts-and-proposals/20 … The community suggested to use Unity8 Shell in combination with QtMir. My company needs to do some reseach on it. Aug 19 08:57:45 Yes we are going to drop the scopes but for good reasons: Their integration into the OS is a pain, it was quickly shoved into the desktop environment and is absolutley not easy to maintain. We are a community project, we need to keep things easy and understandable. Aug 19 08:58:34 @ar7ch, It would be perfect to drop the ballast of Android. My company would be glad, if we could contribute to this alternative. We have not the ressources to develop the core system allone. … Do you have information, that Qualcomm ships would be supported by the pure GNOME mobile? Aug 19 08:58:43 You can come up with ideas if you like what you want to customize, and maybe we can guide you in how to get this done for the OS, and eventually we can alos pick it up for the mainline. I would say that you can use core UT and then apply overlay packages to land your customizations easily Aug 19 09:02:14 @NotKit, Why hardware abstraction is not standardized? Because none of the big players has any interest that his phone is used with another OS than what he provides. Whole Android is a mess, every vendor hacks whatever he likes into the system, they never update kernels and every device has various security flaws at this level Aug 19 09:02:14 . But thats how Google allowed it to grow. … We see every day that our effort for standardization is sabotaged by chip vendors and other parties when they do again non-compliant changes to things that work elsewhere. Not even our Halium approach is easily standardizable for Android 5.1 and 7.1 otherwise mcuh more devices would have been enabled alr Aug 19 09:02:14 eady Aug 19 09:02:41 uh worng ping this was for Marc lol Aug 19 09:02:44 [Edit] uh wrong ping this was for Marc lol Aug 19 09:03:03 @Marc Aurel, No chance.. Aug 19 09:03:43 Scopes would not allow you what you wanted to do Aug 19 09:03:43 @Marc Aurel, No, GNOME mobile has the same issue than all others also: No mainline kernel drivers that are fully opensourced. Bionic instead of glibc API etc... Aug 19 09:05:07 You want to make a unity8 fork and integrate that as an alternative into ut Aug 19 09:05:15 @marc you seem to be interested in ancient history. Did you ever ask yourself why libhybris is called libhybris? Read the opening sentence at their repo: Hybris is a solution that commits hybris, by allowing us to use bionic-based HW adaptations in glibc systems Aug 19 09:05:24 [Edit] Marc you seem to be interested in ancient history. Did you ever ask yourself why libhybris is called libhybris? Read the opening sentence at their repo: Hybris is a solution that commits hybris, by allowing us to use bionic-based HW adaptations in glibc systems Aug 19 09:05:50 So whats hybris? Hubris (/ˈhjuːbrɪs/ from ancient Greek ὕβρις) describes a personality quality of extreme or foolish pride or dangerous overconfidence,[1] often in combination with (or synonymous with) arrogance.[2] Aug 19 09:06:24 Its a joke maybe but thats what it is: We are "over-confident" but know in the same time that our mission will fail from time to time ;) Aug 19 09:06:45 @Marc Aurel, There is Freedreno graphic driver, but it's not enough to get it running without other bionic drivers, I guess... So you either use Halium for libbionic driver support on Qualcomm or use open-source drivers on another SoCs. Aug 19 09:06:48 Indeed, I like the humor in the name of the project 😄 Aug 19 09:08:28 So in my opininon its very diffcult now: Even if Qualcomm would give away source code they can only give you this based on bionic. Their engineers might even no know how to compile for real Linux Aug 19 09:09:01 A common misconception is that because Android uses a Linux kernel it is Linux. Thats not true, they rolled their own OS Aug 19 09:10:27 As others said already, you can try to get kernel, device tree and vendor blobs from your ODM as if you would build a normal Android ROM, but then use it for building a Linux with libhybris and the Android container Aug 19 09:10:58 Everything else will be difficult. You see already yourself, they dont even understand your questions 😆 Aug 19 09:11:46 Bear in mind though that libhybris is not working with recent Android versions beyond 7.1 - BTW is there an ETA when it will become updated? Aug 19 09:32:48 @Flohack krnlyng branch supports it - https://github.com/krnlyng/libhybris-1/tree/android8-initial, but the issue is that Android 8 changed lots of interfaces we use, such as hwcomposer to hwcomposer2 Aug 19 09:34:02 [Edit] @Flohack krnlyng branch supports it - https://github.com/krnlyng/libhybris/commits/android8-initial, but the issue is that Android 8 changed lots of interfaces we use, such as hwcomposer to hwcomposer2 Aug 19 09:34:13 [Edit] @Flohack krnlyng's branch supports it - https://github.com/krnlyng/libhybris/commits/android8-initial, but the issue is that Android 8 changed lots of interfaces we use, such as hwcomposer to hwcomposer2 Aug 19 11:28:22 are there any android 8 hallium ports Aug 19 11:30:55 @opendata, no, there is no halium-8 yet Aug 19 11:31:07 okay Aug 19 11:31:16 hwcomposer2 is a mess, only devices released with 8 will have it Aug 19 11:31:19 IIRC Aug 19 11:31:35 mine is released with 8 :) Aug 19 11:33:30 XA2? Aug 19 11:33:32 waaat? Aug 19 11:34:14 @opendata, don't you have mainline on that? :) Aug 19 11:34:31 or it was different SoC... Aug 19 11:37:27 K31j0 yeah Aug 19 11:37:38 NotKit only really basic Aug 19 11:38:32 hybris has hwc2 supporty though Aug 19 17:19:17 efeftaes was added by: efeftaes Aug 19 17:24:09 hmm Aug 19 17:24:12 issue here - build/core/dex_preopt.mk:47: *** target pattern contains no '%'. Stop. Aug 19 17:24:20 this is after mka mkbootimg Aug 19 17:25:53 But it also appears for hybris-boot, so it's not solved by just install the abootimg package, which includes mkbootimg. Aug 19 17:26:07 The build system is Ubuntu 16,04 Aug 19 17:27:24 Is it to do with dependencies? I get a cryptic error message after lunch claiming "Trying dependencies-only mode on a non-existing device tree?" Aug 19 17:28:34 But as I understand it, one can ignore that error in some cases. Aug 19 17:38:16 @duncan^, You can skip this, this means nothing Aug 19 17:38:35 That dex-preopt error, though... Aug 19 17:38:40 What is at that line in the file? Aug 19 17:42:36 $(foreach b,$(DEXPREOPT_BOOT_JARS_MODULES),$(eval $(call _dexpreopt-boot-jar-remove-classes.dex,$(b)))) Aug 19 17:43:05 Adding a % to the pattern so you have $(foreach b,$(DEXPREOPT_BOOT_JARS_MODULES),$(eval $(call _dexpreopt-boot-jar-remove-classes.dex,%,$(b)))) appears to fix it, likewise for any other similar errors that come up Aug 19 17:43:08 but it feels wrong Aug 19 18:44:27 (Photo, 973x514) https://irc.ubports.com/wRUujwqs.png please help someone working on this device in setting up the manifests file Aug 19 18:45:15 @Levis Raju, its missing your/the github username Aug 19 18:45:41 means ? … i am a newbie following halium docs Aug 19 18:45:44 please detail Aug 19 18:45:57 show your local_manifests Aug 19 18:45:57 ^ Aug 19 18:46:06 @lyudmila_rev17, he's probably using a pre-made manifest Aug 19 18:46:15 iirc that device was ported before Aug 19 18:46:38 yes its premade Aug 19 18:46:39 (Document) https://irc.ubports.com/E0RYLeH5.xml Aug 19 18:46:50 how to get it working for me ? Aug 19 18:47:13 @Levis Raju, wait it's incorrecy Aug 19 18:47:14 @Levis Raju, [Edit] wait it's incorrect Aug 19 18:47:20 ya abishek, i was waiting for you Aug 19 18:47:30 @vanyasem, :( Aug 19 18:47:31 who the hell PRed that manifest Aug 19 18:47:34 no wonder it's broken Aug 19 18:48:00 aand that was @abhishek_01 Aug 19 18:48:05 @vanyasem, someone smart, and someone sleepy merged it Aug 19 18:48:11 yes and @JBBgameich merged it Aug 19 18:48:17 i blame you both for that :P Aug 19 18:48:18 @vanyasem, 😫 Aug 19 18:48:21 This broke it: https://github.com/Halium/halium-devices/commit/bec5cc2a599dc37a893dc31a210378f43f98a34f#diff-92424e73e0f3dfde356c3050a7f80c26 Aug 19 18:48:48 @JBBgameich, are you free now to resolve it, or do you want me to do it instead? Aug 19 18:49:52 @vanyasem, i already have the correct one, IDK what i did https://gist.github.com/abhishek9650/0a33682de9c2307dd8694ea2168cb578 Aug 19 18:50:04 what is its fix ? to revert it back to los remotes ? Aug 19 18:50:07 @abhishek_01, it's also incorrect Aug 19 18:50:15 @vanyasem, [Edit] i already have the correct one, IDK what i did with that one ..https://gist.github.com/abhishek9650/0a33682de9c2307dd8694ea2168cb578 Aug 19 18:50:21 you don't need to include revisions, you don't need common qcom repos Aug 19 18:50:25 also formatted incorrectly Aug 19 18:50:38 also haven't you forked the kernel tree? Aug 19 18:50:48 why are you using the default LOS repo? Aug 19 18:50:56 @vanyasem, i know that .. i keep it like that for a reason ... Aug 19 18:51:08 @abhishek_01, what reason? Aug 19 18:51:36 @vanyasem, Can you please do it? I'm currently busy with something else actually. Aug 19 18:51:57 @JBBgameich, sure Aug 19 18:52:30 Thanks Aug 19 18:53:28 (Photo, 971x509) https://irc.ubports.com/BsQ0m7I9.png Aug 19 18:54:48 sync sources Aug 19 18:55:06 @vanyasem, tbh i broke few things in the trees present in halium repo.. i will be fixing few things and polishing the sources as we have n linker now, like i did for https://github.com/sailfishos-wt88047 Aug 19 18:55:12 @abhishek_01, pm me plz Aug 19 18:55:19 repo sync -c -j 16 … . … this one right ? Aug 19 18:56:14 that command still gets me "fatal: duplicate path external/stlport in /home/levis/halium/.repo/manifest.xml" Aug 19 18:56:30 the manifest is invalid. Aug 19 18:56:48 @Levis Raju, https://gist.github.com/abhishek9650/0a33682de9c2307dd8694ea2168cb578 here replace it with this one Aug 19 18:57:07 please wait until we fix it, i PMed Abhishek about the issue Aug 19 18:57:36 (Y) Aug 19 19:06:54 @JBBgameich could you please take a look at https://github.com/Halium/halium-devices/pull/114 ? Aug 19 19:09:27 hal repo is just github, you need to specify `Halium/`. you made a small mistake after re-formatting it Aug 19 19:09:43 [Edit] hal repo is just github, you need to specify `Halium/`. you made a small mistake while re-formatting it Aug 19 19:10:04 wait .. ```hal``` remote is already defined ... Aug 19 19:10:06 in that Aug 19 19:10:25 @abhishek_01, it is. it's just plain `github` remote, you need the `Halium/` path Aug 19 19:10:40 @vanyasem, Looks fine, but I didn't do more than checking that the repositories actually exist in the Halium org. Aug 19 19:10:52 good, merged Aug 19 19:11:01 @vanyasem, please remember that @JBBgameich Aug 19 19:12:20 @Levis Raju, try the new manifest Aug 19 19:12:28 https://raw.githubusercontent.com/Halium/halium-devices/ac4ebc2b29fa6700bcb7827a7cd57a38533ec365/manifests/wingtech_wt88047.xml Aug 19 19:12:29 @vanyasem, I know that in general. The commit that broke it was merged by LNJ it seems Aug 19 19:22:28 There's no need to place blame in this situation, just fix the issue Aug 19 23:38:50 Is there a way to update device-port on github if I want to pick something up? Aug 19 23:39:03 @K31j0, huh? Aug 19 23:39:11 https://github.com/Halium/projectmanagement/issues/57 Aug 19 23:39:15 I want to pick osprey up Aug 19 23:39:20 don't want to create a second issue Aug 19 23:39:39 @UniversalSuperBox, who blamed who? the fact i joked about the "git blame" feature? :P we solved it quickly and easily, what's the matter Aug 19 23:39:56 @K31j0, well you can just start porting it Aug 19 23:40:00 there are 2 solutions Aug 19 23:40:31 1) i close this issue for inactivity, you make a new one … 2) i edit this issue when you ask me to, and then eventually you get into the org and edit it yourself Aug 19 23:40:49 but for now, just start porting, you're welcome to do so Aug 19 23:41:11 Okay Aug 19 23:41:55 1st is the quickest solutions considering there was no activity since february. but well for that to happen you need to at least achieve the same level of progress Aug 19 23:42:02 good luck my Ukrainian brother Aug 19 23:44:48 Thanks Aug 19 23:44:58 Hmm, I see they forked the trees into org Aug 19 23:45:11 They probably aren't even with LOS by now Aug 19 23:46:10 oh LNJ2 started the port, interesting. but abandoned it it seems Aug 19 23:46:28 Yep, not even and he was doing something to make it work better with Halium, I suppose Aug 19 23:46:41 @K31j0, huh? Aug 19 23:46:50 you must modify your tree to make it work with halium Aug 19 23:47:06 so well it's expected that the tree was forked Aug 19 23:47:16 so it goes under "starting the port" term Aug 19 23:47:23 yes Aug 19 23:47:43 it's described in the docs, make sure you read them all the way to the end prior to starting the port so you understand the steps Aug 19 23:47:54 Okay Aug 19 23:48:20 Just hoping the target won't die until I get a decent image, this device isn't the greatest Aug 19 23:48:45 it's split into 4 steps: … 1) getting it to build … 2) getting it to boot … 3) getting tests to pass … 4) solving rootfs-specific issues Aug 19 23:48:56 [Edit] it's split into 4 steps (if simplified): … 1) getting it to build … 2) getting it to boot … 3) getting tests to pass … 4) solving rootfs-specific issues Aug 19 23:50:15 are tests fully working on 7.1 now? there was something wrong in the past Aug 19 23:50:26 no Aug 19 23:50:34 that's an upstream libhybris issue Aug 19 23:50:50 and no one is really up to fix them. half of them need to be killed with fire Aug 19 23:51:15 that doesn't really affect the port itself. it's just the tests themselves that are broken Aug 19 23:51:28 So you fieldtest stuff that doesn't have a test for it Aug 19 23:51:31 I guess Aug 19 23:51:48 i will tell you more, it's undocumented :P Aug 19 23:52:13 i can only help you with testing audio. testing camera is only known to Bhushan i guess :P Aug 19 23:52:23 [Edit] i can only help you with testing audio. testing camera is only known to Bhushan and NotKit i guess :P Aug 19 23:52:40 Cameras are always magic to me so won't go anywhere without help, I guess :P Aug 19 23:52:49 This uses droidmedia too, am I right? Aug 19 23:53:21 audio uses droidmedia pulseaudio module, yes. and as for camera, i don't know Aug 19 23:54:11 Okay, btw one of the ospreys in my house is in half-broken state, thanks EU warranty service standards. Aug 19 23:54:16 It's 2AM, guess I'll go to sleep Aug 19 23:54:17 see ya Aug 19 23:54:29 it's 3 AM, so same. bye. good night Aug 20 01:33:39 I've still not solved the issue with it demanding a % in patterns in android_build **** ENDING LOGGING AT Mon Aug 20 03:00:00 2018