[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2023-01-21)

Shall F-Droid be included in the ROM(s)?


  • Total voters
    190
Search This thread

Dfis

Senior Member
Sep 21, 2022
135
6
Hello.
It's possible to update carrier config (IMS) for "Partner" carrier in Israel with VoLTE/VoWIFI support. Something like: amss_fsg_liliac_Partner_Israel_volte_vowifi_tar.mbn
Thanks
 

rez78

Senior Member
Nov 16, 2017
160
32
After latest update every turn on phone i see this notification: "the keychain app keeps crashing". What is it?
 

jurkoman

Senior Member
Oct 24, 2015
77
14
Hi, i have found an bug with missing incoming calls on latest update. In random moment i dont see who is calling me and phone freezes until SystemUI FC and helps only restart with button combination vol+ and power. After restart i dont see who called me in recent calls. In my work is quite annoying and most of time incoming calls work properly.
Edit: In stock rom .228 fw everything works perfect
 
Last edited:

rez78

Senior Member
Nov 16, 2017
160
32
Another bug for me in latest build: Bluetooth don't work,don't want turn on. I've reinstalled rom,but some issue
 

mxbndr

Senior Member
Sep 29, 2010
52
5
Another September build thing: When the device loses service (tunnel, basement, etc), it can't reconnect automatically. I always have to manually put it to 2G/EDGE, then back to LTE, and it will work. Compounding this issue is that when there is no mobile service, it will reset all network connections trying to find service, and so it will not stay connected to WiFi either. As soon as mobile service is restored, WiFi will reconnect and stay connected.

This isn't a huge problem most of the time, but when I travel outside of my normal home area it can be a real pain.

Is there a way to tell the phone to search for 2G/EDGE/GSM when there is no service, and then for LTE when it's on 2G? Even an app would be fine.
 

Rataplan626

Senior Member
Feb 7, 2006
387
100
Another September build thing: When the device loses service (tunnel, basement, etc), it can't reconnect automatically. I always have to manually put it to 2G/EDGE, then back to LTE, and it will work. Compounding this issue is that when there is no mobile service, it will reset all network connections trying to find service, and so it will not stay connected to WiFi either. As soon as mobile service is restored, WiFi will reconnect and stay connected.

This isn't a huge problem most of the time, but when I travel outside of my normal home area it can be a real pain.

Is there a way to tell the phone to search for 2G/EDGE/GSM when there is no service, and then for LTE when it's on 2G? Even an app would be fine.
Works fine for me (18.1 that is). Bluetooth works perfectly fine too. Actually streaming to a BT speaker while I'm typing this. So for you with issues, make a backup so you can always return to the current state, and then try a full wipe and reinstall. The rom works fine, so you can only try to narrow down where the issue is. Logcats / dmesg from when you enable Bluetooth or try to reconnect to network could also be supplied so there is some insight of what's happening.
 
  • Like
Reactions: rez78

7alvoo

Senior Member
Jul 18, 2019
161
52
I updated TWRP 3.7.0 and fixed the date handling.
I found the option to turn on the 18.1 special restart options (Setup>System>Hand Gesture>Switch On>Special Restart Option) so I thought I'd try the 18.1 version.
I applied a dirty flash but enabled the adb options first and it worked perfectly.

My experience has been remarkably positive.
- significant uptime improvement +15%+
- the system smoother and faster
- under 17.1 I never used the Ultra Dim feature but here under 18.1 it is very useful
- the gallery reads the sd card perfectly and fast it was stuttering for me under 17.1
did not start the 'snap camera' it is a 'safe mode' system after rebooting and clearing the cache it works
however it eats the battery the Open Camera is the better solution.

Thank you for your outstanding system!
 

mxbndr

Senior Member
Sep 29, 2010
52
5
I will find some logs. In the meantime, another couple of issues:
  • When restarting, either soft or hard, the phone does not reboot. It behaves like it's on (for example, my watch still shows as connected), but the screen is off and non-responsive (as if the phone was off; even the vibration for when it turns off occurs). The only way to reboot the device is to hold up on the volume key at the same time. The first time I did this, Nova Launcher crashed and several shortcuts (from a pair of different apps) were gone and had to be recreated.
  • Sometimes, when unplugging the device, it still shows as connected to USB even when it's not. This is on multiple cables and chargers (one charging block, one car USB).
 

mxbndr

Senior Member
Sep 29, 2010
52
5
Works fine for me (18.1 that is). Bluetooth works perfectly fine too. Actually streaming to a BT speaker while I'm typing this. So for you with issues, make a backup so you can always return to the current state, and then try a full wipe and reinstall. The rom works fine, so you can only try to narrow down where the issue is. Logcats / dmesg from when you enable Bluetooth or try to reconnect to network could also be supplied so there is some insight of what's happening.

What logs are needed? And do they need to be captured at a specific instance? Here are some SysLog found:

  • dmesg
  • event
  • logcat
  • modem
  • pstore_console
  • pstore_devinfo
 

decsimon

Senior Member
Aug 12, 2015
63
6
hi, i can't find the latest october 2022 version of lineageos17.1....there is only september
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    January updates out. Security updates only, MicroG versios will follow in about a week when I'm back from vacation. Stay safe!
    5
    I uploaded MicroG builds for all 3 versions, they are named e.g. lineage-19.1-20230131-MICROG instead of lineage-19.1-20230131-UNOFFICIAL but are contained in the same folder.

    As they are not compatible with each other (not sure if you can dirty-flash one over the other, at least you need to wipe system) you have to be careful to choose the correct one!
    5
    The 2G setting is gone since 19.1 i believe on derfelot's build as well.
    As for the fingerprint it's been like this on flamefires builds for a while, dunno why, some of his changes broke that functionality because on derf's builds it's working fine.
    I can double-check why the 2G setting is gone but it looks like it was removed upstream. I see if I can patch it back.
    As for the fingerprint: This is not "broken" but working as intended: A lot of people here complained that touching the on/off button immediately unlocks the phone. Hence I decided to follow suit with upstream LOS to disable this if the fingerprint is integrated into the powerbutton and cherry-picked a change used in similar LOS devices: https://github.com/Flamefire/androi...mmit/924352c24a95959941fe5a471741528dc2d87026
    Unfortunately there isn't a user-setting to change this although I was thinking about adding one. I think that the current setting being the default makes sense also from a security perspective as unlocking the phone also enables NFC payments so doing that by accident can be a real problem.

    Anyway: I'm currently very packed with work as I'm backporting security patches to the kernel, incorporating new changes from 19.1 to 17/18.1, updating blobs to hopefully resolve the connection loss issue (has anyone observed those on 19.1?) and just got the MicroG build working on 18.1 so at least that will be there once I'm done
    3
    I wiped all the data and did a clean install, but the system doesn't want to boot.
    You need to format the data partition, not just wipe it. It is usually possible to upgrade to a higher Android version by dirty flashing. but downgrading to a lower version usually requites you to format. The steps I usually follow are
    1. Format data partition
    2. Install the ROM
    3. Boot the system, go through first time setup, setting whatever screen lock (pattern, PIN) you had when you made the backup
    4. Boot to recovery
    5. Restore the backup

    Good luck!
    3
    - 2G is not selectable anymore as preferred network type in Settings (I sometimes need that when I'm in the mountains)
    I found this: "Android 12 users need to go to Settings > Network & Internet > SIMs > Allow 2G"

    However I just quickly checked on the spare phone and I do still have that setting on latest 19.1, although it is more hidden than on 17.1 (which I'm using personally)

    Also switching to 2G is what I do when I have network issues (and done by the switcher service on startup). But I've seen a changeset that might help better here. Will be included in the February builds if that works.

    EDIT: wiped system, reflashed zip and OpenGapps, wiped Dalvik (or rather ART) and cache... and it fixed itself. That's bit odd.

    Wiping dalvik and cache is what I always do. Here I guess there was something on /system which shouldn't be there. Glad you could fix that! The SafetyNet fix is one of the things I do test for every update so I'd be surprised if it doesn't work.
  • 53
    LineageOS 17/18/19 for Sony Xperia XZ1 Compact

    logo.png


    RELEASE

    This is an alternative ROM for the Sony Xperia XZ1 Compact.

    Creating this to honor the great work of modpunk and derf elot from https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/ which seems to be discontinued. Posting an own thread to keep the latest versions visible, I'm NOT claiming authorship over the ROM.
    I basically just build the ROM using the latest changes from upstream LineageOS/Google and kernel updates (usually incorporated by derf elot ) See my post.

    FEATURES
    • Signed with dev keys
    • EAS kernel
    • Passes SafetyNet out of the box (thanks Rooted_Ansh, Havoc-OS Team and kdrag0n)
    • Seedvault (Video)
    • IMS support (thanks to Rooted_Ansh and also Shujath)
    • 17.1 has stock Sony camera (not possible on 18+)

    DOWNLOAD

    You can download the latest release here.
    HINT: Download both the ZIP and md5sum file so TWRP can check the consistency of the upload/download.
    Make sure you download the right version, vanilla LineageOS is named lineage-*UNOFFICIAL-lilac.zip while the MicroG version is named lineage-*-MICROG--lilac.zip

    REQUIRED FIRMWARE: 47.2.A.11.228

    IMPORTANT:
    I only test the 17.1 releases myself. The 18.1/19.1 are build from mostly the same sources and hopefully work. I only test them roughly.
    Backup download

    INSTALLATION

    IMPORTANT:
    Magisk seems to cause issues (bootloops) on update, so remove it first and reinstall if required. Note that Magisk is usually not required unless you want root.
    1. Put the zip file of the ROM on your SD card or internal store and boot into recovery.
    2. When coming from stock ROM, do a full wipe (i.e. factory reset) via "Wipe". Do not wipe system! When flashing the stock ROM you can select to not keep user data which is equivalent to this step.
    3. Go to "Install", select the zip file and add optionally the gapps zip. Then flash it.
    4. After updates you may now wipe cache&dalvik (option after install)
    I suggest to use modpunks TWRP recovery. Again: Don't forget the md5sum file!
    TWRP 3.3.1-0 by modpunk / derf elot
    Or use the latest TWRP for 17.1/18.1 or TWRP for 19.1.
    3.7.0 Seems to work well with latest updates (decryption working) but LineageOS 19.1 (Android 12) requires the ones with "_12" suffix, e.g. 3.6.2_12.

    For ease of use I suggest to flash this recovery (only required once):
    1. Boot in Fastboot mode: Hold "Volume Up" while connecting the USB cable to phone and PC
    2. Flash TWRP by running this on the PC: fastboot flash recovery twrp-3.3.1-0-lilac-android10-1.img
      (adjust the filename if necessary)
    3. From now you can boot TWRP by turning on the phone with "Volume Down" + Power
    I heavily recommend to make a full backup before any installation so you can go back in case of issues. Flashing an older ROM usually helps to recover bootloops etc.

    Upgrades between versions​

    Dirty-flashing (e.g. from 17.1 to 18.1) works well but you have to also flash a GApps version matching the Android version or the device will bootloop.
    For the upgrade to 19.1 you may need to fully remove OpenGapps by wiping /system and install e.g. MindTheGapps.

    SUPPORT

    There is NONE. If you have any issues or question ask in the thread so maybe someone else knows the answer.
    I'm just providing the ROM (Lineage 17.1 variant) I use myself for others to try to and just build the Lineage 18.1 ROM without much testing.
    If you prefer to use a more well-tested Android 11 ROM, I suggest to look at Havoc-OS.
    Contributions to the sources are welcome and likely get integrated into the next release.

    Contributors
    modpunk, derf elot, Rooted_Ansh, Flamefire, linckandrea
    Source Code: https://github.com/Flamefire/android_device_sony_lilac, Original: https://github.com/whatawurst/

    If you want to buy me a coffee/beer, I'll appreciate it but it is not necessary.
    Also please consider donating to the original authors too or to local charities as requested by @modpunk

    Special thanks to landsome for donating a test phone for bug hunting and development.

    ROM OS Version: Android 10/11/12
    ROM Kernel: Linux 4.4.x
    Based On: LineageOS
    GApps: None included, except for the MICROG builds. Recommended is OpenGApps for 17/18 and MindTheGapps for 19.
    22
    CHANGELOG


    2022-01-20

    • January security patches
    • Kernel updates
    • MicroG builds added (build date 31st Jan, but same sources)
    2022-12-27
    • December security patches
    • AGPS fix (using Google servers)
    • Kernel updates (e.g. Wireguard v1.0.20220627, improved security against stack attacks)
    2022-11-15
    • November security patches
    • WLAN driver update
    • Huge APN update
    2022-10-13
    • October security patches
    • Kernel update
    • APN for DIGI HU
    • Option to switch temporarily to 2G on boot
    2022-09-29
    • September security patches
    • Kernel update
    • APN update
    2022-08-12
    • August security patches
    • Kernel update (CIP st20)
    2022-07-25/28
    • July security patches
    • Kernel update
    2022-06-30
    • June security patches
    • Kernel update
    • Backport fix for CVE-2021-39686
    • Workaround fixing bootloop with recent OpenGapps (20220503 tested)
    2022-05-16
    • May security patches
    • Fix mic volume issue with wired headsets
    • Known issue: OpenGapps after 15/2 result in bootloop
    2022-05-03
    • April security patches
    • Kernel update (CIP st5-tag)
    • Removed LineageOS updater (unused application here)
    • Added Sony identification packages (Compatibility for some Sony apps from other sources)
    2022-03-20
    • March security patches
    • Updated some carrier configs (mostly Indian&Chinese) for IMS (VoLTE...)
    • Better support for flip covers
    • Allow disabling battery optimizations for the SMS app
    2022-02-20
    • February security patches
    • Kernel 4.4.302 (final LTS kernel)
    • Re-enable VoLTE toggle switch (there were reports of modem crashes when VoLTE is disabled, can't reproduce this, hence added the setting back)
    2022-01-23
    • January security patches
    • Kernel 4.4.299
    • Wireguard v1.0.20211208
    • Enhanced display brightness range
    • Experimental Ultra-Dim mode
    2021-12-19
    • December security patches
    • Kernel 4.4.295
    • QCom driver updates
    • Fix some permission issues
    • Reset phone ID to XZ1C
    2021-11-29
    • November security patches
    • Kernel 4.4.291
    • Fix IMS on 17.1
    • Fix/enhance Wifi-Display
    • Fix some power hints
    • Update APNs
    2021-10-19
    • October security patches
    • Kernel 4.4.288
    2021-09-18
    • September security patches
    • Include some more security patches from AOSP
    • Clang 11 for LOS 17.1 version (same as 18.1, improved optimizations)
    • Misc bugfixes backported from Android 11 to Android 10
    • Kernel 4.4.283
    2021-08-11
    • August security patches
    • Fix bug with switch 3G->4G in XperiaParts not working on slow boot
    • Include some more security patches from AOSP
    • Kernel 4.4.279
    2021-07-20
    • July security patches
    • Kernel 4.4.275
    2021-07-03
    • June security patches
    • Update to Linux Kernel 4.4.272
    • Updated APNs
    20
    I'm happy to announce the June update. Took a lot more work as I backported quite a bit to our kernel to fix CVE-2021-39686 although I'm not sure we were ever really affected by that. Anyway the backport fixes that hole and a few potential others making the device a bit safer!
    15
    @MarkMRL Update 20220516 is out which should also fix the headset issue. Reproduced, found and fixed it as far as I can tell.
    14
    I updated the ROM with the January security patches. I also included the "Ultra Dim" QuickSettings tile to reduce the screen brightness (overall). But that is experimental. I'm thinking about including that in the range of the brightness, i.e. make the lowest brightness levels less. Problem is that there are only 255 values possible so I have to define a switch-over point somehow and distribute those 255 values over effectively 2 distinct ranges. Let's see...

    I also added Google Drive downloads temporarily as a backup if AFH fails again...