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

Search This thread

lecorbusier

Senior Member
Nov 28, 2012
1,109
120
Samsung Galaxy S5
LG G6
I had a 3000mAh "Akku King" battery with the size of the standard one(and NFC antenna). So no custom back cover necessary. But Akku King is just a german based online shop, probably not shipping worldwide.
 

RBraverman

Senior Member
Aug 16, 2011
296
22
I had a 3000mAh "Akku King" battery with the size of the standard one(and NFC antenna). So no custom back cover necessary. But Akku King is just a german based online shop, probably not shipping worldwide.


I can only find a 4200/4800mAh or - ready 6800mAh batteries. None of which I trust and I can't remember how to tell if they're real or Memorex.
 

lecorbusier

Senior Member
Nov 28, 2012
1,109
120
Samsung Galaxy S5
LG G6
And such batteries should come with a back cover and the phone will fit in no case no more and if such a heavy load drops it will certainly break.
I regarded the additional 200mAh of my battery just as a small bonus.
And i never got a foul battery, whether most likely forged "genuine" ones for an LG phone or all the others for all kinds of stuff, mostly from third party suppliers.
 
Last edited:

purplevike

Senior Member
Apr 2, 2012
60
38
Security Patches

While my hope is that the bugs of lineage os 16 will be worked out in 17, is there anyone willing to post a video on how to maintain this ROM? A walk thru instructional on how to keep it patched (security updates only) it appears all of the major forks discontinued as of Nov ... I know the devs are busy working on 17.1 and maybe this will be a moot point. But as far as reliable bluetooth and call recording with Record My Call 14.1 has it covered well for some of us. I would be willing to learn

Ps
@haggertk thank you for taking us this far your work is not unappreciated

I know this post is 4 months old, but I would also like to know if this is something that the casual user could accomplish. This Unofficial 14.1 is far-and-away my favorite OS for the S5, and I see no reason to fix what isn't broken.

As FettyWap stated, I'd also like to thank @haggertk for his continued support, and welcome any update. Even quarterly patches would be very much appreciated.
 
  • Like
Reactions: FettyWap

Reverse-anastomosis

Senior Member
Oct 31, 2018
288
174
@purplevike I have since migrated to 16 and I am dealing with intermittent Bluetooth issues. What features are you looking to hold on to in 14.1. I agree it is superior as far as reliability is concerned. I did find some alternatives for call recording etc

I'd still be using my s5 if it weren't for the Bluetooth unreliability after 14.1. There is still an open ticket regarding Bluetooth stability. I filed a long time ago, never even acknowledged by haggertk...it seems to only affect a few of us though so maybe not worth his time given how much he's got going.
 

PostToasted

Member
Feb 13, 2018
22
8
I think there are more of us than meets the eye with Blue Tooth issues after 14.1
I also just gave up on my S5 and upgraded to an S9. Problem solved. My S5 is still running Nougat as a backup unit.
If I had to guess, the issues are caused by the newer Blue Tooth Driver going into power management that the S5 hardware wasn't designed to deal with, causing the crashes. My idea is to integrate the older driver into the newer rom and see how that goes, if that could even be done?

I'd still be using my s5 if it weren't for the Bluetooth unreliability after 14.1. There is still an open ticket regarding Bluetooth stability. I filed a long time ago, never even acknowledged by haggertk...it seems to only affect a few of us though so maybe not worth his time given how much he's got going.
 
  • Like
Reactions: FettyWap

purplevike

Senior Member
Apr 2, 2012
60
38
It Just...Works

@purplevike I have since migrated to 16 and I am dealing with intermittent Bluetooth issues. What features are you looking to hold on to in 14.1. I agree it is superior as far as reliability is concerned. I did find some alternatives for call recording etc

The loss of the ability to screen cast was a non-starter for me. Besides the buggy nature of bluetooth disconnects, and other inexplicable anomalies, (notifications and the like.) 16.1 just wasn't for me. 14.1 with updated patches is the perfect blend of functionality, reliability, usability, and security.
 

fipsy

Senior Member
Feb 6, 2013
796
295
Hannover, Germany
Most people certainly know that Google has recently implemented Covid-19 exposure notifications in its Play Services. They appear as the first menu item in the settings under Google. If you select this menu item, you will only see a white page. Normally, however, numerous setting options should appear there. This functionality is a prerequisite for using the national Covid-19 apps, which are now being rolled out by the national authorities. It seems that these apps will not be usable with Lineage 14.1 on the S5, right?
 
  • Like
Reactions: pmduper
Re: Google COVID-19 exposure notifications

Most people certainly know that Google has recently implemented Covid-19 exposure notifications in its Play Services. They appear as the first menu item in the settings under Google. If you select this menu item, you will only see a white page. Normally, however, numerous setting options should appear there. This functionality is a prerequisite for using the national Covid-19 apps, which are now being rolled out by the national authorities. It seems that these apps will not be usable with Lineage 14.1 on the S5, right?

On a Galaxy S5 G900M LineageOS 16.0 klte build 2020-04-27 + Open GApps Pico with Display > Style Dark the > Settings > Google > COVID-19 Exposure Notifications panel is white whithout any text.

Only when Display > Style Light is selected is the text visible.

That COVID-19 panel links to Android help https://support.google.com/android/answer/9888358
***
 
  • Like
Reactions: fipsy and pmduper

fipsy

Senior Member
Feb 6, 2013
796
295
Hannover, Germany
@curiousrom: But it should not only link to the Android help but also offer two options to delete the Random IDs and to deactivate covid-19 tracing as you can see on the attached Screenshots from a German Smartphone where the tracing works. If these options are not present I suppose this is an indication that tracing will not work.

By the way: Lineage 14.1 doesn't offer a menu item Display -> Style Dark or Light.
 

Attachments

  • IMG-20200528-WA0004.jpg
    IMG-20200528-WA0004.jpg
    50.2 KB · Views: 240
  • IMG-20200528-WA0005.jpg
    IMG-20200528-WA0005.jpg
    91.6 KB · Views: 231
Last edited:

fipsy

Senior Member
Feb 6, 2013
796
295
Hannover, Germany
After I have deleted the Google Play Services data via the settings, the menu item no longer appears in the Google settings. All very strange. It's a pity that there is no feedback on this...
 

fipsy

Senior Member
Feb 6, 2013
796
295
Hannover, Germany
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.
 

Attachments

  • IMG_20200617_010856.jpg
    IMG_20200617_010856.jpg
    246.8 KB · Views: 240
Last edited:

fipsy

Senior Member
Feb 6, 2013
796
295
Hannover, Germany
I leave the subjective evaluation of the app's usefulness to the scientists. I'm all about the technical aspect. I would be interested to know why the API does not work with LineageOS 14.1.
 

DrGEROH

Member
Mar 26, 2011
10
1
No LTE on G900T with QC2 Modem ?

First, thanks for making this LOS 14.1 ROM available. I don't need the latest LOS on my old SM-G900T (official nightly 16.0 builds from LOS), but it is nice to have a more recent Android OS on the device (compared to the last 6.0.1 TW ROM by Samsung).

Two observations:

(1) I was unable to install this ROM with TWRP v3.4.0.0; I needed to use TWRP v3.3.1.0 to install this ROM successfully.

(2) I installed this from stock ROM build MMB29M-G900TUVU1GQC2; I'm finding that data is limited mostly to HSPA or HPSA+ -- I rarely see LTE using an AT&T SIM.

This is a back-up device; my daily is an unlocked SM-G930U (S7), also with an AT&T SIM, and I always have LTE data. I found one old xda-developers thread that seemed
to address this issue: forum.xda-developers.com/tmobile-galaxy-s5/lte-connection-issues-lineageos-t3554259, which references a potential solution using force_g900f_ril_blobs.zip (also by OP of this thread). Can anyone here comment on whether this solution is appropriate for the G900T running this LOS 14.1 ROM to get reliable LTE data? If so, do I need to root the device to apply?

Update:
I tried to install the referenced ZIP from TWRP; it failed, so I wiped this unofficial 14.1 and am giving an official 15.1 nightly from Feb 2019 that I managed to find with a little Googling. So far, so good with regard to LTE connectivity...
 
Last edited:

Top Liked Posts

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

    Code:
    #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.

    GApps:
    LineageOS recommends Opengapps. I use Opengapps mini. If you are running lineage-14.1 then you want ARM 7.1.
    http://opengapps.org/

    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.

    Downloads:
    Official (lineage-14.1) - https://download.lineageos.org
    Official SU Addon - https://download.lineageos.org/extras
    54
    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:
    http://lineageos.org/
    https://www.reddit.com/r/LineageOS/
    https://www.facebook.com/lineageandroid
    https://twitter.com/lineageandroid
    https://plus.google.com/113897076738126120764
    35
    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.
    33
    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.