Monday, 2026-07-13

*** n2klb_ is now known as n2klb02:03
T42<elros34> @nightishaman just curious how usb => uart will help you debug your issue better? It's not like don't have acces to logs now06:20
T42<nightishaman> @elros34 Kernel gdb maybe to get more infos07:01
T42<elros34> ok never used it07:01
sharksOH YEAH! I downgraded pulseaudio-modules-droid to 14.2.106 and pulseaudio woudn't start, "Failed to parse module arguments". My old arguments were `rate=48000 hw_volume=false use_legacy_stream_set_parameters=true`. I removed the legacy_stream_set_parameters argument and we've got audio in calls!!! The Xperia 10 IV is a working phone again!07:06
sharksThankyou again mal, I've said it before but you're a legend among men07:07
T42<TheVancedGamer> replace find_get_pid with `get_pid(find_pid_ns(nr, &init_pid_ns));` (re @nightishaman: mal: I can maybe fix...)07:09
T42<nightishaman> @TheVancedGamer thanks07:10
T42<TheVancedGamer> fwiw you can also grab a USB-C breakout board, it's what I use for uart on my pixel07:10
sharksOkay now things are getting scary, I have a basically fully functioning port so I would like to get jolla store access etc... but reading hadk-faq I need to get OBS first? however I don't know what I am doing fully, and some things eg. sledges name, links for https://webhook.merproject.org/webhook are out of date, so not sure if the guide is fully reliable. Anyone willing to walk me through it?07:29
T42<elros34> more info about obs in hadk-hot -< that one which nobody is reading07:32
sharksThanks elros, I'll read up on what I can see there. Either way seems like first step is to contact @Keto so hopefully they spot this sometime07:34
T42<elros34> yeah you need account first07:35
sharksNot really worth releasing my port to the public without jolla store so yeah I'll have to work out how to set that up07:37
T42<adampigg> simple, you ping keto with some config (re @SailfishFreenodeIRCBridgeBot: <sharks>Not really w...)07:40
sharks@adampigg is this for jolla store or for OBS? I need to give keto the output of `ssu s` for jolla store but not before I've got OBS according to hadk-faq07:42
T42<adampigg> ah ok07:42
sharksSo I guess I just have to wait until it's a reasonable hour of the day in Sweden07:43
sharksDoes anyone have an official Xperia 10 IV in their drawer at the minute? What are the chances the output of `ssu s` is the same and I've already got jolla store access? haha08:11
Ketoxqcc54?09:21
sharksHey - `ssu s` spits out "Device model: Xperia 10 IV (pdx225 / pdx225)" on my build. My phone in particular is XQ-CC72 but I presume it will work on XQ-CC52 as well09:22
sharksI think 54 is 10V09:23
sharksI have not ported that09:23
Ketothat pdx225 is probably slightly wrong value to use for the model/variant... but I'm not sure09:29
sharksDrat, I wouldn't know how to change it now! It's worked up until now!09:30
sharksIt's the value all the LineageOS people used so I assumed I could use it too09:30
sharksSo do I need to come back another day after I've worked out how to change that value to XQ-CC72?09:36
Ketoafaik pdx225 is common X10IV platform, but then there are different xqcc* variants, which may require slighlty different configuration09:36
Ketothe official Jolla images are for xqcc5409:38
sharksHmm, I used Jolla official SFOS for 1.5yrs which was "supposed" to be for XQ-CC54, and it never had any problem. And as I say the Lineage people refer to the both of them as pdx225 and offer identical images for either 54 or 72.09:38
sharksIt appears I was wrong, it is 54 not 52 but points still stand09:39
sharksSee eg. https://wiki.lineageos.org/devices/pdx225/install/09:40
Ketoyeah, it probably works, I don't know what are the differences in those variants. but we just haven't had 72 device to test it09:41
sharksThe difference AFAIK is esim vs. second physical sim, but otherwise identical. But as I say I've used your image on a 72 device for a long time and have observed no apparent differences between that and a 54 device09:42
sharksAnyway if you want me to go back and change it to XQ-CC72 I guess I can work out how to do that and come back again another day?09:45
sharksI also wondered if it should be "murray" instead of "pdx225" but as I say, I have used pdx225 the whole time. Also fixup-mountpoints already used pdx225 which was another reason I was relatively confident that was a reasonable decision09:48
Ketoyes, that probably would be better. also we might need to think a bit how we name and identify these when there is a "official" and "community" port for the same device09:49
sharksSorry - what would be better? murray or XQ-CC72?09:50
Ketoxqcc7209:50
sharksOkay, and people who have a 54 will hopefully not be affected09:51
Ketoyes09:51
sharksI will try and work out how to change it tonight I guess and ping you again tomorrow09:51
sharksI agree we need some distinction between this and the official port, to be honest I thought Jolla might have a plan seeing as they have floated the idea of a community port a few times! But happy to work with you there.09:52
Ketounfortunately can't help you more right now, as I don't remember/know all the details09:56
sharksNo worries, as I say I'll try to figure out what I can in the next hour or two and ping you same time tomorrow if that works09:56
sharksWorst case I start all over again with xqcc72 instead of pdx225 and just make all the same changes I guess!09:58
sharksOh no I have to rebuild everything and I'm failing on the first hurdle10:21
sharks`breakfast $DEVICE` doesn't work when Android thinks the device is pdx225 but sailfish wants xqcc7210:21
sharksI'm not entirely convinced this is a good idea10:22
T42<BigChadCat> Couldn't you do something with init that sets the value to xqcc72 on runtime and let the codename remain pdx22510:26
sharksIs that an option? I'm just a guy sitting in front of a keyboard. @Keto or @mal can you please weigh in on this?10:27
T42<BigChadCat> I mean I'm more of an AOSP engineer and not SF, but we do this quite a lot of times10:29
sharksOh? Do you have an example I can look at in a device repo somewhere?10:30
T42<BigChadCat> github.com/xiaomi-sm615010:31
T42<BigChadCat> 10:31
T42<BigChadCat> You just want to change a property, right?10:31
T42<BigChadCat> Where is that property read from?10:31
T42<BigChadCat> https://github.com/xiaomi-sm6150/android_device_xiaomi_phoenix/blob/lineage-23.2/init/init_phoenix.cpp10:32
T42<BigChadCat> this is what I meant10:32
T42<BigChadCat> It runs on boot, and it detects a property to differentiate between global and CN variant of the device, and depending on that, sets SKU props10:32
sharksI don't know enough about Sailfish to know if I can do that10:33
sharksI would love it if I could10:34
T42<BigChadCat> same tbh, but it's worth a thought10:35
T42<BigChadCat> wish they sold these devices in IN10:35
malsharks: HABUILD_DEVICE env var10:35
sharksSorry mal, can you elaborate? I do not have that env var set in platformsdk or habuild. Do I set it in both, then run `breakfast $HABUILD_DEVICE`, then `make hybris-hal droidmedia etc` and it will output these to "./out/target/product/$DEVICE/" rather than "./out/target/product/$HABUILD_DEVICE/" so the `build_packages.sh` scripts are happy?10:38
sharksI just don't want to sit here for two hours while hybris-hal builds if that's not going to work10:39
malmake hybris-hal will output to whatever android think it wants to do, the HABUILD_DEVICE is for packaging part10:40
mali.e. build_packages.sh to find things correctly10:40
sharksso I ran `export HABUILD_DEVICE=pdx225` then `rpm/dhd/helpers/build_packages.sh --droid-hal`, and it fails because "Can't open ./out/target/product/xqcc72/obj/KERNEL_OBJ/.config: No such file or directory"10:41
sharksbecause it's in "./out/target/product/pdx225/..."10:42
sharksI could maybe just rename the directory but surely that will break something else10:42
malexport DEVICE=xqcc5410:42
malexport HABUILD_DEVICE=pdx22510:42
malI use those in my builds10:43
sharksI hate to say it but that is 100% not working here10:43
sharksOh that's why10:50
sharksrpm/droid-hal-xqcc72.spec should be rpm/droid-hal-pdx225.spec still10:51
sharksthis is going to get messy10:51
malyeah, if I remember correctly sony people said same image could be used with xqcc54 and xqcc7210:52
sharksYeah I can confirm that firsthand like I said10:53
sharksChanging the spec filename didn't fix it, I guess there's a lot more things like that where I don't know if I should be using $DEVICE or $HABUILD_DEVICE10:53
sharksWhy does `build_packages.sh --droid-hal` verify the kernel config, and where does it get the idea that the kernel config is at "./out/target/product/$DEVICE/..."?10:57
sharksright, "%define device" in rpm/droid-hal-pdx225.spec has to still also be pdx225, not xqcc7211:03
sharkswoo, built dhd, let's see if I can keep going11:04
sharksdang, stuck again at mw, "No provider of 'droid-hal-xqcc72-devel' found."11:09
sharkstime to grep logs11:09
sharksoh is it because I made a new target?11:10
sharksyeah totally is, okay gotta run build_packages with no params first i guess11:11
sharkshmm even then I still get it11:14
sharksAh, droid-configs/rpm/droid-config-xqcc72.spec is still supposed to have device pdx225 but also rpm_device xqcc5411:30
sharksor xqcc72 rather11:31
sharkssimilar story for droid-hal-version11:34
sharksno that didn't fix it11:36
sharkswhy is it looking for droid-hal-xqcc72-devel? I have in droid-local-repo droid-hal-pdx225-devel11:36
sharksoh there's a FAMILY variable11:38
sharksGreat, `export FAMILY=pdx225` did it11:40
malsharks: patterns need to be adjusted for the new spec naming11:45
sharksThat one I've worked out ahead of time, yet to be seen if I have done it right though11:45
sharksbuilding the mic now so should know shortly11:46
sharksAh crap I forgot parse-android-dynparts and things11:46
sharksshould have read my own notes11:46
sharksheh, there goes the phone. Nearly time to flash and see if it works11:56
sharkswell it booted12:04
sharksseems to work12:05
sharks`ssu s` now says "Device model: Xperia 10 IV (xqcc72 / xqcc72)"12:06
sharksSo I think I was successful12:06
sharksI will commit changes and go to bed. @Keto are you around sometime in the morning UTC tomorrow to talk about OBS things?12:08
Ketowhat kind of OBS things?12:10
sharksI am following hadk-faq & hadk-hot, it says in order to have jolla store access I should have OBS set up, and in order to do that I need an account, which I need to ping you about12:11
Ketook12:13
sharksThanks12:13
T42<nightishaman> @TheVancedGamer nr doesnt exist I substited for kctx tgid13:15
T42<nightishaman> https://github.com/maltesermailo/android_kernel_google_gs-6.1_google-modules/blob/lineage-23.2/gpu/mali_kbase/platform/pixel/pixel_gpu_dvfs_metrics.c#L28013:17
T42<b100dian> @NotKit the waydroid-ATV is not currently built for HALIUM, is that right? One needs to at least build that vendor image13:33
T42<b100dian> (halium is the waydroid way of working with hybris no?)13:33
T42<NotKit> @b100dian right. There are some patches at waydroid_vendor updated for 1613:34

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