• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[OFFICIAL] LineageOS 17.1 for z3c

Status
Not open for further replies.
Search This thread

pawloland

Senior Member
Jan 23, 2019
183
71
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

Member
Nov 23, 2008
47
10
@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.
 
Last edited:

L.Lmar

Member
Aug 4, 2016
12
4
@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.
Magisk 20.4 flashable zip, can be updated to the latest via the app, but it seems versions after 20.4 do not survive LOS updates. Magisk app v.22 is fine
p.s. Need to push sdcard quite deep so that it snaps into place
 
  • Like
Reactions: armorgeddon

MxUltra

Member
Feb 7, 2010
8
0
Hi, it might be a bit off topic.
I just tried 17.1 on my z3c and noticed that some of my apps for work do not work on Android 10, so I wanted to go back to 16.0 but i don't have the zip file anymore. As I could not find a recent download for 16.0 I wanted to ask if someone still had recent version?
I think I had lineage-16.0-20200901-nightly-z3c-signed.zip (I think it was the last 16.0 Version) so if someone could upload it or point me to a download link it would be very appreciated.

regards
 

steve8x8

Senior Member
Jul 7, 2014
398
136
Samsung Galaxy S4 Mini
OnePlus One
Hi, it might be a bit off topic.
I just tried 17.1 on my z3c and noticed that some of my apps for work do not work on Android 10, so I wanted to go back to 16.0 but i don't have the zip file anymore. As I could not find a recent download for 16.0 I wanted to ask if someone still had recent version?
I think I had lineage-16.0-20200901-nightly-z3c-signed.zip (I think it was the last 16.0 Version) so if someone could upload it or point me to a download link it would be very appreciated.

regards
You have a PM... For all others: there's still a microG version (only a bit older) on https://download.lineage.microg.org/z3c/
 
  • Like
Reactions: MxUltra

Samare

Member
Nov 6, 2014
43
17
Just as with other Android 9 and 10 roms, I had heavy battery drain because of the media.extractor process.
https://forum.xda-developers.com/t/10-official-carbonrom-cr-8-0-z3c.4047649/post-84715425

I worked around it by killing it at boot with a simple Tasker profile (Edit: I added a two minutes delay to make sure the process is already started) :
<TaskerData sr="" dvi="1" tv="5.9.3">
<Profile sr="prof2" ve="2">
<cdate>1616707624817</cdate>
<edate>1617276057191</edate>
<flags>8</flags>
<id>2</id>
<mid0>3</mid0>
<nme>Kill media.extractor</nme>
<Event sr="con0" ve="2">
<code>411</code>
<pri>0</pri>
</Event>
</Profile>
<Task sr="task3">
<cdate>1616707684454</cdate>
<edate>1617276057191</edate>
<id>3</id>
<pri>100</pri>
<Action sr="act0" ve="7">
<code>30</code>
<Int sr="arg0" val="0"/>
<Int sr="arg1" val="0"/>
<Int sr="arg2" val="2"/>
<Int sr="arg3" val="0"/>
<Int sr="arg4" val="0"/>
</Action>
<Action sr="act1" ve="7">
<code>123</code>
<Str sr="arg0" ve="3">killall media.extractor</Str>
<Int sr="arg1" val="0"/>
<Int sr="arg2" val="1"/>
<Str sr="arg3" ve="3"/>
<Str sr="arg4" ve="3"/>
<Str sr="arg5" ve="3"/>
</Action>
</Task>
</TaskerData>

Like mentioned, we currently have to use Magisk 20.4 to root it.
The best way is to install LineageOS then Magisk 20.4 and finally Magisk 22 all through recovery.

Edit: I finally identified the problematic file, a 70 MB opus file.
 
Last edited:
  • Like
Reactions: armorgeddon

Samare

Member
Nov 6, 2014
43
17
Hey guys,

Does anyone have cell service issues - no service in spite of the phone recognizing the SIM card and even the network?

Thanks.
No problem here.
It may be obvious, but do you have enough credit?
Did it work just before flashing this rom?
You could make a nandroid backup on the micro sdcard and try the original Android 6 one.
 

mcsly100

Member
Mar 25, 2021
7
0
No problem here.
It may be obvious, but do you have enough credit?
Did it work just before flashing this rom?
You could make a nandroid backup on the micro sdcard and try the original Android 6 one.
Yes, everything worked fine on the stock rom, but unfortunately I have no backup of that, so I installed CM 12.1 and it seems to have no such problem either (I wouldn't mind having 17.1 though)...
 

NeoArian

Recognized Developer
Nov 25, 2017
1,270
2,891
Sony Xperia Z2
Sony Xperia Z3 Compact
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!
 
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

Do we expect all to work?
 

NeoArian

Recognized Developer
Nov 25, 2017
1,270
2,891
Sony Xperia Z2
Sony Xperia Z3 Compact
Hello everyone,

when I'm doing system updates after the installation process is completed the file is not deleting automaticly.
Then I need to manually boot into trwp and delete the system update file there.
My Phone is not rooted.
What can I do that the update file where deleted automaticly?

Best regards
Sepp

You can enable that updates should be deleted after installation in the Updater. You can find it in settings -> system ( -> advanced ) -> Updater -> three dots -> preferences -> Delete updates when installed.
 

tomKater

Member
Jul 29, 2014
33
7
Huawei MediaPad M5 Lite
Hello,

I need some help.

I did the update 20210413 today with OTA system. Unfortunately, after the flash, the phone reboots in bootloop (the lineageos logo turn a while and after that it reboots in recovery mode, in twrp).

I tryied to flash manually the previous version (20210330), same behavior

It's not the first time I have this issue after update with OTA system. This time, I did a backup in twrp BEFORE update (boot, system and data). Strangely, when I do a restore with this backup, I'm in bootloop again (the difference is the bootloop is endless this time, no go back to recovery automatically).

Do you have a solution for me ? I would like to avoid flashing from scratch and setup again all my phone :(
 
Hello,

I need some help.

I did the update 20210413 today with OTA system. Unfortunately, after the flash, the phone reboots in bootloop (the lineageos logo turn a while and after that it reboots in recovery mode, in twrp).

I tryied to flash manually the previous version (20210330), same behavior

It's not the first time I have this issue after update with OTA system. This time, I did a backup in twrp BEFORE update (boot, system and data). Strangely, when I do a restore with this backup, I'm in bootloop again (the difference is the bootloop is endless this time, no go back to recovery automatically).

Do you have a solution for me ? I would like to avoid flashing from scratch and setup again all my phone :(
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
 
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.