[ROM] LineageOS 20.0 UNOFFICIAL - 1.0 [2022-10-03]

Search This thread

No1Alien

Member
Feb 16, 2015
35
120
LineageOS 20.0 for Sony Xperia XZ1 Compact

logo.png



RELEASE

This is an alternative ROM for the Sony Xperia XZ1 Compact, offering several privacy features.

Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.

FEATURES
  • Signed with dev keys
  • Up-to-date kernel
  • WireGuard kernel support
DOWNLOAD

ROM: https://sourceforge.net/projects/yoshino/files/lilac/lineage-20.0/
TWRP: https://sourceforge.net/projects/yoshino/files/lilac/twrp/
GApps: https://sourceforge.net/projects/yoshino/files/gapps/

Check the ChangeLog below for firmware requirements!


INSTALLATION

Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).

Or if you are coming from Lineage 19.x, dirty flash to 20.0 is possible too: flash the new TWRP, ROM, and GApps, su addons (if needed).

Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.

When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now ;)

Recommended GApps: MindTheGapps provided in this thread.

KNOWN ISSUES
  • Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
  • You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh

Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, sohrab1985


Source Code
https://github.com/whatawurst/android_device_sony_lilac
https://github.com/whatawurst/android_kernel_sony_msm8998
https://github.com/whatawurst/android_device_sony_yoshino-common

Rom Information
ROM OS Version:
Android 13
ROM Kernel: Linux 4.4

Version Information
Status:
Stable
Current Stable Version: 1.0
Stable Release Date: 2022-10-03
 
Last edited:

No1Alien

Member
Feb 16, 2015
35
120
SECURITY ADVICE

Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!


How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.
 

Sneexy

Member
Sep 12, 2021
6
3
Hello, I've flashed this ROM onto my device and it works, however Wi-Fi seems to randomly disconnect for a few seconds then reconnect, sometimes doesn't reconnect at all. Tried searching for a solution but found none. It seems to disconnect when any type of location activity happens? Currently rooted but also happens without root.
 

victor126

Senior Member
Sep 30, 2017
52
14
Hello, I've flashed this ROM onto my device and it works, however Wi-Fi seems to randomly disconnect for a few seconds then reconnect, sometimes doesn't reconnect at all. Tried searching for a solution but found none. It seems to disconnect when any type of location activity happens? Currently rooted but also happens without root.
did you format data
reboot to recovery
wipe all internal portions
reboot to recovery
then flash rom

just curious because i was gona try it
 

susetoyix

Member
Aug 17, 2019
16
2
I have done clean flash and I don't get any notifications or call screen on phone calls causing missed calls. No problems on wifi and mobile
 

norabitox

Senior Member
Dec 13, 2020
153
37
61
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
4G calling didn't work for me.
I used carrierconfig, the LOS version with 4G calls working.
This requires root.
The carrierconfig is located at data/user_de/0/com.android.phone/file.
carrierconfig-com.android.crrierconfig-~.xml
Replace the contents without changing the numbers in the name.
Why don't you try it?
sorry for my weird english.
 

azndan2

Senior Member
Apr 24, 2010
696
135
Los Altos
4G calling didn't work for me.
I used carrierconfig, the LOS version with 4G calls working.
This requires root.
The carrierconfig is located at data/user_de/0/com.android.phone/file.
carrierconfig-com.android.crrierconfig-~.xml
Replace the contents without changing the numbers in the name.
Why don't you try it?
sorry for my weird english.
What do I replace the contents with?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Paypal app iss not working for me, when I open it the app directly closes. Also clearing app cache didn‘t change anything.
    I haven‘t installed Magisk, so not rootet currently.
    Are you guys also face this issue?
    Install Magisk, enable zygisk and add PayPal to the denial list.
    Maybe you also need to set a valid build fingerprint with the help of "MagiskHidePropsConfig" Magisk Module.
    Should work then.
    It fixed it for me on 19.1 at least and across different devices, should be the same for 20.
    2
    @multiwirth Thanks a lot for your suggestions!
    I just installed magisk, enabled zygisk, added PayPal to the deny list, this alone didn't solved it.
    So I then installed "MagiskHidePropsConfig" Module, but PP still doesn't work yet.
    I assume I now need to figure out how to set a valid fingerprint via termux.
    hope I find some time this evening to figure this out.
    best regards!
    @multiwirth I just tried out your tip with setting a new device fingerprint via termux and this was finaly the solution, after reboot I was now able to open PayPal App without force closing again.
    So Big Thanks again for your help on this :)
    2
    @derf elot Not sure where to post issues, I'll try here first:

    I built a custom LOS20 build for Lilac today, based on current (as of nov 8) state of whatawurst and lineageos repo's, and while it builds, Bluetooth seems to crash (when turning BT on via quick tile, or when trying to pair a new device (no devices show up in the list of available devices, a crash of the bt app instead). Logcat fragment here.

    I did another build without two BT related commits (1, 2) from yoshino-common repo (reverted them), but BT still crashes. Not sure where to look, it seems a selinux_android_setcontext call fails.

    I found only one reference to a similar issue, without context, apparently from a logcat of raven device (Google Pixel 6 plus).

    ROM is plain, no other patches, no gapps, no magisk etc. I built a signed build, with keys generated by the build script (including 'bluetooth' key).

    On your LOS20 1.0 build BT works OK.

    Hello,

    I am assuming, you are signing the build with your own keys? In that case, you shouldn't use your own for bluetooth, otherwise they won't match the ones used for the BT module. The way I am doing it is to use the bluetooth keys from build/target/product/security/ to sign, instead of my own.

    Hope that helps.
    1
    @multiwirth Thanks a lot for your suggestions!
    I just installed magisk, enabled zygisk, added PayPal to the deny list, this alone didn't solved it.
    So I then installed "MagiskHidePropsConfig" Module, but PP still doesn't work yet.
    I assume I now need to figure out how to set a valid fingerprint via termux.
    hope I find some time this evening to figure this out.
    best regards!
    Do you have tried to "hide magisk app"?
    1
    Here is another solution (from xMarvin732 related to LSposed Zygisk, Shamiko zygisk), works with smart banking apps to me:
  • 14
    LineageOS 20.0 for Sony Xperia XZ1 Compact

    logo.png



    RELEASE

    This is an alternative ROM for the Sony Xperia XZ1 Compact, offering several privacy features.

    Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.

    FEATURES
    • Signed with dev keys
    • Up-to-date kernel
    • WireGuard kernel support
    DOWNLOAD

    ROM: https://sourceforge.net/projects/yoshino/files/lilac/lineage-20.0/
    TWRP: https://sourceforge.net/projects/yoshino/files/lilac/twrp/
    GApps: https://sourceforge.net/projects/yoshino/files/gapps/

    Check the ChangeLog below for firmware requirements!


    INSTALLATION

    Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).

    Or if you are coming from Lineage 19.x, dirty flash to 20.0 is possible too: flash the new TWRP, ROM, and GApps, su addons (if needed).

    Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.

    When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now ;)

    Recommended GApps: MindTheGapps provided in this thread.

    KNOWN ISSUES
    • Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
    • You tell me...
    Contributors
    derf elot, modpunk, Rooted_Ansh

    Thanks to the yoshino testers (let me know if I forgot to add you)
    coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, sohrab1985


    Source Code
    https://github.com/whatawurst/android_device_sony_lilac
    https://github.com/whatawurst/android_kernel_sony_msm8998
    https://github.com/whatawurst/android_device_sony_yoshino-common

    Rom Information
    ROM OS Version:
    Android 13
    ROM Kernel: Linux 4.4

    Version Information
    Status:
    Stable
    Current Stable Version: 1.0
    Stable Release Date: 2022-10-03
    6
    On a side note since it's unofficial, is it possible to add signature spoofing for MicroG?
    Making unofficial and custom builds of LineageOS for microG based on this ROM is (very high) on my ToDo list.
    No promises on ETA though :)
    4
    I have a solution to this (from the author of the tool / project I use for my builds). I will try it out when the cloud instance I am using wakes up (which will be about lunchtime (UK time) :)
    So that problem is solved, but my builds are failing, I think because of problems with the signature spoofing patches from lineageos4microg. That may be because they are not yet fully working with Android 13.
    ....
    later.

    Building without the signature spoofing patches works fine, but it is not possible to start microG because, without the patches, it cannot pretend to be Google play service :)

    It's not yet possible to make a build Lineage for microG for Android 20 that works
    https://github.com/lineageos4microg/docker-lineage-cicd/issues/335#issuecomment-1275363668

    I think I'd better go and shut down the very powerful and fast (and expensive) cloud VMs that are still trying to build.

    I will monitor the lineageos4microg issues, and have another try at making the builds when it has a chance pf succeeding. Sorry to have got your hopes up
    3
    I still don't know how to fix it in my build. I wpuld assume that it should be somewhere in the LineageOS source trees. Whoever built this ROM must have picked it up in their build, but I don;t know how to add it to mine.
    I have a solution to this (from the author of the tool / project I use for my builds). I will try it out when the cloud instance I am using wakes up (which will be about lunchtime (UK time) :)
    3
    no i said t Mobil and its virtual carriers like mint are the only ones this phone is not white listed on so yes it works on t mobile.

    white listed meaning it works on att and its virtual carriers but they wont provision the volte because sony didnt give them some paperwork or money i guess.
    Perhaps there's a misunderstand of what "white listed" means.
    It suggests it's "explicitly allowed".
    To say some carries are "the only ones where it's not whitelisted" would suggest that (a) it's whitelisted (and allowed) on other carriers, and (b) not allowed on T-Mobile and MVNOs.

    But it is allowed on T-Mobile, and it's not allowed on others like AT&T - which is the opposite of what you said. So you must either mean it's not blacklisted on T-Mobile, or it is whitelisted on it.

    Or maybe you mean something else entirely - at which point I'm again confused.