yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] fbs:
ahm.. I wasn't aware of your problems.. but anyway your ROM itself seems to be corrupted, by the logcat you have posted.. so no tests with it are really "valid"..

and even when testing something with a clean rom, you have to repeat like 3 times to be more precise...

there are sooooooooooooo many variables that can influence in almost everything you do with a smartphone..

I mean.. if you take a picture and it takes too long to "save" it, what could be the cause?

- no ready free ram, the system has to empty some

- your i/o scheduler might have a bug and keeps waiting for nothing

- another app is already writing to your SD and your picture will be in the "queue"

- that part of your sd is slower because it was used too many times

- there weren't contiguous space on sd to save the picture, system has to write tiny pieces in each little space it finds

- your cam app is stupid and try to save the 8MB picture in little pieces of 1kb a time

- a process/app is in loop consuming all your cpu resources

uh if I think a bit more I can easily double this list.. lol
[Galaxy S 5 Original Android Development] fipsy:
I do not really think the ROM is corrupted because I've never had such messages before and after I installed Boeffla kernel, the messages also didn't show up anymore. The problems only occurred directly after flashing the current LOS ROM from September 27th.

Yeah, you're right. I have now tested it several times under different conditions with both Boeffla kernels (yours and Andi's) and there are no significant differences after several attempts anymore.

However, it's quite clear that your changes to the kernel fixed the problems with killed background apps on my system. I have now reproduced this several times.
[Galaxy S 5 Original Android Development] fbs:
This is the general idea all the people have.. But, come on, you are a developer, you know a BAD code will be slow no matter how much ram you have..

In this Android context, much more RAM won't make any smartphone really "faster". It will just ALLOW lots of apps to be all running together without closing(killing) the least used ones. UNLESS you use a HUGE app that would use more than 1GB of RAM, and I haven't seem anything coming near that.....
[Galaxy S 5 Original Android Development] fipsy:
I totally agree with you! When I had the problem with am_low_memory, the system reported that more than 500 MB of RAM was unused. This makes it quite clear to me that it cannot really be a lack of memory, but rather a software problem.
[Galaxy S 5 Original Android Development] andip71:
To 1) The right way is to report this to LineageOS team, so they can officially fix it. I never fixed issues in official LineageOS or OOS code myself, as I consider it not my cup of tea. One may consider this a very harsh opinion, but it is like it is.

So I will not do any work here, especially not as this kernel is soon completely dead (I am hoping every week they start LineageOS 15 now, so I can put this device to rest in peace).

The situation is quite bad with code quality for the S5 here. I have my opinions why and told the developers many time to not do specific things. But they decided to not listen to me and thus I am not fixing their stuff now.

to 2) zRam: Also something which links into the above. The zRam/vnswap driver was backported from a driver from a higher kernel release quite long time ago. This broke the ability to unload or change it after it has been loaded. This is when I decided to strip that down to a safe minimum, as everything else would have required workarounds. I hate workaround solutions that break one day again, so... thanks to the devs also not listening to me, I had to remove it.

Yeah, I am a developer and software architect.

And this is why I say "more ram is good". I was NOT saying that in the context of having a lot of bad, broken code like in the Galaxy S5 world. I was saying that as a general statement, assuming normal quality code.

And the general statement is just true, nobody will ever dispute this.

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
Lord Boeffla,

Is there a chance we could get an earlier beta build of the kernel available? I have major lag with the recent builds and went to install 4.0 over the top. Now my bluetooth is broken and it says "Bluetooth Share Has Stopped" on boot. I'm going to try to flash the ROM, then your kernel again to see if that fixes it. But I know the earlier builds worked well!
[Galaxy S 5 Original Android Development] KazuDante:
have to use latest to fix bluetooth error , and other kernel thats not up to date with Lineage's changes that they made in the kernel will give you that bluetooth error sadly.(from what i experienced)

For the lag part i find that weird because to me it look like its much snappier , but then again the lag could be for the rom that you are using and also the certain apps that you have installed. So i guess try a clean full-wipe and re-install the rom with the latest Boeffla beta kernel ( i think its on 11 now) and see if it still lags but Bluetooth should be fixed with latest (beta) Boeffla kernel.
[Galaxy S 5 Original Android Development] andip71:
Today there will be the regular maintenance update.

But what I saw in the changes, it is not much... I would not have too much hope.

Andi
[Galaxy S 5 Original Android Development] Legitsu:
lets talk turkey, how much would it cost us to pay you for a los15 version
[Galaxy S 5 Original Android Development] andip71:
No money in the world can create me the time I need for it (which I do not have).

I am sorry, but LOS 14.1 is really the end now.

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
So an older build is available somewhere? Any clue why my downgrade borked the kernel?
[Galaxy S 5 Original Android Development] andip71:
Dont know what you mean by "your downgrade" etc.

But on the S5, I am not surprised about anything that goes wrong. It is a sh*** device with a sh*** LineageOS implementation (sorry, but this is my opinion).

Older kernels are in the test folder on www.boeffla.de, as always.

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
1) I attempted to downgrade the kernel from 4.1beta11 to 4.0 by flashing over in TWRP. When I rebooted, bluetooth wouldn't turn on saying "Bluetooth Share has Stopped" repeatedly. I wonder whether you know the cause, if others have seen it before, or if there is a fix. Also whether there is a proper method to go back to a previous version of your kernel. I tried flashing the ROM to return to LineageOS kernel, but it stopped with Error 7

2) That's not fair, the S5 is still a perfectly capable phone. I think LineageOS is more problematic than the hardware (sorry, but this is MY opinion ;)

3) The Test folder only contains the latest 3 beta kernels as best I can tell. Are earlier kernels available to download?
[Galaxy S 5 Original Android Development] andip71:
1) This is the right way. But 4.0 stable is very old, so would recommend you try beta9 instead.

And no, I have no idea without looking into it. The S5 is quite a mess, there were many kernel rebases in tha past months, useless upstreaming and other stuff. I explained before I adviced some devs to not do specific things but they did as they wanted. So now we have the mess and I will not clean that up for such an old device.

2) I have a different opinion, always had on the S5. But that is nothing to discuss.

3) The last three maybe, if you want a specific earlier beta, I can make it available too.

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
Maybe the odd numbered earlier builds? 1,3,5,7 would help me solve this issue?! THanks!
[Galaxy S 5 Original Android Development] andip71:
Uploaded them for you.

Andi
[Galaxy S 5 Original Android Development] ldeveraux:
Thanks a ton! I'll test them out when I get home. THanks again!
[Galaxy S 5 Original Android Development] andip71:
Hi all,

maintenance update out, as promised.

Version 4.1-beta12

04.10.2017

Update: Updated with latest official LineageOS kernel commits as of 04.10.17, 08.00 CET

Enjoy

Andi
[Galaxy S 5 Original Android Development] fipsy:
I'd also recommend beta9. For me this was the best working version of the last time.
[Galaxy S 5 Original Android Development] KazuDante:
does the beta9 have the bluetooth error.
[Galaxy S 5 Original Android Development] fipsy:
I don't think so. But it has the UMS error.
[Galaxy S 5 Original Android Development] audianer:
Hey,

does anybody is using OC?
[Galaxy S 5 Original Android Development] 10goto10:
I don't think overclocking is worth the extra power usage, heat and instability for this device. I tried it myself, can't really perceive the difference. Benchmarks only improve by 5% or so. Not to mention thermal throttling will kick in more often, which caps your speed even if you're overclocked. Even with stock frequencies, with sustained all core usage the cpu can hit 80c in 5 minutes! This is dangerous and will also degrade the battery (Li-Ion cells is sensitive to heat.)

If you need more performance, try switching the Interactive governor tunables to performance or switch to the conservative CPU governor. Try also bumping the min GPU frequency. You can also undervolt to reduce thermal throttling but this comes at the risk of instability (every chip is different so you must stress test the device to ensure stability with your desired voltages) and is totally unsupported.

Hope this helps.
[Galaxy S 5 Original Android Development] Ragnar Eldur:
Hey guys I just got myself the flagship Galaxy S7 Plus and I'm wondering how to root it, can anyone help me?
[Galaxy S 5 Original Android Development] j1gga84:
I would say you are completely wrong here ;)

Please ask this in the Galaxy S7 forum and/or the SuperSU/Magisk Thread ;)

regards
[Galaxy S 5 Original Android Development] fipsy:
[MENTION=947981]Lord Boeffla[/MENTION]: I have a question about a kernel internal. You can probably answer that easiest. For the next kernel the dev sets the ALMK to off by default, after I've been really nagging in the LOS thread (already have a bad conscience).

It is said that you can already deactivate the ALMK by writing a zero to the file /sys/module/lowmemorykiller/parameters/enable_adaptive_lmk. In my opinion, however, this has no effect at all at the moment. Could you perhaps check if the value in this file is taken into account at all and turns off the ALMK? Would be so nice! Thanks a lot!
[Galaxy S 5 Original Android Development] Ragnar Eldur:
Oh haha yeah forgot this is meant for the S5
[Galaxy S 5 Original Android Development] andip71:
Interesting move, which I am not happy with. I am not sure whether I will follow switching off the LMK completely. My opinion is, this is not a real solution to the problems but only a dirty workaround.

I can check early next week if that piping a zero would help. And you probably would need to pipe zeros for all different LMK levels in to make it work at all...

Andi
[Galaxy S 5 Original Android Development] fipsy:
Hi Andi, thanks for your answer! Please excuse me if I didn't explain something properly, I'm not really into this thing. But as I have understood, there was originally no adaptive LMK in Android N or Lineage 14.1, but only the "normal" LMK. The adaptive LMK was probably backported from Android O as I have understood. This adaptive part was formerly turned on by default. Since then, more and more users have been complaining about the fact that important apps are simply being killed. We also had the problem since Boeffla Kernel beta10 (you remember?). And that is now being revoked. However, the LMK remains active and the ALMK also unchanged except that it's no longer standard.

In the Kernel Adiutor there is a switch that can only switch off the "new" adaptive part of the LMK (as far as I understand it). I have attached an appropriate screenshot. And this is done by piping a zero into the file mentioned above. But I do not think that this has any effect at all at the moment.

[MENTION=7978913]fitittome[/MENTION] and me were also wondering what the adaptive LMK exactly is. Whether it's an independent piece of code or just an extension of the LMK and in many parts the same code. Depending on this, it could also be possible that something went wrong with the "backport", which ruined the functionality of the whole LMK.
[Galaxy S 5 Original Android Development] Blackburn119:
You mean the fifth right? cause iPhone 8 plus should be place the the first spot above OnePlus 5, and you're on a wrong thread.
[Galaxy S 5 Original Android Development] Ragnar Eldur:
Ooooooo we have an iSheep, why don't you go to your little iHerd...

Android is freedom and power, iOS is stinking jail on a deserted island...

Don't choke on your rotten Apple! ?

By the way 6.2 inch QHD SUPER AMOLED this little beast has but is still smaller in size than the 5.5 inch ****ty IPS chunky iPhone. And nothing beats the ultra dual pixel camera. Oh and guess what, it still has the headphone jack because they know how to make a slick phone without compromise. Real teach masters at work, Samsung rules.

Apple products are for people that know nothing about technology.
[Galaxy S 5 Original Android Development] Amirk365:
Dude chill. I don't like them either but the phone is fast af. Now back to the topic
[Galaxy S 5 Original Android Development] haggertk:
Let's get one thing straight. One thing that I'm pretty sure Paul and I have explained before...

Adaptive LMK is not new to klte. It has been in the kernel from the periods of [2016-01-26, 2017-08-14], [2017-09-12, present].

Adaptive LMK has been a part of the klte kernel since 2016-01-26 in the cm-13.0 branch. It isn't a backport from O or anything of the sort. I did not include Adaptive LMK in the most recent rebase (pushed 2017-08-14) because I didn't feel that it really did anything of value. However, a bug reported was submitted (https://jira.lineageos.org/browse/REGRESSION-1076) and I received a large amount of personal communications complaining that the feature was missing. Based on response from the bug submitter, re-adding the the feature resolved the bug so it was re-merged into the kernel.
[Galaxy S 5 Original Android Development] Ragnar Eldur:
Haha ok Roger, over and out.
[Galaxy S 5 Original Android Development] andip71:
Hi all,

maintenance update is out.

Version 4.1-beta13

11.10.2017

Update: Updated with latest official LineageOS kernel commits as of 11.10.17, 08.00 CET

Enjoy

Andi
[Galaxy S 5 Original Android Development] fipsy:
Thank you! I wonder that the new LOS version is not out so far...
[Galaxy S 5 Original Android Development] andip71:
Still being built, it is then 4th next one that drops out of the build process...

https://jenkins.lineageos.org/job/android

Andi
[Galaxy S 5 Original Android Development] fipsy:
I am already very excited about the new version. Because some things were considered, which I always complained. Especially regarding SDcardFS and LMK.
[Galaxy S 5 Original Android Development] fipsy:
I wanted to come back to that in closing. The fact that the deactivation of the ALMK seemed to have no effect on the observed problem was because the issue had nothing to do with the ALMK. I already had that hunch. The problem was that the size of the zcache was ignored by the lowmemorykiller (https://review.lineageos.org/#/c/192510/). [MENTION=516058]fbs[/MENTION]: This also explains why the problem seemed to be solved by disabling zcache. The last commits have finally fixed the issue.

See also here: https://xdaforums.com/showpost.php?p=74123460&postcount=8716
[Galaxy S 5 Original Android Development] andip71:
Finally good news :)

Andi
[Galaxy S 5 Original Android Development] fbs:
I wanted to tell you that lmk is doomed and the zcache just aggravated the problem, lol, but it's not solved
[Galaxy S 5 Original Android Development] fipsy:
Depends on what you consider to be the problem. The *visible* problem with killed apps seems to be solved. The problems "under the hood" that are not visible by now are not solved, of course! But after all I've experienced with lineage OS and the S5, my expectations are extremely low - as my signature shows. ;-p
[Galaxy S 5 Original Android Development] andip71:
Hi all,

weekly maintenance update is out:

Version 4.1-beta14

18.10.2017

Update: Updated with latest official LineageOS kernel commits as of 18.10.17, 08.00 CET

Enjoy

Andi
[Galaxy S 5 Original Android Development] Nico1544:
Nice Work :) i Love your work:)

I want to start my own Kernel and need a little Bit help. ITS very nice if can help me a little Bit :)
[Galaxy S 5 Original Android Development] andip71:
Depends what you need.

To be honest: I do not have the time and capacity to teach someone from ground up. So you should know how to build a kernel from scratch at least etc.

If you then have a few dedicated questions, fine for me.

Just bear in mind, I will be "gone" to longer holidays very soon in a week, where I will not respond at all and also not read in forums for more than 3 weeks.

Andi
[Galaxy S 5 Original Android Development] fipsy:
Hi Andi, I have the feeling that there is a problem with either the new config app or the kernel, regarding the battery statistics. Up to now it has worked perfectly. But now the device had been running for 5:30 hours since the last disconnection from the mains supply when I also reset the custom values. The device has nearly not been used in the following 5 hours. Nevertheless, the statistics say that the display has been switched on for 5 hours, which is definitely wrong. With a discharge rate of -13%/h (which is stated), there could not be a residual charge of 88% after 5 hours. A discharge of about 2%/h over a period of 5 hours is however correct. It is also wrong that the display has been on for 12 hours since charging.

[IMG="Screenshot Boeffla Config"]https://s1.postimg.org/3ool5nu573/Screenshot_20171019-192533k.png[/IMG]

In fact, the screenshot of BetterBatteryStats clearly shows that the display was only switched on for 2 minutes. This is also in line with reality. So there is a problem with the detection of display on and off:

[IMG="Screenshot BetterBatterStats"]https://s1.postimg.org/6gn662mevj/Screenshot_20171019-192609k.png[/IMG]
[Galaxy S 5 Original Android Development] andip71:
Well, I think I need to be able to reproduce that behaviour in order to investigate anything.

So far I have not seen it ever. Probably I need to do exactly the same steps you did. I.e. putting device to charger, exactly knowing when to reset the custom statistics, when to remove it from charger, etc etc. Not sure if I will ever be able to reproduce it.

And in general: Battery statistics runs completely without kernel dependency, it even runs on devices not having Boeffla-Kernel, so the kernel is out of question here. However, I have to admit the code is very complex, it would not be a surprise when there are still bugs in it.

In the app, the code was not changed in one single line even since introduction a few weeks ago. So if, then this issue was in all the time.

Unfortunately (or fortunately) I will not do any changes to it in the next 4.5 weeks even, as I am close to going on holidays for a long time. I will even not read forums during that time. But when I am about to leave soon, I will state a message in the boards.

So, if you find a way to reproduce the display easily, then I can try this once I am back towards end of November and if I can also see it on my device, I am happy to investigate and fix.

Thanks

Andi
[Galaxy S 5 Original Android Development] fipsy:
I would agree with that. I've had it twice so far. Once a few weeks ago and again yesterday. I'm using an inductive charging station. Maybe it's related to that, too? But as I said, it's not that easy to reproduce. Everything seems to be fine today. But it's good to know that the function has nothing to do with the kernel, but only with the config app.
[Galaxy S 5 Original Android Development] fipsy:
[MENTION=947981]Lord Boeffla[/MENTION]: I was wrong earlier, the recognition of "display off" doesn't seem to work for me anymore. Even after many hours of deep sleep, the Config App still shows 00:00:00 display off. I have turned the display on and off many times without any change. I have also deleted the data and cache of the Boeffla Config App, reinstalled version 2.5.02 and restarted the Boeffla-Config V2 service. Without any success. By the way: The Boeffla-Config V2 service is 28 MB in size. This is huge! Is the Boeffla-Config V2 service also responsible for battery statistics? Because it always runs. No matter whether the battery statistics or other background services are activated or not.

What I also find irritating is that in version 2.5.02 (second image) the statistical data are evaluated differently than in 2.5.03 (first image). If I exchange the versions without any change in the data, the percentage values differ by 0.8%. A little weird, too. The difference between the following two screenshots is only the Boeffla Config Version.

[IMG="Boeffla Config V 2.5.03"]https://s1.postimg.org/6sb59u97r3/Screenshot_20171020-170839k.png[/IMG] [IMG="Boeffla Config V 2.5.02"]https://s1.postimg.org/5afhfr9fgv/Screenshot_20171020-171114k.png[/IMG]
[Galaxy S 5 Original Android Development] Nico1544:
Yes i have Read a Tutorial die building Kernels but have some troubels with a toolchain haha

Nico from Germany
[Galaxy S 5 Original Android Development] fipsy:
I have installed the new Boeffla Config app with battery statistics on my old Galaxy S3 with CyanogenMod 11. There the problem is exactly the same: Display Off is not recognized correctly. The display has been off for at least 19 hours since it was charged. However, only one second Display Off is displayed.

[IMG="Screenshot S3"]https://s1.postimg.org/36fapidgdb/Screenshot_2017-10-21-01-41-20k.png[/IMG]

What also irritates me quite a bit is the number of measured values collected. In almost 10 hours of "Display Off" only one single value was recorded?! That doesn't seem like much of a statistic to me. And 11 measured values in total over a period of more than 11 hours also seem to me to be far too few for statistics.

[IMG="Screenshot S5"]https://s1.postimg.org/6o9fggkhnj/Screenshot_20171021-154838k.png[/IMG]

I also noticed that the Boeffla-Config V2 service is not registered as a receiver for display on/off intents. Wouldn't it make sense to register the service as a broadcast receiver for the Intents android.intent.action.SCREEN_OFF and android.intent.action.SCREEN_ON and then record one value for each corresponding event? That would be ideal for accurate statistics.
[Galaxy S 5 Original Android Development] andip71:
Inductive charging is something I cannot test myself, but should make any difference.

As said, I can absolutely not reproduce this at all.

The receiver for the display on/off events is registered in code, not in manifest. That is the usual way to do it, there is no need to register that in the manifest.

I can only imagine you use a kind of intent blocker maybe? No idea why it behaves like that for you.

Or maybe the Boeffla-Config background service gets killed from time to time, then it would explain why the events are not recognized anymore.

You can check that easily: When you open Boeffla-Config, long press on the version information on the overview page, right upper corner. Then some debug info comes up, especially the service status. It must always be on true for both service status lines. If it is showing false for "service status start", then something killed the background service.

I guess you do not greenify Boeffla-Config in any way etc...

The second thing we can do is:

- you enable debug mode in the app settings (app maintenance section -> debug mode). Restart the app then.

By doing this, all received intents (screen off, on, batter change, charger etc.) are logged into bc.log file, so we know more about whether the intents do arrive at all or not etc.

Andi