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

Known Major Issues

Audio quality during voice calls: Voice calls in handset mode are still too loud. Resolved with lineage-16.0-20200210-nightly-z3

FM Radio buggy: Slow scanning, FM radio is not always starting correctly. We are not working on that right now. Workaround: Let the phone do the initial scan for ~30 min or so, than you can use it.

WiFi issues (low (?) speed @ 5GHz, hotspot): This topic is related to a dirty workaround. We are aware of the issue (since years) but don't have a better solution atm.

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!

VOIP: Mic not working when on hands-free mode. Affected apps e.g. WhatsApp, Google Duo, Skype. Work-around:

Modify file /system/vendor/etc/audio_effects.xml according to this change (delete two lines).

You need write access to /system. I recommend using ADB during TWRP recovery mode to perform that. You need to mount /system beforehand in TWRP.

This disables the default Echo Compensation and Noise Suppression effects. With the current setup, they are not working anyways (NS/AEC is handled differently). This does not affect normal voice calls, as they are not used for voice-calls anyways.

Bluetooth Low Power may create wakelocks in certain scenarios. Not yet tested that myself, but seems to affect the whole shinano family since a long time already.

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. This issue seems to be present since years with our open source custom ROMs.

GNSS: GLONASS and BEIDOU not working correctly --> will be fixed with LOS17.1

You tell us (with logs please)...

More detailed test log here

Further hints

If you need Google Apps we recommend the "nano" package, however, I personally use the "stock" package which works as well.

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

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

Details on any WiFi issues - please state your country & used frequency channels (if possible). Please test and report if the situation gets better with the MAGISK module linked below.

A big THANK YOU also to [MENTION=9647158]ronnay ryukay[/MENTION] for having maintained the inofficial thread!