**** BEGIN LOGGING AT Mon Nov 09 03:02:03 2020
Nov 09 06:27:00 <ubptgbot> <JayAware> which path do i put my device kernel?
Nov 09 06:27:03 <ubptgbot> <JayAware> manually
Nov 09 06:29:14 <ubptgbot> <JayAware> @NotKit
Nov 09 06:29:48 <ubptgbot> <NotKit> need context of what you're trying to do
Nov 09 06:30:02 <ubptgbot> <JayAware> building halium 9
Nov 09 06:30:06 <ubptgbot> <JayAware> for ubports
Nov 09 06:31:21 <ubptgbot> <JayAware> @NotKit
Nov 09 06:34:03 <ubptgbot> <NotKit> still does not help, building which way?
Nov 09 06:34:20 <ubptgbot> <NotKit> if you compile kernel out of tree, follow any out of tree compilation guides
Nov 09 06:34:39 <ubptgbot> <JayAware> we use separate kernel source
Nov 09 06:34:48 <ubptgbot> <JayAware> it is not in tree
Nov 09 06:37:19 <ubptgbot> <NotKit> then you do not put it in tree and compile separately
Nov 09 08:09:29 <ubptgbot> <JayAware> https://del.dog/thygnopere.txt
Nov 09 08:09:34 <ubptgbot> <JayAware> boot image is built
Nov 09 08:09:43 <ubptgbot> <JayAware> but, system image gives this error
Nov 09 08:12:01 <ubptgbot> <JayAware> @NotKit
Nov 09 08:12:43 <ubptgbot> <NotKit> why do you build system image if your device supports Treble?
Nov 09 08:16:08 <ubptgbot> <JayAware> @NotKit [why do you build system image if your device supports Treble?], It is not actually supported
Nov 09 08:16:19 <ubptgbot> <JayAware> We made a vendor partition manually
Nov 09 08:17:37 <ubptgbot> <NotKit> um... does it boot phh-gsi for Android Pie?
Nov 09 08:18:23 <ubptgbot> <JayAware> No, I guess
Nov 09 08:18:42 <ubptgbot> <JayAware> We can make a treble image of halium though
Nov 09 08:19:13 <ubptgbot> <NotKit> I feel confused since you said you made a vendor partition
Nov 09 08:19:26 <ubptgbot> <NotKit> if it is non-Treble, why do you need vendor partition then?
Nov 09 08:19:55 <ubptgbot> <JayAware> It's complicated as it is
Nov 09 08:20:18 <ubptgbot> <JayAware> I've asked a friend to test the gsi
Nov 09 08:20:23 <ubptgbot> <JayAware> Let's see if it works
Nov 09 08:22:57 <ubptgbot> <NotKit> @JayAware [It's complicated as it is], I agree. Basically do not mix things together. If you plan to go Treble way with custom-made vendor partition, then build kernel and use GSI. … If you need device specific Halium 9 based build, fix device tree to compile kernel in place and build full systemimage with vendor files inside, no need for
Nov 09 08:22:57 <ubptgbot> a vendor partition
Nov 09 08:24:36 <ubptgbot> <NotKit> well, mixing can work to some extent, but it's up to you to fix what may break in any case
Nov 09 08:36:27 <ubptgbot> <JayAware> @NotKit [I agree. Basically do not mix things together. If you plan to go Treble way with …], Kernel was compiled in boot image
Nov 09 08:36:41 <ubptgbot> <NotKit> you mean halium-boot or?
Nov 09 08:37:06 <ubptgbot> <JayAware> @NotKit [you mean halium-boot or?], Yes halium-boot
Nov 09 08:40:37 <renderer001> Hi I still have not found any answers, but can someone tell whether an android version 10, and a kernel 4.14.116 is compatible with any of the available builds.
Nov 09 08:41:19 <ubptgbot> <JayAware> @JayAware [https://del.dog/thygnopere.txt], @NotKit can you help with this?
Nov 09 08:42:19 <ubptgbot> <NotKit> I don't know what is wrong there, but libinit_E is probably defined in your device tree
Nov 09 08:42:37 <ubptgbot> <JayAware> @NotKit [I don't know what is wrong there, but libinit_E is probably defined in your devi …], Yes, so do I comment it?
Nov 09 08:42:56 <ubptgbot> <NotKit> no idea what it does or if it is needed, but you can try
Nov 09 08:43:06 <ubptgbot> <JayAware> Ol
Nov 09 08:43:09 <ubptgbot> <JayAware> [Edit] Ok
Nov 09 12:06:24 <ubptgbot> Emmy SINXXXX was added by: Emmy SINXXXX
Nov 09 13:22:09 <ubptgbot> Lubomir was added by: Lubomir
Nov 09 13:24:13 <ubptgbot> <JayAware> https://del.dog/eamowuhudu.txt
Nov 09 13:24:27 <ubptgbot> <JayAware> @NotKit got past libinit_E, now this
Nov 09 13:24:47 <ubptgbot> <Ern_st> Do you know how to troubleshoot that ?  … `Camera2ClientBase: Camera 0: Opened. Client: hybris (PID 0, UID 32011) … Camera2Client: syncWithDevice: Camera 0: Timed out waiting sync with HAL … Camera2Client: notifyError: Error condition 1 reported by HAL, requestId -1 … `Regarding GSI V10 and camera app crashing the phone with ubuntu compat
Nov 09 13:24:47 <ubptgbot> layer
Nov 09 13:25:24 <ubptgbot> <Ern_st> It's at the end of the logcat : https://paste.ubuntu.com/p/6nGgrpHchR/
Nov 09 13:25:25 <ubptgbot> <NotKit> @JayAware [@NotKit got past libinit_E, now this], not something I've encountered
Nov 09 14:23:07 <ubptgbot> <Ern_st> I was able to get the media.camera service trace as mentioned in logcat : … `CameraTraces: Process trace saved. Use dumpsys media.camera to view. … `Does it speak to you this trace : https://paste.ubuntu.com/p/YDgXCrnsnD/ ?
Nov 09 14:23:39 <ubptgbot> PsychoDad81 was added by: PsychoDad81
Nov 09 14:24:40 <ubptgbot> <PsychoDad81> Hi has somebody some sucsess with the galaxy s7 (herolte)?
Nov 09 14:33:31 <ubptgbot> <Ern_st> This also is I guess relevant : … ` Camera3-Device: Camera 0: waitUntilDrainedLocked: Error waiting for HAL to drain: Connection timed out (-110) … Camera3-Device: Camera 0: sendRequestsBatch: RequestThread: Unable to submit capture request 282 to HAL device: Function not implemented (-38) … Camera3-Device: Camera 0: clearStreamingRequest:
Nov 09 14:33:32 <ubptgbot>  Device has encountered a serious error`
Nov 09 14:50:42 <ubptgbot> <aribk> @PsychoDad81 [Hi has somebody some sucsess with the galaxy s7 (herolte)?], I'm working on that device.
Nov 09 14:51:48 <ubptgbot> <aribk> I've got Ubuntu Touch up and running, but there are still multiple issues to be solved.
Nov 09 14:54:47 <ubptgbot> <X YZ> Hi all, is anybody working on or thinking of porting the Amazon Fire HD 10? Would make a really nice affordable UT-tablet, if it was possible, I think ...
Nov 09 14:57:30 <ubptgbot> <NotKit> @X YZ [Hi all, is anybody working on or thinking of porting the Amazon Fire HD 10? Woul …], bootloader does not seem to be unlockable
Nov 09 14:59:19 <ubptgbot> ROSATI WILKINSON was added by: ROSATI WILKINSON
Nov 09 15:03:26 <ubptgbot> <X YZ> @NotKit [bootloader does not seem to be unlockable], In the developer options there is an entry "OEM unlocking - Allow the bootloader to be unlocked". Have not dared to set it, because I am currently trying to play around and customize, to see how far I can get with the stock FireOS. But thought this looks promising ... so let's see ...  Whe
Nov 09 15:03:26 <ubptgbot> n changing it to "on" a warning box "Allow OEM unlocking" comes up, warning about losing device protection features. So it just might be unlockable ...
Nov 09 15:58:14 <ubptgbot> <shellphish> @X YZ [In the developer options there is an entry "OEM unlocking - Allow the bootloader …], That allows you to run something like … fastboot OEM unlock
Nov 09 15:58:24 <ubptgbot> <shellphish> Which WILL wipe data
Nov 09 15:58:49 <ubptgbot> <shellphish> But setting the option in dev settings is pretty harmless unless you have your Bitcoin wallet in there
Nov 09 16:03:07 <ubptgbot> <X YZ> @shellphish [Which WILL wipe data], That's why I did not change the setting. There is no use in actually unlocking (and losing data) until I want to flash something. And so far there does not seem to be any alternative recovery or ROM available for this device.
Nov 09 16:07:30 <ubptgbot> <SomeIrrelevantPerson0000> Hey @NotKit, I got a problem with my udev rules not showing up in UT. I can add it manually. Also, when compiling it I did add the option to add it into my system image as well by adding the lines to the device.mk file. … So the udev rules copies into the system.img successfully, but it doesn't show up when I boot into Ub
Nov 09 16:07:30 <ubptgbot> untu Touch. I verified within adb that the rules are being copied over successfully. Is this a symlink problem or something?
Nov 09 16:12:56 <ubptgbot> <aribk> (Document) https://irc.ubports.com/R4hZ6PW2.markdown
Nov 09 16:21:25 <ubptgbot> <PsychoDad81> @aribk [<reply to media>], Not Bad so far
Nov 09 16:24:18 <ubptgbot> <aribk> @PsychoDad81 [Not Bad so far], Well, progress is slow. Are you interested in working on it also?
Nov 09 16:26:25 <ubptgbot> <PsychoDad81> If i had the skills and the time 😅
Nov 09 16:27:31 <ubptgbot> <aribk> OK. Well, if you should change your mind (or know anyone else who would like to try...) ;)
Nov 09 16:36:31 <ubptgbot> Royce Pearcyа was added by: Royce Pearcyа
Nov 09 16:49:20 <ubptgbot> <PsychoDad81> The Only Thing i could offer ist testing New Versions, if that is helpfull
Nov 09 17:14:00 <nergzd723[m]1> <renderer001 "Hi I still have not found any an"> Android 9 is compatible
Nov 09 17:48:16 <ubptgbot> <Royce Pearcyа> (Photo, 626x878) https://irc.ubports.com/WKy0iWyy.png
Nov 09 23:06:07 <ubptgbot> FOG ringuette was added by: FOG ringuette
Nov 09 23:52:44 <ubptgbot> <skyliner_369> I'm wondering if there might be instructions on going from TWRP to a helium core
Nov 09 23:56:28 <ubptgbot> <skyliner_369> nevermind. Phone's too old to be considered by TWRP. was an LG escape
**** ENDING LOGGING AT Tue Nov 10 00:42:46 2020

**** BEGIN LOGGING AT Tue Nov 10 00:50:51 2020
Nov 10 00:56:44 <ubptgbot> <skyliner_369> gosh, browsing the open source stuff on LG kinda is... oof
Nov 10 00:57:51 <ubptgbot> <skyliner_369> also unable to locate package repo...
Nov 10 01:14:59 <ubptgbot> <skyliner_369> and error 13...
Nov 10 01:21:37 <ubptgbot> <skyliner_369> could I use Git over Repo? if so, how?
Nov 10 01:27:46 <ubptgbot> <skyliner_369> basically I'm following the basic guide to build for a not-already-done phone and, well, I have no idea what I'm doing. it almost seems easier to downgrade to Ubuntu 16.04 to get the guide to work...
**** ENDING LOGGING AT Tue Nov 10 02:59:56 2020