Related
Is this possible on Androids (mostly, this phone?) Before this I had a windows phone and I had a software where I could set a minimum and maximum cpu clock rate.. and then it will overclock dynamically as needed! If you are running a game and it needs more power, it will overclock it while the game is running.. dynamically without you having to change the clock-rate manually.
This will solve battery life problems when overclocking to 1.8ghz. There is no need for it to be draining the battery at 1.8ghz if you are only texting and probably even a 200mhz cpu can do that lol
Hope what I said makes sense.
it's easily done by installing Setcpu,provided that your phone has been rooted and kernel modded to allow overclocking.
Sent from my IDEOS X5
Actually it is already done in stock ROM without root, setCPU provides a way to change the default way of handling the CPU frequencies and governors.
The stock ROM comes right out of the factory can do "cpu stepping" itself, just like the intel "Speedstep" thing. But the factory powersaving profile (or if you wish to call the scaling) might not match our taste. Then there it comes the apps called Setcpu which enhances the cpu stepping behavior according to our preference. The enhancement considers the frequency of sampling cpu load, thresholds modifications, and other considerations.
In Setcpu, we can accord one of the following scaling setting that suits our taste. From my experience, each scaling setting behaves as follows:
ondemand - runs at Min or at Max (eg. 200 MHz or 1200 MHz)
interactive - adjusts frequencies according to the real load
conservative - behaves like "interactive" but incline to power saving
performance - always runs at Max
powersave - always runs at Min
userspace - disables Setcpu scaling and uses stock scaling
smartass - behaves like "interactive" but always runs at Min when LCD screen is off
And again, the phone must be rooted and kernel modded for Setcpu to work properly.
I've been using setcpu with conservative. I like conservative because it gives you a lot of control over the throttling of the cpu. It seems to work pretty good.
Are you getting any benefit from overclocking to 1.8GHz? I also overclocked to 1.8GHz, but I didn't see any noticeable improvement past 1.0-1.2GHz.
I like to use interactive Cox I enjoy the fast sampling rate and hence the high responsiveness.
Sent from my IDEOS X5
Personally I have not tried overclocking yet.. still need to update the kernel, but I'm afraid it might get unstable.
Didn't know that CPU could do it dynamically using different profiles.
Thanks all for the help
Tcm9669 said:
Is this possible on Androids (mostly, this phone?) Before this I had a windows phone and I had a software where I could set a minimum and maximum cpu clock rate.. and then it will overclock dynamically as needed! If you are running a game and it needs more power, it will overclock it while the game is running.. dynamically without you having to change the clock-rate manually.
This will solve battery life problems when overclocking to 1.8ghz. There is no need for it to be draining the battery at 1.8ghz if you are only texting and probably even a 200mhz cpu can do that lol
Hope what I said makes sense.
Click to expand...
Click to collapse
I have setcpu but the x5 is not listed....??
I own my X10 from January but didn't use it as my main phone - instead I played a lot with tons of apps.
BTW se's 2.1 ROM is VERY stable! Even when I have about 200-300 apps installed (internal memory was full) and about 20-30 was launched after boot - I had no FCs or any other issues (except slow boot up (about 2-3 minutes) and slow start of new apps). It's very stable comparing to HTC for example.
About CPU frequency - I used SystemPanel to monitor a lot of things, including CPU usage. With 2.1 ROM CPU frequency was 250-500 MHz at idle with CPU load 7-30%.
Now with 2.3 ROM CPU frequency don't fall lower than 720 and mostly is about 900 MHz at idle! With CPU load 1.9-9%.
Seems that it should consume battery A LOT!
Am I alone with that issue?
No, everyone has it. (On SE 2.3.3 ROM) But you've got it worse then me ^^...
might be why some folks are having battery drain issues
Karlson2k said:
About CPU frequency - I used SystemPanel to monitor a lot of things, including CPU usage. With 2.1 ROM CPU frequency was 250-500 MHz at idle with CPU load 7-30%.
Now with 2.3 ROM CPU frequency don't fall lower than 720 and mostly is about 900 MHz at idle! With CPU load 1.9-9%.
Seems that it should consume battery A LOT!
Am I alone with that issue?
Click to expand...
Click to collapse
SystemPanel does not give accurate CPU stats. Numbers like 720 and 900 are not possible on stock kernel.
CPU frequencies can only be 245-384-576-768-998, nothing in between.
Use CPUSpy or some other CPU monitor to get a more accurate idea of how your CPU is behaving.
Xperia X10i via Tapatalk
Yes i got this issue too,phone is always 998 in use,even if it's not heavy use ,so battery drain is horrible :s
I haven't been able to find any info on undervolting the Xoom, so have started this thread in the hope that some may find it beneficial.
What is undervolting?
It basically involves reducing the amount of electrical voltage running through the CPU. It does not affect the speed of the CPU at all, just the amount of power that it uses. The stock configuration of CPUs usually has a fairly high voltage, to cater for the fact that CPUs are not exactly identical.
Why undervolt?
Reduce power consumption, and therefore increase battery life.
Why not undervolt?
Can affect stability, and there is a small risk of damage to your device.
Disclaimer: Undervolting, like overclocking, does have the potential to damage your device. It's very rare, but not unheard of. I've never had a problem, but you may. Good luck, and don't blame me.
My config:
Model: MZ601 Xoom
Kernel: Tiamat Xoom v2.1.0
Undervolting software: SetCPU 2.2.4
My voltages before UV:
MHz mV
216 770
312 770
456 825
608 900
760 975
816 1000
912 1050
1000 1100
1200 1150
1408 1250
1504 1325
1600 1400
1704 1400
So after doing a bit of testing, I've found that I can lower my voltages noticeably throughout the range, reducing the amount of power my Xoom uses, and prolonging my battery.
My UV voltages:
MHz mV
216 770
312 770
456 775
608 825
760 875
816 925
912 975
1000 1000
1200 1075
1408 1125
1504 1175
1600 1250
1704 1325
Notes:
It is not possible to UV any less than 770 mV (with the kernel I'm using anyway).
Given that the mV for the 456 CPU frequency is so similar to 216, I set my minimum clock frequency to 456, which makes the device more responsive.
So, you may want to try these voltages, and see how they work for you.
To test: (Instructions for SetCPU)
Set your min & max speeds to the same frequency, for example 456.
Set the voltage of the 456 frequency to an amount lower that the current amount, for example 775. (It's generally best to adjust your voltage down only 25mv at a time.)
Perform a "Stress Test", for at least about 5 seconds.
If the device locks up or reboots, the mV is too low - try a higher mV.
Once you've found the optimal voltage for that frequency, move onto the next one, for example 608, then 760, etc.
If your device locks up or freezes during testing, you can force a reboot by holding down the Volume Up button, and the Power button.
The voltages I've used above may work for you, or you may have to increase them a little on your device. You may also get better voltages than me - if so, please post your results.
Battery test results
Performed some battery performance testing by doing the following steps:
1. Set the screen to not turn off, and brightness to 10% (screen needs to be on to keep the stress test running, and brightness low to minimise the battery drain of the screen, as that's not what we're testing).
2. Disabled all network connections (WiFi, Bluetooth, Data, GPS) to minimise battery drain by other factors.
3. Closed all other apps, and did not use the Xoom at all during the tests.
4. Charged Xoom to 100%.
5. Set CPU speed to 1504mhz using SetCPU (both min & max frequencies the same for accurate testing).
6. Unplugged the Xoom.
7. Ran "Stress Test" for 2 hours (give or take 20 seconds).
I performed the above steps for both stock voltage, and undervolted voltage. Results as follows:
1. For stock voltage (1325mV on Tiamit Tachi kernel), battery life went down to 62%.
2. For undervolted voltage (1175mV, which is nice & stable for me), battery life went down to 72%.
Findings:
I was expecting battery savings, but not quite this much.
Standard voltage (at 1504mhz) at this CPU load, drains at about 19% per hour.
UV voltage at this CPU load, drains at about 14% per hour.
Standard voltage at this CPU load, the Xoom would drain battery entirely after about 5.26 hours.
UV voltage at this CPU load, the Xoom would drain battery entirely after about 7.14 hours.
In addition to the battery savings, the Xoom was only slightly warm after the UV tests, but very warm after the standard voltage tests. (Standard voltage test was performed first.)
Note: For general usage (email, browsing, basic apps & widgets), the CPU is not as heavily used. But in situations where the CPU is heavily used (such as intensive games), these results show there is significant potential for battery savings.
super nice tips. Tq very much
126-608 -175
Others -150
This is my settings... no prob at all.
Would I use setcpu app or just use the Moray(in settings) or does it matter
rayhodge02 said:
Would I use setcpu app or just use the Moray(in settings) or does it matter
Click to expand...
Click to collapse
Not sure what the "Moray" is, but any tool capable of undervolting should be ok. I like and use SetCPU, but I've tried other tools on other devices in the past, and they did similar things.
nobody wants to share their result after trying?
Very good job, I try
Sent from my Xoom using xda premium
pls share ur best result
I try your results and they're unstable in function off the useful task, exemple impossible to play simple games.
That's all right just for basic tasks like navigation, music ...
Sent from my Xoom using xda premium
Hmm, your stress testing seems inaccurate.
I used your values and did a stress test at each frequency for around 10 seconds. No problem. But my xoom restarted just 5 mins later while I was surfing the net.
So I increased each frequency by 25-50 and it stayed stable since then.
for me i just underclock my xoom to 912mhz. it is almost as fast as 1ghz. and i save battery alot.
Gregus59 said:
I try your results and they're unstable in function off the useful task, exemple impossible to play simple games.
That's all right just for basic tasks like navigation, music ...
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Try bumping up the voltages a little bit at a time, until you find a stable setting. The settings I listed are what are stable for my Xoom (even intensive 3D games), but CPUs vary. What I get, others may not, and others may get better than me.
musashiken said:
Hmm, your stress testing seems inaccurate.
I used your values and did a stress test at each frequency for around 10 seconds. No problem. But my xoom restarted just 5 mins later while I was surfing the net.
So I increased each frequency by 25-50 and it stayed stable since then.
Click to expand...
Click to collapse
They're not 100%. The longer you stress test, the more likely the CPU is stable, but 10 seconds gives a general idea. If unstable, just do as you did, and increase by 25mv or so.
omnia1994 said:
126-608 -175
Others -150
This is my settings... no prob at all.
Click to expand...
Click to collapse
Can you confirm your mV values? -175 sounds like a big saving. Surely your mV is not less than the minimum 770?
What kernel are you using?
do some proper tests to establish how much extra time you will get from a fully charged batt.
i would think its perhaps a tiny bit at most...
the screen would take a huge amount of the batt, the processor would use only a small percentage, so surely cutting a small fraction off a couple of steppings is fairly pointless?
baron von bubba said:
do some proper tests to establish how much extra time you will get from a fully charged batt.
i would think its perhaps a tiny bit at most...
the screen would take a huge amount of the batt, the processor would use only a small percentage, so surely cutting a small fraction off a couple of steppings is fairly pointless?
Click to expand...
Click to collapse
1. It depends what you're using the device for. Games, for example, can use a lot of CPU, so undervolting in this instance, will definitely use noticeably less battery.
2. If CPU voltage throughput didn't make any difference, we'd all just run our devices at 1700mhz all the time.
3. With undervolting, I can run my Xoom at the same voltage at 456mhz, as it run at 216mhz. This means I set my minimum frequency to 456 instead, and for the same minimum battery consumption, my device is noticeably smoother.
If you want to know how much extra time you will get from a fully charged battery, YOU do some tests.
lindsaytheflint said:
Can you confirm your mV values? -175 sounds like a big saving. Surely your mV is not less than the minimum 770?
What kernel are you using?
Click to expand...
Click to collapse
Yes i m sure. Has been using these settings till now.. no prob at all. Using tiamat stock gpu kernal with moray rom
i agree that during low intensity operation the power savings are probably nearly negligible, but during CPU-intense usage it could save a bit.
I myself am not willing to leave my Xoom on full bore for a series of tests lasting 7-10 hours each just to quantify how much power undervolting can save under super extraordinary circumstances.
But even if the energy savings is an arguable benefit, the reduction in CPU temperature is not. That alone makes this worth doing, IMO.
Agree.. after setting it my xoom now has lower temp when playing it
Caveats: Every CPU and GPU does not come from the same bin, fabricated on the same date and possibly not manufactured in the same facility. They may each display different physical properties and a wider range of stability than others. What works for me may not work for you.
That being said, I've been stress testing my device with different settings for the past couple weeks trying to find a sweet spot of stability, speed, battery life and heat output.
I'm going to share two setups: my current one that I've stress tested for less than 24hrs but has proved stable through all conditions encountered thus far and my tried and true setup I've used for over a week with no trouble.
Tried and true setup:
Governor - ondemand
Range - 100MHz through 1.6GHz
100MHz - 800mV
200MHz - 825mV
300MHz - 850mV
400MHz - 900mV
500MHz - 900mV
600MHz - 900mV
700MHz - 925mV
800MHz - 950mV
900MHz - 1000mV
1000MHz - 1025mV
1100MHz - 1100mV
1200MHz - 1125mV
1300MHz - 1150mV
1400MHz - 1175mV
1500MHz - 1250mV
1600MHz - 1350mV
Experimental but stable battery saver:
Governor - ondemand
Range - 100MHz through 1.6GHz
100MHz - 775mV
200MHz - 775mV
300MHz - 800mV
400MHz - 800mV
500MHz - 825mV
600MHz - 850mV
700MHz - 875mV
800MHz - 900mV
900MHz - 950mV
1000MHz - 1000mV
1100MHz - 1100mV
1200MHz - 1125mV
1300MHz - 1150mV
1400MHz - 1175mV
1500MHz - 1225mV
1600MHz - 1350mV
GPU setup:
Low power state - 100MHz @ 800mV
High performance state - 400MHz @ 1050mV
Notes:
Custom governors were not stable for me AT ALL! I've found ondemand to be the best one for me and my needs, personally.
100MHz @ 750mV was so, SO close to being stable for me but my phone would routinely reboot in the screen off state. I'm assuming the stress of apps updating in the background, notifications etc was just too much.
As much as I love WidgetLocker (and I really do!), I found it to consume valuable resources, have more pronounced wake up lag and generally contribute to instability.
I use Chainfire3D to run my games etc. at x4 MSAA. As previously stated by Chainfire, the Mali can run at x4 with almost no extra overhead. I imagine that if one doesn't use x4 MSAA, one *might* be able to get away with 400MHz @ the stock 1000mV setting. That being said, I consider an extra 50mV to run at 133MHz faster to be a bargain.
Many games can be run with x16 MSAA with minimal overhead but I've found that for some resource intensive ones, especially multiplayer, they'll slow down unless the GPU is fed at 1200mV but this in turn causes a lot of heat generated so I would advise to avoid turning on x16 MSAA for those that you do find slowing down.
I use and recommend Voltage Control (donate version for extra features!) for setting up clock range and voltage for both the CPU and GPU. It also allows one to set boot settings (at setup or init.d script) and create multiple profiles. I do not recommend init.d script for untested settings as it could cause you issues.
Edit: Not everyone's kernels may support GPU OC/UV or the CPU ranges listed here. I am not responsible if you bork your device.
Here's someone else's method for testing settings:
Here's how I test UV settings.
Turn on everything. Wifi, bluetooth, max brightness, the whole works. This ensures the system is at maximum strain.
Start at maximum CPU clock
Lock the CPU clock (set the minimum and maximum allowed clock to the clock you are currently undervolting)
Lower the voltage by one step
Start a benchmark for a few minutes to see if undervolted clock is stable
If it passes, lower it again go back to step 4
When it freezes up your phone, reboot it and increase the voltage at that clock by two steps and consider it safe
Move to next frequency and go back to step 3.
You reached your lowest clock? Congrats, you should have a well undervolted CPU
Your voltages should always be lowering when your go from the highest clock to the lowest. If it happens that you have to increase the voltage at a lower clock, then also increase the higher clock frequency. I had a few hard locks because of this.
Example.
1000mAh (1GHz) > 900 mAh (900MHz) *< 950 mAh (800MHz) * > 700mAh (600mAh)
The 800MHz voltage is now higher than the 900MHz voltage. Also increase the 900MHz voltage to the same or higher voltage of the lower one.
1000mAh (1GHz) > 950 mAh (900MHz) > 950 mAh (800MHz) > 700mAh (600mAh)
Now that you have it undervolted, you may find that it could hardlock/reboot on you. When it happens do this:
Increase the voltage on all undervolted clocks by one step.
Continue using the device for a day
If the device locks up again, go back to back step 1
If its ok for a day, then every day lower the voltage back to what you had of only one clock (I suggest you go from highest to lowest)
You should be able to find which undervolt caused the reboot fairly quickly and still be able to normally use the phone and keep the rest of the "optimal" undervolts.
Click to expand...
Click to collapse
Sent from my GT-N7000 using xda premium
I don't think UV saves battery. It is display that sucks most of the juice.
You save less than 2% with extreme UV and after a single reboot caused by instability - you lose even more battery.
There's an excellent thread in Nexus S forums - "battery drain benchmarks" (please search it).
I had similar UV settings and my phone never crashed during benchmarks or stress tests.
But it always crashed while installing 100+ apps with app backup restore, restoring backups with TB or MBR, gaming.
After removing UV, it never crashed.
I haven't tested UV with ICS... would see and report if it really saves battery.
Boy124 said:
I don't think UV saves battery. It is display that sucks most of the juice.
You save less than 2% with extreme UV and after a single reboot caused by instability - you lose even more battery.
There's an excellent thread in Nexus S forums - "battery drain benchmarks" (please search it).
I had similar UV settings and my phone never crashed during benchmarks or stress tests.
But it always crashed while installing 100+ apps with app backup restore, restoring backups with TB or MBR, gaming.
After removing UV, it never crashed.
I haven't tested UV with ICS... would see and report if it really saves battery.
Click to expand...
Click to collapse
I'm not sure if you've read everything through carefully or you would have seen that I've covered several of your points.
You also would have seen the method I use for stress testing and would have noted that I aim for four things: speed/performance, stability, power management AND thermal regulation.
While I agree that the display, barring a wonky or misbehaving app, will almost always be the #1 battery drainer - power management will certainly help to conserve battery life.
You also would have seen I mention profiles. There may not be a one size fits all setting for everyone but one can most certainly set up profiles for different scenarios.. Such as TiB backups/restores.
Sent from my GT-N7000 using xda premium
Did you do some benchmarks at the highest speed several times to make sure you are getting extra performance? With this phone I noticed that while the phone wont crash.. .some times performance will drop when running at settings now fully correct.
Sent from my GT-N7000 using XDA
You covered a lot of points but UV is total waste of time.
You get nothing out of it.
http://forum.xda-developers.com/showthread.php?t=1478406
Could you please post your data, how much battery do you save after UV?
Disagree boy, cause with wakelock screen is off, there is significant battery drain, I went to 10 hours life on single charge, due to wakelock.
Normally with deepsleep about 2 days. That's a reduction of 87.5% with screen off. Cpu running @200mhz.
Do the same with undervolting will dramatically increase battery life in that situation. So overal it will be a fraction compared to using the device with screen on, but still significant.
Edit: guess I was wrong here
Sent from my GT-N7000 using Tapatalk 2
baz77 said:
Disagree boy, cause with wakelock screen is off, there is significant battery drain, I went to 10 hours life on single charge, due to wakelock.
Normally with deepsleep about 2 days. That's a reduction of 87.5% with screen off. Cpu running @200mhz.
Do the same with undervolting will dramatically increase battery life in that situation. So overal it will be a fraction compared to using the device with screen on, but still significant.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I actually did the test on Gingerbread.
I set min and max to 200 MHz, activated flight mode and had stock music player running for 3 hours - with undervolt and without undervolt.
To my surprise battery consumption was the same.
May be experts who know about our processor architecture can shed some light here.
Boy124 said:
You covered a lot of points but UV is total waste of time.
You get nothing out of it.
http://forum.xda-developers.com/showthread.php?t=1478406
Could you please post your data, how much battery do you save after UV?
Click to expand...
Click to collapse
I understand where you're coming from, boy.
I don't have data at the moment though I wish I did. But to be honest, it'd be scrambled anyway since whenever I'm not working or mission critical when I need proven stability, I'm testing out all different sorts of settings leading to lots and LOTS of reboots and such!
That being said, anecdotally, I have seen improved battery life for myself but maybe it's a placebo and I could be wrong about it - I have been before in the past. I do feel though that under my normal usage scenarios, I am experiencing less battery drain. It's difficult to quantify though exactly what this is due to since I experiment with kernels, voltages and frequencies.
But if all I'm getting is a 2% boost, man - I'll take it! Like any modder, whether it's min/maxing in a game, working on a car or whatever else, every little bit of a parameter squeezed out is something.
I also feel that you're too caught up on a single aspect, the battery life thing, to the detriment of my overarching holistic goal - efficiency.
Originally I started undervolting and experimenting with frequencies because of thermal output. I had wanted to experiment with x16 MSAA settings, which led to my GPU needing 400MHz and 1200mV which led to lots of heating up which led to me experimenting with everything I could.
Efficiency is what I want. The best performance at the best speeds at the best battery life at the best thermal regulation I can manage.
Now I'm looking at energy efficiency. I'm seeing suggestions that 100MHz may not be as efficient as 200MHz on our Exynos because the tradeoff in frequency power usage isn't worth the longer time spent completing tasks. I'm also seeing that in some situations, a performance best governor targeting max freq may be efficient because less time is spent completing a task and a quicker return to sleep.
I'm just sharing what I'm doing and hopefully others can benefit.
http://forum.xda-developers.com/showthread.php?t=1369817
Sent from my GT-N7000 using xda premium
Wow, thats illogical makes me wonder the math behind it.
Sent from my GT-N7000 using Tapatalk 2
While I appreciate the effort thrown into this, I humbly acknowledge the conclusion is incorrect.
When you lower Voltage slightly, without affecting stability, you pretty much put a toll on the processor for extra "wear and tear" and reduce its lifespan. However, this comes at the reward of reduced current.
So, it should be saving you battery. Underclocking it (safely) is also going to save you battery. And the same thing with different governors, like interactivX compared to regular ondemand, by finishing off processes quicker and reducing the frequency and voltage quicker, and going into Deep Sleep quicker.
I don't have the means to run a Scientific Experiment to prove these claims, nor the time to conduct them. But the majority of "hackers" synonymously agree it saves a noticeable power. These include themers, kernel developers and the casual user. I don't think an educated MAJORITY can be incorrect to the scale of this test's claims.
Hi,
Can anyone direct me to some info on altering CPU settings on my N10?
I've recently rooted and flashed the latest AOKP ROM and am interested in the performance control.
The current max is set to 1700Mhz which, of course, is the rated value for the CPU. Will I do any damage by increasing it and what effects do changing the voltage setting have?
Also, is there a guide to using Governor and IO schedulers?
Thanks in advance.
Pharmbob said:
Hi,
Can anyone direct me to some info on altering CPU settings on my N10?
I've recently rooted and flashed the latest AOKP ROM and am interested in the performance control.
The current max is set to 1700Mhz which, of course, is the rated value for the CPU. Will I do any damage by increasing it and what effects do changing the voltage setting have?
Also, is there a guide to using Governor and IO schedulers?
Thanks in advance.
Click to expand...
Click to collapse
Well I have to say that I haven't come across any device specific tutorials for governors or schedulers, and I would love to see someone put one together for the N10. My understanding is that the stock MHz value is purposely set on the slightly lower side to prevent any possibility of electrical issues. In regards to the voltage, lowering it may cause loss of display due to a lack of power and a major problem with increasing voltages is usually thermal throttling from high CPU temperatures.
But if you're interested in more governor and over clocking capabilities you should look at the KTManta kernel, I'm running it right now. You should be able to relatively safely over clock up to 1800MHz without crazy effects, but much more than that and you'll significantly reduce the tablet life.
Sent from my Nexus 10 using XDA Premium HD app
Huggogguh said:
Well I have to say that I haven't come across any device specific tutorials for governors or schedulers, and I would love to see someone put one together for the N10. My understanding is that the stock MHz value is purposely set on the slightly lower side to prevent any possibility of electrical issues. In regards to the voltage, lowering it may cause loss of display due to a lack of power and a major problem with increasing voltages is usually thermal throttling from high CPU temperatures.
But if you're interested in more governor and over clocking capabilities you should look at the KTManta kernel, I'm running it right now. You should be able to relatively safely over clock up to 1800MHz without crazy effects, but much more than that and you'll significantly reduce the tablet life.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Does overclocking to 1800MHz make much of a difference to performance?
I've just flashed the KTMANTA kernel and I am impressed.
Would it be detrimental to increase the GPU Max?
Pharmbob said:
I've just flashed the KTMANTA kernel and I am impressed.
Would it be detrimental to increase the GPU Max?
Click to expand...
Click to collapse
im not on AOKP ROM so i dont know how the CPU performance is optimized but on original rom the CPU speed rarely/never gets over
1000mhz
so overclocking to 1800mhz is pointless.
you need to upper the boost pulse instead
Patrik G said:
im not on AOKP ROM so i dont know how the CPU performance is optimized but on original rom the CPU speed rarely/never gets over
1000mhz
so overclocking to 1800mhz is pointless.
you need to upper the boost pulse instead
Click to expand...
Click to collapse
And what does the boost pulse do?
Pharmbob said:
And what does the boost pulse do?
Click to expand...
Click to collapse
it will boost the CPU speed higher when its under load
change this settings (leave the rest at default) in KTweakerT and the N10 will fly
CPU Governor: pegasusq
I/O Scheduler: ROW
under "Governor Adjustmensts" change these:
boostpulse_value: 1700
up_threshold: 40
up_threshold_at_min_freq: 20
Under Extras:
to keep your saved settings when the screen i off you will need to change the "Screen off profile Mhz" to something else than the Defualt setting
change it to 100mhz
also go in under the "Thermal Throttle Control" (settings for kids)
change these values to:
CPU start Throttle: 100
CPU Stop Throttle: 99
Memory Start Throttle: 100
Memory Stop Throttle: 99
that is the only way to get rid of the Throttling control.
one note is when you play games lock the min/max mhz to the same speed for an example (MIN 1500mhz/MAX 1500mhz)
its the up/down CPU speeds changes that causes it to lag
for movies lock the min/max speed at 800mhz and your blu ray movies will play without microstutter
also use BS player that has the fastest HW decoding
NOW Enjoy your Nexus 10 as it was ment to be used
Patrik G said:
it will boost the CPU speed higher when its under load
change this settings (leave the rest at default) in KTweakerT and the N10 will fly
CPU Governor: pegasusq
I/O Scheduler: ROW
under "Governor Adjustmensts" change these:
boostpulse_value: 1700
up_threshold: 40
up_threshold_at_min_freq: 20
Under Extras:
to keep your saved settings when the screen i off you will need to change the "Screen off profile Mhz" to something else than the Defualt setting
change it to 100mhz
also go in under the "Thermal Throttle Control" (settings for kids)
change these values to:
CPU start Throttle: 100
CPU Stop Throttle: 99
Memory Start Throttle: 100
Memory Stop Throttle: 99
that is the only way to get rid of the Throttling control.
one note is when you play games lock the min/max mhz to the same speed for an example (MIN 1500mhz/MAX 1500mhz)
its the up/down CPU speeds changes that causes it to lag
for movies lock the min/max speed at 800mhz and your blu ray movies will play without microstutter
also use BS player that has the fastest HW decoding
NOW Enjoy your Nexus 10 as it was ment to be used
Click to expand...
Click to collapse
Thanks for the info, I'm apprehensive about altering the thermal settings though. Will letting the processor get as hot as 100 degrees not reduce the life of the chip?
Pharmbob said:
Will letting the processor get as hot as 100 degrees not reduce the life of the chip?
Click to expand...
Click to collapse
sure if it would
i have already measured the CPU temp without the back case and its nowhere near 100 degrees
50 is more true so you are safe even without the Throttling control.
the thermal throttling control isnt measuring temps it only guess them.
Patrik G said:
it will boost the CPU speed higher when its under load
change this settings (leave the rest at default) in KTweakerT and the N10 will fly
CPU Governor: pegasusq
I/O Scheduler: ROW
under "Governor Adjustmensts" change these:
boostpulse_value: 1700
up_threshold: 40
up_threshold_at_min_freq: 20
Under Extras:
to keep your saved settings when the screen i off you will need to change the "Screen off profile Mhz" to something else than the Defualt setting
change it to 100mhz
also go in under the "Thermal Throttle Control" (settings for kids)
change these values to:
CPU start Throttle: 100
CPU Stop Throttle: 99
Memory Start Throttle: 100
Memory Stop Throttle: 99
that is the only way to get rid of the Throttling control.
one note is when you play games lock the min/max mhz to the same speed for an example (MIN 1500mhz/MAX 1500mhz)
its the up/down CPU speeds changes that causes it to lag
for movies lock the min/max speed at 800mhz and your blu ray movies will play without microstutter
also use BS player that has the fastest HW decoding
NOW Enjoy your Nexus 10 as it was ment to be used
Click to expand...
Click to collapse
Sorry for being such a noob but this is my first android device. I installed the kt room and the tweaker it all works fine. Bit whem i changed the room all my stift dissapeard. I vacker up my last rom can i just switch to that and backup with titan?
Btw it improved gta gaming very much. Bit what happens IF i always have the min/max on 1500?
Sent from my Nexus 10 using XDA Premium HD app
p0xis said:
Bit what happens IF i always have the min/max on 1500?
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
the tablet will explode after 30 minutes.
its the new Self destruction detection from samsung.