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

[OFFICIAL] LineageOS 18.1 for Xperia Z3 Compact

Search This thread

wtor68

Member
Nov 4, 2017
19
7
It's been a while since you asked - have you resoved your issue?
I just updated from 17.1 to 18.1 (even without wiping data), and although (or because???) I never used FM Radio before, I got it working without a complaint (the headphone socket seems to be a bit worn though)...
I installed 18.1 from scratch. The radio was not working after that. But it comes back to live with an later update. I'm currently some weeks behind, but with the latest update i had done from 19.10.2021 it worked for me.
 
  • Like
Reactions: steve8x8

L.Lmar

Member
Aug 4, 2016
27
13
I have tested magisk 23012 with app v23.0 and it's working

Probably due to included debug information and lack of code optimization
Hi, could you kindly explain me what are the steps you follow to install magisk on Sony Z3C with LOS 18.1 (now I'm on "lineage-18.1-20211130-nightly-z3c-signed.zip") and apply the "canary build" you mentioned.
Thank you in advance.
 

L.Lmar

Member
Aug 4, 2016
27
13
Hi, could you kindly explain me what are the steps you follow to install magisk on Sony Z3C with LOS 18.1 (now I'm on "lineage-18.1-20211130-nightly-z3c-signed.zip") and apply the "canary build" you mentioned.
Thank you in advance.
Install as usual apk or rename to .zip and flash via recovery (before that remove release magisk if installed)
It should be noted that in the current versions of the Manager app they have removed MagiskHide and modules repository
 
Last edited:
  • Like
Reactions: fravit
Hello,

i'm also facing that issue since long time. We have two z3c devices, one with 17.1 and one with 18.1. Both show this issue. It happen randomly. Sometimes two times a day and sometimes only one time in tree weeks. After wifi is stuck, it cannot be disabled and as you said a following normal reboot stucks forever. In that case only a hard reboot by button or a 'reboot -p' on a local shell is possible to reboot the device. I have no solution for that, unfortunately... may be @NeoArian has some idea on that.

Many thanks
Good to hear i'm not the only one.
Well i submitted the bug to gitlab where Arian responded and said he couldn't find anything helpful in my provided log.
I don't know how to debug this issue nor how to fix it.
Have minimal experience in building ROMs but that's basically all.
It's quite complex to mess around and develop so i have much respect for everyone who's doing this work in his free time for next to nothing.
But unfortunately without an error message in the log, there's little to nothing he could do for us since this issue also happens randomly.
Also haven't touched my linux enviroment in a long time... :D
 
lol there we go again wifi crashing the hell out
photo5294289552103552264.jpg

Tried getting logs but again nothing really useful.
Logcat just goes crazy...
No idea how to debug this issue, it just goes crazy.
Got last_ksmg before and after force-reboot but still can´t find anything.
Looks like normal linux bootup...
Dunno what triggered it, was listening to some music via bluetooth, not even streaming via wifi.
 

Attachments

  • 2021-12-07-03-24-57.txt
    140 KB · Views: 8

morkr

New member
Dec 13, 2021
2
0
Hi,
I recently updated my z3c from 17.1 to 18.1 and have the seemingly common problem of the wakelock to which a solution is shown here:
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.

I have two questions:
1. Is that going to be included into the official builds anytime soon?
2. Even if yes to 1.: could I build my own version with the above change and install it without losing my data, settings, apps?
i.e. is it possible to easily switch between self-built and official?
If yes, update via adb sideload through the recovery (LOS recovery atm) or another way?

I have zero experience building android roms, but am working on linux (experiments included) for years and am pretty confident I could build LOS for myself, if neccessary.

Any answer is appreciated!

Regards
 

L.Lmar

Member
Aug 4, 2016
27
13
Hi,
I recently updated my z3c from 17.1 to 18.1 and have the seemingly common problem of the wakelock to which a solution is shown here:


I have two questions:
1. Is that going to be included into the official builds anytime soon?
2. Even if yes to 1.: could I build my own version with the above change and install it without losing my data, settings, apps?
i.e. is it possible to easily switch between self-built and official?
If yes, update via adb sideload through the recovery (LOS recovery atm) or another way?

I have zero experience building android roms, but am working on linux (experiments included) for years and am pretty confident I could build LOS for myself, if neccessary.

Any answer is appreciated!

Regards
Properties in /system/build.prop are editable and applied at boot. No need to rebuild the system.
For persistent setting it is enough to execute
Code:
adb shell setprop persist.ro.qti.sensors.smd false
 

morkr

New member
Dec 13, 2021
2
0
Properties in /system/build.prop are editable and applied at boot. No need to rebuild the system.
For persistent setting it is enough to execute
Code:
adb shell setprop persist.ro.qti.sensors.smd false
Wow, cool!
That's easier than I imagined!
I will try that out when I have a moment.
Thanks for the lesson :)
 
Good evening.

i think i finally found a way to reproduce the odd wifi bug:
After messing around a little more, i just noticed i could stream YT music for like forever when using a wired headset connection but after using bluetooth for audio streaming, it was a matter of 10 to 30 minutes until i lost the internet connection and wifi stopped working. (Tried it a few times to verify)

I just got a log from the beginning until the end, there are some wifi related messages, maybe this time there´s something useful.
So @NeoArian if you feel bored enough, maybe you want to have a look into it :)

Wish you all a great time and happy new year
 

Attachments

  • log.zip
    591.3 KB · Views: 5

NeoArian

Recognized Developer
Nov 25, 2017
1,277
2,916
Sony Xperia Z2
Sony Xperia Z3 Compact
Hi,
I recently updated my z3c from 17.1 to 18.1 and have the seemingly common problem of the wakelock to which a solution is shown here:


I have two questions:
1. Is that going to be included into the official builds anytime soon?
2. Even if yes to 1.: could I build my own version with the above change and install it without losing my data, settings, apps?
i.e. is it possible to easily switch between self-built and official?
If yes, update via adb sideload through the recovery (LOS recovery atm) or another way?

I have zero experience building android roms, but am working on linux (experiments included) for years and am pretty confident I could build LOS for myself, if neccessary.

Any answer is appreciated!

Regards
1. Yes, we might merge it soon.
2. Yes, you can easily build the ROM yourself, instructions can be found here: https://wiki.lineageos.org/devices/z3c/build
To switch between the self built and official one, you need to note that the official builds are signed. More information regarding migration can be found here: https://wiki.lineageos.org/signing_builds
After taking care of the different signing keys you can just use adb sideload in lineage recovery. You might get a warning about the signature and you need to press ok during installation to proceed installing the new build.
 

L.Lmar

Member
Aug 4, 2016
27
13
@NeoArian
OTA system updates do not preserve /system/addon.d scripts, including Magisk survival script, which prevents it from being reinstalled on subsequent updates
 

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    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
    3
    Good news from Magisk developers. They fixed the issue where magisk 23 cannot be installed or did not survive system update. Latest canary build 👈
    3
    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
    3
    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.
    2
    I did a clean installation of "lineage-18.1-20210727-nightly-z3c-signed.zip" + "MindTheGapps-11.0.0-arm-20210412_124103.zip"
    (using, as recovery, lineage-18.1-20210727-recovery-z3c.img) -> OK!
    Then I tried to install Magisk following crackyh suggestion of modifying
    boot_patch.sh: the risult was unsuccessfull.

    I tried all the combinations of TWRP (twrp-3.3.1-z3c-20200212.img) and LOS 18.1 Recovery with Magisk 20.4, 22.1 and 23.0
    I didn't succeed.
    In synthesys, the risults was identical to that described by wtor68 in this post .

    wtor68 suggested here of fixing the Magisk apk "by zipalign / apksigner".
    As I'm not able to use those 2 commands in ADB Studio, could someone (wtor68 ?) help me to solve ?
    Is it possible to attache Magiskxxxx.apk file after the "zipalign /apksigner" operations?

    Thanks a lot in advance!
    I've done this on an linux ubuntu system, but it should be also possible on windows. These are the steps:

    # install packages (on windows download them anywhere): apt install zipalign apksigner # create a keystore: keytool -genkey -v -keystore my-release-key.keystore -alias my_key -keyalg RSA -keysize 2048 -validity 10000 # download Magisk and patch the file, then: zipalign -p -f -v 4 Magisk-v23.0.apk Magisk-v23.0_mod.apk # optional, verify: zipalign -c -v 4 Magisk-v23.0_mod.apk apksigner sign --ks my-release-key.keystore Magisk-v23.0_mod.apk

    Then you can install the apk directly or rename it to zip and install by twrp.