• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][pioneer][11] LineageOS 18.1

Search This thread

malerocks

Senior Member
Mar 6, 2018
437
103
Anyone know why the last build was pulled? I updated to it before it was but everything on my phone is working fine for now. Curious to know if there is anything I need to watch out for.
 

Marek W.

New member
Apr 5, 2021
2
0

VoIP-Apps do not work if WI-Fi Calling is activated


Hello, guys,

if Wi-Fi Calling is activated its not possible anymore to establish SIP/VoIP connections with VoIP-App(s), like LinPhone or FritzFon.


With deactivated Wi-Fi and mobile-connection or with deactivated Wi-Fi Calling anything works fine and its possible get the SIP-Registration. I think this behaviour is since approx. End of May 2021.


/device pioneer /version lineage-18.1 /date 2021-07-15 /kernel 4.4.205-g061f611 /baseband 20200722_BY120_Daily /mods Google Apps

anyone here with the same issue??
 

imska

Senior Member
Aug 7, 2015
201
71
free-droid.com
Oh wow, I also have been wondering for a while already about why signal can't see my photos. Now I can confirm that only pictures > 2.1 megapixels are not working.
Unfortunately, the link does not solve this issue... Is it something with the signal app or with the rom? Telegram can handle bigger pictures, only signal can't...
 

BoernMe

Member
Jul 4, 2019
16
4
Frankfurt
Oh wow, I also have been wondering for a while already about why signal can't see my photos. Now I can confirm that only pictures > 2.1 megapixels are not working.
Unfortunately, the link does not solve this issue... Is it something with the signal app or with the rom? Telegram can handle bigger pictures, only signal can't...
Got the same issue with Threema :-(
 

FishNum153

New member
Sep 21, 2021
1
0
Hey,

I've a problem with the bootloader. Whenever I try to enter bootloader-mode, the devices reboots.
I tried:
adb reboot bootloader, from recovery, via the reboot menu and pressing the volume button during startup.

Does anybody have a suggestion what I can do, to reactivate/reenable the bootloader-mode?

Thank you!!
 

BoernMe

Member
Jul 4, 2019
16
4
Frankfurt
@LuK1337 then this might actually be related to the rom itself?
Getting back to this issue I have a log on a freshly flashed XA2 with just Threema on it and 1 picture taken with the default camera app:
09-21 15:27:07.039 1730 1823 I ActivityTaskManager: Displayed ch.threema.app/.mediaattacher.MediaAttachActivity: +188ms
09-21 15:27:07.052 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
09-21 15:27:07.056 736 736 I android.hardware.power-service-qti: Power setMode: 5 to: 0
09-21 15:27:07.066 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.067 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.069 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.069 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.069 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.070 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.071 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.071 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.071 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.072 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.073 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.073 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.073 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.073 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.075 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.075 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.075 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.075 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.090 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
09-21 15:27:07.096 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.100 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.100 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.100 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.100 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.102 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.103 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.103 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.103 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.111 805 1045 W APM::AudioPolicyEngine: getDevicesForStrategy() unknown strategy: -1
09-21 15:27:07.112 1730 2455 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
09-21 15:27:07.153 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
09-21 15:27:07.161 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.162 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.163 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.163 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.163 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.164 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.164 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.164 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.164 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.165 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.166 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.166 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.166 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.166 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.166 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.167 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.167 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.167 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.180 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
09-21 15:27:07.186 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.190 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.190 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.191 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.191 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.193 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
09-21 15:27:07.194 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
09-21 15:27:07.194 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
09-21 15:27:07.194 3859 4388 D skia : --- codec->getAndroidPixels() failed.
09-21 15:27:07.264 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
09-21 15:27:06.949 0 0 E q6asm_callback: payload size of 8 is less than expected.

Sending the picture to another device using bluetooth file transfer actually causes this issue on the other phone as well. Apparently there is actually something wrong with the jpeg itself pointing it to the direction of the camera app?!
Update:
I tried using different Camera Apps (such as Simple Camera from F-Droid) and the problem is non-existing. Thus I assume that there is something wrong mit the standard "org.lineageos.snap"-app. But surprisingly only in this rom. On my XZ2 Compact the app works just fine. How can this XA2-specific app-problem be fixed?
 
Last edited:
  • Like
Reactions: imska

Webexplr

Senior Member
Hey, I have problem writing data to NFC card (it's actually an e-money card). Phone doesn't have trouble reading the card information via NFC, but it's unable to update data on the chip.

I managed to grab a logcat. Can someone please tell me whether my phone's NFC is broken or something else happened? Thanks in advance.

EDIT
The attached txt file won't show up so I uploaded it on G-Drive here
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    @LuK1337 then this might actually be related to the rom itself?
    Getting back to this issue I have a log on a freshly flashed XA2 with just Threema on it and 1 picture taken with the default camera app:
    09-21 15:27:07.039 1730 1823 I ActivityTaskManager: Displayed ch.threema.app/.mediaattacher.MediaAttachActivity: +188ms
    09-21 15:27:07.052 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:07.056 736 736 I android.hardware.power-service-qti: Power setMode: 5 to: 0
    09-21 15:27:07.066 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.067 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.069 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.069 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.069 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.070 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.071 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.071 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.071 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.072 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.073 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.073 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.073 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.073 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.075 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.075 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.075 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.075 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.090 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:07.096 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.100 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.100 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.100 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.100 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.102 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.103 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.103 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.103 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.111 805 1045 W APM::AudioPolicyEngine: getDevicesForStrategy() unknown strategy: -1
    09-21 15:27:07.112 1730 2455 I system_server: oneway function results will be dropped but finished with status OK and parcel size 4
    09-21 15:27:07.153 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:07.161 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.162 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.163 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.163 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.163 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.164 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.164 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.164 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.164 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.165 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.166 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.166 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.166 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.166 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.166 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.167 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.167 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.167 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.180 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:07.186 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.190 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.190 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.191 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.191 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.193 3859 4388 D skia : libjpeg error 116 <Corrupt JPEG data: 134 extraneous bytes before marker 0xc0> from output_message
    09-21 15:27:07.194 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from output_message
    09-21 15:27:07.194 3859 4388 D skia : libjpeg error 52 <Quantization table 0x00 was not defined> from setjmp
    09-21 15:27:07.194 3859 4388 D skia : --- codec->getAndroidPixels() failed.
    09-21 15:27:07.264 3126 3148 I MediaProvider: Redacting with new FUSE for /storage/emulated/0/DCIM/Camera/IMG_20210921_105422.jpg
    09-21 15:27:06.949 0 0 E q6asm_callback: payload size of 8 is less than expected.

    Sending the picture to another device using bluetooth file transfer actually causes this issue on the other phone as well. Apparently there is actually something wrong with the jpeg itself pointing it to the direction of the camera app?!
    Update:
    I tried using different Camera Apps (such as Simple Camera from F-Droid) and the problem is non-existing. Thus I assume that there is something wrong mit the standard "org.lineageos.snap"-app. But surprisingly only in this rom. On my XZ2 Compact the app works just fine. How can this XA2-specific app-problem be fixed?
  • 9
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    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. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    6
    @LuK1337 I just wanted to say thank you for your great work! Your work makes our phones live longer, and that's worth real money (donation is on it's way ;-))! I am really happy with how my phone works now. Usually you are only hearing from us when something is not working, which is probably not super motivating :)
    4
    [ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]

    However if you want to flash whole firmware package onto both slots, you can follow the guide below:

    1. Download latest firmware with XperiFirm.
    NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
    Code:
    for f in FILE_*; do unzip $f; done
    unzip boot.zip -d boot
    2. Go to the directory where the firmware got downloaded to and remove following files:
    - boot_X-FLASH-ALL-18AE_0x00.hash
    - boot_X-FLASH-ALL-18AE.sin
    - persist_X-FLASH-ALL-18AE_0x00.hash
    - persist_X-FLASH-ALL-18AE.sin
    - system_other_X-FLASH-ALL-18AE_0x00.hash
    - system_other_X-FLASH-ALL-18AE.sin
    - system_other_X-FLASH-ALL-9B8D_0x00.hash
    - system_X-FLASH-ALL-18AE_0x00.hash
    - system_X-FLASH-ALL-18AE.sin
    - system_X-FLASH-ALL-9B8D_0x00.hash
    - userdata_X-FLASH-CUST-18AE.sin
    - vendor_X-FLASH-ALL-18AE_0x00.hash
    - vendor_X-FLASH-ALL-18AE.sin
    - vendor_X-FLASH-ALL-9B8D_0x00.hash
    3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
    4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
    5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
    6. Flash https://androidfilehost.com/?fid=4349826312261712574
    7. Profit?
    4
    As it's already tomorrow and a new build is released, I dare to give a hint:

    dead // 636865636b20746f6d6f72726f77203a5e29
    In the left (input) view, switch the format from binary to hexadecimal.
    3
    So I tried it and it seems to fix the issue. I had now two nights in which the phone charged properly without reboot, while before I had to reboot every evening to make it charge again.

    Please let me know if there is anything else I can do to help debugging!
    Let me know if it still works on April 13th.