[CLOSED][OFFICIAL] LineageOS 17.1 for z3c

[hojnikb]

same here, no sound.

 

[pawloland]

@NeoArian are you aware of the sound issues with latest build Cheers

 

[NeoArian]

@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!

 

[tomKater]

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!

@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 0610 from scratch so I could decide to wait for or not.

 

[NeoArian]

@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.

No, the build won't be rebuilt. The next build will be there 7 days after the latest build.
Best would be to go with the older build for now.
However, if I find some time for it, I will provide a hotfix zip for the users who already updated to the new build.
Greeting, Arian.

 

[NeoArian]

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

 

[Zwulfulfsn]

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.

I can confirm that with installed hotfixes #1 - #3 via TWRP sound came back on my device (calls, music, headset, bluetooth). Big thank to NeoArian for his immeadiate help.

 

[xfranky81]

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

Yay, thanks! Hotfix3 confirmed working \o/ :good:

 

[Serf95]

Thank you @NeoArian.

1) Is the encryption working correctly?

2) The delay time when you lock the screen, works incorrectly. The time you have not set before locking the screen is immediately locked after you turn off the screen. Could you fix this bug? I would like to set the time before auto-locking.

 

[YukiS]

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?

I also bought my Z3 Compact from AliExpress and was having the same issue until I restored the stock 23.5.A.1.291 firmware with the official flashing tool Emma (instead of Flashtool as the installation guide suggests) then did a clean flash back to LOS 17.1 afterwards.

 

[tblr0ne]

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.

 

[L.Lmar]

lineage-17.1-20201027 no sound :crying:

 

[shadowCOD]

2 annoying but manageable issues found

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

 

[NeoArian]

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.

The broken build server got in again :/
It will be fixed again with the next build, sorry for the inconvenience.

lineage-17.1-20201027 no sound :crying:

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

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

Is anyone else here affected form the first issue?
I will look into the controller support when I find some time.

 

[pawloland]

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.

Speaking of sixaxsis controller app. If I am not mistaken it wasn't updated for ages and it isn't even available for download from play store. The last android version that is supported by the app is IIRC android 6 or 7. You can easly find people complaining about it online, from back the android 7/8 era.

 

[eXecu7or]

2020-10-20 - same sound issue for me.

I'm sticking to 2020-10-06 since it's the most stable.

I do have a slight inconvenience whereas after a reboot, the SD card takes some time to activate the apps on it. It generally requires a reinsertion, even thought the storage applet reads it properly and all.

Thank you for your continued effort.

 

[crott]

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!

 

[NeoArian]

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!

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.

 

[crott]

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 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.
This time I tried with pin instead of password.
I'm doing something wrong or there is some issue indeed.

 

[xfranky81]

The broken build server got in again :/
It will be fixed again with the next build, sorry for the inconvenience.

Just to confirm, sound works again out of the box in 20201103