FORUMS

The OnePlus 2 & The Year of Smartphone Compromises

We are very close to entering the last third of 2015, and we have now seen many of … more

OnePlus 2 Teardown, Major Android Vulnerability – XDA TV

The OnePlus 2 has been officially released. That and much more news is … more

What Do You Think About Fingerprint Scanners?

More and more phones are featuring fingerprint scanners, and with many promising … more

What’s Next for Samsung and Its Flagships?

If we were to say that the Galaxy S6 was a leap of faith made by Samsung, we … more

REMOVED

13,921 posts
Thanks Meter: 23,074
 
Thread Closed Subscribe to Thread Email Thread
15th February 2013, 05:58 PM |#191  
OP Account currently disabled
Flag Phoenix, Arizona
Thanks Meter: 23,074
 
Donate to Me
More
Update:
-Added information on DynInteractive
The Following 3 Users Say Thank You to MBQ_ For This Useful Post: [ View ]
 
 
15th February 2013, 09:07 PM |#192  
OP Account currently disabled
Flag Phoenix, Arizona
Thanks Meter: 23,074
 
Donate to Me
More
Update:
-Reverted back to the normal font
The Following 3 Users Say Thank You to MBQ_ For This Useful Post: [ View ]
17th February 2013, 04:52 AM |#193  
AndreiLux's Avatar
Senior Member
Thanks Meter: 14,526
 
Donate to Me
More
Quote:

OnDemand:

Basically, this Governor will allow your phone to use CPU speeds on demand, meaning.. If you're sending a text, your phone wont require much memory, but if you're playing a graphically intense game, it will use both cores, most likely at your highest set CPU speed, and will idle back down when you finish your game.

No.

It doesn't require much memory? What? CPU governors control CPU frequency, memory has nothing to do with this. Ondemand also has nothing to do with cores as it's not a hotplug aware governor.

Ondemand stands for that it scales up on load in frequency and then detects the load and scales back to a frequency which is fullfills the "demand" of the current load dynamically.

Quote:

OndemandX:

The same idea of Ondemand, but when the screen turns off, the max screen off profile is 500MHz.

And the max screen off profile is what? It's maximum frequency the CPU is allowed to.

Quote:

Interactive:

The same idea of Ondemand, but Interactive scales your CPU to the highest frequency faster than Ondemand does.

No it doesn't.

Interactive scales by default in steps towards max frequency, Ondemand in its default implementation scales immediately to max frequency.

Quote:

Conservative:

Slower CPU scaling, less aggressively as well. For example, lag will occur if using this Governor while running multiple apps, because the idea of this kernel is to be as conservative as possible.

No it doesn't.

Conservative means that it scales conservatively, not that it is conservative. It pretty much very similiar to Interactive in that it scales up and down in frequency steps. It actually can be one of the most aggressive governors out there.
Quote:

Intellidemand:

An intelligent Ondemand. It acts like Ondemand if the GPU gets busy, but it loads the CPU frequencies up just a tad faster and more efficient than Ondemand.

And what does it do when the GPU is not busy? First of all it is broken in the regard of actually even checking GPU load, which is the one single thing which sets this apart from Ondemand, and has a minimum frequency in such cases. Secondly, it's identical to Ondemand in all other situation.

Quote:

Wheatley:

One of the favored Governors of users. It is based on Ondemand, but was built with performance in mind, and maxes out c4 time (Simply put: It keeps your phone nice and fast). When opening and running apps, it will ramp up the CPU. Reduced sampling intervals was included as well, and a unique feature of this Governor is the Sampling interval can be lower than the target residency, which prevents wakelocks without hurting battery life.

No.
Quote:

(Simply put: It keeps your phone nice and fast)

No, it means that it improves battery by increasing the time spent in the C4 low-power state.
Quote:

When opening and running apps, it will ramp up the CPU.

As any other governor.
Quote:

and a unique feature of this Governor is the Sampling interval can be lower than the target residency, which prevents wakelocks without hurting battery life.

Wakelocks have nothing to do with governors.
Quote:

Hotplug:

Based off of Ondemand. It allows a CPU to go offline with minimal usage. When you're sending messages, browsing settings, or other simple tasks, most likely one of your CPUs will be offline, which means in the long run, it will increase your battery life. When your screen goes off, it will shut off a core of your phone, which drastically improves battery life.

Actually when your screen goes off all your cores go off. What it does is that it limits itself to 1 core when doing activity when the screen is off.
Quote:

PegasusQ:

Samsungs Governor for multi-core phones. Based off of Ondemand. This kernel controls hotplugging as well, but doesn't hotplug a CPU (unless the developer changed the kernel to do so) when the screen is on.

Well does it do hotplugging or not? Yes it does, even without the developer.


I got tired by now and I even left out all the ancient governors. More tomorrow. I hope some people get the point I'm trying to make here, who allowed this to be stickied?
The Following 14 Users Say Thank You to AndreiLux For This Useful Post: [ View ]
17th February 2013, 06:45 PM |#194  
The-Captain's Avatar
Recognized Themer / Retired Forum Moderator
Thanks Meter: 3,191
 
More
Back on-topic here guys. I don't think AndreiLux intended to come off as saying everything in this thread was wrong, but just wanted to contribute in making sure it was correct. No more post in here about if it was rude or not though, this thread has been derailed enough. Thanks.

~ The-Captain
The Following 9 Users Say Thank You to The-Captain For This Useful Post: [ View ]
17th February 2013, 07:05 PM |#195  
Quote:
Originally Posted by The-Captain

Back on-topic here guys. I don't think AndreiLux intended to come off as saying everything in this thread was wrong, but just wanted to contribute in making sure it was correct. No more post in here about if it was rude or not though, this thread has been derailed enough. Thanks.

~ The-Captain

wishing that andreilux post be edited in another way.
thx in advance
The Following 2 Users Say Thank You to samersh72 For This Useful Post: [ View ]
17th February 2013, 07:33 PM |#196  
TheMysteriousOne's Avatar
Senior Member
Thanks Meter: 524
 
More
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W
Quote:
Originally Posted by The-Captain

Back on-topic here guys. I don't think AndreiLux intended to come off as saying everything in this thread was wrong, but just wanted to contribute in making sure it was correct. No more post in here about if it was rude or not though, this thread has been derailed enough. Thanks.

~ The-Captain

I was waiting for you.

Anyways, MBQ, waiting for whatever corrections/updates you deem fit.

Sent from my Galaxy Nexus using xda premium
The Following User Says Thank You to TheMysteriousOne For This Useful Post: [ View ]
17th February 2013, 08:25 PM |#197  
Senior Member
Thanks Meter: 105
 
More
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W
I notice a difference already with my on screen battery drain from following your guide. Thank you!!!!
The Following 3 Users Say Thank You to butikofer08 For This Useful Post: [ View ]
18th February 2013, 07:35 AM |#198  
AndreiLux's Avatar
Senior Member
Thanks Meter: 14,526
 
Donate to Me
More
I actually missed what happened here, maybe for the better.
Quote:
Originally Posted by The-Captain

I don't think AndreiLux intended to come off as saying everything in this thread was wrong, but just wanted to contribute in making sure it was correct.

Although certainly not everything is wrong, the vast amount of information is wrong. It's supposed to be a "simple" introduction to things but it severely veers off cliff on several things. The explanations seems to be actually copied, or may I say, "rewritten in OP's own words" (Probably why so much is wrong) from all over the place, with little actual knowledge on the topics. Some of the governor explanations really sticked out as painfully wrong and I corrected some of them.

I doubt OP can actually explain anything in this "guide", as I've said most of it is wrong and copied out of context. The zRam explanation is actually out of this world:
Quote:

Avoids disk paging, compresses your RAM. Disk paging means the way your phone saves temporary data. It helps with fragmentation of your disk and the physical space, which, over time, keeps speed stable and prevents any system slowdowns.

Disk paging doesn't even exist on a phone, unless you have a custom kernel which supports, and you yourself actually created a swap space. Fragmentation doesn't exist / doesn't matter on solid state memory.

This really shouldn't be a sticky, and people really would be better off following other guides.
Last edited by AndreiLux; 18th February 2013 at 07:43 AM.
The Following 4 Users Say Thank You to AndreiLux For This Useful Post: [ View ]
18th February 2013, 07:56 AM |#199  
OP Account currently disabled
Flag Phoenix, Arizona
Thanks Meter: 23,074
 
Donate to Me
More
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W
Quote:
Originally Posted by AndreiLux

I actually missed what happened here, maybe for the better.
Although certainly not everything is wrong, the vast amount of information is wrong. It's supposed to be a "simple" introduction to things but it severely veers off cliff on several things. The explanations seems to be actually copied, or may I say, "rewritten in OP's own words" (Probably why so much is wrong) from all over the place, with little actual knowledge on the topics. Some of the governor explanations really sticked out as painfully wrong and I corrected some of them.

I doubt OP can actually explain anything in this "guide", as I've said most of it is wrong and copied out of context. The zRam explanation is actually out of this world:
Disk paging doesn't even exist on a phone, unless you have a custom kernel which supports, and you yourself actually created a swap space. Fragmentation doesn't exist / doesn't matter on solid state memory.

This really shouldn't be a sticky, and people really would be better off following other guides.

Don't care

Thx

Sent from my Galaxy Nexus using xda premium
The Following 3 Users Say Thank You to MBQ_ For This Useful Post: [ View ]
18th February 2013, 08:12 AM |#200  
namtombout's Avatar
Senior Member
South, TX
Thanks Meter: 508
 
More
Re: [GUIDE] CPU Governors, TCP algorithms, Android Tips, & IO Schedulers: In my Own W
Haters gonna hate. MBQ thanks for everything you've done for the xda community.

Rick Ross said it best..These haters wanna hold me back.. These haters can't hold me back.
The Following User Says Thank You to namtombout For This Useful Post: [ View ]
18th February 2013, 09:31 AM |#201  
Asmodicus's Avatar
Senior Member
Flag Tennessee
Thanks Meter: 665
 
More
Quote:
Originally Posted by AndreiLux

I actually missed what happened here, maybe for the better.
Although certainly not everything is wrong, the vast amount of information is wrong. It's supposed to be a "simple" introduction to things but it severely veers off cliff on several things. The explanations seems to be actually copied, or may I say, "rewritten in OP's own words" (Probably why so much is wrong) from all over the place, with little actual knowledge on the topics. Some of the governor explanations really sticked out as painfully wrong and I corrected some of them.

I doubt OP can actually explain anything in this "guide", as I've said most of it is wrong and copied out of context. The zRam explanation is actually out of this world:
Disk paging doesn't even exist on a phone, unless you have a custom kernel which supports, and you yourself actually created a swap space. Fragmentation doesn't exist / doesn't matter on solid state memory.

This really shouldn't be a sticky, and people really would be better off following other guides.

I assume, in your own way, that you're trying to help. Thing is, your condescending tone makes no one want to listen to you. Instead of coming into this thread offering your criticisms, you could offer your assistance to edit the OP. Maybe you're not deliberately trying to be so abrasive, but that's the way you come across. To me, anyway.

MBQSniper is nothing if not helpful, patient, and kind when helping other users. None of us know everything. If we did, we wouldn't be here.
Last edited by Asmodicus; 18th February 2013 at 09:35 AM.
The Following 3 Users Say Thank You to Asmodicus For This Useful Post: [ View ]

Read More
Thread Closed Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes