**** BEGIN LOGGING AT Thu Jan 11 03:00:02 2018 Jan 11 04:44:27 @Ern_st run this when SSHed into the device: zcat /proc/config.gz Jan 11 04:44:36 it will show you the current kernel config Jan 11 04:48:06 @vanyasem thanks, so i'm missing something see : https://paste.ubuntu.com/26358151/ Jan 11 04:48:28 The proc/config.gz doesn't reflect the defconfig... Jan 11 04:48:58 even if my BoardConfig.mk points to the correct one seems to be... Jan 11 04:49:23 @Ern_st it's intended. and it's okay in most cases. the configuration is being altered in the build process, you can manually find where and disable that. but again, it's not needed in most cases Jan 11 04:50:13 I'm trying to have the correct config for lxc Jan 11 04:50:26 @Ern_st your phone defconfig looks ok actually. i am only concerned about user namespace, you don't really need to enable it Jan 11 04:51:43 Ah ok i'm battleling to enabling it :) Jan 11 05:23:12 why are you doing that exactly? is something broken? Jan 11 06:00:51 Naively i want an LXC-checkconfig all green. Jan 11 06:16:36 @Ern_st, You do that by building a new kernel and making changes to your defconfig Jan 11 06:17:14 @Mr_Doge see : https://paste.ubuntu.com/26358151/ Jan 11 06:26:11 @Ern_st, I have the same issue :/ Jan 11 06:29:41 Not sure what is issue there Jan 11 06:29:48 Kernel config is totally fine Jan 11 06:29:59 And you should move to next step Jan 11 06:32:36 I'm ok with your feedbacks, i'll work on the next step ^^ Jan 11 06:46:14 is it impossible to adapt a proprietary firmware that only works for linux 3.x on linux 4.x? Jan 11 08:00:39 @bhushanshah, I think they saw "Cgroup namespace: required" on the phone output, which should be not there maybe. Question is always does it work or not? Container running or not? Jan 11 10:04:43 @mariogrip when u have time (i know you don't have) plz can you add channel for vivid also, because i will publish it in xda, so people can be sur nnow that this device is still supported and developpment is in progress Jan 11 10:24:11 @mariogrip … question … why mariogrip/remove-selinux branch of android_build isn't yet merged with halium7.1 branch? is there any reason? ^^ Jan 11 10:24:25 it breaks some devices Jan 11 10:27:09 oki thx Jan 11 10:32:18 I disabled Config_USER_NS,... To eliminate some errors... … How can this impact my build Jan 11 10:32:31 none Jan 11 10:37:04 Also CONFIG_FW_USER_LOADER=y (Something like that)... It created some error firmware_class error.. so i disabled it.. there were no commits to patch it on the sample kernel provided by Dalton... Jan 11 10:37:30 Can it do something bad? Jan 11 12:15:03 @vince1171, Can share repo link? Jan 11 12:26:53 itviewer was added by: itviewer Jan 11 12:51:35 In general why is selinux removed completely I wonder? Jan 11 13:16:53 @Herrie, Because also Ubuntu Desktop does not use it, and instead AppArmor was introduced. Probably was easier to port the desktop to mobile. But was not our design decision Jan 11 13:18:09 Flohack: Ah OK Jan 11 13:18:14 Was just wondering Jan 11 13:19:23 Anyone has made any experiences with Android drivers using/ requiring SElinux? Jan 11 13:20:11 schmittlauch: I think so ;) Jan 11 13:20:15 What target are you looking at? Jan 11 13:24:24 schmittlauch: Let's put it this way: I managed to build some minimal Android bits without completely removing SElinux ;) Jan 11 13:24:29 But not for Halium/UBPorts Jan 11 13:24:49 Didn't get anything to boot yet, but it managed to build which was already something Jan 11 13:27:13 @Herrie, I am trying the same now: I leave AUDIT=y in the kernel config, but then you need to supply the correct kernel cmdline to disable it again. Leaving it on will lead to permission problems probably Jan 11 13:27:43 In my case, bootloader overwrites kernel cmdline, and my CMDLINE_EXTEND=y gets also ignored ^^ Jan 11 13:28:16 So I have a hard time passing in the right kernel cmdline and my SELinux is now switched on... And of course the LCX does not start anymore etc Jan 11 13:28:19 @Flohack, that's weird. shouldn't happen. Jan 11 13:28:38 @trivial_inanity, It happened for all devices I tried to port so far. Jan 11 13:29:09 The cmdline in device tree has maybe 3 parameters, but then you boot and the effective cmdline has 5 to 20 parameters ^^ Jan 11 13:29:10 @Flohack, Works fine for me. 3.10 and 3.0 Jan 11 13:29:20 Don't have a 3.4 device, so can't try Jan 11 13:29:28 and of course it has console=null or none inside ^^ Jan 11 13:29:48 Flohack: Which target? Jan 11 13:53:44 Herrie: I'm currently investigating on whether to use a MAC on a mobile OS also using libhybris (you have to guess yourself which one). I also heard from some hw people that they currently disabled SElinux and I'm just afraid that andorid drivers may at some point require it being active. Jan 11 13:54:41 @Flohack: re cmdline, you know there is workaround.. do you? Jan 11 13:54:44 AppArmor looks much friendlier than SElinux, but it sucks to have certain parts using the latter Jan 11 13:55:14 @Flohack: actually even that patch is for your device >_< Jan 11 13:58:22 @Flohack : see 2nd paragraph : https://wiki.ubuntu.com/Touch/ContainerArchitecture Jan 11 14:00:04 @bshah> @Flohack: actually even that patch is for your device , I applied already yes ^^ thx Jan 11 14:00:26 @Herrie, S3 Neo at the moment. Was the same with S3, S3 LTE and HTC One X 😆 Jan 11 14:00:48 But this time even with the patch it does not work, or my patch does not work 😆 Jan 11 14:08:32 I am loosing my sanity over audio -.0 Jan 11 14:11:34 Me too.. @bhushanshah what can be the reason for "Found audio cards... none" or similar in Kernel log Jan 11 14:11:42 No driver? ^^ Jan 11 14:12:39 I am not sure.. my issue at moment is different though Jan 11 14:12:50 I am loosing sanity over call audio Jan 11 14:23:10 schmittlauch and Herrie: The Linux kernel only allows one Linux Security Module (SELinux and Apparmor are both LSMs) active at a time. You can only have one. No Android driver should require SElinux be enabled. Jan 11 14:23:42 You do still need the sepolicy to be available, or the build system gets upset. It's not used. Jan 11 14:26:23 @UniversalSuperBox, Well I am fighting a few things on my device and decided to build with SELinux structures, but then turn it off at boot time. This should work to give some kernel calls inside that a blob (mostly not a driver) will maybe require Jan 11 14:27:15 Only one may be active. You can build SElinux, AppArmor, TOMOYO, Smack, AND Yama in if you really want to. Jan 11 14:29:12 es Jan 11 14:29:14 yes ^^ Jan 11 14:35:57 thx for your experiences Jan 11 14:43:54 @BlueKenny, Same problem Jan 11 15:30:05 @Herrie, With selinux you need fix missing yourself Jan 11 17:04:39 Anyone up for fixing the installation script of UBPorts?? Jan 11 17:19:02 @Mr_Doge, @UniversalSuperBox is on the case maybe :) Jan 11 17:49:07 Wouter Jansen was added by: Wouter Jansen Jan 11 19:13:01 RavengamerSpace was added by: RavengamerSpace Jan 11 19:18:27 @Mr_Doge, Explain Jan 11 19:19:17 @JBBgameich, I'm still scratching my head how to use halium-devices, are you around? Jan 11 19:24:52 @UniversalSuperBox, It had a same error as the stock halium script had (the one which is mentioned in the docs).... allocation error... So i tried rootstock installer from UBPorts docs, halium script from the docs, then one which @vanyasem provided.. with and without busybox... @jbb's script was able to install.. but with a corrupted system image... And also had troubles setting of the ssh connection.. since ut-halium-compact was able to boot.. but Jan 11 19:24:53 connection was refused Jan 11 19:25:06 We that's a lot of typing Jan 11 19:29:10 is it needed apparmors patch in halium-7.1 ? Jan 11 19:38:06 @Walid, well you need apparmor for Ubuntu Touch, has nothing to do with halium ;) Jan 11 19:42:03 should test_egl work btw? Jan 11 19:42:25 no, never worked for me :) Jan 11 19:42:42 @Flohack, no Jan 11 19:42:44 segfault? Jan 11 19:42:47 only egl config Jan 11 19:42:59 hmm strange in ubports old times this was working if I remember Jan 11 19:43:08 test_hwcomposer is start point to be sure that graphive is good Jan 11 19:43:36 I know but this gives me more headaches... hmm your mm.so was for Marshmallow right? Which android version is that Jan 11 19:43:42 maybe I need lp.so? Jan 11 19:44:46 mm.so work good with ubports 5.1 and halium Jan 11 19:45:37 hmm ok Jan 11 19:45:43 I got 48 egl configs ^^ Jan 11 19:48:00 @Mr_Doge, Well first, it's not the script, it's your phone Jan 11 19:48:11 Second, ssh probably wasn't enabled. Jan 11 19:48:16 IT WORKS WORKS WORKS Jan 11 19:48:18 can you see log in var/log/lightdm Jan 11 19:49:02 image :) Jan 11 19:49:42 wait Jan 11 19:51:38 (Video, 0s)https://irc.ubports.com/dT5Xydex/file_3721 Jan 11 19:52:23 @doniks_, Yeah, I am. Basically merge this PR, repo sync to download the manifests and then use `. halium/devices/setup "device"` to check out the manifest of a device Jan 11 19:52:30 https://github.com/Halium/android/pull/8 Jan 11 19:52:56 So not everyone who wants to build an image for a device has to port it again. Jan 11 19:53:06 Where are my credits :P Jan 11 19:53:11 ohhh, you source it? `. halium/devices/setup "device" Jan 11 19:53:36 you can, it should save you running source build/envsetup and lunch yourself Jan 11 19:53:51 you can just run the script too, but then you will have to do that steps yourself afterwards Jan 11 19:53:55 and you do it from one level ABOVE the halium dir Jan 11 19:53:57 @Flohack, yeahhhhh, thats good Jan 11 19:54:13 @doniks_, It should be callable from everywhere Jan 11 19:54:23 dont think so Jan 11 19:54:35 Are you using 5.1 or 7.1? Jan 11 19:54:51 @Walid, so what next? Jan 11 19:54:58 oh wait Jan 11 19:55:01 7.1 Jan 11 19:55:02 @doniks_, The 5.1 version is not yet very clever. A few commits would need to be merged over from 7.1 Jan 11 19:55:08 @UniversalSuperBox, 😐.. idk but script did some black magic thing to setup the ssh... Yeah i remember it failed to some dkpg command with openssh.. Jan 11 19:57:02 It goes TWO levels up from the DEVICES_ROOT folder Jan 11 19:57:04 @Flohack, you work on halium-5.1? see log in /var/log/lightdm , also what rootfs did you use Jan 11 19:57:04 https://github.com/doniks/halium-devices/blob/halium-7.1/setup#L7 Jan 11 19:57:22 that is ABOVE the halium folder Jan 11 19:57:48 Oh, it shouldn't. DEVICES_ROOT is REPO_ROOT/halium/devices Jan 11 19:57:57 ok, it is :) Jan 11 19:58:09 It's the root of the android tree Jan 11 19:58:20 @Walid, reference rootfs by bhushan, I am still only in halium guide Jan 11 19:58:35 Hi all, I have a question to ask. How can we compile halium or android project using GPU so that it compiles in no time.. Is that possible ? Jan 11 19:58:44 shouldn't REPO_ROOT = ./halium ? Jan 11 19:59:11 ok try now xenial rootfs maybe will work, also u can use vivid to test Jan 11 19:59:44 @doniks_, repo root should be the folder you initially run repo init in Jan 11 20:00:11 the one where there is a .repo right? Jan 11 20:00:24 @Walid, shall I switch to ubports now? Jan 11 20:00:25 yeah Jan 11 20:01:07 @Flohack, yes u can build ubports-5.1 it will work thought Jan 11 20:01:13 oki Jan 11 20:01:51 @JBBgameich, I did it like we discussed the other day, like "right now" here : https://gist.github.com/doniks/4370dc9790f98f66f6e7d00ba182266c#file-gistfile1-txt-L10 Jan 11 20:02:02 @donR, It doesn't take any time... 20-25 minutes to compile all .. Jan 11 20:02:06 but that puts REPO_ROOT one level too high Jan 11 20:06:16 oh, sorry, there's one mistake in there. the halium-devices repo shouldn't be in ./halium-devices but in ./halium/devices Jan 11 20:06:33 the folder where hybris-boot is inside too Jan 11 20:07:51 you mean ONE level lower than the REPO_ROOT, or you mean TWO Jan 11 20:08:54 also, I'm trying now with one ../ less and try to source it, but I think you can't source AND pass a parameter $0, or can you Jan 11 20:13:45 In your tree, there is a halium folder. Inside that folder there is libhybris and hybris-boot. Just add another folder called devices there Jan 11 20:14:22 So it's in `$TREE_ROOT/halium/devices` Jan 11 20:18:34 I've updated the gist, could you check? Jan 11 20:18:53 added cd halium cd .. and devices as target for the clone Jan 11 20:19:17 As an insurance policy, you might want to Jan 11 20:19:33 olddir=`pwd` … cd newdir … cd $olddir Jan 11 20:20:12 stefanomelchior was added by: stefanomelchior Jan 11 20:20:20 I don't think so ... it needs to be in exactly THAT folder "halium" not any other "newdir" ... Jan 11 20:21:48 I mean, don't work in relatives when you're going to be moving around the tree a lot. Jan 11 20:21:54 It's not very readable. Jan 11 20:22:05 oh ok Jan 11 20:24:00 so eitherway, I think I got the folder structure now, but I'm confused by the sourcing Jan 11 20:24:27 if I `source ./halium/devices/setup`, then I can't pass the DEVICENAME Jan 11 20:24:45 Well, no... Because you're sourcing the file, not running it Jan 11 20:24:55 if I run `./halium/devices/setup DEVICENAME`, then I need to do the lunch stuff afterwards anyway Jan 11 20:25:01 Ok, try with running Jan 11 20:25:17 I remember having it working with sourcing, but I might be wrong Jan 11 20:25:19 ok, lets remove lunch, etc from the script? Jan 11 20:25:47 it almost looks to me the script could be reduced to Jan 11 20:26:05 If you use `.` instead of `source`, does it work then? Jan 11 20:26:26 cp ./halium/devices/DEVICENAME/manifest.xml .repo/local_manifests/manifest.xml Jan 11 20:26:29 lemme try Jan 11 20:27:32 Alternatively, you could probably have the script ask for input when sourcing it Jan 11 20:28:05 I'll look into that tomorow. Sounds like a good Idea Jan 11 20:28:28 Although this script was initially made for CI usage ... Jan 11 20:28:37 hmm Jan 11 20:28:52 Take input with environment variables then Jan 11 20:29:28 export DEVICE="potter" … . setup.sh Jan 11 20:29:57 👍 … Nobody is currently using it on a CI, so there is no real problem anyway Jan 11 20:30:09 But this sounds like a solution working for everyone Jan 11 20:31:19 Env vars are something that should be very familiar for CI users anyway Jan 11 20:32:07 uh, sorry, I might have been wrong, $@ DOES actually pass a parameter, both with . and source Jan 11 20:32:19 but $0 is bash when I . or source Jan 11 20:32:24 Only in Bash, though Jan 11 20:32:30 ah Jan 11 20:32:58 So if you're requiring Bash, no problem. If your shebang is /bin/sh though... Jan 11 20:33:41 sure, but I think $0=bash messes with this line Jan 11 20:33:43 DEVICES_ROOT="$(dirname "$(readlink -f "${0}")")" Jan 11 20:33:52 uh Jan 11 20:34:12 I think I'd put $0 into another variable before that point for readability, as well. Jan 11 20:34:14 again, I think we could make this so much simpler and stabler Jan 11 20:34:19 just one cp ?! Jan 11 20:34:39 everything else can go in the README Jan 11 20:34:41 Like this it can be run from everywhere Jan 11 20:34:46 I'm a stickler for code readability don't hate me. ._. Jan 11 20:35:02 And does not mess around if run from the wrong path Jan 11 20:35:17 @JBBgameich, but we were just talking about not RUNNING, but SOURCING it right?! Jan 11 20:35:41 You can always expect people to do the wrong thing with the right code Jan 11 20:36:11 @ErnyTech, https://github.com/Halium/android_build Jan 11 20:36:31 @UniversalSuperBox, I'm ALL for readability. I think less code is one way to achieve that. Don't make your scripts too smart Jan 11 20:36:58 Btw, I think most lines in this script are for making it more fail safe Jan 11 20:37:14 Like, looking if the device folder does really exist before using it Jan 11 20:37:33 People might misspell the codenames for example Jan 11 20:38:05 sure. then cp would throw an error Jan 11 20:38:14 But one thing is too much for sure, one "new" in a comment Jan 11 20:38:15 either way, I guess I got it now Jan 11 20:38:32 👍 Jan 11 20:38:50 Do emojis even arrive on IRC btw? Jan 11 20:39:08 :) that was a thumbs up Jan 11 20:39:25 Ok :) Jan 11 20:40:31 Guys shall I do 1 repo = 1 device manifest? Jan 11 20:44:13 Oneplus 3 lxc work!!! Jan 11 20:45:11 finally! I also want to try kde mobile when everything is ready Jan 11 20:46:09 has anyone managed to make the mobile data network work? Jan 11 20:47:27 @bhushanshah, guess what, pm-rootfs-20171219-163639.tar.gz works fine on my deb Jan 11 20:47:51 I'm gonna retest now to be sure that 1220 does actually really fail and I didn't screw it up Jan 11 20:50:30 Proud to have my first port ticket done: https://github.com/Halium/projectmanagement/issues/41 Jan 11 20:50:32 @Flohack, I'd also love to know that answer. Put differently, can you reuse (parts of) a repo folder for multiple ports Jan 11 20:50:57 @doniks_, Ok nvm I can do it later ^^ Jan 11 21:02:20 jup affirmative I can boot the pm rootfs 20171219 just fine on my port but 20171220 stays black Jan 11 21:02:34 how do I disect what broke? Jan 11 21:03:01 ssh works Jan 11 21:21:04 (Photo, 753x755) https://irc.ubports.com/wSIDEyKI/file_3723.jpg Jan 11 21:21:06 Hi everyone, … I try to port Halium on my Huawei P8 Lite but I'm stuck because I can't found the xml file Jan 11 21:37:46 you need to write it yourself Jan 12 00:29:14 @doniks_, I've thought on what broke... I'd try latest CI rootfs and see if it works.. Jan 12 00:29:24 Wait let me give link Jan 12 00:35:34 @doniks_, http://mobile.neon.pangea.pub:8080/view/All/job/generic_rootfs/68/artifact/result/halium-rootfs-generic.tar.gz … (Even if this says halium rootfs it's pm rootfs) **** ENDING LOGGING AT Fri Jan 12 03:00:02 2018