| rinigus | piggz: did it work last night? | 05:59 |
|---|---|---|
| Decked | Hello everyone, I've been having some trouble porting SailfishOS to an old LG G2, is this the right place to ask? | 07:02 |
| Decked | I'm not sure if this is even working, I've never used IRC to begin with | 07:02 |
| T42 | <Herrie1982> @Decked [I'm not sure if this is even working, I've nev …], It is working, yes this should be the right place | 07:10 |
| Decked | Great, thanks. | 07:11 |
| T42 | <Herrie1982> G2 is quite similar to Nexus 5 in terms of specs | 07:11 |
| T42 | <Herrie1982> There might be something done for it already | 07:11 |
| Decked | I see, can I ask a small thing anyway? | 07:13 |
| T42 | <Herrie1982> Sure you can ask, I'm not an expert on SFOS porting, but might be able to give you an answer, otherwise the other people here could. | 07:17 |
| Decked | So I was trying to port Sailfish os from Lineage 17.1, but I'm now stuck on part "7.2.1 Building the droid-hal-device packages". When I use the command `rpm/dhd/helpers/build_packages.sh --gg` the script can't build gst-droid.spec because it says it's missing gstreamer-photography-1.0. I've checked and it's gstreamer1.0-plugins-bad is already installed on both the PlatformSDK and on the The Target_SDK | 07:20 |
| Decked | I tried removing the dependency on meson.build since I'm sure it's already installed but it fails somewhere else because there is still the dependency defined somewhere else | 07:22 |
| T42 | <Herrie1982> I'm not sure how well 17.1 is working for SFOS port. For most other OS-es (UBPorts, LuneOS, Mobian etc) using Halium project) they're using either a 12.1, 14.1 or 16.0 based CM/LOS). I haven't done any SFOS ports myself, so cannot really help you there. | 07:23 |
| Decked | I'm pretty new on SailfishOS but I saw that they added Android 10 support as of lately so I thought to give it a chance. From my understanding this problem isn't even related to the Android base and I can't find anything on the FAQs or IRC logs | 07:26 |
| Decked | Anyways, thanks a lot either way, I'm sorry to trouble you | 07:29 |
| rinigus | Decked: I wonder whether you use too new gst-droid. check the version that you try to build against sfos 4.0.1 changelog | 07:30 |
| Decked | Hmm other than the fact that Gstreamer will be replaced by MW I can't find anything. I'll try building it without it and report back | 07:37 |
| rinigus | Decked: the repos are checked out under hybris/mw/, so see the version of gst-droid over there. for sony tama, I had to build gst-droid manually, without using -gg | 07:51 |
| Decked | Looks to me as 1.0.0 | 08:00 |
| rinigus | check with git log | 08:01 |
| rinigus | I am using 0.20210304.0 | 08:01 |
| Decked | I see 0.20210430.0 | 08:01 |
| rinigus | that could be too new. checkout older version and build using rpm/dhd/helpers/build_packages.sh --build=hybris/mw/gst-droid | 08:03 |
| rinigus | Decked: otherwise it will checkout the newest version again. | 08:04 |
| Decked | Seems to have worked! thanks a lot | 08:06 |
| rinigus | maybe this will help a bit - https://github.com/sailfishos-sony-tama/main/blob/hybris-10/hadk-sony-xz2.md . grep for gst- and there is an instruction next for gmp-. those replace -gg build | 08:06 |
| Decked | You suggestion worked perfectly, I changed to configuration to exclude gstreamer1.0-droid, ran --gg, after that I included it again and built gst-droid on 0.20210304.0 as you suggested | 08:09 |
| Decked | I'm now building the rootfs (I think) | 08:10 |
| Decked | For some reason my PC is complaining about my Wacom Tablet being disconnected and reconnected when building it O.o but alright | 08:10 |
| Decked | Time to see if it boots | 08:12 |
| Decked | Ugh failed to extract filesystem, what now | 08:15 |
| rinigus | Decked: maybe someone can chip in with fs extraction, my port is not based on lineageos and has different mic packing | 08:17 |
| rinigus | I suggest to get a log with the error, paste on pastebin-type site and send URL over here. maybe someone can look and help you | 08:18 |
| Decked | I'm using the lineageos recovery, could that be the reason? | 08:18 |
| Decked | [ 268.902183] tar: exec bunzip2: No such file or directory | 08:24 |
| Decked | Here's the problem | 08:24 |
| rinigus | Decked: you mean to flash it? no idea, we used to use twrp for lineageos based ports... don't know how it is now | 08:26 |
| Decked | Yeah, I might try flashing TWRP first | 08:27 |
| Decked | Oh this is a problem | 08:42 |
| Decked | TWRP worked but got out of memory before finishing | 08:42 |
| T42 | <b100dian> Decked: I don't have bunzip2 in twrp either. I am flashing the boot img with fastboot or with twrp then use something along these lines for pushing the unbzipped tar and exctracting it on device https://pastebin.ubuntu.com/p/4sFnxbnZGS/ | 08:49 |
| Decked | Well my TWRP has bunzip2 installed with it but now the installation fails because the phone runs out of memory | 08:52 |
| Decked | Using tar manually on adb shell also fails because it runs out of memory | 09:03 |
| T42 | <Herrie1982> We had some issues with tar on LuneOS from TWRP | 09:23 |
| T42 | <Herrie1982> I think we use the busybox one now to do the unpacking | 09:23 |
| T42 | <Herrie1982> @Herrie1982 [I think we use the busybox one now to do the u …], Yes see https://github.com/webOS-ports/android-update-package/commit/ad157df224ddc6ece8d641309c8c4b606c7650b4 | 09:30 |
| Decked | I see | 09:33 |
| Decked | Replacing busybox in TWRP did the trick thanks a lot | 09:51 |
| T42 | <Herrie1982> Some of these funny quirks... | 09:57 |
| Decked | Hmm the phone won't boot after flashing, something something boot verification failed. | 10:02 |
| T42 | <elros34> Decked, I guess you are booting android now. Follow 2 kernel related points from: collabedit.com/kr9xx. That wont be enough to get gui on 17 base but maybe at least telnet. | 10:25 |
| Decked | @elros34 sorry for the late reply, I'm not booting from Android, it's the phone itself that refuses to boot anything after flashing boot.img | 12:43 |
| T42 | <elros34> If You didnt follow advices mentioned in that url then your are probably missing sailfish specific initramfs in hybris-boot.img and your kernel might be trying to boot from /system partition so you are basically booting android | 12:46 |
| T42 | <elros34> also flashing boot.img is wrong, you must use hybris-boot.img | 12:47 |
| Decked | Yeah I did that | 12:47 |
| Decked | Sorry I mispelled | 12:48 |
| Decked | But I'm 90% sure I'm not booting android, in fact I don't think I'm booting anything at all | 12:48 |
| Decked | With the phone in that state plugging it via USB shows me the various MMC partitions as if I'd plugged in an hard drive and the recovery is unaccessable anymore | 12:49 |
| T42 | <elros34> most important is to check how device shows in host dmesg: as android or mer boat loader | 12:50 |
| Decked | [ 6735.911416] scsi 6:0:0:0: Direct-Access Qualcomm MMC Storage 1.00 PQ: 0 ANSI: 2 | 12:53 |
| Decked | Nothing else | 12:53 |
| Decked | lsusb shows Bus 001 Device 019: ID 05c6:9006 Qualcomm, Inc. QHSUSB__BULK | 12:54 |
| T42 | <elros34> is that first messega after you flashed hybris-boot or several reboots later? | 12:54 |
| Decked | After I flashed hybris-boot, but the phone refuses to boot it whatsoever | 12:54 |
| Decked | I'm 100% sure that the kernel didn't even load | 12:55 |
| Decked | nor the bootloader | 12:55 |
| T42 | <elros34> so did you needed to revert skip_initramfs | 12:55 |
| T42 | <elros34> ? | 12:55 |
| Decked | The phone is a LG G2 from 2013 so I skipped that part | 12:56 |
| Decked | I don't think that applies to it | 12:56 |
| T42 | <elros34> so it doesn't use system as root? | 12:56 |
| Decked | I don't know, I know it uses a separate recovery partition though | 12:58 |
| T42 | <elros34> check in fstab where system partition is mounted, in / or in /system | 12:59 |
| Decked | From android right? | 13:00 |
| T42 | <elros34> in device repo you will find fstab | 13:00 |
| Decked | Sorry about my ignorance but I don't follow you | 13:02 |
| Decked | I don't have any fstab files other for the ones for the initramfs | 13:04 |
| T42 | <elros34> https://github.com/LineageOS/android_device_lge_g2-common/blob/lineage-17.1/rootdir/etc/fstab.g2#L14 | 13:05 |
| Decked | Oh my bad I searched for fstab only | 13:06 |
| T42 | <elros34> maybe vbmeta then, don't you have such a partition? | 13:08 |
| Decked | Hmm the phone is basically bricked at this point let me try to fix it and I'll get back to you | 13:10 |
| Decked | Ok managed to get into the recovery, there's no vbmeta partition | 13:11 |
| Decked | DDR cache dbibak fota grow modem mpt pad2 recovery sbl1 ssd tz | 13:12 |
| Decked | aboot cust drm fsc laf modemst1 pad persist rpm sns system tzbak | 13:12 |
| Decked | boot dbi encrypt fsg misc modemst2 pad1 rct rpmbak spare tombstones userdata | 13:12 |
| Decked | Realistically I should have tried to port Sailfish from an older LineageOS version | 13:13 |
| piggz | rinigus: why would tbuilder not auto install a deb that is available? | 15:31 |
| piggz | https://paste.mozilla.org/GSRcf9WC | 15:31 |
| rinigus | piggz: it caches the available dependencies. remove caches in the build folder | 15:33 |
| rinigus | let me write it into the docs as well | 15:33 |
| rinigus | piggz: caches described in the updated readme of tbuilder | 15:42 |
| piggz | rinigus: now another issue finding some packages | 15:47 |
| piggz | rinigus: ah, failed to install because of sig verification | 15:50 |
| piggz | you must have had that? a workaround? | 15:52 |
| rinigus | piggz: you could either add repo with an option to disable sig check out run zypper refresh manually in target (not snapshot) and accept non signed repo | 16:06 |
| piggz | rinigus: now, a funky file path is missing Cannot find file: /parentroot/data/piggz/mer/android/tbuilder/amazfish-build/src/harbour-amazfish/parentroot/data/piggz/mer/android/tbuilder/amazfish-build/build/SailfishOS-4.0.1.48-armv7hl/harbour-amazfish.spec. | 16:15 |
| piggz | this folder exists and is the source /parentroot/data/piggz/mer/android/tbuilder/amazfish-build/src/harbour-amazfish/ | 16:16 |
| piggz | but there shouldnt be a parentroot/ in there | 16:16 |
| rinigus | piggz: ohhh, that's something unexpected | 16:19 |
| rinigus | do you compile with "shadow_builds"? | 16:20 |
| piggz | shadow_builds: | 16:21 |
| piggz | - harbour-amazfish.spec | 16:21 |
| piggz | i just copied that from the example | 16:21 |
| rinigus | would you mind to try without? | 16:21 |
| rinigus | just remove that option. not sure if it will help | 16:22 |
| piggz | rinigus: yeah, that seems to be building now | 16:23 |
| rinigus | to see where that issue came, please check how symlink was defined in spec. ls -l spec? | 16:24 |
| piggz | lrwxrwxrwx 1 piggz piggz 49 May 2 20:12 harbour-amazfish.spec -> ../src/harbour-amazfish/rpm/harbour-amazfish.spec | 16:34 |
| piggz | looks ok | 16:34 |
| rinigus | piggz: it does look fine, indeed | 16:43 |
| rinigus | piggz: but I wonder where is this /parentroot sneaking in? let me find check if I can reproduce it | 16:46 |
| T42 | Tz %lastname% was added by: Tz %lastname% | 16:59 |
| T42 | <Tz %lastname%> https://t.me/joinchat/2l_0GNGNKwtkOWY0 | 17:30 |
| rinigus | piggz: just in case - is src/harbour-amazfish folder or a link somewhere further? | 17:51 |
| T42 | <adampigg> A folder | 17:52 |
| rinigus | @adampigg: I tried to reproduce it with /parentroot/tmp/test and a project under it, but no luck. no such weird path. | 18:29 |
| rinigus | would you mind to paste build.log for failing case? just define using shadow_builds as before and touch the spec to start the rebuild | 18:29 |
| rinigus | would also help to have `pwd` from the shell where you run tbuilder | 18:30 |
| T42 | <adampigg> rinigus: i warn you, my path is a funny one (tho it has always worked) | 18:57 |
| rinigus | piggz: not sure about "always", let me grep the logs | 18:58 |
| rinigus | :) | 18:58 |
| T42 | <adampigg> PlatformSDK [piggz@linux-f1uu amazfish-build]$ pwd | 18:59 |
| T42 | <adampigg> /home/piggz/mer2/android/tbuilder/amazfish-build | 18:59 |
| T42 | <adampigg> the funny bit: | 18:59 |
| T42 | <adampigg> PlatformSDK [piggz@linux-f1uu amazfish-build]$ file /home/piggz/mer2 | 18:59 |
| T42 | <adampigg> /home/piggz/mer2: symbolic link to /parentroot/data/piggz/mer/ | 18:59 |
| rinigus | piggz: OK, I will try with something similar. let's see | 19:02 |
| rinigus | if I can reproduce | 19:02 |
| piggz | rinigus: background.... | 19:03 |
| piggz | all my builds happen on my spinning disk, as it has space, mounted in /data, in /data/piggz/mer | 19:03 |
| piggz | all the scripts/docs usually use ~/mer as a folder, so i made that a symlink | 19:04 |
| piggz | but, once in the sdk, that symlink doesnt work, so, i made another mer2 which works from within the sdk | 19:04 |
| piggz | ANDROID_ROOT uses that one | 19:05 |
| rinigus | Yeah, I used to use something like it, but ended up settling with just home. Let me see if I can reproduce it with symlinks in the path | 19:12 |
| rinigus | piggz: nope, it still works here as well. if I make ~/tmp/test -> /parentroot/tmp/test and use ~/tmp/test/subdir as a project dir, all seems to be resolved fine | 19:28 |
| rinigus | it detects that build should be done in /parentroot/tmp/test/subdir/build/SailfishOS-4.0.1.48-aarch64/yamui.spec (which will fail, but for other reasons). no double parentroot in the path | 19:29 |
| rinigus | as you have | 19:30 |
| piggz | ok, i just wont use shadow build | 19:30 |
| piggz | for now, until i can be bothered debugging | 19:30 |
| rinigus | let's stick with that :) | 19:30 |
| rinigus | many packages don't support it anyway, so it is easier to do without. I can build few of my own with the shadow builds, but not the port | 19:32 |
| Umeaboy | Hi! Is there a fix for the python error when running the repo init command for hybris-17.1 ? | 21:09 |
| T42 | <b100dian> You can run repo commands outside of the platformsdk shell | 21:10 |
| Umeaboy | I OK. | 21:11 |
| T42 | <elros34> or use python2 compatible repo from same site you have downloaded python3 one | 21:11 |
| Umeaboy | The HABUILD_SDK python version is 3.4 and 3.5+ is needed. | 21:16 |
| Umeaboy | Isn't it time to update the chroot to a newer version of Ubuntu ? | 21:17 |
| Umeaboy | It would get rid of this issue as the python version would be more correct. | 21:18 |
| Umeaboy | Just saying. | 21:21 |
| T42 | <elros34> for older devices is good to have old ubuntu chroot for compability reasons, for newer device you just don't need to use chroot at all | 21:23 |
| T42 | <b100dian> I was also wondering, so one could just build the android bits in the host system and call it a day? | 21:28 |
| T42 | <b100dian> So, I now have different crashing services (other than servicemanager) since i added LD_PRELOAD here https://github.com/b100dian/droid-config-tucana/commit/53536e2cc4861556d69b846d0d0599158ae2fddb for servicemanager.rc and then added the cheesburger init files (parent commit). Here is the sys/fs/pstore output: https://pastebin.ubuntu | 21:38 |
| T42 | .com/p/qBMsQ9Nfz3/ | 21:38 |
| T42 | <b100dian> Maybe you can help with any of the questions: | 21:38 |
| T42 | <b100dian> Q1: `drv2604_firmware_load, ERROR!! firmware not found` at about 12th second: this is not built as a module, however systemd seems to run the mounts before that, wondering why it doesnt find the firmware. | 21:38 |
| T42 | <b100dian> Q2: There are now other services crashing, do they also need the LD_PRELOAD patch? Or do they need listing in disabled_services.rc? (grep for `>>>`. Example: /system/bin/hw/android.system.suspend@1.0-service) | 21:38 |
| T42 | <b100dian> Q3: Reboot at second 88: `adsp subsystem failure reason: err_qdi.c:450:EF:sensor_process:1:dog_virtual_user.c:240:USER-PD DOG detects stalled initialization, triage with IMAGE OWNER.` Does this sound familiar? I've recently switched audio and wlan to modules, but they seem to not be loaded automatically from rootfs's /lib/modules, in | 21:38 |
| T42 | fact, some "disagrees about version of symbol module_layout" messages are around second 41 which indicate modules are loaded from .. /vendor/lib maybe? (the untouched vendor partition..) | 21:38 |
| *** Sellerie3 is now known as Sellerie | 21:38 | |
| Umeaboy | elros34: Would you happen to know how it works to patch a newer release of Lineage once it's released? I'm curious about how it works. I know we can see all the commits, but I mean, what decides that that file should be patched so that the Hybris image can be built? My phone uses a unofficial version of Lineage 18.0, but the latest official version of Lineage is 18.1 | 21:45 |
| T42 | coddato was added by: coddato | 21:49 |
| T42 | <coddato> Hi Is there a build for herolte ? | 21:50 |
| T42 | <elros34> Umeaboy: latest patches are for lineage-17 not 18. Preparing patches for lineage 18 is not trivial so without having some knowledge and spend a lot of time you will not be able to do this. I only patched some vendor sdk android sources once using existing patches for older base and even that wasn't piece of cake | 21:55 |
| Umeaboy | coddato: Yes: https://forum.xda-developers.com/t/sailfish-os-for-the-samsung-galaxy-s7.3745646/ | 21:56 |
| T42 | <elros34> @b100dian I am wondering why do you add hybris-16 rc files if you are using hybris-17? | 22:04 |
| T42 | <elros34> dmesg is not enough to figure out what is wrong, you should check logcat and journal. | 22:04 |
| T42 | <b100dian> Not that clever, right? Just trying everything I did not try. So you're saying i should back off the cheesburger init stuff because it was lineage-16 specific | 22:05 |
| T42 | <elros34> I thinks you should follow hybris17 device repos: xperia x10 II, fp3 and probably some other devices | 22:06 |
| T42 | <elros34> here is another device (no idea whether this one works): https://github.com/SailfishOS-sagit/droid-config-sagit | 22:10 |
| T42 | <b100dian> Thanks, I'll try to look more into those. The xiaomi sagit seems promising:) - I know you said you dont' know if it works, just cheering that I recognize some patterns | 22:20 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!