yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] hiaschey:
It took my g900f just 40-60s to start (~8 logo transitions) after screen-off on the 27SEP nightly after a factory wipe (at ~30s bluetooth speaker autoconnected) with gapps 7.1 stock (but the triangle-shaped things like "gmovies" disabled) and about 20 extra Apps installed (no games though, Launcher = Pixel Launcher).

Also, the Interface itself is blazingly fast, no issues for the last hour since I've flashed
[Samsung Galaxy S 5 Unified Development] jdrch:
The few times this has happened to me I fixed it by flashing the latest GApps. Note that this results in many of your Google settings being reset and makes the reflashed phone show up as a new device in Google Play, just FYI. I'm not sure if this is the technically correct explanation but apparently if your Android build version gets too far out of sync with your GApps base you run into issues like that.

---------- Post added at 12:50 ---------- Previous post was at 12:48 ----------

Oh also, FYI: as much as I love this ROM, the S5's hardware (i.e. I'm not blaming LOS) just couldn't keep up with my workflow and use case for the past few months. Ergo, I've replaced it with a Moto Z2 Force, but will still keep it around for playing podcasts and whatnot as its still MUCH faster than my Shield K1 (my previous podcast player) and has better mitigations against the humid bathroom environment than either the Z2F or the K1.

---------- Post added at 12:51 ---------- Previous post was at 12:50 ----------

Oh also, FYI: as much as I love this ROM, the S5's hardware (i.e. I'm not blaming LOS) just couldn't keep up with my workflow and use case for the past few months. Ergo, I've replaced it with a Moto Z2 Force, but will still keep it around for playing podcasts and whatnot as its still MUCH faster than my Shield K1 (my previous podcast player) and has better mitigations against the humid bathroom environment than either the Z2F or the K1.
[Samsung Galaxy S 5 Unified Development] Brigham999:
Anyone else had issues with Android Pay since 20 Sep update? Just tried it with the 27 Sep and it's still not working. I'm using the Android Pay fix zip.

Update: It's not Android Pay, it's NFC. Tested with a few tags and it's definitely not working
[Samsung Galaxy S 5 Unified Development] paulcarroty:
People, which camera applications do you use?

I tested the stock app from Lineage, Z Camera and Camera 360. Sometimes the images are not bad, but in most cases I see blurring and strange colors, the people's faces can be immediately taken to the shooting of The Walking Dead.

Device G900T, all updates were installed - as I understood, the firmware of the cameras should have been updated?
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
I've had no problems with Open Camera. Though, Camera 360 is highly reviewed, so it's strange that there's be such problems with it.
[Samsung Galaxy S 5 Unified Development] paulcarroty:
Real life isn't the review score. So, I have a great success with One Plus Camera and can recommend it for all - superb photos!
[Samsung Galaxy S 5 Unified Development] bytes2bits:
I was unable to snap off a photo with the front facing camera. Otherwise it works well. Was that your experience also? No big deal, just curious.
[Samsung Galaxy S 5 Unified Development] paulcarroty:
Yep, the same issue.
[Samsung Galaxy S 5 Unified Development] eldrake:
There might be a slight change, yet they still keep crashing. Thanks anyway for your advice!
[Samsung Galaxy S 5 Unified Development] systemcrash:
Slow motion video actually works with this camera (so it is possible on G900F and LineageOS). Selfie cam only seems to work for video, but not for photo. Panorama no-go.

Is this the camera app that the Ukrainian dude hacked to work on certain snapdragon chipsets? Or taken from the One+ ROM?
[Samsung Galaxy S 5 Unified Development] fitittome:
Check this out:- Reddit
[Samsung Galaxy S 5 Unified Development] Lore1:
Please, could one of the developers tell the admins of jenkins, that jenkins does not produce ROMs for 3 days now?
[Samsung Galaxy S 5 Unified Development] fitittome:
They are aware. The signing machine is down for maintenance.
[Samsung Galaxy S 5 Unified Development] Lore1:
thx
[Samsung Galaxy S 5 Unified Development] paulcarroty:
This is the official 1+ camera app.
[Samsung Galaxy S 5 Unified Development] Brigham999:
G900F here with latest 27 Sep build. Can anyone please help with why NFC has stopped working since the 20 Sep build?

UPDATE:

Well, what a numpty I am!!!! I just bought a new battery which I installed around the same time as the 20 Sep update. Turns out it's not NFC enabled! DOH!
[Samsung Galaxy S 5 Unified Development] paulcarroty:
Here's my rating of the best non-stock camera app for S5 which works under Lineage 14.1:

3. Open Camera - unclear detalization, but better than Camera 360 and Z Camera - apps with more than 100M installation in Google Play!

2. One Plus Camera - very good quality of photos, but I don't like slightly 'better' colors than IRL. The major details: frontal camera doesn't works.

1. The unexpected winner - HTC Camera! Very good photos and videos plus good panorama.

Hope my experience will be helpful for someone.
[Samsung Galaxy S 5 Unified Development] Fil in XDA:
I just found out that the default camera (Snapdragon camera) does not save videos to SD card. I had to use a 3rd party camera app.
[Samsung Galaxy S 5 Unified Development] fitittome:
Yes. True. Set storage to Sd-card. It stores photos there but videos on internal.
[Samsung Galaxy S 5 Unified Development] J-Lindo:
Downloaded the HTC Camera. Not bad, though all goes to hell with it if you try to enable HDR in the top left corner.
[Samsung Galaxy S 5 Unified Development] Immortal0907:
For the new guys who are wondering how to get this on their phones... https://youtu.be/jf7RrRjroK4
[Samsung Galaxy S 5 Unified Development] fipsy:
Same here! This is simply a bug in the memory management, which has made a huge impact on the task killer since the LOS version of September 20th. Most users just don't notice it. We are currently discussing this in the Boeffla kernel thread.

Just try out the special kernel built created by [MENTION=516058]fbs[/MENTION]. It fixes the problem for me. It would be interesting to know if it fixes the problem for you, too!
[Samsung Galaxy S 5 Unified Development] MikeRWK:
I uninstalled los filemanager and need to reinstall it to enable sd permissions, now when i try its telling me theres not enough storage on my phone which isnt true.
[Samsung Galaxy S 5 Unified Development] J-Lindo:
I updated to TWRP 3.1.1-0 and tried using the GApps Aroma installer (10/01), and it crashed/rebooted repeatedly. Don't suppose anyone's got a word on what's up with it?
[Samsung Galaxy S 5 Unified Development] MikeRWK:
Try using the regular gapps?
[Samsung Galaxy S 5 Unified Development] pepe100:
Aroma is not compatible with TWRP 3.1.1.0. if you want use aroma you must downgrade to TWRP 3.0 versions. But the problem is that some new Roms are not compatible with TWRP 3.0. It seems that Arona installer is obsolete now.
[Samsung Galaxy S 5 Unified Development] fitittome:
From what I've read Aroma installer just isn't supported anymore, its not going to get fixed.
[Samsung Galaxy S 5 Unified Development] Blackburn119:
You forgot to mentioned HDR mode doesn't work in HTC camera

---------- Post added at 05:26 AM ---------- Previous post was at 05:22 AM ----------

Try TWRP version 3.0.2 it works for me but have to crash/reboot 2-3 times before it can install
[Samsung Galaxy S 5 Unified Development] fitittome:
I noticed a problem with the 27SEP nightly and went back to 20SEP. I tried again yesterday and been running OK. I'm thinking its a dodgy app that's triggering it, just trying to figure out which one.
[Samsung Galaxy S 5 Unified Development] paulcarroty:
HDR works, I shot minimum 5 photos for the test.

---------- Post added at 12:51 PM ---------- Previous post was at 12:45 PM ----------

Only little freeze if you enabled HDR first time. After closing and opening again the app works good.
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Which version u using to get HDR working?
[Samsung Galaxy S 5 Unified Development] fitittome:
Looking here for upcoming changes:-

https://download.lineageos.org/klte/changes/

But any idea why these are being merged into klte? They look a bit 'out of place' to me.

https://review.lineageos.org/191416

https://review.lineageos.org/191387
[Samsung Galaxy S 5 Unified Development] paulcarroty:
HTC Camera 9.20.974075, Lineage 20170920, G900T.
[Samsung Galaxy S 5 Unified Development] eurohunter:
wow, i hope this change will make kltespr variants to be correctly configured when booting on LTE https://review.lineageos.org/#/c/189128/ , can't wait to flash it!
[Samsung Galaxy S 5 Unified Development] fbs:
I have to admit, my build is lighting fast.. lol.. trimmed down boeffla beta11.. with no swap, no zram, no zcache, and a "timely" lowmemorykiller

anyone can see whats hapenning with LMK using: echo 5 > /sys/module/lowmemorykiller/parameters/debug_level and then cat /proc/kmsg

willl open a thread about it depending on the comments about it here
[Samsung Galaxy S 5 Unified Development] SB4BBs:
Battery life somewhat improved
[Samsung Galaxy S 5 Unified Development] fitittome:
That may be a good thing.

What concerns me is that there are clearly some issues here with the standard ROM and the dev isn't getting proper feedback on. Specific reproducible tests etc. Submitted properly with logcats. I haven't checked JIRA recently but I bet there isn't one open for LMK issues on klte, but I may be wrong. :D

Whilst boeffla is a brilliant guy, he is dropping support for S5. The reality is that with every other LOS release something breaks his kernel, although he would say vice a versa. Right now he fixes things pronto, but that's not going to be the case from here on in, is it?
[Samsung Galaxy S 5 Unified Development] fipsy:
Proper feedback is however also extremely difficult, if the errors only occur under certain conditions and always manifest themselves differently. Unfortunately, this is almost always the case with memory problems. I posted some logcats where the memory problems were clearly visible (especially am_low_memory). And I'm very sure that these problems are not related to any app, because they appeared all of a sudden and are definitely related to some kernel commits as of Spetember 20th or 27th. And besides, these problems disappear if you use the kernel compiled by [MENTION=516058]fbs[/MENTION]!

My personal impression is also more of the reverse: With each new LOS version new bugs are emerging (UMS broken, LMK problems, to name just two) and Lord Boeffla tries to fix the bugs as far as possible. UMS is working again in Boeffla, for example. I am testing almost every new LOS version with the LOS kernel and then with the Boeffla kernel. It definitely has its reason why I always use the Boeffla kernel and not the LOS kernel! Please read this article by Lord Boeffla. It explains a lot and was very informative to me! It also explains why he has no interest in continuing to support the S5. I can understand it, although I plan to use my S5 for some more time - I've only had it for six months now. And I would never buy a smartphone that doesn't have a replaceable battery!!! :mad:
[Samsung Galaxy S 5 Unified Development] fitittome:
But us lot going on about it here is all very well, but when you consider that the dev is supporting all these LOS devices, don't you think we should be making life a bit more easy for him properly identify and reproduce a problem, in order to prioritise a fix? This is of course in addition to the security fixes like blueborn and his day job.

N9005

N900P

N900T

N900V

N900W8

SM-G900AZ

SM-G900F (this one's mine and clearly the most important!)

SM-G900M

SM-G900R4

SM-G900R7

SM-G900T

SM-G900V

SM-G900W8

SM-S902L

SCL23

SM-G9006V

SM-G9008V

SM-G900K

SM-G900L

SM-G900S

SM-G900P

SM-G900I

SM-G900FD

SM-G900MD

SM-G9006W

SM-G9008W

SM-G9009W
[Samsung Galaxy S 5 Unified Development] yurkennis:
Just experienced a similar corruption with definitely no TWRP involved: with "Internal storage only" initial setup and SD set as "Portable" but never actively used, I:

= made TWRP Nandroid backup

= manually flashed newer LineageOS

= made another TWRP Nandroid backup

= under regular boot, formatted SD to Adoptable; moved apps to it when app supported that; "migrated other data" from internal storage to Adopted

= after night of phone staying idle, discovered that all apps that were moved to SD are now gone--and typically can't be reinstalled

So there is no TWRP ever involved between formatting SD as Adopted and facing corruption/data loss.
[Samsung Galaxy S 5 Unified Development] jdrch:
Appreciate the thorough investigation.
[Samsung Galaxy S 5 Unified Development] paulcarroty:
I can understand ya, buddy :) Thinking to buy second American S5 for backup 'cause they are cheap in my non-English speaking location and Sammy produce the good&stable hardware.
[Samsung Galaxy S 5 Unified Development] Castor-designs:
Which file do I need to use as the custom twrp for SM-G900F? I see 4 files in the accordant folder: https://androidfilehost.com/?w=files&flid=152802
[Samsung Galaxy S 5 Unified Development] fitittome:
They are old. We have official 3.1.1 at https://eu.dl.twrp.me/klte/
[Samsung Galaxy S 5 Unified Development] omgbossis21:
The first one correlates with bison during the build process and the setting appears it was enabled but set false afterward thus not being used. The second changes some permissions including how selinux behaves with a specific activity.

While I'm posting lineageOMS build have been broken for some time and lineageOMS has stopped development to work on the latest android version. When that starts up I will again be compiling and I'll try to get one last OMS build on this version since we will lose lord boeffla on the next version.
[Samsung Galaxy S 5 Unified Development] fitittome:
Thanks for the detail. I also found an explanation for

why

they are showing up in the changelog and it seems, that there will be many more changes in future, to confuse people like me. One of the Lineage Team explained it like this:-

And so Google moves on, leaving everyone else to clear up behind them.......
[Samsung Galaxy S 5 Unified Development] ariel5zal:
great thanks man....:good:
[Samsung Galaxy S 5 Unified Development] investinwaffles:
I did a dumb thing and flashed the SmartPack kernel while I was out of town last night, and Android is claiming my adopted SD Card is "corrupt". I can see all the files in TWRP though but I don't have a computer to back up to until tomorrow night.

Anyone have a link to the stock LOS kernel for KLTESPR 9/27 (not sure if I can extract it or just flash the nightly again manually) ??

I haven't had any issues using the LOS updater to flash the latest nightlies, and even with the last nightly it was completely fine until I flashed the SmartPack kernel (trying to get my microphone working again)

Even with previous builds of Smartpack, I haven't had an issue with my adopted SD card until just now
[Samsung Galaxy S 5 Unified Development] Lilon:
This Rom is honestly amazing good work! No issues what so ever thank you.
[Samsung Galaxy S 5 Unified Development] Immortal0907:
Anyone experiencing "Cant connect to camera"?

It appears from time to time when I try to use camera app or any other app that I try to use camera through... for example telegram, instagram... after reboot its back to normal...
[Samsung Galaxy S 5 Unified Development] j1gga84:
Which build and which kernel do you use?

regards
[Samsung Galaxy S 5 Unified Development] Immortal0907:
Stock kernel, all the build from end of the september to now.. I clean installed many times but still it appears and its kinda annoying
[Samsung Galaxy S 5 Unified Development] j1gga84:
Hmm okay, that is really strange :confused:

I thought this issue was already fixed and that it was only an issue of LOS based ROMs and custom kernels..

regards
[Samsung Galaxy S 5 Unified Development] Immortal0907:
Yeah I dont know.. but since im currently on stock I cant provide logs.. so if anyone has some solution I can try, will flash los again... i also tried wipeing camera cache data but nothing... reboot is the only thing that solves it

Tho its not Snap problem since camera is completely not working in any app
[Samsung Galaxy S 5 Unified Development] paulcarroty:
Devtools -> Enable Terminal app -> open Terminal from your apps list -> Type 'su -' -> Enter -> 'killall mediaserver'. Can be easily automated.

---------- Post added at 05:40 PM ---------- Previous post was at 05:31 PM ----------

Flash the nightly for your device again.
[Samsung Galaxy S 5 Unified Development] Immortal0907:
Umm whats that exactly doing ? Should I type that when I get error or should I type it like a solution not to get error
[Samsung Galaxy S 5 Unified Development] investinwaffles:
Nice, didn't know if it would cause any issues but of course Chrome won't download anything because the SD card is "missing" so I need to find a computer to plug into :p
[Samsung Galaxy S 5 Unified Development] fipsy:
You're right. You're right. There is no question that Lineage's developers deserve all the credit. However, the problem is also that if new bugs arise as a result of new versions in such a fast sequence, it is hardly possible to fix them reliably. Lineage 14.1 is now 9 months old and anything but perfect. Now it's already time for Lineage 15 and I'm afraid we'll end up with a number of more or less poorly working operating systems. I also think my next smartphone won't be Samsung anymore. Nevertheless, the focus should be on leaving at least ONE well-functioning lineage 14.1 at the end. Right now I'm not really convinced....

---------- Post added at 07:33 PM ---------- Previous post was at 07:26 PM ----------

That's one of the reasons why I don't want to rely on Samsung in the future. And why I will not install Lineage 15 on the S5 any more, but will stay with 14.1.

---------- Post added at 07:54 PM ---------- Previous post was at 07:33 PM ----------

One of the best sentences I've read about this topic in recent years. And if you don't use Lineage or Android O (this is probably about 90% of the Android users), you are released for launch. :p That's how you drive people into Apple's arms.

---------- Post added at 08:00 PM ---------- Previous post was at 07:54 PM ----------

This happens whenever a camera-app crashes or does not release the camera. Recently, Lineage was changed so that an app can only connect to the camera once. Previously, it was possible to connect several times so that the error did not occur.
[Samsung Galaxy S 5 Unified Development] paulcarroty:
https://androidforums.com/threads/mediaserver-what-is-it.15784/

Type the commands every time after error and your mediaserver will restart.
[Samsung Galaxy S 5 Unified Development] Immortal0907:
Oh thanks.. I think that I found an app that does that
[Samsung Galaxy S 5 Unified Development] MikeRWK:
When I use bluetooth my phone will only show a blue square with the date/time on it and the only way to get rid of it is to pull the battery, the songs keep playing.Does anyone have an idea whats going on?
[Samsung Galaxy S 5 Unified Development] MikeRWK:
Thanks so the phone must be thinking its got a cover on it when its in my pocket? It must be electrical interference from welding
[Samsung Galaxy S 5 Unified Development] fitittome:
There is a magnetic sensor close to the Home key. That triggers flip cover activation and it defaults to closed. :rolleyes: It will be OK now you've disabled it.
[Samsung Galaxy S 5 Unified Development] Immortal0907:
Ok here is something strange... This never happened before on any of devices I had... So I flashed latest nightly with latest gapps pico pack... but when I want to install by clicking on 3dots next to the app name and clicking on install nothing happens (i click it there 3-4 times still nothing) but when I actually go into the app (where it shows description reviews etc) and then click the install button it works... tried clearing cache and data of play store and play services and nothing and I checked its all up to date ...

just to clarify... picture one is when it wont download, picture two is when it works.
[Samsung Galaxy S 5 Unified Development] Fleakm:
Anyone notice this in Google voice detection aka "OK google"
[Samsung Galaxy S 5 Unified Development] eurohunter:
I just tried it now, and installation works just fine for me even from the 3 dots. I have the latest nightly with pico gapps. So the issue must be on your end
[Samsung Galaxy S 5 Unified Development] Castor-designs:
But these are compatible with the lineageos built in update function as well?
[Samsung Galaxy S 5 Unified Development] fitittome:
Yes!

---------- Post added at 07:52 AM ---------- Previous post was at 07:18 AM ----------

Think how it used to be when we really did have nightlies every night! MAYBE there is a case to be made for Snapshot builds. Who knows? :angel:
[Samsung Galaxy S 5 Unified Development] ShahabJafri:
So I went through the last thirty forty pages of this thread and found there's some issue introduced in Sep 20 build and decided to flash the Sep 13 build last night. Downloaded TWRP from here, Rom from LiOS page and OpenGapps Micro. Installation went smooth and the phone was set up completely in an hour. Installation of Magisk was also uneventful. So far the ROM seems very stable and fast. If only the Flipcover app could be improved this will be the best Android experience on our phone.
[Samsung Galaxy S 5 Unified Development] paulcarroty:
The issue in Sep 27, I use the build from 27.09 without problems.
[Samsung Galaxy S 5 Unified Development] DragonQ:
"Some issue" is pretty vague. What's wrong with 20/09? I use that because someone mentioned that battery drain and performance issues had returned with 27/09, on their phone anyway. I am curious about 04/10 but haven't had time to try it.
[Samsung Galaxy S 5 Unified Development] fipsy:
I'll probably go back to the Sep 13th version, too. The only problem is that there are also some bugs: UMS mode doesn't work anymore and sdcardfs is corrupted. However, since the current versions have a fat bug in the LMK, which leads to apps being killed in the background and automated tasks not running anymore, the version from Sep 13th is the last one to be recommended.
[Samsung Galaxy S 5 Unified Development] fitittome:
04OCT runs great, no probs at all.

The only issue that I have found, is if you load 3C Toolbox Pro you will then see MP-Decision errors in the logcat. But I cannot see any impact whatsoever on battery life or anything else prior to loading 3C Toolkit, so I am not bothered by whatever is causing the problem.

It is important to note that the 04OCT release has the best SD-Card support with sdcardfs. This is where all the on-going development is happening in Oreo and you can see the dev is backporting patches (if I am understanding things right) along with support for ntfs and exfat.
[Samsung Galaxy S 5 Unified Development] fipsy:
The LMK bug! If you run apps in the background (e.g. backup or synchronization scripts like FolderSync or Titanium) they will be terminated after a few seconds. At least if you have a larger number of apps running, so that the memory is well utilized. In versions before September 20th, this worked perfectly. It is propably an error in the kernel, which also exists in version 10/04.
[Samsung Galaxy S 5 Unified Development] fitittome:
But didn't we establish that this isn't a bug? It's just that the apps you are using haven't kept up with the currrent scheduling mechanisms. These mechanisms were optional for apps in Nougat. I guess those apps will fail completely on Oreo but just don't work very well with our version of Nougat which has a smidgen of Oreo mixed in with it. #GBBO

Systemcrash's explanation

Background Execution Limits mumbo jumbo.