**** BEGIN LOGGING AT Fri Sep 27 02:59:57 2019 **** BEGIN LOGGING AT Fri Sep 27 04:20:54 2019 Sep 27 05:48:53 Vince and I have been working on a recovery suitable for Ubuntu Touch. Is there interest in the broader Halium space in having a fully featured recovery (full busybox support)? Sep 27 05:49:42 It does include the system-image components necessary for our OS upgrades so I’m basically asking if someone’s turned off by that. Sep 27 05:50:50 [Edit] It does include the system-image components necessary for our OS upgrades so I’m basically asking if someone’s having a problem with that. Sep 27 05:52:43 Idk all is ok with twrp Sep 27 05:52:51 It’s not „fully featured“ in the sense that it doesn’t have a backup-and-restore story Sep 27 05:53:12 But can it work with android? Sep 27 05:53:14 @Luka Panio [Idk all is ok with twrp], official ports need the system-image portions so TWRP wouldn’t be enough Sep 27 05:53:33 @Luka Panio [But can it work with android?], You can theoretically install android ROMs with it as well, though untested Sep 27 05:54:09 @fredldotme [official ports need the system-image portions so TWRP wouldn’t be enough], But there is no system-image partition Sep 27 05:54:17 Only system Sep 27 05:54:22 And data Sep 27 05:54:32 In android based phones Sep 27 05:55:06 you don’t understand, `system-image` is a set of tools to compose official Ubuntu Touch releases Sep 27 05:55:23 Ohh ok Sep 27 05:55:29 What it dose? Sep 27 05:56:23 For upgrade? Sep 27 05:57:14 yes it’s for upgrading the system Sep 27 06:12:25 Is it possible to port halium for a device with 8gb internal storage? Sep 27 06:13:17 8gb total or 8gb on the userdata partition? Sep 27 06:15:23 @Venji10 [Is it possible to port halium for a device with 8gb internal storage?], You can but then the user has left only little space for stuff. The rootfs and such should.not.be more than 2 gigs at the end Sep 27 06:20:52 @fredldotme [8gb total or 8gb on the userdata partition?], Total Sep 27 06:21:29 then you won’t have much free space available for user data, as Florian said Sep 27 06:33:49 use microSD maybe Sep 27 06:34:12 for rootfs and such Sep 27 07:02:27 @NotKit [use microSD maybe], Which is not easy to achieve right now Sep 27 07:03:03 @Flohack [Which is not easy to achieve right now], one line change in init script Sep 27 07:07:47 @NotKit [one line change in init script], Well then this port would require to have an SD card always in place. It would be better to have an option to do this, and from thereon it geets complicated ^^ Sep 27 07:13:46 yeah, but it works for testing and allows to work on other port parts Sep 27 07:27:40 True Sep 27 13:41:43 or better yet, get rootfs into system partition instead of data Sep 27 13:54:51 system partitions are like 1.7GB Sep 27 13:55:05 isn;t data much bigger? Sep 27 13:56:17 of course data is bigger, it's for data, not the system Sep 27 13:57:27 and we'll never be able to sign images and enable locking bootloader, until rootfs is placed in system partition Sep 27 14:11:45 You won't be able to sign them without oem's key afaik Sep 27 14:13:03 and where did lineageos and microg get their keys? Sep 27 14:13:38 According to the fastboot spec, it is permissible to sign the boot image with a key contained in the boot image. Sep 27 14:13:52 Though that will not send you to GREEN boot state Sep 27 14:14:25 https://source.android.com/security/verifiedboot/boot-flow Sep 27 14:21:54 @dohbee [and where did lineageos and microg get their keys?], Not sure about other vendors, but sony bootloader won't boot any non-sony-provided firmware (that is bootimgs and system images) if it's not unlocked as far as I can tell Sep 27 16:33:05 Hmmm same here Sep 27 16:33:16 On s5 active att Sep 27 16:33:27 And no bl unlock Sep 27 16:34:53 @Luka Panio [On s5 active att], Safestrap? Sep 27 16:35:11 Kinde of it Sep 27 16:35:23 It wount help Sep 27 16:35:28 No kexec Sep 27 16:36:27 Just for flashing stock based rom **** ENDING LOGGING AT Sat Sep 28 02:59:59 2019