[CLOSED][OFFICIAL] LineageOS 17.1 for z3c

[tomKater]

Thank you!
Fortunately, in contrast to Version 2, where I had to fully re-implement some parts of the power management, this fix now only requires 3 lines of source code change in total

Hi,

Good job ! Thank you for you efforts. Now looking forward to having the correction by OTA.
I investigate my battery drain for a while now and there is another wakelock that often appears : "mmc0:0001:2".
I could not determine what this was due to. It appears during the night, without action from my part. Only one post on xda found, and no solution.

Does anyone have the same ?

 

[L.Lmar]

@tblr0ne , @L.Lmar : can you please also test this version?

This version is good too

 

[Spaceoid]

Hi,

Good job ! Thank you for you efforts. Now looking forward to having the correction by OTA.
I investigate my battery drain for a while now and there is another wakelock that often appears : "mmc0:0001:2".
I could not determine what this was due to. It appears during the night, without action from my part. Only one post on xda found, and no solution.

Does anyone have the same ?

When I still used the Z3C I had the same wakelock, back on LOS 16. Another user told me this:

https://xdaforums.com/t/9-lineageos-16-0-for-z3c.3886777/post-79782864

 

[tomKater]

When I still used the Z3C I had the same wakelock, back on LOS 16. Another user told me this:

https://xdaforums.com/t/9-lineageos-16-0-for-z3c.3886777/post-79782864

Thank you for this information. I'm a little suprised by the answer, since this wakelock has the consequence of keeping the phone in "awake" status, but I will pay attention to the possible battery drain or not.

 

[NeoArian]

Some bugs appeared on the last 3 updates. Reflashing did not fix the problems. I have no gaps installed, root.
The problem appears when I enable Safe Start, when the device is encrypted.
1. Accelerometer sensor, autoprotect, proximity does not work.
2. When turning on the phone, a long startup before the screen where you must enter the password is displayed. Usually the first startup should be faster, asking for the password.
The problem lies somewhere in the encryption of the device, in the option Safe start.

Am I understanding the issue correctly, that only when your device is encrypted and when booting to safe mode the sensors are not working correctly for you?
At the end of December we have indeed merged a patch to stat the sensors service on late_start in order to fix some issues with encrypted devices (encrypted devices without an actual password/pin set did not boot previously).

 

[versus2165897]

Am I understanding the issue correctly, that only when your device is encrypted and when booting to safe mode the sensors are not working correctly for you?
At the end of December we have indeed merged a patch to stat the sensors service on late_start in order to fix some issues with encrypted devices (encrypted devices without an actual password/pin set did not boot previously).

Yes, that's right.
When Safe Start is turned on, the accelerometer does not work. Therefore, screen rotation, light sensor does not work.

 

[Zwulfulfsn]

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.

 

[NeoArian]

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.

 

[crpdvv]

Will it be possible to apply this kernel patch to official LineageOS 17.1 z3c build:

VPN mode not working due to missing kernel patches (#2193) · Issues · LineageOS / issues / android · GitLab

Expected Behavior Application that provide a VPN mode to work such as the Orbot app....

gitlab.com

To fix this problem with orbot:

Fails to bootstrap with VPN mode enabled (oreo?) · Issue #151 · guardianproject/orbot

Recently installed android 8(.1) on a device. Orbot works fine, until VPN mode is enabled - then, it never bootstraps at all. Disabling VPN mode makes bootstraping work again, and connectivity is t...

github.com

Or was the patch already applied?
I still have this problem with orbot with latest 17.1 build:
lineage-17.1-20210223-nightly-z3c-signed.zip

 

[mindyabiznis]

Hey @NeoArian is there any possibility at all of adding dualshock4 Bluetooth compatibility to this?

Thee ps4 remote play app is telling me that it's not compatible but I thought android 10 supported it natively.

 

[NeoArian]

Hey @NeoArian is there any possibility at all of adding dualshock4 Bluetooth compatibility to this?

Thee ps4 remote play app is telling me that it's not compatible but I thought android 10 supported it natively.

I have just tried to connect a dualshock 4 controller via bluetooth to my phone and it worked just fine. On my newer devices it's possible to use the trackpad as mouse input, that was not possible but apart from this it works good for me. Is it not connecting at all for you or is your issue that the trackpad is not working?

 

[mindyabiznis]

Edit double post

 

[mindyabiznis]

I have just tried to connect a dualshock 4 controller via bluetooth to my phone and it worked just fine. On my newer devices it's possible to use the trackpad as mouse input, that was not possible but apart from this it works good for me. Is it not connecting at all for you or is your issue that the trackpad is not working?

It tells me my device is not dualshock 4 compatible when I go into the remote play app.

The controller pairs with the phone and it seems to work on the phones UI but not in the remote play app.

Do you have a ps4 and the remote play app works?

 

[NeoArian]

It tells me my device is not dualshock 4 compatible when I go into the remote play app.

The controller pairs with the phone and it seems to work on the phones UI but not in the remote play app.

Do you have a ps4 and the remote play app works?

My brother has a ps4 but i do not use google services on my z3c and hence the remote play app doesn't start for me. What do you need the app for? Don't you intend to use the controller for games on your phone?

 

[mhanbury]

Hi, Can someone please confirm if Ant+ sensors are supported on this ROM and if the Ant service hal is installed as a system app?

 

[J_C_D]

Just a note on the LineageOS for MicroG build variant that I want to share here:

AFAIK, MicroG Core versions 0.2.16 and 0.2.17 are having a bug related to Google / Firebase Cloud Messaging (GCM/FCM) which prevents Apps from initially registering for Cloud Messaging.

So, if you install this ROM for the first time, you should use an older release that has MicroG core version 0.2.15 bundled.
Then, install your Apps, allowing them to register for Cloud Messaging. If that succeeded, you can upgrade the ROM to the latest release of LineageOS for MicroG. Cloud Messaging registration will stay intact in this case.

 

[steve8x8]

MicroG Core versions 0.2.16 and 0.2.17

Can someone provide a translation to NanoDroid versions? I.e., is 23.1.2.20210117 affected by this, and which version isn't?

 

[armorgeddon]

Hi guys,
before opening the bootloader on my newly bought Z3 Compact in order to run LOS 17.1 then I'd like to ask the following question: Is it still even possible to backup the device's DRM keys from the TA partition? In case it's still possible is there an up-to-date how-to available somewhere? All I found seemed outdated to me. In case DRM key backup is still possible I wonder if it's still needed at all since reading across this forum and a German one I got the impression that at least in the past LineageOS had implemented something which basically out of the box gives near Stock-ROM-camera-quality which is all I care about in regards to the DRM issue. So is that still the case or did Sony intervene in the meantime and prevent that?
Thanks very much for reading!

 

[pawloland]

Hi guys,
before opening the bootloader on my newly bought Z3 Compact in order to run LOS 17.1 then I'd like to ask the following question: Is it still even possible to backup the device's DRM keys from the TA partition? In case it's still possible is there an up-to-date how-to available somewhere? All I found seemed outdated to me. In case DRM key backup is still possible I wonder if it's still needed at all since reading across this forum and a German one I got the impression that at least in the past LineageOS had implemented something which basically out of the box gives near Stock-ROM-camera-quality which is all I care about in regards to the DRM issue. So is that still the case or did Sony intervene in the meantime and prevent that?
Thanks very much for reading!

DRM keys are still on your phone if previous owner didn't tinker with it before, or if he backed them up, and restored them properly. These keys are only functional on stock ROM, they will do nothing on custom rom, or they will even break things on custom rom, because they aren't meant to be there (I am not sure about that, never tried it). You can follow old guides, this phone is old, so the guides are also old, but not outdated - there wasn't any new stock updata since android MM. Wether it is needed or not, I would say it is not needed if you plan to use only custom roms and never come back to stock, but if you want to go back to stock at some point for wathever reason, you would need TA backup, to have the exact same experience as before unlocking bootloader. If you don't do TA backup, you will lose your unique DRM keys forever. Personally I would back them up, because it doesn't cost anything and can come in handy in the future.

 

[armorgeddon]

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