yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] countryfolk07:
I haven't had any focus issues either. Took some distance pictures over the weekend. Good sharp focus on everything.
[X Style (Pure) Android Development] dirtyhank:
Interesting finding today, I was playing with some virtual memory settings when I noticed the stutters got really bad. Since the stutters may be related to VM handling I tried different combinations and for some reason enabling ZRAM seems to reduce stutters.

Of course this may be purely coincidental and further testing needs to be done but it's worth a try. I'm using 500MB ZRAM with swappiness set to 50.
[X Style (Pure) Android Development] Note 3 Chicago:
That's quite interesting. I was going to write this afternoon about how I finally have the 300 stutter free. I've had not a single stutter since yesterday night.

I had an idea about memory being involved. I tinkered with the KSM and ZRAM settings, but didn't get your results. Of course I'm no dev. So I went through every single app I had running, I checked logcats for them, and I installed and uninstalled apps, services, and xposed modules which changed the UI, and everything I could think of.

- Is anybody with stutters running xposed? According to my logcat, sometimes when I had a stutter on mine, I got a memory error on the "flat style modules" (one or more of keyboard, status bar, icons). There seems to be some kind of conflict with the 300 and the flat style modules. No problems with gravitybox, interestingly, but I'm pretty sure gravitybox uses memory differently somehow. (I'm not nearly as smart as [MENTION=2400758]dirtyhank[/MENTION] at this.)

- I tested apps of different ages. Old apps caused stutters, newer ones didnt, when the apps required a service to be kept in memory. For example, Appsi sidebar causes stuttering. Glovebox doesn't.

- I tested services of different sizes. Big services didn't seem to matter, but how the service stayed in memory did. For example, Yaata caused a lot of stuttering if you asked the chathead to stay in active memory.

-I also tinkered with a bunch of settings. Eclipse with the butterfly timer loads works very, very well, but drains battery very fast and led to throttling at high temps. Ghostpepper and Eclipse (standard) both worked really nicely with an overclocked big cores and standard clocked little cores.

I don't know if this helps at all. But here's what I did:

- I eliminated those flat style modules

- checked GPU rendering and HW in Dev options

- overclocked BIG to 1958 (do NOT go higher) and kept little standard

- stuck on eclipse and/or ghostpepper

-msm_thermal on, core control off

-GPU matters! cpufreq, 600/180

fsync on, noop, 1024

Idle freq 384

Input boost 960, core 1

It's the smoothest android I've ever had, faster than my wife's iPhone. And I'm running right now with eight xposed modules on, and layers turned on, and six background services I'm forcing to stay in memory just to see how far I can push it before it stutters. And the battery life is fantastic, too.
[X Style (Pure) Android Development] JeffreyM:
After playing around with some custom roms I got in every ROM a huge battery drain.

With stock software i haven't got any battery problems so I decided to go back to stock... but with a different kernel.

I'm impressed with the Frankenclark kernel.

Battery drain at night only 2% (Data & Wifi off)

SOT: 51minutes --> 100% - 71%.

I really like it. I'm using the settings of profile: Balanced Profile.

Thanks!
[X Style (Pure) Android Development] HikingMoose:
I agree with most of what you say, except that the point of a custom kernel is not to improve performance. In the 6 years I've been into Android development, the point of custom kernels has always been to improve performance and battery. That's why the developers try to clean up the code and polish it. I've never heard anyone saying they want to run a custom kernel to decrease performance. That is counter productive. The reason they add the extra settings and governors is to allow the end user to dial in the performance they like.

Other than that I agree with what you said. The end user must dial in their p kernel to suit your needs. For instance, the butterfly and other profiles prime keep talking about, run like garbage for me. I had to find my own settings to smooth out the jankyness of marshmallow.
[X Style (Pure) Android Development] Note 3 Chicago:
Have you tried Eclipse? That works well. I also think apps have a ton to do with it. Badly coded apps, or background services, or memory issues, can all have negative effects.
[X Style (Pure) Android Development] HikingMoose:
I haven't tried eclipse, but I doubt it could beat my settings.
[X Style (Pure) Android Development] Note 3 Chicago:
Which are? :D
[X Style (Pure) Android Development] guile50:
Also curious to know the moose settings.

Really satisfied with this kernel and trupure. I used some workarounds for the Brazilian dual Sim version and it works fine, minimal overnight loss with WiFi on, lots of push notifications, currently at 60% and 2h30m SOT. Had to make my own setup tho, trying to load profiles in ex kernel manager makes my phone freeze and reboot so I'm playing with what I have. Anyways thanks for the awesome kernel hank.
[X Style (Pure) Android Development] jason2678:
Getting good results with those zram and swapiness settings here too. Still on v0.9-300. Thank you.
[X Style (Pure) Android Development] HikingMoose:
Well, like I said, I haven't tried eclipse, so I can't say for sure mine are better.

But here's what I like:

Interactive for both governors.

Under clocked the big cores to 1440 and the small cores to 1248. I crank up both touchboost sliders to about 25%. And set two cores to touchboost to 1248 instead of one (even though I don't know if it really has an effect).

Right now I am hotplugging, but plan to try turning off of to see if there are any performance gains. I have a minimum of one core online and 5 while screen on. Maximum of 2 online even screen off.

GPU is set to cpufreq.

Moto display if off, so I use swipe to wake.

I/O schedulers I set to fiops at 1024 for internal and external I leave noop with a read ahead of 512.

I'm trying the zRam settings every I'd talking about.

I use Westwood for my tcp congestion control (I think it's on by default with this kernel).

YMMV, but I like em!
[X Style (Pure) Android Development] gpz1100:
Agreed, the point is to improve things, but it's not a magic pill. Some users want better battery life, others want increased performance. The dev of any kernel sets default parameters to what they feel is appropriate. My point is one may still need to tweak settings further to achieve the result they want. Based on reading many posts, folks expect a one size fits all solution without doing any more legwork.

I've got my settings dialed into where the phone sips battery while screen is on. Using the performance profile in the OP as a base. I change the min cpu's online to 1 and disable touchboost altogether. Also max core speeds are dropped to stock values (no OC). Using moto display but approach is disabled and notifications are turned off from 12:00am to 11:59pm - effectively I don't want the screen coming on for notifications. The screen will come on if the phone is picked up or twisted (most of the time).

On the recommendation some posts up about turning off all the power saving apps, my latest experiment was to disable amplify and powernap. I did leave naptime running (which enables doze mode immediately after screen off). Last night, with wifi off, my consumption was .3%/hour - almost the same as when those two were enabled. We'll see how well it does during the day with wifi on and notifications coming in (2 email folders imap and google voice). I'll leave this set up for several charge cycles. Even with amplify and powernap, I was still seeing a good 90+min of wake time during screen off over the course of 2 days. Ultimately, success is determined by how much battery is consumed over a period of time with a particular screen on time. 40% left after 3 days would be very acceptable for my light usage.
[X Style (Pure) Android Development] HikingMoose:
Yeah, I love the battery life of stock after coming from all of the custom ROMs that are only getting 2hrs SOT!
[X Style (Pure) Android Development] guile50:
I got 4h30m on pac rom, man, what are you doing[emoji55]

I mean, I never got anything better than 3h on stock, after I've gone custom, the minimum time and that with a really bad signal is 3h30. I'm sitting at 49% with 3h19 and that is the craziest result I have got.
[X Style (Pure) Android Development] revolagoy:
HikingMoose,

Your settings are working great! I am assuming you are using the kernel auditor app to set your preferences. What are the ms set at for the two touch boost sliders that are at 25%?
[X Style (Pure) Android Development] Psykitt:
Thank you dirtyhank!

Maybe you can tell me what ROM you are using.

Greetings Psykitt
[X Style (Pure) Android Development] dirtyhank:
Stock (MPHS24.49-18-3) with Xposed (GravityBox and Amplify).
[X Style (Pure) Android Development] lbaquerizo:
Can you please help me with the link of xposed can't seem to find the right version
[X Style (Pure) Android Development] HikingMoose:
You're the first I've heard that gets better battery life on a custom ROM. They all have huge battery drains that EVERYONE talks about. The developers know it, and are trying to fix it. That's great that your phone is so different from the rest of ours.
[X Style (Pure) Android Development] Naddict:
http://xdaforums.com/showthread.php?t=3034811

try xposed-v80-sdk23-arm64.zip

http://xdaforums.com/attachment.php?attachmentid=3631566&d=1454436795
[X Style (Pure) Android Development] HikingMoose:
Thank you. I honestly don't know if the touchboost sliders matter. I always just slide then over around 25% or so. I never use an exact number. I just bumped mine way up to 3000ms for both last night, to see if it would help with smoother scrolling.

But I am trying some new settings because I woke up at 86% some reason. But I made a lot of changes yesterday.

I turned off wake controls, because the previous night I only lost 2%(with no wake controls), but last night I lost 14% with swipe to wake on.

I also went back to my old standby governor settings that anyone familiar with me will remember.

- small cores -conservative governor

- open governor tunables, set the down differential to 40 (when CPU usage drops below 40% it will clock down). I set my up threshold to 70. So when a CPU is getting used, it ramps up immediately for smoothness, and by raising the down differential, it will tend to hold your cores higher while screen being touched (I.e. scrolling), but 3000ms later all the cores turn off but one, and stay off until the one is over 70 used.

This is with both touchboost sliders at 3000ms. Watch your cores, they should all 4 fire up when you're touching the screen, and after you stop, they should shut off. If you want then to hotplug sooner, just adjust your settings. But I like them to hold my CPUs on while I'm scrolling, then if I stop scrolling, thrills shut off.
[X Style (Pure) Android Development] dirtyhank:
I installed xposed-v80-sdk23-arm64.zip. Just make sure root is working properly before installing Xposed.
[X Style (Pure) Android Development] chris23445:
I have a question for anyone that may be able to assist me. I installed this kernel 3 days ago on Stock 6.0. At first, my battery and performance were great. The past two days I have had horrible battery drain, my phone has not been able to go to deep sleep. I have never had this issue before and I haven't done anything except replace my kernel. I've attached screenshots to show my problems more clearly. Any help is appreciated, as I am not very great at kernels or wakelocks.
[X Style (Pure) Android Development] dkeepitabuck:
Viper4android was working when I was using the stock optimized kernel and now it doesn't work with the Frankenclark kernel. Can someone tell me how to fix this please?
[X Style (Pure) Android Development] Grafidio:
Viper works for me fam, I just install the apk after a flash of a new ROM, change your selinux to permissive
[X Style (Pure) Android Development] gpz1100:
Didn't you run trupureMM at some point? Why the return to stock over that?

My experiment (post 993) is going well. Lots of wake time without amplify and powernap but overall battery consumption about the same. Sometime next week i'll reintroduce t2k to see what effect that has on the battery drain.

If a lot, then revert to way it is now (2nd paragraph of the link above).
[X Style (Pure) Android Development] dirtyhank:
I ran TruPureXMM for a while when I got the device but switched to Stock when I started more serious kernel development. I liked TP but wanted to base my testing on pure stock.

I might as well ditch Amplify for a while, I installed Naptime when you guys mentioned it and it's working great, the standby battery life is crazy.
[X Style (Pure) Android Development] HikingMoose:
Stock is odexed, trupure is not. That's a good enough reason to use stock over trupure.
[X Style (Pure) Android Development] gpz1100:
?? What benefit is there after the initial booting?
[X Style (Pure) Android Development] HikingMoose:
It's optimized, so they're usually a little smoother. Plus it's a little less buggy. But I haven't tried trupure since December, or so, so maybe it's less buggy now.
[X Style (Pure) Android Development] dkeepitabuck:
I'm on TruPure 2.64 w/Frankenclark kernel and I don't have any issues.
[X Style (Pure) Android Development] lbaquerizo:
Same here. No issues whatsoever with trupure 2.64 and the latest kernel
[X Style (Pure) Android Development] Grafidio:
I'm on 2.7, I find this one much better than 2.6.4
[X Style (Pure) Android Development] dkeepitabuck:
Cool. I just haven't downloaded it yet. I'm gonna backup my user apps with TB and flash 2.7 now.
[X Style (Pure) Android Development] lbaquerizo:
If I dirty flash I have to reflash xposed and download again all the modules?
[X Style (Pure) Android Development] dkeepitabuck:
I'm not familiar with the dirty flash. I did a backup of my apps with TB and did a clean wipe then flashed the newest TruePure. I flashed my backup and the xposed zip after.
[X Style (Pure) Android Development] arcardinal:
Has anybody else experienced issues playing Youtube videos in 1440p? The video seems to freeze, but the audio keeps playing.
[X Style (Pure) Android Development] SpasilliumNexus:
Nothing to do with this kernel. It happens in general with this phone, even on stock.
[X Style (Pure) Android Development] GaetanWD:
What kind of SOT should i expect with the battery optimization set up? On Trupure 2.7 i only 3h20. I've seen people getting around 5 hours. How can i get better battery life?
[X Style (Pure) Android Development] SpasilliumNexus:
If anyone has issues with settings not sticking in Kernel Adiutor (like vibration), there's a modded version of Kernel Adiutor, which has tons more features added and unlocked, such as per-app settings, and actually keeps your settings on every boot.
[X Style (Pure) Android Development] lbaquerizo:
Everything depends of what you do with the phone. I'm my case I play games so no matter what I do I get average battery and people that get lots of standby is cause they don't use it that much
[X Style (Pure) Android Development] guile50:
Speaking about battery life... I'm having these kernel wakelocks quite a lot after I've installed frankenclark... Does anyone know what they are? Some say kernel wakelocks are normal but they are basically keeping my phone from sleeping sometimes (even with nap time). Is there anyway I can debug or provide better information about them? I don't have many partial wakelocks that I see as a problem.
[X Style (Pure) Android Development] dirtyhank:
That WL happens on many MM kernels. Some other devs have blocked it but I'm not so sure about it. I might add a toggle in future releases.
[X Style (Pure) Android Development] dirtyhank:
Very cool project. I'll add it to the OP.

EDIT: The "Start-Up Commands" is great, I love it. If they add custom commands it'll be perfect

Thanks!!!
[X Style (Pure) Android Development] spyder52:
Hmm can't find download link..
[X Style (Pure) Android Development] *.jpg:
The link is in the first post. I just confirmed it's working.
[X Style (Pure) Android Development] chris23445:
I have the same wakelocks. I had two days where my phone was almost never in deep sleep, and my wakelock battery drain was atrocious. I restarted my phone and it got better. I'm going to keep an eye on it. My phone isn't entering deep sleep as often as it was with the stock kernel.

I tried to apply the Nexus 5X Butterfly profile but I could not get the settings to work at all. Everything I change in Kernel Adiutor changes back instantly.
[X Style (Pure) Android Development] Fast_Zombie:
If you want to apply these profiles, you should look up for .sh scripts (there is the link to post with scripts in the profiles thread) and apply them using Fx explorer with root privileges. Then you can check the fact that these settings have applied in Kernel Auditor.
[X Style (Pure) Android Development] chris23445:
I downloaded the "butterfly_v1.1.sh" and used FX Explorer with root to apply the settings. I tried this multiple times and none of the settings were applied when I looked in Kernel Auditor.
[X Style (Pure) Android Development] Fast_Zombie:
This is what I get when I run these scripts.
[X Style (Pure) Android Development] chris23445:
Very strange. I tried running the script multiple times two days ago, and my target loads would not change at all. It seems now, after running it two more times, the settings have stuck. Quick question, is 633 mHz your minimum load for the big cores?
[X Style (Pure) Android Development] Fast_Zombie:
Nope, I can fine tune it down to 302 MHz. But there is a protip: due to some unknown reasons, these settings won't apply if none of big cores are running. You should tick the checkbox next to one of these cores, rush into frequency list and change lowest boundary to 302 MHz.
[X Style (Pure) Android Development] guile50:
i'm getting permission denied, even with root permissions...
[X Style (Pure) Android Development] Fast_Zombie:
Have you installed root module for fx explorer?
[X Style (Pure) Android Development] guile50:
yes sir. supersu is already permitting it.

edit: downloaded sh script runner, same error.
[X Style (Pure) Android Development] Fast_Zombie:
Hmm. What about busybox?
[X Style (Pure) Android Development] guile50:
patched up and good to go, sir. already installed (and updated) too.
[X Style (Pure) Android Development] gpz1100:
@Fast_Zombie

Check under settings|apps, if script executor has storage permission enabled?
[X Style (Pure) Android Development] countryfolk07:
[MENTION=2400758]dirtyhank[/MENTION], how difficult is it to add governors? I've been following the Nexus 5x kernel tweaking thread. Using the scripts posted there with fantastic results. The OP there just wrote a new profile script using impulse governor, a modified interactive, with very good results. Just wondering.
[X Style (Pure) Android Development] dirtyhank:
Do you know which kernels implement that governor?
[X Style (Pure) Android Development] MrMeeseeks:
You have to give r/w permissions to /system/lib/modules. I use ES file explorer and it is under root explorer. Not sure how it works in other file managers.
[X Style (Pure) Android Development] Fast_Zombie:
My script executor is fx manager and of course it has storage permissions. I can't see any other fx-associated apps in this list, except for root companion.
[X Style (Pure) Android Development] fdc77:
[MENTION=2400758]dirtyhank[/MENTION]

i have noticed that kernel adiutor and ex kernel manager does not retain settings after a reboot,

so i have found an app on google play that execute script at boot, i'm using it to boot device with butterfly or eclipse script.

https://play.google.com/store/apps/details?id=com.ryosoftware.initd&hl=it

Script can be found here:

http://xdaforums.com/showpost.php?p=64645746&postcount=900

remember, these scripts give their best without hotplug
[X Style (Pure) Android Development] countryfolk07:
I do NOT. I am sorry. I'll try to figure out how to find one. Thank you for your efforts in this project. It needs to be a Moto kernel? In the 5x thread I think DU had it.
[X Style (Pure) Android Development] *.jpg:
Maybe I'm just lucky, but Kernel Adiutor has always retained settings for me on TruePureX with this kernel.
[X Style (Pure) Android Development] dirtyhank:
No, a 5X kernel is OK.
[X Style (Pure) Android Development] odin13:
Not too shabby imho :)

TruPurex 2.5 + Frankenclark 0.7.1

Lionheart gov

Mostly streaming video over wifi and browsing/reddit/g+

Thnx Dirrrrty Hank!!

Verstuurd vanaf mijn XT1575 met Tapatalk
[X Style (Pure) Android Development] screech:
Me too. Actually it seems the auto focus is hunting very aggressively. Currently camera is unusable

Am on franken kernel. Re flashing stock now
[X Style (Pure) Android Development] Psykitt:
Hello screech,

what ROM are you using?

Greetings Psykitt
[X Style (Pure) Android Development] Note 3 Chicago:
Interesting finding. Naptime and no amplify/greenify has better battery life, but, for me, naptime brings back the stutters on the 300 version. I'm not exactly sure why (still investigating), but my supposition is the ramping up of the cores after aggressive doze. It still sleeps nicely without naptime, so I may just do without naptime anyway. Plus, naptime never saved my settings anyway, so I was only using it for aggressive doze.
[X Style (Pure) Android Development] Th3DaRk_Vampire:
offtopic: naptime and doze setting editor do the same thing right? i use doze setting editor
[X Style (Pure) Android Development] screech:
Trupure 2.7

---------- Post added at 08:02 AM ---------- Previous post was at 07:58 AM ----------

I should add

Switching to the stock kernel fixed my issue. Before I switched I had the balanced profile and blue active for small cores.

Trying other camera apps did not help.
[X Style (Pure) Android Development] Note 3 Chicago:
As far as I know. But Doze Settings Editor crashes for me, and Naptime doesn't save settings. I'm not even sure any of these apps are necessary with MM and Frankenclark, tbh; we can adjust and tinker with the kernel settings to maximize battery anyway.
[X Style (Pure) Android Development] HikingMoose:
Hmmm. I just started using naptime in last weekend. I haven't noticed it causing any stutters that were not already present with the 300 version. I've always hated greenify, it never extended my battery life, in fact it always seemed to use more battery.
[X Style (Pure) Android Development] Note 3 Chicago:
Greenify did the same for me also, particularly on MM. But the Naptime lag is a known issue with all aggressive doze apps. I was a little surprised to find that it was on the 300 kernel too, as I thought the higher tick rate might address the lag problem. I'm not sure Naptime is needed anyway, though; kernel settings can get great battery life anyway.
[X Style (Pure) Android Development] gpz1100:
How can naptime be causing lag? With aggressive mode on all it does is enable doze as soon as the screen is off rather than waiting for certain thresholds to be met.

Any lag after waking up would be a function of the min core speeds and governor's not ramping up fast enough IMO.

IOW, naptime's influence should only be happening during screen off.

Do you have any references for naptime/aggressive doze lag?
[X Style (Pure) Android Development] Note 3 Chicago:
^^^It is the ramp-up. So when the screen first turns on you have stutters, freezing, lag, etc. See here:

http://xdaforums.com/apps/greenify/aggressive-doze-experimental-feature-t3223731
[X Style (Pure) Android Development] gpz1100:
[MENTION=6637263]Note 3 Chicago[/MENTION], thanks for the explanation. It makes sense now. Perhaps this lag is a function of what's running in the background. With more sync's being delayed more lag will be present at wake up time.

I only have 3 things that require actual ongoing data - 2 imap folders and google voice. All of which is whitelisted in the battery optimizer screen.