**** BEGIN LOGGING AT Thu Jan 31 02:59:57 2019
Jan 31 06:18:13 <ubptgbot> <ilyaishere> @Daniel, Hey, that's better than what I have :)
Jan 31 06:18:28 <ubptgbot> <ilyaishere> I get a black rectangle
Jan 31 06:19:07 <ubptgbot> <ilyaishere> In your case that might be wrong IM specified in kwinwrapper
Jan 31 06:20:34 <ubptgbot> <JBBgameich> @Daniel, Btw, there is a mobile settings app as well which I unfortunately forgot to include in the image earlier. The package name is plasma-settings
Jan 31 11:36:47 <ubptgbot> <cesium55> bye everyone
Jan 31 11:36:49 <ubptgbot> <cesium55> (Sticker, 496x512) https://irc.ubports.com/kkGlnYSN.webp
Jan 31 11:36:50 <ubptgbot> <cesium55> (Sticker, 456x512) https://irc.ubports.com/cAZ0rWeo.webp
Jan 31 11:36:52 <ubptgbot> <cesium55> (Sticker, 512x341) https://irc.ubports.com/uYkcm9PX.webp
**** BEGIN LOGGING AT Thu Jan 31 12:35:07 2019
Jan 31 13:28:47 <ubptgbot> <ankaos> j5lte not fixed error :(
Jan 31 13:36:06 <ubptgbot> <Tygerpro Tygerpro> What's the error
Jan 31 13:40:20 <ubptgbot> <ankaos> screen not open
Jan 31 13:41:13 <ubptgbot> <ankaos> lxc-android running
Jan 31 13:54:29 <ubptgbot> <Tygerpro Tygerpro> Ok, hybris-boot or halium-boot which rootfs and what is exact error?
Jan 31 14:10:59 <ubptgbot> <ankaos> hybris-recovery and pm-caf
Jan 31 14:37:29 <ubptgbot> <Tygerpro Tygerpro> Did you add use rules?
Jan 31 14:37:34 <ubptgbot> <Tygerpro Tygerpro> Udev*
Jan 31 14:41:11 <ubptgbot> <ankaos> yes
Jan 31 15:50:10 <ubptgbot> <Tygerpro Tygerpro> What happens if you use hybris-boot instead of hybris-recovery?
Jan 31 20:19:03 <ubptgbot> <archi_dagac> h
Jan 31 20:19:14 <ubptgbot> <archi_dagac> @Flohack, Hi
Jan 31 20:19:21 <ubptgbot> <archi_dagac> what about i9300?
Jan 31 20:21:06 <ubptgbot> <archi_dagac> I heard 3.1x kernel is in use
Jan 31 20:32:12 <ubptgbot> <Flohack> @archi_dagac, If you find me a lineageos port for S3 which has kernel 3.1 then I take a look
Jan 31 20:32:24 <ubptgbot> <Flohack> S3 is on 3.0 afaik
Jan 31 20:32:58 <ubptgbot> <archi_dagac> my friend went to town, no internet. I will ask to him
Jan 31 20:33:37 <ubptgbot> <Flohack> oki
Jan 31 20:33:42 <ubptgbot> <archi_dagac> I watched your s3 neo port. :) very good
Jan 31 20:34:35 <ubptgbot> <Daniel> @JBBgameich, Thanks, I'll check it out...
Jan 31 20:35:11 <ubptgbot> <VeryOriginalUsername> @Flohack, wasn't there a 3.4 or 3.10 for S3 based on the tizen reference device that used same hardware?
Jan 31 20:36:57 <ubptgbot> <VeryOriginalUsername> also if d2 is codename for S3 then here it is https://github.com/LineageOS/android_kernel_samsung_d2/blob/cm-14.1/Makefile
Jan 31 20:37:03 <ubptgbot> <Flohack> @VeryOriginalUsername, Well it also needs to fit the device and vendor repo. If you find a triple <kernel, device, vendor> that works for Android, it will hopefully also work for UT. Simply upgrading the kernel to some version of an Android might not work
Jan 31 20:37:24 <ubptgbot> <Flohack> @VeryOriginalUsername, codename is i9300 😅
Jan 31 20:37:49 <ubptgbot> <VeryOriginalUsername> interesting, d2-common page says it's a codename for qcom variant of s3 https://github.com/LineageOS/android_device_samsung_d2-common
Jan 31 20:37:57 <ubptgbot> <VeryOriginalUsername> oh wait, qcom variants were for USA.....
Jan 31 21:00:38 <ubptgbot> Dariolol was added by: Dariolol
Jan 31 21:00:58 <ubptgbot> <Dariolol> hi guyz
Jan 31 21:07:39 <ubptgbot> <c_smith> @VeryOriginalUsername, And past three quite locked down
Jan 31 21:07:51 <ubptgbot> <c_smith> @VeryOriginalUsername, [Edit] And past the s3 quite locked down
Jan 31 21:26:47 <ubptgbot> <Daniel> I am having a problem with the halium setup  script. … In lines 104-122 DEVICE is exportet to setup-makefiles.sh, but then the scripts changes the directory to DEVICE_COMMON_TREE which causes the setup-makefiles.sh to write the COMMON files to the DEVICE specific vendor directory, which in turn causes the system image ro fail buidlin
Jan 31 21:26:48 <ubptgbot> g, because these files are not there (but instead in the DEVICE_COMMON_TREE). … Am I the only one affected (Asus Z00A CM repo)?
Jan 31 22:08:49 <ubptgbot> <NotKit> I suppose so, since we don't have that many devices with common trees
Jan 31 22:33:25 <ubptgbot> <Tygerpro Tygerpro> My device has a common tree as well as the device one, I just copy the manifest into .repo/local_manifests when I start from scratch
Jan 31 22:34:46 <ubptgbot> <aurnytoraink> (Document) https://irc.ubports.com/p18Fonv7.xml
Jan 31 22:34:49 <ubptgbot> <JBBgameich> @Daniel, Can you open an issue on the halium-devices repository so the person who wrote this code can fix it?
Jan 31 22:43:37 <ubptgbot> <Daniel> @Tygerpro Tygerpro, Yes, that's what I did, too. I can confirm that works. However I am currently preparing to upstream my work, so I would like to build it properly, without the need to patch the setup script.
Jan 31 22:44:07 <ubptgbot> <Daniel> @JBBgameich, Sure, I'll do that this weekend...
Jan 31 22:45:37 <ubptgbot> <Tygerpro Tygerpro> @Daniel, I know alot of the common repos like selinux and qcom-common got added to the halium repo so try removing those
Jan 31 22:46:30 <ubptgbot> <Tygerpro Tygerpro> Keep the ones that have your actual device in them (such as lge)
**** ENDING LOGGING AT Fri Feb 01 02:59:56 2019