**** BEGIN LOGGING AT Sun Feb 11 03:00:01 2018 Feb 11 03:00:12 Truly these are the end times Feb 11 03:00:33 what does that even mean? Feb 11 03:00:41 https://paste.ubuntu.com/=cr95NrnSMM/ Feb 11 03:00:51 I have no idea, but I expect it's something kernel-side Feb 11 03:01:05 And I also expect that I do not have the experience to debug or fix it Feb 11 03:05:53 welll.... that just means you have to learn! Feb 11 03:06:20 I'm really starting to think that might not be the best use of my time Feb 11 03:06:34 possibly. Feb 11 03:07:32 I'm thinking put Lineage back on the 5X and continue porting to the G5 Plus with my newfound knowledge Feb 11 03:07:45 hmmm Feb 11 03:08:14 I've been using my htc one m8 as a backup. I don't think anyone's started a port for that Feb 11 03:13:25 dalton, can you confirm for me that it should be mounted r/w at that point? Feb 11 03:13:50 It should be read-write no matter what Feb 11 03:13:56 ok Feb 11 03:14:19 I'm tempted to just build a static fully fledged busybox and add it to the fs Feb 11 03:14:33 How will that help? Feb 11 03:14:44 I have no idea. I'm tired. Feb 11 03:14:49 You aren't even leaving initramfs yet Feb 11 03:17:12 does twrp run the lineageos kernel? Feb 11 03:17:21 They build their own Feb 11 03:22:20 @UniversalSuperBox that cgroup error is not your main problem Feb 11 03:22:26 That it isn't Feb 11 03:22:55 L3 is however issue Feb 11 03:23:04 Does dmesg show anything interesting? Feb 11 03:23:15 Nope Feb 11 03:23:39 @UniversalSuperBox, here it is Feb 11 03:25:40 L1011 Feb 11 03:25:45 Isn't that issue? Feb 11 03:26:00 I manually mounted it all Feb 11 03:26:09 If I let it get mounted correctly, I can't get ssh Feb 11 03:26:17 Everything just stops Feb 11 03:26:19 I don't understand Feb 11 03:26:34 Never panics Feb 11 03:27:59 Maybe it stops USB? Feb 11 03:28:08 Nope, it responds to pings Feb 11 03:28:40 Hmm Feb 11 03:29:05 https://paste.ubuntu.com/=5XH4z2PgVt/ Feb 11 03:29:08 This is literally all that's running in userspace Feb 11 03:29:49 what happens if you set init=/bin/bash and start things yourself? Feb 11 03:30:17 Hmm... Can I do that with halium-boot? Feb 11 03:30:26 I guess I've never tried Feb 11 03:30:31 Wait, no Feb 11 03:30:39 Because I don't have a shell Feb 11 03:30:41 just don't kill the telnet server Feb 11 03:33:09 It's got eleven processes to worry about but it still can't reboot Feb 11 03:33:54 why so many sshd's Feb 11 03:35:08 One's running on *:ssh, one on the actual ip address, and the last on ipv6 Feb 11 03:36:52 Ah, no. Here we go Feb 11 03:37:09 https://paste.ubuntu.com/=6kMmzVgCb3/ Feb 11 03:37:14 That's why. Doesn't get me anywhere though Feb 11 03:38:08 Well, @bhushanshah, if you don't have any ideas I think I'm going to head to bed Feb 11 03:39:20 Okay.. I am really not sure what's going on also Feb 11 03:40:48 whelp Feb 11 03:42:26 Also my fibre connection is down... *panics* Feb 11 07:57:11 @bhushanshah, Dialup Feb 11 07:57:25 Beep beeeeep bip bbbeep beep Feb 11 09:19:13 Hello Feb 11 09:20:42 I'm trying to build the boot IMG on another machine. Maybe it works. I'm downloading now the device specific source. And I'm pushing up now the files I've edited Feb 11 09:22:53 What means I try it using a virtual server. Cause of better internet connection Feb 11 09:27:27 @Manu, I built one completely on an online vm Feb 11 09:27:41 Ah okay Feb 11 09:38:56 1033 messages wtf is going on here 😆 Feb 11 09:59:54 I managed to build the boot image successfully yesterday Feb 11 10:00:08 today I get this error Feb 11 10:00:19 any ideas ? Feb 11 10:00:58 chmod +x it... I hope I didn't break it with my pr yesterday Feb 11 10:08:42 It was my PR :/ I'll fix it Feb 11 10:10:36 run `repo sync` again, that should fix it Feb 11 10:21:50 I get now this error: Feb 11 10:21:53 https://pastebin.com/LrFc0sYJ Feb 11 10:23:19 First: why are you building as root? And you probably need to install schedtool Feb 11 10:23:50 Because I have only a root account on this server Feb 11 10:25:02 It would be better to create a unpreviligated account Feb 11 10:25:15 Okay Feb 11 10:38:33 @Ellenjott, I've tried but the problem persist Feb 11 10:44:46 I've created a pull request for fixup mountpoints Feb 11 10:47:30 I've tried it again on my computer and I get an output with errors issuing make hybris-boot: Feb 11 10:47:33 https://pastebin.com/6BLxgisz Feb 11 13:15:47 Camilo was added by: Camilo Feb 11 14:37:25 Fwd from trainailleur: @YougoChats Hugo, I just tried su -c 'setprop sys.powerctl reboot,bootloader' on my other OnePlus One, running 15.04 stable, and it works there. Just not on 16.04 build 138 for some reason. … Thank you again for the suggestions. I learned a lot just by trying them. Feb 11 14:38:33 He is trying to get the phone in recovery and/or fastboot from terminal because hardware buttons are broken Feb 11 14:38:59 And adb also doesn’t work Feb 11 14:39:52 Does any of you happen to know if and how to do this on 16.04? Feb 11 14:45:39 `systemctl --force reboot recovery` Feb 11 14:45:55 Ok sorry, that won't work with upstart ... Feb 11 14:46:11 `reboot -f recovery` Feb 11 14:46:29 Thanks, I will give it a try. Feb 11 14:53:01 So sync as non root user is almost done Feb 11 14:54:28 Dalton, that works. So does reboot -f bootloader, which is what I needed. Many thanks! Thank you too Hugo for thinking this might have changed with Halium and asking here. Feb 11 15:21:24 Good morning guys, y f*cked up my system doing a partial update, so I'll take a time to come back :p Feb 11 15:42:17 So some failures again Feb 11 15:42:19 https://pastebin.com/sWknMYiC Feb 11 15:42:51 I only understand something with permissions denied Feb 11 15:42:53 Should I change them? Feb 11 15:44:11 Did you build as root in this tree earlier? Feb 11 15:44:27 Yes I did one time Feb 11 15:45:32 `chown -R user:grup out/` Feb 11 15:45:43 Okay Feb 11 15:46:05 or just delete the old folder Feb 11 15:46:12 Probably safer Feb 11 15:46:13 Okay Feb 11 15:52:40 Are the warnings normal? Feb 11 15:53:08 Yep, lots of em Feb 11 15:53:20 Okay Feb 11 15:58:18 https://pastebin.com/GbQFNZiZ Feb 11 15:58:33 Again something with denied permissions Feb 11 16:10:23 What to do? Feb 11 16:11:49 @Manu, learn basics of GNU/Linux ^^ Feb 11 16:12:28 Ya I have already some basics but I don't know what to do now Feb 11 16:18:35 @Manu, Maybe try to clean the build tree (were you the one who asked about using root for building?) Feb 11 16:19:01 Okay Feb 11 16:19:09 @Ellenjott, Yes I've asked Feb 11 16:19:29 If you used root at any time for building, this might be the problem Feb 11 16:19:32 I'm not familiar with building halium I'm doing it the first time Feb 11 16:19:37 np Feb 11 16:19:41 Okay Feb 11 16:20:25 I think it's the best if you delete the whole `out` folder in your tree and then rebuild everything (`mka mkbootimg`, `mka hybris-boot`, etc.) Feb 11 16:20:38 Okay Feb 11 17:15:22 has anyone tried running Halium with vivid rootfs? Feb 11 17:15:50 In theory it'd work on 5.1 and 5.1-caf, maybe 7.1 Feb 11 17:17:37 So i think I have to remove in a file all the apk and .jar extensions. But where? Because I got this output Feb 11 17:17:40 https://pastebin.com/hQVTuStd Feb 11 17:18:52 @Manu, Remove all APKs and JARs in the proprietary-files.txt in your device tree (and also common device tree), then rerun the halium-devices setup script Feb 11 17:36:10 Manu Did that help? Feb 11 17:36:22 Nope Feb 11 17:36:48 There was only one Entry I removed it Feb 11 17:37:03 You need to remove all apks and jars Feb 11 17:37:27 and run `./halium/devices/setup ` again Feb 11 17:37:56 Ya there was in all the 3 files i mean in one file one entry with a .apk extension Feb 11 17:38:16 Just be sure there are no apks and jars left Feb 11 17:38:32 Ya but same issue Feb 11 17:38:53 After runnning the setup script? Feb 11 17:38:58 is there a setup-makefiles.sh script in your device-tree? Feb 11 17:39:16 btw, which device do you use? Feb 11 17:39:45 Wait... Feb 11 17:40:04 @JBBgameich, Yes there is one Feb 11 17:40:17 I use the galaxy s4 international Feb 11 17:40:24 With code name jfltexx Feb 11 17:41:24 What's the error again? Feb 11 17:42:49 Here Feb 11 17:42:53 https://pastebin.com/Qca0cFLe Feb 11 17:43:23 Oh, that's something different ... Feb 11 17:43:29 Okay Feb 11 17:46:20 I think you hit a java library there again #comment-it-out Feb 11 17:46:47 I'll also fork the repo and fix it Feb 11 17:47:09 Okay Feb 11 17:50:27 Please create a pull request adding your manifest to halium-devices: … https://github.com/Halium/halium-devices/tree/halium-7.1/manifests Feb 11 17:50:34 Manu Feb 11 18:00:27 Okay I added my manifest as .txt file Feb 11 18:00:49 I mean a pull request Feb 11 18:04:01 Ah okay Feb 11 18:06:31 Okay but now Feb 11 18:07:02 It should ask you to open a pull request Feb 11 18:07:43 Okay Feb 11 18:17:02 Manu Please edit the existing pull request, instead of opening a second one Feb 11 18:17:42 Okay😂 I'm not very familiar with github Feb 11 18:17:52 :D Feb 11 18:18:51 Also please fork all repositories and upload your changes on a `halium-7.1` branch Feb 11 18:19:24 You mean on my github account? Feb 11 18:24:19 @Manu, Yeah Feb 11 18:24:31 Okay Feb 11 18:27:39 @Manu, The best way is probably, you first read or watch a git tutorial Feb 11 18:29:10 Ah okay Feb 11 18:44:08 Manu … If you add these two lines, it should work: … ``` … ``` … Or wait until https://github.com/Halium/android/pull/13 gets merged. Feb 11 18:44:53 Okay thanks😁 Feb 11 18:45:14 I also had this problem with my yuga Feb 11 18:45:25 Okay Feb 11 19:42:23 @UniversalSuperBox Trying to build initramfs-tools-halium, getting errors I don't understand: https://gist.github.com/rockybulwinkle/5c3c8cf07cbe05434575d61d247ad276 Feb 11 19:44:24 You will need userspace qemu arm64 emulation. Are you sure it's set up? Feb 11 19:44:53 I think so? Feb 11 19:45:21 I was getting exec format error before but fixed it after moving to my laptop which has qemu-user-static installed. I checked, it was compiled with arm64 Feb 11 19:46:33 The log says "See debootstrap.log". Can you also paste this one? Feb 11 19:46:49 I cat'ed it in the previous pastie, want it separate? Feb 11 19:47:05 Oh, sorry, I overlooked it probably :) Feb 11 19:47:33 I was trying to include everything I thought was relevant. :) Feb 11 19:48:02 And I checked, those files do exist in the chroot Feb 11 19:49:06 I was checking the bashrc/profile stuff because I've seen things like this before, where bash itself can't find a file. Not chroot being unable to find the program. Feb 11 19:49:48 Is there a reason you need to build initramfs-tools-halium? Feb 11 19:50:09 You suggested I try it yesterday Feb 11 19:50:42 If you include halium-boot into your tree, it will download the initrd from our ci Feb 11 19:50:56 So you don't need to build that yourself Feb 11 19:51:00 ah. Feb 11 19:51:20 how do I go about including it? Feb 11 19:52:26 add this: … ``` ``` … to the end of .repo/manifest.xml Feb 11 19:52:30 ok Feb 11 19:52:37 and include it into the main Makefile Feb 11 19:52:38 Fwd from JBBgameich: ```diff --git a/core/main.mk b/core/main.mk … index 083d2fe..3964e1c 100644 … --- a/core/main.mk … +++ b/core/main.mk … @@ -646,6 +646,7 @@ subdirs += \ … # Specific projects for Halium … subdirs += \ … halium/hybris-boot \ … + halium/halium-boot \ … halium/droidmedia … FULL_BUILD := true``` Feb 11 19:53:39 And if your device tree doesn't define TARGET_KERNEL_ARCH, apply this patch: … https://github.com/Halium/halium-boot/pull/1.patch Feb 11 19:55:19 No need Feb 11 19:55:57 Ah, you just merged it :) Thanks Feb 11 19:56:23 That thumbs-up emoji on https://github.com/Halium/initramfs-tools-halium/pull/6 says "merge it" to me Feb 11 19:56:57 Couple more tests first Feb 11 19:57:14 It looks good, but I didn't test it on a device yet Feb 11 19:57:32 I'm currently just build-testing halium-boot with different devices Feb 11 20:01:34 so, repo sync -c doesn't set which branch I'm on. … (venv) [rocky@Saturn hybris-boot]$ git status … Not currently on any branch. … What branch should I be committing to? Feb 11 20:02:04 We normally use halium-7.1 as branch name Feb 11 20:02:11 ok Feb 11 20:05:16 It didn't recognize the branch name halium-7.1. what do? I tried doing "git checkout -b halium-7.1" but I have a feeling this was the Wrong Thing (tm) Feb 11 20:05:37 Mr MoMo was added by: Mr MoMo Feb 11 20:07:18