**** BEGIN LOGGING AT Sat Jan 16 03:00:36 2021 Jan 16 03:32:22 Bartholomew was added by: Bartholomew Jan 16 04:35:10 I'm following the docs :/ Jan 16 04:35:31 I did that do I need to do it again Jan 16 05:36:07 i already have ti/omap4 Jan 16 05:54:51 hi Jan 16 05:56:23 hi can u help me? Jan 16 05:58:36 @NotKit [Abdullah AL I had a look at https://github.com/AndroidBlobs/device_nokia_Dynamo …], I banned from telegram. Anyway, How can I set the kernel compilation there? Setting up all the files from here https://github.com/imasaru/android_device_tree_template? Jan 16 06:00:41 i cant figure out xml file Jan 16 06:01:06 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/WpicjqBWXmXquPpRFkwaUbpb/message.txt > Jan 16 06:01:10 i get this error Jan 16 06:12:00 nvm fixed it by resyncning Jan 16 06:20:42 @NotKit [Abdullah AL I had a look at https://github.com/AndroidBlobs/device_nokia_Dynamo …], [Edit] I was temporarily banned from telegram. Anyway, How can I set the kernel compilation there? Setting up all the files from here https://github.com/imasaru/android_device_tree_template? Jan 16 06:28:02 i did `./mer_verify_kernel_config ` and got many errors and warnings how do i fix them Jan 16 06:54:04 here is what i did https://pastebin.com/tqKfuQgp Jan 16 06:55:23 * here is what i did https://pastebin.com/7KtSt26B Jan 16 06:55:29 pls help Jan 16 07:05:27 nwebi3 was added by: nwebi3 Jan 16 07:10:05 ignore the warnings, add and define the errors to whatever it says that is allowed for example to fix "ERROR: CONFIG_IP6_NF_MATCH_RPFILTER is invalid Allowed values : y" go open the file in text editor and write down CONFIG_IP6_NF_MATCH_RPFILTER=y at the end Jan 16 07:10:27 you can use ./mer_verify_kernel_config | grep ERROR to identify the errors too Jan 16 07:11:18 but which file? the defconfig? Jan 16 07:11:29 yeah Jan 16 07:11:51 there is no CONFIG_IP6_NF_MATCH_RPFILTER in it Jan 16 07:12:04 that's just an example he wrote Jan 16 07:12:16 yeah you're gonna add it yourself instead Jan 16 07:12:30 ya but lets say "CONFIG_SYSFS" is invalid Jan 16 07:12:44 so i need to add it to defconfig myself if it dosent exist there Jan 16 07:12:51 yes Jan 16 07:13:10 thanks :) can i add it anywhere in the defconfig Jan 16 07:13:35 yeah I dont think that'd matter but you should probably add it to the very bottom so you know where to find them just in case lol Jan 16 07:13:47 alright! thanks a lot Jan 16 07:20:01 yay fixed all errors :D Jan 16 07:20:42 `halium/hybris-boot/Android.mk:73: *** There should be a one and only one device entry for HYBRIS_BOOT_PART and HYBRIS_DATA_PART.` Jan 16 07:20:57 now im getting this on running `mka mkbootimg` Jan 16 08:17:10 did you add your device to fixup-mountpoints ? Jan 16 08:31:00 it is already there Jan 16 08:31:26 * mighty17[m] uploaded an image: image.png (41KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/CQxySDqMEVAqfDjxMZioXlth/image.png > Jan 16 08:31:27 here is a pic ^^ Jan 16 08:33:02 hmm Jan 16 08:33:39 https://github.com/mer-hybris/hybris-boot/pull/35 Jan 16 08:33:45 I am not really sure how to fix that Jan 16 08:33:50 but someone will probably help you Jan 16 08:34:18 should i add it again? Jan 16 08:34:33 no Jan 16 08:34:49 I probably just remember it wrong and the problem is unrelated Jan 16 08:35:04 oh okay Jan 16 08:35:19 the partitions seem correct https://redmine.replicant.us/projects/replicant/wiki/GalaxyTab270GTP31xx Jan 16 08:35:38 should i add other as well? Jan 16 08:37:57 @mighty17[m] [should i add other as well?], I am not really sure :/ Jan 16 08:38:16 @dopamine404 [I probably just remember it wrong and the problem is unrelated], As I said might be completely unrelated Jan 16 08:38:56 okay i will wait for someone else Jan 16 08:39:03 yup Jan 16 08:39:06 good luck Jan 16 08:39:13 make clean will help? Jan 16 08:39:36 trying won't hurt :p Jan 16 08:40:03 didnt help Jan 16 08:40:07 same error Jan 16 08:40:52 can u see if the partitions are not like how halium wants it? Jan 16 08:41:04 https://docs.halium.org/en/latest/porting/common-system-build-errors.html Jan 16 08:41:13 already tried that Jan 16 08:41:18 your error is listed here Jan 16 08:41:20 oh Jan 16 08:41:41 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/JgoVBPbZrvvvRHTkzWJFMquU/message.txt > Jan 16 08:41:47 I have no clue then Jan 16 08:41:47 this is the error Jan 16 08:42:01 thanks for your help anyways :) Jan 16 08:42:11 lets wait for someone else then Jan 16 08:42:13 no problem :) Jan 16 08:42:18 yeah Jan 16 08:42:38 if you don't get a reply just write a few hours later Jan 16 08:42:55 alright! thanks!! Jan 16 09:07:06 https://github.com/Halium/projectmanagement/issues/237 all contributions are welcome Jan 16 09:11:06 that reminds me i need to make one for Samsung Galaxy Tab 2 aswell Jan 16 09:14:11 @mighty17[m] [that reminds me i need to make one for Samsung Galaxy Tab 2 aswell], If you have the time go for it Jan 16 09:14:29 https://github.com/Halium/projectmanagement/issues/238 :) Jan 16 09:14:34 @NotKit [@ArunSojanParolikkal since it is used only to export those values to sysfs, it i …], I was successfully able to build halium-boot.img after reverting the commit. Building systemimage fails, however, with the compiler making the following complaint: Jan 16 09:14:34 hardware/broadcom/libbt/src/hardware.c:53:10: fatal error: 'samsung_macloader.h' file not found … #include . I found a samsung _macloader.h file here: https://review.lineageos.org/c/LineageOS/android_device_samsung_zero-common/+/166592/1/includ Jan 16 09:14:34 e/samsung_macloader.h#1 Is this something generic that I could use, or is there a file specific to my device? Jan 16 09:14:56 I think I remember this error Jan 16 09:14:59 Wait a second Jan 16 09:15:09 @dopamine404 [Wait a second], Yeah sure Jan 16 09:15:22 okay Jan 16 09:19:33 I think I remember"> Was that to me or to him Jan 16 09:19:57 to him :p Jan 16 09:20:09 @ArunSojanParolikkal [I was successfully able to build halium-boot.img after reverting the commit. Bui …], http://www.mardy.it/blog/2019/07/notes-on-porting-the-samsung-j3-to-halium-+-ubports.html I am not sure if this will help Jan 16 09:20:31 but the bt repo might be useful Jan 16 09:21:24 if not I would suggest just trying to bodge the header file somewhere Jan 16 09:26:18 @dopamine404 [http://www.mardy.it/blog/2019/07/notes-on-porting-the-samsung-j3-to-halium-+-ubp …], I'll check it out, thanks. Jan 16 09:26:28 no problem Jan 16 09:39:11 ... it clearly finds two paths to /boot and /data somewhy Jan 16 09:39:26 as there are 2 paths Jan 16 09:39:35 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ZWRCjXUsGoNjYtQszggwpjnl/message.txt > Jan 16 09:39:41 in fixup-mountpoints Jan 16 09:40:36 https://github.com"> hey another j5 user Jan 16 09:40:40 we have https://github.com/Kiciuk/local_manifest Jan 16 09:41:29 That manifest is already working Jan 16 09:41:37 And we have a lot of things working in UT too Jan 16 09:42:14 @actuday [I was successfully able to build halium-boot.img after reverting the commit. Bui …], you can probably skip building systemimage for now and use halium_arm64 generic one Jan 16 09:42:25 but make sure you have Android 9 vendor flashed Jan 16 09:42:33 @nergzd723 [And we have a lot of things working in UT too], oh really? Jan 16 09:43:05 @nergzd723 [And we have a lot of things working in UT too], did you guys create an issue at projectmanagement? Jan 16 09:43:37 @nergzd723 [And we"> I think the original author didn't do anything to upstream that :( Jan 16 09:44:07 btw you'd need rsyslogd workaround too Jan 16 09:44:20 ah I see Jan 16 09:44:31 check the fstab Jan 16 09:44:38 I don't know where does it look Jan 16 09:44:47 but I bet there are two paths for boot and data Jan 16 09:44:53 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/oyaCewYnwpQqsXXDPCGHvhFy/message.txt > Jan 16 09:45:03 fstab.espresso Jan 16 09:45:24 It must be device/samsung/*/rootdir/*fstab Jan 16 09:45:57 surely there are two entries for data and boot Jan 16 09:46:28 remove that recoveryonly boot line and the f2fs data line Jan 16 09:46:49 @nergzd723 [btw you'd need rsyslogd workaround too], did you guys get UT to actually launch? Jan 16 09:47:07 @nergzd723 [btw yo"> yes Jan 16 09:47:13 damn Jan 16 09:47:13 ?? Jan 16 09:47:31 edit it manually Jan 16 09:47:33 boot or recovery one? Jan 16 09:47:46 boot one with recoveryonly parameter Jan 16 09:48:24 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/fjDaKUmWWvmPQMgsRnmrFVgt/message.txt > Jan 16 09:48:40 I don't wanna be that guy but could you send me the boot and system image? :p Jan 16 09:49:36 thanks it was successful now :D Jan 16 09:50:53 @nergzd723> @nergzd723 [btw yo" [yes], how can I contact you btw? Jan 16 09:51:27 me and a friend have been working on this for a while now If we get stuck atleast we'll have a source Jan 16 09:52:01 nergzd723:matrix.org xD or write me an email Jan 16 09:52:33 lmfao alright Jan 16 09:54:49 https://pastebin.com/B525HMB2 Jan 16 09:55:18 when i do make mrproper it says error Jan 16 09:55:32 which error? Jan 16 09:55:45 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/KlGLcCzNvOXTkWIIBZLuowRX/message.txt > Jan 16 09:55:52 unknown target mrproprt Jan 16 09:55:57 * unknown target mrproper Jan 16 09:56:24 make clean Jan 16 09:56:37 no don't Jan 16 09:56:45 Cd into kernel dir and do it there Jan 16 09:56:51 ohh right Jan 16 09:57:18 welp add this to docs :P Jan 16 09:57:43 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/aLJZCHqxyDdKEzAiWqIevgfq/message.txt > Jan 16 09:57:51 same like pmos port? Jan 16 09:58:22 what did you do then? Jan 16 09:58:32 did you do mrproper or clean in kernel dir btw? Jan 16 09:58:39 mrproper Jan 16 09:58:48 Ah okay Jan 16 09:59:03 as in find the thing and edit menuconfig? Jan 16 09:59:32 no, that's not it Jan 16 09:59:34 probably Jan 16 09:59:47 ugh but why can't it find it Jan 16 10:00:28 try make clean in halium and kernel dirs Jan 16 10:00:30 And try again Jan 16 10:00:34 It must work Jan 16 10:00:39 * mighty17[m] uploaded an image: image.png (15KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/PdMEyAsUUwirHawrXfRJqdbD/image.png > Jan 16 10:00:48 okay Jan 16 10:01:30 then `mka mkbootimg` again? Jan 16 10:02:19 yes, btw you might skip that if you already have mkbootimg in your host system Jan 16 10:03:05 skipped it anyways Jan 16 10:04:41 btw when do i need to apply the "many" patches for 3.4 kernel Jan 16 10:05:26 first, just build it :P Jan 16 10:19:08 Clamtacos was added by: Clamtacos Jan 16 10:22:08 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/CoVPtkzQhTnwCQflXYDeHakd/message.txt > Jan 16 10:24:18 ree its a proprietary blob Jan 16 10:25:15 any idea how to fic Jan 16 10:25:28 fix* Jan 16 11:03:54 uh that's the kind of issues I've been talking about xD Jan 16 11:04:00 weird dependency ones Jan 16 11:04:25 ooof but this is issue in lineage as well :/ Jan 16 11:04:44 https://www.reddit.com/r/LineageOS/comments/9rtnjn/build_issue_with_galaxy_tab_2_70_espressowifi/ Jan 16 11:04:58 but i dont understandd what to do :P Jan 16 11:05:02 https://github.com/TheMuppets/proprietary_vendor_ti/blob/master/omap4/graphics/SGX540_120/libsrv_init.so Jan 16 11:05:19 add that repo to path vendor/ti Jan 16 11:05:21 run repo sync and build again Jan 16 11:06:53 vendor/ti?! how Jan 16 11:07:31 add it to xml file... Jan 16 11:07:36 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/qfWmGeLVHCbAZqtKFtpwvNrJ/message.txt > Jan 16 11:07:44 it is vendor/samsung Jan 16 11:07:53 oh new vendor Jan 16 11:08:13 name="proprietary_vendor_ti" remote="them" Jan 16 11:08:27 and path vendor/ti Jan 16 11:08:41 ya gotcha Jan 16 11:17:02 ``` Jan 16 11:17:04 lmao again Jan 16 11:19:19 more hardware to include? Jan 16 11:26:28 no solution? Jan 16 11:30:01 bhatia1583 was added by: bhatia1583 Jan 16 11:46:43 anyone? Jan 16 11:49:43 https://github.com/LineageOS/android_device_samsung_espresso3g/blob/cm-14.1/proprietary-files.txt Jan 16 11:49:46 can this help Jan 16 11:51:22 do i need to get it from the device> Jan 16 11:51:25 ?* Jan 16 11:52:30 Do redmi 8 have official lineage os Jan 16 11:55:55 @mighty17[m] [anyone?], I'll take a look a few hours later busy rn Jan 16 11:56:15 @H@ñß9ñ [Do redmi 8 have official lineage os], you should be able to check it on their site Jan 16 11:56:42 okkay thanks Jan 16 11:58:05 @dopamine404 [you should be able to check it on their site], Already check it on GitHub not avaible Jan 16 11:58:14 you need to find another vendor/samsung Jan 16 11:58:22 Specifically for building for espresso Jan 16 11:58:40 apparently them doesn't have enough libs Jan 16 11:58:40 ah okay Jan 16 11:59:04 @H@ñß9ñ [Do redmi 8 have official lineage os], yup it does Jan 16 11:59:20 there is one specifically for espresso3g Jan 16 11:59:30 https://github.com/TheWiggles/proprietary_vendor_samsung_espresso3g Jan 16 11:59:55 Yes, that one has the files needed Jan 16 12:00:06 Yay! Jan 16 12:00:07 @H@ñß9ñ [Do redmi 8 have official lineage os], https://wiki.lineageos.org/devices/ginkgo/ Jan 16 12:00:20 @dopamine404 [yup it does], Do lineage foundation have telegram official group on telegram Jan 16 12:00:29 have no idea Jan 16 12:01:12 and remove the vendor/samsung or make a new one Jan 16 12:01:47 Redmi 8 olive not ginkgo Jan 16 12:02:00 Seem that they still not release yet Jan 16 12:02:08 ah Jan 16 12:02:09 Thanks Jan 16 12:02:13 @H@ñß9ñ [Seem that they still not release yet], yeah possible Jan 16 12:02:19 @H@ñß9ñ [Thanks], no problem man Jan 16 12:32:25 mount: .halium-install-rootfs.wmtru: mount failed: Operation not permitted. Jan 16 12:32:41 I came across this error while trying to use halium-install Jan 16 12:32:45 try sudo maybe? Jan 16 12:32:58 nope Jan 16 12:33:00 doesn't work Jan 16 12:54:05 rm those .halium-install folders and try again Jan 16 12:55:25 would have done that if they existed lmao Jan 16 12:55:44 this used to work like a week ago Jan 16 13:08:05 I fixed it Jan 16 13:08:08 have no idea how Jan 16 13:15:58 Error: Device for nexthop is not up. now I am getting this. Jan 16 13:20:15 fixed that too. Jan 16 13:31:34 so does it work? xD Jan 16 13:33:36 ehh kinda :p Jan 16 13:33:44 I am in pre-init right now Jan 16 13:33:50 not really sure how to proceed Jan 16 13:34:02 huh, weird Jan 16 13:34:05 CONFIG_AUTOFS4_FS=y not found in /proc/config.gz … CONFIG_DUMMY=y found in /proc/config.gz, must be disabled Jan 16 13:34:13 have you fixed rsyslogd? Jan 16 13:34:14 huh Jan 16 13:34:18 that shouldn't happen Jan 16 13:34:24 is in my diagnosis.log Jan 16 13:34:31 I am currently trying the halium rootfs Jan 16 13:34:40 try halium-boot Jan 16 13:34:46 hmm Jan 16 13:34:47 I haven't checked hybris-boot Jan 16 13:34:55 alright Jan 16 13:34:57 let me do that Jan 16 14:01:21 yas halium built!! Jan 16 14:01:40 `#### make completed successfully (01:44:58 (hh:mm:ss)) ####` Jan 16 14:03:50 now my kernel is 3.4 should i do Halium reference rootfs? Jan 16 14:03:55 ayee good job Jan 16 14:04:37 thanks dopamine404 Jan 16 14:05:58 @actuday [I was successfully able to build halium-boot.img after reverting the commit. Bui …], If you still working on it, check the commits here … Its for A20 but actually the same soc … https://gitlab.com/arpio/kernel_samsung_a20_halium/-/commits/master/ Jan 16 14:06:41 anyone?? what should i do Jan 16 14:06:56 maybe try ubuntu touch Jan 16 14:07:19 ahh, but 3.4 Jan 16 14:07:19 :O Jan 16 14:07:21 great job Jan 16 14:07:32 try Ubuntu Touch first Jan 16 14:07:41 If you want to run Ubuntu Touch Jan 16 14:07:49 better debug it than other distro Jan 16 14:07:54 I know ubuntu touch reqires 3.10 Jan 16 14:08:04 [Edit] I know ubuntu touch requires 3.10 Jan 16 14:08:31 no ubuntu touch req 3.4 Jan 16 14:08:44 okay!! Jan 16 14:09:14 I know ubuntu touc"> meh, you can patch it to work on older kernels, take hammerhead as an example Jan 16 14:09:18 ``` Jan 16 14:09:18 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. You may learn your device’s kernel version by finding “Kernel Version” in the About page of your Android settings. The kernel version can also be found in the Makefile at the top level of any Linux kernel source t Jan 16 14:09:18 Some Halium distributions may use a kernel as old as 3.4, such as Ubuntu Touch. Jan 16 14:09:20 also I think 3.4 works too Jan 16 14:09:44 can someone give me address to matrix room? Jan 16 14:10:10 btw mighty17 you might want to do this: https://docs.ubports.com/en/latest/porting/halium_7-1/Building.html Jan 16 14:10:17 set the console to tty0 Jan 16 14:10:27 ya i was reading that Jan 16 14:10:39 because it breaks almost every single time someone ports their device xD Jan 16 14:10:45 lol Jan 16 14:10:47 can someone give m"> #halium:matrix.org Jan 16 14:11:04 it will say you are not invited :/ Jan 16 14:11:34 @actuday [I was successfully able to build halium-boot.img after reverting the commit. Bui …], As far as I remember, add this to your manifest … https://github.com/LineageOS/android_hardware_samsung/tree/lineage-16.0 Jan 16 14:11:47 btw I'm honestly surprised you didn't hit any errors at all Jan 16 14:12:06 `If the type of the ‘data’ or ‘userdata’ partition is f2fs, you need to change it to ext4` Jan 16 14:12:18 only cache is f2fs so no changes right? Jan 16 14:12:29 yeah, probably Jan 16 14:12:34 lol lucky me Jan 16 14:12:46 Also you deleted the line with f2fs data I believe Jan 16 14:12:52 not the cache Jan 16 14:14:39 yes Jan 16 14:15:44 ` CONFIG_DEFAULT_SECURITY is set, but to y not "apparmor".` Jan 16 14:15:53 so change it to y? Jan 16 14:16:30 @arpio1 [As far as I remember, add this to your manifest … https://github.com/LineageOS/an …], It does contain the header file I'm missing. But what do I name it when adding the repository to the manifest? Jan 16 14:17:09 *to y not apparmor* Jan 16 14:17:19 I guess you should ignore it Jan 16 14:17:26 I think 3.4 doesn't support apparmor Jan 16 14:18:17 fixed it Jan 16 14:18:27 and it says CONFIG_VT is twice Jan 16 14:18:31 but i see it only once Jan 16 14:18:45 https://pastebin.com/evgGcZYK Jan 16 14:18:48 @actuday [It does contain the header file I'm missing. But what do I name it when adding t …], Nevermind, I'll look at the A20 manifest Jan 16 14:19:32 ... Jan 16 14:19:39 There is CONFIG_VT is not set Jan 16 14:19:44 that is # Jan 16 14:19:50 isnt # like comments Jan 16 14:19:51 and the second occurrence it's redefined as y Jan 16 14:19:57 No Jan 16 14:20:13 oh my bad Jan 16 14:20:18 If you first define it as =y then redefine it as # is not set it won't build it Jan 16 14:21:08 oh i removed the # and now 0 errors :D Jan 16 14:22:50 i need to build again now 😩 Jan 16 14:23:02 @actuday [Nevermind, I'll look at the A20 manifest], Its just the kernel. Just check the defconfig commits, if you build halium-boot, you won't have the size issue with the boot image. Jan 16 14:25:15 @arpio1 [Its just the kernel. Just check the defconfig commits, if you build halium-boot, …], I'm not sure I understand. I already built halium-boot. Jan 16 14:25:35 And there already is an entry for the kernel in my manifest. Jan 16 14:26:42 @arpio1 [Its just the kernel. Just check the defconfig commits, if you build halium-boot, …], And i found the patches where I probably could boot to gui, but I'm now on android 10😔. At least with the patches I can boot pmos Jan 16 14:33:20 @actuday [I'm not sure I understand. I already built halium-boot.], Thats actually all what you need. Flash halium-boot, @erfanoabdi gsi v10 and his samsung-usb-teathering patch. Your phone will stuck at samsung boot logo but you should have SSH if your kernel config is right. Jan 16 14:33:44 @arpio1 [Thats actually all what you need. Flash halium-boot, @erfanoabdi gsi v10 and his …], Alright. Thanks Jan 16 14:35:49 ``` Jan 16 14:35:49 [ 50% 5/10] Downloading initramfs to : /home...alium-boot_intermediates/halium-initramfs.gz Jan 16 14:35:49 Downloading https://github.com/halium/initramfs-tools-halium/releases/download/continuous/initrd.img-touch-armhf Jan 16 14:35:57 its stuck here Jan 16 14:36:45 isnt it like 4mb only Jan 16 14:37:08 @arpio1 [Thats actually all what you need. Flash halium-boot, @erfanoabdi gsi v10 and his …], Where do I get the GSI from? Google turned up nothing Jan 16 14:37:30 yeah Jan 16 14:37:44 @actuday [Alright. Thanks], If you have bootloop try try disabling tzdev … https://gitlab.com/arpio/kernel_samsung_a20_halium/-/commit/e7708d5d3dbee416a5850f2823c7ba61c2ddfa3b Jan 16 14:38:32 https://pastebin.ubuntu.com/p/FHp84zZJtb/ Jan 16 14:39:02 well see the pastebin Jan 16 14:39:59 `mka halium-boot` Jan 16 14:42:05 huh Jan 16 14:42:25 which kernel did you use? Jan 16 14:42:45 3.4 Jan 16 14:42:52 repo Jan 16 14:42:59 https://github.com/Unlegacy-Android/android_kernel_ti_omap4/blob/3.4/espresso/ Jan 16 14:43:34 what error are u talking about Jan 16 14:44:07 @NotKit [you can probably skip building systemimage for now and use halium_arm64 generic …], Where can I get the generic image from? Jan 16 14:45:19 mpilib Jan 16 14:45:28 did you enable it in config btw? Jan 16 14:45:32 @actuday [Where can I get the generic image from?], https://ci.ubports.com/job/UBportsCommunityPortsJenkinsCI/job/ubports%252Fcommunity-ports%252Fjenkins-ci%252Fgeneric_arm64/job/main/ Jan 16 14:46:11 I dunno Jan 16 14:46:33 I guess no there was nothing like that on wiki Jan 16 14:48:10 you don't actually need that library Jan 16 14:48:15 I wonder why it builds at all Jan 16 14:48:59 error: too many arguments to function 'count_leading_zeros' Jan 16 14:49:12 This is the issue but well it takes 2 args Jan 16 14:50:55 Is it way harder to Port Halium from a newer LineageOS Version like 18 oder 16.? Jan 16 14:57:40 perhaps disable building that lib? it's used for signature checks etc, but you don't need it Jan 16 15:00:49 https://gist.github.com/EralpCelebi/227800867a14a7208efec619503cb828 yikes. Jan 16 15:02:14 Okay will try Jan 16 15:26:02 there is nothing like `mpilib` Jan 16 15:27:57 `CONFIG_MPILIB=y` ? Jan 16 15:30:30 you need to not build it Jan 16 15:30:57 =n then? as it isnt there inthe defconfig Jan 16 15:32:31 weird, then something depends on Jan 16 15:32:32 it Jan 16 15:35:54 welp i did it = n and now i have Jan 16 15:37:58 it still builds, huh Jan 16 15:38:05 I don't really know how to fix that :P Jan 16 15:38:39 https://gist.githu"> ugh what, it worked last time I tried Jan 16 15:38:45 how did that break? lol Jan 16 15:39:57 welp where should i ask then Jan 16 15:40:50 it dosent make sense count_leading_zeros takes in 2 parameters Jan 16 15:40:56 so it shouldnt really error Jan 16 15:45:19 i will try with Halium reference rootfs Jan 16 15:45:32 `Once you have built the system.img from the android tree, you can download and install the rootfs using the halium-install script from the halium-scripts repository.` Jan 16 15:45:38 any idea how to do this nergzd723 Jan 16 15:46:56 get halium-install Jan 16 15:47:13 btw hybris-boot builds and halium-boot does not? that's strange af Jan 16 15:47:19 yup Jan 16 15:47:25 3.4 hacks :P Jan 16 15:47:29 how? Jan 16 15:48:17 meh you're building Linux Jan 16 15:50:28 ¯\_(ツ)_/¯ Jan 16 15:50:34 git clone? Jan 16 15:51:05 yes Jan 16 15:51:25 ``` Jan 16 15:52:45 https://gitlab.com/JBBgameich/halium-install Jan 16 15:52:47 use this one Jan 16 15:57:26 and then? Jan 16 15:57:35 ./halium-install... Jan 16 15:58:06 yes Jan 16 15:58:15 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/TAKCbvtwKOvyUzlifVByebuU/message.txt > Jan 16 16:19:48 nergzd723: `./halium-install -p halium ` Jan 16 16:19:48 where is system.img? Jan 16 16:21:09 out/target/product/espresso* Jan 16 16:21:14 somewhere there Jan 16 16:22:38 yup Jan 16 16:22:47 and i need to be in download mode or smth? Jan 16 16:22:59 oh in twrp cool Jan 16 16:23:20 @thiesyy [Is it way harder to Port Halium from a newer LineageOS Version like 18 oder 16.?], basically you need Android base and Halium version to match Jan 16 16:23:26 so 18 is not supported Jan 16 16:23:36 fck Jan 16 16:26:58 what to do after this `./halium-install -p halium ` Jan 16 16:29:16 reboot? Jan 16 16:29:37 yes Jan 16 16:29:48 and get an error xD Jan 16 16:30:21 how? Jan 16 16:30:26 i cant see anything in tab Jan 16 16:30:35 rndis interface should be up Jan 16 16:30:42 Check Debug Halium notes Jan 16 16:30:52 There are many ways to troubleshoot :D Jan 16 16:31:02 i cant understand xD Jan 16 16:31:25 lsusb shows Google Inc. Nexus 4 (fastboot) Jan 16 16:32:08 huh, that's weird Jan 16 16:32:14 what is in dmesg | tail? Jan 16 16:32:39 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/GdRhFEYTAuvnqpXOoBDxOZFm/message.txt > Jan 16 16:33:00 yay you got into hybris debug console Jan 16 16:33:15 oh :D Jan 16 16:33:29 https://docs.halium.org/en/latest/porting/debug-build/early-init.html Jan 16 16:33:31 read this Jan 16 16:33:48 i already did Jan 16 16:34:00 it confused me more Jan 16 16:35:28 ``` Jan 16 16:35:28 # uname -a Jan 16 16:35:28 Linux (none) 3.4.113-gd502f547-dirty #1 SMP PREEMPT Sat Jan 16 15:44:58 IST 2021 armv7l GNU/Linux Jan 16 16:35:30 pog Jan 16 16:36:09 * mighty17[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/ytbCxQXTTjxwyykJksZMOYKL/message.txt > Jan 16 16:36:53 :D Jan 16 16:36:57 check init.log Jan 16 16:37:03 https://pastebin.com/g9kis3Rk Jan 16 16:37:05 huh weird no diagnosis.log Jan 16 16:37:29 `mount: mounting /dev/block/platform/omap_hsmmc.1/by-name/DATAFS on /data failed: No such file or directory` reee Jan 16 16:37:35 make sure that is correct Jan 16 16:37:36 ya no diagonosis.log :v Jan 16 16:37:47 where? Jan 16 16:38:30 cd /dev/block/platform/ && find Jan 16 16:38:49 in telnet? Jan 16 16:39:03 yes Jan 16 16:39:06 and send the output Jan 16 16:39:37 ``` Jan 16 16:39:37 ~ # cd /dev/block/platform/ && find Jan 16 16:39:37 /bin/sh: cd: can't cd to /dev/block/platform/ Jan 16 16:40:13 ``` Jan 16 16:40:13 cat diagnosis.log Jan 16 16:40:13 No /proc/config.gz. Enable CONFIG_IKCONFIG and CONFIG_IKCONFIG_PROC Jan 16 16:40:32 * nergzd723 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/MasuhNKbeQvcXaVpDEtsmHxx/message.txt > Jan 16 16:40:43 * nergzd723 sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/CkzoDiGbNoMozKNUNCmHCLUj/message.txt > Jan 16 16:40:53 there is Jan 16 16:40:55 ls shows dev Jan 16 16:41:22 cd /dev && find | grep data Jan 16 16:41:48 ``` Jan 16 16:42:00 nothing, huh Jan 16 16:42:11 ig i neeed to enable those Jan 16 16:42:53 yeah Jan 16 16:43:18 they are enabled Jan 16 16:43:27 hehe Jan 16 16:43:32 now begins the fun part Jan 16 16:43:36 in defconfig Jan 16 16:43:49 those probably don't exist in 3.0 lmfao Jan 16 16:43:56 * those probably don't exist in 3.4 lmfao Jan 16 16:44:04 @thiesyy [fck], which device? Jan 16 16:44:13 S5 neo Jan 16 16:44:16 Samsung galaxy tab 2 Jan 16 16:44:17 I guess you should use halium-boot Jan 16 16:44:32 okay lets try Jan 16 16:44:33 it doesn't check ikconfig options Jan 16 16:44:42 and it doesn't need fixup-mountpoints Jan 16 16:44:50 but that issue with that library is weird Jan 16 16:44:58 ikr Jan 16 16:45:05 idk how to fix that either Jan 16 16:46:29 oh wait Jan 16 16:46:37 is it coz of console=tty0 thingy Jan 16 16:47:35 no, probably not Jan 16 16:48:02 welp Jan 16 16:48:10 atleast more prog than mainline :P Jan 16 16:49:53 https://docs.halium.org/en/latest/porting/debug-build/early-init.html#forcing-debug-mode Jan 16 16:50:24 hybris-boot won't work on your device, at least without patches Jan 16 16:50:36 you can make that lib compile Jan 16 16:50:41 it's not like it's used anywhere Jan 16 16:51:01 you can make that count_zeros build, edit it manually and remove the second argument or something Jan 16 16:52:43 reee Jan 16 16:52:45 later Jan 16 16:52:51 how do i go to twrp now Jan 16 17:01:27 but it takes 2 args :P Jan 16 17:01:39 oh wait Jan 16 17:01:41 yes Jan 16 17:03:57 removed 2nd arg Jan 16 17:04:10 or should i add 2 args where it is defineed Jan 16 17:05:17 @thiesyy [S5 neo], https://www.gsmarena.com/samsung_galaxy_s5_neo-6506.php? wasn't it released with Android 5? Jan 16 17:05:39 ok wow it built Jan 16 17:05:43 55 secs Jan 16 17:05:53 sure it did xD Jan 16 17:06:14 Has lineageos with android 10 Jan 16 17:06:37 i mean only 1 error seems sus Jan 16 17:06:40 Has lineageos with and"> Maybe try halium-7.1? Jan 16 17:06:53 There should be Android 7 port Jan 16 17:21:59 hi Jan 16 17:22:18 hi Jan 16 17:23:13 @Carlod[m] [hi], finally after 3 try Jan 16 17:23:34 @Carlod[m] [hi], [Edit] finally after 3 tryies Jan 16 17:37:38 Eli4s_Anyway was added by: Eli4s_Anyway Jan 16 17:51:06 nergzd723: size of image larger than device Jan 16 17:51:07 F Jan 16 17:57:04 halium-boot is around 9 mb Jan 16 17:57:04 BOARD_BOOTIMAGE_PARTITION_SIZE := 8388608 Jan 16 17:57:07 so wont work Jan 16 17:57:28 huh, boot.img too big? Jan 16 17:57:43 yep Jan 16 17:57:59 I guess you can try disabling some config options Jan 16 17:58:14 like what xD Jan 16 18:02:03 which are unnecessary? Jan 16 18:09:29 yeah, filesystems, networking... Jan 16 18:09:40 how big is boot.img? Jan 16 18:12:44 9.2mb Jan 16 18:12:50 ????/ Jan 16 18:18:58 mighty17, which is your device? Jan 16 18:19:17 @thiesyy [Has lineageos with android 10], yes, but it doesn't mean it has to be used for port Jan 16 18:19:30 Samsung Galaxy Tab 2 @NotKit Jan 16 18:20:05 uh, TI OMAP 4430... Jan 16 18:20:13 yup... Jan 16 18:25:15 @midhunvnadh were you the one porting for Redmi 7a (pine)? Jan 16 18:25:33 @NotKit [@midhunvnadh were you the one porting for Redmi 7a (pine)?], No Jan 16 18:26:22 uh, TI OMAP 4430..."> well what now Jan 16 18:29:52 I'm not sure. There may be some workarounds, like using stronger ramdisk compression like lzma, or chainloading from another partition using a smaller ramdisk Jan 16 18:34:07 welp i dunno about anything like that Jan 16 18:34:51 mighty17, you should be probably able to drop udev from from halium-boot ramdisk to make it smaller Jan 16 18:35:29 i dont understand xD Jan 16 18:37:37 you probably need to unpack the ramdisk, modify it, repack it again, do mka halium-boot Jan 16 18:37:55 first check the size of zImage Jan 16 18:37:58 It might be that it's too big already xD Jan 16 18:38:15 zImage? in out dir? Jan 16 18:38:39 I don't know where it stores the kernel build results Jan 16 18:38:51 usually it's in arch/arm/boot/zImage Jan 16 18:39:44 yup Jan 16 18:39:45 I'm not sure. There may"> yeah, something like isorec on exynos 4412 might work Jan 16 18:39:54 5.3 mb Jan 16 18:39:59 > <@nergzd723:matrix.org> first check the size of zImage Jan 16 18:40:00 * 5.2 mb Jan 16 18:40:32 huh that's good... I'd say, so you'd need to fit halium-boot ramdisk in 2.8MB xD Jan 16 18:40:44 lol Jan 16 18:40:53 boot.img can go to 8mb max ig Jan 16 18:41:15 mainline was 4.9 mb Jan 16 18:41:29 how can i do that Jan 16 18:41:53 I believe the ramdisk is 3.85MB Jan 16 18:42:08 androidramdisk? Jan 16 18:42:20 no, this https://github.com/Halium/initramfs-tools-halium/releases/tag/continuous Jan 16 18:42:42 yup Jan 16 18:43:14 https://github.com/Halium/initramfs-tools-halium/blob/38ccd90825a1d241ddbe682799ac7ae6fdece5e3/build-initrd.sh#L46 Jan 16 18:43:20 I guess you'd need to edit this Jan 16 18:43:31 although idk, fitting it in 8MB might be tricky Jan 16 18:43:41 making the kernel smaller should be better :( Jan 16 18:44:03 ya Jan 16 18:44:11 removing more conifgs!!! Jan 16 18:44:35 but which ones? Jan 16 18:44:51 hm Jan 16 18:44:56 I don't think it's reasonable with kernel Jan 16 18:45:00 https://pastebin.com/pNMiXjVQ Jan 16 18:45:21 you can't realistically strip 1 mb from 5.3 mb compressed kernel already Jan 16 18:45:22 hybris is 5 mb tho Jan 16 18:46:02 wut, how comes halium-boot is much larger than hybris-boot Jan 16 18:46:20 you can't realistically"> /shrug I have no experience with shrinking downstream Jan 16 18:46:40 halium-boot = 9.2mb Jan 16 18:46:40 hybris-boot = 5.5 mb Jan 16 18:46:40 hybris-boot ramdisk includes just busybox Jan 16 18:46:55 is it coz of ugly hax i did (that lib thingy) Jan 16 18:46:58 halium-boot ramdisk pulls in systemd-udev, glibc and few other binaries Jan 16 18:47:05 yup ^^ Jan 16 18:48:10 i can try removing only one and see Jan 16 18:48:18 but arent they all important Jan 16 18:49:05 you can probably boot without udev, but will need to specify datapart=/dev/mmcblkxpx in cmdline as this will break the logic for finding it by label Jan 16 18:49:14 halium-boot ramdisk pul"> so can he edit the initramfs-tools .sh script and then try to build that rootfs again? Jan 16 18:49:41 or just repack ramdisk, usually that works for me Jan 16 18:49:54 Also it depends on libc6-dev, do we really need -dev version of glibc? Jan 16 18:50:03 or just repack ramdisk,"> how do i do that Jan 16 18:50:16 cpio magic Jan 16 18:50:37 idk what that means Jan 16 18:50:53 I think it's done with some cpio command Jan 16 18:51:23 ah i see Jan 16 18:51:39 copy in copy out Jan 16 18:53:21 anyways i will wait for a definitive answer :D Jan 16 18:55:50 btw where is that file Jan 16 18:55:53 i cant seem to find it Jan 16 18:58:03 initramfs-tools-halium/build-initrd.sh Jan 16 18:58:11 no such folder Jan 16 18:58:24 well, clone it :D xD Jan 16 18:58:36 oh lol Jan 16 23:36:17 golliath51 was added by: golliath51 Jan 16 23:41:25 repo init -u https://github.com/Halium/android -b halium-9.0 --depth=1 … File "/home/david/halium/.repo/repo/main.py", line 79 … file=sys.stderr) … ^ … SyntaxError: invalid syntax Jan 16 23:41:36 help me please Jan 16 23:44:05 which version of python i should use for halium 9 Jan 16 23:44:27 2.7 or 3.6 Jan 16 23:44:39 which one are you using right now? Jan 16 23:44:48 2.7 Jan 16 23:44:53 try 3.6 Jan 16 23:44:58 [Edit] try 3 Jan 16 23:45:07 this is the same result Jan 16 23:46:31 may be a wrong change Jan 16 23:48:22 I work on VM on Ubuntu18.04 Jan 17 00:31:01 anarchist47 was added by: anarchist47 Jan 17 00:36:15 3.6 has the same error as 2.7? Jan 17 02:41:45 Well what am I supposed to do **** ENDING LOGGING AT Sun Jan 17 02:59:57 2021