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

[OFFICIAL] LineageOS 18.1 for Xperia Z3 Compact

Search This thread

NeoArian

Recognized Developer
Nov 25, 2017
1,271
2,899
Sony Xperia Z2
Sony Xperia Z3 Compact
2okPze5.png


Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.

Features
Individuality

Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.

Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.

More detailed instructions at:
Install LineageOS on z3c

Downloads
Download LineageOS 18.1 for Xperia Z3 Compact.
If you prefer TWRP over Lineage recovery, you can get it here.
Recommended Google Apps can be found here.

Installation
Please follow the instructions here.

Upgrade from LineageOS 17.1
Please follow the instructions here.
Note that you might NOT necessarily need to wipe your data if your data is not encrypted and you do not have a screen lock set!

Source code
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

The device specific source code can be found in the LineageOS Github repo.
Z3 Compact device tree
Sony Shinano common device tree
Sony MSM8974 common device tree
Sony MSM8974 kernel
The used defconfig is lineageos_shinano_aries_defconfig.

Changelog:
Changes for z3c

Bug reports:
How to submit a bug report
LineageOS GitLab

Donate to support development:
Donate via PayPal to NeoArian
Donate via PayPal to LineageOS
 
Last edited:

crackyh

Member
Mar 4, 2018
6
2
Hi,

Very Thank you for your work :)

With the 17.1, I initially used Magisk 20.4. It was OK.

With the 18.1, I'm trying to install Magisk 23.0, but for now it's KO with me (I'm android newbie ;)):
- Magisk-23.0.zip install with TWRP: OK
- Magisk-23.0.apk install: OK
- but Magisk app tell me that Magisk is not installed
- I try to patch boot img..., same
Some tips for Magisk and z3c / android 11?

Best regards
 
Last edited:

Klbgr

Senior Member
Hi,

Very Thank you for your work :)

With the 17.1, I initially used Magisk 20.4. It was OK.

With the 18.1, I'm trying to install Magisk 23.0, but for now it's KO with me (I'm android newbie ;)):
- Magisk-23.0.zip install with TWRP: OK
- Magisk-23.0.apk install: OK
- but Magisk app tell me that Magisk is not installed
- I try to patch boot img..., same
Some tips for Magisk and z3c / android 11?

Best regards
This worked for me
 

L.Lmar

Member
Aug 4, 2016
15
5
I have tried upgrading from 17.1 without wiping data without success. Loading reached the wallpaper, then boot animation started again
 

NeoArian

Recognized Developer
Nov 25, 2017
1,271
2,899
Sony Xperia Z2
Sony Xperia Z3 Compact
I have tried upgrading from 17.1 without wiping data without success. Loading reached the wallpaper, then boot animation started again

Everything is looking good except I can't unlock the screen for some reason. I use my old pattern but instead of unlocking it throws me right back to the unlock screen again. Any ideas?
In this case you should wipe data. There might be issues if you have used a pattern. I have tested an upgrade from 17.1 to 18.1 without a pattern/pin set.
The reason for this is that support for the legacy credential hash support was deprecated and we had to remove the legacy hardware keystore.
If you want to keep your data, you could try to remove the pattern on 17.1 and do the upgrade, but i can't guarantee that it will work.
Sorry for the misleading comment in the OP.
 
  • Like
Reactions: Mr.Tom_Tom

mcsly100

Member
Mar 25, 2021
8
0
In this case you should wipe data. There might be issues if you have used a pattern. I have tested an upgrade from 17.1 to 18.1 without a pattern/pin set.
The reason for this is that support for the legacy credential hash support was deprecated and we had to remove the legacy hardware keystore.
If you want to keep your data, you could try to remove the pattern on 17.1 and do the upgrade, but i can't guarantee that it will work.
Sorry for the misleading comment in the OP.
Thanks for the clarification. All good now.
 

t.Lancer

Senior Member
Jun 14, 2010
64
6
Just wanted to give my thanks for supporting this phone. Although I have moved to the XZ2c. the Z3c still acts as my backup.

thanks again!
 

Samare

Member
Nov 6, 2014
43
19
I've changed my build.prop

Code:
ro.qti.sensors.smd=true
to
Code:
ro.qti.sensors.smd=false
-> problem solved.

By the way, I checked an old build.prop from LineageOS 17.1 and it used to be disabled, which explains why this problem is linked to 18.1.
 

rm43115

Senior Member
May 13, 2017
158
45
In this case you should wipe data. There might be issues if you have used a pattern. I have tested an upgrade from 17.1 to 18.1 without a pattern/pin set.
The reason for this is that support for the legacy credential hash support was deprecated and we had to remove the legacy hardware keystore.
If you want to keep your data, you could try to remove the pattern on 17.1 and do the upgrade, but i can't guarantee that it will work.
Sorry for the misleading comment in the OP.
I tried the update without wiping anything - it ended in a boot loop.
Any change for upgrading without wiping data partition?
 

Samare

Member
Nov 6, 2014
43
19
Is there a reason why GPS doesn't work for any App / Tracker while Screen is turned off?

I did a short test with FitoTrack without any problem. I'm guessing you made sure to enable the location permission in always mode?

I tried the update without wiping anything - it ended in a boot loop.
Any change for upgrading without wiping data partition?

Same here.
You can either try the integrated Seedvault backup (enable the backup apps option) or use the Migrate (requires root) or OAndBackupX (not tried) app.
 
Last edited:
  • Like
Reactions: NeoArian

Top Liked Posts

  • 1
    If you have successfully flashed the recovery image (with your `fastboot flash recovery lineage-18.1-20210921-recovery-z3c.img`, then you should be able to boot into recovery as follows:
    - disconnect all cables and wait until any illuminates LEDs go out
    - press and hold the Volume down key
    - press the Power key unti you hear a buzz
    The phone shoudl then reboot into recovery

    That did the trick. Thank you very much!
  • 1
    Good evening,

    i found an issue in this rom:
    There's something wrong with the thermal engine and/or hotplug.

    If the device heats up (while playing a game etc.) the thermal engine will eventually disable two cpu cores.
    That's fine but it seems like those two cores will be permanently offline until a reboot, even after the device cooled down.
    Usually the device would use all four cores again but it simply doesn't.
    It runs at two cores effectively until a reboot.

    I also noticed, if the device is running for a long time in standby, one core eventually gets disabled permanently and it's running with only 3 cores all the time.
    Hotplug/msmdecision simply breaks and do no longer work correctly.

    I also wasn't able to enable those cores manually.


    The same behavior occurs when messing around with the battery profiles.
    Cores disabled by the power saving mode will stay offline even after changing the profile back to normal.

    I opened a bugreport on gitlab for lineageos but as i know, the lineage team doesn't really care and probably never read any reports and that's why I'm posting this issue here again.
    Hopefully our maintainer takes notice of this :)
    Just for you information, we do read the issues on gitlab. However i'm having exams this month and hence i'm pretty busy. Apart from that it doesn't seem like it's true what you mention, the cores get enabled just fine again.
    1
    Just for you information, we do read the issues on gitlab. However i'm having exams this month and hence i'm pretty busy. Apart from that it doesn't seem like it's true what you mention, the cores get enabled just fine again.
    Hi,
    thanks for your reply.
    I´m really sorry about this but in my experience bugreports on gitlab don´t get much attention at all.
    I reported a few there and waited for like 6 months and more and still got no response.
    Since no mod seemed kind enough to assign the report to anyone, i assume the maintainer didn´t even take notice of it, so after months i got in touch via dm and to my surprise he actually responded nicely and fixed the
    issue in like no time.

    Not 100% sure how moderation is managed at gitlab but for me it pretty much seems like no one reads reports or simply ignore them, also nobody assign to the maintainers , comment or reject reports and due to this maintainer never take notice of issues.
    I experienced this with many different devices already.
    Also with flooded threads on xda, there´s usually no chance getting in contact.
    And that´s especially the case with older devices where developers won´t look around frequently and don´t test everything which is totally fine btw. :)


    Well about this case i´m not quite sure but for me there´s definitely an issue with those cpu cores after intensive usage and heat up.
    Not sure if a logcat may help in this case, haven´t seen any errors.
    So if there´s anything i can do, please let me know.
    I´m not really skilled at debugging but i have a ready to go build enviroment and can apply patches in order to build and test changes.

    BUT the most important now, take your time with your exams and good luck ;)
    1
    Hi, I faced a similar bootloop with the latest LOS 18.1 20210907, I hadn't with previous updates like others had.
    I flashed the LOS and magisk-v22.1_mod_sony.zip (I cant figure out how to modify the current version, so found this on github).
    After endless loops and phone getting hot I forced it off. Then a few hours later, I thought as I use gapps,
    I'd reflash gapps pico too. It booted fine and out of bootloop.
    Thought I'd share, perhaps a solution for some IF similar and in bootloop.

    Now I just to get my head around latest magisk, unless someone could perhaps upload a premodded version of latest magisk? Thank you
    Hi, the same happened to me.
    I tried to update to LOS18.1-20210831-nightly-z3c-signed.zip starting from LOS18.1-20210727... + MindTheGapps-11.0.0-arm-20210412_124103.zip + Magisk-v23.0.apk.
    Using as recovery twrp-3.3.1-z3c-20200212.img the update failed (bootloop); the same with recovery lineage-18.1-20210727-recovery-z3c.img.
    The only way to solve, it was to "format /system", and then install from LOS recovery LOS and Gapps (loosing a lot of time to set apps and data)
    I didn't install Magisk anymore, waiting for solution and/or suggestion to solve the bootloop problem.
    Moreover, I have a question about updating LOS in the correct way: what recovery is it better to use?
    a) TWRP
    b) LOS recovery and wich ? the last (corresponding to the new version ) or that corresponding to the version to be updated?
    Thanks!
    [To install Magisk you could give a look to this post.]
    1
    EDIT:
    nvm flashed boot.img from an old build and it´s now showing the charging animation!
    So in lineage-18.1-20210907 offline charging seems broken...
    Don´t let the battery drain to 0% lol 😅
    1
    Hello everybody
    I'm sorry but has anyone the lastest los 17.1 build to share? I prefer to keep lastest 17.1 available for a while before considering to move to 18.1
    Thank you
  • 12
    2okPze5.png


    Introduction
    LineageOS, an open-source Android distribution, is available for several devices,
    with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
    Join us and breathe new life in your device, be it old or new.
    If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.

    Features
    Individuality

    Customization is paramount to productivity.
    That’s why LineageOS promises to push for user personalization and preference.
    Everyone is unique and your device should be too.
    Security
    Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
    Trust will help you understand the security of your device and warn you about possible threats.
    We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
    And to make your device more secure, lock everything behind an enhanced lock screen.
    Longevity
    LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.

    Installation:
    If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below.
    If you are coming from stock or other ROMs, you need to make a factory reset.
    As always, make sure to backup before installing this ROM.

    More detailed instructions at:
    Install LineageOS on z3c

    Downloads
    Download LineageOS 18.1 for Xperia Z3 Compact.
    If you prefer TWRP over Lineage recovery, you can get it here.
    Recommended Google Apps can be found here.

    Installation
    Please follow the instructions here.

    Upgrade from LineageOS 17.1
    Please follow the instructions here.
    Note that you might NOT necessarily need to wipe your data if your data is not encrypted and you do not have a screen lock set!

    Source code
    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.

    The device specific source code can be found in the LineageOS Github repo.
    Z3 Compact device tree
    Sony Shinano common device tree
    Sony MSM8974 common device tree
    Sony MSM8974 kernel
    The used defconfig is lineageos_shinano_aries_defconfig.

    Changelog:
    Changes for z3c

    Bug reports:
    How to submit a bug report
    LineageOS GitLab

    Donate to support development:
    Donate via PayPal to NeoArian
    Donate via PayPal to LineageOS
    2
    Thanks again NeoArian for supporting the Z3 Compact! :)
    I've installed LineageOS 18.1 and everything is fine except...
    a kernel wakelock: sensor_SMD 2000000000
    Because of that, deep sleep isn't what it should be.

    It seems that the Z3 Compact isn't the only phone with that problem: msm8937-common: Disable the Significant Motion Detector

    Screenshot_20210724-214751_BBS_1.png


    Screenshot_20210724-214808_BBS_1.png
    2
    I've changed my build.prop

    Code:
    ro.qti.sensors.smd=true
    to
    Code:
    ro.qti.sensors.smd=false
    -> problem solved.

    By the way, I checked an old build.prop from LineageOS 17.1 and it used to be disabled, which explains why this problem is linked to 18.1.
    1
    Thank you @NeoArian for your awesome work!
    Just a question: now that 18.1 is out, will there be any more builds for 17.1 (e.g. security patches)? I'm asking because I'm going to wait some time before doing the move to 18.1.
    No, there won't be further updates of lineage-17.1.
    1
    I have tried upgrading from 17.1 without wiping data without success. Loading reached the wallpaper, then boot animation started again

    Everything is looking good except I can't unlock the screen for some reason. I use my old pattern but instead of unlocking it throws me right back to the unlock screen again. Any ideas?
    In this case you should wipe data. There might be issues if you have used a pattern. I have tested an upgrade from 17.1 to 18.1 without a pattern/pin set.
    The reason for this is that support for the legacy credential hash support was deprecated and we had to remove the legacy hardware keystore.
    If you want to keep your data, you could try to remove the pattern on 17.1 and do the upgrade, but i can't guarantee that it will work.
    Sorry for the misleading comment in the OP.