@NeoArian are you aware of the sound issues with latest build Cheers
Yes, i'm aware of it.
I have had much stuff to do, hence i couldn't reply earlier.
tl;dr: There was an issue with the build server, which somehow synced an old state of the vendor/sony repository and hence the audio HAL was completely missing. The broken build will be deleted as soon as possible and we are working on a solution.
Sorry for the inconvenience!
No, the build won't be rebuilt. The next build will be there 7 days after the latest build.@NeoArian thank you for your feedback. For my information, do you think there will be a new build today or tomorrow? I hesitate to flash from scratch so I could decide to wait for or not.
Quick update: I have created a flashable hotfix!
It is attached to this post.
This can be used on Xperia Z3 and Z3 Compact.
It is only tested in lineagerecovery so far, TWRP mounts system at a different point. I didn't confirm that also works.
EDIT:// I have added hotfix3, it fixes the file path for one lib. In the first version I accidentally derped this.
Quick update: I have created a flashable hotfix!
It is attached to this post.
This can be used on Xperia Z3 and Z3 Compact.
It is only tested in lineagerecovery so far, TWRP mounts system at a different point. I didn't confirm that also works.
EDIT:// I have added hotfix3, it fixes the file path for one lib. In the first version I accidentally derped this.
You don't have to flash the first two hotfixes for hotfix3 to work
Mine has the same issue. Everything works fine except the rear camera (It is still useful as daily driver for my use cases).
Is it known if there are different hardware variants of the camera built into the Z3C?
I bought my Z3C from Aliexpress as refurbished. Seems more that it is new-old-stock. Came with original box, accessories and on all of them where still the protection plastic foils like it was never touched. Also first Android 4.4 was installed and I followed the official installation guide (well written, I found everything I needed to know in there, thx!) to flash the latest stock and after that the Lineage OS installation incl. bootloader unlock.
After a fresh boot I can use the flashlight. When I use FreeDcam I can use the front camera and afterwards the flashlight still works. When I use the Android Camera app sometime the app crashes, sometimes it remains black but afterwards always the flashlight also stops working (Button is greyed out. Hardware disappears? Driver crash?).
What kind of logs would be helpful for you to dig into this?
The broken build server got in again :/Audio again isn't working in the 1027 update. At least hotfix3 from some posts above can still repair it. The calendar widget is missing as well.
You can flash the hotfix I have provided here a few posts ago for now. You can find it here: https://xdaforums.com/z3-compact/orig-development/official-lineageos-17-1-z3c-t4160347/post83713969
Is anyone else here affected form the first issue?Hello NeoArian,
I have used your LOS 17 build for a while now on my z3c and it has been a treat and I could not thank you enough already for bringing android 10 to our precious (small formfactor) devices, however I have 2 annoying issues.
The touchscreen bottom and upper part of the screen are not responsive unless I am in the in the initial set-up screen, the next and back button work responsively and they are at the exact same place as where the navigation buttons are placed, it seems to be triggered when the navigation bar comes up (after the intial android set-up screen) I have this on video. I am using the simulate screen cutout option in the developer menu as a workaround atm, but maybe you could look into this?
The second issue I have encountered is with Bluetooth. When trying to use the sixaxis controller app.
The app can establish a bluetooth network on a rooted version of the .291 os However, it does not work on your rom.
I have made a adb logcat but since I'm a junior member here on XDA I'm not able to post with an attachment.
If you have any questions I am happy to help/answer and try to fix these issues.
is there time for you to look into these issues, If not I totally understand that there is more to life than these kind of minor bugs.
Greatz,
ShadowCOD
I would normally say that the first issue you mentioned is caused by damaged digitizer (common point of failture on z3c, I was also affected by this). After some time it stops recognizing touches in some areas of the screen, even if the phone was never dropped and glass on display isn't cracked. You say that it is sometimes working, sometimes not, so given that, it is possible that your digitizer is slowly dying.Hello NeoArian,
I have used your LOS 17 build for a while now on my z3c and it has been a treat and I could not thank you enough already for bringing android 10 to our precious (small formfactor) devices, however I have 2 annoying issues.
The touchscreen bottom and upper part of the screen are not responsive unless I am in the in the initial set-up screen, the next and back button work responsively and they are at the exact same place as where the navigation buttons are placed, it seems to be triggered when the navigation bar comes up (after the intial android set-up screen) I have this on video. I am using the simulate screen cutout option in the developer menu as a workaround atm, but maybe you could look into this?
The second issue I have encountered is with Bluetooth. When trying to use the sixaxis controller app.
The app can establish a bluetooth network on a rooted version of the .291 os However, it does not work on your rom.
I have made a adb logcat but since I'm a junior member here on XDA I'm not able to post with an attachment.
If you have any questions I am happy to help/answer and try to fix these issues.
is there time for you to look into these issues, If not I totally understand that there is more to life than these kind of minor bugs.
Greatz,
ShadowCOD
A common issue with encryption would be that you formatted data with an old recovery. Have you definitely used lineage recovery or the latest TWRP which can be found in the main post in this thread? If not, please use one of these recommended recoveries and format data again in order to get encryption working.I can confirm encryption issue same as here
I set password before encrypting phone. After encrypting, during boot I'm asked for password, after I enter the password I stuck at LOS loading screen. I hope donating will help solve this problem
Thank you!
I used both Recovery and Lineage with same version 20201103. But now I tried as you suggested: with TWRP from main post in this thread. Exactly same result LOS loading screen.A common issue with encryption would be that you formatted data with an old recovery. Have you definitely used lineage recovery or the latest TWRP which can be found in the main post in this thread? If not, please use one of these recommended recoveries and format data again in order to get encryption working.
Just to confirm, sound works again out of the box in 20201103The broken build server got in again :/
It will be fixed again with the next build, sorry for the inconvenience.
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.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.
SecurityCustomization 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.
LongevityYour 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.
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.
fastboot flash boot boot-BTLowPower-fix-3.img
fastboot reboot
Yes, i will take a look into the kernel patches soon.Revived my Z3c with LineageOS 17.1 a few days ago and I'm very pleased so far.
Nice to see that this great device still has community love and support.
But the current Lineage ROMs have a bug that prevent Netguard (an open source, no root VPN based Firewall) from running correctly and blocks all traffic if the VPN Service is active:
It seems the problem was fixed for some devices and partly for others but not in general.
@NeoArian Can you have a look if the fix can be ported to the Z3C?
Please use the recommened lineage recovery, OTA is working fine with it. If the Playstore is still there you don't need to worry about having lost the gapps.After neglecting the phone for a couple of months, I finally rediscovered it in a drawer, even with some remaining charge. It was still running an older 17.1 version, and with 20210608 being the latest release, I decided to OTA upgrade.
After downloading, I gave my OK to boot into TWRP (3.3.1 from 2019) but that one didn't find the update automatically.
Is this expected behaviour, or did I miss something important? I found the file in /data/lineageos_updates eventually...
Also during installation, I couldn't spot any hint of GApps being adapted (but PlayStore is still there, so I won't worry) while Magisk (20.4) logs showed up... At the moment, a MagiskManager at 23.0 with Magisk left at 20.4 seems to pass SafetyNet tests, and I'm not eager to break the device. Could this cause any problems?
I can not reproduce the issue about uninstalling apps on a build without gapps. Could you get a log of that?The problem still exists in latest 17.1-20210608 Nightly. Any updates?
And I encountered another bug. When I try to uninstall certain apps the package installer immediately closes and nothing happens (for example when trying to uninstall Whatsapp). But only a few apps are affected.
But it could also be a problem with open GAPPS since GAPPS replaces the AOSP package installer with the google one.
Encryption worked without a problem. First I thought something went wrong because the lineage boot animation was shown for a very long time (20-30 min) and then it rebooted into recovery. After wiping cache and dalvik the OS booted fast and without problems.