yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V42​

Nougat and Marshmallow, Custom and Stock ROM.

Download BHB27-Kernel Click here

Changelog Click here

Note:

Use this with the latest version of my mod KernelAdiutor-0.9.9.4.+37 or up to control the many featuring of the kernel.

Download Kernel Adiutor App

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

Always post a bug with [MENTION=5747496]bhb27[/MENTION] and a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

If the device Random reboot all the logs are lost so just described like I ask above
[Moto Maxx Android Development] ChazzMatt:
You can also dirty flash the ROM and temporarily revert back to "stock" kernel, just to see. Run it for a couple of days. If you still have shutdowns, then yes it's probably the battery.

IF you don't have any shutdowns, then you know the "safe" settings in the stock kernel are OK, and you can go back to using the custom kernel but you will have to adjust your settings to find out what's causing the shutdowns.

As an examples, some phones don't like undervolting.
[Moto Maxx Android Development] Septfox:
What do the Speaker Driver Leakage and Headset High Performance Mode options do in the aduitor? The description for the former especially is pretty vague.

Maybe kernel-related, probably not: why does our device not react to headset inline volume controls? Does the hardware simply not measure anything on the mic line aside from "on" and "short-to-ground", or is it something that can potentially be fixed through software?
[Moto Maxx Android Development] fgl27:
both do the same, kernel side sw to improve or avoid audio distortions...

I don't have a headset with that to test, is a really basic thing the config is on the ROM side and is there, if it doesn't work need to know if any one can make a headset with that featuring to work to know if the device has or not the proper support working.
[Moto Maxx Android Development] Septfox:
If they're improvements, why not enable them by default? Are there potential downsides to using either of them?
[Moto Maxx Android Development] gangrenius:
My Bluetooth audio is horrendous

Bumpn gums from my vzw DROID Turbo xt1254

---------- Post added at 01:01 AM ---------- Previous post was at 01:01 AM ----------

I might need to flash a mod because it's that bad on my vzw turbo

Bumpn gums from my vzw DROID Turbo xt1254
[Moto Maxx Android Development] kitcostantino:
while they are *improvements* they may not *always* cause desired effects. at least, i am fairly certain that is the methodology at play.

i have used both of those options and not noticed any drastic improvements, nor drawbacks, but the differences are subtle. perhaps a little higher volume with less distortion is the best way to describe what it does for my quark when i enable those two.

Giving us the option to flip a switch for a setting only some want or may find beneficial versus changing a default setting eliminates having said new setting being blamed for issue x,y,z that does not exist.

i understand the idea and honestly i agree with the mentality of 'if its better, then why not?' but i also understand where devs are coming from considering the blame-fest that seems to ensue whenever an undereducated user has an issue and lacks the skill to communicate beyond vague general descriptions like 'my bluetooth headset doesn't work right on this ROM'. if i were a dev, i would want to be able to say "no changes were made to audio.. you did that yourself, genius". i think that is why the default settings have remained pretty much the same the life of the quark RR ROM. it is a smart move, honestly. avoids dummy users complaining. well, at least i am pretty sure that's why. ;)

many thanks to [MENTION=5747496]bhb27[/MENTION] for the continued efforts.
[Moto Maxx Android Development] Septfox:
Yes, that's...that's why I asked if there were any potential downsides to using it.

I like to think I'm a reasonably educated user, at least educated enough to be dangerous to myself. Thus why I requested clarification on what they specifically do and if something could blow up if they were switched on and left on.

It was also curiosity; I'm really curious about what software workarounds are at work here.

I would guess that the "Headset High Performance Mode" either throws more resources at audio processing, or actively shapes the audio going out to reduce the volume on frequencies that the SoC doesn't handle well. Or is it instead something like what's described here?

"Speaker Driver Leakage" is even worse...to what driver are we referring to? The software driver? The physical driver (part of/most of the speaker itself)? Which speaker; the loudspeaker or earpiece speaker? What does "leakage" even mean in this context? The only thing I can seem to find online is this.

If it seemed like I was just blindly demanding to know why everything apparently nice and desirable wasn't on from the get-go or wasn't immediately fixed and polished so it could be...I apologize, that wasn't my intention. I really just want to understand what's behind the switches. The Google has provided very few answers.
[Moto Maxx Android Development] kitcostantino:
lol. no, man. ive seen many of your posts over my time at xda and i know you know your stuff and know what you're doing. ;) whenever i post, i try to phrase whatever i say to where it will retain it's usefulness over time or possibly help others that stumble upon it later . i truly did not mean you specifically or even in a general sense. i had a specific (unrelated to you completely) scenario in mind. apologies if that's how it seemed, totally not my intent in the least.

honestly, i cant speak to what the exact processes are in those two. while i have seen that before, i do not even remotely know what the workaround is specifically. after re-testing it for shiggles, i can say i lost bluetooth audio on my quark today after applying them (the irony, right?) , but then regained it after a reboot.

my best guess, though is the gain is being adjusted and the "workaround" has to do with the signal processing itself. ive never looked too hard for an explanation, but i have never seen one.
[Moto Maxx Android Development] Marky__Mark:
I had it which is why i went back to stock.
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V43​

Nougat and Marshmallow, Custom and Stock ROM.

Download BHB27-Kernel Click here

Changelog Click here

Note:

Use this with the latest version of my mod KernelAdiutor-0.9.9.4.+37 or up to control the many featuring of the kernel.

Download Kernel Adiutor App

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

Always post a bug with [MENTION=5747496]bhb27[/MENTION] and a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

If the device Random reboot all the logs are lost so just described like I ask above
[Moto Maxx Android Development] 3Dota:
there's new xt1254 kernel ... any chance it will be implemented?

https://xdaforums.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795/post71247262
[Moto Maxx Android Development] fgl27:
Moto doesn't released they sources quickly takes a lot of time.

I expect very little changes, does this kernel works on that updated ROM?

It must.
[Moto Maxx Android Development] gangrenius:
Can I flash that second zip he shared that just has the modem img and fag img and other thing? On RRremix xt1254?

Bumpn gums from my vzw DROID Turbo xt1254
[Moto Maxx Android Development] fgl27:
don't know, try and report do the proper backup first.
[Moto Maxx Android Development] gangrenius:
I flashed and it updated my modem but I had to flash the OS and kernel again because the package had stock kernel and it was not compatible with RRremix but I have the updated modem now for xt1254

Bumpn gums from my vzw DROID Turbo xt1254
[Moto Maxx Android Development] jcarter3729:
Is there a way to go back to stock kernal without reflashing the whole Rom again?
[Moto Maxx Android Development] fgl27:
no we don't have a kernel that is boot.img only there is modules that are in /system/ so you need to re flash the ROM zip or restore a before backup, there is no way around it.
[Moto Maxx Android Development] Chinnu1103:
I flashed the kernel v43 with the latest RR7.1 update but the CPU frequencies are changing continuously and the maximum frequency is coming to only 1190HZ. It is also not letting me change the maximum frequency..

When I clean flashed the ROM again without the kernel, the problem is not there..

But I like this kernel a lot.. what should I do?

It is a problem due to intellithermal? But it is in default values..
[Moto Maxx Android Development] Debuffer:
It's thermal. I use intelli thermal with 70 and 85 custom values.
[Moto Maxx Android Development] Diego1751:
oh boi that gets hot doesn't it? on my xt1254 the screen actually can get hot enough that it hurts to touch if I forget Im turbo charging and I start doing lots of stuff
[Moto Maxx Android Development] Debuffer:
It doesn't get too hot here. Maybe because of my configurations
[Moto Maxx Android Development] fgl27:
Are you charging and or "heavy" using it (games, 4g, high resolution video play or just a heavy app for too long)? the below helps, thermal-engine. never fails me...

you are not supposed to charge using the Turbo charger and use the device, it will make it explode (but not really) :silly:, but will make it hot and can make it too lag to use, using a 1A max charger or USB charge it to a PC will not cause a too big lag.

at least on my end I have play games on USB pc charge without problems, but using the turbo I had a reboot because of the over heat....

I always use default thermal option aka thermal-engine no problemo.
[Moto Maxx Android Development] Diego1751:
Does this kernel have bln?
[Moto Maxx Android Development] fgl27:
what supposed to be that?
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V44​

Nougat and Marshmallow, Custom and Stock ROM.

Download BHB27-Kernel Click here

Changelog Click here

Note:

Use this with the latest version of my mod KernelAdiutor-0.9.9.4.+37 or up to control the many featuring of the kernel.

Download Kernel Adiutor App

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

Always post a bug with [MENTION=5747496]bhb27[/MENTION] and a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

If the device Random reboot all the logs are lost so just described like I ask above
[Moto Maxx Android Development] Diego1751:
Back light notifications for the capacitive buttons
[Moto Maxx Android Development] fgl27:
and what makes you think that is a kernel thing?
[Moto Maxx Android Development] mohangj:
Does BHB27-Kernel-V44.zip support Quark Stock 6.0.1 Indian Rom
[Moto Maxx Android Development] 3Dota:
yes ...
[Moto Maxx Android Development] Diego1751:
When I searched for it the other day I'm pretty sure that I saw it needed kernel support, I think I saw that answer earlier in this thread. My apologies if that's wrong

Also by the way everyone: I have been using these settings after a good amount of personally testing and getting pretty excellent battery life and very good performance for my use cases, I have almost no noticable lag or problems (outside of themes not applying lol but NVM) Lots of short quick multitasking, lots of music playback over BT, some Snapchating and pretty regular user. Chrome, syncing, messaging, Dt2w etc

CPU 268-2688, zzmove Prof #5, state notif & power efficient wk que, CFS power save, all boosting off.

Undervolt -5(do your own testing)

Hotplug: Auto Smp: down 70% up 90%, cycle down 1 up 3, delay 30ms, Max CPU 3 min 1

Gpu power save, Max 600

I/O Row read ahead 3072 RQ on

Lmkiller bhb27 recommend

(Currently testing fsync, CRC, logging, laptop mode, and etc effect battery life and performance now that I have a stable set up that works well)
[Moto Maxx Android Development] lazlow_og:
Yes it has. ;)
[Moto Maxx Android Development] Einheit-101:
Either TWRP or this Kernel destroyed my device, i flashed everything pretty fine and the device boots, but i have no WiFi anymore and my MAC Adress is 02:00:00:00:00:00

There is absolutely no way of repairing WiFi, no re-flash, no ROM, nothing helped so far, seems like a partition is damaged which is not updated by any ROM that i install.

And i am 99% positive no one here ever heard of that issue^^
[Moto Maxx Android Development] Debuffer:
Flash the modem.
[Moto Maxx Android Development] Einheit-101:
I actually fixed it suddenly by flashing MCG24.251-5-5

Looks like MPG24.107-70 isn't compatible for some reason, or do you really have to Flash the Modem separately??? That's stated nowhere. Only ROM+Kernel.
[Moto Maxx Android Development] fgl27:
can you be the problem, TWRP will do anything unless you ask it to do it, so what have you really done?

the only thing that can break wifi like that is if you flash the kernel then for some reason, change your boot.img for another one by restoring a backup flashing a zip that has a boot.img, quark kernel is not just a boot.img it is too big there is part that are in the system included the wifi, changing the boot.img after flash this kernel makes the wifi drivers in system incompatible with with the kernel of the new boot.img, is all in the op, or you had done something wrong or some file miss to flash and you miss reading the logs and TWRP screen.
[Moto Maxx Android Development] mubaidr:
This might be happening because of damaged wifi module, lg g3 had this very problem and it was common for that model. Same happened in that case wifi mac address was assigned: 02:00:00:00:00:00
[Moto Maxx Android Development] Einheit-101:
Could a try to install Magisk cause it?

I simply flashed everything fine, everything worked, and I gave Magisk a go because why not. Device didn't boot, I restored a backup of the stuff that I flashed just before flashing magisk because I ain't that stupid. Most likely there went things wrong. But anyway it works great now^^
[Moto Maxx Android Development] fgl27:
so you make something that makes the device not boot, they you just complain about everything else without disclosing the problem that you cause?

you are fun...:good:
[Moto Maxx Android Development] Psykopato:
É normal o modo de alto brilho desativar sozinho?

Estou com a ultima versão do kernel e do adiutor, seto o modo alto brilho, porém algumas vezes, quando desligou a tela e seta pra desligado.
[Moto Maxx Android Development] Einheit-101:
Well the backup repaired the boot back then, it was just the wifi that was broken. Couldn't imagine Magisk breaks something that bad that even a reflash doesn't solve it afterwards.
[Moto Maxx Android Development] Shadowmancer_br:
Magisk isn't compatible with our device, flashing it will aways cause bootloop and corrupt the ROM.
[Moto Maxx Android Development] ceelos218:
I'm running magisk just fine.. on AEX rom for quark.
[Moto Maxx Android Development] fgl27:
Like supersu you can flash latest version of supersu or magisk on custom ROM, but on stock is need a old version of supersu before to make supersu to work, regarding on how to make magisk to work on stock I have no idea but the principal is the same, magisk dev must be informed about it, there is a lot of people working on magisk informing on github they will take care of it.

as magisk uses a lot of supersu scripts to install things they probably use the latest latest, so they must do some workaround with older scripts to fully support some moto devices, as others moto devices have this same behavior regarding supersu, they all must have regarding magisk so eventual the fix will came...
[Moto Maxx Android Development] Einheit-101:
TheSt33v already gave everything to the Magisk devs, i'm pretty sure a fix will come but i am not in a hurry, i just would like to use S-PushTan along with xPosed and root before July 2017, because then SMS TAN will be disabled here in Germany. And to use S-PushTan i need to hide Root+XPosed, because some company developers are beyond stupid and block root users.
[Moto Maxx Android Development] Shadowmancer_br:
Thanks for the info, seems I'm outdated :silly:
[Moto Maxx Android Development] zys52712:
Any chance of getting a kernel update from 3.10.x to 3.18.x?
[Moto Maxx Android Development] gangrenius:
[emoji23] [emoji23] [emoji23] [emoji23] [emoji23]

Bumpn gums from my vzw DROID Turbo xt1254
[Moto Maxx Android Development] fgl27:
that is not how update of linux works.
[Moto Maxx Android Development] vinydasilveira:
My Quark is heating up fast. It reaches 60°c and the power drops to 1574mhz CPU and 500mhz GPU. So far so good, does not influence the performance with regard to the games. These latest versions of the bhb27 kernel no longer make 90k on antutu, and 3D performance has dropped. I know it is difficult to balance power, battery life and stability, but these latest updates Quark lost power and battery life, stability is the same. I'm going back to the old versions. Any way, thanks for everything. Do not get me wrong, it's just the opinion of a hard user.
[Moto Maxx Android Development] Einheit-101:
Super SU wanted an update - did it - rebooted - root lost - reflashed super SU - bootloop^^ haha

I simply restored a backup, but should we better not update super su?
[Moto Maxx Android Development] Marky__Mark:
Installed the latest and the phone died after every reboot as soon as the lock screen came up. I think the battery stats were messed up. Do we need to have a full charge when installing this? Im glad a did a backup because it completely borked my phone. Im on the last cm13 snapshot.
[Moto Maxx Android Development] fgl27:
Kernel Adiutor update

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

Download Kernel auditor

Changelog

Installation

Just Install the apk on any ROM enjoy it.

If encounter any problem:

Clear data of yours BHB27 Kernel Adiutor app + deleted the KernelAdiutor and KA_profiles folder from internal memory (if not possible by the android file manager use TWRP one), reboot to recovery and clean/wipe Dalvik and cache before reporting things.

You can make a copy of profiles.json file inside KA_profiles folder (in case you save a profile), after the reboot place it back on the folder then apply the setting on the app, if encounter problem after the apply the profile is the problem deleted it and redo the cleaning and don't use it again...

This helps when the apps functions are odd, misbehaving and or slow to load/display.

Sharing profiles

The only thing need to share a profile is the file profile.json in side KA_profiles folder, it can be just simple copy and past to another devices, the file is very small and easy to share.

Use my version of Kernel Adiutor to better support this Kernel. :good:

[IMG="XDA Labs"]https://img.xda-cdn.com/oshFRo1rSEHTP5__wCXMO3e3u-I=/http%3A%2F%2Fimgs.xda-labs.com%2F0621sigs%2Flarge%2Fcontributor.png[/IMG]
[Moto Maxx Android Development] fgl27:
BHB27-Kernel-V45​

Nougat and Marshmallow, Custom and Stock ROM.

Download BHB27-Kernel Click here

Changelog Click here

Note:

Use this with the latest version of my mod KernelAdiutor-0.9.9.4.+38 or up to control the many featuring of the kernel.

Download Kernel Adiutor App

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

Always post a bug with [MENTION=5747496]bhb27[/MENTION] and a log .zip

BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP

If the device Random reboot all the logs are lost so just described like I ask above
[Moto Maxx Android Development] monza1412:
Hey [MENTION=5747496]bhb27[/MENTION], as always thanks for your work, but I'm having some random reboots in the latests versions of your kernel (v44, v45, probably some other older ones), I can not give you more detail, as they are, as I said, random. With no particular app, the phone just freeze and reboots by itself. I believe that happens more frecuently with heavy memory/cpu apps like chrome, remote desktop, etc.

The funny thing is that in your vanilla CM kernel, I don't have any of this reboots problems, I was running calsurferpunk unnoficial LOS and all was working flawless, so I intend to believe that there is something added that mess things up, I'm currently switching off some kernel options trying to identify the reboots cause, but I'm kind of lost. (already tryed disabling BCL,CPU Efficiency Flags, I'm currently suspecting from the thermal engine, or the power saving flags).

I must say that's not an insolated 7.1.1 thing as I already have some reboots in the stock verizon 6.0.1 a while ago, I believe with the v43 or v44. Can't remember exactly.

I know that kernel logs are erased with reboots, but maybe I can provide the console_ramoops logs, I believe that franco use those logs in these particular situations.

Please don't take it the hard way, I'm not trying to bash your work or be some kind of a dickhead, just sharing my own experiences.
[Moto Maxx Android Development] Competentpsycho:
Not sure what ROM you are on, but check for this setting: Developer options -> Store logger data persistently on device

There is another setting right above it which controls how big it will let the logs get.

Then reboots won't wipe the logs and you might be able to get some useful logs for this.

However it may be your battery. I had similar issues before replacing mine. BHB kernel likely undervolts and may be a bit more aggressive compared to stock kernel you are using and it likely gets to a point where the older battery can't supply the necessary voltage as consistently during intense apps/processing with increased current draw. You can check by overvolting slightly from what you currently have set, and maybe decrease clock speeds/screen brightness and see if it happens less. I haven't had the reboots since I replaced my battery and have gotten much improved battery life that doesn't shut down at around 20% anymore.
[Moto Maxx Android Development] monza1412:
Thanks for the hint, I will definitely check it out :good:

As for the battery, I don't know, I have taken good care with it, no fast charging, not complete charging/descharging cicles, so I'm assuming battery degradation should be minimal-

Strange thing is that cm kernel three also has under-volt capabilities, only bhb can confirm if the under-volt present in both ramifications of the kernel it's the same or if it's something else involved. :confused:

I'm methodically testing with only a couple of added options disabled (currently CRC and Fsync only), I will see in the upcoming days if there is some relation involved with the random reboots or not.
[Moto Maxx Android Development] lazlow_og:
Hows the battery life as compared to stock 6.0.1 kernel?
[Moto Maxx Android Development] fgl27:
chrome is a very common app everyone uses it, I do, I also do use some others app that can really cause stress on the device like stress test for cpu ,gpu and ram as I do make changes related to it I always test for different scenarios, and I never ever have a reboot during light, heavy or stress test use so the kernel is not the one to blame at least on my device, may something else you did that is causing a incompatibility I have no idea, yo need to tell me a situation were is good then is bad, because the stock kernel and custom kernel have over 3000 changes I can't find one to blame with your descriptions...

undervolting options are all the same if you don't ever change a thing there, is all in stock voltage for your device...

so if you say you have problems on more then one ROM, muts be a case of some app some change you use, and no one else seems to use as I don't have problems or reports about it... try to find a cause if there is and let me know so I can work on something...

if you can find a stable version of my kernel for you that also helps..

btw I always run whit CRC and Fsync on the off position, so that can't be a problem...

:good: