Database Develop

SetCpu for rooted Droid 3

What are the best settings to use on the droid 3 for overclocking?
Sent from my DROID3 using Tapatalk

I don't know the best settings, but I set it my SetCPU too low for my "ScreenOff" settings... So sometimes when I tried to turn my screen back on, my phone wouldn't have enough cpu power to turn itself back on... so make sure you don't set governors too low! easy enough fix though when you do.

don't think you can overclock until custom kernals are out.

Heelfan71 said:
don't think you can overclock until custom kernals are out.
Click to expand...
Click to collapse
Correct, but you can still set governors to under-clock and help battery-life.

I set my droid 3 to 800 mhz max, 300 mhz min, but the widget doesnt change, and if i open the app i can watch it jump to 1000 mhz. I have used setCPU on other phones, so I know how to work it.
Does setcpu not work with moto's hotplug governor? I've seen other forums say not to change that

If you set it to 300 and 800 or 600 using "ondemand" it works but the phone gets a little laggy.
Using "motplug" and trying to underclock freezes the device for me.
You can pull the battery to get it working again.
Sent from my rooted Droid 3 (Xda-Premium)

I looks like if you set the governor to anything but mot_hotplug the second core does not get deactivated with the phone is idle. So battery life may actually suffer.
*RETRACTED*

fotoingo said:
If you set it to 300 and 800 or 600 using "ondemand" it works but the phone gets a little laggy.
Using "motplug" and trying to underclock freezes the device for me.
You can pull the battery to get it working again.
Sent from my rooted Droid 3 (Xda-Premium)
Click to expand...
Click to collapse
I experienced this as well, but was using ondemand and 300-600 with screen off. Phone wouldn't turn on at all unless a battery pull was performed, scared me a bit to be honest until i realized what was happening. Decided to stick wit mot_hotplug until we get a custom kernel.

[Q] Galaxy Note N7000 Oveclocking Problems

So heres the deal...
Galaxy Note running RocketRom v22
AbyssNote 4.2 kernel
whenever i try to overclock to anything above 1500 and do a benchmark of it the phone stalls and eventually restarts... tried different voltage settings , tried setcpu , antutu cpu master pro , quadrant , antutu benchmark... no matter what my overclock crashes... anyone can help ?

Razor-1911 said:
So heres the deal...
Galaxy Note running RocketRom v22
AbyssNote 4.2 kernel
whenever i try to overclock to anything above 1500 and do a benchmark of it the phone stalls and eventually restarts... tried different voltage settings , tried setcpu , antutu cpu master pro , quadrant , antutu benchmark... no matter what my overclock crashes... anyone can help ?
Click to expand...
Click to collapse
Did you also raise the voltage SLOWLY and appropriately? If you did then you are tough out of luck. When it comes to overclocking, it also depends on the luck of the draw that you get

I am in the same boat. Before I upgraded to the newest abyss kernal I could get 1600 on stock voltages but now I can't get past 1500.
I think that just might be the highest that your phone and my phone can go on this kernal!

i tried undervoltage too =/ so maybe i just got one of the unlucky devices ?

A bit off topic.
I am on Midnote ICS and was appalled to see that the max CPU speed is limited to 1200 megs any idea why? Also Antutu Master CPU pro keeps on force shutting down the phone. Kindly help.

anilisanil have you tried Setcpu ?

anilisanil said:
A bit off topic.
I am on Midnote ICS and was appalled to see that the max CPU speed is limited to 1200 megs any idea why? Also Antutu Master CPU pro keeps on force shutting down the phone. Kindly help.
Click to expand...
Click to collapse
because its ICS, the kernal is limited to 1200

So anyone else tried overclocking and had same problems as me?
Sent from my GT-N7000 using xda premium

[Q] Cpu Frequency

Hello .. I'm Asking About The Maximal Cpu Frequency That I can Set On My Galaxy Mini To Be Faster And Smooth
Without having breaking it ??
& Thx !! :good:

Oh God .. Nobody Wanna Reply ...

poursystem said:
Oh God .. Nobody Wanna Reply ...
Click to expand...
Click to collapse
On stock it's set to 600MHz. 748MHz works for me without any hiccups.

200min and 780max
Governor : smartassv2
Sent from my GT-S5570 using xda app-developers app

i set my cpu to 806mhz for playing games but always lower it to 480mhz for normal use

max should not be more than 800 and min could be 100

dheeraj (dhlalit11) said:
max should not be more than 800 and min could be 100
Click to expand...
Click to collapse
Your phone would lag on such a low freq. After waking it up from sleep...... max: not more than 748mhz.... min: 320mhz.... governor: smartassv2/ondemand... i/o scheduler: sio/deadline.... respectively.
Sent from my GT-S5570 using xda premium

ashu.bigsmoke said:
Your phone would lag on such a low freq. After waking it up from sleep...... max: not more than 748mhz.... min: 320mhz.... governor: smartassv2/ondemand... i/o scheduler: sio/deadline.... respectively.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
and at min as 320mhz the battery would be sucked like hell even when the screen would be off
even my galaxy s with bigger screen don't lag with 100mhz clock speed
if the lag would be there it would be very small as till the lock screen is passed the processor would be at required speed
and setting it depends on person thats why i wrote "could be"

ashu.bigsmoke said:
Your phone would lag on such a low freq. After waking it up from sleep...... max: not more than 748mhz.... min: 320mhz.... governor: smartassv2/ondemand... i/o scheduler: sio/deadline.... respectively.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
dheeraj (dhlalit11) said:
and at min as 320mhz the battery would be sucked like hell even when the screen would be off
even my galaxy s with bigger screen don't lag with 100mhz clock speed
if the lag would be there it would be very small as till the lock screen is passed the processor would be at required speed
and setting it depends on person thats why i wrote "could be"
Click to expand...
Click to collapse
So, I think it's better to set min on 200mhz.

dheeraj (dhlalit11) said:
and at min as 320mhz the battery would be sucked like hell even when the screen would be off
even my galaxy s with bigger screen don't lag with 100mhz clock speed
if the lag would be there it would be very small as till the lock screen is passed the processor would be at required speed
and setting it depends on person thats why i wrote "could be"
Click to expand...
Click to collapse
It would not drain the battery because when you put screen off the device goes to deep sleep mode.... and saves a lot juice..... and even on galaxy y and latest entry level phones of samsung the default clocking is min: 315mhz and max: 832mhz, that also on 1200mah battery....
Sent from my GT-S5570 using xda premium

If you can adjust the screen off frequency set it to 125MHz.
Set the max screen-on frequency to 758MHz. Min to 300Mhz
Note: The higher the frequency you set, the faster your battery drains out.

try an app call "system tuner pro" with it you can ajust the CPU frequently when the screen is in deep sleep... also does a lot more... try it

ashu.bigsmoke said:
It would not drain the battery because when you put screen off the device goes to deep sleep mode.... and saves a lot juice..... and even on galaxy y and latest entry level phones of samsung the default clocking is min: 315mhz and max: 832mhz, that also on 1200mah battery....
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
i dont think samsung give deep sleep functionality in stock kernel
and if deep sleep is there that means way too much lag while waking up device
Samsung is not giving 315mhz as min speed in any of its kernel, 315mhz is way too much for min

dheeraj (dhlalit11) said:
i dont think samsung give deep sleep functionality in stock kernel
and if deep sleep is there that means way too much lag while waking up device
Samsung is not giving 315mhz as min speed in any of its kernel, 315mhz is way too much for min
Click to expand...
Click to collapse
It has deep sleep.... every phone has it man.... .... I have a galaxy Y so I know which freq. is min. Its 315mhz.... If there would be no deep sleep... your phone would no last even half a day... Search and think before you post...
Sent from Galaxy mini running CM10(Android 4.1.2 (Jellybean)).

Thx All :good:

CPU Info

I am using Carbon ROM 4.3 with Chronic kernal. The settings were at a min of ~1700mhz and a max of ~2200mhz. Before i set this I let the cpu temp cool to about 23 degrees Celsius. I then set the cpu governor to performance. Then I started running AnTuTu benchmark ver4. After the cpu integer test the cpu froze up. I was cooling my phone using a freezer with the phone on a paper towel which was on a bag of ice. The CPU crashed at the CPU float point test.
After another test I found that my CPU becomes unstable after 2160mhz.
The settings for the posted benchmark were CPU Min at 1674mhz and CPU Max at 2160mhz with the governor set at performance.

The minimum freq is mute when the gov is performance. Performance just keeps the cpu at the MAX freq.
Sent from my SPH-L720 using Tapatalk 2

Cloaker said:
The minimum freq is mute when the gov is performance. Performance just keeps the cpu at the MAX freq.
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
What he said.
Also you can just put the phone in the freezer for a while and let it cool way way down and then run the test while leaving it in the freezer.
Sent from my SPH-L720 using xda app-developers app

eskomo said:
What he said.
Also you can just put the phone in the freezer for a while and let it cool way way down and then run the test while leaving it in the freezer.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I am aware of this. I did have it in the freezer until it cooled down enough. The problem was not overheating, it was the CPU becoming unstable at full load with the processor being overclocked. The phone was still cold but it went to a reboot or just turned off.

Gotcha. I missed that part. I wasn't fully awake yet at 4:30am.
Sent from my SPH-L720 using xda app-developers app

Ok buddy here is your issue buddy its all about volts and throttle limits ive been fine tuning oc steps on antutu, cf bench, geekbench2 and geekbench3. Im stable all the way up to 2106 so far I use ktoonzs kernel cuz it has more options in his app the control alot of the throttling and volts. Ok understanding what it means what the phone just shuts off or reboots when the phone shuts off and wont cut back on you either have to do pull the battery out or plug the charger in to get the phone to boot up that means you had a power overload it drawed to much power on the battery which means you neesd to drop volts on your max step. Now if the phone is just rebooting or if the app FC back to the home screen that means that you dont have enough volts for your max step you only have to add or substract volts on that one step not on the whole board the best way to do this is just by finding your volts for that max step first yes scores will be low but once you find the volts then you start adjusting the throttle limits that way you can control the heat of the cpu but once you find the sweet spot of that oc step move to the next one and start over again for the next oc step doing the steps I listed above I will post pics of what I gotten so far. On a further note I have found that the freezer trick hurts you more then gaining anything cuz if you cool the cpu and battery to much it will make the cpu run sluggish cuz its to cold to run and if the battery is to cold it makes the phone think it dont have enough power to run on that oc step and makes the phone reboot so bare in mine the freezer isnt always the best way to do this I found that if the battery is below 28c it will reboot the phone during benching and if the cpu is below 25c it sluggish as hell the best app to use is cool tool on the app store if you use kt kernel I can give you the direct path to monitor cpu temp like his app does hope this helps you understand alil better of whats going on if you need anymore info just pm me
The #1 misfit
of my crew of misfits

As you see in the 4 pic my score close to what the GT-I9500 are getting on antutu
The #1 misfit
of my crew of misfits

[Q] Mini Performance

Hey, i think i have a big problem.
Im using a new ROM (this one http://forum.xda-developers.com/showthread.php?t=2622069) and i changed my Max CPU freq to 729Mhz and Min freq. to 122Mhz using ONDEMAND. So i decided to run a benchmark test using Quadrant Standard Edition and i got around 800 points i was kinda shocked because i saw many screenshots from other Mini Users with 2000+ points using an old ROM in this post -> http://forum.xda-developers.com/showthread.php?t=1437030.
I dont know what i have done to get so low score, i only have facebook and skype installed and greenify. I think my phone is faster then before but with this Benchmark Score i think my phone is in a pretty bad condition
Any suggestion?

erasem said:
Hey, i think i have a big problem.
Im using a new ROM (this one http://forum.xda-developers.com/showthread.php?t=2622069) and i changed my Max CPU freq to 729Mhz and Min freq. to 122Mhz using ONDEMAND. So i decided to run a benchmark test using Quadrant Standard Edition and i got around 800 points i was kinda shocked because i saw many screenshots from other Mini Users with 2000+ points using an old ROM in this post -> http://forum.xda-developers.com/showthread.php?t=1437030.
I dont know what i have done to get so low score, i only have facebook and skype installed and greenify. I think my phone is faster then before but with this Benchmark Score i think my phone is in a pretty bad condition
Any suggestion?
Click to expand...
Click to collapse
Well, what you're running is a Jelly Bean, which is NOT officially supported by Galaxy Mini's hardware.
Also, if you think your phone is already fast, then DON'T believe benchmark. I never choose benchmark for testing phone's smoothness, instead I use the ROM around 1 week, then see how does it responds. If it's faster, then I would say the ROM is good.