[EOL][KERNEL] [OnePlusX] [OOS 3.x.x/2.x.x] Boeffla-Kernel (12-06-2017)

Status
Not open for further replies.

ihs0201

Member
Feb 18, 2016
14
9
0
Hi could someone kindly share their saturation, display value and contrast value from the dislplay+led section in the boeffla configuration app. I moved the slider a while ago but forgot to take a screenshot before doing so. Thanks a lot :)
 

taaeem

Senior Member
Feb 22, 2014
1,013
642
0
Hamburg
Possible bug report with the kernel app, it always sets the SELinux mode to strict when it applies the profile, even if I added the permissive stuff in Settings and kernel load, it just stays on moderate until the profile gets applied and after that it's on strict...
And because of that Viper4Android won't work..
 

jonrodz

Senior Member
Nov 9, 2014
610
224
0
San Pedro Sula
Possible bug report with the kernel app, it always sets the SELinux mode to strict when it applies the profile, even if I added the permissive stuff in Settings and kernel load, it just stays on moderate until the profile gets applied and after that it's on strict...
And because of that Viper4Android won't work..
You need to go to settings > kernel startup actions and enable this...1460673878982.jpg
 

CertifiedBlyndGuy

Retired Forum Moderator / Inactive Recognized Deve
Jun 11, 2014
1,936
2,983
113
Boulder
I know Lord Boeffla said no, but would you be interested in making a CAF version of this kernel? I may try at it myself while I'm working on SwellKP and NH, but you obviously have a lot more experience
 

migueldbr

Senior Member
Nov 30, 2011
1,879
510
0
Coimbra
@Lord Boeffla the 27mhz idle gpu frequency seems to be the cause of scrolling stutters (micro stutters), is that why you have it disabled and set the min gpu @ 200mhz? A lot of kernel developers add the 27mhz step to the idle frequency and usually its not possible to remove it (with kernel adiutor it only lets me choose the min gpu freq to 200mhz, but when it idles it always goes back to 27mhz). But with your kernel and app it lets me choose the minimum gpu freq even when idle, which is awesome. I never understood why i had better scrolling performance on oxygen rom (because it uses min gpu freq @ 200mhz instead of 27mhz) because once i flashed your kernel i would edit right away, making the minimum gpu freq @ 27mhz. With min gpu freq @ 200mhz it solves my micro stutters when scrolling (im assuming the stutters happen because the gpu idles too soon, going to idle before even ending the scroll movement). Is this correct?

I also experienced this on my previous device (LG G2 on cm13) because it would also idle @ 27mhz, and did not experience it on stock rom (which goes to idle at higher gpu freq), so thats the only explanation that makes sense to me..
 
Last edited:

andip71

Recognized Developer
Apr 22, 2008
17,094
67,644
263
Potsdam
www.boeffla.de
@Lord Boeffla the 27mhz idle gpu frequency seems to be the cause of scrolling stutters (micro stutters), is that why you have it disabled and set the min gpu @ 200mhz? A lot of kernel developers add the 27mhz step to the idle frequency and usually its not possible to remove it (with kernel adiutor it only lets me choose the min gpu freq to 200mhz, but when it idles it always goes back to 27mhz). But with your kernel and app it lets me choose the minimum gpu freq even when idle, which is awesome. I never understood why i had better scrolling performance on oxygen rom (because it uses min gpu freq @ 200mhz instead of 27mhz) because once i flashed your kernel i would edit right away, making the minimum gpu freq @ 27mhz. With min gpu freq @ 200mhz it solves my micro stutters when scrolling (im assuming the stutters happen because the gpu idles too soon, going to idle before even ending the scroll movement). Is this correct?

I also experienced this on my previous device (LG G2 on cm13) because it would also idle @ 27mhz, and did not experience it on stock rom (which goes to idle at higher gpu freq), so thats the only explanation that makes sense to me..
More or less this is the reason why I default to 200 instead of 27 MHz.
Scrolling stutters a bit more with 27, and also GPU performance for other tasks is too low for some.

And I was tired of answering the same question over and over again why scrolling is less smooth with my kernel. So I put it on the stock 200 MHz. Everyone can then actively down it to 27, with knowing what he does.

Andi
 

migueldbr

Senior Member
Nov 30, 2011
1,879
510
0
Coimbra
More or less this is the reason why I default to 200 instead of 27 MHz.
Scrolling stutters a bit more with 27, and also GPU performance for other tasks is too low for some.

And I was tired of answering the same question over and over again why scrolling is less smooth with my kernel. So I put it on the stock 200 MHz. Everyone can then actively down it to 27, with knowing what he does.

Andi
Sorry, didnt know you had already answered this question before, thanks for the explanation. It is much better @ 200mhz to be honest. Earlier I flashed ashwins cm13 and noticed it idled @ 200 too, that's probably why it is so smooth. But oxygen+boeffla kernel(@ 200mhz idle) is as smooth as cm13 imo. Thanks for the awesome kernel btw
 
  • Like
Reactions: andip71

SlanDev

Senior Member
Apr 9, 2015
164
43
0
I had a few problems with boeffla:

- Boeffla Config app does not work. It won't change the settings, and there is no "apply" button. (MPDecision is on, app doesn't show the warning)
- Too low performance. On 2.57 GHz I got only 40k AnTuTu and 700 geekbench points. I know that Benchmarks =/= actual performance, but I think something's wrong when they are much lower than 2.3 GHz on blu.spark.

Changing voltages (using kernel adiutor since boeffla config doesn't work, as I mentioned) didn't make the benchmarks change.

Installation:
Dirty-flashed over blu.spark on Oxygen 2.2.1.

What did I do wrong?
 

andip71

Recognized Developer
Apr 22, 2008
17,094
67,644
263
Potsdam
www.boeffla.de
I had a few problems with boeffla:

- Boeffla Config app does not work. It won't change the settings, and there is no "apply" button. (MPDecision is on, app doesn't show the warning)
- Too low performance. On 2.57 GHz I got only 40k AnTuTu and 700 geekbench points. I know that Benchmarks =/= actual performance, but I think something's wrong when they are much lower than 2.3 GHz on blu.spark.

Changing voltages (using kernel adiutor since boeffla config doesn't work, as I mentioned) didn't make the benchmarks change.

Installation:
Dirty-flashed over blu.spark on Oxygen 2.2.1.

What did I do wrong?
I do not know what is wrong, but there is something completely wrong!!!

When Boeffla-Config cannot apply settings, then something is severely messed up.
BTW - There is no apply button, as I do not like that philosophy in general.

As you said, you had blu spark before. No clue what all gets changed by blu spark, but recently another user was reporting similar stuff and he did a clean install as next step. Since then all is working fine for him.

I can only recommend to go for a clean install when you had another custom kernel etc installed before.

Andi
 
  • Like
Reactions: SlanDev

SlanDev

Senior Member
Apr 9, 2015
164
43
0
I do not know what is wrong, but there is something completely wrong!!!

When Boeffla-Config cannot apply settings, then something is severely messed up.
BTW - There is no apply button, as I do not like that philosophy in general.

As you said, you had blu spark before. No clue what all gets changed by blu spark, but recently another user was reporting similar stuff and he did a clean install as next step. Since then all is working fine for him.

I can only recommend to go for a clean install when you had another custom kernel etc installed before.

Andi
Ok, then I'll use Titanium Backup for my apps and do a complete reinstall of OOS, and flash Boeffla over the original kernel.

If Boeflla Config has no apply button, does that mean it instantly applied changes or when I leave the app?
 
Status
Not open for further replies.