yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] Xileforce:
In the log it looks like he got up to 115?? O_o
[Nexus 6 Android Development] simms22:
looks like it was a thermal shutdown according to the log :confused:
[Nexus 6 Android Development] hellsgod:
I just wasn't able to push it that hard before, thats why I was asking.
[Nexus 6 Android Development] simms22:
now why the chocolate fudge cant i get mine to shut down? im assuming you disabled thermal throttle? since it reached shutdown. if not, i bet its a bug. i always disable thermal throttle.
[Nexus 6 Android Development] bbedward:
I haven't been able to push it close to that hard regardless :p I'm still up on my original test build (slightly different than what's on github because it has debugging logs throughout)

All it does is bring cores online when screen comes on - but the worker thread is totally done after that. So even if screen goes off, comes on, thermal driver should shut them down if it deems necessary.

Idk what's causing that :confused: my phones still cold been playing music and using it periodically while tethering throughout the cavs game.
[Nexus 6 Android Development] hellsgod:
There's no problem with normal usage. I did a prime test with it. I just didn't rebooted any time I did it in the past, so who knows :) Maybe I pushed it harder this time than before. Thanks for your time :)

hells

---------- Post added at 02:42 AM ---------- Previous post was at 02:37 AM ----------

Oh, and btw. your zen-decision runs really well. In general it does the same like mako (4 cores always on) but Zen seems to perform better. I talked with a few people who are using the build and they all say the same. Less hiccups in scrolling and more responive. So is it just the simple way the driver handles the thing, which can give an improvement?
[Nexus 6 Android Development] bbedward:
I'm assuming the thermal throttling was unrelated although i've never seen it :p

But there's certainly less overhead to using ZD as a complete replacement to mako. Make has all the code that isn't used, but it is still constantly creating worker threads even while in 4 core mode I think. ZD is only (ideally) creating up to 1 worker thead at a time to make sure cores are online, and that's when the screen goes online. Otherwise the ZD driver should be completely idle.

and the one UP thread it does create should finish relatively quickly.
[Nexus 6 Android Development] aalupatti:
Where can I get more info about " Moto QuickWakeup" ?

Searched but could not find much

THanks
[Nexus 6 Android Development] hellsgod:
Yep, I was never using the active hp code in mako, thats why I gave your zen-decision a shot. And I'm impressed :)

hells
[Nexus 6 Android Development] Xileforce:
Gah see this is my conundrum. If I pull mako, ppl get upset cuz most ppl use mako, and lots like the hotplugging, and if I pull msm ppl get upset cuz msm goes down to one core :/ .....maybe zen decision + msm would be the way to go.
[Nexus 6 Android Development] bbedward:
Mako needs a disable toggle by default. Maybe I can help you with this later on :good:

ZD isn't ready to go into a zen release until I mitigate input boost. Probably use franco's touch notifier except I want to globally expose a configurable touch_boost_duration and share it between all the governors.
[Nexus 6 Android Development] Megaflop666:
Build it and send a test out
[Nexus 6 Android Development] wrongway213:
See how many peope use MSM on this kernel maybe? It doesn't feel natural or intuitive to me on Vindi at all, and I came from Hydra (the MSM kernel of all MSM kernels, lol)... I would be curious to see if I am the oddball who feels this way, or if others are still sticking with Mako even now that MSM is in the mix. I think MSM is a better hotplug, but not for your kernel, at least now with the current commits.. imo you need to pull WAY more from Hydra if you want to go MSM over Mako and make it perform as well as it does now.. but I could be the only one who feels this way. Just my 2 cents - quite curious what others feel about MSM on Vindi as an MSM fan myself.
[Nexus 6 Android Development] hellsgod:
In the end its still your kernel ;) If someone doesn't like it after that, there are plenty other around. You can't suit everyone.

hells
[Nexus 6 Android Development] Xileforce:
The global touchboost thing would be pretty cool! Although IK certain people,cough, [MENTION=1811927]simms22[/MENTION] , hate touchboost so they use ondemand. Also certain governors implement touchboost themselves, would those break? I've thought about adding in a toggle for mako before, and I even tried once back when I was even more noob but failed :(
[Nexus 6 Android Development] Xileforce:
I'm not quite sure what to pull to improve msm. I've already got all the msm commits. :( 85% of hydra is upstream patches and stuff. He does have touchboost though and he works that into the hotplug so that could be one thing.
[Nexus 6 Android Development] bbedward:
With a globally configurable touch boost interval you can set it to 0 in 1 place, and it will be 0 on all governors.
[Nexus 6 Android Development] Xileforce:
Oooooooo I like!
[Nexus 6 Android Development] wrongway213:
I dunno what it is, all I know is I have run all the other kernels (Franco, lean) you pull from and your versions of their governors all run great, even compared to the "original" kernel in question. However, running this and running Hydra with same settings... your kernel does not do well on this test. I am not sure what to make of this.. maybe just my device setup on Hydra, why I said I am curious what others say.. not comparable on my phone though lol but this is awesome on interactivex or conservative for me.. make of that what you will lol
[Nexus 6 Android Development] hellsgod:
Hydra uses cpu boost. I dont think cpu boost is needed that way. You have different boosts, like hotplug boost and thread migration boost for example which can smooth out some jitters or even give you better performance. If you dont use any active hp anymore, you don't need a thread or hp event boost. I'm just using zen-decision and a touch boost for 500ms on all cores and the device runs better than with any active hp.

I think its just a different way to handle things :)

hells
[Nexus 6 Android Development] bbedward:
Well if google/QC/Moto decided "active" hot plugging doesn't provide any benefit on this device, who is to say they are wrong :)

Also if the drivers like mako are leaving CPUs offline permanently in "all-core mode" then I'd assume that's not a very desirable behavior either ;)
[Nexus 6 Android Development] Xileforce:
OK guys, just made a test build with zendecision only in it. No msm or mako. Cuz ik some ppl wanted to try it. Here ya go

https://docs.google.com/file/d/0B6n0VW96A9ModTFhWEJWT1A3b0k/edit?usp=docslist_api
[Nexus 6 Android Development] Custodian:
Heh, Google is still struggling to fix **** like "memory leakage" let alone "perfect" UI smoothness at 60 FPS. Leave it up to the non-google devs on XDA to figure out that if you sync up the update interval with actual screen refreshes, you eliminate ui jitters and increase overall smoothness of animations lol...its Google of course they have some of the most talented devs, but doesn't mean they're the say all in the android community.
[Nexus 6 Android Development] bbedward:
Hey, ZD is a "handler" for the malfunctions caused to the system that the disabling of MPD causes.

It isn't written by google/Moto/QC though :)

The fact that replacing MPD in-kernel rather than just using MPD is still up for debate though :p
[Nexus 6 Android Development] jiv101:
I'm really hating synapse right now.... It's changing my kcal values and making it this weird dark translucent colors
[Nexus 6 Android Development] Custodian:
Throw me a test kernel, let's see... :)

---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------

Uninstall and reinstall Synapse, that did the trick for me :p
[Nexus 6 Android Development] Xileforce:
https://docs.google.com/file/d/0B6n0VW96A9ModTFhWEJWT1A3b0k/edit?usp=docslist_api 2.3 with mako and msm removed and zen decision added.
[Nexus 6 Android Development] info[]box1:
[MENTION=4517211]Xileforce[/MENTION] ... Hey remember me Vinny Blanco from the Bronx.

I need your UKM uninstaller zip. Please kind Sir. No issues or troubles, just would be nice to have in my backpack. ;)
[Nexus 6 Android Development] Xileforce:
I don't have a ukm uninstaller.zip but I believe there is one in the ukm thread.
[Nexus 6 Android Development] info[]box1:
Copy that. Well I have that one, not sure if needed a special one. Since I flashed an special one.. Guess I'm good. Thank for all "energy and persistence"..
[Nexus 6 Android Development] bbedward:
My solution is not yet complete, until then ;)

XileForce and others already have solutions to handle the other functions of MPDecision, zen doesn't have these yet. And I'm not quite happy with the current solutions so until I put it all together there won't be a complete Z solution.
[Nexus 6 Android Development] Xileforce:
Z solution :D sounds like something that saves the world during a zombie apocalypse. Just throwin that out there.
[Nexus 6 Android Development] bbedward:
I don't like things so divergent :p why have 7 settings for 7 governors when we could just have 1. Changing cpufreq governors used to be a popular and easy option for kernel tweakers, if we make changing between governors inconvenient by changing specific governor code or by removing functionality when changing between them then that is certainly against my goals :)
[Nexus 6 Android Development] Custodian:
Flashed, boots but "ilauncher" is the launcher I use to test animation speeds for stutter/jitter etc, for various ROMs and it just lags like hell using vindicator, I have no ideal on how to reproduce this error with logs either. Tested with every governor and scheduler too...lol
[Nexus 6 Android Development] Xileforce:
Hmmm...I just tried it myself and it seems to run fine. However there is a few things that I can this k of that may be affecting it. GPU min frequency on vindicator is 110mhz which is quite a bit slower than 240mhz. You can try raising your min frequency for GPU to 240mhz in synapse. You could also try running simple on demand governor for GPU which is a tad more aggressive. If that fixes it for you I can probably fix that kernel side.
[Nexus 6 Android Development] dwang:
Thats strange, its buttery smooth for me running chroma. I like it better than mako.

I'm using the google now launcher.
[Nexus 6 Android Development] Xileforce:
Completely agree and look forward to seeing your implementation :)
[Nexus 6 Android Development] bbedward:
Why not check on the CPU activity and frequency using something like kernel auditor? Make sure everything's online and behaving correctly.

And also...

Spoiler content hidden.
[Nexus 6 Android Development] Xileforce:
Oooooo how do u find interactivity improvements O_o
[Nexus 6 Android Development] bbedward:
J

On a solid state hard drive:

https://youtu.be/1cjZeaCXIyM

Also http://algo.ing.unimo.it/people/paolo/disk_sched/results.php

The latter shows results on a variety of storage mediums including emmc.

Certainly better than cfq, I respect Paolo's test since maintaining BFQ for at least a few kernel releases many years ago. The simple light deadline/noop solution may not be ideal (or even close to ideal) for even solid state applications.

Basically while read/write jobs are going on in the background foreground activity isn't compromised. So I can be bringing up my photo collection to my phone from PC and my phone isn't going to become unusable because of the way BFQ is prioritizing interactivity.
[Nexus 6 Android Development] Xileforce:
Interesting! How does fiops compare? That's always been my goto
[Nexus 6 Android Development] bbedward:
No idea but fiops is apparently a dead project with no maintainer. Last update 3 years ago?

BFQ may eventually replace CFQ as the heavy disk scheduler in mainline Linux (because upstream won't accept more than one in the classification). Since BFQ is heavily based on CFQ they've suggested submitting it as a patchset on top or CFQ. I can't speak for that process specifically but only for the current results BFQ gives :)
[Nexus 6 Android Development] Xileforce:
Oh wow I did not know that about FIOPs. Previously I had gotten my highest androbench scores with FIOPs but now u have converted me! Going to try out BFQ.
[Nexus 6 Android Development] bbedward:
The androbench scores are irrelevant. Refer yourself to the youtube video I posted which shows all thoroughput scores as being pretty much equal on SSD between CFQ/BFQ/Deadline/Noop. It's the interactivity factor that makes a difference, even on SSD (like BFS).

From my tests, I/O scheduler nets no difference in androbench but that isn't the whole story
[Nexus 6 Android Development] Xileforce:
Yea that video is impressive. I'm running bfq right now and am going to see how things go over the next day or so.
[Nexus 6 Android Development] bbedward:
Combine that with ZD and you will be OK ;)
[Nexus 6 Android Development] Xileforce:
Yes, master.
[Nexus 6 Android Development] linus207:
2.3 zd is flyin! I am speechless! Zen all the way.
[Nexus 6 Android Development] bbedward:
ZennyVindyvici?
[Nexus 6 Android Development] Xileforce:
Lol I see what u did there
[Nexus 6 Android Development] linus207:
What bfq read ahead buffer size would You recommend ?
[Nexus 6 Android Development] bbedward:
This is a setting irrelevant to the I/O scheduler itself, but I think 1024 is OK. Not sure what (if any) benefits are seen from increasing it. I don't know of any way to really measure :p
[Nexus 6 Android Development] Custodian:
No no no, install ilauncher from the app store by suckgami...I have 0 issues with launcher3 based launchers

---------- Post added at 12:42 PM ---------- Previous post was at 12:32 PM ----------

Using synapse I see that the kernel GPU defaults to 27 MHz even with the min set to 240mhz :p..that could be the issue.
[Nexus 6 Android Development] Megaflop666:
Loving this build, just flashed it again over the latest temasek v11.1 he [MENTION=3515982]apascual89[/MENTION] unleashed this morning. Zen decision makes everything so much sweeter...
[Nexus 6 Android Development] Xileforce:
That is normal. It will always go down to 27mhz when it isn't doing something. That's its idle freq.
[Nexus 6 Android Development] linus207:
I think You have a name for new Zen Kernel [emoji41]
[Nexus 6 Android Development] Megaflop666:
Zendicator
[Nexus 6 Android Development] Shilalygawd:
Can't get it to boot with AOSIP :(
[Nexus 6 Android Development] jarjar124:
I've been getting some crashes/reboots when using zen decision. I would be browsing web or texting then my phone would freeze then reboot. I know I have to post a log and I will tonight. I just reverted back as I have school and can't have it rebooting at times. Just wanted to let you guys know. Might just be me tho. Lol
[Nexus 6 Android Development] aoaleman:
Weird, working perfect here.
[Nexus 6 Android Development] bbedward:
Yes any stuff from /sys/fs/pstore/ would help track it down :) it shouldn't be doing anything while the screen is on really, but if there's a bug somewhere I'd like to find it, I'm up 17 hours myself on it atm
[Nexus 6 Android Development] hellsgod:
Zen-decision also works in an internal test build from me on a few devices since you pushed it to git. No crashes or other things to mention :)

hells
[Nexus 6 Android Development] Xileforce:
Same. Running solid here.
[Nexus 6 Android Development] tansuperman:
I guess the ota app doesn't work. It says I'm up to date, yet there is a new version. 2.3. No biggie, I'll just delete the app and update here.
[Nexus 6 Android Development] USA-RedDragon:
Try deleting /sdcard/Vindicator folder
[Nexus 6 Android Development] Xileforce:
I recommend following the pushbullet channel as well because that will always work. In case app doesn't for whatever reason
[Nexus 6 Android Development] le1tho:
I am getting freeze and reboot when changing from other GPU governors back to msm-adreno-tz. All others except msm-adreno-tz don't give freezing. I noticed it already from 2.3T2, then 2.3Simms3 and now on 2.3-not the zen one.
[Nexus 6 Android Development] Xileforce:
Its been happening for as long as I can remember :( I'm not sure what is causing it as I only use Zens GPU commits AFAIK :(.
[Nexus 6 Android Development] MarceloSiciliano:
Its just my phone or using zen hotplug generates a lot o heat?
[Nexus 6 Android Development] tatoniss:
Giving your test kernel with only zen decision a try. Haven't tried it long yet but the interactive governor was kind of laggy for me. Switched to ondemand and man this thing flies. Actually got a antutu score that was around 51000. I haven't got that on a 5.1 rom without using the performance governor in a long time.
[Nexus 6 Android Development] Aerigon64:
Which kernel is better for battery life when web browsing and using Tapatalk, conservative, intelliactive, or on demand.
[Nexus 6 Android Development] Xileforce:
You kinda just have to try them all. I like conservative. Because it is on demand based and I think its a bit smoother than interactive.
[Nexus 6 Android Development] Xileforce:
No issues here. It does leave all 4 cores on whenever the screen is on though

Interactive can be laggy at times. I recommend giving conservative a shot if you like on demand. Conservative is on demand based and has some neat patches in it.
[Nexus 6 Android Development] hellsgod:
I'm not done with my testing, but the overall picture in my kernel seemed to be better with mako in quadcore mode. No idea why, because it does the same like zen, runs all cores on screen on. Zen was faster in some areas, maybe because there's no active "active hp" wq in the background on zen. Most of the team said the battery / heat is better with mako and switched back.

hells
[Nexus 6 Android Development] Aerigon64:
Yeah I try the all the problem is I'm addicted to changing settings so I haven't ever been able to test exactly what effect different settings and governors have. ?
[Nexus 6 Android Development] LunaticSerenade:
The DreamManagerService wake lock is evil. But, 8hrs 40mins awake, and I have 49% of my battery left. :D

Sent from my Nexus 6
[Nexus 6 Android Development] Xileforce:
Interesting. I think I actually got like the best battery yet on ZD xD
[Nexus 6 Android Development] SeVIIn:
Seeing a 0.5% increase in battery drain per hour on the ZD version and a 2.8% drop in overall benchmarks, don't personally notice a difference in responsiveness one way or the other though.
[Nexus 6 Android Development] bbedward:
^^^ ZD doesn't actually do anything while the screen is on :) no threads running, nothing but idle. All 4 cores are staying on, but that's the stock behavior.

Remember the purpose wasn't to replace mako , just handle the cases of CPUs never coming online when disabling MPD ;)
[Nexus 6 Android Development] MarceloSiciliano:
Just got back to the build without zen
[Nexus 6 Android Development] Xileforce:
This is why I can't understand any of the reports I'm seeing O_o
[Nexus 6 Android Development] bbedward:
I did change this, https://github.com/bbedward/ZenKernel_Shamu/commit/a49992b4362cbcd0f1c053077b42c6c3d431de7e . Which may alleviate some unintended issues.

Likewise i adapted touchboost to be on the governors specifically, but to be adjustable globally in:

/sys/kernel/touch_boost/{input_boost_duration_ms, input_boost_freq}

Not sure if you want to change to that, but I prefer it :silly: I never change governor anyway though.
[Nexus 6 Android Development] Shilalygawd:
I wish I knew your secret. I've tried everything with the current 5/3 build. 2.2, 2.3, and 2.3T1&2 all lead to a bootloop on AOSIP for me
[Nexus 6 Android Development] Xileforce:
Possibly some new ramdisk changes on the latest build.
[Nexus 6 Android Development] LunaticSerenade:
Regarding the DreamManagerService wakelock.

This was not an issue on a Vindicator a few versions ago (I couldn't tell you which one precisely).

[MENTION=4517211]Xileforce[/MENTION], do you have any thoughts on what could be causing it?

I know ambient display will have some impact on the battery life, but it shouldn't make it be awake 100% of the time.
[Nexus 6 Android Development] Xileforce:
Can u post a screen shot of your BBS kernel wakelocks and partial wakelocks page and other page for me again please? BBS is what I use so that's the one I understand.
[Nexus 6 Android Development] LunaticSerenade:
I will after a full day of use.

Just for funsies, I wiped dalvik and cache, flashed 2.3 (the non-ZenDecision one), and so far, it's sleeping like a baby.

We shall see what it does tomorrow. I'll put up some screenshots after about 75% battery usage.
[Nexus 6 Android Development] Shilalygawd:
Hopefully it'll work itself out on future builds. I feel naked without your kernel.
[Nexus 6 Android Development] urnamese3:
Edit: nvm
[Nexus 6 Android Development] hellsgod:
Yes, sure. But Zen and mako had the same purpose in my builds, run all cores online on screen on. Thats why I don't understand the difference :)

hells
[Nexus 6 Android Development] info[]box1:
100% euro skank thick center cut bacon ROM and grade A vindicator kernel. Will make you slap your momma. xD
[Nexus 6 Android Development] linus207:
I have noticed little worse battery life on 2.3zd. Usually I got 6.5h sot, now I have 5.5h
[Nexus 6 Android Development] bbedward:
In 4-core mode mako isn't doing anything except creating a thread every 2s or so. The thread doesn't really do anything except keep repeating itself.

ZD was solving the problem of cores going offline permanently at low battery or from a thermal event, etc.
[Nexus 6 Android Development] rignfool:
So... In layman's terms... And in theory... We would get better battery life with ZD because its not 'running' like mako HP is?

Meaning creating threads uses CPU cycles and ZD does not do this?
[Nexus 6 Android Development] bbedward:
Potentially in theory, both are suspendable and go idle during suspend. The timer mako is running doesn't really do any work (when in 4-core mode) so it isn't really taking a noticeable amount of CPU time. I gave hells and xileforce a patch that adds a disable sysfs to mako so it can be disabled.

So disable it -> stops running threads, clears any pending threads. Enable it -> starts it back up again.

Zen is running a thread to check CPUs every time the screen comes on, if the battery is > 15%.
[Nexus 6 Android Development] hellsgod:
The question for me remains why my tester switched back to mako, because they noticed more battery consumption, if both are doing more or less the same in quadcore mode. I'm just curious why that could be. I haven't done my testing yet, I only refer to the feedback I got. I've released a mako and zen-decision build to get a bigger picture. Maybe my tester were wrong, we'll see :D

hells
[Nexus 6 Android Development] bbedward:
From the code perspective I don't see that as a possibility. Maybe they suffered from permanently disabled cores and didn't notice it ;)

I have made some cleanups and modifications to it. Not redundantly initializing the work anymore, and it can be scheduled on any CPU (first version was locked to cpu0 at all times), so maybe those will help :)
[Nexus 6 Android Development] simms22:
ive been seeing about the same battery life using previous kernels and zd. as long as i use ondemand, i see around 5.5h+ sot mostly.
[Nexus 6 Android Development] eltnav:
I am getting lower benchmarks with ZD. How about you guys?
[Nexus 6 Android Development] Xileforce:
This is what I've been telling ppl who report bad battery life too lol

Yup same, my battery may have actually been a bit better.
[Nexus 6 Android Development] rignfool:
Not that my comment means anything...

Doesn't ZD have its own boost?

So wouldn't your tester(s) be boosting twice... Since you boost in governor?
[Nexus 6 Android Development] hellsgod:
Nope. Zen doesn't have a boost. Touch boost is independent :)

hells
[Nexus 6 Android Development] le1tho:
But isn't all 4 cores always online bring less battery life against hotplugging?