**** BEGIN LOGGING AT Sun Jan 17 02:59:57 2021
Jan 17 03:40:03 <ubptgbot> michaelsiu was added by: michaelsiu
Jan 17 04:47:45 <ubptgbot> Harz4u was added by: Harz4u
Jan 17 04:48:30 <ubptgbot> <Harz4u> (Photo, 716x772) https://irc.ubports.com/fpdPf9Gw.png 2021-01-17 10:17
Jan 17 04:48:37 <ubptgbot> <Harz4u> Is my mobile supported
Jan 17 04:48:52 <ubptgbot> <Harz4u> Please advice
Jan 17 04:50:17 <ubptgbot> <Harz4u> My mobile is LG Stylus 3. It's not found in the device area of Ubuntu touch... So I wish to port my device...
Jan 17 04:50:34 <ubptgbot> <Harz4u> Could you help
Jan 17 05:26:56 <mighty17[m]> If it's not supported you can port it
Jan 17 05:27:04 <mighty17[m]> You already have 3.18 kernel
Jan 17 05:31:19 <ubptgbot> <dopamine404> @golliath51 [repo init -u https://github.com/Halium/android -b halium-9.0 --depth=1 …   File "/ …], you should maybe try your luck with a virtualenv
Jan 17 05:31:19 <ubptgbot> <dopamine404> using python3
Jan 17 05:31:39 <ubptgbot> <dopamine404> or install repo locally using your os's package manager
Jan 17 06:02:48 <ubptgbot> <Fuseteam> i think its yes you can port it, the docs are at docs.halium.org
Jan 17 06:09:59 <ubptgbot> <zxce3> Is it possible for android 6 like Samsung galaxy J2 prime to install ubport
Jan 17 06:10:07 <ubptgbot> <zxce3> [Edit] Is it possible for android 6 like Samsung galaxy J2 prime to install ubport?
Jan 17 06:11:30 <mighty17[m]> u have android 5 then?
Jan 17 06:12:59 <ubptgbot> <zxce3> @mighty17[m] [u have android 5 then?], I have a Samsung galaxy J2 prime android version 6
Jan 17 06:25:57 <mighty17[m]> <ubptgbot "<zxce3> @mighty17[m] [u have and">
Jan 17 06:26:40 <mighty17[m]> Dude you have android 7 https://forum.xda-developers.com/t/rom-g532x-7-1-2-alpha-lineageos-14-1-for-galaxy-j2-prime.3946388/
Jan 17 06:26:59 <mighty17[m]> Correct me if I'm wrong
Jan 17 08:23:17 <ubptgbot> <Harz4u> @mighty17[m] [If it's not supported you can port it], How to port
Jan 17 08:24:12 <mighty17[m]> Harz4u - https://docs.halium.org/en/latest/porting/first-steps.html
Jan 17 08:24:31 <ubptgbot> <Harz4u> When I searched on the lineage os github repository, u could not find repository for my device
Jan 17 08:24:36 <mighty17[m]> <mighty17[m] "Dude you have android 7 https://"> but u need to confirm if this is correct rom or find one yourself
Jan 17 08:25:00 <ubptgbot> <Harz4u> How do I check that
Jan 17 08:25:14 <mighty17[m]> whats your device's codename
Jan 17 08:25:45 <ubptgbot> <Harz4u> M400dk
Jan 17 08:25:52 <ubptgbot> <Harz4u> Lg
Jan 17 08:25:54 <mighty17[m]> okay lemme search
Jan 17 08:27:29 <mighty17[m]> stylo 3 or stylo 3 plus?
Jan 17 08:27:45 <ubptgbot> <Harz4u> Stylus 3
Jan 17 08:28:54 <mighty17[m]> stylo? or stylus?
Jan 17 08:29:09 <ubptgbot> <Harz4u> stylus
Jan 17 08:29:17 <mighty17[m]> huh weird
Jan 17 08:29:20 <mighty17[m]> i cant find any
Jan 17 08:29:32 <ubptgbot> <Harz4u> I think styo is also correct
Jan 17 08:29:47 <mighty17[m]> welp i cant find any roms :(
Jan 17 08:30:18 <ubptgbot> <Harz4u> What to do then??
Jan 17 08:30:30 <mighty17[m]> i dont know
Jan 17 08:30:52 <ubptgbot> <Harz4u> Ok... So there is no option... Thanks
Jan 17 08:41:44 <nergzd723> <mighty17[m] "Well what am I supposed to do"> You need to shrink halium-boot, perhaps try stronger compression, but you'd need kernel support for it
Jan 17 08:48:08 <mighty17[m]> <nergzd723 "You need to shrink halium-boot, "> 3.4 support I don't think it's possible
Jan 17 09:53:24 <nergzd723> CONFIG_RD_XZ must be supported
Jan 17 10:08:53 <mighty17[m]> kk
Jan 17 10:16:08 <nergzd723> but you'd need to repack halium-boot ramdisk as lzma-compressed
Jan 17 10:20:10 <mighty17[m]> <nergzd723 "CONFIG_RD_XZ must be supported"> Ree still 9.2mb
Jan 17 10:20:19 <mighty17[m]> And then mka halium-boot
Jan 17 11:04:56 <nergzd723> you'd need to change halium-boot initramfs
Jan 17 11:05:05 <nergzd723> I don't know where does it look for it though
Jan 17 11:06:01 <mighty17[m]> 😧
Jan 17 13:46:19 <mighty17[m]> <nergzd723 "I don't know where does it look "> anyone else here knows?
Jan 17 14:05:54 <ubptgbot> <Max> i need help. has anyone the halium image for s6? would been nice if someone could send it. Thanks.
Jan 17 14:54:07 <ubptgbot> Sundev79 was added by: Sundev79
Jan 17 14:54:53 <ubptgbot> <golliath51> @Fuseteam [3.6 has the same error as 2.7?], yes
Jan 17 15:08:20 <ubptgbot> <golliath51> @dopamine404 [you should maybe try your luck with a virtualenv], allways the same error
Jan 17 15:09:40 <ubptgbot> <golliath51> I follow the docs.halium.org and I don't understand why I have this error at the second command
Jan 17 15:11:03 <ubptgbot> <golliath51> I am not the only to have this problem
Jan 17 15:11:55 <pandu> Which devices you guys are working on??
Jan 17 15:12:43 <ubptgbot> <golliath51> File "/home/david/halium/.repo/repo/main.py", line 79 …     file=sys.stderr)
Jan 17 15:13:17 <ubptgbot> <golliath51> when I deleted file= into the file, there is not problem
Jan 17 15:14:14 <ubptgbot> <golliath51> the script is wrong or i missing a package to works
Jan 17 15:18:08 <mighty17[m]> Reee how do I decrease size of halium boot
Jan 17 17:31:18 <ubptgbot> <dopamine404> does anyone have any idea how to fix kernel build  errors concerning the gid_t -> kgid_t and uid_t kuid_t
Jan 17 17:31:22 <ubptgbot> <dopamine404> my kernel is 3.10
Jan 17 17:42:01 <ubptgbot> <hassanh92> @dopamine404 [does anyone have any idea how to fix kernel build  errors concerning the gid_t - …], Check here the common errors while building halium.  … https://docs.halium.org/en/latest/porting/build-sources.html#documented-errors
Jan 17 17:56:30 <ubptgbot> <dopamine404> @hassanh92 [Check here the common errors while building halium.  … https://docs.halium.org/en/ …], don't think that'll help 😅
Jan 17 18:32:43 <ubptgbot> <dopamine404> @hassanh92 [Check here the common errors while building halium.  … https://docs.halium.org/en/ …], oh wait that will help.
Jan 17 18:32:48 <ubptgbot> <dopamine404> thank you mate :D
Jan 17 18:35:11 <ubptgbot> <hassanh92> (Sticker, 512x512) https://irc.ubports.com/7TQtxNFJ.webp
Jan 17 20:35:15 <ubptgbot> <dopamine404> so my halium boot image gets stuck on boot without any way to communicate with it
Jan 17 20:35:21 <ubptgbot> <dopamine404> and it doesn't reboot either
Jan 17 20:35:38 <ubptgbot> <dopamine404> does anybody know a way for me to diagnose this?
Jan 17 20:41:03 <ubptgbot> <dopamine404> -or even better how to fix it-
Jan 17 20:41:42 <ubptgbot> <NotKit> @dopamine404 [so my halium boot image gets stuck on boot without any way to communicate with i …], did you get telnet before?
Jan 17 20:41:56 <ubptgbot> <NotKit> you can try flashing only halium-boot without rootfs installed
Jan 17 20:41:57 <ubptgbot> <dopamine404> nope
Jan 17 20:42:05 <ubptgbot> <dopamine404> yep tried that
Jan 17 20:42:11 <ubptgbot> <dopamine404> so I could get a telnet connection
Jan 17 20:42:21 <ubptgbot> <dopamine404> but it doesn't start either
Jan 17 20:42:30 <ubptgbot> <NotKit> hm, revert to stock kernel config and enable only CONFIG_DEVTMPFS, then see if you can get telnet
Jan 17 20:42:47 <ubptgbot> <dopamine404> without any UT modifications?
Jan 17 20:42:51 <ubptgbot> <NotKit> yes
Jan 17 20:42:57 <ubptgbot> <dopamine404> alright
Jan 17 20:42:59 <ubptgbot> <dopamine404> will try
Jan 17 20:43:26 <ubptgbot> <NotKit> what is the device/SoC?
Jan 17 20:43:30 <ubptgbot> <dopamine404> why do you think this might be happening :D
Jan 17 20:43:45 <ubptgbot> <dopamine404> @NotKit [what is the device/SoC?], J5 2016 j5xnlte msm8916
Jan 17 20:44:06 <ubptgbot> <NotKit> hm, so not something too special
Jan 17 20:44:14 <ubptgbot> <dopamine404> yup
Jan 17 20:44:35 <ubptgbot> <dopamine404> actually nergzd723 from irc provided me with his own halium boot image for the j5 2015
Jan 17 20:44:51 <ubptgbot> <dopamine404> and I could boot into the rootfs using that
Jan 17 20:44:57 <ubptgbot> <dopamine404> and ssh into it
Jan 17 20:45:07 <ubptgbot> <dopamine404> but mine seems to be just stuck
Jan 17 20:56:11 <ubptgbot> <dopamine404> @NotKit [hm, revert to stock kernel config and enable only CONFIG_DEVTMPFS, then see if y …], and yes I have telnet now
Jan 17 20:57:32 <ubptgbot> <NotKit> @NotKit [CONFIG_DEVTMPFS=y … CONFIG_VT=y … CONFIG_NAMESPACES=y … CONFIG_MEMCG=y … CONFIG_CGROUP_D …], check if you can enable those without kernel breaking, it should allow to boot to rootfs at least
Jan 17 20:58:55 <ubptgbot> <dopamine404> let me try
Jan 17 21:05:01 <ubptgbot> <dopamine404> oh shit that did something.
Jan 17 21:05:17 <ubptgbot> <dopamine404> [Edit] oh that did something.
Jan 17 21:07:07 <ubptgbot> <dopamine404> @NotKit [check if you can enable those without kernel breaking, it should allow to boot t …], the screen looks corrupted but I still get a telnet connection
Jan 17 21:07:30 <ubptgbot> Biju Boomtown was added by: Biju Boomtown
Jan 17 21:09:00 <ubptgbot> <Biju Boomtown> All other devices have to be adapted by their owners. The support group for this process is this one.
Jan 17 21:30:51 <ubptgbot> <ankaos> Hı
Jan 17 21:32:37 <ubptgbot> <ankaos> How find input keys output?
Jan 17 21:32:59 <ubptgbot> <ankaos> Power and volume keys?
Jan 17 22:15:33 <ubptgbot> Austrini was added by: Austrini
**** ENDING LOGGING AT Mon Jan 18 02:59:57 2021