yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Purpeltendire:
Thanks, I appreciate it.

Thank you. :) Anything in particular you'd like to see?

EDIT: Phone decided to shut itself off while I wasn't paying attention, so the stats were all reset. No results today unfortunately. :(
[HTC Rezound] Squirrel1620:
Re: A Governor a Day

Ok so this was intellidemand underclocked 1.35 ghz normal usage mostly 3g/wifi
[HTC Rezound] Purpeltendire:
Re: A Governor a Day

Thanks. That definitely makes me think something weird went on with my device, there was way too much use from the Android OS. I'll redo it tomorrow and hope for better results.

Sent from my Infected Rezound.
[HTC Rezound] zekemo:
Re: A Governor a Day

I like battery monitor widget pro, it has great graphs that show all sorts of info while screen is on/off. Also, thank you for this tread it will be a very interesting read
[HTC Rezound] ozo012:
Hey Squirrel,

Would you mind posting your voltages and other detailed kernel settings? Also what app are you using (Kernel Tuner I assume?)

Thanks!

Chris
[HTC Rezound] Squirrel1620:
Re: A Governor a Day

Android tuner
[HTC Rezound] Purpeltendire:
Re: A Governor a Day

I installed it this morning to try it out, but I've been having stability issues since I installed it; random reboots and such. I have a feeling that running about 5 monitoring services at once isn't helping things either.

I'm not getting any abnormal CPU usage this time around with Intellidemand, though.

Sent from my Infected Rezound.

Update: I've been having stability issues all day since switching from Funky to Linaro Deluxe+ by iHateWEBos. I *think* it might be my massive undervolting (-100mV). But I'm not sure. Hopefully I can get it sorted out before tomorrow. Sorry for the delay in testing.
[HTC Rezound] chupajr:
Yeah, it's almost certainly the undervolting, especially if you are running overclocked.
[HTC Rezound] Purpeltendire:
Re: A Governor a Day

I'm underclocked actually. :p But since I upped voltage by 25 all around, the reboots have stopped.

So now I'm back to normal, testing OnDemand today. I'll have to go back and redo the ones I've already done, given the changes in kernel and voltage. I'll do a few more before that though, I know Lionheart was requested so that will definitely come tomorrow.

Sent from my Infected Rezound.
[HTC Rezound] Purpeltendire:
50% down on OnDemand.

OnDemand at 50%

Intellidemand at 50%

If I'm honest, I don't really feel a difference between this and Intellidemand. It seems to be draining a little more evenly than Intellidemand, but other than that there's no real change in smoothness. I can see why this is the go-to default governor though; it's a great, well-rounded governor that balances smoothness with battery life, and doesn't make any huge sacrifices. Because OnDemand is less GPU-bound than Intellidemand, it's probably going to end up being a better choice than Intellidemand. But I'll save that conclusion for tonight. :)

Forgot to mention something. I'm using Battery Widget Free to try out what zekemo said. It's decent and it has an absolute wealth of information, but it seems as if it takes a lot of power to do its monitoring compared to other services like GSam or SystemPanel. It also seems to have a lot of stuff that might be useful to some people, but that just aren't needed in my use.
[HTC Rezound] Purpeltendire:
Well, not much has changed since the 50% post earlier.

OnDemand End 1

OnDemand End 2

OnDemand End 3

Man this one was boring compared to Intellidemand. No weird stuff, no crashing, nothing exciting whatsoever. I think that's my verdict on OnDemand. It doesn't do anything badly at all, but it doesn't do anything so great that it outshines anything else. It's completely average. :p

Even the graphs look the same as Intellidemand... further emphasizes my point haha. If you're not looking for anything in particluar, go with this governor. It's the best of every world, rolled into one well-rounded package that just does things right. I wish I had more to say, but there's just not that much to talk about here. Have a good night everyone!
[HTC Rezound] sanders539:
Re: A Governor a Day

This may sound dumb so forgive me, is it not good to have different governors on each CPU? Like maybe on demand for CPU0 and DanceDance on CPU1?

Another thing, I am trying to get android tuner to set my governors, but it is failing to set it for CPU1. It keeps changing it back to badass.

I don't quite understand what it means with the "free" setting either... i am guessing it is setting it to come on only when needed, however it never shows it coming on. CPU0 will go to 100% and CPU1 will say offline...
[HTC Rezound] Purpeltendire:
There's no such thing as a dumb question. :)

I think it is, especially when you have each core running independently. However to get the full effect of each governor I test and to not mix results, I'm testing with both cores on the same governor.

I don't know about the issue with Android Tuner, as I use Kernel Tuner because I like the UI a little more. If you're willing to try Kernel Tuner then I could help you out via Private Message, otherwise I'll let someone else chime in.
[HTC Rezound] shrike1978:
If anything, you want to use a performance oriented governor like ondemand on the second core, the idea being that you want it to finish its work as quickly as possible and turn back off. As for when it switches on, it's not instant as soon as the CPU goes over a certain level...at minimum, the first core has to go above the idle_freq and stay there for a certain number of checks. The sample rate of the Android Tuner interface is much, much, much longer than the sample rate that mpdecision is working at, so it's quite likely that the frequency is bouncing up and down behind the scenes that you aren't seeing. Frequency isn't the only thing that goes into a CPU plug decision either...it's important, but there are other things as well, and just being above idle_freq by itself is not always enough to plug the second core.
[HTC Rezound] Purpeltendire:
Thanks for that shrike. :)

Okay, Lionheart. First, sorry for the lack of a 50% post for this. I watched a movie, and when I came back to my phone it was at 40% already haha.

Lionheart 1

Lionheart 2

Lionheart 3

If you don't care about battery life, this is going to be a good governor for you. :p Even during idle periods (like watching a movie) the battery drain was around 5% per hour. Over the course of the day the battery drain was at 6.3% per hour according to BetterBatteryStats. The only other comparison I can draw to that is against Intellidemand, which was at 4.9%. That's a 1.4% difference per hour, which over Lionheart's 13 hour life would have meant an extra 18% of battery -- that's almost one fifth. :eek:

One thing I did notice that sets this governor apart from others was the amount the governor put the CPU up past the limits I set in Kernel Tuner. It did this with OnDemand too I believe, but I noticed it more with Lionheart for some silly reason.

As far as feel goes, Lionheart feels superb. I did notice it seemed to slow down a lot when opening a bunch of tabs in Chrome, but other than that it was smooth and handled daily tasks with ease.

Due to the quick ramping up of speeds, this is a good governor if you use your phone on and off frequently; ie you pull your phone out to check something several times within a small period, or you're constantly answering emails. But that being said, I really hope you either have an extended battery or a charger nearby, because you''re going to need it. I barely got 1:45 in screen-on time before I took the screenshots, with below 20% battery left.

Any suggestions for a governor tomorrow?
[HTC Rezound] Squirrel1620:
Re: A Governor a Day

Very nice wright up I've never used Lionheart.. I believe smartass is a pretty popular one
[HTC Rezound] Purpeltendire:
Smartass it shall be! iHateWebOS's kernel has V2 so I'm using that.

SmartassV2 at 50%

Missed it by that much... as I checked the percentage it clicked from 50 to 49. :mad:

So far I quite like this governor. The battery drain isn't bad, I think it's around 4% per hour. It feels very responsive and there's not a lot of lag. Applications were opening faster than in Lionheart, which I found interesting. I won't get into specifics until tonight's post, but so far I'm a fan. If there are no suggestions for tomorrow or Friday, I might compare this to Wheatley and redo Wheatley/DanceDance under the new settings. I think they're very comparable, but I honestly don't know which would be better.

Stay tuned! :) Final Smartass post will probably be around 0100-0200 EST. These are probably pretty late for you eastern guys, sorry about that. But I usually crash around midnight PST. :p
[HTC Rezound] sanders539:
Re: A Governor a Day

What scheduler are you using with this governor?
[HTC Rezound] Purpeltendire:
I'm doing all these tests using Noop. :)

Alright, here's the final results on SmartassV2.

SmartassV2 End 1

SmartassV2 End 2

SmartassV3 End 3

Battery drain ended up being about 4.4% per hour, which is a lot better than Lionheart's 6.3%. As I said in the 50% post, it felt very nice, very little lag that I noticed. I really really liked the fact that when the screen is turned off, the phone goes straight to Deep Sleep without sitting at 192 MHz. I think with a bit of tweaking, I could easily find myself using this as my daily governor whenever I'm not testing.

The scaling was extremely aggressive though. The CPU spent almost zero time away from the 1566MHz max set by the governor itself. Sure, it made to get things done, but at the cost of battery life. I don't really need a full clock to answer a text message before I turn the screen off again. :p

During use, I noticed the usual battery drain while XDA loaded all the new posts, or a web page was being unresponsive. But there was nothing over-the-top about the drain. CPU according to the grahps on SystemPanel showed far lower loads than any other governor so far; makes sense given the amount of time the phone was in Deep Sleep.

Overall this is a very nice daily use kernel, I can see why it's popular. Immediate ramping down of the CPU once the screen is off is a great feature, and the phone ramps up so quickly you're not likely to notice any lag.
[HTC Rezound] Purpeltendire:
Taking today to sort out the update of Infected 2.2 (reboots galore, SwiftKey issues until like five minutes ago, etc.),

I'll be doing the default for the Deluxe+ that comes with it (lulzactive) tomorrow, and then if nothing gets requested I'll go back to DanceDance and Wheatley and do a big comparison between DanceDance, Wheatley, and SmartassV2. :) Depending on how Lulzactive performs, it might be in the comparison as well.
[HTC Rezound] Snuzzo:
Re: A Governor a Day

Making some changes to my source so if you wish to use my kernel in these tests also/instead you will be able to.
[HTC Rezound] sanders539:
Re: A Governor a Day

I have started using the smartassv2 governor after reading your review of it. I have to say, it is very good. I am using the row scheduler and I only lost 2% battery in an hour. Granted that was just sitting on the counter while I work. But even using the phone to browse xda, it seems to be doing a lot better than before. I would like to see a review on lulzactive. I haven't seen any explanations on that governor so I don't really know what is designed for.
[HTC Rezound] shrike1978:
lulzactive is basically interactive with variable frequency scaling and a built-in sleep profile.
[HTC Rezound] Purpeltendire:
Thanks! Your kernel was great for undervolting, handled it much better than Deluxe+. But the massive number of governors in Deluxe+ is experiment friendly.

Glad I can help. :) Is there anything to read on how ROW works? I can't say I've looked a whole lot, but I don't know much about it.
[HTC Rezound] sanders539:
Re: A Governor a Day

I have not found anything on row. I tried running row with lulzactive and got a lot of reboots, I don't think they like each other too much. I am looking forward to your next review!
[HTC Rezound] shrike1978:
ROW stands for Read Over Write. It's a fairly new I/O scheduler that is designed from the ground up for flash memory based mobile devices. It does not implement any fairness or operation ordering. Instead, it breaks things down into several first-come first-served queues, based on read vs. write and the priority of the operation. Each of those queues gets a number of allowed requests, 100 each for reads and high priority reads, 2 for high priority synchronous writes, and 1 each for regular and low priority writes, synchronous writes, and low priority reads.

Each I/O request that comes in gets put in the appropriate queue. It serves all reads first, then synchronous writes, then asyncronous writes, in priority order (high to low), serving a request at a time out of the current queue, decreasing that number of allowed requests each time. It continues serving requests out of the current queue until either the number reaches 0, or there are no requests left in the queue, then it moves on to the next one. If it empties a queue and there is still a positive number of allowed requests associated with it, it will go back to that queue and serve new requests that come in before continuing with the lower priority queue. It continues this until all queues have be processed, then the request counts get reset and it starts over at the top.

The idea is that since we don't need to worry about ordering requests (since flash memory doesn't need that), and mobile devices are much more dependent on reads than writes in order to be responsive, we should heavily priority reads over writes, but we shouldn't let reads complete starve writes.

The above is the way I implement it in my kernel and is the reference implementation. It's possible to tune those queue depths to pretty much anything at compile time.

---------- Post added at 10:14 AM ---------- Previous post was at 10:01 AM ----------

Totally offtopic here for a bit, but I just noticed you're from Elba, sanders. I grew up in Opp. O.o
[HTC Rezound] Purpeltendire:
Thank you sir. :) That helped a lot.

Today is a heavier usage day for me, so the battery stats might be less accurate than I'd like.

Lulzactive at 50%

Performance-wise, I haven't found much to complain about. It seems to keep up just fine, the only laq I experience is right when I open Chrome - if I try typing too quickly, it often bogs down or crashes the app. But I think that's Chrome and not the actual governor, because I see that regularly.

I did have a pretty big wakelock this morning though. Apparently after I turned off 3G/4G and Wifi, GApps decided it really wanted to update everything, so while I was at the gym my phone was trying valiantly to check my email for me. :p Unfortunately while it did that it drained nearly 15 percent of my battery.

After that, the phone settled down. Battery consumption while idle doesn't seem out of the ordinary -- the stats are screwy because of the wakelock, but for about an hour of not using it, I saw about a 1.5% drop. Overall usage should probably be in the neighborhood of 5%.

Note: I might have to redo this tomorrow or something. The wakelock really messed things up. :(
[HTC Rezound] sanders539:
Re: A Governor a Day

For some reason I can not get that kind of screen on time. While on the road today with the boss, I was catching up on some reading and with only 45 minutes of screen on time, my phone dropped down to around 40%.

We are practically neighbors shrike!
[HTC Rezound] Purpeltendire:
Are you using auto brightness, or manually setting the brightness to a fairly high level? Outdoors, or anywhere there's lots of sunlight, you need the screen brighter. I tend to spend a fair bit of time indoors, so I don't need to go past the first 3 or so notches on the brightness slider very often.
[HTC Rezound] sanders539:
Re: A Governor a Day

I never use auto brightness. I do have to keep the screen pretty bright BC of being outside, but I would still expect about and hour and a half screen on time.

A little more on topic, if you had to rank the governors you have tested so far, how would you rank them?
[HTC Rezound] Purpeltendire:
Hmm interesting. Do you have any big wakelocks that are preventing your phone from sleeping when it's turned off? Also, what're your voltage tables like and are there any apps that push notifications constantly?

Oooh... good question.

SmartassV2

Wheatley

DanceDance

OnDemand

Intellidemand

Lulzactive

Lionheart

Those are based on my usage, because I don't play games or benchmark or anything. So battery life, smoothness, and app responsiveness are what matter the most for me.

Okay, Lulzactive. I'm definitely going to do this again tomorrow, on top of the wakelock I didn't have SystemPanel's monitoring service running. :(

Lulzactive End 1

Lulzactive End 2

Lulzactive End 3

Experiences were decent, other than the wakelock. Towards the end of the day it seemed like it was holding battery quite well while I wasn't using it. Screen-on time was excessive during the first half of the day, and then minimal during the second half haha. Looking at the CPU Usage charts, the ramping up was very good. I didn't notice any weird crashes or abnormal 'chugging' (CPU not keeping up). But I really do need to use this for another day to get a good idea of how it performs.
[HTC Rezound] sanders539:
Re: A Governor a Day

Well, handcent every now and then will hold a wake lock when it is trying to download a message. (Which that app isn't working right after flashing infection) Other than that, no unusual wake locks. If the stock message app would do group messaging right, I wouldn't use handcent.

Edit: Not sure what is causing this..

https://www.dropbox.com/s/anx0ak3cufflp3o/Screenshot_2013-03-08-23-49-10.png
[HTC Rezound] Purpeltendire:
Quick search shows a popular fix attempt is clearing your applications cache. If that doesn't work try this:
[HTC Rezound] Purpeltendire:
Today was a far more accurate representation of Lulzactive than yesterday, I'm glad I chose to redo it.

Lulzactive Redo 1

Lulzactive Redo 2

Lulzactive Redo 3

Also, as you can see I changed around the screenshots. I took out redundant information (IE Apps list being listed like 3 times, battery graph, etc)

Sorry for the lack of the 50% post, I was pretty busy today (and my car battery died in a parking lot, yay).

As I saw yesterday, the ramping up was quite good. I found there to be very little lag in anything I did. Battery life was constant around 5.5% per hour, regardless of whether or not I was using the phone a lot or not. The only exception to that was using Maps w/Location on, which doubled the consumption.

Overall, I can't say I'm incredibly impressed with this governor, but I can't say it was bad either. Shrike hit the nail on the head, it's a pretty basic governor with frequency scaling and a sleep profile. It's a little more conservative than Ondemand was, and I think if I had used Ondemand for the same amount of screen-on time as Lulzactive, Lulzactive would have performed better in regards to battery with much the same feel and performance. So I'd definitely choose this over Ondemand.

I won't be posting results for about 3 days, I'm planning on doing a BIG 3-way comparison between Smartass, DanceDance, and Wheatley. That should be posted late Wednesday, so now you have something to look forward to. :)
[HTC Rezound] Purpeltendire:
A few quick updates while I'm taking a break in homework.

-I hate Daylight Savings Time. I ended up waking up far later than I wanted to yesterday and didn't use my phone that much. So I'm probably extending the comparison post to Wednesday in order to have comparable usage.

-I'm going to take out Battery Monitor Widget, and probably stop using the OS battery and app information; I already use the same information from GSam and there's no point in having redundant information. Also, I will start using the Battery Management portion of Android Tuner Free, so that I can get estimates for 100% battery use. This will start after the DanceDance/Wheatley/SmartassV2 comparison, because I thought of it about 5 minutes ago. :silly:

-I edited the thread title to reflect the date of the last governor post I've made. Make sure I remember to update that! :p

-In case anyone was wondering, I'll be staying on Infection 2.1 and Deluxe+/Hiro Kernel until I finish the testing. Partly so that I don't randomly change and skew results, and partly because it can take battery readouts 3-5 days to settle after a new flash, and I want to keep this up as frequently as possible. However! One thing I'm willing to do is once I've finished the governors, I could take the most popular ones and test them ROM to ROM (ie. Infection vs TRON or CM 10.1 vs PAC-Man). This probably wouldn't be for a little while as I'm not done yet, but what do you all think about that?

Cheers,

Purple.
[HTC Rezound] Purpeltendire:
Scary! :cool:

Scary 1

Scary 2

Scary 3

If all you care about is battery life, then this is actually an extremely good choice -- but you'd better be prepared to make sacrifices for that battery life. Because the default sampling rate for mpdecision is 500 milliseconds, and Scary only goes up one frequency at a time, you're effectively stuck at the lower frequencies for a few seconds. Now, for many things (like just checking email, etc) this really isn't a bad thing. But if you throw in things like Nova Launcher, SwiftKey & predictions, monitoring services, and all the other things that many of us have constantly running on our phones, this leads to some serious lag. Chrome crashed while trying to load several times, actually.

Now, about the battery life. The drain while screen was off was pretty usual, most governors are on par there. But because of the way Scary ups clock rate, the usage while doing little things like checking the clock and such dramatically decreases. So at one point earlier in the day, my battery consumption was around 2.0% per hour, which is absurdly low.

So yeah. This is a great governor for battery, and if you really want to squeeze all the time in the world out of your device then it's probably not a bad choice. But you'll take a big performance hit, and I personally don't think it's worth it.
[HTC Rezound] greensky23:
Awesome, awesome write-up series!

What about interactive? Enabled by default in HIRO kernel RC1.
[HTC Rezound] Purpeltendire:
Re: [03/14/13] A Governor a Day

Thanks. :)

I can do that today! I just got up. :p

Sent from my Infected Rezound.
[HTC Rezound] Snuzzo:
Re: [03/14/13] A Governor a Day

Regarding Scary; raise minimum frequency to 384 and reduce mpdec idle to 384. Want more from Dance dance, raise up threshold to 50 and lower down threshold to 80. My baked in config is balanced which plays well with our device.
[HTC Rezound] Purpeltendire:
Awesome. :) The raise to 384 is something I didn't consider, but it would considerably diminish the initial lag. If the thresholds were also tweaked on Scary it would lead to something that would basically be a copy of conservative, but it might be worth looking into later.