[ROM] [OFFICIAL] LineageOS 14.X for Galaxy S5 | Android 7.X Nougat

Search This thread


Senior Member
Jun 3, 2016
It is as I suspected: With LineageOS 14.1 it is obviously not possible to use the Nearby.EXPOSURE_NOTIFICATION_API of Google Play Services. Although the Play Services are up to date (version 20.18.17, updated end of May) and Google writes in its documents that the functionality should be available from Android 6.0 on. I wonder what's causing it. There is only the error message as in the screenshot below.
As I can recognize on your pic, you use the German Corona warning app on your S5. It needs a very stable Bluetooth connection (the S5 supports Bluetooth 4.0 LE) and all the necessary Google APIs. This app only runs flawless with the latest MM (6.0.1) stock ROM. This can be a modified (debloated) one. The reason why it fails on Lineage or AOSP based ROMs: Samsung doesn't publish the source code for all drivers, so the developers can't fix this issues. I'm using the Covid 19 app too with a rooted stock based, modified ROM on my S5. The app works like it should without problems since nearly 20 days, a factory Android 6 is official still supported by the RKI programmers.
Last edited:


Senior Member
Dec 4, 2017
Running a test now with two brand new extended batteries it appears this ROM is capable of an extra day of battery life one is a 17.1 havoc ROM the other is 14.1 no gapps installed no WiFi or phone radio

Bruh havoc ROM is rubbish
The UI lagged and the battery drained so fast and it was getting warm for no reason
(Edited) 02.08.20

Havoc OS has more fixes to it now and it's much more stable
And battery life and standby and performance is brilliant network reception issue is fixed
The latest lineage os not just yet

I'm using lineage os 17.1 and this battery https://www.amazon.co.uk/GadFull-co...uPWNsaWNrUmVkaXJlY3QmZG9Ob3RMb2dDbGljaz10cnVl

It's 2800mah and this is my stats for heavy usage
1% left with 6hr SOT


  • Screenshot_20200713-212049_Settings.png
    110.6 KB · Views: 85
  • Screenshot_20200713-211906_Settings.png
    110.7 KB · Views: 87
Last edited:


Senior Member
Dec 4, 2017
Running a test now with two brand new extended batteries it appears this ROM is capable of an extra day of battery life one is a 17.1 havoc ROM the other is 14.1 no gapps installed no WiFi or phone radio

And the fact that you used no gapps is pretty biased and unfair

Battery life is even better without gapps I tested this out for myself
Gapps will reduce battery life abit

Unfair testing I don't agree with you


Jun 23, 2020
Black smearing seems a little bit more predominant in lineage than in stock
I know that is completely normal for OLED displays
Anyone has tips to reduce it ?
Last edited:


Senior Member
Aug 16, 2011
App to help with battery useage

Literally over night - possibly the same day I upgraded the firmware on my Plantronics to the worst ... firmware ... ever (battery used to last 2 days, I'm lucky 2 hours now) - but I digress - the battery in my S5 started to plummet, but I can't tell why, as I've really no usage data on them.
I've tried a couple of apps hoping one would SIMPLY tell me which apps were using what, but that's harder to find than you might think.
ANY ideas, would be gratefully accepted.

BTW, the battery is about 6 months old.


Senior Member
Jun 16, 2018
Security Patch Level

Lineage 14.1 is still appreciated with a good amount of users at your download side.
Any change you could spin a security update?

Thank you in advance @haggertk


Senior Member
a thing was done

It has the Oct 2020 ASB, latest chromium webview, latest tzdata, etc.
Thank you for keeping 14.1 updated. I use it as reference implementation for testing other android 7 ROMs. Can you pleaae tell me, why I am not able to advertise Bluetooth low energy beacons with android 7 custom ROMs? Android 8..10 works as expected.


Senior Member
Thank you for keeping 14.1 updated. I use it as reference implementation for testing other android 7 ROMs. Can you pleaae tell me, why I am not able to advertise Bluetooth low energy beacons with android 7 custom ROMs? Android 8..10 works as expected.
14 is dead and has been for years, aside from security patches or tzdata updates, you get what you get.

If I had to guess, it either didn't work in the AOSP baseline that is 4 years old. That and the fact that 14 was the last branch that had the whole platform based on the hot mess that is CAF -- CAF's changes platform wide could have broken it even if it worked in AOSP.


New member
Dec 13, 2013
Phone sometimes reboots after turning the screen on

I've done a clean install already, problem persists; can someone take a look at the logs, please? Tell me if there's anything else I should provide that might be helpful.

Top Liked Posts

  • There are no posts matching your filters.
  • 293
    LineageOS official builds have been released.

    #include "std_disclaimer.h"
     * Your warranty is now void.
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.

    Build/Variant Map:
    [OFFICIAL] klte - SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L
    [OFFICIAL] klteduos - SM-G900FD, SM-G900MD
    [OFFICIAL] kltedv - SM-G900I, SM-G900P
    [OFFICIAL] kltekor - SM-G900K, SM-G900L, SM-G900S
    [OFFICIAL] klteusc - SM-G900R4, SM-G900R7 Moved to klte build as of 19 April 2017
    [OFFICIAL] kltevzw - SM-G900V, SM-S902L Moved to klte build as of 11 March 2017

    FAQ/Frequent Statements
    Q0: When ${THING}?
    A0: No ETAs. Don't ask.
    Q1: You list my phone above but there isn't a build uploaded, why not?
    A1: Haven't gotten around to it yet.
    Q2: But when will you get to building it?
    A2: Damn it, see Q0/A0.
    Q3: How often will builds be produced?
    A3: Whenever I get to them and feel like uploading.
    Q4: But ${THING} isn't working for me. I cannot live without ${THING}. :crying:
    A4: Not surprising, lineage-14.1 is still young. Some features aren't ported and some may still be buggy. Maybe lineage-14.1 isn't ready for you yet. And don't cry.
    Q5: Xposed/Magisk?
    A5: Don't know. Maybe, maybe not. I'll ignore you if you complain about something and are using them. Don't even think of talking about it.
    Q6: Can I complain about something?
    A6: I'd prefer not, but be prepared for me to ignore you.
    Q7: Can I report a bug?
    A7: Absolutely. Please ensure that you are running stock ROM and kernel. No Xposed or other hacky crap. Create a logcat.
    Q8: When will you fix ${THING} that I just reported?
    A8: Damn it, see Q0/A0. And if your ${THING} isn't something that bothered me, it probably just got shuffled to the back of the line.
    Q9: Can I donate?
    A9: Code, yes. Money, no.
    Q11: My bluetooth seems to mostly work except it gets glitchy when I turn my screen off, put it in my pocket, walk away from it by more than a couple feet, etc. Why?
    A11: Your OUI isn't recognized by macloader. We're doing the right thing for cm-14.x+ and giving EVERYONE the correct BT and WIFI firmware/calibration data. Send me the first three octets of your WIFI MAC address as well as the output of the instructions in this post.
    Q12: Can I dirty flash from CM to LineageOS?
    A12: The official timeframe for dirty-flashing from CM to LineageOS is over.
    Q13: HALP, I restored a TWRP backup and now cannot get my radio to work.
    A13: First, don't panic. You have a full backup, it's just that something weird is happening on boot of the restore. We can get through this. Go ahead and restore that nice, clean backup again (Yes, restore it AGAIN!), but DO NOT REBOOT YET! Using the TWRP file manager, delete these two directories:
    • /data/data/com.android.providers.telephony/databases/
    • /data/data/com.android.providers.telephony/shared_prefs/
    Now you may reboot your phone.

    LineageOS recommends Opengapps. I use Opengapps mini. If you are running lineage-14.1 then you want ARM 7.1.

    Doesn't Work:
    • CM ThemeEngine - Not ported to lineage-14.x
    • VoLTE - Didn't work on cm-13.0. Didn't work on cm-14.1. Don't expect great things, even devices from the same generation as ours that had VoLTE on M (e.g., bacon) don't have it on N.

    Official (lineage-14.1) - https://download.lineageos.org
    Official SU Addon - https://download.lineageos.org/extras
    Where is this Lineage os ?

    It will be LineageOS as soon as we finish standing up a new Gerrit code review instance (should happen today) and merge rebranding patches. Currently it is a 100% bare fork -- CM source == LAOS source.

    I'd expect official builds are at least a week away. There are a lot of offers for server time and storage space coming in, but no one really wanted to do much thinking along those lines yesterday during the holiday and step 1 really is getting Gerrit running.

    Suffice to say, cyngn's actions over the weekend accelerated our timeline. We'd been planning to be cut over to new Gerrit by New Year's, but by deleting DNS entries and disabling SSH access to CM gerrit really has pulled the rug out from under us.

    Please bear with us. If anyone is looking for general OFFICIAL LineageOS information/messaging, stick to these locations -- we control them:
    Builds are being uploaded to the usual place, all with filenames containing the 20161027 date.

    Changes of note:
    - Kernel update to 3.4.12. Ozzy is grinding through, only about 100 releases left to go.
    - seccomp-bpf. Well, this isn't exactly new to my builds, the last one or two had it, but I went ahead and merged it.
    - Dirty COW fix. Yeah, all of you probably are running rooted, but we don't want some rogue app doing root-level stuff without you being prompted now, do we? This may have been in the last build, I cannot remember the time of day that I kicked it off...
    - Anything merged into the greater cm-14.0 tree.
    - Oh yeah, some camcorder thing. It appears to be working for me. It should work for you. Or it may completely blow up. It is still under active review. Beware, dragons.

    Yes, I know that work is being done on cm-14.1 (Android 7.1). Not every project is forked yet, I don't want to deal with a frankentree, and I'd just as soon let that settle down a bit (first devices successfully booted only just last night). So no, no cm-14.1 yet. And no, I don't know when.
    CM-14.1 builds are going up. I updated the first post, but if you don't feel like clicking back, they are here. klte is up already and kltevzw will be soon thereafter. The rest will come in due time. All will have the date of 20161029 in the filename.

    If you want to dirty-flash upgrade from cm-14.0, you MUST flash new Android 7.1 gapps immediately after flashing cm-14.1 before booting the ROM or fail city will result.

    For those asking what's different from the @javelinanddart build, pretty much just everything that's been committed in the last couple days to the greater CM tree. I did compile this using MALLOC_SVELTE which may help with our relatively low-memory device. If this looks good over the next couple days I'll merge it upstream.

    Oh yeah, I also picked this unmerged commit that will let you actually change the status bar battery representation.