Related
Hey Guys,
Thought I Would share for any interested...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Added a setting for charging that is 100/1400 conservative with a priority above everything except the heat one. so like 91 heat and 89 charging.
Seems stable, zippy and doesn't kill the battery too fast. All good.
Nobleskill
UPDATE: the settings above worked a treat for me on froyo but after updating to gingerbread I found it was back to the old drawing board time. For whatever reason, and being fair to Samsung and gingerbread by saying that the tab is now older and been used and abused its whole life, I wasn't able to apply the same level of undervolting without lockups and rebooted.
Why? Well could be a few reasons, the one mentioned above I really think plays a part in it. I also think though that gb is just different. Obvious I know but I mean its different at a base operating level. It needs new bootloaders and as alot of the experienced developers currently doing the tab gb stuff I think are finding its got a few curveballs its very happy to throw into the mix. The other point is that the control app has been updated dramatically with new ui and a more polished look to the outside which I think also follows into the coding. Xan, the developer must be a very talented individual and is pioneering the CPU control at kernel level IMO and really deserves our support. You can get the fee apk but I think its worth a donation just for the free version.
I notice the newer kernels are also having preset UV settings which is awesome. Gives you a base to build on and as each tab is different, yours may not go as low in volts as little Johnny's tab but it may go further than big Bob's one, it provides a good starting point. Or whatever..
Jump on over here: http://forum.xda-developers.com/showthread.php?t=943669
This guy is my favourite developer evar! Very friendly, very talented and shares <3. Read this thread as much as you can, its brilliant and has a few gems hidden in the posts. Also the kernel's are basically on the cutting edge. Its this guys patches that find their way to other, and all I'm pretty sure, kernels and roms.
thanks a lot buddy ! I was really looking for this !!!!!! you're my hero !!!!
Your most welcome mate. Any issues make sure and let me know through this thread.
Nobleskill
Ps. Watch how big a difference it makes to battery drain with screen off and below 30. I keep thinking it will die before I get a charger and like 4 hours later its only gone down by about 10 percent.
As always, support the Dev's if your able to. They richly deserve it and it doesn't have to be much to make a difference. )
nobleskill said:
Your most welcome mate. Any issues make sure and let me know through this thread.
Nobleskill
Ps. Watch how big a difference it makes to battery drain with screen off and below 30. I keep thinking it will die before I get a charger and like 4 hours later its only gone down by about 10 percent.
As always, support the Dev's if your able to. They richly deserve it and it doesn't have to be much to make a difference. )
Click to expand...
Click to collapse
there is a problem regarding those settings. did you try to restart the Tab after? mine doesn't start at all ! I should try several times to keep pressing the power button and then, after few minutes it starts again. after uninstalling the Set CPU and Voltage Control, everything comes to normal.....any advice?
SetCPU seems to be very crashy on the SGT. You might want to try not decreasing the voltages quite as much, some CPUs can't cope with it. I've got mine set even lower and I'm fine.
The "performance" governor locks the speed at the "max" value, the "powersave" one locks it at the "min" value. It's a pity that the "Ondemand" and "Interactive" governors seem to be so unstable as either would be better for performance than "Conservative".
I've also got another profile for "Charging" which ramps everything up a bit.
One thing I have noticed after spending some time in here is that all SGT's are not created equal!! I have no issues with the settings above, none at all. It boots fine, runs super fast with 2200 being the average score in quad. And I am on my second day without charging... its been lighter usage but still....
I guess I got lucky but all I can say is trial and error, or search for a simillar problem with another user and ask what settings if any worked for them. My thinking is that there would be batches that will run one way and others that won't.
nobleskill said:
One thing I have noticed after spending some time in here is that all SGT's are not created equal!! I have no issues with the settings above, none at all. It boots fine, runs super fast with 2200 being the average score in quad. And I am on my second day without charging... its been lighter usage but still....
I guess I got lucky but all I can say is trial and error, or search for a simillar problem with another user and ask what settings if any worked for them. My thinking is that there would be batches that will run one way and others that won't.
Click to expand...
Click to collapse
Its the CPU. They all have different tolerances on the minimum they can run at. Samsung just uses a voltage that guarantees all of them will work at. I've decreased everything 800mhz and up to -200mv. So far so good.
ovigt71 said:
there is a problem regarding those settings. did you try to restart the Tab after? mine doesn't start at all ! I should try several times to keep pressing the power button and then, after few minutes it starts again. after uninstalling the Set CPU and Voltage Control, everything comes to normal.....any advice?
Click to expand...
Click to collapse
Try install jus UV & set the limit to 1400ghz. Run it for a day or two.
I have problem with SetCPU, give up on it. So now i only have UV installed.
thanks for the settings, no problems since 1 day
Sorry for stupid question, Am I need to flash kernel for 1400ghz? Or just use SetCPU with overcome 1.0 karnel?
Since there are some karnel said they are for 1.4ghz so I am confusing on it, tks!
izamoscar said:
Sorry for stupid question, Am I need to flash kernel for 1400ghz? Or just use SetCPU with overcome 1.0 karnel?
Since there are some karnel said they are for 1.4ghz so I am confusing on it, tks!
Click to expand...
Click to collapse
If the kernel does not support >1ghz, then setcpu cannot set the speed to anything higher.
The overcome kernel supports an overlock of 1.2 and 1.4Ghz.
Overcome Kernel 1.0 is an overclock kernel. Just install setcpu to oc
nobleskill said:
Hey Guys,
Thought I Would share for any interested...
Seems stable, zippy and doesn't kill the battery too fast. All good.
Nobleskill
Click to expand...
Click to collapse
with the settings above do you have it set up as "Save as boot settings"? i had set mine at bfq and limit clock to 1200mhz and not changing anything else saving it as boot but when i went to restart the tab it got stuck on the Galaxy Tab screen, i had to re-store my backup in order for the tab to re-start.
also how did you get the 600mhz:?-100=?mv?
i am using richardtrip's [Kernel] [EURO] [1.4ghz OC/UV] MCR EXT4 compatible/Voodoo Sound V15 22/02 hope that helps with what i am asking.
I gave up on Set Cpu and switched to Cpu Tuner, a choise I don't regret at all.
Sent from my GT-P1000 using Tapatalk
Recently changed to overcome kernel 2.0 and have changed to bfq. All stiull running smoothly.
And yeah i have mine all set to set at boot.
Thanks! Was looking for this.
I copied your settings to the last detail (bfq scheduler) and my Tab is crashing.
Now I am trying with lower UV.
braby said:
I copied your settings to the last detail (bfq scheduler) and my Tab is crashing.
Now I am trying with lower UV.
Click to expand...
Click to collapse
Sorry buddy its been ages I should probably update this. I find that overcome has gottan alot better I still use the same undervolting but no profiles on set CPU. Just set to 100 min and1400 Max ondemand. I can use bfq and have no issues but one thing I know for sure, and I think it was even stated in this thread, no 2 of these are the same... same deal with more strain on the CPU than others so if my settings didn't work for you I'm sorry for that but all I can suggest is what I did to find the right setting... experiment, trial and error...
Best of luck,
Nobleskill
I found out what I did wrong...on Screen Off profile I didn't set "Performance" scaling, instead I did "Conservative"...the Tab was only crashing when screen was off!
Now that I switched it to performance it works just fine...
Using Overcome 1.4.2...
What's has better battery life, now that you have experience with both, with the profiles mentioned above or "On Demand" with no profiles?
That's a tough one as I use my tab a whole heap more and for many more things. I have 3 times as Widgets and so on... put it this way I used to get 2 days with low to moderate use on the setting in this thread, now with extremely heavy usage, I'm talking 8 hours or more almost straight with web browsing, ebooks, video, music, news ect...
I like my new set up cause its alot easier to configure and I find the most important aspect to battery life is the undervolting... overcrowded seems to handle the just fine. The only other thing I really swear by is an app like juice defender or battery boost.. set them up and its turning things off when not used which can be massive...
Hope this has helped and I'm happy to hear you sorted the crash issue.
Nobleskill
This is a message from a developer who is in a team who develops a kernel with a very large overclock. Do not take this is an idiot babbling, read this and take it to heart as this is very important.
I want to talk to you about overclocking our phone and how dangerous it can actually be. I love overclocking, and have overclocked my main computer, and I overclock my phone, but my overclock (as you can see from my signature) is very mild. A simple 800MHz overclock.
When we first got overclocking on our phone (thanks to Fugumod), we were around 800MHzish and it gave a nice boost. It got up to 1GHz and it gave another good boost. Over time, we have discovered the phone works at high speeds, now 1366 in Fugumod, and 1400 in G3MOD. Now if you look at these speeds and compare it to the original clock speed on our phone (667MHz, or you can look at the Spica which has the same CPU but with a larger transistor process: 800MHz), this is a 204% overclock on Fugumod and 209% on G3MOD.
Now let's put these percentages into perspective: on your desktop computer, a 200% overclock is normally only possible with serious cooling: water or liquid nitrogen, and we are attempting to do this in a PHONE with NO cooling, and NO ventilation. Furrthermore, it is kept in our pockets beside our thigh muscle: the largest muscle in our body and it emits a large amount of heat. These are not ideal conditions for a CPU to be kept in, especially when it is in a fragile state such as overclocking. We are lucky however because phones have clock governors which clock it back when it is idling to conserve power.
When you overclock the CPU, you must also overvolt it to keep the system stable while overclocked. However the downside is that if you overvolt your CPU, you will use more power, and also reduce the lifespan of our CPU. Let me show you how much more power is required to run the phone at 1.4GHz.
Now, as we don't know the exact power consumption of our CPU, I will assume the power consumption is 100mW. In overclocking a desktop computer, we use this algorithm:
Code:
OC Wattage = TDP * ( OC MHz / Stock MHz) * ( OC Vcore / Stock Vcore )^2
So that means 100 * (1400 / 667) * (1525 / 1200) ^ 2 = 338mW. That is over 3 times the power consumption of the CPU at stock speeds. That also in turn effects the lifespan of the CPU as the transistors are both having to work twice as hard (as the CPU clock is twice as high) and are drawing three times the power consumption, this means the CPU will last 6 times less at 1400MHz.
When we were starting out with overclocking our phones, we didn't have a lot of the nice new features we have discovered that boost performance but now that we do, these huge overclocks just aren't as necessary anymore.
TL;DR
Guys, our phone can go at 1.4GHz or 1.36GHz, yes. But is it a good idea to keep it at those sorts of speeds? No. The reason marcellusbe and the G3MOD team provide such HUGE overclocks are for rare occasions. When the phone is just doing nothing, we expect you to put it back to 667/800MHz, but when you are wanting to play Angry Birds or emulate Castlevania 4 or something, you put it up to 1400MHz, but put it back again once you are done. 24/7 usage at 1400MHz or 1366MHz is DESTROYING your CPU and your battery.
USE OVERCLOCKING WITH EXTREME CAUTION
Extra Information
Here is a graph to show the power consumption increase from running the CPU at higher overclocks and also the reduction from undervolting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Even an i7 is rarely oced to 200% - its too much and can be dangerous
cdesai said:
Even an i7 is rarely oced to 200% - its too much and can be dangerous
Click to expand...
Click to collapse
Precisely my point.
Nice one mate...
Maybe when you get time just include UnderVolt also...People are waiting for some stuff to come up for that also...
dharamg3 said:
Nice one mate...
Maybe when you get time just include UnderVolt also...People are waiting for some stuff to come up for that also...
Click to expand...
Click to collapse
+1 For that too
Nice information. I always used to keep my phone to 1200 mhz. Damn should reduce it now
Thanks, excellent info.
Sent from my GT-I9000 using Tapatalk
I never try to go beyond 800Mhz
I think it is sufficient for daily use
(More than sufficient)
exactly.... i was going to post somthing like this
when u need that boost (like for ps1 emulator or hd games) us upto 1.3ghz
but otherwise just leave it at 800-900mhz...
u dont need crazy oc all the time!
Doesn't SetCPU (or any other app for that purpouse) do exactly that? If you set scaling and min/max freq. accordingly? What is the difference beetween that and setting in manually?
Gud info mate......
Governer should be Ondemand right ????
Hm, a guy called Kyrillos told me, that normal voltage at 667MHz is 1200mV. So, in newest g3mod, from 500MHz on, its higher, at 800MHz its already 0,1 volt above max in stock.
So how dangerous is it to let it allday at [email protected] ?
DaBigFreak said:
a guy called Kyrillos told me,
Click to expand...
Click to collapse
He s a recognized developer. A very good one infact. He was right by the way. Its only the faulty reading.
---------- Post added at 01:32 PM ---------- Previous post was at 12:54 PM ----------
Hillbeast excellent, excellent info. That s the precise reason I don t use high overclocked kernels. Maximum I goto is 800MHz.
raja4sure said:
Gud info mate......
Governer should be Ondemand right ????
Click to expand...
Click to collapse
Yes. I use it mostly. Other devs and experienced users here as well for what i've noticed. Or conservative which saves battery because it scales freq more gradually. http://www.setcpu.com/ - http://www.setcpu.com/#7
And profiles, especially the Temp and screen off. Prevents from overheating and exscessive battery discharge, respecitvelly.
DaBigFreak said:
So how dangerous is it to let it allday at [email protected] ?
Click to expand...
Click to collapse
Probably very. But overclocking in general shortens life span of electronic components, primarily because of increased heating. If that worries someone that it is probably best not to overclock at all.
I personally see no difference between manipulating cpu freq manually or by using some app to do it when necessary. If I'm wrong then please feel free to elaborate.
dharamg3 said:
Nice one mate...
Maybe when you get time just include UnderVolt also...People are waiting for some stuff to come up for that also...
Click to expand...
Click to collapse
I will update this thread and I hope it will actually get stickied as it's quite important information in my opinion and it could save some peoples phones.
mrvek said:
Doesn't SetCPU (or any other app for that purpouse) do exactly that? If you set scaling and min/max freq. accordingly? What is the difference beetween that and setting in manually?
Click to expand...
Click to collapse
SetCPU will obviously set the max and min settings, but in an ideal situation you will want to have a mild overclock (or none at all) if you are just using for phone for normal functions such as TXTing or browsing or something like that, but SetCPU can't detect when you are wanting a more intense operation such as a game, so you're best to adjust it when you are needing it and switch it back.
I keep a SetCPU widget on my home screen to do that.
DaBigFreak said:
Hm, a guy called Kyrillos told me, that normal voltage at 667MHz is 1200mV. So, in newest g3mod, from 500MHz on, its higher, at 800MHz its already 0,1 volt above max in stock.
So how dangerous is it to let it allday at [email protected] ?
Click to expand...
Click to collapse
The stock voltages for our phone at 667 is 1200mV, yes. At 1300mV you will notice a mild increase in consumption.
If we follow the same algorithm in the OP:
Code:
OC Wattage = TDP * ( OC MHz / Stock MHz) * ( OC Vcore / Stock Vcore )^2
We get (again, assuming the standard consumption is 100mA) 100 * (800 / 667) * (1300 / 1200) = 140mA. Yes, it's higher but not too much higher. If you UV it by 50mV @ 800MHz you'll go to 130 and at 1200mV it'll be 118mA.
Overclocks like this are still not 100% safe, but they are nowhere near as dangerous as a 300% power consumption increase.
This is the Information I was looking for past 2-3 weeks. Finally you posted it here.
Thanks hillbeast
Hey man. I really appreciate your effort to inform. I just would like to add something.
Overclock: in modern cpus power consumption increases almost linearly with clock. Let us say linearly to be safe. It means double clock double power (and so heat)
Voltage: when you increase the voltage the power increases approx quadratically (double voltage for times power). But also higher voltage means stronger signals in transistors and so higher stability.
Heating and lifetime: the heat decreases the lifetime of electronic components but not in a linear way. Please also note if a circuit does not die very soon (infantile mortality) it will last very long in normal conditions. So even if it was cut by half starting from the normal 10 years expected lifetime it would be anyway long for a phone.
So it is clear voltage is much more important than clock for power consumption. Decreasing the voltage you could have an overclocked cpu which consumes and hests up less than the stock one. Of course it is less likely to be stable.
Personal computer cpus needs cooling and are difficult to overclock because they become very unstable when overclocked so you have to increase voltage.
Finally to be clear I want to repeat your lesson.
DO NOT OVERCLOCK UNLESS YOU REALLY KNOW WHAT YOU ARE DOING. and don't complain with developers if your phone will break.
Sent from my GT-I5800 using XDA App
After reading this, I will never overclock more than 1GHz. Thanks
I agree extreme 200% overclocking is harmful to cpu and disagree with some of the points.
I don't think wattage and tdp formula are correct. If it is correct in reality battery should drain in 1/3rd of the stock time and should heat up immediately. we are just increasing the power supply in mv which is 1200 to 1500%. That means 25% power increase.
When the phone is in idle (no music, wifi, data ...) mode cpu/armcore is completely turned off. That means no frequency, no power supply and no heat. Other peripherals have separate clocks and they will keep running in idle mode. This is the difference between desktop and phone cpu.
frequency is 'no of times turning on and off transistors in a circuit per second'. In fact cpu's are designed to work at much more frequencies than stock. But stock frequency is decided by considering various operating conditions worldwide and $$. Personally i use 1020Mhz and phone operates like stock frequency.
I don't agree with one of the last statements:
hillbeast said:
So that means 100 * (1400 / 667) * (1525 / 1200) ^ 2 = 338mW. That is over 3 times the power consumption of the CPU at stock speeds. That also in turn effects the lifespan of the CPU as the transistors are both having to work twice as hard (as the CPU clock is twice as high) and are drawing three times the power consumption, this means the CPU will last 6 times less at 1400MHz.
Click to expand...
Click to collapse
Assuming you use setcpu, your phone spend most of the time in standby. if you use your phone a lot, it will be in standby 70% of the time.
Assuming that when your phone is not in standby the clock is automaticly set to 1400 (which is probably not, but we're doing worst case), your phone will be overclocked 30% of the time.
If your statement about battery drain is correct, the processor will use 160% more battery than usual. This, will not result in a huge battery drain, because actually, the processor is draining very little battery compared with things like display, wifi, 3g and so on.
If your statement about lifespan of the cpu is correct, the lifespan of the cpu is reduced to 75%. Considering that a cpu can last years and that you usually throw your phone away way before the cpu stops working, doesn't seem like a big deal to me.
That is true. Unless you run your phone 24/7 at max OC speed and phone heats up excessively there really should not be problems. That's why we have good apps and scaling governors that save the cpu and battery. In my case the phone spends most time at 400Mhz, then on 800, then 1400 then other freqs (based from setcpu report - info → time in state). Main profile beeing 400/1400, ondemand. And temp doesn't go over 31°C on daily use. What increases temp are mostly games but for that i use several setcpu profiles (in this point i disagree with hillbeast and the ability of setcpu to know my specific requirements. I know that it can't know what i need and when but if I set manually the requiered freq (max) to play a game the phone would heat up significatly (angry birds for about 30 mins gets me to 36°C - relatively high). And then i need profiles not to overheat the phone. And now when I already have profiles, why not let everything be automatic?).
Please don't get me wrong, I agree that OC-ing is quite risky and it should (must‼) be done with great caution and that is an implicit requirement.
It seems alot of people dont know the proper way to undervolt their phones, so I'm gonna try to help out! This is my first attempt at a guide, and i tend to ramble so just tell me if it makes no ****-for-sense
Undervolting is great, it allows us to change the voltage in our phones while we use it! this can really increase battery life and reduce heat in the phone. but if its not done right, it causes many more problems than it fixes.
When you are following this guide you WILL have issues! This is not a generic disclaimer, it is the TRUTH! the goal here is to find out where your phone stops working, and you cant do that without causing it to STOP WORKING.
once again: THIS WILL MAKE YOUR PHONE FREEZE, IT WILL HAVE AWFUL BATTERY LIFE, AND IT WILL MAKE BAD THINGS HAPPEN
But after its all done it should work much better
To start off, too much or too little voltage in the phone causes any number of things including:
Reboots (Screen Off and Screen On)
Lagging
Phone Overheating (Hot to the touch)
Reduced Battery Life (this includes the phone using more power, as well as reducing the battery's ability to hold a charge)
'Strange' issues with things shutting off/not working (WIFI, Bluetooth, your favorite app, ect...)
Many other 'weird' things
If you are having any of the above issues, and you are using a custom kernel, they may be caused by inproper undervolting.
THIS CAN BE THE CASE EVEN IF YOU HAVE NOT DONE ANY UNDERVOLTING YOURSELF!!!
Most custom kernels have undervolting build into them, and even 'stock voltage' versions allow overclocking, and those frequencies have no 'safe' voltage associated with them.
How to Properly Undervolt your Phone:
*this assumes you have no idea where to start, if you have some past experience, USE IT!!!*
First, Undervolting a phone the right way is not a quick job, like most things in life the more time you put into it the better your end result will be. For me i like to take an ENTIRE WEEK OR MORE to get all my settings down right. whenever you decide to do this, expect any and all of the issues i listed above to happen while you are trying to find the right settings.
Step 1: Starting Fresh
Disable all overclocking, undervolting, AND PROFILES on the ROM, you need to get the stock speeds working before you try to push the phone to its limit.
This will be your baseline. Use the phone like you normally do, text, call, surf the web, even let it sit in your pocket for a while. Do this for as long as you need to to be sure that everything is stable.
If you have any issues during this stage. STOP! add +25mv to every frequency across the board and start over. Do this up to 3 times if necessary, if after you have added +75mv to your stock voltage and you are still having issues, it is most likely something else in the rom causing the issue (rogue app, wrong kernel version, phone was dropped in the toilet too many times...) try to fix that first, or just try to ignore the issue, its up to you.
Otherwise, if everything is stable, Continue to step 2!
Step 2: Start Lowering Voltages
Lower all of the voltages by -25mv across the board. (If your phone needed any voltage added over stock to be stable, skip this step.)
This is where you begin testing the waters. Once again use the phone like normal, including some screen off time, as well as some CPU intensive tasks (playing music while websurfing, gaming, ect.)
If your phone is still stable after a good amount of time, then do it again. Your looking for the moment when things start to go wrong.
When you notice your first random reboot, or you start to feel the phone getting hot, or not responding STOP! you found the limit of your phone. Go back to the last working voltages you have and use them for step 3.
The more time you spend at this step the better your overall result will be! if you dont get any symptoms in an hour, they might show up later in the day, or overnight. Just take your time and have some patience.
Step 3: Lowering Voltages Independently
Now that you have a stable working phone. you can start lowering voltages one by one!
Starting with the lowest frequency, lower the voltage by -25mv.
Run this for a while, until you feel it is stable. Then move to the next highest voltage and do the same.
*If you have any issues, undo ONLY that frequency!!! Write down that frequency somewhere. you are done with it! you know that frequency is stable, and you shouldn't need to touch it again!!!
Keep doing this till you get to your stock maximum frequency, then continue to step 4!
*NOTE:* if any 2 voltages have more than a 100mv difference (125mv difference on Morfic's Kernels) between them, you need to raise the others around it to be equal or less than that. For exampe:
if at 1ghz, the phone is at 1000mv and at 1.2ghz the phone is at 1150mv. the higher one needs to be lowered (set 1.2ghz to 1125mv). if that is not stable for you then you must raise the lower one higher (set 1ghz to 1025mv).
Step 4: OVERCLOCKING!
At this point you should have a completely stable phone with no overclocking, grats! Now you get to start raising the frequency.
starting with the next highest frequency, set it to its stock voltage. if this is more than 100mv (125mv for Morfic's kernels) more than the previous frequency, set it to 100mv (125 for morfic) more than that.
run this until it is stable, and keep reducing it as much as you feel until you find instability. set it one step higher and move on to the next highest frequency.
if, after setting the voltage to 100mv (or 125mv) more than the last one, it is not stable, you need to raise the lower frequency's voltage up. sometimes this can cause a chain reaction that makes you raise 3, 4, or even all of the other frequencies up, if this happens you need to decide if that frequency is worth it to raise all the other frequencies to the next level.
If all is running good, proceed to step 5!
Step 5: The part where you hate me
(this step is optional, its just something i do to help with stability)
Now that you have a fully overclocked phone that is running as low of a frequency as it can safely, raise all of the voltages up by +25mv!
yes yes, i know, it sounds retarted to just undo that hard work and all that time you just put into finding the perfect voltages, but just hear me out.
Even if you spent a week on each step, did everything perfectly and tested everything you ever do on your phone and it is all completely stable. one day you are going to do something that will push the phone, which is running at its limit. so by adding 25mv to everything you are giving yourself some insurance. you may loose some battery life (i honestly don't ever notice a change with only 25mv) but when your phone alarm goes off in the morning to get you up for class, or you get that call you got that job you wanted, just be happy its not frozen on the table, or black screened in your pocket.
There you go! you should now have a stable phone with great battery life, and now you can stop bugging the devs about 'that strange reboot that is still there' or 'how every time you use his kernel you get black screens'
To Long; Didn't read Version:
If your having issues with your phone and you think its related to UV, and your much too busy/lazy/cool to read the above, try this: (Results will most likely be worse...)
Set (all of) your lowest voltages to 775mv (or 750 if you think your phone can do it)
Set your 1ghz voltage around 1000mv (give or take 50-100mv)
Set the highest speed to no more than 100mv below its stock seting.
Set the rest of all the speeds below 1ghz on a line between it and the lowest, and after 1ghz on a line between it and the highest. ex(From Morfic's T15 Kernel):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Post any questions or feedback you have, ill try to answer it as best i can!
Truly a great guide. I agree mostly with the last part, my alarm stopped ringing two days in a row, so I added 25 mv across the board, and it works perfectly. Thank you on behalf of the community, everyone will appreciate this guide for sure.
Helped fix an overheating problem!
Sent from my LG-P999 using XDA
This is done using setcpu?
Sent from my LG-P999 using XDA
imoumni said:
This is done using setcpu?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Any CPU managing app. I use CPU Master but there's lots more options out there. I don't use SetCPU because it took nearly a year to update.
Sent from my amazing LG G2x running Bionix Reloaded v1.4
Klathmon said:
*NOTE:* if any 2 voltages have more than a 100mv difference (125mv difference on Morfic's Kernels) between them, you need to raise the others around it to be equal or less than that. For exampe:
at 1ghz, the phone is at 1000mv if at 1.2ghz the phone is at 1200mv. the higher one needs to be lowered (set 1.2ghz to 1175mv). if that is not stable for you then you must raise the lower one higher (set 1ghz to 1025mv).
Click to expand...
Click to collapse
First off, thanks for this guide. I do rely on my phone's alarm clock pretty regularly so I'll have to start setting another alarm clock while I do this. Also, consider posting this in Android General to reach a larger audience.
My only question: I understand what you're saying, but I think your example may be incorrect. 1200mV - 1000mV = 200mV difference, so you would need to change one or the other by 75 to 100mV, right?
This is done using setcpu?
Click to expand...
Click to collapse
It can be done with any app that works with this phone.
I use an app called "System Tuner Pro" because it allows you to add voltage from stock settings (my phone seems to like a minimum voltage of 775 vs the 750 that most kernels start with) and im not sure any more but i think its free...
r4d14n7 said:
My only question: I understand what you're saying, but I think your example may be incorrect. 1200mV - 1000mV = 200mV difference, so you would need to change one or the other by 75 to 100mV, right?
Click to expand...
Click to collapse
thanks, yeah thats what i meant to say
All Fixed
Klathmon said:
It can be done with any app that works with this phone.
I use an app called "System Tuner Pro" because it allows you to add voltage from stock settings (my phone seems to like a minimum voltage of 775 vs the 750 that most kernels start with) and im not sure any more but i think its free...
thanks, yeah thats what i meant to say
All Fixed
Click to expand...
Click to collapse
No problemo. Looks like System Tuner is free but the Pro version is $3.99. How is it on resources? That's the only thing that worries me about these jack-of-all-trades apps.
r4d14n7 said:
No problemo. Looks like System Tuner is free but the Pro version is $3.99. How is it on resources? That's the only thing that worries me about these jack-of-all-trades apps.
Click to expand...
Click to collapse
it keeps a service running all the time, but is very CPU friendly, and wont hog resources. So far it hasn't been a problem for me at all.
and just for full disclosure; the dev is a close friend of mine, so i may be a bit biased
EDIT: added a quick "help im lazy" version for people that dont want to put the time/effort into doing it the right way.
Sent from my LG-P999 using Tapatalk
thanks for this
Thank you, this was very helpful!
Thanks for taking the time to make a great post.
I just started to OC/UV my G2X. I will use this as a guide.
-Thanks again
a noob question, Whats the difference between an app (eg, setcpu, pimpmycpu etc etc) lowering the voltage for you and "one doing it via your guide"
cricketAC said:
a noob question, Whats the difference between an app (eg, setcpu, pimpmycpu etc etc) lowering the voltage for you and "one doing it via your guide"
Click to expand...
Click to collapse
not really sure what you mean, to the best of my knowledge, no programs out there automatically undervolt for you. you use those programs to reduce or increase the voltage in each frequency yourself.
Hope that helps
Klathmon said:
not really sure what you mean, to the best of my knowledge, no programs out there automatically undervolt for you. you use those programs to reduce or increase the voltage in each frequency yourself.
Hope that helps
Click to expand...
Click to collapse
sorry, my bad. I just flash faux kernel. I thought all frequencies worked at the same voltages (silly me!) lol. Thatswhy when i saw there were different voltages for every frequency, i thought this guide was about that. (i.e i thought faux already did it for us in his kernel). lol
If my phone is stable at the current voltages that came with faux kernel, should i still try lowering them?
How much of a battery life can i get if i lower them by -25mv?
Lets say, i flash another kernel in the future and then reflash any oc/uv later on. Do i have to do these steps again or just simply input the (uv)values which i get after doing it right now?
cricketAC said:
sorry, my bad. I just flash faux kernel. I thought all frequencies worked at the same voltages (silly me!) lol. Thatswhy when i saw there were different voltages for every frequency, i thought this guide was about that. (i.e i thought faux already did it for us in his kernel). lol
If my phone is stable at the current voltages that came with faux kernel, should i still try lowering them?
How much of a battery life can i get if i lower them by -25mv?
Lets say, i flash another kernel in the future and then reflash any oc/uv later on. Do i have to do these steps again or just simply input the (uv)values which i get after doing it right now?
Click to expand...
Click to collapse
its up to you. personally, i would follow the "if its not broken, dont fix it" rule. if your happy with the current battery life, and you like the stability, no need to change it. But if you really want to go for broke, and squeeze every last bit of battery life out of this phone, then by all means go for it (you can ALWAYS undo it all) although -25mv most likely wont make much of a difference.
and to the second question, as long as its the same kernel, the same values should be alright, but each kernel is different. (i can get -50mv more on faux123's kernels, but i get better battery life on Morfic's even with the higher voltage)
Since we all have the same phone couldn't we all use the exact same voltages? and are the ones pictured yours?
noxary said:
Since we all have the same phone couldn't we all use the exact same voltages? and are the ones pictured yours?
Click to expand...
Click to collapse
Voltage depends on the chip (CPU) you have - every chip is different. you need to try playing with it according to what your chip can endure.
Klathmon said:
its up to you. personally, i would follow the "if its not broken, dont fix it" rule. if your happy with the current battery life, and you like the stability, no need to change it. But if you really want to go for broke, and squeeze every last bit of battery life out of this phone, then by all means go for it (you can ALWAYS undo it all) although -25mv most likely wont make much of a difference.
and to the second question, as long as its the same kernel, the same values should be alright, but each kernel is different. (i can get -50mv more on faux123's kernels, but i get better battery life on Morfic's even with the higher voltage)
Click to expand...
Click to collapse
If I end up squeezing every bit of juice, wouldn't that make my charger life short?
This guide needs a sticky!
Thank you for taking the time to write this.
Here's a response from a PM i recieved about my Antutu benchmark scores. This is meant to be a reference to others who are working to squeeze optimal performance out of their captivates.
Hi, want to know what setting you do to reach more than 4000 points on antutu bench xD i just cant go more than 3800
Regards
Click to expand...
Click to collapse
Overclock at your own risk!
I am not responsible to any damage to your phone
I've had lots of experience over clocking desktops computers, I started when I was 14 years old or something. I am very happy to share my experiences here with my captivate.
Here's what I've been using to test the stability and speed of each incremental change: https://play.google.com/store/apps/...chMark&feature=nav_result#?t=W251bGwsMSwyLDNd
It's Antutu Benchmark.
Some may not like Antutu, and that's understandable, it's just the standard i have used to compile my testing results. if you have a better app to use suggest it!
The highest Antutu score i was able to achieve was 4044 when i was on 1.508 ghz. running Devil .86
Recomendations/Results:
I've been testing mostly stock settings between devil .86 and semaphore 1.2.5sc and devil keeps coming out on top with it's scores. not trying to start a war, but devil is just faster. don't get me wrong i love semaphore.
I am using Slim ICS 4.1, it's been the most stable ROM for me so far, if somebody can post their results with a different ROM and kernels then i gladly support it!
Slim: http://forum.xda-developers.com/showthread.php?t=1517486
Tests between Semaphore 1.2.5.sc and Devil .86
I had both semaphore and Devil running live OC of 116% and after each test devil kept winning by about 50-80 points.
I recommend the Devil Kernel by DerTeufel1980, DerTeufel1980 is very helpful and supportive, he also turns out updates like a machine!
The devil kernel supports increasing frequency as well as live OC. It also has so many other cool features that make it fast(like GPU overclocking). This is why I recommend this kernel for Overclocking speed and stability.
His kernel is here: http://forum.xda-developers.com/showthread.php?t=1642460 Sometimes he posts a downloadable release in the middle of a page so you usually have to search for it.
Advice/Settings
Overclocking to high stable frequencies, and having the least apps active is the key to getting the highest overclocking scores with Antutu.
To get scores over 4000 I use this set up:
My settings, SIO, Conservative governor, Frequency at the 1300mhz step, live OC at 116%(this yielded 1.508ghz). I had UKSM on(whether on or off didn't seem to make a difference during my tests), i had the GPU overclocked to 250mhz. I was using the XL mem version (391mb ram).
I had intended on running more tests on the big mem version but the constant reboots got tiresome, if anybody wants to take this up I'll gladly support it.
Crashes: Crashes are inevitable when testing. sometimes you get lucky and only the app crashes, most of the time though you will get a frozen screen or a few seconds followed by a reboot. depending on your kernel some may reset your settings. Use NS tools and save a setting that you know is stable and save your test settings so you can start from where you left off.
Voltages: the key to stability!
BE VERY CAREFUL WHEN YOU ADJUST YOUR VOLTAGES! too much is harmful to your chip!! Heat and overvolting is harmful!
these are my voltages:
Arm voltages
1400mhz it's 1.475
1300mhz its 1.450
Int Voltages
1400mhz it's 1.25
1300 it's 1.225.
The rest is stock. If anybody has found stable underclocking for the lower frequencies please post them here.
Live OC:
Something strange i noticed was that whenever i would do a odd numbered live OC i would get major instability... 116% was much more stable than 115%. weird huh? also i am pretty much unable to get a stable live OC of more than 116 regardless of the frequency step. Each phone will have it's own stability limit for Live OC. Some phones can go all the way up to 130%, but that's rare.
the key is to keep finessing it and carefully and incrementally change things till you find a nice sweet stable spot, other phones can achieve more live OC.
My favorite Fast Stable Safe setting:
My phone is almost always on this setting for everyday use: SIO, Conservative, Freq OC at 1200 and Live OC at 116% yielding 1.392ghz. with a bit of voltage increase this has become my favorite setting, i always use this setup.
Some may balk at my use of the conservative governor, I Love it actually, CPU spy reports that the conservative governor barely ever uses the highest step for regular usage. Which is great because you don't need the highes step to be running all the time as most actions don't require it, the less high voltage you send to the chip the better. It also helps with battery life.
HEAT!!!!
Warnings about heat. voltage increases mean more latent heat. your phone is a closed system so the heat gets locked in easily... Warm is allright(not wonderful) any hotter than warm and you need to take steps to manage the heat. I've found two easy ways to deal with it, aside from putting it in my refrigerator lol
For stress testing I ussually have the battery cover off, one less thing to get hot.
One simple way to manage it when you feel the sd card slot warm is to press the SIM/Sd slot to your lips and blow air through the phone, this will help cool it down. another way to manage the heat is to do this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I borrowed a cooling fan from my gaming computer and set the phone up on it with the battery cover off. this really helped keep it cool.
Also, never leave your phone sitting in the sun on a hot day, I don't know why you would in the first place. But just don't.
Higher scores are achievable... just keep tweaking things.. I deleted all my user apps so nothing would run in the background and that did helps my scores a bit.
Also airplane mode prevents unwanted texts form interrupting testing. that way the phone can focus only on the task at hand
I bet wiping the SD card would improve read/write speeds incrementally...
If somebody wants to research this please post it here
Please read this before you post "results"
Please run at least 2 or 3 tests to sort of average the scores before you post about a result. This will help keep information clean of errors that can affect test results.
for example when i was doing a 1.392ghz test on Antutu, during the knights hacking thier swords scene a glitch happened and my frames per second shot up to 102 fps. It occurred for a few seconds but it was enough to offset the scores A LOT. I got a 4185 on 1.392ghz which doesn't seem possible. consequently I hold the #6 score listed for the captivate :laugh:
This is why I say get an average for the scores. with my 1.392ghz set up i tend to get scores ranging from low 3800's to high 3900's
Remember each phone is different!
Have fun tweaking!
Hope this helps!
Hi.
Thanks for sharing.
My undervolting values are:
100 Mhz = 800
200 Mhz = 850
400 Mhz = 950
800 Mhz = 1125
1000 Mhz = 1225
1200 Mhz = 1300
The attachment is a graph with my experiments to find a fast and stable configuration. The red line is my best so far.
BitteredBro said:
Hi.
Thanks for sharing.
My undervolting values are:
100 Mhz = 800
200 Mhz = 850
400 Mhz = 950
800 Mhz = 1125
1000 Mhz = 1225
1200 Mhz = 1300
The attachment is a graph with my experiments to find a fast and stable configuration. The red line is my best so far.
Click to expand...
Click to collapse
Excellent! i might have to try some of your undervolting! Did you do tests with a max voltage set to determine stability?
also what do you test it with?
What voltage you undervolt, arm or init
Sent from my SGH-I897 using xda app-developers app
melvinaury said:
What voltage you undervolt, arm or init
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
My guess is that it's the ARM voltages, idk though.
My phone doesn't like speeds over 1.4 nor live OC over 20%. Those are my max settings without freezes or reboots.
For stability testing I use nbajam and blood and glory. Those games are very sensitive to changes in voltage and overclocking.
Sent from my SGH-I897 using xda premium
melvinaury said:
What voltage you undervolt, arm or init
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Those are arm voltages.
I don't feel comfortable messing with Int voltages.
Anybody able to get a stable 1.6? I can't seem to get it stable...
Sent from my SGH-I897 using xda app-developers app
I think Icepack might work better!
bravomail said:
I think Icepack might work better!
Click to expand...
Click to collapse
Hahaha! Good idea!
Sent from my SGH-I897 using xda app-developers app
baconatorXVI said:
My favorite Fast Stable Safe setting:
My phone is almost always on this setting for everyday use: SIO, Conservative, Freq OC at 1200 and Live OC at 116% yielding 1.392ghz. with a bit of voltage increase this has become my favorite setting, i always use this setup.
Some may balk at my use of the conservative governor, I Love it actually, CPU spy reports that the conservative governor barely ever uses the highest step for regular usage. Which is great because you don't need the highes step to be running all the time as most actions don't require it, the less high voltage you send to the chip the better. It also helps with battery life.
Click to expand...
Click to collapse
Great info, thanks. I had my phone running 1.5ghz (directly, no Live OC) all day long on Glitch kernel a while back... before I started flashing Devil. Right now on Devil I am trying out underclocking while using live OC, so I have the frequency set to 800 with a 110% Live OC so the CPU is at 880mhz. SmartassV2 and SIO. It is very responsive and I should try a higher Live OC I think.
I had trouble using the GPU OC feature... have you been using that at all? I think I remember someone mentioning they had GPU OC plus a Live OC on top of that... I would think that would be harmful to the GPU, right? I set the GPU back to 200mhz since I was getting more and more frequent FCs, freezes and reboots. Thanks for your posts and sharing your results.
They Drew First Blood said:
Great info, thanks. I had my phone running 1.5ghz (directly, no Live OC) all day long on Glitch kernel a while back... before I started flashing Devil. Right now on Devil I am trying out underclocking while using live OC, so I have the frequency set to 800 with a 110% Live OC so the CPU is at 880mhz. SmartassV2 and SIO. It is very responsive and I should try a higher Live OC I think.
I had trouble using the GPU OC feature... have you been using that at all? I think I remember someone mentioning they had GPU OC plus a Live OC on top of that... I would think that would be harmful to the GPU, right? I set the GPU back to 200mhz since I was getting more and more frequent FCs, freezes and reboots. Thanks for your posts and sharing your results.
Click to expand...
Click to collapse
No problem, your post on the devil kernel thread helped convince me to switch to SmartassV2. I'll probably bring a condensed version here for whoever else stumbles here.
I've only had one troubling experience with gpu overclock on. I was going for a high antutu score running something like 1.5ghz. Anyways, for whatever reason during one stage of the test, can't remember which, i got a strange green flashy line across the screen. it was very unsettling cause i thought it was a hardware issue that i would have to live with. it stayed there even though i stopped the test. turning the screen on and off didn't fix it either. thankfully rebooting fixed the issue.
The only other time i've seen visual artifacts like that is when I would overclock my graphics card on my desktop. so i assume it was a graphical processing error.
I can't say for sure if gpu overclocking AND live OC together cause problems. although I wouldn't be too disappointed if my cappy died, then i'd unfortunately have to upgrade to the Galaxy SIII
Dumb question, but how have you two over clocked the gpu? Is it possible to underclock while having the CPU overclocked? For my phone, the gpu always locks before the ram/proc. I can tell because the screen gets all fuzzy with lines which makes me reboot.
Sent from my SGH-I897 using Tapatalk 2
goob1284 said:
Dumb question, but how have you two over clocked the gpu? Is it possible to underclock while having the CPU overclocked? For my phone, the gpu always locks before the ram/proc. I can tell because the screen gets all fuzzy with lines which makes me reboot.
Sent from my SGH-I897 using Tapatalk 2
Click to expand...
Click to collapse
Well we are able to overclock our GPU's because the devil .79 and on kernel allows the choice between either 200mhz(stock) or 250mhz.
to underclock the gpu you would need to talk to a kernel maker.
Maybe you need to increase your voltages... don't increase them too much though. I'm not totally familiar with the architecture and design of each processing bit inside the captivate but from my knowledge of computers, more voltage makes it more stable.
this question should be asked to a kernel maker! i hope you find your solution.
are you past warranty? you're positive it's not a rom issue? did this happen while it was stock?
baconatorXVI said:
Well we are able to overclock our GPU's because the devil .79 and on kernel allows the choice between either 200mhz(stock) or 250mhz.
to underclock the gpu you would need to talk to a kernel maker.
Maybe you need to increase your voltages... don't increase them too much though. I'm not totally familiar with the architecture and design of each processing bit inside the captivate but from my knowledge of computers, more voltage makes it more stable.
this question should be asked to a kernel maker! i hope you find your solution.
are you past warranty? you're positive it's not a rom issue? did this happen while it was stock?
Click to expand...
Click to collapse
Overclocking GPU is an option, but it is disable as well as the 56/60 Hz switch.
Hey guys, I'm new to this forum but not Android Central. Anyways, I just recently switched to jelly beans build 14 w/lean kernel. For some reason my battery life is just terrible. I'm just barely making it through an 8 hour workday, and that's not even using it that much. I was wondering if you guys had any tips for good battery life on this ROM/Kernel combo. I do have set cpu installed and running but I'm only Overclocked to 1.6 and undervolting by 50 mv. I also have a save battery life profile that drops it down to 1026 when the screen is off, it's charging, or battery is below 40%. Can you guys give me advice on settings to use to save battery life? I really like this ROM and kernel but I'm getting such terrible battery life. I think it's probably more user error than anything but maybe you guys could provide some tips.
Thanks in advance.
Nick
sent from my Galaxy S3 on beans 14 via tapatalk 2
How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
http://rootzwiki.com/topic/31329-ke...nimalistic-kernel/page__st__1410#entry1042976
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!
nicholi2789 said:
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!
Click to expand...
Click to collapse
I actually have my voltages set to exactly what Imoseyon has listed for the nominal cpu. As far as my screen off, I honestly just picked a low number and since I don't see lag I keep it there haha in addition, I use interactive governor which scales up the cpu once the screen comes on so it balances out either way.
To check which cpu type you have, do this. Details on what the cpu differences are included in the link as well. Matching your cpu type and adjusting your voltages may help extend your battery life but some say it is marginal.
No, your radio actually stays the same unless you manually flash a different one. I should also ask, what else do you have enabled? For example, in Maps/Settings, do you have everything disabled except "Enable Location History"?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2
nicholi2789 said:
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2
Click to expand...
Click to collapse
Well it's under Location Settings but if you have Maps frozen until needed then it's an unnecessary step. You have done even more than I do or suggest haha I haven't frozen anything.
What would you say you're seeing as your average screen on time?
Sent from my SCH-I535 using xda app-developers app
Oh average screen on time is probably around 2.5 to 3 hours or so. Nothing crazy. I just wanna get my battery life back to before, where basically I could leave home fully charged and work a 10-12 hour day and come home with around 30% or so battery life. That's good enough for me.
So about these recommended voltages. I have the "fast" processor, should I just st the voltages for what he recommends? Are those recommended for bet battery life or best performance? I want to undervolt as much as possible without creating an unstable system or causing damage.
And can you help me understand the governor settings, my understanding is that "ondemand" activate both cores when needed, and interactivex is all the time? Is that roughly correct?
sent from my Galaxy S3 on beans 14 via tapatalk 2
Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!
nicholi2789 said:
Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!
Click to expand...
Click to collapse
Yea flashing kernels and roms is very addicting. Since you have a fast cpu, you can actually UV much lower than I can with my nominal cpu. You can set your voltages to match Imoseyon's table and you'll be fine or maybe try lower. I know from experience that I can't UV lower than 900 mv without my phone immediately locking up lol You can even hold off on setting voltages at boot if you want to get a feel for performance while UV'ed.
I can't really speak on OC vs. regular clock battery life, I keep mine OC'ed at 1.62 ghz so I'd notice minor drops in battery life compared to say 1.8 ghz. I don't even have much need for that since its fast enough to me as is. I haven't noticed too much of a hit on battery, I still range between 2.5-4 hours screen on pending if I'm on LTE or wifi during that charge.
Also, if you want to try your hand at really digging into kernel settings then you should also check out the the Team Kernelizer's thread for KT747 kernel. Personally, I use LeanKernel cuz it works really good for me so I applied some settings from there but not everything was applicable. This thread has some really knowledgeable people in it. Definitely give KT747 a look, or any other kernel for that matter, and see which ones you like the best.
Yeah i think i may have had a bad battery. I checked and I know my phone is deep sleeping, but since adjusting my voltages and settings last night it'd definetely improving. I have my voltages set to 25mv under what is recommended on that chart down to 1.4 the in the lower clock settings o have it exactly at the recommended settings. Seems to work okay. I have set on boot enabled but i also have the stock voltage settings on my SD Just in case of a boot loop.
sent from my Galaxy S3 on beans 14 via tapatalk 2
Does anyone have any suggestions? I really like this ROM and would prefer to keep it if possible but this battery life is terrible. Ant ideas on some measures I could take to try and improve it a bit?
I wiped cache partitions, davlik cache, and did factory reset before installing. I even do them twice just to be sure.
Would maybe wiping and re flashing the Rom help? I'm totally stumped here.
sent from my Galaxy S3 on beans 14 via tapatalk 2
I don't understand. I used cpu spy and i know phone is deep sleeping. I have set CPU to drop the clock speed when screens off.
Why the heck is it using so much battery? I'm dropping about 6-7% battery at idle. Somebody shed some insight.
sent from my Galaxy S3 on beans 14 via tapatalk 2