yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] fipsy:
Even if that's the way it should be, we're at Nougat and not Oreo! So it's a bug. This is especially the case if "Low memory" is reported on the one hand, but 600 MB RAM is unused on the other hand! That's not a bug? If widespread apps such as Titanium or FolderSync, which are used by millions of users, no longer work, then it doesn't really matter where the cause lies, does it?

To be honest, I'm getting so tired of Android that I'm seriously considering switching to Apple. As an Android user since February of 2010. The effort for this open system is meanwhile greater than the benefit.
[Samsung Galaxy S 5 Unified Development] ShahabJafri:
I see the discussion has already moved on from the point I was first quoted and [MENTION=5110154]fipsy[/MENTION] and [MENTION=7978913]fitittome[/MENTION]s have already described the issues which were introduced supposedly in Sep 20 onwards version.

From what I could see, the developers are trying to backport / integrate Oreo features to 14.0. For me having cutting edge version on my device isn't of that much priority than having a stable device. Also, when code is changed (and a big project like LiOS) it takes time for it be tested in the wild. I'd rather have a tested and stable version on my device than having the latest nightly.
[Samsung Galaxy S 5 Unified Development] fitittome:
https://www.theguardian.com/technology/2017/apr/03/ios-11-apple-latest-update-older-apps-stop-working

Check this out........ the grass is always greener........ :D
[Samsung Galaxy S 5 Unified Development] fipsy:
Okay, you may be right. It's no better with Apple. But the current state is simply not acceptable for normal users anymore. If the effort to use an operating system is greater than the benefit, then it will die. Miscrosoft was at the edge of the abyss with Windows, but as it looks like at the moment, they are just getting the curve in Windows 10 and I hope that Google (and ultimately Lineage) will get this curve as well. Unfortunately, it doesn't look like it at all at the moment!

---------- Post added at 05:07 PM ---------- Previous post was at 05:04 PM ----------

It's the same with me, too. It must be an acceptable compromise between actuality and functionality! An operating system is not an end in itself for me!
[Samsung Galaxy S 5 Unified Development] fitittome:
Be positive, loads and loads of users are using the latest builds without any issues. Issues may well lurk under the hood, but most users don't notice them. My youngest, who is a heavy gamer had a touchscreen issue the other day. I thought I would install the latest nightly on there for him. Only to discover that he installs them himself!!!! He was bang up to date! F$%k me, he's only 10! My eldest uses Android Pay, he's 14......... He set that up, not me. I digress.

Did you know that Kernel Adiutor has an LMK section where you can set specific LMK profiles that get applied on boot?
[Samsung Galaxy S 5 Unified Development] fipsy:
That's the point! As soon as you have slightly higher requirements (even if it only means that you want to synchronize certain directories e. g. at night with Dropbox, Yandex or Microsoft) or make some backups of your files you are hooked!

Since I have always used the Boeffla kernel (only there I can configure the charging current, which is very important to me), I have of course never used the Kernel Adiutor, although I know the app. However, I don't like to change the LMK values. In my experience, this often makes the device slow and leads to further problems.
[Samsung Galaxy S 5 Unified Development] fitittome:
I cannot believe you said that! The profiles are complex numbers, but pre-set. Very light, Light, Medium, Aggressive, Very Aggressive, Do not press this one, etc.
[Samsung Galaxy S 5 Unified Development] fipsy:
I meant the Boeffla Config app, there are no predefined profiles. But even if I find a profile that is running at the moment, I don't have a good feeling about it, because it always can't work anymore. This means that I would have to check every day whether the desired background tasks were running properly. Right now I'm doing this, but it's annoying and not a permanent solution because it leads the sense of automated tasks to absurdity!
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Get OnePlus 5 with 6gb or 8gb ram you will never be worrying about it again
[Samsung Galaxy S 5 Unified Development] Immortal0907:
believe me I am an hardcore android user too... and I tried switching to lumia 640xl, windows 8 on it was bad then windows 10 mobile came out and it went from bad to worse... and you cant do anything about that... As for apple they pretty much make older devices like 5s unusable by 'updating it' they simply make newer ios drain and slow older iphones... so when you think a little android is still the best option
[Samsung Galaxy S 5 Unified Development] Steve Geemaggio:
Hello,

Just want to say thanks to [MENTION=2693412]haggertk[/MENTION] for all the hard work getting LOS up and running on the S5. I've been using it for a long time now and have no complaints. Thanks again.

In case people don't know. Already a cool guy has got Oreo running on the S5 Check it out here:

https://xdaforums.com/galaxy-s5/unified-development/rom-lineageos-15-0-klte-t3680666

Great to see the S5 getting so much attention.

Great work by all!
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
Oops... Wrong Thread...

I'm not one to gossip, so you didn't hear this from me... LMAO! :)

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

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Samsung Galaxy S 5 Unified Development] fipsy:
I think this is very unlikely, because the size of the available memory has nothing to do with the fact that the LMK does not function properly. I still have 600 MB of RAM free if the system reports "low memory" and terminates the processes. That's only happened since September 20th. These problems never existed before. And it also doesn't happen when I downgrade to the old version.
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Since 20th Sep LOS devs took your and everyone 600MB free memory to feed Zram, Adaptive LMK, Swap more aggressively ever than before... I guess that's why.
[Samsung Galaxy S 5 Unified Development] fipsy:
I wanted to check this and flashed LOS 10/04 again (so I now used LOS kernel), deactivated the "Adaptive Low Memory Killer" with Kernel Adiutor and set the profile to "Very light". That didn't change anything. All problems are exactly the same!

Don't tell me this is "low memory" with LMK set to "very light":

([MENTION=7860020]Blackburn119[/MENTION]: In my opinion it just doesn't fit, even if I take your statement into account. Why are processes killed if the LMK is set up very light, so that even empty applications should not be killed until 102 MB of free RAM are reached but 465 MB are still available?)

10-05 20:18:59.336 I/ActivityManager(838): Low on memory:

10-05 20:18:59.337 I/ActivityManager(838): MemInfo: 78,072K slab, 13,512K shmem, 6,772K vm alloc, 32,800K page tables 12,944K kernel stack

10-05 20:18:59.337 I/ActivityManager(838): 9,720K buffers, 496,924K cached, 198,052K mapped, 156,364K free

10-05 20:18:59.337 I/ActivityManager(838): ZRAM: 111,688K RAM, 431,856K swap total, 152,908K swap free

10-05 20:18:59.337 I/ActivityManager(838): Free RAM: 464,956K

10-05 20:18:59.337 I/ActivityManager(838): Used RAM: 1,133,263K

10-05 20:18:59.337 I/ActivityManager(838): Lost RAM: 32,949K
[Samsung Galaxy S 5 Unified Development] haggertk:
I'll say one thing... Zram has been on consistently for over a year. Swap tuneables have not been changed in ages. Adaptive LMK was *re-added* due to rampant *****ing that it was left out of the kernel rebase (it was in and on using the same settings as is now with the old kernel).

I'm going to turn off adaptive LMK but leave it in the kernel. Those of you who want to play with it can do so, but the default will be disabled.

The dev did not "take your ram" any more than was the case prior to the kernel rebase.
[Samsung Galaxy S 5 Unified Development] ssamurai:
thank you for the breatiful ROM

I'm trying to restore the WIFI password ans SSID from the old rom I already did a backup with "wifi connexion manager" and I have the "wpa_supplicant.conf" from the old ROM

the issue that is ggiving me a headache from yesterday is when I restore the backup with "wifi connexion manager" it told me that it restored the 58 wifi AP but when I check I find only 8 AP the ones who are not protected with password I did it many time no success (my phone is rooted btwn) so I went to the classic methode I took the "wpa_supplicant.conf" I change the one in /data/misc/wifi still no AP with the password I opened the new file that I alredy copied it has all the APP inside but when I use an app the show the saved password I got only one the I entred manually so I search on the root directory I fount another file with the same name in system\etc\wifi I replaced and opned it it has the whole AP password but still the issue

I don't know is the file tha contain the wifi password is located somewhere else with a different name so if anyone know how to restore them I'll be thankful

the phone was rebooted many times still the same issue
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Hahaha thanks for not being silent, you should have clarified this more early to keep everyone away from misunderstanding.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
By going through the last few pages of this thread, and reading comments about zram, swap, LMK etc, I have a feeling like reading a complaint book. People even complain like the dev break this thing, that thing etc.. haggertk is maintaining this ROM(s) for almost an year without much issues. In my opinion, LOS is the only reliable alternative for stock ROM (on the basis of development and maintenance). Seems like you guys all forget about the hard work of dev to bring and maintain this ROM. Anyone can point issues (with logs), or even criticise (if you are sure), but here... what the hell...
[Samsung Galaxy S 5 Unified Development] fitittome:
Don't you guys understand?

The dev has switched off LMK to stop you all whinning

. He's not going to go around all the forums and Reddit etc. preaching this stuff. Anyway, IMHO, LMK isn't the problem it's the symptom.

As I understand it LMK is only doing what it is meant to be doing, LMK acts on what the kernel reports to it and LMK is proven.

So, to me albeit as a non-programmer, it is clear there is a bug somewhere much deeper in the system.

Not a single one of those people having issues could be bothered to spend a little time and get some real live data, exhibiting the problems to help the dev narrow the issue down. The *one* JIRA submitted (well done for doing that) went a little way to resolving, but no logcats were supplied and the dev was left to guess what the causes might be. But the dev went to the trouble to explain what he said a few posts back.

This bug isn't going to go away. It will get sucked up into Oreo but become much less significant with it's increased memory demands etc.

Because of our collective inaction an opportunity has been lost here to help make the S5 a better device and more capable of a smooth transition to Oreo.
[Samsung Galaxy S 5 Unified Development] DragonQ:
I am starting to question the stability of this ROM (well, the 20/09 build anyway). Every now and then (maybe once a day) I get random application crashes. It happens frequently with Magisk where it just stops working completely and I lose root until I reboot. I thought this was a Magisk bug (and it might still be) but other applications are having similar problems. I can notice when using my phone overnight that Twilight randomly turns off and then back on again 10-15 seconds later. This can happen a dozen times over a few minutes, then it stops and seems fine. Similarly, I've been driving when RocketPlayer seemingly exits for no reason. I start it up again, and it exits again. Clearly something strange is going on here - has anyone got similar issues?

I've attached some logs of what happened late last night - they are likely incomplete because Matlog itself also exits randomly! I can see lots of "<application> has died" log messages. Is it possible this is related to the memory issue currently being discussed?

10-05 22:28:05.242 I/TWILIGHT(19041): [22:28:05.242, main]: Low memory restart succeeded
10-05 22:28:05.242 I/TWILIGHT(19041): [22:28:05.242, main]: Service start com.urbandroid.lux.action_command_restart_on_low_memory
10-05 22:28:05.242 I/TWILIGHT(19041): [22:28:05.242, main]: Extra memory_low_time
10-05 22:28:05.242 I/TWILIGHT(19041): [22:28:05.242, main]: Extra android.intent.extra.ALARM_COUNT
10-05 22:28:05.242 I/TWILIGHT(19041): [22:28:05.242, main]: Extra memory_low_delay

There's also lots of Memory trim requested messages too.
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
I'm also having issues with apps being killed. No crash prompts, they just stop. Only since updating to the 10/4 build.

I have GSAM and 1Weather icons in the status bar and they will randomly disappear. I launch the apps and they appear again. Once, I unlocked the phone and Swype was asking to be configured again.
[Samsung Galaxy S 5 Unified Development] cal002:
You are confused what "Free RAM" means: "Free" != unused. "Free" includes cached data

(ActivityManager's perspective is different than kernel's, that's why the "cached" above

is larger than "Free RAM"). If you think the system would drop caches, thereby degrading overall

system performance, just to keep your background apps running, you're wrong.

Maybe you could get more insights by running "dumpsys meminfo" ("dumpsys meminfo -h" for help).
[Samsung Galaxy S 5 Unified Development] Immortal0907:
looks like its closing apps due to low ram memory... it may have something to do with LMK which is topic right now... since its disabled wait for next nightly and see if problem persists
[Samsung Galaxy S 5 Unified Development] DragonQ:
I am not running the 10/04 build though, I'm on 20/09. When was this issue supposedly introduced?
[Samsung Galaxy S 5 Unified Development] Immortal0907:
just read posts few pages back.. its not an issue.. its low memory killer which can be aggressive some times so maintainer will disable it in next nightly... lmk is standard 'feature' in android ram management... it simply kills some processes so it can make space for others... but like I said here it can go 'hulk' sometimes... so if youre up to try next nightly update from 20/09 should work fine I think...
[Samsung Galaxy S 5 Unified Development] DragonQ:
Alright I will try that, thanks. It's pretty crazy that it can just stop all of these pretty important apps on a whim though. I'll have a look and see if I'm running any high-memory apps that I can do without in the mean time.
[Samsung Galaxy S 5 Unified Development] fitittome:
Well that's an eye-opener. :good: I have attached a dumpsys from my daily driver that does not exhibit these problems. It maybe a useful benchmark for those who are.
[Samsung Galaxy S 5 Unified Development] DragonQ:
Sorting my running apps by RAM usage doesn't show anything obvious that I can ditch. Most of it is Google or Android system stuff. I did see some applications pop up sometimes without me opening them, e.g. Maps. Not sure why. The only non-essential app that was using 100+ MB of RAM was System Panel 2, so I tried uninstalling that. I can't really check current RAM usage whilst driving though so I don't think I'm going to find a "smoking gun" app.

I know Immortal0907 said it's "not an issue" but when actively-used applications like an audio player are being stopped rather than background tasks like Facebook notifications or something, clearly something wrong (be it a configuration issue, or the OS using too much RAM itself, etc.).
[Samsung Galaxy S 5 Unified Development] 10goto10:
Yeah, that's the messed-up part. Audio playing apps or apps that have ongoing notifications should be marked as 'perceptible', and thus will be killed second-to-last to the visible, currently running app.

Maybe the adaptive LMK has gotten buggy or something. I disabled it on mine on Oct-04, but I still can't steam audio while browsing the web without having the player close. Running Sep-13 build with the same exact gapps and installed apps shows no issues. App memory usage (as indicated in settings) doesn't show any changes, if anything, the latest builds shows lower memory usage (at the expense of usability.)

Sorry if I came across as entitled. I appreciate haggertk's (et al) thankless work for keeping this device up to date.
[Samsung Galaxy S 5 Unified Development] DragonQ:
It's interesting that 13/09 works for you, since that build was horrifically laggy and battery hungry for me, something that 20/09 fixed. Annoyingly there were a LOT of changes between 13/09 and 20/09 builds, so even if we can narrow the regression down to that week there's a lot of possible culprits. However, the last change labelled "lowmemorykiller" was actually in 13/09 so it's a bit odd if that build is fine.
[Samsung Galaxy S 5 Unified Development] 10goto10:
I'm using a custom kernel (Boeffla beta10) without any tweaks, maybe the merges to the kernel differed slightly somehow so the LMK changes didn't get merged to the custom kernel or something. Works for me. *shrug*
[Samsung Galaxy S 5 Unified Development] fipsy:
That's how I see things, too. However, I believe that disabling ALMK in the kernel adiutor has no effect at least at the moment. Is that possible? Regardless of whether ALMK is switched on or off in the Adiutor, the LMK always strikes mercilessly, even if a lot of free RAM is still available.

---------- Post added at 03:22 PM ---------- Previous post was at 03:14 PM ----------

I think we have all praised the work of the developers more than once! There's no doubt about it! But if there are serious problems, you have to be able to name them! And if these problems occur suddenly from one version to the next and spread across multiple versions (like in this case), then understandably the waves start to blow up. And logcats have also been posted several times. I can't see any unjustified "complaints" here.

I would just like to remind you that I was one of the first users to point out the problems with sdcardfs filesystem several times in March of this year. I was considered insane by most users here (with the exception of [MENTION=7978913]fitittome[/MENTION]) and the reactions were similar to yours. 3 months later it was clear to everyone that there was a very serious problem with sdcardfs. So please be a little more cautious with criticism when new bugs are named. Otherwise, no one will dare to open their mouth. Solely adulation is not the purpose of a forum!
[Samsung Galaxy S 5 Unified Development] fitittome:
Just wondering and out of my depth, I was browsing through some of the changes and spotted that BFQ had been upgraded. BFQ handles the scheduling of reading and writing to storage. I guess that ZRAM and Swapping would all be handled through BFQ too. If BFQ was 'misbehaving' surely this would affect the general responsiveness of the system etc. maybe to the point that LMK would think the application is no longer in use. I am looking at the changes here on Gerrit.

[MENTION=7518817]cal002[/MENTION] what would be the best way of 'looking' at performance of BFQ when a device starts to misbehave? Perhaps there something like dumpsys meminfo that mere mortals can understand?
[Samsung Galaxy S 5 Unified Development] fipsy:
At first glance, I would also sign this statement. On the other hand, it must also be said that the problems have started with the September 13 version. The changelog for this version documents 13(!) changes to the "lowmemorykiller". The correlation seems therefore to be evident!

---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------

Then you didn't read my contributions! In the meantime I have invested about 5 hours in clearing up the error. The logfiles are unfortunately not very informative. For example, a "am_low_memory" condition occurs suddenly, although there is still enough memory and then all processes are killed. I documented that, too.
[Samsung Galaxy S 5 Unified Development] fitittome:
Thanks. But we have all fallen into the assumptions trap before. See my above post...... It may well be nothing, I do not know enough, but the only way to track down this bug is by gathering evidence and getting it easily reproducible...... then filing a JIRA. ;)
[Samsung Galaxy S 5 Unified Development] fipsy:
Thank you for the explanations! But if the system has a choice of dropping caches and slowing down the system a bit or terminating *running* applications in the background and causing errors, then I choose the first! :D

---------- Post added at 04:14 PM ---------- Previous post was at 04:10 PM ----------

As I said before, as far as I know, on September 13th. Please check the changelog of this version. Many changes have been made to the lowmemorykiller there.

---------- Post added at 04:25 PM ---------- Previous post was at 04:14 PM ----------

Exactly! But I think I remember the first time I had problems with killed apps was on September 13th. I've written this somewhere before, many pages back. ;)
[Samsung Galaxy S 5 Unified Development] fitittome:
Here you go, monkey playing with a machine gun again. :D

Just to eliminate those BFQ changes Kernel Adiutor has an option to change the I/O Scheduler. I never realized that one could change these things on the fly. I changed mine, on internal storage to 'deadline' which is apparently a reasonable way to do this sort of thing. It seems to work fine, much as before.

You never know it may help.....
[Samsung Galaxy S 5 Unified Development] Immortal0907:
Here it is. So now just wait and see...
[Samsung Galaxy S 5 Unified Development] jiml8:
For those who are having trouble with the LMK, I would recommend you investigate a bit of kernel tuning.

Personally, I have not found it to be necessary; I am on the 20/9 build and don't experience the problems with apps being killed that others report. However, everyone's configuration is different so my experience may not translate to you.

I have found that many linux systems benefit enormously by tuning some of the sysctls, and Android is a linux system.

Take a look at these tunables:

vm.dirty_background_ratio

vm.dirty_ratio

vm.overcommit_ratio

vm.overcommit_memory

The first two affect the size and handling of the cache, and the second two affect how the system treats virtual memory. I know the first two are available in the stock LOS kernel; I am not certain about the other two.

The effect of these tunables is both subtle and complex, but will have a profound effect on how your system behaves. Because of this, I will refer you all to the wealth of online literature rather than writing a huge post here to describe them.

I have solved subtle problems on many different linux systems by configuring these tunables to match the usage pattern and purpose of the system in question.
[Samsung Galaxy S 5 Unified Development] fipsy:
As far as I'm concerned, I have a reproducible test for the LMK problem. I synchronize approx. 5 GB of data with my NAS via the App FolderSync. If that works, everything's okay. This test has not yet been a single time wrong regarding the LMK issue.

I changed the scheduler from bfq to cfq and ran the test app. It's the same as before: The app is killed after a few seconds. So it seems to have nothing to do with the scheduler.

By the way: The adaptive LMK is switched off here according to Kernel Adiutor! In effect, this simply means that a zero is written to the file /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk:

echo '0' > /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk

That's why I asked if the value in this file is taken into account at all! Because no matter if the switch is on or off, I don't see any difference!

With regard to my last sentence, I wonder whether this will make any difference. After all, it is already possible to switch off the ALMK - without any noticeable effect.