yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] ChrisMirza:
Okay, BFQ is the recommended for MM, what about cpu governor? I'm on zz 5 profile and seems to be okay. Other governors (except zzmove, nightmare and darkness) keeps the cpu 1 (cpu0) frequency always at "hispeed_freq" when it's the only the activated.

Gpu simple algorithm ramps Gpu freq to max everytime, turning it off the Gpu seems to be less aggressive.

Enviado de meu Moto MAXX usando Tapatalk
[Moto Maxx Android Development] fgl27:
you don't really understand the features is all on the 1° page please read it all... the default config on the kernel is for performance vs battery as it is write on the chagelog, not battery or performance alone, zz 5 is the most aggressive and lag governor that zz have is not for performance is just for battery.

the function of simple gpu algo is to make the GPU more battery friendly making the frequency run down more then when is off, it only works on msn-adreno-tz.

you may chose any config there is many many options, test has much as you wanna and make your on recommendation, recommendation are recommendation you can or not fallow.
[Moto Maxx Android Development] ChrisMirza:
Well, simple gpu puts Gpu in 600hz even when scrolling the page, when it's off it stays close to 200-300.

Gpu idler works ok.

Enviado de meu Moto MAXX usando Tapatalk
[Moto Maxx Android Development] fgl27:
yes you are right, I check more and there is some over use here... I will disable it on a next build and enable idler by default to see. :good:
[Moto Maxx Android Development] ChrisMirza:
Can you check the governors (except zzmove, nightmare and darkness) keeping the cpu0 (cpu 1 at adiutor) at the 'hispeed_freq tunable' when it's the only cpu activated?

Is it only for me?

Enviado de meu Moto MAXX usando Tapatalk
[Moto Maxx Android Development] fgl27:
enable show cpu usage on developer options... auditor cpu is not a perfect display of the current cpu freq as you can see on the pic.

and some gov don't have hispeed_freq.
[Moto Maxx Android Development] veloct:
I'm having the same results as you, it's also laggy at times but i'm on the standard CM kernel. Running 3/2 via clean install and Slim mini gapps. I just rebooted to create a backup and it seems snappy again, I'll see if that continues.
[Moto Maxx Android Development] Latiken:
I can also confirm the lagginess, it seems to be an issue with MM.
[Moto Maxx Android Development] GreaterLesser:
I'm not sure about the others but I've always had this feature enabled even when it wasn't default and I had it enabled in LP and experienced nothing like this.
[Moto Maxx Android Development] iiWoodstocK:
Same. I've had sweep2wake and dt2w enabled since the very first test build that introduced it and I haven't seen any overactive CPU usage, nor any of the potential battery drain that the wakelock could cause.
[Moto Maxx Android Development] Latiken:
I'm starting to experience reboots again albeit not as common. Currently running zzmoove profile 8 and changed voltage to -60mV.

I'm starting to think it might be a bug with the kernel. Will update.
[Moto Maxx Android Development] ChazzMatt:
Stop undervolting and see what happens.

For awhile Franco refused to listen to any bug reports from people undervolting on the gen5 Nexus 5. There was nothing wrong with his kernel people weren't messing up trying to lower the microcurrent of electricity LG had deemed necessary to run the device. People got really into it, trying to save battery that way -- but it was giving him fits trying to figure out any possible bugs in his kernel, when most of the time it was the undervolting causing the issue.

So, stop the undervolting, see if you have any reboots?
[Moto Maxx Android Development] Latiken:
I will next time I get a random reboot. Haven't gotten one in like a day.

Back on RR LP, I would get them even after I defaulted to the normal voltage; it got so bad that it would reboot every 10 minutes. I switched to MM since this is the version baybutcher is focusing on.
[Moto Maxx Android Development] drizzzzzz:
[MENTION=5747496]baybutcher27[/MENTION] did you change the audio buffer size at all? I have only had crashes while using BT voice and music (BT and not). I had this issue on CF before he increased the buffer size. I don't know if everyone else is experiencing reboots when they are playing music or what, but I've had no other reboots (keeping voltage offset at about -35mV).
[Moto Maxx Android Development] fgl27:
I don't understand your problem try to explain better. Audio files buffer size are a ROM thing not a kernel.
[Moto Maxx Android Development] fgl27:
Test build

BHB27-Kernel-V126-CM-RR-Test-15-M.zip​

Marshmallow only.

Changelog

Many changes to the kernel read all at the change-log...

Download BHB27-Kernel for M

To use this, Check my RR marshmallow Thread WIP

Bug report: make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.

BTW. Once we finish testing this version, I will make it a stable, and port some of the new featuring to the 5.1 kernel.
[Moto Maxx Android Development] fndpena:
Phone is rebooting from time to time, happened twice this morning. Then I've restored all the settings in kernel adiutor, tried to manually reboot and it was taking forever to boot (stucked on boot animation), ended up forcing turn off and now the dalvik cache is being rebuild :/. My phone was fine yesterday, before installing bhb27 (was using stock cm kernel before that).
[Moto Maxx Android Development] drizzzzzz:
Sorry, should've posted this in the ROM thread. Just thought it might be a cause of some reboots.
[Moto Maxx Android Development] fndpena:
So... phone was occasionally rebooting after changing some settings on kernel adiutor. Btw I'm running CM13 with the latest kernel.

Then I went and removed all the settings that I had changed and disabled "apply on boot". Problem seems to be gone, no more reboots after several hours.

But if possible, I wanna find out why it was happening... I only changed a few things like: governor to zzmoove (profile 2), scheduler to noop, enabled wakeup boost and I guess this is it... If I would bet, I would say that is zzmoove's fault, but it's only a guess... Any clue guys?
[Moto Maxx Android Development] ChrisMirza:
Zzmove profile 2 is good but outdated, it doesn't update anymore, try the 5 profile.

Does it freezes before reboot? Might be the voltage, did you minus it?

Enviado de meu Moto MAXX usando Tapatalk
[Moto Maxx Android Development] fndpena:
No freezing, just reboots... I've only changed those options, no undervolt... I guess I'm gonna keep the default settings. Umbrella_core is good for battery as well.
[Moto Maxx Android Development] ChrisMirza:
It simply reboot?

My phone reboots sometimes when I try to multitask while it's in landscape mode...

Yeah, I know your feel.

Enviado de meu Moto MAXX usando Tapatalk
[Moto Maxx Android Development] fgl27:
CM13 is out of data, there is a lot of improves that the dev did not had time to do.

wakeup boost is not recommended to use, I don't.

@ all

I'm not paying too much attention to bugs reports that I don't have on RR, At this moment all the MM ROM's are wip, CM13 is out of data, so when things are more stable on the ROM side I will see they all if there is bugs to see...

I don't have any reboot at all ever, I use my recommended config but I change a lot and it never happens to me.

Out of data ROM, Root/Xposed app and undervoltage may be the problem off all random reboots.

Clean install and a simple clean of dalvik and cache help too...
[Moto Maxx Android Development] fgl27:
Kernel Adiutor update

KernelAdiutor-0.9.9.4.+02.BHB27-Mod.apk​

Major overhaul on the features a brand new app check changelog!

Download Kernel auditor

APK or ZIP?

If you have building Kernel auditor like in RR you must use the zip.

If you don't if install it from play you must use the apk, if using the apk please uninstall your version first.

* To install the zip 1° uninstall any updates that you made via play of Kernel Adiutor

* Clear data of yours Kernel Adiutor app

* Then flash via TWRP, no wipe is need.

* If encounter any problem try to clean dalvik and cache before reporting things

* This must work on any ROM 5.1 or 6.0

* No updates to the Kernel is need to use all the changes

Changelog

* All the changes port from Team-Singularity Kernel Adiutor made by yoinx developer

Use my version of kernel auditor to better support this Kernel.

A lot of changes on this version If there is something else to update/Fix on Kernel Adiutor please let me know, I tested everything is all working.
[Moto Maxx Android Development] fgl27:
More pics XDA have a limit of pics for post.

Enjoy :good:
[Moto Maxx Android Development] newbe1droidx:
Installed RR6 two days ago with stock kernel. No problems at all. Want to try this kernel. Do I need to uninstall Auditor first or flash kernel then Auditor then wipe cache/ dalvic and reboot. Or wipe first?

Droid turbo by the way
[Moto Maxx Android Development] GreaterLesser:
You just have to wipe the data for kernel auditor before installing the kernel.
[Moto Maxx Android Development] newbe1droidx:
Awesome thanks for the quick reply.
[Moto Maxx Android Development] GreaterLesser:
[MENTION=5747496]baybutcher27[/MENTION]

Just a friendly reminder to link the Kernel Auditor QS tile to your new KA app in the next build. Installing the zip on the current build and using the QS tile cause the systemUI to crash because the old app is missing now.
[Moto Maxx Android Development] ChrisMirza:
Bhb, when I try to add profiles based on apps the KA simply closes. No crash, no error, it simply closes.

Enviado de meu Moto MAXX usando Tapatalk
[Moto Maxx Android Development] Latiken:
KA hangs on asking for SU perms. Installed the KA update zip.
[Moto Maxx Android Development] immadeofpixels27:
Happened to me, too. I rebooted again (idk if that's necessary). The 'vanilla' KA was also installed for me after updating, see if it is for you and if so uninstall it and use the new one (remember it's named BHB27 Kernel Adiuter)
[Moto Maxx Android Development] fgl27:
works for me you need to check my post pic, there is a specific pic abou SKA per app monitor you need to give the app access.

no su hang for me fallow the recommendation... my su is set to just grant permission not ask, but that is not the problem...
[Moto Maxx Android Development] immadeofpixels27:
Used the zip, as I'm running RR. The weird thing is that I can't seem to find SuperSU in settings, and it shows not installed in play store. If I install it and convert to system app, it disappears after reboot.. Can't tell if that was happening before I used the zip.
[Moto Maxx Android Development] fgl27:
there is no connection to my zip to su disappearing. :eek:. you probably update su wrong via play, just download a su zip and flash it. go to su thread on XDA.

I flash that zip dozens of time testing the new app no problem ever...
[Moto Maxx Android Development] immadeofpixels27:
Yeah I don't think it was related to the zip, but I didn't notice until KA hung on waiting for su access. This has happened before on your ROM, but installing from Play store and converting to system app worked that time.
[Moto Maxx Android Development] iiWoodstocK:
Flashed the .zip with no issue. Opened the app, granted SuperSU and set up my configuration. So far everything is good
[Moto Maxx Android Development] Latiken:
I tried reinstalling the two zips, and wiping cache and dalvik which did not work; SuperSU was completely deleted.

I installed it from the Play Store which seems to have fixed it. I can now use KA.
[Moto Maxx Android Development] streebs87:
I also had to install SuperSU from the Play store because it was gone. Everything seems to be working just fine though.
[Moto Maxx Android Development] Latiken:
Seems like several people are experiencing this issue.

I think it may have to do something with our SU binaries not having been updated, since I remember I never bothered to update them.

That may be the issue; I have no idea what else it could be.

It's an easy bug to fix at least, and SuperSU merges back into settings nicely.
[Moto Maxx Android Development] newbe1droidx:
After making recommended changes do I need to enable on boot for each setting change. Thanks
[Moto Maxx Android Development] richii0207:
With intelliactive, add a zero to the frequency missing it. Or just replace the entire line with the correct frequency. The configuration for that setting is wrong, which is trying to ramp the frequency to 172 which does not exist which is most likely causing the freezing.

Intelliactive is made by one of the most recognized kernel devs that knows his stuff. Most of the governors nowadays are just a config edit or two with a name snapped on it by a random user. If anything, this one should run more flawlessly than the random governors, given the proper tuneables.
[Moto Maxx Android Development] raspdeep:
Where do you change the frequency from? I'm assuming you use KA?
[Moto Maxx Android Development] Latiken:
If you want to keep the settings then yes.

Keep in mind that certain settings (I think only CPU Voltage) survives a reboot even without apply on boot enabled. Be careful when undervolting.
[Moto Maxx Android Development] KuroIgunashio:
The lastest version of Kernel Adiutor not works in RR Lollipop (causes Force Close), for now i run the +01 version without problems.

Enviado desde mi Moto MAXX mediante Tapatalk
[Moto Maxx Android Development] richii0207:
Ya, under the tuneables in the CPU section.
[Moto Maxx Android Development] raspdeep:
I've look through the tuneables but didn't see which one you were talking about tho. Which parameter did you change to 1720?
[Moto Maxx Android Development] richii0207:
I saw that the configs for the two_step_freq was missing a zero. You can try to changing it and see if that helps with the freezing. If not, then there another underlying issue. It's a shame in that case as that governor by Faux is amazing.
[Moto Maxx Android Development] gimpy1:
A couple of days ago, I flashed bb's kernel, but have been using it as flashed with no tweaks. Today I decided to use his performance tweaks in post #2. But first I ran an antutu benchmark test. The result was a reading of 66473. The one prior to that one yesterday was 61614. I did the tweaks as close as I could and then "enabled at boot" just the ones I tweaked.

I rebooted and let the phone set about ten minutes, then ran antutu. The reading I got after the tweaks was 84836. I think that is quite a large difference for one quick test?

I do have a couple of questions on setting up the kernel? I only have enabled the ones that I did the tweaks on. Do I need to enable all of the others even though I did nothing to them?
[Moto Maxx Android Development] newbe1droidx:
I think you only have to enable on boot if you make changes as others are still default settings
[Moto Maxx Android Development] gimpy1:
Ok, Thx.
[Moto Maxx Android Development] Latiken:
I'm running the latest test and I have noticed even more reboots than before.

This is beyond frustrating.

If it continues I'll disabled all undervolting and test.
[Moto Maxx Android Development] iiWoodstocK:
I think it's a combination of everyone's kernel settings like CPU governor and undervolting, etc. because I still am not experiencing any reboots.

Out of curiosity, those of you who tried my kernel settings, how's that working so far?
[Moto Maxx Android Development] raspdeep:
Not sure if this is the right one?
[Moto Maxx Android Development] raspdeep:
I've tried your setting, it seems to be more stable but zzmoove is too laggy so I didn't use it for long. Dt2w requires 4 taps to wake after device is sitting for a while which is quite annoying. I'd prefer a governor that is quick to response and multitasking so now I'm trying intelliactive but lower max frequency to 1.7ghz. Ui is responsive but still testing on battery life
[Moto Maxx Android Development] iiWoodstocK:
FYI, zzmoove is not the governor I recommended, it's yankactive. I chose that because it's battery friendly, but more geared towards performance so no lag.
[Moto Maxx Android Development] raspdeep:
Oh yankactive is also laggy but little better than zzmoove. Does d2tw need 4 taps to wake at times?

However, I do keep the rest of ur recommended settings while testing. So far no reboot or freeze yet. Intelliactive is responsive even with lower max frequency. Drawing avg of 300mah instead of 500 600mah with screen on while surfing
[Moto Maxx Android Development] iiWoodstocK:
Occasionally dt2w won't wake on the first double tap, but that's usually only when my phone has been asleep for a very long time. Otherwise any other time it wakes on the first double tap.
[Moto Maxx Android Development] raspdeep:
Cool.. Will share more info after few days testing again
[Moto Maxx Android Development] Latiken:
If anyone is willing to try my settings here you go:

Performance based.

CPU: Zzmoove, profile 8

2572MHz Max, 422MHz Min

Schedule work queues enabled.

Undervolt -70mV

GPU: Simple-ondemand

600MHz Max, 200MHz Min

Gaming mode enabled.

Thermal: Intellithermal

Frequency Throttle 70°C

Core Throttle 75°C

Hotplug: IntelliPlug

Cores: Balanced.

Hysteresis Value 8.

If anyone experiences or doesn't experience reboots on these settings let me know.
[Moto Maxx Android Development] neur0tk:
I had system UI FC a few times not sure if it's from a theme or not :) I'll revert to stock theme
[Moto Maxx Android Development] Jarbas santos:
kernel BHB27

this kernel works in stock rom 5.0.2 lollipop?
[Moto Maxx Android Development] Shooting Star Max:
This does not work with stock. Use CM or RR.
[Moto Maxx Android Development] Jarbas santos:
this kernel works in stock rom 5.0.2 lollipop?

---------- Post added at 02:16 PM ---------- Previous post was at 02:12 PM ----------

obrigado pela informação, ja ia fazer o flash
[Moto Maxx Android Development] fgl27:
Kernel Adiutor update

KernelAdiutor-0.9.9.4.+03.BHB27-Mod.apk​

Same as above but this version I fix the app not open on 5.1.1 and under...

No need to update if install V 0.9.9.4.+02 on MM.
[Moto Maxx Android Development] Fezorzo:
I got some random freezes every 2-3hrs on CM13, the phone hangs for like 7-8 seconds and then comes back to normal, using the governors darkness, Nightmare and Intelliactive, although it may happen in more governors 'cause I haven't tested any other besides that and Interactive. Other than that I had no issues with the kernel
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V127-CM-RR-L.zip​

Lollipop only.

Changelog

Download BHB27-Kernel for L

Bug report: make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.

I make a Mokee version tomorrow or late this week...
[Moto Maxx Android Development] immadeofpixels27:
Is this version also compatible with MM? Or is it just a port of the latest 126 test kernel for L?
[Moto Maxx Android Development] raspdeep:
I used to have this problem but after using the settings suggested by [MENTION=7109882]iiWoodstocK[/MENTION], the freezing went way.

http://xdaforums.com/showpost.php?p=65719915&postcount=431

You can change the governors but keep the rest of the settings (except cpu undervolting which you should adjust depending on how your phone reacts to it but I'd suggest to leave it at stock for the period of testing until stable then you start tweaking it) and it should be good.

Hit him with lots of thanks btw :)
[Moto Maxx Android Development] raspdeep:
OK, I've tested my settings for about 2 days and it seems pretty good and stable. Do note I'm using these settings for testing because I want a responsive UI (where zzmoove are too laggy for me), d2tw should wake on first try, good battery life. I do not play much games (only CoC at times) and these settings works great for me. The base settings comes from here by [MENTION=7109882]iiWoodstocK[/MENTION] except for the following changes

1) Governor changed to intelliactive

2) CPU max at 1574 or 1728mhz

Results are on screenshot. About 6.5 SOT with wifi and LTE usage mixed. I do whatsapp, viber, surfing, some youtube videos, email syncs, pushbullet, pushing messages to my pebble watch via bluetooth.

Feel free to try and post your results and any comments so we can continue to share :laugh:
[Moto Maxx Android Development] ChazzMatt:
Read the post. ;) You actually quoted it when asking the question...

Also there's a changelog link IN that post for your other question. So, go back and read the post.
[Moto Maxx Android Development] immadeofpixels27:
Didn't see that lollipop only part, it just looked like part of the filename since there wasn't even a space...

As for the changelog, the fact that the first bullet states "included all stable changes from M" and then there are more entries confused me.
[Moto Maxx Android Development] ChazzMatt:
There IS a space. It's a completely separate line in [MENTION=5747496]baybutcher27[/MENTION]'s the post. :rolleyes: Don't make me post a screenshot of his post.

You just didn't read it before quoting it.
[Moto Maxx Android Development] immadeofpixels27:
XDA Labs app didn't parse the text properly, and I was in a hurry. My bad.
[Moto Maxx Android Development] ChazzMatt:
[MENTION=5747496]baybutcher27[/MENTION], according to the changelog this version has busybox?

My phone went crazy when I installed this -- even though I wiped all the caches and re-flashed SuperSu before re-booting. ;) My alarm rang, went off, rang again. my once-per-day scheduled autoboot kept triggering and re-booting the phone, etc.

Luckily I read the changelog, so suspected why. I already have a busybox app, which installs busbox -- so there was some kind of conflict.

BusyBox by Stericson

https://play.google.com/store/apps/details?id=stericson.busybox&hl=en

I've used it for years. Sure, enough when I opened that busybox app, it said it detected another busybox installation with a custom kernel and asked if I wanted it to take care of the situation?

I said yes, then rebooted and everything has been fine since.

So, just FYI for anyone who already has busybox installed.
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V127-1-CM-RR-L.zip​

Lollipop only.

Minor fix over V 127.

Changes:

Ajust start script for lollipop

Fix intellitermal not enable at boot.

Disable umbrela core as default cpu gov, to prevent lock on a low frequency.

For some reason the governal Tunables (hispeed_freq) is be lock in some low frequency in some governors...

If the frequency is not achieving the max set check for governal Tunables (hispeed_freq) and set that to the max.

Change that or, change the governor or even put the device to charge fix that..

If there is another problem on the kernel let me know on this thread.
[Moto Maxx Android Development] fgl27:
Yes there is a build in busybox, the main reason is to support init.d as on CM in general is broken in most devices, I tested and know init.d is work ok.

I used the same busybox as BusyBox On Rails app.

The recommendation must be to uninstall not the app but the busybox via the app that the user use to install busybox then install this kernel... In my test there was no problem when I test this kernel with a busybox from a app that is way I not ask for remove just post that warning, but I did not test with that busybox app you post.

:good:
[Moto Maxx Android Development] gimpy1:
Just an fyi. I use V4A from guitardedhero's installs. I did his latest update just now which caused the phone to go into a boot loop. I am on RR 6. and was using your latest kernel. I had to reflash your rom to get out of the boot loop.

I then flashed the V4A update, then flashed your kernel update. All is good now. I'm not exactly sure what caused the boot loop. Now, I have the best of both worlds, latest v4a update and your latest rom and kernel. ?
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V128-CM-RR-L.zip​

Lollipop only.

Changelog

Download BHB27-Kernel RR-CM

Download BHB27-Kernel Mokee

Use the below app to be able to disable BCL cpu hotplug

Bug report: make with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.