| T42 | <FakeShell> mal: do you happen to have your libhybris vulkan icd code somewhere? i am trying to make an icd of vulkan and even tho now it picks up my icd, right after that vulkaninfo throws a Bus error. passing in VK_LOADER_DEBUG=all as an env var shows that it is finding my gpu and driver: | 02:48 |
|---|---|---|
| T42 | <FakeShell> Using "Mali-G68 MC4" with driver: "libvulkan_hybris.so.1" | 02:48 |
| T42 | <FakeShell> to add to that, gdb shows no symbols or where we even are, as if the stack pointer is corrupted ^^ | 02:49 |
| rinigus | @b100dian: nice to see you resuming :). as you have done already, droid-hal-pdx224-kernel and friends should go to droid-hal at obs | 06:43 |
| rinigus | there should be nothing pdx223 specific in droid-hal-pdx223. we used the same approach for tama and it worked. | 06:44 |
| rinigus | actually, we should probably make droid-hal-vendor-dlkm into pdx223 and pdx224 versions. | 06:46 |
| rinigus | mal: probably dlkm can be somehow handled differently, but that way it allows to simply transfer los config to sfos | 06:48 |
| rinigus | I am adding dlkm files to sfos root, not separate partition. that way its easy to update. | 06:48 |
| rinigus | @b100dian: my mistake - dlkm is already different for pdx223 and 224 | 06:53 |
| rinigus | @b100dian: for me, sb2 -t sony-xqct54-aarch64 rpm -qa | grep kernel does list kernel. kernel is needed to make sure that dlkm is the same version as the corresponding kernel. see spec buildrequires | 07:01 |
| T42 | <b100dian> rinigus: thanks. I think I don't understand why just building droid-hal makes the dlkm package not be able to find the kernel one | 08:32 |
| T42 | <b100dian> Maybe I need to do the other steps to up until --version | 08:33 |
| T42 | <b100dian> But I remember an error at --config, let me try again | 08:33 |
| T42 | <b100dian> hmm sb2-config showtarget: default target has not been set. Maybe its because of this | 08:40 |
| rinigus | @b100dian: no, you should have the target set to as in sony-... well, if you copy commands from hadk | 08:58 |
| T42 | <b100dian> I did set it with sb-config -d sony-xqcq54-aarch64 and rebuilt packages with —droid-hal .. | 09:12 |
| rinigus | so, for some reason the package is not pulled via buildrequires from local repo. no idea why. also, not sure it was pulled automatically in my case either | 09:25 |
| rinigus | @b100dian: I can reproduce your error, I think. it looks to be an issue for the first build, when you don't have yet kernel installed | 09:55 |
| rinigus | now somehow it was installed for me before (I removed it from repo as a part of the test) | 09:56 |
| T42 | <b100dian> So, to proceed with the next steps (config and version) I would like to know if you have local changes to build --config with HABUILD_DEVICE vs DEVICE diffs? | 10:13 |
| rinigus | @b100dian: I don't build them locally, only via OBS | 10:33 |
| rinigus | how did you build dlkm? | 10:33 |
| T42 | <b100dian> `rpm/dhd/helpers/build_packages.sh --build=hybris/mw/droid-hal-vendor-dlkm --spec=rpm/$HABUILD_DEVICE.spec` is the command that fails | 11:05 |
| T42 | <b100dian> `rpm/dhd/helpers/build_packages.sh --droid-hal` before that succeeds | 11:05 |
| T42 | <b100dian> it might be that you have build the whole thing and _then_ added the dlkm dependency in the dhd | 11:06 |
| rinigus | @b100dian: if you set mainver and relver in spec to some numbers and after the first build swap to the current implementation it would work too. I'll try to find a better working solution | 11:08 |
| T42 | <b100dian> Good, let me try that next - right now I figured the manifest didnt sync hybris/droid-configs :D so I am trying to build forward up to —version | 11:09 |
| rinigus | locally? | 11:11 |
| T42 | <b100dian> too much error prone ;) ? | 11:12 |
| rinigus | @b100dian: no need as we have obs anyway. | 11:18 |
| rinigus | and keeping local config minimal | 11:18 |
| T42 | <b100dian> your last suggestion worked, I've uploaded the dlkm package, thanks | 11:20 |
| T42 | <b100dian> I am just going out, will test in the evening. | 11:20 |
| rinigus | enjoy! | 11:21 |
| rinigus | hmm, in principle we have already kernel-modules. which probably can be loaded in linux manner, not using scripts in android side. something that maybe even nicer in longer term | 11:28 |
| rinigus | @b100dian: found the way to install kernel before building dlkm. updated our hadk accordingly in dlkm section | 11:47 |
| rinigus | @b100dian: automatically updated vendor_boot with the wrong dtbo and phone refused to boot. on top of that, was unable to access the phone anymore via fastboot and even newflasher got "Error, no DATA reply!" | 13:22 |
| rinigus | fortunately, emma managed to flash stock android 13. so, lots of updates coming up, I guess | 13:23 |
| rinigus | its tempting to remove vendor_boot and boot img flashing from configs via update scripts. and let flash the images manually. but hopefully its isolated case. | 13:24 |
| T42 | <b100dian> Hmm I think I got that no DATA and used flash mode for newflasher... | 13:24 |
| rinigus | @b100dian: I was in flash mode with newflasher (green led) | 13:25 |
| rinigus | spooky | 13:25 |
| T42 | <b100dian> Yeah, but I definitely didnt have a windows machine for emma, so it was either green or fasboot blue led | 13:26 |
| T42 | <b100dian> So the uodates will be tested on devel by us :) | 13:26 |
| rinigus | before newflasher worked, its the first time for this | 13:30 |
| rinigus | @b100dian: was it that after unlocking bootloader, system updates should be done via newflasher? | 13:41 |
| T42 | <b100dian> rinigus: if you mean that the stock OS won't notify/install sony updates I guess that's correct. Not sure about emma. But mono xperifirm + newflasher should work, though it's a hassle to back up just to reflash everything | 14:22 |
| T42 | <b100dian> maybe extracting xperifirm sin files with unsin and flashing them discretionary | 14:22 |
| T42 | <b100dian> or even better, re-running extract-proprietary blobs and re-building lineage vendor..? | 14:23 |
| T42 | <b100dian> Fantastic job, rinigus! It booted right away : https://irc.thaodan.de/.imgstore/4b609898/file_7501.jpg | 15:08 |
| rinigus | @b100dian: nice! happy it worked. I'll later will proceed with the update of stock via newflasher (files are already here), then to LOS, and then to SFOS. as all files are in place, shouldn't take too long. if it works... | 15:23 |
| rinigus | as for emma, that did not provide the latest stock version for some reason. | 15:23 |
| T42 | <b100dian> rinigus: you don't remember having the network stuck at 3.5G instead of 4/5G, do you? | 17:36 |
| rinigus | @b100dian: no, not really | 17:36 |
| T42 | <b100dian> ok, just checking, will try to see what's happening in my case | 17:37 |
| mal | correct ofono binder config? | 17:37 |
| mal | the interface version | 17:37 |
| mal | @b100dian you have this https://github.com/mer-hybris/droid-config-sony-murray/blob/master/sparse/etc/ofono/binder.d/murray.conf ? | 17:38 |
| T42 | <b100dian> Yes https://github.com/sailfishos-sony-nagara/droid-config-sony-nagara/blob/main/sparse/etc/ofono/binder.d/nagara.conf | 17:40 |
| T42 | <b100dian> Let me check another sim though | 17:40 |
| mal | @b100dian do new nagara blobs also use aidl for nfc, sensors and gps? | 17:43 |
| mal | is that a14 based build? | 17:43 |
| T42 | <b100dian> lineage 21 so I guess yes | 17:44 |
| mal | so then probably you need the aidl versions of middleware | 17:44 |
| T42 | <b100dian> but I am not 100% sure since sensors work. I am just following rinigus' steps now and managed to boot on the sibling 5 IV | 17:44 |
| mal | check binder-list | 17:45 |
| mal | both hwbinder and binder to see where those things are | 17:45 |
| mal | are you using v7 blobs? | 17:45 |
| T42 | <b100dian> just one mention about the 3G / 3.5G stuff: Another SIM works fine with 4g, even shows as "connected" to Volte - probably only for the sms thing | 17:46 |
| T42 | <b100dian> mal: hang on, we're using lineage that rinigus brought up | 17:46 |
| T42 | <b100dian> which means stock blobs | 17:47 |
| rinigus | @b100dian: do you have double sim? I have single sim + esim (latter doesn't work on los). maybe that's why and I didn't test such config on los. could be broken already there | 17:47 |
| T42 | <b100dian> mal: binder-list | 17:48 |
| T42 | <b100dian> https://pastebin.ubuntu.com/p/5SnkktjzWp/ | 17:48 |
| T42 | <b100dian> rinigus: I thought they are all dual sim + microSD hybrid. Now I need to check.. But for the record I was using the 1st SIM tray, Orange (just purchased) didn't work (3.5G) but vodafone (a bit older the sim, 1y?) worked 4G | 17:49 |
| mal | that uses hidl for sensors and gnss, but for nfc I don't see anything there do maybe it's in binder-list -d /dev/binder | 17:49 |
| rinigus | mal: nfc is broken on sfos. probably sits on aidl | 17:50 |
| mal | I have wip nfc aidl code | 17:50 |
| mal | it already does talk to binder | 17:50 |
| rinigus | mal: great! is it already in out? as I know on android its android.hardware.nfc.INfc/default -> aidl | 17:52 |
| mal | I need to test on another device to be sure the code works, some device I know has working nfc | 17:52 |
| mal | unless you want to test my code | 17:53 |
| rinigus | mal: on android we have working nfc. sure, I can test. just need first to get back to sfos | 17:53 |
| rinigus | turned out that my dev pc/nagara combination refused to work anymore and I have to restore now all back from stock android. may take full evening... | 17:54 |
| mal | https://github.com/mer-hybris/nfcd-binder-plugin/commits/jb63598 | 17:54 |
| rinigus | thanks! | 17:54 |
| rinigus | @b100dian: I will add mal's nfcd binder to obs. then let's see who will get it to test first :) | 17:56 |
| rinigus | @b100dian: nfcd-binder-plugin is compiled and should be already zypper up away | 18:03 |
| T42 | <b100dian> :) | 18:31 |
| T42 | <b100dian> will try soon | 18:31 |
| T42 | <b100dian> mal: dual sim should be autodetected in /etc/ofono/ril_subscription.d/dual-sim.conf as it comes from sparse-14 right? | 18:31 |
| T42 | <b100dian> zypper in jolla-settings-networking-multisim #of course | 18:33 |
| mal | does the device have two real slots or one + esim | 18:36 |
| T42 | <b100dian> should have an actual dual sim the XQCQ54C0B | 18:40 |
| mal | https://github.com/mer-hybris/droid-hal-configs/blob/master/sparse/etc/ofono/binder.d/dual-sim.conf | 18:42 |
| mal | that is where the binder dual sim config is | 18:42 |
| mal | the configs are a bit of a mess | 18:42 |
| rinigus | @b100dian: there is also msim script in lineage that should somehow preconfigure it correctly. we may have to start there - but I haven't looked into it at all. | 18:47 |
| T42 | <b100dian> mal: I really was confused by the same-named file in /etc/ofono/ril_subscription.d | 18:48 |
| mal | yeah, it's for the ril plugin | 18:50 |
| T42 | <b100dian> rinigus: one more question: do you have telnet after boot is done? Should I look into usb-moded stuff or do you have another way to debug since wifi is a bit laggy | 19:27 |
| rinigus | @b100dian: no, I don't have telnet. There seem to be some interference with one android service and I couldn't fix it. See usb issue at our repo | 19:56 |
| rinigus | Wifi worked for me | 19:56 |
| T42 | <b100dian> Yes, works good but with some lag. Ok, noted | 20:16 |
| mal | @b100dian did you test that new nfc code yet? | 20:21 |
| b100dian | I zyppered up, let me find an app. nfc logger from openrepos I guess? | 20:22 |
| mal | yeah, or if you just have some simple tag you could see if works | 20:22 |
| b100dian | got this in nfc logger and systemctl status nfcd: "Xperia5IV nfcd[3086]: [dbusaccess] Name ':1.275' timed out" | 20:28 |
| b100dian | anything I need to restart & watch logs for? | 20:29 |
| mal | maybe run nfcd manually with /usr/sbin/nfcd -vvvvvv | 20:30 |
| mal | run "systemctl stop nfcd" before | 20:31 |
| b100dian | I did get 1 time (only) a target detected / type 4a tag / idle => have_target | 20:34 |
| mal | hmm | 20:34 |
| b100dian | but it is very hit or miss, I cannot get it now again | 20:34 |
| mal | make sure nfcd is still running and hasn't crashed or something | 20:35 |
| b100dian | This is the success on the log https://pastebin.ubuntu.com/p/2dr2z2sz7J/ | 20:35 |
| mal | so seems to work then | 20:36 |
| b100dian | this is the second time when it didn't https://pastebin.ubuntu.com/p/fQWQC5nNRZ/ | 20:36 |
| b100dian | so the first time it worked, but exactly once | 20:37 |
| mal | hmm | 20:37 |
| b100dian | might've been a race with waking up the display? | 20:38 |
| mal | not sure, maybe | 20:41 |
| b100dian | I mean I did have to turn on the screen exactly at that test. wasn't able to reproduce though | 20:41 |
| mal | but that tells the basic code is ok at least and it can see a tag etc | 20:41 |
| b100dian | yes, it did read, that's correct | 20:42 |
| mal | I will recheck the code and of course test more on some of my devices | 20:42 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
