[Xperia Z3 Original Android Development] Mr.Tom_Tom:
Remarks, Questions & Answers

Known Major Issues

Official Lineage Recovery is currently broken. There are two options:

TWRP recovery (inofficial build, optional): TWRP

Unofficial Lineage Recovery build.

WiFi issues in some countries (e.g. Iran): low speed @ 5GHz, hotspot and connection issues. This topic is related to a dirty workaround. A solution is here but will not be integrated into our official Lineage kernel.

Disk Encryption: Disk Encryption is working, however not with the default password (no password). Workaround: Set password first, then start disk encryption, not the other way round! Solved

Bluetooth Low Power may create wakelocks in certain scenarios.* Solved

Thermal throttling of CPU cores: Due to a design issue of the thermal manager ("Thermanager") when used with older kernels like ours you have to expect that the frequency throttling of the CPU cores may fail, especially after(!) the device was getting hot and is recovering. This may lead to performance issues until reboot and other issues. Workaround: reboot device after heavy use.*

Reported size of adoptable storage seems to be wrong. However, remaining free space seems to be reported accurately.

Formating a SD card as internal storage may cause the card to be reported as "corrupted".

Screen rotation may not work after a while. Solved, to be integrated into builds from mid April 2021 onwards.

You tell us (with logs please)...

* To our knowledge, these are general issues on all AOSP/LineageOS based custom ROMs for this device family (Shinano). However I would be happy to be mistaken here and if sombody has a solution.

Further hints

This ROM currently does not work with the Z3 Dual SIM variant. Here's a build for the Z3dual.

If you need Google Apps we recommend the OpenGApps "nano" package, however, I personally use the "stock" package which works as well. The ROM also seems to work with MicroG and BiTGApps.

Magisk - see this post for issues with latest Magisk versions

If you need to install a lot of apps you may run out of internal DATA storage capacity, especially if you install one of the larger GAPPS packages. These apps are initially placed on the system partition and do not cost you DATA capacity. However, every update which comes over the Play Store then fills up your data partition. Using an SD card formated as "external" storage does not help you much (unless you use a tool like app2sd which is no more recommended) and isn't encrypted. Formating the SD card as "adoptable storage" comes with the drawback that some apps do not allow to be migrated to this storage, and unfortunately this is true for some streaming music/video apps which need to store a lot of data obviously (for offline use). The solution I am using is to partition a SD card as "mixed", which gives you the possibility to offload at least some apps to adoptable storage while you still have a classical external FAT32 partition where e.g. your streaming app can save its offline files:

Find a large (I tested a 400GB microSDXC card) and fast ("A1" or higher) Micro SD card.

Follow this guide to partition your SD card. Note: all data on the card will be lost.

Restart your phone.

When you are notified that a new storage card has been detected, use it as "external". (Your internal partition has been recognized at that point already and does not need interaction.)

Go to settings / Storage. Verify that you see three entries: 1. Your internal phone storage of 16GB. This includes your SYSTEM partition. 2. Your SD card with an SD card symbol. The size shown should be the full capacity of the card. If you click on it, your "external" partition is shown (misleading) as "System" and blocked. Click on migrate data to migrate all possible apps to your adoptable storage. 3. Your sd card partition formated as mobile storage (unencrypted!).

How to create logs:

Follow How To Logcat

When creating a log, can you make sure you run the command with the -b option to include kernel messages:

adb logcat -b all

If your device randomly reboots:

Go to Settings -> System -> Advanced -> Developer options -> Store logger data persistently on device. After the reboot occured: Pull the logs from /data/misc/logd/ (root required).

If your device crashes during boot and reboots to recovery:

adb pull /proc/last_kmsg

Please submit logs from clean systems without "Exposed" or similar modifications in place

Your feedback is wanted regarding the following topics

Please have a look at lineage-18.1!

A big THANK YOU also to @ronnay ryukay for having maintained the inofficial 17.1 thread!