Team EOS Nightly builds... Are they overclocked? - Xoom Q&A, Help & Troubleshooting

Since installing builds 29, 30, 31 I have noticed my battery life shrinking and the xoom running warmer. Am I imagining things or are these builds overclocked upon flashing?

Nope, not by default. I'm running EOS 32 and it came set up like this:
Governor: Interactive
Minimum Frequency: 216 MHz
Maximum Frequency: 1000 MHz
Maybe you can use an app like System Tuner to undervolt your Xoom? Not sure what else could be draining your battery so fast while warming your device.

It could be my imagination and maybe I am just using the device more and giving it a workout when playing with all these EOS builds.
Thanks for the clarification.

Can someone just let me know what overclocked exactly means ?
is it helps to make mobile/tablet faster ?

CPUs have the ability to run faster than they are clocked by the manufacturer. The tablet ships with a CPU clock speed of 1 GHz. This speed is specified because the CPU manufacturer has deemed it the optimum speed (in terms of stability and possibly power consumption) for that particular CPU. By modifying the kernel, you can add the ability to change this maximum (and minimum) threshold. Theoretically, yes, if you increase the clock speed, your tablet will run faster.
The clock speed is how many cycles a CPU can do per second. So, at 1 GHz, a CPU executes ~1,000,000,000 cycles per second. By setting the maximum speed to 1.5 GHz, your CPU can now execute ~1,500,000,000 cycles per second. A CPU also has an instructions per cycle rating. So the more cycles you can execute in a second, the more instructions your CPU can process in that second.
You must keep in mind that when you increase the clock speed, you may sacrifice battery life and/or stability (higher frequency needs higher voltage). Additionally, even though we all have the same CPU in our tablets, there are small variances. I may have no stability issues running at 1.7 GHz while you may suffer boot loops running at 1.7 GHz. Furthermore, running at a higher clock speed may cause more heat and electronics don't operate very well when overheating.
Finally, the governors are used to regulate the clock speed. Just because your CPU is clocked to 1 GHz, doesn't mean it's running at that speed 100% of the time. If it's sitting idle, it may be running at ~0.250 GHz (250 MHz). Then, when you wake up the tablet and open an application, the governor realizes you need more CPU power so it increases the "maximum" until either 1) You no longer need additional power 2) You've reached the maximum threshold set by the kernel.

"The clock speed is how many executions a CPU can do per second. So, at 1 GHz, a CPU can process ~1,000,000,000 instructions per second. By setting the maximum speed to 1.5 GHz, your CPU can now execute ~1,500,000,000 instructions per second"
Not sure if I am misunderstanding your lesson. Please understand this no attempt to troll or argue, but Clock speed is a reference of the frequency of the processor. They are basically saying your processor has an operating frequency of 1 Ghz. Instructions per second is measured by IPS (instructions per second). For instance, My AMD Quad Core processor operates at 3.0 Ghz but can handle 42,820 MIPS. They are not directly proportionate.

terrymc2708 said:
"The clock speed is how many executions a CPU can do per second. So, at 1 GHz, a CPU can process ~1,000,000,000 instructions per second. By setting the maximum speed to 1.5 GHz, your CPU can now execute ~1,500,000,000 instructions per second"
Not sure if I am misunderstanding your lesson. Please understand this no attempt to troll or argue, but Clock speed is a reference of the frequency of the processor. They are basically saying your processor has an operating frequency of 1 Ghz. Instructions per second is measured by IPS (instructions per second). For instance, My AMD Quad Core processor operates at 3.0 Ghz but can handle 42,820 MIPS. They are not directly proportionate.
Click to expand...
Click to collapse
You're right and wrong
IPS is a function of clock speed so they ARE directly proportionate.
(Clock speed) X (instructions per clock) = IPS
I used "instructions" to simplify the example but you're right, I should be using another word.
Thanks for pointing that out!

Thanks skinien
I'm having motorola xoom ... planning to root it to have ICS ... any idea what will be optimal overclock speed for it .... mostly for playing games on it

nash.android said:
Thanks skinien
I'm having motorola xoom ... planning to root it to have ICS ... any idea what will be optimal overclock speed for it .... mostly for playing games on it
Click to expand...
Click to collapse
From what I've seen, a lot of people stay around 1.5. Just make sure you don't click "set on boot" immediately. Use it for a while too make sure its stable at your chosen frequency.
Sent from my ADR6400L using XDA App

On ICS, mine is super stable at 1.4Ghz. My crashes, no reboots. And I'm using the Lagfree governor, so clearly I'm not locked in at 1.4 all the time. That's just the max speed based on CPU intensive activity...

Widgets not shown in Applications
I uploaded November 6th build on my Xoom Wifi. I have the following error - clock stopped & then I did not see Widgets under apps. Please let me know how to invoke widgets.
Thanks,
Pingala

Related

CPU Freq: How do you keep yours?

This is a question I've never seen asked, but it's an important one. What are you phones CPU Freqs? What Govs do they have, and what Profiles do you use?
Rom: PyroIce
Main: 192 Min, 918 Max. OnDemand.
Screen Off: 192 Min, 384 Max. PowerSave.
InCall: 192 Min, 540 Max. Interactive.
Time 11pm-7am: 192Min/Max Powersave.
Sent from my HTC myTouch_4G_Slide using Tapatalk
that's cool, i might start using profiles again. from fiddling around i've noticed the difference between the ondemand and conservative governors- with ondemand, the processor seems to go from min. to all the way to max. and back down to min, and doesn't use the middle frequencies as much, while on conservative, the processor doesn't shoot up to max. as easily and seems to meander thru the middle frequencies a lot more. it makes sense too, because i've noticed that the phone seems snappier with ondemand.
i noticed you're using some of the others... i'll have to check them out as well.
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
AgentCherryColla said:
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
Click to expand...
Click to collapse
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
yellowjacket1981 said:
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
Click to expand...
Click to collapse
If you run a Sense 3.6 Rom, boost the CPU to 1Ghz. 918Mhz Lags.
Sent from my HTC myTouch_4G_Slide using Tapatalk
yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yes.
You cannot use anything the kernel doesn't already serve as an option, though.
SetCPU doesn't create options - it allows you user-level access to the ones already existing.
Normally you have no control over your clock speed but with it you can...say... limit the maximum clock speed to only be two-thirds of the stock speed.
Since it doesn't ramp up all the way, it doesn't drain as much power.
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done. But if you don't do much with your phone, and don't need a lot of high-end CPU ability, why let it run flat out?
You can also set it to be like that only sometimes, and maximize battery savings by telling your device to chill out when it doesn't have to be awesome.
Now, if you get into custom kernels where you or a dev has opened up more options, SetCPU will again give you user level control over them.
Especially once you get into overclocking beyond manufacturer(s) recommendations, not having some end-user level control over the processor like this is irresponsible.
If you think I run a 1.7 or 1.9 or 1.5+anything on the device flat-out balls-to-the-wall all the time, I would ask you if you drive your car with the gas pedal smashed to the floor all the time. (it's a fitting analogy)
No, again, that would be irresponsible abuse of the hardware for no good reason.
If not SetCPU, then there would be something else to use, but SetCPU is a great interface that not only works well but is maintaned within the XDA community by a member here.
I will always go for the XDA community member version of any app first - it's usually a problem solved from a perspective very near the way I am perceiving the issue, supports the community, and is always easier to find help on if necessary.
What's even cooler is SetCPU is given away free by the dev to XDA members.
I did go ahead and buy it anyway to support the dev. It is a fantastic tool at my disposal, and I have come to realize just how much time and energy goes into making this kind of stuff.
Beyond all that, though, there are a ton of crap apps and software out there slapped together by people who don't care or didn't put the right level of effort into their work. When I find something that actually works and works well after sifting through a sea of garbage, if there is a paid version of the app i'll usually buy it not only as a thank you but also to encourage that particular person to keep working. They - unlike many, many others (in my opinion) earned it.
I know i'm drifting off topic a bit, sorry for that - I just really appreciate quality work and SetCPU falls in with that crowd nicely.
Even without a custom kernel providing options beyond stock, there is still a lot of value this app can hold for anyone with root level access to their device.
Blue6IX said:
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done.
Click to expand...
Click to collapse
Is this true? in my mind, I feel like it will take longer/not be as smooth, but wouldn't necessarily be worse for battery than a higher clock speed.
On a one-for-one comparison it leans more towards an even playing field, until you add that it's a dual-core processor and it very heavily skews the results towards less battery at higher clock speeds for complex operations.
Faster CPU speeds process the actions more quickly, and when you have to crunch a lot of numbers real quick like you do for most games the higher clock speed (especially on the dual core we are using) will complete the act with less power used. It is able to keep up with and/or outpace the flow of data being thrown at it.
If you are just using a notepad or browsing some forums maybe...sending a few texts? Then the higher clock speeds show a negative return on battery usage - you don't need it and it's wasteful.
But when the data has to stay buffered because the CPU is taking it's time working with it, not only is there more electricity consumed by keeping the processor alive longer but also the juice spent on keeping the data buffered.
The data computed is the same data computed at any speed (unless you lose data along the way...) but the power spent on completing that operation is not equal - not by a long shot.
On single core older processors where you are talking about a couple hundred megahertz one way or another the equation is much different, significantly diminshed returns on electricity invested, but with higher quality and multi-core processors especially they can cut through the data with significant ease when sufficiently powered.
But this is on processor intensive activities, and gaming is the first thing that comes to mind. For most other use of the device it's worth underclocking it and you will see battery gains.

[Q] Overclocked at 1600mhz - not scaling at 1.4ghz and 1.5ghz

Hello!
as I finaly rooted my TF (after a year of stock ) I have already hit few obstacles while making it perfect. Now i have a question regarding overclocking.
My device: ARHD Rom with guevors kernel 21.4
I use my TF at 1,6ghz via SetCPU. In CPUStats it says it doesnt use 1,4ghz and 1.5ghz freqs at all as the time at those freqs is zero. But when I clock it up to 1.4 or 1.5, it does use them (note: when set to 1.5ghz, 1.4ghz freq is still not used). What could be the reason for that?
Thank you for your answers
miHah
Looking at cpu histories it usually defaults to the lower stuff except when you do complex calculations, in which it uses as much as it can until it's done. That's why it doesn't use those middle freqs as much, if that makes any sense.
I agree with Thing o Doom. A lot depends on what the processor/software decides it needs or wants.
I stopped using a wide range of frequency like 216-1200 and stuck with a straight 1200MHz only on the min and max.
Depending on the CPU load will determine whether it even hits a certain frequency and also based on the type of governor.
If you have a governor that is set for performance and your range is 1400 - 1600, the governor interacts with the rest of the system and may ramp straight up to 1600 without every hitting 1500.
Hope that expands on Doom's answer.
I use interactive gov. and usualy cpu clocks scale at every cpu freq described in kernels scaling. I use 216-1400 now and cpu uses all clocks in that range (depends on the need ofc). But if i use 216-1600 then not all of the freqs are used. I meant to say if u scale it to 216-1600 there should be some point where cpu would use 1400mhz freq, but mine doesnt at all. So the scaling goes from 1200 directly to 1600 and no in between resulting the cpu to be more time at higher clocks when not actualy needed (when it could just use 1400 or 1500mhz).
Anyway, i now use scale of 216-1400mhz and seems to be working great dunno why I even bothered with 1600, but this one thing not scaling at those two freqs did scare me as I thought there is smth wrong with my tf

[POLL] Tested Dual-core ( 972 mhz) vs Single-core ( 1.836 Ghz)

Hello guys,
Since i`ve seen so many debates about single vs dual-core, today i was bored and i tested with antutu and quadrant this thing.( I know that benchmarks isn`t a real proof in day-to-day performance )
WANT THE SCRIPTS FOR UNDERVOLTING AND FORCING CPU1 ONLINE OR OFFLINE ? See 2nd post
SO , what I actually did:
-flashed a freshly new rom ( using elegancia 3.1.0 for about 2 weeks and i found to be very stable and smooth with better battery life than any other rom i`ve tested)
-flashed latest bricked kernel min 192 mhz max 972 mhz with gpu oc @300mhz, lagfree governor, I/O deadline, both cores online via init.d script, booted and tested with antutu and quadrant and then i let the phone settle for a while to see what is the power consumption in stand-by with battery monitor widget.
-after that, i flashed bricked kernel with only max speed change to 1836 mhz, cpu1 offline via inid.d script and made those tests again
Here`s what I got:
Antutu: 4827 (both cores online, clocked @ 972 Mhz)
Quadrant: 2592
BMW: -19mA
Antutu: 4593 ( cpu1 offline, clocked @ 1.836 Ghz )
Quadrant: 3393 ( cpu1 offline, clocked @ 1.836 Ghz )
BMW: -28mA
Those numbers doesn`t reflect exactly the user experience. Some apps opened faster with 2 cores, some faster with only 1 core clecked at higher speed. The only major difference i noticed was in the browser( stock ICS browser) where the more fluid experience was with both cores on.
I`m gonna test those 2 configuration further to see which one has better battery and post some screenshots.
I will add a poll to see which configuration you think is the best.
Be aware that SoC are not created equaly, so the UV script or OC will NOT work with all devices.
Unrar the archive and choose what you want
This files needs to be copied in /system/etc/inid.d and then set the right permissions ( read: all 3 needs to be checked; write: owner checked; execute: same as read) . You need a file explorer that has access up to root ( i recommand Root exploer)
Benchmarks should always be done using Performance governor for consistency
Michealtbh said:
Benchmarks should always be done using Performance governor for consistency
Click to expand...
Click to collapse
I knew that, but i wanted a more real-life experience, and in my opinion there isn`t that much difference in lagfree vs performance. I ran benchmarks 2 times and the scores where almost identical
Please be aware that because of the instruction sets hard coded at low level into the cpu it doesn not mean that 2x 900mhz cpu cores is equal to 1x 1800mhz cpu core because of the way in which the second core is utilised. Its exactly the same with pc's hence why sometimes an AMD cpu with 2 cores can give a better real world performance benchmark than an intel cpu with 4 cores. the same applies vice versa, it just depends on what instruction sets were used and how the cpu is used. Benchmarking stuff like this is not a reliable way to test
Jonny said:
Please be aware that because of the instruction sets hard coded at low level into the cpu it doesn not mean that 2x 900mhz cpu cores is equal to 1x 1800mhz cpu core because of the way in which the second core is utilised. Its exactly the same with pc's hence why sometimes an AMD cpu with 2 cores can give a better real world performance benchmark than an intel cpu with 4 cores. the same applies vice versa, it just depends on what instruction sets were used and how the cpu is used. Benchmarking stuff like this is not a reliable way to test
Click to expand...
Click to collapse
Thanks (I'd use thanks button,but i'm limited to 8 oer day) for clarifying this for me and any other users, this post should be sticky because many members on xda think that way. I am aware that 2x900 doesn't equal 1x1800, but I didn't knew the exact explanation. The only reason that I did these tests was to see which configuration gives the best battery life. Their not equal, but acording to antutu, quadrant and end user experience they are comparable
Thanks for your time in doing these tests... It might not be reliable but it was interesting to know bout it... Im curious between the two tests though, which test puts the cpu under more stress? the first test shows awesome result on the battery so being single core might stress the cpu more, im guessing
Sent from my HTC Sensation using Tapatalk
AndroidNeophyte said:
Thanks for your time in doing these tests... It might not be reliable but it was interesting to know bout it... Im curious between the two tests though, which test puts the cpu under more stress? the first test shows awesome result on the battery so being single core might stress the cpu more, im guessing
Sent from my HTC Sensation using Tapatalk
Click to expand...
Click to collapse
33% left and it's running for15 hours with 2 cores

I don't understand overclocking

I flashed Sebastion's overclock kernel and installed System Tuner. I see that I have option to set the CPU overclocked to 1.8 GHz, I didn't even know it could go this high. Then I see "CPU0" and "CPU1". Are these both cores? Because if they are, I only see "CPU0" being overclocked. Does this mean only one core is being used at such a high speed?
I've set it for 1.51GHz and "ondemand". That seems reasonable, right? Any other suggestions?
Some kernels allow you to clock to 1.9, but its not recommended as you can easily fry your chip. CPU 0 and CPU 1 are the two cores, you are correct. I'm not entirely sure if one or both cores are overclocked, but my suspicions would be only the first core, simply because the 'ondemand' governor only turns on the second core if the first one is unable to run process the load efficiently. 1.5 is pretty reasonable yes, but you can even make it lower an still get good performance, an lower clock speeds mean slightly better battery too. I'm running at 1.4 with a badass governor, which is better again for battery consumption.
Sent from my Sensational pokeball that caught Charmeleon 5.1.0!

Note 3 not going over 1497600 mhz

First I'd like to say excuse my ignorance. So my note 3 was lagging bad after the update to the newest software so I decided to root my device. Not running a custom rom or anything but the main reason I did so was to be able to set my cpu to certain frequencies. So I have done the root. And have tried multiple app from no frills to trickster mod. But each one I have. It will not let me change the frequency above 1497600 mhz. Each time I click on save no matter what frequency above that one it always reverts to 1497600. I use xposed installer and thought I found a module to fix it (dvsf disabler) but if that is what fixes it ive still had no luck. The phone doesnt run horrible but there is a little bit of lag. Does anyone know why this is happening, and how I coukd fix this?
Anyone have any idea? If this is posted in the wrong forum please let me know, I'm just looking for a way around this.
If your CPU frequency is anywhere close to 1,497,600 MHz, I would like to have a word with the laws of physics, and inform it that it is broken. Simply put, there is a limit on how high your CPU can be clocked before it becomes hot as hell and unstable. The highest clock speed I have even heard of a CPU reaching is around 7,000 MHz, which was a very highly overclocked Pentium 4. Newer high end x86_64 CPUs generally don't tend to get overclocked to much higher than 4,000-5,000 MHz, although they are much more efficient with those cycles than a P4, and have the advantage of hyperthreading. Your phone's CPU honestly shouldn't be clocked higher than 3,000 MHz, and if it's a rather weak CPU, it might not even be able to be overclocked to higher than 2,000 MHz.
Or is it perhaps the case that you meant to say your CPU is clocked at 1,497.6 MHz (decimals are important!), and it won't go higher, because as I have just mentioned, there is a limit to how high you can go?
Basically 1.4 ghz. There have been people overclocking at way above that as the cpu is supposed to be around 2.3ghz.

Categories

Resources