yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] ArastaD0t:
I have a problem with wifi, they tell me there is no internet access, how can I send some useful logs or how i can help?
[Samsung Galaxy S 5 Unified Development] kurtn:
AFAIK the setup wizard has no section for WiFi log in. Do it manually.
[Samsung Galaxy S 5 Unified Development] Andresine:
Clean install and format data on my SM-G900F and bluetooth does not work .
[Samsung Galaxy S 5 Unified Development] Andresine:
Anyone text bluetooth?
[Samsung Galaxy S 5 Unified Development] vlad3647:
in my case is no working
[Samsung Galaxy S 5 Unified Development] Andresine:
Ok thanks cause i supose that only was my phone
[Samsung Galaxy S 5 Unified Development] kltelegacy:
Bluetooth doesn't work for me either. My phone can see and pair with devices but won't connect to them.
[Samsung Galaxy S 5 Unified Development] ArastaD0t:
I have a problem with wifi, they tell me there is no internet access, how can I send some useful logs or how i can help
[Samsung Galaxy S 5 Unified Development] Username already in use:
This is fantastic news!

Now i can rest assured that my daily driver will continue to be usable after the updates stop for Los 18.1 (which i´m currently on).

In my country (Sweden), 3G will be available to atleast 2025. There is no Android phone that has what i´m looking for anymore... Weird aspect ratio, non removable battery, no Lineage support, no headphone jack, no notification led etc. etc.

Your work is very much appreciated mr Khalvat!
[Samsung Galaxy S 5 Unified Development] kurtn:
New "do not disturb" mode is amazing. No sound or vibration at all. - on i9300. Bug on klte: we still get vibrations on swipe up gestures, hardware back and menu button and keyboard.

Sorry. Maybe its a bug vom lineageOS sources. I9300 was no good comparison. There I don't have any vibration with 20.0
[Samsung Galaxy S 5 Unified Development] brt4722:
Thanks khalvat. I will wait with installing.
[Samsung Galaxy S 5 Unified Development] khalvat:
Build 2022-10-05

Merged october security patch

fixed home button

fixed bluetooth connect

selinux is enforcing
[Samsung Galaxy S 5 Unified Development] brt4722:
Installed the updated build. Bluetooth connects but sound goes via mobile, not earbuds.
[Samsung Galaxy S 5 Unified Development] Andresine:
Installed the update and my emulated 0 folder is empty. I cant access to my data in my file explorer. Only show external sd. I will try install the 27-09-2022 one.
[Samsung Galaxy S 5 Unified Development] Andresine:
the same problem with 27-o9-2022 rom. i made a full wipe a format data and a clean install and the problem is gone . i supose that maybe is for magisk . i dont know, home button works great but i cant connect with other device with bluetooth.
[Samsung Galaxy S 5 Unified Development] kurtn:
Phone reboots with every APP uninstallation. No WiFi internet connection after such a reboot
[Samsung Galaxy S 5 Unified Development] Andresine:
Yes, me too.
[Samsung Galaxy S 5 Unified Development] ArastaD0t:
sorry my bad, i dont do fresh install, i do it now and Wifi Internet connection is working and SD Card now doesnt ned be Formated! But Connecting to bluetooth Headohones still isnt working :( (klte G900F)

Otherwise thanx Khalvat for this work
[Samsung Galaxy S 5 Unified Development] brt4722:
Also
[Samsung Galaxy S 5 Unified Development] brt4722:
Phone is faster then with lineageos 19.
[Samsung Galaxy S 5 Unified Development] Labad Shabawar 142:
I understand very well , no offence taken . I'm new to XDA , and couldn't figure out how to start a new post . And as such I decided to jump into any post and was hoping whoever replied would tell me how to do that . But please forgive me I meant no harm , I'm just desperate to find the files I need . Could you tell me how I start a new thread . Thanks
[Samsung Galaxy S 5 Unified Development] EyzTOP01.L:
Working pretty well on G900M or klteubb (Latin America Model or Vodafone model). Except from some minor bugs: ⭕Accelerometer sensor not detected as shown in "Device Info Hw", so that auto-rotation doesn't work nor a rotate-button pops-up when doing so.⭕ As well fingerprint is not so smoothly recognized when trying to unlock screen as in stock-rom.

Build Number: G900MUBS1CQAD.

Thank you very much for this stable-ROM.

PD: Sorry for the low-recording quality
[Samsung Galaxy S 5 Unified Development] Razizi:
Hi Guys, this ROM disables the touch buttons. I don't see anyone with the same issue... any ideas?
[Samsung Galaxy S 5 Unified Development] DarkSteve:
I wasn't familiar with "Device Info Hw", that's quite a nifty little app!

I'm running the current build (2023-06-23), and all sensors worked fine for me. The little soccer ball moved around the field, the gyroscope worked, etc. (This is on a standard klte, my kltedv is still running khalvat's older 2022-12-27 build.)

Again, on my klte with the latest build, I can unlock the phone using my fingerprint flawlessly every time.

Maybe this is a klte vs kltedv vs klteduos vs kltechn (etc) issue?

Sorry, I haven't experienced that issue on my klte - out of curiosity, what model of phone do you have?

My klte is my test/play phone, the device I try all this stuff out on. But my kltedv is my main phone that I rely on, so I'm more conservative when it comes to updates. It's working perfectly now running December's build, so I'm hesitant to update without a good security reason.

Absolutely, thank you very much khalvat!

Given the age of the phone, I'm impressed you can get any modern OS running on it so well.
[Samsung Galaxy S 5 Unified Development] Razizi:
I have a Samsung G900F which is klte I believe.

Can I ask you what version of TWRP you are using?

and which GApps?

I tried wiping the entire phone and flash LineageOS20... but no luck with touch butons.

I can't figure it out why the touch buttons don't work. only the home button works...
[Samsung Galaxy S 5 Unified Development] Razizi:
SILLY ME, it turns out I downloaded klteactivexx instead of klte ROM. OOPS. i'll try klte now!
[Samsung Galaxy S 5 Unified Development] kurtn:
So you enabled gesture navigation? Change to three button navigation
[Samsung Galaxy S 5 Unified Development] CLAUDIO 969:
almost everything works apart from some lag but the stock camera is wrong the resolution i had to install a camera apk

anyway thanks 1000 to Mr. khalvat for the great work
[Samsung Galaxy S 5 Unified Development] EyzTOP01.L:
Mine is klteubb; Anyone more has tested this ROM on it?

-- Build number (take it only as reference): G900MUBS1CQAD. --
[Samsung Galaxy S 5 Unified Development] DarkSteve:
My klte is a G900F like yours, my kltedv is a G900I.

I'm using twrp-3.7.0_9-0-klte, which should work on the entire klte family. I'm using it on both my klte and kltedv.

I don't use gapps, I switched to Cyanogenmod (later Lineage) to get away from google's spyware!

Oh, d'oh!

I bricked my tablet last year doing something similar :geek: Hopefully the right ROM will solve the issue :)
[Samsung Galaxy S 5 Unified Development] DarkSteve:
:unsure: I've never heard of that model.

Khalvat doesn't have a build specific for it - which build are you using? From what I can see, he's only got builds for:

klteaio

klteactivexx

kltekor

kltekdi

kltedv

kltechnduo

klteduos

kltechn

klte

I'm guessing this is the source of your sensor issues!

EDIT: Just in case people are having trouble finding the build for their specific device, here is the link to the parent folder. Just choose your device :cool:
[Samsung Galaxy S 5 Unified Development] DarkSteve:
I was just thinking, I think a lot of people are probably having issues due to using the wrong build.

It appears that the klteactivexx build has a disproportionate number of downloads compared to the device's popularity:

Double-check which build you downloaded if you're having trouble!

EDIT: Ah, I see the issue. The most recent upload is highlighted at the top of the page:

But the most recent upload is not the build most people need, it's just the last model to have it's build uploaded.

Again, make sure you have the correct build for your phone before posting about things not working!
[Samsung Galaxy S 5 Unified Development] brt4722:
Is twrp possible on s5 g900A.

Is android 13 also possible.

Cant find a working twrp
[Samsung Galaxy S 5 Unified Development] DarkSteve:
A few years back, the official maintainer of LineageOS's klte family (haggertk) posted that the G900A is no longer supported in the klte build, sorry. I'm guessing the source that Khalvat is using also doesn't support your phone.

I could be wrong, so keep searching for your model, but be prepared for bad news!

EDIT: Some hope for you, I found a thread about rooting and flashing your phone. It's several years old, but better than nothing!

Also, your phone model is klteatt which may help when searching for ROMs and guides, such as this one.
[Samsung Galaxy S 5 Unified Development] brt4722:
Thanks. I will search.
[Samsung Galaxy S 5 Unified Development] brt4722:
No custom Rom. I did flashed it to android 6 stock rom. It came with android 5. Better than nothing
[Samsung Galaxy S 5 Unified Development] vlad3647:
Android 5?
[Samsung Galaxy S 5 Unified Development] brt4722:
Yes
[Samsung Galaxy S 5 Unified Development] brt4722:
My s5 came with 5 so upgrade it to 6
[Samsung Galaxy S 5 Unified Development] DarkSteve:
Sounds about right. The first S5 models came out with Android 4.4 KitKat. Later ones came with Android 5, and the last ones came with 6.
[Samsung Galaxy S 5 Unified Development] abiyar77:
i have samsung s5 sm-G900f

i download this vertion

i love it but the back button and the recents button don't work

is that the wrong ROM and my TWRP work normaly can it be the TWRP version ?
[Samsung Galaxy S 5 Unified Development] kurtn:
Yes. Wrong version. Your phone is klte without any additional letters.
[Samsung Galaxy S 5 Unified Development] abiyar77:
can you give me the link of the right version please
[Samsung Galaxy S 5 Unified Development] kurtn:
The link is in OP
[Samsung Galaxy S 5 Unified Development] abiyar77:
uh ok thank you.
[Samsung Galaxy S 5 Unified Development] Abøú:
Custom kernel support
[Samsung Galaxy S 5 Unified Development] loubri:
Hey, i think i got a bug.

I tryd to share the screen with my TV today and the phone turned with a blakscreen into a restart.

Maybe it can be fixed. (I made a clean flash with the "lineage-20.0-20230623-UNOFFICIAL-klte.zip)

I like the Rom very much. Good work so far. (y)

A big THX from my side.🤓
[Samsung Galaxy S 5 Unified Development] cicada 3301:
My phone is s5 sm-G900f, i'm using "lineage-20.0-20230623-UNOFFICIAL-klte.zip"

The ROM is amazing, but the Bluetooth is unstable when I use earbuds. Sometimes the Bluetooth turns off and reconnect after 5 seconds. This happens randomly, sometimes after 15 minutes, sometimes after an hour, and sometimes every 5 minutes.
[Samsung Galaxy S 5 Unified Development] Abøú:
why vdd restriction cannot be toggled off
[Samsung Galaxy S 5 Unified Development] Abøú:
why this app force-stop
[Samsung Galaxy S 5 Unified Development] Abøú:
i just want the best for our S5
[Samsung Galaxy S 5 Unified Development] DarkSteve:
I experience this too, but I was also getting that with previous official LineageOS releases. It happens with both my klte and my kltedv. It seems to happen more or less often depending on the bluetooth device, and I don't think it has anything to do with the quality of bluetooth device. My Bose noise-cancelling bluetooth headphones cost me hundreds of dollars, and it still drops out occasionally.

It also manifests in different ways depending on the device. For example, I have a bluetooth speaker that will often disconnect at the end of songs. I have to switch the speaker off and back on for it to reconnect. But my bluetooth headphones will randomly drop out for a fraction of a second at almost any time, but at the end of songs will occasionally disconnect and instantly reconnect - "Samsung Galaxy S5 lost, connected to Samsung Galaxy S5".

It's not the headphones, because it never happens when I connect to my HTPC or someone else's device. Also, it doesn't appear to happen when I connect to my Samsung Galaxy Tab A (gta3xlwifi), currently running Magendanz's LOS18. (I didn't upgrade to 19.1 because that build has gapps baked in.) I suspect it's a quirk of the bluetooth hardware in the klte family of phones. It happens with mulitple LOS versions from multiple devs, and only with that model of phone.

I don't have a solution, sorry. But it's definitely not just you! I have found it happens less often with khalvat's unofficial builds than with the official builds, but that could be a LOS20 thing rather than a khalvat/haggertk thing (the official builds only go up to LOS18).

Lastly, do you install gapps? I don't, so I was wondering if that was a factor?
[Samsung Galaxy S 5 Unified Development] cicada 3301:
are you sure its a quirk of the Bluetooth hardware because my earbuds was working flawlessly when i was using android 6, and yes im using gapps.
[Samsung Galaxy S 5 Unified Development] DarkSteve:
Yeah, and bluetooth had no problem on my phone with the stock hardware as well, hence it's a quirk of the hardware on this phone.

The bluetooth hardware was better controlled by the proprietary software the phone shipped with. The lack of this proprietary software, I believe, is the cause of the problem. The driver itself mostly works, but it needs additional software to keep it working smoothly.

And thanks for the info about gapps. Now I know it has nothing to do with google's proprietary stuff. I'm guessing it's a proprietary Samsung thing instead.
[Samsung Galaxy S 5 Unified Development] cicada 3301:
thank you for sharing this information i hope the open source community find a solution to control the hardware like Samsung proprietary software did.
[Samsung Galaxy S 5 Unified Development] curiousde2002:
Hi everybody,

I'd like to upgrade my klte from the February build to this one "lineage-20.0-20230623-UNOFFICIAL-klte" via a dirty install.

In the past I always did this by deinstalling magisk and all the modules, then wiping system, dalvik and cache and then flashing ROM, Gapps and finally magisk again.

My question now:

Would you recommend formatting system at all and if so, what about magisk?

Does it survive wiping the system, so better not touch it?

I'm asking this because I recently had bootlooping after deinstalling magisk, so maybe no need to deinstall it before doing all the wipes.

Thank you very much in advance!
[Samsung Galaxy S 5 Unified Development] Trim30:
Good day everyone. Previously I had lineage 18.1 installed on my galaxy S5 model G900V, and I decided to install Lineage 20 that in this forum describe, the klte version, I had some other problems but I was finally able to install it. When trying this new system I realized an error or problem, when I have the phone turned off and I put it to charge the screen appears with the battery symbol and a few moments later the screen turns off and turns on again showing me the battery symbol and this cycle repeats itself constantly without changing. Can you help me solve this problem, it will only happen with my cell phone or it is part of the system. Thanks for your help.
[Samsung Galaxy S 5 Unified Development] kurtn:
Did you enable advanced charging control? It is harmful.
[Samsung Galaxy S 5 Unified Development] Trim30:
Thanks Kurtn, I had charging control activated, I deactivated it but the same problem continues
[Samsung Galaxy S 5 Unified Development] EyzTOP01.L:
I've finally figured out: is not a software issue, nor an OS build error. Simply my device's previous owner had let it stump, so probably that has impacted on the sensor and made it disattach on a hardware-level. Sorry for the inconvenience caused on this thread. Aside from my faults, everything including the fingerprint works pretty well. ✔✔✔
[Samsung Galaxy S 5 Unified Development] asdf2345:
This made my phone bootloop. I don't know if it's related but my phone is the SM-G902L which never got anything past 4.4.2. The Optimized 7.1.2 ROM seems fine, and that is probably what I will end up actually using on this phone.

Edit: Nevermind, I apparently had to use klteaio. Not sure what the difference from klte is, but it worked so whatever.
[Samsung Galaxy S 5 Unified Development] DarkSteve:
We went over this a couple of pages ago, with people having all sorts of issues because they're installing the wrong build.

It shouldn't be surprising that the different versions of the Galaxy S5 are different. They're literally not the same hardware configuration, hence the need for different builds.

Khalvat has released builds for:

klteaio

klteactivexx

kltekor

kltekdi

kltedv

kltechnduo

klteduos

kltechn

klte

He isn't hiding them, they're all neatly organised into their own folders along with a recovery image (in case you're not using TWRP). I'm baffled that page after page is full of people posting about how their phone doesn't work after installing a build for a different phone.
[Samsung Galaxy S 5 Unified Development] asdf2345:
My question is why does klte work for other ROMs, but this one needs klteaio? I only picked it because aio made me think all in one and I wanted to see if it would do anything.
[Samsung Galaxy S 5 Unified Development] DarkSteve:
I cannot fathom the confusion of thoughts that formed this question. It's nonsensically phrased.

Klte is the phone, it doesn't "work for other ROMs", you need the ROM for klte for it work on the klte phone. Just like you need the klteaio ROM if you want it to work on the klteaio phone. I have two phones, a klte and a kltedv, and I need to download both the klte ROM and the kltedv ROM to suit my two phones.

If you'd actually read (or just skimmed) the forum, you'd see page after page of people installing the klte ROM on their non-klte phone, then complaining it doesn't work. Just like you did.

You'd also see people installing the klteactivexx ROM on their non-klteactivexx phone and having issues. This was more understandable as the Sourceforge page highlighted that ROM as "the latest". People assumed it was the latest klte ROM instead of the latest ROM Khalvat uploaded.

So to answer you broken question, the klte doesn't work for other ROMs (whatever that means), and you need the klteaio ROM because you have a klteaio phone.
[Samsung Galaxy S 5 Unified Development] LineArc:
Any chance of getting it for AT&T galaxy S5 active?
[Samsung Galaxy S 5 Unified Development] DarkSteve:
Yes, there's a 100% chance, as it's still officially supported, and Khalvat provided LOS20 builds for the Galaxy s5 Active almost a year ago. I even linked you to the ROM three comments above yours. If only you could be bothered reading.

The most basic research is beyond you, huh?
[Samsung Galaxy S 5 Unified Development] LineArc:
Well thank you but my active model number is 850A which I could find earlier. Let's see if I could find it now
[Samsung Galaxy S 5 Unified Development] kurtn:
That's a completely different device.

Samsung Galaxy Alpha (S801) - Full phone specifications

www.gsmarena.com
[Samsung Galaxy S 5 Unified Development] DarkSteve:
:ROFLMAO:

So you don't have an S5 Active, you have an S5 Alpha.

Friggan hilarious 😹

EDIT: Apparently you have a locked bootloader, as per this thread:

This ROM does not work with Exynos variant (SM-G850F) nor a locked bootloader (SM-G850A).
[Samsung Galaxy S 5 Unified Development] curiousde2002:
Hi everybody,

looks like I bricked my klte.

It was on the latest build "lineage-20.0-20230623-UNOFFICIAL-klte" and due to a very laggy performance I decided to clean install the same ROM without Gapps.

I swiped factory reset in TWRP-3.7.0_9-0-klte but then I wanted also system to be wiped so I wiped dalvik, system, data and cache right after the factory reset.

When I tried to reboot into recovery (what I always do after any kind of wipe) it was stuck at the TWRP splash screen.

I tried several times, removed the battery and even reflashed TWRP-3.7.0_9-0-klte via Odin.

Odin showed "passed", but same result.

I can boot into download mode, but booting into recovery always ends up at the splash screen. :(

Thanks for any help!
[Samsung Galaxy S 5 Unified Development] DarkSteve:
Hmm, I bricked my Samsung Galaxy Tab A 10.1 last year, and couldn't get into TWRP. Took me ages just to get into download mode so I try reflashing.

Ultimately, I had to re-flash the stock rom, which got everything working again, then I flashed TWRP, then I used TWRP to wipe the device and install LOS from the SD card. All good from there.

I haven't had this issue on my phone, but re-flashing stock on my tablet got the device back to a "known point" which allowed me to get back to LOS. Try this as a fallback if you run out of ideas.

My last thoughts:

Redownload TWRP, just in case your copy has been corrupted in some way (e.g. bitrot).

Also, and I'm not trying to tell you to suck eggs, but verify you really have a klte (and not a variant). This has bitten lots of people in the past.

Make sure you're flashing the correct rom and not a rom for one of the variants. Lots of people in this forum accidentally downloaded the activexx variant rom, or they think the klte rom will work on the entire klte family, which it won't.

Good luck! (You can find stock roms on Sammobile.)
[Samsung Galaxy S 5 Unified Development] curiousde2002:
Thank you very much for really quick reply!

I will try that and for stock roms I found this "https://samfw.com/firmware/SM-G900F/DBT/G900FXXU1CRA2" which is free of charge whereas sammobile requires a premium membership for archived ROMs like the G900F.
[Samsung Galaxy S 5 Unified Development] DarkSteve:
:eek:

Oops! Sorry, I didn't realise. I haven't needed to download the stock for my phone yet (just my tablet). But I'm familiar with samfw and that should be fine (y)
[Samsung Galaxy S 5 Unified Development] LineArc:
Finally you are not talking before processing 😭
[Samsung Galaxy S 5 Unified Development] io2345:
NikGApps says ARM64. Is this the correct version? Or is it only ARM (BitGApps says: ARM)?

Besides: Are there any installation instructions for the ROM itself? Coming from latest offical Lineage-Release 18.1. Also, please let me know if there is an official version planed yet. I have no hurry and could easily wait a couple of weeks more, if that saves me from installing twice.
[Samsung Galaxy S 5 Unified Development] kurtn:
LineageOS 20 will never be official for old devices like Samsung S5. What's the problem with 18.1 ?
[Samsung Galaxy S 5 Unified Development] asdf2345:
I only tried it for fun myself. You're probably best off using the optimized LineageOMS 14.1 ROM with such an old phone. Android versions have long life cycles so it being 7.1.2 isn't an issue. Runs a lot better and faster than this ROM, with the advantage of no Material Design 3.
[Samsung Galaxy S 5 Unified Development] io2345:
No problem with 18.1 . It's just that my dirty flash has problems detecting sensors, so I would have to clean flash and start from scratch anyway.

Question could also be: Why not releasing officialy, if ROM is running fine?
[Samsung Galaxy S 5 Unified Development] io2345:
Thanks for pointing me to that. Maybe I will give it a try. Though it's simply cool running recent Android versions on a vintage phone. The hardware itself isn't bad at all. Of course a little slower than modern phones. But: I'm old, my phone is old -> Perfect match ;-):cowboy:
[Samsung Galaxy S 5 Unified Development] ProcyonNova:
100% agree with this, this is actually my primary motivation for doing this. It's great proof of concept that even a phone from ten years ago can run the current version of Android. I greatly appreciate developers like khalvat here, and others, who port Lineage and AOSP to ancient phones like this. I hope very much that Android 14 will make its way to the GS5 and continue going forward.

This phone isn't my daily driver anymore and hasn't been for over six years. But I love this kind of stuff.