Develop Bugs

overclocking

Hi,
Does over clocking the compact III give it more performance?
How does one overclock it in the first place?
i tried to search the artemis threads but could not find any information

Search for Battery Status Today Plugin

http://forum.xda-developers.com/showthread.php?t=282006&highlight=artemis+overclock

thanks for the response and the link
how did i miss that one ??

No problem. I had the same question a few days ago so knew what to look for. (For the record I have my P3300 at 260 using the Battery Status Today plugin and it is stable for everything including TomTom. The difference in performance is quite noticable when multitasking.)

thanks for the reply,
what is the normal speed of the orbit/compact III/p3300?
will overclocking my device cause it harm in the long run?

xda_guy said:
thanks for the reply,
what is the normal speed of the orbit/compact III/p3300?
will overclocking my device cause it harm in the long run?
Click to expand...
Click to collapse
Hi, not a very long term user, but my O2 Orbit runs fine at 273 with BatteryStatus. 289 seems not to be stable for me.

My P3300 runs max. at 273MHz. 286MHz makes device unstable, when it is full loaded.

xda_guy said:
thanks for the reply,
what is the normal speed of the orbit/compact III/p3300?
will overclocking my device cause it harm in the long run?
Click to expand...
Click to collapse
The normal speed is 201, I believe. Overclocking creates more heat, takes more power, but seems to be stable when used in moderation (270ish max).
I had to take it off my phone because even overcloking to 210something caused me to not be able to stream video with WMP over wifi.

xda_guy said:
thanks for the reply,
what is the normal speed of the orbit/compact III/p3300?
will overclocking my device cause it harm in the long run?
Click to expand...
Click to collapse
201 is the stock speed.
Overclocking could damage your device, especially if you push the edges of the chip's ability. Further continual over clocking might lessen the lifespan of the device.
That said there seem to be a good number of people overclocking to 250-260 without any obvious adverse effects. It may cause harm but for the most part seems safe as long as done in moderation. No one can say for certain though, it is a calculated risk.

Well BatteryStatus is your big friend here. The beta version (1.04) has an option called cpu scaler. I use it all the time. It works like this: you tell the program what you want to be the lowest cpu speed (for example 100Mhz) and you tell give in what the highest clockrate should be (for example 260Mhz). Depending on the load on you device BatteryStatus scales the clockspeed down or up. So when needed it gives you the extra power, and when not needed it will slow the device down, saving extra power and also saving the life of the processor.
I personally use the speeds mentioned above. But, when the speed is scaled down to 100Mhz the screen starts flickering a bit. If I were you I would not go down the 100Mhz.

Overclocking
I’ve Overclocked my XDA Orbit (O2) using Omapclock + OmapClockPlus successfully running at 264 speed anything above that doesn’t work on my phone, Reporting all programs running fine including Camera.

Dead Artemis...
JanetPanic said:
201 is the stock speed.
Overclocking could damage your device, especially if you push the edges of the chip's ability. Further continual over clocking might lessen the lifespan of the device.
That said there seem to be a good number of people overclocking to 250-260 without any obvious adverse effects. It may cause harm but for the most part seems safe as long as done in moderation. No one can say for certain though, it is a calculated risk.
Click to expand...
Click to collapse
Hi folks,
today my artemis is died.....
He only shows the start screen (T-Mobile Logo) and won´t to da any more... useing bootloader mode an flash the rom back to wm5 (WM6 was before) is successful but then is the same, only starting logo and nothing more.... (he fews me this for more than 5 hrs now....)
I used Battery Status with @ 260 MHZ...
Maybe this was the problem...
Regards,
Andy

mine's on constant 260 with xcpuscalar, no side effects, been like that for ages.

battery drain and Snap with CM6?

CM6 is definitely great, I think without question it is a vast improvement.
The only issue I have is my battery life is ABSOLUTELY HORRIBLE. Could be the worst battery life I've had with any phone. But maybe that's just the EVO, with it's big screen and speedy processor. I underclock to 384 mhz sometimes but then the thing slows down and even freezes. I have 3 different batteries and they all perform about the same (not good.) Before I had a partial wake issue but that's gone, and battery life still stinks. I've also tried calibrating but nothing really seems to make it better.
I hear the snap thing is good for battery life but I everytime I open that thread I get a headache. I love this phone and am obsessed wtih it but that thread is a bit much even for me!
Can anyone give me a quick and dirty explaination of what snap is / how to use snap? Which kernel to flash? Some day I hope to digest that mammoth of a thread, but right now I'm too busy reading texts for college and Just want better battery life.
Thanks!

Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.

nyc_zx10 said:
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
Click to expand...
Click to collapse
Yeah, I tried System Panel but the things eating my battery were mostly system things, like Browser. I guess I could give it another go.
Why are Juice Defender reviews so bad? I've considered it before also, maybe will try playing with it again

snap 8.2 is the current release. you can try any of the kernels, but i would avoid the 7.0/7.1 SD Card implementations since that technology has been put on the back burner for a bit.
Snap allows you to you Overclock and Undervolt (aka: UV).
Overclocking of course is for speed and Undervolting may save battery.
all EVOs are not created equal. some like undervolting some do not. so snap is available in multiple flavors. each with a different UV floor. the lower the floor the more potential battery saving..but also the more chance for a random reboot or wifi/gps acting funny. remember UV retards the amount of power so things can act goofy. the different UV floors are 800mv - 925mv. for example...i use the 8.2_900 because it works well with my EVO. the 8.2_800 booted great but after a while started rebooting itself. 8.2_850 just hung at bootup. the 8.1 kernels didn't work for me at all. 7.3b1 was great.
HAVs is adaptive..so don't get stressed if your device fails to boot properly the first time. wipe the cache/dalvik and try again.
so download a few of the 8.2 kernels.
make your nandroid
begin trial and error (I'd suggest starting at 800, 850 then 900 to get a feel)
don't be afraid to wipe the Cache and Dalvik multiple times.
don't worry about the whole thread. just grab the last few pages and read the OP. then feel free to ask.
i also recommend setCPU. you can find some threads for SetCPU configurations to help. BUT....make sure SetCPU is disabled when flashing the new kernel. once you get a working kernel you can enable SetCPU...but during testing phase it will give you gray hair.
jmxp69 said:
Just a few quick thoughts on voltages/freqs after seeing a handful of discussion in the thread:
1) Every 8.2 kernel has voltages lower than stock. The default stock voltage @ 245 is something around 1050.
2) No real effort is made to UV at the top end. It's a little lower, but the objective at the highest CPU frequency is not to UV. Most of the benefit of UV comes at the low end of the scale when your phone is idle (most of the time). Less voltage = less draw.
3) nHAVS scales voltage at each step. There is a min.max voltage at every cpu frequency. This range is fairly small--50-75mv, but it enables HAVS to decide based on feedback from the CPU which one to apply. And the max at each step is lower than stock. So no matter how you slice it, even if you're running 925, you are undervolted. This becomes a question of how undervolted.
4) OC is not about undervolting, it's about overclocking. The differences is voltage vs. frequency. OC means we're increasing the CPU frequency beyond stock which is 998mhz in the case of Evo. If you move your SetCPU slider beyond 998mhz, you're overclocking.
The objective of overclocking is speed. The objective of undervolting is battery savings. Snap gives you both. We overclock when we increase the fequency with SetCPU. We undervolt automatically via nHAVS. As of this writing, UV is handled in the kernel, it happens most at the bottom end of the frequency scale.
I hope this helps clear up some of the questions. Great conversation by the way.
Click to expand...
Click to collapse

GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol

Thank you Dragin!!!
That helps a lot! So once you have Snap setup at what you feel is "good" does your phone seem to perform as well as before you had it undervolted? Man, sounds like a pretty involved process - maybe I better wait until I can really sit down and play with it.

goodelyfe said:
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Click to expand...
Click to collapse
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App

foueddyf said:
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I think he's talking about when ur figuring out the best setup

Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App

I had the same issue, left to stock with kingx.
Sent from my PC36100 using XDA App

nyc_zx10 said:
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you know what in particular Juice is doing to give you better battery life? like what does Turn off certain things based on conditions or?
That is some good battery life.

Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App

nyc_zx10 said:
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Meh... see I really don't want to do those things. I can turn off data sync myself and just have gmail forward me a text message when I have an email. I just was hoping there was a way to get decent battery life without going back to the days of Winmo
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)

berardi said:
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
Click to expand...
Click to collapse
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.

DraginMagik said:
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
Click to expand...
Click to collapse
Thanks man, appreciate the breakdown.
You have inspired me, I'm going to bite the bullet and try this snap7.5_925 kernel. I'll report back my luck
I do enjoy this stuff, really - just right now it would be irresponsible for me to spend too much time on it. School comes first right now.

DraginMagik said:
... after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
Click to expand...
Click to collapse
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.

loupy said:
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
Click to expand...
Click to collapse
Yeah dragin, don't hog those sweet settings! I'm enjoying Snap 7.6 and it seems to be helping out my battery life a bit, but I'd love to see your SetCPU details.

I've found that the issue for me is bluetooth. If I have it on constantly my battery will drain 10-15% per hour. With bluetooth off it's only draining 1%-2% per hour.
Seems like the bluetooth needs work on CM6 in order to have the efficiency that the other ROMs i've tried (Fresh and EViO) have. Nonetheless, I'm sticking with CM6 and just use the bluetooth when necessary.

I have the same issue with bluetooth on CM 6.0.0. I am running the stock kernel that comes with cyanogenmod, so this is definitely not a snap issue. There was a bug submitted about a month ago:
code.google.com/p/cyanogenmod/issues/detail?id=2136
I *really* hope this can get fixed for the 6.1 release, but it is currently listed with a low priority. I really love CM6, but basically making bluetooth unusable for more than a few hours really makes me struggle with the using this rom.

Why not the 7.6 with turbo...just wonderin

[Q] Decks or Cm7's best kernel (SVZ vs Tiamat vs Godmode)

Hi guys, i've been looking into many threads and reading a lot of posts and asking a lot of questions. however i know that their is not for sure answer to this but i would like to see what you guys believe to be your best kernel for battery and performance. i have seen people say it is Godmode (v9), Tiamat v4.1.0, Tiamat v3.3.7, and Savaged-zen v2.2.1. (ALL of these ARE with SBC-OFF). i just want to know what is you best kernel at the moment for your evo with decks or cm7.
Side Question: what is the difference between the governors: (Interactive, InteractiveX, Smartass, SmartassV2, Savaged-zen, and Lag Free)?
- Thank You

I like Tiamat 4.1.0, but I can't help you for your side question. I'm still new to development and rooting

kendallc123 said:
I like Tiamat 4.1.0, but I can't help you for your side question. I'm still new to development and rooting
Click to expand...
Click to collapse
i know you said your new but im just wondering have you tried any other kernels?
and what is your battery life with Tiamat 4.1.0

I've used damn near every kernel available for CM7. And by far the BEST kernel for battery life is Savaged Zen. I'm on a stock battery and it just seems to last forever. Add to that the fact that the battery lasts all day without sacrificing performance at all. Every phone is different and you may or may not see the same results. This is just what has worked for my phone. Honestly, your best bet is to get flash happy with various kernels until you find one that gives you the performance and battery life that you're looking for. By the way, I use SVZ Manager with my kernel so that I can toggle SBC on and off as I please. It's a nice apk that gives you some flexibility.
**CLICK HERE**

Green_Arrow said:
i know you said your new but im just wondering have you tried any other kernels?
and what is your battery life with Tiamat 4.1.0
Click to expand...
Click to collapse
I've tried Tiamat 4.0.8 and a Savaged Zen kernel (can't remember which version). They both gave me about 12 hours of battery life on an average day(for me). But an average day for me is going to school, so I'm not on my phone as much. I haven't gotten to really test the battery life because I haven't looked at it on the weekend when I'm not at school. But like Concordium said, every phone is different! Try them all!

Tiamat 3.3.7 sbc
Sent from my PC36100 using XDA App

Concordium said:
I've used damn near every kernel available for CM7. And by far the BEST kernel for battery life is Savaged Zen. I'm on a stock battery and it just seems to last forever. Add to that the fact that the battery lasts all day without sacrificing performance at all. Every phone is different and you may or may not see the same results. This is just what has worked for my phone. Honestly, your best bet is to get flash happy with various kernels until you find one that gives you the performance and battery life that you're looking for. By the way, I use SVZ Manager with my kernel so that I can toggle SBC on and off as I please. It's a nice apk that gives you some flexibility.
**CLICK HERE**
Click to expand...
Click to collapse
at the moment i am using the latest svz kernel with the svz manager as well. i have been flashing many kernels and for a while i was happy when i used the godmode kernel my phone lasted me 1 day and 6 hours, however he is no longer updating his kernels =( i'm hoping to find another kernel such as that one that will give me around the same results ^_^

Green_Arrow said:
at the moment i am using the latest svz kernel with the svz manager as well. i have been flashing many kernels and for a while i was happy when i used the godmode kernel my phone lasted me 1 day and 6 hours, however he is no longer updating his kernels =( i'm hoping to find another kernel such as that one that will give me around the same results ^_^
Click to expand...
Click to collapse
I liked Godmode. But it didn't seem to give me as good battery life as savaged zen has given me. Each phone is different though.

Concordium said:
I liked Godmode. But it didn't seem to give me as good battery life as savaged zen has given me. Each phone is different though.
Click to expand...
Click to collapse
well im testing this one out at the moment and it has given me so far 17 hours and 20 mins, still at 31% battery, im just not sure if it'll do better than godmode did, at the moment im running it on the smartass kernel and i ran godmode on interactive so maybe that is the prob... however another issue is i've heard that svz is no longer updating as well... do u know if this is true? and one random thing that only a few people have told me is that they run on performance and overclock their phone and get the best battery from it, is that possible or a lie?
Edit: it lasted 20 hours and 53 mins, so since it didn't do as good as GodMode did then im gonna try the tiamat 4.1.0 now cause it has first place in the poll atm.

Green_Arrow said:
well im testing this one out at the moment and it has given me so far 17 hours and 20 mins, still at 31% battery, im just not sure if it'll do better than godmode did, at the moment im running it on the smartass kernel and i ran godmode on interactive so maybe that is the prob... however another issue is i've heard that svz is no longer updating as well... do u know if this is true? and one random thing that only a few people have told me is that they run on performance and overclock their phone and get the best battery from it, is that possible or a lie?
Edit: it lasted 20 hours and 53 mins, so since it didn't do as good as GodMode did then im gonna try the tiamat 4.1.0 now cause it has first place in the poll atm.
Click to expand...
Click to collapse
Its true that its not being updated anymore. It sucks but I plan to ride it out as long as the kernel functions properly with CM. Once it starts screwing up then I'll switch.
Those who say they get the best battery life by overclocking and putting their phone on performance are full of crap. Performance governor is basically the polar opposite of Powersave. Performance keeps your cpu constantly running at a high frequency. Logic states that overclocking to 1.13 ghz and perpetually running at that frequency requires more power than running at 245 mhz. The more power required the less time your battery will stay alive. Powersave gives you best battery life but gives you crap performance. Interactive, Smartass, and Ondemand give you a balance of performance and battery life. Performance gives you the best performance but crap battery life.
By the way, do you really need a phone that can stay off the charger for more than 21 hours? :-x

Concordium said:
Its true that its not being updated anymore. It sucks but I plan to ride it out as long as the kernel functions properly with CM. Once it starts screwing up then I'll switch.
Those who say they get the best battery life by overclocking and putting their phone on performance are full of crap. Performance governor is basically the polar opposite of Powersave. Performance keeps your cpu constantly running at a high frequency. Logic states that overclocking to 1.13 ghz and perpetually running at that frequency requires more power than running at 245 mhz. The more power required the less time your battery will stay alive. Powersave gives you best battery life but gives you crap performance. Interactive, Smartass, and Ondemand give you a balance of performance and battery life. Performance gives you the best performance but crap battery life.
By the way, do you really need a phone that can stay off the charger for more than 21 hours? :-x
Click to expand...
Click to collapse
no i do not but! 3 days of the week im at school doing nothing for 8-10 hours so... i think if my phone can run longer than a day w/o charging then it mean i can play games on my phone while waiting and by the end of the day i'll still have battery. and does it make sense for someone to get better battery life on interactive than on smartass?

Green_Arrow said:
no i do not but! 3 days of the week im at school doing nothing for 8-10 hours so... i think if my phone can run longer than a day w/o charging then it mean i can play games on my phone while waiting and by the end of the day i'll still have battery. and does it make sense for someone to get better battery life on interactive than on smartass?
Click to expand...
Click to collapse
Well Smartass, as I've heard it described, is sort of like Interactive 2.0. It's basically the interactive governor but better. Unfortunately, I do not know enough of the exact specifics of the governors to tell you which SHOULD be getting better battery. I would just run each of those governors and see which one works better for you.
And I thought your phone already lasted 21 hours with a decent amount of usage. You need to test the governors/kernels in the exact situation you are going to be using the phone. Interactive, Ondemand, and Smartass would all manage the phone pretty much the same if you just leave it alone and let it sit till the battery drains. but they each manage the power allocation supplied to the cpu very differently during actual use. One ramps up the voltage quickly while one scales it up more gradually. So take your charger with you to school, in case you run into trouble, and use the phone as you believe you will be using it in the future. Then you'll have a more accurate idea of which setup works best for you.

Concordium said:
Well Smartass, as I've heard it described, is sort of like Interactive 2.0. It's basically the interactive governor but better. Unfortunately, I do not know enough of the exact specifics of the governors to tell you which SHOULD be getting better battery. I would just run each of those governors and see which one works better for you.
And I thought your phone already lasted 21 hours with a decent amount of usage. You need to test the governors/kernels in the exact situation you are going to be using the phone. Interactive, Ondemand, and Smartass would all manage the phone pretty much the same if you just leave it alone and let it sit till the battery drains. but they each manage the power allocation supplied to the cpu very differently during actual use. One ramps up the voltage quickly while one scales it up more gradually. So take your charger with you to school, in case you run into trouble, and use the phone as you believe you will be using it in the future. Then you'll have a more accurate idea of which setup works best for you.
Click to expand...
Click to collapse
just wondering what do you keep your cpu settings at: the governor, cpu min & max?

When I am plugged into my wall charger I keep it at 1113/245. I use Performance for benchmarking and testing since I don't need to worry about battery life and Smartass when doing everything else. For normal every day use I have it at 1036/245/Smartass, Interactive, or Ondemand. I don't really have a preference between the three governors since they all make my battery last more than long enough. So it usually comes down to whichever my clumsy finger happens to accidentally select first. If I happen to not go home and need more life then I'll drop to 729/245/Conservative or Powersave. I use conservative if I still need to be able to use the phone a bit and powersave if I want my phone to just sit there and look pretty till I get back home.

Concordium said:
When I am plugged into my wall charger I keep it at 1113/245. I use Performance for benchmarking and testing since I don't need to worry about battery life and Smartass when doing everything else. For normal every day use I have it at 1036/245/Smartass, Interactive, or Ondemand. I don't really have a preference between the three governors since they all make my battery last more than long enough. So it usually comes down to whichever my clumsy finger happens to accidentally select first. If I happen to not go home and need more life then I'll drop to 729/245/Conservative or Powersave. I use conservative if I still need to be able to use the phone a bit and powersave if I want my phone to just sit there and look pretty till I get back home.
Click to expand...
Click to collapse
why is ur lowest 245 and not 128? sorry if im bugging you

Green_Arrow said:
why is ur lowest 245 and not 128? sorry if im bugging you
Click to expand...
Click to collapse
You're not bugging me man. This place exists so people can ask questions and get help.
I keep my min at 245 because I've read, in multiple places, that allowing it to go any lower is not something your cpu really appreciates. Just like there is such thing as too high with your clock speed there is also a too low. And everywhere I have seen 245 is the preferred low end. I am not 100% sure as to why but I would assume that it is because your cpu needs at least a certain amount of power to run the basic processes required to keep your phone functional. Similar to a computer. Lower the cpu too much and it just can't do what it needs to.

Concordium said:
You're not bugging me man. This place exists so people can ask questions and get help.
I keep my min at 245 because I've read, in multiple places, that allowing it to go any lower is not something your cpu really appreciates. Just like there is such thing as too high with your clock speed there is also a too low. And everywhere I have seen 245 is the preferred low end. I am not 100% sure as to why but I would assume that it is because your cpu needs at least a certain amount of power to run the basic processes required to keep your phone functional. Similar to a computer. Lower the cpu too much and it just can't do what it needs to.
Click to expand...
Click to collapse
i see do u happen to know of a good thread that talks about this? cause i keep mine at the lowest because i read that its better for battery life, but they never said anything about it being bad

Green_Arrow said:
i see do u happen to know of a good thread that talks about this? cause i keep mine at the lowest because i read that its better for battery life, but they never said anything about it being bad
Click to expand...
Click to collapse
I don't remember there being a thread dedicated to this. I just remember it from posts I saw within different OC/UV threads. Do a Google search for it and see if that returns any results. Like I said, I doubt you'll find a full dedicated thread. But you may be able to find the individual posts where it's mentioned.

Concordium said:
I don't remember there being a thread dedicated to this. I just remember it from posts I saw within different OC/UV threads. Do a Google search for it and see if that returns any results. Like I said, I doubt you'll find a full dedicated thread. But you may be able to find the individual posts where it's mentioned.
Click to expand...
Click to collapse
thank you, you have been really helpful ^_^

With Tiamat 4.1 and juicedefender I get the best battery performance and v6 supercharger I have a smooth screen with no problems or lag at all.

[Q] AOKP Ktoonsez + KT747 = ?

Hey I want to know how KT747 kernel works with AOKP Ktoonsez and Task650. From what I hear its pretty good. My main concern is battery life. I heard some people get around 5 hours of onscreen time which is incredible. If you are running these two together, what are good settings for good battery life? I'm using KT747 with CM10 M2 and Ktoonservative/noop but battery life is kinda bad. Thanks

I'm running that setup and although i can't really compare my battery stats to your as i have a 4400mah battery, i can say that for my phone atleast the battery life is superb. I actually just plugged it in after 67 hours, with about 7 hours screen on time. Obviously this isn't going to happen on a stock battery (mine came with a 2100mah), you could realistically expect a little less than half these numbers. I would suggest taking a look at this thread, which discusses overclocking and undervolting settings. I have posted pics of my personal undervolting settings (page 15, post 150), however your device may differ. I discuss why and my suggested method to finding the best value's for your device in the same thread, post 152 on page 16. Of course the discussion has many other opinions and suggestions as well so try them out until you find the one that works best for you. One thing i didn't mention is to disable the cpu settings in the settings>rom control>performance menu as it will conflict with the settings in ktweaker and can actually drain the battery much faster than normal.

dntesinfrno said:
I'm running that setup and although i can't really compare my battery stats to your as i have a 4400mah battery, i can say that for my phone atleast the battery life is superb. I actually just plugged it in after 67 hours, with about 7 hours screen on time. Obviously this isn't going to happen on a stock battery (mine came with a 2100mah), you could realistically expect a little less than half these numbers. I would suggest taking a look at this thread, which discusses overclocking and undervolting settings. I have posted pics of my personal undervolting settings (page 15, post 150), however your device may differ. I discuss why and my suggested method to finding the best value's for your device in the same thread, post 152 on page 16. Of course the discussion has many other opinions and suggestions as well so try them out until you find the one that works best for you. One thing i didn't mention is to disable the cpu settings in the settings>rom control>performance menu as it will conflict with the settings in ktweaker and can actually drain the battery much faster than normal.
Click to expand...
Click to collapse
Thanked*. Will take a look at the thread. Last time I undervolted I used some guys settings which were extremely wonky and cause a lot of mishaps. I'm still looking for good ones so I might try yours. Thanks.

DarthDerron said:
Thanked*. Will take a look at the thread. Last time I undervolted I used some guys settings which were extremely wonky and cause a lot of mishaps. I'm still looking for good ones so I might try yours. Thanks.
Click to expand...
Click to collapse
Sounds like too much undervolt.

jethro650 said:
Sounds like too much undervolt.
Click to expand...
Click to collapse
Just tried it, it was a little to much so I bumped everything up a little bit. Seems fine now. Going to flash AOKP later today.

Thats actually how i got those settings, i used what someone said was stable on theirs. It wasn't, playing pretty much any game on my phone would cause a reboot in less than 5 minutes. I think i ended up about 20 mv higher on all steps than his settings. You just have to find what works for you phone.

dntesinfrno said:
Thats actually how i got those settings, i used what someone said was stable on theirs. It wasn't, playing pretty much any game on my phone would cause a reboot in less than 5 minutes. I think i ended up about 20 mv higher on all steps than his settings. You just have to find what works for you phone.
Click to expand...
Click to collapse
Indeed. I have AOKP with Ktoonsez/sio and voltage a little higher than yours. Works fine, battery is good.

I have recently switched to the noop scheduler after an article i read which basically said there is no need for a scheduler using flash memory. All the other schedulers are designed for physical hard drives which have seek times, flash does not. Using these schedulers actually creates an artificial seek time, thereby wasting cpu clock cycles and burning precious energy in the process.

dntesinfrno said:
I have recently switched to the noop scheduler after an article i read which basically said there is no need for a scheduler using flash memory. All the other schedulers are designed for physical hard drives which have seek times, flash does not. Using these schedulers actually creates an artificial seek time, thereby wasting cpu clock cycles and burning precious energy in the process.
Click to expand...
Click to collapse
Was always on noop and ktoonservative. Most people recommend those two together

Boss-njo said:
That rom is no go.
Click to expand...
Click to collapse
Care to elaborate?

Boss-njo said:
That rom is no go.
Click to expand...
Click to collapse
I think its pretty good. I find it more stable than other roms, imo.

KT747/Cm10 m2
Hi,
I installed Cm10 m2, then ran it, rebooted, and installed kt747, cleared caches and fixed permissions, could not boot afterwards, Anyone else have this problem?

Mitch.sc said:
Hi,
I installed Cm10 m2, then ran it, rebooted, and installed kt747, cleared caches and fixed permissions, could not boot afterwards, Anyone else have this problem?
Click to expand...
Click to collapse
Hmm, I've never had that problem with KT. Make sure you have correct version, AOSP JB. I would recommend flashing CM10.0.0, the latest CM10 stable build.

Does undervolting really save battery life?

Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet

TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
What part of "you won't save more than 2%" you didn't understand?

ilusi0n_ said:
What part of "you won't save more than 2%" you didn't understand?
Click to expand...
Click to collapse
Well, i don't really understand WHY it doesn't save more than 2% of the battery life. Afaik, EXUV does reduce heat and improve battery life by miles. But that's what I thought. In reality which is this, im not rly sure why that even with EXUV, it still cant save more than 2% of the battery life.
Sent from my S800 China Phone

TiTAN-O-One said:
Hey guys i saw this video on youtube (http://youtu.be/5nrOWZUsEEc) that explains that undervolting wont make your phone save battery life more than 2% even with EXUV. I need explanations for this as i don't really understand.
Via the Internet
Click to expand...
Click to collapse
I'm not technically expert with things like this but I have read an article/ blog before that undervolting may damage a phone since it was designed to work with that specific voltage. So, I actually didn't do that even UC or OC. Just saying.....

Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)

r25txe said:
Undervolting doesn't save battery as your CPU will still try and draw the manufacturer set levels.
If it doesn't get those levels it must step down its own level which essentially means that the activity that needs processing needs more time, and consequently, more battery.
Even if you manually adjust the clock speed of your CPU down to match your new voltages, the same applies.
UC/UV is quite simply the worst voodoo that persists across these forums.
/stripped down explanation
(I didn't even watch the video)
Click to expand...
Click to collapse
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/samsung-kernel-msm7x30/commit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware

sir mordred said:
we can control the hardware through software so we can control the voltages and frequencies through kernel
devs can put new frequency levels as manufacturers did (like this :https://github.com/Christopher83/sa...mmit/899d5a296a43a6d32c2468bba8121c3a1915dd68)
if its not true and if this method doesnt work, Why all kernel devs on XDA trying the same thing??
https://github.com/faux123/android_kernel_oppo_n1/commit/eaa6639979e1144f28c14e6de48994d41e5d20d8
https://github.com/franciscofranco/hammerhead/commit/104890313a73dae0e7d7a13975801cc568d231ad
in summary EXUV and UV are absolutly battery-friendly
and do not forget undervoltage cant damage the hardware but overvoltage(ı mean OC) can damage the hardware
Click to expand...
Click to collapse
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.

So to sum all this up. We just have to leave the CPU & voltage tables alone since it damages hardware?
Via the Internet

It's not that you have to, but that chip designer recommends it.

r25txe said:
I've based my reply above on this post.
It is a much longer version of what I summarised earlier.
And, sorry, even UC/UV can damage your hardware in rare situations.
It does baffle me why people spend so much time tweaking things as you mention when the net returns are negligible, and often cancelled out.
Click to expand...
Click to collapse
That was also the POST that I'm referring to that I've read :good: