No; I had to set it down for a while, and haven't had time yet to pick it back up. In the meantime I've been happily using stock Sony firmware with both VoLTE + VoWiFi. But I want to find time to start poking at this again. I will probably have to start over from scratch using the notes I wrote here, because I honestly can't remember at this point (after all the time that has gone by) where I left off, or what my workflow was that I came up with to produce a build of 15.1 that has at least working VoLTE. (Though I probably still have a copy kicking around of the 15.1 build I came up with that has working VoLTE, if that would be useful/helpful to you.)
Yes, if you read my other posts, you'll see that I called out how previous builds of LOS for Z3+/Z5 family could never have had working IMS/VoLTE. Kang-ing of Qualcomm IMS userland blobs from Sony ROMs was woefully incomplete.
I realize that at this point Oreo is too old to be attractive to users as a third-party ROM, at least as long as usable Android 10/11 builds exist. Still, I think it is important that the IMS puzzle gets solved on Oreo first, because from what I've gathered, Oreo is the last version of Android that supports the older IMS service APIs without any changes. To continue to use these blobs in Android 9/10/11, shims will likely need to be written. (Either that, or IMS blobs from other phone model stock ROMs that are written for Android 9+ and are also compatible with the MSM8994 modem will need to be substituted in.) But before we get to writing shims, we should make sure there isn't anything else we have missed...making sure it runs in Oreo correctly is a good way of doing that.
OK, after I gave up all development for this phone, I can share where I ended.
I initally thought that not working IMS is the problem of our old vendor binary rild library. I came across qualcom proprietary leak (actualy I later found 3 different) unfortunatelly for different chipset, which means parts of code is still provided by qualcom as binary only, so I can't use it. But lot of the code was available and the version was somehow matching the last official z5 version (like year 2017 in source code headers, it was without git versioning). I was able to compile vendor rild library which don't need rild-wrapper and other modifications (speaking about berni and tarkzim repos). But because of dependencies, I was forced to compile like 30 binaries which I replaced those from vendor blobs. I spent enormous time especially with making gps work. Then IMS was not working still. Although I was partially successfull running those ims blobs (I learned apex format for this, which is really useful chroot like environment, very good for unresolved dependencies), but then I wasn't able to make ims.apk working. When I was hopeless, I contacted eErenYeager (who first ported ims.apk to oreo and higher) and he gave me very usefull tip, that I need to use rild from oreo. So ims.apk started to work, but to my biggest surprise, it was not enough. Only then I realized, that I need to modify the modem directly and ammend IMS config for my specific carrier. I can't remember the software now (you mentioned you used it, I mean the exact technique) but it exist only for windows, which I don't have and not planning to. It also means, my other phone xiaomi santoni, which has IMS supported in ROM, was not using volte at all. I just thought its a matter of carrier supporting it (they list this device as volte supported), I had also enabled volte in my personalized carrier web portal settings, enabled in lineageos, yet it was not working and I wasn't even aware of it. I felt really mad after discovering, that carriers provide their ims modem settings to device manufacturers, who are either directly program it to modem, or they have a proprietary way to program the modem from OS. Such a waste of time.
I gave up, I'm buying new phone by the end of the year, will do proper thorough research regarding manufacturer provided software for the phone before. Shame on qualcomm !!
github.com
Good to know it's a known issue, too bad then... I guess there is no solution for it?
(don't think anything these days comes close to the z5c with respect to the small size and battery life)
