Thursday, 2021-08-26

T42<birdzhang> @XAP2P
mighty17[m]<skvorl> I don't own a pinephone sadly, and making it work on other device sounds too much work04:34
mighty17[m]<mal> "mighty17: sfos can run even on..." <- As hybris is an integral part of sfos?04:34
T42<XAP2P> Very thanks! (re @birdzhang: @XAP2P https://githu...)08:42
malmighty17[m]: libhybris is not a requirement for sailfish if there are proper drivers available for everything08:57
T42<edp_17> When building gmp-droid, I am getting this error:
T42<edp_17> I am on commit b61b740987a9880fccf5401220644c7dcf184be209:00
T42<edp_17> How can I solve it?09:00
T42<edp_17> Ignore the error I reported on gmp-droid. After re-cloning, it built fine! 👍10:12
T42<edp_17> Hi guys. I am getting "Unable to find package: patterns-sailfish-device-configuration-$DEVICE" error when running the mic. Patterns are migrated to meta packages and I do have zypper and busybox-static in patterns-sailfish-device-configuration-$
T42<edp_17> When I built configs, only one pattern .rpm is generated in droid-local-repo. What else should I check?10:52
T42<edp_17> I only have 'patterns-sailfish-device-configuration-common*.rpm' but 'patterns-sailfish-device-adaptation-$DEVICE*.rpm' and 'patterns-sailfish-device-configuration-$DEVICE*.rpm' are missing from local repo.10:54
T42<Tirthankar> How port sailfish os In Redmi Note 9 pro ?10:59
T42<elros34> @edp_17 did you run helper script or did you migrate manually? If you are missing then maybe there is something wrong with script10:59
T42<edp_17> @elros34 : I ran the helper script after when I updated the hybris/droid-configs/droid-configs-device11:01
T42<elros34> so do you have these inc lines?11:04
T42<elros34> include*11:04
T42<edp_17> @elros34 : Nope. Those two lines were missing in that .spec file. Once I added, both missing .rpm packages generated.11:04
T42<edp_17> Thanks for the help!11:05
T42<elros34> will be useful for others to figure out why script fail11:05
T42<edp_17> When I ran the script I got the message 'Already migrated'. I think few months ago I started to build 4.0 for this device but then I stopped. I first ran the migration script at that time and might be there was a bug that is already fixed since.11:10
T42<edp_17> Another question. What does 'patterns-sailfish-rnd' do in patterns-sailfish-device-configuration-$
T42<elros34> check yourself, zypper download it and then rpm -qp --requires path/to/patterns-sailfish-rnd*rpm11:12
T42<edp_17> How I meant was, I found this in my treltexx pattern but wasn't in the i9100 😊 and I am not sure whether it should be there or not.11:14
T42<edp_17> I'll do what you advised.11:14
T42<edp_17> I see. So this is required for connma-tools, gbd, mce-tools and for others.11:16
T42<edp_17> Oh, another question. 😊 In rpm/dhd/helpers/ I spotted that I do have 'CPPFLAGS+= -I../include -std=gnu99 -std=gnu99 -std=gnu99' in there instead of 'CPPFLAGS+= -I../include' but I don't know how did it go into it. I kept trhe longer but am not sure what this is doing.11:22
T42<elros34> yeah it's bug, some script adds -std-gnu99 every time is executed, pleas efix it:)11:25
T42<elros34> it should be added only once obviously11:26
T42<edp_17> I see. Thanks. I already left it there three times. Does it cause a problem?11:27
T42<elros34> AFAIK no11:28
T42<edp_17> Thanks.11:28
T42<edp_17> Hi, it's me again. Can you please advise how to solve this one?
malwhich android base? is there a reason why you build the droid ngfd plugin?13:44
T42<edp_17> mal: cm12.113:44
T42<edp_17> There is no reason, it was in the mw folder, so I thought it was needed.13:45
T42<edp_17> Should I just simply ignore that and do not build?13:45
malthe native version is recommended, it is enabled with
malthe native version is in default repos so no need to build13:47
malif you have new enough dhd submodule it should not be build vibrator packages13:48
T42<edp_17> mal: Thanks. I have that in my .inc, so I am puzzled why this repo was cloned into mw. I'll remove it then.13:48
T42<edp_17> Yep, I have the latest dhd.13:48
T42<edp_17> Thanks for confirming.13:48
T42<edp_17> Okay, so I don't need 'qt5-feedback-haptics-droid-vibrator' either.13:49
T42<edp_17> I just built that. 😊13:50
T42<edp_17> mal: I've got a new error for sensorfw:
T42<edp_17> I am on the latest master.13:52
malyou have the latest droid-hal packages built?13:59
maland installed14:00
malat least the devel package14:00
mal@edp_17 is the build environment new or old?14:00
maljust thinking if there are remnants of old build in sensorfw repo? try "git clean -x -f -d" in sensorfw source folder14:02
T42<edp_17> I updated toolings, targets and all sub-modules including all in hybris/mw.14:02
T42<edp_17> I try this clean up and retry.14:02
T42<elros34> but did you build droid-hal?14:04
T42<edp_17> Yes, that built.14:07
T42<edp_17> Doing that clean helped and sensorfw has built too. Thanks!14:07
malif see any issues like that with other packages use the same fix14:08
T42<edp_17> Thanks, mal, I will do. However, for this device this was the last package. Now I do the mic. 😊14:09
T42<eriki73> Just tried to build droid-hal but it seems to hang...15:13
T42<eriki73> It doesn't seem to use CPU at all...15:14
T42<eriki73> NVM, got it fixed...15:45
mighty17[m] any help here?16:13
malmighty17[m]: I think you should be building the older versions of droidmedia and gst-droid and gmp-droid mentioned in logs earlier16:15
mighty17[m]im on hadk now16:16
T42<eriki73> Now, I am not able to build gst-droid: No provider of 'pkgconfig(droidmedia)' found.16:19
mighty17[m]go to hybris/mw/gst-droid folder and do `git checkout 364c13e3f6b3d99a87b58beb526bd13f377ce6f4`16:21
T42<eriki73> Now it states that pulling updates fails from git... It is I guess logical but I cannot build with that... (re @SailfishFreenodeIRCBridgeBot: <mighty17[m]>go to h...)16:22
mighty17[m]no no16:22
mighty17[m]then run `rpm/dhd/helpers/ -b hybris/mw/gst-droid`16:23
T42<eriki73> I was just following the hadk...16:23
mighty17[m]yeah im on the same step as you :)16:24
T42<eriki73> And now I get an ld error...16:24
T42<eriki73> And now I get a ld error... (edited)16:25
T42<elros34> if you will follow only hadk then your will not even be able to boot your device:) There is also  and
mighty17[m]@elros34 moved to 4.1 and that seems to have fixed all build issues16:29
malmighty17[m]: which version of droidmedia did you build?16:29
mighty17[m]i hope it boots on device tho*16:30
mighty17[m]mal: acc to git log its on 9450a66a133ffa4df4af5f1d2af5b09ff794606d16:30
mighty17[m]changed the gst-droid and gmp-droid to the one recommened in logs16:31
T42<eriki73> I still seem to get a ld error...16:35
T42<elros34> ld error doesn't tell much .... but probably some leftovers, got to directory which contains sources and run git clean -xdf16:40
T42<eriki73> ld: undefined reference to `dlclose'16:42
T42<eriki73> @elros34 , cleaning with git did not help16:42
T42<elros34> in what context do you get that error? always provide full logs16:43
T42<elros34> how did you change revison?16:44
T42<eriki73> Did change with git checkout16:45
T42<elros34> I guess you meant git checkout <some revison>, that is not enough. You need to checkout to master now and then add --recurse-submodules16:46
T42<elros34> Did you downgrade also droidmedia first?16:47
T42<eriki73> Oops forgot, where is it located?16:49
T42<eriki73> it was not in mw...16:49
T42<elros34> grep for it in link I provided, it has location16:51
mighty17[m]@elros34 is it fine to flash a diff android base (ie with some new configs) with sfos (which doesnt have those configs?)16:55
malif you get those dlclose errors etc you probably have too new droidmedia16:56
T42<eriki73> where is gmo-droid then? That I could not find in the link...17:26
T42<eriki73> where is gmp-droid then? That I could not find in the link... (edited)17:26
T42<elros34> mighty17[m] I guess depends on what do you mean by some configs17:26
T42<elros34> @eriki73 it will be cloned in mw/  by build_packages.sh17:27
mighty17[m]some configs means CONFIG_NETFILTER_etc17:28
T42<elros34> how kernel config is related to different android base, sorry I do not get fully understand what you want to achieve but hey try17:29
T42<elros34> @eriki73 btw you can also skip building it and comment it out from patterns, there is really no need to care about hw acceleration in browser before you got gui17:30
mighty17[m]what i mean is my android base is also built by me and has some more commits in the kernel than that of sailfishos, either i can risk and try it with that or get the commits in sfos build (which i dont want to as they are wip)17:31
mighty17[m]but nvm imma try it17:33
T42<eriki73> —gg refuses to run after I have checked out a commit...17:35
T42<elros34> hard to tell without details but without offline argument for script your sources will be updated to latest17:46
T42<eriki73> Ok, building with offline argument now...17:47
T42<eriki73> Hmm. why can't I execute logcat?18:48
T42<b100dian> droid-hal-init has crashed. Try executing logcat as soon as possible18:52
T42<eriki73> It seems it fails immediately on boot, @b100dian18:57
T42<eriki73> Also, it fails beacause: can't open '/usr/bin/droid/': No such file or directory19:01
malthat is not an error, that file is optional19:01
T42<eriki73> Then it is the NOTCONFIGURED exitcode of tha main command...19:04
maldo you have system and vendor partitions mounted correctly?19:06
T42<eriki73> Where are they mounted?19:07
T42<eriki73> Seems that they aren't mounted at all...19:10
malare you sure did fixup-mountpoints correctly? other option is that fstab was not copied to out/ during hybris-hal build19:14
T42<eriki73> should the fstab be directly in out19:17
malno, somewhere under it19:24
malsomething like ut/target/product/$DEVICE/root/19:25
malcould be also somewhere else19:25
T42<eriki73> There is fstab.hardware19:29
T42<eriki73> and that is everything...19:30
T42<eriki73> Even the entries there are not mounted...19:55
T42<eriki73> I guess it did not create mount units at all...20:05
malcan you show the fstab file and also the entries you added to fixup-mountpoint20:07
malthat seems strange, in fixup out have a/b style partitions but fstab doesn't20:12
T42<eriki73> My device definitely has a/b20:13
malhow do you see those on device?20:14
malwell I probably would try defining for example "a" slot ones with the names you see in fstab so the replacing script works20:20
T42<eriki73> What parts of the build I need to rerun after that?20:25
malI think make hybris-hal and the repackage droid-hal, those should be enough20:26
malthe latter can be done using "rpm/dhd/helpers/ -d", if course after first doing make hybris-hal in HABUILD_SDK20:27
T42<eriki73> And after that? rebuild the image?20:31
T42<eriki73> Any tips for easier flashing under twrp... The zip fails...20:35
T42<eriki73> Last time I unbzipped and extracted the tar manully...20:36
malI think some other people had some hints how to handle that issue20:38
T42<eriki73> Now everything is mounted except vendor...20:49
T42<adampigg> @eriki73 for that issue, i hand-balled all the kickstart scripts to pack/unpack as a .tar.gz ... was a bit of a pain, but should all be in the volla repo20:49
mal@eriki73 you seem to be missing /vendor from fstab, add it there manually and rebuild20:53
T42<eriki73> Yep, just doing that20:53
malsome devices are missing it, most new devices actually20:53
T42<eriki73> Do I need to repackage droid-hal?20:55
T42<adampigg> yes20:56
T42<eriki73> I think I am starting to understand how does the build system work...20:57
T42<elros34> if you are going to make new image for every single change that will be pain. Create vendor.mount on device and enable it via systemctl to speed up  your work or copy droid-hal rpm to device and install20:59
malyeah, rebuilding image is not critical thing to do, copying rpms is easier, just don't make the mistake of editing too much on device and forgetting to add the changed to your repos21:01
T42<eriki73> Now, I got everything mounted... droid-hal-init still fails21:20
malhow does it fail now?21:21
T42<eriki73> First timeout then NOTCONFIGURED....21:22
malshow whole output of "journalctl -b --no-pager"21:23
T42<eriki73> Looks like it does not begin on system boot?21:34
malthat seems to be missing the early messages from the log21:37
malreboot the device and try to get the log soon after booting21:38
T42<eriki73> SELINUX is on... Maybe it should be off?21:41
malwhich android base are you using?21:43
T42<eriki73> Android Pie (re @SailfishFreenodeIRCBridgeBot: <mal>which android b...)21:43
malwhich one was pie again? 9?21:43
T42<eriki73> Yeah...21:43
T42<eriki73> hybris-16.021:44
malhow did you disable selinux?21:44
T42<eriki73> I guess I didn't (re @SailfishFreenodeIRCBridgeBot: <mal>how did you dis...)21:45
malyou should have CONFIG_SECURITY_SELINUX=y and CONFIG_SECURITY_SELINUX_BOOTPARAM=y in kernel defconfig and then either CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 in defconfig or selinux=0 in kernel commandline21:46
malalso CONFIG_AUDIT=y should be there, you can disable audit from kernel commandline using audit=021:47
malhmm, so it times out for some reason21:55
malI don't see any errors from droid-hal-init21:55
malmaybe try increasing TimeoutSec= in /usr/lib/systemd/system/droid-hal-init.service21:56
malof course this is just a temporary hack until we figure out why it fails21:56
malother way to debug is to mask droid-hal-init service and start it manually after boot, and then use /usr/libexec/droid-hybris/system/bin/logcat to check the android side logs right after starting droid-hal-init21:57
T42<eriki73> It is now 45...21:58
T42<eriki73> logcat read failure21:59
malanything new in journal?22:01
malis droid-hal-init still running when you tried logcat?22:01
piggzmal: how does qt plugin evdevtablet differ to evdevtouch22:04
T42<eriki73> There was stiil selinux related stuff.. So, I edied defconfig and now I get a bootloop...22:06
T42<amyosx> erik, is there anything linux you dont do?22:08
T42<eriki73> Use KDE Plasma? (re @amyosx: erik, is there anyth...)22:09
T42<amyosx> lmao22:09
T42<eriki73> Well, I am a long time GNOME user...22:09
T42<amyosx> i de hop22:09
T42<eriki73> Why does it bootloop?22:12
T42<elros34> don't you use some halium or ubuntu kernel? I see apparmor in your log22:22
T42<eriki73> It is a mixture between halium and los kernel...22:25
T42<eriki73> But I guess a normal los would be better?22:26
T42<eugenio_g7> rinigus: re flatpak on aarch64 - have you tried applying the tls-padding workaround?22:26
T42<elros34> @eriki73  in sfos we keep selinux so probably you have config_default_security!=selinux and maybe other changes22:27
T42<amyosx> @eriki73 what device are you trying to port?22:30
T42<eriki73> sargo22:30
T42<amyosx> ooh nice22:30
T42<eriki73> Well, the Halium kernel with sfos initrd boots but the kernel I am trying to build with sfos build system doesn't ...22:37
T42<amyosx> oof22:41
T42<eriki73> And that is with almost the same sources...22:41
malyou are sure it uses same defconfig?22:43
T42<eriki73> That is the change... I did make sure it passes the hybris tests (errors only)22:43
malcan you show your defconfig22:44
T42<eriki73> And I disable apparmor now...22:44
T42<eriki73> Just a sec ..22:44
T42<eriki73> And I disabled apparmor now... (edited)22:48
T42<elros34> CONFIG_SECURITY_SELINUX_DISABLE=y is wrong and obviously Config_Audit=n also which is selinux dependency22:48
T42<elros34> fw_loader also, you seems to not read notes you got22:50

Generated by 2.17.1 by Marius Gedminas - find it at!