yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] BonnyBedlamBoy:
boeffla-kernel-3.0-beta22-CM13.0 is the one for me that works without issues regarding the only game that i am playing (trials Frontier). builds before and after are causing random stuttering within the game.

Gesendet von meinem Nokia 5110
[Galaxy S 5 Original Android Development] benjamen50:
Live display and Ambient Display are two completely different things and are unrelated right?
[Galaxy S 5 Original Android Development] andip71:
Then this is your golden version :)

Yes, of course. I do not use any of them, so I could have mixed it up.

Andi
[Galaxy S 5 Original Android Development] jose13683:
I use livedisplay in night mode in the before-going-to-bed surfing on internet. But the random reboots seem unrelated, I have them also with livedisplay disabled.

What kind of logs can I provide to help track the issue? A logcat after the random reboot? Or the last_kmsg? I am pretty newbye with logs...
[Galaxy S 5 Original Android Development] andip71:
Usually last_kmsg or better debug info file created by Boeffla Config.

But on the S5, usually the logs are quite useless. So I would not expect a lot.

I would rather do a clean install first. I have no reboots myself, also my German reference users reported nothing.

Andi
[Galaxy S 5 Original Android Development] yetep:
Hey Folks, Currently using this kernel and it's amazing. Has drastically changed my experience with my phone.

Quick question though - is there a way to change/modify the values within this kernel for the Automatic gain control of the mic? Nobody can hear me very well using any app that records video.
[Galaxy S 5 Original Android Development] andip71:
No, this is not possible.

We are not having any documentation about the audio hub used, and we will not get any.

So far nobody managed to control that from kernel side on the S5 unfortunately.

The only solution is apparently: Going back to Samsung Stock roms again, there it seems to be working out of the box.

Andi
[Galaxy S 5 Original Android Development] yetep:
You my friend are the best dev support I have came across.

Thank you. I'll try the switch. Does your TW rom kernel allow it?
[Galaxy S 5 Original Android Development] andip71:
No, it is not a question of software, it is a hardware piece that we cannot better control. So this is not dependent of TW or CM, the function cannot be implemented at all.

Details can be found in the FAQ section of my homepage if you are interested.

But it seems (I heard from many others, I personally dont use the S5 for calling ever) on Samsung Stock the microphone works better out of the box. So no need to control it further.

Andi
[Galaxy S 5 Original Android Development] AkiroX:
So. I've got this little gremlin that keeps bothering me.

The touchscreen stops responding after a little while?

Yes, I've got an undervolt and an underclock. But do they have to do anythin' with it?

My phone isn't frozen, like if I hold the power button it still shows the reboot menu, etcetc. Just I can't touch anything.

Usually happens after a little while of idling with the screen OFF.

Any ideas?

Otherwise this kernel is godlike. Ripped off about 120mv from the CPU, PegasusQ with the balanced core scheduler and 1.9GHz and I can live a day with 6+ hours screen on.

It's unreal to say the least.
[Galaxy S 5 Original Android Development] andip71:
I would at least disable your undervolting for some time to give it a comparative test for some days.

I am pretty sure, battery life will not significantly change. But stability should.

Not more I can say, my touch screen never stopped working so far, luckily.

Andi
[Galaxy S 5 Original Android Development] cmdmilitia13:
I'm running resurrection remix 4/23 & this kernel.. Flashed everything 2 days ago.. 1st day with it,I was getting alot of random reboots.. Tried governers in this order: ondemand(reboots),intellidemand(reboots),intelliactive(reboots) all reboots happened randomly while surfing the web.. So I tried yankactive around 830pm.. It's now 544pm(Eastern time) & haven't had a single reboot or hiccup as of yet.. Battery life has been good.. 5hrs+ screen on time,cnt complain.. Anyone hsving random reboots resurrection can try yankactive or maybe it just my device...This my 1st Samsung device & my last.. I'm coming from a Nexus 5(always been a Nexus fan) which apparently T-Mobile has no more of so they sent this has a replacement.. This kernel & resurrection remix rom makes me feel much better bout this POS lol no offense to anyone who loves Samsung..
[Galaxy S 5 Original Android Development] !crazy:
Many governors have issues on S5 and CM/AOSP, but interactive, which is default anyway, works rock stable, is fast, tunable etc. and won't cause you any issues (that I'm aware of.).

If you care about stability, use interactive.

---------- Post added at 05:01 PM ---------- Previous post was at 04:51 PM ----------

Do you have any of screen wakeup options (dt2w or s2w) enabled?
[Galaxy S 5 Original Android Development] andip71:
Hi guys,

CM13 kernel maintenance update for you:

Version 3.0-beta26

02.06.2016

Update: Ramdisk of official CM13.0 build of 02.05.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] The_Voice_70:
"Boeffla`s finest" with todays nightly and beta26;) Thanks for everything, Andi. And: relax "in the sun";)
[Galaxy S 5 Original Android Development] jujjk:
Init.d support doesn't seem to be working, or maybe it's very unreliable. The logs tell me it's executing the scripts, but nothing is being run. Running BK 3.0-beta26 and latest CM13 nightly 13.0-20160502-NIGHTLY-klte. I've checked all the scripts and they have all the correct permissions. Logs aren't telling me much at all. So at the moment I have to emulate init.d support through Kernel Auditor.
[Galaxy S 5 Original Android Development] andip71:
How did you try to run init.d scripts?

Usually on cm the kernel should not run it as the rom runs it.

Where did you see the scripts in which log?

And what makes you believe they do not run correctly?

Andi
[Galaxy S 5 Original Android Development] jujjk:
I checked boeffla-kernel.log for any error/warning messages, and it's telling me the scripts were executed. I tried running the script straight from the terminal, and it executes fine when I run it manually. It seems like init.d support is completely broken in CM13 from my trial and error and according to this and this. What is even weirder is even if I force init.d script handling within BK, it isn't working. I guess your kernel is doing its job, but CM13 isn't. The reason I know it isn't working is because the script and its associated binary is supposed to open a loopback proxy, and it isn't if I try running it through init.d.
[Galaxy S 5 Original Android Development] j1gga84:
[MENTION=947981]Lord Boeffla[/MENTION]

When I use boeffla kernel I have an error in logcat (attached screenshot), sometimes more, sometimes less, this error is not present with stock kernel I guess.

Concerning this issue, thejester123 gave me a tip how to remove this error:

http://xdaforums.com/showpost.php?p=66591916&postcount=2243

I asked him how to enter these commands in terminal emulator but no answer until now..

Maybe you can help me or maybe you know why this error occurs with boeffla kernel.

I know, it is posted in ResurrectionRemix ROM thread but I have this error with every CM13.0 based ROM, also on CM13.0 stock.

EDIT:

what do you think of that patch, that it included in stock CM kernel but not in boeffla:

http://review.cyanogenmod.org/#/c/133943/ ?

thanks & regards
[Galaxy S 5 Original Android Development] andip71:
The "tip" in the first post is not recommended. By this you remove mpdecision completely = you have no hotplugging anymore. This is certainly not what you want.

The patch you refer to is not merged, so it is also not included in CM.

Second, it is not a kernel patch but a patch concerning the ramdisk.

As I always take latest ramdisks it will be included automatically when it gets merged into CM.

However - nothing will happen the next 3.5 weeks. I am leaving pretty much tomorrow to my annual holidays.

So there will be no updated for the next weeks by me anyways.

BTW - what is the fuzz about this logspam? Best is you disable kernel logger and then your log is more than clean :)

Andi
[Galaxy S 5 Original Android Development] 2phazt:
Have a nice trip, Andi ?
[Galaxy S 5 Original Android Development] andip71:
Thanks my friend.

I might post a picture of lovely Florida at some time.

People following me on Twitter or Facebook anyways are "in the loop" :)

Andi
[Galaxy S 5 Original Android Development] DirkStorck:
Have a nice vacation Andi... I think we can survive some weeks. Everything is running stable :)

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] j1gga84:
[MENTION=947981]Lord Boeffla[/MENTION]

The strange thing is, that this error doey not occur when using stock kernel!?

And concerning kernel logger, I have disabled it in Boeffla config, hmm..!?

Wish you also a nice vacation :)

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Ok, think you have that in logcat, not kernel log.

Then yes, then you cannot switch it off.

Well, I cannot say where it comes from. Stock kernel is compiled with the rom, not standalone like a custom kernel. That is most likely the difference.

But as the rom (logcat is a rom log) encounters this thingy, a rom dev can probably find where it gets triggered in the code.

And then we know if there is a solution to it.

At least I am not aware this is causing any issues...

Andi
[Galaxy S 5 Original Android Development] andip71:
Btw, threads are full on powerhal problems.

If you want to test something, try to allow the rom overwriting kernel settings in Boeffla Config settings.

Because my kernel puts limits in for mpdecision, maybe that is why it complains...

Just an idea.

Andi
[Galaxy S 5 Original Android Development] j1gga84:
What kernel settings do you mean?

The ones in attached screeshot?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Yes, these are the ones that restrict mpdecision in my kernel.

Of course I do not recommend to allow the overwrites, as then mpdecision can and will mess up your profile.

But you can try if you want.

Andi
[Galaxy S 5 Original Android Development] andip71:
Hi all,

last maintenance update before I will disappear for 3 weeks for holidays:

Version 3.0-beta27

05.05.2016

Update: Updated with latest official CM kernel commits as of 05.05.16, 8am CET

Update: Ramdisk of official CM13.0 build of 05.05.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] DirkStorck:
Have a save trip and a nice time. ?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] finotti:
last_kmsg

(I know the developer won't be able to reply, but maybe someone else can.)

I've had a couple of reboots followed by bootloops (until I removed the battery and restarted) on Temasek CM13 ROM (2016-04-28) and Boeffla beta25. (The phone is T-Mobile 900T.) I went looking for last_kmsg to see if I could see what is causing (or, more likely, post here and see if someone could spot the problem), but after reboot there was no such file in /proc/. Do I need to enable any configuration for these files to be created?

Thanks in advance!
[Galaxy S 5 Original Android Development] andip71:
Samsung removed last_kmsg with Android 5 completely (stupid Samsung, as always).

I brought it back, however maybe it is not always working as it should (in your case).

Andi
[Galaxy S 5 Original Android Development] jinkerz9430:
Has anyone tried the double tap to wake ? i have tried it with 3 different roms and it doesnt work in any of them. But,,,, yet this kernel still so goood! hahahah
[Galaxy S 5 Original Android Development] carabinieri5675:
It works for me. No problems with dttw.

Gesendet von meinem Siemens S 4
[Galaxy S 5 Original Android Development] andip71:
It works just fine.

I only use official cm nightlies though...

Andi
[Galaxy S 5 Original Android Development] jinkerz9430:
Hmm. I dont know why it isnt working for me. Im even using the boeffla config v2 app. And i uninstalled the auditor one i installed before that one. At first i was using conservative mode but then i decided to try with the default mode and performance mode, but not even with them it worked. Im currently using AICP rom and my device is the G900t
[Galaxy S 5 Original Android Development] carabinieri5675:
Lord boeffla give you only the guarantee, that this kernel works perfect with official CM. With other ROM's it could happen, that something is not working. But if everything else is working, maybe you have to make a clean install.

Gesendet von meinem Siemens S 4
[Galaxy S 5 Original Android Development] jinkerz9430:
I did a clean install of the rom. Then i installed the script cleaner one and then i installed the latest beta. But i did it with the previous beta too and nothing
[Galaxy S 5 Original Android Development] 2phazt:
Kernel is for g900f.
[Galaxy S 5 Original Android Development] jinkerz9430:
well. I guess that's the only feature doesnt work for g900t. The other ones work just fine.
[Galaxy S 5 Original Android Development] J0shimi:
Does this kernel with Mokee Rom?
[Galaxy S 5 Original Android Development] FlemishDroid:
You can try and if it doesn't work reflash Mokee rom. Lord Boeffla only supports official CM rom.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Galaxy S 5 Original Android Development] bilbonotry:
Somebody made a version of Boeffla kernel for mokee in mokee thread.
[Galaxy S 5 Original Android Development] zrockcool:
guys, anyone here experiencing flickering green light on half screen of the device when its about to turn off its screen?

My device is sm-g900f installed with latest cm13 nightlies and boeffla kernel. Everything is in default.

Appreciate for replies. Tnx!
[Galaxy S 5 Original Android Development] 2phazt:
No. It's either something you configured wrong or a hardware issue. Kernel is working fine here.
[Galaxy S 5 Original Android Development] JulGer01:
Think thats a known problem with many g900f. I also have that. It only appears when the screen is on for a longer time and disappears if it is off for some time.

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] zrockcool:
did already a factory reset and clean install still has the issue. set my phone sleep to 30 seconds. lets say the screen is on, no flickering, until the moment it will go to sleep thats the time the screen goes dim but half only, the other half has this flickering green light and then thats the time the screen goes to sleep.

---------- Post added at 04:56 PM ---------- Previous post was at 04:52 PM ----------

when the screen is on the screen is fine no flickering at all. it just happen when the phone is about to sleep. isnt that wierd? it just start to happen when i update my cm13 nightlies recently.
[Galaxy S 5 Original Android Development] Mar-cel:
If I in the Boeffla-kernel app, hotplug profile: zzmove native 2 cores max activate.

Than are 4 Cores active and not only 2 cores is this a bug?

Or have I misunderstood something?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] TioCareca:
Some governors and hotplug configurations not working as they should, as they are a bug or a conflit within the rom i cannot tell...
[Galaxy S 5 Original Android Development] 2phazt:
Maybe some hotplug settings only work with the corresponding governor.
[Galaxy S 5 Original Android Development] TioCareca:
Maybe...
[Galaxy S 5 Original Android Development] ZaneZam:
yes in fact there are two modes "native hotplugging" ONLY works with zzmoove the others with the other governos. and keep in mind when monitoring

core switching that with zzmoove hotplugging cores first have to come down before the desired hotplug profile works correctly. so if u change to for example

2 core profile 2 cores first have to come down then they should stay off of course. just to refresh how that actually works. and just theoretically spreaking as i cant

really say if any bugs a running around on the S5 :)
[Galaxy S 5 Original Android Development] andip71:
The zzmoove native hotplugging only works when zzmoove is used as governor.

Andi
[Galaxy S 5 Original Android Development] venereo:
Used to happen when I had double tap to wake up selected and seems to be a problem with proximity sensor. No undervolt here
[Galaxy S 5 Original Android Development] fbs:
Since I understand myself as a android user, all my phones get laggy as hell when downloading in high speed or installing any big app. Who to blame? Kernel or rom?

---------- Post added at 01:19 PM ---------- Previous post was at 01:18 PM ----------

It seems the system is dumb enough to not give high priority to itself, the launcher, the surfaceflinger, whatever....
[Galaxy S 5 Original Android Development] andip71:
The whole Android eco system contributes to that.

Drivers, io, java etc.

Andi
[Galaxy S 5 Original Android Development] tharik816:
Who kltedv users ..edit script n falsh its work
[Galaxy S 5 Original Android Development] j1gga84:
I use latest boeffla on my device but when I try to copy the whatsapp folder to my external SD (around 400MB) the transmission is very, very slow :confused:

What can I do here? I have a 64GB Samsung MicroSD..

regards
[Galaxy S 5 Original Android Development] andip71:
Is it different with stock cm kernel?

Maybe you need to play with the readahead buffer, although in theory I doubt that.

Andi
[Galaxy S 5 Original Android Development] Simone:
Hi, Lord Boeffla! Are you back developing?
[Galaxy S 5 Original Android Development] TioCareca:
He is still in vacations...
[Galaxy S 5 Original Android Development] andip71:
Not yet. In 1,5 weeks.

Andi
[Galaxy S 5 Original Android Development] SMAIE:
hey Guys,

Very quick question. I have CM13 installed about to flash boeffla-kernel.

I have

boeffla-kernel 3.0-beta27-CM13.0-g900f - change log says Update: Updated with latest official CM kernel commits as of 05.05.16

Im running CM13 18.04.2016 - month old nightly

Can i flash the latest boeffla-kernel 3.0-beta27 to my running CM13?

Or would i need to update my CM13 to 05.05.16 build then flash boeffla-kernel 3.0-beta27?

cheers
[Galaxy S 5 Original Android Development] andip71:
You should be fine to flash it.

User report it still to run fine with latest nightlies.

Usually I update the kernel at least once a week, but I am on holidays still. So it will take some more time, first I have to come back in 1,5 weeks.

Andi
[Galaxy S 5 Original Android Development] SMAIE:
Thank you Working Great! Loving this Kernel. Managed to calibrate my screen to much more neutral accurate colours.

I couldnt find the MDNIE setting to turn off screen sharpening, is there plans to add this in at later date?
[Galaxy S 5 Original Android Development] andip71:
The sharpening thingy is only available on s3 mdnie driver.

Andi
[Galaxy S 5 Original Android Development] The_Voice_70:
Guys ... be cool ;) Nightlys running fine with beta27. Everythings fine;) Be relaxed ;)))
[Galaxy S 5 Original Android Development] Jatinder Tiwana:
guys I just installed android 6.0 now whenever I fur try to install SuperSU binary my phone gets stuck at boot. Any help?
[Galaxy S 5 Original Android Development] TioCareca:
did you flash supersu or install it from store?
[Galaxy S 5 Original Android Development] ScratMan38:
[MENTION=947981]Lord Boeffla[/MENTION] : Does this : https://review.cyanogenmod.org/#/c/146515 require kernel update ?
[Galaxy S 5 Original Android Development] andip71:
Well, how I understand it is:

This changes makes CM boot also on MM boot loaders.

As long as you are not on a MM boot loader, all is good.

But I will for sure merge this in asap when I am fully back.

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
Official MM Touchwiz is available in France (XEF) for the G900F, and I wanted to install it and then return to CM (while keeping MM bootloader and modem).

So I'll have to wait for your kernel to be updated, as stock kernel doesn't support the features I need.
[Galaxy S 5 Original Android Development] SMAIE:
Really loving this Kernel very stable on CM13.

Just wanted to ask has anyone tired this Kernel on Resurrection Remix Rom/ or can you? is it stable on RR?

cheers
[Galaxy S 5 Original Android Development] j1gga84:
Why don't you ask this question in RR Thread [MENTION=7414576]SMAIE[/MENTION] ;)

regards
[Galaxy S 5 Original Android Development] TioCareca:
http://xdaforums.com/galaxy-s5/unified-development/kernels-ukp-cm13-aosp-m-unofficial-t3373737
[Galaxy S 5 Original Android Development] steveokinevo:
This is working good so far with the latest bliss rom. Thx!
[Galaxy S 5 Original Android Development] HichemTn:
****************
[Galaxy S 5 Original Android Development] Blooperto:
You downloaded the wrong kernel. That one is for bacon as it shows in the screenshot. Download the right one for klte(g900m/f)

Enviado desde mi SM-G900M mediante Tapatalk
[Galaxy S 5 Original Android Development] Jatinder Tiwana:
Installed from playstore
[Galaxy S 5 Original Android Development] TioCareca:
Strange, mine works, instaling binaries normal way via supersu app...
[Galaxy S 5 Original Android Development] benjamen50:
Haha, I did that before when I tried to install this kernel for the first time. :good:
[Galaxy S 5 Original Android Development] andip71:
Hi all,

I am not yet fully back from my holidays, nevertheless a quick maintenance update already for you:

Version 3.0-beta28

26.05.2016

Change: VNSwap has been removed by CM, now zRam of ~423 MB size is used by default -

if you do not like that, you can switch it off in Boeffla-Config in "Settings -> Kernel startup actions -> Disable default zRam" (reboot required)

Note: You cannot configure zRam size anymore, only switch the 423 MB on or off (I might change this in future, but have no immediate plans for it)

Update: Updated with latest official CM kernel commits as of 26.05.16, 8am CET

Update: Ramdisk of official CM13.0 build of 26.05.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] ScratMan38:
Deleted
[Galaxy S 5 Original Android Development] TioCareca:
You ever tough about using anykernel2 for not needing to update ramdisk so often?
[Galaxy S 5 Original Android Development] andip71:
Yee, and answered already many times in all different threads all over.

I don't like anykernel. And I am honest enough to say - I don't care about roms not compatible to official cm. Sorry.

Andi
[Galaxy S 5 Original Android Development] SMAIE:
Thanks Lord Boeffla, whats the correct way to update this kernel? im running Version 3.0-beta27 already, shall download and flash over in twrp?

cheers
[Galaxy S 5 Original Android Development] TioCareca:
Thank you anyway...
[Galaxy S 5 Original Android Development] andip71:
Simplest is to use the action menu in Boeffla Config app. Then all goes completely automagically.

But you can also just download and flash in recovery, as you wrote already.

Andi
[Galaxy S 5 Original Android Development] venereo:
Flash supersu 2.65 from recovery and everything should be fine

Note: you have to repeat that on every kernel update.
[Galaxy S 5 Original Android Development] fbs:
Mic volume for recording anything, like WhatsApp voice message is too low. Kernel or rom fault?
[Galaxy S 5 Original Android Development] andip71:
Known issue with CM. On Samsung stock all is fine.

I suspect rom issue, as drivers are the same. I diffes them long ago.

But nobody knows for sure.

Andi
[Galaxy S 5 Original Android Development] j1gga84:
[MENTION=516058]fbs[/MENTION]

Concerning low microphone levels check out this thread:

http://xdaforums.com/showthread.php?t=3190613

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] venereo:
Flash current rom with own kernel and you have your answer