[ROM][Unofficial][10.0][signed][OTA] Lineage OS 17.1 for Xperia Z1 compact

Search This thread
. . .
The rom is very stable, fast and up-to-date --> nearly perfect!
. . .
But the battery cycle time is very poor compared to stock rom.
. . .
Thanks for the in general positive feedback.
Regarding battery behavior - let's start first with some generic statements:

When you say, you come from Stock ROM, this means Android 5.0.2 (aka API level 21) or even Android 4.4.4 (aka API level 20). LineageOS 17.1 is Android 10 (aka API level 29) - each Android generation in general is more resource-demanding than its predecessor, which obviously also impacts the battery behavior. Same as for the opensource-parts of Android, this also applies especially to the Google-apps, which also have grown over time and are for sure not really known for their energy efficiency (the Google Play services for Android 5 are significantly lighter than those for Android 10).

Custom ROMs consist of an Opensource part, but they also make use of the device manufacturer's closed source drivers (so called vendor blobs). So specific energy optimizations depend on the collaboration of specific kernel tweaks (open source) with the closed source device drivers. Whilst there are manufacturers being developer friendly, others aren't by means of really sharing their tweaks. And Sony is "not that developer friendly", even if one could get a different impression, when looking at their open devices program... - There are specific examples, where Sony even implemented things in their closed source parts, which didn't truly have a technical meaning other than making it more difficult for Custom ROM developers... (e.g. Camera)...
Talking about vendor blobs, the last vendor blobs from Sony for this device, which are still in use, come from 2015 and were designed for Android 5.0.2 and the Android 10 operating system has to work with them, which also isn't really ideal.

So from that generic stand point, I am not surprised, that the latest Stock ROM has shown a better battery behavior than this ROM. So in the case of older devices like this one, you indeed have often only the choice between an outdated Stock ROM with an outdated Android version, which does not provide basic privacy features and hasn't received any security update since years, but is lightweight, and a modern, but meanwhile heavier Custom ROM.

I'm not saying, that there isn't any potential for improvement, but neither @115ek nor myself are really "kernel/device cracks" being able to optimize everything - we take advantage of the work of very good developers, who managed to get the Z1c working with modern Android versions. Nevertheless, based on the above stated, I am pretty sure that it won't be possible to fully get to the level of the Stock ROM.

Regards, M.
 

Schuwarth

Member
Nov 4, 2013
38
20
Thanks for the in general positive feedback.
Regarding battery behavior - let's start first with some generic statements:

When you say, you come from Stock ROM, this means Android 5.0.2 (aka API level 21) or even Android 4.4.4 (aka API level 20). LineageOS 17.1 is Android 10 (aka API level 29) - each Android generation in general is more resource-demanding than its predecessor, which obviously also impacts the battery behavior. Same as for the opensource-parts of Android, this also applies especially to the Google-apps, which also have grown over time and are for sure not really known for their energy efficiency (the Google Play services for Android 5 are significantly lighter than those for Android 10).

Custom ROMs consist of an Opensource part, but they also make use of the device manufacturer's closed source drivers (so called vendor blobs). So specific energy optimizations depend on the collaboration of specific kernel tweaks (open source) with the closed source device drivers. Whilst there are manufacturers being developer friendly, others aren't by means of really sharing their tweaks. And Sony is "not that developer friendly", even if one could get a different impression, when looking at their open devices program... - There are specific examples, where Sony even implemented things in their closed source parts, which didn't truly have a technical meaning other than making it more difficult for Custom ROM developers... (e.g. Camera)...
Talking about vendor blobs, the last vendor blobs from Sony for this device, which are still in use, come from 2015 and were designed for Android 5.0.2 and the Android 10 operating system has to work with them, which also isn't really ideal.

So from that generic stand point, I am not surprised, that the latest Stock ROM has shown a better battery behavior than this ROM. So in the case of older devices like this one, you indeed have often only the choice between an outdated Stock ROM with an outdated Android version, which does not provide basic privacy features and hasn't received any security update since years, but is lightweight, and a modern, but meanwhile heavier Custom ROM.

I'm not saying, that there isn't any potential for improvement, but neither @115ek nor myself are really "kernel/device cracks" being able to optimize everything - we take advantage of the work of very good developers, who managed to get the Z1c working with modern Android versions. Nevertheless, based on the above stated, I am pretty sure that it won't be possible to fully get to the level of the Stock ROM.

Regards, M.
Thanks for the explanation and your work for this device!
 

115ek

Senior Member
Jan 30, 2017
550
618
Dropping google apps completely is a good idea for several reasons. Also when it comes to battery usage.
If you really can't renounce apps relying on the google framework, microG can be a less ressource-intensive alternative.
And then there are the performance settings in the battery options you may also try.

Anyway: If I bring my device to the office it'll also loose battery faster than outside. Leaving it in a place with bad reception is most likely having an influence.
And one more tip: Sometimes also a reboot is a good idea.
 
  • Like
Reactions: MSe1969

veloc_h

Senior Member
Oct 10, 2019
52
3
Even me as a noob has now understood the difficulties you are facing and the problems in General to create a custom rom for an old mobile, especially for a Sony mobile, whose developpers hide important parts of their code. Thanks a lot, @MSe1969 !
 
  • Like
Reactions: MSe1969
sorry, I should have written: the parts of the kernel, which include the Sony cam module. I would like to have the Sony cam because it would be a pity not tu use the outstanding qualitty of this cam.

I have a rought idea, that there are certain prerequisites for the Munjeni (or Sony) code, which are related to kernel or the Android Version.
To conclude the Sony camera topic:
  • If I have understood your request correctly, you would like to use the Sony Stock Camera app, which has been shipped with the Android 5.0.2 Stock ROM - so I seriously doubt - taking e.g. Android 10 specific features like "scoped storage" into consideration - that this would even be possible at all.
  • What I explained in my previous post about battery behavior, many aspects of that post would also apply to this topic. So this would by far not be trivial at all and would involve a lot of work and testing!
  • Camera indeed has been a big topic for this device: Android 5.x Custom ROMs used the Android 4.3 drivers (w/o that Sony DRM BS involving the TA partition) as a workaround (with lower resolution), there was no Android 6 Custom ROM with a working cam, and starting with Android 7, a breakthrough was made in regards to a working cam, which means that many excellent devs have put already effort into this topic - devs having more skills in that specific area than we do.
  • The Z1c is not my primary ("daily driver") device, and I think it's the same for @115ek - that having said and considering that this is a hobby for us (we both have more than one device thread), I am pretty sure that you will understand, that - independent from its unproven technical feasibility - "this won't represent our highest priority", to put it diplomatically, but bluntly...
Nevertheless, feedback, questions and ideas are welcome! But not all can be implemented.
:cool:
 
  • Like
Reactions: tramp20 and 115ek

tramp20

Senior Member
Jan 15, 2012
733
138
Rosenheim
Yes, that's exactly how it works and I can confirm that the magisk survival script does its job very well :)

You are really sure that a ROM update does not kill all Magisk versions > 20.4?
I don't believe this ( I have several Z1c) and you are alone with this statement.
look here:
 

veloc_h

Senior Member
Oct 10, 2019
52
3
  • If I have understood your request correctly, you would like to use the Sony Stock Camera app, which has been shipped with the Android 5.0.2 Stock ROM - so I seriously doubt - taking e.g. Android 10 specific features like "scoped storage" into consideration - that this would even be possible at all.
  • What I explained in my previous post about battery behavior, many aspects of that post would also apply to this topic. So this would by far not be trivial at all and would involve a lot of work and testing!
  • Camera indeed has been a big topic for this device: Android 5.x Custom ROMs used the Android 4.3 drivers (w/o that Sony DRM BS involving the TA partition) as a workaround (with lower resolution), there was no Android 6 Custom ROM with a working cam, and starting with Android 7, a breakthrough was made in regards to a working cam, which means that many excellent devs have put already effort into this topic - devs having more skills in that specific area than we do.
  • The Z1c is not my primary ("daily driver") device, and I think it's the same for @115ek - that having said and considering that this is a hobby for us (we both have more than one device thread), I am pretty sure that you will understand, that - independent from its unproven technical feasibility - "this won't represent our highest priority", to put it diplomatically, but bluntly...
In the meantime I have asked munjeni to make available the specific commits in his kernel in order to create a pull request, but he said they were too old (he didn't specify his statement yet).
"... you would like to use the Sony Stock Camera app, which has been shipped with the Android 5.0.2 Stock ROM - so I seriously doubt - taking e.g. Android 10 specific features like "scoped storage" into consideration."
-> I should have written: does it make sense and is it possible to implement the Sony stock camera app; limited scope for reading and writing files: obviously a conflict of a user-right system (?)
"... by far not be trivial at all and would involve a lot of work and testing!"
Ok, I do understand that.
"... won't represent our highest priority"
It was my second phone until I lost my number one mobile, that's why I wondered to buy a new or another used mobile or to keep the z1c. Because a friend had installed a new battery und a new vibration sensor I decided to give LOS a try (and because revengeos on Mi5 made me quite happy, including acceptable photos). But this is my personal "priority" and I really appreciate that you und 11Sek take your (free!) time for the LOS z1c development. Generally I'm buying used electronics and try to use the gadgets as long as possible. The z1c is quite powerful (compared to my second mobile, a s3mini) and the camera sensor (20mb) is quite huge for the time, the z1c was sold and even now.
By the way: I'm surprised, how performant the s3mini behaves with Android 5 and without google!

I'm going to test the slider power save settings and I will report the results.
Thanks and best regards
veloc_h
 
  • Like
Reactions: MSe1969

yldun

New member
Feb 3, 2021
4
3
Hello,
Thanks for your work, I'm glad to be able to use Lineage 17.1 now :) using the «A standard version».
I used to run Lineage 16.1 before, and it worked well.

I have an issue with the camera, and although some of you pointed an issue with gallery, I'm not quite sure it's the same : the video is working fine, but I can't save photos. When I click to take the photo, depending on the app [Simple Camera, Open Camera, the basic camera], it freezes or does nothing. Using Open Notes scan, results are the same.
I'm worried I'm the only one with this issue.
Maybe I missed some answers, but if you have lead me so I can run further diagnostics, I'll be glad to do so.

Have a nice day,
 
My plan was to use only the built in gps module of the z1c.
Edit: therefore I have disabled any google server. wlan and network gps source.
In fact, in Android 10, there is no distinction any longer, whether to use GPS or coarse location, the system decides it. What you should do, as indicated by me, is the following: Install Déjàvu from FDroid as coarse location provider. It has no internet connection and simply records locally, what the GPS finds. By doing so, you have no connection to any location server and you have a properly configured microG not disturbing any GPS fix.
 
  • Like
Reactions: veloc_h

veloc_h

Senior Member
Oct 10, 2019
52
3
déja vu according to https://github.com/n76/DejaVu#:~:te...data acquired by the phone stays on the phone. "uses locally acquired WLAN/WiFi AP and mobile/cellular tower data to resolve user location. Collectively, “WLAN/WiFi and mobile/cellular” signals will be called “RF emitters” below."
My intention was to use the gps on my walks in the middle of nowhere, where there is no wlan, no cellular, only the built in gps module. Or didn't I understand the principle?
 
déja vu according to https://github.com/n76/DejaVu#:~:text=Déjà Vu - A Local RF,called “RF emitters” below.&text=All data acquired by the phone stays on the phone. "uses locally acquired WLAN/WiFi AP and mobile/cellular tower data to resolve user location. Collectively, “WLAN/WiFi and mobile/cellular” signals will be called “RF emitters” below."
My intention was to use the gps on my walks in the middle of nowhere, where there is no wlan, no cellular, only the built in gps module. Or didn't I understand the principle?
:)
OK, I'll explain again.
1. You only want to use your GPS and do not want to deal with any coarse location provider. Understood.
2. A side effect of microG is, that if you don't configure a coarse location provider, it may disrupt the location process, even if you don't want to use it. Hence, you need to configure a coarse location provider just for the sake of getting a proper GPS fix.
3. You could easily use the shipped Mozilla location provider. Mozilla isn't Google, but the Mozilla location provider is a server, to which your phone needs to send cell tower data, and I understand, that you don't like that idea. So my suggestion to install and configure Dejavu in microG should give you, what you want:
GPS fix isn't disrupted any longer and no cell tower data sent to any server.
 
  • Like
Reactions: veloc_h

veloc_h

Senior Member
Oct 10, 2019
52
3
When I click to take the photo, depending on the app [Simple Camera, Open Camera, the basic camera], it freezes or does nothing.
did you check the gestures settings? I don't have this issue (basic built in cam and open camera). Which version of LOS have you got?
 

2faraway2

Senior Member
Apr 24, 2016
184
29
You are really sure that a ROM update does not kill all Magisk versions > 20.4?
I don't believe this ( I have several Z1c) and you are alone with this statement.
look here:

You're right, I didn't read your question carefully that you are already on 21.4.
I'm still on 20.4 (means I didn't updated to 21.4) and on this release the rom ota-update works fine thanks to the survival-script

Sorry for the confusion !
But for me a hint not to update magisk .. ;-)
 
  • Like
Reactions: tramp20
New builds with February 2021 ASB patches available

Hi all, new builds are available and offered as OTA updates via the updater app.

A. Standard LineageOS 17.1 build
  • Security String 2021-02-05
  • misc. kernel patches

B. Pre-installed microG build variant with additional security patches
  • Security String 2021-02-05
  • misc. kernel patches
  • Bromite System webview updated to 88.0.4324.141
  • Bromite Browser updated to 88.0.4324.141
  • F-Droid 1.10-alpha-234
  • microG 0.2.17.204714-5

@115ek - please update OP/Changelog

Regards, M.
 
  • Like
Reactions: tramp20 and 115ek

tramp20

Senior Member
Jan 15, 2012
733
138
Rosenheim
Thank you for this new update.

Btw: OTA not yet available (06:00) from 20210114

Are these kernel patches important/necessary?

See https://forum.xda-developers.com/t/...1-for-xperia-z1-compact.4007983/post-84404975

It is a lot of work:
uninstall Magisk 21.4 (all settings are gone).
install 20.4 (configuring all again)
update Magisk and Manager to 21.4
Hi,
rgd. OTA - which build variant (A or B) do you use?
Rgd. Kernel - I try to keep Kernel "current" by trying to apply, whatever sec. patches are available for 3.4, which is out of maintenance, but there still ARE thing being back ported.
For sure, you can omit kernel patches for a while by restoring the patched boot.img, but this leaves you more and more open to issues...
 

tramp20

Senior Member
Jan 15, 2012
733
138
Rosenheim
Hi,
rgd. OTA - which build variant (A or B) do you use?

Sorry, I am using A.
Thank you for explaining and ofc maintaining.

Today I patched the newest boot.img in the Magisk Manager 21.408 (with many bug fixes). Patching ended without error but after flashing this patched boot.img I lost root again as before.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    flashed the May build, tried to reboot to system - and again I ended up in a bootloop
    1. Before uninstalling Magisk you have to restore Magisk to the original name (unhide)!
    After uninstalling Magisk you have to flash the original boot.img from the new LOS ROM (this is very important because on our XPerias the uninstall routine does not remove all changes to ram disk):
    flashboot flash:raw boot boot.img

    2. Don't boot now!
    Instead do a "fastboot reboot" and press Vol down until the phone boots to TWRP.

    3. Install now in TWRP the patched Magisk_23.001p.zip.
    The patched Magisk installs correct, the Maggisk app (formerly Manager) is installed as a stub. Starting this stub downloads the full app.

    4. Then you have to config Magisk.

    5. Make a TWRP backup!

    Patching the boot.img from the Manager fails every time so you have to use this method.

    All Magisk updates can be installed without problems.

    Important: every ROM update destroys parts of the boot partition, you can boot normal but boot to TWRP does not work.
    So if the kernel has no important updates then after installing the update, restore the boot partition from #5.


    Patching the Magisk_xxx.zip:
    Please read my post in https://github.com/topjohnwu/Magisk/issues/3636
    Especially the patch from user bleckdeth (I can use it but I don't understand it).

    I can offer to download
    1. the actual patched boot_patch.sh
    2. the already patched Magisk app-debug_23001p.zip

    Link to 1: https://www.magentacloud.de/lnk/KqvysqQq
    Link to 2: https://www.magentacloud.de/lnk/jVvSM4Qu



    With this method you can flash Magisk on LOS 17.1 and 18.1.
    It seams that many XPeria are affected, topjohwu knows this problem since Jan 2021 :-(
    2
    @lm089:
    As stated here all magisk versions > 20.4 are causing trouble (either bootloops or a simply not installed magisk) after the rom update.
    So my recommandation would be to stick with 20.4 (with this release you would also be able to do the OTA updates furthermore) ..
    2
    I think it's not a problem of complexity. It's more a question of if we want to include it.
    If, then it would also only make sense for the microg builds.

    However, I don't really like the fact of including an arbitrary prebuilt apk.
    But in the end the microg builds are in @MSe1969's responsibility. So I'm just giving my opinion here.

    What about adding it on your own at first? Did you already try?
    Hello @115ek, correct, this would only make sense for the microG builds.

    @android666 Thanks for the interesting contribution, I will definitely have a look and do some testing.

    In fact, as this is a Stub, which requires to download the official AA app, which will then "update" the stub, it could be an interesting feature.

    Will get back on that, but no promises
    1
    Strange, same boot problems after updating as with the previous 2 verions: always reboots to trwp after installing from Ota. Will try the same as last time

    UPDATE:
    again tried to follow your hints from the March update (https://forum.xda-developers.com/t/...1-for-xperia-z1-compact.4007983/post-84656157), incl. full formatting of /data then restoring internal memory etc. Then, after the manual update of this full LOS version I again still end up in that bootloop that finally gets me back into twrp.
    I tried to uninstall Magisk 22.1 at various stages in my restore / update flow (first after an update, and then once again before the next update) , but that didn't help either.
    Wiped Dalvik multiple times, did multiple SELinux corrections + repair of /data and /system file systems, but I can't get the device to boot into the May update.
    Since I already did a complete fresh / clean install back in March I don't feel much like doing that once again.
    Instead, I'll stick with the April one for now.
    If you want to have some kind of log let me know.
    Hmm... Difficult to comment.
    Some thoughts:
    You use Magisk. Did you flash Magisk from recovery, so a "survival script" has been installed? Or did you use the "patch & flash boot.IMG" method? The former is meanwhile considered obsolete by Magisk docu.
    Could that survival script cause the trouble?
    Also, seems that most recent versions of Magisk in general cause trouble with our Z1c, there is an open issue right now.
    Also, when doing OTA update and using Magisk, it is key that the /data partition is accessible during the TWRP update execution, so never skip the decryption passphrase, in case your device is encrypted.
    Also, seems that for older devices not running on the latest Android main version, the newest Magisk versions introduce trouble, so may be wise to stick with an older version.
    Last, but not least, it may be an idea to temporarily deactivate all Magisk modules before the update. Also, do you maybe have an app requiring root, which auto-starts at boot? Also a potential troublemaker...
    I don't use Magisk myself, just some thoughts - maybe others have any idea?
    In my OP7T thread, a Magisk issue could be solved by using a version from Beta channel, but the OP7T has a crazy a/b partition layout, whilst the Z1c most probably requires an older version of Magisk...

    Edit: Yes, if you can produce a log, this could always help.
    1
    To be honest, I never heard of a "survival script" before. Any way to check whether tat still is there after uninstalling Magisk?

    How did I install Magisk? That's been years ago, back then flashing from recovery was the only way known to me, and since then I updated from the Magisk.apk every time there was an update. Right now I'm running the latest version (23), yesterday it was still V22.1
    What I call "survival script" is the stuff stored in /system/addon.d - please check, whether you find any file there with the name "magisk" in it.

    Normally, during an update, the entire /system partition is replaced. This however would mean, that everything, you have flashed via recovery onto the /system partition, like e.g. Gapps, would be lost after an update. Therefore, there is a mechanism within the flash process to execute the scripts in the /system/addon.d directory with a specific parameter, which first copies certain stuff and of course the scripts themselves into a temporary place, then the /system partition is replaced, and then the saved stuff is flashed again (by executing the same script again with a post-install parameter).

    Magisk normally does not aim at modifying the /system partition, but it also used to store such a script there, to simply re-patch /boot and restore Magisk. Later versions of Magisk work differently, and if for whatever reason such an old Magisk survival script still is present, it will do the things, which have been meaningful in an older version, but not now. Hence we have a potential trouble maker.

    You said you did a clean flash, but did you really wipe the /system partition, too? Or, did you maybe restore your old /system partition via TWRP, which would also restore /system/addon.d with those scripts ?
  • 19
    This thread aims at providing LineageOS 17.1 builds for the Sony Xperia Z1 compact with current security patches.
    You can consider this thread as a successor of our LineageOS 16.0 thread, where you may also find some useful information.
    This is the joint effort of 115ek and MSe1969 (contributions welcome).

    Code:
    #include <std_disclaimer.h>
    /*
    * Your warranty is now void.
    *
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
    *
    */

    We offer two build variants:
    A. Standard LineageOS 17.1 build
    This build flavor aims at providing LineageOS 17.1 "as is" with most recent security patches.
    If you want to install Google Apps (GApps) you have to use this build variant.
    GApps are optional, of course. The smaller the GApps package, the better (pico). If you want "Okay google" support you need at least nano.
    Just check the package comparison to see what fits your needs.

    B. Pre-installed microG build variant with additional security patches
    For the security/privacy focused (more details about below feature list, see here)
    • Pre-installed microG and F-Droid same as the LineageOS for microG project
    • Pre-installed AuroraStore
    • eSpeak TTS engine (FOSS TTS solution)
    • Bromite as default browser
    • Additional security hardening features listed below
    • Cloudflare as default fallback DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
    • Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
    • Increased max. password length of 64
    • No submission of IMSI/phone number to Google/Sony when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView
    • Extra control of sensor access for additionally installed user apps (Special access under app permissions)
    • Firewall (control internet access per app - under Trust)
    • Constified JNI method tables


    Status
    List template by AdrianDC
    Code:
    - Partitions (Data, Cache) : Ext4 and F2FS supported
    - Bluetooth : Ok
    - WiFi : Ok
    - WiFi Hotspot : Ok
    - RIL - Phone - Data : Ok
    - GPS : Ok
    - Camera : Ok
    - Camcorder : Ok
    - Lights : Ok
    - MicroSD : Ok
    - Accelerometer : Ok
    - Compass : Ok
    - Gyroscope : Ok
    - Touchscreen : Ok
    - FM Radio : Ok (mono)
    - ANT+ : Ok
    - Vibrator : Ok
    - Microphone : Ok
    - Audio & music : Ok
    - Bluetooth audio : Ok
    - MHL: broken
    - NFC : Ok
    - Kernel : Ok
    - Graphics : Ok
    - 3D Rendering : Ok
    - Clock : Ok
    - Offline Charging : Ok
    - USB : Ok
    - USB OTG : Ok
    - Encryption : Ok
    - SEPolicies : enforcing
    Limitations
    Following limitations are known:
    • NFC-HCE does not work (needed for example for google pay)
    • FM does not work in stereo mode (mono works fine, though)
    • MHL does not work
    • 5 GHz hotspot does not work (2.4 GHz hotspot works fine) (5 GHz option disabled with 2020-03-11 build as it isn't even available on stock)
    • GPS gets wrong time due to GPS week rollover since 3rd November 2019 (of importance when you record GPS tracks for example). fixed with 20200520 build
    • Using GApps AND encrypting the device may result in bootloops. More infos here.
    • Standard Trebuchet Launcher shows small artifacts in the fonts of app names in some situations.
    Download
    FAQ
    What recovery system to use?
    Please use this TWRP if you want to use OTA updates and/or encryption.

    What about root access?
    Root isn't included per default (except root over adb, but it's off by default).
    If you want to gain root access to your apps use magisk (everything > 20.4 is broken):
    ANT+ isn't working?
    You need the 2 apps:
    afterwards setting proper permissions is essential!
    1. Go to Apps & Notifications -> See All Apps
    2. Select 'ANT Radio Service'
    3. Select Permissions
    4. Select Additional permissions
    5. Slide switch to allow using of ANT hardware
    This refers to those instructions which worked for me :)
    I've got problems AND have magisk/exposed installed
    We won't support anything related to magisk/exposed/other heavily system modifying things.
    If you're encountering problems please make sure you're using a clean installation (at most gapps) to verify/reproduce the issue.

    Bugreports
    You'll find information about logging here.
    Please also note how you got the error or how it can be reproduced.
    Sources
    Credits
    • SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
    • NeoArian: also big thanks to him ;)
    • rcstar6696
    • SuperLamic
    • drakonizer
    • AdrianDC
    • munjeni: thanks for tips and tricks
    • nailyk: thanks for tips and tricks
    • All the other contributors on sony msm8974 platform
    • LineageOS team

    Installation instructions


    XDA:DevDB Information
    Lineage OS 17.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact

    Contributors

    115ek, MSe1969, SpiritCroc, NeoArian, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
    Source Code: https://github.com/lin17-microg/local_manifests

    ROM OS Version: Android 10
    ROM Kernel: Linux 3.4.x

    Version Information
    Status:
    Stable
    Stable Release Date: 2020-12-29

    Created 2019-11-22
    Last Updated 2021-05-12
    7
    New builds with March 2021 ASB patches available

    Hi all, new builds are available and offered as OTA updates via the updater app.

    A. Standard LineageOS 17.1 build
    • Security String 2021-03-05
    • System Webview on 88.0.4324.152

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-03-05
    • Bromite System webview updated to 88.0.4324.207
    • Bromite Browser updated to 88.0.4324.207
    • F-Droid 1.11
    • microG 0.2.18.204714

    @115ek - please update OP/Changelog

    Regards, M.
    7
    New builds with May 2021 ASB patches available

    Hi all,
    new builds are available and offered as OTA updates via the updater app.

    A. Standard LineageOS 17.1 build
    • Security String 2021-05-05
    • System Webview on 90.0.4430.82

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-05-05
    • Bromite System webview updated to 90.0.4430.204
    • Bromite Browser updated to 90.0.4430.204
    • microG upstreamed (but no new version)
    • Update: AuroraServices 1.1.1

    @115ek - please update OP/Changelog

    Regards, M.
    6
    Changelog

    12.05.2021

    • ASB Security string 2021-05-05
    • standard build only:
      • System Webview on 90.0.4430.82
    • microG build only:
      • Bromite System webview updated to 90.0.4430.204
      • Bromite Browser updated to 90.0.4430.204
      • microG upstreamed (but no new version)
      • Update: AuroraServices 1.1.1
    11.04.2021
    • ASB Security string 2021-04-05
    • standard build only:
      • System Webview on 89.0.4389.105
    • microG build only:
      • Bromite System webview updated to 90.0.4430.59
      • Bromite Browser updated to 90.0.4430.59
      • F-Droid 1.12
      • Update: AuroraStore 4.0.4 with AuroraServices 1.1.0
    09.03.2021
    • ASB Security string 2021-03-05
    • standard build only:
      • System Webview on 88.0.4324.152
    • microG build only:
      • Bromite System webview updated to 88.0.4324.207
      • Bromite Browser updated to 88.0.4324.207
      • F-Droid 1.11
      • microG 0.2.18.204714
    07.02.2021
    • ASB Security string 2021-02-05
    • misc. kernel patches
    • microG build only:
      • Bromite System webview updated to 88.0.4324.141
      • Bromite Browser updated to 88.0.4324.141
      • F-Droid 1.10-alpha-234
      • microG 0.2.17.204714-5
    14.01.2021
    • ASB Security string 2021-01-01
    • standard build only:
      • Kernel slightly upstreamed
      • System Webview: Fix of persistent histogram bug (eating space in some cases)
    • microG build only:
      • Bromite Webview on 87.0.4280.131
      • Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)
      • Updated F-Droid to 1.10-alpha1-212
    29.12.2020
    • introduce microG build variant (see this post or the OP for more information)
    18.12.2020
    • synced LineageOS sources (security patch level December 05, 2020)
    08.11.2020
    • synced LineageOS sources (security patch level November 05, 2020)
    • Seedvault is included officially now (inbuilt backup solution)
    07.10.2020
    • synced LineageOS sources (security patch level October 05, 2020)
    13.09.2020
    • synced LineageOS sources (security patch level September 05, 2020)
    17.08.2020
    • synced LineageOS sources (security patch level August 05, 2020)
    13.07.2020
    • synced LineageOS sources (security patch level July 05, 2020)
    16.06.2020
    • further GPS improvements
    • synced LineageOS sources (security patch level June 05, 2020)
    20.05.2020
    11.05.2020
    • synced LineageOS sources (security patch level May 05, 2020)
    16.04.2020
    • synced LineageOS sources (security patch level April 05, 2020)
    15.03.2020
    • fixed livedisplay
    • fixed OTA update URL
    11.03.2020
    • remove 5GHz hotspot option as it isn't available even on stock
    • start signing builds
    • enable OTA updates
    • synced LineageOS sources (security patch level March 05, 2020)
    28.02.2020
    • fixed sony bootlogo
    • fixed TWRP time bug
    25.02.2020
    • fixed buggy bootanimation
    11.02.2020
    • DRM fix (Netflix and co should work now)
    • synced LineageOS sources (security patch level February 05, 2020)
    01.02.2020
    • SE enforcing
    • synced LineageOS sources (security patch level January 01, 2020)
    22.11.2019
    • initial release
    5
    New build is up.
    17.08.2020
    • synced LineageOS sources (security patch level August 05, 2020)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone