Related
Has anyone noticed that the cpu throttles based on its current stress level.
Sent from my HTC Liberty using XDA App
That's deff interesting. I haven't done much playing with CPU apps because the one time I put setCPU on my Aria it caused all kinds of issues. But that was like three days after the Aria launched so setCPU may support Aria now.
According to Android System Info I get:
480mhz 23.08%
600mhz 76.92%
So it is throttling for sure.
Maybe SetCPU will work now? but I hope it can throttle lower than 480. is there a limit to how low it can go?
All phones throttle in order to save juice. Your phone wouldn't last long at 600mhz. So this won't help with setcpu since the kernel still needs to be hacked. The CPU should clock lower in full sleep mode
Sent from my Behold II using XDA App
sentinel79 said:
but I hope it can throttle lower than 480. is there a limit to how low it can go?
Click to expand...
Click to collapse
It can, my Aria shows it is at 245.76Mhz 95.61% of the time
Android system info shows lower clocks, like 200Mhz, but my Aria hasn't operated at that speed at all.
Shad0wguy said:
It can, my Aria shows it is at 245.76Mhz 95.61% of the time
Android system info shows lower clocks, like 200Mhz, but my Aria hasn't operated at that speed at all.
Click to expand...
Click to collapse
That is when your phone is at full sleep. You won't see that speed when the screen is on.
Sent from my Behold II using XDA App
psychoace said:
That is when your phone is at full sleep. You won't see that speed when the screen is on.
Sent from my Behold II using XDA App
Click to expand...
Click to collapse
Okay this makes sense then since it was a fresh install and I had yet to put it to bed
Hey guys any of you running set cpu? i have a profile set so that when i turn the screen off it drops the cpu down to 250mhz. I'm having a issue where sometimes it dosen't wake back up. Anyone else had this happen?
I noticed this Tuesday. They don't play nice together...yet. setcpu needs info about the hummingbird cpu in order for it to work. Setcpu's dev will most likely have an update for this soon. For now, i'd uninstall it and keep an eye out on the program for an update.
sweet glad to know that its not just me.
I had this same problem with the Overclock Widget for the same purpose (shut down CPU while screen sleeps)... After removing Overclock... I have yet to have a blank screen situation.
I've got mine (SetCpu) set to the "on-demand" preset. Have not had a wake up issue yet...
SetCpu seems to be quite different on the Epic than on the EVO. More presets and options....
madocs said:
I've got mine (SetCpu) set to the "on-demand" preset. Have not had a wake up issue yet...
SetCpu seems to be quite different on the Epic than on the EVO. More presets and options....
Click to expand...
Click to collapse
Scratch that - this morning the EPIC didn't wake. Battery out, back in, screen off, didn't wake.
Uninstalled SetCpu, all is back to normal (except for the crap battery life of course).
Emailed the SetCpu dev, he thinks it is related to the kernel. I'll try out a custom ROM/kernel as soon as one is ready to see if it resolves the issue.
I'm not having any issues with my epic and setcpu, right now the screen off profile is: 200Mhz, ondemand, & priority @ 100.
In the Vibrant forum there are numerous threads in which the OPs screwed up their phones using setCPU. I'd stay away from apps like setcpu, juice defender, task killers, etc.
Chalup said:
In the Vibrant forum there are numerous threads in which the OPs screwed up their phones using setCPU. I'd stay away from apps like setcpu, juice defender, task killers, etc.
Click to expand...
Click to collapse
i agree with staying away from set cpu but juice defender and task killer are essential to me getting decent battery life on my epic lol
vavaud said:
I'm not having any issues with my epic and setcpu, right now the screen off profile is: 200Mhz, ondemand, & priority @ 100.
Click to expand...
Click to collapse
How long have you had it in use? I was cool for a day, then it wouldn't wake up.
From the dev: "The scaling is the issue, I think. Ondemand crashes the Galaxy S, but conservative doesn't seem to."
I'm ready to hit some customs, battery life just isn't good enough so far.
2.0t03speed said:
i agree with staying away from set cpu but juice defender and task killer are essential to me getting decent battery life on my epic lol
Click to expand...
Click to collapse
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
madocs said:
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
Click to expand...
Click to collapse
I was using conservative on set cpu when i got the lockup
Sent from my Epic 4G
I have been using setCPU and ATK since 9/2 with no problems so far. I have it set on conservative and 200 when screen is off. I been getting around 10-12 hours with moderate uses. With little use today I am at 9 hours with 50% battery left.
madocs said:
I've had good results with the conservative setting of SetCpu. With ATK and SetCpu, I had double the prior norm in battery life. Over past 2 days I've gotten over 12 hours and I plugged in before full drain both days. Started at 6:30 this morning, should get a good read on potential. Expecting 15+ which would officially resolve my battery issues.
Click to expand...
Click to collapse
I ended up at with over 15 hours logged and ~15-20% battery remaining last night. Good enough for me. Bluetooth/GPS/Wifi on all day, 4G off, screen turned down, ATK.
No Problem with CPU Set at 200
I kept having the same issue until I changed the lower limit to 200 and used Conservative setting.
Now, no problem at all!
I think I tend to agree with you.... I tried running the phoenix kernel on my epic, and the phone would not wake up (was told it was because phoenix defaults to 100/1000) and was told to use setcpu.. tried it... wow... what a disappointment.. setcpu kept giving me way different readings everytime I ran it.... not nice at all....
I've since tried this again, this time, placing setcpu.txt on my /sdcard will see if this helps..... so far, so good......
I have a screen off profile set for 400mhz max 200mhz min with conservative governor. My main profile is 1200mhz max and 200mhz min. This is with the mixup kernel and I never have any lock up issues
Sent from my Emotionless Beast of an Epic using the XDA App
i have my min at 200 for all of my profiles. My screen max is 400 and it keeps my phone from waking up. It's set to conservative. I'm also using it with juice defender, so i'm not sure if that's the culprit or what. Does anyone else have any suggestions on settings for screen off?
Hello,
I just installed SetCPU and configured some profiles. I'd like to hear comments about them:
Screen Off 83/83
Charging 667/83
Battery < 15% 83/83
Battery < 30% 222/83
What do you think of setting 83/83? Too low?
How can I overclock?
I'd like to set a profile for temperature controlling, what is considered a high temp?
Thanks!
I would like to know about this as well. How has those settings worked out for you so far?
Using 83/83 was way too slow. When I had screen off and wanted to turn it back on, it would take too long.
I'm currently using these profiles (in order off priority):
Charging 667/83 (ondemand)
Screen off 222/83 (conservative)
Battery <30% 222/83 (conservative)
I haven't figured out how to overclock yet.
Sent from my GT-I5800L using XDA App
For overclocking we would nees a custom kernel that supports overclocking.
Sent from my GT-I5800 using Tapatalk
s3th.g3ck9 said:
For overclocking we would nees a custom kernel that supports overclocking.
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
Which I assume we don't?
Not yet. But now that the first view custom roms came up i believe we will find one coder that's building a custom kernel.
Sent from my GT-I5800 using Tapatalk
s3th.g3ck9 said:
Not yet. But now that the first view custom roms came up i believe we will find one coder that's building a custom kernel.
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
That's exciting! Are the custom roms you refer to the ones from samfirmware?
Nope... I refer to the real custom roms. Aosp, jpb light, jpa hybrid... And currently there seems to be an eclair rom with ext4 fs is in work... Have Look in the development section.
Sent from my GT-I5800 using Tapatalk
I also hope to get on whit overclocking. This phone just needs a little more juice.
Sent from my GT-I5800 using XDA App
iomartin said:
Using 83/83 was way too slow. When I had screen off and wanted to turn it back on, it would take too long.
I'm currently using these profiles (in order off priority):
Charging 667/83 (ondemand)
Screen off 222/83 (conservative)
Battery <30% 222/83 (conservative)
I haven't figured out how to overclock yet.
Sent from my GT-I5800L using XDA App
Click to expand...
Click to collapse
Thanks for the info. I'll give this a try.
Charging 667/667 (performance)
Screen off 166/83 (performance)
Temp >37C 166/83 (conservative)
rest of the time i have under-clocked it to 333/166 (conservative)
ondemand scaling is a bit laggy when switch speeds...
current setup gives me bout 45-52 hours of usage time.
this includes around 200 msgs a day(outgoing), a total of about 1 hour wifi on time...and around 30 mins bluetooth on.plus an "always screen on " option while texting...
apps/widgets running
$brightness is minimum....always.can increase using widgets when u wanna read or check sumthin out, then revert back to min.
#battery indicator pro
#sceen filter(to reduce brightness below android's set level, good at nite)
#chompsms
#ultra keyboard
#task killer
#extended control widgets
running all the time...
s3th.g3ck9 said:
Not yet. But now that the first view custom roms came up i believe we will find one coder that's building a custom kernel.
Sent from my GT-I5800 using Tapatalk
Click to expand...
Click to collapse
Yeah, but we need someone who's crazy enough to try to overclock his i5800 without any information on the CPU X)
SetCPU lagged my phone like crazy all the time it was on.
Launcher pro+SetCPU was a damn nightmare, apps took close to 9 secs to load.
zeyk said:
Charging 667/667 (performance)
Screen off 166/83 (performance)
Temp >37C 166/83 (conservative)
rest of the time i have under-clocked it to 333/166 (conservative)
ondemand scaling is a bit laggy when switch speeds...
current setup gives me bout 45-52 hours of usage time.
this includes around 200 msgs a day(outgoing), a total of about 1 hour wifi on time...and around 30 mins bluetooth on.plus an "always screen on " option while texting...
apps/widgets running
$brightness is minimum....always.can increase using widgets when u wanna read or check sumthin out, then revert back to min.
#battery indicator pro
#sceen filter(to reduce brightness below android's set level, good at nite)
#chompsms
#ultra keyboard
#task killer
#extended control widgets
running all the time...
Click to expand...
Click to collapse
Do you get lag after turning the screen on?
I used to have anipet Aquarium Live Wallpaper + ADW Launcher EX, and had huge lag when turning the screen on - with 222/83. I stopped using the Live Wallpaper, and it got better, but there's still lag sometimes. I don't know how heavy ADW Launcher EX is, if it is it's fault or not.
Using performance scaling, if I'm not mistaken (the documentation page of setcpu is down) forces the cpu to always run at the max frequency, so it'd be the same as setting the max and min frequency as the same value, right?
I'll give a try at using conservative instead of ondemand and see if I get less lag, though I'd expect exactly the opposite!
What's the point on downclocking the CPU while using the phone ? I mean, 333mhz makes me think i bought a chinese phone (And not a cool one like the ZTE Blade).
Gsam101 said:
What's the point on downclocking the CPU while using the phone ? I mean, 333mhz makes me think i bought a chinese phone (And not a cool one like the ZTE Blade).
Click to expand...
Click to collapse
i totally agree, i would love to able to overclock it, not underclock it
i have undeclocked it coz i want a longer "ON" time...i am texting and callin ppl most of the time so battery lasts jus for a day.i don't wanna charge it everyday.plus using at 333 isnt so bad..i don't play games(much)...and even when i do(angry birds,paper toss) it works fine...u will get used to it....and whats the point in overclocking this phone? with a crappy resolution no HD game will run on it.
the only thing that sucks at low speeds is the gallery.however this can be "solved" by using the Quickpic app.it's better organized and hella fast.but it lacks the fancy looks...
@iomartin..there is no delay or lag and i have disabled the lock screen also.i use go launcher btw.
zeyk said:
i have undeclocked it coz i want a longer "ON" time...i am texting and callin ppl most of the time so battery lasts jus for a day.i don't wanna charge it everyday.plus using at 333 isnt so bad..i don't play games(much)...and even when i do(angry birds,paper toss) it works fine...u will get used to it....and whats the point in overclocking this phone? with a crappy resolution no HD game will run on it.
the only thing that sucks at low speeds is the gallery.however this can be "solved" by using the Quickpic app.it's better organized and hella fast.but it lacks the fancy looks...
@iomartin..there is no delay or lag and i have disabled the lock screen also.i use go launcher btw.
Click to expand...
Click to collapse
i dont have to use it for anything specific, i just want to OC it
stubborn_d0nkey said:
i totally agree, i would love to able to overclock it, not underclock it
Click to expand...
Click to collapse
A bit useless.. But there is a way to clock it at 523mhz if we read the CPU's specifications... That could be cool..
zeyk said:
Charging 667/667 (performance)
Screen off 166/83 (performance)
Temp >37C 166/83 (conservative)
rest of the time i have under-clocked it to 333/166 (conservative)
Click to expand...
Click to collapse
Wow thanks for this. I used these settings except for the last one (underclocking when the cellphone is being used)
Last time I recharged was 63 hours ago, and battery indicator still shows 50% left! I have:
- Watched an episode of Kenny vs Spenny (640x480)
- Played ~1h of games
- Surfing + downloading ~30min on Wi-Fi
- Installed ~ 10 apps
- Texted about 50 messages
- Made about a total of 10 minutes of calls
- Sent songs through bluetooth for.. ~10 minutes
- Listened to music for about ~30 mins
Still 50% left? Amazing. Of course this can (or is) a problem with the crappy indicator and it can quickly decrease to ~15 in a heartbeat, but it still is pretty amazing.
Phone says it has been on for 73 hours, I wonder if that's the actual time I recharged it for the last time, or if It's the last time it was charged?
Once again thanks for those profiles. First time I used the app I reckon setting the same but I used OnDemand scaling (What's the difference between these btw?) and It lagged like hell when I turned the screen on again. None of that happens now, the phone works the same way as if it had normal clock speeds.
Oh and I don't use 3G and I've got APNDroid blocking all internet connections. I wonder if that does anything to the battery life?
EDIT: Now I used some bluetooth for 15 mins and made few calls and it got bumped down to 15% and told me to recharge. Guess It'd still work for about 6 hours on stand-by but still the battery life for me was ~67hrs, whilst being ~48 before.
Here are my current stable settings:
SetCPU
Min: 100mhz
Max: 1000mhz
Governor: Ondemand
Profile: Screen Off
--Min: 100mhz
--Max: 200mhz
--Priority: 100
--Governor: Ondemand
Tegrak:
Governor: Ondemand
Scaling: 100-1000mhz
Optimization:
--200mhz Core Voltage: 1025mv
--100mhz Core Voltage: 925mv
Both SetCPU and Tegrak are running side by side.
No random reboots for over a week.
Battery should last between 20-25 hours with normal usage.
Certain phones might need a higher voltage, you may need to do some experimenting to get things stable.
Old text
Anyone experiencing random reboots should try using SetCPU or Tegrak to set the CPU to 1000mhz-1000mhz instead of 100mhz-1000mhz.
I was previously getting 3-4 reboots per day. I set my CPU to 1000mhz-1000mhz using Tegrak four days ago and have not had a single reboot since.
Sure, my battery only lasts about 10 hours vs 20 or so, but at least I can rely on my phone.
Of course I could just be lucky, and who knows it might just randomly reboot any time now.. So, obviously there is no guarantee it will work for anyone else.
Just as a note I also tried 200-1000 and 400-1000, but still had random reboots every few hours.
I am currently testing 200mhz-200mhz with the screen off and 1000mhz-1000mhz with the screen on using SetCPU. I will update this thread in a few days or if it randomly reboots.
Update: 200mhz during screen off causes the phone to not wake up (happened three times). I'm currently testing 400mhz.
Update 2: I got a random reboot last night while asleep using 400mhz. I will see if it continues.
Update 3: Got another reboot at 400mhz. I am now testing 100mhz-1000mhz at 1.275v Core and 1.100v Internal for all frequencies, this should rule out any voltage issues.
Update 4: Made a spreadsheet with my findings, it does not seem to be a voltage issue.
Update 5: Scratch that, I have been using a [email protected] screen off profile for the last 20h... No black screen of death or random reboots. Next up is [email protected]
Update 6: [email protected] is unstable, rebooted after 3 hours. Testing [email protected], 6 hours in and no reboots yet.
Update 7: [email protected] seems to be stable, 24 hours and no reboots yet.
Old text
Click to expand...
Click to collapse
Here is a spreadsheet of my current findings.
My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here, but for some odd reason this (seems to have) fixed it for me. Although, on EG22 I also got a lot of random reboots, so maybe I have a different issue.
I did not get reboots on ED12, EE03, or EF02..
EG22, EH06, and EH17 randomly reboot for me.
I thought it might be similiar to the sleep of death phones would get going from 100 Mhz to deep sleep and also tried boosting to 200 Mhz on EH17 but it didn't help. It may be related and your discovery may aid Devs in fixing the problem If it is still there when source is released.
Sent from my SPH-D700 using XDA App
I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium
xopher.hunter said:
I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
+1 That's what I think.
That would explain why my phone never reboots with the screen on.
I think we may be onto something in this thread.
Sent from my SPH-D700 using XDA App
Agreed. My phone has always randomly rebooted when the screen is off. I set the minimum to 400 Mhz as well. Will let you know what goes down.
Someone should point the SamSprint devs to this thread lol. That would be amusing if it was in fact the problem/solution to random reboots.
Sent from my SPH-D700 using xda premium
Ok, so far 400mhz screen off has been stable, 12:56 on battery, and 1:01 screen on time.
I noticed something.. Here is what CPU Spy says:
1000mhz: 00:55:03
400mhz: 1:35:09
Deep Sleep: 9:22:42
I reset the stats once, which is why 1000mhz is 6 min different from the screen on time.
The phone was asleep for 11:55, but it was only in deep sleep for 9:22, what this tells me is when the screen is off and the phone needs to "do something" (I have Skype open 24/7, and 3 accounts in k9)it will jump up to 400mhz (or normally, anywhere between 100-1000mhz) for a time until it is finished, and then drop back into deep sleep.
It might be worth a try to bump up the voltage for 100mhz and 200mhz and see if that helps anything.
So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?
when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?
If its really this simple as far as clock and voltage how the hell does Samsung not find that.
Sent from my SPH-D700 using xda premium
What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.
ss4rob said:
What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.
Click to expand...
Click to collapse
SetCPU is free for xda members
Sent from my SPH-D700 using Tapatalk
I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard
radugb said:
So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?
Click to expand...
Click to collapse
What scaling are you using?
This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.
omair2005 said:
when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?
Click to expand...
Click to collapse
Good catch. Here are the voltages on EH06 (as reported by Tegrak):
1000mhz
Core Voltage: 1275mv
Internal Voltage: 1100mv
800mhz
Core Voltage: 1200mv
Internal Voltage: 1100mv
400mhz
Core Voltage: 1050mv
Internal Voltage: 1100mv
200mhz
Core Voltage: 950mv
Internal Voltage: 1100mv
100mhz
Core Voltage: 950mv
Internal Voltage: 1000mv
Could someone list out the stock voltages on EC05?
Lord-Anubis said:
I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard
Click to expand...
Click to collapse
That is what I thought at first... But then I tried the EF02, and EE03 modems and still experienced reboots (I am currently on the EE03 modem).
poit said:
This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.
Click to expand...
Click to collapse
While this is true (for now) it could lead to a more viable fix. If the voltage actually is lower in GB, that could be at least part of the problem.
I'm wondering what is the battery life difference between 1000MHz (as max) and overclocked 1400MHz?
In most [low-end] phones little OC consumes a lot of power, but I don't see this issue in SGS.
Are you using your phone overclocked? How long last your battery?
opt1user said:
I'm wondering what is the battery life difference between 1000MHz (as max) and overclocked 1400MHz?
In most [low-end] phones little OC consumes a lot of power, but I don't see this issue in SGS.
Are you using your phone overclocked? How long last your battery?
Click to expand...
Click to collapse
I dont know why would you do that... I use SGS in max 800mhz(underclocked) and its perfectly fast... But regarding your question, prolly would be about a day and a half of battery with those settings on OC.
I think its perfectly fast as it is but to your question ... i think it really depends on how you use it i dont belive it will last more than a day of it is used as intended ...
Gonzas10 said:
I dont know why would you do that... I use SGS in max 800mhz(underclocked) and its perfectly fast... But regarding your question, prolly would be about a day and a half of battery with those settings on OC.
Click to expand...
Click to collapse
I tried underclocking my SGS (aokp build 28) to 800mhz, and it crawled, never got to the first unicorn in past the boot animation. seriously.
I over locked up to 1200, no over volt. Don't feel any impact on batterry since phone is only less 1 percent of time in that CPU state.Rest of time it is idling.
Sent from my GT-I9000 using xda premium
im running SGS with 1000MHz and i don't need more power on my phone :S
Not much diff actually
Sent from my GT-I9100 using XDA
there can be a difference in battery life, but there does not necessarily have to be one I assume... after all, it is only the maximum available for the processor, most of te time it will not run at that speed... I for one do not overclock my phone (actually, I have underclocked it to 800mhz) since I have no need for these speeds (just using my phone for messaging and some browsing)...
please correct me if I am wrong since I do not know much about how the SGS processor exactly works
i cant see how it shouldnt impact battery.