yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] andip71:
Hi,

to cut a long story short: I will bring back the touch boost (cpu boost) control. But mpdecision will still boost you to 1574 MHz.

Without losing mpdecision, this cannot be changed (mpdecision is a closed source component).

You can move to other kernels, that have its own hotplug logic implemented if you want. Because I will always stick with mpdecision due to my close-to-stock objective.

So I am afraid, the switch you want is not possible in my kernel.

Regarding thermal throttling: This is some own thermal throttling logic zzmoove had implemented. As this led to reboots, especially on the S5, it got removed by the dev. But this has nothing to do with overheat protection.

Andi
[Galaxy S 5 Original Android Development] andip71:
I understand you would like to have all of that in one app.

However, this is not at all kernel related, and I am usually trying to not mix kernel and rom things.

Second, I also do not want to reinvent the wheel too much. All of that exists in multiple other apps, so I really do not have plans to replicate that again in my app.

Thanks for undrestanding

Andi
[Galaxy S 5 Original Android Development] Balrog86:
Yes, I understand this.

I just thought as you already implemented the useful trim command, it'd not a big change having an option doing it at boot time.

I also don't want to change to another kernel, I like your work.

Have a nice Day :)
[Galaxy S 5 Original Android Development] andip71:
Hi all,

here we go for a new update to LineageOS 14.1 Boeffla-Kernel:

Version

4.1-beta5

26.07.2017

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

Change: Internal kernel busybox updated to latest version 1.27.1 (self-compiled from sources, www.busybox.net)

Change: Touch boost (= CPU boost) configuration is enabled again in Boeffla-Config

(however note, the CPU peak to 1574 MHz is a mpdecision feature and not coming from cpu boost = you cannot get this removed by changing the touch boost settings)

Enjoy

Andi
[Galaxy S 5 Original Android Development] Legitsu:
you can't run zzmove AND MPDescision doing so leads to crashes even with the latest zzmove

even with MPDescision killed and zzmove native default selected crashes still occur I don't think zzmove is ever going to be 100% stable on every 801 device

zzmove has its own thermal protection routines anyway

unrelated do you know what the state of your frandom code is ?

sk8er tried to enable it it didn't seem to do anything
[Galaxy S 5 Original Android Development] andip71:
ZaneZam used zzmoove as daily driver on his 801 based OPO for 2 years without issues. It is more a s5 specific issue. Yeah, no Samsung anymore, lesson learned.

About frandom - I am not aware I have done any frandom implementation on the s5.

It is anyways a placebo only, not worth any efforts.

Andi
[Galaxy S 5 Original Android Development] Legitsu:
I have pretty much given up on making ZZMOVE work on my kltevzw

killing MPDescision greatly improves stability but it still RR's at least once every 4 to 8 hours

with lots of tweaks to zzmoves hotplugging and thermal behavior you can stretch that to 10 or so

alas

old device is old old device is unsupported
[Galaxy S 5 Original Android Development] KazuDante:
side questions , if im not mistaken on this kernel the gpu was boosted to 600mhz correct? am i the only kltevzw user that noticed that its not reaching or even displaying the 600mhz for the gpu? -because i tested a different kernel for the vzw and it ran the gpu at a max of 600mhz.
[Galaxy S 5 Original Android Development] Legitsu:
578 should be the max

id love to be-able to push the gpu beyond 600Mhz tho
[Galaxy S 5 Original Android Development] andip71:
GPU OC has been removed long time ago as it was proven to not have any effect.

Suspicion was this was limited by code in the trusted zone, which we cannot influence.

So, you have to live with 578 max I am afraid.

Andi
[Galaxy S 5 Original Android Development] KazuDante:
I'm no expert but when I compared the other kernel that pushed the kltevzw too 600mhz the one game I play everyday lost that little annoying lag, at first I assumed that it was due to touch boost that I could not configure yet since I don't have the means to get the pro version of the Boeffla app to be able to use the tunnable section. Then again a 4% increase in GPU is still a difference but I guess not as much if it went even higher.

Also quick question - can the trusted zone (remember seeing that file in a kernel and inside a rom) also effect the camera not functioning on a device that was flashed with a different ROM?
[Galaxy S 5 Original Android Development] Legitsu:
I suspect you could probly get around it by tweaking the pll/clockgen/bus ratio

the way to know would be to push the clock limit to something silly like 700Mhz and run antutu
[Galaxy S 5 Original Android Development] Legitsu:
the camera is broken on current LOS kernels

I would't use base LOS kernel source to power my toaster

use lb's
[Galaxy S 5 Original Android Development] andip71:
All done in the past, as previously mentioned.

It had no effect.

So I why is camera working fine for me then?

Andi
[Galaxy S 5 Original Android Development] The~Skater~187:
Camera is working fine here as well. No issues at all and I'm based off the same kernel source.
[Galaxy S 5 Original Android Development] saman3080:
#1
[Galaxy S 5 Original Android Development] andip71:
Hi all,

update rolling out now:

Version

4.1-beta6

02.08.2017

Update: Updated with latest official LineageOS kernel commits as of 31.07.17, 16.00 CET

Change: Internal improvements in kernel start script

Enjoy

Andi
[Galaxy S 5 Original Android Development] JohnnyMwanza:
Double tap to wake up...

hello how do i get Double tap to wake up working on my S5 with boeffla
[Galaxy S 5 Original Android Development] andip71:
By enabling it in Boeffla-Config, as simple?

But do not expect miracles, the S5 has no proper hardware support for it. So it does not work as nicely as on the OnePlus or LG phones.

Andi
[Galaxy S 5 Original Android Development] JohnnyMwanza:
Thank you

Alright Thank you.... i tried that about 3 days ago.... its hasnt been responding even with beta 6....i knew it had to do with it being supported with the hardware.... anyway thank you Lord Boeffla... keep up the Good work :)
[Galaxy S 5 Original Android Development] andip71:
But when you enable it, it still must work.

It does here, just not as responsive as on other phones due to the given limitations.

Andi
[Galaxy S 5 Original Android Development] JohnnyMwanza:
Still not Working

Well still sure why its not responding but my S5 gives a Flickering effect of green before going off or when the brightness is full turned down.... i donk know if that could cause this... plus i have no idea why my S5 flickers like that... when it was new it didnt do this.....
[Galaxy S 5 Original Android Development] andip71:
I cannot answer why your s5 flickers.

We do not even know which rom (version) you use, nor if you have g900f or something else etc etc.

It seems to be a S5 issue, I heard from time to time it flickers for some people, but there was no trace back to the kernel.

Andi
[Galaxy S 5 Original Android Development] JohnnyMwanza:
Yes its G900F but otherwise ill just work with the Off-screen Fingerprint wake up..... thank you for the help Lord Boeffla
[Galaxy S 5 Original Android Development] SuperSandro2000:
Probably hardware defect. Had the same thing a while ago and got a screen replacement.
[Galaxy S 5 Original Android Development] JohnnyMwanza:
Sure....

How Much did the screen cost where u bought it???
[Galaxy S 5 Original Android Development] SuperSandro2000:
Was still in my warranty. Dunno know. Think it is a two year warranty here in Germany and I think I got another two on the screen now. But I probably ditch the s5 soon.

I would keep the screen as long as it functions because it will probably soon completely break and then buy a new screen for about 50€ plus installation or buy a new phone.
[Galaxy S 5 Original Android Development] epsoopl:
Disable HW overlays and force gpu rendering in developer options. This solved my screen flickering. If not. flash full stock with odin,check nand erase all. Use it for while and play with brightnes, set it to full. Then flash other rom.
[Galaxy S 5 Original Android Development] SuperSandro2000:
It did not fix my issue completely but for 95% of it. I still see a very thin lighter line at lowest brightness. Make sure to reboot after you change the settings.

Edit: problem is back. Gonna do the second thing when I get home.
[Galaxy S 5 Original Android Development] fipsy:
Please read this post: https://xdaforums.com/showpost.php?p=73285481&postcount=7669

There are heavy problems when sending or receiving media with WhatsApp on the new kernel as of 2017-08-02!
[Galaxy S 5 Original Android Development] j1gga84:
I don't think it is kernel related.

Currently I am using smartpack lite kernel and it also uses LOS kernel commits and it's build date is also 2017-08-02 and I have absolutely no issues with sending or receiving media files via whatsapp.

Did you try a clean install of LineageOS ?

You can do a full backup in recovery, flash latest LOS on a fully clean system, install Whatsapp and Boeffla kernel again and report back.

regards
[Galaxy S 5 Original Android Development] andip71:
This nonsense made my day.

Thanks for giving me a good laugh.

Andi
[Galaxy S 5 Original Android Development] fipsy:
First: Thanks for your nice answer and the suggestions!

It is not directly kernel related but definitely indirectly: If I flash the kernel from 2017-07-26 everything works fine. If I flash the kernel from 2017-08-02 the problems immediately occur. I do nothing else than flashing the kernel with TWRP. Tested it three(!) times. Always the same result! So it's reproducible.

BUT: I have a second Galaxy S5 for testing. As you recommended I made a fresh install on this phone, configured everything as on the other one and the issue doesn't occur. So changing the kernel from the old 2017-07-26 version to 2017-08-02 changes something that produces these problems. Only the developer could give a hint what has been changed and could cause these problems.

I have to find it out or I have to use the LOS kernel that doesn't make any problems. I can not and will not configure my phone completely new as I just did it 4 weeks ago and I don't have the time to spend 5 days every month for configuring the phone completely new.

Cheers, Volker

---------- Post added at 06:54 PM ---------- Previous post was at 06:50 PM ----------

This is definitely not the kind of answer that makes people think about donating again...
[Galaxy S 5 Original Android Development] andip71:
Fipsy, this is quite simple.

I read your post in the LingeageOS thread, and you surely know the old German saying:

"So wie man in den Wald ruft, so kommt es zurück".

The thing is, you said the kernel needs to be

blamed

. Without any prove this is the case, just your own personal experience. However there are hundreds using my kernel not having the described issue, hence this was a very brave post not stating the truth.

Now I know, Germany and Germans have a big "blaming culture". I know that, being German myself. They do not say "I believe xyz causes it", they say "xyz is to be blamed". Which is also not the most friendly way as you surely concur.

In short: when someone publicly want to blame work I have done (for free btw.) for a reason that is not true, please accept I usually have a good laugh. My reaction to these kind of posts is very sensitive, or even allergic.

It is about the wording, the way to say things. And not following the blaming culture, which is so common in our country.

Don't know if the message came across. Peace.

Andi

P.S.: I am not heading for donations at all, I only want people to donate who truly feel they should.
[Galaxy S 5 Original Android Development] fipsy:
Hi Andi,

thanks for the explanations!

What I meant when I used the word "blame" in this context was "Schuld / Ursache für ein Problem". In english: The cause for a problem. When I noticed that the problem only occured with the latest Boeffla Kernel from 20170802 and not with any earlier versions, my first assumption was wrong that LOS was responsible. I wanted to express this in the LOS-Thread. It was not meant as an accusation but an uncouth explanation.

To prove that there is a relation to boeffla kernel, yesterday I made a lot of testing on the fresh installed S5. The problem has two originators and is also related to the Apps2SD binding method as I earlier supposed. Since boeffla kernel 20170802 it is not possible anymore to unbind folders that have previously been bound with the Apps2SD mount script (su.d or init.d). You may reproduce this by yourself. With earlier kernel versions it worked like a charm. You have been able to bind and unbind folders as often as you wanted. This is not possible anymore with the new kernel. So there must have been a change in the handling of folder bindings with the new kernel.

If I delete the Apps2SD mount scripts so that no folders are bound from the external to the internal sdcard everything is okay and sending and receiving media with WhatsApp works again.

So at the moment there are only two ways to solve the problem: Not using folder mounts or not using the newest boeffla kernel. Would be nice if both was possible again as it was until 2nd of august.

But we also have a big culture in not taking other people seriously. Especially if they have critical spirit... Maybe these are two sides of the same medal.

Two years ago I really did. Maybe I will feel like this again. Depends on whether the problem can be solved. :angel:

Cheers, Volker
[Galaxy S 5 Original Android Development] Legitsu:
nobody else has any problems remotely like yours

the flickering screams hardware failure to me and yes its possible for the kernel to make a hardware problem more evident but doesn't change the fact that its still a hardware problem
[Galaxy S 5 Original Android Development] fipsy:
Because obviously no one has the same configuration as me. Try the following and you will be able to reproduce the failure that is 100% related to the kernel.

It is NO hardware problem and it is reproducible on two different fresh installed Galaxy S5 devices: The essential point is, that the external sdcard from which the folder was bound with Apps2SD is exFAT formatted! When it is FAT32 formatted WhatsApp is able to send and receive media with Boeffla Kernel beta6. If it is exFAT formatted it is not possible to send and receive media anymore!

So what to do to provoke this error:

Sorry, I have investigated nearly 2 days in unpleasant work to find out all of this. And I have been subjected to an avalanche of ridicule and mockery. It's really dreary...
[Galaxy S 5 Original Android Development] omgbossis21:
Unfortunantly unoriginal kernels aren't supported here so id ask this in the boeffla thread. You can logcat on a working buld and logcat on a non working build (preferably same kernel, boeffla if it always works on stock lineage). The logcat will give an idea of the issurme but boeffla only sync the latest kernel stock builds to his. It sounds like a storage issue that using the privacy guard tool to grant permissions like storage may fix. A logcat is needed for sure though.
[Galaxy S 5 Original Android Development] andip71:
I am honest - I have no idea.

The diff between beta 5 and beta 6 is only CM commits and one single script change which has no influence.

I also diffed code changes between beta 6 and official CM14.1 repo - only boeffla changes are in, as before on beta5.

If you had said it works with beta4 but not with beta5 anymore, then I would have thought the new busybox could cause it.

So - no idea honestly. Maybe next beta magically fixes it again, although that would be very interesting.

I can only recommend you to stay on previos beta for now, or revert to LinageOS stock kernel.

Have no better news, sorry.

(and excuse my ignorance: I do not try to replicate it - I never used app2sd and never want to use it)

What could still help:

- any logcat output which indicates issues with the mount of the directory on ext sd card?

- what when you try to write into that mounted folder with a file manager app (total commander, solid explorer, root explorer etc.) - any error then?

Andi
[Galaxy S 5 Original Android Development] it'sup:
I know I'm super late on this post, but is their any support for SM-900H?
[Galaxy S 5 Original Android Development] andip71:
Not official, as I do not own this device.

Maybe someone else can comment whether the kernel works ok on a 900H too.

Andi
[Galaxy S 5 Original Android Development] fipsy:
Thanks a lot for your answer!

Yes, it's really strange. Because with beta5 it works. I'm using beta5 again now for 2 days and have no issues. I love your kernel because it makes me able to control the charging current. Resulting in a cool smartphone when charging and a longer battery life.

I also hope for a magical fix. :) It maybe a complex concurrence of many different issues that cause this problem. I have another issue with external memory that I'm trying to track down since many weeks without any success: The binding of the external sdcard in /storage/1234-5678 (just an example) sometimes gets lost. This subsequently causes heavy errors with many applications. But the sdcard still is accessible in /mnt/media_rw/1234-5678. Only the binding to /storage/ gets lost. I have no idea what the reason for this issue is. But it probably has nothing to do with the issue we talked about.

I also would not use it if it was possible to set the media storage location in WhatsApp! But it still isn't. And I don't want to have all the media stored on my internal card.

I'll investigate some time now in this logcat and give feedback then.

No problems! Copying with Root Explorer and ES File Explorer to the bound folder on the internal sdcard works without any issues.

But I just made a test with receiving a video with WhatsApp. The video could be downloaded and saved to the bound folder without any issues! Just when receiving pictures this doesn't work. The progress indicator begins to rotate when trying to download the picture and immediately stops rotating. It's very strange. I think we need a logcat now... :D
[Galaxy S 5 Original Android Development] andip71:
Well, not really unfortunately.

There is not specific error spotted in the log.

This is really a weird thing. I will let you know once I have more ideas.

Andi
[Galaxy S 5 Original Android Development] fipsy:
I had already feared this. :crying: When I was looking at the logfile the only difference I noticed was that in the case of success the downloaded picture was processed by the media scanner whereas it wasn't processed if the download was unsuccessful. :rolleyes:

Thanks a lot for you effort so far! I'm curious if we will find something sometime...

Volker
[Galaxy S 5 Original Android Development] andip71:
The thing is... the LineageOS commits between beta5 and 6 are more than 60. So I cannot even offer you to remove commit by commit until the one causing it is found.

Also it does not make sense as these commits are in stock kernel too (hopefully, I mean... there is no proof for that I guess, I just can prove what is in my kernels 100%).

So let's see if tomorrows nightly makes any difference with beta6 for you.

Andi
[Galaxy S 5 Original Android Development] fipsy:
That's understandable. The thing is that with actual LOS kernel the issue doesn't occur. My first deed was to revert to the last LOS version from 20170726. If using this LOS version with boeffla kernel beta5 everything is fine, but if using the same (old) LOS version with boeffla kernel beta6 the error occurs. That was the reason why I located the origin for the problem in the boeffla kernel.

I'm curiuos, too. ;)

Volker
[Galaxy S 5 Original Android Development] jjkrause1:
I opened my Boeffla-Config app this morning and a "Tip of the day" popped up. Before I could read it, I got a notification saying a newer version was available so I installed it. The tip didn't reappear after I restarted the app. Can anyone tell me what it said?
[Galaxy S 5 Original Android Development] andip71:
Good! This reminds me, I should probably display the tip of the day last thing, so an app update cannot interfere anymore.

It said:

Did you know, it is simple to go back to stock value for a particular setting??

Every setting in Boeffla-Config "knows" what the stock value is. You can easily find out the stock value for it by long-pressing the description of the setting (for sliders long-press the value left of the slider).

Then a dialog window shows up, telling you what the stock value of the setting is. And in most of the cases you can automatically apply that by a button click.

You should certainly check that out, many do not even know about it.​

Andi
[Galaxy S 5 Original Android Development] it'sup:
Hey, uhh wow The lord himself.... "but wouldn't that hard brick your device? By the way, Thanks a lot for your work!!! Your kernels are the best out there!!! The best!:angel:
[Galaxy S 5 Original Android Development] andip71:
I doubt it would be a hard brick.

But comparing the phone specs, it is not even worth a try.

CPU is quite different between the phones, so it would not work.

Andi
[Galaxy S 5 Original Android Development] fipsy:
I just installed the new LOS version 20170809. And it became even more worse. Now the error also occurs with the LOS kernel. It's not possible anymore to receive pictures with WhatApp if the WhatsApp folder is bound to an exFAT formatted, external sdcard with Apps2SD. If I revert to LOS version 20170802 with LOS kernel everything immediately is okay again. So obviously your Boeffla Kernel anticipated one week earlier the change that was now also made to LOS kernel and is responsible for this problem. That's really enervating to me... :eek:

But we now know: Some of the kernel changes made in LOS is responsible for this issue. You just reflected them sooner than the LOS-team. But that knowledge doesn't help me...
[Galaxy S 5 Original Android Development] andip71:
Aaaaaaaaaaaaaah :)

Sorry you have the pain, but I am now relaxed because I understand probably what happened.

Some of the changes last week made it into my kernel, but obviously not into the official kernel anymore.

Hence the issues.

The good thing on that story is, however: They will for sure revert the things again that break the stuff. Then we have finally a solution.

You can still use beta5 btw... nothing wrong with it. It is just missing the faulty commits + a script improvement I did which is not essential.

Andi
[Galaxy S 5 Original Android Development] fipsy:
I'm not sure anymore. I'm confused more and more every day. Yesterday in the evening I installed the LOS version 20170802 without Boeffla Kernel and everything was fine. But today in the morning I saw that there was a WhatsApp picture that could not be received. But I did *nothing* between yesterday evening and today. Except sleeping. :silly: WhatsApp has also not been updated or anything like that. Then (for testing purposes) I installed LOS 20170802 without Boeffla Kernel on my test phone and it also doesn't work on that phone! Just version 20170726 works on both phones. But I'm sure that 20170802 without Boeffla Kernel was working yesterday evening and on every test I made in the last week. I'm totally confused by now...

Thanks! I will do that. But this cannot be a long term solution...

Volker
[Galaxy S 5 Original Android Development] Trey n:
Regardless of changing cpu governors it has no effect. . .

Any fix? Thx :)
[Galaxy S 5 Original Android Development] andip71:
No, works as it should. No fix required.

Are you using my app (Boeffla-Config) to change the governor?

Andi
[Galaxy S 5 Original Android Development] Trey n:
Yep
[Galaxy S 5 Original Android Development] andip71:
Then pls describe your issue more in detail.

As it works for the rest, we need to understand your problem.

You change the governor, and then "there is no effect". What does that mean?

i.e.

- is the governor resetted again when you close and open the app again?

- anything else...?

Andi