Database Info

[Q] My device keeps powering off when the I put the screen to sleep.

For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?

supadupadoug said:
For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
Click to expand...
Click to collapse
Flash community kernel your getting sod or try removing your Oc UV settings
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Ok thanks. What is sod by the way???

supadupadoug said:
Ok thanks. What is sod by the way???
Click to expand...
Click to collapse
Sleep of death
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

oh lol im learning slowly but fa showly.

supadupadoug said:
oh lol im learning slowly but fa showly.
Click to expand...
Click to collapse
All good
Infusion kernel is great kernel but your settings are going to be trial an error play around with.UV that's usually the probably with sod
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Question about uv. is less best ie -25? and what does disabling the various clock speeds do?

Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.

Thanks I will give that a try. to oc really isn't my goal just to improve battery life. Right now seems to be working ok @12k with frequency uv @75-50

jdbeitz said:
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Click to expand...
Click to collapse
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)

You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation

supadupadoug said:
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
Click to expand...
Click to collapse
No prob. Buddy glad to have ya
Sent from my SAMSUNG-SGH-I997R using XDA Premium App

Entropy512 said:
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
Click to expand...
Click to collapse
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.

Dani897 said:
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Click to expand...
Click to collapse
Not a clue - I only know what netarchy has done, not what he plans on doing.
The architecture of voltage/CPU frequency control is significantly different in GB kernels than Froyo. In general it's cleaner, so a lot of the issues with rapid frequency changes might go away in GB. For example, there's some code in the base kernel that's supposed to facilitate rapid voltage changes (not exactly sure how... the only documentation people outside of Samsung have for the MAX8998 is kernel source code.)

Well guys I have some news. I continued use with set cpu no oc just uv on freq above 624 @ -75 and I kept my screen off profile set to 644 max powersave scaling, and my battery life has been outstanding i check emails frequently been texting all morning and playing wwf and im @ 70% after 4 hrs of use. I know I read % doesn't mean much compared to some volts ratio but I think this is worth mentioning. And for my purposes the goal has been achieved in extending battery life and still having exceptional performance.

Oh and I wanted to add that my phone recharges much faster especially with the screen off with these setting. Maybe nothing new to you but def a plus for a(us) neewb's reading.

[Q] Overlocking Values in SetCPU?

I have at max: 1200 MHz ,at min 83 and in typeerformance, are these values corecct or wrong for a custom rom?
-Greeting-
PD:Andro's Rom (3 days for release)

Yes, or no, because you need a screen off profile or your battery life will be damn short.

I think this should be in the general section and i recommend using the conservative governor over the performance since conservative goes to the minimum frequency when phone is not being used i.e. when screen is off. This is best for performance since it automatically goes to the maximum frequency when screen is on and when screen is off it goes to the minimum which is good for battery.

1200 is too high....
It will damage your battery....
I use 100 MHz to 800 MHz....
Its average and most of the users use the same....

[email protected] said:
1200 is too high....
It will damage your battery....
I use 100 MHz to 800 MHz....
Its average and most of the users use the same....
Click to expand...
Click to collapse
I think that is a very wise thing to do. I shall see how my phone runs at that speed.

Oks.thx.
Now:
MAX:800
MIN:83
Type: Conservative.
Are these values correctly now?
-Greettings-

AndroKite said:
Oks.thx.
Now:
MAX:800
MIN:83
Type: Conservative.
Are these values correctly now?
-Greettings-
Click to expand...
Click to collapse
Yeah its good.... ^_^
Happy to help..... ^_^

My batery temp is 27º - 28º celcius,is a good temp or maybe it can be danger for my battery?
-Grettings-

AndroKite said:
My batery temp is 27º - 28º celcius,is a good temp or maybe it can be danger for my battery?
-Grettings-
Click to expand...
Click to collapse
Aslong as its not 35+ degrees you are ok
Sent from my GT-I5800 using XDA App

Lol! Did you make a mistake by posting this question in the development section? Suppose to put at general section.
Accidentally sent from my ultra speedy SG3 phone using tapatalk.
P.S If my post have helped you, don't feel shy to click the thanks button

That frecuency will eat your battery.
I use my SetCPU at frecuencies 400-800Mhz, and use profiles for screen off (83-400Mhz), battery <20% (200-600Mhz), time (2am-6am) (83-83Mhz powersave)
always on demand (except time profile)
Greetings

My config is
Main 400-800 Mhz Ondemand Set on boot
Profiles
Temp >45°C 200-500 Mhz priority 100 Ondemand
time 2am-6am 83-83 Mhz priority 95 powesave
screen off 83-500 Mhz priority 90 Ondemand
Battery <20% 200-600 Mhz priority 80 Ondemand
I have g3mod 2.0 OC kernel
Greetings

I just use basic settings, no profiles or anything. Look in my signature.
I may add a few profiles after my lil bro is finished playing games on my phone.

My battery temp is 39 degrees Celsius is it that a good tempeture?

anything between 83 and 800 would work like charm and enough for day to day tasks..use conservative governor..set profile for screen off and on call..

[Q] Difference between under-clocking and under-volting

I'm using the Faux Kernel on my Skyrocket. I'm using Set CPU for speed control, under-clocking for more battery life.
I head the terms UC, OC, UV and OC. When I use Set CPU, I assume that when I set maximum CPU speeds, I'm under-clocking. But what is under-volting? Is that different? Is there an advantage to doing both?
Harry

There is an advantage to undervolting you need either fauxs app or systemmtuner to do so.
Undervolting is giving the cpu less power and asking it to do the same amount of work it was doing before
Sent from my GT-P7500 using xda premium

That sounds a bit more dangerous in terms of doing damage to the phone or having reboots etc. when you are giving the circuity less power than it was designed.
For those who chose to undervolt for power savings, it is usually done in conjunction with under-clocking, or is it a one or the other type thing?

Not really, under volting is not as dangerous as over volting (used to also achieve higher overclocks). Over volting can actually damage hardware if you provide too much juice.
Under volting just reduces the voltage, if its not enough the app freezes or worse the phone reboots. If that happens, bump it up one more step (+12500) and you should be fine. Find where you can go low but still be stable (for me it happens to be -87500) you will save more battery.
Dixit

all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good

icenight89 said:
all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good
Click to expand...
Click to collapse
My exact setup. -100mV UV, and 1.188 gHz UC. Went from 100% to 0% in 1 day 7.5 hours with 3 hours of screen on time. No juice defender either. I think its pretty food. Using faux 009u, btw.
Sent from my SAMSUNG-SGH-I727 using XDA

Only issue I got with Fauxclock is that it saves the CPU clocks I set (say 1.298ghz max) but it doesnt actually save the voltage after a reboot. I look at the VDD table and its still stock.
So only way to get it to work is to manually edit the VDD table itself. Not sure if this is by default that fauxclock doesnt actually save the voltages after a reboot.
Dixit

Don't see fauxclock in the application store, sorry, Google Play Station.

Thats cause its not in the Google Play. Its a separate app at this location
http://rootzwiki.com/topic/4550-app09-beta-snapdragon-dual-core-oc-control/
Dixit

Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.

Fauxclock has very basic CPU clock settings, it was created just for that faux compatible kernels so the original developer didnt spend weeks on it. It was just a simple and fast and effective GUI to set min/max clocks and also voltages (global scale). You can however set one other clock which is the "screen off" clock, but thats about it.

harry_fine said:
Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.
Click to expand...
Click to collapse
they will, use one or the other. U can manually change global vdd table and use setcpu, or forego advanced profiles in setcpu, but u can't/shouldn't use both

FauxClock force closes on launch for me..
EDIT: Getting a Faux kernal fixed that. Wow I feel dumb.

Shadeslayers said:
FauxClock force closes on launch for me..
Click to expand...
Click to collapse
Are u using faux kernel?

Any tips or thread about how to manually change global vdd table so that I can use SetCPU for the profiles and adjust voltage manually?
Is there a risk to that? If I set it and the phone won't boot, it sticks!

use Gideon UV/OC script and change vdd as u see fit. If it doesn't work u can always flash Gideon stock back

icenight89 said:
use Gideon UV/OC script and change bed as u see fit. If it doesn't work u can always flash Gideon stock back
Click to expand...
Click to collapse
What exactly is the difference between flashing Gideon's script or just using FauxClock? Thanks!

fauxclock gives u dynamic min/Max and voltage control as per user settings. Gideon is pre-set and makes use of init.d script. u can change it, but every change requires a reboot

[Q] Battery Life

Ive been using Lithium v1.2.1 and recently flashed to 1.3 and i have been experiencing worse battery life than i had on the stock rom...any roms any of you have used that have outstanding battery life?

philipvipe123 said:
Ive been using Lithium v1.2.1 and recently flashed to 1.3 and i have been experiencing worse battery life than i had on the stock rom...any roms any of you have used that have outstanding battery life?
Click to expand...
Click to collapse
Didn't realize v3 was out. I'll flash tonight and see if I experience any issues...
Sent from my MB865 using xda premium

philipvipe123 said:
Ive been using Lithium v1.2.1 and recently flashed to 1.3 and i have been experiencing worse battery life than i had on the stock rom...any roms any of you have used that have outstanding battery life?
Click to expand...
Click to collapse
give it a few charge cycles. often the battery stats are just screwed up after a new rom. If it is still bad in a few days, then something may be wrong.

Apex_Strider said:
Didn't realize v3 was out. I'll flash tonight and see if I experience any issues...
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Okay, so I've been running Lithium v1.3 for several weeks now, and even with an added overclock and other tweaks, I still have pretty darn good battery life with moderate to heavy usage. I can get a full day's charge running at 1.25 GHz and emailing/texting/calling/gaming throughout the day. Just updating concerns from the OP with my own experiences while running this awesome rom! :good:

Apex_Strider said:
Okay, so I've been running Lithium v1.3 for several weeks now, and even with an added overclock and other tweaks, I still have pretty darn good battery life with moderate to heavy usage. I can get a full day's charge running at 1.25 GHz and emailing/texting/calling/gaming throughout the day. Just updating concerns from the OP with my own experiences while running this awesome rom! :good:
Click to expand...
Click to collapse
can atrix 2 be overclock to 1.2 ghz without any issues nd how much further can it be overclock before it become unstable?

philipvipe123 said:
Ive been using Lithium v1.2.1 and recently flashed to 1.3 and i have been experiencing worse battery life than i had on the stock rom...any roms any of you have used that have outstanding battery life?
Click to expand...
Click to collapse
you haven't mentioned how many hrs you got in stock or how much less you getting in other ROMs
I am using stock ROM, 55% is enuf for me to go 12hrs which includes 4hrs of whatsapp, 2-3 hrs of gaming, continous gprs usage, 2 hrs of wifi tethering . a fullcharge once gave me 24hrs plus... I am very happy with the stock ROM

X-jo said:
you haven't mentioned how many hrs you got in stock or how much less you getting in other ROMs
I am using stock ROM, 55% is enuf for me to go 12hrs which includes 4hrs of whatsapp, 2-3 hrs of gaming, continous gprs usage, 2 hrs of wifi tethering . a fullcharge once gave me 24hrs plus... I am very happy with the stock ROM
Click to expand...
Click to collapse
do u have a extended battery or have underclock ur processor ....cause seriously i doubt thats even a possible figure lol with 1500mah battery my lg optimus one was running just 7 hours before it died.....with totally heavy usage
what game where u running ....was it some heavy game like nova ...dead space or small time killer??
cause when i play dead space for 2 hours my battery drip to 50% from 100% on stock rom with gprs on

GaganPla said:
do u have a extended battery or have underclock ur processor ....cause seriously i doubt thats even a possible figure lol with 1500mah battery my lg optimus one was running just 7 hours before it died.....with totally heavy usage
what game where u running ....was it some heavy game like nova ...dead space or small time killer??
cause when i play dead space for 2 hours my battery drip to 50% from 100% on stock rom with gprs on
Click to expand...
Click to collapse
no extended battery for me, i just bought the phone a week back. no extra accessories.. just stock ROM, stock phone and stock charger/battery.
the game i played for 2-2,5hrs was stick cricket, then i played Extreme Skating and Pro Zombie Soccer for 30 min. Today i played Sims 3 for an hour and that took 10% of my battery. I switched on Mobile Hotspot in my phone and used its GPRS on my laptop(tethered) for an hour, that also took 9-10%.
btw, my prev phone was an LG OP1 . Let me know if you want me to check anything else.

overclock
GaganPla said:
can atrix 2 be overclock to 1.2 ghz without any issues nd how much further can it be overclock before it become unstable?
Click to expand...
Click to collapse
it depends from phone to phone yes some of them run stable 1.2ghz i myself run stable 1.32 ghz but there are rumours maimum is 1.375 ghz give it a try

answersamir said:
it depends from phone to phone yes some of them run stable 1.2ghz i myself run stable 1.32 ghz but there are rumours maimum is 1.375 ghz give it a try
Click to expand...
Click to collapse
mind telling how did u overclock ur phone or procedure....???did u use setcpu?
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
X-jo said:
no extended battery for me, i just bought the phone a week back. no extra accessories.. just stock ROM, stock phone and stock charger/battery.
the game i played for 2-2,5hrs was stick cricket, then i played Extreme Skating and Pro Zombie Soccer for 30 min. Today i played Sims 3 for an hour and that took 10% of my battery. I switched on Mobile Hotspot in my phone and used its GPRS on my laptop(tethered) for an hour, that also took 9-10%.
btw, my prev phone was an LG OP1 . Let me know if you want me to check anything else.
Click to expand...
Click to collapse
than i gues i have issues with battery ....what a coincidence even i got my atrix 2 a week back.....though it was a replacement

We use tekahuna's milestone overclock modules for overclocking.
Changing the cpu speed involves echoing the desired table entry into the /proc/overclock/mpu_opps entry as root.
ie:
Code:
echo 3 1250000000 1375000 > /proc/overclock/mpu_opps
3 would be cpu slot 3 (3 is the highest on the atrix 2 typically set to 1ghz)
1250000000 is the desired frequency in hertz (1250 with six more zeroes at the end)
and 1375000 is the desired voltage in microvolts (1.375v). Tekahuna has said that 1.4v is the highest that these modules can push this. In my experience, that's not enough extra voltage to make a big difference in max overclock speed.
I recommend extensive testing of an overclock before you alter the init scripts to match. (well if you're using a rom with init built in)

Init.d support can be added to any rom by flashing this
http://forum.xda-developers.com/showthread.php?t=1710980
Motorola lied and I'm still locked mb865

GaganPla said:
can atrix 2 be overclock to 1.2 ghz without any issues nd how much further can it be overclock before it become unstable?
Click to expand...
Click to collapse
As answersamir stated, it realty depends on the phone. I've clocked as high as 1.3GHz stably but don't really need that high of a clock speed, so I scaled back to 1.25GHz with underclock at 240MHz at echo 0. You'll just have to experiment without the echo 3 settings in the init.d folder making slow (100MHz) incremental jumps to see where your phone can run stable before random reboots or freezing occurs... after changing settings, reboot each time, and run for a while at the new clock speed to test.
Sent from my MB865 using xda premium

GaganPla said:
mind telling how did u overclock ur phone or procedure....???did u use setcpu?
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
than i gues i have issues with battery ....what a coincidence even i got my atrix 2 a week back.....though it was a replacement
Click to expand...
Click to collapse
use Battery Monitor Widget, charge the phone till you see 100% in that app, A2 shows charge in multiples of 10, so 100% in A2 battery means it reached 95%. Via the BMW app, you can add a widget to your homescreen in counts of 1% so you will see real battery %. Also it will show mAh, so when you charge untill it reaches 100% or 1740/1740mAh then only stop charging. You can see battery graphs and all that.
Hope yours is set to Settings->Battery $ data manager ->Battery mode -> Night-tiime saver
cos mine is
also via that app, it shows for me voltage of ~4113mV and a decent temperature of 33-35 degree celcius while charging.
Install the app and let us know the details. Also hope you are using the motorola charger and connecting it directly other than via usb->pc

X-jo said:
use Battery Monitor Widget, charge the phone till you see 100% in that app, A2 shows charge in multiples of 10, so 100% in A2 battery means it reached 95%. Via the BMW app, you can add a widget to your homescreen in counts of 1% so you will see real battery %. Also it will show mAh, so when you charge untill it reaches 100% or 1740/1740mAh then only stop charging. You can see battery graphs and all that.
Hope yours is set to Settings->Battery $ data manager ->Battery mode -> Night-tiime saver
cos mine is
also via that app, it shows for me voltage of ~4113mV and a decent temperature of 33-35 degree celcius while charging.
Install the app and let us know the details. Also hope you are using the motorola charger and connecting it directly other than via usb->pc
Click to expand...
Click to collapse
BTW NOW I M ON ICS leak
as u may see image speak itself

moofree said:
We use tekahuna's milestone overclock modules for overclocking.
Changing the cpu speed involves echoing the desired table entry into the /proc/overclock/mpu_opps entry as root.
ie:
Code:
echo 3 1250000000 1375000 > /proc/overclock/mpu_opps
3 would be cpu slot 3 (3 is the highest on the atrix 2 typically set to 1ghz)
1250000000 is the desired frequency in hertz (1250 with six more zeroes at the end)
and 1375000 is the desired voltage in microvolts (1.375v). Tekahuna has said that 1.4v is the highest that these modules can push this. In my experience, that's not enough extra voltage to make a big difference in max overclock speed.
I recommend extensive testing of an overclock before you alter the init scripts to match. (well if you're using a rom with init built in)
Click to expand...
Click to collapse
pls explain more in details....i m totally confused with echo thing nd r this lines to be typed in terminal emulater ?

GaganPla said:
pls explain more in details....i m totally confused with echo thing nd r this lines to be typed in terminal emulater ?
Click to expand...
Click to collapse
Here's a simple step-by-step for overclocking:
Open Root Explorer or download HERE
Navigate to: system>etc>init.d then select the Oc3 with Text Editor
Find the echo 3 value that reads: echo 3 1125000000 61 > /proc/overclock/mpu_opps
Then, using the text editor in Root Explorer, change the echo 3 value from 1125000000 to *up to 1200000000 or even higher. (see note below!)
Hit the "back button" and Root Explorer will ask you to save changes. Confirm the changes, and reboot.
After rebooting, open SetCPU and you will see your changes there.
*You can experiment with your clock speed, and a good rule of thumb is to bump up slowly, rather than making large jumps all at once. Start by going from 1125 to 1150 and reboot. Then, if all is well and you've ran at this higher clock speed for a good 5 to 10 minutes, do the above listed process again and go from 1150 to 1175, and so on until you reach your highest stable overclock speed.

Apex_Strider said:
Here's a simple step-by-step for overclocking:
Open Root Explorer or download HERE
Navigate to: system>etc>init.d then select the Oc3 with Text Editor
Find the echo 3 value that reads: echo 3 1125000000 61 > /proc/overclock/mpu_opps
Then, using the text editor in Root Explorer, change the echo 3 value from 1125000000 to *up to 1200000000 or even higher. (see note below!)
Hit the "back button" and Root Explorer will ask you to save changes. Confirm the changes, and reboot.
After rebooting, open SetCPU and you will see your changes there.
*You can experiment with your clock speed, and a good rule of thumb is to bump up slowly, rather than making large jumps all at once. Start by going from 1125 to 1150 and reboot. Then, if all is well and you've ran at this higher clock speed for a good 5 to 10 minutes, do the above listed process again and go from 1150 to 1175, and so on until you reach your highest stable overclock speed.
Click to expand...
Click to collapse
thanks dude.....i was totally lost with this overclocking thing....i think this info should be added in beginners guide .....it was so easy to overclock my old defy

GaganPla said:
thanks dude.....i was totally lost with this overclocking thing....i think this info should be added in beginners guide .....it was so easy to overclock my old defy
Click to expand...
Click to collapse
You can also underclock in the same way, by changing the echo 0 values. I set mine to underclock to 240MHz at echo 0. Also, using SetCPU you can change the CPU mode (which, you probably already know) from mot_hotplug to performance to ondemand, etc. Experimenting with these settings can either improve or decrease your battery life with the new overclocked speed.
Also, check out THIS THREAD post by rdavisct that gives further explanation to the topic.

Apex_Strider said:
Here's a simple step-by-step for overclocking:
Open Root Explorer or download HERE
Navigate to: system>etc>init.d then select the Oc3 with Text Editor
Find the echo 3 value that reads: echo 3 1125000000 61 > /proc/overclock/mpu_opps
Then, using the text editor in Root Explorer, change the echo 3 value from 1125000000 to *up to 1200000000 or even higher. (see note below!)
Hit the "bacre k button" and Root Explorer will ask you to save changes. Confirm the changes, and reboot.
After rebooting, open SetCPU and you will see your changes there.
*You can experimetherent with your clock speed, and a good rule of thumb is to bump up slowly, rather than making large jumps all at once. Start by going from 1125 to 1150 and reboot. Then, if all is well and you've ran at this higher clock speed for a good 5 to 10 minutes, do the above listed process again and go from 1150 to 1175, and so on until you reach your highest stable overclock speed.
Click to expand...
Click to collapse
Hmm there a problem....there no oc3 file in init.d???

pros and cons OC/UV

about time for me to change roms again. i know there are many with this option, but have never chose to pursue that option due to lack of understanding benefits. always seemed to get satisfactory battery life out of phone, but could it be better? i have noticed different speeds on my phone with different roms but is this something that can speed up and keep the smooooth in my phone?
just thought i would get some feedback of the advantages and disadvantages of overclocking and undervolting.
will it harm my infuse?
what are good settings?
what exactly would the OC or UV each do?
if i run a search on this, i know i am going to get the phone book and just figured i would get a more specific answer directly as opposed to piecing little bits together and still not being confident in what my interpretation would be.
everyone in the infuse community always seems to have the answers and dont steer the dullards such as myself in the wrong direction.
you guys are the MAN, and well, you women.....your the woman i reckon

captemo said:
will it harm my infuse?
Click to expand...
Click to collapse
No, so significant damage can be done with overclocking. Alhought if you set your ghz too high your phone might become unresponsive, overheat and/or auto reboot your device. This is normal if your on GB and some ICS roms. Don't see it much on JB becuase the some kernels dont support it. Just be sure to play with your settings and MAKE SURE SET ON BOOT IS DISABLED or else your phone will be stuck in a bootloop when overclocked beyond stable settings.
captemo said:
what are good settings?
Click to expand...
Click to collapse
I usually stick with 1400 ghz because 1600 ghz[max] drains battery too quickly for not much of performance boost and 1600 is considered unstable on most GB and ICS roms. As for CPU governor Id stick with ONDEMAND.
captemo said:
what exactly would the OC or UV each do?
Click to expand...
Click to collapse
OC is over clocking your processor to a higher ghz for better perofmance and under volting is drawing less energy

Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2

Garen21 said:
Is there like a guide saying what each CPU governor does? Because some of them are pretty confusing with their terminology, like smartassv2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1420742

I used to under volt a lot to get better battery life. But it seemed to make a couple apps hang now and then.
I am now on Scotts PA JellyBean ROM. Battery life is very good for me stock with this. So I have left under volt to stock settings.
Normally I'll run on smartassV2 governer. With NOOP i/o. And 100mhz - 1400mhz.. just for a little extra boost.
When I know I'll be playing a game or multitasking, I'll boost it to 1600mhz.
Overall stock settings run amazing, both battery life and performance, on Scott's PA JB and CM10.
After doing some reading, I believe I can get better results from using the above settings. It all depends on what your personal goal is.
The biggest concern you should have when overclocking is mentioned above. Boot loop, just make sure you test it for a while with set on boot un checked.
Undervolting you can go to low and also boot loop, so same applies here... leave set on boot un checked. All phones are different on what settings they run best at. Just gotta play around and see what works for you.
A good rule of thumb for under voting... go down 25mv at a time and test it out... keep going down 25mv until you get a problem or boot loop and then go back.. then you'll know your max.
You can safely under volt more on the lower frequencies than you can the higher ones. Personally I never undervolted more than 100mv across the board. And when I did, I usually kept it around -50mv.
Sent from my SGH-I997 using xda app-developers app

not for infuse but a good reference for ocuv. explains what they do
http://forum.xda-developers.com/showthread.php?t=1827635
Sent from my GT-I9300 using xda premium

This is the best guide I've found covering kernel and system tuning - CPU parameters, governors, schedulers, init.d, loadable modules, etc. It's for the SGS2 (i9000) and some of the governors/schedulers are not available on the Infuse, but much of this is applicable to our phone:
http://forum.xda-developers.com/showthread.php?t=1369817
As for OC/UV, as long as you stay away from the "Performance" governor (this runs the phone at max freq all the time), and undervolting below -75 to -100 you generally will be safe. As phones are different, it is important to test in gradual steps to ensure your phone will be reliable. Use a good CPU manager, like SetCPU, Antutu, or Voltage Control. Make sure you enable the "revert to stock" feature so that you can boot recovery and turn off any bad OC/UV. As noted above, do not check the enable on boot setting until you are certain you have a good config.
The decision to OC should take into account how you use the phone. If your phone is asleep more than 80% of the time on average, you can probably run an OC config and still have overall good battery life (i.e. lasting an entire day with nightly recharges). If you use your phone for music playback or something else that prevents it from sleeping, OC may not be for you. If you run CPU intensive games, it is better to disable UV settings while OCed.
Use CPU Spy to keep an eye on your time at each freq state (and sleep). Use the default battery stats and graph to monitor which apps are consuming the most battery. Use apps like Better Battery Stats, Android Assistant and Watchdog for more detailed monitoring of what is keeping the phone awake and which apps/processes are top cpu resource consumers. With this information you can identify problem apps and decide whether you should remove them from your phone.
From the "unintended functionality" side of the house, there are certain tweaks that will cause your phone to run at max freq ... mucking around with phone properties in build.prop can lead to runaway rild process problems (usually shows up as unusually high "Dialer" in the standard battery stats list and a phone that is warm or hot to the touch). Some of the tweak scripts in adrenaline and tbolt can cause similar problems. There is a known bug in the infuse network drivers that shows up as much higher than normal Android OS battery usage. This can usually be corrected (short term fix) by toggling Flight/Airplane mode off/on. Running the stock UCLB3 GB kernel also seems to minimize this issue (assuming you are running a GB ROM), but flash with caution as you will need to disable voodoo lagfix first. (You will also lose CWM recovery, OC/UV capability, and be on the slower stock file system setup).

I have done a fair amount of experimenting including lots of time on conservative governor with Fmax=1600 and never had any problem that I attributed to OC'ing.
In contrast I did find a limit on UVing. I just updated my thread with my experience on uv here:
http://forum.xda-developers.com/showthread.php?p=32552571#post32552571
The bottom line is that for MY phone, the following works fine:
100 Mhz: 950mv max – 50mv = 900 millivolts
200 Mhz: 950mv max – 25= 925 millivolts
400 Mhz: 1050mv max – 50mv = 1000 millivolts
800 Mhz: 1200mv max – 75 mv = 1125 millivolts
1200 Mhz: 1275mv max – 50mv = 1225 millivolts
1600 Mhz: 1400mv max – 75mv = 1325 millivolts
Some other links with others' experience suggestions about UV'ing for Infuse:
Hozw low is your undervolt?
http://forum.xda-developers.com/showthread.php?t=1693689&highlight=kernel
[Q] Recommended SetCPU settings?
http://forum.xda-developers.com/showthread.php?t=1292836&highlight=setcpu
You’ll note the last thread has comments from Entropy’s settings.
Also Zen and qkster gave advice in the first thread (my thread).
All three guys very well respected and worth listening to.
Entropy mentioned you can uv the higher frequencies more than the lower (different than what was posted earlier in this thread). I don’t know for sure but I’d lean toward Entropy’s advice on that matter.
I think all in all somewhere between 50 and 100 is the max you can expect to undervolt.
What can be achieved varies with phone as stated by many.
You are welcome to experiment with slowly decreasing. That's what I did.
But in the benefit of hindsight, the process of slowly decreasing is tedious. And going beyond the limit was a little scarey for me. Could've been worse if the phone crapped out at a critical time during "experimenting". Like almost everything related to battery life, the results (how much benefit) seem y subjective (difficult to measure quantitatively). Most people say they don’t notice a dramatic difference with UV. If you want to get the low hanging fruit without a lot effort, you might just try 50 down. That's what I'd do if I had to do it all over again.
By the way, setcpu can be set up to provide a failsafe escape route even if you go overboard. There is a zip file that will toggle the setcpu settings off when launched from CWM. You just have to put the zip file on your sd card before you start tweaking. See "safe mode" in the setcpu documentation.

started to wonder at first whether i would get any responses after 218 views and nothing, but i knew the community would come through as they always do. all the regulars as usual regulars ( Zen, Quickster and others) are always eager to help. i think you have all provided me with the valuable info i requested.
thank you much party people