yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Android Development (Snapdragon)] maanteel:
Build 0415 is running :) , after a short visit of stock rom. One thing done.

1. Magisk 22.1 confuses me , it does not root. SafetyNet API error. Just flashed it as usually in TWRP.

2. Also Google Play app is not available (I flashed opengaaps nano) :

"google play services are not supported " is the error when starting the google app.

Some things are wrong - but I still have no glue.

Edit: I restored back to official with TWRP backup. Maybe I try it dirty. I assume the adoptable storage make problems.
[Galaxy S 5 Android Development (Snapdragon)] Deollzz:
I compiled it myself using the github sources, boots fine, as soon as encryption is enabled, it bootloops, (For me anyway).

No Magisk installed.

format data removes the encryption, and the Rom starts after installation without problems, but as soon as the encryption is activated, a reboot logically occurs which ends in a bootloop. Boot - Reset -Boot - Reset.
[Galaxy S 5 Android Development (Snapdragon)] Deollzz:
Root with Magisk 22.1 does not cause any problems, Viper FX and AFWall+ work fine, only the encryption of the smartphone is no longer possible.
[Galaxy S 5 Android Development (Snapdragon)] robla1000:
Just a silly (?) question:

I have a lot of Backups back from 2017....

I'm not sure what to do with them.... Can they be of any use for me, now?
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
I would not know how these can be for any use any longer.

If you have an old Harddisk lie around, put them on there and decide later what to do with it 😉
[Galaxy S 5 Android Development (Snapdragon)] robla1000:
Yeah, I might as well do that... Iḿ allways a bit uneasy to throw backups away, but can't figure out what I might do with them.

Thanks..
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
What is your message here?

Do not fill thread in XDA with useless messages saying in fact nothing tributing to the subject.

This is not Telegram, this is XDA.
[Galaxy S 5 Android Development (Snapdragon)] robla1000:
Not so harsh...
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Hi Robla

I just noticed all over XDA, new juniors posting everywhere like above, just to push up their numbers counter postings....
[Galaxy S 5 Android Development (Snapdragon)] robla1000:
Well, that's bad... and...what a life do they have....
[Galaxy S 5 Android Development (Snapdragon)] Ralf_Volles:
I couldn't find an answer to Roguas question in the 2 years+ of postings since he asked. The original stock ROM does support the on borad ANT+ of the phone. But as I run this ROM and it seems not to support the on borad ANT+ hardeware of the phone, I kindly ask if any body does no a way to enable it?

Regards,

Ralf
[Galaxy S 5 Android Development (Snapdragon)] ripee:
Builds 0510 are up with the May security updates in my signature.
[Galaxy S 5 Android Development (Snapdragon)] argonaut459:
Wikipedia says:

ANT is a proprietary (but open access) multicast wireless sensor network technology designed and marketed by ANT Wireless (a division of Garmin Canada).[1] It is primarily used for sports and fitness sensors. ANT was introduced by Dynastream Innovations in 2003, followed by the low-power standard ANT+ in 2004, before Dynastream was bought by Garmin in 2006.[2]

So, as I read it - it costs money. Money no free ROM developer is ready to shell out.

Your best bet would be to ask around other Software / Hardware developers that maybe code specifically for such devices.
[Galaxy S 5 Android Development (Snapdragon)] Ralf_Volles:
What costs money is to get a certification of the official ANT+ brand and it is clear that this is nothing aimed for by Custom-ROM developers. But most of the resources are open source as I understand it.

Regards,

Ralf
[Galaxy S 5 Android Development (Snapdragon)] Not-Aus:
So is this alive now, or is it dead?
[Galaxy S 5 Android Development (Snapdragon)] ripee:
That depends if you want to use my unofficial builds from Lineage sources.
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
cant find the link(s) :-(
[Galaxy S 5 Android Development (Snapdragon)] maanteel:
follow the line :)

View attachment 5327705
[Galaxy S 5 Android Development (Snapdragon)] robla1000:
Does anyone knows, how GPS works in kccat6-phones?

Is there a chip, or is it integrated in -for example- batteries?

Is it possible to disconnect GPS completely?
[Galaxy S 5 Android Development (Snapdragon)] EeeK:
just flashed my SM-G901F, any chance of getting volte working on this rom?

google playstore will suddenly quit or reboot while installing app
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
As far as I know, and I'm pretty sure, GPS is integrated in removable battery.

My guess is to search internet for a replacement battery without GPS.

If you can't find those, never turn on GPS, that should fo the job.
[Galaxy S 5 Android Development (Snapdragon)] Advanced Android User:
Thank you so much for keeping LineageOS updated for LentisLTE. I just installed your latest release using TWRP without any issues.
[Galaxy S 5 Android Development (Snapdragon)] ripee:
Builds with the June security patches will be up within 3 hours.
[Galaxy S 5 Android Development (Snapdragon)] slizer_:
Hi ,

I have a Problem with the Camera App , when I change the Destination for Pictures to SDCard , the Images are stored in

Android/data/org.lineageos.snap/files/ not in the DCIM Folder on SDCard .

With the Version 20210510 is the same .
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
I'm sorry, and feel a bit stupid, but I don't see where the line points at :-(
[Galaxy S 5 Android Development (Snapdragon)] snsnse:
Could it be that you're confusing this with NFC functionality? See e.g.

Should I use non-Samsung batteries in my Samsung device? | Samsung UK

FAQ for Samsung Mobile Device. Find more about 'Should I use non-Samsung batteries in my Samsung device?' with Samsung

www.samsung.com
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
Yes you are right.

Nfc is in battery
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
See close-up samsung battery s5:

EB-BG900BBE 2800 MAH
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
I do not see the line or post you point out so clear to me...
[Galaxy S 5 Android Development (Snapdragon)] snsnse:
Try this:

kccat6 - Google Drive

kccat6

drive.google.com
[Galaxy S 5 Android Development (Snapdragon)] c341:
Link please. Thanks!
[Galaxy S 5 Android Development (Snapdragon)] snsnse:
.TWRP - Google Drive

drive.google.com
[Galaxy S 5 Android Development (Snapdragon)] tr0jance:
Does anyone has the link for the latest lenteslte release?
[Galaxy S 5 Android Development (Snapdragon)] snsnse:
ripee's directory on google drive:

ripee - Google Drive

drive.google.com

lentislte is here:

lentislte - Google Drive

lentislte

drive.google.com
[Galaxy S 5 Android Development (Snapdragon)] ripee:
Everything is under the google drive icon in my signature, which is a link to my google drive with the folders in it. You can also find my signature listed under my profile in the app/mobile version of xda.
[Galaxy S 5 Android Development (Snapdragon)] snsnse:
The link of the google drive icon points to http://tiny.cc/ripee , which (currently?) does not lead to the google drive directory, at least for me.
[Galaxy S 5 Android Development (Snapdragon)] ripee:
I blame tiny.cc lol. I fixed the link with the original one from drive.google.com
[Galaxy S 5 Android Development (Snapdragon)] bothered:
Should i use twrp twrp-3.3.1-0-kccat6.img or twrp-3.2.3-0-kccat6.img with yours, many thanks and good work :)
[Galaxy S 5 Android Development (Snapdragon)] ripee:
3.3+
[Galaxy S 5 Android Development (Snapdragon)] EeeK:
Encounter this when I tried to unlock my phone while battery is red. Any idea?

View attachment 5360941
[Galaxy S 5 Android Development (Snapdragon)] waldfee:
turn off flip cover
[Galaxy S 5 Android Development (Snapdragon)] andreoide:
True nasty problem I encountered few years ago also, solution I made was freeze the flip cover
[Galaxy S 5 Android Development (Snapdragon)] ripee:
New builds are on their way, with the July security patches.
[Galaxy S 5 Android Development (Snapdragon)] wazupp:
Hello! Found a funky bug whilst using the camera app. The phone will completely crash if you switch from the back facing camera to the front facing camera in video mode.
[Galaxy S 5 Android Development (Snapdragon)] Marvin732:
is there a android 10 or 11 coming in the near future :) ? the g901f has been on LineageOS 16 for quite a long time since its not very widely spread like the normal Galaxy S5
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
I did not build this. Better to ask [MENTION=5876638]xamio[/MENTION]
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
https://xdaforums.com/showpost.php?p=71096178&postcount=185

https://xdaforums.com/showpost.php?p=71098050&postcount=193

Corinna
[Galaxy S 5 Android Development (Snapdragon)] gillus66:
Funny, I also had some kind of crash this morning with the same build, just after waking up and putting the phone out of plane mode. Not sure if it was a reboot or cut-out, but the screen went black and the phone wouldn't start again. I had to remove the battery ! This has happen on a regular basis since I decided to test CM/RR on my S5.

If I can help providing logs files or somethng, just ask !
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
Seems like a fix was found for the video scaling issue:

(Cross-post from the Resurrection Remix thread)
[Galaxy S 5 Android Development (Snapdragon)] xamio:
Looks promising.

Last builds are not too stable at the moment, also experiencing random reboots.

FlipFlap should be somewhere, it does get build and packaged, from the build log:

[ 87% 30176/34519] target Package: FlipFlap (/data/lineage-14.1/out/target/product/kccat6xx/obj/APPS/FlipFlap_intermediates/package.apk)

[ 87% 30179/34519] Install: /data/lineage-14.1/out/target/product/kccat6xx/system/priv-app/FlipFlap/FlipFlap.apk
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
It is listed under Settings > Apps and it's running (started on boot). The app just doesn't seem to have an interface, so you can't start/open it. I have no idea if it does anything, because I have no flip cover for my phone.
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
At least in the RR build, you'll find it under Settings in the "Device" section, last item "Flip cover". It shows up when you attach and use a flip cover for the first time and then, at least in my experience, the "Flip cover" Settings item never disappears again, even when removing the flip cover from the device.

Corinna
[Galaxy S 5 Android Development (Snapdragon)] omniamutantur:
Flip cover setting is now showing up in the 170220 build, and the app is working perfectly. Thanks!
[Galaxy S 5 Android Development (Snapdragon)] prysme:
I did not find it under setting / apps, could you please provide me with a screenshot ?

In fact opening the cover is waking up the phone, but closing it does not do anything.

---------- Post added at 02:14 PM ---------- Previous post was at 01:27 PM ----------

I confirm, FlipFlap is here and is working fine ! Thanks !

No more cut out and the flip cover is working.
[Galaxy S 5 Android Development (Snapdragon)] michaelbelachev:
Hi, guys! Please, send me a backup partition LOS of /cache. My phone need to restore this broken partition.
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
Indeed, the item is there (in the Feb. 20 build). I simply overlooked it.

Why would you need that? You should be able to simply wipe (format) that partition from recovery and restart -- I do that all the time when updating (dirty flashing) the OS. The /cache partition does not include any critical information.
[Galaxy S 5 Android Development (Snapdragon)] michaelbelachev:
You don't understand me) After not correct update phone to new build (not wipe cache and dalvik), my phone don't want boot in system. I tried all methods, install via Odin, restore old backup, but didn't succesfully. So, I believe, when I restore normal cache partition, my phone will boot in system) Can you send me this? It's not hard) Thanks)
[Galaxy S 5 Android Development (Snapdragon)] Pulli67:
Hello everyone,

the version of the 12.02.2017 runs on my device. (G901FXXU1CPJ1)

Unfortunatley, I can not change this ROM to a later version.

After a Dirthy Flash (including wipe Cache/Dalvi) hangs on the device at boot time. Back up a flashing on the version of the 12.02.2017 works fine.

After a full wipe and restore data via Google, it comes to a bootloop on the device.

I recover the data about TWRP the device at boot hangs up again.

What can I do so that the update goes through?

Please excuse my bad English.

Thank you Pulli67
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
Well, I indeed don't get it. The only thing that is important in order to be able to boot your OS is that the /cache partition is available and has the right format. It is not such that this partition needs to contain some specific content -- the OS will boot fine when you completely wipe the partition from recovery. I don that all the time when dirty flashing a new OS version.

I would therefore recommend to re-format your cache partition from recovery. If that doesn't resolve your issue, something else is wrong. Most likely, there is some issue with your apps/data -- which then could be fixed by performing a factory reset. Have you checked the output of 'adb logcat' when the phone is booting? This may give some hints on what is going wrong.

(I will not send you my cache partition, as it may contain private data.)
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
So if I understand it correctly, you can not upgrade to newer versions than Feb. 12, but you can restore a backup of version Feb. 12? Correct?

So you can do a clean install of newer ROMs (> Feb. 12), boot into the OS, restore the apps (via Google) but when you then reboot, the device hangs?

Then apparently something was changed in the OS that is incompatible with your apps. I would recommend to run 'adb logcat' during boot to check for errors in the boot process. Maybe that way you can find out which app causes the reboot?

[MENTION=5899396]michaelbelachev[/MENTION]: this may be the same issue as you're experiencing?
[Galaxy S 5 Android Development (Snapdragon)] michaelbelachev:
I tried factory reset, reformated this partition, but not succesfully. Cache partition will not have private information if you wiped it) Ok, I will send you logcat.
[Galaxy S 5 Android Development (Snapdragon)] omniamutantur:
Hi, [MENTION=5899396]michaelbelachev[/MENTION]. Here is the cache partition from the latest available firmware from the SAMMOBILE site (CPJ1 baseband). Hope it helps!
[Galaxy S 5 Android Development (Snapdragon)] pbecks1963:
Hello guys,

I stopped flashing Lineage OS after build 15-02-2017 (very stable build). It seems that (guessing....) aptx is causing problems (?) in the latest build. There are no knew builds after 20-02-2017. I am looking for a change-log or a blog that will tell me some more of what is happening...

Anyone?
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
[MENTION=5876638]xamio[/MENTION] is the one who is building all these LineageOS builds. He seldom come on here. Usually I will ask him for a changelog, but then I've stopped since it might get annoying and pretty rude to him. Don't get me wrong. He has done a fantastic job for continuing to develop this device.
[Galaxy S 5 Android Development (Snapdragon)] xShigiga:
issues?

After installing the 18.02 & the 20.02 Version my phone was turning off randomly without restarting..

And i also rooted my phone with the New supersu Version after the 20.02 Version my device was unrooted and it zooms in in 720p Videos

And btw thanks for creating a Version for the g901f its way faster now really thank you very much
[Galaxy S 5 Android Development (Snapdragon)] ripee:
11 is next on my list. Once I finish up a couple minor bugs with the apq8084 kernel, I will pick my trlte-common commits to apq8084-common, which is the common device tree used by kccat6 and lentislte.

I will be skipping 10 entirely and eventually enforcing the kernel on the S5 Plus, like I have recently done on the Note 4. All the sources are public: github.com/apq8084
[Galaxy S 5 Android Development (Snapdragon)] Marvin732:
Nice! Thats awesome :D
[Galaxy S 5 Android Development (Snapdragon)] oddfellow667:
Wow this would be incredible... I have a few kccat6 (S5 Plus) devices here, using one of them as my daily driver (still with the last released LOS 16). I could use one (or two?...) of them for testing your builds, if this could help development...

Many thanks for your time and effort! Really nice device still... removable battery, heimdall flashable, TWRP available, and with a little patience still usable for most apps and some websites ;-)
[Galaxy S 5 Android Development (Snapdragon)] dziugas1959:
But damm, iam still on the official „LineageOS“ and damm, how i miss every week or even day or even month (tbh that was weird how they changed throu the year's) there was an update, but then just out of nowhere it was just discontinued i never had good luck with any other ROM than „LineageOS“ not to mention Unofficial build's just never went good for me, so for now i will hold on maybe out of the blue it appear's back on the official or when a stable unofficial Android 10-11 releases.
[Galaxy S 5 Android Development (Snapdragon)] ripee:
Can you elaborate by what you mean by unofficial builds never having gone good for you. Are you experiencing any problems with any unofficial builds that are out there, mine or anyone else's, that you haven't experienced with official builds? Keep in mind that official builds were made from the same sources as unofficial builds, the only difference is the filename and build label.

Lineage didn't discontinue the 16.0 builds just out of nowhere. They needed the infrastructure to run 18.1 builds alongside 17.1. One thing is for certain, official 16.0 will never come back.

On a related matter, if I ever get 18.1 working on kccat6 and lentislte, I will not be submitting them for official support. It's too much of a hassle to go through the process and too much of a time commitment to maintain the sources on a regular basis.
[Galaxy S 5 Android Development (Snapdragon)] dziugas1959:
Just high instability mainly crashes and stuff not working, now while iam not a dev on „Android“ or „Custom ROM'S“ i can't say that it is a golden rule, but it's my personal experience maybe your build's will be much more stable i don't know, which was my main reason for the grief of „out-of-the-blue under the bus throw of support for the kccat6“

I never advocated for 16.0 official build's if anything i wish it would get 17.1 or 18.1 builds.

If you do, and it's stable and no need for full reformat, then i will use your build's. I already use your „TWRP“ build's since i trust them.
[Galaxy S 5 Android Development (Snapdragon)] Marvin732:
Oh yes i would definitely do that too!

I was porting myself LineageOS 14.1 to my old THL T6 Pro phone because there was no rom really that was newer than 4.4.2 and it is MT6592 based phone.

I have moved on from my Galaxy S5+ G901F like 2-3 years ago and i still come here because i care about the phone and would love to see updates for it, because its a nice phone.

I wish there was a way to port MIUI to the G901F.

My only reason to move on from the G901F was because lineageos 16 was kind of buggy with it, it would drain the battery when turning off the phone over the night and at all, it would drain quickly, didnt had that problem when i was on 15.1
[Galaxy S 5 Android Development (Snapdragon)] ripee:
A full reformat would be necessary from 16.0 to 18.1, you can't avoid it. The battery drain bug remains, but since the S5 Plus was affected by it even in its official builds, it's not something I will be working on unless I manage to fix it by accident.
[Galaxy S 5 Android Development (Snapdragon)] Marvin732:
I don't know how to locate the problem but it wasn't there in 15.1, gotta find the rom in my archives

EDIT:

Apparently my oldest 15.1 is lineage-15.1-20180820-nightly-kccat6-signed

Gonna try it and also keep my S5 Plus turned off overnight since whenever i have it off and start it in the morning, the battery is drained to 0%
[Galaxy S 5 Android Development (Snapdragon)] Not-Aus:
Rebooting to TWRP and shutting it off from there will not drain the battery.
[Galaxy S 5 Android Development (Snapdragon)] Marvin732:
Is there anything I can help to port 18.1 to kccat6?
[Galaxy S 5 Android Development (Snapdragon)] ripee:
When the time comes, flash the rom, root it, and get logs with the SysLog app. But not yet.
[Galaxy S 5 Android Development (Snapdragon)] dziugas1959:
That was what i was afraid of „A full reformat“

I will watch your progress, but since i have important programs i probably won't be jumping to it, when back in the day the move from 14.1 to 15.0 to 16.0 was without data loss (Formating).
[Galaxy S 5 Android Development (Snapdragon)] Marvin732:
yeah it was because it stayed on official build i think
[Galaxy S 5 Android Development (Snapdragon)] ripee:
You need a specially built experimental build (that's what it's actually called) to migrate between unofficial and official builds. But this is unrelated to being able to dirty flash from one version to the next. While in your case it was possible, it's generally not recommended since any logs generated from dirty upgrades are usually useless for debugging.

It just so happens that dirty upgrading from 17.1 to 18.1 is the easiest and cleanest upgrade to make since Google is running out of backend ideas to make new versions different from old versions, so the upgrade is a smaller jump. As much as I'd like to run 17.1 builds when the time comes, there's no point if I have the apq8084 commit history ready to go straight to 18.1 and fix its bugs directly.

As for your inconvenience in clean flashing the new version, well none of us like to reinstall all our apps and set up our devices from scratch, but dirty flashing many version on top of one another is a recipe for bugginess which can be incorrectly blamed on any bugs that appear in the new version.

Progress on 18.1

The commits keep on coming! There are around 60 more to add, plus a handful of vendor changes, but the small device trees and kernel should be ready.