yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Original Android Development] 2phazt:
It IS a well known cm bug (since cm12) and it would be totally great if this could be fixed by the kernel.

The only working workaround atm is to disable wifi when using bluetooth...
[Galaxy S 5 Original Android Development] andip71:
But there is no way to cure rom problems on kernel level.

This is almost impossible.

Andi
[Galaxy S 5 Original Android Development] spaziomilano:
For now i always on stock kernel and always on the Bluetooth in my car... and yes i have try on many other car and always the same problem, on touchwizz i dont have this problem. it's not a rom bug because i have try many rom ( stock cm13, RR, Dirty Unicorn,A.i,cp...)and always this problem.
[Galaxy S 5 Original Android Development] andip71:
Don't understand what you want to tell us finally.

Hm

Andi
[Galaxy S 5 Original Android Development] 2phazt:
All those roms are based on cm and have the same faulty implementation. Only Touchwiz has the original closed source samsung drivers.
[Galaxy S 5 Original Android Development] andip71:
This is the (sad) truth.

Andi
[Galaxy S 5 Original Android Development] spaziomilano:
yes, ok, fine, but no solution!! no idea to fix that? we have the best system, the best rom,the best of the best custom kernel and the best developer, is not possible to fine why, why is only just that again an again...sorry:(:rolleyes: it's because it's almost perfect but always this same problem.
[Galaxy S 5 Original Android Development] andip71:
It it were simple, someone had resolved it already in the past 1,5 years.

And I disagree on: we have the best system - the S5 is outdated meanwhile + Samsung is not known to be supportive to developers. So you cannot expect everything working fully fine on non-Samsung roms.

And the "best developers" left the S5 already a while ago to move to newer and more exciting hardware. Same goes for me honestly, S5 is more or less maintenance only for me too.

This is the sad truth. If you want everything working, go on Samsung Stock TW rom.

Sorry, had to say these honest words

Andi
[Galaxy S 5 Original Android Development] spaziomilano:
I want to cry:(:crying: thank for all
[Galaxy S 5 Original Android Development] JulGer01:
Btw, touchwiz had Bluetooth stuttering too! Not as often as Cyanogenmod, but it has them. So... Not Rom nor kernel related.
[Galaxy S 5 Original Android Development] andip71:
Hi all,

maintenance update again (after many CM code changes last night):

Version 3.0-beta32

13.06.2016

Note: This kernel version works only on official CM13 nightly of 12.06.16 or newer !!

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

Update: Ramdisk of official CM13.0 build of 13.06.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] spaziomilano:
Thanks for your hard work.

Envoyé de mon SM-G900W8 en utilisant Tapatalk

---------- Post added at 10:30 AM ---------- Previous post was at 10:06 AM ----------

someone has put the best settings with this kernel?
[Galaxy S 5 Original Android Development] milanokiara:
Just buy the boeffla app v2 pffffff,please help me,how have the good setting, do you have a detail?
[Galaxy S 5 Original Android Development] andip71:
There is a thread for it.

The S5 is not much used by ne, so I don't have a special settings profile.

Andi
[Galaxy S 5 Original Android Development] 2phazt:
Well, I can understand this changes.

But it would be definitaly painful if you drop the s5 since I updated to it from the s3 because of your kernel.
[Galaxy S 5 Original Android Development] mikey1975:
Respect for your decision.

Regards.

Michael Vermylen
[Galaxy S 5 Original Android Development] TioCareca:
Respect that, combining life/work/development/support can be hard and stressful... Keep your head up as you work as been amazing and we all known time passes and our device is getting old...
[Galaxy S 5 Original Android Development] The_Voice_70:
Hi Andi ;)

Deepest respect for you decision to handle things like that. In last years you made so incredible things possible. With so many devices and your fantastic kernels. And the rules are very simple for all users: use clean CM. Nothing else. And we are very thankful for all the things you have done. Absolutly great forever.
[Galaxy S 5 Original Android Development] f0xy:
I respect your choices! From my personal experiences, balancing life and work alone is very testing!

You have always gone above and beyond with all your kernel/support work.

If people cannot complete certain tasks that come with using a custom kernel, they shouldn't be here.

Keep up the sterling job and for sure, keep it the least priority, which I have no doubt you will x
[Galaxy S 5 Original Android Development] andip71:
CM13 kernel update:

Version 3.0-beta33

16.06.2016

Note: This kernel version works only on official CM13 nightly of 12.06.16 or newer !!

Note: You have to use Boeffla-Config version 2.2.51 or higher in order to use all functionality !!

New: Doze control - in latest Boeffla-Config, you can switch Doze completely on or off (I do not like Doze as it sometimes delays notifications, so I switch it off) at overview page

Change: Kernel initialisation script fixes

Update: Ramdisk of official CM13.0 build of 16.06.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] J0shimi:
If the kernels keep coming I'll be more than happy, good luck finding the best outcome for you andi, your work has and will always be appreciated.
[Galaxy S 5 Original Android Development] KKTHX:
Anyone have and could share beta 30 recovery zip ?

boeffla-kernel-3.0-beta30-CM13.0-g900f.recovery.zip
[Galaxy S 5 Original Android Development] Pjerisimo:
For which phones are they developing now? Which phone are you going to get next, oneplus 3?
[Galaxy S 5 Original Android Development] The_Voice_70:
Everythings fine with beta 33 on latest nightlys. Nothing to investigate;) Great work and a lot of thanks...
[Galaxy S 5 Original Android Development] htb2050:
One pluses, Nexuses, xperia z series. Lg g5
[Galaxy S 5 Original Android Development] andip71:
Oneplus one, OnePlus2, oneplus x.

And I will get a OnePlus 3 today, but not sure if I will develop for it ever.

Andi
[Galaxy S 5 Original Android Development] Pjerisimo:
Why not, time issues or phone has some problems?
[Galaxy S 5 Original Android Development] carabinieri5675:
He made a big announcement in this thread last week. Maybe you should read it instead of asking already answered questions.

Gesendet von meinem ONEPLUS A3003
[Galaxy S 5 Original Android Development] andip71:
I do not even have this phone, so how should I comment on problems that might exist or not.

Read my announcement, then you know more.

Andi
[Galaxy S 5 Original Android Development] KKTHX:
No one have beta 30?

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 5 Original Android Development] andip71:
I put it up for you especially, it is on the download folder.

But why the heck do you want to use such an old version?

Andi
[Galaxy S 5 Original Android Development] KKTHX:
Thank You for UP beta 30 :D

Because it is compatible with cm13 build form 05-06-2016 (last build with working bluetooth) newer version are not compatile as you wrote in changelog.
[Galaxy S 5 Original Android Development] ScratMan38:
Looks like this change https://review.cyanogenmod.org/#/c/150235 has been merged in the 21/06 nightly, and that it requires a kernel update.

It fixes the "Bluetooth Share has stopped" issue when using BT, requiring to reboot the phone.
[Galaxy S 5 Original Android Development] DirkStorck:
It says nothing that this one fixes the bluetooth issue... where did you read that? Thanks!
[Galaxy S 5 Original Android Development] ScratMan38:
Comes from the guy who made the fix :
[Galaxy S 5 Original Android Development] andip71:
All,

maintenance update for the CM13 kernel:

Version 3.0-beta34

21.06.2016

Note: This kernel version works only on official CM13 nightly of 12.06.16 or newer !!

Note: You have to use Boeffla-Config version 2.2.51 or higher in order to use all functionality !!

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

Update: Ramdisk of official CM13.0 build of 21.06.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] JulGer01:
Thats not fixing the Bluetooth issue. It just clouds it. There will be no more Bluetooth sharing crash message. Bluetooth crashes non the less. Btw it starts on 2016.06.06. Builds before that work ok. That's also including the boeffla kernel. As off that date, the Bluetooth problems are there too. Latest kernel version without problem is beta28. Just in my opinion...
[Galaxy S 5 Original Android Development] j1gga84:
All the bluetooth issues and the issue with flashing lockscreen while unlocking the phone has been "introduced" which changing to MM kernel blobs by the CM team.

Maybe next CM13.0 nightly could bring a fix for that flashing:

https://www.cmxlog.com/13/klte/

What do you mean [MENTION=947981]Lord Boeffla[/MENTION]

Some kernel related changes but I don't know what they could be for.

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Hi, what makes you believe, the screen flashing is fixed by these commits? To me it does not look like it. Or did I overlook something?

The kernel related changes are not spectacular, just the usual "hardening" of bugs. But nothing you would notice...

Andi
[Galaxy S 5 Original Android Development] rec0re:
Hi, i would like to try install the cm13 boeffla kernel on my phone, is the kernel working on aicp 11 for klte??? My installed aicp is the latest nightly from 22.6.2016, please help me, thxxx?!
[Galaxy S 5 Original Android Development] carabinieri5675:
Lord Boeffla told everyone many times, that he is only supporting official CM. If you have a different ROM, you have to test by yourself. This thread is only for official CM support and if you can't read the first post, don't flash. It is always recommended to read the first post.

Gesendet von meinem ONEPLUS A3003 mit Tapatalk
[Galaxy S 5 Original Android Development] rec0re:
I don't need support, i need a tip for a running kernel, after that i flashed all standart boeffla kernel from v.28 to v.34 and nothing is running and phone stuck in bootloop! I hope thats not to much for you?
[Galaxy S 5 Original Android Development] carabinieri5675:
You don't read again. You cannot expect really a Tip for another kernel in Lord Boefflas Kernel thread. Sorry, no more words needed. Otherwise the mod will delete everything.

Gesendet von meinem ONEPLUS A3003
[Galaxy S 5 Original Android Development] fbs:
testing zzmoove governor can simply crash the phone and corrupt the filesystem to the point of needing a wipe data.

three things are incredible:

1. how a governor (which is there a couple of YEARS) can crash everything up

2. how a kernel crash can corrupt the file system this hard

3. how a simple file that didn't get written or something makes android bootloops forever
[Galaxy S 5 Original Android Development] andip71:
Two comments:

A) this is very rare, only had it once myself

B) it is also specific to f***** Samsung Galaxy s5. Never had it on my oneplus devices, although it is the same zzmoove code. Samsung again doing something special, and one of many reasons I am not taking on Samsung devices anymore forever.

Andi
[Galaxy S 5 Original Android Development] magic288:
Hey,

When i Install Boeffla Kernel on newest Nightlies my Kamera Start with FC. With Stock cm Kernel not. Why?
[Galaxy S 5 Original Android Development] ZaneZam:
I'm hunting this "bug" since ages and yes as Lord said zzmoove (with same code! ) runs on many devices stable for months now only here on the s5 it tend to crash (but indirectly not zzmoove itself!!) and well if a kernel crashes or a part of it then everything can happen. What this is in particular is pure coincidence. Only thing I know zzmoove randomly provokes the crash somehow but we (me and more important some brave and patient testers, as I don't have a s5) didn't find any cure yet. Only thing what might help is dealing with voltages on upper frequencies. I think some of u even got it stable running with that method (wink to [MENTION=5163281]THE_[/MENTION]voice_70 [emoji6] *g*) but that might again be a device specific thing, I don't know.

And yes that's frustrating and might get on samsungs account, I'm also done with that brand but not only because of that there are many reasons for devs to do their things on other much more nerv saving devices [emoji4]
[Galaxy S 5 Original Android Development] andip71:
Because CM team rolled back more than 12.000 lines of code.

Or in short: Boeffla-Kernel needs an update.

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

update to CM13 Boeffla Kernel to reflect the huge code rollback CM team did (and which broke camera etc.).

Version 3.0-beta35

26.06.2016

Note: This kernel version works only on official CM13 nightly of

25.06.16

or newer !!

Note: You have to use Boeffla-Config version 2.2.51 or higher in order to use all functionality !!

Change: Sync of high resolution scheduler implementation with CM13 source tree

Update: Updated with latest official CM kernel commits as of 26.06.16, 8am CET (incl. big rollback of MM sources - same as official CM tree)

Update: Ramdisk of official CM13.0 build of 26.06.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] rommy667:
Wow thanks for the super fast update man :)
[Galaxy S 5 Original Android Development] venereo:
Sorry Andy, it's not for you! Anyone experiencing problems with Xpo*** on latest update?
[Galaxy S 5 Original Android Development] andip71:
So why do ask this here then?

Isn't that a question for a xpo*** thread instead?

Andi
[Galaxy S 5 Original Android Development] venereo:
This is the group of people with bigger probability of having same setup as me, sorry! Full wipe solved the issue!
[Galaxy S 5 Original Android Development] afr33sl4ve:
I'm really tempted to flash this kernel, after reading that it's compatible with the G900T. I came here because my bluetooth is lagging considerably, even with AudioFX/V4A disabled/removed. It seems to be an AOSP memory management issue. Will this kernel help? I came from the Cyanogenmod forums about this exact issue, and linked here.

Granted that it works on the G900T. Can I dirty flash over CM12.1? I'd really hate to set everything up again.

Thanks!
[Galaxy S 5 Original Android Development] andip71:
Bluetooth for the s5 is also quite ****ty on cm.

I would not bet anything gets better in that aspect by my kernel.

Andi
[Galaxy S 5 Original Android Development] The_Voice_70:
beta35 checked on nightlys ... all quiet and clear. I hope the guys don`t change anything in kernel ;) Rollback was really good. Never change a running system. I don`t use bluetooth and I know exactly why. Great work again by Andi on this crazy machine which make my hairs more grey in last time ;)
[Galaxy S 5 Original Android Development] HAJT669:
With the beta35 the camera force close!? Fix please, and thank you, your work is the best
[Galaxy S 5 Original Android Development] JulGer01:
How come you think it's the kernel?

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] HAJT669:
Because with the beta34 it doesn't happend
[Galaxy S 5 Original Android Development] j1gga84:
Which ROM are you using and which build?

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
Read change log. Then it should be clear...

Andi
[Galaxy S 5 Original Android Development] afr33sl4ve:
Turns out that, in my case, the bluetooth is fighting with the wifi. Turning off the wireless seems to have solved my bluetooth issues.

I'll still flash this kernel when I get home from work.
[Galaxy S 5 Original Android Development] andip71:
Guys,

I might be searching for 2-3

EXPERIENCED

testers soon, that are on a CM13 based custom rom like RR (where my kernel is working, but having issues like dalvik cache wipe does not work etc.).

Would like to test a new kernel/app combo to see how that works for them...

And before you ask: Yes, I am currently testing to change the whole Boeffla foundation and be a) even closer to stock, without loosing functionality and b) supporting anykernel2 concept (point b required a).

This should significantly improve compatibility with custom roms (although I will still give no support for it)

Isn't that exciting news?

So - stay tuned.

Thanks

Andi
[Galaxy S 5 Original Android Development] yousuf.shareef:
Latest kernel is compatible with which nightly?? The older version I can see is for 28th
[Galaxy S 5 Original Android Development] JulGer01:
Try it. If not working restore...

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] HAJT669:
When going to have the new update!?
[Galaxy S 5 Original Android Development] j1gga84:
Don't ask for ETAs, it's against xda rules!

New kernel will be released when there is a need for it.

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] andip71:
When I released it [emoji3]
[Galaxy S 5 Original Android Development] andip71:
Hi all,

new things are coming up soon, I will change the complete concept of Boeffla-Kernel during start phase very soon (yes, I will move on to anykernel method).

Hence, I release my kernel now as last stable releases following still the old concept (static ramdisk method).

CM13.0 -- Version 3.0 stable

04.07.2016

Note: This is the last version of this Boeffla-Kernel which comes with a static ramfisk.

New kernel versions will work with a completely new concept (anykernel method).

Note: This kernel version works only on official CM13 nightly of 25.06.16 or newer !!

Note: You have to use Boeffla-Config version 2.2.51 or higher in order to use all functionality !!

Fix: Swappiness sliders in Boeffla-Config working again

Change: Change sponsoring information from hubo.in to android-hubo.de

Update: Ramdisk of official CM13.0 build of 04.07.16

Enjoy

Andi
[Galaxy S 5 Original Android Development] Antydoto:
Download link ? Redirect to 2016.06.26 version.
[Galaxy S 5 Original Android Development] j1gga84:
www.boeffla-kernel.de

regards
[Galaxy S 5 Original Android Development] andip71:
www.boeffla-kernel.de

Where did you see a redirect ??

Andi
[Galaxy S 5 Original Android Development] andip71:
Not happy to see direct URLs here, as I might any time change them completely and then they are broken again.

The only valid entry is www.boeffla-kernel.de

Andi
[Galaxy S 5 Original Android Development] j1gga84:
I edited my post, no problem, thanks for the hint and thanks for the update, running as expected :) :good:

regards
[Galaxy S 5 Original Android Development] arrigo13:
Andi, you had me scared! LOL this is good news. Thank you for the hard work!

Sent from my klte
[Galaxy S 5 Original Android Development] fbs:
oh my god we'll have a new version with absolutely NO new features and tweaks!!!
[Galaxy S 5 Original Android Development] htb2050:
Seriously? Why don't you do it your self then?
[Galaxy S 5 Original Android Development] andip71:
Is it?

You know more than me even?

Scary [emoji23]
[Galaxy S 5 Original Android Development] venereo:
Congrats on now web site and for taking care of the future for us. Some changes in the update rom flow but no big deal.

Will flashing take much longer with anykernel?

Thanks for your time!

V
[Galaxy S 5 Original Android Development] andip71:
No. It will be a matter of seconds as before. You will not notice a difference. Flashing the anykernel takes, hm... maybe 5 seconds approx? So, no big deal.

Andi
[Galaxy S 5 Original Android Development] airidosas252:
Thanks for your wonderful kernel. So far, with latest CM13 installed, it's running wonderfully.

From what I gathered, slim cpu governor gave the most reliable results, both in battery and performance.

By the way, don't you plan implementing GPU voltage control? I really like such features and those are real handy.

With tons of flashing and stressing I got over 4h of SOT, which is pretty good. :)
[Galaxy S 5 Original Android Development] andip71:
No plans for GPU voltage control as nobody succeeded to put that into a msm8974 device ever.

I also tried it for two days just to find out the voltages seem to be locked completely.

Also, if I could, I would remove all undervolting (also CPU) from my kernels.

Undervolting does not help for anything but just adds instability in worst case. So it is kinda useless stuff which I personally stopped using already for more than 2 years completely.

Andi
[Galaxy S 5 Original Android Development] airidosas252:
Yeah, I've noticed that, too. I had a bad experience with UV throughout all of my devices, which I developed on.

Even slight undervolt results in stuttery UI and 3D stuff lags badly. Even so, from what I've seen, klte already runs on very low voltages compared to other SD801 devices.
[Galaxy S 5 Original Android Development] Kadajo:
Undervolt help with cpu Temps, device is definitely colder with Undervolt.
[Galaxy S 5 Original Android Development] andip71:
And why should I have a cold device?

It does not live longer, not consume more battery, is not faster or slower...

I am not sacrificing on stability just for having a colder device.

The devices are built to take the heat the sometimes develop without issues.

Andi
[Galaxy S 5 Original Android Development] j1gga84:
When I flash ROMs, when apps are optimised at first start up, when transferring bug data to external SD and so on the device gets pretty warm but I never had any problems with dying batteries or devices so not a problem at all.

A device that costs some 100 bucks should manage the heat ;)

Regards

Gesendet von meinem SM-G900F mit Tapatalk
[Galaxy S 5 Original Android Development] ScratMan38:
Will the anykernel method allow setting SELinux to "permissive" at boot ? Because my camera still doesn't work with SELinux set on "enforce" :(

So I absolutely need SELinux to remain in permissive mode in order to be able to use the camera.
[Galaxy S 5 Original Android Development] andip71:
Yup.

The SoCs are usually specified for quite high temperatures.

I do not remember from top of my head, but the driver code shutting down a msm8974 SoC completely was showing temperatures above 80-90 C for it to happen.

So there is enough buffer.

Andi
[Galaxy S 5 Original Android Development] Kadajo:
I just think it's good to have that option. It's one of many that I like in your kernel. Of corse not the cost of stability so undervolting is lottery. For my s5 I have heavy undervolt settings with lionheart and no issue at all.
[Galaxy S 5 Original Android Development] andip71:
Lucky one. But remember - when you have crashes, lose data etc., do not complain. You are fully out of support with undervolting.

And GPU undervolting will never come for mentioned reasons, technically not possible as it seems.

Andi
[Galaxy S 5 Original Android Development] carabinieri5675:
There are a few existing devices having no problem with this. But the main users having problems. S5 is a diva and you know this. Because of this the Lord decided to skip this part of the kernel. My opinion, his decision is better for everyone.

Gesendet von meinem ONEPLUS A3003
[Galaxy S 5 Original Android Development] kris_l:
Hi, i'm using slim 6.01 alpha 0.4.

I've repacked kernel but after that boeffla-config doesn't recognize kernel. I'd like to switch off button lights but there is no option for that in kernel adiutor. Can i disable lights using adb?

adb settings put system button_key_light 0 - doesn't work.

I'm waiting for anykernel version of boeffla kernel but maybe in the meantime could i disable button lights somehow ?

best regards
[Galaxy S 5 Original Android Development] andip71:
You need much more than repackaging the kernel with a new ramdisk.

It is not that simple.

Wait for the anykernel version, it is not far away.

Andi
[Galaxy S 5 Original Android Development] airidosas252:
One bug or really not - when running on stock kernel settings, Asphalt 8 lags crazily. I tried messing around with settings and the only solution was to put governor to performance, then lag has vanished considerably. That's with your kernel.

When completely stock CM13 is being run, no such problems.