[ROM] [OFFICIAL] LineageOS 14.X for Galaxy S5 | Android 7.X Nougat
- Thread starter haggertk
- Start date
curiousrom
Recognized Contributor
Thank you haggertk for your continuous support on our S5
My best wishes for 2021
FYI the LineageOS S5 klte family maintainer haggertk created a new thread here:
[ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
***
FYI, Privacy Guard is deprecated in Lineage 17 (Android 10) and above and a "no go" for me!
The app option "start at boot" should be in the hand of the user, not only for battery reasons.
Just another example of Giigle's dictatorship!
Therefore, I appreciate Lineage 14.1 a lot
as well as...
Last edited:
Sorry for the late late question. With this 14 I have no problems with BT. I think you told me before that it was due to a issue of drivers on the new roms. Does the 18 take care of this issue?
curiousrom
Recognized Contributor
Bluetooth Issues & LineageOS Versions?
¯\_(ツ)_/¯
Search that 18.1 thread or ask in it: [ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
My Galaxy S5 G900M LineageOS 17.1 klte build 2021-02-28 @ the present does not have any Bluetooth issue but that varies for some users as you can read in [OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants > Known Bugs chapter.
I suspect that it's related to the build date & hardware revision of the S5 itself but users never include enough data points to troubleshoot the issues.
According to DevCheck > System: Manufacturing date August 25, 2015 for my S5 G900M.
And that's with the most recent S5 Odin Flashable Modem & Bootloader for my device.
***
¯\_(ツ)_/¯
Search that 18.1 thread or ask in it: [ROM][UNOFFICIAL][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)
My Galaxy S5 G900M LineageOS 17.1 klte build 2021-02-28 @ the present does not have any Bluetooth issue but that varies for some users as you can read in [OFFICIAL] LineageOS 17.1 for Galaxy S5 klte + Variants > Known Bugs chapter.
I suspect that it's related to the build date & hardware revision of the S5 itself but users never include enough data points to troubleshoot the issues.
According to DevCheck > System: Manufacturing date August 25, 2015 for my S5 G900M.
And that's with the most recent S5 Odin Flashable Modem & Bootloader for my device.
***
I was told it was due to Samsung not releasing drivers. In my case it may be due to the device (car BT) which was second generation BT from 2005 . Many individuals have the problem, but my problem only occurs with this sole device. 14.1 works flawlessly but the 15,16,17 that I have tried all drop signal continuously.
A REALLY bizzare problem just popped up. I'd transferred a coupla photos to my Win7 desktop via bluetooth and all was well.
Tried it later on and the phone complains that it can't transfer an unknown file type. Huh?!?
I can transfer any other file, I can transfer a photo from another S5, but I can't transfer from THIS phone to ANY PC, via bluetooth. Un-paired phone and re-paired, no joy. Restarted phone, no joy.
Ideas?
Anyone?
**************** UPdate ************
Now it seems that ANY file going OR coming into the phone is 'unknown send failed"!
Tried it later on and the phone complains that it can't transfer an unknown file type. Huh?!?
I can transfer any other file, I can transfer a photo from another S5, but I can't transfer from THIS phone to ANY PC, via bluetooth. Un-paired phone and re-paired, no joy. Restarted phone, no joy.
Ideas?
Anyone?
**************** UPdate ************
Now it seems that ANY file going OR coming into the phone is 'unknown send failed"!
Last edited:
@haggertk Yes indeed! I know this is WAY old, but still runs like a top and I'd like to second this request. Many of us still appreciate when "a thing is done."
It seems like it's too late but I will say about this now. Thx for sharing this first!
It's completely same with the official one from LineageOS team, unless they added unofficial patches on the top of it before.
I do not remember the exact security date but it should be still new!
I will try to update them by time to time when I have enough free time.
ROM: LineageOS 14.1
Android Version: 7.1
Type: Unofficial
Supported Device(s): kltexx (klte, klteduos, kltedv, kltekor)
Download Link: this
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
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
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
293LineageOS 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:
FAQ/Frequent Statements
GApps:
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/extras67Source:
https://github.com/LineageOS
https://review.lineageos.org
My Picks for unofficial (official doesn't pick anything):
https://github.com/haggertk/cm_build_stuff/tree/cm-14.154
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/11389707673812612076435Builds 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.33CM-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.
