yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Purpeltendire:
As requested this morning with good timing, here's Interactive. :)

Interactive 1

Interactive 2

Interactive 3

Past that it has been used on a few stock kernels, I didn't know much about it. I did a little digging and found this:

So now I knew what to expect, more or less.

Or so I thought. Actually, this governor completely threw me by surprise. In my experience, Ondemand was smoother than Interactive, by a lot. It seemed to take a moment to gear up before becoming as responsive as it should have been. This happened several times when coming quickly from screen off to unlock to opening an app such as messaging or phone. I think in one instance GApps crashed, too. Not sure if it was related or not.

Other than those hiccups, the governor ran fine, with little to no response time delay. I was generally pleased with its performance.

CPU usage according to SystemPanel seems to me a bit on the high side compared to other governors. Battery life was only marginally worse than Ondemand, in fact with Ondemand using 4.2% per hour and Interactive using 4.3%, even over a full day the difference is negligible.

This is another great day-to-day governor, doing nothing stellar but doing most things well. In my experience the lack in smoothness left me a little wanting, however; that coupled with the difference in battery, however little it may be, makes me lean towards Ondemand. I think that if I took a few days more to use Interactive, that I would probably end up choosing that though.

Hope you enjoyed this. :) Suggestions for Saturday and/or Monday? (Sundays are usually weird for me, different enough that I don't do a writeup)
[HTC Rezound] Snuzzo:
Please give me your write-up on Lazy. It's been iffy for me, one day it's stellar the next has been horrendous. See if you can tame the beast.
[HTC Rezound] Purpeltendire:
Re: [03/15/13] A Governor a Day

Sounds good, setting it now. :)

Sent from my Infected Rezound.
[HTC Rezound] Purpeltendire:
I might have tamed it. :victory:

Lazy 1

Lazy 2

Lazy 3

First off, sorry this is so late. Long day.

That's what I found on it. But when I looked at Kernel Tuner, screenoff_maxfreq was set to 0, so that was a bit weird.

At first I had some pretty bad battery drain -- caught up on some news, then took a 15 minute shower. I came back and the phone had sucked six percent. But after that it seemed to level out, maybe dropping 1-2 percent between times when I checked my phone every 25-30 minutes. That goes with the overrall usage of 4.4% per hour from BBS.

One thing I did notice is that if there was an application running while the screen was off -- and I mean anything, from MyBackup Root to a download in Chrome -- the phone would freak out. Three times I thought I would have to pull the battery because the screen wouldn't come on, but each time it eventually came on after a few button presses.

Other than that, there was a bit of unusual lag in XDA and Steam, and a couple GApps crashes. But I can't say there was anything truly horrendus... what were you seeing Snuzzo? And I'll run this again tomorrow, if it starts freaking out I'll amend this post. If you're running tweaked mpdecision settings or something different from stock, let me know what the changes are and I'll copy them. Here are my voltage tables and mpdecision/governor settings for reference.
[HTC Rezound] Snuzzo:
Same as what I've been experiencing on it. Again, just wanted to see your thoughts with it also and make sure it wasn't just me.
[HTC Rezound] dplane:
Thanks for this super helpful thread purple! Would you mind trying Savagedzen, Badass and Brazilian wax? I probably most interested in the 2nd.
[HTC Rezound] Purpeltendire:
Alright, no problem. :)

I can do Badass tomorrow and SavagedZen Tuesday for sure, but Funky Kernel, Ermagerd, and Hiro all do not have BrazilianWax. If you could point me to a kernel that did, I'd love to try it out.
[HTC Rezound] dplane:
My bad on the Brazilian..thought I had seen it in hiro but you are correct. Mustve thought of Asswax (seriously did a pimp come up with these names) Perhaps Skywalker then? Think that's supposed to be a tweaked SavagedZen if I'm not mistaken.
[HTC Rezound] Purpeltendire:
Sure, I can do Skywalker on Wednesday. :) Gives me an excuse to update to Hiro RC1, too. :p

Update: Edited post 3 to display link to individual governor writeups, as the thread is a bit of a mess and tough to search through. That should make it easier if you want to check something quickly, or are just browsing and want to know my thoughts on a specific governor.
[HTC Rezound] dplane:
You're the man! Thx!! :D
[HTC Rezound] Purpeltendire:
My pleasure. :)

Okay, Badass!

That's what I found on the governor. Now, that was more or less completely wrong in my experience, so lets just go to the writeup, shall we? :cool:

Badass 1

Badass 2

Badass 3

I had an interesting experience with this governor, and I can't say it was unpleasant.

I didn't really check stats during the day, so I was largely basing my early opinions on how it felt. And my early opinions were that it sucked, I'm not going to lie. I was seeing screen-off battery drain that seemed excessive, and I couldn't figure out why because there were no wakelocks that I could find. Things settled down after the early morning though, and I began to mentally revise my opinion.

Taking a look at the detailed screen info, I can see I was right about having more screen off drain than usual -- the ratio was 38% drain while on, 31% while off. Compare that to Lazy, which had 44% and 22% respectively, and it paints an interesting picture. While screen off drain was significantly higher, it also appears that screen off drain was lower by a fair bit. I think that the differences in screen on time are offset by the differences in brightness levels, so those percentages are probably pretty accurate.

The governor actually seemed geared towards the light-duty processes that make up my daily usage pattern -- mainly email, GTalk or SMS, and some browsing on the web and XDA. My app usage didn't seem to affect the phone nearly as much as on other governors.

Looking at CPU Spy, it spent a lot of time (a value equivalent to almost all the screen-on time, actually) at 192 Mhz, and only about a half an hour at the maximum clock of 1566 Mhz. Other than that, it spent a little over 20 minutes at all the other governors combined, which given the summary I found was not the result I was expecting. Given that, I was pleasantly surprised to find my overall battery consumption at 4.4%, which seems to be the average. I'll bet that this governor performs better with more screen on time, to a point, but it's probably not suited to a CPU1-only application where it would sit idle for a long time.

SavagedZen tomorrow!
[HTC Rezound] Purpeltendire:
Here's SavageZen.

SavageZen 1

SavageZen 2

SavageZen 3

I think this governor has a lot of potential. The CPU upscaling was great; the phone spent barely any time above 810 MHz, and it mostly sat at Deep Sleep, 384 MHz, and 810 MHz. That makes for a very battery friendly governor. However, there was a ridiculous amount of screen off drainage -- far too much in my opinion. Some of this might have been Chrome being stupid, but even after force closing the application the drain continued.

Performance was decent. Nothing to write home about (although I guess that's exactly what I'm doing) but it wasn't horrible. A little lag, and it didn't like it when you pressed the power button really quickly after the screen went off.

Even with the bad drainage, the phone used only about 4.2% per hour, which is pretty good. If someone were to set screenoff_maxfreq to something like 192 to limit screen-off drain, this could help a lot. Best I can recommend if you want to use this is try that, and maybe you'll get less discharge than I did.

What am I doing tomorrow... oh. Skywalker.

Edit: Results are invalid, the governor is not working properly on our devices.
[HTC Rezound] shrike1978:
I never put badass in Ermahgerd because I never got it to work right. I had it in test kernels several times and I tweaked it and massaged the code in every way I knew how, but I never could get it to work well. Even looking at the stats on millisecond scales, I never could get the slow-peaking feature to work, so I eventually just trashed it.
[HTC Rezound] Purpeltendire:
Re: [03/19/13] A Governor a Day

I don't blame you. The slow peaking wasn't really evident from what I saw; if it were working properly, I think there would have been a lot more time spent on other frequencies and there definitely should have been more time sitting at 918 MHz and 1188 MHz.

Sent from my Infected Rezound.
[HTC Rezound] Purpeltendire:
And without further ado, here's Skywalker.

Obligatory Star Wars quote, which is also oddly relevant:

Skywalker 1

Skywalker 2

Skywalker 3

Well, this was interesting. I was expecting something like SavageZen, and that's not at all what this ended up being like. If anything, it was closer to Performance than any other governor I've heard of. It spent all the time it wasn't in deep sleep at 1566 MHz, which was the max clock. Because of this, battery performance took a big hit. I was using 5.3% per hour according to BBS, which is easily the least battery friendly of any governor I've tested so far.

The upside of running at the max clock all the time was that there was no lag whatsoever. But that was probably the only upside to this governor. GApps crashed so many times I don't even want to think about it. I pretty much gave up trying to use GTalk after having it crash over and over again, either right when I tried to start it, or mid-sentence. One time it crashed when I was three words away from finishing a long sentence.... Oh, was I pissed. :p

Bad battery life and no frequency scaling to speak of, coupled with the new Crash-O-Matic 3000 feature... yeah this was not a fun day. I did get good screen on time though, about 2 hours 15 minutes. Given that I'm writing this almost two hours earlier than usual though... I don't think it's worth it. At all.

Sorry Luke. You really aren't a Jedi yet. :cool:

Edit: Results are invalid, the governor is not working properly on our devices.
[HTC Rezound] Purpeltendire:
Well, this explains a lot.

So. That's why iHWO says on his first post that the following governors don't like being set on the second core;

PegasusQ

Nightmare

AbyssPlug

Adaptive

Asswax

Skywalker

SavagedZen

So I won't be doing testing on those governors. Just so everyone knows.

This leaves me with only Conservative and Performance left to do before I'm done with all the working governors Hiro RC1 has to offer.
[HTC Rezound] snowride20:
Re: [03/20/13] A Governor a Day

This is a great read and something I have always wanted to do but never found time. Do you have a favorite governor so far?
[HTC Rezound] Purpeltendire:
Thanks. :)

I'd have to say DanceDance; it was stable and had a great balance between performance and battery life. I was liking Conservative today, but then it decided to do a few boot loops earlier. :(

I'll be posting a writeup for Conservative in a few minutes, but it won't have data to go along with it.
[HTC Rezound] Purpeltendire:
As I said in an earlier post, Conservative was performing very well, but then I had a few boot loops earlier which cleared all of my statistics. :( So here's the writeup.

I was actually pretty impressed with this governor. I was expecting it to be a lot like Scary, which sacrificed performance for the best battery life possible. But what I found was that it scaled at a reasonable pace, and had a bit of lag but nothing too extreme. I mainly experienced some slowness immediately after unlocking my device and swiping across my homescreens; the CPU had to work for a moment to catch up.

I was keeping an eye on the data throughout the day, so I'll try and do my best to remember. Battery usage should have been around 3.8%, which was very good. With the screen off, the usage was maybe 2%. I probably would have had around 1 hour 45 minutes of screen time. The CPU frequencies up to my cap of 1566 were all used a fair bit, but I believe the CPU had much longer times spent at 1566 and 384 if it wasn't deep sleeping.

Unfortunately, it was a bit unstable and I had bootloops. But if it weren't for that, this governor would have gotten a very good review from me. As it is, it's a good governor for battery and could easily last 26 hours on a single charge, if not more... but the stability is a big issue. My phone hasn't been too sensitive, and I think this governor would be much worse for someone who had a device that was picky.

Performance tomorrow.
[HTC Rezound] ssoares01:
Just wanted to say thanks!!! Awesome writeups!
[HTC Rezound] dplane:
Thank you so much for writing about the 2 requests I made. Can't say I had some of the issues you seemed to have with SavagedZen or Skywalker but I will agree they seemed erratic and I didn't quite see the benefit of either. I am currently back on Intellidemand for (in my experience) unmatched sleep performance after I continuously notice LulzActive does not seem to truly go into deep sleep on my phone. Intelli flatlines (good), Lulz, while still getting good battery life and performance overall..seems to draw considerably more in sleep (if it even truly sleeps at all that is). Sounds like I perhaps need to try DanceDance again as a compromise between the 2.
[HTC Rezound] Purpeltendire:
If sleep performance is one of the things you're looking for, may I recommend SmartassV2? From what I remember the screen-off drain wasn't bad at all, due to the fact that it slept so quickly after turning off the screen. After 16 hours, it had stayed at Deep Sleep for nearly 13, and only spent about 5 minutes at 192 MHz.

I actually should redo Intellidemand, because I'm looking through my screenshots and it's in the old format, plus I have my doubts about the accuracy. :p I agree with you on Lulzactive though, the sleep profile was very odd and the drain seemed to be excessive.

Thank you. :) I'm glad you enjoy them.
[HTC Rezound] gleggie:
Re: [03/21/13] A Governor a Day

Great reviews man! I always thought Wheatley was battery king, but lately I've liked the balance between performance and battery life of lulzactive. Gonna try dance dance, smartassv2 and intellidemand out :)
[HTC Rezound] Purpeltendire:
Thanks! :) Yeah, when I first started looking into the Rezound I thought that the Wheatley/Noop combo was unbeatable. But I'm glad that these tests showed otherwise, because variety keeps us from getting bored. :p

Here's Performance! I must say, I was surprised.

Performance 1

Performance 2

Performance 3

So other than a random 26 seconds, the CPU spent all time active at the max clock of 1566 MHz. As can be expected, there was very rarely any lag. I think the only thing I did to slow the phone down was upload to Dropbox while trying to type in Chrome, and that slowed the phone down only until the second core activated. Then it was smooth sailing.

Battery performance was interesting. For a lot of the day, it was hovering around 4.8% per hour, which is about what I expected. But after I had eaten supper I checked again and it had gone down to 4.3%, and stayed there until I took the screenshots. I can only imagine it was because I wasn't using the phone all that much, being at my computer.

The one thing I did have an issue with was the screen-off drain. As you can see in the Screen Details shot (Performance 3), the phone drained

more

while the screen was off than when it was on. This shocked me. I think the governor was just keeping the CPU active for a period of time after the display shut off, leading to a lot of CPU cycles stacking up and draining the battery. The extra hour and a half spent at full speed while the screen wasn't on would confirm that.

Final verdict: This is actually a pretty good governor. It's only flaw is that it doesn't go back to Deep Sleep as quickly as it could, especially when there isn't anything happening. This led to excessive battery drain. However, keeping the CPU at its max clock actually saved some battery, because no time or effort was spent on cycling up and down through the speeds. That's why I think it performed so well.

Hope you all enjoyed these. :) If you want me to redo any of the governors, don't hesitate to ask. I'm already redoing Intellidemand either Saturday or Monday.
[HTC Rezound] platinumrims:
Re: [03/22/13] A Governor a Day

I prefer govs like conservative, dance dance, lagfree, and scary. Something that scales in smaller increments usually gives me the smoothest scrolling, with lagfree being the best, but the worst on my battery. If I could find something like conservative that ramped up as fast as lagfree but didn't stick around the max clocks constantly I think it would be perfect. Conservative takes longer to ramp up, lagfree takes too long to ramp down to min clock. What ever will I do :'(
[HTC Rezound] Purpeltendire:
Re: [03/22/13] A Governor a Day

Off the top of my head I don't know, but I think that you can tweak the governor settings with Conservative. If you were to change the up threshold to a smaller value, it would ramp up more quickly. Powersave bias might be a setting worth looking into as well, it will make the governor favour lower frequencies.

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

Yea I lowered the threshold. But idk if it's even doing anything lol. Meh
[HTC Rezound] Snuzzo:
Re: [03/22/13] A Governor a Day

Lower down threshold on dance dance. Make it like 25.

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] platinumrims:
Re: [03/22/13] A Governor a Day

Dance dance was giving me reboots. That's why I got off of it. It would reboot my phone on unlock like once a day
[HTC Rezound] Snuzzo:
Re: [03/22/13] A Governor a Day

I haz a sad. :( What can I do to fix it?!?

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] platinumrims:
Re: [03/22/13] A Governor a Day

Ohz noze, not haz sad. :( idk. I liked dancedance but teh rebewts. Not sure why it was doing it.
[HTC Rezound] sanders539:
Re: [03/22/13] A Governor a Day

Can anyone explain the governor settings in kernal tuner? ie: sample rate, ignore nice load, etc.. Are the numbers in milliseconds?
[HTC Rezound] Purpeltendire:
Re: [03/22/13] A Governor a Day

Microseconds is the unit for sample rate. Load/threshold are in percentages I believe. So the smaller the number, the sooner whatever that function will happen is the general rule.

Up threshold determines where and when the CPU will scale up.

Powersave bias is defaulted to zero, the higher the number the more the governor will favour lower frequencies.

Down differential kind of acts as the down threshold. It's more complicated than that, but my hands are cold so I'm not typing it all. :p

Sampling down factor affects how long the governor stays at higher frequencies when it's actually doing something. Default is 1, higher values mean the CPU will stay at higher frequencies longer.

http://xdaforums.com/showthread.php?t=1369817 This is a good writeup of the governors and tweaks, tweaks are in post two.

Sent from my Infected Rezound.
[HTC Rezound] Purpeltendire:
Intellidemand redo!

First off, pay less attention to the BetterBatteryStats stuff. I had a weird usage pattern today... used it normally until about 9 PST, then had a mild crisis to deal with over GTalk until like now. So non-stop typing for a solid hour and a half kind of ruined the battery usage percentage... it was way lower earlier.

I'm also glad to be redoing this now that Intellidemand has been getting so much attention in Infection 2.3 and Hiro as a very good governor.

Intellidemand Redo 1

Intellidemand Redo 2

Intellidemand Redo 3

Great governor. I think this can give Wheatley a run for its money. From memory, my usage up until my typing storm was around 2 hours screen on time, and 3.9% battery usage. That's truly fantastic. I ended with a pretty high hourly percentage, BUT! I also ended with nearly 3 hours of screen-on time. For many people that's not only high, it can't be done. So all the more amazing because of it.

Performance wise, this is a very close runner to OnDemand. Little lag unless you go out of your way to look for it, and good scaling too.

Final conclusion is that this is a capable all-rounder, and it supports tweaking so you can go even further to customize it to your needs. I highly recommend you do so. :)
[HTC Rezound] Purpeltendire:
Update: Infection 2.3 looks solid, so I think I'll take the rest of the week to update to the Dev Edition and let it settle.

But after that... keep an eye out for a thread comparing iHWO's Hiro Kernel RC1 and Snuzzo's Funky Kernel 2.9. :fingers-crossed: I'm really curious to see how this one will play out, because while there are clear differences in each kernel from a technical perspective, I really don't know how those differences come into play for the everyday user.

I'm planning on using 1566 MHz, Wheatley/Noop, and -50mV undervolting (192 @ 750 mV). So I'll be doing a writeup on percieved performance and battery life. :good:
[HTC Rezound] Snuzzo:
Everything running good?

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] Purpeltendire:
Yessir! Sent you a PM earlier, 'Black Screen of Death'; is literally nonexistant from what I've seen and tried. I figured I'd try a few other governors while I test the OC branch, Wheatley and Intellidemand both perform well at 1566/384. Is there anything specific you want to have tested while I'm running it?
[HTC Rezound] Snuzzo:
Nope. Nothing specific. I just hope you enjoy it. :)

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] Purpeltendire:
Guess what? Snuzzo's Funky 2.9 has BrazilianWax. Looks like you're in luck, even if it's a bit late haha. I'll do it tomorrow for you; Infection 2.3 would appear to have settled a lot over the past two days. :) There will be one little difference, and that is that 2.9 isn't stable with both core minimums at 192 MHz. So they'll be at 384 MHz, the next step up.

EDIT: Only stable on single core, so I'll run Core0 Brazilian for the most effect, and Core1 Intellidemand as a good middle-ground governor.

EDIT again: Not even stable on a single core. :( Sorry. With Core0 or Core1 set to Brazilian, Kernel Tuner can't enable both cores. It sits at the "Enabling all cores, please wait" dialogue until you force-close the application.
[HTC Rezound] feralicious:
Here's a nice companion thread for this one, it gives a description of a bunch of governors.:

Governors explained
[HTC Rezound] Purpeltendire:
Good find.

I went and checked my bookmarks, looking for the thread I was reading that had information on the governors I knew little or nothing about. And that thread just so happens to be the one you found. :p
[HTC Rezound] gleggie:
Hey just a heads up snuzzo just released 3.1 and its sweet.. I think He just fixed some bugs from 3.0
[HTC Rezound] Purpeltendire:
Alright, cool. It'd be better to do the most recent versions of each, so I'll redo Funky for 3.1 after I'm done getting data for Hiro, which should be by tomorrow or Friday depending on my final usage today on Hiro.

One thing I noticed is that Snuzzo mentioned that for the most part, the updates he'll be making will either be bug fixes or updates via upstream. So unless there's a huge change to HTC Source, the review bit for Funky should remain pretty relevant. :)
[AT&T Samsung Galaxy S II SGH-I777] wildchild048:
I'm new to Samsung so can someone help me root and install cwm.The phone is on 2.3.6 stock.

I tyred searching and came up with root instructions but not for 2.3.6.
[AT&T Samsung Galaxy S II SGH-I777] Pirateghost:
you could start by doing your homework.....we have stickies for a reason