[OFFICIAL] LineageOS 17.1 for z3c

Search This thread

schnuff*1

Senior Member
Jan 29, 2013
169
38
I'm coming from carbon rom 8.1.0, flashed this clean with gapps nano, but back camera is not working. Also from time to time the device freezes and no messages coming in anymore. Only a hardreset helps.
The version is the latest from november. Is it a buggy version or is it my only error?
Thanks for the help!
 

crott

Member
Jul 25, 2014
21
2
Wroclaw
www.netcreate.pl
I have just tried to encrypt my device with a pin and it worked as expected.
Could you maybe try again or get some logs so that we can look further into it?
Also, as Serf95 told you, it's worth a try to flash the latest stock firmware again before trying it.

We are looking into the screen lock issue. Was the GPS behaviour better from builds which are older then a week? We have merged some GPS patches.

NeoArian I've bought second Z3C because I use first as daily driver without GAPPS. But apparently I need apps that requires GAPPS.
Second z3c I installed exactly same, exactly same issue: after encrypting indefinite LOS animation at boot.
Without GAPPS it works fine, but with GAPPS it's not working.
This time I used current versions: lineage-17.1-20201110-nightly-z3c-signed, lineage-17.1-20201110-recovery-z3c and open_gapps-arm-10.0-nano-20201111.

Any suggestions what logs (and how please any/tutorials links) could I get to shed some light on this issue?

I went also this road but I'm stuck another errors I can't resolve:
z3c:/ # tune2fs -l /dev/block/mmcblk0p25
tune2fs 1.43.3 (04-Sep-2016)
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p25
1|z3c:/ # e2fsck -f /dev/block/mmcblk0p25
e2fsck 1.43.3 (04-Sep-2016)
/dev/block/mmcblk0p25 is in use.
e2fsck: Cannot continue, aborting.

Thanks.
 
Last edited:

pawloland

Senior Member
Jan 23, 2019
178
67
Hi everyone!
About back camera problem - from my experience if is not working, in order to fix it you have to flash latest firmware using Emma and then flash recovery + rom.

And going to the main point of this post - MMSes are not working.
I tested latest build of LOS 17.1 (lineage-17.1-20201110-nightly-z3c-signed.zip) to check if it will resolve the issue (it didn't).
I decided to do the whole procedure from the grounds up, to make sure MMSes aren't working not because of my fault.

- I flashed latest firmware using emma.
- I tried sending and receiving MMSes on stock MM (success).
- I flashed twrp-3.3.1-z3c-20200212.img recovery.
- I flashed just lineage-17.1-20201110-nightly-z3c-signed.zip, without magisk and without gapps.
- I booted to system, turned on mobile data and tried to send MMS (failed to do so).
- I tried to receive MMS (also failed to do so, I only get message, that there is MMS available for download but it can't be downloaded. I is downloading forever until it stops and says that the message can't be downloaded.)

At this point I was sure it isn't my fault. I checked APN settings and took screenshots of the configuration (didn't change anything, just took ss).

I remembered that MMSes had been working before, with custom ROM on my device. I checked older versions of LOS 17.1 but they have the same issue.
I have one of an old UNOFFICIAL 16.0 build from you @NeoArian, saved on my computer. I gave it a try.
- wiped system, data, cache
- flashed twrp recommended for LOS 16.0 - twrp-3.3.1-z3c-20200212.img
- flashed lineage-16.0-20190510-UNOFFICIAL-z3c.zip, without magisk and without gapps
- booted to system, turned on mobile data
- tried sending and receiving MMSes and ........... IT WORKED ON A FIRST TRY

I checked APN setting on LOS 16 to compare them with configuration from 17.1 and they were exactly the same.
Now I am sure that MMSes are broken on LOS 17.1. Could you @NeoArian give it a look?
They were working on your unofficial builds of LOS 16, so you may know or remember how to fix it :fingers-crossed:.

Thanks in advanced.
 

tomKater

Member
Jul 29, 2014
30
5
Huawei MediaPad M5 Lite
I'm coming from carbon rom 8.1.0, flashed this clean with gapps nano, but back camera is not working. Also from time to time the device freezes and no messages coming in anymore. Only a hardreset helps.
The version is the latest from november. Is it a buggy version or is it my only error?
Thanks for the help!

If I can help too : about the camera stock issue : I encountered this problem too when I flashed my Z3C from scratch (while previously I have used this build with no problem). I had to flash several times (and immediately testing the camera) before stock camera works again. No idea why.

Maybe this can help.
 

pawloland

Senior Member
Jan 23, 2019
178
67
Hi everyone!
About back camera problem - from my experience if is not working, in order to fix it you have to flash latest firmware using Emma and then flash recovery + rom.

And going to the main point of this post - MMSes are not working.
I tested latest build of LOS 17.1 (lineage-17.1-20201110-nightly-z3c-signed.zip) to check if it will resolve the issue (it didn't).
I decided to do the whole procedure from the grounds up, to make sure MMSes aren't working not because of my fault.

- I flashed latest firmware using emma.
- I tried sending and receiving MMSes on stock MM (success).
- I flashed twrp-3.3.1-z3c-20200212.img recovery.
- I flashed just lineage-17.1-20201110-nightly-z3c-signed.zip, without magisk and without gapps.
- I booted to system, turned on mobile data and tried to send MMS (failed to do so).
- I tried to receive MMS (also failed to do so, I only get message, that there is MMS available for download but it can't be downloaded. I is downloading forever until it stops and says that the message can't be downloaded.)

At this point I was sure it isn't my fault. I checked APN settings and took screenshots of the configuration (didn't change anything, just took ss).

I remembered that MMSes had been working before, with custom ROM on my device. I checked older versions of LOS 17.1 but they have the same issue.
I have one of an old UNOFFICIAL 16.0 build from you @NeoArian, saved on my computer. I gave it a try.
- wiped system, data, cache
- flashed twrp recommended for LOS 16.0 - twrp-3.3.1-z3c-20200212.img
- flashed lineage-16.0-20190510-UNOFFICIAL-z3c.zip, without magisk and without gapps
- booted to system, turned on mobile data
- tried sending and receiving MMSes and ........... IT WORKED ON A FIRST TRY

I checked APN setting on LOS 16 to compare them with configuration from 17.1 and they were exactly the same.
Now I am sure that MMSes are broken on LOS 17.1. Could you @NeoArian give it a look?
They were working on your unofficial builds of LOS 16, so you may know or remember how to fix it :fingers-crossed:.

Thanks in advanced.
Ok, so I did more tests on latest LOS 17.1. What I discovered is that MMSes are working but only when mobile data is DISabled, which is super weird.
- just wifi enabled - receiving/sending MMSes works (at first time I tried it with just wifi, the notification came up, that asked to grant permission for downloading MMSes via wifi. I granted it and MMS was downloaded successfully).

-just mobile data enabled - receiving/sending MMSes doesn't work at all. It is sending/receiving them until error, just how I described it in previous post.

-mobile data and wifi is enabled - receiving/sending MMSes doesn't work at all. It seams that mobile data has higher priority, so even though that wifi is working, it tries to use mobile data and fails to do so and when it fails it doesn't fall back to wifi.

-mobile data and wifi is DISabled -receiving/sending MMSes works :silly:. It is extremely weird, since it wasn't working last time i tried it with this configuration. It may be that since last time I have tried, I have given default messaging app every possible permission, disabled battery optimization, enabled unlimited data usage of mobile data and wifi and in roaming etc. After that when I try to send or receive MMS and have wifi and mobile data disabled it works. While sending/receiving MMS I can see data transfer indicator in the middle of status bar. I think that the messaging app sees, that there is no internet and since I've gave it every possible permission, it uses mobile data to send/receive MMS, even thought it wasn't enabled by hand, by me. In this scenario, mobile data must be used for sending/receiving MMSes, because there is no other option for messaging app to fall back.

So here is my thesis describing the MMS bug:

When mobile data is enabled by hand by a user, messaging app can't send/receive MMSes, even thought the internet is available. When none internet is available, messaging app enables mobile data automatically, just to receive/send MMS and then it works (mobile data isn't "turned on", it doesn't show any sign of it being enabled in QS and status bar. I know it is used only from data transfer indicator, that shows for a few seconds while MMS is being sent/downloaded). It seams that the app mistakenly tries to enable mobile data automatically, even thought it is already enabled, so it fails and stops, so at this point it never reaches the part of actual sending/receiving MMS.

With this information it should be easier to fix the issue, because now we know, how the environment must be configured for it to fail.

I would like to know if it happens to anyone else on the latest LOS 17.1 - and if it happens - I would like to know if edge cases I described in this post, check out to your situation.

Cheers
 
Last edited:

schastang

Senior Member
Nov 18, 2016
61
3
Sony Xperia Z3 Compact
Ok, so I did more tests on latest LOS 17.1. What I discovered is that MMSes are working but only when mobile data is DISabled, which is super weird.
- just wifi enabled - receiving/sending MMSes works (at first time I tried it with just wifi, the notification came up, that asked to grant permission for downloading MMSes via wifi. I granted it and MMS was downloaded successfully).

-just mobile data enabled - receiving/sending MMSes doesn't work at all. It is sending/receiving them until error, just how I described it in previous post.

-mobile data and wifi is enabled - receiving/sending MMSes doesn't work at all. It seams that mobile data has higher priority, so even though that wifi is working, it tries to use mobile data and fails to do so and when it fails it doesn't fall back to wifi.

-mobile data and wifi is DISabled -receiving/sending MMSes works :silly:. It is extremely weird, since it wasn't working last time i tried it with this configuration. It may be that since last time I have tried, I have given default messaging app every possible permission, disabled battery optimization, enabled unlimited data usage of mobile data and wifi and in roaming etc. After that when I try to send or receive MMS and have wifi and mobile data disabled it works. While sending/receiving MMS I can see data transfer indicator in the middle of status bar. I think that the messaging app sees, that there is no internet and since I've gave it every possible permission, it uses mobile data to send/receive MMS, even thought it wasn't enabled by hand, by me. In this scenario, mobile data must be used for sending/receiving MMSes, because there is no other option for messaging app to fall back.

So here is my thesis describing the MMS bug:

When mobile data is enabled by hand by a user, messaging app can't send/receive MMSes, even thought the internet is available. When none internet is available, messaging app enables mobile data automatically, just to receive/send MMS and then it works (mobile data isn't "turned on", it doesn't show any sign of it being enabled in QS and status bar. I know it is used only from data transfer indicator, that shows for a few seconds while MMS is being sent/downloaded). It seams that the app mistakenly tries to enable mobile data automatically, even thought it is already enabled, so it fails and stops, so at this point it never reaches the part of actual sending/receiving MMS.

With this information it should be easier to fix the issue, because now we know, how the environment must be configured for it to fail.

I would like to know if it happens to anyone else on the latest LOS 17.1 - and if it happens - I would like to know if edge cases I described in this post, check out to your situation.

Cheers

Hi pawloland,

Same issue on my unit with this firmware.
But even with mobile data turned ON or OFF and Wifi turned ON or OFF, I have still no luck in sending or receiving MMS :(
I live in France and my provider is SFR (I have double checked APS configuration, it's OK)

During my tests, after enabling Wifi (while mobile data was disabled), I had a notification to tell me I have an incoming MMS and that I have to enable an option to receive MMS with mobile data disabled (see attachment). But MMS still cannot be downloaded :(

I'm currently trying to find the right configuration / combination to be able to send and receive MMS!

Any help would be appreciated.
@NeoArian: Thanks a lot for this firmware :good:
 

pawloland

Senior Member
Jan 23, 2019
178
67
Hello,

I have done few more tests, and after restoring default APN, I can now receive and send MMS with WiFi ON or OFF and mobile data ON or OFF :)
So you are saying that you can have wifi turned off and mobile data turned on, at the same time and after that you can successfully receive and send MMSes - am I getting it right? I would be very glad if you could try this exact scenario for me just one more time, to make sure every possible scenario is working for you. If that's the case then good for you. I still can't receive MMSes while having mobile data turned on manually :(
 
Last edited:

schastang

Senior Member
Nov 18, 2016
61
3
Sony Xperia Z3 Compact
So you are saying that you can have wifi turned off and mobile data turned on, at the same time and after that you can successfully receive and send MMSes - am I getting it right? I would be very glad if you could try this exact scenario for me just one more time, to make sure every possible scenario is working for you. If that's the case then good for you. I still can't receive MMSes while having mobile data turned on manually :(

Here are the last tests I have done (Airplane mode OFF, 4G/LTE):
- WIFI OFF / mobile data OFF : OK (sending and receiving)
- WIFI ON / mobile data OFF : OK (sending and receiving)
- WIFI OFF / mobile data ON : KO (sending and receiving) with 4G/LTE network at first time, BUT if I switch to 3G/H, it works! Could you please check by yourself with this test (1st attempt in 4G/LTE failed, then switch to 3G/H as "preferred network" and see what happen) ? try to"force stop" the SMS/MMS app before switching from 4G to 3G. Not sure if it still works after switching back to 4G (one of my attempt was OK, one other failed so I don't know what to think :confused:, I don't remember if I "forced stop" the SMS/MMS app before switching back to 4G)
- WIFI ON / mobile data ON : I don't know. Behaviour is really strange. Sometimes it works, sometimes it doesn't. I think it depends on what is the first network enabled (Wifi or Mobile data) after disabling "airplane mode".

Hope it helps.

Regards,
 

NeoArian

Recognized Developer
Nov 25, 2017
1,227
2,762
Gladbeck
Good evening.
I'm sorry that I'm not really active here currently, I'm having much to do with university.
I appreciate your detailed testing. Could you also try to use a different SMS app and set it as default in settings? I will test it myself too whenever I get some time for it.
Greetings, arian.
 
  • Like
Reactions: .:B:.

pawloland

Senior Member
Jan 23, 2019
178
67
Here are the last tests I have done (Airplane mode OFF, 4G/LTE):
- WIFI OFF / mobile data OFF : OK (sending and receiving)
- WIFI ON / mobile data OFF : OK (sending and receiving)
- WIFI OFF / mobile data ON : KO (sending and receiving) with 4G/LTE network at first time, BUT if I switch to 3G/H, it works! Could you please check by yourself with this test (1st attempt in 4G/LTE failed, then switch to 3G/H as "preferred network" and see what happen) ? try to"force stop" the SMS/MMS app before switching from 4G to 3G. Not sure if it still works after switching back to 4G (one of my attempt was OK, one other failed so I don't know what to think :confused:, I don't remember if I "forced stop" the SMS/MMS app before switching back to 4G)
- WIFI ON / mobile data ON : I don't know. Behaviour is really strange. Sometimes it works, sometimes it doesn't. I think it depends on what is the first network enabled (Wifi or Mobile data) after disabling "airplane mode".

Hope it helps.

Regards,
Hi, I tested this quickly without success. I tried 3G, it didn't help, so I went back to 4G, enabled wifi and mobile data. Then I disabled "Mobile data always active" in dev setting (I had it enabled in previous tests). After I disabled it, I could send and receive MMSes on wifi+mobile data or just mobile data, untill I've disabled wifi and mobile data. After reenabling mobile data, I again couldn't send nor receive MMSes. I think that this option in dev settings is causing problems with MMS that won't send nor receive using mobile data enabled by hand.
 

nuess0r

Member
Feb 26, 2012
8
4
If I can help too : about the camera stock issue : I encountered this problem too when I flashed my Z3C from scratch (while previously I have used this build with no problem). I had to flash several times (and immediately testing the camera) before stock camera works again. No idea why.

Maybe this can help.

Yesterday I was reading what the other folks of the Z3C Carbon ROM are discussing and found a solution, at least for mine back camera problem:

You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.

Source: https://forum.xda-developers.com/showpost.php?p=81904527&postcount=14

This worked for me the first time I tried. Some others in the Carbon ROM thread where not successful. As TomKater wrote, he had to flash several times to get the camera working, I suggest that when the camera does not work after deleting /data/credmgr to try it several times and to see if this makes a difference. Good luck!
 
  • Like
Reactions: rm43115

john_matrix

Senior Member
Nov 22, 2008
409
100
France
Hello,
Camera wasn't working since the beginning and as advised, I have flashed the stock ROM and now camera is working again on LOS 17.1.
Only my digitizer is broken (at the bottom) and I have to replace it.
 

TolokOFF

New member
May 6, 2019
3
0
Hello! I am using the latest official version of LineageOS 17.1, and I noticed that the minimum screen brightness is much higher than the minimum brightness on the stock firmware. What could this be related to and will it be fixed? The same problem was on LineageOS 16 (also official builds)
 

TolokOFF

New member
May 6, 2019
3
0
Hello! I am using the latest official version of LineageOS 17.1, and I noticed that the minimum screen brightness is much higher than the minimum brightness on the stock firmware. What could this be related to and will it be fixed? The same problem was on LineageOS 16 (also official builds)
I also noticed that the Assertive Display function, which worked on the stock firmware, does not work on LineageOS 17.1. Regarding brightness, I noticed that the firmware only has 255 brightness levels, while the stock firmware has 4096 levels.
See file "max_brightness" - /sys/devices/leds-qpnp-24/leds/wled:backlight. Maybe this information will help to fix this problem. Sorry for my English, I used a Google Translator
 

TolokOFF

New member
May 6, 2019
3
0
Sorry for the many posts, but I found another problem in the latest official build of LineageOS 17.1 (from 11/17/2020)
Wi-Fi works only in b/g modes, if in the router settings you set the network to work only in n mode, then the phone cannot connect to the network - it sees it, but nothing happens when you try to connect. Reboot doesn't help. What could be the problem?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Good Evening!

    It's the time again, you might have already noticed that lineage 18.1 is official for some devices now. We, the sony shinano maintainers, were not sleeping and have also prepared our device for 18.1. I have uploaded a test build here: https://sourceforge.net/projects/ep...18.1/lineage-18.1-20210406-UNOFFICIAL-z3c.zip
    I would appreciate some testing/feedback on this build. There shouldn't be major issues on the test build, from my own testing it should be on-par with 17.1.
    I am optimistic that we can also achieve an official release of 18.1 for the z3c.

    All source codes can be found on the lineageos github in lineage-18.1 branches + additional patches for sony msm8974 are up on gerrit: https://review.lineageos.org/q/status:open+-is:wip

    Happy flashing!
    1
    I use Magisk 20.3 because everyhting works fine :)

    No warranty that the latest version works and there is no other way since LOS 17, AFAIK....
    1
    @pawloland Thanks for answering! I successfully backed up my DRM keys using "Universal (Dirtycow-based) TA Backup v2" which was very easy to do and didn't even need rooting the device prior.

    *EDIT* I successfully installed this ROM now, all looking good so far. What's the recommended method to root this LineageOS ROM?

    *EDIT2* Well, the enjoyment with the device only lasted for a very short while since I now discovered that SD-cards won't click-in into the Z3Cs reader. Appalling quality control at Sony, attention to detail traditionally only to their DRM systems :-( I'll try to get a replacement device from the seller, so my question above regarding how to root best is still valid.
    Magisk 20.4 flashable zip, can be updated to the latest via the app, but it seems versions after 20.4 do not survive LOS updates. Magisk app v.22 is fine
    p.s. Need to push sdcard quite deep so that it snaps into place
    1
    Hi, it might be a bit off topic.
    I just tried 17.1 on my z3c and noticed that some of my apps for work do not work on Android 10, so I wanted to go back to 16.0 but i don't have the zip file anymore. As I could not find a recent download for 16.0 I wanted to ask if someone still had recent version?
    I think I had lineage-16.0-20200901-nightly-z3c-signed.zip (I think it was the last 16.0 Version) so if someone could upload it or point me to a download link it would be very appreciated.

    regards
    You have a PM... For all others: there's still a microG version (only a bit older) on https://download.lineage.microg.org/z3c/
    1
    Just as with other Android 9 and 10 roms, I had heavy battery drain because of the media.extractor process.
    https://forum.xda-developers.com/t/10-official-carbonrom-cr-8-0-z3c.4047649/post-84715425

    I worked around it by killing it at boot with a simple Tasker profile (Edit: I added a two minutes delay to make sure the process is already started) :
    <TaskerData sr="" dvi="1" tv="5.9.3">
    <Profile sr="prof2" ve="2">
    <cdate>1616707624817</cdate>
    <edate>1617276057191</edate>
    <flags>8</flags>
    <id>2</id>
    <mid0>3</mid0>
    <nme>Kill media.extractor</nme>
    <Event sr="con0" ve="2">
    <code>411</code>
    <pri>0</pri>
    </Event>
    </Profile>
    <Task sr="task3">
    <cdate>1616707684454</cdate>
    <edate>1617276057191</edate>
    <id>3</id>
    <pri>100</pri>
    <Action sr="act0" ve="7">
    <code>30</code>
    <Int sr="arg0" val="0"/>
    <Int sr="arg1" val="0"/>
    <Int sr="arg2" val="2"/>
    <Int sr="arg3" val="0"/>
    <Int sr="arg4" val="0"/>
    </Action>
    <Action sr="act1" ve="7">
    <code>123</code>
    <Str sr="arg0" ve="3">killall media.extractor</Str>
    <Int sr="arg1" val="0"/>
    <Int sr="arg2" val="1"/>
    <Str sr="arg3" ve="3"/>
    <Str sr="arg4" ve="3"/>
    <Str sr="arg5" ve="3"/>
    </Action>
    </Task>
    </TaskerData>

    Like mentioned, we currently have to use Magisk 20.4 to root it.
    The best way is to install LineageOS then Magisk 20.4 and finally Magisk 22 all through recovery.

    Edit: I finally identified the problematic file, a 70 MB opus file.
  • 8
    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 17.1 for Xperia Z3 Compact.
    If you prefer TWRP over Lineage recovery, you can get it here.
    Recommended Google Apps package: Open GApps (choose ARM as Platform and 10.0 as Android, use the Variant you want. Recommended nano package)

    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 out 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

    XDA:DevDB Information
    LineageOS 17.1 for z3c, ROM for the Sony Xperia Z3 Compact

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

    Version Information
    Status: Stable

    Created 2020-09-08
    Last Updated 2020-09-12
    6
    Good Evening!

    It's the time again, you might have already noticed that lineage 18.1 is official for some devices now. We, the sony shinano maintainers, were not sleeping and have also prepared our device for 18.1. I have uploaded a test build here: https://sourceforge.net/projects/ep...18.1/lineage-18.1-20210406-UNOFFICIAL-z3c.zip
    I would appreciate some testing/feedback on this build. There shouldn't be major issues on the test build, from my own testing it should be on-par with 17.1.
    I am optimistic that we can also achieve an official release of 18.1 for the z3c.

    All source codes can be found on the lineageos github in lineage-18.1 branches + additional patches for sony msm8974 are up on gerrit: https://review.lineageos.org/q/status:open+-is:wip

    Happy flashing!
    5
    Hello @NeoArian , hello community. I'am very happy to see that the "BTLowPower" wakelock issue was fixed by @J_C_D and that it was merged into the android_kernel_sony_msm8974 repository last week. Thanks to all of you that spend your time supporting the Z3C and other older devices until now.
    5
    Yes, that's right.
    When Safe Start is turned on, the accelerometer does not work. Therefore, screen rotation, light sensor does not work.
    Thanks for the report. We were able to reproduce it and have fixed it. We will merge the fix within some days so that it will be fixed in the upcoming releases.
    Greetings, arian.
    4
    GOOD NEWS EVERYBODY!!!
    I managed to finally fix the persistent "BTLowPower" wakelock
    which caused the CPU to no longer enter Deep Sleep state and thus resulted in high battery drain once Bluetooth had been enabled! 🍻

    UPDATE: I just found a much simpler solution that does the trick! The real culprit was a #ifdef in BT Power Management that was introduced by a commit in July 2019 and then has fallen into oblivion :ROFLMAO:.
    Fixed! -> Version 3.
    @tblr0ne , @L.Lmar : can you please also test this version?



    *** TESTERS NEEDED! ***

    Find attached the modified boot.img. USE AT OWN RISK!

    Installation:
    - reboot Z3C into Bootloader (Vol+)
    - flash new boot image over current LineageOS17.1 installation using fastboot
    Code:
    fastboot flash boot boot-BTLowPower-fix-3.img
    - reboot
    Code:
    fastboot reboot

    NOTE for Magisk users:

    After flashing the new boot image, it is required to re-install Magisk. Do this by immediately booting into TWRP after the new boot image is flashed.
    Also note that you need Magisk v20.4 for this! Later versions won't work.
    Anyway, you will be able to upgrade Magisk to up-to-date versions using Magisk Manager after the system has booted.

    @NeoArian when everything seems ok, I will create a merge request in LineageOS/android_kernel_sony_msm8974. Is this the correct place / way to go?
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