**** BEGIN LOGGING AT Fri Dec 18 02:59:56 2020 Dec 18 03:41:12 @NotKit [ok], ok the phone does show a connection but i can't ssh to it Dec 18 03:45:56 nvm just had to flash dtbo Dec 18 03:48:56 it's working! i'm gonna test my sim Dec 18 03:57:34 ok so the vibration motor is broken Dec 18 04:18:15 @mintphin [ok so the vibration motor is broken], is that new? Dec 18 04:18:27 yeah Dec 18 04:18:30 the gsi doesn't have this issue Dec 18 05:22:30 KanajariyaReal was added by: KanajariyaReal Dec 18 05:22:48 How to build kernel standalone for RMX1851 Dec 18 05:24:54 Or How to build halium boot image for RMX1851 Dec 18 07:07:34 RadekR was added by: RadekR Dec 18 07:30:07 Where can I buy ubuntu touch tablet? Dec 18 07:32:39 wait for the pinetab to be restocked. Dec 18 07:38:12 Does anyone know the default sudo password for the Manjaro edition PinePhone? Dec 18 07:41:34 i think it’s the same as your login password but i’m not sure. Dec 18 07:41:49 also that’s off-topic Dec 18 07:45:54 btw what’s the progress on alarm for halium? Dec 18 07:50:29 @mintphin [btw what’s the progress on alarm for halium?], Alarm? Dec 18 08:02:09 arch linux arm Dec 18 08:10:09 Sorry, wrong group! Dec 18 08:10:28 BTW, tried that. No worky. Dec 18 11:52:42 (Sticker, 512x512) https://irc.ubports.com/avTc6laF.webp Dec 18 13:55:17 Any idea about: … multiple definition of '__aeabi_unwind_cpp_pr0' Dec 18 17:19:14 https://bpa.st/SHPA Dec 18 17:19:18 full log Dec 18 17:45:59 Jeez, I wish I knew more about fixing errors myself, that way I can fix my own errors, and help others. I hope you can figure it out Luka Dec 18 18:47:58 Retying_1918 was added by: Retying_1918 Dec 18 19:12:20 @NotKit Great news, mobile data works fine! I think that would mean calls and texting work too. Dec 18 19:17:34 doesn’t show up as a mi a3 tho Dec 18 19:17:35 (Photo, 960x1280) https://irc.ubports.com/IsOO53s0.png Dec 18 19:17:48 Oof Dec 18 19:19:53 @mintphin [doesn’t show up as a mi a3 tho], Bcz of gsi Dec 18 19:19:59 Paul B was added by: Paul B Dec 18 19:20:40 @Lukapanio [Bcz of gsi], i'm not working on the gsi Dec 18 19:20:42 Hi guys! I'm trying to port Halium to the Oneplus 7 Pro. I'm a little lost. So I'm on the fstab part of porting Halium, and would run readlink -f /dev/block/bootdevice/by-name/system, the output was /dev/block/platform/soc/1d84000.ufshc/by-name/system which confuses me from looking at fixup-mountpoints. I was expecting something like /dev/ Dec 18 19:20:43 block/sdX or something like that haha. Anyone know how to help? Dec 18 19:20:49 this is a device-specific build Dec 18 19:21:07 it tries to get device name from systemimage, which is shared Dec 18 19:21:14 should be fixed Dec 18 19:21:26 [Edit] it tries to get device name from LXC container systemimage, which is shared Dec 18 19:21:38 oh ok Dec 18 19:22:29 @Paul B [Hi guys! I'm trying to port Halium to the Oneplus 7 Pro. I'm a little lost. So I …], flash stock android9 and use this halium-boot https://build.lolinet.com/file/halium/guacamole/halium-boot.img Dec 18 19:23:23 @erfanoabdi did you patch system-settings app to display correct device name? Dec 18 19:23:32 @NotKit [@erfanoabdi did you patch system-settings app to display correct device name?], nope Dec 18 19:24:34 Oh sweet, will do @erfanoabdi Thanks! Dec 18 19:26:39 Will that IMG work with UBPorts? Dec 18 19:26:45 yeah Dec 18 19:26:49 1 Dec 18 19:26:50 Cool 👍 Dec 18 19:27:32 flash stock android 9 … flash that img to boot … boot to twrp and flash ubports gsi … reboot Dec 18 19:28:02 i guess it has broken touchscreen, but boots Dec 18 19:28:10 Yeah that's what I figured. Thanks dude! Oh haha Dec 18 19:28:19 😁🙌 Dec 18 19:30:03 Carl Dimiceli was added by: Carl Dimiceli Dec 18 19:33:39 @erfanoabdi [😁🙌], Bro OOS 11 gsi possible? Dec 18 19:34:22 @Amitkranand [Bro OOS 11 gsi possible?], Ot Dec 18 19:34:33 @Lukapanio [Ot], OK I removes it Dec 18 19:39:46 @erfanoabdi [i guess it has broken touchscreen, but boots], hah, it seems to be the thing really consistent with OnePlus Dec 18 19:40:06 lol yeah Dec 18 19:51:42 Wow loook!! It's amazing Giveawey💥🤑🚀🤑💥 … https://bit.ly/3aqz9J9 Dec 18 20:06:21 Anyone able to help me with this error, I know I need to do a #include somewhere but not 100% sure where … halium/kernel/motorola/msm8937/drivers/usb/gadget/function/u_ether.c:2060:33: error: invalid application of 'sizeof' to incomplete type 'struct rndis_packet_msg_type' … link->header = kzalloc(sizeof(struct rndis_packet_msg_typ Dec 18 20:06:21 e), … ^ Dec 18 20:39:31 Seeing it was only to do with ethernet over usb I decided to remove it for now seeing it's not mandatory to boot, but I now have an unexpected EOF, anyone able to help with this? … https://pastebin.com/8p268gLW Dec 18 20:40:52 It may be used for debugging, keep it, add the import near the top Dec 18 20:42:08 Okay, I just need to find out where the file is kept so I can write the include but i'll figure that part out, are you able to help with the unexpected EOF? Pretty sure that will still be an issue with the build after Dec 18 20:42:47 @Andeddokira [Okay, I just need to find out where the file is kept so I can write the include …], It may not, fix the first error, removing parts will not help. Dec 18 20:45:19 @erfanoabdi I downloaded the GSI image from here https://build.lolinet.com/file/halium/GSI/ but when going to TWRP and trying to flash the zip it gives me "Zip file is corrupt!" Dec 18 20:45:48 Oh worked when I tried again... LOL Dec 18 20:51:14 Now it looks like it just simply just doesn't boot Dec 18 20:51:40 [Edit] Now it looks like it just simply doesn't boot Dec 18 20:52:35 I'm just stuck on my boot logo screen Dec 18 20:53:44 Oh and yes I'm on stock Android 9 Dec 18 20:55:43 I simply extracted stock firmware, ran fastboot -w update images.zip, did my first boot otherwise TWRP doesn't work, went to TWRP, flashed halium_boot.img, flashed the UBPorts GSI image, rebooted and am stuck. Dec 18 21:05:30 @Paul B [I simply extracted stock firmware, ran fastboot -w update images.zip, did my fir …], Did you format data? Dec 18 21:05:42 Oh nope, I'll try that rn Dec 18 21:05:57 Before gsi it's needed … To disable encryption Dec 18 21:06:21 Oh, right. Forgot about the encryption. I'll do both rn! Dec 18 21:06:24 Format data and flash gsi again Dec 18 21:07:44 @antoine_62 [It may not, fix the first error, removing parts will not help.], Okay adding a simple #include to the top of u_ether.c resolved the sizeof error but the unexpected EOF error is still there Dec 18 21:09:09 @erfanoabdi [Before gsi it's needed … To disable encryption], Still doesn't seem to boot with formatting data then installing the GSI image Dec 18 21:24:37 Alright so here is my full log of the build if anyone can help me resolve the unexpected EOF, it happens literally at the end of putting the boot img together … https://pastebin.com/Bu1uV3xe Dec 18 21:29:12 @Paul B [Still doesn't seem to boot with formatting data then installing the GSI image], flash halium-ramdisk too Dec 18 21:29:27 https://build.lolinet.com/file/halium/GSI/tools/halium-ramdisk.zip Dec 18 21:31:48 @Andeddokira [Alright so here is my full log of the build if anyone can help me resolve the un …], I might sound stupid, but did you modify /bin/bash? Dec 18 21:34:05 I don't remember modifying it recently and have tried building the kernel successfully for a different device the other day Dec 18 21:34:09 @Andeddokira [Alright so here is my full log of the build if anyone can help me resolve the un …], probably remove dm=\\\"system none ro,0 1 android-verity /dev/mmcblk0p53\\\" from kernel cmdline since we do not care about verity anyway Dec 18 21:34:51 @NotKit [probably remove dm=\\\"system none ro,0 1 android-verity /dev/mmcblk0p53\\\" fr …], Sorry where abouts would I remove that from? Dec 18 21:35:13 device tree or device common tree Dec 18 21:36:19 @NotKit [probably remove dm=\\\"system none ro,0 1 android-verity /dev/mmcblk0p53\\\" fr …], sounds about right. I thought about that, but I didn't think it was it for some reason. could it be the "\\\" getting in the way of building the image? Dec 18 21:37:04 something failed with escape sequence Dec 18 21:38:49 Oh, I mean, with halium 7.1 building, there wasn't the "\\\" in the make halium-boot part. I just thought that those extra "\\\" could have boinked up the build command Dec 18 21:39:14 @NotKit [probably remove dm=\\\"system none ro,0 1 android-verity /dev/mmcblk0p53\\\" fr …], Okay so i've commented the line out under the device tree and am running the build, should be able to update you in 5 mins Dec 18 21:42:51 That fixed it, successfully built after that line was removed Dec 18 21:43:02 Thats good Dec 18 21:43:06 good luck Dec 18 21:43:20 Thanks for all your guys help Dec 18 21:45:30 One last thing, when making system image, I always run into this error and have never been able to figure it out … ninja: error: '/home/andeddokira/UbuntuTouch-S8/halium/out/soong/host/linux-x86/bin/d8', needed by '/home/andeddokira/UbuntuTouch-S8/halium/out/soong/.intermediates/frameworks/base/packages/EasterEgg/EasterEgg/android_com Dec 18 21:45:31 mon/dex/EasterEgg.jar', missing and no known rule to make it Dec 18 21:46:17 There is a guide for that in the halium docs Dec 18 21:46:29 I think Dec 18 21:47:39 @WolfLink115 [There is a guide for that in the halium docs], There is yes, I just literally read signapk.jar as being literal rather than an example, will follow that guide, thanks Dec 18 21:48:11 Np. not sure if it is for the same thing, but it says jar, so it might work Dec 18 21:58:22 @WolfLink115 [Np. not sure if it is for the same thing, but it says jar, so it might work], Any other places you know where I might be able to check, the guide references proprietary-files.txt but it seems that both those files in the device tree and the device common tree have had the apks and jars successfully removed by the script Dec 18 21:59:58 Wait. It is asking for d8, not signapk.jar. Hang on, imma check something Dec 18 22:16:40 This is weird. Maybe comment out the dependency it is asking for, d8. Last I checked, soong isnt even needed for UBPorts Dec 18 22:19:36 @WolfLink115 [This is weird. Maybe comment out the dependency it is asking for, d8. Last I che …], Do you know roughly where the d8 dependency gets stated? Dec 18 22:20:52 @Andeddokira [Do you know roughly where the d8 dependency gets stated?], Nope. I haven't built Halium 9 yet. I was planning on it, but got mega sidetracked. If anything, check Android.bp files, soong relies on those i believe Dec 18 22:21:04 Im sorry. Dec 18 22:21:11 [Edit] Im sorry that I cannot help. Dec 18 22:24:48 @WolfLink115 [Nope. I haven't built Halium 9 yet. I was planning on it, but got mega sidetrack …], No that's all good, you've been plenty of help, will look at those files, might try grep for it Dec 18 22:25:15 @Andeddokira [No that's all good, you've been plenty of help, will look at those files, might …], Ok, good luck, I hope you get it working! Dec 18 22:36:07 Woow! 😱Woow! Binance crazy team! They announced airdrop for all fans … LOOK this post - https://bit.ly/3h1fjp9 Dec 18 22:36:18 @Carl Dimiceli [Woow! 😱Woow! Binance crazy team! They announced airdrop for all fans … LOOK this …], Spam Dec 18 22:37:35 @Andeddokira [No that's all good, you've been plenty of help, will look at those files, might …], have you checked https://github.com/ubports/porting-notes/wiki/Halium-9? Dec 18 22:46:35 @Deathmist1337 [have you checked https://github.com/ubports/porting-notes/wiki/Halium-9?], Yup and i've followed the guide there with the standard halium guide. Decided I'd try using the gsi but seems my boot img may be no good, can't get past the splash screen. Do I need to flash the ramdisk and apparmor_enabler? I assumed not seeing Dec 18 22:46:35 I built the kernel using halium Dec 18 22:48:20 splash screen as in OEM logo or Ubuntu Touch one? Dec 18 22:48:37 @Deathmist1337 [splash screen as in OEM logo or Ubuntu Touch one?], sorry oem logo Dec 18 22:48:40 and does it bootloop? Dec 18 22:48:50 nope just sits there Dec 18 22:49:39 ok, check `dmesg` on your system to see if USB is working on the device, you should see something like `Halium initrd` or `GNU/Linux device` towards the end Dec 18 22:56:21 @Deathmist1337 [ok, check dmesg on your system to see if USB is working on the device, you shoul …], Sorry had to plug my device into my native linux machine as I use wsl2 on windows to build so I can take advantage of my I9. Doesn't appear to be showing in dmesg though Dec 18 22:56:49 uh, I don't think WSL has USB passthrough, I don't know how to help honestly Dec 18 22:57:26 @Deathmist1337 [uh, I don't think WSL has USB passthrough, I don't know how to help honestly], It doesn't hence using my other machine that has linux natively running on it, so ignore the wsl part that's only for building purposes Dec 18 22:58:10 well run `dmesg -w` on the linux box, and reboot the phone while it's plugged in to see if anything appears Dec 18 22:59:06 I assume you ran the kernel defconfig through https://github.com/erfanoabdi/halium-boot/blob/halium-9.0/check-kernel-config before building halium-boot? Dec 18 23:00:25 @Deathmist1337 [well run dmesg -w on the linux box, and reboot the phone while it's plugged in t …], Nothing happened. Also yes I did, there was a few things I couldn't patch as there were no settings available in the kernel. An example is the 3 settings that involve CGROUP_MEM_RES_CTLR Dec 18 23:02:17 that's fine, can you send the `.config` file here (or upload to a paste service)? you can run `find out/ -type f -name .config` to locate it Dec 18 23:04:30 (Document) https://irc.ubports.com/QuZfWAv3.txt Dec 18 23:05:49 hmm, does your device have a vendor partition? 3.18 kernels are from around Android 6/7 launch era Dec 18 23:07:23 without a vendor partition the GSI won't work Dec 18 23:07:40 @Deathmist1337 [hmm, does your device have a vendor partition? 3.18 kernels are from around Andr …], Treble support was added to the device via the community, i'm just using the kernel that is utilized with the lineage 16 gsi built for the device, but have already done all the tweeks to get treble working on the device Dec 18 23:08:41 There is a 4.9 kernel that I can build from source for lineage 16 but it's not being used in the current release so decided to avoid building with that incase there was a reason they hadn't started using it Dec 18 23:11:29 I wonder why `CONFIG_USB_CONFIGFS_RNDIS=y` didn't get set by the kernel checker script Dec 18 23:12:28 Nothing got set by the kernel checker script, had to set it all myself, also had to modify u_ether.c to have a include statement at the top for rdnis Dec 18 23:13:17 @Andeddokira [Nothing got set by the kernel checker script, had to set it all myself, also had …], oh, you could've ran it with the `-w` flag Dec 18 23:13:19 well looks like there's bit of good news for "fully upstreamed" android hardware: https://www.phoronix.com/scan.php?page=news_item&px=Android-AOSP-Close-Linux-5.9 Dec 18 23:13:58 if you can boot mainline you shouldn't involve Android in the process unless you want to run android Dec 18 23:14:04 [Edit] if you can boot mainline you shouldn't involve Android in the process unless you want to run android :p Dec 18 23:14:13 Lol Dec 18 23:14:27 @Deathmist1337 [if you can boot mainline you shouldn't involve Android in the process unless you …], i know right :p Dec 18 23:14:58 @Deathmist1337 [oh, you could've ran it with the -w flag], wait so the -w flag makes the changes for me? Dec 18 23:14:59 @Deathmist1337 [oh, you could've ran it with the -w flag], as in `./check-kernel-config -w path/to/defconfig` Dec 18 23:15:24 the -w is supposed to be at the end i thought Dec 18 23:15:41 oh yeah Dec 18 23:15:50 really dumb how that works Dec 18 23:15:53 lol Dec 18 23:15:55 ikr Dec 18 23:16:24 @Fuseteam [i know right :p], That has something to do with FSCRYPT being disabled from what the link says Dec 18 23:17:13 @WolfLink115 [the -w is supposed to be at the end i thought], Okay so if I slap -w at the end I can then have the script auto patch the kernel for me? Dec 18 23:17:14 Andeddokira you'll probably also need `CONFIG_FW_LOADER_USER_HELPER=y` so any firmware will get loaded, for some reason the script tries to disable this option and that caused by device to not boot. Dec 18 23:17:21 well kernel defconfig yes Dec 18 23:18:30 @WolfLink115 [That has something to do with FSCRYPT being disabled from what the link says], filesystem encryption? that's what is is about? Dec 18 23:18:48 @Deathmist1337 [Andeddokira you'll probably also need CONFIG_FW_LOADER_USER_HELPER=y so any firm …], Okay i'll try add in `CONFIG_FW_LOADER_USER_HELPER=y` and see if I can get it to boot, may even try loading the 4.9 kernel instead Dec 18 23:18:49 @WolfLink115 [That has something to do with FSCRYPT being disabled from what the link says], [Edit] filesystem encryption? that's what it is about? Dec 18 23:18:59 @WolfLink115 [That has something to do with FSCRYPT being disabled from what the link says], Disabling it gives "better SoC performance" on modern SoC's, which doesnt seem wrong, nor right. That also seems to be the kernel config that enables filesystem encryption on the device, hence the "crypt" Dec 18 23:19:09 @Andeddokira [Okay i'll try add in CONFIG_FW_LOADER_USER_HELPER=y and see if I can get it to b …], remember `CONFIG_USB_CONFIGFS_RNDIS=y` too, that should make USB work Dec 18 23:19:41 @Deathmist1337 [remember CONFIG_USB_CONFIGFS_RNDIS=y too, that should make USB work], That one was meant to be enabled already? That's odd that it's not Dec 18 23:19:45 Wait. I may have jumped to conclusions with that Dec 18 23:19:47 @WolfLink115 [Disabling it gives "better SoC performance" on modern SoC's, which doesnt seem w …], ah performace vs security hmm, so wait that patch disables that? Dec 18 23:20:31 @Fuseteam [ah performace vs security hmm, so wait that patch disables that?], No, i think the patch allows users to boot mainline kernel, even with encryption enabled. Dec 18 23:20:42 That is pretty cool if you ask me Dec 18 23:21:47 @Andeddokira [That one was meant to be enabled already? That's odd that it's not], enabled by the script yes, enabled for Android not necessarily; my device uses `CONFIG_USB_CONFIGFS_F_GSI=y` for that (which broke `CONFIG_USB_CONFIGFS_RNDIS=y` for porting stuff) Dec 18 23:23:30 @Deathmist1337 [enabled by the script yes, enabled for Android not necessarily; my device uses C …], so even if menuconfig states it's enabled it might not actually be enabled? Dec 18 23:24:07 menuconfig is correct, it takes dependencies into account Dec 18 23:27:59 @Deathmist1337 [menuconfig is correct, it takes dependencies into account], Ah okay so it should have been set. Anyway i've jumped over to the 4.9 kernel and ran check-kernel-config with -w which would have saved me so much time if I knew that before, the amount of times I went into autopilot setting stuff and accidentally exiting men Dec 18 23:27:59 uconfig, will build the kernel and see what happens Dec 18 23:29:52 I mean you could still at least try the 3.18 one :p if the 4.9 kernel works nice though you might as well use it I suppose Dec 18 23:32:14 Okay i've clearly messed something up now [195/447] including frameworks/base/Android.mk ... … build/make/core/droiddoc.mk:188: error: FindEmulator: find: `tools/metalava/manual': No such file or directory Dec 18 23:32:26 you forgot to apply patches Dec 18 23:33:08 hmm idk if those are needed for halium-boot actually Dec 18 23:33:10 @WolfLink115 [No, i think the patch allows users to boot mainline kernel, even with encryption …], ah interesting Dec 18 23:33:32 anyway the command to apply them is `hybris-patches/apply-patches.sh --mb` and it's in https://github.com/ubports/porting-notes/wiki/Halium-9 Dec 18 23:34:00 @Deathmist1337 [you forgot to apply patches], Says patches already applied so forced it to apply them anyway and same issue Dec 18 23:34:33 @Fuseteam [ah interesting], I think if we are going to talk about off topic things, then we should move to a private message. Dec 18 23:34:46 @Deathmist1337 [anyway the command to apply them is hybris-patches/apply-patches.sh --mb and it' …], Actually forgot the —mb but getting a repo rebase error Dec 18 23:34:48 @WolfLink115 [I think if we are going to talk about off topic things, then we should move to a …], yeah probably Dec 18 23:37:25 @Andeddokira [Actually forgot the —mb but getting a repo rebase error], you can run `repo sync -l` to unapply the patches, BUT this also tries to clear any of your changes; I think you can save a git stash your changes and pop them afterwards, but you could also just `git diff > changes.diff` and `patch -p1 < changes.diff` after you Dec 18 23:37:25 're done again Dec 18 23:38:07 will give repo sync -l a try and then re apply my changes Dec 18 23:38:53 seems to be error: Cannot checkout LineageOS/android_bionic causing the issue Dec 18 23:40:04 and this is why I hate `repo` :) you can try deleting it's folder with `rm -rf bionic` in the source root Dec 18 23:41:15 @Deathmist1337 [and this is why I hate repo :) you can try deleting it's folder with rm -rf bion …], Perfect that command did the trick thank you :) Dec 18 23:52:19 Guess 4.9 isn't a go, get (bootloader) Image size exeeded partition limits … (bootloader) Preflash validation failed when flashing it Dec 18 23:52:52 that is really odd, how big is the image? Dec 18 23:53:07 17mb, pretty sure that's the same size as the old one as well Dec 18 23:53:54 so that means you have a 16 MiB boot partition, you may have to disable some features (such as NFS, CIFS and other network filesystems) to get it to fit Dec 18 23:55:06 @Deathmist1337 [so that means you have a 16 MiB boot partition, you may have to disable some fea …], just edit those using make menuconfig and disable them? Dec 18 23:55:12 yea Dec 18 23:55:32 those are safe bets to go for since you won't be needing them anyway especially during early porting Dec 18 23:57:37 fastboot boot might just work even if it's too small for the boot partition and you still want to test Dec 18 23:57:40 [Edit] fastboot boot might just work even if it's too big for the boot partition and you still want to test Dec 18 23:59:27 You could try to flash it through twrp Dec 18 23:59:44 @Deathmist1337 [yea], Got that error whilst trying to flash it using fastboot. Also all networking filesystem are already disabled so that's not fun Dec 18 23:59:57 @WolfLink115 [You could try to flash it through twrp], Will try flash using twrp to see what happens Dec 19 00:00:05 @Andeddokira [Will try flash using twrp to see what happens], ok Dec 19 00:02:27 @WolfLink115 [ok], same error in twrp Dec 19 00:02:42 @Andeddokira [same error in twrp], Ok, then that doesn't work Dec 19 00:02:57 I guess do what Jami said. Dec 19 00:03:43 @WolfLink115 [Ok, then that doesn't work], Tried but all network files systems are already disabled, anything else I can safely disable that will free up some size? Dec 19 00:03:47 you'll have to disable more stuff, or re-clone 3.18 kernel and see if you get it booted with the proper configs Dec 19 00:04:18 @Deathmist1337 [you'll have to disable more stuff, or re-clone 3.18 kernel and see if you get it …], Think it might be faster to go back to 3.18 and then try building with that seeing that would fit Dec 19 00:04:30 Unless you want to go to the very dark side and try to repartition your boot partition. But I would not recommend that to anyone because I almost lost a phone from doing that Dec 19 00:06:11 @WolfLink115 [Unless you want to go to the very dark side and try to repartition your boot par …], I will try 3.18 for now and if I still have issues with it then i'll try repartition, I got a few spares of these phones so if I kill one, I kill one Dec 19 00:06:29 @Andeddokira [I will try 3.18 for now and if I still have issues with it then i'll try reparti …], Ok. good luck again Dec 19 00:07:31