Sunday, 2026-07-12

*** n2klb_ is now known as n2klb02:04
sharksDang, is it the case that no audio during calls is not a trivial thing? I thought it was a relatively common issue but there doesn't seem to be a relatively common solution?03:54
sharksAlso @mister_magister did you solve the not being able to reject a call issue? I have noticed it is happening to me too04:56
sharksFrom the logs on 2023-04-13 mal, k1gen and edp_17 were all having issues with audio in calls and they suspected because they all used hidl_compat. I am also using hidl-compat. Does anyone know if they ever got to the bottom of this problem? Does fp4 / motog7 / pixel4 still have no audio in calls?07:16
sharksOn 2023-07-25 it was mentioned that you need dummy-af if you have vendor.qti.*.am@ in binder-list, but I have both. Do I need audioflinger or something?07:27
sharks_Do I need the jb2q audio even though I have Android 15?09:53
malno, you don't use jb2q, and you should have dummy-af11:51
T42<Mister_Magister> yes i did solve it (re @SailfishFreenodeIRCBridgeBot: <sharks>Also @mister...)12:45
T42<Mister_Magister> but unless you have motorola with similar vendor it mostlikely won't help you12:46
malsharks: call audio is usually just about getting the hidl_compat module to function properly12:52
rinigusb100dian: I have added https://github.com/sailfishos-sony-nagara/main/blob/main/scripts/create-manifest-snapshot.py15:21
rinigusthat will allow us to keep an eye on our local changes in HADK and LOS repos. bit easier to work with updates15:22
T42<nightishaman> mal: Any guess why my problems from yesterday are still occuring? Do I need to set a version somewhere still?19:06
malwas the target update successful?19:08
maltry what you see with sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -m sdk-install zypper if pulseaudio19:08
T42<nightishaman> https://pastebin.com/PATP0L1719:10
T42<nightishaman> 14.219:10
T42<elros34> did you update also platform sdk? Where do you even have this issue?19:20
malI suspect the target update was only partial19:21
malwhat does this say: sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -m sdk-install zypper in --force pulseaudio19:21
malbut that says it's up to date19:22
malare you really sure you updated the target?19:22
malwhat does this say: sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -m sdk-install ssu re19:22
T42<nightishaman> Device release is currently: 5.0.0.6219:43
malyesterday I said this: I suggest first running "sdk-foreach-su -ly 5.1.0.11" then "sdk-foreach-su -ly zypper ref" and finally "sdk-foreach-su -ly zypper dup"19:44
malyou didn't do that?19:44
maloop19:45
T42<elros34> missing ssu re?19:45
malfirst one was supposed to be "sdk-foreach-su -ly ssu re 5.1.0.11"19:45
malyes19:45
maloops19:45
mal@nightishaman "sdk-foreach-su -ly ssu re 5.1.0.11" then "sdk-foreach-su -ly zypper ref" and finally "sdk-foreach-su -ly zypper dup"19:46
T42<nightishaman> https://pastebin.com/kpnUytTa19:47
T42<nightishaman> nvm19:48
malon the other hand it might be easier to reinstall the target, I remember I had some issues updating targets19:52
malbut try and see if you have too many issues with dependencies19:53
T42<nightishaman> well accidentally pressed ctrl c now im stuck in zypper is cleaning up19:53
T42<nightishaman> how would i reinstall it properly?19:53
malreinstalling would be just to remove the target using sdk-assistant and the installing clean target using the instructions19:54
malyou would only need to reinstall the target, tooling and platform sdk are easier to update19:55
T42<elros34> btw "then" in command might not work20:01
T42<nightishaman> https://pastebin.com/as1EBEMi this happened when installing aarch64 target, do i need to use i486 one?20:05
T42<nightishaman> made a mistake20:07
T42<elros34> update platform sdk first20:08
maland tooling20:14
T42<nightishaman> https://pastebin.com/QhApvagu20:29
T42<nightishaman> platform sdk updated20:29
T42<nightishaman> the rest reinstalled20:29
sharks_Is there any documentation regarding what it entails to get hidl_compat "functioning properly"? AFAIK there's nothing in the logs about how fp4 or motog7 solved it.20:30
mal@nightishaman go to hybris/mw/pulseaudio-moduled-droid and run "git clean -x -f -d"20:31
maland make sure the repo is in correct version, 14.2.10620:31
T42<nightishaman> mal: repo is on branch master20:35
malthat pulseaudio-moduled-droid should be at commit 65edd31f62f22e2eec1f765608ca9c6ae5c4af7b20:36
T42<nightishaman> commit 72273cc48b288847c45e6753998fb42672a3aeb3 (*HEAD* -> *master*, *tag: 14.2.109*, *origin/master*, *origin/HEAD*)20:36
T42<nightishaman> that also okay?20:38
malno20:45
maltoo new20:46
malMister_Magister: what issues did you have with 5.1 on older devices?20:46
Mister_Magisterwifi not working, audio not working20:46
T42<nightishaman> mal: It did work tho with git clean20:47
malMister_Magister: on fp2 wifi works fine, audio seems to have issues20:48
T42<nightishaman> Should I downgrade to tag and redo —mw or continue20:48
Mister_Magistermal: well wifi had some massive issues but it was somewhat related to rfkill so maybe i'll try to enable that20:48
mal@nightishaman run in hybris/mw/pulseaudio-moduled-droid these commands "git clean -x -f -d" and then "git reset --hard 65edd31f62f22e2eec1f765608ca9c6ae5c4af7b" and the build it using "build_packages.sh -b hybris/mw/pulseaudio-moduled-droid"20:49
malMister_Magister: looks like audio issue is some version mismatch in pulseaudio droid module and pulseaudio20:49
malMister_Magister: "module.c: Module "module-droid-card" version (17.0.102) doesn't match the expected version (17.0)"20:50
malchecking what is wrong20:50
Mister_Magisterhmmm okay20:50
malMister_Magister: pulseaudio-modules-droid-jb2q needs to be 14.2.103 to work with pulseaudio 17, testing once it builds on obs20:51
Mister_Magisterokii thakns20:53
malneed to test which wpa versions work on fp220:53
Mister_Magistermal: so i still have device plugged in since that time i tried it20:54
Mister_Magisterit got some dust but i can check stuff if you want me to20:54
Mister_Magisterye so this is in journal https://paste.opensuse.org/pastes/edea78d1f25520:55
Mister_Magisterand i noticed i have CONFIG_RFKILL not set20:56
Mister_Magisterso maybe if i enable config_rfkill it will just work20:56
Mister_Magisterbut the TLS context is also scary20:56
Mister_Magisterif you have any ideas i'm open20:56
malyeah, I have rfkill enabled20:57
malpossible the tls issue is that something broke before it20:57
malMister_Magister: so enable rfkill and test again and if it still fails then we can look again, btw after updating pa droid module audio works20:58
Mister_Magisteroki20:58
Mister_Magistermal: fp2 devel repo?20:58
malMister_Magister: remember to update droid-config submodule to correct version, 41cd1d9dbe6f644c98478705a4d96e9eb3fe0a9020:58
malyes, I tested with fp2 devel20:59
malnoticed some bugs in mer kernel checker, some missing version conditionals20:59
Mister_MagisterI've already updated dcd to 41cd1d9dbe6f644c98478705a4d96e9eb3fe0a90 in the past, man i read your PSA :)21:00
malok21:00
Mister_MagisterI just ctrl+f PSA in telegram channel xd21:00
malI'll probably just push the fix for those directly without PR if the repo allows21:01
T42<b100dian> rinigus: cool, so what is the plan, compare the snapshots?21:05
Mister_MagisterI'm scared of rebuilding hal because i often have undocumented steps and it like never works when i rebuild it 5 years later21:07
Mister_Magisterok last rebuild was only 3 years ago21:07
malI had to find what kernel version I had used, I had the kernel repo in some test branch which wasn't correct21:08
T42<nightishaman> i just got display!!21:08
T42<nightishaman> on setup21:08
malnice21:08
T42<nightishaman> it reboots21:08
malMister_Magister: I have text document for each device with all instructions for those21:09
T42<nightishaman> 5.1.0.11 be hailed21:09
Mister_Magistermal: yeah that'd be smart wouldn't it xd21:09
Mister_Magistermal: "libhybris hwc2 compat module" how do i know if i'm using it and have to rebuild it?21:10
malMister_Magister: and for more recent devices I have made scripts so I can rebuild hybris-hal etc with one command and update obs with anohter21:10
malMister_Magister: hwc compat module is needed for android 8+ https://github.com/mer-hybris/hybris-boot/blob/master/Android.mk#L31921:10
T42<nightishaman> reboot takes long21:11
Mister_Magisterso if i have 8+ android i 100% use it and have to rebuild hal21:11
T42<nightishaman> ok it shutdown instead21:11
malMister_Magister: depends if you plan to update qt5 qpa hwcomposer plugin21:12
Mister_Magisterah21:12
malMister_Magister: note that there are some performance improvements when using hwc2 compat and latest qpa plugin21:12
Mister_Magistermal: hmm mer-kernel-check wants CONFIG_NF_LOG_IPV4 but my kernel doesn't have it21:13
Mister_Magistermal: nice!21:13
malMister_Magister: update to latest mer-kernel-check21:13
Mister_MagisterI have lat… maybe not latest but i cloned it couple days ago21:13
malI just pushed the fix 10 minutes ago :)21:14
Mister_Magister:)21:14
T42<nightishaman> ok now im stuck at "User data could not be encrypted and then it goes black"21:14
malalways nice to push changes directly to master branch :)21:14
T42<nightishaman> mal: git push —force21:15
T42<nightishaman> ur colleagues will love that21:15
malat least it wasn't a force push21:15
Mister_Magistermal: that's how I do it :)21:18
T42<nightishaman> mal: telnet goes away as lipstick starts and encryption wont work so it shuts down21:19
mal@nightishaman did you enable encryption in patterns?21:19
Mister_Magistermal: I just built hybris-boot on android 12.1 and i can't believe how quick that was. hybris-hal rebuild on android 14 takes like 30 minutes21:20
Mister_Magisterit was under 5 minutes21:20
Mister_Magisteri'm astounded21:20
Mister_Magisterwhy can't google just be like google in the past21:20
T42<nightishaman> mal: i did21:20
mal@nightishaman you should not enable encryption unless you know what you are doing (it won't work in regular community style builds)21:20
Mister_Magistermal: mer-kernel-check still fails because I don't have CONFIG_L2TP_IP21:21
T42<nightishaman> ah okay21:21
T42<nightishaman> so i cant save my data?21:21
malso comment the encryption package from patterns and then "build_packages.sh -c" and then build new image21:21
T42<nightishaman> since i cant lock bootloader21:21
malI can instruct how to build different type of image later but let's get more things working first and once most things work reliably then we can look at the image building21:22
T42<b100dian> you can add encryption later, there's community encryption for that. Not sure what you mean by locking bootloader, sailfish apps don't look at that, android does21:23
T42<nightishaman> I wanna make my device proof against thiefs21:23
mal@b100dian I use official encryption package on fairphones21:23
T42<b100dian> I don't think any jolla official device has bootloader relock.21:23
T42<elros34> it doesn't even boot.21:23
T42<b100dian> :)21:24
Mister_Magisteroh apparently I DO have CONFIG_L2TP_IP false alarm21:24
T42<elros34> What is the point of encryption on device which barely works21:24
T42<b100dian> mal: I know but you folks should change the "normal" porting way to instruct everybody to make system images ;)21:24
T42<nightishaman> well, first get sfos working, then encryption, then waydroid21:24
mal@b100dian jolla phone has :)21:24
T42<b100dian> got your priorities alright21:24
T42<b100dian> mal: I have secretly hoped you would say that21:25
T42<nightishaman> i would buy jolla phone if i had money21:25
mal@b100dian well early porting is easier without lvm based image21:26
mal@b100dian I always start official ports with community style builds and once I'm happy to the way those work I change those to lvm based builds and then build on OBS21:27
T42<NotKit> the latter would definitely need custom builds if you have A16 vendor (re @nightishaman: well, first get sfos...)21:27
T42<b100dian> makL I'm almost at my third (was started by rinigus) and still don't get it ;p21:27
mal@b100dian get what?21:28
T42<b100dian> lvm images21:28
T42<b100dian> but dont' worry now, I would only say that this needs more documentation21:28
malmaking lvm based images is rather simple21:28
T42<b100dian> @NotKit what's the latest waydroid base these days?21:28
T42<NotKit> A13 officially, A16 from Waydroid-ATV21:29
malyeah, documentation how to make those lvm based builds is almost non-existent21:29
T42<b100dian> What about 14-15?21:29
T42<b100dian> mal: yup21:29
T42<NotKit> Waydroid-ATV may have them, but why at this point? easier to skip21:29
mala14 based ports need something newer than a13 waydroid21:30
Mister_Magistermal: but that was released wasn't that?21:30
T42<b100dian> @NotKit so just run A16 on A14 ports. Good deal. But that's for one to build themselves, it is not published as images already21:30
malMister_Magister: what was?21:30
Mister_Magisternewer waydroid21:30
Mister_Magisterthat's what i heard21:30
malafaik no images for newer waydroids21:31
malI did full official way for fp4 and fp5, even packaged droid-system (includes the content of /system, /vendor etc)21:32
Mister_MagisterI've rebuilt just hybris-boot, repackaged hal, updated -jb2q, and now i'm gonna build image21:35
maldid you check version of libhybris etc also21:35
T42<nightishaman> the good thing is, the udevd bug is also gone21:35
Mister_Magisterno, there wasn't PSA about that21:35
malMister_Magister: it's not requirement but always good to update21:36
Mister_Magisteri mean i updated versions of other packages last time i was updating to 5.1 if that's what you're asking21:36
malcheck the versions from fp2 devel21:36
malok21:36
malthere hasn't been any new libhybris version recently21:36
mal@nightishaman you mean the slow boot or what?21:40
T42<nightishaman> mal: yes, but now its crashing on boot, nullptr in gpu driver21:41
Mister_Magistergreat jenkins decided to poop the bed21:42
mal@nightishaman at which point of boot?21:44
T42<nightishaman> https://gist.github.com/maltesermailo/78736af93919d57162d218992a5c4d3421:45
T42<nightishaman> mal: 60s after boot, before ui21:45
T42<nightishaman> ui did work before21:45
T42<nightishaman> either there's a bug in the ui but there's definitely a NPR in the driver21:46
malwhich libhybris version did you use?21:52
maldid you have some changes in the earlier image you built?21:52
malI mean something you changed on device?21:53
T42<nightishaman> i did the setup21:53
T42<nightishaman> i pressed okay on eula21:53
T42<nightishaman> and then it rebooted21:54
T42<nightishaman> and then crash21:54
maldo you you master branch libhybris or the pr-testing branch?21:58
malwhich device was that again?21:58
T42<nightishaman> pixel 721:59
malis it qcom?21:59
T42<nightishaman> google tensor g2, mali gpu21:59
malhmm, ok21:59
malprobably first device with such soc22:00
T42<nightishaman> its pr-testing22:00
maldo you have the tls-padding library on device?22:00
T42<nightishaman> yes22:00
maland the needed /etc/ld.so.preload ?22:01
T42<nightishaman> yes22:01
malbut the first startup wizard did show22:02
T42<nightishaman> until eula yes22:02
malI wonder if it would be worth it to try with master branch of libhybris and removing that /etc/ld.so.preload just to see how it behaves22:03
T42<nightishaman> what first22:04
malwhat dO you mean?22:04
T42<elros34> didn't you recently enable booster media? Some booster-silica is in logs maybe media one22:04
T42<nightishaman> what to try first22:04
T42<nightishaman> @elros34 no i didnt22:05
malwhat happens if you just remove that /etc/ld.so.preload22:06
T42<nightishaman> then lipstick doesnt start again22:11
malok22:12
malmaybe try installing master branch libhybris and see how it works22:12
maljust trying to rule out issues22:12
T42<nightishaman> any specialties or just git checkout22:16
T42<nightishaman> mal: there is a subdirectory named libhybris with a detached head, probably submodule, what to do22:23
T42<nightishaman> /hadk/hybris/mw/libhybris/libhybris/22:23
malgo to mw/libhybris and run git reset --recurse --hard origin/master22:24
malhopefully that will also reset the submodule22:24
malcheck that before building22:24
T42<nightishaman> it did22:26
malthen build_packages.sh - hybris/mw/libhybris22:26
malsorry; build_packages.sh -b hybris/mw/libhybris22:26
T42<nightishaman> mal: now it immediately crashes after udevd22:48
T42<nightishaman> 30s in22:48
malok22:52
T42<nightishaman> trusty crashed again22:53
malmaybe build the pr-testing branch again then, although it wouldn't affect trusty23:02
mala bit difficult to say what causes what in your case, if the crashes are random for example23:06
T42<nightishaman> the gpu crashes happen every time23:08
T42<nightishaman> the trusty crashes make me wonder23:10
T42<nightishaman> im gonna have to wait until my usb cereal arrives then to test23:12
T42<nightishaman> to get proper kernel debug23:13
T42<nightishaman> okay they postponed it till end of august23:21
T42<nightishaman> shame23:21
Sharks_Forgive me if I'm slack at replying, currently on morning tea break at work, but I can't see any apparent fault in `/system/bin/logcat -b all | grep -iE "voice|pcm|voip|incall|start_voice|s23:34
Sharks_top_voice"` when making a call. Am I looking in the wrong spot? https://paste.opensuse.org/pastes/e9201fda5d5223:34
malSharks_: you are using sailfish 5.1?23:36
malwhich pulseaudio-modules-droid version do you have? and droid-config submodule revision?23:36
Sharks_5.1.0.10 at the minute, yes. I have 'pulseaudio-modules-droid-common-14.2.109-1.aarch64', 'pulseaudio-modules-droid-14.2.109-1.aarch64', 'pulseaudio-modules-droid-hidl-1.5.1-1.aarch64'. Droid-configs-device is @41cd1d923:40
maltoo new pulseaudio-modules-droid, you should build 14.2.106 (commit 65edd31f62f22e2eec1f765608ca9c6ae5c4af7b)23:45
malwhen building next image use 5.1.0.11, that is the latest 5.1 release23:46
T42<nightishaman> mal: I can maybe fix the bug, it is here:https://github.com/maltesermailo/android_kernel_google_gs-6.1_google-modules/blob/1e54b63b9e871d876f6b98276ce0bf5c8f891cad/gpu/mali_kbase/platform/pixel/pixel_gpu_dvfs_metrics.c#L28023:48
T42<nightishaman> 23:48
T42<nightishaman> task is null23:48
malhmm, I wonder what causes it to be null23:49
T42<nightishaman> the process died that made the ioctll23:49
Sharks_thankyou mal, when I get home from work I will try that. Really appreciate it, I was quite lost trying to work out where I had gone wrong.23:50
malSharks_: when building pulseaudio-modules-droid, either use "build_packages.sh -b hybris/mw/libhybris" or use build_packages -o --mw (that -o means offline mode i.e. it won't update to latest commit before building)23:51
malSharks_: yes, it's a bit problematic when latest package versions won't work with latest public sailfish release, it happens sometimes23:52
Sharks_Understood, I'll delete the rpms in droid-local-repo, clone the correct version and build the offline mode. I was also planning on upgrading to 5.1.0.11 once I had the bugs ironed out23:53
malI'll go offline now, it'a already 3 am here23:54
Sharks_Goodness, I thought two nights ago it was bad that I was still debugging at 1:30AM23:55
Sharks_Thanks again, I'll let you know how I get on this evening23:55

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