[ROM][UNOFFICIAL-ABANDONED][11] LineageOS 18.1 for Samsung Galaxy S5 (klte*)

Search This thread

haggertk

Senior Member
2okPze5.png


LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps) . LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

Device source code:
Kernel source code:
My picks:

Build Compatibility:
The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.​
BuildModel
klteSM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
klteactivexxSM-G870F
klteaioSM-G900AZ, SM-S902L
kltechnSM-G9006V, SM-G9008V
kltechnduoSM-G9006W, SM-G9008W, SM-G9009W
klteduosSM-G900FD, SM-G900MD
kltedvSM-G900I, SM-G900P
kltekdiSC-04F, SCL23
kltekorSM-G900K, SM-G900L, SM-G900S

Downloads:
Installation Instructions:
  • Download latest build
  • Boot into recovery
    • Lineage recovery images are included in the download section and that's what I support. If you feel like using TWRP and something isn't working then take it up with the TWRP maintainer
  • If not updating from one of my earlier unofficial builds, then format/system, /data, and /cache
    • For Lineage recovery:
      • Format -> Format data/factory reset (this does /data and /cache)
      • Format -> Format system partition
    • For TWRP figure it out. And no, "wipe data" isn't the same as formatting data
  • Install LineageOS zip
  • If this is your initial installation of LineageOS 18.1, then flash any addons (e.g., gapps)
Reporting Bugs:
  • DO NOT even think about reporting bugs if you are running a custom kernel, Magisk, or Xposed
  • Grab a logcat after the problem has occurred
  • If there is a random reboot then grab /proc/last_kmsg. A logcat AFTER the reboot will be worthless
  • Note which build AND device you have
  • Read the thread, at least the last month's worth of posts. Don't report things that others already have.
Compatibility Notes:
  • Bootloader version doesn't matter. Anyone who tells you so doesn't know what they are taking about. My Developer Edition G900V is still running the original 4.4.2 KK aboot. My G900W8 is running the latest 6.0.1.
  • All builds except for klteactivexx MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
  • You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
  • External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. It was kind of broken in 17 and we likely won't merge the changes to add it back in for 18. I'm not going to pick the open changes to re-add support because I'm not going to deal with "but it worked on haggertk's unofficial builds" bug reports after we eventually go official. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
Donations:
  • I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
 
Last edited:
Thank you Mr. @haggertk for keeping our old S5 up to date. :cool: 👍

It's not mentioned in the OP @ the present but could you tell me please if SELinux is set to Permissive or Enforcing?

If it's SELinux Permissive would you say that it's not ready to be used as a daily driver with important user accounts @ the present?
***
 
Last edited:
  • Like
Reactions: HippoMan

ttesty

Senior Member
Dec 17, 2010
65
9
G900T.. CrDroid 7.0 lineage-18.1-20201225-INOFFICIAL-klte.zip... BitGapps v19 .. Magisk 21.1 ... TWRP 3.4... latest Modem.
Radio: G900TUVU1GRJ1 (6.0.1)

Good news: mostly everything works fine (including cellular data, calls, apps).
Problems: Google Maps crash (have to use incognito mode as workaround), Location data limited to GPS only (not AGPS/cellular).

Abnormal errors (most were there in previous releases, and these are periodic/frequent, seen in some other 18.x ROMs):

AGPS Location (partly related to BitGapps v19):
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: Failed:
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: java.lang.SecurityException: uid 10005 does not have android.permission.ACCESS_FINE_LOCATION.
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-28 09:18:28.399 866 1040 W ActivityManager: Appop Denial: Accessing service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService from pid=2118, uid=10005 requires appop COARSE_LOCATION

TCP read errors:
12-28 09:29:36.462 1321 2335 E TcpSocketTracker: Unexpected socket info parsing, family 10 buffer:java.nio.HeapByteBuffer[pos=96 lim=588 cap=60000] xAAAABQAAgAAAAAAKQUAAAoBAADVBBRsAAAAAAAAAAAAAP//CsRBmgAAAAAAAAAAAAD//0p9ibwAAAAAAIt51wAAA
....
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: java.lang.IllegalArgumentException: Bad position 65632/588
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.Buffer.position(Buffer.java:259)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.ByteBuffer.position(ByteBuffer.java:812)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at com.android.networkstack.netlink.TcpSocketTracker.skipRemainingAttributesBytesAligned(TcpSocketTracker.java:427)

Missing hardware:
12-28 09:27:59.244 0 0 E sdhci_msm_vreg_disable: vdd-io Cannot find Regulator
12-28 09:27:59.253 0 0 E samsung_dsi_panel_event_handler: unknown event (7)

RIL:
12-28 09:23:00.594 474 815 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=72
12-28 09:23:00.596 474 474 E RIL-QMI : qmuxd: RX 47 bytes on fd=21 from qmux_client_id=0x1
 
Last edited:

ttesty

Senior Member
Dec 17, 2010
65
9
G900T.. CrDroid 7.0 lineage-18.1-20201225-INOFFICIAL-klte.zip... BitGapps v19 .. Magisk 21.1 ... TWRP 3.4... latest Modem.
Radio: G900TUVU1GRJ1 (6.0.1)

Good news: mostly everything works fine (including cellular data, calls, apps).
Problems: Google Maps crash (have to use incognito mode as workaround), Location data limited to GPS only (not AGPS/cellular).

Abnormal errors (most were there in previous releases, and these are periodic/frequent, seen in some other 18.x ROMs):

AGPS Location (partly related to BitGapps v19):
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: Failed:
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: java.lang.SecurityException: uid 10005 does not have android.permission.ACCESS_FINE_LOCATION.
12-28 09:22:53.058 2118 2118 E IndoorOutdoorPredictor: at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
12-28 09:18:28.399 866 1040 W ActivityManager: Appop Denial: Accessing service com.google.android.gms/com.google.android.location.internal.server.GoogleLocationService from pid=2118, uid=10005 requires appop COARSE_LOCATION

TCP read errors:
12-28 09:29:36.462 1321 2335 E TcpSocketTracker: Unexpected socket info parsing, family 10 buffer:java.nio.HeapByteBuffer[pos=96 lim=588 cap=60000] xAAAABQAAgAAAAAAKQUAAAoBAADVBBRsAAAAAAAAAAAAAP//CsRBmgAAAAAAAAAAAAD//0p9ibwAAAAAAIt51wAAA
....
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: java.lang.IllegalArgumentException: Bad position 65632/588
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.Buffer.position(Buffer.java:259)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at java.nio.ByteBuffer.position(ByteBuffer.java:812)
12-28 09:29:36.469 1321 2335 E TcpSocketTracker: at com.android.networkstack.netlink.TcpSocketTracker.skipRemainingAttributesBytesAligned(TcpSocketTracker.java:427)

Missing hardware:
12-28 09:27:59.244 0 0 E sdhci_msm_vreg_disable: vdd-io Cannot find Regulator
12-28 09:27:59.253 0 0 E samsung_dsi_panel_event_handler: unknown event (7)

RIL:
12-28 09:23:00.594 474 815 E RIL-QMI : qmuxd: TX message on fd=21, to qmux_client_id=0x1, len=72
12-28 09:23:00.596 474 474 E RIL-QMI : qmuxd: RX 47 bytes on fd=21 from qmux_client_id=0x1

This seemed to fix a few of the problems. Some of the problems might not be exclusive to the ROM - rather GAPPS etc:

pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
 

gaindelioide

Member
Mar 23, 2020
15
27
Once again thanks a lot Mr Haggertk for bringing android 11 to our beloved Samsung Galaxy S5. Here are some screenshots made with my SM-G900F
 

Attachments

  • Screenshot_20201229-145111_1.png
    Screenshot_20201229-145111_1.png
    122.5 KB · Views: 600
  • Screenshot_20201229-145226_Trebuchet.png
    Screenshot_20201229-145226_Trebuchet.png
    136.5 KB · Views: 594
  • Screenshot_20201229-150810_Trebuchet-01 (1).jpeg
    Screenshot_20201229-150810_Trebuchet-01 (1).jpeg
    193.5 KB · Views: 504
  • Screenshot_20201229-152023_Trebuchet-01 (1).jpeg
    Screenshot_20201229-152023_Trebuchet-01 (1).jpeg
    114.5 KB · Views: 511
...Here are some screenshots made with my SM-G900F

Thanks for the effort 👍 but 2 comments:

You should not post personal data like your device's IMEI & Vorschau > Eindeutige id. You could black them out with an image editor or just delete those screenshots.

Because the common language in this thread is English maybe you could change the System language to that before taking the screenshots?

How does the Settings panel looks like?
***

And for you guys who ran LineageOS 17.1 previously: any noticeable changes you could comment on?
***
 

ttesty

Senior Member
Dec 17, 2010
65
9
Pretty stable. I get a lot of these messages for many different applications and during boot time. Probably normal page faults (data missing from memory).

12-30 00:24:14.808 0 0 F : pgd = d4dbc000
12-30 00:24:14.808 0 0 F : [00000000] *pgd=00000000
12-30 00:24:14.808 0 0 W Pid : 32432, comm: hone.app2sd.pro
12-30 00:24:14.808 0 0 W : CPU: 0 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
12-30 00:24:14.808 0 0 W : PC is at 0x7215022a
12-30 00:24:14.808 0 0 W : LR is at 0x72150227
12-30 00:24:14.808 0 0 W pc : [<7215022a>] lr : [<72150227>] psr: 600e0030
12-30 00:24:14.808 0 0 W sp : be853ce0 ip : 00000000 fp : be853d4c
12-30 00:24:14.808 0 0 W : r10: 136b32c0 r9 : ade4ce00 r8 : 00000000
12-30 00:24:14.808 0 0 W : r7 : 00000000 r6 : 136b32c0 r5 : 00000000 r4 : 00000000
12-30 00:24:14.808 0 0 W : r3 : 00000001 r2 : 00000000 r1 : 00000000 r0 : 717b4f84
12-30 00:24:14.808 0 0 W Flags : nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
12-30 00:24:14.808 0 0 W Control : 10c5787d Table: 14dbc06a DAC: 00000015
12-30 00:24:14.808 0 0 W : [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
12-30 00:24:14.808 0 0 W : [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
12-30 00:24:14.808 0 0 W : [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
12-30 00:24:14.808 0 0 W : [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
12-30 00:24:14.808 0 0 W : Exception stack(0xd222bfb0 to 0xd222bff8)
12-30 00:24:14.808 0 0 W bfa0 : 717b4f84 00000000 00000000 00000001
12-30 00:24:14.808 0 0 W bfc0 : 00000000 00000000 136b32c0 00000000 00000000 ade4ce00 136b32c0 be853d4c
12-30 00:24:14.808 0 0 W bfe0 : 00000000 be853ce0 72150227 7215022a 600e0030 ffffffff

12-30 00:29:17.388 0 0 F : pgd = d8634000
12-30 00:29:17.388 0 0 F : [00000000] *pgd=00000000
12-30 00:29:17.388 0 0 W Pid : 4629, comm: verycallcontrol
12-30 00:29:17.388 0 0 W : CPU: 0 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
12-30 00:29:17.388 0 0 W : PC is at 0x7215022a
12-30 00:29:17.388 0 0 W : LR is at 0x72150227
12-30 00:29:17.388 0 0 W pc : [<7215022a>] lr : [<72150227>] psr: 600b0030
12-30 00:29:17.388 0 0 W sp : be854930 ip : 00000000 fp : 132bb498
12-30 00:29:17.388 0 0 W : r10: 132bc0a8 r9 : ade4ce00 r8 : 00000000
12-30 00:29:17.388 0 0 W : r7 : 00000000 r6 : 132bc0a8 r5 : 00000000 r4 : be8529b8
12-30 00:29:17.388 0 0 W : r3 : 00000001 r2 : 00000000 r1 : 00000000 r0 : 717b4f84
12-30 00:29:17.388 0 0 W Flags : nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
12-30 00:29:17.388 0 0 W Control : 10c5787d Table: 1863406a DAC: 00000015
12-30 00:29:17.388 0 0 W : [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
12-30 00:29:17.388 0 0 W : [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
12-30 00:29:17.388 0 0 W : [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
12-30 00:29:17.388 0 0 W : [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
12-30 00:29:17.388 0 0 W : Exception stack(0xd86b9fb0 to 0xd86b9ff8)
12-30 00:29:17.388 0 0 W 9fa0 : 717b4f84 00000000 00000000 00000001
12-30 00:29:17.388 0 0 W 9fc0 : be8529b8 00000000 132bc0a8 00000000 00000000 ade4ce00 132bc0a8 132bb498
12-30 00:29:17.388 0 0 W 9fe0 : 00000000 be854930 72150227 7215022a 600b0030 ffffffff
12-30 00:29:17.616 0 0 E [SSP] : proximity_open_calibration - Can't open cancelation file
12-30 00:29:17.616 0 0 E [SSP] : set_proximity_threshold - SENSOR_PROXTHRESHOLD
 
Last edited:

gaindelioide

Member
Mar 23, 2020
15
27
Thanks for the effort 👍 but 2 comments:

You should not post personal data like your device's IMEI & Vorschau > Eindeutige id. You could black them out with an image editor or just delete those screenshots.

Because the common language in this thread is English maybe you could change the System language to that before taking the screenshots?

How does the Settings panel looks like?
***

And for you guys who ran LineageOS 17.1 previously: any noticeable changes you could comment on?
***
Hi curiousrom,
Thank you for yours advices. Could you please tell me precisely what you mean with the "Settings panel"? The QS panel or the General Settings panel?

I can tell you that since I flashed the ROM I have not had any particular issue worth a mention in my system. Only WhatsApp crashes from time to time. The phone app is behaving the way I expected it. The sensor is functioning properly since I do not see a black screen anymore after a call. With LineageOS 17.1 that still persist.

I will stay in touch through this thread for reporting any misbehavior of the system. Mr Haggertk is really doing a great job for the owners of our legendary device Samsung Galaxy S5. I own an SM-G900F.
 

ttesty

Senior Member
Dec 17, 2010
65
9
Some of the unhandled page faults on startup (there are many):

[ 60.743339] CPU: 1 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
[ 60.743345] PC is at 0x7118e758
[ 60.743348] LR is at 0x7118e755
[ 60.743353] pc : [<7118e758>] lr : [<7118e755>] psr: 60000030
[ 60.743355] sp : 92bec890 ip : 00000000 fp : 92bec904
[ 60.743359] r10: 92bec940 r9 : ac1f1400 r8 : 00000000
[ 60.743364] r7 : 137cbb60 r6 : 00000000 r5 : 00000000 r4 : 57fb4540
[ 60.743368] r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 70831754
[ 60.743374] Flags: nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
[ 60.743379] Control: 10c5787d Table: 2489c06a DAC: 00000015
[ 60.743399] [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
[ 60.743410] [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
[ 60.743419] [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
[ 60.743429] [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
[ 60.743435] Exception stack(0xe3acdfb0 to 0xe3acdff8)
[ 60.743440] dfa0: 70831754 00000000 00000000 00000000
[ 60.743446] dfc0: 57fb4540 00000000 00000000 137cbb60 00000000 ac1f1400 92bec940 92bec904
[ 60.743452] dfe0: 00000000 92bec890 7118e755 7118e758 60000030 ffffffff
[ 60.778394] Thread-1: unhandled page fault (11) at 0x00000000, code 0x005
[ 60.778402] pgd = e489c000
[ 60.778591] [00000000] *pgd=00000000

[ 67.835852] Pid: 2836, comm: APIGuard3Backgr
[ 67.835860] CPU: 2 Tainted: G W (3.4.113-lineageos-g11473dbb0031 #18)
[ 67.835867] PC is at 0x7d48bc70
[ 67.835871] LR is at 0x712ba17f
[ 67.835877] pc : [<7d48bc70>] lr : [<712ba17f>] psr: 000f0030
[ 67.835880] sp : 7b20aa80 ip : 00000000 fp : 00000060
[ 67.835885] r10: 00000000 r9 : a9774e00 r8 : 00000000
[ 67.835891] r7 : 12cd26e8 r6 : 12cd24b8 r5 : 12cd2708 r4 : 710feac8
[ 67.835897] r3 : 70f53c50 r2 : 12cd2708 r1 : 00000000 r0 : 00000003
[ 67.835904] Flags: nzcv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
[ 67.835910] Control: 10c5787d Table: 1e69406a DAC: 00000015
[ 67.835932] [<c010be28>] (unwind_backtrace+0x0/0xec) from [<c01121a8>] (__do_user_fault+0x100/0x14c)
[ 67.835945] [<c01121a8>] (__do_user_fault+0x100/0x14c) from [<c011251c>] (do_page_fault+0x328/0x36c)
[ 67.835957] [<c011251c>] (do_page_fault+0x328/0x36c) from [<c0100358>] (do_DataAbort+0x10c/0x200)
[ 67.835969] [<c0100358>] (do_DataAbort+0x10c/0x200) from [<c01059d4>] (__dabt_usr+0x34/0x40)
[ 67.835976] Exception stack(0xdecdffb0 to 0xdecdfff8)
[ 67.835982] ffa0: 00000003 00000000 12cd2708 70f53c50
[ 67.835990] ffc0: 710feac8 12cd2708 12cd24b8 12cd26e8 00000000 a9774e00 00000000 00000060
[ 67.835998] ffe0: 00000000 7b20aa80 712ba17f 7d48bc70 000f0030 ffffffff
 

yoshkapundrick

Senior Member
Mar 17, 2016
205
50
Minor issue. When logging in to my wifi which is wpa enterprise it requires a domain name as the phase 2 authentication defaults to MSCHAPV2 and has no option for "do not authenticate". Since I don't know my domain name is there a workaround?
 
...
  • All builds except for klteactivexx MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
  • You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.

See S5 Odin Flashable Modem & Bootloader and S5 Screen Lock Fingerprint Battery Tests @ Idle - BetterBatteryStat.
***
 
  • Like
Reactions: dcarvil

Prove N.

Senior Member
Aug 23, 2015
212
186
It seems like my SC-04F doesn't show charging when I plugged in. The % goes up after rebooting.

Baseband: SC04FOMU1XQH1 (latest)
ROM Build: kltekdi, build 20201225

These are the logs when I only wiped System and Cache. I later formatted Data and it's still the same.

Thank you for your work!

e: Logcat: https://pastebin.pl/view/4de644ca
dmesg is the uploaded file.

e3: after formatting. Had to have Magisk to get dmesg log
dmesg: https://pastebin.pl/view/46bc06dc
logcat: https://pastebin.pl/view/1d2b50a8
 

Attachments

  • kmsg-SC-04F-11.txt
    39 bytes · Views: 16
Last edited:

HaniAhsan

New member
Jan 1, 2021
3
1
Hey @haggertk, I have a SM-S902L. Can I use the rom for SM-S900L for my device? If not would you be so kind and add support for my model? I had been waiting for lineage 17.1 for quite some time now and installed an unofficial build to get android 10. I just found this amazing thread which is a way for me to get android 11. :love: Please consider my request. Thanks ;)
 
  • Like
Reactions: hiariq

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    @jimsters sure it's ok to post but might get more attention if not posted in an abandoned thread. 😉
    This is official now.
    1
    @jimsters sure it's ok to post but might get more attention if not posted in an abandoned thread. 😉
    This is official now.
    ah ok thanks
  • 53
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps) . LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    Device source code:
    Kernel source code:
    My picks:

    Build Compatibility:
    The noted models are the only ones supported. If you have a model that isn't listed and ask politely then I might work to add compatibility.​
    BuildModel
    klteSM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8
    klteactivexxSM-G870F
    klteaioSM-G900AZ, SM-S902L
    kltechnSM-G9006V, SM-G9008V
    kltechnduoSM-G9006W, SM-G9008W, SM-G9009W
    klteduosSM-G900FD, SM-G900MD
    kltedvSM-G900I, SM-G900P
    kltekdiSC-04F, SCL23
    kltekorSM-G900K, SM-G900L, SM-G900S

    Downloads:
    Installation Instructions:
    • Download latest build
    • Boot into recovery
      • Lineage recovery images are included in the download section and that's what I support. If you feel like using TWRP and something isn't working then take it up with the TWRP maintainer
    • If not updating from one of my earlier unofficial builds, then format/system, /data, and /cache
      • For Lineage recovery:
        • Format -> Format data/factory reset (this does /data and /cache)
        • Format -> Format system partition
      • For TWRP figure it out. And no, "wipe data" isn't the same as formatting data
    • Install LineageOS zip
    • If this is your initial installation of LineageOS 18.1, then flash any addons (e.g., gapps)
    Reporting Bugs:
    • DO NOT even think about reporting bugs if you are running a custom kernel, Magisk, or Xposed
    • Grab a logcat after the problem has occurred
    • If there is a random reboot then grab /proc/last_kmsg. A logcat AFTER the reboot will be worthless
    • Note which build AND device you have
    • Read the thread, at least the last month's worth of posts. Don't report things that others already have.
    Compatibility Notes:
    • Bootloader version doesn't matter. Anyone who tells you so doesn't know what they are taking about. My Developer Edition G900V is still running the original 4.4.2 KK aboot. My G900W8 is running the latest 6.0.1.
    • All builds except for klteactivexx MUST be running a marshmallow (6.0.1) radio for RIL to work. If you are about to report that RIL/radio isn't working then I pretty much guarantee this is your issue.
    • You MUST be running a marshmallow (6.0.1) NON-HLOS for the fingerprint reader to work. If you are about to report a fingerprint reader problem then you either have old firmware (update it), your /data was previously encrypted and you performed a "clean" flash without FORMATTING /data (start over and FORMAT /data), or your reader is just broken.
    • External SD cards don't support POSIX (ext*, f2fs) or NTFS filesystems anymore. It was kind of broken in 17 and we likely won't merge the changes to add it back in for 18. I'm not going to pick the open changes to re-add support because I'm not going to deal with "but it worked on haggertk's unofficial builds" bug reports after we eventually go official. If this affects you then just bite the bullet, copy any data off you really want to save, and reformat as exfat.
    Donations:
    • I absolutely don't personally accept them. If you really feel that this work deserves it, then find a local food bank or animal shelter/rescue and throw some money their way. You can also throw some the way of LineageOS, but we're actually doing pretty well right now.
    23
    Note that the Galaxy S5 klte family is not included in the initial promotion but should follow eventually.

    I'll probably ship in the coming week. They're ready, but I don't want to be the first set our the door on the infra. As it is, we're already flying this thing in direct law tonight.
    9
    Official LineageOS 18.1 for the Galaxy S5 klte family Launched!

    FYI these haggertk's commits are now marked as Merged so it should be available in the next update if all goes well with the Lineage automated builder:
    And it's confirmed in the LineageOS build target list and the wiki pages https://wiki.lineageos.org/devices/ also.

    The respective wiki pages include an upgrade guide.

    Thank you to the Lineage Team & Mr. haggertk for keeping our old S5 up to date. :cool: 👍
    ***
    9
    Official LineageOS 18.1 Launched!

    FYI the Official LineageOS 18.1 is launched as you can read in this official blog: Changelog 25 - Exemplary Eleven, Ravishing Recorder, Captivating Calendar, Beaming Backup

    The first batch of builds should be available starting 2021-04-01 if all goes well with with the LineageOS automated builder. Click on nightly even if the lineage-16.0 label has not been updated yet.

    Note that the Galaxy S5 klte family is not included in the initial promotion but should follow eventually.
    ***
    7
    Hey @haggertk, I have a SM-S902L. Can I use the rom for SM-S900L for my device? If not would you be so kind and add support for my model? I had been waiting for lineage 17.1 for quite some time now and installed an unofficial build to get android 10. I just found this amazing thread which is a way for me to get android 11. :love: Please consider my request. Thanks ;)

    Yeah, that's easy -- I dropped G900AZ and S902L during 17.1 bring-up because I wasn't about to formally fork a device tree and create a new build for those devices that needed <M RIL stack without any evidence of a continuing userbase. I have the work already done locally for 17. One commit in that device tree and then importing the vendor blobs will have it done for 18.