[ROM][OFFICIAL] LineageOS for Samsung Galaxy S5 LTE+ (G901F) / LTE-A (G906S/K/L)

Search This thread

Nachtbaron

Member
Mar 15, 2020
11
1
Guys, I need your help!

I installed Lineage 16 for kccat6 (the last official nightly build of Feb. 21) following the instructions of a youtube video. What I did: Activated USB-Debugging -> Download Mode -> flashing TWRP 3.2.3-0 via Odin 3.13.1 -> Wipe to factory reset -> installing Lineage and Gapps (ARM 9.0 Pico)

Everything worked like in the video, but Lineage was stuck in the booting screen. So I did a complete wipe and installed Lineage again (maybe that was a mistake). Everything worked out fine, but some time after I did all the settings and installed all of my apps, I tried to make a restart and suddenly I was stuck in a boot loop. So I redid everything, but after a while my phone just turns off and the boot loop appears again. Till that point Lineage is working fine btw.

Of course I did backup of Stock ROM with TWRP before starting the process, but it didn´t help. Then I downloaded and flashed Stock ROM with Odin, but after the Samsung logo there is a boot loop again...
I´m really desperate now. Any ideas how to escape this issue?
 
Last edited:

maanteel

Senior Member
Apr 19, 2015
103
48
  • Like
Reactions: Nachtbaron

Nachtbaron

Member
Mar 15, 2020
11
1
Thanks for you quick answer, but I´m a little bit confused. I flashed Stock ROM with Odin, but Lineage with TWRP.
So you recommend to flash Stock ROM with TWRP now?
 

Nachtbaron

Member
Mar 15, 2020
11
1
Update: I tried everything again and now I don´t even get in recovery anymore (neither TWRP nor official one). Only Download Mode is working. So it´s getting worse every time I try, though I didn´t do anything differently or wrong! Even reflash of Stock ROM and/or TWRP doesn´t work.

I´m waiting now and hope there´s somebody, who can help me out.
 

ripee

Recognized Developer / Recognized Contributor
Aug 25, 2014
3,602
6,626
drive.google.com
You're welcome! I started a new job last December which has given me next to no time to work on custom roms. Next month I will be even more busy, but I'd hate to forget how to work on all this fun hacky stuff, so I'll be posting new builds whenever possible.

I'll run twrp-3.6.1_9-0-kccat6 as well but no promises when it'll be available.

Edit: twrp-3.6.1_9-0-kccat6 is up, both img and tar, in the .TWRP folder on the Google Drive linked in my profile. I didn't run a new twrp for lentislte as teamwin managed to build it from the official sources.
 
Last edited:

Marvin732

Senior Member
You're welcome! I started a new job last December which has given me next to no time to work on custom roms. Next month I will be even more busy, but I'd hate to forget how to work on all this fun hacky stuff, so I'll be posting new builds whenever possible.

I'll run twrp-3.6.1_9-0-kccat6 as well but no promises when it'll be available.

Edit: twrp-3.6.1_9-0-kccat6 is up, both img and tar, in the .TWRP folder on the Google Drive linked in my profile. I didn't run a new twrp for lentislte as teamwin managed to build it from the official sources.
Even though it is "only" LineageOS 16, i am very thankful for the dedication to update the ROM :)
I think there hasn't been much progress in finding the culprit for the boot problem in LOS 18.1?
Even so, thank you for the update :D
 
  • Like
Reactions: maanteel

JustJamesDev

New member
Sep 15, 2020
3
0
I just built the latest LOS 16 source for kccat6, and all seems fine but the fingerprint scanner doesnt work/respond. Has anyone else had this issue or any ideas?
 

bege10

Senior Member
May 26, 2018
223
61
Germany
Edit: twrp-3.6.1_9-0-kccat6 is up, both img and tar, in the .TWRP folder on the Google Drive linked in my profile.
Thank you very much for maintaining TWRP for this device!
With 3.6.1 OTA updates of /e/OS (based on LineageOS for microG) fail. When booting to recovery the TWRP UI opens and nothing more happens. No update, no error, nothing.
After reflashing 3.6.0 the update works as it did before.
 
  • Like
Reactions: maanteel

bege10

Senior Member
May 26, 2018
223
61
Germany
Update: I tried everything again and now I don´t even get in recovery anymore (neither TWRP nor official one). Only Download Mode is working. So it´s getting worse every time I try, though I didn´t do anything differently or wrong! Even reflash of Stock ROM and/or TWRP doesn´t work.

I´m waiting now and hope there´s somebody, who can help me out.
I don't know whether you still search for an answer.
On my kccat6 this works if nothing else works:
- install stock ROM in download mode with ODIN, boot into system
- install TWRP in download mode with ODIN (immediately reboot to recovery)
- flash LineageOS-based ROM with TWRP

Note: TWRP 3.6.1 doesn't work here.
 

m6rcomoto

New member
Jun 23, 2022
2
2
I don't know whether you still search for an answer.
On my kccat6 this works if nothing else works:
- install stock ROM in download mode with ODIN, boot into system
- install TWRP in download mode with ODIN (immediately reboot to recovery)
- flash LineageOS-based ROM with TWRP

Note: TWRP 3.6.1 doesn't work here.
I´ve got the same problem as Nachtbaron with twrp-3.6.1_9-0-kccat6, lineage-16.0-20220418-UNOFFICIAL-kccat6.zip and open_gapps-arm-9.0-pico-20220215

Everything works fine at first, getting through Google and LineagOS menus. The LineageOS desktop appears fine, but then after a few seconds the phone gets into a bootloop.

-- EDIT 18:36
Tried MindtheGapps in stead of Open GApps, and got the same problem. However I found out that the bootlooping started after I tried to assign a 32Gb SD card as internal memory. So I did the above mentioned install again and took the SD card out, and now it´s working fine.

Not of much use though with just 16Gb internal memory. Hopefully this problem gets adressed in a future update.

-- EDIT 21:57
As External Storage the SD card doesn´t cause bootloops. On this phone apps aren´t transferable to SD unfortunately, even when forced through developer options. The camera app and my navigator app do allow data to be stored on the external SD, so the phone might be usable after all.

-- EDIT July 16th
The phone just rebooted during a call. That happened once before. Battery was about 70%. It also rebooted once after waking it up and starting an app. This compromises usability.
 
Last edited:
  • Like
Reactions: maanteel and bege10

Rp38g

New member
Jul 28, 2022
4
0
Hello, i got this rom and i have some problems with sim network. I would like to know if i'm the only one.
- Sometimes the phone just loses 4g signal and i cannot get it back until reboot my phone
- "Antenna switch" happens a lot and takes about 10s. during those 10s i lose signal
- My phone often reboot during calls
 

Not-Aus

Senior Member
Hello, i got this rom and i have some problems with sim network. I would like to know if i'm the only one.
- Sometimes the phone just loses 4g signal and i cannot get it back until reboot my phone
- "Antenna switch" happens a lot and takes about 10s. during those 10s i lose signal
- My phone often reboot during calls
Please use the latest firmware. (Firmware is not LineageOS Version!)
 

c341

Member
Jun 23, 2021
5
1
Please use the latest firmware. (Firmware is not LineageOS Version!)
What do you mean? Latest stock firmware?

Currently I have the last stock firmware on it, there I constantly lose the network (Vodafone) and takes forever until the kccat6 connects again or must restart it.

My main question now would be:

Which combination would now be the best for a successful and working LineageOS installation?

Firmware from ripee and especially TWRP ? Read that the current TWRP from ripee makes problems. Get to this unfortunately not the previous version.

Thanks!
 

user815

New member
Aug 7, 2022
2
1
Read that the current TWRP from ripee makes problems. Get to this unfortunately not the previous version.
What problems do You mean? The chapter with problems using the sd-card as internal memory is not a fault of ripee's lineageos-build, imho. Samsung never supported this function and I made the exact same experiences with other LineageOS-Builds:
1.) 2 pcx. Samsung S5 (G900F),
2.) Samsung Galaxy Note 8.0 (N5110) and
3.) Samsung Galaxy Tab Pro (T520)

I actually have another effect with ripee's build: When I shutdown the G901F and reboot it 10 hours later, it has lost about 20% of its akkuload. When I shut it down and reboot it immediatly and let the display off, the akkuload drops only 3% 10 hours later. That is some kind of suspect. ;)
 

c341

Member
Jun 23, 2021
5
1
What problems do You mean? The chapter with problems using the sd-card as internal memory is not a fault of ripee's lineageos-build, imho. Samsung never supported this function and I made the exact same experiences with other LineageOS-Builds:
1.) 2 pcx. Samsung S5 (G900F),
2.) Samsung Galaxy Note 8.0 (N5110) and
3.) Samsung Galaxy Tab Pro (T520)

I actually have another effect with ripee's build: When I shutdown the G901F and reboot it 10 hours later, it has lost about 20% of its akkuload. When I shut it down and reboot it immediatly and let the display off, the akkuload drops only 3% 10 hours later. That is some kind of suspect. ;)
The issue with the SD card (as internal memory) is known to me and I did not mean.

Basically I just want to know the following:

Is it possible to install the latest "TWRP 3.6.1_9-0" from 'ripee' in conjunction with the firmware "lineage-16.0-20220418-UNOFFICIAL-kccat6" also from 'ripee' without hesitation? Or does the "TWRP 3.6.1_9-0" make problems here?

If so, can someone provide the previous version of "TWRP 3.6.1_9-0" for kccat6?

---------------


Currently I have the last stock firmware on it, there I constantly lose the network (Vodafone) and it takes forever until the kccat6 connects again or I have to restart it.

Are the problems also known with LineageOS ?


Thanks!
 
Last edited:
  • Like
Reactions: user815

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Hi,

    i have tried to compile a new LOS16-build according to the official guide but without success.
    repo sync was successful but the result of breakfast kccat6 is:

    Code:
    [email protected]:~/android/lineage$ breakfast kccat6
    including vendor/lineage/vendorsetup.sh
    build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_kccat6".
    13:34:53 dumpvars failed with: exit status 1
    /usr/bin/env: ‘python’: No such file or directory
    build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_kccat6".
    13:34:54 dumpvars failed with: exit status 1
    build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_kccat6".
    13:34:55 dumpvars failed with: exit status 1
    
    ** Don't have a product spec for: 'lineage_kccat6'
    ** Do you have the right repo manifest?

    Then i tried to extract proprietary blobs but there is no ~/android/lineage/device/samsung/kccat6 folder and no extract-files.sh file.

    Do you have any ideas or suggestions?

    kccat6.xml

    Use this manifest. It includes our kernel with a couple of changes that are now required to build the kernel. This is purely a clerical thing that the kernel on Lineage doesn't have.
    2
    Thank you ripee!
    I should have mentioned that this is my very first try for an own build. I'm not familiar with the build-tools, i'm just following step by step the official guide.
    So i have absolutely no idea where to put this kccat6.xml file..
    build scripts

    If you're running Ubuntu and you haven't already set up your build environment in a way that's easy to manage, download my scripts repo and run build_environment.sh then rename all instances of "19.1" to "16.0" in lineage-19.1.sh and run that as well. It will sync down the bare minimum codebase you need to build from branch 16.0

    When the codebase is synced, put kccat.xml in /android/lineage-16.0/.repo/local_manifests
    1
    Hi,

    i have tried to compile a new LOS16-build according to the official guide but without success.
    repo sync was successful but the result of breakfast kccat6 is:

    Code:
    [email protected]:~/android/lineage$ breakfast kccat6
    including vendor/lineage/vendorsetup.sh
    build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_kccat6".
    13:34:53 dumpvars failed with: exit status 1
    /usr/bin/env: ‘python’: No such file or directory
    build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_kccat6".
    13:34:54 dumpvars failed with: exit status 1
    build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_kccat6".
    13:34:55 dumpvars failed with: exit status 1
    
    ** Don't have a product spec for: 'lineage_kccat6'
    ** Do you have the right repo manifest?

    Then i tried to extract proprietary blobs but there is no ~/android/lineage/device/samsung/kccat6 folder and no extract-files.sh file.

    Do you have any ideas or suggestions?
    1
    Many models are affected by this problem. I did not think that there is official information about it. Do you know the source of this information?
    If you search this thread you will find it.
    1
    Does that mean that I have to reboot to TWRP and shutdown my smartphone under TWRP ?
    I do it this way:

    - Create a text file "openrecoveryscript" with this contents
    Code:
    reboot poweroff
    - copy this file to /cache/recovery (this must be done before every shutdown)
    - reboot to TWRP
    - if the data partition is not encrypted you need to do nothing else, if it is encrypted you must unlock it in TWRP, then the phone shuts down.

    I do this procedure with a little Tasker task. So I just need to tap the shortcut of this task and the phone shuts down with no more action.
  • 83
    lineage-os-logo.png

    LineageOS for Samsung Galaxy S5 LTE+ / LTE-A

    Code:
    - Your warrenty is now void.
    - You [b]WILL[/b] trip KNOX!
    - You have been warned.
    - Use at your own risk.
    Introduction:

    This is the thread for the offical port of LineageOS to
    • Samsung Galaxy S5 LTE+, SM-G901F, codename kccat6, and
    • Samsung Galaxy S5 LTE-A, SM-G906S/K/L, codename lentislte.
    • This port is mostly stable. Still, there's no software without bugs.

    How to install:

    • For kccat6, use bootloader CQJ1, CQJ2 or later.
    • For lentislte use bootloader CPL1.
    • install custom recovery, ideally directly from the TWRP project.
      For kccat6: twrp-3.3.0-0-kccat6.img
      For lentislte: twrp-3.3.0-0-lentislte.img
      Note: TWRP 3.2.1-0 is required starting with Lineage-15.1/Oreo!
    • Enter recovery mode
    • Factory reset
    • Flash below ROM
    • Optionally flash Gapps. I suggest OpenGapps.
    • Optionally, if you want SU, install the LineageOS SU addon.
    • Reboot

    Know problems:

    • Sometimes the SIM doesn't show up after reboot.
    • Occasional Camera hiccups.

    State of kernel security:


    Download from:

    Official nightly builds:
    Test builds (only on demand or request):

    Sources:


    XDA:DevDB Information
    LineageOS for Samsung Galaxy S5 LTE+ / LTE-A, ROM for the Samsung Galaxy S5

    Contributors
    cvxda, sassmann, xamio, sktjdgns1189
    Source Code: https://github.com/LineageOS

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: kccat6: CQJ1/CQJ2, lentislte: CPL1
    Based On: Lineage OS

    Version Information
    Status: Beta

    Created 2017-01-08
    Last Updated 2019-04-17
    51
    Notes:

    Thanks to @Stamgastje for the first cut of these notes.

    History and older builds (LineageOS)

    The Lineage OS project -- a.k.a. Lineage Android Distribution (LAD) -- is a continuation of the CyanogenMod project, which was discontinued in December 2016. Before maintaining Lineage OS 14.1 ROM for this phone, @xamio maintained CyanogenMod ROMs (CM13, CM14.1). You can still find these builds via the link to his site (ionkiwi.nl) above. The original (and oldest) CyanogenMod builds for this phone were created by @sktjdgns1189. His original builds are still available here: http://fsrv1.sayanogen.com/KCCAT6-13/, and this was the original thread on this forum.

    Installation

    Below some hints that may help you to install these ROMs on your phone.

    Clean install, or dirty flashing?

    What is the difference?
    The difference is whether you clean (format) the entire /data partition (which contains your apps and user data, as well as the dalvik cache), or not, before flashing the new ROM image:
    • A clean install means: clean the /system, /data (incl. dalvik cache) and /cache partitions, and then install the ROM
    • Dirty flashing means: clean the /system and /cache partitions, as well as the dalvik cache, but not the entire /data partition, before installing the ROM
    With a clean install, you need to manually restore your apps and user data after flashing the new ROM image. With a dirty flash, there is no need to do this -- so this is the faster, but riskier solution. Therefore, it is always recommended to make a backup of your apps (e.g. with Titanium Backup) and user data (internal storage) before flashing any ROM image.

    When could you consider a dirty flash?
    It is, generally speaking, possible to perform a dirty flash:
    • When upgrading a ROM to an newer build of the same ROM (but be careful when upgrading between major versions, e.g. from CM13 to CM14.1)
    • When upgrading from CyanogenMod 14.1 to Lineage OS 14.1 (as Lineage OS is the continuation of CyanogenMod, based on the same sources)

    When should you perform a clean install?
    In all other cases, so e.g.:
    • When downgrading a ROM to an older build of the same ROM
    • When switching between ROMS, e.g. from CyanogenMod to Resurrection Remix (or vice versa). Reason: different ROMs use different code bases that are usually not 100% compatible (exception is upgrading from CyanogenMod 14.1 to Lineage OS 14.1, see above)

    (Note: in case you choose to perform a dirty flash over your existing ROM, don't forget to re-flash the GApps package immediately afterwards!)

    How to dirty flash an official weekly over an unofficial build (and vice versa)?

    When trying to update an unofficial build to an official weekly build, I get an error message in TWRP saying
    "Can't install this package on top of incompatible data. Please try another package or run a factory reset". How do I fix that?


    At the start of an installation the installer checks the build keys. They differ between unoffical and official builds, and the installer refuses to overwrite builds with different keys. To fix this you have to install the official keys before trying to install the official build:
    1. Run this script called lineage-migration-signed.zip in TWRP.
    2. Then install the official ROM zip.
    You only have to do this for the first switch from unoffical to offical build.

    There may be reason to dirty flash an unofficial build over an official build, for instance, if you're developing or testing new stuff. The problem is the same, just in the other direction: You have to install the unofficial build keys:
    1. Run this script called lineage-migration-unsigned.zip in TWRP.
    2. Then install the unofficial ROM zip.

    Modem and bootloader

    Which version do I need?
    Builds from Sept. 19 (cm-13.0-20160919-UNOFFICIAL-kccat6xx.zip) and later should use a Marshmallow modem & bootloader (starting with 'C', so e.g. CPE1, CPH3, CPJ1). Older builds require a Lollipop modem & bootloader (starting with 'B', so e.g. BOH4, BOK2).

    Generally, it is recommended to use the latest modem that is compatible for your device.

    How do I get these images?
    The original ROM files containing the modem and bootloader files are available from the Sammobile site. You have to extract bootloader and modem files and flash them to your device using Odin (Windows) or Heimdall (Linux, MacOS, Windows).
    • Download the firmware file from Sammobile's firmware page for the G901F, G906S, G906K or G906L, depending on your device. The last ones available are CQJ1/CQJ2 for G901F, CPL2 for G906S/K/L. Assuming you download the CQJ1 version for G-901F, the resulting file will be called G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip.
    • Unpack that file. On Windows, right click on the file and choose "Extract all...". On Linux/Mac, simply use the command line:
      Code:
      $ unzip G901FXXU1CQJ1_G901FDTM1CQJ1_DTM.zip
      After unpacking you get a new file G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. This is a standard tar archive and can be opened with any archiver capable of handling the tar format (especially with tar itself). The attached .md5 suffix indicates, that a md5 checksum has been attached to the file.
    • Extract the file. On Windows you can do this by installing the swiss-army knife of archivers, 7zip. It installs an entry for the right-click context menu. Use it to extract G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5. On Linux/Mac, simply use the command line:
      Code:
      $ tar xf G901FXXU1CQJ1_G901FDTM1CQJ1_G901FXXU1CQC1_HOME.tar.md5
      Apart from the different download page and the different file names, the procedure is the same on the G906 variants.

      Either way, this extracts the following list of files:
      Code:
      NON-HLOS.bin  cache.img.ext4   recovery.img  sdi.mbn
      aboot.mbn     hidden.img.ext4  rpm.mbn       system.img.ext4
      boot.img      modem.bin        sbl1.mbn      tz.mbn
      The files with suffix .img and .img.ext are the actual system files. You don't want them, unless you want to reinstall stock Samsung Android.
      The files NON-HLOS.bin and modem.bin constitute the baseband, all other files with .mbn suffix constitute the bootloader.

    How do I flash these images on Windows with Odin?
    This is only marginally more complex than by using Heimdall (see below). The difference is that Heimdall can immediately flash the extracted .bin and .mbn files, while Odin needs them packed into a tar file. Fortunately you already have 7zip!
    • Select all of the aforementioned .bin and .mbn files. Right click to open the context menu. Select 7zip and choose Add to archive... from the sub menu
      Screenshot_20170125_120950.png

      This opens 7zip's archive dialog. As Archive format choose tar. Append .md5 to the archive filename and press the OK button
      Screenshot_20170125_121840.png

      Congratulations, you're now the happy owner of an Odin file with only bootloader and baseband images.
    • Sidenote: You could also create a tar.md5 file, you just have to append the md5 sum to the just created tar file. It's not really tricky, but you'd need an additional md5sum tool which is not available on Windows by default, so we just skip this here.
    • If you haven't already, download and install Odin.
    • Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
    • Connect your device to your PC's USB port.
    • Start Odin.
    • Select the .tar file you just created.
    • Enable (only) these options: 'Auto Reboot' and 'F. Reset Time'.
    • Flash the images.

    How do I flash these images on Linux/MacOS/Windows with Heimdall?
    • If you haven't already, download and install Heimdall. If you have trouble with the most recent version of Heimdall (the official version 1.4.1 has a few annoying bugs) you have to rebuild heimdall from source by yourself. Instructions for rebuilding can be found here and here.
    • Boot the phone into download mode: Power off the phone, then press and hold Volume Down + Home + Power buttons. You'll see a severe warning message. Ignore it by pressing Volume-Up. You're now in download mode.
    • Connect your device to your PC's USB port.
    • Check if Heimdall recognizes your device:
      Code:
      $ heimdall detect
      If it doesn't, you have to do some digging:
      • On Windows you might have to install Samsung device drivers.
      • On Linux you might have to create a udev entry for your device. As root, open or create the file /etc/udev/rules.d/51-android.rules and add a line
        Code:
        SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0660", USER="[insert your non-root username here]"
        , then reboot the machine.
      • On Mac... sorry, I have no idea what to do on a Mac in this case.
    • Flash the bootloader and baseband images:
      Code:
      $ heimdall flash --APNHLOS NON-HLOS.bin \
      --MODEM modem.bin --SBL1 sbl1.mbn --DBI sdi.mbn \
      --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn
      This may take a minute or two and then reboot your device automatically. It might reboot into your recovery. That's nothing to worry about. Just reboot from there into system.
    16
    LineageOS 15.1 (Oreo) preview builds

    I made LineageOS 15.1 preview builds available for kccat and lentislte.

    This is very much Work In Progress.
    Only for the experimentally inclined, don't use as daily driver.
    This is only for toying around, I don't take bug reports yet.

    Working:
    • Audio
    • Bluetooth
    • Camera (Photos only)
    • Deep Sleep
    • Display
    • Fingerprint
    • Google Play (with clean install, and a bit bumpy at installation time)
    • GPS
    • Hardware Keys
    • Lights, Torch
    • NFC
    • RIL
    • USB
    • Sensors
    • Wifi
    Not working yet: Everything else. Most notably
    • Camera (Video)
    • Google Play (see above)
    • IR
    • SELinux

    Corinna
    16
    If I delete those files before reboot:
    /data/dalvik-cache/arm/[email protected]@boot-telephony-common...
    the sim card is recognized.

    Thanks, maybe that's a hint for a solution.

    You were really up to something there. @sassmann created a patch to remove these files at startup, and it seems this really makes the RIL startup *much* more reliable. Over 60 reboots with 4 devices with only one fail on one device, and after another small tweak no fail on that device either.

    We need a bit more time for testing so the patch may not make it into the tomorrow's official build, but what's one week, right?

    Edit: I merged the patches so this should be in tomorrow's builds. Thanks again, @Krapotke!
    Edit 2: @Krapotke, I gifted you Ad-free, I'm just so glad we have a workaround.


    Corinna
    16
    Lineage 15.1 goes official for kccat6/lentislte

    Apart from the occasional SIM problem it looks like we're in a pretty good shape now. I triggered the process to make 15.1 the official release for our device. First official builds are going to be built tomorrow or, if the timing isn't quite right, the week after (Monday is lineage-15.1 build day ATM).

    Let's dive in,
    Corinna