[KERNEL] [OnePlus2] [OOS3/OOS2] Boeffla-Kernel (18-12-2017)

[andip71]

Thats what I was trying, but I couldn't get it to work:
https://forum.xda-developers.com/showthread.php?t=2287494
Maybe it can be implemented for people like me ... would be awesome!
Thanks in advance!

I am very sorry my friend. But this has absolutely zero to do with kernel space.
And I cannot put something in a kernel tweak app, that is not related to the kernel.

Sorry, but I am very strict in not mixing up these things.

I did not try the guide myself, so I cannot comment whether it would work or not. When I have some time, just out of curiosity, I will look at it and let ya know.

Andi

 

[Adam3Sixty]

Yes, I think I understand what you mean now.

So basically, the backlight dimmer is nothing else than a function that translates the brightness values the rom wants to set (0-255) to converted ones. This follows a specific function, which I took from another kernel as all these kernels implement the same conversion as far as I could see.

This conversion is very visible in low brightness but also in high brightness areas, this is the effect we have.

What you are requesting is to follow the same conversion curve for low brighness but less aggressive for high brightness.
At least this is what I understand.

Basically this means to change the conversion function for it, which means I need to completely look into that first (as said, I took it ready as it was). This requires some time, I put it on my list for investigation, however no promise when I can look after it. Ok?

Thanks
Andi

Thank u for explaining it so well

If u want to look into it, by all means do so, if u do not have the time and it is not over significant importance than feel free to ignore it. I guess it is something that is only person to myself so not of overly high priority.

Everything u do is awesome, I am hoping to get a OnePlus 5 at some point and i am so glad u r already working on it!!

Sent from my brain, via my thumbs, onto the screen of a OnePlus Two input device

 

[Acelogic_]

Greetings Lord Boeffla, I have a request for the OP2 kernel. I would like to some how get the Drivedroid application working with this kernel, but I have no idea if this kernel has the patches required ( UMS support from what I heard) (Drive Droid Thread : https://forum.xda-developers.com/showthread.php?t=2196707 ). It's okay if we're EOL at this point, you don't have to look into it if you don't want to. I completely understand that I should've gotten a newer phone at this point, however it would be a big convenience to have DriveDroid working. For some background I'm running lineage OS 14.1 Aug 24th 2017 build.

 

[andip71]

Thank u for explaining it so well

If u want to look into it, by all means do so, if u do not have the time and it is not over significant importance than feel free to ignore it. I guess it is something that is only person to myself so not of overly high priority.

Everything u do is awesome, I am hoping to get a OnePlus 5 at some point and i am so glad u r already working on it!!

Sent from my brain, via my thumbs, onto the screen of a OnePlus Two input device

Sure. The thing is - this is very subjective. Some like it as it is, some want it a bit more in one direct, some in another.
When I find time I can try to make the curve a bit more reasonable (on OP3 and OP5 it is a bit different, maybe I should take this algorith for a try).

Greetings Lord Boeffla, I have a request for the OP2 kernel. I would like to some how get the Drivedroid application working with this kernel, but I have no idea if this kernel has the patches required ( UMS support from what I heard) (Drive Droid Thread : https://forum.xda-developers.com/showthread.php?t=2196707 ). It's okay if we're EOL at this point, you don't have to look into it if you don't want to. I completely understand that I should've gotten a newer phone at this point, however it would be a big convenience to have DriveDroid working. For some background I'm running lineage OS 14.1 Aug 24th 2017 build.

The patches are in, I can confirm that.
I never tested this myself as I do not have a use case for that.
Other testers say, it only works "half" when I remember correctly.
Seems like the patches are not fully working on modern 64 bit kernels.

You can try it, maybe it works good enough for you.

Andi

 

[ft_ft]

I am very sorry my friend. But this has absolutely zero to do with kernel space.
And I cannot put something in a kernel tweak app, that is not related to the kernel.

Sorry, but I am very strict in not mixing up these things.

I did not try the guide myself, so I cannot comment whether it would work or not. When I have some time, just out of curiosity, I will look at it and let ya know.

Andi

Hello Andi,
I just saw the LAN OTG module and thought Lan over USB would be sort of similar

Yesterday I found this:
https://github.com/Genymobile/gnirehtet
Running pretty good on a Raspi
Using that for now

Thank you very very much!

 

[andip71]

Hello Andi,
I just saw the LAN OTG module and thought Lan over USB would be sort of similar

Yesterday I found this:
https://github.com/Genymobile/gnirehtet
Running pretty good on a Raspi
Using that for now

Thank you very very much!

Na, LAN OTG is something very different. And it is very shaky too, I really should remove that longer term.

Great you found a good solution for you !!!

Andi

 

[andip71]

Hi all,

new update is out.

Version 2.4-beta5
06.09.2017

• New: Boeffla generic wakelock blocker added in version 1.1.0 - this is an expert function only, so please click for the usage guide on Boeffla homepage
  (Note - the following wakelocks are blocked by default already: qcom_rx_wakelock, wlan, wlan_wow_wl, wlan_extscan_wl, netmgr_wl and NETLINK)
• Fix: Boeffla touchkey LED control driver fixed to allow all possible configurations again and reflect stock behaviour as default (LEDs fully off, LED on screen touch, configurable duration etc.)
• Change: Internal kernel busybox updated to latest version 1.27.2 (self-compiled from sources, www.busybox.net)
• Change: cpuidle driver tweaked

Enjoy
Andi

 

[minty95]

Hello
I updated my kernal from stock to the latest Boeffla Kernel (after clean flash lineage, full wipe, flash superSu, and app installed etc) all went well but then I updated to latest Lineage nightly and of course started getting error messages from the Boeffla app (if I understand corectly when flashing a nightly you overwrites the Boeffla kernel by the stock)

After reading and checking I realised that after installing a new nighty I should have flashed superSu again and Boeffla kernel again

Just a question, I presume that I must flash all three, nightly, superSu and Boeffla kernel one after another before booting ?

Many thanks for a quick confirm, then I can reflash, full wipe and start again

 

[TheVic!]

Hello
I updated my kernal from stock to the latest Boeffla Kernel (after clean flash lineage, full wipe, flash superSu, and app installed etc) all went well but then I updated to latest Lineage nightly and of course started getting error messages from the Boeffla app (if I understand corectly when flashing a nightly you overwrites the Boeffla kernel by the stock)

After reading and checking I realised that after installing a new nighty I should have flashed superSu again and Boeffla kernel again

Just a question, I presume that I must flash all three, nightly, superSu and Boeffla kernel one after another before booting ?

Many thanks for a quick confirm, then I can reflash, full wipe and start again

That is correct. And I would follow that Order as well. Rom, SU and kernel.

 

[pure.by]

Hi all,

new update is out.

Version 2.4-beta5[...]
Enjoy
Andi

Awesome new functionality! Thank you so much once again

---------- Post added at 01:58 PM ---------- Previous post was at 01:51 PM ----------

A quick question regarding scripting... Is there any practical difference between "Profile Scripting" and "Action → Scripting"?

As far as I understand, "Action Scripting" is applied on every boot (or executed manually through interface) regardless of the chosen profile, and "Profile Scripting" will be executed every time a corresponding profile activates (or when phone boots into a corresponding profile); is that correct? Is there more to it?

 

[andip71]

Hello
I updated my kernal from stock to the latest Boeffla Kernel (after clean flash lineage, full wipe, flash superSu, and app installed etc) all went well but then I updated to latest Lineage nightly and of course started getting error messages from the Boeffla app (if I understand corectly when flashing a nightly you overwrites the Boeffla kernel by the stock)

After reading and checking I realised that after installing a new nighty I should have flashed superSu again and Boeffla kernel again

Just a question, I presume that I must flash all three, nightly, superSu and Boeffla kernel one after another before booting ?

Many thanks for a quick confirm, then I can reflash, full wipe and start again

You are in the wrong thread, we are only talking OOS kernel here. So you should go to the right thread fist.
Then second: For LineageOS on OP2 you have to use latest kernel version I provide, no older or stable one. Even written in the download section.
Stable kernel is too old for latest Lineage roms.

Awesome new functionality! Thank you so much once again

---------- Post added at 01:58 PM ---------- Previous post was at 01:51 PM ----------

A quick question regarding scripting... Is there any practical difference between "Profile Scripting" and "Action → Scripting"?

As far as I understand, "Action Scripting" is applied on every boot (or executed manually through interface) regardless of the chosen profile, and "Profile Scripting" will be executed every time a corresponding profile activates (or when phone boots into a corresponding profile); is that correct? Is there more to it?

You got it right.

Action -> scripting is executed once after a system start only (or manually as you like).

Profile script is run every time a profile gets applied (i.e. during boot, after switching profiles etc.)

So one is static and the other is related to profiles. Thats it.
(and before you ask: during boot first the profile script gets executed, and finally the static script)

Andi

 

[minty95]

You are in the wrong thread, we are only talking OOS kernel here. So you should go to the right thread fist.
Then second: For LineageOS on OP2 you have to use latest kernel version I provide, no older or stable one. Even written in the download section.
Stable kernel is too old for latest Lineage roms.

Hi
Thanks, sorry about wrong thread

Saw about that I had to use the latest kernel Beta ... just had missed the section about reinstalling when flashing nightlies

All is clear now, and all is working just fine

many thanks

 

[andip71]

Saw about that I had to use the latest kernel Beta ... just had missed the section about reinstalling when flashing nightlies

All is clear now, and all is working just fine

many thanks

No worries, excellent all is fine for you now.

Andi

 

[andip71]

Ok folks, time has come: I am starting to a small 10-days holiday break now. Visiting Oktoberfest in Munich and roaming around with my friends from Florida in the Berlin area.

This means: No update on kernels an app in the next days. Whatever happens in the world, I am away from home and could not do anything.

Please also note, support from myself will be reduced to a bare minimum per nature. I try to read from time to time in the forums, but I will not have the chance for any detailed answers.

CU all again Monday the week after next.

Have a great time
Andi

 

[yajumh11]

do i need to change anything to get good battery life?

 

[Au5t1n]

Any update on the custom charge rate driver? I miss this functionality

 

[andip71]

Any update on the custom charge rate driver? I miss this functionality

Nope, this is not planned anymore on the OP2.

Things that make trouble are not worth messing with it.

Sorry
Andi

 

[ThaRealSaad]

Hi, love the kernel and the support. Well done devs. But I have one little issue. After flashing this kernel and trying out different profiles. Snapchat no longer let's me sign in. Saying that third party apps or plug ins are against their poilcy. Anyone else facing this issue?

 

[andip71]

Hi, love the kernel and the support. Well done devs. But I have one little issue. After flashing this kernel and trying out different profiles. Snapchat no longer let's me sign in. Saying that third party apps or plug ins are against their poilcy. Anyone else facing this issue?

At least I cannot contribute to that. I am not a snapchat user.
Maybe they check safetynet etc. I have no idea why snapchat would be having an issue with a custom kernel, but seems it has.

Let's see whether someone else is chiming in with some more information.

Andi

P.S. And it is only one dev, me, myself, .... there is not a team behind the Boeffla initiative, just one single poor man

 

[ThaRealSaad]

At least I cannot contribute to that. I am not a snapchat user.
Maybe they check safetynet etc. I have no idea why snapchat would be having an issue with a custom kernel, but seems it has.

Let's see whether someone else is chiming in with some more information.

Andi

P.S. And it is only one dev, me, myself, .... there is not a team behind the Boeffla initiative, just one single poor man

Hahahaha I did not know that. Support and development is great for just one single man. Hats off to you sir! And regarding the issue I asked a senior developer who is a cousin of mine. He said that the issue could be that Snapchat detected the root since I'm on SuperSU. So next time I flash root I'll use Magisk so I am able to hide the root from apps like Snapchat that mess up. Thanks for your effort and support.