• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Stable][ROM]LineageOS 15.1 for Z5C (suzuran)

Search This thread

torukk

Member
Sep 19, 2014
45
29
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 !!
 

alex009988

Senior Member
Jun 8, 2011
419
170
Berni did you try this tree https://github.com/joel16/android_device_sony_kitakami-common to improve the camera for oreo? I tried joel common tree. common vendor and port camera changes of satsuki tree and vendor to karin tree and vendor and got non wroking camera - "Unowm CameraID" in the log. I also try to port back the way of working camera from Q but libshim of common tree is kinda incompatible to oreo, I also tried to port camera and fm from here https://github.com/x-keita but with no result.
 

alex009988

Senior Member
Jun 8, 2011
419
170
Joel is part of our small developer team. So I think, we're using each others ideas.
I don't know if he made something different than myself.
According to his changelog he uses different way to enable the camera.
- Back-ported camera wrapper from 17.1 sources. (No more half-assed closed source camera wrapper)
- Fixed front camera force close in Snap.
- Fixed video camera fps in Snap.

If you take a look at vendor he doesn't use Kang camera.qcom.so from suzu
and take a look at the commits from 26 nov.
I tried to represent tree and vendor commits but got camera non-working. Maybe I did something wrong or it requires something else.
So if this is indeed new way of camera fix, it will be good if you take a look at that commits and represent this for suzuran, after that me doing the same for karin
 
Last edited:

threader

Senior Member
May 31, 2010
206
135
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 !!
Sad to hear this, real shame the correct sources didn't leak...
Do you have the modified sources available so anyone interested can pick up the work?
 
Last edited:

Berni-0815

Senior Member
Sep 22, 2016
2,074
1,831
Germany
Sony Xperia Z5 Compact
New version out; see 1st post.

  • Android security patch level: 5 September 2021
  • Switched to signed builds!
 

Attachments

  • Screenshot_20210925-124131_Settings.png
    Screenshot_20210925-124131_Settings.png
    89.4 KB · Views: 13
  • Like
Reactions: TRKARTAL

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    New version out; see 1st post.

    • Android security patch level: 5 September 2021
    • Switched to signed builds!
    1
    New version out; see 1st post.
    • Android security patch level: 5 October 2021
  • 23
    Hi all:

    Here is a LineageOS 15.1 ROM for Z5 compact.

    Download 2021-10-17

    This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into twrp and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.

    Kernel sources
    Tree sources

    Features:

    • OS Version: 8.1.0 Oreo
    • Kernel: Linux 3.10
    • New: Android security patch level: 5 October 2021
    • Using sony blob's from stock version 32.4.A.1.54

    Important informations:
    • You should be familiar with general installation of custom roms.
    • Required for installation: TWRP 3.2.1(pick the version from 2018-02-23!!!)
      OR use my self built TWRP-version 3.5.2!
    • This ROM needs a clean install, old /data may cause problems!
    • This ROM is pre-rooted.
    • This ROM comes with F-Droid and UnifiedNLP.

    Working:
    • Phone calls
    • SMS
    • Manual mobile network search
    • WIFI
    • Bluetooth
    • Fingerprint
    • GPS
    • Location services
    • LiveDisplay (see attached pictures)
    • Enforced SELinux support (see attached picture)
    • New: Camera; built-in app (Snap *) ) and 3rd-party apps (Thanks to @torukk)
      *) Snap is only working with main camera! If you switch to the so called "selfie" camera, the app crashes and can't be restarted any more. If that happens, you have to clear the app storage (long press app -> app info -> clear storage). OpenCamera is working in both modes.

    These things are NOT working (don't ask!)
    • Encryption
    • FM-Radio (not included)
    Maybe some more things are not working.

    Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.

    Changelog
    9
    New version out; see 1st post.
    Changes:
    Fully working phone calls.
    Fully working SMS
    8
    Aren't you spreading yourself thin by also trying to maintain the Oreo version, along with Nougat & Android 10?
    The answer is quite simple:
    • los14.1 (N) is as stable as possible and development seems to be stopped.
    • los17.1 (Q) does not work stable enough at this device and I don't know how to fix that. And the memory issue (running out of memory) is still not fixed.
    • The sources of los15.1 (O) are as stable as possible. Why shouldn't I try to make this build better than before (camera)?
    7
    I'm now focussing on the network and outgoing call problem
    After some weeks trying to fix one of these problems I have to say that I'm not able to do so!

    I don't know enough about object orientated programming (c++ and java) to even know where to search and I don't want to end every day frustrated by that.

    So I've decided to stop every development on LineageOS 15.1 (and higher)!

    I'm sorry about that... :(
    6
    New version out; see 1st post.
    Android security patch level: 5 July 2020