**** BEGIN LOGGING AT Sun Nov 24 02:59:58 2019
Nov 24 03:01:19 <ubptgbot> <EmilSMN> My device is not in fixup-mountpoints
Nov 24 03:01:35 <ubptgbot> <vanyasem> @EmilSMN [My device is not in fixup-mountpoints], Then take your time and add it there
Nov 24 03:01:49 <ubptgbot> <vanyasem> Before building Halium
Nov 24 03:01:59 <ubptgbot> <vanyasem> Thank you
Nov 24 03:25:32 <ubptgbot> <EmilSMN> @vanyasem [Then take your time and add it there], Как узнать что там написать?
Nov 24 03:25:47 <ubptgbot> <vanyasem> This chat is English only
Nov 24 03:25:57 <ubptgbot> <vanyasem> Please at least use the translator
Nov 24 03:26:21 <ubptgbot> <EmilSMN> @vanyasem [Then take your time and add it there], How to find out what to write there?
Nov 24 03:26:33 <ubptgbot> <vanyasem> Read the appropriate section in the docs !
Nov 24 03:26:59 <ubptgbot> <vanyasem> If you have something specific you want to ask - go ahead
Nov 24 03:27:31 <ubptgbot> <IranFSilva> There's a small guide at the halium documentation page, basically you should take a look at the data of your device but there's a tool described at the halium docs.
Nov 24 03:28:55 <ubptgbot> <IranFSilva> [Edit] There's a small guide at the halium documentation page, basically you should take a look at the fstab file of your device, also there's a tool described at the halium docs that will turn the process easier.
Nov 24 03:31:26 <ubptgbot> <IranFSilva> http://docs.halium.org/en/latest/porting/build-sources.html#include-your-device-in-fixup-mountpoints
Nov 24 08:20:46 <ubptgbot> <EmilSMN> @IranFSilva [http://docs.halium.org/en/latest/porting/build-sources.html#include-your-device- …], It does not say what exactly to add to fixup-mountpoints. Rather it is said that, but it is not said where to get it.
Nov 24 09:05:36 <ubptgbot> <intel777> Check /boot and /data part declaration in your fstab.qcom
Nov 24 09:05:44 <ubptgbot> <intel777> [Edit] Check /boot and /data declaration in your fstab.qcom
Nov 24 09:06:57 <ubptgbot> <intel777> it can be found somwere in halium/device/[vendor]/[device]/
Nov 24 09:07:11 <ubptgbot> <intel777> mine was in "rootdir" directory
Nov 24 09:15:14 <ubptgbot> <vanyasem> @EmilSMN [It does not say what exactly to add to fixup-mountpoints. Rather it is said that …], It does say that
Nov 24 09:15:28 <ubptgbot> <vanyasem> “In your device’s fstab file”
Nov 24 09:15:42 <ubptgbot> <vanyasem> Please pay attention
Nov 24 09:44:30 <ubptgbot> <VeryOriginalUsername> @intel777 [it can be found somwere in halium/device/[vendor]/[device]/], Or you can just run `grep /boot`
Nov 24 09:44:41 <ubptgbot> <VeryOriginalUsername> @intel777 [it can be found somwere in halium/device/[vendor]/[device]/], [Edit] Or you can just run `grep -r /boot`
Nov 24 09:45:04 <ubptgbot> <intel777> it won't work if it isn't declared
Nov 24 09:45:21 <ubptgbot> <intel777> so beter  … ```find . -name fstab.qcom```
Nov 24 09:46:33 <ubptgbot> <VeryOriginalUsername> @intel777 [it won't work if it isn't declared], Hmm this is indeed true, but I haven't seen a device without a declared boot part in fstab, yet there are probably plenty
Nov 24 09:46:39 <ubptgbot> <VeryOriginalUsername> @intel777 [it won't work if it isn't declared], [Edit] Hmm this is indeed true, but I haven't seen a device without a declared boot part in fstab, yet there are probably plenty of those
Nov 24 09:48:36 <ubptgbot> <intel777> well, mine original fstab.qcom for some reason was without /boot declaration
Nov 24 09:48:52 <ubptgbot> <intel777> so must add it mysekf
Nov 24 09:48:55 <ubptgbot> <intel777> [Edit] so must add it myself
Nov 24 14:57:40 <ubptgbot> Alex Alcalá was added by: Alex Alcalá
Nov 24 15:22:00 <ubptgbot> <intel777> So, I finally fixed kernel
Nov 24 15:22:13 <ubptgbot> <intel777> But now  I facing another problem
Nov 24 15:22:19 <ubptgbot> <intel777> ```Kernel panic - not syncing: No working init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.```
Nov 24 15:22:40 <ubptgbot> <intel777> It seems that halium isn't injected itself in kernel?
Nov 24 15:23:00 <ubptgbot> <intel777> [Edit] It seems that halium hasn't injected itself in kernel?
Nov 24 15:35:06 <ubptgbot> <intel777> And the same with hybris-recovery
Nov 24 15:36:08 <ubptgbot> <intel777> https://pastebin.com/BRErDEEa … log
Nov 24 18:39:44 <ubptgbot> <Daniel> @NotKit I was able to get proper colors being display without glamor/dri when killing the following lines: … https://github.com/NotKit/libhybris/blob/x11/hybris/egl/platforms/x11/x11_window.cpp#L220 … and  … https://github.com/NotKit/libhybris/blob/x11/hybris/egl/platforms/x11/x11_window.cpp#L498
Nov 24 18:40:45 <ubptgbot> <Daniel> I was thinking about a condition like  … || ((wnb->format != m_format) && !(drihybris))
Nov 24 18:41:07 <ubptgbot> <Daniel> Do you want me to PR or is this too hacky?
Nov 24 20:26:27 <ubptgbot> <intel777> @intel777 [Kernel panic - not syncing: No working init found.  Try passing init= option to …], So, I unpacked kernel using Android Image Kitchen, and here is 'Hybris adaptation bootstrapping initramfs init script.' init script in ramdisk, so why kernel telling me that it's can't find it?
Nov 24 20:27:04 <ubptgbot> <intel777> or I must somehow pass init=init to kernel boot parameters?
Nov 24 20:27:15 <ubptgbot> <intel777> or init=./init?
Nov 24 20:56:00 <ubptgbot> ThaBlacMamba was added by: ThaBlacMamba
Nov 24 20:56:16 <ubptgbot> <ThaBlacMamba> have a question
Nov 24 20:56:39 <ubptgbot> <ThaBlacMamba> My phone can run lineageOS but we only have oreo device trees
Nov 24 20:57:29 <ubptgbot> <NotKit> @intel777 [So, I unpacked kernel using Android Image Kitchen, and here is 'Hybris adaptatio …], is it Android 8 device?
Nov 24 20:57:31 <ubptgbot> <ThaBlacMamba> Is there anyway to build halium on oreo?
Nov 24 20:58:15 <ubptgbot> <NotKit> @intel777 at least from your log, the problem is that it skips initramfs - skip_initramfs option in cmdline
Nov 24 20:58:33 <ubptgbot> <intel777> @NotKit [is it Android 8 device?], it's 8 kernel, as I can't find any 7.x.x
Nov 24 20:58:58 <ubptgbot> <intel777> @NotKit [@intel777 at least from your log, the problem is that it skips initramfs - skip_ …], thats true, there is skip_initramfs in boot options
Nov 24 20:59:01 <ubptgbot> <NotKit> have you tested that 8 kernel can boot LOS14 on your device?
Nov 24 20:59:03 <ubptgbot> <intel777> so I should remove it?
Nov 24 20:59:10 <ubptgbot> <intel777> @NotKit [have you tested that 8 kernel can boot LOS14 on your device?], it boots
Nov 24 20:59:43 <ubptgbot> <NotKit> https://github.com/sailfish-on-fxtecpro1/kernel-fxtec-pro1/commit/ba669c41a4340ea5728e36d7402c91af92995f2b - similar patch should solve that particular issue
Nov 24 21:03:10 <ubptgbot> <intel777> thanks, will try
Nov 24 21:15:37 <ubptgbot> <intel777> ```Mer Debug telnet on port 23 on rndis0 192.168.2.15 - also running udhcpd``` … Yah, it's works now
Nov 24 21:16:17 <ubptgbot> <intel777> Oh jesus crist 3 days of brainstorm on that sources
Nov 24 21:17:04 <ubptgbot> <intel777> android-verity at first, no init now
Nov 24 21:19:58 <ubptgbot> <Mattia990> @intel777 [Mer Debug telnet on port 23 on rndis0 192.168.2.15 - also running udhcpd … Yah, i …], Check the dmesg for understanding why you are in telnet and not in ssh
Nov 24 21:20:20 <ubptgbot> <intel777> im in telnet coz there is no /data/system.img and /data/initramfs.img I assume
Nov 24 21:20:37 <ubptgbot> <intel777> because I was tired restoring 17gb of data every time
Nov 24 21:21:00 <ubptgbot> <intel777> now I do everything that needs and will try boot
Nov 24 21:21:04 <ubptgbot> <intel777> [Edit] now I'll do everything that needs and will try boot
Nov 24 21:21:11 <ubptgbot> <intel777> [Edit] now I'll do everything that needs to be done and will try boot
Nov 24 21:22:20 <ubptgbot> <intel777> [Edit] im in telnet coz there is no /data/system.img and /data/rootfs.img I assume
Nov 24 21:33:44 <ubptgbot> <intel777> oh, well, I was wrong
Nov 24 21:41:24 <ubptgbot> <intel777> so I cat'ed diagnostics, it showed me some kernel parameters that I must change, I done it, rebuilding the kernel
Nov 24 21:41:41 <ubptgbot> <Mattia990> @intel777 [so I cat'ed diagnostics, it showed me some kernel parameters that I must change, …], Good
Nov 24 21:41:44 <ubptgbot> <intel777> There was a lot of —-[cut here] —- shit in dmesg
Nov 24 21:42:01 <ubptgbot> <intel777> Really like hundreds
Nov 24 21:42:09 <ubptgbot> <Mattia990> @intel777 [There was a lot of —-[cut here] —- shit in dmesg], Don't look at that, look at the errors and something else
Nov 24 21:42:34 <ubptgbot> <intel777> gocha, will do if it'll fail now
Nov 24 21:47:17 <ubptgbot> <intel777> While it compiling...  … Is it theoretically posible to port Halium on Project Treble?
Nov 24 21:47:40 <ubptgbot> <intel777> Imagine how much devices will be supported at once
Nov 24 21:48:50 <ubptgbot> <intel777> oh, halium based on 7.something, yeah, will be hard time to find kernel that supports both 7.x and treble
Nov 24 21:51:32 <ubptgbot> <intel777> ```  iSerial                 3 GNU/Linux Device on rndis0 10.15.19.82```
Nov 24 21:51:34 <ubptgbot> <intel777> is it?
Nov 24 21:51:45 <ubptgbot> <intel777> like booting?
Nov 24 21:51:52 <ubptgbot> <UniversalSuperBox> Yep, appears so
Nov 24 21:51:57 <ubptgbot> <intel777> O MY FUCKING GOD
Nov 24 21:52:04 <ubptgbot> <intel777> im sorry
Nov 24 21:52:05 <ubptgbot> <UniversalSuperBox> Good work :)
Nov 24 21:55:25 <ubptgbot> <intel777> Oh, so I got ssh, but it still on kernel logo, so I guess troubleshooting begins
Nov 24 21:56:59 <ubptgbot> <UniversalSuperBox> Yep, graphics time!
Nov 24 22:16:37 <ubptgbot> <ThaBlacMamba> Hey why not run Halium through chroot in a barebones android custom rom
Nov 24 22:18:13 <ubptgbot> <UniversalSuperBox> That's a very long and complex answer that I can't do justice to over a text chat or with my limited knowledge. Short story... give it a try and let us know how it works
Nov 24 22:24:08 <ubptgbot> <ThaBlacMamba> It just seems to me since android already has a linux base you should be able to just run ubuntu touch in a container like other linux distros
Nov 24 22:24:53 <ubptgbot> <UniversalSuperBox> Yes, Ubuntu for Android was exactly that. Canonical moved on from that approach about six years ago.
Nov 24 22:25:35 <ubptgbot> <ThaBlacMamba> Why?  This new approach is a pain in the ass and doesn't keep up with android updates
Nov 24 22:25:47 <ubptgbot> <ThaBlacMamba> making porting it difficult
Nov 24 22:26:25 <ubptgbot> <ThaBlacMamba> For example I have an oreo device tree and a lineageOS 15 ready to use
Nov 24 22:26:35 <ubptgbot> <UniversalSuperBox> But it created an operating system that shipped on five different mass-produced devices from two different vendors
Nov 24 22:26:48 <ubptgbot> <ThaBlacMamba> Newer devices have lineage16 and a pie devices
Nov 24 22:27:00 <ubptgbot> <UniversalSuperBox> Again, if you think you can do it, do it. Don't spend your time explaining it to me
Nov 24 22:28:00 <ubptgbot> drapatyi was added by: drapatyi
Nov 24 22:28:18 <ubptgbot> <ThaBlacMamba> a lot of people on xda-developers would like to port ubuntu touch but this sems to be the main barrier
Nov 24 22:28:21 <ubptgbot> <UniversalSuperBox> But if you're trying to tell us that you think what we're doing (that works, mostly) is wrong without evidence, I'm afraid you're barking up the wrong tree.
Nov 24 22:29:07 <ubptgbot> <UniversalSuperBox> If you can get Ubuntu Touch in a chroot on top of Android working just like you can with this approach and it's easier than Halium porting, please do so and let us know.
Nov 24 22:29:23 <ubptgbot> <UniversalSuperBox> Because we aren't blind to this being hard
Nov 24 22:35:00 <ubptgbot> <drapatyi> Hi guys, not sure this is a proper channel to reach for a help regarding running Ubuntu Touch + Halium Boot. But I found this contact in Halium-boot documentation: http://docs.halium.org/en/latest/porting/first-steps.html#support-channels . … So my story is kinda short. It's second day I'm trying to run Ubuntu Touch on my oneplus2. And I
Nov 24 22:35:00 <ubptgbot>  kinda stuck at the step of getting ssh access, https://docs.ubports.com/en/latest/porting/installing-16-04.html#get-ssh-access … But I'm able to connect via telnet to halium-boot image, looked through the dmesg but haven't found anything useful, and kinda desperate right now. Can someone please help me to find a way to find more logs/configs to un
Nov 24 22:35:00 <ubptgbot> derstand what went wrong during a boot? I will be very greateful, thanks
Nov 24 22:35:42 <ubptgbot> <drapatyi> [Edit] Hi guys, not sure this is a proper channel to reach for a help regarding running Ubuntu Touch + Halium Boot. But I found this contact in Halium-boot documentation: http://docs.halium.org/en/latest/porting/first-steps.html#support-channels . … So my story is kinda short. It's second day I'm trying to run Ubuntu Touch on my oneplus2
Nov 24 22:35:42 <ubptgbot> . And I kinda stuck at the step of getting ssh access, https://docs.ubports.com/en/latest/porting/installing-16-04.html#get-ssh-access … But I'm able to connect via telnet to my phone and see halium boot kernel, looked through the dmesg but haven't found anything useful, and kinda desperate right now. Can someone please help me to find a way to fin
Nov 24 22:35:42 <ubptgbot> d more logs/configs to understand what went wrong during a boot? I will be very greateful, thanks
Nov 24 22:36:38 <ubptgbot> <UniversalSuperBox> Maybe some of the information that you can get from https://docs.halium.org/en/latest/porting/debug-build/dmesg.html would be helpful?
Nov 24 22:37:12 <ubptgbot> <drapatyi> :) Thanks @dal Already tried that
Nov 24 22:37:17 <ubptgbot> <intel777> @drapatyi [Hi guys, not sure this is a proper channel to reach for a help regarding running …], cat /diagnostics.log
Nov 24 22:37:19 <ubptgbot> <drapatyi> [Edit] :) Thanks @UniversalSuperBox  Already tried that
Nov 24 22:37:21 <ubptgbot> <intel777> try it
Nov 24 22:37:32 <ubptgbot> <drapatyi> no file /diagnostics.log
Nov 24 22:37:32 <ubptgbot> <UniversalSuperBox> @intel777 [cat /diagnostics.log], It's not hybris-boot, it will not have diagnostics.log
Nov 24 22:37:33 <ubptgbot> <intel777> helped me
Nov 24 22:37:40 <ubptgbot> <intel777> oh
Nov 24 22:38:02 <ubptgbot> <drapatyi> @UniversalSuperBox [It's not hybris-boot, it will not have diagnostics.log], correct
Nov 24 22:38:21 <ubptgbot> <UniversalSuperBox> @drapatyi [:) Thanks @UniversalSuperBox  Already tried that], Could we see the logs generated by an unsucessful boot?
Nov 24 22:38:31 <ubptgbot> <UniversalSuperBox> paste.ubuntu.com
Nov 24 22:38:55 <ubptgbot> <drapatyi> is dmesg will be enough?
Nov 24 22:39:01 <ubptgbot> <UniversalSuperBox> It's a good start
Nov 24 22:39:11 <ubptgbot> <drapatyi> 5 secs
Nov 24 22:40:35 <ubptgbot> <drapatyi> dmesg: https://paste.ubuntu.com/p/RyXzPCm9YQ/
Nov 24 22:41:07 <ubptgbot> <UniversalSuperBox> Sorry, we need it from the previous boot that didn't worrk correctly
Nov 24 22:41:11 <ubptgbot> <drapatyi> I'll also try to get kernel logs using pstore/ramoops
Nov 24 22:42:39 <ubptgbot> <drapatyi> hm.. this is booted but there's no ssh, so I assume halium didn't start ubuntu touch' kernel
Nov 24 22:46:44 <ubptgbot> <drapatyi> I can't find also pstore/ramoops logs so I assume it's because there was no actually kernel panic.. For some reasone it just looks like it didn't start rootfs.img or something like this
Nov 24 22:47:28 <ubptgbot> <drapatyi> maybe that's because of: `[    4.179672] cat: write error: Invalid argument` ?
Nov 24 22:48:01 <ubptgbot> <UniversalSuperBox> Do you have the folder `/data/system-data`?
Nov 24 22:48:05 <ubptgbot> <UniversalSuperBox> As seen from Recovery
Nov 24 22:49:00 <ubptgbot> <drapatyi> no, there's /data folder at all and I see lot's of failed mounts in dmesg
Nov 24 22:49:08 <ubptgbot> <drapatyi> [Edit] no, there's /data folder at all and I see lots of failed mounts in dmesg
Nov 24 22:49:16 <ubptgbot> <drapatyi> [Edit] no, there's /data folder at all and I see lots of failed mount commands in dmesg
Nov 24 22:49:41 <ubptgbot> <UniversalSuperBox> Right, you need to boot into TWRP
Nov 24 22:50:30 <ubptgbot> <UniversalSuperBox> Oh, I see. Silly me.
Nov 24 22:50:38 <ubptgbot> <UniversalSuperBox> `run-init: opening console: No such file or directory`
Nov 24 22:50:52 <ubptgbot> <drapatyi> oh... BTW in halium linux image I can jkust `mount /dev/mmcblk0p42 /mnt`
Nov 24 22:50:55 <ubptgbot> <drapatyi> [Edit] oh... BTW in halium linux image I can just `mount /dev/mmcblk0p42 /mnt`
Nov 24 22:51:07 <ubptgbot> <drapatyi> so I suppose there's some script that also adds some mount options to this mount
Nov 24 22:51:25 <ubptgbot> <UniversalSuperBox> Find the `console=` argument in your kernel cmdline and remove it. It'll probably be in a BOARD_KERNEL_CMDLINE variable in your device folder.
Nov 24 22:51:26 <ubptgbot> <drapatyi> and that's why there are lots of `mount ...` related errors
Nov 24 22:51:47 <ubptgbot> <drapatyi> @UniversalSuperBox [Find the console= argument in your kernel cmdline and remove it. It'll probably …], I assume that's in sources?
Nov 24 22:52:32 <ubptgbot> <UniversalSuperBox> Yes. However you're also having trouble like "`initrd: This rootfs does not have any writable-paths defined`" which should definitely not happen with an Ubuntu Touch image.
Nov 24 22:54:14 <ubptgbot> <drapatyi> hm... I used image that Vince1171 mentioned about here in porting guide: https://github.com/Vince1171/OnePlus2-Halium-Prebuild . … But I actually found that it uses latest built on jenkins. And looks like there are different types of Ubuntu Touch not sure which one to actually choose, since this phone is ARM64
Nov 24 22:54:38 <ubptgbot> <drapatyi> [Edit] hm... I used image that Vince1171 mentioned about here in porting guide: https://github.com/Vince1171/OnePlus2-Halium-Prebuild . … But I actually found that it uses latest built on jenkins, so not tied to particular version. And looks like there are different types of Ubuntu Touch not sure which one to actually choose, since this
Nov 24 22:54:38 <ubptgbot> phone is ARM64
Nov 24 22:59:13 <ubptgbot> <drapatyi> @UniversalSuperBox [Find the console= argument in your kernel cmdline and remove it. It'll probably …], So... there's no `console=` in my device: … https://paste.ubuntu.com/p/FsPnYDPp9w/
Nov 24 23:00:23 <ubptgbot> <UniversalSuperBox> I'm not sure, something doesn't seem right with the installation.
Nov 24 23:00:37 <ubptgbot> <UniversalSuperBox> Uh, try `cat /proc/cmdline` from your telnet shell
Nov 24 23:01:41 <ubptgbot> <drapatyi> https://paste.ubuntu.com/p/CN9mMB35Ks/
Nov 24 23:02:41 <ubptgbot> <drapatyi> [Edit] hm... I used image that Vince1171 mentioned about, here in porting guide: https://github.com/Vince1171/OnePlus2-Halium-Prebuild . … But I actually found that it uses latest built on jenkins, so not tied to particular version. And looks like there are different types of Ubuntu Touch not sure which one to actually choose, since this
Nov 24 23:02:41 <ubptgbot>  phone is ARM64
Nov 24 23:03:58 <ubptgbot> <UniversalSuperBox> Do you have a `/tmpmnt/systemimg`?
Nov 24 23:04:05 <ubptgbot> <UniversalSuperBox> .ing
Nov 24 23:04:07 <ubptgbot> <UniversalSuperBox> .img
Nov 24 23:04:31 <ubptgbot> <drapatyi> nope. nothing in `/tmpmnt/`
Nov 24 23:04:40 <ubptgbot> <UniversalSuperBox> It's moved to `/userdata` then
Nov 24 23:05:02 <ubptgbot> <drapatyi> there's no `/userdata` directory
Nov 24 23:05:37 <ubptgbot> <UniversalSuperBox> No, /root
Nov 24 23:05:43 <ubptgbot> <drapatyi> but there's a system.img is in `/root/userdata/system.img`
Nov 24 23:05:54 <ubptgbot> <drapatyi> [Edit] but there's a system.img in `/root/userdata/system.img`
Nov 24 23:05:59 <ubptgbot> <UniversalSuperBox> Is anything in `/root/android/system`?
Nov 24 23:06:57 <ubptgbot> <drapatyi> https://paste.ubuntu.com/p/Gx8dcpCz4K/
Nov 24 23:07:05 <ubptgbot> <vince1171> @drapatyi [https://paste.ubuntu.com/p/CN9mMB35Ks/], systempart=/dev/disk/by-partlabel/system datapart=/dev/disk/by-partlabel/userdata … those arguments change the way UT boot … if compile the halium-boot.img and system.img yourself, you need to revert https://github.com/Halium/android_device_oneplus_oneplus2/commit/46552eadda7f95b94a3f5
Nov 24 23:07:06 <ubptgbot> 4406af9aa3f278b8cb3
Nov 24 23:07:52 <ubptgbot> <drapatyi> @vince1171 [systempart=/dev/disk/by-partlabel/system datapart=/dev/disk/by-partlabel/userdat …], wow.. interesting why that was merged:)
Nov 24 23:08:10 <ubptgbot> <drapatyi> I'll do it Vince, and rebuild
Nov 24 23:08:32 <ubptgbot> <drapatyi> I looked for something like this, because this `/dev/disk/by-partlabel/` looked suspicious
Nov 24 23:08:53 <ubptgbot> <drapatyi> @vince1171 [systempart=/dev/disk/by-partlabel/system datapart=/dev/disk/by-partlabel/userdat …], [Edit] wow.. interesting why that was merged? then :)
Nov 24 23:14:31 <ubptgbot> <vince1171> @drapatyi [https://paste.ubuntu.com/p/CN9mMB35Ks/], [Edit] systempart=/dev/disk/by-partlabel/system datapart=/dev/disk/by-partlabel/userdata … those arguments change the way UT boot … if you compile the halium-boot.img and system.img yourself, you need to revert https://github.com/Halium/android_device_oneplus_oneplus2/commit/46552eadda
Nov 24 23:14:31 <ubptgbot> 7f95b94a3f54406af9aa3f278b8cb3
Nov 24 23:16:26 <ubptgbot> <vince1171> @vince1171 [systempart=/dev/disk/by-partlabel/system datapart=/dev/disk/by-partlabel/userdat …], `systempart=/dev/disk/by-partlabel/system datapart=/dev/disk/by-partlabel/userdata` are used in production, (with the ubports installer for example) … if you use the halium-install script, you need to remove those arguments :) … the ubports-
Nov 24 23:16:26 <ubptgbot> installer and the halium-install scrpit don't install UT the same way and those args tell halium-boot which way should be used  … And I've added those arguments to the sources because those sources will soon be automaticly build for a "official release" (and so installed with the ubports installer)
Nov 24 23:16:45 <ubptgbot> <vince1171> I should add it to the wiki
Nov 24 23:17:48 <ubptgbot> <drapatyi> @vince1171 [systempart=/dev/disk/by-partlabel/system datapart=/dev/disk/by-partlabel/userdat …], I'm confused a bit. Does that mean that I can do all the installation using ubports installer right now? or oneplus2 will be added soon?
Nov 24 23:21:13 <ubptgbot> <vince1171> @drapatyi [I'm confused a bit. Does that mean that I can do all the installation using ubpo …], no you can't use the ubports installer for op2 right now … but in a few weeks, I think so … but feel free to already install it now with the halium-install script and give me your feedback :)
Nov 24 23:21:37 <ubptgbot> <drapatyi> thanks Vince, it helped just rebuilt all halium-boot and flashed it with fastboot now ssh available
Nov 24 23:23:54 <ubptgbot> <NotKit> @ThaBlacMamba [It just seems to me since android already has a linux base you should be able to …], just to add to earlier discussion, it's a bit more complicated
Nov 24 23:24:03 <ubptgbot> <NotKit> proper Linux system
Nov 24 23:25:21 <ubptgbot> <NotKit> normal Linux systems rely on different set of kernel features to work (which requires kernel recompilation already), then libc and some Android components have to be patched to work with libhybris, then you need Android-side modifications to remove parts that are not used and you got your implementation of Halium
Nov 24 23:25:56 <ubptgbot> <drapatyi> So I did this: … ```#Changed revision to commit before your changes … #in halium_build_dir: … cat  halium/devices/manifests/oneplus_oneplus2.xml | grep Halium/android_device …     <project path="device/oneplus/oneplus2" name="Halium/android_device_oneplus_oneplus2" remote="hal" revision="7ce54ff66f294ce4cdf7e27e679ea53974ef03c9" /> … ./h
Nov 24 23:25:56 <ubptgbot> alium/devices/setup oneplus2 … make clean … mka halium-boot```
Nov 24 23:28:16 <ubptgbot> <vince1171> @drapatyi [So I did this: … #Changed revision to commit before your changes … #in halium_build_ …], not the easiest way to do, but it  should be  good ^^
Nov 24 23:39:32 <ubptgbot> <drapatyi> @vince1171 [not the easiest way to do, but it  should be  good ^^], now it's crashing right after X starts, but looking through logs it doesn't look like an graphics related crash... Looks like something related to wifi: … * console-ramops: https://paste.ubuntu.com/p/X9fhc5Fq23/ … * console-dmesg-0: https://paste.ubuntu.com/p/Hfc98YRDYD/
Nov 24 23:55:07 <ubptgbot> <vince1171> @drapatyi [now it's crashing right after X starts, but looking through logs it doesn't look …], That's strange … I'll rebuild the .img's and install it tomorrow
Nov 25 00:01:42 <ubptgbot> <drapatyi> @vince1171 [That's strange … I'll rebuild the .img's and install it tomorrow], Created this PR right now, if I find anything else I'll add here: … https://github.com/Halium/android_device_oneplus_oneplus2/pull/1
Nov 25 00:10:31 <ubptgbot> <drapatyi> @vince1171 [That's strange … I'll rebuild the .img's and install it tomorrow], [Edit] Created this PR right now, if I find anything else I'll add here more: … https://github.com/Halium/android_device_oneplus_oneplus2/pull/1
Nov 25 01:51:50 <ubptgbot> 奥莉辜 was added by: 奥莉辜
**** ENDING LOGGING AT Mon Nov 25 02:59:58 2019