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

[ROM] LineageOS 17.1/18.1 UNOFFICIAL - (Update: 2021-11-29)

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


  • Total voters
    105
Search This thread

ygofoust

New member
Oct 10, 2021
2
2
Thanks very much for your help! To me there is an annoying issue with Gboard or swiftkey keyboard that there is a keyboard selection bar, when enabling gestures.

How do you remove the bar? It is really a waste of space for a small screen.

Thanks!
 
  • Like
Reactions: PhobiaSoft

ygofoust

New member
Oct 10, 2021
2
2
@7alvoo thanks for the link. I tried to understand it with google translate. They seemed to solve the issue with the navigation bar? However I couldn't find the setting after check nearly every possible setting.
 
  • Like
Reactions: mstrnemo

berti42

Member
May 8, 2016
7
1
I flashed the September Version of 18.1 and it seems, that everything is working well. I wiped my old 17.1 system plus data, cache and DALVIK with the latest TWRP, so i did a clean install. I also installed gApps pico then for minimizing Google at my device. At the beginning the wifi connection was cut often. But now i couln't notice that. For mobile data i had to change the APN configuration for my german provider "Drillisch". Later i will check GPS and battery drain.
 

mstrnemo

Senior Member
Feb 1, 2021
130
14
Pictures under the + mark
/i don't think it's a very wise decision to use these apps mainly for password writing/
Very interested in this but i could not find that screen either
@7alvoo thanks for the link. I tried to understand it with google translate. They seemed to solve the issue with the navigation bar? However I couldn't find the setting after check nearly every possible setting.

I second this Any help would be appreciated
 

trax7

Senior Member
May 15, 2012
952
344

For people who want to use F2FS:​

0. (Optional) Backup your data and apps and install latest TWRP 3.5.2 from the TWRP official site.
1. Reboot to TWRP > Go to Wipe > Advanced Wipe > Select Data > Repair or Change FIle System > Click F2FS

* CHANGING FILE SYSTEMS WILL WIPE ALL YOUR DATA *

2. Reboot to recovery again
3. Mount /vendor (should be handled automatically, only if you get mount error when flashing)
4. Flash zip file in attachments after flashing the ROM. It should support encryption too.
5. Enjoy! :)

Note: There is no point to make F2FS for /cache! In fact, it gets reduced performance in real world use.

** Here is why you might want to switch to F2FS.
*** If someone is interested in kernel building, there are kernel patches that can be applied for better operation and performance.
 

Attachments

  • FSTAB-EXT4_F2FS-encryptable_footer-LILAC.zip
    124 KB · Views: 4
Last edited:

berti42

Member
May 8, 2016
7
1
Now, i tested GPS with the app "Here we go" and everything is working fine. On the first try it didn't work because i didn't switch on the location-switch in settings:) I want to grant access to location service to only some selected apps and so i limited it in the location settings. Battery drain also seems to be as good as LOS 17.1
 
Last edited:
  • Like
Reactions: 7alvoo

petefoth

Senior Member
But you wiped system which gets rid of the OS if I understood it correctly. After wiping system you need to again install stock rom + then install lineageos on top of that. Someone correct me if I'm wrong.
In my experience, it is not necessary to install stock ROM before moving from LineageOS 17 to 18. The latest Stock ROM was Android 9 / Pie. Why would you need to go back an Android version (from LOS 17 / Android 10 / Q to Android 9 / Pie) when moving to LOS 18 Android 11 / R?

I have swapped between 17 and 18 with no problems
 
  • Like
Reactions: PhobiaSoft

toejam119

Senior Member
In my experience, it is not necessary to install stock ROM before moving from LineageOS 17 to 18. The latest Stock ROM was Android 9 / Pie. Why would you need to go back an Android version (from LOS 17 / Android 10 / Q to Android 9 / Pie) when moving to LOS 18 Android 11 / R?

I have swapped between 17 and 18 with no problems
When I installed 18.1 from 17.1 I didn't install stock rom in between, I just flashed 18.1 on top of 17.1, but I didn't wipe system in between, he wiped system which would remove his operating system completely, thus he's back to 0, thus now requiring some of the stock files again if he wants to install any LineageOS version. At least this was the order of installation with modpunk's version.

I quickly googled and found the following:
"Wiping system in TWRP erases your entire Android OS. Your device will no longer have an operating system. It will not wipe all of your user apps and data, as those are stored on the /userdata (Data) partition."
 

petefoth

Senior Member
When I installed 18.1 from 17.1 I didn't install stock rom in between, I just flashed 18.1 on top of 17.1, but I didn't wipe system in between, he wiped system which would remove his operating system completely, thus he's back to 0, thus now requiring some of the stock files again if he wants to install any LineageOS version. At least this was the order of installation with modpunk's version.

I quickly googled and found the following:
"Wiping system in TWRP erases your entire Android OS. Your device will no longer have an operating system. It will not wipe all of your user apps and data, as those are stored on the /userdata (Data) partition."
With official Lineage OS it is not necessary to install stock when installing 18.0 after wiping system.
I have just done the following on an Xperia Z3 (because I don't have my XZ1 Compact available for such experiments) but I am sure the same is true for this device.
  1. TWRP Wipe my existing system (an Android 10 / Q based /e/ OS ROM)
  2. TWRP Install `lineage-17.1-20210708-nightly-z3-signed.zip`
  3. Reboot system and complete first time setup wizard
  4. Power off
  5. Reboot to TWRP
  6. TWRP Wipe | Advanced | System
  7. TWRP Install `lineage-18.1-20210805-nightly-z3-signed.zip`
  8. TWRP Wipe Cache / Dalvik
  9. Reboot system and complete first time setup wizard
So, I do not believe it is necessary to install Stock ROM when installing 18.0 after wiping system.

But I'm always pleased to be proved wrong, so I'm willing to learn from your experience if following this sequence does not work for you.
 
Last edited:

mugenXperia

New member
Oct 14, 2021
4
1
Hi,

thanks for the rom. I really like to upgrade my XCompact to a more recent version. However, as it is a japanese model, I would like to try to make some changes in the kernel (NFC). I follow the instruction given from the source you gave in the post, but did not succeed. Would it be possible for your to share your build tools or which other magic sauce you may have.

Thanks
 

petefoth

Senior Member
Why this step? You wiped away LineageOS 17.1 you just installed.
Yes, because we were discussing whether or not it is necessary to flash a Stock ROM before flashing LOS 18.1. You suggested it would be necessary because @berti42 had wiped his system.

he wiped system which would remove his operating system completely, thus he's back to 0, thus now requiring some of the stock files again if he wants to install any LineageOS version.

I do not believe that to be the case, so I followed this process to check whether or not it was true. What I found out is that there is no need to flash a stock ROM when moving from 17.1 to 181 whether or not you have wiped the system. If I had not wiped the system, the experiment would not have proved anything.

In normal circumstances, I would never wipe the system when installing, because I believe that the old system is wiped as part of the install, so wiping would be a waste of time, effort and processing cycles. This thread is starting to become the same, so I will stop :)
 

PhobiaSoft

Senior Member
Aug 6, 2015
78
34
www.youtube.com
After updating to the September 18th version of 18.1 I've found that Chromecast no longer works on this device. The Cast device search works correctly but hangs upon actually trying to connect. Tried with an original release Chromecast and a Chromecast Ultra, and they both exhibit the same issue. It was working on the August 11th version of 18.1.

Can anyone reproduce this issue? Is Casting working for you on the September 18th version of 17.1 @Flamefire ? In any other situation, I would just downgrade, but my retinas are very grateful that the Sony logo is dimmed on the phone's startup now and I don't know if I can go back lol


EDIT: Reflashing the September 18th version of 18.1 fixed the issue, so it was likely a TWRP error of some kind that caused my problem, and not anything wrong with this version of the ROM. All is well now :)
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 10
    Currently uploading the new builds. Gonna take a bit...
    The 18.1 version seemingly works, passes SafetyNet etc. but as usual, I don't really test that version although I can now say that it flashes clean over the previous release and boots fine. Thanks to the test phone by @landsome
    I tested the 17.1 version the same way: Flash over previous release, boot and SafetyNet is working. However I'll flash that on my own phone tomorrow and test it a bit more "in production". Hence you'll find that in the "Testing Only" folder on AFH until I verified it a bit more. No time left for that today but if you want to give it a try feel free.
    As mentioned I fixed the IMS bug on 17.1 and on my phone (October build with only that patch applied) VoLTE and VoWIFI work fine.

    As for GPS: The XZ1C has known hardware issues with the GPS antenna. The ROM if flashed correctly works ok although I noticed that GPS is shaky too. Some users reported that squeezing the left edges often helps...

    I'll tackle the HD audio stuff later. That needs some more work to do it properly.

    Donations: See the initial post and my profile (About section). Always welcome and keeps me motivated to put in a bit of extra effort :) Please note that I often integrate changes from others, like modpunk/derfelot, linckandrea etc. On Github you can usually see that as "authored by X, committed by Flamefire" as I try to keep the author unchanged. So others deserve credit (and donations) too.
    7
    I'm writing this from my phone updated to 17.1 November build. Hence I consider it stable :)

    December update will be there mid December, I'd say. Not sure if I manage to fix HD audio till then

    So far, wish you a nice Advent season!
    5
    Updates will be there as soon as I got time. Likely in the next 2 days as usual ;)
    5
    Next update to keep you guys posted and tell a bit where the donations go:
    I was successfully able to reproduce a working ROM at the state of the October build. This is good news because it means at least I'm able to publish a fixed 17.1 version where IMS (VoLTE, VoWifi) works again if the November sources really don't work anymore and more importantly also means I have a starting point to bisect which changeset breaks the boot process. This is still VERY cumbersome but at least something.

    This trial&error method would NOT be possible without the test phone, as a failed attempt (soft brick) means I have to completely reset the phone, flash stock etc. which I obviously can't do on my own phone (which I especially now really rely on)
    The donations allowed me to upgrade my build machine with more RAM and SSD memory. This was still expensive but due to the donations it wasn't that much any more and at least the RAM (but not the SSD) is also useful for myself as I have my games on another partition on the same PC ;-) The SSD(s) were required as LOS (especially multiple versions) takes a lot of space and having that and the extended RAM allows for faster turnaround times in building making testing a bit easier. For comparison: A full LOS build from scratch on my old machine took ~8hrs, now on my new PC with the extended RAM and SSD I'm down to about 2hrs.

    So far... Now comes the painful work of figuring out what breaks the boot.
    Still: If anyone has information on how to debug such soft bricks that would help a lot!
    4
    Updates will be there as soon as I got time. Likely in the next 2 days as usual ;)
    Sorry guys the updates will take a bit longer after a very unpleasing experience with bootloops and the need for a partial reset of my phone during the tests of the latest update.
    As I'm currently quite busy and really need my phone I got to be careful with experiments so either I find enough spare time to test it again to find the cause or I'll likely wait for the test phone which @landsome shipped 3 days ago, so it should be here anytime soon.

    @ortizjammet and anyone who wants to play with HD audio:
    I attached 2 files which you can try: 1 is the original (renamed as you can see) one the modified one I used to get PA to recognize HD audio. You can try those with:
    -
    Bash:
    adb root
    adb shell mount -o remount,rw /vendor
    adb push ./audio_policy_configuration.xml /vendor/etc/audio_policy_configuration.xml

    Then reboot. To go back to original reflash LOS or repeat the above with the original file
  • 33
    LineageOS 17.1/18.1 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.1)

    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.
    REQUIRED FIRMWARE: 47.2.A.11.228

    IMPORTANT:
    I only test the 17.1 releases myself. The 18.1 are build from mostly the same sources and hopefully work.

    INSTALLATION

    Put the zip file of the ROM on you sdcard or internal store and boot into recovery.
    I suggest to use modpunks TWRP recovery. Again: Don't forget the md5sum file!
    TWRP 3.3.1-0 by modpunk for LineageOS 17.1
    TWPR 3.5.0-0 by derf elot for LineageOS 18.1
    Or use the latest TWRP from https://twrp.me/sony/sonyxperiaxz1compact.html.

    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.

    KNOWN ISSUES
    • UnifiedNlp doesn't work with LineageOS 18.1 yet
    • Spell checking doesn't switch if you change keyboards
    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
    ROM Kernel: Linux 4.4.x
    Based On: LineageOS

    Version Information
    Status:
    Stable
    Stable Release Date: 2021-10-19
    12
    CHANGELOG


    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
    10
    Currently uploading the new builds. Gonna take a bit...
    The 18.1 version seemingly works, passes SafetyNet etc. but as usual, I don't really test that version although I can now say that it flashes clean over the previous release and boots fine. Thanks to the test phone by @landsome
    I tested the 17.1 version the same way: Flash over previous release, boot and SafetyNet is working. However I'll flash that on my own phone tomorrow and test it a bit more "in production". Hence you'll find that in the "Testing Only" folder on AFH until I verified it a bit more. No time left for that today but if you want to give it a try feel free.
    As mentioned I fixed the IMS bug on 17.1 and on my phone (October build with only that patch applied) VoLTE and VoWIFI work fine.

    As for GPS: The XZ1C has known hardware issues with the GPS antenna. The ROM if flashed correctly works ok although I noticed that GPS is shaky too. Some users reported that squeezing the left edges often helps...

    I'll tackle the HD audio stuff later. That needs some more work to do it properly.

    Donations: See the initial post and my profile (About section). Always welcome and keeps me motivated to put in a bit of extra effort :) Please note that I often integrate changes from others, like modpunk/derfelot, linckandrea etc. On Github you can usually see that as "authored by X, committed by Flamefire" as I try to keep the author unchanged. So others deserve credit (and donations) too.
    7
    I'm writing this from my phone updated to 17.1 November build. Hence I consider it stable :)

    December update will be there mid December, I'd say. Not sure if I manage to fix HD audio till then

    So far, wish you a nice Advent season!
    6
    Updated with the July security patches.
    Note: AndroidFileHost was quite quirky today, so use the md5sum files to verify the integrity of the files