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

Status
Not open for further replies.

Sam Nakamura

Retired Forum Moderator
Dec 7, 2015
5,476
4,530
113
Landshut (Ndb.)
Hey Lord, last days a did a little trail'n error with different kernels and was pretty surprised by the performance of other kernels and the achieved SOT (about 5 hours SOT), on previous versions (beta1 - 4) "my settings" (shutting down lots of kernel related stuff like little cluster running only on 1 or 2 by default and changing big to min1/max4) achieved only with luck get to 3,5 to 4 hours SOT. The other kernel in specific didn't allow to much changes like in your awesome config app which together with @nicesoni_ash comments on leaving all core related stuff made me wonder if "my settings" are the culprit of this low SOT. Intend to save battery actually waste it. So I tested again this morning with your beta5 and switched on early noon to beta 6 with only changing governers to zzmoove and let all other core related stuff unchanged. Surprisingly I got a wonderful ride on resurrection remix (last relesae) of more than 7 hours SOT with still good 10% power left. (Edit: even hit the eighth hour :good: )
So I learned today that sometimes overdoing the settings is a bad idea because the outcome is actually the opposite, sometimes it is good to leave things as they are.. And of course SOT is not all, I actually just want to avoid to recharge my phone twice or thrice a day, which was the situation quite a while :)
Thanks for your awesomeness!
 

Attachments

Last edited:

andip71

Recognized Developer
Apr 22, 2008
17,094
67,644
263
Potsdam
www.boeffla.de
Hey Lord, last days a did a little trail'n error with different kernels and was pretty surprised by the performance of other kernels and the achieved SOT (about 5 hours SOT), on previous versions (beta1 - 4) "my settings" (shutting down lots of kernel related stuff like little cluster running only on 1 or 2 by default and changing big to min1/max4) achieved only with luck get to 3,5 to 4 hours SOT. The other kernel in specific didn't allow to much changes like in your awesome config app which together with @nicesoni_ash comments on leaving all core related stuff made me wonder if "my settings" are the culprit of this low SOT. Intend to save battery actually waste it. So I tested again this morning with your beta5 and switched on early noon to beta 6 with only changing governers to zzmoove and let all other core related stuff unchanged. Surprisingly I got a wonderful ride on resurrection remix (last relesae) of more than 7 hours SOT with still good 10% power left. (Edit: even hit the eighth hour :good: )
So I learned today that sometimes overdoing the settings is a bad idea because the outcome is actually the opposite, sometimes it is good to leave things as they are.. And of course SOT is not all, I actually just want to avoid to recharge my phone twice or thrice a day, which was the situation quite a while :)
Thanks for your awesomeness!
I can only agree!

So many people tend to overdo it (because they think trying everything to the extreme helps).
But it is a rarely known fact, this can be very counterproductive.
Stock kernels are usually quite well balanced, so when you change some settings too extreme, it gets out of it's balance and the negative effects take over.

I recommend to slightly change and tweak the kernels only. This usually gives best results.

Thanks
Andi
 

CounterC

Senior Member
Oct 26, 2012
2,029
635
0
Hey Lord, last days a did a little trail'n error with different kernels and was pretty surprised by the performance of other kernels and the achieved SOT (about 5 hours SOT), on previous versions (beta1 - 4) "my settings" (shutting down lots of kernel related stuff like little cluster running only on 1 or 2 by default and changing big to min1/max4) achieved only with luck get to 3,5 to 4 hours SOT. The other kernel in specific didn't allow to much changes like in your awesome config app which together with @nicesoni_ash comments on leaving all core related stuff made me wonder if "my settings" are the culprit of this low SOT. Intend to save battery actually waste it. So I tested again this morning with your beta5 and switched on early noon to beta 6 with only changing governers to zzmoove and let all other core related stuff unchanged. Surprisingly I got a wonderful ride on resurrection remix (last relesae) of more than 7 hours SOT with still good 10% power left. (Edit: even hit the eighth hour :good: )
So I learned today that sometimes overdoing the settings is a bad idea because the outcome is actually the opposite, sometimes it is good to leave things as they are.. And of course SOT is not all, I actually just want to avoid to recharge my phone twice or thrice a day, which was the situation quite a while :)
Thanks for your awesomeness!
Always getting the max out of the OP2 this guy :laugh:
Well done mate, have applied same settings now, what scheduler u use?
 

Sam Nakamura

Retired Forum Moderator
Dec 7, 2015
5,476
4,530
113
Landshut (Ndb.)
Always getting the max out of the OP2 this guy :laugh:
Well done mate, have applied same settings now, what scheduler u use?
Pure coincidence, mate.. :) I'm innocent and can't explain that and trying to verify that but looks good..
Scheduler is stock sio, governer zzmoove, gpu on simple_ondemand and lowered to 27mhz, no core changes at all, little more entropy like 256 / 384..
Rom sided I choose efficient battery profile with automatic optimization + greenify Beta & force doze..
Not sure how important the rom sided part is
 
  • Like
Reactions: adil089

adil089

Senior Member
Apr 29, 2014
635
181
0
Pure coincidence, mate.. :) I'm innocent and can't explain that and trying to verify that but looks good..
Scheduler is stock sio, governer zzmoove, gpu on simple_ondemand and lowered to 27mhz, no core changes at all, little more entropy like 256 / 384..
Rom sided I choose efficient battery profile with automatic optimization + greenify Beta & force doze..
Not sure how important the rom sided part is
Hmm... I would be interested to know the effect the ROM setting have on battery as well. Does anyone know anything about it?
 

knpk13

Senior Member
Dec 11, 2015
2,087
1,204
193
Hmm... I would be interested to know the effect the ROM setting have on battery as well. Does anyone know anything about it?
This was asked and answered previously by Lord Boeffla. Search for it. (He said the ROM profile modes will not overwrite any kernel settings, so theoretically there should be no effect)
 

beschoenen

New member
Dec 27, 2014
3
0
0
Hopefully, you guys can help me, I've been unable to tether wifi on my OnePlus 2.

I know the new Beta 6 should fix the tethering issue, but it doesn't for me.

- OOS 3.1.0: Tethering works.
- Clean flashed stock CM14.1: Tethering doesn't work.
- Clean flashed CM14.1 with Boeffla: Tethering doesn't work.

I'm not sure what do.

Java exception from when I click the tethering tile:
Code:
12-16 01:32:33.273  1052  7060 E ActivityManager: Sending non-protected broadcast com.google.android.carrierentitlement.SILENT_ENTITLEMENT_CHECK from system 9571:com.android.settings/1000 pkg com.android.settings
12-16 01:32:33.273  1052  7060 E ActivityManager: java.lang.Throwable
12-16 01:32:33.273  1052  7060 E ActivityManager: 	at com.android.server.am.ActivityManagerService.checkBroadcastFromSystem(ActivityManagerService.java:18037)
12-16 01:32:33.273  1052  7060 E ActivityManager: 	at com.android.server.am.ActivityManagerService.broadcastIntentLocked(ActivityManagerService.java:18626)
12-16 01:32:33.273  1052  7060 E ActivityManager: 	at com.android.server.am.ActivityManagerService.broadcastIntent(ActivityManagerService.java:18717)
12-16 01:32:33.273  1052  7060 E ActivityManager: 	at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:499)
12-16 01:32:33.273  1052  7060 E ActivityManager: 	at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:2967)
12-16 01:32:33.273  1052  7060 E ActivityManager: 	at android.os.Binder.execTransact(Binder.java:565)
I can upload a full logcat if needed.
 

knpk13

Senior Member
Dec 11, 2015
2,087
1,204
193
- Clean flashed stock CM14.1: Tethering doesn't work.
- Clean flashed CM14.1 with Boeffla: Tethering doesn't work.

You answered your own question right there. If tethering doesn't work on stock CM, I don't see how it's going to start working on Boeffla. Might be a CM bug since tethering doesn't work on stock CM as well. I'm currently on CM13 with Boeffla, so can't test for you.
 
  • Like
Reactions: pure.by

andip71

Recognized Developer
Apr 22, 2008
17,094
67,644
263
Potsdam
www.boeffla.de
Ok, I did not see what happened (again !!), but as the OP2 thread is constant subject to misbehaving, I am closing it for now.

Let's see when and if I open it again.

There seems to be an extraordinary high number of rude and misbehaving members in the OP2 area... sad. But not my problem.

Say thanks to the idi*ts.

Andi
 
Last edited by a moderator:

andip71

Recognized Developer
Apr 22, 2008
17,094
67,644
263
Potsdam
www.boeffla.de
Hi all,

maintenance update for Lineage 14.1 kernel (former CM) is out:

Version 6.0-beta8

08.01.2017

  • Note: Name change for kernel from CM to LineageOS (although currently it runs on both)
    (you should use Boeffla-Config app version 2.4.26 or higher)
  • Update: Updated with latest official LineageOS kernel commits as of 08.01.17, 10am CET
  • Change: Internal kernel busybox updated to latest version 1.26.1 (self-compiled from sources, www.busybox.net)
Enjoy
Andi
 
Status
Not open for further replies.