yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] HikingMoose:
Well, to my surprise, the settings are more battery friendly than I expected. So I'll probably keep some of your mods, and try to tweak a few things for my own personal set up. After 2 days with your exact settings, SOT is a little less than what my old settings get, but not much, and it responds a little different (better than my settings in some instances), so I think I'll use yours as a base and try make little tweaks here and there.

My biggest problem right now is when scrolling in Tapatalk (which always has lousy performance - but is a good way to judge kernel performance), it's sluggish at the first bit of a page, then is smooth. Then when I get to the next page it's sluggish again. Even if I give it time to preload... It's still laggy until I touch the screen a few times. Does this with my settings, and your settings, and even if I set my governors to performance. Oh well, I'll keep tweaking, that's half the fun for me anyway lol. If I find something ground breaking, I'll let you know so you can try it too!

EDIT: So I just went to adjust some CPU settings and I can't. The Big cores are set to a max of 960 now, and a min of 633 and I can't change them. All 6 cores are pinned event though I'm not doing anything (But Play Music is downloading a 6.5GB playlist, so maybe that is keeping it pinned?). I might get rid of this Kernal Adiutor Mod if it can't change settings. Unless the script is not allowing me to modify them?
[X Style (Pure) Android Development] gpz1100:
^^Use OS monitor to see which app is keeping your cpu's pegged.
[X Style (Pure) Android Development] rehpyc:
[MENTION=4141782]HikingMoose[/MENTION] I've ran into various cases in which I'd need to change the value 2-3x before KA Mod would visually change the setting lol. Kinda just gotten use to typing the command in terminal or creating a quick script to execute. Let me know if you find any positive changes to enhance my current settings. Are you using the 100 or 300 version of the kernel? Tapatalk may just not respond nicely to the 300 if it's what you're using (and it's what I use).

[MENTION=2400758]dirtyhank[/MENTION] Some further changes coming.. working on some VM tweaks that seem promising for added smoothness
[X Style (Pure) Android Development] HikingMoose:
I'm using the 300. I went back to regular KA and I can make changes now. It's weird, because everyone said they switched to KAMod because they couldn't get settings to stick in regular KA, but I had the opposite experience lol. Anyway, thanks for sharing your settings. As a bit of a battery guru myself, it's nice to see what others come up with. Your settings perform another than expected.
[X Style (Pure) Android Development] elite001mm:
Hey [MENTION=2400758]dirtyhank[/MENTION] I tried experimenting with bricked hotplug before in KA but I wasn't able to get it to do what I wanted it to do. So first, here's my question:

Can you set the kernel to have one big core as well as one small core on at all times?

It was just a theory of mine that if one big cores as well as one small cores were on at all times, then perhaps it would give the system a little more headroom in terms of having to plug/unplug cores all the time, and in the long run, it could be more efficient. (I don't know how much more powerful the big cores are nor do I know how much more power they drain). Just observing the stock kernel, it seems to do something like this.

What I wanted was this:

Big core 1- online at all times (cpu0?)

Big core 2- last core to be plugged (cpu1?)

Small core 1- online at all times (cpu2?)

Small core 2- first core to be plugged (cpu3?)

Small core 3- second core to be plugged (cpu4?)

Small core 4- third core to be plugged (cpu5?)
[X Style (Pure) Android Development] rehpyc:
The big cores are really inefficient, thus they don't kick in until you do something system intensive. Having one on all the time will be an unnecessary battery drain.
[X Style (Pure) Android Development] dirtyhank:
I'm afraid you can't do that. Bricked hotplug always evaluates for plugging the first offline core, being CPU0-3 the little cores and CPU4-5 the big cores. So, for instance, if CPU3 is offline it won't even consider plugging CPU4 (unless the load is so high that justifies plugging them both). When it comes to unplugging, bricked always evaluates the CPU with the highest index first.
[X Style (Pure) Android Development] ilovemeow:
camera focus faulty

both 100/300 mhz

xt1572 dual sim india edition

TrupureMM 6.0

tested:

6.0 stock kernel new camera apk	:	pass for focus

6.0 stock kernel old camera	apk	:	pass for focus

6.0 custom kernel old camera apk : not tested

6.0 custom kernel new camera	apk	:	fail for focus
[X Style (Pure) Android Development] dirtyhank:
Ok guys, party time!!!

v0.11 is pretty much done but since the installer is new I think we better give it some more testing before pushing it to the OP. These are the changes:

Aroma Installer

Better camera focus

Less CPU usage from DT2W/S2W

Minor updates and bugfixes

RELEASE NOTES

The Aroma Installer is pretty basic but will let choose flavor (100Hz/300Hz), Max CPU Frequency for each cluster and which start-up scripts you want to install. These scripts will be installed to /sdcard/frankenclark/scripts and for now I've just included [MENTION=3004396]rehpyc[/MENTION] script verbatim and a minor modification with better performance GPU. Even though the installer will let you install both, it doesn't make much sense as they are pretty much identical.

The camera focus issue is a tough nut to crack. I've been working with [MENTION=698699]screech[/MENTION] on it and after much testing we found out that using less aggressive compiler flags for the camera driver helps a lot. I'm not saying it's fixed for good but I'm confident it'll be better.

Thanks a lot to rehpyc and screech for their help

This is a test version and although I've tried to test as much as possible there are a lot of things than can go wrong, especially with the installer. You're warned. If you don't have the skills to recover from a crash wait for the final release.

https://www.androidfilehost.com/?fid=24499762636007649

Let me know how it works for you.
[X Style (Pure) Android Development] newHere:):
Thank you very much [MENTION=2400758]dirtyhank[/MENTION] for your awesome work!

It is great to have such a responsive developer like you :)
[X Style (Pure) Android Development] unitz0mbie:
working fine, installed perfectly and everything, even with the battery scripts do i still change it to the one posted on OP? or do i leave as is
[X Style (Pure) Android Development] dirtyhank:
Please, test it as it is.
[X Style (Pure) Android Development] daniel.1983:
Thanks for this release! I installed it and checked the applied settings of both scripts (gpu + other) in kernel audiator. Everything has been set, as far as I can see. Good job!
[X Style (Pure) Android Development] screech:
Worked for me too
[X Style (Pure) Android Development] rehpyc:
[MENTION=2400758]dirtyhank[/MENTION] feel free to set the gpu max to 600 for everyone. I haven't seen any worse battery life since doing so, as well as logged speeds show it doesn't really perform any differently for my non-gaming use. Will help those who do gpu intensive tasks tho. Once I'm finished with my normal 2 day test cycle (tomorrow) with some new VM settings, I'll have you try them out.

Yay for Aroma options. Thanks again for your constant dedication over providing a great kernel!
[X Style (Pure) Android Development] Th3DaRk_Vampire:
V11 installed and testing... not problem at the moment... all working normal
[X Style (Pure) Android Development] SpasilliumNexus:
Guys I'm pretty sure he wants you to test for longer than an hour or so. More like a day to a few. Just because your phone boots after flashing it doesn't mean everything is okay.

With that being said, I'll too test it for a bit and report any issues, should any come along. Thanks!
[X Style (Pure) Android Development] htcslic:
Camera in test version has killed my regrets from switching from Note. Last version I just thought the camera was garbage. So much better in test version can't wait for release!
[X Style (Pure) Android Development] ilovemeow:
i thought it was the hw issue too
[X Style (Pure) Android Development] middleearth1010:
Looking good the only issue I can see is blueactive won't stick in kernel auditor so I'm not sure if it's an app issue though. Let me know if there is anything I can do to help you figure out what it is. Logs etc.

Edit a reinstall of. 11 dalvik/cache wipe after fixed. Running smoothly.
[X Style (Pure) Android Development] chrislui:
Would you mind fixing this issue?

http://xdaforums.com/moto-x-style/development/kernel-frankenclark-t3289939/post66401303#post66401303

v.011 still have this issues.
[X Style (Pure) Android Development] dirtyhank:
It's not an issue, it's set to this value on purpose, if you want stronger vibration use Kernel Adiutor Mod, EX Kernel Manager or simply write you own start-up script. A one line script with this can do the job:

echo 127 > /sys/vibrator/pwmvalue
[X Style (Pure) Android Development] dirtyhank:
Cool, thanks. Right now the only VM tuning I've included in the default settings is:

setprop dalvik.vm.heapminfree 2m
[X Style (Pure) Android Development] dirtyhank:
I'm mainly interested in two things:

Any issues with the Aroma Installer, suggestions and comments are welcome too.

Camera focus performance, whether the changes fix the issue for most people.
[X Style (Pure) Android Development] ggs2:
2.5hr SOT, 82 percent battery gone, not heavy use. Is this normal? Have bbs log file but don't know how to share using XDA app
[X Style (Pure) Android Development] revolagoy:
A couple questions: 1. Do you have to install the script you select from aroma with an app after booting or is the one you selected installed automatically? What if you select both scripts? 2. I am not sure what frequency to select. I have run your kernels in the past. Have your past kernels come with the highest frequency selected by default? I have just installed your kernels and run them without tweaking settings with a kernel app.

Thanks for the great work!
[X Style (Pure) Android Development] HikingMoose:
Wait, you're at 82%, or are you at 18%? Normal will depend on your usage and settings. There is a user that's regularly getting 7 hours screen on. Most get 4.

---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------

I enjoyed the installer (at first I thought it would be an annoyance). I liked the simple descriptions attached to each setting which will help out the noobs that are diving into kernels for the first time.
[X Style (Pure) Android Development] dirtyhank:
Nope, the selected scripts will be installed to /sdcard/frankenclark/scripts and run automatically on start-up in the same order as they are listed in the installer. You can also install you own scripts there later if you want.

Previous versions were using a max frequency of 1536MHz for the A53 (little) core and 2016MHz for the A57 (big) core. The A53 1632MHz freq is unstable on my device but might not on others, that's why I previously capped at 1536MHz, but now we have the installer I'd rather let the user choose.
[X Style (Pure) Android Development] revolagoy:
Thanks for the quick reply!
[X Style (Pure) Android Development] elite001mm:
I thoroughly enjoyed the installer. I especially liked the option to choose frequencies and the preset settings. Mostly because i really dislike using apps to change my kernel settings after boot. Its not always reliable. Camera focus seems good for me, I can't speak for battery life yet but all is well so far. Will report back later on battery. Thank you for the great work!
[X Style (Pure) Android Development] ggs2:
I am at 18 % :)

Even if i get 3.5 hours I would be more than happy.

I don't have facebook installed, my phones dosn't do too much of deep sleep i think, irrespective of my settings

---------- Post added 26th April 2016 at 12:13 AM ---------- Previous post was 25th April 2016 at 11:59 PM ----------

For v.11, even arom installer doesn't start for m :(

gets stuck at starting aroma installer
[X Style (Pure) Android Development] dirtyhank:
Can you connect via adb when this happens and send me the aroma log? /tmp/aroma/.install.log
[X Style (Pure) Android Development] Note 3 Chicago:
Love the Aroma version. 0.11 is running smoothly on mine; no problems.

---------- Post added at 09:29 PM ---------- Previous post was at 09:22 PM ----------

Here's a question. The other night I was in a restaurant in a bad cell area (they exist, even on VZW) and my phone hit 127 degrees. This wasn't from the kernel, of course, but it got me wondering whether there is a better way to control heat at the kernel level since this handset does tend to run warm, at least for me (YMMV, of course). Right now I have core control off and thermal throttling on in Frankenclark settings...does anyone else use the thermal settings? [MENTION=2400758]dirtyhank[/MENTION], is there anything that can be done to keep this thing cooler? If not, don't invest too much time; it was just an idea.
[X Style (Pure) Android Development] HikingMoose:
Sounds like you could benefit from starting from scratch. You're on stock MM right? What version of the phone do you have ( US, European, Indian etc).
[X Style (Pure) Android Development] gpz1100:
@DH,

Can you tell us what specific changes were made to the camera?
[X Style (Pure) Android Development] rehpyc:
To anybody who hasn't played with their Low Memory Killer or Virtual Memory settings in KA/KA-mod, could you please pm me the settings you have under each? Seems I can't find the paper I wrote the default values down on before toying with them over the past few days lol.
[X Style (Pure) Android Development] dirtyhank:
Thermal throttling will start scaling down the CPU when it reaches 60ºC (140ºF) and start shutting down cores at 80ºC (176ºF). Below the 60ºC it doesn't do much to control temperature. I think we could lower this limit to let it throttle sooner or maybe implement some sort of tunable.

In the meantime the only thing you can do to keep it cool is cap the max CPU frequencies. Not using a "trigger happy" CPU governor can help too.

If I'm not mistaken the heat dissipation from the CPU is more or less proportional to the CPU frequency and the square of the voltage. So as you can see it's very important to keep the CPU running in low-freq, low-voltage states as much as possible (from a heat and power consumption point of view).

EDIT: For reference here's the voltages for each frequency:

Little

302mhz: 800 mV
384mhz: 800 mV
460mhz: 855 mV
600mhz: 855 mV
672mhz: 880 mV
787mhz: 915 mV
864mhz: 935 mV
960mhz: 955 mV
1248mhz: 1015 mV
1440mhz: 1055 mV
1536mhz: 1075 mV
1632mhz: 1090 mV

Big

302mhz: 870 mV
384mhz: 870 mV
480mhz: 870 mV
633mhz: 870 mV
768mhz: 880 mV
864mhz: 885 mV
960mhz: 890 mV
1248mhz: 935 mV
1344mhz: 945 mV
1440mhz: 960 mV
1536mhz: 975 mV
1632mhz: 990 mV
1689mhz: 995 mV
1824mhz: 1015 mV
1958mhz: 1035 mV
2016mhz: 1040 mV
[X Style (Pure) Android Development] dirtyhank:
Default LMK values are:

28032,32640,37248,41856,62463,71680 (in 4K pages, divide by 256 to get MB)

Virtual Memory default values are:

dirty_background_ratio:5

dirty_expire_centisecs:200

dirty_ratio:20

dirty_writeback_centisecs:500

extra_free_kbytes:94400

laptop_mode:0

min_free_kbytes:6389

overcommit_ratio:50

swappiness:60

vfs_cache_pressure:100
[X Style (Pure) Android Development] dirtyhank:
Well, I didn't change anything in the camera code. I modified the compiler flags for the camera driver so optimization flags were more conservative.

My best guess is that the aggressive optimization flags made some of the floating point calculations proner to rounding errors or at least less precise. Funny thing is most custom kernels for other devices use these flags (even more aggressive ones) and it doesn't seem to affect camera focus, but I guess Motorola implemented the distance calculations in such a way that they are very sensitive to any manipulation.
[X Style (Pure) Android Development] ggs2:
I am on Stock MM, Indian version (xt1572/dual sim variant)...

Ready to change ROM also as long as its stable (use it primarily for office work so tough for me to flash often and check stability)

I use only hangout,exchange and xposed (for xprivacy) mostly.

very rarely Wapp
[X Style (Pure) Android Development] screech:
I am still hanging this on ffast-math acting on the auto-focus. If the floating point math used to measure "sharpness" is off, then it will make very high res blurry photos .. which is what it was doing. Since you have the before/after kmods would be interesting to see if the assembly shows any interesting diffs ..
[X Style (Pure) Android Development] Psykitt:
Hello guys and thanks for the effort!

Unfortunately my photos are still blurry.

Greetings Psykitt
[X Style (Pure) Android Development] screech:
[KERNEL] [v0.10] [MM 6.0 Stock ROM] Frankenclark

Never mind.

[MENTION=2400758]dirtyhank[/MENTION] looks like the O2 compile for the camera v4l modules got reverted in this aromatic build

Reloaded the 300-O2-camera build u had given me and confirmed.
[X Style (Pure) Android Development] dirtyhank:
That's odd, I've recompiled and double checked the flags are modified for the module. I've uploaded an updated version, please test and let me know:

https://www.androidfilehost.com/?fid=24521665358594547
[X Style (Pure) Android Development] Naddict:
Fwiw...I too had blurry pics...just installed the test and they seem to be much better. Not blurry at all.
[X Style (Pure) Android Development] screech:
My now familiar to some lamp sez .. This version is good.
[X Style (Pure) Android Development] Psykitt:
Hi dirtyhank and screech!

You made my day!

Blurry pictures seem to be gone!

I will do further tests tomorrow and let you know (because darkness comes above the land now in Germany).

Greetings Psykitt
[X Style (Pure) Android Development] MrMeeseeks:
Yeah they are both stock-based. There shouldn't be any problems.
[X Style (Pure) Android Development] rsmiff:
Works great!
[X Style (Pure) Android Development] guraki:
Third day in a row and constantly 4.5+ sot!!!! Great kernel!!many thanks to the dev!!
[X Style (Pure) Android Development] WelcomeToTheSkye:
Same here running amazingly
[X Style (Pure) Android Development] freakzapster:
I'm barely crossing 2 hours how you guys manage to cross 4 hours of SOT???

CAN ANYONE EXPLAIN PLEASE.
[X Style (Pure) Android Development] rockinandroid:
Hey, Flashed v2 and not seeing overclock in ROM toolbox Pro...anyone know why.....any help is appreciated...thanks
[X Style (Pure) Android Development] patt2k:
All of us use our phones differently. If you have it a lot lets say full charge unplugged at 10AM and by 8PM you have 5% with 4-5 sot. That means you on your phone a lot.
[X Style (Pure) Android Development] dmb219:
That's true, everyone uses their phone differently - different apps, different use. I get 5-6 hrs sot most days if I'm on the phone that much (which I'm not). Apps that hit the battery hard obviously will change that. I get good battery life with all the roms and kernels available for this phone, can't say I've seen any difference.
[X Style (Pure) Android Development] dirtyhank:
I've been doing some experiments with hotplugging and I'm not done yet with it but just thought I'd share a cool thing I've found out. For those of you eager to shut some cores down for good here's a pretty straightforward way to do it through the msm_performance parameters.

You'll need a terminal with a root shell

. Let's say you want to shut the big cores down, then you run this command:

echo "-1:0" > /sys/module/msm_performance/parameters/max_cpus

If you want to enable just 2 little cores and 1 big core:

echo "2:1" > /sys/module/msm_performance/parameters/max_cpus

I think you get the idea. If you want to restore default mode:

echo "-1:-1" > /sys/module/msm_performance/parameters/max_cpus

Let me know how it works for you.
[X Style (Pure) Android Development] Ghost9867:
Wow man this is awesome

But is possible to add the 2 tap to wake ? This would be awesome

And there is some shrewdness to make it run cooler ?
[X Style (Pure) Android Development] patt2k:
Downclock gpu. Double tap not even one kernel has it. Even on LP for moto pure.
[X Style (Pure) Android Development] cerobles1:
Wow this is awesome. It does not stick after reboot, so you have to run the terminal script again. But it is pretty cool. Kernel Audiutor shows the cores are off. Trying "2:0" to see how much more battery can be squeezed out of this SoC. Not sure why this isn't already built in. Battery seems to be draining slower. Thanks dude.
[X Style (Pure) Android Development] patt2k:
Good to know :D
[X Style (Pure) Android Development] guraki:
What i/o scheduler do you prefer guys? Is any scheduler better concerning smoothness?
[X Style (Pure) Android Development] Ghost9867:
I use noop and it's awesome
[X Style (Pure) Android Development] dirtyhank:
New version

v0.3

Color control (KCAL)

frandom support

New optimization flags

ZRAM disabled by default

As always, remember these are unrooted images, do your magic ;)
[X Style (Pure) Android Development] fdc77:
Fsync on/off and Color control (KCAL) can't be set with kernel adiutor, anyone can confirm this?

is this a kernell or apk problem?

i'm on xt1572 euro
[X Style (Pure) Android Development] dirtyhank:
KCAL works for me, remember you have to press the power button to activate changes.

Fsync works too but there's a bug in KA, it reports Fsync disabled by default but it's enabled. If you enable it then the switch works fine until next reboot
[X Style (Pure) Android Development] fdc77:
ok for fsync, this can be set using trickster mod, but under screen menu i have only the option to change brightness mode and nothing more.
[X Style (Pure) Android Development] guraki:
Why did you select cfq scheduler and only 128 kb read ahead buffer?
[X Style (Pure) Android Development] beefgoat:
I've installed the test kernel a few times with different settings and it has worked flawlessly every time. I'm now using the 300hz with the standard GPU script and 1560 on the LITTLE.
[X Style (Pure) Android Development] kadopt:
[offtopic]OTA update for European devices released and captured!

http://xdaforums.com/showthread.php?p=66559931[/offtopic]
[X Style (Pure) Android Development] HikingMoose:
Any thoughts in offering undervolting? It might not add a ton of battery savings, but does help some, and keeps things cooler if done right.

I used to enjoy testing my older devices to see how low of a voltage they could handle. My S4 could undervolt by -150mv on all clocks, but my wife's could only handle -75.

---------- Post added at 06:33 PM ---------- Previous post was at 06:21 PM ----------

OK. Well I'm not very familiar with the differences between the Indian version and my own, but if you're having recovery issues, starting from scratch might help. Or maybe reinstall your recovery. What recovery are you on? It could be as simple as updating your recovery to the proper one. The aroma installer worked fine for the rest of us.
[X Style (Pure) Android Development] xpakage:
I think you answered your own question. I know you have read many threads (help in all I have seen) and the "if done right" truly made me laugh out loud. There are soooooo many users who ask why something is not working when they had to read the answer when they downloaded the "improvement, update, or ROM". If done right, I would bet a Kodiak bear could wear a Hamster skin to help keep warm, or vice versa....... LOL..:highfive:
[X Style (Pure) Android Development] fdc77:
Don't flash frankenclark on top of 6.0.1 update or wifi stop working
[X Style (Pure) Android Development] kadopt:
[MENTION=2400758]dirtyhank[/MENTION]

To fix this you'll probably need motorola sources right? Boot/recovery image is not enough?
[X Style (Pure) Android Development] dirtyhank:
I've researched it but seems like the Snapdragon 808 doesn't handle undervolting that well. Nobody has been able to achieve significant stable undervolting yet :(