[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Phatboyj420:
Totaly configuration dependant. Meaning I have much better results with CYMBALINE I just got 48 Hours out of 85% battery on Embryo-4.1 w/ CYMBALINE and BLN active its all about your config I will say that I had Verry little usage with that run but even 48 hours at 100% Batt. and Zero use would be F___ing Amazing On this device.

I know there will be non believers so first I ask that you note my post name (it is not Skyrocket123) Second I will try to remember to take a screeny next time.

again it comes down to Configuration I use Juice deffender beta and the JuiceDeffender Ultimate Key and if used correctly this answers for most of my batt savings Try to use as many of the options available in the app as possible to reach max savings. For the most part the only things I havent used in this app (options wise) is The peak schedule and weekend schedule.

My config

1.in juice deffender I use the CPU stepping 192mhz/min 1080mhz/max-idle 1512mhz/max

2.I also use SystemTunerPro to set CPU freq/Volt with init.d script Ill edit with my exact freq/vltg later

3.Also in SystemTunerPro I set the screen-off CPU freq to 192mhz/min 1080mhz/max (this may seem redundant as to step ones max-idle setting but I have yet to notice any conflict and all freqs are being utilized appropriatly)

From 2. Edit My init.d freq/vltg settings output from SystemTunerPro.apk Just realized I forgot to state that I'm using a 3500 Ma Ext.Battery Even so I never got above 30hrs before CYMBALINE rescued me

*

[CENTER]echo "192000 825000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "310500 850000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "384000 850000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "432000 875000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "486000 875000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "540000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "594000 925000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "648000 950000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "702000 975000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "756000 975000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "810000 1025000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "864000 1025000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "918000 1025000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "972000 1025000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1026000 1050000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1080000 1050000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1134000 1075000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1188000 1075000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1242000 1100000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1296000 1100000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1350000 1125000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1404000 1175000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1458000 1175000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1512000 1200000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1566000 1200000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1620000 1250000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1674000 1250000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1728000 1275000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1782000 1275000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo "1836000 1300000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels[/CENTER]

I have had Zero force closes Zero Reboots,or problems of any kind this has become my best device,Rom,Kernel,Configuration to Date ( Thanks to Mohan for most of it)

If I didn't note a change I probably have not applied it ( Gov/IO Schdlr left alone )

Notes:

To use the CPU settings with JuiceDeFFender you have to install the AOSP helper I did this without proplems. Same is true if you want to apply the Network scaling spoke of below. Just follow the directions in Jdefender.

Help Requested:

The only option I Havent been able to use effectively is the network switching opyion I have it set (using a Rogers Radio UCLF3) but looking at the logs provided in-app it has not been able to switch network based on battery or signal strenth. I would appreciate any help with getting the network switching working.

I think this might be achieved by making some various build.prop changes but I do'nt understand well enough to decide witch changes to apply

The 2 changes that stick out to me are in the build.prop under CNE Module ( persist.cne.bwbased.rat.sel=false & persist.cne.bat.based.rat.mgt=false ) but as I said I am just guessing.

Mohan

Glad to see you in the JB DEV threads