yashsingh1/xdaforums huggingface dataset:
[ONE Original Android Development] Stroky:
You are right, and as i said it is not included in Boeffla.

There is the Stock hotplug and the additional zzmoove hotplug for the zzmoove governor, but it has nothing to do with zen hotplug

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] acidburn94:
Okok yes youre right!

Sent from OnePlus
[ONE Original Android Development] deepaklunked:
Hi all. I seem to get awesome battery life with this kernel. Dont know how, but maybe because only since yesterday, i am using wifi; before that i had 4g. Also, i flashed this kernel like 2 days ago. The only tweak i did is, change the governor to smartmax. Nothing else. Anyhow, i am impressed with this kernel.. Will test it further.

Sent from my OmniBacon
[ONE Original Android Development] fermasia:
Zzmove is not a hotplug driver, it works together with mpdecision AFAIK. What it does do is support hotplug profiling and a bit deeper set of options for it's governor. That said, there might me some hotplug implementation named zzmoove, I don't really know.

We could try adding zzmove the way Lord Boeffla implemented, but one has to understand it's logic, I don't know what you guys are used to but there's no point in just adding or changing stuff before really knowing how it works and testing if it will benefit overall performance.

Have you spent some time testing the kernel right how it is? I mean, I'm getting good results and staying close to stock options is not a bad thing at all, since stock is allways more integrated with the rest of the build. Let's make sure throwing stuff it's worth it....

I will try to look into Zzmoove when I'm finished looking around and testing Zen Hotplug, which I didn't know and I'm trying to compare it's performance to stock CpuQuiet.
[ONE Original Android Development] acidburn94:
Thank you! Im using your kernel and actually im getting normal/good result with smartmax

Sent from OnePlus
[ONE Original Android Development] xflowy:
so my short conclusion with your kernel on smartmax and row. its smooth but still with some lags here and there and by far not as smooth as zen decision and scheduler + smartmax. also there are several moments where my touches arent registered first time im hitting.
[ONE Original Android Development] venky716:
Here you go, Zen decision with CpuQuiet

Flash this ukm to control CpuQuiet from synapse.

https://drive.google.com/file/d/0B_HLm5mfHuwKemFUNVowd2loVTA/view?usp=docslist_api
[ONE Original Android Development] Stroky:
Wow great. I will try that with the next update from omnirom

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] fermasia:
How did you compare against Zen Hotplug if I haven't even published a version using that? I'm actually testing one in my phone at this moment. What you are comparing is a completely different ROM using another custom kernel, that used a completely different config, to Omni + my kernel not using Zen Hotplug. I haven't had any lags at all using the default config (Smartmax, Deadline, PowEffQueues On) taking into account the whole point of the kernel is to balance optimizations so we can get a smooth enough experience with better battery results.

But there's no magic, if someone says their kernel will provide you with much more screen time and improved smoothness and better performance, it's just placebo or a scam... If any of us knew a magic way to boost performance and power comsumption we would be working elsewhere and not here...our only difference from stock developing is we dare to do not so stable things to push the limits a bit further.

Btw, touchscreen firmware is completely stock (haven't modified anything) so there can't be any difference from stock Omni. Can anyone else confirm having touchscreen issues?
[ONE Original Android Development] fermasia:
Sorry, but where's Zen Decision in your post? I can't see anything of that.

About the UKM flashable, please credit it propperly if you are going to link to other dev's work, that's Tyr's UKM. Jusst FYI, I will be updating my UKM whenever I get some time too.

Cheers :good:
[ONE Original Android Development] venky716:
Extremely sorry for not crediting [MENTION=4804871]DerRomtester[/MENTION] completely slipped my mind.

His is the only ukm that works with CpuQuiet AFAIK.

The setting im running is to mimic Zen which basically puts all cores online all the time.

Doing this on CpuQuiet and smartmax results is freq staying at around 1ghz while in use resulting in lower heat and lower battery consumption.

I remember Franco saying the best way to save battery is lower freq at quad core mode.

He also said all cores online wont work the same way it does with Nexus 6 due to 3.10 kernel.

The best we can hope is to use lower freq and thus reduced heat and drain.

I completely agree with your point that there is no magical kerne/rom out there, under similar circumstances the results will be same the only way to get more battery is by crippling performance and features.
[ONE Original Android Development] KenjiHannya:
UKM TYR v4 no chance?
[ONE Original Android Development] venky716:
Haven't tried, but I think tyr no longer uses CpuQuiet.

Its replaced by mako.

You could flash and see if CpuQuiet is still supported by v4 ukm.

Anyway v3 is sufficient for what I want it to do which is putting all 4 cores online. Rest I use kernel auditor anyway.
[ONE Original Android Development] KenjiHannya:
I flash v3

He appeared to you?
[ONE Original Android Development] venky716:
Yes I've the same, a lot more things don't work with tyr ukm that's why I use kernel auditor.

Sorry for the OT [MENTION=5190317]fermasia[/MENTION] I guess we should stop with this now.
[ONE Original Android Development] KenjiHannya:
Kernel Adiutor have been better ?
[ONE Original Android Development] DerRomtester:
Yes Cpuqiet is still inside UKM.

Of course there are these error messages if your kernel does not support this functions. It is especially desinged for my kernel.
[ONE Original Android Development] acidburn94:
Actually i'm getting very good results with smartmax and deadline and cpuquiet on, i am about 2.30 sot with 45 minutes of GTA and 55% remained! Thanks for your awesome kernel but i think zen hotplug will be even better;) good job!
[ONE Original Android Development] abhibnl:
To be honest the CPU Quiet is one of the smoothest yet battery friendly hotplug i've ever used. Now that i'm on CM build, i really can notice minor differences between mako hotplug in Tyr kernel and cpu quiet in omni. I have never tried zen, so i can't comment about it.

Sent from OnePlus One
[ONE Original Android Development] Bobbi lim:
I disabled CPUquiet as it was causing quite a drain on stock Omni kernel
[ONE Original Android Development] karthi89:
deleted
[ONE Original Android Development] fermasia:
You mean that you've switched to Mpdecision? Let me quote, just cause this comment may mislead some users, that if you disable both CpuQuiet and Mpdecision, there's no other hotplug driver in the kernel, meaning you'll be off any core hotplugging driver at all... and that won't probably give any better battery results, but worse ones.
[ONE Original Android Development] abhibnl:
I can assure you CPUquiet is way better than MPDecision.

Sent from OnePlus One
[ONE Original Android Development] DerRomtester:
Of course it is. It is a very smart hotplug.
[ONE Original Android Development] Stroky:
So it is like the zen Version?

Gesendet von meinem A0001 mit Tapatalk
[ONE Original Android Development] erad1:
Getting (XNPH25R-like) sleep numbers thanks to your kernel and Omni 11/17! Thank you for such a nice kernel!
[ONE Original Android Development] DerRomtester:
Zen what ?
[ONE Original Android Development] Stroky:
Sorry,

Zen Hotplug
[ONE Original Android Development] Bobbi lim:
That was on Omni's stock kernel which comes with CPUquiet.

Correct me if I'm wrong but I've used both CPUquiet and Mpdecision from HTC One X to HTC One M8 and now the OPO. To me, I rather have 0 hotplug turned on. CPUquiet is awesome when it comes to standby but it tends to cause relatively more drain when using. Mpdecision on another hand, causes more drain when idle but lesser drain when using. A simple comparison of CPUquiet and Mpdecision.

I've tried mako hotplug but it turned out causing more heat and drain. Intelliplug on the other hand seems to turn the phone very sluggish and everything lags and heats up causing a reboot.

All are compared against 0 hotplug being used.

I'm sorry I couldn't test out your kernel for you this weekend with latest Omni. The buttons on the phone as well as status bar's quicksettings doesn't work for me. I've tried the ROM + stock kernel, no gapps & SuperSU and I had the issue. I download and clean flash again with the same problem. I flashed ROM + kernel also same issue. I switched to CM13 also the same. I went back to 5.x and they were gone. My phone seems to have borked up this weekend.
[ONE Original Android Development] dankatz1:
Oh snap!

Stock Settings give me way better battery than the stock kernel of OmniROM from the 17th.

All day (about 13 hours with 4.5 SOT) outside on LTE with brightness set to manual high (about 80%?) with moderate use, left with 14ish% before charging. Moderate use.

Best compare for me though is when I'm playing vainglory (online MOBA). Average game would take me 20 minutes. On OmniROM stock kernel and stock settings I would have lost about 15%+ and on this kernel with its stock settings with the game on same settings I lose about 10%.

Always loved your kernel, thank you once again!
[ONE Original Android Development] fermasia:
Version 10 released

New version available. Many changes to be noticed (included Zen Hotplug driver and Zzmoove - disabled by default) and under the hood (new toolchain, new flags, experimental control of WLAN wakelocks, added Westwood TCP protocol, and many other optimizations). Let me know how this version goes, so that I can adjust things for the next release. As usual, you'll find the link in the second post, and aditionally check the third post about Zzmoove profile choosing details. :good:
[ONE Original Android Development] acidburn94:
Thanks fermasia:)
[ONE Original Android Development] kalapapa:
Does this kernel support f2fs

Thanks
[ONE Original Android Development] markvd90:
Flashed latest Omni and your kernel.

For some reason my wifi ain't working anymore.
[ONE Original Android Development] mk_bomber96:
WiFi is broke

---------- Post added at 10:04 AM ---------- Previous post was at 10:04 AM ----------

WiFi is broken

---------- Post added at 10:31 AM ---------- Previous post was at 10:04 AM ----------

Okay just tested

Both kernel v9 and v10 break wufi with today's omni marshmallow build.

Don't flash them with today's build.
[ONE Original Android Development] xflowy:
nice to see the zen hp got included. assuming you find out, that is has benefits to leave 4 cores on the whole time since hotplugging costs battery and running 4 corres on low is better then 2 cores on high.

could u tell me which governors you included?

thanks.
[ONE Original Android Development] fermasia:
People, right after I pushed v10, Omnirom pushed new kernel commits included in the new ROM build. That's why wifi's broken. I'll have to resync my source later today and reupload v10.
[ONE Original Android Development] KenjiHannya:
Ok, waiting for the new build for testing :D

Cheers :D
[ONE Original Android Development] cr3pt:
Any chance for new build today? :)
[ONE Original Android Development] jukiewalsh:
Don't know how much more clear he could say it.

"I'll have to resync my source later today and reupload v10"

---------- Post added at 09:16 PM ---------- Previous post was at 09:13 PM ----------

Didn't intend for that to sound so rude but he did already say later today
[ONE Original Android Development] DerRomtester:
No.
[ONE Original Android Development] fermasia:
Done, I synced with Omni's source and rebuilt v10, and reuploaded the file. Now wifi should work fine.

Sorry for the delay, back here it's still "today" - lol

:good::good::good:
[ONE Original Android Development] KenjiHannya:
Tnx ?
[ONE Original Android Development] just4u32:
Thanks for the kernel mate!

I just flashed the latest kernel, and your latest UKM.

I can control CPUQueit, but getting SSeekBar has failed on GPU Freq Scaling. Any ideas why?

Except that, does anyone feel like sharing a profile or detailed settings?

Thanks!
[ONE Original Android Development] asanuma:
How to set the profile number in Kernel Auditor once zzmoove selected?

I can't find Governor Optimizers.

Could anyone please assist me how to set it in Kernel Auditor?

Thanks.
[ONE Original Android Development] deepaklunked:
Using synapse is a good choice here.

Tapatalked through VM-ed Bacon
[ONE Original Android Development] sax0406:
The option is under the tunable section.
[ONE Original Android Development] asanuma:
I installed Synapse, where can I set for the profile number?
[ONE Original Android Development] Xerosnow:
I installed the latest build. My wifi is still broke. I'm on 11/17 build. Is there any workaround?
[ONE Original Android Development] kantjer:
Use Older kernel/Rom or latest ROM/Kernel don't mix.
[ONE Original Android Development] Xerosnow:
Oops. Would it work if I just flash the older version of kernel now?
[ONE Original Android Development] kantjer:
I think it will. Just try it
[ONE Original Android Development] Xerosnow:
It worked. Thank you :)
[ONE Original Android Development] jokermithun:
fusionjack's omni based rom with donkey kernel v.10 is really awesome experience:thumbup:...thank u sir for ur good kernel....feels like i own a new nexus device
[ONE Original Android Development] Knox316:
Lol

Enviado do meu A0001 através de Tapatalk
[ONE Original Android Development] fermasia:
I thought I had it solved with synapse and zzmove but I haven't. Stick with Kernel Adiutor for now. Right under the field where you select the governor you'll find the tunables section and there the profile_number to choose from.
[ONE Original Android Development] fermasia:
In case you haven't solved it already check my previous answer.
[ONE Original Android Development] fermasia:
Gpu freq seekbar is broken cause the sysf in Omni is probably different, I'll have a look at that. Kernel Adiutor seems to be the best choice for now.
[ONE Original Android Development] asanuma:
I have installed UKM and Syanapse.
[MENTION=5190317]fermasia[/MENTION] if I want back to use Kernel Auditor, how to unistall UKM?

Thanks.
[ONE Original Android Development] Bobbi lim:
No need to uninstall UKM. Just uninstall Synapse, do a reboot and download kernel auditor from the play store
[ONE Original Android Development] :
Using latest kernel with latest omni build, can I still use omni power profiles while using this?

Thx
[ONE Original Android Development] asanuma:
Done. Thanks
[ONE Original Android Development] jokermithun:
kernel auditor app works great with kernel....:thumbup:

Sent from my A0001
[ONE Original Android Development] fermasia:
Sorry, since 6.0 I haven't checked power profiles at all. Can you spot under what config option are them available?
[ONE Original Android Development] :
LOL you seem to be under the impression that I know this sh*t :p . I'm one of those that just chooses the easiest setup for my kernel, won't spend hours trying to configure anything .

If you tell me where to look I will gladly give you the info. I am referring to the power profiles enabled in the Performance Section of Omni (in case i didn't explain myself correctly).

Thanks!!
[ONE Original Android Development] fermasia:
I should have a better look, but power profiles will probably work fine, since they operate just by limiting cpufreq. I tried swapping the default profile and freqs were locked in any kernel monitor I checked. But if you want to use them to lock frequencies when screen is off, I'm not sure these profiles will profit you at all since the kernel already handles screen-off freqs. Give it a try, you won't brake anything you can't solve by unticking power profiles!

Cheers. :good:
[ONE Original Android Development] :
Awesome thanks
[ONE Original Android Development] brisac:
smartmax_eps and fiops scheduler aren't included or they will be implemented in future?
[ONE Original Android Development] :
charging was nonexistent on slimsaber and this kernel. It showed it was charging but for a good half hour without using percentage did not increase.

Also on Kernel Audiator not all frequencies were show in voltage section. which is to bad. Love this kernel :)
[ONE Original Android Development] fermasia:
Is this an ironic comment or my english is not good enough to get you right?
[ONE Original Android Development] fermasia:
I'll probably merge them back in the next release. Well, actually fiops was not included in v9 (but was on previous releases).
[ONE Original Android Development] :
I love the kernel, no irony buddy :)

just some issues I faced.
[ONE Original Android Development] fermasia:
Good you like, yet I wouldn't use a kernel if you can't charge your phone! :D

I haven't worked it for SlimSaber, I'm not sure what modifications have been done there, so things might not work.
[ONE Original Android Development] fermasia:
Sorry, duplicated post. :eek:
[ONE Original Android Development] :
I am having same issues on Omnirom unofficial 6.

I dont have the issue on lightning kernel version 4. I dont understand the issue, but I am not the only one.
[ONE Original Android Development] budbay:
Thanks for the good work, enjoying zz profiles on omni. Ive been using DriveDroid app for a while and i was wondering if you could add support for usb drive in your kernel. In the app forum he links this commit:

https://github.com/CyanogenMod/android_kernel_lge_hammerhead/commit/46bd47757a9f34c1d95dd2620414893212fb0526#

Or check out the drivedroid app forum here on xda. Everything is working in cd mode so not a huge deal if this cannot be done but would be a bonus. Thanks.
[ONE Original Android Development] fermasia:
I don't use drivedroid to test it, but I'll try to merge that code in the next release, as long as it doesn't bring up any conflicts. :good: Let me know if DriveDroid actually works once v11 is out.
[ONE Original Android Development] kodora:
Hey [MENTION=5190317]fermasia[/MENTION], I've been using your kernel for a few cycles now and I must congratulate you on a great job. For now I'm trying to fine tune zzmoove for my personal use and trying to fully take advantage of the hotplug part. But I have a little issue.. As it has been reported here, not all frequencies appear and when I undervolt, somehow the values don't stick. Thanks
[ONE Original Android Development] fermasia:
Can you ellaborate a bit more? What frequencies are you unable to see and where (synapse?)?
[ONE Original Android Development] budbay:
I will let you know. Thank you for giving it a try.
[ONE Original Android Development] kodora:
[MENTION=5190317]fermasia[/MENTION] I am using kernel adaptor because synapse is crashing when layers are applied to frameworks. But what I demonstrate here happened on synapse also.

The two screenshots that I post bellow show what I see.

On the screenshot where there are different mV values, is what happens when I undervolt globaly.

On the screenshot where the "null" is bellow 30 0 MHz, is what happens when I undervolt the frequency directly.
[ONE Original Android Development] pa.pn2:
very nice kernel so far

im very satisfied.

thx alot fermasia
[ONE Original Android Development] fermasia:
Ok, thanks for the feedback. That will be solved in the next-release (which might be coming soon).
[ONE Original Android Development] usmani:
I'm using kernel aduitor as well and I can't activate zen. I disable cpu quiet, only 1 core works then i activate zen hotplug and nothing happens. 4 cores do not activate only one core is working. Will you look into this too?
[ONE Original Android Development] fermasia:
Hello :good:

The problem is I can't reproduce that behavior. Here, at my end, it's working fine, all 4 cores pulgged in. Can anyone else confirm troubles like the one described by this user?
[ONE Original Android Development] budbay:
I can confirm, using kernel adiutor. I'm on zz relax, turn off cpu quiet, then turn on zen hotplug, only one core comes on line. when I turn on cpu quiet again all is normal.
[ONE Original Android Development] :
you might need their flashpath.

for me clean flash omnirom from Herna, then you kernel.

Or slimsaber then your kernel.

I think you could be dirty flashing donkey kernel upon donkey kernel version. If thats the case, with anykernel format it isnt entirely a mystery why it cant be reproduced :)

if you post from which version users should dirty flash your kernel versions they will likely have it fixered ;)
[ONE Original Android Development] fermasia:
I was finally able to reproduce it. It seems Zen Hotplug can't take over easily when it's enabled onto CPU Quiet, yet I haven't been able to get some propper logs or narrow the reason for it.

Still, there's a workaround: first turn off CpuQuiet, then enable Zen Hotplug and right after that, switch the CPU governor to any other than the one that was selected. Right after that Zen takes over propperly and you can set any cpu governor you like, including Zzmoove.

If anyone can provide some logs of the glitch, that would help.

Cheers :good:
[ONE Original Android Development] usmani:
That is not zen taking over, actually. If you turn off cpu quiet then without enabling zen switch cpu governor all four cores come online. No hotplugging is enabled.
[ONE Original Android Development] fermasia:
You may be right. But Zen is supposed to resemble that behavior by keeping all cores online too, so I can't be 100% sure if it's working at all or not. Are you completely sure it's not working at all? I should have a better look into Zen's code, I'm not familiar with it's logic, but as I've initially said, I don't see significant improvementes with Zen over CpuQuiet and I don't have a lot of free time to invest into into it, I must admit.
[ONE Original Android Development] usmani:
Yes when no hotplug is enabled all cores stay force online. Anyway remove it if it's not working, it's just keeping all cores online basically, which can be done like we talked above anyway.
[ONE Original Android Development] fermasia:
No, a hotplug driver does more than just plug and unplug cores during screen on time. It handles workqueues, screen off and on events, etc. You can have a look at the code if you like. Nevertheless, it's not like I feel it's the right choice for a config (it's not defaulted), we'll see if it's worth to keep it in the code or not.
[ONE Original Android Development] pa.pn2:
mhhh no wifi in latest omni build for me.anyone else?
[ONE Original Android Development] fermasia:
I was just about to post saying I saw some new committs pushed into the official Omni source, as herna has released a new build. Please, take into account that in such an early stage of MM developement, this will happen regularly, and when it does, things may fail until I get to update. And this is one of those times.

Why do I say this? Cause people come into the thread and see these posts and say "huh, no wifi with this kernel, damn" which is somehow true, but would be nice if they can get that information alongside the fact that is part of the developement process, and most important: that it will be solved as I release a new version later today.

I just wish users where this fast to post usage feedback, logs, etc. :p Well, not fast, I just wish they would do that at all! (Inner monologue: no, no, shut up and cut the crap, we know that's exactly how you get moody and begin wishing you had bought an Iphone where you can do fu**** nothing but avoiding to spare all this hours here).

Cheers :good:
[ONE Original Android Development] pa.pn2:
no problem dude

kernel worked in previous build without problems.i just wondered myself if its kernel or rom related

dirty flashed rom now,everything is fine.waiting for an update of your kernel:)

was just an alert for anyone else not to flash the kernel on top of latest build