**** BEGIN LOGGING AT Wed Mar 27 02:59:57 2019 Mar 27 08:37:45 suranju410 was added by: suranju410 Mar 27 09:28:21 i added caf repo, got this error … The repository 'http://repo.halium.org/caf xenial InRelease' is not signed … how can i resolve it ? Mar 27 10:35:20 Pierre Drolet was added by: Pierre Drolet Mar 27 11:49:41 nthnael was added by: nthnael Mar 27 14:37:34 Hello, build just finished, bust need an alternative link to download halium-rootfs (impossible from browser and even with wget). Someone have this here ? Mar 27 14:44:05 http://bshah.in/halium/halium-rootfs-20170630-151006.tar.gz Mar 27 14:50:46 thks, i had this url it wasn't working but now it works... Mar 27 15:44:24 Samurai Ninja was added by: Samurai Ninja Mar 27 16:15:58 tsimonq2 was added by: tsimonq2 Mar 27 16:21:25 Is work going on over using Android 9 sources Mar 27 16:22:04 If there is then I am ready to test Mar 27 16:22:50 Sorry, but that effort is nowhere near needing people to test. Also, Halium should be invisible to the end user, so you'd be testing Plasma Mobile or Ubuntu Touch using Halium, not Halium itself. Mar 27 16:24:00 I only have a Android 9 device to try things so I was asking Mar 27 16:24:22 Can I try porting to lineage 16 sources Mar 27 19:33:41 I've been trying to build a tissot image for the past couple of days. I originally had issues with `mka mkbootimg` but was able to download a more recent version of the hybris boot Android.mk and that seems to work. Mar 27 19:35:08 However, now when I try to run `mka systemimage` it asks for proprietary blobs that I just can't seem to find anywhere Mar 27 19:37:17 The first one in particular is `fingerprintd` but if I comment that out in the `proprietary-files.txt` document it changes to another one... Mar 27 20:01:14 Is there anywhere I can check for those proprietary bits outside of TheMuppets' Github? I've already ran the `extract-files.sh` on both LineageOS and Stock Android. Mar 27 20:01:14 Alternatively, is there a way I can just tell the build to ignore the fingerprint reader? Due to privacy reasons I don't like using it so not having it isn't a big deal to me Mar 27 22:50:10 SomeRandom_Person was added by: SomeRandom_Person Mar 27 22:52:44 I know this is a very stupid question, but I will ask anyway. I'm trying to port halium to the moto g5s (montana), I (think) that followed all the steps but when i try to sync it gives out an error like this: /halium/devices/setup: line 23: [: /home/me/Downloads/Halium: binary operator expected … The given device is not su Mar 27 22:52:44 pported. :( Mar 27 22:53:14 Does anyone know how to fix it? Mar 27 23:39:22 🤔 Mar 27 23:45:12 What directions are you following? Mar 27 23:45:33 http://docs.halium.org/en/latest/porting/get-sources.html Mar 27 23:46:19 Ok, does this happen after you make your manifest? Mar 27 23:46:32 yes Mar 27 23:46:41 i configure the .xml file Mar 27 23:46:51 try to run to run setup.sh Mar 27 23:47:07 and it pops out this error Mar 27 23:47:54 Ok, try putting your manifest in ".repo/local_manifests" and just do repo sync again Mar 27 23:48:01 ok Mar 27 23:48:30 Any suggestions on my issue? Mar 27 23:55:11 Ummmmm Mar 27 23:55:17 Pardon me but... Mar 27 23:55:18 https://pastebin.com/a9scb7ym Mar 28 00:52:48 Ok Solved This Problem Mar 28 00:53:25 but "The given device is not supported" error is still happening Mar 28 01:11:56 Hmm, can you paste your manifest? Mar 28 02:00:14 Ok, i'll start debug tonight, first steps done, system is booting up, staying on start screen but lsusb tell it's ok like in that step : https://docs.halium.org/en/latest/porting/debug-build/early-init.html Mar 28 02:02:17 if log in is ok i'll add my device (vegetalte - BQ aquaris E5-4G) Mar 28 02:02:35 have a nice day **** ENDING LOGGING AT Thu Mar 28 02:59:57 2019