OK when I run CyanogenMod and change performance. It always goes back to the original setting. And 1 more question why is the min CPU frequency at 1026
Sent from my Nexus 4 using xda app-developers app
Try applying "set on boot"
mattoaida said:
OK when I run CyanogenMod and change performance. It always goes back to the original setting. And 1 more question why is the min CPU frequency at 1026
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'm not sure about the settings not sticking, but I can explain the min frequency thing. If you're running the stock CM kernel, or a kernel that uses MPDecision, upon touching the screen, it locks the minimum frequency to 1ghz for about one second to aid project butter. This allows for smoother transitions and faster loading, as events such as animations and applications opening usually occur as a result of you poking something on the screen
Connor Baker
Connor Baker said:
I'm not sure about the settings not sticking, but I can explain the min frequency thing. If you're running the stock CM kernel, or a kernel that uses MPDecision, upon touching the screen, it locks the minimum frequency to 1ghz for about one second to aid project butter. This allows for smoother transitions and faster loading, as events such as animations and applications opening usually occur as a result of you poking something on the screen
Connor Baker
Click to expand...
Click to collapse
OK but does this drain a lot of battery
Sent from my Nexus 4 using xda app-developers app
Related
Now that we have a new way to overclock in v14 there are near unlimited variables to overclocking with this kernel. I've found a good balance of performance with 1300ghz step and live OC value of 121%. Let us know what has worked for you. You may include voltages as well.
I'm using reborn90's settings
200-1000; 110% live oc arm volt; 800/950/1100/1175 int volt; 1000/1000/1000/1025
Seems rather steady, I also recommend turning save on boot in settings of nstools before applying these settings just in case xD
Sent from my SCH-I500 using xda premium
I am on 100-1300 with 116% Live OC, haven't played with voltage yet but everything runs great.
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
mleonm5 said:
I can't seem to get any live OC percentage stable and anything around 118% + automatically freezes and reboots.any suggestions?
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Do you UV first then live oc? Or is it just stock voltages?
Sent from my SCH-I500 using xda premium
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
mleonm5 said:
For the most part I just use stock voltages when playing around with live OC because I haven't found any voltages in threads that i'm sure are stable.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
it depends on how far you phone can go, some can oc more then others but some less then others, I usually never go passed 1.2ghz ,I'd rather save battery.
Sent from my SCH-I500 using xda premium
Just my opinion, but since Android 4.0 relies so heavily on the hardware rendering capabilities of the phone you'd be better off to UNDERCLOCK the CPU to 800mHz, and apply the Live OC to say 125% and have an effective CPU speed of 1000mHz while increasing the GPU clock by the same amount. I've tried it and it works very well but I didn't stick with it long enough to see how it affected battery life. You will need to modify your voltages though. I was at 1250mV on the 800mHz step.
If anyone is interested in just using stock settings, i found this thread interesting:
http://forum.xda-developers.com/showthread.php?t=1424064
100-800 mhz, 125% live oc.
So how much of a change have you noticed from Stock kernel to Glitch. I tried OCing once.. and it froze.. and phone died.. and ended up having to wipe / re-flash. Probably user error though
Just wanted to say I accidentally OC'd to 1.4ghz with 110% LOC and man did this thing fly and didn't even crash.
Sent from my ICS Mesmerize
I noticed I'm able to achieve higher stable oc (over 1500) using low leakage voltage and live oc of 116 or less. Without low leakage i can barely acheive 1400 oc at anything over 110 live oc. Never noticed this much difference in internal voltage stability in previous kernel version. I wonder what's changed?
So I was trying to mess around with CPU profiles and I noticed that the low end of the CPU is clocked at 1GHz. If I lower it with Rom Toolbox, it just goes right back up after I leave the menu. the profiles won't stick, governors don't make a difference, and I'm a little confused.
Can someone shed some light on this for me?
I thought the lowest speed was 384 MHz? Install CPU Spy and check what it says.
It is 384MHz. The lower frequency change because of project butter that make the cpu run at a higher frequency when you touch the screen.
Sent from my Nexus 4 using xda app-developers app
Dont you need a custom kernal in order to change the clock speeds?
sent via xda premium with nexus 7
No, we can already change it but it won't stick since it has its own frequency management.
Sent from my Nexus 4 using xda app-developers app
Is this somewhat similar to perflocker in HTC devices? It had to be disabled to change any cpu settings AT ALL with the stock kernel.
hervelo said:
No, we can already change it but it won't stick since it has its own frequency management.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
That is why..
sent via xda premium with nexus 7
ed10000 said:
I thought the lowest speed was 384 MHz? Install CPU Spy and check what it says.
Click to expand...
Click to collapse
You're right. I guess it just has its own profile to set at 1GHz when the screen is on, because the CPU Spy showed it in Deep Sleep/384Mhz for the majority of the night.
test1
Hello guys,
I'm here to ask for all of your opinions about the cpu Profiles, frequencies and governor.
For screen on I'm currently using 1200mHz on performance, I would like to know if it would save more battery by using on demand governor.
Some months ago I had a discussion with few xda members about this subject. But that was on aurora v4. Now I'm currently on v5 u17. Let me know your opinion. Thanks
Sent from my U8800 using xda app-developers app
To be honest, I've never experienced any benefits of setting cpu profiles for screen on, screen off etc. Your phone will work much more smoothly if you stick as close to the defaults as possible.
I don't use profiles. My min is 245 and max 1200, using on demand governor.
For a while I experimented with profiles, and had bad lag when unlocking the phone, and terrible battery use when screen on.
Independent of profiles, your governor will put your phone into deep sleep when the screen is off anyway.
Do a search for "race to idle" this explains in more detail the benefits of using ondemand as opposed to other governors in terms of battery use etc.
IMHO, Android as a platform would be far better served if people stuck close to the default settings and cpu profiles. Most of the time, any negligible benefits are just placebo.
Sent from my U8800 using xda app-developers app
So according to the race to idle running with performance governor saves battery
Sent from my U8800 using xda app-developers app
In theory yes, but if your cpu is always running at max frequency, ie even when doing nothing, then no.
I have done tests, and my battery always lasts longer using ondemand as opposed to performance, or other governors.
Sent from my U8800 using xda app-developers app
Use interactive/bfq that's the best in my opinion
Sent from my U8800-51 using xda premium
I have nexus 7 3G 32gb with trinity kernel,stock ROM.And i have question how do i overclock GPU?
Use Trinity kernel toolbox. It has the option to set the speed of the GPU and adjust the CPU voltages
Sent from my Nexus 7 using xda app-developers app
winged mantis said:
Use Trinity kernel toolbox. It has the option to set the speed of the GPU and adjust the CPU voltages
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Can my GPU burn or something like that?Or high GPU frequency will cause only reboot?
I've read that the max recommended GPU speed is 484.Going much higher the battery will drain too much and will get hot. If you set the speed to high it will become unstable and usually reboot. It will reboot and rest default speeds long before it will have time to melt. Just don't use your over clock settings to be set on boot
Sent from my Nexus 7 using xda app-developers app
FatalaS said:
I have nexus 7 3G 32gb with trinity kernel,stock ROM.And i have question how do i overclock GPU?
Click to expand...
Click to collapse
1. easiest way, use the trinity kernel toolbox and adjust the gpu slider up or down.
2. or manually go to /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc/ with a root file explorer(like root explorer) and manually edit the variable and save it.
yes, it can get very hot if overclocking the gpu. especially when playing cpu intensive games. worst thing is youll reboot if things go haywire.
Excessive voltage and heat can easily fry a CPU/GPU and other motherboard components, so be careful.
Sent from my Nexus 7 using Tapatalk HD
I'm running fauxs kernel, and in his op it says for battery life to turn mpdecision off. When I leave it on only the first 2 cores run and idle at 384mhz, but when I turn it off all 4 cores are running constantly, and the 3 & 4 core idle at 702 mhz. Maybe I'm missing something, but how can turning mpdecision off be better on battery when you have all 4 cores running constantly instead of 2?
Sent from my Nexus 4 using xda app-developers app
Sounds like you're running his enhanced stock kernel, the recommended settings only apply to faux kernel
Michealtbh said:
Sounds like you're running his enhanced stock kernel, the recommended settings only apply to faux kernel
Click to expand...
Click to collapse
No, I'm using the 008 mainline
mpdecision kicks in when you touch the screen it ramps the min cpu speed to 1026 so it uses more battery but increase responsivness
DynamicRam said:
mpdecision kicks in when you touch the screen it ramps the min cpu speed to 1026 so it uses more battery but increase responsivness
Click to expand...
Click to collapse
See, that I knew already, and it does make sense. But when I turned mpdecision off, it was doing the exact same thing, but instead of only having the first two cores online, it had all 4 cores online constantly with the last 2 at 702mhz. From what I read, people are saying turning mpdecision off is better for battery but I just don't understand how it could be with 4 cores running constantly instead of 2, unless I'm doing something wrong (which I probably am lol)
Sent from my Nexus 4 using xda app-developers app