yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Anikscha:
Grave yard concept

The support time of Android is a grave yard concept!

It survives just because the mobile market is dominated by greenhorns and kids.

As a desktop OS it would be a "none starter"!

Lineage could do so much better, by rethinking its policies and concept!

A secure future can only be achieved by a long time support of certain versions.

I see only 3 solutions for N:

1. [MENTION=5110154]fipsy[/MENTION] (quote) Why not release an unofficial update with the keys of the official version, so that it can be installed over the official version?

or

2. [MENTION=2693412]haggertk[/MENTION] (quote) In case the developer keeps up his promise for the unofficial support, spend the time ones and swap to the unofficial version.

or

3. Go for the permanent solution and forget Lineage!

[MENTION=7978913]fitittome[/MENTION] BTW, I donate regularly to several projects, but certainly not to "grave yard concepts"!

Save some bytes! Cut down those 200 terabytes and choose wisely the versions for LTS!

Especially by the advantage of Lineage for personal configurations an upgrade cause the disadvantage.

Who wants to spend more time for the phone than with the phone?

Lineage should not follow the madness of Giigle, like:

"If you're not paying for the product, you are the product".

Rethink the structure of that project !!!
[Samsung Galaxy S 5 Unified Development] haggertk:
Wanna go from Lineage official release keys to test keys without wiping? Reverse the sed in the update-binary (really a script) in https://blunden.se/migration and then flash on top of a running system.

Figure out the details. Back up. No warranty.
[Samsung Galaxy S 5 Unified Development] haggertk:
Impossible. The keys are highly secured for good reason. Only one director (the one who also has Lineage LLC liability) has access.
[Samsung Galaxy S 5 Unified Development] fipsy:
Thank you VERY much for this information! Will try that shortly.
[Samsung Galaxy S 5 Unified Development] daniel3x:
Script to migrating from official to new unofficial builds:

https://mega.nz/#!K9YhQYiC!5neBRDgPvZ3PObKtSOviPbLf8ohb-R1KFG624Za3V2w

Flash the script and then flash the unofficial build.

Reverted and tested by me. Thanks [MENTION=2693412]haggertk[/MENTION]
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
Just for clarification purposes, I've got 2 quick questions...

1) Is this script to will allow for an individual to Migrate

"from any"

Official LineageOS Builds

"to any equivalent"

Unofficial LineageOS Build (equivalent = 14.1 to 14.1, etc...)?

2) Does the individual simply place this script at the top of the flash order with the Unofficial LineageOS at #2?

Thank you! :)

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[Samsung Galaxy S 5 Unified Development] daniel3x:
1) Yes. The only thing that i don't know is if you can migrate and upgrade from official LOS 14.1 or LOS 15.1 to unofficial LOS 16 (i dind't test) but that is not recommended btw.

2) Sorry but i don't understand corretly that question, my english ins't very good. You flash the script.zip in TWRP to allow flash the unofficial builds. You just need to do this one time. Then if you wanna go to official builds you need to flash the other script that haggertk gave us.

I hope that you understand my poor english :)
[Samsung Galaxy S 5 Unified Development] loc1507:
Is there a changelog or something similar for the unofficial 14.1 build by [MENTION=2693412]haggertk[/MENTION] ?
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
[MENTION=4795768]daniel3x[/MENTION] & [MENTION=2693412]haggertk[/MENTION], It must be the humidity here... LMAO!

It just clicked to me regarding the script files to go to and from an Official/Unofficial builds.

Please disregard the second question since I just read it again and realized that I hadn't phrased it correctly. My apologies.

What I had meant to ask (for the second question) was my seeing the scripts posted on the Official LineageOS 14.1 thread and, though it would go without stating that it applies to the LineageOS 14.1 builds.

I know that I would not really use them for crossing to and from 14.1, 15.1, etc...

but, I'm wondering if they will work to go to and from Official/Unofficial within the LineageOS 15.1 or the 16.x.

I don't mean Upgrading/Downgrading the Android Version itself. I mean sticking to the Android Version but, going to and from Official/Unofficial.

I can only assume that it's intended for the LineageOS 14.1 Official/Unofficial but, I prefer not to "Assume" anything.

I hope that I explained this question okay via text... :eek:

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[Samsung Galaxy S 5 Unified Development] fipsy:
First of all: Thanks again! With the script posted by [MENTION=4795768]daniel3x[/MENTION] I just migrated from the official LOS14.1 to [MENTION=2693412]haggertk[/MENTION]'s unofficial version and it worked like a charm.

This is a very important additional piece of information. At first I didn't really understand haggertk's statement "Reverse the sed in the update-binary" either. After I read it again and looked at the script, it was clear to me. If you don't know what "sed" is on linux, you don't quite understand.

When I look at the script I assume that it can be used with all LineageOS versions and is not specific to 14.1, as it only exchanges the keys in /data/system/packages.xml, which will probably work the same way for all versions. Correct me if I'm wrong.
[Samsung Galaxy S 5 Unified Development] v00d007:
I know it's off topic (so sorry, op) but I'm already long searching for an addon for Firefox v57+ which (still) can download youtube videos. As in v57 the whole addon system was redesigned my old and perfectly working FVD youtube downloader isn't compatible anymore. So, I tested lots of addons, but most of them aren't even designed for Android (but nevertheless installable, grrrrh...), so that the action button is missing and the others fail to do what I want: download videos.

Tested FF v57, 58, 59, 60. Now still using v52 that's not the best in performance and very resource eating.

Anyone?
[Samsung Galaxy S 5 Unified Development] fitittome:
NewPipe? My teenager swears by it.
[Samsung Galaxy S 5 Unified Development] swiftbones74:
+1 for newpipe. Great app, that does exactly what its what it says it does.
[Samsung Galaxy S 5 Unified Development] krazie1:
I was wondering if anyone has the last official build (07/06/18) they can send my way through PM. Thank You.
[Samsung Galaxy S 5 Unified Development] MRizzi:
PM sent.

sha256sum 9f031f90c81956d08383c4eab64050042270789050ca982991b4a3efa15cd827
[Samsung Galaxy S 5 Unified Development] mr1994:
can you send latest official 14.1 to us
[Samsung Galaxy S 5 Unified Development] IKGapirov:
Latest Official LineageOS-14.1
[Samsung Galaxy S 5 Unified Development] SalsifiPourri:
what is better between latest official and latest unofficial ? i think, there's no point to stay in the latest official release
[Samsung Galaxy S 5 Unified Development] daniel3x:
some minor bugs fixes and most important lots of security patchs
[Samsung Galaxy S 5 Unified Development] kutysam:
Where do we get the unofficial builds? Cant find the link
[Samsung Galaxy S 5 Unified Development] IKGapirov:
The Link to Unofficial LineageOS-14.1
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
The following link takes you to the Unofficial LineageOS 14.1 Repo from Haggertk.

https://androidfilehost.com/?w=files&flid=140204

Just keep in mind that the Unofficial LineageOS 14.1 builds also stopped when the Official LineageOS 14.1 builds ended.

I, personally, am not aware of any other developer continuing the Unofficial LineageOS 14.1 for the klte developments but, you never know what the future holds.

Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.
[Samsung Galaxy S 5 Unified Development] swiftbones74:
***Deleted because of server side error***
[Samsung Galaxy S 5 Unified Development] kutysam:
Tried Fresh install with opengapps 7.1 and unofficial and official... but both don't load. Anyone else faced this?
[Samsung Galaxy S 5 Unified Development] jerfsonpaiva:
Update your baseband and the TWRP to the lastest.
[Samsung Galaxy S 5 Unified Development] j1gga84:
Why is it not possible that 2 branches stay active and official, like LOS 14.1 and 15.1 ?

regards
[Samsung Galaxy S 5 Unified Development] kutysam:
Was referring to Google Assistant doesn't load*
[Samsung Galaxy S 5 Unified Development] kaBOOOM2k5:
Lack of

- official manpower

- server hardware to build and store so many officials branches etc
[Samsung Galaxy S 5 Unified Development] Nerva:
I have a question on the Snap Camera app. Just about every other camera app I've seen has at least an option to use the volume up/down buttons to control the zoom, but I don't see a way to choose that in the Snap Camera app. Am I missing something, or are all the options just the ones listed on the left panel?
[Samsung Galaxy S 5 Unified Development] fitittome:
Loopy Lookback - Can someone check this on 14.1 pls.

Trying to document what I'm seeing on my device running LineageOS 15.1 (Oreo 8.1). Just rebooting and using adb for confidence I'm doing a:-

# /system/bin/ip route show table 0

but I am seeing loopback errors. I'm guessing this is not normal.

default dev dummy0 table dummy0 proto static scope link
default via 10.56.15.181 dev rmnet0 table rmnet0 proto static
10.56.15.182 dev rmnet0 table rmnet0 proto static scope link
10.56.15.180/30 dev rmnet0 proto kernel scope link src 10.56.15.182
broadcast 10.56.15.180 dev rmnet0 table local proto kernel scope link src 10.56.15.182
local 10.56.15.182 dev rmnet0 table local proto kernel scope host src 10.56.15.182
broadcast 10.56.15.183 dev rmnet0 table local proto kernel scope link src 10.56.15.182
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
unreachable default dev lo proto kernel metric 4294967295 error -101
unreachable default dev lo proto kernel metric 4294967295 error -101
unreachable default dev lo proto kernel metric 4294967295 error -101
unreachable default dev lo proto kernel metric 4294967295 error -101
fe80::/64 dev dummy0 table dummy0 proto kernel metric 256
default dev dummy0 table dummy0 proto static metric 1024
unreachable default dev lo proto kernel metric 4294967295 error -101
unreachable default dev lo proto kernel metric 4294967295 error -101
unreachable default dev lo proto kernel metric 4294967295 error -101
unreachable default dev lo proto kernel metric 4294967295 error -101
unreachable default dev lo proto kernel metric 4294967295 error -101
local ::1 via :: dev lo table local proto none metric 0
local fe80::9406:b9ff:feae:f7d6 via :: dev lo table local proto none metric 0
ff00::/8 dev dummy0 table local metric 256
unreachable default dev lo proto kernel metric 4294967295 error -101

I am guessing this behaviour is not seen on 14.1. The reason for my ask is that I this neat little Netguard, No Root Firewall is not working on 15.1 or 16.0 and I'm trying to get a handle on the problem.
[Samsung Galaxy S 5 Unified Development] fitittome:
Thanks for that. Those errors are there too on 14.1. Oh well. Dead project, lol. 16.0 is progressing at incredible speed. I'm using it right now on my S5. Almost good enough as a DD. Notifications are a sore point at the moment. AFWall+ I miss. I haven't run rooted on my DD since 14.1.
[Samsung Galaxy S 5 Unified Development] Anikscha:
Squished users

Yeah sure, there is O and P in development and next year version 10 and sure, the developers and [MENTION=2693412]haggertk[/MENTION] spent a lot of time and effort.

No doubt, but the language of the users sound different!

https://stats.lineageos.org/model/klte

Your own statistic is the proof!

I spent a lot of time for my own configuration and other users did as well.

Some of my paid apps do not function on O or P, but I spent more than 250 $ on those, plus a good amount on donations!

Of course, that is not a fault of Lineage, but app developers are forced into that mad "upgrade race" as well and not all of them upgrade their apps in time or even not at all!

As result, the users are squished !!!

I took 9 month with N from the first installation until everything ran smooth!

Who is willing to repeat that grandiose "time killer" exercise?

In summery, the choice users have, is an unsupported Stock Rom or an abandoned Lineage N version.

What a great situation!

:rolleyes:

Which headline will fit the facts:

"Sandbox Games"?, "Grave Yard Concept"?, or "Squished Users"?

Yes, I regret deeply to recommend Lineage to my friends.

Sorry, for that.

However, alternatives do exist!

The G800F, which never reached the official level, is nicely and constantly supported unofficially every month.

Also for the G900 model a supported solution is out there:

https://aokp.co/about

It includes the latest security patches!

So, no need to beg for support on N.

A G800F supported by N and a G900F on AOKP will do until Libre is on the market.

https://puri.sm/posts/librem-5-general-development-report-october-15th-2018/

Than, not a single dollar anymore for anything in connection with Giigle, the Black Hole for time, money and privacy!

It's up to the users now, to stand up for them self, or resign here.

Great future... and please, let me know, if anything from above is incorrect!

Good luck and good bye...

;)
[Samsung Galaxy S 5 Unified Development] fitittome:
Hey, I run a CookShop in rural UK. I've build my own 15.1 but haven't figured out how to manage it for 16.0. Not sure why your problems have landed on me, but I do offer a cracked screen replacements at great prices. :cool:
[Samsung Galaxy S 5 Unified Development] Anikscha:
Your activities here in the forum mislead my conclusion, that you a part of the Lineage Team.

Sorry for that.

:good:
[Samsung Galaxy S 5 Unified Development] haggertk:
Respectfully, eat it. I did miss Sept and by the time I realized it Oct was imminent. I'm busy. I'll get to it after Oct is merged platform side.
[Samsung Galaxy S 5 Unified Development] Anikscha:
With respect to the users, it wasn't me who left them in the dark since 2018-7-6!

Guided by statistics, a short announcement would have been appropriate and appreciated!

Instead, it was me since than, who tried to clarify the situation.

In great respect, I am out of here!

No worries, I swapped the Rom.
[Samsung Galaxy S 5 Unified Development] haggertk:
The statistics do not mean what you keep pretending they mean. A 14.1 release being at the top does not mean that a plurality of users continue to use 14.1. That is just the particular build that a plurality of users INITIALLY checked in. We do not track what specific release or even which major revision of OS is being actively used.

No users are left in the dark. We (LineageOS) have always been very clear in the fact that one single release of each build will be supported at a given time. I actively assist in patching 14.1 platform-side because it is still a shipping branch and in alignment with my responsibilities as LineageOS project director; my patching the samsung_msm8974 kernel is because hlte* is still 14.1 and in alignment with my responsibilities of hlte* device maintainer. My typing "brunch $blah" is complete extra credit.

You are making a thing where there is no thing to make.
[Samsung Galaxy S 5 Unified Development] Quirken:
Until I switched from Official 14.1 to Unofficial 14.1 (because official builds stopped), I had zero issues. I wiped the device and put on the unofficial 14.1. (This issue is also present in 15.1, but I had other stability issues there so I reverted to 14.1 unofficial)

Even on a fresh install, the phone refuses to respond to Bluetooth keyboards or mice. You can pair, and it lists "input device" as an active profile. But if you press keys or you try to use the mouse, nothing happens. It stays connected, but that's it. There's no mouse cursor, etc. (I have a Bluetooth remote control that appears to enter power save.) Bluetooth audio appears to be unaffected.

I have a backup I made of the final Official 14.1 build; if I restore this backup and wipe data, from a fresh install, Bluetooth works exactly as expected. I can upload this if that would be helpful in troubleshooting - boot/system backup is about 1GB.

So, it appears something broke between 7/8 and present. I've seen several other people posting about issues.

I've attached a logcat of me pairing the mouse and trying to use it (also tried unpairing, repairing, and turning off and on during the log)

I tried doing what this said with the good version. No luck.
[Samsung Galaxy S 5 Unified Development] j1gga84:
[MENTION=2693412]haggertk[/MENTION]

No release of security patch October for LOS 14.1? The October is nearly over and LOS 15.1 has the fixes since the beginning ;)

Or are there any issues?

Regards

Sent from my SM-G960F with Tapatalk
[Samsung Galaxy S 5 Unified Development] swiftbones74:
Lol, he will probably correct me but, I'm going to answer for him. He's f'ing busy with his other obligations and currently supported builds and he'll get to it when he f---ing gets to it.

[MENTION=7776904]JGGA[/MENTION]84 I hope you can handle the good natured humor. I am mostly joking, However, when it comes to our S5 devs and particularly the one person who has done the lions share of work @CM/LOS maintaining aftermarket software support for us.

All this being said I do believe I read somewhere that he said he had missed the date to build this month and was waiting till next month's patch.

Whatever the case may be, no disrespect to you, I myself greedily download each new 14.1 build,(+15.1+16) I literally can't kiss his cyber ass enough I'm very grateful for this work= extra credit builds supported builds , overall commitment to a now almost five year old phone! A F-tun of other stuff on this one phone alone, (he maintains other's as well).

Bottom line, he'll get to when he gets to it, if he feels like it. Be thankful and polite, DON'T ASK ETA's. This stuff is mostly open source, so you can always fork it and do it yourself.

Have a good day and BTW I had this phone for a long time and not seen one ROM from you. Are there any issues? ;)
[Samsung Galaxy S 5 Unified Development] j1gga84:
first of all, I was not asking for ETA's because I don't use LOS anymore since a long time ;)

second I was not aksing for a new LOS build with security patch october, I was simply asking for the october security patches for LOS 14.1 in general, for all devices, not specially for the S5 because other devices, like my Galaxy Tab S, also have no october patch yet.

I only wanted to know if [MENTION=2693412]haggertk[/MENTION] knows anything about the status or any issues that prevents the release of the security patches, because in the last month the patches were always released nearly at the same time.

And the last point, I already built in the past (https://androidfilehost.com/?w=profile&uid=890129502657589982), mainly for myself, but, because of the lack of time, I do not build anymore, also because the S5 is only my backup device now - I switched to the Galaxy S9 2 month ago and there is enough development going on at the moment :)

regards
[Samsung Galaxy S 5 Unified Development] Henki98:
Latest unofficial los 14.1 work well?
[Samsung Galaxy S 5 Unified Development] haggertk:
15.1 is (currently) easy -- essentially changing a variable in .repo/manifests/default.xml and performing a git fetch $TAG and git merge --log FETCH_HEAD in each project we forked from AOSP. I'm the one that seems to be running that script because most are paying attention to 16.0.

14.1 is harder, at least for us. Google does not release tags on branches they aren't currently shipping on their own devices, which is 8.1.0 (bullhead/angler) and 9.0.0 (sailfish/marlin/walleye/taimen/blueline/crosshatch). OEMs and other trusted parties get zip files containing plaintext patches containing the resolutions for security vulnerabilities noted in the ASB for 7.0.0, 7.1.1, 7.1.2, 8.0.0, 8.1.0, and 9.0.0 baselines. We aren't one of those parties that get to press the easy button. We have to crawl the ASB and backport 8.1.0 changes that the bulletin says are relevant to 7.1.2.

15.1 will get harder in the coming months, since bullhead and angler are likely to get dropped by Google by the end of the year. At that time we will have to cherry-pick changes from 9.0.0 as well. Luckily, 8.1.0 architecturally and code-wise similar to 9.0.0.

14.1 October patches shipped yesterday.
[Samsung Galaxy S 5 Unified Development] Reverse-anastomosis:
Misfiled builds

[MENTION=2693412]haggertk[/MENTION] the latest lineage 14.1 builds are located in the cm-14.1 folder instead of the lineage-14.1 on android file host. Thanks for all that you do!
[Samsung Galaxy S 5 Unified Development] curiousrom:
lineage-14.1 & cm-14.1 Unofficial LineageOS Download Folder Confusion

[MENTION=2693412]haggertk[/MENTION] I can confirm that: currently in your lineage-14.1 folder the most recent is build 2018-08-30 while in the cm-14.1 folder one can find a 2018-10-10: lineage-14.1... 20181010... -UNOFFICIAL-klte.zip.

Edit: BTW could you change this link in the bottom of post #1 of this thread as users are wasting their time trying to find an official S5 LineageOS 14.1 or maybe add a note about your official 15.1 & your unofficial 14.1 & 16.0 builds?

Edit 2: For example this got posted on the next page:

***

Anyway BIG THANKS for your incredible work supporting all those crazily numerous S5 models & firmwares variations! :good:

***
[Samsung Galaxy S 5 Unified Development] warism100:
[MENTION=288772]hegger[/MENTION]tk plz can you do seam thing with lineageos 13

branche i mean if you can compile lineageos 13 for our klte

a big thnx Mr haggertk coz with lineageos 14.1 we can't

import contact from sim card (g900F) latest bootloader

and baseband
[Samsung Galaxy S 5 Unified Development] haggertk:
If your Bluetooth is glitchy (drops when you walk away more than a couple feet, put the phone in your pocket, etc.) send me the requested info and I'll both get you a temporary macloader and also submit the change upstream to make it permanent.
[Samsung Galaxy S 5 Unified Development] notentirelysure85:
[MENTION=2693412]haggertk[/MENTION] absolutely love your work! Really appreciate you sharing your hard work with all of us!

One small issue though, in the Storage Settings screen, it seems to be misreporting my used storage space as a negative number. I've installed a 64GB MicroSD and formatted it as internal storage.

My device is a kltedv running cm-14.1-20161109-NIGHTLY-kltedv.zip and gapps open_gapps-arm-7.1-nano-20161110.zip. No other modifications.

Anyone else seen a similar issue? Apart from misreported free space, it seems to be working fine without issue.

Screenshots are attached.

Thanks! :)
[Samsung Galaxy S 5 Unified Development] AndroidsRus:
So far only problems ive had are the fingerprints not working and rebooting if you try messing with it!
[Samsung Galaxy S 5 Unified Development] haggertk:
You can nuke the fingerprints without wiping by deleting /data/system/users/0/settings_fingerprint.xml and then rebooting. Then setup new fingerprints.
[Samsung Galaxy S 5 Unified Development] haggertk:
This actually happens for me and other device maintainers (more than just klte) when using adopted storage. It will get fixed, but as a cosmetic thing it's fairly low on the list at this stage of the bring up.
[Samsung Galaxy S 5 Unified Development] notentirelysure85:
I understand that. Just making sure you were aware of it :) It is just cosmetic, and still works fine apart from that. Thanks for the reply!

:)
[Samsung Galaxy S 5 Unified Development] Spearman873:
The front camera is very dim/dark on the app Houseparty. Do any of you know how to fix it? I'm on the 11/9 nightly