**** BEGIN LOGGING AT Tue Sep 10 02:59:58 2019
Sep 10 08:35:52 <ubptgbot> Michael Eden was added by: Michael Eden
Sep 10 09:28:05 <sdfn_amrith> hello what is the current version of halium?
Sep 10 09:28:55 <sdfn_amrith> is it possible to port halium for a android device with 3.4 kernel has lineage 14.1 source and kernels
Sep 10 09:29:26 <ubptgbot> Matthew Good was added by: Matthew Good
Sep 10 09:29:32 <ubptgbot> <Matthew Good> Hai
Sep 10 09:29:55 <ubptgbot> <Matthew Good> Halium support this right?
Sep 10 09:30:03 <ubptgbot> <Matthew Good> (Photo, 1280x622) https://irc.ubports.com/eKZVORR7.png
Sep 10 09:54:33 <fgfgf_amrith> anyone?
Sep 10 09:59:54 <ubptgbot> <minlexx> @sdfn_amrith [is it possible to port halium for a android device with 3.4 kernel has lineage 1 …], possible
Sep 10 10:12:15 <ubptgbot> <Matthew Good> Wonder if it's possible to get live boot working
Sep 10 10:17:57 <ubptgbot> <NotKit> @Matthew Good [Wonder if it's possible to get live boot working], what are you trying to do?
Sep 10 10:17:57 <ubptgbot> <NotKit> the screenshot doesn't tell much
Sep 10 10:23:59 <ubptgbot> <Matthew Good> Does halium support the ability to drop to rootfs if mounting the OS fails
Sep 10 10:25:16 <ubptgbot> <JBBgameich> Well the rootfs contains the os,  so I don't see how if should he booted if mounting fails.
Sep 10 10:26:04 <ubptgbot> <Matthew Good> @JBBgameich [Well the rootfs contains the os,  so I don't see how if should he booted if moun …], like what is happening in my screenshot
Sep 10 10:27:27 <ubptgbot> <Matthew Good> (simplified) It mounts the OS on /new_root and then chroots into it via chroots /new_root /init
Sep 10 10:28:21 <ubptgbot> <JBBgameich> That's how a normal boot works, just with switch_root instead of chroot.
Sep 10 10:28:58 <ubptgbot> <Matthew Good> Does halium support doing that
Sep 10 10:30:57 <ubptgbot> <JBBgameich> Sorry, I still don't understand.  Halium boots into the rootfs like this, but of course not if mounting fails, because then it can't access the rootfs at all.
Sep 10 10:31:21 <ubptgbot> <Matthew Good> Ok
Sep 10 10:31:49 <ubptgbot> <Matthew Good> I don't understand it either lol
Sep 10 10:32:38 <ubptgbot> <NotKit> it will dropout to telnet shell in this case
Sep 10 10:33:06 <ubptgbot> <Matthew Good> @NotKit [it will dropout to telnet shell in this case], Ok
Sep 10 10:33:25 <ubptgbot> <Matthew Good> Is it possible to live boot
Sep 10 10:33:47 <ubptgbot> <Matthew Good> Eg boot an OS without installing it
Sep 10 10:34:58 <ubptgbot> <NotKit> not exactly, but in theory you could modify halium-boot to pickup sdcard
Sep 10 10:35:07 <ubptgbot> <NotKit> you would still have to flash boot though
Sep 10 10:35:23 <ubptgbot> <Matthew Good> How come?
Sep 10 10:35:42 <ubptgbot> <Matthew Good> @NotKit [you would still have to flash boot though], Why?
Sep 10 10:36:09 <ubptgbot> <Matthew Good> @NotKit [you would still have to flash boot though], [Edit] What do you mean?
Sep 10 11:24:53 <ubptgbot> <stefanomelchior> @Herrie [@stefanomelchior: Seems you're missing the kernel repo in your device manifest s …], Herrie: just added kernel repo (kernel/bq/msm8953), but still having java related errors
Sep 10 11:34:43 <ubptgbot> <dohbee> @Matthew Good [What do you mean?], Phones do not work the same as your PC, no
Sep 10 11:37:56 <ubptgbot> <Flohack> @Matthew Good [What do you mean?], He means that you have to modify the boot partition which means unlocking the phone and flashing over the original one with a modified kernel
Sep 10 11:38:07 <ubptgbot> <Flohack> Or better, modified initrd script
Sep 10 11:46:35 <Herrie> @stefanomelchior: Can you let me know the URL for kernel repo and will check @ my side
Sep 10 11:47:48 <ubptgbot> <stefanomelchior> @Herrie [@stefanomelchior: Can you let me know the URL for kernel repo and will check @ m …], Herrie: https://github.com/stefanomelchior/android_kernel_bq_msm8953-1
Sep 10 11:48:30 <ubptgbot> <stefanomelchior> I used `revision="lineage-15.1`
Sep 10 11:56:40 <Herrie> @stefanomelchior: OK trying at my end now, should have some results in a few mins
Sep 10 11:57:06 <Herrie> @stefanomelchior: Builder is Threadripper 2990 and have 750/750 fibre, so things fly )
Sep 10 11:57:07 <Herrie> ;)
Sep 10 11:59:13 <Herrie> Hmmz it's failing on audio bits, I've seen this before on another target. Is due to API changes somewhere... I'll have a look
Sep 10 12:06:18 <Herrie> OK found the source, need to do some patching. Seem mer's frameworks_av is older and doesn't match the API in android_hardware_qcom_audio anymore. I'll for LOS and apply Mer's patch instead and switch repo to allow it to continue. I recall I did this previously, but maybe forgot to push it somewhere
Sep 10 12:23:58 <ubptgbot> <Matthew Good> @Flohack [He means that you have to modify the boot partition which means unlocking the ph …], Ok
Sep 10 12:31:02 <Herrie> @stefanomelchior: My build is now close to a "success". My android and halium-devices repos are up to date now on GitHub, so you should be able to replicate. I just built this from scratch now at my builder and it's "working" at my end.
Sep 10 12:31:31 <Herrie> @stefanomelchior: With "success" and "working" I mean that I get an image that completes building
Sep 10 12:32:21 <Herrie> @stefanomelchior: Last bits from my log: https://paste.ubuntu.com/p/dz7MmKW9GF/
Sep 10 12:58:18 <ubptgbot> <stefanomelchior> @Herrie [@stefanomelchior: My build is now close to a "success". My android and halium-de …], so with a `repo sync` I should resync the tree and then build a system.img
Sep 10 12:58:30 <ubptgbot> <stefanomelchior> ops ... `error: Cannot checkout herrie82/android_frameworks_av: ManifestInvalidRevisionError: revision halium-8.1 in herrie82/android_frameworks_av not found … error: in `sync`: revision halium-8.1 in herrie82/android_frameworks_av not found`
Sep 10 12:58:55 <Herrie> It's there... https://github.com/Herrie82/android_frameworks_av/tree/halium-8.1
Sep 10 13:04:52 <Herrie> @stefanomelchior: This is the build script we use @ LuneOS to build the minimal android bits using Halium: https://paste.ubuntu.com/p/dtHcFNRfnS/ This will give us a .tar.bz2 which we use as input for our LuneOS build. We build the kernel @ LuneOS end with other toolchain (Latest GCC provided by Yocto project, GCC 8.3 as of now
Sep 10 13:05:28 <Herrie> Our kernel config requirements are similar to Mer and we can use their kernel verification script 1:1 for LuneOS.
Sep 10 16:37:36 <ubptgbot> Amrock was added by: Amrock
Sep 10 16:40:19 <ubptgbot> <Amrock> I was going through the documentation and porting a device , I saw that CONFOG_IKCONFIG and CONFIG_IKCONFIG_PROC should be set. When I use check kernel config , those are not shown (means it is not set right?)
Sep 10 16:40:30 <ubptgbot> <Amrock> Where to set it?
Sep 10 16:51:47 <ubptgbot> <Akatsu .> inside device defconfig
Sep 10 16:52:08 <ubptgbot> <Akatsu .> Amrock are you going to port ubports?
Sep 10 16:52:40 <ubptgbot> <Amrock> Helium , then ubiports
Sep 10 16:52:51 <ubptgbot> <Amrock> Yes finally I should be
Sep 10 16:53:04 <ubptgbot> <Akatsu .> Ubports requires different kernel parameters
Sep 10 16:53:30 <ubptgbot> <Akatsu .> You have to build halium-boot not hybris
Sep 10 16:53:37 <ubptgbot> <dohbee> ubuntu touch is the OS. ubports is the community/foundation
Sep 10 16:53:57 <ubptgbot> <Akatsu .> By ubports we mean ut
Sep 10 16:55:18 <ubptgbot> <Amrock> But the documentation is for hybris boot right?. Idk I am doing this for the first time. How to build image for halium-boot
Sep 10 16:57:01 <ubptgbot> <Amrock> So if I have to first get a halium port for my device and finally Ubuntu touch os , what path should I take?
Sep 10 16:57:20 <ubptgbot> <Amrock> Is it hybris boot or halium boot?
Sep 10 16:58:01 <ubptgbot> <Akatsu .> Halium docs are for hybris indeed
Sep 10 16:58:16 <ubptgbot> <Akatsu .> Look on ubports docs for halium-boot
Sep 10 16:58:54 <ubptgbot> <Akatsu .> Well what kernel version do you have?
Sep 10 17:01:12 <ubptgbot> <Amrock> 3.4
Sep 10 17:01:32 <ubptgbot> <Akatsu .> Then it's problematic.
Sep 10 17:01:50 <ubptgbot> <Akatsu .> Ubports require 3.10 atleast
Sep 10 17:02:20 <ubptgbot> <dohbee> 3.4 should be fine
Sep 10 17:02:27 <ubptgbot> <Akatsu .> Yes but require patching
Sep 10 17:02:35 <ubptgbot> <dohbee> yes, so add the patches
Sep 10 17:02:36 <ubptgbot> <Akatsu .> *more patching
Sep 10 17:02:47 <ubptgbot> <dohbee> even 4.4 would require patching
Sep 10 17:02:56 <ubptgbot> <Akatsu .> Every single  requires
Sep 10 17:03:05 <ubptgbot> <dohbee> exactly
Sep 10 17:03:17 <ubptgbot> <Akatsu .> But you have more chance to get it working starting from 3.10
Sep 10 17:03:32 <ubptgbot> <Amrock> Is it mentioned in the documentation?
Sep 10 17:03:36 <ubptgbot> <dohbee> only way to not need patching is to get mainline working
Sep 10 17:03:51 <ubptgbot> <Akatsu .> Works for 2 devices xD or more?
Sep 10 17:04:45 <ubptgbot> <Akatsu .> http://docs.halium.org/en/latest/porting/build-sources.html
Sep 10 17:05:27 <ubptgbot> <Amrock> @Akatsu . [But you have more chance to get it working starting from 3.10], No everyrom uses 3.4 and I don't really know how to upgrade to 3.10 (I would have to compile the kernel 3.10 I guess)
Sep 10 17:06:33 <ubptgbot> <Amrock> But I have seen ubiports in Nexus 5 it's older that the device I am porting and many other devices too
Sep 10 17:06:55 <ubptgbot> <Akatsu .> Nexus 5 is 3.4 kernel too
Sep 10 17:07:33 <ubptgbot> <Amrock> Yeah
Sep 10 17:07:46 <ubptgbot> <Akatsu .> It's good idea to look at repos, you can find potential fixes for issues which aren't mentioned in docs
Sep 10 17:08:11 <ubptgbot> <Amrock> OK I will try that
Sep 10 17:08:30 <ubptgbot> <Akatsu .> And lots of them are not mentioned for ubports, like additional lxc defconfig parameters,
Sep 10 17:10:06 <ubptgbot> <dohbee> @Amrock [No everyrom uses 3.4 and I don't really know how to upgrade to 3.10 (I would hav …], no. only devices which shipped with 3.10 kernel can use 3.10 kernel.
Sep 10 17:10:52 <ubptgbot> <Akatsu .> Is that valid from technical standpoint?
Sep 10 17:11:09 <ubptgbot> <Amrock> @dohbee [no. only devices which shipped with 3.10 kernel can use 3.10 kernel.], Yeah or compile the kernel with drivers and follow Linus Torvalds (not possible for me)
Sep 10 17:12:23 <ubptgbot> <dohbee> @Akatsu . [Is that valid from technical standpoint?], yes, because the drivers are proprietary and will not work with different kernels because internal API/ABI is broken all the time with kernel.
Sep 10 17:12:54 <ubptgbot> <dohbee> @Amrock [Yeah or compile the kernel with drivers and follow Linus Torvalds (not possible …], well, the only way to get a newer kernel would be to get open source drivers. at which point you could use kernel 5.2 even
Sep 10 17:13:12 <ubptgbot> <Akatsu .> But it's possible for OEM to upgrade kernel and rewrite drivers
Sep 10 17:13:36 <ubptgbot> <dohbee> @Akatsu . [But it's possible for OEM to upgrade kernel and rewrite drivers], well, you are welcome to go convince said OEM to do that for this device
Sep 10 17:13:45 <ubptgbot> <dohbee> good luck with it
Sep 10 17:14:08 <ubptgbot> <Akatsu .> Sony once from what I know tried to port 4.x on snapdragon 652, like most stuff was broken
Sep 10 17:14:14 <ubptgbot> <dohbee> also, many OEMs can't do that, because they don't have driver source. they get what the SoC maker gives them
Sep 10 17:15:06 <ubptgbot> <dohbee> MTK won't even let OEMs release vendor/device tree for example
Sep 10 17:15:08 <ubptgbot> <Akatsu .> So let's say Qualcomm release 4.9 for snapdragon 625 why it's not possible for oems to upgrade from 3.18
Sep 10 17:15:25 <ubptgbot> <Akatsu .> Mtk is like worst case scenario for open-source
Sep 10 17:16:47 <ubptgbot> <LucentW> @Akatsu . [So let's say Qualcomm release 4.9 for snapdragon 625 why it's not possible for o …], because OEM hunk lots of code specific to their hardware, and that renders porting nearly impossible if not with big efforts
Sep 10 17:16:50 <ubptgbot> <LucentW> @Akatsu . [So let's say Qualcomm release 4.9 for snapdragon 625 why it's not possible for o …], [Edit] because OEM hunk lots of code specific to their hardware, and that renders porting nearly impossible if not with big effort
Sep 10 17:17:14 <ubptgbot> <NotKit> @Akatsu . [Ubports require 3.10 atleast], still 3.4 currently
Sep 10 17:17:33 <ubptgbot> <dohbee> @Akatsu . [So let's say Qualcomm release 4.9 for snapdragon 625 why it's not possible for o …], why are you talking about theoretical things? Qualcom isn't going to do it. Just like they don't ship firmware updates for no longer supported hardware either. And OEMs probably wouldn't bother even if Qualcom did this when new Android versions
Sep 10 17:17:33 <ubptgbot> were released, because it would be too much work for devices they've already released
Sep 10 17:18:31 <ubptgbot> <NotKit> Akatsu really if you want updated kernel, the only thing that could work is teaming up with postmarketOS folks and mainlining the device
Sep 10 17:19:47 <ubptgbot> <NotKit> Qualcomm/OEMs mostly don't care if it is not for their new shiny product
Sep 10 18:24:42 <ubptgbot> <fredldotme> (Photo, 2560x1451) https://irc.ubports.com/A2WToH35.png
Sep 10 18:25:36 <ubptgbot> <fredldotme> guess what that means :)
Sep 10 18:27:09 <ubptgbot> <dohbee> @fredldotme [guess what that means :)], camera rotation is wrong? :P
Sep 10 18:27:43 <ubptgbot> <fredldotme> well, yeah, that too ^^
Sep 10 18:27:53 <ubptgbot> <fredldotme> but hardware support is 100% complete now
Sep 10 18:27:59 <ubptgbot> <bhushanshah> @fredldotme [well, yeah, that too ^^], But gst Droid thingie works?
Sep 10 18:28:08 <ubptgbot> <Amrock> Who writes the Python script in build/tools?
Sep 10 18:29:09 <ubptgbot> <Amrock> I literally got an error with missing space . Only 3 space before a statement inside if
Sep 10 18:29:10 <ubptgbot> <dohbee> @fredldotme [but hardware support is 100% complete now], on xperia?
Sep 10 18:29:43 <ubptgbot> <fredldotme> @bhushanshah [But gst Droid thingie works?], That's with UTs default gst. But a recent change in the frameworks part has caused codec listing to be loaded correctly.
Sep 10 18:29:49 <ubptgbot> <fredldotme> @dohbee [on xperia?], yup
Sep 10 18:29:54 <ubptgbot> <Amrock> Lots of errors in Python including print statement, nothing major atleast
Sep 10 18:30:03 <ubptgbot> <dohbee> @fredldotme [yup], nice!
Sep 10 18:31:49 <ubptgbot> <fredldotme> ah, switching to the front camera fails, but soon (tm)
Sep 10 19:44:29 <ubptgbot> <Amrock> I was able to generate system image . But there was a message "fs is not ext4" . Should it be? Where to change it?
Sep 10 19:45:31 <ubptgbot> <Akatsu .> mountpoints and fstab inside device tree
Sep 10 19:45:38 <ubptgbot> <Akatsu .> its mentioned in docs
Sep 10 20:01:29 <ubptgbot> <Amrock> OK.thanks
Sep 10 20:34:46 <ubptgbot> <JBBgameich> @Amrock [Who writes the Python script in build/tools?], Someone at google.
Sep 11 00:58:07 <B[]> Hello
Sep 11 00:58:26 <B[]> I'm looking to port to a non-supported device
Sep 11 00:58:32 <B[]> What is the best approach to this?
Sep 11 01:01:37 <B[]> Starting from here:
Sep 11 01:01:38 <B[]> http://docs.halium.org/en/latest/porting/first-steps.html
Sep 11 01:04:03 <B[]> What is the best version of Ubuntu to compile this all in?
Sep 11 01:11:47 <ubptgbot> <dohbee> It doesn't matter, any should be much the same
Sep 11 01:12:47 <B[]> Okay ty
**** ENDING LOGGING AT Wed Sep 11 03:00:21 2019