**** BEGIN LOGGING AT Wed May 22 03:02:00 2019
May 22 03:25:28 <ubptgbot> Binance bot was added by: Binance bot
May 22 04:01:00 <ubptgbot> Zuofd23 was added by: Zuofd23
May 22 08:12:28 <ubptgbot> Stas Павлов was added by: Stas Павлов
May 22 11:15:20 <ubptgbot> linda ero was added by: linda ero
May 22 11:15:27 <ubptgbot> <linda ero> (Photo, 955x480) https://irc.ubports.com/Dwjh5Nqo.png hi
May 22 11:15:28 <ubptgbot> <linda ero> (Photo, 955x480) https://irc.ubports.com/c2BVu19E.png http://t.cn/EKF5eXJ
May 22 14:04:18 <ubptgbot> Jade was added by: Jade
May 22 14:04:25 <ubptgbot> <Jade> (Photo, 1043x522) https://irc.ubports.com/n00hwB0S.png hi
May 22 14:04:26 <ubptgbot> <Jade> (Photo, 1043x522) https://irc.ubports.com/J0bmD8yq.png http://t.cn/EKFt80p
May 22 14:16:37 <PureTryOut[IRC]> Huh, for some reason I just can't join this channel via Matrix...
May 22 14:16:59 <Danct12> <PureTryOut[IRC] "Huh, for some reason I just can'"> #halium:matrix.org ?
May 22 14:17:14 <PureTryOut[IRC]> That alias isn't available anymore
May 22 14:17:46 <PureTryOut[IRC]> But now it is? Wtf lol
May 22 14:17:48 <PureTryOut[IRC]> Never mind then
May 22 14:17:59 <PureTryOut[m]> Anyways...
May 22 14:18:49 <PureTryOut[m]> I'm wondering if it is possible to port my Jolla Phone to Halium. There are no Android sources available (due to it running SailfishOS), but the kernel source are and the OS image does include libhybris.
May 22 14:19:58 <Herrie> PureTryOut[m]: Why would you want that, just wondering ;)
May 22 14:20:17 <ubptgbot> lwolcan was added by: lwolcan
May 22 14:20:37 <PureTryOut[m]> Because I don't want SailfishOS anymore, but it's the only usable phone I have atm lol
May 22 14:20:59 <PureTryOut[m]> The SoC isn't available in mainline either, and I don't know enough kernel stuff to port it myself
May 22 14:22:10 <PureTryOut[m]> Besides, I don't like electronic waste (which is why I work on postmarketOS in the first place), so getting it usable for more than just SailfishOS is of interest to me
May 22 14:23:26 <Herrie> PureTryOut[m]: OK clear ;)
May 22 14:24:03 <Herrie> You could run LuneOS with mainline, but you don't have a mainline kernel, so that doesn't work either... You could try to build some android repos for it... Though that might be hard too
May 22 14:24:30 <Herrie> THere might be similar devices in terms of specs though which do have CM/Lineage 12.1/14.1
May 22 14:24:37 <Herrie> That would be my best guess
May 22 14:25:00 <Herrie> You should be able to extract the vendor blobs, there should be some scripts for that on XDA if I remember correctly
May 22 14:25:10 <Herrie> So that makes 2 out of 3 required repos already ;)
May 22 14:28:55 <PureTryOut[m]> Hmm finding similar devices, that sounds logical
May 22 14:29:08 <Herrie> PureTryOut[m]: For vendor blob this might give some clues: https://github.com/anestisb/android-prepare-vendor
May 22 14:29:21 <PureTryOut[m]> Is CM/Lineage just required for the kernel sources or do I need something from the device package/repo as well?
May 22 14:30:13 <ubptgbot> lwolcan was added by: lwolcan
May 22 14:31:34 <Herrie> PureTryOut[m]: You need: Device, Kernel & Vendor as per example at: https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/xiaomi_mido.xml
May 22 14:31:55 <Herrie> Kernel you have, config should be more or less OK. Getting it to build & work seeing it's 3.4 kernel needs a few patches but do-able normally
May 22 14:32:47 <Herrie> I mean adaptations for defconfig are pretty straight forward
May 22 14:33:24 <Herrie> Getting it to work with newer systemd and glibc you need some patches to 3.4. We have them all here for Hammerhead for example: https://github.com/Halium/android_kernel_lge_hammerhead/commits/halium-5.1
May 22 14:33:32 <Herrie> Systemd 232+: https://github.com/Halium/android_kernel_lge_hammerhead/commit/17a8d0630b424d66981900e701ae2a452d4b8726
May 22 14:33:36 <PureTryOut[m]> Yeah we already have it building in postmarketOS so that should be fine
May 22 14:33:54 <Herrie> OK :)
May 22 14:34:06 <Herrie> We needed a few in LuneOS for 3.4 kernels & newer systemd
May 22 14:34:13 <Herrie> Lots of fixes for newer GCC mainly
May 22 14:34:32 <Herrie> We're stuck @ GCC 7.x for now, since GCC 8 requires quite a bit of work on 3,4 kernels
May 22 14:35:06 <Herrie> Not sure if you're on GCC8 already with 3.4 kernels in pmOS, because could borrow a few patches then maybe ;)
May 22 14:36:30 <PureTryOut[m]> I don't care much about systemd tbh lol
May 22 14:36:33 <ubptgbot> <minlexx> this is device-specific in pmOS... some devices compile old kernel with gcc6, others may even with gcc4 (4.9)
May 22 14:36:59 <PureTryOut[m]> Currently we build the kernel with GCC6, although I should at one point try to get it working with GCC8
May 22 14:38:21 <Herrie>  PureTryOut[m]: Well Halium does ;)
May 22 14:38:29 <Herrie> So does UBPorts & LuneOS in general ;)
May 22 14:38:46 <Herrie> Anyway it are only a few commits on 3.4 kernels that are needed
May 22 14:39:08 <PureTryOut[m]> <Herrie " PureTryOut: Well Halium does ;)"> Not really. It comes with some systemd service files but doesn't use systemd itself
May 22 14:39:31 <Herrie> https://github.com/Halium/android_kernel_lge_hammerhead/commit/5754614eb43dea44a99e54898e3b83d4d96d8b83, https://github.com/Halium/android_kernel_lge_hammerhead/commit/bd221854de33b75db7a7fa01cb34274b62a7cbf8 and https://github.com/Halium/android_kernel_lge_hammerhead/commit/17a8d0630b424d66981900e701ae2a452d4b8726
May 22 14:39:32 <PureTryOut[m]> Some people already had Halium working with postmarketOS, and there was no systemd involved 😉
May 22 14:39:40 <Herrie> OK ;)
May 22 14:40:08 <Herrie> Well in LuneOS we only use the minimal Android bits, not the rest from Halium ;)
May 22 14:40:08 <PureTryOut[m]> Tbh I'd still add support for it, even just to help others who might be interested in this 😉
May 22 14:40:12 <Herrie> But we share the kernel etc
May 22 14:40:24 <Herrie> Saves us hassle in maintaining it etc ;)
May 22 14:40:35 <Herrie> Just upstreamed everything incl. the GCC patches we were maintaining previously ;)
May 22 14:41:36 <PureTryOut[m]> Mainlining devices is the best approach, although a lot of work
May 22 14:43:26 <Herrie> PureTryOut[m]: Agree, but a lot of work
May 22 14:44:54 <PureTryOut[m]> Well, let's start searching for some other device with about the same hardware then
May 22 14:50:49 <PureTryOut[m]> I have found a device package of a device with the same SoC, is that enough?
May 22 14:52:35 <Herrie> MIght be a good start
May 22 14:52:43 <Herrie> There's probably more required. Does this one have the MSM8930AA ?
May 22 14:53:01 <Herrie> https://www.gsmarena.com/jolla_jolla-5457.php lists it as dualcore Snapdragen 400 @ 1,4Ghz
May 22 14:53:13 <Herrie> https://en.wikipedia.org/wiki/List_of_Qualcomm_Snapdragon_systems-on-chip#Snapdragon_400_(2013) says it should be a MSM8930AA then
May 22 14:53:47 <PureTryOut[m]> Ah good call, the one I found isn't no
May 22 14:54:24 <PureTryOut[m]> I found a MSM8930AB
May 22 14:55:19 <PureTryOut[m]> Ah found one https://github.com/CyanogenMod/android_device_htc_zara
May 22 14:55:27 <PureTryOut[m]> "Chipset 	Qualcomm MSM8930AA Snapdragon 400"
May 22 14:58:43 <PureTryOut[m]> That's Android 4.2.2 though, the Halium docs mention Android 5.1 minimum
May 22 15:03:12 <Herrie> I'm not sure it's using the MSM8930AA though
May 22 15:05:44 <Herrie> The Jolla I mean
May 22 15:07:38 <ubptgbot> <degen> @NotKit [but I would say it is not worth it, too many effort for obscure hardware], all the kernel modules are marked as `intree: Y` when running `modinfo`, does that mean I can just run a mainline kernel from Sunxi with the PowerVR userspace libraries?
May 22 15:11:07 <Herrie> PureTryOut[m]: Jolla Phone = sbj right? This is also a kernel repo for it with latest patch it seems: https://github.com/KonstaT/sailfishos_kernel_jolla_msm8930
May 22 15:11:19 <Herrie> So I guess it doesn't really matter too much which MSM8930 is in there
May 22 15:11:40 <PureTryOut[m]> It is yes
May 22 15:12:06 <PureTryOut[m]> I already had the kernel source, am just looking for device sources from a similar device
May 22 15:12:37 <ubptgbot> Albert was added by: Albert
May 22 15:17:20 <Herrie> PureTryOut[m]: Seems Sony Taoshan (https://github.com/LineageOS/android_device_sony_taoshan/blob/7d67051b566bccec49e16b4f8825d7e32752a025/lineage.dependencies#L11) and Samsung Serrano (S4) https://github.com/LineageOS/android_device_samsung_serrano3gxx/tree/cm-14.1 are candidates
May 22 15:48:20 <ubptgbot> <rogieroudshoorn> My serranodsdd build boots if that helps
May 22 15:56:09 <ubptgbot> <NotKit> PureTryOut, for sbj, logical step would be to skip building Halium completely and just use prebuilts from SailfishOS
May 22 15:56:36 <ubptgbot> <NotKit> with right scripts, you should be able to start droid-hal-init in the same root as Sailfish does, but probably not in LXC container
May 22 16:02:50 <ubptgbot> Noreen was added by: Noreen
May 22 16:29:48 <ubptgbot> forza4gal was added by: forza4gal
May 22 17:23:23 <ubptgbot> <Marcos> Voy
May 22 17:24:39 <ubptgbot> <Marcos> Wron group! Sorry!
May 22 17:28:19 <ubptgbot> <aurnytoraink> 😅
May 22 17:50:36 <ubptgbot> Alice Kay was added by: Alice Kay
May 22 17:50:39 <ubptgbot> <Alice Kay> (Photo, 1085x557) https://irc.ubports.com/lt9E0Wp4.png hi
May 22 17:50:39 <ubptgbot> <Alice Kay> (Photo, 1085x557) https://irc.ubports.com/mtJYtz9q.png http://t.cn/EKFVyaC
May 22 18:35:47 <sephger> hi :)
May 22 18:38:02 <sephger> I am trying to build Halium for my old Xperia Z3 and I am stuck at the systemimage. Ninja throws an error that "com.qualcomm.location.apk" is missing and there is no known rule to make it. I have tried googling it but I am stuck :/
May 22 18:38:29 <Danct12> remove all apk references
May 22 18:38:39 <Danct12> you dont compile apks to halium
May 22 18:39:09 <sephger> In which file do I find the references?
May 22 18:39:48 <sephger> Sorry if this is common knowledge, I am just starting with this :/
May 22 18:41:32 <Danct12> i would recommend you "grep -r com.qualcomm.location.apk in your device directory
May 22 18:44:48 <sephger> ah I got it :) it was in the device/sony/shinano-common/roprietary-files.txt
May 22 18:45:08 <sephger> thanks for the help :)
May 22 18:45:09 <Danct12> look for all ".apk" files in there and remove it
May 22 18:45:28 <sephger> it was only this one, i will search in other files as well
May 22 18:52:17 <sephger> I couldn't find more apk references but the build still fails with the same error
May 22 18:52:57 <ubptgbot> <UniversalSuperBox> You might need to clean and start over, sometimes the build system doesn't realize you changed things
May 22 18:53:04 <ubptgbot> <UniversalSuperBox> `make clean`
May 22 18:53:22 <ubptgbot> <UniversalSuperBox> And then `make whateveryouweremaking`
May 22 18:54:39 <sephger> still the same error :/
May 22 18:57:46 <sephger> oooh there seemed to be an error in the build/tools/diff_package_overlays.py
May 22 18:58:11 <sephger> nope
May 22 18:58:18 <sephger> still
May 22 19:21:32 <sephger> the problem seems to be the mkbootimg, this creates a file in out where the apk is referenced
May 22 22:55:37 <ubptgbot> <Flohack> @TuxThePenguin [Yeah so it seems to be trying something a few thousand times and getting an inva …], I got the solution today
May 22 22:55:43 <ubptgbot> <Flohack> Read my comment here: https://github.com/lxc/lxc/issues/2953#issuecomment-495003209
May 22 22:56:18 <ubptgbot> <Flohack> If I use cmdline I can write "0-3" into that file, but invalid argument comes with 0-4 or 0-7 as lxc tries to do. So its valid error from kernel
May 22 22:56:38 <ubptgbot> <Flohack> Its becaause I am locking down the max_cpus to 4
May 22 22:56:53 <ubptgbot> <Flohack> Which I need to do for the broken hardware of angler... doh
May 23 00:18:07 <ubptgbot> <TuxThePenguin> Huh weird, my device has 4 cores with no need for max_cpus so I'll check to see that all the cores are enabled when I get home
May 23 00:20:19 <ubptgbot> <TuxThePenguin> @Flohack [Which I need to do for the broken hardware of angler... doh], Huh weird, my device has 4 cores with no need for max_cpus so I'll check to see that all the cores are enabled when I get home
**** ENDING LOGGING AT Thu May 23 03:00:36 2019