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

Search This thread

haggertk

Senior Member
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
 
Last edited:

Haslie

Senior Member
Feb 8, 2016
87
15
Thanks so much for this rom newly cm14 i hope its working on my phone sm g900f

---------- Post added at 02:43 PM ---------- Previous post was at 02:40 PM ----------

What about themes?
 

jcole20

Senior Member
Jan 22, 2012
455
249
Augusta by way of Atlanta
Thanks so much for this rom newly cm14 i hope its working on my phone sm g900f

---------- Post added at 02:43 PM ---------- Previous post was at 02:40 PM ----------

What about themes?
Theme engine isn't working yet on CM 14. Themes are low on the priority list when it comes to CM development. Traditionally you start with the basic components (radio, WiFi, sysui and framework issues) to reach a stable base and then work on features like themes, Bluetooth etc.

For anyone wondering about the stability I'm really impressed with how stable this alpha build is. WiFi and radio is working great on my end. It appears Bluetooth is working though I've not really tested it thoroughly. Many of the root apps we all use seem to have several minor nougat compatibility issues but that's unrelated to the Rom itself.

I'm seeing a minor issue where it's not automatically detecting time zone on setup. A few appearance based settings are non functional it seems at the moment. Overall though the rom runs great and for an alpha its much better than I expected.

Sent from my SM-G900T using Tapatalk
 

Waheed Hassan

Senior Member
Aug 29, 2013
158
148
Sharjah
Launcher MOD

i'm using this ROM for some time and it's running smoothly and with minimal bugs, adoptable storage is working fine on this rom excellent work bro.. @haggertk :good:
and I've created flashable zips for google pixel launcher and wallpaper picker for you guys.. :D

Note: check the attachment for zips and screenshots

HIT THANKS IF I HELPED YOU.. :cowboy:
 

Attachments

  • Pixel_Launcher.zip
    1.9 MB · Views: 4,154
  • Wallpaper_Picker.zip
    1.7 MB · Views: 3,035
  • home_screen.jpg
    home_screen.jpg
    105.6 KB · Views: 30,426
  • app_drawer.jpg
    app_drawer.jpg
    143.8 KB · Views: 30,345
  • adoptable_storage.png
    adoptable_storage.png
    74.6 KB · Views: 30,081

rayzen6

Senior Member
Feb 5, 2016
506
273
@haggertk

I'm sure that u are very Much aware of the bug call delay. But I'm reporting that once again in here.

The bug is like when receiving or calling someone the voice from other side is able to heard like after 6-8 seconds. Like callui is sticking for that time and voice too.

I'm sure ur aware so that I didn't provide log for that.
I hope this may be solved soon too.

But thank you all very much who are contributing for kite development. Thank you! :)
 
Last edited:

dari-woka

Senior Member
Jan 30, 2011
248
55
Thanks for this.
for my the most annoying its the dialer lag, and Spotify..! I don`t know if its just me or for everyone. When I start spotify, the phone reboot

---------- Post added at 04:34 PM ---------- Previous post was at 04:29 PM ----------

by the way, what is sdclang?
 
  • Like
Reactions: rayzen6

haggertk

Senior Member
Thanks for this.
for my the most annoying its the dialer lag, and Spotify..! I don`t know if its just me or for everyone. When I start spotify, the phone reboot

---------- Post added at 04:34 PM ---------- Previous post was at 04:29 PM ----------

by the way, what is sdclang?

I just launched Spotify and am listening to music. Hmm.

I added a FAQ entry for sdclang.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    G'day @haggertk
    Any chance of an update for this timeless gem? Still a favourite with us dinosaurs who are having a hard time moving into the present, (and enjoy good battery performance).
    Thanks mate
  • 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.