Sunday, 2026-05-31

Mister_Magisterit might not be merged but i hope talks start00:00
Mister_Magisteri'm very proud of myself for implementing those gestures :300:00
Mister_Magisterokay now for a tricky question, how do i make it so that sensorfw from my vendor is pulled instead of jolla's00:09
Mister_Magisterig all I can do is to stay version in front of it i guess00:09
nightishamanokay, strace has executed00:15
nightishamanlets look at it00:15
nightishamanmal: it mounts twice, first it mounts /linkerconfig to a tmpfs, then it mounts /linkerconfig/default to /linkerconfig00:18
nightishamanaccording to the strace00:18
Mister_Magistermal: do you mind explaining to me, why sensorfw package, which is version 0.14.4, in jolla repos is 0.15.0-1.14.1.jolla? Where the hell did 0.15.0 come from?00:18
Mister_Magisterit'sa freaking tag00:19
Mister_Magistertag not matching a version should be criminal offence00:20
Mister_Magisterpushed my tag 1.0 so that it's always above jolla's no matter what00:22
malMister_Magister: someone forgot to update the version00:31
Mister_Magister:)00:31
Mister_Magisterlemme make a PR i'm sure it will be merged in timely fasion :D00:32
nightishamanbuiltins.cpp:122700:32
malbut if you build that on obs it should be using the tag+something00:32
malMister_Magister: PR for what?00:32
Mister_Magisterfor version bump :D00:32
malnah00:32
Mister_Magisteryeah i realised that it was tag causing it, hence i tagged my stuff 1.0 so that it's picked over jolla's00:32
Mister_Magistermal: …that was a joke, with the version bump00:33
malMister_Magister: so you have only built it locally? obs should be using tag not spec version00:33
Mister_Magistermal: yes it is using tag00:33
Mister_MagisterI just didn't know that 0.15.0 is using tag, now that I've realised it, i've tagged my changes with 1.0 so that my packages will be picked over packages from jolla repo00:34
malbut even without custom tag it would be newer than official version afaik00:34
Mister_Magisterno without tag it would be 0.14.400:34
Mister_Magisterand jolla is using tag 0.15.000:34
malare you sure?00:34
malon obs that is00:34
Mister_Magisteryes thats why i had this issue00:34
Mister_Magisterwithout tag, the version in .spec is 0.14.4 and that's what OBS will use00:35
nightishamanmal: i found it00:35
Mister_Magisteryou have to use tag 0.15.0 for obs to set version to 0.15.000:35
malobs should be taking tag always00:35
Mister_Magistermal: yes, unless you don't give it a tag00:35
nightishamaninit.rc calls enter_default_ns on line 748, which mounts /linkerconfig/default on /linkerconfig00:35
Mister_Magisterif you pull from master, HEAD it won't use tag00:35
Mister_Magisterit will use .spec version00:36
Mister_Magisterbecause there's no tag provided00:36
malMister_Magister: why would you have a fork of sensorfw without all the tags?00:36
malthat makes no sense at all00:36
Mister_Magistermal: you're missing the point00:36
Mister_Magisterit doesn't matter what the fork has00:36
malyou are missing the point00:36
Mister_Magisterif in tar_git, you supply branch master, and revision HEAD, it will NOT magically change the version to latest tag00:37
Mister_Magisteryou have to specify tag in revision for it to change version to the tag version00:37
malobs does all kinds of magic00:37
Mister_Magisteri'm telling you how it works00:37
Mister_Magisterbecause i just had this issue00:37
maland when you did the test you had all of the tags in the fork?00:37
Mister_Magisterokay the fork has no tags, i guess it's github's default behaviour00:38
malforks always have the tags from when you forked it00:38
Mister_Magisternope00:38
Mister_Magisteryou want me to prove it?00:39
Mister_Magisterit could be because of the "Copy the master branch only" that's selected by default00:39
Mister_Magisterhttps://github.com/Michal-Szczepaniak/sensorfw fresh fork, do you see tags00:40
malwtf, github broke it then recently00:40
Mister_Magisterglad we're on the same page00:40
Mister_Magisteralso yes you're right obs will pull latest tag00:40
Mister_MagisterI was wrong00:41
nightishamanmal: So, I figured out why strace shows a two mounts on linkerconfig. The function MountExtraFilesystems mounts linkerconfig as tmpfs again, then later enter_default_ns mounts /linkerconfig/default as /linkerconfig00:41
Mister_Magistermal: also yes, i was correct, it's the default option "Copy the master branch only" that removes tags00:42
Mister_Magisteryou have to do full fork for tags00:42
nightishamanMister_Magister: thats why i only do full forks00:42
malMister_Magister: so stupid to not have tags of master branch in there, that makes no sense00:42
Mister_Magisterwell that's microsoft for you00:42
Mister_Magisterthey haven't made single reasonable decision in years now00:43
malMister_Magister: why wouldn't you trust me earlier when I said how obs works, I have used it so much that I know what it does and doesn't do00:43
Mister_Magisteryeah you're right, my bad00:43
Mister_Magistersorry00:43
malnightishaman: is MountExtraFilesystems always run?00:45
nightishamanmal: yes00:46
malnightishaman: so which call breaks it?00:47
nightishamanthe builtin enter_default_ns00:47
nightishamanit gets called on post-fs-data by init.rc and causes /linkerconfig/default to be mounted on top of /linkerconfig00:47
malso the linkerconfig/default is not ok?00:47
nightishamanyeah00:47
nightishamanbut we might want to disable MountExtraFilesystems too because mounting twice is redundant00:48
nightishamanI can make a patch ready and start a PR00:48
maljust wondering why my a16 device doesn't have that issue00:49
nightishamanNo idea, but the source code confirms it00:49
T42<b100dian> mal: is pulseaudio at 17.0 in latest ?00:51
T42<b100dian> (sorry I don't know who else to ping)00:51
mal@b100dian pa 17 is in sfos 5.1, not in 5.000:52
malon obs latest is still 5.000:53
T42<b100dian> that answers my question. So I need sailfishos:5.1 on devel00:53
malnightishaman: on my device if I unmount /linkerconfig then /linkerconfig/default has ok content00:54
nightishamanmal: How can I test that on mine?00:55
malI just did umount /linkerconfig and then checked what is under /linkerconfig00:55
Mister_Magistermal: sensorfwd has -c=/etc/sensorfw/primaryuse.conf does that mean i have to override the primaryuse.conf in sparse? it won't load other configs?00:56
nightishamanok im gonna check by unmasking droid-hal-init and expand my test script00:56
malnightishaman: what happens if you just comment out that enter_default_mount_ns from /usr/libexec/droid-hybris/system/etc/init/hw/init.rc00:57
nightishamanif i do umount then i have ok content in /linkerconfig00:58
nightishamanbut not in /linkerconfig/default00:58
nightishamandoes your device somehow copy stuff to /linkerconfig/default?00:58
malmaybe you have multiple mount layers, umount second time00:59
malbut maybe test that commenting first in init.rc to see what happens01:00
malMister_Magister: droid-hal-configs submodule has the default primaryuse.conf, you can override in device config sparse01:02
Mister_Magisterwell that wasn't my question but that's what I did01:02
nightishamancommenting out enter_default_mount_ns causes it to keep the ld.config.txt01:02
Mister_Magisteri was just asking if it can load other configs in that directory so that I don't have to override it01:03
malnightishaman: are android side processes starting better now?01:03
Mister_Magisterwho the heck is hogging all the resources with wordle app xdd01:03
nightishamanmal: still having this: 05-31 01:05:17.547  6042  6042 F linker  : CANNOT LINK EXECUTABLE "/system/bin/odsign": library "libstatspull.so" not found: needed by main executable01:05
nightishamanand this: droid-hal-init: Control message: Could not find 'aidl/android.frameworks.stats.IStats/default' for ctl.interface_start from pid: 2504 (/system/bin/servicemanager)01:05
nightishamanlibstatspull.so is only found in an apex01:07
malthose don't seem very critical processes01:08
malprobably01:08
nightishamanmal: well according to google they are important for ART01:10
malMister_Magister: there is a very odd design in sensorfw https://github.com/sailfishos/sensorfw/blob/b62d0e591d736c904128fcfc8476f22cfdbe53b9/core/config.cpp#L6301:10
malnightishaman: so not for sfos01:10
nightishamaninit.rc waits for it tho01:10
malhmm where?01:11
nightishamanline 110901:11
malprobably different lines in my file01:12
nightishamanthen do grep -rn "odsign"01:12
malcomment it out also01:14
malI assume you mean wait_for_prop odsign.key.done 101:15
nightishamanyes01:15
nightishamanand odsign.verification.done in zygote start01:15
malnightishaman: no01:15
nightishamanwhat01:15
malzygote is not started in sfos01:15
nightishamanwell i commented it out anyway for testing01:16
malI meant the other thing01:16
nightishamanyeah i commented out start odsign and odsign.key.done01:16
malin "on post-fs-data"01:16
nightishamanbut if on zygote-start is never run then statsd wont be run and it will keep filling my log with IStats not found01:17
Mister_Magistermal: I seem to be running into race condition where the gesture sensors are not yet available when lipstick starts… do you have better idea than StartPre: sleep 100000000000001:18
malnightishaman: unless something is wrong zygote should not be starting01:18
Mister_MagisterI… could loop the app and wait check if plugin is available every second01:18
malhow are the sensors not available?01:19
nightishamanmal: How do I stop these from getting spammed every second then? droid-hal-init: Control message: Could not find 'aidl/android.frameworks.stats.IStats/default' for ctl.interface_start from pid: 2504 (/system/bin/servicemanager)01:19
nightishamansince statsd seems to be started in on zygote-start01:19
Mister_Magisterthey just aren't sensorfwd says HYBRIS CTL invalid sensor type: 6554001:19
maldo you see anything about zygote in logs then?01:19
Mister_Magisterand even if i restart my daemon sensorfwd won't give it the sensor anymore01:20
Mister_Magisterbut if i restart sensorfwd it should work fine01:20
malso sensorfw is started too early01:20
Mister_Magisteri would think so yes01:20
Mister_Magisteri wonder if there's something i can condition it on instead of just adding random delay01:21
malmaybe some android service activates those?01:22
T42<b100dian> Doesn't work (re @b100dian: that answers my ques...)01:25
T42<b100dian> Anyone built 5.1 on obs / devel01:26
malwhich device?01:26
T42<b100dian> https://build.sailfishos.org/project/show/nemo:devel:hw:xiaomi:tucana01:26
T42<b100dian> But if I had an example of another device on 5.1 with devel I would probably figure it out01:27
malhow about now01:27
T42<b100dian> hmm :) what did you change mal? Teach the man to fish01:28
malthe order of repos is important in meta01:28
malhttps://build.sailfishos.org/project/meta/nemo:devel:hw:xiaomi:tucana01:28
T42<b100dian> oh, didn't expect that01:29
T42<b100dian> thanks!01:29
malthe nemo:devel:hw:common is still 5.0 so you had it at the bottom which meant it was used for base stuff01:29
malwhich of course is not ok01:30
nightishamanmal: https://pastebin.com/6n2s790f new stuff crashing01:30
malusb service is useless01:30
malcan be disabled01:31
malexample of a service being disabled https://github.com/mlehtima/droid-config-fp4/blob/master/sparse/usr/libexec/droid-hybris/system/etc/init/disabled_services_device.rc01:32
malyou have to check the .rc files for the service name etc to use01:32
nightishamanyeah but the others are part of the camera01:33
nightishamanall the so files they search are in apexes01:33
malbut now linkerconfig should be ok?01:34
malso why are those still failing01:34
nightishamanwell linkerconfig doesnt have those pathes in it01:34
malunless there is something wrong in linkerconfig still01:35
malhow different is the linkerconfig if you create it using the linkerconfig in /apex, I remember there might be one there?01:36
malMister_Magister: that sensorfw PR is a bit of a mess, why 7 commits?01:37
Mister_Magisterwhy not? i made commits as I went01:37
Mister_Magisteryou can always squash it01:37
mal3 commits with same commit message?01:37
Mister_MagisterI'm lazy xd01:38
malsome are removing things you added in another commit, that's not ok01:38
Mister_Magisteryou can always squash it xd but if it is a problem i'll squash it myself01:39
nightishamanmal: when i run linkerconfig right now after starting droid-hal-init, it gives a more expanded linkerconfig which also include libstatspull.so01:39
nightishamanhowever the camera hal is still not included in that linkerconfig01:40
Mister_Magisterhere you go, squashed01:40
nightishamanusing the one in /apex/com.android.runtime makes no difference01:40
malok, something odd still with that01:40
T42<b100dian> (yee I have sound back on jb2q)01:40
Mister_MagisterI've added delay 100 to sensorfw start xd that just made it not start, but 10s was not enough :/01:44
Mister_Magisterokay delay of 20s did the trick01:49
nightishamanmal: as far as i understand, apexd should call android init to tell it to add the apexes to linkerconfig, but for some reason thats not happening01:51
nightishamanhttps://pastebin.com/28eP5Fhd01:51
Mister_Magistermal: I grepped for chopchop and camera gesture and both are only found in /vendor/firmware_mnt/image/adsp.b15 but no clue which service would provide that01:52
nightishamanmal: I'm beginning to think there must be something that executes linkerconfig in /linkerconfig/default that doesnt happen on my device and thats why its ok on urs01:56
malnightishaman: might be, need to check how my device works01:58
nightishamanmal: Found it, perform_apex_config is run again in on post-fs-data02:09
Mister_Magistermal: so I added bash script that does ps aux | grep sensor > /home/sensors to list all android sensor services, and ran it as ExecStartPre of sensorfwd and you wouldn't imagine but none of android sensor services are running02:11
malMister_Magister: not suprising since sensorfw is supposed to wait for the services to appear in the main process02:12
Mister_Magisterthen if it waits for them, why does it still lack my gestures?02:12
nightishamanmal: I have no idea what happened, but for some reason, the ld config is now filled properly02:14
nightishamanim gonna go into recovery and check out what i changed using diff02:14
nightishamanmal: Can you check on your device whether the message with Generated linkerconfig to /linkerconfig shows up twice?02:21
nightishamanit did work now because i moved my script to the second execution of perform_apex_config and my script wrote the proper ld.config.txt02:29
nightishamanthe question is now, why does the second invocation fail02:30
Mister_Magistermal: I've tried to make sesnorfw wait for all the running executables with sensor in the name and no dice02:34
Mister_Magisteralso why in the world are you not asleep yet02:35
nightishamanmy guess is that the switch from bootstrap to default namespace doesnt work for some reason02:44
Mister_Magisteri guess sleep 20 is the answer02:45
T42<the_hiktor> @elros34 i enabled selinux 🙂04:21
T42<the_hiktor> journal droid-hal-init  and some more are dead04:23
T42<the_hiktor> https://paste.opensuse.org/pastes/bd9b3053667a04:41
T42<the_hiktor> dmesg04:41
T42<the_hiktor> selinux status in case you interested https://paste.opensuse.org/pastes/7768b34eff1404:43
T42<elros34> so selinux ok, what would happen (sestatus -v) if you add  handle-unknown=allow to /etc/selinux/semanage.conf and run semodule -B according to07:53
T42<elros34> https://documentation.sas.com/doc/en/dplyboss0phy0lax/10.1/n1uksz2v8f2jktn1cd40pkh5cyxn.htm07:53
T42<edp_17> @Mister_Magister, Hi. here is the output from console when I ran that sensorfw command: https://paste.ubuntu.com/p/nNxb7hcBJj/09:39
Mister_Magister@edp_17 you have same gestures with same IDs so if you want you can use my software to enable them!09:42
Mister_Magisteras expected though :P09:42
Mister_Magisteryou just need to build sensorfw on my fork like here https://build.sailfishos.org/package/show/nemo:testing:hw:motorola:miami/sensorfw-qt5 https://build.sailfishos.org/package/show/nemo:testing:hw:motorola:victara/sensorfw-qt5-hybris and you also need the daemon/settings page to talk to sensorfw and here it is https://build.sailfishos.org/package/show/nemo:testing:hw:motorola:victara/motorola-gestures09:43
Mister_Magisterand you'll have chop chop, camera gesture, and lift to view09:43
Mister_MagisterI'm quite confident it will work on all motorolas since 2014 xd09:44
T42<edp_17> What is chop chop and camera gesture?09:45
Mister_Magister@edp_17 you surely used motorola on stock before…?09:45
Mister_Magisterhttps://www.youtube.com/watch?v=ucQBVQoKltQ09:46
Mister_Magisterthose are like the special something motorola has been known for since forever xd09:47
Mister_Magisterwhich is why it works on all motorolas, because they've been porting same code over and over since 2014 xd09:47
T42<edp_17> No, I never used any of these. I barely used Android on it as I started porting SOFS immediately when I received it.09:48
Mister_Magisterno i get the sentiment :D09:48
Mister_Magisternow you know :D09:48
T42<edp_17> Yeah, thanks :D09:48
Mister_MagisterI do the same i just used stock in past09:48
Mister_Magisterandroid dev told me those are exposed as sensors and after making it work on edge 30 neo apparently it also worked on my 2014 x2 so if both edges of the spectrum are working, everything in between should too09:49
T42<edp_17> So, will both of these gestures be available on SFOS with your custom sensorfw build?09:49
Mister_Magisteryeap09:49
Mister_Magister+ lift to view09:49
Mister_Magisterit's sensorfw + my daemon cause nothing will read those except my daemon09:50
T42<edp_17> I'll try to remember to buld it when I start building 5.1. Then, I'll test and report.09:50
Mister_Magisteryessir09:51
T42<edp_17> I've added a note to my instructions about it, so I won't forget. :) However, I don't know when I will build 5.1 for my devices. So, it will take some time.09:53
Mister_Magisternow I just have to figure out how to make sensorfw wait for those gesture sensors :/10:54
Mister_Magistermal: Turns out you don't have to override primaryuse at all, it loads primaryuse.conf and also sensord.conf.d11:18
Mister_Magisteroh @edp_17 that reminds me you need to add 3 lines to sensord config, i'll give you sample in a second11:18
Mister_Magisterhttps://github.com/VerdandiTeam/droid-config-miami/tree/master/sparse/etc/sensorfw/sensord.conf.d here you go11:19
Mister_Magisternow i need to figure out how to make sensorfwd wait for my sensors11:21
Mister_MagisterOh?! apparently it's using aidl not hidl (probably because it needs the separate branch)11:29
Mister_MagisterI wonder if it would be possible to reload list of available sensors during plugin availability check11:39
Mister_Magisterhmm getSensorList is protected11:47
mal@the_hiktor are you really sure the selinux configs in /etc are correct?12:06
T42<the_hiktor> @elros ok so what this do exactly that thing you sent i tried it but i dont get it what it does it just made my device irresponsive i cant input anything after connecting in telnet in fact the whole terminal freezes12:35
T42<the_hiktor> mal : never been unsure like that in my whole life 🥲12:36
T42<the_hiktor> you can look at them yourself https://github.com/GloboPatro/droid-config-surya12:38
Mister_Magistermal: would you be willing to accept this PR https://github.com/VerdandiTeam/sensorfw/commit/e1d584ed94ac231bcc66339c53b4fd3f4b44c4a812:42
Mister_Magisterit re-fetches sensors list whenever sensor is requested and completely solves my issue12:43
Mister_Magistertho i guess in its current state it leaks a bit of memory xd12:43
mal@the_hiktor which android base?12:50
T42<elros34> @the_hiktor shame so it's not tha easy. It was supposed to change that `deny_unknown` status but I am not sure this is the root of issue12:51
malMister_Magister: well first of all that causes terrible memory leak12:52
Mister_Magister:)))))12:52
Mister_Magisternot that terrible xd12:52
Mister_Magisterbut i did mention it12:52
malhttps://github.com/VerdandiTeam/sensorfw/blob/master/core/hybrisadaptor.cpp#L74412:52
Mister_Magisteryes i mentioned it already :)12:53
maland probably more in strings12:53
Mister_Magister[14:43] <Mister_Magister> tho i guess in its current state it leaks a bit of memory xd12:53
Mister_MagisterI'm asking more about the concept12:53
malneed to think a bit12:54
Mister_Magisteroki doki meanwhile i'll yeet the leak12:54
T42<the_hiktor> mal: 1112:54
T42<the_hiktor> @elros34 so my whole problem is because of selinux ?12:55
Mister_Magistermal: poof, no more leak https://github.com/VerdandiTeam/sensorfw/commit/759d962490079849eedcf4d041e3762fed87501912:56
Mister_Magistercopied it from destructor12:56
mal@the_hiktor you are missing "%define android_version_major 11" from droid-config spec file at least12:56
T42<elros34> @the_hiktor depends on what do you mean by 'whole'. Clearly selinux breaks journal12:56
malbut that missing thing from spec shouldn't affect selinux12:56
Mister_Magisterthough this initManager is sus12:57
T42<the_hiktor> mal : i didnt update the repo you can see last edit was last month😅12:57
T42<the_hiktor> but im aware o that12:57
T42<the_hiktor> of12:57
malok12:57
T42<elros34> please update then. It's 1 minute job. There is no point to waste time on fixed issues12:58
T42<the_hiktor> ik im lazy af 😭12:58
malwhich kernel version does the device use?13:02
T42<the_hiktor> 4.1413:02
T42<the_hiktor> @elros34 ok  done13:09
T42<the_hiktor> any ideas why this happening on what can i do13:10
T42<the_hiktor> or13:10
T42<elros34> maybe mal will know. Are your kernel sources up-to-date too13:11
mal@the_hiktor the semanage.conf change didn't help?13:11
T42<the_hiktor> @elros34 yeah i took latest abandoned sources 😂13:12
T42<the_hiktor> cuz this device is on another level rn13:12
T42<the_hiktor> it has got los 2313:12
T42<elros34> but github repo is with all your changes right?13:12
malwait, CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0 in defconfig?13:14
malis that really still there?13:14
T42<the_hiktor> you look in my repo ?13:14
malyes13:14
T42<the_hiktor> i didnt upload shit reltaed to kernel yet13:14
T42<the_hiktor> ok ok  yell at me people13:15
malhttps://github.com/GloboPatro/android_kernel_xiaomi_surya/blob/hybris-18.1/arch/arm64/configs/surya_defconfig#L77513:15
T42<the_hiktor> i didn't push anything related to the kernel on my repo yet13:16
T42<the_hiktor> wait ill show you me defconfig13:16
T42<the_hiktor> https://paste.opensuse.org/pastes/6fbcaf462f0c13:20
T42<the_hiktor> its messy in there but everything i edited is in bottom iirc13:21
malstill the question, did /etc/selinux/semanage.conf handle-unknown=allow change anything?13:22
T42<the_hiktor> oh i forgot about this msg13:23
T42<the_hiktor> wait lemme try13:23
malcan you show you kernel commandline?13:25
T42<the_hiktor> about the semanage.conf no it didnt do anything13:27
T42<the_hiktor> kernel  commandline like you wanna see  boardconfig.mk ??13:28
malpreferrably from device to show all of it13:29
T42<the_hiktor> is it ok from recovery ?13:35
malmaybe13:35
T42<the_hiktor> and to be sure is it in /proc/cmdline ?13:36
malyes13:36
malalthough it depends if the recovery and boot image can different values embedded in them13:36
T42<the_hiktor> ok ill send it from recovery then ill try to undo what i did in semanage.conf to get it via telnet13:37
T42<the_hiktor> https://paste.opensuse.org/pastes/44963b9f3c1013:38
T42<the_hiktor> https://paste.opensuse.org/pastes/8f82be60fe3713:49
maljust mentioing that sestatus -v looks the same on my working device13:49
T42<the_hiktor> i kept handle-unknown=allow in semanage.conf13:50
malis that second one from where?13:50
T42<the_hiktor> from device via telnet13:51
malcould you try adding androidboot.selinux=permissive to kernel commandline via boardconfig13:51
T42<the_hiktor> device was changing mac addres whenever i try to connect to it13:51
T42<the_hiktor> but nvm13:51
T42<the_hiktor> ok wait13:51
T42<elros34> maybe remove audit=0 for now13:52
malaudio=0 is something we usually want, to prevent huge amounts of log spam13:52
T42<the_hiktor> i remember selinux was permissive13:52
malthe cmdline you showed didn't have that13:53
malanyway worth a try13:53
T42<the_hiktor> sestatus shows that 🫤13:54
malhmm13:55
T42<securebootoff> rinigus: why do the nagara build instructions mention uploading to obs? no way to do a local build? thinking of doing bringup for asahi platform but this stuff annoys me :(15:07
rinigus@securebootoff: I am sure you can do local build. I find OBS is just faster and easier to do. ... and in the end you would want to move to OBS anyway. so, I try to get OBS working as soon as I can to avoid all this local builds15:09
T42<securebootoff> thanks for answering :) the one thing that aosp does really well is the build system, sailfish always makes my head go numb after a while. ig i have to suffer through it15:10
rinigusare you planning to base it on aosp or los?15:11
T42<securebootoff> sony did not publish aosp for asahi15:11
rinigusI see. good luck! I hope you can reuse much from nagara15:13
T42<securebootoff> thanks a ton :) need sailfish to finish the trinity, already brought up lineage, postmarket on mainline, now only sailfish is left15:13
rinigusgood choice - leaving the best for the last15:15
T42<securebootoff> hehe15:17
T42<elros34> @the_hiktor can you besides previous ideas remove also CONFIG_SECURITY_YAMA you have added and get full dmesg? I wonder whether you could copy that selinux policy from different device but maybe it needs to be with similar kernel15:18
T42<b100dian> mal: I don't suppose the qt5-qpa-hwcomposer 5.6.2.27 works on older devices? (lineage 17.1) https://pastebin.ubuntu.com/p/hgXZjt3pJ9/15:55
mal@b100dian if you have latest libhybris hwc compat module (obviously only for devices which actually need it)16:00
malhwc compat module is built for android 8 and newer16:01
T42<b100dian> I think I have one but definitely does not have that graphicbuffer constructor, that's why I assume its' crashing16:01
T42<b100dian> So, just building hybris-hal then build_helpers.sh -d did not get me in the desired state. It seems that I have a stale libhwc2_compat_layer16:03
mal@b100dian check the libhybris version you have in android side build, verify that submodule was updated also16:04
T42<b100dian> tucana needed not the libui_compat_layer and now I find that it does not compile because there is a layersCount parameter which has gone missing nowadays16:04
T42<b100dian> oh, might be a skipped submodule update? That should be good16:04
mal@b100dian what is that layersCount issue?16:04
malwhich android base?16:05
mallibui_compat_layer is for android 10 and newer16:06
T42<b100dian> Yes, android 10. Sorry for jumping to debugging, the submodule was not updated 🤦16:07
mal@b100dian the usual issue then :)16:08
T42<b100dian> Do I need libui_compat_layer for the qpa change? I didn't before16:08
malcan you explain the issue you have with libui_compat_layer? and no, it has nothing to do with the hwc requirement16:09
T42<b100dian> just noticing in the journal that lipstick look it up16:10
maldon't think about it now, fix hwc compat first16:10
T42<the_hiktor> @elros34 similar kernel like from the same device or same kernel version from another device ?16:11
mal@the_hiktor just to be sure, you copied selinux files from the lineage /vendor or whatever place you had those16:12
mal?16:12
T42<b100dian> mal: worked without issues after submodule update. Also seems to have added smoothness, that qpa 5.6.2.2716:57
mal@b100dian yes, it has some performance improvements which hopefully have some effect17:17
nightishamanmal: Is it possible to specifically only build droid-hal-init. I added some debug prints, that I wanna see17:32
malmake hybris-hal only builds the parts that need changes meaning that have changed17:35
T42<b100dian> @adampigg I don't seem to have that waydroid problem, I just updated an Android 10/Lineage 17.1 device to 5.1 - Does that mean I missed a package?17:36

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!