Monday, 2024-10-28

rinigus@b100dian: very interesting! What are those errors? Java and f2fs?05:01
rinigusNot sure how to use gsi with sfos port, but it's ok to learn :).05:02
rinigusI was looking at 1v lineageos code, was thinking whether to port stock to that and then proceed via lineage. Also a backup plan. But as we don't have blobs now, it would make sense to test those05:04
rinigusOn stock, kernel is 5.10. so that's different05:05
T42<b100dian> rinigus: that jar error was java executing probably fontconfig which I had missing on my build machine. The next error is around this point https://pastebin.ubuntu.com/p/vD9f5FhCkY/09:04
T42<b100dian> (and yes I still have space on the host device)09:04
T42<b100dian> re GSI: it is just a test how much is device dependent on the system partition. Turns out that about nothing. Something like the halium image would probably work if so, or we could build a sfos one, but I don't have enough depth on the subject at the moment, just poking at it09:06
T42<b100dian> and yes, I'd prefer sony's OSS to deliver blobs, that's just backup plan09:07
rinigus@b100dian: strange error, I don't have it. maybe something is missing in the build system? these days I am using podman to make sure that my build env is more or less stable and possible to describe by a single file.10:06
rinigusmy used Dockerfile: https://paste.mozilla.org/tdGKN0Ar10:06
rinigusthen all you have to do is to add .gitconfig into the folder with that file and run podman build -t android-env .10:06
rinigusafter that, use by running in checked out android sources by running podman run --rm -it -v pwd:/android android-env:latest10:07
riniguswithin that env, it compiled "nicely" (still some bugs)10:08
rinigusI assume that the errors are from aosp14.10:08
T42<b100dian> I also use an actual focal host, but it is kvm, and a terraform script :) I'll compare the packages, but might try using podman too as cockpit supports it as well ;)10:08
rinigus:)10:08
rinigushere are packages that were a merge from sony aosp and lineage (thinking ahead)10:09
rinigusre GSI and device dependent: that's a good point! I wonder then why volte doesn't work.10:10
rinigusfrom tama days I remember that the camera quality was rather poor at aosp when compared to stock. its probably one of the reasons why stock is used as a base for lineage. so, in terms of hw quality, we may win by going via backup plans.10:11
rinigusin this respect, its good to poke around and see what can we do if we decide to avoid aosp10:12
T42<b100dian> there might be other GSIs out there where volte works10:22
T42<b100dian> my error might be because I was lacking the disks group for /dev/loopX10:22
T42<b100dian> I'll retry later since I now hit that matrix error again and need to go back to your pointers above when I have time10:23
T42<birdzhang> When will we get 5.0 targets on obs? I have a local build and it works well, just want to share 5.0 with my users.13:22
malwhen the release is final13:26
T42<birdzhang> ok13:31
T42<b100dian> rinigus: you said "used same vendor_framework_compatibility_matrix.xml as pasted in that issue"13:42
T42<b100dian> but I don't see any pasted xml in https://github.com/sonyxperiadev/bug_tracker/issues/838, just manual instructions - am I missing out?13:42
rinigus@b100dian: see https://github.com/sonyxperiadev/bug_tracker/issues/848#issuecomment-241202933813:45
T42<b100dian> ah, it was in another issue.. thanks :) s/yodo/nagara I hope?13:46
T42<edp_17> Is there a way to force rebuild pkcon repository? pkcon refresh just hangs and zypper cannot be installed because of the same reason.13:52
T42<b100dian> rinigus: did you also added a new git repo such as hardware/qcom-caf/[common] ?14:01
rinigus@b100dian: looks like yodo and nagara have similar issues while building14:04
rinigusre new repo - no, I don't have such  repo14:05
T42<b100dian> ok, trying to figure out what did I edit wrong from BoardConfig etc.14:11
rinigus@b100dian: I have added a line DEVICE_FRAMEWORK_COMPATIBILITY_MATRIX_FILE := device/sony/nagara/framework_compatibility_matrix.xml vendor/qcom/opensource/core-utils/vendor_framework_compatibility_matrix.xml14:52
rinigusand made that pasted file into device/sony/nagara/framework_compatibility_matrix.xml14:52
rinigusit did complain "Couldn't find AIDL metadata for: vendor.qti.hardware.radio.qtiradio.IQtiRadioStable in file device/sony/common/vintf/vendor.hw.qtiradio_ds.xml" but finished the build14:53
T42<b100dian> ah, that second path I missed, from the two-path line of your define, lemme report back14:54
rinigus@b100dian: https://github.com/sonyxperiadev/bug_tracker/issues/848#issuecomment-244181672314:55
T42<b100dian> so basically we should go back go r34 for now :)?14:55
riniguslet's see with _r3414:56
rinigusyes. not sure how much would it help, but we can try14:57
rinigus@b100dian: I had to add platform/prebuilts/remoteexecution-client in local_manifests/untracked.xml . otherwise sync was unhappy. hopefully it will not prevent building15:11
rinigusnope, errors on build. will send them as feedback15:24
T42<b100dian> this is for r34, right? I seem to be pretty advanced in building r55.. :D As an exercise, it seems..15:24
rinigusit is r34. will try again15:24
riniguswriting down here: r34 is using lunch aosp_xqct54-ap2a-userdebug15:25
T42<b100dian> I continued with testing this Lineage GSI which comes with build instructions too (but downloaded a prebuilt vN):  https://xdaforums.com/t/gsi-14-lineageos-21-trebledroid-based.4654132/15:25
T42<b100dian> This ones has call audio, and some settings/tweaks for VoLTE, did not have success yet, but is full of custom patches :-S15:26
rinigusbut when you are on stock, volte works for you? not sure my provider sets it for me yet. how do I check volte status with stock ?15:27
T42<b100dian> I tested it back on A13, basically for my provider the two tests I make are: 4G still up during call (and data flows in fast), and alternate method: sms gets received :) Because this fails on Vodafone w/o VoLTE for me15:29
riniguswill check whether 4g or 5g stays during a call - that should be sufficient15:31
rinigusthanks!15:31
T42<b100dian> this Lineage GSI I'm testing has an "override volte availability" which is keeping the LTE sign on but not actually working.. so you need to at least refresh a browser page or smth..15:33
T42<b100dian> anyway. this could be a start for stock + lineage port if sony times out15:33
rinigus@b100dian: r34 fails for me: https://github.com/sonyxperiadev/bug_tracker/issues/848#issuecomment-244193359015:41
T42<b100dian> assume you did clean out/ before making r34?15:43
rinigus@b100dian: even removed all sources (except .repo).15:50
T42<elros34> @edp_17 pkcon with zypper backend is a joke, maybe download rpm on other device or sdk target and install it via rpm command17:24
T42<edp_17> Thanks @elros34. Actually that issue was on a device and somehow storeman has caused it. Once storeman removed pkcon started working.18:29
rinigus@b100dian: I may have done something wrong with repo sync. will test r34 again18:56
T42<b100dian> ok. It's good to be prepared for when the blobs will come out ;D18:58
T42<b100dian> In the mean time: the lineage GSI I found can be forced to keep LTE on on calls, it just had wrong APN configs. But SMS did not work for me.18:59
T42<b100dian> I have also tested the built r55 system.img if it would work on stock just for kicks (it doesnt)18:59
mal@b100dian did you get a14 r55 built?19:01
T42<b100dian> yes, with some changes rinigus pointed out, like19:02
T42<b100dian> https://piggz.co.uk/sailfishos-porters-archive/index.php?log=2024-10-28.txt#line3619:03
T42<b100dian> and https://piggz.co.uk/sailfishos-porters-archive/index.php?log=2024-10-28.txt#line36 before that19:05
T42<b100dian> sorry, https://piggz.co.uk/sailfishos-porters-archive/index.php?log=2024-10-28.txt#line2919:05
T42<b100dian> well its all in today's discussion but may be hard to follow19:05
T42<b100dian> @elros34 wiki is now transferred to sailmates succesfully, ping me if you have issues as before19:14
rinigus@b100dian: which los gsi did you get?19:20
rinigussorry, found a link above19:20
T42<b100dian> Ok. It has a slow sf.net download though, but build instructions too19:20
T42<b100dian> the version I used is called lineage-21.0-20241017-UNOFFICIAL-gsi_arm64_vN.img19:22
rinigus@b100dian: and how do you install it? just fastboot flash system? (mainly for a record over here, so I can find it later if needed)19:31
T42<b100dian> Yes, with the rest of partitions being from stock with your newflasher instruction19:31
T42<b100dian> and `fastboot -w` to wipe data19:32
T42<b100dian> also, that needs to be done in fastbootd mode19:32
T42<b100dian> so `fastboot reboot fastbtoot` *or* `adb shell reboot fastboot` first19:32
T42<b100dian> or that usb-volume salute19:33
rinigusthanks!19:37
rinigus@b100dian: r34 building now20:07
rinigus@b100dian: I looked into what LOS repos are used for 1v port. its not that many and seems like sony puts out kernel and dts. 2 repos are generated from blobs, as far as I can see.20:29
rinigusoverview pasted here: https://paste.mozilla.org/gv3bpnhx20:29
T42<b100dian> rinigus: Looks like you're saying making our own Lineage should also be possible. I would have loved to avoid that but not totally against it.21:51
T42<b100dian> The problem with lineage is that it requires some java apps to test the functionality, so you  need to go into java-land packaging too21:51
T42<b100dian> which makes me feel uneasy :) I guess if all rom cookers to it..21:52

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