**** BEGIN LOGGING AT Thu Mar 01 03:00:00 2018
Mar 01 04:34:03 <ubptgbot> <KunalBhat> Hey guys
Mar 01 04:34:34 <ubptgbot> <KunalBhat> I managed to connect to telnet
Mar 01 04:34:36 <ubptgbot> <KunalBhat> https://hastebin.com/ubulapanab.xml
Mar 01 04:34:38 <ubptgbot> <KunalBhat> Here is the log
Mar 01 04:34:46 <ubptgbot> <KunalBhat> dmesg
Mar 01 04:35:17 <ubptgbot> <KunalBhat> There seems to be an error with the data partition ... but Im not so sure. can someone check ?
**** ENDING LOGGING AT Thu Mar 01 04:44:32 2018

**** BEGIN LOGGING AT Thu Mar 01 04:46:58 2018
**** ENDING LOGGING AT Thu Mar 01 04:54:46 2018

**** BEGIN LOGGING AT Thu Mar 01 04:56:06 2018
**** ENDING LOGGING AT Thu Mar 01 05:02:41 2018

**** BEGIN LOGGING AT Thu Mar 01 05:05:55 2018
Mar 01 05:21:56 <bshah> crito: java_library.mk is missing in the sense it is removed from build
Mar 01 05:37:39 <ubptgbot> <JBBgameich> @Qiangong2, You need to regenerate the vendor tree, Just run halium/devices/setup device again
Mar 01 05:42:09 <ubptgbot> <KunalBhat> Has anyone seen my dmesg yet ?
Mar 01 06:05:21 <ubptgbot> <bhushanshah> @KunalBhat, check /diagnosis.log file
Mar 01 06:48:27 <ubptgbot> <Flohack> @KunalBhat, At least it mounts correctly: <6>[    4.728422] EXT4-fs (loop0): mounted filesystem without journal. Opts: (null)
Mar 01 07:57:59 <crito> bshah: then the reference in build/core/config.mk should be removed as well. `BUILD_JAVA_LIBRARY`
Mar 01 09:13:05 <myltap[m]> Hello, when I try to boot in the halium reference rootfs, I have this error : https://privatebin.net/?9a762ffb89465567#BEhv+xglU43aVWPRAkPVpMrlgw07zp/tsAeIiH31EWA=
Mar 01 09:14:13 <myltap[m]> I can set BOARD_KERNEL_CMDLINE in BoardConfigCommon but I don't know which partition set, does someone can help me ?
Mar 01 10:26:07 <crito> should the bluetooth stack be part of halium?
Mar 01 10:27:38 <r0kk3rz> crito: how so?
Mar 01 10:29:21 <crito> I don't know. My thoughts was that halium provides drivers for HW while the custom rootfs will provide userspace tools. my point is that the halium manifest seems to miss system/bt repo to build qcom/bt. thats the reason why I'm asking
Mar 01 10:29:53 <r0kk3rz> we typically use the BT drivers in the linux kernel
Mar 01 10:30:12 <r0kk3rz> not the android ones
Mar 01 10:32:37 <crito> don't know what android hw drivers should be. I only know typically linux kernel drivers. but for my xperia xz1 compact I have to build hardware/qcom/bt which requires header files which are provided by system/bt. now the question is. do I have to build hardware/qcom/bt or not
Mar 01 10:36:05 <r0kk3rz> you might need to build it, even though it wont end up being used
Mar 01 10:36:16 <r0kk3rz> mostly just to keep the android build scripts happy
Mar 01 10:37:49 <crito> alright. then I have to add system/bt stuff to my device.xml to have the required header files. nevertheless I would expect that other BT hw requires this too therefore I'm confused why it's not in the halium manifest
Mar 01 10:38:16 <crito> thx r0kk3rz
Mar 01 10:38:34 <r0kk3rz> theres not always consistency in the world of android :)
Mar 01 10:40:03 <crito> unfortunatelly you are right. I already saw better linux distro packaging/building toolchains and much more consistent ones. but it looks like the world wants to deal with android ^^
Mar 01 12:20:30 <crito> next issue with sepolicies and healthd linking https://dpaste.de/48TG
Mar 01 15:32:25 <ubptgbot> <vanyasem> are you there @UniversalSuperBox
Mar 01 15:32:40 <ubptgbot> <vanyasem> do you have any notes regarding halium-boot? i want to test it
Mar 01 15:32:46 <ubptgbot> <vanyasem> (notes = docs)
Mar 01 15:36:40 <ubptgbot> <vanyasem> https://github.com/Halium/projectmanagement/issues/40 found it, nvm
Mar 01 16:48:40 <ubptgbot> <Walid> apparmor backport for kernel its very old, i think we must update it
Mar 01 16:59:21 <ubptgbot> <stefanomelchior> any idea how I could trouble shoot a halium-boot img when it boot-loops?
Mar 01 17:00:29 <ubptgbot> <stefanomelchior> dmesg on laptop side did not provide any info about it: what about on device side?
Mar 01 17:02:23 <ubptgbot> <stefanomelchior> hybris-boot + halium reference rootfs and hybris-boot+plasma mobile work well
Mar 01 17:03:06 <ubptgbot> <vanyasem> rild problems, disable radio in init rd
Mar 01 17:03:50 <ubptgbot> <stefanomelchior> ok, I'll try.
Mar 01 17:06:15 <ubptgbot> <stefanomelchior> on the other side I borrowed a working halium-boot from JBB (who has a similiar device) and when I flashed it on device altogether with ubport-xenial, it boots, but I can't connect either with telnet and ssh. Dmesg on laptop got no entry when device booted
Mar 01 17:06:31 <ubptgbot> <stefanomelchior> any suggestion how to trouble shoot that other issue?
Mar 01 17:07:23 <ubptgbot> <stefanomelchior> I used system.img from hybris-boot+halium reference rootfs porting
Mar 01 17:19:25 <crito> does anyone else has issues with sepolicy for halium 7.1? I cannot find anything regarding this issue
Mar 01 17:20:03 <ubptgbot> <vanyasem> everything related to selinux has to be disabled
Mar 01 17:20:07 <ubptgbot> <vanyasem> it's not supported
Mar 01 17:21:44 <crito> ok. then why halium is fetching system/sepolicy? and how do I disable it?
Mar 01 17:24:02 <ubptgbot> <vanyasem> comment out selinux mentions in makefiles and disable kernel flags related to it in the defconfig
Mar 01 17:42:34 <crito> ok. let's see if I catch all references
Mar 01 18:00:02 <crito> nothing in my device repo is referencing SElinux stuff but it looks like some cm/los/halium stuff do
Mar 01 18:56:39 <ubptgbot> <Ben Mayo> I'm trying to get ubports booted on my g5 plus. I used halium-boot and the JBBgameich halium-install script. I've also followed the steps in ProjectManagement issue 40, but I can't get lightdm to start and nothing in dmesg is calling out to me as the source of the problem. Any guidance? dmesg: https://paste.ubuntu.com/p/hW9ft94RgK/
Mar 01 19:05:42 <ubptgbot> <Tygerpro Tygerpro> @Ben Mayo, I'm having same issue, it took someone to read my dmeag to notice that my system.IMG was not mounting either correctly or at all, I haven't had a chance to look further
Mar 01 19:08:42 <ubptgbot> <Tygerpro Tygerpro> Looms like your roots.IMG isn't mounting based around the fails I'm seeing at the 2.000 mark
Mar 01 19:12:27 <ubptgbot> <Ben Mayo> Oh wow- didn't even see that. Definitely gives me a good point to work from.
Mar 01 19:27:45 <crito> I'm very unhappy with the state of this project. porting new devices is a mess. dependencies has to be built without needing them just because the toolchain wants it this way. documentation about the toolchain is split over many forum threads instead of using a wiki software. issues are tracked in threads instead of using issue tracker. sorry for that. it's not my intention to flame but there is a hugh
Mar 01 19:27:51 <crito> space for improvements.
Mar 01 19:35:44 <ubptgbot> <UniversalSuperBox> Well, if you want to fix any of those things it starts with you
Mar 01 19:36:03 <ubptgbot> <JBBgameich> As the Halium tree is based on LineageOS, some things might have remained in the tree although not needed. Of course you can make a PR to fix that. Also, the toolchain is an android toolchain, and so you might find information about it in android porting forums. We also have an issue tracker on github, I don't know of any forum t
Mar 01 19:36:03 <ubptgbot> hread about issues
Mar 01 19:39:44 <crito> I know it's based on lineage and I know it's not your fault. It's just like I said, I don't wanna flame. I'm trying to improve things but it's hard to get things done in this android world.
Mar 01 19:41:47 <ubptgbot> <UniversalSuperBox> If you want more documentation, we've got a repository for that. ;)
Mar 01 19:42:26 <ubptgbot> <JBBgameich> @crito, You are right, android is very messy, and that's something we can't really fix.
Mar 01 19:43:34 <r0kk3rz> figuring out how to unwind the spaghetti is usually more costly than just compiling the damn thing
Mar 01 19:44:11 <r0kk3rz> the whole libhybris thing is a fairly ugly means to and end anyway :)
Mar 01 19:46:02 <r0kk3rz> crito: the problem with trying to document everything comes down to the lack of consistency, it seems like no two devices are structured in the same way sometimes
Mar 01 19:46:34 <crito> yep and thats my problem. android is just a kind of embedded linux. and it is a mess to get things done. anyway like I said I want to improve things therefore first things first. pushing back docs, devices and other improvements make sense after it's working in a good manner
Mar 01 19:47:54 <r0kk3rz> im not sure id even consider it 'embedded linux' yes it uses the kernel but it doesnt really follow the kernels philosophy at all
Mar 01 19:48:14 <crito> r0kk3rz: as an embedded linux dev I know other projects where you just write down bootloader and kernel as board-support package. that's it
Mar 01 19:48:47 <r0kk3rz> yes because the kernel is the clean delineation point
Mar 01 19:48:54 <r0kk3rz> where as in android, it actually isnt
Mar 01 19:51:56 <crito> r0kk3rz: you might be right it's not following the linux kernel philosophy but nevertheless from an architectural point of view some OEM's did a big mess to mix up kernel-space and user-space
Mar 01 19:54:07 <crito> so what thanks for your input. at least it shows me that it's at least not only my thoughts.
Mar 01 19:54:27 <r0kk3rz> oh dont worry its a real pita for everyone :)
Mar 01 19:55:00 <r0kk3rz> but im not sure its a problem worth solving
Mar 01 19:58:27 <crito> I don't think that it is worth solving it but it has to be done. I wan't full control about my devices and ensure that quality is not only a word for advertisement
Mar 01 19:58:37 <crito> want*
Mar 01 20:05:24 <r0kk3rz> its only not worth solving because a year later a new android comes out that changes a whole bunch of stuff and then you're back at square one
Mar 01 20:07:44 <crito> yes I see. the only party that could change this is google otherwise you have to deal with a big gap between these projects
Mar 01 20:11:34 <r0kk3rz> yeah and if the whole treble thing is successful that might make things a lot easier
Mar 01 20:40:07 <ubptgbot> <Flohack> Its because the devs in the phone companies never really undestood what Linux is, what Unix is and how abstraction works. Maybe there are devs at Google who understood it at the beginning, but then all eof them were pushed to bring in new features, time to market cut short. What we are seeing today is the result of marketing campaig
Mar 01 20:40:07 <ubptgbot> ns, and to try to catch up with APple. I can only hope that Purism is successful with their hardware, we could then show how Linux can work on a mobile platform without the Anroid mess below
Mar 01 20:44:45 <crito> that would be nice when purism will be successful. but in the meantime I will follow up having a lot of fun with the android world or move over and try to contribute to purism
Mar 01 20:50:46 <ubptgbot> <Flohack> the thing is that to make a successful hardware product in mobile you need a lot of resources or a lot of experience. Both which they dont seem to have. Its one thing getting a laptop done, another doing embedded stuff
Mar 01 20:52:40 <crito> from my point of view the bigger issue is that the definition of a good product differs in mind of developers and consumers.
Mar 01 20:54:18 <crito> you could develop a technically really good phone and nobody will buy it because there too less apps or it is just a noname vendor. history tells me that not the best product wins but the most popular one
Mar 01 21:00:40 <r0kk3rz> yeah i really hope this imx8 thing works out, i really worry its just going to be too compromised to be that useful
Mar 01 22:34:52 <ubptgbot> <ilyaishere> BOARD_HARDWARE_CLASS isn't used by Halium, right? … https://github.com/CyanogenMod/android_frameworks_opt_hardware/blob/cm-14.1/README.mkdn
Mar 01 22:36:05 <ubptgbot> <stefanomelchior> Any suggestion how to fix the following issue on ubports-rootfs running halium-boot: `phablet@ubuntu-phablet:~$ sudo systemctl status NetworkManager.service … Failed to get properties: Failed to execute program org.freedesktop.systemd1: Permission denied … phablet@ubuntu-phablet:~$ sudo systemctl status lxc@android … Failed
Mar 01 22:36:05 <ubptgbot> to get properties: Failed to execute program org.freedesktop.systemd1: Permission denied`
Mar 01 22:36:36 <ubptgbot> <UniversalSuperBox> Ubuntu Touch doesn't use systemd
Mar 01 22:37:11 <ubptgbot> <UniversalSuperBox> As far as you're concerned for most services, just chop off the `systemctl` part of the command. The container service is `lxc-android-config`.
Mar 01 22:41:41 <ubptgbot> <stefanomelchior> how can I see if it is running or not?
Mar 01 22:41:59 <ubptgbot> <UniversalSuperBox> `sudo status lxc-android-config`
Mar 01 22:42:05 <ubptgbot> <UniversalSuperBox> The expected status is `stop/post-start`
Mar 01 22:42:43 <ubptgbot> <stefanomelchior> `lxc-android-config stop/waiting`
Mar 01 22:42:43 <ubptgbot> <Flohack> Or, use Flohacks guessing method, do ps aux and look for processes that look like they wont be on a normal Linux system 😆
Mar 01 22:42:52 <ubptgbot> <Flohack> 80% chance to be right
Mar 01 22:42:55 <ubptgbot> <UniversalSuperBox> your container is not running
Mar 01 22:43:16 <ubptgbot> <UniversalSuperBox> If you'd like to chat specifically about porting Ubuntu Touch, we're at @ubports_porting or #ubports-porting on freenode.
Mar 01 22:44:19 <ubptgbot> <stefanomelchior> oki, thnx
Mar 01 22:45:37 <ubptgbot> <stefanomelchior> I was not expected to be successful today, but it seems obvious that now it is more an ubports/UT related topic
Mar 02 01:46:30 <ubptgbot> <Qiangong2> When I run systemctl --failed, I get this: https://paste.ubuntu.com/p/46D3mf7x8z/
Mar 02 01:46:39 <ubptgbot> <Qiangong2> Does it matter that these two have failed?
Mar 02 01:54:00 <ubptgbot> <Qiangong2> Also, according to dmesg on the device, vold keeps restarting
Mar 02 02:09:20 <ubptgbot> <Qiangong2> Here is a log from the dmesg on the device: http://pastebin.xyz/p?q=a0ZEMGs
Mar 02 02:11:11 <ubptgbot> <UniversalSuperBox> why is that page so dark
Mar 02 02:12:34 <ubptgbot> <Qiangong2> not for me...
Mar 02 02:12:38 <ubptgbot> <Qiangong2> I can re upload it
Mar 02 02:12:56 <ubptgbot> <UniversalSuperBox> What device is this?
Mar 02 02:13:08 <ubptgbot> <Qiangong2> jfltetmo
Mar 02 02:13:12 <ubptgbot> <Qiangong2> https://paste.ubuntu.com/p/P6CD4vDs6F/
Mar 02 02:13:24 <ubptgbot> <Qiangong2> that's a repost of the previous one
Mar 02 02:13:24 <ubptgbot> <UniversalSuperBox> Can you mark that in your issue, #62?
Mar 02 02:13:59 <ubptgbot> <Qiangong2> Yeah, do you know why it's happening?
Mar 02 02:15:41 <ubptgbot> <UniversalSuperBox> Looks like things have been crashing quite a bit before that
Mar 02 02:17:35 <ubptgbot> <UniversalSuperBox> I'd guess that better logs would be in logcat for that service
Mar 02 02:18:21 <ubptgbot> <mariogrip> Try removing the context from the fstab file
Mar 02 02:18:23 <ubptgbot> <mariogrip> like: https://github.com/Halium/android_device_htc_pme/commit/4de59918ba8361111cac2c26ee593a6f80e1d346#diff-881cfbdebfa6c9606812f4e7f595a4d0
Mar 02 02:19:30 <ubptgbot> <Qiangong2> Okay, i'll try that, thanks
**** ENDING LOGGING AT Fri Mar 02 03:00:02 2018