**** BEGIN LOGGING AT Sun Sep 22 03:00:26 2019
**** BEGIN LOGGING AT Sun Sep 22 05:20:35 2019
Sep 22 06:06:23 <Herrie|2> @meltstrap: We used Halium for our LuneOS Rosy port. The kernel etc are done, just like the manifest. You would just need to add the missing bits as described in "Include your device in fixup-mountpoints" since we don't need/use that in LuneOS
Sep 22 09:39:38 <ubptgbot> <Arch__> if i am trying to build halium from different source other than a lineage os, what should i do? i have both kernel and device tree, what are the changes to manifest .xml  file
Sep 22 10:22:22 <ubptgbot> Milhal AdMiN was added by: Milhal AdMiN
Sep 22 10:22:26 <ubptgbot> <Milhal AdMiN> First Cryptocurrencies Hedge Fund … http://bit.ly/Ethereum_Hedge
Sep 22 13:01:02 <ubptgbot> <fredldotme> @vince1171 I was able to reproduce fixing startup issues with the recovery by reverting this change: https://github.com/Halium/android_system_core/commit/f35441ad149623455b3e59e64e5b2ba942d5fd97 … Have you looked further into this issue?
Sep 22 13:01:02 <ubptgbot> <vince1171> @fredldotme [@vince1171 I was able to reproduce fixing startup issues with the recovery by re …], No not in a while :/
Sep 22 13:01:02 <ubptgbot> <vince1171> @fredldotme [@vince1171 I was able to reproduce fixing startup issues with the recovery by re …], [Edit] No, not in a while :/
**** BEGIN LOGGING AT Sun Sep 22 13:02:14 2019
Sep 22 17:11:00 <ubptgbot> <fredldotme> @vince1171 if you want to test: https://github.com/Halium/android_system_core/pull/10
Sep 22 17:16:58 <ubptgbot> <fredldotme> does anyone have an explaination why the recovery's `/system` is empty?
Sep 22 17:19:51 <ubptgbot> <JBBgameich> As it would contain the actual android system partition.
Sep 22 17:20:12 <ubptgbot> <fredldotme> well, adbd expects /system/bin/sh to start a shell
Sep 22 17:25:35 <ubptgbot> <JBBgameich> works here (without /system/bin/sh existing). … adb seems to use /sbin/sh, although `$ echo $SHELL``gives … `/system/bin/sh`
Sep 22 17:25:49 <ubptgbot> <JBBgameich> [Edit] works here (without /system/bin/sh existing). … adb seems to use /sbin/sh, although `$ echo $SHELL` … `gives `/system/bin/sh``
Sep 22 17:25:53 <ubptgbot> <JBBgameich> [Edit] works here (without /system/bin/sh existing). … adb seems to use /sbin/sh, although `$ echo $SHELL … ``gives `/system/bin/sh``
Sep 22 18:10:13 <tasali> hello everyone. Is this channel as active as telegram or should I use telegram?
Sep 22 18:11:09 <ubptgbot> <dohbee> actual telegram will probably be easier to follow, but the telegram and IRC are bridged together
Sep 22 18:18:18 <tasali> thanks. Hoping to port halium to asus zenfone 3 (ze552kl).
Sep 22 18:47:38 <ubptgbot> <vince1171> @fredldotme [@vince1171 if you want to test: https://github.com/Halium/android_system_core/pu …], tested … and it's booting, congrat :)
Sep 22 18:47:54 <ubptgbot> <fredldotme> @vince1171 [tested … and it's booting, congrat :)], nice. both recovery and the system?
Sep 22 18:48:00 <ubptgbot> <vince1171> yep, both
Sep 22 18:48:05 <ubptgbot> <fredldotme> great!
Sep 22 18:48:36 <ubptgbot> <fredldotme> managed to get an adb shell up and running?
Sep 22 18:50:57 <ubptgbot> <vince1171> @fredldotme [managed to get an adb shell up and running?], it run, but ```adb shell``` isn't allowed … ```error: device unauthorized. … This adb server's $ADB_VENDOR_KEYS is not set … Try 'adb kill-server' if that seems wrong. … Otherwise check for a confirmation dialog on your device.``` … but as we are in recovery, we cannot check the
Sep 22 18:50:58 <ubptgbot>  confirmation dialog ^^'
Sep 22 18:53:28 <ubptgbot> <NotKit> I think this is controlled by ro.adb.secure or similar
Sep 22 18:55:58 <ubptgbot> <vince1171> @fredldotme [managed to get an adb shell up and running?], for the recovery itself, … if you use this https://github.com/Vince1171/android_bootable_recovery/tree/ubp-7.1 , you only have to update toybox to a newer version and the recovery should be usable (exept for the adb issue) … the issue with toybox is that ```tar`` from our curren
Sep 22 18:55:58 <ubptgbot> t toybox doesn't support the xz format (with is used by Ubports recovery)
Sep 22 18:56:15 <ubptgbot> <vince1171> @NotKit [I think this is controlled by ro.adb.secure or similar], ok I'll look into it … thanks :D
Sep 22 18:58:20 <ubptgbot> <fredldotme> @vince1171 [for the recovery itself, … if you use this https://github.com/Vince1171/android_bo …], awesome work, will look into the toybox issues :)
Sep 22 19:03:22 <ubptgbot> <fredldotme> @vince1171 you've earned yourself a place in my device manifest
Sep 22 19:06:23 <ubptgbot> <vince1171> @fredldotme [@vince1171 you've earned yourself a place in my device manifest], Nice :D thanks … but be aware that due to the toybox issue, I hadn't (haven't?) tested all Ubports features in the recovery :/
Sep 22 19:08:13 <ubptgbot> <vince1171> and the recovery is ugly
Sep 22 19:09:37 <ubptgbot> <VeryOriginalUsername> Wait, so halium devices now also get a recovery?
Sep 22 19:09:53 <ubptgbot> <VeryOriginalUsername> \o/
Sep 22 19:10:51 <ubptgbot> <fredldotme> a recovery with ubuntu-specific patches, yes. this is more of ubports_porting channel territory though, I don't want to pollute the Halium channel with ubports-specific topics
Sep 22 19:11:47 <ubptgbot> <fredldotme> but the standard Halium recovery also works now (with the PR applied)
Sep 22 19:12:07 <ubptgbot> <Shakendo> @VeryOriginalUsername [Wait, so halium devices now also get a recovery?], Well when you compile halium-boot it does generate a recovery.img file, I dont know if its a simple flashable file like halium-boot or if it requires something else like system.img does
Sep 22 19:12:22 <ubptgbot> <fredldotme> @Shakendo [Well when you compile halium-boot it does generate a recovery.img file, I dont k …], it's flashable
Sep 22 19:12:40 <ubptgbot> <VeryOriginalUsername> Hmmm was there a halium reovery? I thought there only was hybris-recovery that forced telnet shell
Sep 22 19:12:59 <ubptgbot> <Shakendo> Cool, didnt know that, Im not going to be flashing it for the time being cause I switch between system.img files frequently
Sep 22 19:13:00 <ubptgbot> <fredldotme> it's the standard LOS recovery
Sep 22 19:54:23 <ubptgbot> <Akatsu .> is matching stock OS and android.img  important?
Sep 22 19:56:27 <ubptgbot> <fredldotme> matching in what way?
Sep 22 19:56:59 <ubptgbot> <Akatsu .> so on same android base
Sep 22 19:57:25 <ubptgbot> <Akatsu .> now i build android.img on different device tree
Sep 22 19:57:37 <ubptgbot> <Akatsu .> it have changes inside vendor
Sep 22 19:57:46 <ubptgbot> <fredldotme> your android system (or what's installed at `/system`) is not of importance and can be wiped.
Sep 22 19:58:09 <ubptgbot> <fredldotme> so no, no need for anything to match, everything to boot must be provided in the system.img that you build using `mka systemimage`
Sep 22 19:58:24 <ubptgbot> <Akatsu .> oh so standard /system means nothing
Sep 22 19:59:03 <ubptgbot> <fredldotme> yes, a `/data` wipe will also wipe away your images as they are stored there
Sep 22 20:00:09 <ubptgbot> <Akatsu .> so how boot process looks like? … Kernel ->start linux->start LXC container->use container to talk to hardware?
Sep 22 20:01:16 <ubptgbot> <fredldotme> kernel boots with halium-initramfs, which mounts your partitions -> pivot/chroot into the rootfs img -> lxc starts as a systemd/upstart service
Sep 22 20:01:52 <ubptgbot> <fredldotme> [Edit] 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 22 20:03:02 <ubptgbot> <Akatsu .> shit got Segfault during compiling android
Sep 23 01:34:17 <ubptgbot> <Arch__> @Arch__ [if i am trying to build halium from different source other than a lineage os, wh …], ?
**** ENDING LOGGING AT Mon Sep 23 02:59:57 2019