yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Android Development] Note 3 Chicago:
I also think that a lot of lag is from apps (particularly battery-saving apps like Greenify that use resource intensive processes *and* cause lag) and not the kernel. That's why I think that with an optimized device, you can get good battery life and performance and you don't need the battery savers. But I also think that when we're trying to diagnose lag, we should go through the apps, services, and processes we have running first with a logcat before blaming it on the kernel. [MENTION=2400758]dirtyhank[/MENTION] has done a really, really nice job with this, and any lag on frankenclark is less than what would exist on stock, imho.
[X Style (Pure) Android Development] dirtyhank:
Interesting. I've been doing some experiments on ZRAM these days and every once in a while I get stutters right after screen on, I blamed it on too much swapping at once but since I've been using Naptime in Agressive Mode I think I'll redo the testing without Naptime.
[X Style (Pure) Android Development] Note 3 Chicago:
Definitely. It makes a bigger difference than you'd think. And it actually doesn't add that much battery life once the kernel is optimized.
[X Style (Pure) Android Development] rehpyc:
Is naptime much different than doze editor? I mean, it has a doze settings editor within it, so I'd have to look at what else it does. Giving it a try in place of doze editor, with my own custom doze settings. The .9 300 kernel has seemed to provide the same battery endurance as previous versions with some added smoothness. Could get 6.5-7 hrs over 2 days on previous versions, but there was some slightly noticeable stutter. So far, battery seems about the same but with minimal to no stutter.
[X Style (Pure) Android Development] Note 3 Chicago:
AFAIK, Doze editor and naptime are pretty much the same thing. I've found in my personal experience they do more harm than good, because any (slight) gains in battery life are offset by the increase in lag and stutter and lost battery life as a result of the increased CPU ramp-up. Plus, the MPXE on frankenclark doesn't burn much battery on deep sleep, even without any battery app aids. I'd go without either one, tbh.
[X Style (Pure) Android Development] HikingMoose:
I don't understand why some are having these stutters and lag with naptime. I'm using it, and it's almost as smooth as anything I've used (Orion being the only thing smoother). What kind of settings are you guys using with frankenclark? It might be something in there.
[X Style (Pure) Android Development] Note 3 Chicago:
It's not Frankenclark; like the Greenify dev explained, it's a known bug. Basically, after the phone has been dozing a while, the CPU has to ramp up fast. This would ordinarily be okay, but in aggressive doze, background tasks and apps aren't active until they also come out of doze mode. So, if you have a lot of background tasks which have been postponed due to a long-term aggressive doze, all the tasks get done first thing while the CPUs are ramping up and the result is that the phone lags, stutters, or freezes. Now, some devices with only a few apps, or not many background services, don't have this bug because there isn't as much to do when the CPU comes out of doze. In theory, you can mitigate it by having the CPU ramp up via touchboost to max out of doze, but that causes its own problems.

So, in sum, the lag from naptime and its ilk is real, and not Frankenclark, but depends (as with anything else) on what apps and processes you're running.
[X Style (Pure) Android Development] HikingMoose:
That makes sense I guess for people that leave a ton of apps running. I keep my apps killed off to save battery. So only the bare minimum starts when I wake my phone.
[X Style (Pure) Android Development] Note 3 Chicago:
Don't app killers actually use more battery than they save? (Not to mention other negative side effects...)
[X Style (Pure) Android Development] HikingMoose:
Yes they do. I don't use any, just naptime. So far, much better battery life.
[X Style (Pure) Android Development] gpz1100:
For those just running naptime, what kind of screen off wake time are you seeing?

For example on my recent charge

@ 50% battery remaining (just rolled over) I have the following stats
[X Style (Pure) Android Development] rehpyc:
Currently trying just naptime instead of greenify/powernap, and so far the awake time with screen off is way over the norm. With the latter combo, I typically will get only 50-55m of screen off awake time over 2 days.
[X Style (Pure) Android Development] gpz1100:
Right, I'm also seeing high wake time but actual battery consumption is excellent. Ultimately, it's the latter value that's of importance. It could show 48 hours of wake time, but if battery continues to be sipped then it's all good :)
[X Style (Pure) Android Development] MrMeeseeks:
[MENTION=2400758]dirtyhank[/MENTION] Have you considered adding init.d support? It would make it easier for people running the scripts from the advanced interactive thread. Just put it in the folder with correct permissions and let it load at boot.
[X Style (Pure) Android Development] dirtyhank:
Yep, and I could add it if you people think it's useful but I've been reluctant because I don't want to touch the system partition. I use Xposed so I don't mind but other people might want to keep the system partition 100% stock.

I'll try to think of a way to implement it without modifying the system partition. In the meantime I think Kernel Adiutor has some kind of hack to simulate init.d (can't comment though since I haven't tried it).
[X Style (Pure) Android Development] MrMeeseeks:
Yeah, I tried the kernel adiutor thing but i couldn't get it to work. What I did was made a script in rom toolbox and set it on boot. That works but it would easier to just copy/paste into the init folder. I personally don't mind it touching the system partition because it's easy to flash back to stock, but I'm just one person. Maybe we could get a poll going and see where the majority stands on it.

---------- Post added at 03:35 AM ---------- Previous post was at 03:02 AM ----------

Edit: Just one more thing. How do you feel about BFQ for the i/o scheduler?
[X Style (Pure) Android Development] jason2678:
I have xposed and I've made a number of modifications to system myself. If I need to go back to untouched stock for an OTA or something I've got a nandroid backup for that. I'd welcome init.d support.

I've tried the kernel adiutor init.d. It seems like it has some sort of size limitation. It works for a few lines, but refuses to save if you add anything too complex. It might work for some small tweaks, but I can't get it to run ghostpepper.sh even with all the lines that don't really do anything trimmed out of it.
[X Style (Pure) Android Development] Note 3 Chicago:
I don't mind touching the system partition.
[X Style (Pure) Android Development] dirtyhank:
Most likely will be on next release ;)
[X Style (Pure) Android Development] gpz1100:
Re: system modifications

Either give the user the option to use that route or not, or if it's forced, make sure to state so in bold letters. I generally don't do a system image when changing just the kernel. If I know the kernel install will modify the system, then of course a backup will be made first.
[X Style (Pure) Android Development] elite001mm:
[MENTION=2400758]dirtyhank[/MENTION] This isn't a request, as I realize that it would require extra work on your part, but I want to see what you think about this. I think it would be an elegant solution to a problem. Instead of simply adding init.d support or not, you could utilize aroma and simply offer the different variants within aroma. For example:

Normal-100

Normal-300

Init.d-100

Init.d- 300

And so on.

It would be nice and simple to the end user and this way you can still just upload a single file per kernel update.

I don't know how much extra work it would be to keep track of the different versions for you since I'm not a developer, but I thought you should hear the idea :)
[X Style (Pure) Android Development] dirtyhank:
Actually that's quite a neat solution. I'll look into it.

Thanks!
[X Style (Pure) Android Development] TASL:
Just a note, I have been having the same issue of poor camera focus (in some situations the 'aggressive focus seeking'). I had the problem on Stock 6.0 (feb sec patch) and 6.0.1 Asia DS. Problem was solved when I reverted from 0.9 to 0.8. My 2c.

[clarification] I also did a dalvic/cache wipe between kernel flashes, and I have only been testing for the past 4 hours. Will update if the quality reverts back to out of focus. Systemless root, xposed 80 installed.

[Update] might have been more related to Darvish/cache wipe, the focus problem returned. Held my GFs moto x pure 100% stock unrooted) side by side with my phone, her phone was able to get a crisp focus and hold it under the same circumstances that my phone was constantly refocusing. Was fine earlier today though, not sure what is happening. How can I get a log of the camera behavior?

[Update2] reflashed 0.9 and the camera is focusing correctly again. So what would change hours after a fresh flash and multiple reboots that causes the focus to go out? I havent adjusted any country settings except vibration Of which doesn't cause any immediate change to camera focus.
[X Style (Pure) Android Development] Sabissimo:
Deleted
[X Style (Pure) Android Development] tsadev:
[MENTION=2400758]dirtyhank[/MENTION] Could you possibly add UnionFS support?
[X Style (Pure) Android Development] rehpyc:
Ended up reverting back to a nandroid that used 0.6, since it seemed to sip on battery much less than 0.9 has. I think I had skipped 0.7 and maybe even 0.8 before, so I'm not sure how those were in comparison. With the same settings in EX, 0.6 gets 30-35m of SOT for every 5% with texts/emails/browsing while 0.9 only gets about 25m. Not sure if my phone just likes the older version better or if adding the sleep/wake options in later versions added some background battery drain. May try doing further testing.
[X Style (Pure) Android Development] dirtyhank:
Just curious, what do you use UnionFS for?
[X Style (Pure) Android Development] tsadev:
Me personally? I would like to add system applications + libraries without actually modifying the system partition.

In case you happen to be asking about the software itself:

UnionFS is an overlay of sorts that allows you to map directories on different devices (physical or loop) to the same location without modifying the physical location of the files. (http://unionfs.filesystems.org)
[X Style (Pure) Android Development] dirtyhank:
Yeah, I know what UnionFS is, I use Docker pretty much every day :)

I just didn't picture a use case for this device but what you mention makes sense.
[X Style (Pure) Android Development] HikingMoose:
This makes me wonder what version is everyone's favorite? I'm on 0.9 300hz, and it's pretty nice. But battery life is not what I'd expect from stock after using custom ROMs got a few months. I'm at 78% battery with only 40 minutes screen on. (But was in poor reception for a a child hours, and listened to music for 1.5hrs).
[X Style (Pure) Android Development] Cleiton COUT:
Any issues with L Speed?
[X Style (Pure) Android Development] guile50:
I'm getting about 20-35min every 10% depending on the reception. And moose mentioned something important, music playback burns a lot of battery. today I forgot my headset at home and I'm sitting at 2:30h sot with 52%.
[X Style (Pure) Android Development] rehpyc:
Streaming music will always burn battery, and how much is dependent on whether it's over cell data or wifi. Obviously less strength of the former will lead to higher battery use. It's essentially something keeping your phone awake. However, it's not a HUGE battery hog, especially if you have measures in place to limit other apps from taking advantage of the phone not sleeping.

Cell drain is unfortunately the biggest battery drain of anything else. Since I work in an area with pretty terrible reception, I could have 5 or so SOT and the screen and standby having used equal amounts of battery at the end of the day.

May try out 0.7 and 0.8, but I've pretty much solidified that 0.9 has more background drain in comparison, at least with my setup.
[X Style (Pure) Android Development] smohanv:
I don't see my firmware version as mentioned in Op page (screenshot attached). Can I still use this kernel.
[X Style (Pure) Android Development] ffejy462:
Your ROM has the frankenclark kernel as one of the options in the aroma installer.

But, yes, you can use this kernel.
[X Style (Pure) Android Development] dirtyhank:
v0.10

Updated lowmemorykiller driver

BFQ and SIOPLUS I/O schedulers

Updated ZRAM driver (on by default)

User togglable WLAN wakelocks

Basic init.d support

Misc minor updates

RELEASE NOTES:

Again two versions available, 100Hz and 300Hz. I encourage you to try both and let me know your opinion. My daily driver is the 300Hz and I'm pretty happy with it.

After much testing I've decided to enable ZRAM by default for this release. The updated driver seems to work better and makes the system more responsive when multitasking. We'll see how this goes.

Some WLAN wakelocks can be toggled from Kernel Adiutor Mod. If you want to check the full list go to /sys/module/wakeup/parameters. You can disable by echoing "N" to the file. Only disable these wakelocks if you know what your doing. For example:

echo N > /sys/module/wakeup/parameters/enable_ipa_ws

Since I didn't want to modify system partitions I've implement a basic init.d support that requires some user intervention. What I've done is check for the existence of directory /etc/init.d and in such a case execute all *.sh scripts. That directory doesn't exist by default, so if you want to use it you must remount the system partition as rw, create that directory, copy the scripts you want and remount again as ro. For example, from a root terminal:

toolbox mount -o remount,rw /system
mkdir /etc/init.d
cp /sdcard/myscript.sh /etc/init.d
chmod 755 /etc/init.d/myscript.sh
toolbox mount -o remount,ro /system

The scripts are run in alphabetical order, so if you want a particular order I suggest you name your scripts 00-whatever.sh, 01-whatever.sh and so on....
[X Style (Pure) Android Development] zohar_ml:
Thanks for this great kernel!

I'm downloading 0.10 as I type. (you need to update the tread name, it still 0.9)

I have a strange thing that while on call and the screen is off from the proximity sensors, the touch screen still works and I can press call end or any other thing (today I managed to go into flight mode while in a call!)

I wish to go to stock kernel to see if it's from the system or from the kernel.

Can some one help me on how to install the stock kernel (and from where to download it)

Thanks,

zohar
[X Style (Pure) Android Development] dirtyhank:
If you have DT2W/S2W enabled that might be the reason. Probably will have to find a way to disable while on a call.
[X Style (Pure) Android Development] ffonegod:
Quick question.. Does DT2W/S2W produce any battery drain and if so how much does it impact battery performance
[X Style (Pure) Android Development] Makalicious:
Sorry for noob question regarding init.d, but if I create scripts via kernel adiutor it creates said folder in /etc/init.d

Do I still need to do the unmount/remount command from ADB?
[X Style (Pure) Android Development] alejx2ex1:
I have an issue with my USB otg memory, I can't write to the memory.

Btw Im using es file explorer.
[X Style (Pure) Android Development] HikingMoose:
Hey rehpyc, did you end up trying 0.7 and 0.8 to see how they compare?
[X Style (Pure) Android Development] rehpyc:
Not yet. Been testing out diff scenarios between uses of Powernap, Naptime, Greenify, Amplify and Doze Editor. I pretty consistently get 6.5-7 hrs of SOT over 2 days with similar usage, so I feel I have a pretty good baseline for comparison. Will flash .7 tonight and let you know. Now there's .10 to test lol.
[X Style (Pure) Android Development] HikingMoose:
Thanks bud. In the mean time, I guess I need to try 0.6 lol. I'm getting like 4hrs SOT over two days.
[X Style (Pure) Android Development] elite001mm:
Just a quick FYI for anyone who uses the Kernel Adiutor init.d manager thing.... If your scripts made within KA don't work, use a file manager and navigate to the init.d folder and add the .sh extension to your scripts. Ex: if you made a script called "00-GP" It would need to be renamed to "00-GP.sh". :good:
[X Style (Pure) Android Development] shinesthru:
I have tried installing this kernel several times, but have had no success. I'm running TP 2.7, selinux set to permissive, xposed w/ gravitybox, and V4A. I have tried version .09, both 100mHz and 300mHz variations. I have tried fresh downloads each flash. I flash the kernel in the latest TWRP, it boots up, and then begins rebooting. I read through the last 10 pages, and searched the thread, but I wanted to see if there was a known issue before I pull a log since its been a while since Iv'e done that. Thanks in advance.
[X Style (Pure) Android Development] vx2ko:
Let it reboot. I have the same setup. It rebooted about 3 times before it actually started booting.
[X Style (Pure) Android Development] crevis24:
Would like to try your settings to see what I can push the SOT for myself. Would you be able to share your KA settings and any battery saving apps you are using? I have been trying alot of different things but can't seem to get much more than 2.5 or 3 hrs SOT.

Thanks in advance
[X Style (Pure) Android Development] shinesthru:
Thank you for the quick reply. I'm pretty excited to use this kernel as I've heard great things.
[X Style (Pure) Android Development] argenteloup:
Did anyone try bioshock with hotplug?

I couldn't tell the difference between it and bluactive during normal daily usage and gaming, but in Antutu benchmark, it was 20K lower than bluactive.

I'm wondering if any real world situation that bioshock governor could hold down the cpu performance.
[X Style (Pure) Android Development] dirtyhank:
I forgot to mention that with the latest changes I've noticed interactive governor performs better than before, at least on my device. So much so that I've switched from blueactive to interactive and it's almost as smooth.

Maybe it's just in my mind but I'd like to know your opinion, give it a spin ;)
[X Style (Pure) Android Development] shinesthru:
[MENTION=2400758]dirtyhank[/MENTION] Unfortunately I'm still getting random reboots after running v.10 for a few hours. Here's a log: http://pastebin.com/A0nr3u3M
[X Style (Pure) Android Development] dirtyhank:
Reduce max CPU freq for both clusters. Some SoC can't cope with O/C.
[X Style (Pure) Android Development] shinesthru:
Clusters? Meaning cores ("big" & "small")? Sorry, I'm a bit of a novice when it comes to kernel tweaks.
[X Style (Pure) Android Development] dirtyhank:
Yep, each set of cores (big/little) is called a cluster.

In other words, reduce max frequency for all cores :)
[X Style (Pure) Android Development] shinesthru:
Alright, I set the max frequencies to what the stock optimized kernel I was running before had them set at. So far, so good. I'll bump them up if I don't get any reboots to test what it can tolerate. Thanks for the help.
[X Style (Pure) Android Development] ffonegod:
Yea you're correct. Using your balance profile settings.. Everything is smooth and multitasking is blazing.. Got a 76k on antutu. Not bad!
[X Style (Pure) Android Development] urimevs509:
used the performance profile (including overclocking) except I selected interactive governor for both clusters... I only got 60k in Antutu. I usually get almost 80k with bluactive.
[X Style (Pure) Android Development] dirtyhank:
Blueactive will always be better for benchmarks because it ramps up faster and keeps the frequencies high for longer.

Honestly I don't pay that much attention to benchmark scores, I'm more interested in user perceived snappiness.
[X Style (Pure) Android Development] ffonegod:
Only trouble I have now is for kernel adiutor to keep my settings when I reboot.. I apply on boot but settings won't stick.. I'm using the KA modded btw
[X Style (Pure) Android Development] MrMeeseeks:
Mine stick and I'm using that one as well. Did you come from the regular ka? You have to go back into the modded version and select your settings in there.
[X Style (Pure) Android Development] timde9:
This kernel is causing random reboots on my phone. I've narrowed it down by reinstalling stock firmware and then installing this and using it all stock with minimal apps and as soon as I install this the phone just reboots every once I. a while. Even if I just leave the phone completely alone for hours it eventually reboots. Since this is the only thing I installed on top of latest stock firmware for the pure it must be caused by this kernel both 300mhz and 100 MHz versions are affected and it's been happening to me since version .09 still happening with .10
[X Style (Pure) Android Development] elite001mm:
I have not once experienced these reboot problems. I'm on stock February security update. I've used it on trupure also and didn't have any problems. Currently on .10-300 but have been here since .7
[X Style (Pure) Android Development] Note 3 Chicago:
Have you looked at a logcat? It may very well be an app.
[X Style (Pure) Android Development] dirtyhank:
I haven't experienced a single reboot with v0.9 or v0.10. Try to reduce max CPU freq to stock on all cores.
[X Style (Pure) Android Development] dirtyhank:
Kernel Adiutor is pretty picky when it comes to "Apply to boot" settings. Good news is with Kernel Adiutor Mod you can check which settings it has registered to apply. Go "Start-Up Commands" and check whether everything you want is there, if not clear all startup settings. Go back and forth between each tab (CPU, GPU, ...) and "Start-Up Commands" to make sure it's registering your settings.
[X Style (Pure) Android Development] zohar_ml:
I did a simply fix using tasker. turn S2W off when call is on.

I turned DT2W off because the phone keep getting turned on in my pocket (could the light level of the pocket detection be tuned?)

profile: state, phone, call, type=any

enter task: run shell, command=echo 0 > /sys/android_touch/sweep2wake .use root

exit task: run shell, command=echo 1 > /sys/android_touch/sweep2wake .use root

A kernel level fix will be much better :)

Can some one help me with this?

Zohar
[X Style (Pure) Android Development] jason2678:
Easiest way would be to restore a stock nandroid backup. Uncheck everything but boot and it will only restore the stock boot.img. If you don't have a stock nandroid backup then what are you doing modding your phone? :p just joking. (And you will have to flash supersu again if it happens to be a boot.img from before you rooted.)

There are firmware threads for the 1572 and 1575. You need to find the boot.img for your device there if you don't have your own backup.
[X Style (Pure) Android Development] bv90andy:
Hello,

anyone using this kernel on the stock february update? Is it compatible?

Thank you
[X Style (Pure) Android Development] aznflawless:
Does this kernel work with cm13 yet or ever wi? Wifi seems to never work when I flash this kernel.
[X Style (Pure) Android Development] dmb219:
Yes, it works great.
[X Style (Pure) Android Development] bv90andy:
Thank you.
[X Style (Pure) Android Development] ffonegod:
I cleared all start up settings and re apply the balance profile settings.. This is what's shown.. Is it listed correctly.. That's all I see
[X Style (Pure) Android Development] SpasilliumNexus:
Of all the Android devices I had (S3, S3 Mini, Note 4, Nexus 4, Nexus 5, 2013 Nexus 7) their AOSP/Touchwiz based kernels NEVER worked right with CM.

Same with this phone and a lot of others. And I'm pretty sure the thread title would've been changed to reflect that if it did work.
[X Style (Pure) Android Development] dirtyhank:
There should be more commands. Go one setting at a time and make sure it's being registered.
[X Style (Pure) Android Development] dirtyhank:
Read the FAQ on third post