[OFFICIAL] LineageOS 17.1 for z3c

Status
Not open for further replies.
Search This thread

tomKater

Member
Jul 29, 2014
33
7
Huawei MediaPad M5 Lite
This occasionally happens to me when flashing the Z3C and other Sony devices. I can usually get round it by taking the following steps in TWRP:
  1. Backup your data partition
  2. Format - not just wipe - the data partition
  3. Flash the new ROM - I usually do it by installing from SD card, but `adb sideload` should work too
  4. Boot the phone and go through the setup wizard app, setting any screen pattern or PIN you had previously.
  5. Restore the backup of your data partition
I hope that helps

Thank you very much ! It was indeed the right procedure !

It saved me a lot of time. Thanks.
 
  • Like
Reactions: petefoth

marcogiannetta

Senior Member
Sep 29, 2012
254
167
Sony Xperia Z3 Compact
Xperia XZ2
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!

It's been a while since last time I did test a new Android version on this smartphone.
First of all, I'd like to thank you all maintainers for your effort and to congratulate for the great work done with this first build of lineage 18.1.
I did some basic testing (don't expect anything too accurate, since this is not my main device for a while) which I'll resume below:
  • Booting was fine and time is quite comparable with previous lineage versions
  • I succesfully installed a test build of OpenGapps (micro configuration of 20210130), which seems to work pretty well
  • account setup and sync works
  • WiFi working at both 2.4/5 GHz
  • Bluetooth working fine, I had no problems connecting to my bluetooth earbuds and listen to some music
  • NearbySharing is working like a charm and quite fast too
  • online charging is working at full speed (about 1800 mA with a quickcharge 3.0 wall charger)
  • MTP working
  • OTG works for both input devices (mouse, keyboard, etc..) or mass storage
  • camera is fully working (taking pictures with both front/rear cameras, taking videos, flash)
  • phone calls are working, but I believe that microphones are swapped, using the upper one as main, resulting in a low volume during calls
  • mobile data is stuck at EDGE for me, I couldn't get it to use LTE instead
  • audio is fine
  • video playback also seems to be fine (tested on youtube at 1080p)
  • chromecast works, in fact I did cast screen and youtube to a Google Nest Hub without any problem
  • the OS is overall responsive and snappy, even with gapps installed
  • screen rotation, accelerometer, gyroscope, proximity sensor, etc.. all fine
  • double tap to wake and other classic gestures are fine
  • I couldn't test hotspot since, as I said, I was stuck at 2G connection which was quite unresponsive
  • unfortunately I cannot test GPS or NFC neither
I hope I did not forget something important.
I'm going to keep this installed since it's really stable, so feel free to ask me for some other testing and I'll for sure try to do that as soon as I have some spare time :)
 

Samare

Member
Nov 6, 2014
43
18
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!

Thank you NeoArian and all other developers!
Your LineageOS 17.1 build really revived this small phone!
My previous experiences with installing unofficial builds were not as great as this one.
The only things I miss compared to stock Android 6 are the camera button full press to open the camera app (which by the way starts slower than on stock Android 6), the secondary mic noise suppression (which wasn't working anymore on mine anyway) and the service tests opened with the *#*#SERVICE#*#* code.

About this new LineageOS 18.1 (I used MindTheGapps-11.0.0-arm-20210412_124103), I didn't notice any problem compared to 17.1.
In fact, using Migrate to restore all apps and settings, I almost thought the update didn't work since it booted like usual.

For the other users, in addition to Migrate, I of course reinstalled Magisk, which doesn't work natively (even with the workaround of installing 20.4 first) on this new 18.1 build. The boot_patch.sh file has to be modified, I've attached a version of Magisk 22.1 with that file already modified (works at least on Z3C). NeoArian: is there any way to modify the builds so that they use init instead of init.real?

I did some basic testing
Pretty extensive "basic testing"!

  • phone calls are working, but I believe that microphones are swapped, using the upper one as main, resulting in a low volume during calls
  • mobile data is stuck at EDGE for me, I couldn't get it to use LTE instead
  • double tap to wake and other classic gestures are fine
  • unfortunately I cannot test GPS or NFC neither
- Phone calls were fine on 17.1, haven't checked yet on 18.1. UPDATE: still fine on 18.1
- LTE works here (at least band 1). I'll see if I can connect to different bands.
I don't know if it helps, but here's what modemcaps says:
========================================
Sony Xperia Z3 Compact
Model ID : z3c
SoC : SDM800
Modem HW : MTP (msm)
Modem FW : 8974-AAAAANAZQ-00112-61
Modem Link : Generation 2 (Channel 0)
Kernel Base : Linux 3.4.113
Kernel Fork : gb76b4a9ae603
Sys Version : Android 11 (armeabi-v7a)
App Version : 2019-12-27-10 (armeabi-v7a)
https://t.me/ru_fieldtest_modemcaps
========================================
SIM Card : Single SIM
LTE CA : Is not supported
LTE Voice : GSM/UMTS CS Fallback
CDMA2000 1X CS Fallback
VoLTE
Radios : 2G GSM
3G UMTS
4G LTE
GSM Bands : B3 (1800 FDD)
B8 (900/E FDD)
B- (900/P FDD)
B5 (850 FDD)
B2 (1900 FDD)
UMTS Bands : B1 (2100 FDD)
B2 (1900 FDD)
B4 (1700 FDD)
B5 (850 FDD)
B8 (900 FDD)
LTE Bands : B1 (2100 FDD)
B2 (1900 FDD)
B3 (1800 FDD)
B4 (2100 FDD)
B5 (850 FDD)
B7 (2600 FDD)
B8 (900 FDD)
B13 (700 FDD)
B17 (700 FDD)
B20 (800 FDD)

- Double tap to wake didn't work for me on stock Android 6 (at least when on deep sleep). It seems to work now which is an improvement.
- GPS works fine.

I'm using it from now on, so I'll report any problem.
 

Attachments

  • Magisk-v22.1_mod_sony.apk
    6.4 MB · Views: 101
Last edited:

wtor68

Member
Nov 4, 2017
16
4
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!
First thank you NeoArian and all other developers involved for your great work! I also did some short tests and found nothing which was not working. I worked with OpenGapps test build of 20210130. I tested:

- WLAN
- Bluethooth
- Mobil date
- phone call
- Camera/Video/flash light
- Audio and video playback
- normal usage like my los 17.1 daily driver

I used some configuration like i did on my los 17.1 daily driver and it looks really good! Unfortunately I cannot test GPS as my test device had an hardware problem here.

So really fine from my side here, only the test with Magisk to root the device didn't work. But this shouldn't be related to los 18.1. Hopefully Magisk will be functional sometimes later.

Thanks again!
 

Aleomar30

New member
Apr 19, 2021
1
0
Hello
I just installed this ROM on my z3c, which has a faulty touch and I use it with a mouse.
The problem is that there is a kind of highlighting on the desktop icons and I don't know why (could it be because of the mouse?)

Thanks in advance !!
 

Attachments

  • Polish_20210418_232820120.png
    Polish_20210418_232820120.png
    910.7 KB · Views: 25
Hello, I installed 18.1 yesterday (oh boy, it was hard and expensive - SIM Lock with 0 attempts) and I'm impressed. I didn't installed GApps as I can't found ARM pack (anyone help me plz 😁). I skipped LOS17.1 so I compare it to stock 6.0 and in my opinion it's noticably faster and battery lasts longer however maybe because I have no GApps.

Tested so far
- WiFi
- Mobile data
- Phone calls (calling and answering)
- Bluetooth (sending/receiving files, earphones, Xbox gamepad, keyboard)
- GPS (not so advanced tests, I'll test it later)
- Camera (photos, video in front and rear cams, flashlight)
- OTG (pendrives and mouse)
- Screenshots
- Receiving SMS, but not sending (inactive number)
- Charging using microUSB and magnetic connector

Not tested yet:
- Hotspot
- NFC
- Screen recording
- Screen mirroring

Found some visual bugs but not sure if it's LOS or Nova Launcher in beta channel so I'll check it and give info later.

I'm waiting for future builds for tests and hope they'll be [OFFICIAL]!
 
  • Like
Reactions: armorgeddon

Samare

Member
Nov 6, 2014
43
18
About this new LineageOS 18.1 (I used MindTheGapps-11.0.0-arm-20210412_124103), I didn't notice any problem compared to 17.1.
In fact, using Migrate to restore all apps and settings, I almost thought the update didn't work since it booted like usual.
I don't think I wiped data which is why everything was already configured.
Maybe that or MindTheGapps explains the wakelocks.
I'll check it again later with the data wipe.

In the mean time, I went back to 17.1 (20210420) where everything is still fine.
 

NeoArian

Recognized Developer
Nov 25, 2017
1,270
2,892
Sony Xperia Z2
Sony Xperia Z3 Compact
Thanks to everyone for the really detailed testing :) I really appreciate it.
Since yesterday (still on 18.1), I have two kernel wakelocks preventing deep sleep:
- msm_serial_hs_dma
- BTLowPower

I used BBS with the adb shell settings put global hidden_api_policy 1 fix to check the wakelocks.
Regarding the BTLowPower wakelock, @J_C_D has fixed that on lineage-17.1 recently and at this time the lineage-18.1 branch was already forked. I will make sure to include the fix for lineage-18.1 with the next update.
 

wtor68

Member
Nov 4, 2017
16
4
Thank you NeoArian and all other developers!
Your LineageOS 17.1 build really revived this small phone!
My previous experiences with installing unofficial builds were not as great as this one.
The only things I miss compared to stock Android 6 are the camera button full press to open the camera app (which by the way starts slower than on stock Android 6), the secondary mic noise suppression (which wasn't working anymore on mine anyway) and the service tests opened with the *#*#SERVICE#*#* code.

About this new LineageOS 18.1 (I used MindTheGapps-11.0.0-arm-20210412_124103), I didn't notice any problem compared to 17.1.
In fact, using Migrate to restore all apps and settings, I almost thought the update didn't work since it booted like usual.

For the other users, in addition to Migrate, I of course reinstalled Magisk, which doesn't work natively (even with the workaround of installing 20.4 first) on this new 18.1 build. The boot_patch.sh file has to be modified, I've attached a version of Magisk 22.1 with that file already modified (works at least on Z3C). NeoArian: is there any way to modify the builds so that they use init instead of init.real?


Pretty extensive "basic testing"!


- Phone calls were fine on 17.1, haven't checked yet on 18.1. UPDATE: still fine on 18.1
- LTE works here (at least band 1). I'll see if I can connect to different bands.
I don't know if it helps, but here's what modemcaps says:
========================================
Sony Xperia Z3 Compact
Model ID : z3c
SoC : SDM800
Modem HW : MTP (msm)
Modem FW : 8974-AAAAANAZQ-00112-61
Modem Link : Generation 2 (Channel 0)
Kernel Base : Linux 3.4.113
Kernel Fork : gb76b4a9ae603
Sys Version : Android 11 (armeabi-v7a)
App Version : 2019-12-27-10 (armeabi-v7a)
https://t.me/ru_fieldtest_modemcaps
========================================
SIM Card : Single SIM
LTE CA : Is not supported
LTE Voice : GSM/UMTS CS Fallback
CDMA2000 1X CS Fallback
VoLTE
Radios : 2G GSM
3G UMTS
4G LTE
GSM Bands : B3 (1800 FDD)
B8 (900/E FDD)
B- (900/P FDD)
B5 (850 FDD)
B2 (1900 FDD)
UMTS Bands : B1 (2100 FDD)
B2 (1900 FDD)
B4 (1700 FDD)
B5 (850 FDD)
B8 (900 FDD)
LTE Bands : B1 (2100 FDD)
B2 (1900 FDD)
B3 (1800 FDD)
B4 (2100 FDD)
B5 (850 FDD)
B7 (2600 FDD)
B8 (900 FDD)
B13 (700 FDD)
B17 (700 FDD)
B20 (800 FDD)

- Double tap to wake didn't work for me on stock Android 6 (at least when on deep sleep). It seems to work now which is an improvement.
- GPS works fine.

I'm using it from now on, so I'll report any problem.
Hello Samare,

i tried your fixed Magisk package for sony z3c but it doesn't install on my device with lineageos 18.1. If i click for install i got the error message that an error occurred at parsing the package. Is there anything to mind to get it installed?

Thanks!
 

Samare

Member
Nov 6, 2014
43
18
Hello Samare,

i tried your fixed Magisk package for sony z3c but it doesn't install on my device with lineageos 18.1. If i click for install i got the error message that an error occurred at parsing the package. Is there anything to mind to get it installed?

Thanks!
I flashed it on TWRP after renaming it to .zip
 
Last edited:

wtor68

Member
Nov 4, 2017
16
4
I flashed it on TWRP after renaming it to .zip
I already tried the TWRP way. Then the app is there but if i click on it, it asked: "upgrade to full magisk manager to finish the setup. Download and install?" I can only say 'cancel' which doesn't help or 'ok' but then i got he same error like before (error occurred at parsing the package). I don't know the problem here. It's only this package, other apk's install without problems.
 

Samare

Member
Nov 6, 2014
43
18
I already tried the TWRP way. Then the app is there but if i click on it, it asked: "upgrade to full magisk manager to finish the setup. Download and install?" I can only say 'cancel' which doesn't help or 'ok' but then i got he same error like before (error occurred at parsing the package). I don't know the problem here. It's only this package, other apk's install without problems.
I'm guessing the flashing finished with no error? Then you could try installing the same file (this time with the .apk extension) inside Android.
 
Last edited:

wtor68

Member
Nov 4, 2017
16
4
I'm guessing the flashing finished with no error? Then you could try installing the same file (this time with the .apk extension) inside Android.
Yes no flash error but same parser error afterwards at installing apk. Now i tried to install the apk by adb. Here i saw some kind of certificate error. So i fixed the apk by zipalign / apksigner and it installed without problems. Root is back now! But i don't know why it works on your side without this...
 
Last edited:

Samare

Member
Nov 6, 2014
43
18
Yes no flash error but same parser error afterwards at installing apk. Now i tried to install the apk by adb. Here i saw some kind of certificate error. So i fixed the apk by zipalign / apksigner and it installed without problems. Root is back now! But i don't know why it works on your side without this...
Indeed, since I modified it the signature wasn't valid anymore.
On 18.1 I didn't wipe data so the older version was already installed.
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    LineageOS 18.1 became OFFICIAL for Xperia Z3 and Xperia Z3 Compact three days ago. This will mean there won't be new official 17.1 builds anymore and the next build will be 18.1! Once the build is available, i will close this thread and a new one will be created for 18.1.

    Cores 0 and 3 are set to 300 MHz minimum and cores 1 and 2 to 1574 but disabled on low load.
    It's correct that the cores are being shut down on low load. The cores are only enabled when they are needed and in that case they usually run at higher frequencies. That is pretty much inteded behaviour.
    3
    Sadly my z3c screen stopped working this morning, still I would like to thank neoarian for all the efforts you put into keeping the z3c alive. I used your work of art for at least since I can remember using my z3c. I briefly considered buying my 4th or 5th z3c, but decided to continue with a XZ2 compact. Have to figure out how to get Los on that phone yet.
    2
    Here is a log of two attempts to uninstall whatsapp:

    Code:
    06-13 15:08:02.524  3266  4080 E LightsService: Light requested not available on this device. 2
    06-13 15:08:02.568  3266  3295 E UserRestrictionsUtils: Unknown restriction queried by uid 1000 (com.android.wallpaperbackup et al): com.whatsapp
    06-13 15:08:02.575 11455 11455 W SettingsMetricsFeature: action(Pair<Integer, Object>... taggedData) is deprecated, Use action(int, int, int, String, int) instead.
    06-13 15:08:02.576  3266  3686 I DropBoxManagerService: add tag=system_server_wtf isTagEnabled=true flags=0x2
    06-13 15:08:02.580  3266  6911 I ActivityTaskManager: START u0 {act=android.intent.action.UNINSTALL_PACKAGE dat=package:com.whatsapp cmp=com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity (has extras)} from uid 1000
    06-13 15:08:02.613  3083  3083 D Zygote  : Forked child process 12398
    06-13 15:08:02.617  3266  3687 I ActivityManager: Start proc 12398:com.google.android.packageinstaller/u0a61 for pre-top-activity {com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity}
    06-13 15:08:02.639  3266  4975 W OomAdjuster: Fallback pre-set sched group to default: not expected top priority
    06-13 15:08:02.735 12398 12398 D AndroidRuntime: Shutting down VM
    06-13 15:08:02.736 12398 12398 E AndroidRuntime: FATAL EXCEPTION: main
    06-13 15:08:02.736 12398 12398 E AndroidRuntime: Process: com.google.android.packageinstaller, PID: 12398
    06-13 15:08:02.736 12398 12398 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity}: java.lang.IllegalArgumentException: Invalid UUID string: 2D4E-501B
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3270)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3409)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:107)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:214)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:7356)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Invalid UUID string: 2D4E-501B
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at java.util.UUID.fromString(UUID.java:194)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.os.storage.StorageManager.convert(StorageManager.java:2290)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at com.android.packageinstaller.handheld.UninstallAlertDialogFragment.getAppDataSizeForUser(UninstallAlertDialogFragment.java:78)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at com.android.packageinstaller.handheld.UninstallAlertDialogFragment.getAppDataSize(UninstallAlertDialogFragment.java:114)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at com.android.packageinstaller.handheld.UninstallAlertDialogFragment.onCreateDialog(UninstallAlertDialogFragment.java:179)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.DialogFragment.onGetLayoutInflater(DialogFragment.java:417)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.Fragment.performGetLayoutInflater(Fragment.java:1351)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1303)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.FragmentManagerImpl.addAddedFragments(FragmentManager.java:2431)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2210)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2166)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2067)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.FragmentManagerImpl.dispatchMoveToState(FragmentManager.java:3057)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java:3004)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.FragmentController.dispatchActivityCreated(FragmentController.java:184)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7831)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7813)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1306)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3245)
    06-13 15:08:02.736 12398 12398 E AndroidRuntime:        ... 11 more
    06-13 15:08:02.739  3266 12426 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
    06-13 15:08:02.739  3266 17628 W ActivityTaskManager:   Force finishing activity com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity
    06-13 15:08:02.746  3266 17628 W ActivityTaskManager:   Force finishing activity com.android.settings/.applications.InstalledAppDetails
    06-13 15:08:02.756 11455 11477 D OpenGLRenderer: endAllActiveAnimators on 0x7a1ec800 (RippleDrawable) with handle 0x7acf8a50
    06-13 15:08:02.757  3266  3686 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
    06-13 15:08:02.758  3266  3686 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
    06-13 15:08:02.765 12398 12398 I Process : Sending signal. PID: 12398 SIG: 9
    06-13 15:08:02.782  3266  8894 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
    06-13 15:08:02.785  3266  4003 I ActivityManager: Process com.google.android.packageinstaller (pid 12398) has died: vis+99 TOP
    06-13 15:08:02.799  3083  3083 I Zygote  : Process 12398 exited due to signal 9 (Killed)
    06-13 15:08:02.812  3266  6878 W ActivityManager: Unable to start service Intent { act=com.android.launcher3.WINDOW_OVERLAY dat=app://com.android.launcher3:10118?v=9&cv=14 pkg=com.google.android.googlequicksearchbox } U=0: not found
    06-13 15:08:02.825  4983  7052 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
    06-13 15:08:02.834  3266  3688 I libprocessgroup: Successfully killed process cgroup uid 10061 pid 12398 in 48ms
    06-13 15:08:02.841  4647  4647 D ImageWallpaper: wallpaper visibility changes to: true
    06-13 15:08:02.911  4647  4663 I ndroid.systemu: NativeAlloc concurrent copying GC freed 3363(317KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 8153KB/15MB, paused 84us total 157.287ms
    06-13 15:08:03.245  3266  3563 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{1b17414 u0 com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity t-1 f}
    06-13 15:08:04.588  3266  3686 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
    06-13 15:08:04.589  3266  3686 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
    06-13 15:08:04.827   323  3314 E qti_sensors_hal: processInd: Unknown message ID = 3
    06-13 15:08:09.636  3266  3728 E LightsService: Light requested not available on this device. 2
    06-13 15:08:10.474  3266  3266 V SettingsProvider: Notifying for 0: content://settings/system/screen_brightness
    06-13 15:08:11.681  3266  6911 I ActivityManager: Killing 16173:com.android.gallery3d/u0a120 (adj 985): empty #17
    06-13 15:08:11.690   343   343 E lowmemorykiller: Error writing /proc/16173/oom_score_adj; errno=22
    06-13 15:08:11.757  3083  3083 I Zygote  : Process 16173 exited due to signal 9 (Killed)
    06-13 15:08:11.777  3266  3688 I libprocessgroup: Successfully killed process cgroup uid 10120 pid 16173 in 90ms
    06-13 15:08:14.827   323  3314 E qti_sensors_hal: processInd: Unknown message ID = 3
    06-13 15:08:18.311  3266  3266 V SettingsProvider: Notifying for 0: content://settings/system/screen_brightness
    06-13 15:08:24.828   323  3314 E qti_sensors_hal: processInd: Unknown message ID = 3
    06-13 15:08:26.079  3266  4080 E LightsService: Light requested not available on this device. 2
    06-13 15:08:26.378  4983  7052 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
    06-13 15:08:26.381  4983  7052 E BufferQueueProducer: [unnamed-4983-12] setMaxDequeuedBufferCount: 2 dequeued buffers would exceed the maxBufferCount (2) (maxAcquired 1 async 0 mDequeuedBufferCannotBlock 0)
    06-13 15:08:26.381  4983  7052 E Surface : IGraphicBufferProducer::setBufferCount(3) returned Invalid argument
    06-13 15:08:27.382  3266 17628 I ActivityTaskManager: START u0 {act=android.settings.APPLICATION_DETAILS_SETTINGS dat=package:com.whatsapp flg=0x10008000 cmp=com.android.settings/.applications.InstalledAppDetails bnds=[468,565][564,661]} from uid 10118
    06-13 15:08:27.408  3266  4003 W ActivityTaskManager: Request to remove task ignored for non-existent task 191
    06-13 15:08:27.408 11455 11455 W ActivityThread: handleWindowVisibility: no activity for token [email protected]
    06-13 15:08:27.434 11455 11455 D SettingsActivity: Starting onCreate
    06-13 15:08:27.472 11455 11455 D SettingsActivity: Starting to set activity title
    06-13 15:08:27.473 11455 11455 D SettingsActivity: Done setting title
    06-13 15:08:27.473 11455 11455 D SettingsActivity: Switching to fragment com.android.settings.applications.appinfo.AppInfoDashboardFragment
    06-13 15:08:27.484 11455 11455 D PrefCtrlListHelper: Could not find Context-only controller for pref: com.android.settings.applications.appinfo.AppNotificationPreferenceController
    
    
    
    06-13 15:08:34.153  3266 29704 I ActivityTaskManager: START u0 {act=android.intent.action.UNINSTALL_PACKAGE dat=package:com.whatsapp cmp=com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity (has extras)} from uid 1000
    06-13 15:08:34.189  3083  3083 D Zygote  : Forked child process 12510
    06-13 15:08:34.192  3266  3687 I ActivityManager: Start proc 12510:com.google.android.packageinstaller/u0a61 for pre-top-activity {com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity}
    06-13 15:08:34.215  3266  6911 W OomAdjuster: Fallback pre-set sched group to default: not expected top priority
    06-13 15:08:34.296 12510 12510 D AndroidRuntime: Shutting down VM
    06-13 15:08:34.299 12510 12510 E AndroidRuntime: FATAL EXCEPTION: main
    06-13 15:08:34.299 12510 12510 E AndroidRuntime: Process: com.google.android.packageinstaller, PID: 12510
    06-13 15:08:34.299 12510 12510 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity}: java.lang.IllegalArgumentException: Invalid UUID string: 2D4E-501B
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3270)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3409)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:83)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.os.Handler.dispatchMessage(Handler.java:107)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.os.Looper.loop(Looper.java:214)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.ActivityThread.main(ActivityThread.java:7356)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at java.lang.reflect.Method.invoke(Native Method)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime: Caused by: java.lang.IllegalArgumentException: Invalid UUID string: 2D4E-501B
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at java.util.UUID.fromString(UUID.java:194)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.os.storage.StorageManager.convert(StorageManager.java:2290)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at com.android.packageinstaller.handheld.UninstallAlertDialogFragment.getAppDataSizeForUser(UninstallAlertDialogFragment.java:78)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at com.android.packageinstaller.handheld.UninstallAlertDialogFragment.getAppDataSize(UninstallAlertDialogFragment.java:114)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at com.android.packageinstaller.handheld.UninstallAlertDialogFragment.onCreateDialog(UninstallAlertDialogFragment.java:179)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.DialogFragment.onGetLayoutInflater(DialogFragment.java:417)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.Fragment.performGetLayoutInflater(Fragment.java:1351)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1303)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.FragmentManagerImpl.addAddedFragments(FragmentManager.java:2431)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2210)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2166)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2067)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.FragmentManagerImpl.dispatchMoveToState(FragmentManager.java:3057)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java:3004)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.FragmentController.dispatchActivityCreated(FragmentController.java:184)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7831)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.Activity.performCreate(Activity.java:7813)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1306)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:3245)
    06-13 15:08:34.299 12510 12510 E AndroidRuntime:        ... 11 more
    06-13 15:08:34.302  3266  4975 W ActivityTaskManager:   Force finishing activity com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity
    06-13 15:08:34.303  3266 12532 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
    06-13 15:08:34.312  3266  4975 W ActivityTaskManager:   Force finishing activity com.android.settings/.applications.InstalledAppDetails
    06-13 15:08:34.322  3266  3560 I ActivityManager: Showing crash dialog for package com.google.android.packageinstaller u0
    06-13 15:08:34.322  3266  3560 E system_server: Invalid ID 0x00000000.
    06-13 15:08:34.322  3266  3686 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
    06-13 15:08:34.322  3266  3686 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
    06-13 15:08:34.335 11455 11477 D OpenGLRenderer: endAllActiveAnimators on 0x7914b180 (RippleDrawable) with handle 0x7acf8610
    06-13 15:08:34.360  3266  8894 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
    06-13 15:08:34.423  3266  3560 W Looper  : Slow dispatch took 106ms android.ui h=com.android.server.am.ActivityManagerService$UiHandler c=null m=1
    06-13 15:08:34.811  3266  3563 W ActivityTaskManager: Activity top resumed state loss timeout for ActivityRecord{4ea65e7 u0 com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity t192 f}
    06-13 15:08:34.812  3266  3563 W ActivityTaskManager: Activity pause timeout for ActivityRecord{4ea65e7 u0 com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity t192 f}
    06-13 15:08:34.437  3266  8894 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
    06-13 15:08:34.827   323  3314 E qti_sensors_hal: processInd: Unknown message ID = 3
    06-13 15:08:34.840  3266  4003 W ActivityManager: Unable to start service Intent { act=com.android.launcher3.WINDOW_OVERLAY dat=app://com.android.launcher3:10118?v=9&cv=14 pkg=com.google.android.googlequicksearchbox } U=0: not found
    06-13 15:08:34.856  4983  7052 W Adreno-EGL: <qeglDrvAPI_eglGetConfigAttrib:607>: EGL_BAD_ATTRIBUTE
    06-13 15:08:34.872  4647  4647 D ImageWallpaper: wallpaper visibility changes to: true
    06-13 15:08:35.392   313   313 D lights.msm8974: led [solid] = ffffff00
    06-13 15:08:35.497  3266  3685 W ProcessCpuTracker: Failed to stat(/proc/12549): android.system.ErrnoException: stat failed: ENOENT (No such file or directory)
    06-13 15:08:35.497  3266  3685 W ProcessCpuTracker: Skipping unknown process pid 12549
    06-13 15:08:35.498  3266  3685 W ProcessCpuTracker: Failed to stat(/proc/12550): android.system.ErrnoException: stat failed: ENOENT (No such file or directory)
    06-13 15:08:35.498  3266  3685 W ProcessCpuTracker: Skipping unknown process pid 12550
    06-13 15:08:35.498  3266  3685 W ProcessCpuTracker: Failed to stat(/proc/12552): android.system.ErrnoException: stat failed: ENOENT (No such file or directory)
    06-13 15:08:35.498  3266  3685 W ProcessCpuTracker: Skipping unknown process pid 12552
    06-13 15:08:35.499  3266  3685 W ProcessCpuTracker: Failed to stat(/proc/12553): android.system.ErrnoException: stat failed: ENOENT (No such file or directory)
    06-13 15:08:35.499  3266  3685 W ProcessCpuTracker: Skipping unknown process pid 12553
    06-13 15:08:36.188  3266  3686 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
    06-13 15:08:36.189  3266  3686 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
    06-13 15:08:37.234  3266  4975 W ActivityTaskManager:   Force finishing activity com.google.android.packageinstaller/com.android.packageinstaller.UninstallerActivity
    I would shamelessly blame the google apps you installed. Try to report it to the one who made the gapps you used.
    Sorry for the oversight, I had started with 16.0 and related files, and somehow missed that the link had been changed to reference an updated TWRP.

    This is to confirm that, after updating the TWRP inside TWRP, the recent OTA went smoothly, thanks!

    (Is there a specific reason why there are no updates in twrp.me anymore, with the device still listed as supported? Will there be another upgrade to 3.5.0 provided by someone?)
    There are no updates at twrp.me because there is no active maintainer for z3c. I don't continue my twrp build either because lineage recovery does all that's needed.
    @NeoArian I've noticed with Kernel Adiutor that the CPU minimum frequency was set to 1574 MHz instead of 300, making the phone get hotter (and the battery draining faster) than it should when simply browsing a website.
    Is it intended?
    That is not intended and i can not reproduce that. Are the frequencies stuck the whole time or just in specific cases?
    From my z3c:
    Code:
    z3c:/ # cat sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
    300000
    z3c:/ # cat sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq
    300000
  • 12
    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!
    9
    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
    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?
    Yes, i will take a look into the kernel patches soon.
    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?
    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.
    What kind of problems do you talk about with magisk?
    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.
    I can not reproduce the issue about uninstalling apps on a build without gapps. Could you get a log of that?
    I'm sorry about the screen timeout issue, but i currently don't have the time to look into it, the main focus lies on device specific issues and an official release of 18.1.
    5
    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?
    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.