In my humble opinion, Alucard's combo (gov + hotplug) is the best option for battery and performance oriented profiles.Trying now thx
If well set up, it performs amazingly well in both situations.
In my humble opinion, Alucard's combo (gov + hotplug) is the best option for battery and performance oriented profiles.Trying now thx
OK thanks will try that too!In my humble opinion, Alucard's combo (gov + hotplug) is the best option for battery and performance oriented profiles.
If well set up, it performs amazingly well in both situations.
What is the version you are using? that crashesHello. Help is needed. Latest updates.
The application always crashes when I enter the KERNEL-CPU.
How to get rid of this problem?
---------- Post added at 12:41 PM ---------- Previous post was at 11:48 AM ----------
Please, help.
Does not work TOOLS-Profile-profile name-Set Per App Settings-Default.
After the phone is rebooted, the profile does not apply.
I will need the logs to deal with the crashes.I'm using version 54.
Now I'll try your attached version.
I can test the per app profile is working just fine, I manage to get the same problem before, then after the fix no problem.In your beta version when I select a profile and Set Per App Settings it is not possible to include the application in special services.
The last version of the application where the profile is running (namely Default) is 44
The application crashes when I try to enter the CPU. After several successive attempts to select a CPU (about 5-10), the application does not crash and starts up in the CPU. It began approximately in the application from version 48-50.
Great settings as well. Thanks.In my humble opinion, Alucard's combo (gov + hotplug) is the best option for battery and performance oriented profiles.
If well set up, it performs amazingly well in both situations.

Depends on the settings, but it's possible to have similar battery drain combined with better performance in my opinion. I'm using LOS 14.1. I think everything is smoother that without the kernel.So...do these latest posted configurations (CPU gov/Hotplug and such) provide a better overall battery drain compared to stock? Asking the people that posted these modifications or anyone that made BHB's kernel better than with its default settings.
I keep switching back and forth between them as it makes it seem that stock kernel gives a slower overall battery drainage...

Hi BHB, I've seen members of forum Moto Maxx Brasil saying about random reboots, i told then to create a log and send for u, but, they don't... So i got too, and i did...started again after update 75kernel, i did some logs but at end i deleted, today did a new, maybe u can help us. Thx u! U can see my configuration, im here to test if u need, just tell me and i send a feedback about. Ah, i got my last reboot today in lockscreen, when i tried wakeup the phone to unlock.
you can just disable all aply on boot that you enable or clean app data and reboot to cleanup any changes that the app does to the kernel, the zip can show me what changes you have made I will try those to see if causes problem here...
if the problem keeps happening after keep sharing the logs from right after the reboot so I can see what causes it...
are you build the ROM?
or just changing the prop values?Code:[ro.cm.display.version]: [14.1-20171014-OFFICIAL-quark] [ro.build.host]: [EVNS] [ro.build.user]: [EVNS]
You on the same ROM version that first report the problemMore random restart
[ro.cm.version]: [14.1-20171014-OFFICIAL-quark]
Im in Lineage, changed prop for fun, i did a clean install of rom today, nothing changed about props, totally updated, will try again and tell u about newsyou can just disable all aply on boot that you enable or clean app data and reboot to cleanup any changes that the app does to the kernel, the zip can show me what changes you have made I will try those to see if causes problem here...
if the problem keeps happening after keep sharing the logs from right after the reboot so I can see what causes it...
are you build the ROM?
You on the same ROM version that first report the problem
Like I wrote before I run yours config without any problem but I run it on a updated ROM, I share to you before a boot.img because what was needed to change wasn't just related to the kernel...
As I can't reproduce the problem and I'm running a custom ROM that is at least one month update then yours can you update the ROM to a update ROM clean install, then start over yours config...
because the logs just point to the same problem that I can reproduce here I need a change on yours side...