[OFFICIAL] LineageOS 16.0 for Xperia Z3

Search This thread

pgzh

Member
Feb 26, 2013
29
13
I just had another soft reboot and there was no /proc/last_kmsg present.
If I reboot manually however the last_kmsg is present after the reboot! But of course it does only contain information from before the intentional reboot.
So whatever happens seems to prevent last_kmsg from surviving.
What else can I do to get a log? If I reboot to TWRP manually after a soft reset I guess I will only be able to access the log ending with the wanted reboot to TWRP lacking the information about the previous soft reboot. Or am I mistaken here?
 
Last edited:

Mr.Tom_Tom

Senior Member
Feb 16, 2008
181
235
Munich
If I reboot to TWRP manually after a soft reset I guess I will only be able to access the log ending with the wanted reboot to TWRP lacking the information about the previous soft reboot.
Yes, another reboot does not make sense if there is really no last_kmsg available.

Could you please observe the behavior without the MAGISK modules, especially without E(d)xposed. Clean install required unfortunately before we can look further into that issue.
 

pgzh

Member
Feb 26, 2013
29
13
Could you please observe the behavior without the MAGISK modules, especially without E(d)xposed. Clean install required unfortunately before we can look further into that issue.

Of course, I just wiped/reformatted system, data, cache etc. partitions and flashed the latest nightly, nano gapps and su addon.
I did not flash Magisk and will observe.
 
  • Like
Reactions: Mr.Tom_Tom

Mr.Tom_Tom

Senior Member
Feb 16, 2008
181
235
Munich
Persistent logging

Please note, you can enable this option to create persistent logs.

Do not forget to disable this option after completing the debugging. I expect that it consumes a lot of battery, creates significant wear on the storage cells and may leave sensitive data behind.
 

pgzh

Member
Feb 26, 2013
29
13
I just had another soft reboot after the clean install, but this time there actually was a last_kmsg!
Would you please have a look at the attached log?
If it is not useful, I'll enable persistent logging.
Thanks for the support so far!
 

Attachments

  • last_kmsg.txt
    113.8 KB · Views: 11

Mr.Tom_Tom

Senior Member
Feb 16, 2008
181
235
Munich
I just had another soft reboot after the clean install, but this time there actually was a last_kmsg!
Would you please have a look at the attached log?
If it is not useful, I'll enable persistent logging.
Thanks for the support so far!
Thanks a lot, however I did not find any hint in the log so far.
 

pgzh

Member
Feb 26, 2013
29
13
I've got another phenomenon now - my Z3 does not sometimes power off completely and cannot be booted again until I plug in the charger.
Even vol up+power does not reset the phone.
Funny thing is it is enough to plug in the charger for a few seconds, then I can boot again with the power button.
This happens at any charge level, it happens at about 80% battery remaining. After starting again, the phone runs for a few hours without problems.

May I have some kind of hardware fault here? Did somebody else experience something similar before?

Edit: I also noticed that after turning completely off and needing the charger to power up again the phone loses date and time settings. Usually a phone that is turned off will not lose date and time completely, so I guess the phone actually loses power completely. I'm afraid this may really be a serious hardware issue and not caused by software at all.
 
Last edited:

0LDST4R

Senior Member
May 2, 2018
310
221
LE/Germany
I've got another phenomenon now - my Z3 does not sometimes power off completely and cannot be booted again until I plug in the charger.
Even vol up+power does not reset the phone.
Funny thing is it is enough to plug in the charger for a few seconds, then I can boot again with the power button.
This happens at any charge level, it happens at about 80% battery remaining. After starting again, the phone runs for a few hours without problems.

May I have some kind of hardware fault here? Did somebody else experience something similar before?

Edit: I also noticed that after turning completely off and needing the charger to power up again the phone loses date and time settings. Usually a phone that is turned off will not lose date and time completely, so I guess the phone actually loses power completely. I'm afraid this may really be a serious hardware issue and not caused by software at all.


I read all your posts in the last days, i'd think your battery is nearly at the end. I had similar issues with one of my Yugas. ( Xperia Z C6603 ) .
 

pgzh

Member
Feb 26, 2013
29
13
I read all your posts in the last days, i'd think your battery is nearly at the end. I had similar issues with one of my Yugas. ( Xperia Z C6603 ) .

Thanks for sharing this with me. How suddenly did your battery problems start?
I was thinking about my battery beeing bad also, but it is strange I do not get a lot of reboots/poweroffs while using the phone and all of this started happening so frequently out of nothing if it's really the battery.
Anyway I'll get a replacement and check connectors etc inside the phone when replacing.
 

0LDST4R

Senior Member
May 2, 2018
310
221
LE/Germany
Thanks for sharing this with me. How suddenly did your battery problems start?
I was thinking about my battery beeing bad also, but it is strange I do not get a lot of reboots/poweroffs while using the phone and all of this started happening so frequently out of nothing if it's really the battery.
Anyway I'll get a replacement and check connectors etc inside the phone when replacing.


Ok, it started for me with shutdowns at the lower percentage levels, under 40 % f.i. I flashed stock - same result. If the charger was connected it does'nt happened. At the end my Yuga shuts down and rebooted at nearly each battery level, with the phenomen too that it does'nt powered off completely. While not using the phone it does'nt happened, means no use no reboots. Also i can say that the percentage was often displayed irritating, shuts down at 80 %, booted up with 20 % .
 

pgzh

Member
Feb 26, 2013
29
13
Thanks for the more detailed explanation. Sounds very similar to what I am experiencing, but for me it also happens while the phone is not active i.e. screen off.
Still I have ordered a new battery since it seems to get worse quickly, the phone is switching off almost every 2-3 hours now and won't turn on without a charger at all battery levels.
 

pgzh

Member
Feb 26, 2013
29
13
My new battery arrived yesterday and I replaced it yesterday evening.
I encountered two more reboots yesterday evening until I discovered the phone now refuses to charge the battery correctly with one of my chargers, but after a complete charge with another charger I am now reboot-free for a day. The powering off and not turning on issue seems to have disappeared also!
The charger not working anymore is actually a raspberry pi power supply. With it the led turns green, but it does not show as charging in settings and the battery level never goes up. The power supply should deliver 2.5A and works perfectly with my raspberry, I don't know why it is not working after replacing the battery...
And my old battery was definitely defective, it was obviously inflated and had a small spot looking like a burn-mark at the side facing inside the phone. Luckily the phone seems undamaged.

So thanks a lot for the help of you guys and this great ROM! :)
 

0LDST4R

Senior Member
May 2, 2018
310
221
LE/Germany
My new battery arrived yesterday and I replaced it yesterday evening.
I encountered two more reboots yesterday evening until I discovered the phone now refuses to charge the battery correctly with one of my chargers, but after a complete charge with another charger I am now reboot-free for a day. The powering off and not turning on issue seems to have disappeared also!
The charger not working anymore is actually a raspberry pi power supply. With it the led turns green, but it does not show as charging in settings and the battery level never goes up. The power supply should deliver 2.5A and works perfectly with my raspberry, I don't know why it is not working after replacing the battery...
And my old battery was definitely defective, it was obviously inflated and had a small spot looking like a burn-mark at the side facing inside the phone. Luckily the phone seems undamaged.

So thanks a lot for the help of you guys and this great ROM! :)


Ah, glad to hear this, it was the battery. Nice that you could rescue your phone. For a good battery life with your new one i suggest to use a very helpful magisk module, search in magisk manager for "acc" ( advanced charging controller ) developed by @VR25. You can charge to a specified level - over night f.i. - then the charging will be paused until a ( specified ) lower level is reached, then charger kicks in again and so on.

I'm using this module, it really saves the lifespan of your battery.


And now have fun with this great rom. :cool:
 
  • Like
Reactions: santeria27

0LDST4R

Senior Member
May 2, 2018
310
221
LE/Germany
In the past some users report WiFi connection errors to 5 GHz networks because a region problem. I wanna try this the other way, i want general disable connect to 5 GHz networks to test some things. If i remember there was a magisk module and somehow the region was related to the inserted SIM. How to do this?

Thanks in advance.
 
  • Like
Reactions: mer5ad

Mr.Tom_Tom

Senior Member
Feb 16, 2008
181
235
Munich
In the past some users report WiFi connection errors to 5 GHz networks because a region problem. I wanna try this the other way, i want general disable connect to 5 GHz networks to test some things. If i remember there was a magisk module and somehow the region was related to the inserted SIM. How to do this?
Please see the second post of this thread and this post for some more info on wifi country code.

I am not aware of any AOSP based ROM for the Z3 which has VoLTE working yet.
 
  • Like
Reactions: 0LDST4R

Top Liked Posts

  • There are no posts matching your filters.
  • 15
    Disclaimer:
    LineageOS is a free and open-source operating system based on the Android mobile platform. Modifying your device and installing this ROM might cause undesired behavior. You do this at your own risk and under your own responsibility.

    Installation:
    If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP 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 z3

    Download link:
    LineageOS Downloads for z3

    Recommended Google Apps package:
    Open GApps (choose ARM as Platform and 9.0 as Android, use the variant you want. Recommended package: nano)

    Recommended TWRP Recovery
    TWRP build by The Muppets (Updated build: 12Feb2020)

    Official root addon
    LineageOS Extras

    Changelog:
    Changes for z3

    Bug reports:
    How to submit a bug report
    LineageOS GitLab

    Donate to support development:
    Donate via PayPal to NeoArian *** Our main contributor for LineageOS 16 & 17 for Z3 and Z3 Compact ***
    Donate via PayPal to LineageOS

    Thanksgiving
    Thanks to everyone who ever contributed to the custom developement for this device.
    Especially:
    @nailyk
    @rcstar6696
    @Myself5
    @tomascus
    @Diewi
    @xkeita
    @koron393
    @SpiritCroc
    @115ek
    @drakonizer

    Source Code
    The source code of LineageOS is available here.
    The kernel source code for this device is available here.
    The used configuration is lineageos_shinano_leo_defconfig available at arch/arm/configs/lineageos_shinano_leo_defconfig in the kernel source.

    XDA:DevDB Information
    LineageOS 16.0 for Xperia Z3, ROM for the Sony Xperia Z3

    Contributors
    Mr.Tom_Tom, NeoArian
    Source Code: https://github.com/LineageOS

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: 23.5.A.1.291
    Based On: LineageOS

    Version Information
    Status: Nightly

    Created 2020-02-07
    Last Updated 2020-02-07
    8
    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:
      1. Find a large (I tested a 400GB microSDXC card) and fast ("A1" or higher) Micro SD card.
      2. Follow this guide to partition your SD card. Note: all data on the card will be lost.
      3. Restart your phone.
      4. 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.)
      5. 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:
        Code:
        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 @ronnay ryukay for having maintained the inofficial thread!
    8
    ZZZ.......

    Hey guys
    Sorry for not being an active developer these days. No worries please, I plan to continue to work on LOS for our Z3.

    Stay healthy!
    8
    @MrTom_Tom @NeoArian

    It's so great to see an official LineageOS 16 for the old device. Thx so much at both of you for the effort and time which you spending to the z3.

    Hopefully the LineageOS 17.1 will go official some day, too.
    You are welcome. LineageOS 17.1 is in a pretty good shape for z3/z3c. I have built an unofficial version for z3 with February security patch and uploaded it to https://osdn.net/projects/ephedraceae/storage/z3/lineage-17.1/

    It should be in a similar state to 16.0 now. Selinux is enforcing and everything should be working so far.
    4
    Stay tuned

    I've build a new unofficial 17.1 LineageOS ROM with current sources (01 May 2020) and thanks to @ronnay ryukay you can find that here in his thread.

    While this does not address most of the major issues which are described in post #2 here in this thread, we hope it provides a better work-around for the audio issues.

    My current priority remains to refresh the audio subsystem., that's what I am working on right now.