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

Search This thread

gladykov

Senior Member
Jul 12, 2010
63
13
Dirty Flashed. Works well. Small difference with 19.1
- clicking clock in status bar does not open Alarm app anymore

Bugs still existing (comparing to 19.1):
- slide on status bar to adjust screen brightness does not work
-setting saturation to less than 50% causes screen to go BW
- blinking cursor sometimes disappears in address bar of Opera Browser
 

victor126

Senior Member
Sep 30, 2017
52
14
Sorry, what? Can you please be more specific?
First you said it was _not_ whitelisted on T-Mobile (so presumably doesn't work) and now you say it _does_ work on T-Mobile.
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.
 
  • Like
Reactions: 4qx

gladykov

Senior Member
Jul 12, 2010
63
13

Attachments

  • Screenshot_20221004-225757_LineageOS Settings.png
    Screenshot_20221004-225757_LineageOS Settings.png
    353.9 KB · Views: 32
  • Like
Reactions: norabitox

tonsofquestions

Senior Member
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.
 

Brickt0p

Member
May 29, 2022
11
3
just tried to flash it, unfortunately after flashing new twrp version and reboot to recovery I wiped everything:
- system
- cache
- dalvic
- internal memory
After reboot TWRP shows only splashscreen and when restarting it ends in a bootloop. I assume I have to flash twrp via adb via USB connection now, which is currently not possible for me due to no computer available :(
I assume this issue could have been prevented by not wiping cache, right? can someone please confirm.
Also does someon has an idea on how to turn off the phone now? or do I need to run Bootloop until battery is empty?

Thanks and best regards!
 

Arcline

Senior Member
Sep 11, 2016
139
52
just tried to flash it, unfortunately after flashing new twrp version and reboot to recovery I wiped everything:
- system
- cache
- dalvic
- internal memory
After reboot TWRP shows only splashscreen and when restarting it ends in a bootloop. I assume I have to flash twrp via adb via USB connection now, which is currently not possible for me due to no computer available :(
I assume this issue could have been prevented by not wiping cache, right? can someone please confirm.
Also does someon has an idea on how to turn off the phone now? or do I need to run Bootloop until battery is empty?

Thanks and best regards!
Press power + vol up to turn off.
Format data properly - go in the Format data option then type "yes".
 

azndan2

Senior Member
Apr 24, 2010
696
135
Los Altos
I tried replacing carrierconfig contents with those taken from the stock US rom. I also turned on IMS features in Xperia parts but still can't get service on T-mobile. Any ideas?
 
  • Like
Reactions: 4qx and PhobiaSoft

Brickt0p

Member
May 29, 2022
11
3
yes "Press power + vol up to turn off" did the trick, phone is now turned off :)

I already performed "Format Data" after I flashed new TWRP.
I assume the "TWRP Splash Screen Issue" arised due to wiping "Cache" unnecessarily afterwards.

I am guessing this as the following is stated in the TWRP FAQ therefore:
At this point, cache (not dalvik cache) is primarily used for recovery. It's used to store the recovery log and for storing OTA (Over The Air) updates. You probably don't need to wipe cache, and cache is already wiped as part of a factory reset.
 

azndan2

Senior Member
Apr 24, 2010
696
135
Los Altos
I was able to get LTE working on T-Mobile.

Steps:
1. Flash TWRP in OP using fastboot, or existing TWRP.
2. Install LOS 20 zip using TWRP
3. Install Gapps from OP using TWRP
4. (optional) Install magisk
5. In xperiaparts, toggle IMS then auto-reboot
6. Switch to 3G, wait till it obtains EDGE connection (this can take a very long time. 1-5 mins)
7. Switch to LTE, it will eventually obtain LTE connection after 1-2 mins.

Anyone have any idea on how to get around this? Would prefer not to have to do this every time lol.
 
Last edited:
  • Like
Reactions: 4qx

GT500s

Senior Member
Sep 25, 2018
61
11
Great rom ,smooth and very good battery life. Noticed problem with some apps that are closing after open like Xplore or Textra SMS. Also LTE internet speed is very low comparing to Lineage 18 or 19 that i was using previously.
 
Last edited:
  • Like
Reactions: Brickt0p

Arcline

Senior Member
Sep 11, 2016
139
52
Haven't tried it yet but i'm tempted. I will switch to this rom for sure eventually!
On a side note since it's unofficial, is it possible to add signature spoofing for MicroG?
 
  • Like
Reactions: 4qx

decsimon

Senior Member
Aug 12, 2015
60
6
Hi, there is Gcam mod apk working with this Rom? Gcam from PlayStore work only for photo, not for video....thanks
 

Dfis

Senior Member
Sep 21, 2022
72
1
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

Thanks a lot for the rom!
I've noticed that Wifi Calling / VoLTE is not working...
Tried several options from Xperia Parts -> Modem Switcher Activity and still calls not showing them...
Any advice?
** My service provider supports both
Another question, any way to revert to stock camera?
 
Last edited:
  • Like
Reactions: zpunout

Brickt0p

Member
May 29, 2022
11
3
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?
 
  • Like
Reactions: PhobiaSoft

Senz9090

Member
Jul 10, 2022
20
4
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?
Get the one from march 2022 version. ( And update from playstore, not sure its working).
 

Top Liked Posts

  • 1
    By dirty flash do you mean dirty flash over your Los 19.1 MicroG builds?
    Yes. I flashed the new LOS 20 CUSTOM-PLUS-E ROM over the LOS 19.1 version, and everything seemed to carry on as normal when I rebooted :)

    Which is handy because, when I was testing on my test device, I wasn't able to make a restorable TWRP backup of my 19.1 data. I did have an up-to-date ABRT backup, but I didn't need it
  • 3
    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 :)

    I have finally managed to create Unofficial and Custom builds based on this ROM. AndroidFileHost is still unwell, so the ROMs can be downloaded from Jaguar (links will expire in 180 days (2023-05-27) -
    Many thanks to the people here and in the `lineageos4microg/docker-lineage-cicd` repo who have provided invaluable help.

    I have successfully dirty flashed the Custom build on my daily driver, and clean flashed both versions on a test device.. They both seem to work OK, and I haven't bumped into any major problems.

    Have fun, good luck, and please feel free to provide feedback here, or raise issues in my Codeberg repo .

    An outline of the necessary steps in this post in my Codeberg project issue Please feel free to PM me if you would like more information
    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
    By dirty flash do you mean dirty flash over your Los 19.1 MicroG builds?
    Yes. I flashed the new LOS 20 CUSTOM-PLUS-E ROM over the LOS 19.1 version, and everything seemed to carry on as normal when I rebooted :)

    Which is handy because, when I was testing on my test device, I wasn't able to make a restorable TWRP backup of my 19.1 data. I did have an up-to-date ABRT backup, but I didn't need it
    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.