Monday, 2023-03-20

T42<b100dian> @elros34, mal: asus sake update - I got a reboot in 30s. I backed out my init shell changes, and I got a reboot in 60 seconds (this is progress;). The key was to 1. pack ramdisk with `lz4 -l` and 2. unpack_bootimg hybris-recovery.img and repack with mkbootimg --header_version 3 and no cmdline (cause it's in the vendor_boot)00:05
T42<k1gen> replace symlinks in same directory and under same names? for example, I have /vendor/etc/selinux/precompiled_sepolicy - I pull it from my device over adb and place it in hybris/droid-configs/sparse/etc/selinux/minimum/policy, but with name policy.30, right? (re @elros34: just copy sony's dro...)07:25
T42<elros34> yeah, this is how symlinks works but in your case symlinks are not valid untill you mount /vendor that is why you need real files07:29
T42<k1gen> got it. can I build now?07:30
T42<elros34> sure but no idea whether you made all needed changes. In bot cases this will be not you last build07:32
T42<elros34> both*07:32
T42<k1gen> --droid-hal says ERROR: CONFIG_DUMMY is invalid, though I have =n in defconfig and recompiled kernel already07:40
T42<k1gen> here's the log:
T42<elros34> but that is not first error:
T42<k1gen> should I hardcode the path like here? (re @elros34: but that is not firs...)07:55
T42<k1gen> weird, # CONFIG_DUMMY is not set in out/target/product/flame/obj/KERNEL_OBJ/.config07:57
T42<k1gen> but it's =n in defconfig07:57
T42<elros34> yes07:59
T42<k1gen> so how do I fix this? (re @k1gen: --...)08:00
T42<elros34> are you serious? You got the commit with fix and confirmation to add it like that and you ask what to do?08:01
T42<k1gen> so your "yes" was a reply to this, got it (re @k1gen: should I hardcode th...)08:02
T42<k1gen> thanks for helping08:02
T42<elros34> it could be for both of your messages08:04
T42<k1gen> cp: cannot stat './out/target/product/flame/hybris-updater-script': No such file or directory08:05
T42<k1gen> somehow my self-defined /boot got ignored, I think08:05
T42<elros34> did you even build hybris-hal?08:06
T42<k1gen> sure08:06
T42<elros34> without errors?08:06
T42<k1gen> without. I can rebuild if that's the problem08:07
T42<elros34> I bet it is and there were at least one error/warning08:08
T42<k1gen> that's what I thought, script can't find my fstab:
T42<k1gen> I think I should symlink flame to coral in device/google08:15
T42<k1gen> ah, it's already a symlink08:17
T42<k1gen> just copy fstab.hardware then08:17
T42<elros34> but you have fstab in out/ and it's found08:22
T42<k1gen> yes, but then why HYBRIS_BOOT_PART is not specified?08:25
T42<elros34> because there is no valid boot entry there08:29
T42<k1gen> @elros34 I fixed hybris-updater-script thing, can you help me with this:
T42<k1gen> that's after rebuilding hybris-hal09:55
T42<k1gen> why are there two kernel releases?10:10
T42<k1gen> anyone? should I make clean hybris-hal?10:21
malyou mean two rpms in droid-local-repo?10:22
T42<elros34> it's probably the same kind of issue with DTB_OBJ in same file but some different line10:26
T42<k1gen> mal: I mean kernel_release='4.14.212-g1addaa15f7c2 4.14.212-g2d9ce94d3138'10:31
T42<elros34> this is old bug but nobody who have it is willing to fix it maybe you will10:35
T42<k1gen> do I need to ignore dtb kernel_release and pick KERNEL_OBJ one?10:40
T42<elros34> like with the commit, you need to ignore DTB_OBJ directory when evaluate some kernel dir/files10:43
T42<k1gen> got it, let me try10:44
T42<k1gen> fixed this, got another error:
T42<k1gen> Building of droid-hal-flame finished successfully :D11:27
T42<k1gen> --mw can't find ccache, how do I install it?11:33
T42<k1gen> I installed ccache with zypper, it doesn't help:
mal@elros34 do you remember if hadk pdf has any known issues, the repo init url fix I have already done, was there some package installs that are needed in addition to that is told in hadk?12:03
T42<k1gen> cpio is needed to build hybris-hal iirc12:04
T42<k1gen> does anyone know how to install ccache in this environment? (re @k1gen: I installed ccache w...)12:14
malsb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -m sdk-install zypper in ccache12:20
T42<k1gen> thank you!12:21
mal@k1gen which package had issue with ccache?12:27
T42<k1gen> mal: pulseaudio-modules-droid12:28
T42<k1gen> Fatal: 'rpm/kf5bluezqt-bluez4.spec' does not exist (and could not be made from a .yaml)12:29
T42<k1gen> does this error have something to do with ?12:29
T42<k1gen> I resolved it by modifying build_packages.sh12:32
T42<k1gen> droid-hal-version won't build:
malI'm fixing dhd submodule, that and other issue13:03
T42<k1gen> mal: thanks13:04
T42<k1gen> could you send commit link when you finish so I can merge changes locally?13:06
T42<k1gen> by the way, after I finish porting and get a functional device (I hope), will I have the same Sailfish OS version anyone owning an xperia has besides paid features like Android App Support?13:11
T42<k1gen> nice :D13:26
T42<k1gen> mal: I'm sorry, are you still working on the fix?18:04
malyes, there are many things to fix18:05
malI was also fixing some other things parallel to this18:06
T42<k1gen> mal: it's 11:24PM here, I'm going to bed, hope to continue porting tomorrow. please, ping me once you finish fixing droid-hal-version builddeps. goodnight :)21:26
T42<elros34> mal: definitely missing cpio in habuild, outdated mk-cam-conf instruction, repo sync --fetch-modules shouldn't be used for hybris-18, latest url in sdk target installation is never up-to-date when needed so instead there should be tip to use versioned url, remove hardcoded touch node from evdevtouch:/dev/input/event0 when creating droid-hal-device.conf21:26
T42<k1gen> damn, you wrote that in less than a minute?21:27
T42<k1gen> that's all applicable to hadk pdf, right? that's not for me21:28
T42<elros34> mal: 9.3.1 outdated instruction to add droid-hal-hammerhead-detritus, outdated instruction which never helps for masking  /etc/systemd/system/ofono.service when device reboots after minute, outdated instruction for disabling selinux on > android 4.421:31
T42<elros34> mal: 11.1 IIRC sfos archive is now tar.gz not bz2.  Also I think there should be link to somewhere before first make hybris-hal. These are just minimal changes which I think should be done21:40
T42<elros34> @k1gen yeah it was about pdf. You issue is explained in hadk-hot21:42
T42<k1gen> this one? (re @k1gen: droid-hal-version wo...)21:43
T42<elros34> yes that common one21:44
T42<k1gen> thanks for help, didn't see it earlier. building rootfs22:02
T42<k1gen> if I put only _a partitions in fixup_mountpoints, should I have to switch to boot slot a first? also, what android version should I flash before flashing sfos?22:05
T42<k1gen> first one is a stupid quesion, I know. just want to verify22:05
T42<elros34> isn't 'a' default and what use normally use? About android then obviously the one which you used as base hybris-18 -> lineage-1822:07
T42<k1gen> b was the default on three a/b devices I owned22:07
T42<elros34> so what would happen if boot fails, auto switch to 'a'?22:09
T42<k1gen> bootloader loop most of the time22:12
T42<elros34> anyway I do not know how ecatly this slots works, just make sure you use the one which you choose when creating fixup-mountpoints22:14
T42<k1gen> yeah, got it22:14
T42<k1gen> after fixing ofono/binder.conf, got this error:
T42<k1gen> already ran sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper --plus-repo $ANDROID_ROOT/droid-local-repo/$DEVICE in droid-config-$DEVICE-bluez522:22
T42<k1gen> should I add something like Provides: bluez5-configs Obsoletes: bluez5-configs-mer to droid-config-device?22:24
T42<elros34> removing bluez5-configs-mer isn't enough?22:25
T42<k1gen> so no Provides line?22:30
T42<elros34> nothing bad will happen if you add it:)22:32
T42<elros34> I hope so22:32
T42<k1gen> if there's no other way... (re @elros34: I hope so)22:34
T42<k1gen> alright, rootfs built22:52
T42<k1gen> goodnight, now I can sleep peacefully :D22:53
mal@elros34 thanks for the list of issues23:05

Generated by 2.17.1 by Marius Gedminas - find it at!