[EOL][KERNEL] [OnePlus2] [Lineage14/CM13] Boeffla-Kernel (27-03-2018)

[Jongla]

Hi man, i find this problem in my phone too.

I believe it is something related to camera. Look

https://youtu.be/Rn385LpaudU

what's that app you are using to monitor cores?

Sent from my ONE A2001 using XDA-Developers mobile app

 

[Stephen]

Moderator Information,

Off topic post has been cleaned. Please keep posts on topic regarding this kernel and device only.

 

[Riichard63]

Hello there, I made a try regarding camera and big core going offline.
Yes they goes offline but they eventually come online when needed,so it looks like it's not really an issue.

BTW I support this work as this kernel is really good and the dev is really motivated so guys please stay on topic or @Lord Boeffla might definitely close this topic and stop maintaining CM kernel...

 

[lexxx84]

Hello there, I made a try regarding camera and big core going offline.
Yes they goes offline but they eventually come online when needed,so it looks like it's not really an issue.

BTW I support this work as this kernel is really good and the dev is really motivated so guys please stay on topic or @Lord Boeffla might definitely close this topic and stop maintaining CM kernel...

Hi actually some of us would prefer the thread to be closed.. it's just full of people who have no respect for the forum rules and keep making nonsense posts which we have to read all the time, unfortunately. Closure of the thread does not mean that Lord Boeffla will stop developing for OP2, it's just that those inconsiderate users will suffer from their lack of respect and inability to find out information on their own instead of being spoonfed all the time. The smart and respectful ones will know how to troubleshoot by themselves and send logs if required. I for one would much prefer it this way.

 

[andip71]

Hi man, i find this problem in my phone too.

I believe it is something related to camera. Look

https://youtu.be/Rn385LpaudU

Thanks. Oh yes, I have a handle on that now.

It is - indeed - something that changed with the switch from core_ctl to hcube hotplug control.

The good thing is - I think I can work around that. Expect this to be in the next update.

Just in case you do not wanna wait, put your hotplugging settings from min=2, max=4 to min=1, max=4, and you will not face that anymore already.

Hello @Lord Boeffla,

I noticed that there is no French translation for your kernel management app, if you want to send me the strings I would be glad to do it for you when I have some time

BTW I noticed lot of in game lags with your kernel on CM nightly. I tried some gaming profile but lags still there.,eve' with stock profile and performance governor for GPU. Any clue?

Regards.

Edit : I wonder why not any kernel offers the possibility to totally disable little Cpu.

Edit 2 : I also noticed that small core never goes down to their lower frequency when screen is on, on my old Mi4 all cores were able to go back to 300 MHz when my screen was on and I wasn't touching the screen. Is that normal?

Regarding translations: Contact me on [email protected] and I can send you the string list to translate (but might take a few more days as I am currently in the biggest rework of the app for a long time).

what's that app you are using to monitor cores?

Sent from my ONE A2001 using XDA-Developers mobile app

Chainfires Perfmon.

Andi

 

[andip71]

Moderator Information,

Off topic post has been cleaned. Please keep posts on topic regarding this kernel and device only.

Guys,

I opened up the thread on Friday and already 2 and a half days later we have the same mess again.

Nobody learned from it? It seems, OP2 folks are quite "noobish" and "unexperienced" (I had a different word in mind, but would then be a victim of a mod edit too) people.

So thanks for making my life easier by again closing the thread for some time. At least a week, maybe longer.

And sorry for all the people that are here which are able to stay on topic, talk with respect and facts. I am sorry you have to suffer.

I will still post updates on my work here, even if I keep the thread on closed for a while. So feel free to stil check it out.

Andi

 

[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 kernels now as last stable releases following still the old concept (static ramdisk method).

Version 5.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: Only use this version on official CM13 nightlies
• Note: You need at least version 2.2.51 of Boeffla-Config V2 to allow all functionalities to be available
• Fix: Big CPU cluster hotplugging profile "min=2, max=4 (default)" fixed to not switch off cores when certain apps (i.e. camera) are started
• Update: Ramdisk of official CM13.0 build of 04.07.16

Enjoy
Andi

 

[andip71]

Wanna understand what all that fuzz about the "new concept" kernels is about?

You can read latest news on the completely revamped kernel web site www.boeffla-kernel.de.

Article:
http://boeffla-kernel.de/index.php/69-new-concept-kernels-new-app

Enjoy
Andi

 

[andip71]

Anykernel arrived

Hi all,

it is time for the first CM13 kernel with the new anykernel concept.

Before you start, make sure you have read and understood the following:
http://boeffla-kernel.de/index.php/7...new-anykernels

If you ask questions which are addressed in this article, or you have issues which are a consequence of not reading the article, I will not answer. It is your responsibility to understand what you do BEFORE you do it.

(and also read this for more background: http://boeffla-kernel.de/index.php/6...ernels-new-app)

Side note:
Although the kernel is now likely to be much more compatible with custom roms using CM basis, I will not change my support conditions at all. If you report an issue on a non-original CM rom, do not expect me to react (http://boeffla-kernel.de/index.php/support/support)

Ensure you update to latest Boeffla-Config App 2.3.1 BEFORE you flash the new kernel !!!

Enough threatening now, here we go:

Version 5.1-beta1
12.07.2016

• Note: This is the first Boeffla-Kernel with the new anykernel concept.
  Make sure you read and understand the basics: Boeffla-Anykernel Know-How and New concept kernels/New app
  
  
• Note: You have to use Boeffla-Config version 2.3.1 or newer in order to use all functionality !!
  
• This kernel as exactly the same functionalities as the last stable kernel release

Enjoy
Andi

 

[andip71]

Folks,

after around 10 days of the thread being closed, I decided to open it up again now.

Maybe it will be the last time, the thread is open. Because I will close it immediately and finally forever as soon as I see a moderator had to clean up again in the next day due to people not staying on topic or being disrespectful.

So this is my very last warning on that matter:
If that happens again soon - thread closes forever and kernels will not supported anymore on XDA.

I hope this time the people can behave and control themselves.

So READ THE OP to answer your first questions. If you do that and understand what is written here, it should be fairly easy to stay on topic and not ask the same useless questions over and over again.

And just to make it clear: I do not need this thread. I can use my kernels very much without having an XDA thread. Finally such a thread is nothing more than work for me. Having this thread closed makes my life easier. So have that in mind when you post something again.

So now on to the very last trial
Andi

 

[shantam3108]

Folks,

after around 10 days of the thread being closed, I decided to open it up again now.

Maybe it will be the last time, the thread is open. Because I will close it immediately and finally forever as soon as I see a moderator had to clean up again in the next day due to people not staying on topic or being disrespectful.

So this is my very last warning on that matter:
If that happens again soon - thread closes forever and kernels will not supported anymore on XDA.

I hope this time the people can behave and control themselves.

So READ THE OP to answer your first questions. If you do that and understand what is written here, it should be fairly easy to stay on topic and not ask the same useless questions over and over again.

And just to make it clear: I do not need this thread. I can use my kernels very much without having an XDA thread. Finally such a thread is nothing more than work for me. Having this thread closed makes my life easier. So have that in mind when you post something again.

So now on to the very last trial
Andi

Very nice work Andi. Your anykernel concept is very amazing. The code cleanup definitely worked. The phone feels a lot snappier and light than ever. Even the battery life is very better.
Thanks for the great work :
Yes can feel the difference right from boot

 

[return.of.octobot]

Can we please, just this once, not ruin a good thing here guys. The new AnyKernel format should go a long way towards alleviating a great majority of the compatibility issues faced by custom ROM users (which also happens to be the culprit behind a great majority of the pollution in this thread).

That being said, the rules haven't changed. This thread is for support and discussion of Boeffla Kernel as it applies to OFFICIALLY SUPPORTED ROMS, which in this case refers to OFFICIAL CM13 builds for the OnePlus2. Simple enough, if you're running or attempting to run this kernel on any ROM other than the one I just mentioned, that's great, by all means enjoy it; but keep your comments to yourself for the rest of our sake. If we collectively can't refrain from discussing which ROMs this kernel is and is not compatible with outside of CM13, then a separate thread needs to be created specifically for that purpose because it absolutely cannot happen here.

Sent from my oneplus2 using XDA Labs

 

[lexxx84]

Folks,

after around 10 days of the thread being closed, I decided to open it up again now.

Maybe it will be the last time, the thread is open. Because I will close it immediately and finally forever as soon as I see a moderator had to clean up again in the next day due to people not staying on topic or being disrespectful.

So this is my very last warning on that matter:
If that happens again soon - thread closes forever and kernels will not supported anymore on XDA.

I hope this time the people can behave and control themselves.

So READ THE OP to answer your first questions. If you do that and understand what is written here, it should be fairly easy to stay on topic and not ask the same useless questions over and over again.

And just to make it clear: I do not need this thread. I can use my kernels very much without having an XDA thread. Finally such a thread is nothing more than work for me. Having this thread closed makes my life easier. So have that in mind when you post something again.

So now on to the very last trial
Andi

Honestly this post should be stickied on every new page of this thread to warn people to stay on topic.. in fact just to be nice I think I'll quote it on every new page just to provide fair warning

Unfortunately I still have the feeling some people won't bother to follow the rules and the rest of us will have to suffer in the end. I give it a month tops before this thread is closed again, but this time for good

 

[andip71]

... we have it in our hands
We all.

But now back on topic.

Have a nice weekend
Andi

 

[andip71]

Hi all,

update just released.

I decided to remove the zip signature from the flashable zip as it turns out to cause trouble for many recovery versions.
As it, at the same time, provides absolutely zero advantage (everone can unpack the zip, change content, zip and sign it again with the test keys out in the web - so there is anyway no security the zip was not touched since I released it), so why causing trouble for nothing...

Version 5.1-beta2
18.07.2016

• Change: Removed zip signature to be more compatible with certain recoveries
  (do not forget to configure your recovery to bypass signature checks;
  when flashing the kernel out of Boeffla-Config's TWRP screen, this is done automatically temporarily for Boeffla-Kernel zips)
• Change: Build script improvements

Enjoy
Andi

 

[Oodie]

No vibrate altering options in boeffla config app? I can't find it.

Sent from my ONE A2003 using XDA-Developers mobile app

 

[andip71]

No vibrate altering options in boeffla config app? I can't find it.

Sent from my ONE A2003 using XDA-Developers mobile app

Correct. This is not implemented for cm kernels as cm has this setting in its own options (when it is not currently broken again, sometimes this happens).

Andi

 

[Oodie]

Correct. This is not implemented for cm kernels as cm has this setting in its own options (when it is not currently broken again, sometimes this happens).

Andi

Ahh. Thanks . My bad there . Not using a CM based rom right now . Thanks for your reply . But would it be a conflict between two settings ( rom settings & config app ) if you implement in the config app ?

Edit : Have to add this. With correct configuration & without ****ty background apps , kernel is wonderful . No battery drain what so ever .
Compared both stock kernel & Your kernel , & the test results are great . Even 2% drain at night with data on. ( But have to add i'm not using lots of unnecessary cheating texting apps )

 

[andip71]

Ahh. Thanks . My bad there . Not using a CM based rom right now . Thanks for your reply . But would it be a conflict between two settings ( rom settings & config app ) if you implement in the config app ?

Edit : Have to add this. With correct configuration & without ****ty background apps , kernel is wonderful . No battery drain what so ever .
Compared both stock kernel & Your kernel , & the test results are great . Even 2% drain at night with data on. ( But have to add i'm not using lots of unnecessary cheating texting apps )

Yes, when both rom and kernel app change the same settings, it could create a conflict. Hence I try to avoid this.

I have enough mess by e.g. KCAL where rom partially overwrites settings done in the config app (especially on OOS) which makes it very uncontrollable. I try to avoid that whereever possible.

Andi

 

[PeterImmel]

I guess I don't understand the topic right now. I still have the led settings. See the screen shot.
I also still need these because if I set them in cm13 they don't have an effect on blinking speed. Its like this since I'm on cm for two months or so. Also with stock kernel.
If i set the speed with boeffla config app it works.