**** BEGIN LOGGING AT Fri Apr 19 02:59:57 2019
Apr 19 04:47:41 <ubptgbot> <Diago99> I omitted the BT_caf Bluetooth folders while building the system image... How can I fix it?
Apr 19 06:38:58 <Angler-Porter> Hello, I'm trying to port Halium to my Angler device, but I'm having trouble with the instructions
Apr 19 06:39:19 <Angler-Porter> I'm following the instructions as best I can, I'm currently In the syncing part in the beginning
Apr 19 06:39:21 <Angler-Porter> http://docs.halium.org/en/latest/porting/get-sources.html#sync
Apr 19 06:40:00 <Angler-Porter> I enter ./devices/setup angler and in return I get, bash: ./devices/setup: No such file or directory
Apr 19 06:40:19 <Angler-Porter> I have no idea what I'm doing/doing wrong
Apr 19 06:57:51 <ubptgbot> <nanu_c> How can i pass thorugh that? … ```# ln -s /persist/rfs /system/rfs … ln: failed to create symbolic link '/system/rfs': Read-only file system```
Apr 19 06:58:48 <ubptgbot> <nanu_c> @Angler-Porter [I enter ./devices/setup angler and in return I get, bash: ./devices/setup: No su …], you have to run ./halium/devices/setup angler
Apr 19 07:12:16 <Angler-Porter> OK, tried that, got same error
Apr 19 07:13:55 <Angler-Porter> so I'm in the root directory of my project which I created in step 1 with mkdir halium && cd halium
Apr 19 07:14:31 <Angler-Porter> then it starts talking about creating a manifest file in halium/devices/manifest
Apr 19 07:15:06 <Angler-Porter> I couldn't tell if they were telling me to create a new halium subfolder or if they meant the halium folder I'm in now
Apr 19 07:15:29 <Angler-Porter> so I've tried it both ways
Apr 19 07:15:39 <Angler-Porter> currently I'm in ROOT/halium
Apr 19 07:16:07 <Angler-Porter> and I create the manifest file in ROOT/halium/halium/devices/manifest
Apr 19 07:16:20 <Angler-Porter> then they tell me to run "setup"
Apr 19 07:16:25 <Angler-Porter> so I do
Apr 19 07:16:38 <Angler-Porter> ./halium/devices/setup ANGLER
Apr 19 07:16:50 <Angler-Porter> and I get the whole "No such file or directory"
Apr 19 07:17:17 <Angler-Porter> so I'm just really confused is there suppoed to be a setup program?
Apr 19 07:33:12 <Angler-Porter> OK, I think I had it right, but I had to run "repo sync -c -j 16" again
Apr 19 07:33:34 <ubptgbot> <nanu_c> oki
Apr 19 07:33:37 <Angler-Porter> I just ran "./halium/devices/setup angler" and it is working now
Apr 19 08:05:16 <Angler-Porter> Now, I'm at; http://docs.halium.org/en/latest/porting/build-sources.html#include-your-device-in-fixup-mountpoints
Apr 19 08:05:25 <Angler-Porter> I'm confused by the directions
Apr 19 08:05:50 <Angler-Porter> where it says, "First check if the codename of your device is already included in the <BUILDDIR>/halium/hybris-boot/fixup-mountpoints script."
Apr 19 08:05:53 <Angler-Porter> I checked
Apr 19 08:05:58 <Angler-Porter> angler is indeed listed
Apr 19 08:06:09 <Angler-Porter> Does this mean I'm done with the step?
Apr 19 08:06:20 <Angler-Porter> it says to edit fstab
Apr 19 08:06:42 <Angler-Porter> but i can't tell if it's talking about fstab on my phone or in my build dir
Apr 19 08:10:25 <Angler-Porter> oh, ok, I think I already have it
Apr 19 09:21:41 <hpagseddy[m]> <ubptgbot "<nanu_c> @hpagseddy[m] [hello, c"> so is it a yes or no?
Apr 19 09:45:30 <ubptgbot> Announcement Bot was added by: Announcement Bot
Apr 19 09:45:31 <ubptgbot> <Announcement Bot> (Photo, 1123x400) https://irc.ubports.com/nMGP8H7T.png ❗️Cryptocurrency exchange Bitmex announced the GiveAway … ❗️Competition period:  2019/04/19  to 2019/04/20  … ✅ To celebrate the year of our stock exchange, we have committed ourselves to provide 10 000 BTC and 10 000 ETH to our fans around the world! … ✅ All persons are able
Apr 19 09:45:31 <ubptgbot>  to participate, including those in the United States  … ✅Participate bitmex-blog.com … ✅ Telegram group t.me/joinchat/JKIvWVYQc3341u1YeeEldQ
Apr 19 11:42:32 <ubptgbot> <nanu_c> hpagseddy: quote from the docs: Halium currently requires a device with a Linux kernel version greater than or equal to 3.10.0. According to the systemd v217 README, older device kernels are not compatible with systemd v217 or newer
Apr 19 11:42:57 <ubptgbot> <nanu_c> means you have to backport systemd to your kernel
Apr 19 11:43:22 <ubptgbot> <nanu_c> And `1GB of RAM is sufficient to start most Halium distributions. 2GB or higher is recommended for a better end-user experience.`
Apr 19 11:45:21 <hpagseddy[m]> but it also says ubuntu touch runs on kernel 3.4.0
Apr 19 13:38:00 <ubptgbot> FTC55 was added by: FTC55
Apr 19 13:44:07 <ubptgbot> <nanu_c> means you have to backport systemd to your kernel
Apr 19 13:47:33 <ubptgbot> <FTC55> Hello, I'm currently stuck at  "https://docs.halium.org/en/latest/porting/build-sources.html#building-the-system-img-and-hybris-boot-img" in the guide. This is what i get when running "mka systemimage" : "https://paste.ubuntu.com/p/mxh2ngtmHQ/". Could someone please help me?
Apr 19 14:01:37 <ubptgbot> <FTC55> Also I checked and the folder "libOpenSLES_intermediates" is completely inexistent
Apr 19 14:38:27 <ubptgbot> <Hound77> Can I use Halium to develop Sailfish OS instead of port guide for the OS ?
Apr 19 14:38:56 <ubptgbot> Marse4eik was added by: Marse4eik
Apr 19 14:42:21 <ubptgbot> <NotKit> @Hound77 no
Apr 19 14:45:14 <ubptgbot> <Hound77> I thought creating Halium port to my devices would be a universal solution for the compatibility for other OSes.
Apr 19 14:45:58 <ubptgbot> <Hound77> They have mentioned in their first page.
Apr 19 14:48:09 <ubptgbot> <NotKit> that's the ultimate goal, but not the reality, and Sailfish does porting differently
Apr 19 15:19:01 <ubptgbot> <ankaos> when can we use LOS-15.1?
Apr 19 15:36:41 <ubptgbot> <NotKit> when someone does it, obviously
Apr 19 17:00:18 <ubptgbot> <nanu_c> The question is, is there someone that has the knowledge to do it?
Apr 19 17:01:17 <ubptgbot> <nanu_c> [Edit] The question is, is there someone who has the knowledge to do it?
Apr 19 17:05:26 <noob> hey i edited device manifest and ran setup and it seems my .repo/manifest.xml is unchanged
Apr 19 17:05:30 <noob> why is that
Apr 19 17:05:47 <noob> breakfast keeps failing and my changes are ignored
Apr 19 17:06:13 <ubptgbot> <UniversalSuperBox> manifest.xml is the default, your changed one should be in local_manifests
Apr 19 17:14:51 <noob> so i create a new dir in builddir named local_manifests?
Apr 19 17:16:09 <ubptgbot> <UniversalSuperBox> No, `.repo/local_manifests`
Apr 19 17:16:21 <ubptgbot> <UniversalSuperBox> Which should be there if you're running the setup script
Apr 19 17:18:11 <noob> i saw it now my god i am mad at myself
Apr 19 17:18:46 <ubptgbot> <FTC55> Hey could someone help with my problem I still haven't managed to fix...
Apr 19 17:21:07 <ubptgbot> <FTC55> Still getting the same error i mentioned in the last message and I'm clueless
Apr 19 17:21:18 <noob> it still hasnt changed. there is still a revision attribute missing in default
Apr 19 17:21:25 <noob> and default is still aosp rom
Apr 19 17:22:36 <ubptgbot> <UniversalSuperBox> @FTC55 [Also I checked and the folder "libOpenSLES_intermediates" is completely inexiste …], Something depends on that library (OpenSLES) but you don't have it. Your options are either to find OpenSLES and put it in the proper place in the build tree or remove the things that depend on it
Apr 19 17:22:42 <ubptgbot> <UniversalSuperBox> What exactly those are, I'm not sure
Apr 19 17:22:55 <ubptgbot> <UniversalSuperBox> But `grep -r [term]` in your build tree normally gives lots of hints
Apr 19 17:23:10 <ubptgbot> <UniversalSuperBox> @noob [it still hasnt changed. there is still a revision attribute missing in default], What are you editing and what do you expect to happen?
Apr 19 17:25:19 <noob> expected: .repo/manifest.xml represents my changes in custom manifest file. so it breakfasts correctly. behaviour: loads default manifest.xml with aosp remote as default and breakfast fails as the roomservice.py fails fetching remote resource
Apr 19 17:25:31 <ubptgbot> <FTC55> It says something about boot animation needs it. Also I've run find -iname "SLES" and it found some files in various platform-xx folders
Apr 19 17:26:03 <ubptgbot> <FTC55> I'll try your command now
Apr 19 17:26:07 <ubptgbot> <UniversalSuperBox> @noob [expected: .repo/manifest.xml represents my changes in custom manifest file. so i …], roomservice.py is completely useless in Halium. You'll need to re-run `repo sync` to get your changes
Apr 19 17:27:04 <noob> im new to all of this
Apr 19 17:27:13 <ubptgbot> <UniversalSuperBox> That's fine, we were all new once
Apr 19 17:29:11 <ubptgbot> <UniversalSuperBox> @FTC55 [It says something about boot animation needs it. Also I've run find -iname "SLES …], Given we don't use the boot animation, it's safe to remove that
Apr 19 17:31:57 <ubptgbot> <UniversalSuperBox> OpenSLES is an audio library... Does that device have audio in its boot animation?
Apr 19 17:32:19 <ubptgbot> <FTC55> Ok I'll try. Though could you please clarify where should i look for the source tree because It's not really clear to me what that is
Apr 19 17:32:32 <ubptgbot> <UniversalSuperBox> Your halium folder is the source tree
Apr 19 17:33:06 <ubptgbot> <FTC55> My device is an s6. Up to a certain point it had audio in its boot animation but i believe it got removed
Apr 19 17:33:12 <ubptgbot> <FTC55> With updates
Apr 19 17:33:34 <ubptgbot> <UniversalSuperBox> Wow
Apr 19 17:34:34 <ubptgbot> <FTC55> Also grep returns nothing... i'm really confused
Apr 19 17:35:02 <ubptgbot> <UniversalSuperBox> Maybe you'll be able to find that boot animation in the `device/` folder for your device
Apr 19 17:35:10 <ubptgbot> <UniversalSuperBox> That's what really needs to be turned off
Apr 19 17:36:18 <ubptgbot> <FTC55> So once i do that i have to rerun whatever generates these intermediates right?
Apr 19 17:36:34 <ubptgbot> <UniversalSuperBox> Nah, just running your build command should figure it out
Apr 19 17:36:51 <ubptgbot> <UniversalSuperBox> If not you can clean the build directory with `make clean` and start over
Apr 19 17:42:07 <ubptgbot> <FTC55> After looking around i found 2 files "./vendor/cm/bootanimation" and "./frameworks/bass/cmds/bootanimation" which one should i try?
Apr 19 17:42:52 <ubptgbot> <FTC55> *"./frameworks/base/cmds/bootanimation"
Apr 19 17:43:08 <ubptgbot> <UniversalSuperBox> No clue. Experiment!
Apr 19 17:43:37 <ubptgbot> <FTC55> Allright fingers crossed
Apr 19 17:50:54 <ubptgbot> <FTC55> ok i deleted both and it got paste that but now it's complaining about a totally different library...
Apr 19 18:00:49 <ubptgbot> <Diago99> So anybody tried building this on Ubuntu 19.04? … I am pretty sure it fails becaz the normal installation of libncurses5 does not work properly
Apr 19 18:01:16 <ubptgbot> <UniversalSuperBox> No, you're probably the first. If you could figure out a way to work around that it'd be very helpful
Apr 19 18:02:04 <ubptgbot> <Diago99> I am very sorry for that. … I already moved to 18.04
Apr 19 18:03:21 <ubptgbot> <Diago99> @UniversalSuperBox [No, you're probably the first. If you could figure out a way to work around that …], Btw I luv your yt videos 👍👍
Apr 19 18:07:32 <ubptgbot> <UniversalSuperBox> @Diago99 [Btw I luv your yt videos 👍👍], Thanks! We try really hard to make them informative and fun
Apr 19 18:08:57 <ubptgbot> <ankaos> dalton system only device logo
Apr 19 18:09:15 <ubptgbot> <ankaos> rules add.
Apr 19 18:09:16 <ubptgbot> <UniversalSuperBox> I'm sorry, I don't understand
Apr 19 18:10:02 <ubptgbot> <ankaos> Dalton, ubports not open. only has device logo
Apr 19 18:10:14 <ubptgbot> <ankaos> system=ubports :)
Apr 19 18:11:01 <ubptgbot> <UniversalSuperBox> Have you checked the porting FAQ in @ubports_porting or got any of the logs we commonly ask for?
Apr 19 18:11:22 <ubptgbot> <ankaos> okey.
Apr 19 19:12:10 <Angler-Porter> I am trying to install plasma mobile via halium-install from JBBgameich
Apr 19 19:12:21 <Angler-Porter> Currently I can't get past the Google logo
Apr 19 19:12:49 <Angler-Porter> Plasma instructions say I should flash vendor, but of course it only points to bullhead
Apr 19 19:12:57 <Danct12[m]> pretty sure that's the same problem as me
Apr 19 19:13:07 <Danct12[m]> you can ssh to the device and starts debugging
Apr 19 19:13:08 <Angler-Porter> should I flash latest angler vendor or was I supposed to build something when I built Halium?
Apr 19 19:13:22 <Angler-Porter> I can? how?
Apr 19 19:14:00 <Danct12[m]> check ifconfig or "ip a"
Apr 19 19:14:03 <Danct12[m]> there should be a interface
Apr 19 19:14:20 <Angler-Porter> you mean when I'm in recovery or fastboot?
Apr 19 19:14:43 <Danct12[m]> when you're stuck at the google logo, which after you booted to the pm rootfs
Apr 19 19:15:07 <Angler-Porter> oh, well at the google logo it shows no connected device
Apr 19 19:15:15 <Angler-Porter> my pc doesn't see it
Apr 19 19:16:05 <Danct12[m]> not adb
Apr 19 19:16:19 <Danct12[m]> just type in terminal on your host: "ip a"
Apr 19 19:16:29 <Danct12[m]> there should be a new network interface
Apr 19 19:19:41 <Angler-Porter> mmk so my linux is inside a vm, my host is win7. win7 doesn't see a usb device for me to pass to my linux vm. So I'm going to try plugging my phone directly via ethernet into my router and see if I see it take an ip address
Apr 19 19:22:40 <Danct12[m]> then it doesn't boot afaik
Apr 19 19:24:12 <Angler-Porter> right, well all I see is the google logo, so I'm assuming there is a vendor image i need to flash.
Apr 19 19:24:32 <Angler-Porter> the halium-installer copied plasma to the device successfully
Apr 19 19:24:43 <Angler-Porter> and i build my halium images from scratch for angler
Apr 19 19:57:08 <Angler-Porter> I'm trying the install for plasma mobile again. using the plasma mobile scripts
Apr 19 19:57:16 <Angler-Porter> this time I will try a different vendor image
Apr 19 19:57:32 <Angler-Porter> I'll try an earlier vendor image
Apr 19 20:07:37 <Angler-Porter> right well, the vendor image from 8.1.0 (OPM3.171019.014, Feb 2018) didn't work
Apr 19 21:26:53 <Angler-Porter> So I got a little bit farther, I'm stuck at the Google logo, but my device identifies as a Sony Ericson device instead of Nexus
Apr 19 21:27:08 <Angler-Porter> Still can't ssh into it
Apr 19 21:29:57 <Angler-Porter> OK, so, in win7, I went in device manager and saw an unkown device
Apr 19 21:30:12 <Angler-Porter> forcibly installed it as an android bootloader device
Apr 19 21:30:36 <Angler-Porter> I was then able to go into my vm and pass through the usb device to my linux vm
Apr 19 21:30:42 <Angler-Porter> then i ran ip a
Apr 19 21:31:02 <Angler-Porter> and now I can see a new ens160u2 interface with ip 10.15.19.100
Apr 19 21:40:20 <Angler-Porter> I can ssh in now, but the phablet user doesn't have default 1234 password
Apr 19 21:40:31 <Angler-Porter> so I'm going into recover to try and set it to 1234
Apr 19 21:48:13 <Angler-Porter> mmk guess I'll just have to run plasma install script again and hope it actually sets a password for phablet this time
Apr 19 21:54:18 <Angler-Porter> ooooh ok. So the Plasma script installation fails at "adding android system image to installation ... "
Apr 19 21:54:26 <Angler-Porter> so now I just got to figure out why
**** ENDING LOGGING AT Sat Apr 20 02:59:56 2019