• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

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

Search This thread

115ek

Senior Member
Jan 30, 2017
564
632
Hi there,
Is it normal behavior if there are always at least 2 cores online in idle doing absolutely nothing?
All other phones i had so far frequently turned cores on and off and in idle even 3 cores were offline.
Just curious if this is a bug or a feature.

Actually you should be able to control this behaviour via the performance settings. You can find it under settings>battery>battery saver and performance.
Can you check if it makes a difference for you? I haven't looked into it for a long time.

EDIT: In addition to the common (8974 platform) power settings there can also be further device specific settings. Like these. Maybe check what settings your m8 (which is also 8974 afaik) uses...
 

Attachments

  • Screenshot_20200930-203444_LineageOS_Settings.png
    Screenshot_20200930-203444_LineageOS_Settings.png
    72.6 KB · Views: 87
Last edited:
Actually you should be able to control this behaviour via the performance settings. You can find it under settings>battery>battery saver and performance.
Can you check if it makes a difference for you? I haven't looked into it for a long time.

EDIT: In addition to the common (8974 platform) power settings there can also be further device specific settings. Like these. Maybe check what settings your m8 (which is also 8974 afaik) uses...
Oh thanks for the quick reply,
It's actually set to balanced, changing it to efficient will limit the max. cpu clock just like it does on my oneplus 3t.
However 2 cores min still online.

On my HTC One M8 this won't take any effects at all

Will have a look at the sources and compare if i find any differences but probably tomorrow, since you have a build manifest it should be too easy to make my own build then and test :D
Maybe also taking a look at stock, haven't taken a look on it just prepared to unlock.
 

traegr

Member
Sep 26, 2020
13
0
He said he has custom rom already installed. All he has to do is download this one and install it along with gapps. I asked if he has sd card so i can write step by step guide for sd or for no sd

Hi, this might be outdated and not to hijack secc's post but I would love that step by step guide. :p

I want to revive my old Z1 Compact and will be installing this ROM (but no rooting) for the first time. (coming from stock ROM Android 5.1.1 Build 14.6.A.1.236). So far I have downloaded the adb and flashboot and also the TWRP recovery. Haven't unlocked the bootloader yet but that will be next step. I don't plan to do a backup because it's just stuffed with so much bloatware and the data (pictures, videos, etc) isn't all that important so I'm willing to wipe that all.

What do you mean by sd or no sd? I do have a micro sd where I stored my pictures (I'm not sure if they are apps but I don't think so?) but I also have a brand new, unused micro sd card? Could you maybe help me out? Thanks!!
 

115ek

Senior Member
Jan 30, 2017
564
632
Hi, this might be outdated and not to hijack secc's post but I would love that step by step guide. :p

I want to revive my old Z1 Compact and will be installing this ROM (but no rooting) for the first time. (coming from stock ROM Android 5.1.1 Build 14.6.A.1.236). So far I have downloaded the adb and flashboot and also the TWRP recovery. Haven't unlocked the bootloader yet but that will be next step. I don't plan to do a backup because it's just stuffed with so much bloatware and the data (pictures, videos, etc) isn't all that important so I'm willing to wipe that all.

What do you mean by sd or no sd? I do have a micro sd where I stored my pictures (I'm not sure if they are apps but I don't think so?) but I also have a brand new, unused micro sd card? Could you maybe help me out? Thanks!!

Check this older thread. There you'll find Installation Instructions in the OP.
I'd suggest you to use this TWRP.
If you want gapps (optional):
The smaller the better (pico package). If you want for example "Okay google" you need at least nano.
Just check https://github.com/opengapps/opengap...age-Comparison to see what fits your needs.

But the most important part is unlocking the bootloader. Everything else is pretty straight forward. There are enough guides and instructions. When in doubt - ask. ;)
 

traegr

Member
Sep 26, 2020
13
0
I'd suggest you to use this TWRP.
If you want gapps (optional):

But the most important part is unlocking the bootloader. Everything else is pretty straight forward. There are enough guides and instructions. When in doubt - ask. ;)

Thanks for the quick response!
The TWRP I should get is the 3.4.0-1 right?


Check this older thread. There you'll find Installation Instructions in the OP.

I did come across that thread before, but I guess I still couldn't take the plunge to unlock the bootloader haha (will def do it this weekend when I have all the time for it).

I guess with all the different tutorials from different timelines, I couldn't make up my mind whether I wanted/needed to do a TA Backup (which requires rooting - but I do want to use the phone daily and would require banking apps and can't risk them not working). On the other hand, do I really need the DRM keys? I don't use Spotify and my warranty is long over lol. Or are there other functions to the DRM? (Sorry, super newbie here, and possibly for the off-tangent question)
 

115ek

Senior Member
Jan 30, 2017
564
632
Thanks for the quick response!
The TWRP I should get is the 3.4.0-1 right?
Right.


I did come across that thread before, but I guess I still couldn't take the plunge to unlock the bootloader haha (will def do it this weekend when I have all the time for it).
Just follow the official sony instructions for unlocking the bootloader.

I guess with all the different tutorials from different timelines, I couldn't make up my mind whether I wanted/needed to do a TA Backup (which requires rooting - but I do want to use the phone daily and would require banking apps and can't risk them not working). On the other hand, do I really need the DRM keys? I don't use Spotify and my warranty is long over lol. Or are there other functions to the DRM? (Sorry, super newbie here, and possibly for the off-tangent question)
Forget about the DRM keys. It's mostly historical. Earlier, they were necessary to be able to use some special camera functionalities for example. But that isn't necessary anymore. Everything works without them.
You can use netflix and spotify just fine. Banking apps may require installation of gapps as some of them use some checks depending on playservices. But I haven't experiences with that. I'm not using banking apps. Just give it a try.
 

traegr

Member
Sep 26, 2020
13
0
Right.



Just follow the official sony instructions for unlocking the bootloader.
Right so I unlocked the bootloader and tried following all the instructions here and after flashing the twrp, it had an OKAY response with the finished time, I did the "fastboot boot TWRP.img" part the phone booted and got stuck on the SONY logo and then USB connection malfunctioned and windows doesn't recognize it and is now listed as Unknown USB Device. I tried updating the drivers but failed.

What have I done wrong, and how do I fix this? Thank you in advance!
Edit: Was it because I failed to insert a SD card?
 
Last edited:

115ek

Senior Member
Jan 30, 2017
564
632
Right so I unlocked the bootloader and tried following all the instructions here and after flashing the twrp, it had an OKAY response with the finished time, I did the "fastboot boot TWRP.img" part the phone booted and got stuck on the SONY logo and then USB connection malfunctioned and windows doesn't recognize it and is now listed as Unknown USB Device. I tried updating the drivers but failed.

What have I done wrong, and how do I fix this? Thank you in advance!
Edit: Was it because I failed to insert a SD card?

fastboot boot is not working with every recovery image. But why do actually need it?
If you flashed the recovery.img to the recovery partition you can just power off the phone and enter the recovery mode directly. Maybe check these instructions from my old TWRP thread.

It has nothing to do with sd cards ;)
 

traegr

Member
Sep 26, 2020
13
0
fastboot boot is not working with every recovery image. But why do actually need it?
If you flashed the recovery.img to the recovery partition you can just power off the phone and enter the recovery mode directly. Maybe check these instructions from my old TWRP thread.

It has nothing to do with sd cards ;)

I guess I was just trying to follow the instructions to a T ....

Well but the phone is now still stuck on the Sony logo and pressing the power button (or any other key combination) doesn't seem to shut it down
 

115ek

Senior Member
Jan 30, 2017
564
632
I guess I was just trying to follow the instructions to a T ....

Well but the phone is now still stuck on the Sony logo and pressing the power button (or any other key combination) doesn't seem to shut it down

Remove the battery :p

Joke aside: How long did you press the power button? Try holding Vol+ and Power for several seconds (until device turns off). At least that's what I remember darkly.
My dev device indeed has a open backside so I just pull the plug if something goes wrong. But you should achieve the same with a key combination.

Edit: several seconds could also mean 10 secs or so...
 

traegr

Member
Sep 26, 2020
13
0
Remove the battery :p

Joke aside: How long did you press the power button? Try holding Vol+ and Power for several seconds (until device turns off). At least that's what I remember darkly.
My dev device indeed has a open backside so I just pull the plug if something goes wrong. But you should achieve the same with a key combination.

Edit: several seconds could also mean 10 secs or so...

Found the hidden force shutdown button next to the sim insert - forgot all about it until I looked at the manual again. Your method(s) work too of course ;)
But good news! LineageOS17.1 is now successfully installed. Thank you for all your patience and in answering my questions.
:D
 

115ek

Senior Member
Jan 30, 2017
564
632
New build is up. It is also being shipped as ota update.
All october framework security patches were actually already applied before. So this is just a string update shown in the settings. More info here.
07.10.2020
  • synced LineageOS sources (security patch level October 05, 2020)
 

traegr

Member
Sep 26, 2020
13
0
It took me a couple of days to find out but I realize when my phone has been on deep sleep (wifi and mobile data disabled) my alarm clock rings two minutes later than the set time and hitting the snooze is in reference to that time instead of the original time. For example, alarm at 5.30, it rings at 5:32 and snooze would make it ring at 5:42 instead of 5:40 (as I'm used to with other alarms but who knows that might just be the new snooze function). It seems to only happen when the phone has been on sleep a long time bc when I tried reproducing it in the day and it rings on time. Is it a bug ?

Edit: Redundant question about the update build :p
 
Last edited:

115ek

Senior Member
Jan 30, 2017
564
632
It took me a couple of days to find out but I realize when my phone has been on deep sleep (wifi and mobile data disabled) my alarm clock rings two minutes later than the set time and hitting the snooze is in reference to that time instead of the original time. For example, alarm at 5.30, it rings at 5:32 and snooze would make it ring at 5:42 instead of 5:40 (as I'm used to with other alarms but who knows that might just be the new snooze function). It seems to only happen when the phone has been on sleep a long time bc when I tried reproducing it in the day and it rings on time. Is it a bug ?

Edit: Redundant question about the update build :p

I'm not aware of such a behaviour and I use the alarm function every morning (also with different performance settings).
I remember an issue in Lineage 16 when alarms fired at random times after they actually should. This was fixed by disabling the battery optimization for the alarm app. But it's disabled now by default as consequence.

I'll keep my eyes open the next days.
Is it the same delay every time?
 

traegr

Member
Sep 26, 2020
13
0
I'm not aware of such a behaviour and I use the alarm function every morning (also with different performance settings).
I remember an issue in Lineage 16 when alarms fired at random times after they actually should. This was fixed by disabling the battery optimization for the alarm app. But it's disabled now by default as consequence.

I'll keep my eyes open the next days.
Is it the same delay every time?

At first I thought I just slept through the first minute while it rang but the later snoozes seem to indicate that it 'moved'. I have to observe for a few more days and will report back.
 

traegr

Member
Sep 26, 2020
13
0
I'm not aware of such a behaviour and I use the alarm function every morning (also with different performance settings).
I remember an issue in Lineage 16 when alarms fired at random times after they actually should. This was fixed by disabling the battery optimization for the alarm app. But it's disabled now by default as consequence.

I'll keep my eyes open the next days.
Is it the same delay every time?

So my bad... the alarm has been ringing on time whether on deep sleep or otherwise so I don't think there's a bug. Though if the snooze is hit a few minutes later , the point of reference is no longer the original time but from the time the snooze is activated.
 

115ek

Senior Member
Jan 30, 2017
564
632
So my bad... the alarm has been ringing on time whether on deep sleep or otherwise so I don't think there's a bug. Though if the snooze is hit a few minutes later , the point of reference is no longer the original time but from the time the snooze is activated.

Good to hear it was your bad. :)

Concerning the snooze function: This totally makes sense. Think about what would happen in case your "snooze time" is shorter than you wait to hit the snooze button. You'll end up in an undefined state where the new alarm will be in the past. And that doesn't make sense to be honest.
Just a short example: Your default snooze time is 5 min, your alarm fires at 6:00. If the point of reference for the snooze would be the original alarm time now and you enable snoozing at 6:06 (because you weren't able to find your phone for 6 minutes or whatever...) the snooze alarm would be set to 6:05 which lies in the past. That's why the time of disabling the alarm / enabling the snooze is taken as reference.
 

traegr

Member
Sep 26, 2020
13
0
Good to hear it was your bad. :)

Concerning the snooze function: This totally makes sense. Think about what would happen in case your "snooze time" is shorter than you wait to hit the snooze button. You'll end up in an undefined state where the new alarm will be in the past. And that doesn't make sense to be honest.
Just a short example: Your default snooze time is 5 min, your alarm fires at 6:00. If the point of reference for the snooze would be the original alarm time now and you enable snoozing at 6:06 (because you weren't able to find your phone for 6 minutes or whatever...) the snooze alarm would be set to 6:05 which lies in the past. That's why the time of disabling the alarm / enabling the snooze is taken as reference.

Yes I agree with you that it makes way more sense. My old phone with stock ROM did it the other way, which meant less sleep if you hit the snooze a couple minutes before the 'snooze point' :eek:

Off-tangent, I saw that booting into recovery doesn't take me into the TWRP Recovery (I thought of making a backup now that I downloaded all the other apps I want) but the one from Lineage. It has 'factory reset' but no backup and/or restore.
 

115ek

Senior Member
Jan 30, 2017
564
632
Off-tangent, I saw that booting into recovery doesn't take me into the TWRP Recovery (I thought of making a backup now that I downloaded all the other apps I want) but the one from Lineage. It has 'factory reset' but no backup and/or restore.
Did you enable the update recovery switch in developer options?
That's the first thing coming to my mind...
When enabled, a system update will also replace the recovery.

EDIT: I'm going to include an inbuilt back-up solution for testing purposes soon...
 

Attachments

  • Screenshot_20201016-184617_Settings.png
    Screenshot_20201016-184617_Settings.png
    89.4 KB · Views: 85
Last edited:

Top Liked Posts

  • 1
    LineageOS 18.1 "microG Variant" Testbuild

    Hi all,

    for the 2nd build variant ("microG build"), a test build on LineageOS 18.1 is available here:

    It has the same features, as described in the OP for this 17.1 build variant, with the following additions:
    - AuroraDroid app replaces F-Droid app to access F-Droid repositories
    - Option to only use fingerprint unlock for apps and not for the device
    - Optional timeout for Bluetooth and WLAN connections
    - Some more hardening features ported from GrapheneOS

    @115ek and I plan to switch completely to LineageOS 18.1 for both build variants (variant A is already available for LineageOS 18.1, as you for sure know). Right now, this is still a test build, this means we truly appreciate any feedback (especially, if things don't work as expected). And there definitely will be an update with ASB patches for August for both 17.1 build variants.

    Installation instructions:
    • Make a backup in TWRP

    • If your device is not encrypted, it is up to you whether you want to do a clean or dirty flash
    • Do or don't do a factory reset and flash the test build

    • If your device is encrypted, encryption is not compatible! It will be necessary to format the /data partition.
    • If you need to format the /data partition, make sure to before:
      - Backup the 'Internal memory' of your device
      - Watch out for your TWRP backup files and copy them, if needed, to your local PC
    • Format /data, reboot into TWRP and flash the above test build build and boot into an empty system (don't restore anything,yet)
    • Encrypt the device now - it'll take not very long until the device reboots - wait for the reboot to finish
    • Restore now the Internal Memory and reboot to TWRP
    • if you want to "dirty-flash", restore the nandroid backup now and afterwards, still in TWRP,
    • Flash the above test build again
    Feedback appreciated - Thanks & regards, M.
  • 8
    New builds with July 2021 ASB patches available

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


    A. Standard LineageOS 17.1 build
    • Security String 2021-07-05
    • System Webview updated to 91.0.4472.101
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-07-05
    • Bromite System Webview and Browser updated to 91.0.4472.146
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
    • microG 0.2.21.212158-2
    • AuroraStore 4.0.7

    @115ek - please update OP/Changelog

    Regards, M.
    2
    Just installed it yesterday, everything is great. This ROM has LDAC support if anyone's wondering. Even Stock doesn't support LDAC. Thanks again.
    1
    • Kernel: Many sec. patches applied

    Awesome to see my CVE patcher used more!
    You might want to give it another run, I did a huge addition for 3.4 recently from @haggertk's 3.4 backports.

    You might also put the patches on an another branch, as patch output can change/improve overtime and it'll be easier to maintain that way.
    1
    I did already apply before Kevin's 3.4 backports from his LineageOS Samsung msm8974 branch and for the recent patching action with this ROM's Sony msm8974 kernel, I used the patches listed in here as this is also a msm8974 kernel in your 17.1 directory.
    Do you recommend to me to look further?

    And by the way, whilst I have the opportunity to communicate with you:
    As I prefer to truly apply the commits to my/our kernel forks, I have noticed, that few of your patches do not contain commit messages. For some of them, I found them and applied accordingly, but at least for that one I did not manage to find it.
    Do you have the commit message(s) handy?
    And if not - would you like me to make a pull request for those patches, where I was able to identify the originating upstream commit?

    > I used the patches listed in here

    The program is intended to be used to check which patches apply.

    > I have noticed, that few of your patches do not contain commit messages.

    Many of them are plain diffs due to various reasons, eg. Gerrit only gives base64'ed plain diff
    I'm happy to accept patches that replace diffs with matching patches.

    > but at least for that one

    That is https://lkml.org/lkml/2017/10/2/352

    --

    In case it isn't clear, patches are added to this file first https://raw.githubusercontent.com/Divested-Mobile/Kernel_Patches/master/Kernel_CVE_Patch_List.txt

    then downloaded with the program https://github.com/Divested-Mobile/CVE_Checker

    and also checked using the program

    you can use https://github.com/Divested-Mobile/CVE_Checker/blob/master/mk_dir_from_list.sh to convert the program output to a directory of the patches

    you can download prebuilts of the program here https://gitlab.com/divested-mobile/cve_checker/-/jobs/artifacts/master/browse?job=build

    furthermore a large amount of the patches in the list are extracted using this tool https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec, you can add any kernel you want to the script config and extract matching patches from any given repository, and propagate that back into the final patch list


    edit: here is example output https://github.com/SkewedZeppelin/android_kernel_sony_msm8974/commits/fixup it contains an additional ~60 patches
    1
    LineageOS 18.1 "microG Variant" Testbuild

    Hi all,

    for the 2nd build variant ("microG build"), a test build on LineageOS 18.1 is available here:

    It has the same features, as described in the OP for this 17.1 build variant, with the following additions:
    - AuroraDroid app replaces F-Droid app to access F-Droid repositories
    - Option to only use fingerprint unlock for apps and not for the device
    - Optional timeout for Bluetooth and WLAN connections
    - Some more hardening features ported from GrapheneOS

    @115ek and I plan to switch completely to LineageOS 18.1 for both build variants (variant A is already available for LineageOS 18.1, as you for sure know). Right now, this is still a test build, this means we truly appreciate any feedback (especially, if things don't work as expected). And there definitely will be an update with ASB patches for August for both 17.1 build variants.

    Installation instructions:
    • Make a backup in TWRP

    • If your device is not encrypted, it is up to you whether you want to do a clean or dirty flash
    • Do or don't do a factory reset and flash the test build

    • If your device is encrypted, encryption is not compatible! It will be necessary to format the /data partition.
    • If you need to format the /data partition, make sure to before:
      - Backup the 'Internal memory' of your device
      - Watch out for your TWRP backup files and copy them, if needed, to your local PC
    • Format /data, reboot into TWRP and flash the above test build build and boot into an empty system (don't restore anything,yet)
    • Encrypt the device now - it'll take not very long until the device reboots - wait for the reboot to finish
    • Restore now the Internal Memory and reboot to TWRP
    • if you want to "dirty-flash", restore the nandroid backup now and afterwards, still in TWRP,
    • Flash the above test build again
    Feedback appreciated - Thanks & regards, M.
  • 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-07-10
    8
    New builds with July 2021 ASB patches available

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


    A. Standard LineageOS 17.1 build
    • Security String 2021-07-05
    • System Webview updated to 91.0.4472.101
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-07-05
    • Bromite System Webview and Browser updated to 91.0.4472.146
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
    • microG 0.2.21.212158-2
    • AuroraStore 4.0.7

    @115ek - please update OP/Changelog

    Regards, M.
    8
    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.
    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.
    6
    Changelog

    10.07.2021

    • ASB Security string 2021-07-05
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
    • standard build only:
      • System Webview on 91.0.4472.101
    • microG build only:
      • Bromite System Webview and Browser updated to 91.0.4472.146
      • microG 0.2.21.212158-2
      • AuroraStore 4.0.7
    14.06.2021
    • ASB Security string 2021-06-05
    • A few kernel patches
    • microG build only:
      • Bromite System Webview and Browser updated to 91.0.4472.102
      • Upstreamed microG (0.2.19211515-9)
    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