[OFFICIAL] LineageOS 16.0 for Xperia Z3 Compact

Status
Not open for further replies.
Search This thread

onestepb

New member
Feb 4, 2020
1
1
confirm

First of all many thanks for this excellent rom and all the hard work that has been put into it. I really appreciate the hard work and I am very happy with it. I just have problems with a static noise or a very loud crackling while making phone calls.
The loudspeaker for the ear (I put the phone on my ear) is very loud but I could adjust that with the volume control. But I hear all the time a static noise. If I use the official lineage os dialer (phone call by sim card) it is a bit better. If the person on the other end is silent the crackling noise is not to hear or only a bit.
If I use a sip client like ZoiPer the problem is more severe. The crackling, static noise is permanently to hear and very annoying. I suspect that the phone dialer is using a kind of noise cancelling while the sip client cannot use this feature.
Does anybody know how to fix that?

i can confirm that problem: while making phone calls an static, annoying noise is hearable in the background. it disappears when switching to loud speaker or when the person on the other end is quite. i won't call it a crackling noise, it sounds more like using a walky-talkie or like listening to an analog radio channel with a low signal.
 
  • Like
Reactions: Alizad00

john_matrix

Senior Member
Nov 22, 2008
409
100
France
Hello NeoArian,

There is a critical Bluetooth vulnerability:
https://insinuator.net/2020/02/critical-bluetooth-vulnerability-in-android-cve-2020-0022/

Could you please update this ROM with the latest Google Security update patch (February) as this vulnerability has been corrected?

Many thanks in advance!

Note: this vulnerability is not exploitable in Android 10 but result in a crash of the Bluetooth daemon (this could cause some inconveniences)
 
  • Like
Reactions: dhacke

NeoArian

Recognized Developer
Nov 25, 2017
1,227
2,762
Gladbeck
Hello NeoArian,

There is a critical Bluetooth vulnerability:
https://insinuator.net/2020/02/critical-bluetooth-vulnerability-in-android-cve-2020-0022/

Could you please update this ROM with the latest Google Security update patch (February) as this vulnerability has been corrected?

Many thanks in advance!

Note: this vulnerability is not exploitable in Android 10 but result in a crash of the Bluetooth daemon (this could cause some inconveniences)
Hi, the February patch will be merged into lineage-16.0 soon. Since the builds are running on the lineage server I can include the February patch before it is merged into lineage-16.0.
But anyway, it should not take more then 2-3 more days.
Greetings, Arian
 

xnote3.0

Senior Member
Dec 6, 2018
64
11
Can anyone help me? I completely wipe the phone,I try to flash the ROM, then I flash GAPPS, the animation comes, after some minutes the phone reboots to TWRP, even without GAPPS. Am I doing anything wrong?
 

Klaus N.

Senior Member
Oct 14, 2012
1,289
689
Nuremberg
Can anyone help me? I completely wipe the phone,I try to flash the ROM, then I flash GAPPS, the animation comes, after some minutes the phone reboots to TWRP, even without GAPPS. Am I doing anything wrong?
Just to be sure: Have you formatted the data partition before flashing LineageOS (In TWRP > wipe > format data) ? It's important to get rid of the stock data encryption...
 

hapmpt

Member
Oct 22, 2013
11
5
Hi NeoArian,

Just saw your latest commit fixing the typo in the filename. Must have been the most frustrating bug hunt ever, single character mistakes are so hard to find! Does this fix our sound distortion issues?

Cheers and thanks for your persistence!
 
  • Like
Reactions: Klaus N.

NeoArian

Recognized Developer
Nov 25, 2017
1,227
2,762
Gladbeck
Hi NeoArian,

Just saw your latest commit fixing the typo in the filename. Must have been the most frustrating bug hunt ever, single character mistakes are so hard to find! Does this fix our sound distortion issues?

Cheers and thanks for your persistence!
Yes, this seems to fix the audio problems. @Mr.Tom_Tom found the actual typo in the end, so all thanks go to him :D
Together with two other changes, first add the stock dmic acdb id's which should bring the stock fluence configuration in handset mode and second disabling fluence in speaker mode, that should also get the speaker experience inline with stock. However it is not 100% similar to stock yet I think, sometimes I still have an echo on the other end when in speaker mode. But all in all its a huge improvement I think.
 

pawloland

Senior Member
Jan 23, 2019
178
67
Hi @NeoArian
I am using Lineage OS 16 for a year now. I have been there from pretty much the beginning. I just tried the latest nightly and the audio while calling in normal mode is just on point and the loudspeaker mode is also significantly louder, than in previous build. I am very happy to see this issue being fixed after that long amount of time. I honestly wasn't believing it would be ever fixed.
Do you remember the bug when the audio was played super loud and then it was getting quieter and quieter? I think the only problem left now is to make sound in any part of system or any app as loud as it was while this bug was occurring. I think that the maximum loudness of phone in lineage is like 80% of the maximum volume on stock. The same applies for loudspeaker mode - it is now significantly louder, but it steel isn't as loud as stock. It can be also just me imagining the problem, because after all of those audio issues I don't know if I can trust my ears anymore :p.

Right now the builds are official which would suggest that everything is working. Well I still have some problems:
-the wfd (wifi display/mirracast) is sometimes WORKING for me. I remember that it wasn't working so it was abandoned, but later on it was again enabled, because it wasn't causing restarts anymore. I don't remember if you did something to solve this issue but it seems that problem solved itself. I tried connecting to my windows laptop and after couple of tries the phone CONNECTED :D. For the first time in year I was able to connect. Here are my observations:
- the popup on windows is always displayed when device tries to connect to it
- from that popup I can click to connect to device and the phone either decides to connect or not and then the message appears on the windows that says something like "Secured content can't be played on this device"
-audio is being send but is little off sync
-video is sluggish, artifacts can be seen
-after connection is established phone often disconnects from wifi network. If i try to connect to wifi again it is stuck on "Obtaining IP address". It can also happened that the phone connects to wfd and DOESN'T disconnects from wifi. If that happens the video stream is super, mega, ultra blurry, off sync, artifacts can be observed, video is very choppy and connectivity is going to be lost.
As the connection can be established nowadays, can you do something to fix the huge lag while using wfd and connected to wifi?

Next thing is Fm Radio. It doesn't work for me anymore even after manually selecting the frequency (like it was left before).
That is all what I think is left unpolished on lineage side. The rest is regarding TWRP.
-the signature verification always fails on official zips. I don't know if it is the problem with TWRP, that can't verify the zip or the zip itself has wrong signature.
-can't perform OTA updates. I must manually install each update.
-the time in logs is wrong
-after any action performed in TWRP I get error saying ~Can't mount storage.
I attach logs.

Thanks for all of your work. I am looking forward official Lineage OS 17.1 while it gets out from WIP :eek:
 

Attachments

  • recovery.log
    20.7 KB · Views: 3
  • Screenshot_2020-02-11-20-16-04.png
    Screenshot_2020-02-11-20-16-04.png
    112.1 KB · Views: 125
Last edited:

gorodon

New member
Feb 12, 2020
2
0
Main cam issue

After some end of January of start of February Main camera stopped working. Front camera is still working well.
Could you please assist me with this issue?
 

pawloland

Senior Member
Jan 23, 2019
178
67
After some end of January of start of February Main camera stopped working. Front camera is still working well.
Could you please assist me with this issue?
For me both of them work. Try cleaning data of camera app. If it doesn't help make twrp backup (if you want) and flash stock android 6 using emma. If the camera doesn't work on stock it is hardware issue.
 

NeoArian

Recognized Developer
Nov 25, 2017
1,227
2,762
Gladbeck
Hi @NeoArian
I am using Lineage OS 16 for a year now. I have been there from pretty much the beginning. I just tried the latest nightly and the audio while calling in normal mode is just on point and the loudspeaker mode is also significantly louder, than in previous build. I am very happy to see this issue being fixed after that long amount of time. I honestly wasn't believing it would be ever fixed.
Do you remember the bug when the audio was played super loud and then it was getting quieter and quieter? I think the only problem left now is to make sound in any part of system or any app as loud as it was while this bug was occurring. I think that the maximum loudness of phone in lineage is like 80% of the maximum volume on stock. The same applies for loudspeaker mode - it is now significantly louder, but it steel isn't as loud as stock. It can be also just me imagining the problem, because after all of those audio issues I don't know if I can trust my ears anymore :p.

Right now the builds are official which would suggest that everything is working. Well I still have some problems:
-the wfd (wifi display/mirracast) is sometimes WORKING for me. I remember that it wasn't working so it was abandoned, but later on it was again enabled, because it wasn't causing restarts anymore. I don't remember if you did something to solve this issue but it seems that problem solved itself. I tried connecting to my windows laptop and after couple of tries the phone CONNECTED :D. For the first time in year I was able to connect. Here are my observations:
- the popup on windows is always displayed when device tries to connect to it
- from that popup I can click to connect to device and the phone either decides to connect or not and then the message appears on the windows that says something like "Secured content can't be played on this device"
-audio is being send but is little off sync
-video is sluggish, artifacts can be seen
-after connection is established phone often disconnects from wifi network. If i try to connect to wifi again it is stuck on "Obtaining IP address". It can also happened that the phone connects to wfd and DOESN'T disconnects from wifi. If that happens the video stream is super, mega, ultra blurry, off sync, artifacts can be observed, video is very choppy and connectivity is going to be lost.
As the connection can be established nowadays, can you do something to fix the huge lag while using wfd and connected to wifi?

Next thing is Fm Radio. It doesn't work for me anymore even after manually selecting the frequency (like it was left before).
That is all what I think is left unpolished on lineage side. The rest is regarding TWRP.
-the signature verification always fails on official zips. I don't know if it is the problem with TWRP, that can't verify the zip or the zip itself has wrong signature.
-can't perform OTA updates. I must manually install each update.
-the time in logs is wrong
-after any action performed in TWRP I get error saying ~Can't mount storage.
I attach logs.

Thanks for all of your work. I am looking forward official Lineage OS 17.1 while it gets out from WIP :eek:
Hi,
First of all thanks for the detailed feedback, I appreciate it.
About the audio stuff, I think it should be comparable to stock, we are pretty much using the stock setup of the mixer settings. I will hear again when I flash stock next time though to make sure. I did not enable Miracast for the Sony msm8974 devices because I don't consider it as really working, I didn't get the heavy wlan speed drop during it fixed. All TV's shown in settings should be available through Google cast which works good on my Z3C and Sony android TV, will also confirm that again within the next days. I don't think your windows laptop is using Google cast though, do you still stream from the settings -> connected devices -> connection settings -> stream?
What you describe sounds similar to Miracast but that one shouldn't be available in the official build, weird?
FM radio was working okay for me last time I checked. I will downgrade to 16.0 to confirm that in the official builds.
About twrp I have some good news :D
I don't really know about your first problem with zip signature verification, it might be caused by the official builds that are signed with custom created keys.
I have built a new TWRP with OTA updates fixed. @115ek has shared the fix. I will release it within the next days somewhere. Until now you can download it from here: https://drive.google.com/file/d/12f7WrbpkqmSMC1p3OSfRwG7k2BwlmgWt/view?usp=drivesdk
( For Z3 friends: https://drive.google.com/file/d/12eYhVT6-nFGuIlbSiDVEMnODcBUDcMcq/view?usp=drivesdk).
About the wrong time, there was a problem in the Sony timekeep service, many thanks to MarijnS95 who fixed the problem and helped me out really quick. (https://github.com/sonyxperiadev/timekeep/issues/23)
I will try to get this fix merged into LineageOS soon. Then the time will be working fine in TWRP, I already have it fixed on my device. I didn't see "Can't mount storage." On my device. Can you see if that still happens with the new TWRP build?

Greetings, Arian.
 

pawloland

Senior Member
Jan 23, 2019
178
67
I will try it tomorrow and edit this post.
[EDIT 1]: Sorry, I didn't have time yesterday. Anyway here it is.

Right now I am on nightly from 10th of February.
Yes indeed I am using mirracast (as I even wrote before). I don't have any device which has chrome cast, so I am stick with older mirracast. I did a quick research and find that google silently removed mirracast from android probably because the wanted to increase number of sold chrome casts. It explains why the mirracast wasn't working as expected without hacks.
I would also add that fm radio is working like a frequency generator :).

I enable mirracast in settings under:
Connected devices -> Connection preferences -> Cast -> 3 dots in upper right corner -> Check 'Enable wireless display' -> connect to my windows laptop (which uses mirracast standard for streaming, not google cast). It is strange because the more times I try to connect to mirracast display, the more flawlessly it works. As of now my problem with wifi while using mirracast is gone :p. It is weird, but even if this option is available in official builds by your mistake, please don't remove it. It is somehow working very good after couple of sessions :D.

Before I try new twrp I must say that my issue with it started with official builds. I hadn't have any of those issues before. I also observed that after flashing stock using Emma -> flashing twrp from post #1, the problems are gone, until the first flash in twrp. After the first flash, the error with mounting storage is raised. I am not encrypted (I am not sure what encryption means in that context so: internal storage isn't encrypted but i have screen lock (pin code) on my device) and I don't have multiple users on my phone.

Now is the part about new twrp.
My zip for testing was nightly from 12th of February.
- OTA updates works now (but the signature verification must be turned off).
- Time and date only in twrp log is still wrong.
- I still have error with signature verification.
- The "Unable to mount storage" error persist. I am using magisk and I don't have sd card. Maybe it is the cause. Can someone confirm or deny having this issue with magisk installed or not having sd card or even with both of these conditions met?
I can acces internal storage after this error which is mounted in /sdcard. I don't have external sd card so the /external_sd mount point is empty. The /storage mount point is also empty but I don't know what is supposed to be mounted here. Logs from twrp are attached to post.


I found another issue with camera in Telegram X app, when we are in the conversation and try to take a picture.
-when the flash light is turned off, picture is taken correctly,
-when flash light is on auto or always turned on, the preview is cropped and the taken picture is bigger than the preview.
Tried it on different devices and it only works like this on my z3c.
I don't know how to describe it so I recorded it.
https://drive.google.com/file/d/1zpM5auzIt6X47xyT1w7O3V-gaGkCh6CG/view?usp=sharing
 
Last edited:

Azmipemha

New member
Feb 11, 2020
2
0
Ponorogo
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
 * Your warranty is now void.
 *
 * I am 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 me for messing up your device, I will laugh at you.
 */[/COLOR]

Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP 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

Download link:
LineageOS Downloads for z3c

Recommended Google Apps package:
Open GApps (choose ARM as Platform and 9.0 as Android, use the Variant you want. Recommended nano package)

Required TWRP recovery
twrp-3.3.1-z3c-20191107.img

Official root addon
LineageOS Extras

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

Thanksgiving
Thanks to everyone who ever contributed to the custom developement for this device.
Especially:
@tomascus
@Diewi
@xkeita
@rcstar6696
@koron393
@nailyk
@SpiritCroc
@115ek
@Myself5
@drakonizer

Thanks to every LineageOS contributor.

Source Code
The source code of LineageOS is available here.
The kernel source code for this device is available here.
The used configuration is lineageos_shinano_aries_defconfig available at arch/arm/configs/lineageos_shinano_aries_defconfig in the kernel source.


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

Contributors
NeoArian
Source Code: https://github.com/LineageOS

ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x

Version Information
Status: Nightly

Created 2019-11-07
Last Updated 2019-11-07


video calls on whatsapp there are obstacles such as the other person does not hear our voices. or indeed a bug in the microphone during the video call
 

anton472

New member
Mar 11, 2014
2
1
video calls on whatsapp there are obstacles such as the other person does not hear our voices. or indeed a bug in the microphone during the video call

There is such a thing in whatsapp. If only a voice, then the microphone works. If the video, then the microphone for some reason stops working.
 

Gelindo67

Member
Apr 4, 2019
9
0
I have been using Lineage os 16 on my sony z3 compact with satisfaction for some months, the only thing that does not satisfy me is the camera that takes photos with a lot of noise, few details and colors with little saturation. anyone using mods that improve camera quality on lineage os 16? Do you have any advice to give me?
 

BigBrother84

Senior Member
May 25, 2019
159
41

Hi,

Please correct me if I'm wrong, may this work:
https://forum.xda-developers.com/cr...carbomrom-xperia-package-guide-clean-t3816147

If I remember correctly I used it with my previous z2 and worked without camera button. Now I'm stopped interesting and left reading posts cause of XZ1C I got. Also I may try flash it and give feedback after owner solve hardware problem with his z3c and possibly borrow me. Sadly, I don't know when.

Good luck, if you will be trying. Read carefully how to do it. ;)

-------------------------------------
Always do backups!
 

Mr.Tom_Tom

Senior Member
Feb 16, 2008
145
177
Munich
There is such a thing in whatsapp. If only a voice, then the microphone works. If the video, then the microphone for some reason stops working.
video calls on whatsapp there are obstacles such as the other person does not hear our voices. or indeed a bug in the microphone during the video call
Thanks for reporting this issue and I can confirm it for both the Z3c and the Z3. Mic is not working when used in voip applications like WhatsApp or Google Duo AND when phone is on hands-free mode (what is the case when you switch to video).

I am looking into some logs now...
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    Code:
    [COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
    [COLOR="Navy"]/*
     * Your warranty is now void.
     *
     * I am 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 me for messing up your device, I will laugh at you.
     */[/COLOR]

    Installation:
    If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP 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

    Download link:
    LineageOS Downloads for z3c

    Recommended Google Apps package:
    Open GApps (choose ARM as Platform and 9.0 as Android, use the Variant you want. Recommended nano package)

    Required TWRP recovery
    twrp-3.3.1-z3c-20191107.img

    Official root addon
    LineageOS Extras

    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

    Thanksgiving
    Thanks to everyone who ever contributed to the custom developement for this device.
    Especially:
    @tomascus
    @Diewi
    @xkeita
    @rcstar6696
    @koron393
    @nailyk
    @SpiritCroc
    @115ek
    @Myself5
    @drakonizer

    Thanks to every LineageOS contributor.

    Source Code
    The source code of LineageOS is available here.
    The kernel source code for this device is available here.
    The used configuration is lineageos_shinano_aries_defconfig available at arch/arm/configs/lineageos_shinano_aries_defconfig in the kernel source.


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

    Contributors
    NeoArian
    Source Code: https://github.com/LineageOS

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.4.x

    Version Information
    Status: Nightly

    Created 2019-11-07
    Last Updated 2019-11-07
    9
    Note that the first build is scheduled but not yet available for download. No need to worry though, the lineage-16.0 project is in nightly state so it should be up in a maximum of 24 hours.
    Also note that the official builds are signed, so you are not able to just flash them over the current unofficial LineageOS 16.0 builds.
    7
    Hi @NeoArian
    I am using Lineage OS 16 for a year now. I have been there from pretty much the beginning. I just tried the latest nightly and the audio while calling in normal mode is just on point and the loudspeaker mode is also significantly louder, than in previous build. I am very happy to see this issue being fixed after that long amount of time. I honestly wasn't believing it would be ever fixed.
    Do you remember the bug when the audio was played super loud and then it was getting quieter and quieter? I think the only problem left now is to make sound in any part of system or any app as loud as it was while this bug was occurring. I think that the maximum loudness of phone in lineage is like 80% of the maximum volume on stock. The same applies for loudspeaker mode - it is now significantly louder, but it steel isn't as loud as stock. It can be also just me imagining the problem, because after all of those audio issues I don't know if I can trust my ears anymore :p.

    Right now the builds are official which would suggest that everything is working. Well I still have some problems:
    -the wfd (wifi display/mirracast) is sometimes WORKING for me. I remember that it wasn't working so it was abandoned, but later on it was again enabled, because it wasn't causing restarts anymore. I don't remember if you did something to solve this issue but it seems that problem solved itself. I tried connecting to my windows laptop and after couple of tries the phone CONNECTED :D. For the first time in year I was able to connect. Here are my observations:
    - the popup on windows is always displayed when device tries to connect to it
    - from that popup I can click to connect to device and the phone either decides to connect or not and then the message appears on the windows that says something like "Secured content can't be played on this device"
    -audio is being send but is little off sync
    -video is sluggish, artifacts can be seen
    -after connection is established phone often disconnects from wifi network. If i try to connect to wifi again it is stuck on "Obtaining IP address". It can also happened that the phone connects to wfd and DOESN'T disconnects from wifi. If that happens the video stream is super, mega, ultra blurry, off sync, artifacts can be observed, video is very choppy and connectivity is going to be lost.
    As the connection can be established nowadays, can you do something to fix the huge lag while using wfd and connected to wifi?

    Next thing is Fm Radio. It doesn't work for me anymore even after manually selecting the frequency (like it was left before).
    That is all what I think is left unpolished on lineage side. The rest is regarding TWRP.
    -the signature verification always fails on official zips. I don't know if it is the problem with TWRP, that can't verify the zip or the zip itself has wrong signature.
    -can't perform OTA updates. I must manually install each update.
    -the time in logs is wrong
    -after any action performed in TWRP I get error saying ~Can't mount storage.
    I attach logs.

    Thanks for all of your work. I am looking forward official Lineage OS 17.1 while it gets out from WIP :eek:
    Hi,
    First of all thanks for the detailed feedback, I appreciate it.
    About the audio stuff, I think it should be comparable to stock, we are pretty much using the stock setup of the mixer settings. I will hear again when I flash stock next time though to make sure. I did not enable Miracast for the Sony msm8974 devices because I don't consider it as really working, I didn't get the heavy wlan speed drop during it fixed. All TV's shown in settings should be available through Google cast which works good on my Z3C and Sony android TV, will also confirm that again within the next days. I don't think your windows laptop is using Google cast though, do you still stream from the settings -> connected devices -> connection settings -> stream?
    What you describe sounds similar to Miracast but that one shouldn't be available in the official build, weird?
    FM radio was working okay for me last time I checked. I will downgrade to 16.0 to confirm that in the official builds.
    About twrp I have some good news :D
    I don't really know about your first problem with zip signature verification, it might be caused by the official builds that are signed with custom created keys.
    I have built a new TWRP with OTA updates fixed. @115ek has shared the fix. I will release it within the next days somewhere. Until now you can download it from here: https://drive.google.com/file/d/12f7WrbpkqmSMC1p3OSfRwG7k2BwlmgWt/view?usp=drivesdk
    ( For Z3 friends: https://drive.google.com/file/d/12eYhVT6-nFGuIlbSiDVEMnODcBUDcMcq/view?usp=drivesdk).
    About the wrong time, there was a problem in the Sony timekeep service, many thanks to MarijnS95 who fixed the problem and helped me out really quick. (https://github.com/sonyxperiadev/timekeep/issues/23)
    I will try to get this fix merged into LineageOS soon. Then the time will be working fine in TWRP, I already have it fixed on my device. I didn't see "Can't mount storage." On my device. Can you see if that still happens with the new TWRP build?

    Greetings, Arian.
    6
    Good evening,
    since some of you seem to have problems with echo during calls i have digged through patches developer previously applied to our devices. I have tranfsformed them into two magisk modules and would ask the ones who have the problems to test both of the modules. In the first row please test them one by one and then you can also combine them (just install both). Good luck!

    Don't get irritated from the OTA for Lineage 17 text during installation, i just missed to change that from my template.
    5
    So I flashed twrp, and I can't perform OTA. When I click Install in updater phone reboots and then hangs at sony logo and led flashes blue. Forcefully turned off the phone, and booted to twrp. Script started executing, but ended up with the error as before. After that I tried to manually install zip, but as you may expect, without success. Here are logs:

    I haven't seen the signature verification failed error myself but could you try to disable the signature verification within TWRP settings (default is not activated by the way)?

    Anyway Good evening everyone, since i am a little bit sick today i have had some time to look into the mystery call volume problem :D I have experimented really much and got a probably pretty good solution.
    The first change is https://review.lineageos.org/c/LineageOS/android_device_sony_z3c/+/264153 where i have updated the mixer_paths from the latest stock ROM and dropped all modifcations we previously had on top of the stock one except the one linked in the commit message. https://review.lineageos.org/c/LineageOS/android_device_sony_shinano-common/+/264152 This commit drops custom acdb id's for dual microphone configurations we previously had. I don't understand why we had these changes but when falling back to the default acdb id's (43 for speaker dmic and 41 for handset dmic) The volume is not that crazy loud anymore and similar to stock i think. I have also enabled Fluence here: https://review.lineageos.org/c/LineageOS/android_device_sony_shinano-common/+/264150 That should enable Qualcomm’s dual-mic echo cancellation technology and seems to work good so far.
    One problem is left, you might now that my bottom speaker is broken so i can't test the speaker mode output myself, so i have not merged the changes yet. Would someone be so kind and test the build i compiled? download: https://drive.google.com/open?id=1r2ipI5gfZpxPTxCSYpyIBEse2Hsr3FF7 Note that you can not flash this build over the official nightly because of the different signing of the official build. Please wipe data. If you are still on my latest unofficial build you can just flash it as always.

    In order to get some impressions how the experience should be i flashed the stock OS today morning myself, i think the calls should be on a similar level now, assumed that the speaker works as intended.

    I have also tested GPS on stock and found out that it can connect to GLONASS and Beidou sattelites, i think on Lineage we are not able to do so currently. I will look into this within the next days and keep you updated on this.
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