**** BEGIN LOGGING AT Sun Apr 29 03:00:03 2018 Apr 29 10:55:08 Rip telegram 2013-2018 Apr 29 11:34:07 Has something happened to Telegram? Apr 29 11:35:01 big power outage in one of the central (amsterdam) data centres Apr 29 11:35:17 knocked telegram offline in big parts of europe Apr 29 11:36:30 also in Asia, west usa, australia, russia, arabian emirates, africa... pretty much everywhere Apr 29 11:36:37 Oh Apr 29 11:36:56 I haven't read reports about latin america Apr 29 11:45:09 @mayltonfnds Hello, how did you fare with those kernel config changes? Apr 29 11:45:40 I had some problems Apr 29 11:45:57 I'm installing rootfs again right now Apr 29 11:46:42 As long as i use my daily phone to it, I have to restore my system when I need it Apr 29 11:49:51 Yes, I've had the same thing, I had my phone out of service for about a week and I just restored it yesterday Apr 29 11:55:41 The bad thing is that you have to do everything again every time you get back to work on halium Apr 29 11:56:04 The good thing is that now I am sure I can login in ssh Apr 29 11:56:20 What I did is back up my rootfs.img and system.img using `adb pull` so I can just `adb push` it back again (and install `hybris-boot` again of course) Apr 29 11:56:22 Which I couldn't before Apr 29 11:56:35 Oh, nice Apr 29 12:01:27 My current problem is that lxc-android container is not running Apr 29 12:02:47 https://paste.ubuntu.com/p/2NkSSWZPrY/ Apr 29 12:03:34 try `lxc-checkconfig` again Apr 29 12:04:05 there's a problem Apr 29 12:04:12 try `lxc-checkconfig` again (if you missed prior message( Apr 29 12:04:23 CONFIG_IP6_NF_TARGET_MASQUERADE: missing Apr 29 12:04:39 This setting is already set in my defconfig Apr 29 12:04:42 Interestingly I had the same problem, but it didn't affect me starting LXC Apr 29 12:04:57 I wonder if that's a bug in lxc-checkconfig Apr 29 12:05:03 i don't know it that's the reason though Apr 29 12:05:08 Is there anything else missing ? Apr 29 12:06:09 https://paste.ubuntu.com/p/tBzr69kbxG/ Apr 29 12:06:29 only user namespace Apr 29 12:06:40 That's on par with mine (User namespace apparently isn't a problem if it's missing) Apr 29 12:06:51 ye Apr 29 12:08:59 would you be able to post the result of `PAGER=cat systemctl status lxc@android -l` ? Apr 29 12:10:26 sure Apr 29 12:10:26 https://paste.ubuntu.com/p/H28Xgn3SSD/ Apr 29 12:11:34 Well, we have a couple of errors in this output Apr 29 12:12:29 Notably it's similar (but not the same as :/) https://docs.halium.org/en/latest/porting/debug-build/debug-android-userspace.html#lxc-android Apr 29 12:12:35 it's failing to allocate memory, so it can't create cgroups Apr 29 12:13:10 nvm it's not the same error as that, it doesn't involve netcls Apr 29 12:13:13 @reivilibre, and my kernel is 3.18 Apr 29 12:19:07 maybe try this: `lxc-start -n android -L /tmp/lxc.log -l DEBUG` and see if we get any more interesting messages Apr 29 12:24:18 https://paste.ubuntu.com/ Apr 29 12:24:47 https://paste.ubuntu.com/p/jN28TPy2n4/ Apr 29 12:25:20 OK I clearly don't know the magic incantation to run an LXC container alone Apr 29 12:25:39 πŸ˜‚ Apr 29 12:25:53 maybe we can try a different route first and see if anything turns up from that Apr 29 12:26:13 first clear the kernel message buffer with `dmesg -c` Apr 29 12:26:32 then try `systemctl start lxc@android` again, give it time to fail, then post the output of `dmesg` Apr 29 12:28:27 I got a lot of messages like this Apr 29 12:28:29 [ 29.232794] Nested SchedTune boosting groups not allowed Apr 29 12:29:09 anything else ? Apr 29 12:29:21 Ye Apr 29 12:29:34 and is that from running `dmesg -c` or `dmesg` after trying to start it? Apr 29 12:29:37 It's a enormous output Apr 29 12:29:47 from dmesg Apr 29 12:30:13 if you run `dmesg -c` then `dmesg` immediately after, is it empty? Apr 29 12:30:49 yes Apr 29 12:31:43 then you did `systemctl start lxc@android`, then `dmesg`, and the output is massive? Apr 29 12:32:03 yes Apr 29 12:32:06 look Apr 29 12:32:25 https://paste.ubuntu.com/p/bPjXFrg8ms/ Apr 29 12:32:55 this is what i got a few seconds after dmesg -c without systemctl start lxc@android Apr 29 12:33:07 now look it with systemctl start lxc@android Apr 29 12:39:21 https://paste.ubuntu.com/p/sNjKTs5Pgr/ Apr 29 12:39:55 I see what you mean, that's certainly a lot of that one message Apr 29 12:41:02 ye Apr 29 12:42:52 there's something interesting Apr 29 12:44:21 ya? Apr 29 12:44:36 once i tried systemctl status lxc@android Apr 29 12:44:44 and it was successfully working Apr 29 12:44:55 but it stopped a few seconds later Apr 29 12:45:02 sorry Apr 29 12:45:05 Yeah it might be because it didn't fall over immediately Apr 29 12:45:14 I meant . Apr 29 12:45:27 systemctl unmask lxc@android && systemctl start lxc@android Apr 29 12:45:38 [Edit] I meant Apr 29 12:47:50 Do you possibly have AppArmour compiled into your kernel? Apr 29 12:48:11 I don't know Apr 29 12:48:26 if you run `apparmor_status` does it tell you anything of the sort? Apr 29 12:48:36 or try `/sbin/apparmor_status` (some binaries seem to be there) Apr 29 12:50:04 -bash: /sbin/apparmor_status: No such file or directory Apr 29 12:50:22 looks like there is no file system mounted here Apr 29 12:50:36 Like, there's nothing when I try ls Apr 29 12:50:44 OK well I haven't seen enough evidence to suggest that AppArmour is in any way involved, so I'll try and see if we can coax LXC to giving us more output Apr 29 12:51:31 Hmm, as far as I remember, I had an /sbin in mine.. Apr 29 12:51:57 no idea if apparmor_status is included though Apr 29 12:52:15 ye Apr 29 12:53:59 does /var/lib/lxc exist? Apr 29 12:54:47 ye Apr 29 12:55:43 can you `cd /var/lib/lxc/android` and see if there is a config file in that directory? Apr 29 12:55:56 not sure what it would be called Apr 29 12:58:25 ls /var/lib/lxc/android/ … config pre-start.sh rootfs Apr 29 12:58:41 eyyy, `config` looks promising Apr 29 12:59:01 haha Apr 29 12:59:32 can you peek in there and see if it looks like `lxc.blahblah = blahblah` Apr 29 13:00:18 Like this? Apr 29 13:00:21 file /var/lib/lxc/android/config … /var/lib/lxc/android/config: ASCII text Apr 29 13:00:37 try `cat config | grep lxc.log` Apr 29 13:01:29 and after that? Apr 29 13:01:33 was that empty? Apr 29 13:01:40 no output Apr 29 13:01:52 maybe can you just post the full file ? :-) Apr 29 13:02:27 root@localhost:/# cat /var/lib/lxc/android/config | grep lxc.log … root@localhost:/# Apr 29 13:02:28 ? Apr 29 13:02:52 just /var/lib/lxc/android/config (you can transfer it to your PC with `adb pull /var/lib/lxc/android/config` if you want) Apr 29 13:04:10 root@localhost:/# /var/lib/lxc/android/config … -bash: /var/lib/lxc/android/config: Permission denied Apr 29 13:04:22 sorry, use `cat` to read it Apr 29 13:05:43 https://paste.ubuntu.com/p/pPjrBScHHT/ Apr 29 13:07:01 yeah that's looking like what we needed Apr 29 13:07:22 yaaay Apr 29 13:08:25 edit it and add this line: `lxc.log.level = 1` Apr 29 13:08:43 at the end? Apr 29 13:08:57 yeah, at the end will be fine Apr 29 13:09:12 can I edit it from the ssh? Apr 29 13:09:56 You could use `vi` but it's probably easier to do `echo 'lxc.log.level = 1' >> /var/lib/lxc/android/config` Apr 29 13:10:17 sure πŸ˜‚ Apr 29 13:10:26 I didn't know I could do it Apr 29 13:10:38 Lots of people use `vi` for many years... because they can't figure out how to leave it :-) Apr 29 13:11:03 done Apr 29 13:11:20 now try starting lxc@android again Apr 29 13:12:02 done Apr 29 13:12:23 check its status now Apr 29 13:13:04 https://paste.ubuntu.com/p/DZ7v6JvWHq/ Apr 29 13:13:25 looks like that line doesn't work Apr 29 13:14:09 well that's a bit of a shame Apr 29 13:14:30 maybe you will have to go into `vi` and remove that line Apr 29 13:15:22 why no use nano? (if it is there at all) Apr 29 13:15:27 done Apr 29 13:15:34 `nano` wasn't there at least for me Apr 29 13:15:42 It isn't Apr 29 13:15:44 I resorted to `ed` and then `vi` when `ed` wasn't there Apr 29 13:16:00 vi is fine Apr 29 13:16:06 I learned how to use it Apr 29 13:16:26 ok, I still haven't learnt >.> Apr 29 13:16:29 Oh good, you know more than me about vi then, I can just about make simple changes, write them, and quit :-P Apr 29 13:16:55 @reivilibre, me too πŸ˜‚πŸ˜‚ Apr 29 13:18:30 well this leaves us in a situation, because I'm certainly not an LXC/cgroups mage, and I don't know how we can get it to give us more detailed information Apr 29 13:19:58 I notice that systemd does tell us what command it ran... maybe we can try and copy it Apr 29 13:21:02 do you mean this '--logfile and --logpriority options' ? Apr 29 13:21:19 yeah I think I see how we might be able to get some more output Apr 29 13:21:37 try doing this for me: `find -name "lxc@android.service"` Apr 29 13:22:16 let me know if you get any hits, it's probably going to be /etc/systemd/blah/lxc@android.service Apr 29 13:23:16 @reivilibre, ./etc/systemd/system/multi-user.target.wants/lxc@android.service Apr 29 13:23:46 if you restart lxc manually, android image gets permanently corruputed Apr 29 13:23:49 and you have to reflash it Apr 29 13:23:53 never restart lxc manually Apr 29 13:24:11 Hmm, that sounds dangerous. What's the suggested route? Apr 29 13:24:27 Is it fine if we add some arguments to the lxc@android service file? Apr 29 13:24:40 why Apr 29 13:24:42 you don't need that Apr 29 13:24:48 We're trying to get more logging output Apr 29 13:24:52 fix your container, don't hack it Apr 29 13:24:57 you have enough logging info already Apr 29 13:25:20 Any suggestions for the error https://paste.ubuntu.com/p/H28Xgn3SSD/ ? Apr 29 13:25:27 dmesg, mount, systemctl, systemctl statux lxc@android, lxc-checkconfig Apr 29 13:25:39 output of those will give you enough info for a fix Apr 29 13:26:10 [Edit] dmesg, mount, systemctl, systemctl status lxc@android, lxc-checkconfig Apr 29 13:26:50 Yes, but systemctl status lxc@android doesn't give all loglevel messages (it'd be good to have level 1 (debug) messages, no?) Apr 29 13:27:13 you don't really need that Apr 29 13:27:40 What do I/does mayltonfnds need then? :-P The error is a mystery to me Apr 29 13:27:56 pastebin output of commands i gave you above Apr 29 13:28:42 Just a second Apr 29 13:30:43 @vanyasem any details why restarting manually corrupts the android image, though? That seems a bit dangerous yet not mentioned in the docs as far as I saw Apr 29 13:31:27 i don't know why, it's just a fact. search the chat on telegram to find more info Apr 29 13:31:59 that might explain why my rootfs.img and system.img once vanished by themselves xD Apr 29 13:33:48 just a fool question: do you think my .rules might me something related to it? Apr 29 13:37:05 @vanyasem here you have my dmesg output https://paste.ubuntu.com/p/MbVPQzb643/ Apr 29 13:38:21 mount output: https://paste.ubuntu.com/p/bDDRdpHKcm/ Apr 29 13:39:17 systemctl output: https://paste.ubuntu.com/p/N7Tvb4ZVpw/ Apr 29 13:40:51 systemctl status lxc@android output https://paste.ubuntu.com/p/kTb6KPzkXQ/ Apr 29 13:41:51 lxc-checkconfig output https://paste.ubuntu.com/p/jscG63MPjM/ Apr 29 13:42:44 you may want to provide `PAGER=cat systemctl status lxc@android -l` so you don't get the lines chopped off Apr 29 13:42:58 OBS: CONFIG_IP6_NF_TARGET_MASQUERADE is SET in my defconfigs. but somehow it shows as missing in that output Apr 29 13:43:57 @reivilibre, Here you have https://paste.ubuntu.com/p/9gHzKSfSpQ/ Apr 29 13:44:21 I'm asking for @vanyasem as the chopped output is probably not as useful Apr 29 13:44:45 Oh, I see 😘 Apr 29 13:44:51 [Edit] Oh, I see Apr 29 13:45:05 @mayltonfnds, this is ok Apr 29 13:45:29 @mayltonfnds, chopped output Apr 29 13:45:38 plz send a full status Apr 29 13:45:42 [Edit] plz send a full output Apr 29 13:46:24 @vanyasem if you mean systemctl status, he mentioned it to me: Apr 29 13:46:26 https://paste.ubuntu.com/p/9gHzKSfSpQ/ Apr 29 13:46:32 no Apr 29 13:46:36 i mean `systemctl` Apr 29 13:46:37 @mayltonfnds, Here you have full output Apr 29 13:46:47 Oh, I see Apr 29 13:46:49 it's a different thing damn it Apr 29 13:47:49 sorry pal I didn't know to which one you referred to, Apr 29 13:48:13 yeah i get how IRC works :P @mayltonfnds got it Apr 29 13:48:29 Here you have full output for systemctl https://paste.ubuntu.com/p/Vz6KVdqp9M/ Apr 29 13:48:43 can you respond to individual messages or so on telegram? Apr 29 13:48:50 yeah Apr 29 13:48:53 Ahhh Apr 29 13:49:11 @mayltonfnds, and plz full output of `systemctl status` Apr 29 13:49:19 without mentioning a service Apr 29 13:49:45 oh and please link me to your device's fstab Apr 29 13:49:50 i need to check one things Apr 29 13:49:50 [Edit] i need to check one thing Apr 29 13:50:12 sounds like the professional has arrived or something :-) Apr 29 13:50:27 systemctl status https://paste.ubuntu.com/p/RhHyqjbMdq/ Apr 29 13:50:31 i took a break from halium for 2 months, i have ported 3 devices previously Apr 29 13:50:37 @vanyasem, Oh, sorry Apr 29 13:50:55 @vanyasem That's pretty good going, you seem like you know your stuff Apr 29 13:51:25 every device is different, so you can't really know everything :P but i do my best Apr 29 13:51:38 at least i will gather all required logs for bhushan if i fail to fix it myself :P Apr 29 13:52:20 My savior has come Apr 29 13:52:21 haha Apr 29 13:52:48 do you have a separate firmware partrition on your device? link me to your fstab Apr 29 13:53:59 root@localhost:~# cat /etc/fstab … # UNCONFIGURED FSTAB FOR BASE SYSTEM Apr 29 13:54:00 wth?! Apr 29 13:54:00 no, from your device tree Apr 29 13:54:04 not from the device itself Apr 29 13:54:29 it's usually in `rootdir/etc/` Apr 29 13:54:37 do you mean github link? Apr 29 13:54:41 and has a name life `fstab.qcom` or `fstab.CODENAME Apr 29 13:54:42 [Edit] and has a name life `fstab.qcom` or `fstab.CODENAME` Apr 29 13:54:43 @vanyasem, oh Apr 29 13:54:45 @mayltonfnds, yep Apr 29 13:54:59 [Edit] and has a name like `fstab.qcom` or `fstab.CODENAME` Apr 29 13:56:56 I can't find it Apr 29 13:57:03 here you have github link Apr 29 13:57:04 https://github.com/LineageOS/android_device_leeco_x2/tree/cm-14.1 Apr 29 13:57:39 Also, here you have my manifest if you need something https://gist.github.com/maylton/bc1243ce24fd0ad3646f63f8b9720d41 Apr 29 13:57:52 @mayltonfnds, thank you for finding that fstab yourself πŸ˜† Apr 29 13:58:26 I tried searching for it but nothing was found Apr 29 13:58:29 haven't you forked any of the trees? Apr 29 13:58:32 why? Apr 29 13:59:07 Well, I have most of them Apr 29 13:59:33 but I used a manifest of a friend as base Apr 29 13:59:36 weird, fstab is not there Apr 29 13:59:45 He used it for porting sailfishOS Apr 29 14:00:11 @vanyasem, I told you 😞 Apr 29 14:00:20 ookay Apr 29 14:00:58 i forgot the way to get a list of all partritions on a device tbh Apr 29 14:01:29 I may know Apr 29 14:01:32 https://github.com/TeamWin/android_device_leeco_x2/blob/android-8.1/recovery/root/etc/twrp.fstab Apr 29 14:01:34 just a second Apr 29 14:01:44 @vanyasem, okay i will just use the one from twrp tree Apr 29 14:01:47 for reference Apr 29 14:01:59 ok Apr 29 14:02:02 okay so your device has a /firmware partrition Apr 29 14:02:12 as you can see from that fstab Apr 29 14:03:16 @mayltonfnds, now take a look at your mount output Apr 29 14:03:27 neither /cache nor /firmware are mounted Apr 29 14:03:34 that's the most likely issue Apr 29 14:03:51 and as they are bind mounted into the contatiner, and it depends on them, it fails to starty Apr 29 14:03:56 [Edit] and as they are bind mounted into the contatiner, and it depends on them, it fails to start Apr 29 14:04:13 oh Apr 29 14:06:28 any idea of how to get them mounted? Apr 29 14:08:21 i am trying to recall the fix, i was off for 2 months :P i remember someone facing that issue before Apr 29 14:09:12 this? http://docs.halium.org/en/latest/porting/build-sources.html?highlight=fstab#include-your-device-in-fixup-mountpoints Apr 29 14:09:29 i remember UBports having an issue with partritions not being mounted if they have `context=` in fstab, though i am not sure if that's related (and you don't seem to have an fstab at all) Apr 29 14:10:02 @dohniks, I did that already Apr 29 14:10:17 including firmware partition? Apr 29 14:10:19 How did you do the fixup-mountpoints withhout a fstab file? :-P Apr 29 14:10:29 Those selinux context things should already be removed by the halium-devices config script Apr 29 14:10:32 @mayltonfnds, have you PRed it upstream? Apr 29 14:10:35 i don't see your commit Apr 29 14:10:43 if not, please do it now Apr 29 14:10:45 @dohniks, not sure Apr 29 14:11:02 please open a pull request with your changes on github Apr 29 14:11:02 right now Apr 29 14:11:13 i will review it Apr 29 14:11:23 https://github.com/Halium/hybris-boot/pulls Apr 29 14:11:27 here's the repo Apr 29 14:13:46 Ok Apr 29 14:14:00 you can also look this Apr 29 14:14:04 https://forums.ubports.com/topic/1169/porting-halium-to-leeco-le-max2-aka-x2-x820 Apr 29 14:14:28 There is everything I've done so far Apr 29 14:15:05 please don't post diffs in a blogpost, properly push them to your repo Apr 29 14:15:09 [Edit] please don't post diffs in a blogpost, properly push them to your repo's fork Apr 29 14:15:43 also better use JBB's script to install Halium if rootstock (default) doesn't work for you Apr 29 14:15:52 https://github.com/JBBgameich/halium-install this one Apr 29 14:16:08 it's the most stable and tested one Apr 29 14:16:21 I see Apr 29 14:17:42 The changes you need me to show are related to fstab? Apr 29 14:17:47 also i suggest you to join https://t.me/halium_notes Apr 29 14:18:00 @mayltonfnds, they are related to your mounts, yes Apr 29 14:18:28 i want you to upload all of your changes to github, including fixup-mounpoints, your kernel, and your device tree (don't fork vendor, there's no need for it) Apr 29 14:18:39 i also want you to fill in the device info in the docs if you haven't done so already Apr 29 14:19:01 and to open an issue in https://github.com/Halium/projectmanagement/issues if you haven't done so already Apr 29 14:19:20 Ok Apr 29 14:19:20 i will give you some time to do everything i've said, there's no hurry Apr 29 14:19:27 ping me if you get stuck Apr 29 14:19:31 first things first Apr 29 14:19:45 @vanyasem, Pornhub tf Apr 29 14:19:59 I'm not a master at doing these stuff Apr 29 14:20:12 @alamo18, it's an official halium channel for undocumented notes πŸ€·β€β™‚οΈ Apr 29 14:21:21 first i have to fork hybris-boot right? Apr 29 14:21:42 yeah, do it step by step as i said it Apr 29 14:22:00 you can mention me in your pull request, which will notify me and will speed things up Apr 29 14:22:04 (@vanyasem on GitHub) Apr 29 14:22:14 ok Apr 29 14:43:53 Just a thought: I have to pull request in hybris-boot 10.1 brach? Apr 29 14:44:08 I can't make a pull request in master branch Apr 29 14:44:13 can you not? Apr 29 14:44:20 @mayltonfnds, there's no such branch in the repo lol Apr 29 14:44:28 I don't know Apr 29 14:44:28 you forked the wrong repo Apr 29 14:44:31 I just PR'd to master https://github.com/Halium/hybris-boot/pull/48 :S Apr 29 14:44:35 Did I? Apr 29 14:44:47 @mayltonfnds, yes, you did. now fork the right repo and be more careful next time Apr 29 14:44:53 you have to PR to master Apr 29 14:45:20 @reivilibre, I forked this one Apr 29 14:45:39 are you familiar with git? Apr 29 14:45:40 (Photo, 653x899) https://irc.ubports.com/Iq0oINnx.png Apr 29 14:45:40 there is no hybris-10.1 branch on this repo Apr 29 14:46:43 (Photo, 1366x768) https://irc.ubports.com/UjduVj6N.png Apr 29 14:47:05 you need to fork **Halium**'s hybris-boot, not **mer** Apr 29 14:47:28 My God Apr 29 14:54:28 Do you need help with using `git`? Apr 29 14:55:13 I think so πŸ˜‚ Apr 29 14:55:32 But i don't want to flood the group Apr 29 15:01:32 I think I got it Apr 29 15:03:44 https://github.com/Halium/hybris-boot/pull/49 Apr 29 15:05:55 @mayltonfnds, fix it now Apr 29 15:06:09 @vanyasem, excuse you Apr 29 15:06:18 @UniversalSuperBox, πŸ‘€ Apr 29 15:06:32 dalton do you need help with the five ex Apr 29 15:07:05 Always. But I think doniks discovered the problem is a kernel option Apr 29 15:07:48 @UniversalSuperBox, have you fixed 4.4 kernel Apr 29 15:07:50 in halium-boot Apr 29 15:08:01 I haven't touched a device with kernel 4.4 ever Apr 29 15:08:08 we stopped somewhere at that point 2 months ago Apr 29 15:08:13 up to continue working on that? Apr 29 15:08:38 iirc it was configfs that was not supported Apr 29 15:08:54 As I think hybris-usb supports configfs, you can likely copy the relevant parts from there. Apr 29 15:09:05 that's what i was playing with Apr 29 15:09:14 i never finished it, but i will soon Apr 29 15:09:25 dalton just reminded me of that Apr 29 15:09:52 @vanyasem, What do you mean by emmc partition? Apr 29 15:10:11 emmc filesystem Apr 29 15:10:19 you only need vfat and ext4 partitions Apr 29 15:10:41 you can't mount emmc, so you don't need to include them Apr 29 15:11:04 Do you mean those sdX partitions? Apr 29 15:11:06 by emmc do you mean f2fs? Apr 29 15:11:18 No, the partition type is called emmc Apr 29 15:11:25 I haven't heard of that one Apr 29 15:11:33 Android is weird Apr 29 15:11:40 yes, it really is Apr 29 15:11:55 vold knows how to handle it, we don't... so we don't handle it Apr 29 15:12:20 I did not get what I am supposed to do actually Apr 29 15:12:37 @UniversalSuperBox you port 'potter', right? Did `echo 1 > /dev/wcnss_wlan` work for you? (I'm porting the non-plus Moto G5) Apr 29 15:12:55 You need to do both that and the other thing Apr 29 15:13:05 @mayltonfnds, Just remove the lines that have `emmc` in them Apr 29 15:13:11 The echo sta > thing Apr 29 15:13:24 @UniversalSuperBox, that guy has no fstab in the device repo btw Apr 29 15:13:27 I assume you didn't get an error on the `echo 1` thing about 'bad address' though? Apr 29 15:13:31 @UniversalSuperBox, I did? Apr 29 15:13:32 how do we work with that? @UniversalSuperBox Apr 29 15:13:36 @reivilibre, Yeah, I did Apr 29 15:13:39 @vanyasem, Never had to Apr 29 15:13:49 @dohniks, Didn't you turn off apparmor and everything magically worked? Apr 29 15:13:54 @UniversalSuperBox, same. twrp has an fstab Apr 29 15:14:04 yoink Apr 29 15:14:06 but it's completely different from what i see in fixup mountpoints Apr 29 15:14:18 am i crazy or is something wrong here Apr 29 15:14:47 @UniversalSuperBox, oh that. yeah I needed to turn some apparmor config off to make pm happy again Apr 29 15:16:08 I can't see anything like emmc https://github.com/Halium/hybris-boot/pull/49/files Apr 29 15:16:25 @mayltonfnds, you're looking at the wrong thing Apr 29 15:16:30 Sorry. i might be blind or totally noob Apr 29 15:16:47 https://github.com/TeamWin/android_device_leeco_x2/blob/android-8.1/recovery/root/etc/twrp.fstab Apr 29 15:16:49 look here Apr 29 15:16:53 for partition types Apr 29 15:16:56 and remove emmc ones Apr 29 15:17:21 you only need system, cache, userdata and modem Apr 29 15:17:46 Oh Apr 29 15:17:49 Now i see Apr 29 15:18:32 So I have to change my fix-mountpoints with that partitions right? Apr 29 15:18:43 instead of those i used before? Apr 29 15:18:48 just remove all emmc ones Apr 29 15:18:52 and update the rp Apr 29 15:18:54 [Edit] and update the pr Apr 29 15:19:22 @vanyasem, firmware? Apr 29 15:19:38 @dohniks, modem is firmware Apr 29 15:19:41 on that device Apr 29 15:19:42 ah Apr 29 15:28:04 @vanyasem, Done Apr 29 15:28:52 LGTM? Apr 29 15:29:08 'looks good to me' Apr 29 15:29:27 Oh, great πŸ˜‚ Apr 29 15:29:32 thanks Apr 29 15:29:40 English is not my native language Apr 29 15:29:44 np Apr 29 15:30:16 @mayltonfnds, English is not my native as well, no need to be ashamed of that. I am Russian :P Apr 29 15:30:18 merged Apr 29 15:30:46 Great! Apr 29 15:30:54 @vanyasem, Thanks Apr 29 15:31:40 Now do I have to push my leeco_x2.xml manifest to github? Apr 29 15:32:04 @mayltonfnds, yep. step-by-step Apr 29 15:32:10 yes, you need to fork Halium/halium-devices Apr 29 15:32:43 halium/libhybris/compat/camera/camera_compatibility_layer.cpp:54:35: fatal error: gui/NativeBufferAlloc.h: No such file or directory … #include … ^ … I get this when trying to build for sony nicki (trying to build in fact), using cm trees for that device + ha Apr 29 15:32:43 lium 5.1 Apr 29 15:32:56 sorry, IRC Apr 29 15:33:07 I've read somewhere it causes problems on android 6+ but I'm doing cm12.1 Apr 29 15:33:46 [Edit] I get this when trying to build for sony nicki (trying to build in fact), using cm trees for that device + halium 5.1 Apr 29 15:33:49 https://pastebin.com/WUp1FnDM Apr 29 15:35:33 reivilibre, /dev/block/bootdevice/by-name/metadata ? Apr 29 15:35:53 i don't see that anywhere in your fstab Apr 29 15:36:01 assuming i am looking at the right one https://github.com/Wzedlare/android_device_motorola_cedric/blob/cm-14.1/rootdir/etc/fstab.qcom Apr 29 15:36:46 @VeryOriginalUsername, Does your device not have a 7.1 tree at all? Apr 29 15:36:47 D'oh, I feel stupid, it was actually text from the line before wrapping-round onto the next Apr 29 15:36:54 will remove that line :-) Apr 29 15:37:02 @UniversalSuperBox, it has a messy one, with some things branded as cm and some as lineage Apr 29 15:37:16 reivilibre, that's what code review is for. it's ok Apr 29 15:37:31 yeah :-) a world without code review... would be a scary world Apr 29 15:39:52 @mayltonfnds, Shark on irc ? Apr 29 15:40:12 @mayltonfnds, [Edit] Shark from irc ? Apr 29 15:40:21 @UniversalSuperBox, should I try 7.1 though? Apr 29 15:40:55 @VeryOriginalUsername, If it is there .. then that should be your first choice Apr 29 15:41:02 I don't really know... I think you've done this enough to bring a tree up pretty fast Apr 29 15:41:16 So I don't think it'd be a significant undertaking to at least try it Apr 29 15:41:51 well I have this laziness phase now since I have 11 days off school 😜 Apr 29 15:42:12 reivilibre, merged Apr 29 15:42:18 good work, keep it up Apr 29 15:42:22 @vanyasem ta! Apr 29 15:42:38 i am glad to see Halium active again Apr 29 15:44:41 I'm glad for Halium's existence to be frank :-) Apr 29 16:03:17 Pushing a PR for my precious Xperia M, let me know if I've done something wrong Apr 29 16:03:39 @mayltonfnds fix your pr Apr 29 16:04:33 Plz pay attention to details, they are important Apr 29 16:05:04 I just read what you said Apr 29 16:05:37 isn't my profile a "remote"? Apr 29 16:07:56 no, it isn't Apr 29 16:08:02 your profile is your profile Apr 29 16:08:05 nothing more, sorry Apr 29 16:08:15 Where are we looking Apr 29 16:08:33 @UniversalSuperBox, https://github.com/Halium/halium-devices/pull/86 Apr 29 16:09:03 @mayltonfnds, https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/samsung_dream2lte.xml Apr 29 16:09:03 take a look at this manifest Apr 29 16:09:03 Aha, I see here. Do we have docs about this Apr 29 16:09:05 @mayltonfnds, If you want to use an extra remote for your profile, you need to add a section before. Apr 29 16:09:11 😢 Apr 29 16:09:48 http://docs.halium.org/en/latest/porting/get-sources.html#remotes Apr 29 16:09:50 Here we are Apr 29 16:10:14 the IRC bot is slow again Apr 29 16:10:39 How's it going ubptgbot Apr 29 16:10:44 Pretty good thanks Apr 29 16:10:51 @vanyasem, You're a liar Apr 29 16:11:06 (Photo, 750x324) https://irc.ubports.com/4uVzBJEi.png Apr 29 16:11:08 am i? Apr 29 16:11:10 Matrix might be working show, though Apr 29 16:11:19 The bridge has been up and down for the past few days Apr 29 16:11:35 yeah that's matrix what i was talking about Apr 29 16:11:47 it's one bot, so i made an assumption that it's slow overall Apr 29 16:11:49 i don't use IRC Apr 29 16:12:06 I'm only using IRC because of that precise problem with the Matrix bridge :-) Apr 29 16:12:21 okay thanks got it Apr 29 16:12:32 I'm starting to think that I should set up a Quassel core or apply for my Ubuntu membership and get their bouncer set up... Apr 29 16:12:40 Anyway that's offtopic Apr 29 16:13:47 Guys does github have a dark theme maybe? πŸ˜… Apr 29 16:13:52 nope Apr 29 16:14:03 My eyes bleed from that light one Apr 29 16:14:09 And I can't really turn the lights on Apr 29 16:14:36 if you install a browser extension (e.g. Stylish?) you can install user-made stylesheets for e.g. dark github theme Apr 29 16:15:05 @UniversalSuperBox, speaking of which ... I find it a bit odd that we use a remote called "halium" which is ALL of github? https://github.com/Halium/android/blob/halium-5.1/default.xml#L26 Apr 29 16:15:16 That's explained in the docs too Apr 29 16:15:37 http://docs.halium.org/en/latest/porting/get-sources.html#halium-7-1 Apr 29 16:15:45 note self: practise reading Apr 29 16:15:52 [Edit] note to self: practise reading Apr 29 16:16:01 @reivilibre, Thanks] Apr 29 16:16:12 @dohniks, It's not a great solution, but I guess it works Apr 29 16:16:15 @VeryOriginalUsername yw Apr 29 16:16:21 I'm just gonna #BlameMarius and be done Apr 29 16:16:48 I'm quite confused on how to make a halium-7.1 branch Apr 29 16:17:01 `git checkout -b halium-7.1` Apr 29 16:17:05 @dohniks, At least you can use it for your personal forks without having to specify the revision Apr 29 16:17:12 And then `git push --set-upstream origin halium-7.1` Apr 29 16:26:12 I'm afraid halium-7.1 brach forked los-15.1 files Apr 29 16:26:51 @mayltonfnds, It means you checkouted a wrong branch Apr 29 16:26:52 oof Apr 29 16:27:14 Please read how git works. It's not that complicated and is getting continuously annoying Apr 29 16:27:32 @mayltonfnds, then `git checkout cm-14.1` `git branch -D halium-7.1` (This will delete your 15.1 based halium-7.1 branch) `git checkout -b halium-7.1` Apr 29 16:27:35 @mayltonfnds, [Edit] then `git checkout cm-14.1` `git branch -D halium-7.1` (This will delete your 15.1 based halium-7.1 branch) and then`git checkout -b halium-7.1` Apr 29 16:27:40 @mayltonfnds, [Edit] then `git checkout cm-14.1` `git branch -D halium-7.1` (This will delete your 15.1 based halium-7.1 branch) and then `git checkout -b halium-7.1` Apr 29 16:27:42 @vanyasem, sorry for that Apr 29 16:29:44 Will repo sync remove files that I created or only repair my repo? (i accidentally deleted something) Apr 29 16:30:00 what did you accidentally delete? Apr 29 16:30:13 device/qcom/common Apr 29 16:30:14 @VeryOriginalUsername, It won't delete changes if you don't use β€”force-sync Apr 29 16:30:47 K Apr 29 16:30:52 I'm doing this on gcloud, so speed isn't a problem, just wanted to know that :p Apr 29 16:36:27 https://github.com/Halium/hybris-boot/pull/50 Apr 29 16:36:32 Can someone review? Apr 29 16:37:03 sure Apr 29 16:37:34 please give me a link to your device tree on github Apr 29 16:37:37 i need it to check the PR Apr 29 16:37:42 @VeryOriginalUsername Apr 29 16:37:59 https://github.com/LineageOS/android_device_sony_nicki/tree/cm-14.1 Apr 29 16:38:33 no, your PR is incorrect Apr 29 16:38:58 What did I miss? Apr 29 16:39:26 @VeryOriginalUsername, a discussion that happened 15 minutes ago Apr 29 16:39:40 emmc parts? Apr 29 16:40:25 Commented on the issue Apr 29 16:41:02 Oooh, I "inspired" myself with the suzu mounts, where presumably all partitions are mentioned Apr 29 16:41:21 some of them came from the Mer project, they could be incorrect Apr 29 16:43:09 Correcting :) Apr 29 16:44:24 I think it should be done now Apr 29 16:44:54 it's weird Apr 29 16:45:01 why were there so many partitions Apr 29 16:45:05 and only 3 in fstab Apr 29 16:45:17 No idea, but every cm-based rom works just fine Apr 29 16:45:17 but none of my business, pr looks good Apr 29 16:45:35 Literally everything is working (can't test front camera though, hw issue on my device) Apr 29 16:45:37 `FOTAKernel` is a nice name for a partition Apr 29 16:45:40 i like it Apr 29 16:46:14 Actually, it's used as recovery on pre-2015 (I think) sony devices Apr 29 16:47:01 well just keep that in mind Apr 29 16:47:16 in case something won't in the future, we could have missed a modem partition or so Apr 29 16:47:23 merging Apr 29 16:47:50 I'll keep that in my saved messages on telegram just so I can guess what's wrong in future :p Apr 29 16:48:06 were you able to boot halium reference with this config? Apr 29 16:48:21 how about we keep the PR open until we are sure that everything works? Apr 29 16:48:28 @vanyasem, sure Apr 29 16:48:50 it looks weird, i can't just merge it :P it has nothing to do with you, i have just never worked with Sony before Apr 29 16:49:03 @vanyasem, Well, don't yell at me after you read this, but I haven't really tested anything yet Apr 29 16:49:38 it's a long process, take your time Apr 29 16:50:17 i spent 3 months until i got to the point where i can run UBports on my main phone Apr 29 16:52:02 don't stop working, let me know if you need any assistance Apr 29 16:52:46 Also, I don't really have any experience just yet, just a 15yo so-called nerd trying to satisfy himself with new and new linux-ish knowledge Apr 29 16:52:56 So expect many help requests from me πŸ˜† h Apr 29 16:52:57 [Edit] So expect many help requests from me πŸ˜† Apr 29 16:52:59 i am 15yo as well :P Apr 29 16:53:24 Nice hair though Apr 29 16:53:39 the average age in this projects gets youger and younger with every day Apr 29 16:53:48 anyways we're getting OT here Apr 29 16:58:27 Preparing a clean kernel configuration and charging up the phone for some initial maybe-testing if nothing fails with make process (unlikely xD) Apr 29 17:02:02 @VeryOriginalUsername, Your phone will be connected the entire time you're testing Apr 29 17:02:09 So you don't really need to charge it :P Apr 29 17:02:20 yeah don't worry about charge, your phone is gonna be charging for HOURS during testing unless you get lucky ;-) Apr 29 17:02:33 All testing is done via ssh/telnet when connected to your PC Apr 29 17:02:48 Yeah, it has some defection and only charges with OEM cable and has to be connected to a pc (power brick doesn't work) Apr 29 17:08:55 ayy lmao I copypasted things from github to fixup-mountpoints and didn't remove "+" that came with it Apr 29 17:21:50 https://pastebin.com/8NXHrKUe Apr 29 17:22:28 https://github.com/ewentual/android_kernel_sony_msm8x27/tree/halium-7.1 Apr 29 17:24:34 I see, CROSS_COMPILE is somehow not defined Apr 29 17:58:40 Would someone take a look at it now? https://github.com/Halium/halium-devices/pull/86#pullrequestreview-116173622 Apr 29 17:59:05 @mayltonfnds, fix all issues Apr 29 17:59:08 and then ping people Apr 29 17:59:19 format your xml accordingly Apr 29 17:59:21 it's a mes Apr 29 17:59:22 [Edit] it's a mess Apr 29 17:59:28 use newlines and spaces Apr 29 18:16:41 Is it ok now? Apr 29 18:19:06 @mayltonfnds, no Apr 29 18:19:18 please open someone's else manifest and see how it's done Apr 29 18:19:26 what is that? who taught you to do that? Apr 29 18:20:01 ok, no problem Apr 29 18:35:45 My last try for today Apr 29 18:39:28 Much better. I'm just not sure if the revision needs to be set for the them remote. It's probably unnecessary. Apr 29 18:40:10 According to http://docs.halium.org/en/latest/porting/get-sources.html#remotes Apr 29 18:40:15 the answer is yes Apr 29 18:40:47 It makes it the default revision to the following "projects" Apr 29 18:42:13 I'm talking about the remote called "them", which you are using for your proprietary_vendor repo. You can probably remove the revision in the tag of the proprietary_vendor repo. Apr 29 18:42:46 hmm Apr 29 18:43:19 The them remote is defined by the base manifest and already sets a cm-14.1 revision, do you don't need to set it in the project tag again. Apr 29 18:43:25 [Edit] The them remote is defined by the base manifest and already sets a cm-14.1 revision, so you don't need to set it in the project tag again. Apr 29 18:44:55 Oh, I see. i was wondering how it works when I don't have that remote in my .xml file btw Apr 29 18:47:17 @mayltonfnds, magic. pure magic Apr 29 18:47:36 but I don't think it matters once i have seen many devices with them set Apr 29 18:48:21 Is it ok now btw? Apr 29 18:48:28 I'll have a look Apr 29 18:48:50 why do you define `proprietary_vendor_leeco` twice Apr 29 18:49:06 @mayltonfnds, I probably have push access there, so I can fix the remaining issues. Apr 29 18:55:15 @vanyasem, only the last one is required tbh Apr 29 18:55:27 @mayltonfnds, so remove the unneeded one? Apr 29 18:55:37 I already did it Apr 29 18:55:42 thank you JBB Apr 29 18:57:00 Guys, I know I've been a pain in the ass, but I'm just doing this because I really want that thing running on my device Apr 29 18:57:54 @vanyasem Any remaining issues or can the PR be merged now? Apr 29 18:58:08 [Edit] @vanyasem Are there any remaining issues or can the PR be merged now? Apr 29 18:59:28 @JBBgameich, it's ok, you can merge it Apr 29 19:00:51 Okay, merged Apr 29 19:02:11 last step, halium documentation, right? Apr 29 19:02:29 @mayltonfnds, yep, fill in device information Apr 29 19:02:45 please do it carefully.. Apr 29 19:07:14 Gi Bix was added by: Gi Bix Apr 29 19:10:13 https://github.com/Halium/projectmanagement/issues/74 Apr 29 19:10:50 plz link your manifest Apr 29 19:11:08 in the issue Apr 29 19:11:25 Yes, just noticed that Apr 29 19:11:58 I can link it to halium/halium-devices or do i have to link it to my repo? Apr 29 19:12:14 you have to link the manifest you PRed to halium-devices Apr 29 19:12:31 ok Apr 29 19:12:48 @mayltonfnds, to halium/halium-devices, like it's done on the issue template. Apr 29 19:12:59 Olivier 'reivilibre' was added by: Olivier 'reivilibre' Apr 29 19:13:18 @JBBgameich, Ok, thanks Apr 29 19:20:36 done Apr 29 19:26:16 I think it's enough for today πŸ˜† Apr 29 21:20:35 skull_admin was added by: skull_admin **** ENDING LOGGING AT Mon Apr 30 03:00:06 2018