yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] wizardknight:
I am probably getting a 5-10% gain, but the gains you see will vary by all the usage unique to your phone.

The risk is crashing whatever process is running, corrupting data, or causing your OS to not boot.

Just like overclocking, take it down a small step at a time to find the sweet spot, and you should be fine.

The big advantage for me is the reduction in heat the phone generates.
[X Style (Pure) Android Development] XDleader555:
In kernel Aduitor, go to CPU voltage, and then tap the voltage you would like to adjust. Alternatively, swipe the banner to the left where it says apply on boot to set a global voltage offset.
[X Style (Pure) Android Development] ACardAttack:
Has the bluetooth streaming and audio issues that this seems to cause with CRdroid and Resurrection remix been fixed?
[X Style (Pure) Android Development] mddunner:
I have had good results with the msm releases. No Bluetooth hiccups like before. I'm on cr Droid 3.5
[X Style (Pure) Android Development] lknnnn:
maybe the highest score on gb4
[X Style (Pure) Android Development] lknnnn:
Unfortunately the voltage of a53 cluster cannot be lower.
[X Style (Pure) Android Development] t895:
That's really impressive, but how's your battery life?
[X Style (Pure) Android Development] Alibaba0101:
Has anyone noticed that the two big cpu's power down on lineage os after the phone goes to sleep? I thought it may be kernel related, but after installing handbag kernel and making sure the governer is set for performance the same thing happens. After sleep, both core 5 and core 6 usage goes down to practically zero. That's also when i believe the phone becomes sluggish and i believe the bluetooth issues are related. I set the governor for core 5 and 6 to performance, but it didn't appear to make any difference. The behavior is still the same. After restart core 5 and 6 act normally, as soon as the phone goes to sleep. Their usage goes to zero and they never recover after that.

Anyone else?
[X Style (Pure) Android Development] XDleader555:
There's a bug on the big cores where voltages between 302mhz and 633mhz are tied to 633mhz. if you want to undervolt the big cpu, undervolt A57-633mhz.

Trying to find time to debug everything.
[X Style (Pure) Android Development] lknnnn:
And today the Android system keeps waking the phone，is this another bug？I tried clean install，it didn't help.

:eek:Sorry.It is because of my network error，not the kernel.
[X Style (Pure) Android Development] Alibaba0101:
big cores

so after changing the big core governer to on demand and making a few tweaks, the big core are acting more normally as opposed to staying in a powered down state most of the time.
[X Style (Pure) Android Development] HPAR:
Every time I change the RGB values, some time later they return to the default value, even if I reboot and set to apply on reboot

(Lineage 13 and hand bang 2.3.3)
[X Style (Pure) Android Development] Andvark:
I assume that you are using Kernel Adiutor for setting the RGB values.

I found that the RGB values were reset every time the phone was locked and then unlocked, but the other display settings were left intact. Turned out that the LiveDisplay RGB settings were being rewritten every time the display was turned back on. I got around the issue by setting the desired RGB values in the Color Calibration section of the LiveDisplay settings (RR 5.8.3).
[X Style (Pure) Android Development] dzidexx:
Turn off live display, auto brightness & outdoor mode

or don't touch RGB values.
[X Style (Pure) Android Development] Andvark:
Those things are already disabled. The Color Calibration (RGB) settings are still enabled; I've found no way to disable it.
[X Style (Pure) Android Development] dzidexx:
[MENTION=6541979]Andvark[/MENTION]

If you disable(what I wrote) you can change rgb,

If those are enabled rgb is changing auto(night, day, sun, clouds ...).

In KA I change only: minimum RGB, hue, screen value.
[X Style (Pure) Android Development] Andvark:
Thank you for your instructions, but I also need to set the RGB values from within KA. I have several display profiles defined in KA that I access through a KA Profile widget.

I gave up trying to get this to work with RR (other ROMs like AICP don't have this issue, at least when I last tried them). I was just attempting to answer another user's question regarding this issue.
[X Style (Pure) Android Development] dzidexx:
These were not instructions.

I do not know English well.

[MENTION=6541979]Andvark[/MENTION]

You wrote was working on AICP - with handbag 2.3+ or aicp kernel?
[X Style (Pure) Android Development] Andvark:
With AICP kernel. The only reason I used handbag with RR was for handbag's KCAL support (RR's kernel does not have KCAL support).
[X Style (Pure) Android Development] dzidexx:
You can try simple kernel - 1.2 & 1.3 also has it.

Restore RR kernel first. [MENTION=6541979]Andvark[/MENTION]
[X Style (Pure) Android Development] HPAR:
I did something that worked. In kernel adiutor I selected the value from red to 240, green to 240, and blue 256. On the live display I selected the corresponding percentage in k.a .. For some reason, even after restarting, the values ​​does not return to the default.
[X Style (Pure) Android Development] Andvark:
I had also done this, which is how I determined that the RGB values were coming from the live display settings and overriding the KA settings. Unfortunately it isn't a viable solution when you have more than one display profile defined in KA as I do (I access them through a KA Profile widget).
[X Style (Pure) Android Development] lilcdroid:
Kernel source for the Moto X Clark 7.0 Nougat.

https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPH25.200-15
[X Style (Pure) Android Development] Vink67:
Briked_hotplug let the big and little cpu to 600mhz.

Never goes up.
[X Style (Pure) Android Development] clarkcant:
I've been around the block when it comes to flashing ROMs, but I've never flashed a kernel. Does anyone have the patience to explain what a kernel is and what the benefits/drawbacks of flashing one are?
[X Style (Pure) Android Development] rowlers:
http://www.makeuseof.com/tag/consider-using-custom-android-kernel/

Plus - more options, potential for more battery life, more performance potential?

Negatives, more opportunity to screw something up, maybe not as stable?
[X Style (Pure) Android Development] noisufnoc:
Quick observation, CPUZ seems to cause a reboot on my phone.
[X Style (Pure) Android Development] t895:
What ROM and kernel are you using? I just tried it and it caused a crash on RR with HangBag msm 2.3.3
[X Style (Pure) Android Development] noisufnoc:
Lineage OS 14.1-20170731-NIGHTLY-clark, and HandBag-msm-2.3.3-20170731-1546
[X Style (Pure) Android Development] t895:
Ok, so I just checked it with the stock kernel for RR and there's no crash. Is there anything I could provide to help diagnose it?
[X Style (Pure) Android Development] noisufnoc:
I appreciate the offer, but I'm rolling back to the LOS kernel right now. I'm fighting an issue getting my phone to charge at a normal rate and want to factor out any unnecessary variables.
[X Style (Pure) Android Development] t895:
What are you using to check the rate, Ampere? And if so, what's the rate?
[X Style (Pure) Android Development] noisufnoc:
I'm using Ampere, I was seeing rates around ~400mA on my AUKEY Quick Charge 2.0 Car Charger. I'm getting over 1000mA on the factory Motorola Fast Charger.

In the car the phone uses more power than what's in coming, so it never gives an estimate of how long to charge (the dotted line out to the future) and the battery slowly drains.
[X Style (Pure) Android Development] t895:
Are you using different cables between the chargers? It could be a problem with one of the cables that is causing the bad charge rate
[X Style (Pure) Android Development] Spencervb256:
So I've been using this kernel for a while with all my custom ROMs and back when there were issues with 2.0 and bootloops. I was just reading a bit about the f2fs file system, and wondered what it's benefits are, and if it is safe to use now? Wondering if I'll see any performance improvements?
[X Style (Pure) Android Development] t895:
Nothing has really changed (in regards to the filesystem), the f2fs changes were reverted and now it won't cause bootloops
[X Style (Pure) Android Development] Spencervb256:
Alright thank you. So format data as f2fs and it should be safe and I may or may not see performance improvements?
[X Style (Pure) Android Development] t895:
Just wipe it as you usually would in TWRP, you shouldn't have to worry about what file system you have. The ROM/Kernel you flash will worry about that for you
[X Style (Pure) Android Development] thejase:
This kennel is very impressive! Very stable/smooth and runs well through the different speeds. I was wondering if any of you have played with the voltages (particularly lowered globally)? I realize that each piece of silicon is different and that results vary but just looking for a good place to start to globally. I'm happy with sleep sipping battery life but am trying to decrease battery life during surfing without losing smoothness. Is it just better to lower Max clocks or lower voltage? Thanks in advance everyone.
[X Style (Pure) Android Development] wizardknight:
I like my -95mv under-volt.
[X Style (Pure) Android Development] CSouthwick:
I tried a 25 global undervolt and had instability. Might be just bad luck with the device.
[X Style (Pure) Android Development] lknnnn:
My voltage table is here.Just for reference.
[X Style (Pure) Android Development] Spencervb256:
Could anyone tell me what would fix the lag with the camera when switching between front and back camera? It is an issue with all nougat roms but apparently it is a kernel issue and would be fixed once the source was released. So what im asking is if this is true that once handbag gets updated with the source code released by Moto, then this issue should be fixed?
[X Style (Pure) Android Development] fliperpl:
hey guys

what settings are u recommending for moto x style with heavy multitasking - with that i mean i have some apps in background, like messenger,snapchat,bluemail,deezer,steam,gestures

also i want some battery saving when my phone is in my pocket

from today i am using blue_active with maple, phone is very fast but it is a little hot and propably will drain battery too much
[X Style (Pure) Android Development] sideeffects:
I am using Handbag v2.3.3 and managing it using Kernel Adiutor. My governor and CPU frequency are not sticking on boot for the big core. Settings for little core are setting on boot properly.

I don't think it's a fault with the kernel necessary but are there any suggestions to get this working? Is it working on EX Kernel Manager?
[X Style (Pure) Android Development] CCJ22:
I'm confused with this bit here:

There are two branches:

msm - Uses the stock msm_core_ctl to handle hotplugging

hotplugs - Uses custom hotplugging solutions (Currently only bricked_hotplug)

Why do some pick one over the other?
[X Style (Pure) Android Development] CCJ22:
I wonder if we're asking these questions in the wrong thread?
[X Style (Pure) Android Development] XDleader555:
Nope, just your developer not developing. Also the low number of users with a Moto X Pure (Compared to other phones). It looks like there are about 300 users of this kernel based on downloads.

msm_core_ctl is the default on many android roms. It's the equivalent of the old mpdecision, but better.

hotplugs branch uses custom programmed hotplugs made by various developers. They're not necessarily better or worse than msm_core_ctl, but can offer flexibility or functionality.

Definitely a kernel bug. If I could get proper permission by patching sepolicy, a lot of things would be automated. I've toyed with sepolicy and the various utilities used (such as magisk or sepolicy-inject) to patch it into the ramdisk, but I couldn't seem to wrap my head around it, even after a week. I also believe something else, like msm_thermal or core_ctl, is affecting the cpu speeds/governor. I haven't been combing through the code as much as I used to.

If the LineageOS team decides that there's some beneficial code to merge into the moto x pure branch, It'll get merged into handbag eventually. Correct me if I'm wrong, the released kernel code hasn't changed too much and I haven't seen much activity on LineageOS gerrit.
[X Style (Pure) Android Development] CCJ22:
You're a gentleman and a scholar. Thank you
[X Style (Pure) Android Development] pyckvi:
.... Sorry ignore this, was dumb question.....
[X Style (Pure) Android Development] Sherrillface:
How do i get predetermined kcal color profiles ?
[X Style (Pure) Android Development] dzidexx:
https://xdaforums.com/oneplus-2/general/kernel-adiutor-kcal-color-profiles-t3382086
[X Style (Pure) Android Development] Sherrillface:
So of i flash another rom after the installation of handbag it will stick with new rom automatically because of anykernel2 correct?
[X Style (Pure) Android Development] chaostrodamis:
The kernel in the new rom will overwrite handbag. You will need to flash handbag again after. All Anykernel2 does is leave the ramdisk from your rom/previous kernel intact when flashing a Anykernel kernel such as handbag
[X Style (Pure) Android Development] gokart2:
-o3/-ofast version, with graphite optimizations
[X Style (Pure) Android Development] R77:
Whats the difference between HandBag-msm-2.3.3-20170731-1546.zip and HandBag-hotplugs-2.3.2-20170730-0034.zip which one is more better for battery life?
[X Style (Pure) Android Development] XDleader555:
How would you feel about a new kernel branch that requires Magisk to work? We can't use any optimization other than -Os since the payload would be too big for the boot loader.

Magisk would let me enable module loading on boot and therefore decreasing the initial payload size, since we can use superuser to bypass sepolicy restrictions on init scripts.

Stick with msm if you're alright with the default hotplugging. Some users prefer to use a custom hotplug (Only bricked at the time being), which is why we have a second branch. I've gotten the same battery life more-or-less on either branch.
[X Style (Pure) Android Development] chaostrodamis:
A magisk version would be really interesting
[X Style (Pure) Android Development] Sufyan#:
Can i flash it over stock nougat???
[X Style (Pure) Android Development] obsolete1:
It won't work. No one to my knowledge has published a kernel that will flash over

stock

nougat.

I know it does not say anywhere in the description that one has to be on a custom ROM for this kernel, but if it worked on stock more than likely someone would put that in their description.
[X Style (Pure) Android Development] trashy111:
Feature Request: Automatically listens to conversations for car talk, and automatically interjects 'Their car looks nicer than yours' at every opportunity.
[X Style (Pure) Android Development] wizardknight:
[MENTION=3623188]XDleader555[/MENTION]

Any chance you would consider recompiling this kernel with the latest code, and releasing an updated version.

New features would be great, but just getting any security patches or other small fixes that might have happened in the last 6mo would be awesome too. :o
[X Style (Pure) Android Development] OverkillSRB:
I agree, would love a LOS 14.1 up to date Handbag kernel, mostly for voltage control.
[X Style (Pure) Android Development] XDleader555:
Version update to 2.3.5

The only merged security fix was the WPA wifi hack, I've added it to the latest kernel.

Voltage control is still under testing. I dug pretty deep around new-years when I had time off from school, and I figured out why the first few voltages of the A57 core are tied together.

Seems like there's a hardware bug with the internal voltage regulator on the msm8992. To circumvent this regulator, they set a pre-defined voltage so it never gets called.

If you want, you can test out the latest build. I haven't been playing with it too much though. I removed the ability to edit the first few voltages because they're tied together anyways.

I also separated the upper and lower bounds so that the system automatically chooses a proper voltage in-between (For your tweaking pleasures).

I'd suggest removing any automatically applied voltage controls before flashing the latest kernel.
[X Style (Pure) Android Development] :
[MENTION=3623188]XDleader555[/MENTION] I installed your latest 2.3.5 earlier today. First time installing your kernel actually. I'm using [MENTION=5053748]obsolete1[/MENTION] 's AOSP Extended and noticed the camera wont open. I get an error stating "Cannot Connect to Camera". Everything else worked great, love having the extra options.
[X Style (Pure) Android Development] kellerman40:
XDA downloads are down, anyone has a mirror for the latest version?
[X Style (Pure) Android Development] GchildT:
Camera works fine for me, but my WIFI doesn't work.

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

Issue fixed with a simple Dalvik wipe.
[X Style (Pure) Android Development] kellerman40:
Camera doesnt work for me too. Im on LOS 14.1 12march build
[X Style (Pure) Android Development] :
Can I flash an older version over the latest version? Wanna see if itll fix the camera.
[X Style (Pure) Android Development] kellerman40:
Did try that and still no camera.
[X Style (Pure) Android Development] :
You caught me just in time. Just made my backups and was about to flash it. So I guess I'll just reflash my rom with a clean start, its been a while anyway. Thanks
[X Style (Pure) Android Development] kellerman40:
Yeah, i tried with latest LOS nightly and the camera was a no go. Same with NucleaROM, dont know about other roms.
[X Style (Pure) Android Development] :
Well I'm on AospExtended and the camera was a no go.
[X Style (Pure) Android Development] cksky:
I guess you are on nougat modem, just like me.

First, you should back to stock MM firmware, and use the most updated unofficial TWRP image from hashbang173. Link is below:

https://androidfilehost.com/?fid=818070582850499631

Then, flash the latest official LineageOS nightly and this kernel. The camera should be ok now.
[X Style (Pure) Android Development] :
Aww that sucks.
[X Style (Pure) Android Development] kellerman40:
Is it really possible to go back to MM fw from stock nougat firmware? It doesnt want to flash gbt.bin or bootloader files, gives preflash validation errors when tying to go back. Stock 7.0 flashes well...
[X Style (Pure) Android Development] jason2678:
Skip bootloader and gpt.bin. They can't be rolled back. Everything else can. Just pay attention to the output and repeat any steps that fail, usually non-hlos.bin.

You can rollback the whole system or just the modem stack. Just don't take an OTA in that mixed state. That tends to hard brick.
[X Style (Pure) Android Development] kellerman40:
I stupidly tought that the bootloader causes the problem... So flashing MM modem should be enough. Will try that, thanks!
[X Style (Pure) Android Development] jason2678:
Might be unnecessary, but I'd flash the whole modem stack and erase the settings, just to be on the safe side. Make sure every step is successful. Repeat if its not.

fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
[X Style (Pure) Android Development] SYNYST3R1:
Did you get this to work? With hybrid modem/bootloader like this I get no signal. Really a bummer to not have a working camera
[X Style (Pure) Android Development] kellerman40:
I flashed modem from RETEU 6.0.1. Still got no camera, everything else worked tho.
[X Style (Pure) Android Development] SYNYST3R1:
Alright, thanks. Hopefully someone can figure out what is going on with the camera
[X Style (Pure) Android Development] kellerman40:
By the way I tried it on latest NucleaROM, dunno about other roms.
[X Style (Pure) Android Development] :
Sorry to hear that but thanks for taking one for the team
[X Style (Pure) Android Development] iTakMD:
I'd like to thank you for this kernel, i'm using kernel with ExKernelManager to underclock both my CPU and GPU (and changing governors) because they were getting too hot when i was playing games. Now it runs much cooler and the battery life is lasting a bit longer.

As for the Camera, my camera still works after flashing the recent kernel. I'm using the most recent LineageOS 14.1 nighty with OpenCamera app and never touched the modem (hope that helps).
[X Style (Pure) Android Development] kellerman40:
Thanks for response. That might be down to bootloader version.
[X Style (Pure) Android Development] iTakMD:
My bootloader is A0.48 (2015-10-30).
[X Style (Pure) Android Development] kellerman40:
A0.52 here, unfortunately no way to go back..
[X Style (Pure) Android Development] yk1999:
I am using los unofficial build 31/3 on nougut firmware. The camera Doesn't seem to work. It says can't connect to camera. Is there a fix?
[X Style (Pure) Android Development] Tran Tien:
I have a problem when the camera does not work when flashing on Modem Nougat, how to fix?
[X Style (Pure) Android Development] tomlemange:
I've tried flashing this on stock 7.0 and it seems to break WiFi. Is this because I'm using stock rom?
[X Style (Pure) Android Development] DrDominate:
Post says it's meant for lineage os, so yes, it appears stock rom is out of the question.
[X Style (Pure) Android Development] parker.stephens:
Yea, flashing it on stock 7.0 nougat, it probably messes something up with the modem causing cellular and Wi-Fi not to work. It was made for LOS 7.1.2 without the Nougat modem. So by this context, it should not work on unofficial builds either.
[X Style (Pure) Android Development] OverkillSRB:
For some reason, voltage control does not seem to work for me. I tried Kernel Adiutor and a few other applications, but to no success. I am on LOS 14.1. 7th january 2018 build, with bootloaderl A048.

Does anyone have any clue to why?
[X Style (Pure) Android Development] hafhaus:
Oreo?

Hi.. does this kernel work on xt1572 with oreo lineage 15.1? thx
[X Style (Pure) Android Development] Itz_GoodPlayer:
Hi, will you still updating it?
[X Style (Pure) Android Development] Hybrid Theory:
This is the only kernel I could find that works on roms with nougat modem but camera doesn't work.
[X Style (Pure) Android Development] TotemFallico:
Hello.

Recently an unofficial LOS Pie rom has appeared. I did read that it's mostly supported on LOS based roms, but does it have support for Pie roms?
[X Style (Pure) Android Development] Curlyfry2121:
Maybe you? It matters about your usage, like as I'm a light user my cores go into sleep a good amount of the time.
[X Style (Pure) Android Development] dzidexx:
Very good JOB!

https://youtu.be/mBHb9tQJ8Sw
[X Style (Pure) Android Development] ismithx:
I mean in the instance where I put my phone down entirely (i.e. last night, out of my history I only see the little cores in deep sleep half of the time). This seems unusual as I would have been alseep most of that time and my phone would have been inactive.

the reason I know this is because I cleared the usage history yesterday evening and checked this morning and it had only deep slept half of the time. Then again it could be the governor/core parameters I put in.
[X Style (Pure) Android Development] Curlyfry2121:
Weird. Mine when hotplugged I get a really nice deep sleep percentage over night. You might need to check your parameters maybe.
[X Style (Pure) Android Development] mddunner:
I'm new to installing different kernels, but I am considering being the guinea pig for the CR Droid 7.1.2 rom on moto x pure. What is the best backup method for the current kernel before performing this installation?
[X Style (Pure) Android Development] creeperlwd:
Have been using it since yesterday, it's working pretty well so far with ondemand for cpu, bricked hotplug, powersave for gpu and noop for i/o.

One thing I did notice compared to AICP's default kernel is that it is missing DT2W. I don't use it anymore but it might be a feature you could add after figuring out the overclock.
[X Style (Pure) Android Development] Curlyfry2121:
Just copy the boot.img from the rom zip and if you wanna flash it flash it as an image in twrp