I was wondering if the speed mod kernel for the international galaxy s is compatible with the Samsung vibrant
Sent from my SGH-T959 using XDA App
Any Kernel recommended for a stock Froyo Vibrant?
I need good battery life and CWM
mozXegX said:
Any Kernel recommended for a stock Froyo Vibrant?
I need good battery life and CWM
Click to expand...
Click to collapse
any should work i think, overstock always had decent battery for me or try bali uv
Try this. If you get any crashes, reduce all millivolts back -25 each until it's perfectly stable.
Bali-X 1.2 found here: http://forum.xda-developers.com/showthread.php?t=1043947
Get SetCPU off the Market and use these settings:
Conservative Governor
100 - 1200 frequency
1200 at -25mv
1000 at -50mv
800 at -75mv
400 at -125mv
200 at -150mv
100 at -175mv
Screen Off Profile of 100 - 800 Conservative
If you want to tweak out a little more energy savings, though at the cost of some performance, you can set the typical frequency to 100 - 1000, or even 100 - 800.
Be sure to calibrate your battery (charge to 100%, unplug, re-plug, charge to 100%, unplug, re-plug, charge to 100%, unplug, replug, charge to 100%, then either delete the batterystats setting with Root Explorer, or use the Battery Calibration mod from the market once you're done bump charging, but don't bump charge too many times, as it's not healthy for the battery in the long term.) after installing Bali X and setting the voltage tweaks.
Still, the best battery saver of all has to do with your display, as it uses far more juice than anything else. Since it's an AMOLED display, lighter colors burn more juice than darker colors. Use a dark themes for your commonly used programs like Googles http://www.blackle.com/ as well as your messenger, and use black wallpaper.
Related
Am on Froshedyo Vanilla + Green minimal theme and was wondering does the min CPU of 245mhz and 19mhz eat up the amount of battery? Do they run the same voltage? Any of you guys see a difference as far battery life running 19? I know it makes the phone take a little longer to wake up when a call is coming in. Thoughts?
Currently I have it 528/245 Smartass with a charging profile
I always had problems with lag when I clocked down to 19. I never really felt that it provided any extra battery life, but others feel that it does.
+1 on the lag. We run 245 and its smooth.
Sent from my FroyoEris using Tapatalk
+1
There have been occasions, possibly the particular combination of ROM, the apps installed, and what app or method I'm using to overclock which have resulted in 19 working fine sometimes, but most of the time at least 160 or 210 (?) would be a necessary happy medium so that waking the screen or answering calls wouldn't be downright excruciating, so my short answer is yes, at least 210 or 245. I forget and am too lazy to look if 210 was an option, and I'm tired. LOL.
FroShedYo runs Conap's CFS kernel, and, IIRC, it was made quite clear in that thread that the kernel runs best at a minimum of 245 MHz.
I'll say this - last month I spent a lot of time going back and forth between xtrSENSE and xtrROM, both running at 604.8 max and as low as 19.2 min (I tried all steps from 245 down to 19.2), and CELB, running at 710 max and 245 min, and I get much better battery life with CELB. In fact, with xtrROM I had to set some of my update times for apps that I use to longer intervals just to get through the end of the day with 20% battery life left. With CELB I never finish the day with less than 40%, and it's often over 50%.
It may be different for you, but that's what happens on my phone.
I use 19.2.
122 and 19.2 both use the same voltage though I believe. I only use 19.2 because it keeps the average down.
I listen to pandora with 19.2 min 480max smartass with no lag.
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
Interesting point you raise actually.
I've just installed Setcpu and used the on demand governor. I left the values as default (200mhz for minimum and 1.2 ghz for maximum) - with no overclock.
I've immediately noticed swiping through the screens is a bit smoother and the biggest improvement is the gallery. All my photos appear much smoother. Before the gallery app was a bit lagy.
I haven't set any profiles yet such as screen off.
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
jzuijlek said:
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
Click to expand...
Click to collapse
Have you tried this yet though on the Galaxy S2?
There is definitely less lag than before - as stated, specifically in the gallery app. Just generally swiping feels more responsive as well. Battery is still pretty awesome, especially when using Lightening Rom 1.1 and the Android battery calibration app.
Hmm. I'll try SetCPU on the SGS2 and post back the findings (Performance+Battery).
I don't know how can it get any more smoother, I mean its already SO smooth!
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
alexleon said:
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
Click to expand...
Click to collapse
IT IS TRUE. I agree with every single line you wrote, it is just my expericence.
I have too setcpu conservative and undercloked 800 Mhz.
There no slow down or lag at all... But I am wondering if it gives a real boost to battery life. I am not sure of this.
I'll keep you guys posted... But I think that an undevolted Kernel it is really a need as for the solution of the damn dual core ginger bug that is sucking 20% of my battery every day
Well,from my experience with my Desire and Desire HD(won't even bother with the Hero,I had no real knowledge then),governors can make a huge difference.I for one like smartass or interactive governors(mostly the same).I wouldn't suggest conservative,interactive does the job much better.Tasks get done in less time and the CPU throttles down more quickly.Other than that,you can underclock or overclock all you like,it never made any big difference in battery life for me(Unless Sammy's CPUs are different in that aspect-Snapdragons are really "overclock-friendly").That's personal preference after all!
Anyway,the best solution IMO would be a vdd_levels interface.For those who don't know what it is,it is a mod made by -snq(Meet him at the Desire forums-That guy's a true LEGEND!He can patch/modify anything!),which practically allows you to change the voltage levels of the CPU on the fly rather than having to stick with the values hardcoded into the kernel.Using this and a simple script in GScript to change values that won't survive reboot or in init.d to be applied on boot,you can find the optimal voltages for your CPU(Don't forget,every CPU is unique and different),thus reducing heat and maximizing battery life.
If a dev brings that to the SGS2 it will be a big step in the right direction as far as I'm concerned.
I use SetCPU without issue, but only to run profiles (i limit the device to 500mhz when the screen is off). The rest of the time it scales itself up to 1.4GHz without fuss and using stock voltage. Battery life is fine, best ive had for an android device.
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
I did set ondemand which is a little more reactive and slightly smoother.
Though System Tuner is less cpu-consuming and much more useful on the SGS2. No need for all those complicated settings from setCPU. Only changing governor and changing frequencies on standby are useful.
leedavis said:
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
Click to expand...
Click to collapse
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
I am using Check Rom with set CPU I have it 1.2ghz max and 200. Using conservative governer. I been off charge for 15hrs, however I am using light usage I am on 72% screen on has been 5h 25m at time of writing. Not yet calibrated the battery.
jonny68 said:
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
Click to expand...
Click to collapse
What are the settings are you using for the setcpu program in your S2?? Did you remove the Juice defender application?
I'm looking for a good baseline to see what works best on this phone.
list everything, screenshots prefer and please specify your rom, kernel, and theme.
Mine are as follows...
all info in my sig. I use 500-1400 conservative with a 500-500 power save profile set for when the screen is off.
My battery lasts between 28-42 hrs pending my usage level from high - low. YMMV.
Miui
200 to 1200
Conservative
Noop
Using no-frills
Same settings when using perception. Awesome battery life, almost two days.
Sent from my SGH-I777 using Tapatalk
CM7
200-1400 On demand
nothing else changed in setcpu
using red drop them for theme changer
CM7 launcher (ADW)
Widgetlocker for lockscreen theme
So, I'm heavily themed, but not much in widgets.
Seems good on battery, can last ~14 hours with moderate to high use.
Stable as well, no major crashes other than the usual browser and market.
I use Voltage Control myself and I've UV'd all across the board by -50. I've also dropped max speed to 1000Mhz. The rest should be pretty self explanatory...
Oh and I can't really list battery life because my usage really varies day to day, by quite a bit. I will say that I definitely get through an entire day with very high usage with no problems at all. Much... MUCH better than when I was running stock.
Default voltages and frequencies, ondemand, ignore nice load
llescaflownell said:
CM7
200-1400 On demand
nothing else changed in setcpu
using red drop them for theme changer
CM7 launcher (ADW)
Widgetlocker for lockscreen theme
So, I'm heavily themed, but not much in widgets.
Seems good on battery, can last ~14 hours with moderate to high use.
Stable as well, no major crashes other than the usual browser and market.
Click to expand...
Click to collapse
Do you notice any difference at all in performance? How much display time do you get?
Cansomeone tell me the stock voltages I think mine are messed up
Sent from my SAMSUNG-SGH-I777 using xda premium
roadrash7 said:
Cansomeone tell me the stock voltages I think mine are messed up
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Add 50 to each of the ones in my picture posted in the reply up above.
Simba501 said:
Default voltages and frequencies, ondemand, ignore nice load
Do you notice any difference at all in performance? How much display time do you get?
Click to expand...
Click to collapse
Day to day performance, there really is no difference than stock, but to compare quadrant, I got ~3300 stock, but at this OC I get ~4400. It's gonna be smooth as butter either way, I just like numbers
Display time, I'm not too sure, but my settings are at its 1/3 highest (so not too bright, but not too dim either for me). If I were to approximate, I would say a good 2 hours of the display being on, give or take an hour or too (not the best estimate, but Ill try and keep track next time and report back).
Rooted stock
No themes
I get a good 14 to 18 hrs (minimal usage during the day and heavier usage evenings/nights - lots of wifi or data intensive apps)
Kadin said:
Add 50 to each of the ones in my picture posted in the reply up above.
Click to expand...
Click to collapse
thanks but it looks like that is not stock settings, turns out if you click revert in setcpu it tells you how to get back to stock. they are...
1200-1275
1000-1175
800- 1075
500 - 975
200 - 950
my new settings are...
1200-1175
1000-1100
800 - 1000
500 - 925
200 - 850
all is well so far. stress test with no probs.
Here's my settings
Main Profile: 200Mhz Min 1Ghz Max running conservative governor. During the day. Conservative is performing better than ondemand for me.
I've also been toying with the up and down thresholds on the conservative governor to find a difference. Haven't really experienced any lag unless I set the up threshold to 90 or over.
Screen Off: 200 Min 500 Max also conservative
Charging: 200 Min 1400 Max ondemand
Battery <25% 200Min 800Max conservative
I've been finding the phone is just as good running at 800mhz max on the main profile. It's amazing how much faster this thing is then my captivate.
As far as voltages
1600: 1450
1400: 1325
1200: 1225
1000: 1100
800: 1000
500: 900
200: 825
Been getting amazing battery life. Been on battery for 10 hours now. Still 65% battery. Not bad.
My phone absolutely blows for overclocking. anytime i try the settings posted here it locks up
Also using No Frills here. Settings are:
Max: 1200
Min: 200
Conservative and Noop
I unplug it at 7am and by the time I get off of work at 5:30ish I still have 60%+ of my battery left. Running MIUI with quite a few widgets and I leave wifi on all the time.
roadrash7 said:
thanks but it looks like that is not stock settings, turns out if you click revert in setcpu it tells you how to get back to stock. they are...
1200-1275
1000-1175
800- 1075
500 - 975
200 - 950
my new settings are...
1200-1175
1000-1100
800 - 1000
500 - 925
200 - 850
all is well so far. stress test with no probs.
Click to expand...
Click to collapse
Thanks for this!
DJSLINKARD said:
My phone absolutely blows for overclocking. anytime i try the settings posted here it locks up
Click to expand...
Click to collapse
Might have to Overvolt. I had to overvolt 1400Mhz by 25mv in order to get it stable.
Also I've noticed lately when it's not happy with the setCPU settings I'm using the phone seems to emit a high pitched frequency when you put your ear to the back cover. When I get stable it appears to stop.
roadrash7 said:
thanks but it looks like that is not stock settings, turns out if you click revert in setcpu it tells you how to get back to stock. they are...
1200-1275
1000-1175
800- 1075
500 - 975
200 - 950
my new settings are...
1200-1175
1000-1100
800 - 1000
500 - 925
200 - 850
all is well so far. stress test with no probs.
Click to expand...
Click to collapse
Not sure what to tell ya. I just installed SetCPU and this is the default settings showing - the same as Voltage Control and what I was referring to. I deleted the boot and profile settings first from Voltage Control and then rebooted, then installed SetCPU.
The only thing I can think of is that since I'm running UnNamed with Entropy's daily driver, maybe the voltage was tweaked from him? I'm only assuming because reading through his thread doesn't seem to indicate that he upped the default voltage on all levels. Unless I missed it somewhere.
This is in Entropy's Daily Driver thread - http://forum.xda-developers.com/showpost.php?p=18433190&postcount=213
Kadin said:
Not sure what to tell ya. I just installed SetCPU and this is the default settings showing - the same as Voltage Control and what I was referring to. I deleted the boot and profile settings first from Voltage Control and then rebooted, then installed SetCPU.
The only thing I can think of is that since I'm running UnNamed with Entropy's daily driver, maybe the voltage was tweaked from him? I'm only assuming because reading through his thread doesn't seem to indicate that he upped the default voltage on all levels. Unless I missed it somewhere.
This is in Entropy's Daily Driver thread - http://forum.xda-developers.com/showpost.php?p=18433190&postcount=213
Click to expand...
Click to collapse
Thanks for the clarification
I'm still trying to find settings that give the most performance and give the best battery life
bump...
No one cares to share?
Stock voltages and frequencies - on demand
Charging - stock frequencies - on demand
screen off - 200-500 conservative
I've install Rom Toolbox,
and i saw there is a "CPU slider" where i control the clock speed.
i've put it to 1000MHz instead of 1200MHz and tested it for several days
i really dont feel any difference in performance.
browsing seems same, games like asphalt is equally smooth.
heating is similar, equally warm.
the only difference is quadrant benchmark.
1200MHz scores 3200-3400
1000MHz scores 2600-2900
frankly speaking, i'm not sure if there's any difference in battery life.
is there any way to accurately test whether the clock speed affects the battery life?
i've seen other threads, where there are very different opinions.
some say it will improve battery life, and some say its worst.
http://forum.xda-developers.com/showthread.php?t=726019
Quote: (SetCPU doesn't make a difference in battery life, it can only shorten it. The kernal already has the best settings for CPU speed built in.)
http://forum.xda-developers.com/showthread.php?t=1305465
Quote: (if you are able to stand the side effects of underclocking, it will surely boost your batery life.)
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it). If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
slig said:
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it).
If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
Click to expand...
Click to collapse
HI, thanks for replying. I understand what you mean. the phone dont operate at 1200MHz all the time. but when using browser, and playing games, such as asphalt, it runs at max CPU usage almost the entire gaming duration.
Anyway.....
the real question is whether the clock speed is directly proportional to the battery consumption.
while reading your post, i thought of a brilliant ideal how to verify this.
the CPU slider not only allows you to set the max CPU speed,
you can set the min CPU speed as well.
So, i thought of an experiment, lets set the min & max CPU to 1200MHz,
this way, the phone will be running constantly at max CPU even when its idle.
let the phone be turn on till it run out of battery, record the time, T1.
then repeat again with max and min CPU set to 1000MHz.
record the time it is turn on till it run out of battery, record time as T2,
then compare T1 & T2, this could certainly work.
it would be nice if any member here happens to have 2 sgs2, and tried them ;-)
There are two more things to consider
1. CPU is not the only element that consumes power.
2. SGS2's Exynos is always clocked at 200MHz when the screen is off - check if this minimum slider affects that too.
Please let know how your experiment goes.
Regards
when the screen is off, the phone will be in "deep sleep" state. i think thats less than 200MHz.
anyway, i wont be doin this experiment any time soon.
you see, this is my only phone, i need to use it.
i dont have much oportunity to leave it and wait for it to run out of juice.
still, i'll try it when i have the chance.
First of all, I am totally new to this forum.(I mean as an registered user)
Before that I always had the thing from the forum what I needed.
Now here is my question,
If i overclock the processor speed of my android device to a higher position, isn't it gonna take more battery power than usual?
Phone model: Xperia Live With Walkman
Boot loader: unlocked
Root Access: Rooted
Kernel: Rage 3.2
ROM: Real ICS r6
overclocking is going to drain your battery obviously.
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
saqib nazm said:
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
Click to expand...
Click to collapse
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Saimoon said:
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Click to expand...
Click to collapse
Power consumption = Voltage x Voltage x cpufreq x some constant for your device. If you OC (raise the cpufreq) you will have more power consumption and more heat generation because most of the power is dissipated as heat and the heat is what damages your cpu. It is probably impossible to kill your cpu in one go, because your device should shut off when it begins to over heat (this will look like a random reboot). But you will slowly degrade the over all performance of your cpu and eventually you get to a point where you see a lot of random reboots. So if you decide to OC you probably want to also undervolt as well. This is because power consumption (and heat) scale with the square of the applied voltage. One rule of thumb is that your maximum cpufreq is actually determined by the voltage. For example, my cpu is rated to be stable at 1 GHZ and 1200 mV, so when I OC and UV, I scale the cpufreq as high as I can go, as long as the voltage is not greater than 1200 mV, for me this is 1.5 GHz.
Also remember that your cpu governor will have a big effect on your power consumption and it is probably doing a good job keeping the cpu running in the low range of the cpufreq table, so you are unlikely to see big effects of OC or UV on real life battery consumption.
every chipset is different, even though the brand and model is the same. noone can guarantee you any safe value to overclock.
Thanks Giving!
Thanks Everybody for helping me out!
I am applying 1.402 GHz :laugh:
Overclocking is not the only thing you have to think of in order to improve your phone's overall performance. The most important issue for me is choosing the right kernel and applying the right governor + I/O scheduler. From my experience with Mini (i have tried ALL available kernels and most of ROMs) I can surely say that now with my phone (ICS .587, custom ROM + kernel) overclocked to 1.5 GHz battery with minimal use (20 mins calls, 40 mins WiFi per day) lasts at least 60 hours. When I bought my phone (GB, no OC, all stock) battery was struggling to stay alive for 24 hours with the same minimal use. Conclusion: first pick the right kernel and ROM, then OC.