I'm wondering what settings people are using for undervolting. I'm running Neutrino v2.5 GT with the patch and supercharger. Seems like if I set anything above 50 I get a reboot. Kinda a total noob when it comes to UV so any help would be appreciated
I would like to know this too please.
Sent from my MB860 using XDA
I'm currently running this:
1300: -150
1200: -100
1100: -50
1000: -50
800: -50
456: -100
216: -150
I've tried lower but I started getting reboots, at these voltages it's been good for a few days now.
Every Atrix isn't the same so while one set may work for one persons phone it may not on yours. One thing, though. DO NOT break the 100mv limit. Meaning if 1GHz is at 1000mv, then the step below it (912MHz if you're on a 1GHz kernel) shouldn't go below 900mv. This is a limit on the Tegra 2 set by Nvidia and going passed the 100mv limit cancels out undervolting across the board. Meaning if 1GHz is at 1000mv and you set 912MHz to 875mv or lower, it won't matter what the undervolting application says. Your phone will NOT be undervolted. I'm able to under volt fairly well and I usually stick to 1GHz kernels to save on battery. If you're using a 1GHz kernel, try leaving the first two frequencies alone (don't change 1GHz or 912 MHz). Here's what I've been using on CM9 with faux123's 1GHz kernel:
1GHz - no change
912MHz - 25
750MHz - 50
608MHz - 95
456MHz - 105
312MHz - 115
216MHz - 135
This has been stable for me since I got my Atrix and works really well on a couple of my friend's Atrix. If this causes reboots then set 912MHz back to no change at 950mv and I can almost promise you the problem will be fixed. Also, if you're a battery saving whore like I am and you're on AT&T, flash the N_01.100.00R European radio. This will allow you to set your phone to GSM Only by dialing *#*#4636#*#* and changing GSM auto (PRL) and use the EDGE (2G) service providing you with MUCH better battery life. If you need the higher speeds then switch back or simply reboot the phone. Hope this information helps.
On a side note, underclocking is another useful way to conserve battery. I never did this on GB ROMs as everything became terribly slow, but on ICS, underclocking barely hinders performance. I have mine underclocked at 750MHz and in terms on scrolling, opening apps, playing games, web surfing, even moving through homescreens, it still outperformed any GB ROM I've used at 1GHz and even 1.3GHz. Even benchmarks are fairly the same. Going on 53 hours with HEAVY usage. e.g. Web browsing all day, texting, few phone calls, and playing games.
Sent from my AT&T CM9 MB860 on EDGE
I'm on Turl's CM9 build v9 with faux123's 1GHz kernel and I undervolt to:
1GHz - 950 mV (-50)
912 - 930 mV (-20)
750 - 830 mV (-70)
608 - 730 mV (-120)
456 - 630 mV (-170)
312 - 530 mV (-245)
216 - 430 mV (-320)
I tried an extreme that someone else had on their Atrix with 216 MHz at 400 mV, and 100mV increment up and my phone became unstable (with 912 MHz at 900mV). Following some other people's advice to undervolt less at 912MHz I arrived at my current setting that is stable for my phone.
I'm using Neutrino 2.2 with the latest faux kernel because I couldn't get phone to deep sleep with 2.5 even with the update installed.
I used pimp my cpu and managed these undervolts, it wouldn't let me go past -250mV is that normal?
1300Mhz -125 mV = 1175 mV
1200Mhz -100 mV = 1100 mV
1100Mhz -50 mV = 1050 mV
1000Mhz -50 mV = 950 mV
800Mhz - 175 mV = 725 mV
456 Mhz - 200 mV = 600 mV
216 Mhz - 250 mV = 500 mV
I was quite surprised of the jump in mV to 1000Mhz, it just wouldn't take any lower voltage without freezing. But I have extended my battery life loads by using pimpmycpu its cool as. Also from the above post does that mean my 800Mhz undervolt is ok or not?
Enkidu1978 said:
I'm using Neutrino 2.2 with the latest faux kernel because I couldn't get phone to deep sleep with 2.5 even with the update installed.
I used pimp my cpu and managed these undervolts, it wouldn't let me go past -250mV is that normal?
1300Mhz -125 mV = 1175 mV
1200Mhz -100 mV = 1100 mV
1100Mhz -50 mV = 1050 mV
1000Mhz -50 mV = 950 mV
800Mhz - 175 mV = 725 mV
456 Mhz - 200 mV = 600 mV
216 Mhz - 250 mV = 500 mV
I was quite surprised of the jump in mV to 1000Mhz, it just wouldn't take any lower voltage without freezing. But I have extended my battery life loads by using pimpmycpu its cool as. Also from the above post does that mean my 800Mhz undervolt is ok or not?
Click to expand...
Click to collapse
Your phone isn't undervolted at all since you broke the 100mv limit. Might show that you are, but the phone is still running with high power consumption.
Also, if you wanna go lower, get SetCPU. Goes all the way down to -500mv and doesn't lock you to increments of 25. You can set any value such as -69mv, -146mv, etc.
Sent from my AT&T CM9 MB860 on EDGE
I'm using the 1.3ghz kernel anyone got safe recommendations not breaking the 100mw rule
Sent from Atrix 4g Neutrino 2.5
I'm running faux 1.3 too n that's wat I'm trying to figure out too. Because according to what you're saying I'd only be able to UV at lowest 2 or 3 speeds
squee666 said:
I'm using the 1.3ghz kernel anyone got safe recommendations not breaking the 100mw rule
Sent from Atrix 4g Neutrino 2.5
Click to expand...
Click to collapse
As I stated earlier, not ever phone is built the same. What works for someone else may not work for you.
CREAPFACE said:
I'm running faux 1.3 too n that's wat I'm trying to figure out too. Because according to what you're saying I'd only be able to UV at lowest 2 or 3 speeds
Click to expand...
Click to collapse
The best idea is to do minimal undervolting on higher frequencies as they need more power and do the more intense undervolting on lower frequencies.
I changed mine up, a bit. This is what I'm working with, now:
1GH no change = 1000mv
912MHz -25mv = 925mv
750MHz -50mv = 850mv
608MHz -100mv = 750mv
456MHz -150mv = 650mv
312MHz -225mv = 550mv
216MHz -300mv = 450mv
To me, undervolting is a way to mainly save power, further, when the screen is off while conserving as much as I can when I'm actually using the phone.
Sent from my AT&T CM9 MB860 on EDGE
Pretty sure it just the rom. Switched to redpill to test it and with undervolting I had %60 battery left after all day of heavy use.
Im on jokersax 0.33, installed setcpu, but i dont see voltages menu at all.
Can somebody guide me pls
Sent from my MB860 using XDA
Its the 3rd tab at the top. It says main, then profiles, then voltages. Not sure if its on there if your not running a custom kernel
CREAPFACE said:
Its the 3rd tab at the top. It says main, then profiles, then voltages. Not sure if its on there if your not running a custom kernel
Click to expand...
Click to collapse
Thats y maybe,.. i am on kernel which comes with jokersax ROM, so probably i cannot get it ;(
EDIT: Yes, i installed http://www.jokersax.com/upload/Atrix-CM9-Kernel-025b-ext4-1.00GHz.zip and i got Voltage tab.
I am testing Neroga settings now.
akyboy said:
Thats y maybe,.. i am on kernel which comes with jokersax ROM, so probably i cannot get it ;(
EDIT: Yes, i installed http://www.jokersax.com/upload/Atrix-CM9-Kernel-025b-ext4-1.00GHz.zip and i got Voltage tab.
I am testing Neroga settings now.
Click to expand...
Click to collapse
Phone froze 2 times and restarted, restoring from standby.
Any ideas what i should change?
Tnx
You have to start out pretty low and work ur way up til u don't get any reboots. Also I'd try faux123's kernel the 1.3 is where its at
I couldn't find any voltage tab
I've tried the standard kernel that comes with the neutrino and faux 1,45ghz for cm7...
Any suggestion?
Neroga said:
Every Atrix isn't the same so while one set may work for one persons phone it may not on yours. One thing, though. DO NOT break the 100mv limit. Meaning if 1GHz is at 1000mv, then the step below it (912MHz if you're on a 1GHz kernel) shouldn't go below 900mv. This is a limit on the Tegra 2 set by Nvidia and going passed the 100mv limit cancels out undervolting across the board. Meaning if 1GHz is at 1000mv and you set 912MHz to 875mv or lower, it won't matter what the undervolting application says. Your phone will NOT be undervolted. I'm able to under volt fairly well and I usually stick to 1GHz kernels to save on battery. If you're using a 1GHz kernel, try leaving the first two frequencies alone (don't change 1GHz or 912 MHz). Here's what I've been using on CM9 with faux123's 1GHz kernel:
1GHz - no change
912MHz - 25
750MHz - 50
608MHz - 95
456MHz - 105
312MHz - 115
216MHz - 135
This has been stable for me since I got my Atrix and works really well on a couple of my friend's Atrix. If this causes reboots then set 912MHz back to no change at 950mv and I can almost promise you the problem will be fixed. Also, if you're a battery saving whore like I am and you're on AT&T, flash the N_01.100.00R European radio. This will allow you to set your phone to GSM Only by dialing *#*#4636#*#* and changing GSM auto (PRL) and use the EDGE (2G) service providing you with MUCH better battery life. If you need the higher speeds then switch back or simply reboot the phone. Hope this information helps.
On a side note, underclocking is another useful way to conserve battery. I never did this on GB ROMs as everything became terribly slow, but on ICS, underclocking barely hinders performance. I have mine underclocked at 750MHz and in terms on scrolling, opening apps, playing games, web surfing, even moving through homescreens, it still outperformed any GB ROM I've used at 1GHz and even 1.3GHz. Even benchmarks are fairly the same. Going on 53 hours with HEAVY usage. e.g. Web browsing all day, texting, few phone calls, and playing games.
Sent from my AT&T CM9 MB860 on EDGE
Click to expand...
Click to collapse
Can you explain exactly how you set your phone to 2G only? Reason I'm asking is 'cause I flashed the radio you mentioned and tried to use 2G only, but it keeps resetting back to gsm/cdma (prl).
Switched to neutrino EE n haven't had a problem since. Battery will last me 2 days
Related
tegrak promised he was going to upgrade his tegrak overclock app to work with all kernels and it looks like he's delivered! (see http://forum.xda-developers.com/showthread.php?t=1101355
I'd installed the free version as tegrak suggested a couple months back to see if it would work with my phone. It didn't, but yesterday, it upgraded to version 0.6.0.9. I had a bullet kernel that allows OC to 1.2 ghz with no voltage adjustments. The free version doesn't OC but will let you know if the paid version will work with your phone.
The paid version ($2) works. At least on my phone it does. Maybe no need for special kernels anymore. I haven't tried it with a rom that doesn't support OCing and overvolting yet but I'm going to do that this weekend.
The higher speeds need overvolting and there's no directions on how to do it. tegrak overclock will officially only let you go to 1.3 ghz but if you select the fine "optimization" you can go way up beyond that. I immediately zoomed it up to 1600 mhz with no voltage adjustments and the phone locked up and started buzzing. I had to pull the battery and reboot. Don't do that! Go up a little at a time and then let the stability test run (pull down notification screen to see how many seconds are left.)
There are buttons to adjust by small amounts. You should be able to set it at 1.4 ghz with a little overvolting without too much trouble. Right now my phone is stable at 1524 mhz and core voltage of 1361 mv using an "on demand" profile of 100-1524mhz and it's not hot. Quadrant score at that setting was 3201. That's pretty good for a kernel that only supports OC to 1200 mhz.
I couldn't get to 1600 yet without locking up the phone -- needs more overvolting I figure.
If you have sgs overclock, after you up the speed, it will have the top speed bar at the bottom 100mhz and you will have to drag it up there. I don't know why this should make a difference but my quadrant score was in the 2700s before I did it.
Write down your figures 'cause if the phone locks up and you have to pull battery and reboot, the phone will ask you if you really want that speed that didn't work, and when you say "no" you'll be back at the beginning again.
There is more discussion in the 19000 forum on tegrak's 2.3.4 kernel (for I9000) and the OC app. according to tegrak's guide, the Galaxy S can be stably undervolted using his utility at various speeds and I guess save battery life:
speed standard core voltage undervolt
1000mhz 1275 mv 1225 mv
800mhz 1200 mv 1125 mv
400mhz 1050mv 950mv
200mhz 950mv 825mv
100mhz 950mv 800mv
There is a dialog in the app to set the voltage for each of these speeds in addition to setting the OC speed and voltage. I'm not sure whether tegrak has tested this on the various flavors of Galaxy S or whether he means the I9000. I'll just have to see.
here is his figure for a 1200mhz OC.
speed standard core voltage overvolt
1200mhz 1275 1310
Seems to be working good!
All nonsense and misspelled words courtesy of my unsupported samsung device.
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. The tab will not show up if your kernel does not have these features. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the voltage adjustment that the kernel you are using has either the HAVS or SVS sysfs interface implemented. If it does not, it will not work.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
Looks neat. I would try it but I am a complete noob at kernel clocking and voltage. Is there a guide for N1 volt changing?
I would give a try... looks nice GUI... emmm... does this same like SS4N1?
Androidity3000 said:
Looks neat. I would try it but I am a complete noob at kernel clocking and voltage. Is there a guide for N1 volt changing?
Click to expand...
Click to collapse
It's a lot of trial and error, you have to find the lowest voltages you can while still being stable and its different for all phones. Here is an example of a HAVS table that is stable on about 50% of dIncs (which share the same processor with the n1, so I'm guessing your voltages may be similar)
128000 850 875
245000 850 875
384000 875 900
422400 875 950
460800 875 975
499200 875 975
537600 875 975
576000 875 975
614400 875 1000
652800 875 1025
691200 900 1050
729600 900 1075
768000 925 1100
806400 1100 1150
844800 1100 1150
883200 1100 1150
921600 1125 1200
960000 1150 1200
998400 1175 1225
1036800 1200 1225
1075200 1225 1250
1113600 1225 1250
You can use these as a starting point. They may or may not be stable for you. If you're running an SVS kernel (only one set of voltages comes up when you start the app, use the voltages on the right of the table.
clustered said:
I would give a try... looks nice GUI... emmm... does this same like SS4N1?
Click to expand...
Click to collapse
I'm unfamiliar with ss4n1, but this is an app that is used to adjust cpu voltages so that you may under or overvolt the cpu.
chad0989 said:
It's a lot of trial and error, you have to find the lowest voltages you can while still being stable and its different for all phones. Here is an example of a HAVS table that is stable on about 50% of dIncs (which share the same processor with the n1, so I'm guessing your voltages may be similar)
128000 850 875
245000 850 875
384000 875 900
422400 875 950
460800 875 975
499200 875 975
537600 875 975
576000 875 975
614400 875 1000
652800 875 1025
691200 900 1050
729600 900 1075
768000 925 1100
806400 1100 1150
844800 1100 1150
883200 1100 1150
921600 1125 1200
960000 1150 1200
998400 1175 1225
1036800 1200 1225
1075200 1225 1250
1113600 1225 1250
You can use these as a starting point. They may or may not be stable for you. If you're running an SVS kernel (only one set of voltages comes up when you start the app, use the voltages on the right of the table.
Click to expand...
Click to collapse
My N1 runs fine with this settings, thanks.
Sent from my Nexus One using XDA Premium App
IncrediControl v1.3
Major changes include:
Ad Free has now been turned into a key that removes the ads from the free version. This allows donors who have downloaded the ad free version from the site to update through the market.
HAVS voltage checking. Minimum voltages can no longer be set higher than maximum voltages.
Boot voltages are now stored in the application’s data directory. Boot settings will now persist if you update your ROM or restore the application and data from a backup.
I'm new to undervolting background. I remember reading about havs before but forget most of what it is. .. . . .can I ask when setting the voltages what is the correspondance of havs voltage to normal voltage? It appears to be higher by most ppl, is there a set amount which it should be higher than original undervolt per frequency?
Jandyman said:
I'm new to undervolting background. I remember reading about havs before but forget most of what it is. .. . . .can I ask when setting the voltages what is the correspondance of havs voltage to normal voltage? It appears to be higher by most ppl, is there a set amount which it should be higher than original undervolt per frequency?
Click to expand...
Click to collapse
Most generally set the voltages lower than whatever undervolt is provided by the kernel. It takes a lot of trial and error to get the voltages as low as possible while still being stable. If you look above I posted an example table that you may use as a starting guide.
chad0989 said:
Most generally set the voltages lower than whatever undervolt is provided by the kernel. It takes a lot of trial and error to get the voltages as low as possible while still being stable. If you look above I posted an example table that you may use as a starting guide.
Click to expand...
Click to collapse
Thanks. I just realised my kernal doesn't support havs so its tab/settings are irrelvant anyway XD But I used your table but then found another table in a thread for a kernal for my phone with voltages much lower again and I adopted those values without any stability problems so far
EDiT:My second question has been answeres . .read changelog now that I kno I can restore my custom Voltage table through titanium backup this is now one my my favourite utilities
Wait . . .just realised that 'set on boot' isn't working for me :/
When I apply changes and click set on boot and restart my changes are lost and voltages are back to default! it does say 'boot settings found' though
And another question on a related note, let's say voltage at 122 is 800mv. . . .and voltage at 192 is also 800mv. Does this mean the battery drainage of running at 122 and 192 is identical?
(Because if this is the case it would mean by always setting the minumun frequencies at the highest voltage of a certain mv range you get the same battery drain but tasks get done faster so its being drained for less time . . .saving battery?)
Jandyman said:
Wait . . .just realised that 'set on boot' isn't working for me :/
When I apply changes and click set on boot and restart my changes are lost and voltages are back to default! it does say 'boot settings found' though
And another question on a related note, let's say voltage at 122 is 800mv. . . .and voltage at 192 is also 800mv. Does this mean the battery drainage of running at 122 and 192 is identical?
(Because if this is the case it would mean by always setting the minumun frequencies at the highest voltage of a certain mv range you get the same battery drain but tasks get done faster so its being drained for less time . . .saving battery?)
Click to expand...
Click to collapse
Are you clicking set on boot and then clicking apply afterwards? You must check the box and then click apply. Try restoring defaults and trying again.
Also, a higher frequency running at the same voltage will draw more power than a lower frequency at the same voltage. While the voltage is the same, the current draw at a higher frequency is more = more drain.
IncrediControl v1.4:
This is mostly a bug fix release but I have also added:
Automatic detection of the minimum and maximum voltages supported by your kernel
Unless any more bugs arise, the next release will have some new goodies to play with...
http://www.incredikernel.com or from the market.
The first two values in incredicontrol are a digit shorter than the rest, what are these for?
Are these the pm mode cpu freq values? Or should der be a 0 at the end.
Jandyman said:
The first two values in incredicontrol are a digit shorter than the rest, what are these for?
Are these the pm mode cpu freq values? Or should der be a 0 at the end.
Click to expand...
Click to collapse
Post the frequency table you're getting. Thanks.
Here you go
Jandyman said:
Here you go
Click to expand...
Click to collapse
Looks like the kernel dev made those frequencies usable. If you utilize them then you can adjust the voltages. If you don't use them then you can leave them. What kernel?
Sent from my ADR6300 using XDA App
Ah ok, in that case because the frequency is so much lower I should be able to put the voltage wayyyy down am I right? Its already undervolted by about -50)
I'm using UmaroKernal 1.06
Jandyman said:
Ah ok, in that case because the frequency is so much lower I should be able to put the voltage wayyyy down am I right? Its already undervolted by about -50)
I'm using UmaroKernal 1.06
Click to expand...
Click to collapse
In theory you should be able to go pretty low on them. But it only matters if you actually use those frequencies. What is your minimum frequency set at?
Sent from my ADR6300 using XDA App
chad0989 said:
In theory you should be able to go pretty low on them. But it only matters if you actually use those frequencies. What is your minimum frequency set at?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Well I'm not using them atm because I was afraid they would cause instability on wake mode and in sleep mode I taught they would keep the phone out of om state for longer than what was worth the battery saving.
At the moment the minimum frequency for both screen on and screen on is 122880 @775mv
After some research, I've chosen to run -50 up to 1,000Mhz.
I've ran V.11 HL at -50 from 100 to 1000 with NO problems. Then I tried ML at -50 across the board with no problems and now I'm running LL at -50.
My question is whether anyone has compiled user settings into one location to find patterns. That is, does 100Mhz generally perform better at -25 or -250mv? How about 200, or 400...?
Has this been attempted?
My hope is to find a trend to aide in finding the 'best' settings based on many users.
ML Settings
I'll start.
Now running:
Mhz UV/OC
1,400 -0
1,300 -50
1,200 -50
1,000 -0
800 -25
400 -25
200 -25
100 -25
Problems encountered
None after 12hrs
Phone did some funny things when attempting to fix brightness to high while outside. This was while using the above settings on the Low Leak platform. I am now reverting back to the High Leak to play around some more.
I've run -25 from 100-1,000Mhz for nearly 24hours without any problems.
Here's what I've had setup for a few weeks and I have zero problems whatsoever. Using Medium Leakage.
1300 MHz - [email protected] 217 MHz - 1.400V / -50mV
1200 MHz - [email protected] 200 MHz - 1.350V / -50mV
1000 MHz - [email protected] 200 MHz - 1.250V / -50mV
800 MHz - [email protected] 200 MHz - 1.200V / -75mV
400 MHz - [email protected] 200 MHz - 1.050V / -100mV
200 MHz - [email protected] 200 MHz - 0.950V / -150mV
100 MHz - [email protected] 100 MHz - 0.950V / -200mV
I would like to know what kind of battery life everyone's getting. With light use, my phone drains 5% an hour.
The new glitch 12 has some recommended setting in the op.
Good staring point
sent from outerspace
Wait...your settings are right in line with op.
My bad!
sent from outerspace
Updated
Samsung Fascinate
CDMA
ROM ED05
MIUI 1.9.16
Glitch v12 ML (9/15/11)
Voltage Control
deadline / ondemand
200-1300
1300 -25
1200 -25
1000 -50
800 -50
400 -75
200 -75
Just set it last night. Will report back on progress later.
dblash,
From MIUI 1.8.26 to 1.9.16; from using Glitch to non Glitch, I average about 18 hours of battery life under 'normal' use. normal should be understood as about 30-45min heavy usage in the morning, about 15min over lunch, and about 1hr of heavy use in the evening. My screen brightness is usually set to full brightness too.
My settings are
1.4GHz / -50mV
1.3GHz / -50mV
1.2GHz / -50mV
1.0GHz / -50mV
800MHz / -75mV
400MHz / 75mV
200MHz / 100mV
Sent from my SCH-I500 using XDA App
Keep having little Glitches with the Newest Glitch kernel. Decided to remove it and troubles go away. I'm currently running stock (MIUI 1.9.16) settings without any kernel
What are the glitches your having?
Sent from my SCH-I500 using XDA App
dblash said:
Here's what I've had setup for a few weeks and I have zero problems whatsoever. Using Medium Leakage.
1300 MHz - [email protected] 217 MHz - 1.400V / -50mV
1200 MHz - [email protected] 200 MHz - 1.350V / -50mV
1000 MHz - [email protected] 200 MHz - 1.250V / -50mV
800 MHz - [email protected] 200 MHz - 1.200V / -75mV
400 MHz - [email protected] 200 MHz - 1.050V / -100mV
200 MHz - [email protected] 200 MHz - 0.950V / -150mV
100 MHz - [email protected] 100 MHz - 0.950V / -200mV
I would like to know what kind of battery life everyone's getting. With light use, my phone drains 5% an hour.
Click to expand...
Click to collapse
pretty similar to this voltages, too lazy to type it out.
Sent from my MIUI SCH-i500
Most recent glitch was Google+ fc-ing 4 times when trying to type. Reflashed MIUI and fc goes away. There were several less critical issues as well.
Sent from my SCH-I500 using XDA App
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
I'd go lower, but haven't really bothered.
Sent from my SCH-I500 using XDA App
Glitch updated last night and fixed all of the lag issues, things are working much much better now.
just curious about what might be a safe undervolt range to set my CPU at? I've got the 1.3ghz set at -75 and the middle frequencies at -100. I seem to be getting a little better battery life no forcecloses yet. I had a Droid x last time and the oc app just had a selection of extreme undervolt but I never remembered what the voltages were
Proud graduate of flashaholics anonymous
Undervolting depends on CPU Type. Theirs no specific UV for a CPU because their all different.
To find out what is best for your phone try different uv's and see what works best.
Sent from my SCH-I500 using XDA App
Since moving up to CM7 I can't see any difference when undervolting. Could tell a difference when on FROYO however.
I'm assuming the you want to be a lower mV at higher mhz and a higher mV at a lower mhz? Correct?
Keuka79 said:
just curious about what might be a safe undervolt range to set my CPU at? I've got the 1.3ghz set at -75 and the middle frequencies at -100. I seem to be getting a little better battery life no forcecloses yet. I had a Droid x last time and the oc app just had a selection of extreme undervolt but I never remembered what the voltages were
Proud graduate of flashaholics anonymous
Click to expand...
Click to collapse
those are my exact settings aswell... I see some going -150 uv on the lower frequencies, but i have not tried it yet. I know from 1000-1300mhz -75 is all i can go without freezing.
Yeah I tried to push 1.0 to 1.3 over -75 and it locks up and reboots.
Proud graduate of flashaholics anonymous
So I followed Droidstyles "how to" guide on how to put ics on my phone.( http://forum.xda-developers.com/showthread.php?t=1238070 )
I love it so far but now it leaves me wanting more from my phone. Im trying to learn how to overclock my cpu.
I currently have Teamhacksung 6.1 on my phone. And in my "about phone" section my kernel version reads
3.0.8-g0d5605e-dirty
[email protected] #1
Not too sure if those are the same thing. Can i overclock my CPU with the current kernel i have or do i have to put another one on my phone?
Thanks alot for any replies!
Djp2012 said:
So I followed Droidstyles "how to" guide on how to put ics on my phone.( http://forum.xda-developers.com/showthread.php?t=1238070 )
I love it so far but now it leaves me wanting more from my phone. Im trying to learn how to overclock my cpu.
I currently have Teamhacksung 6.1 on my phone. And in my "about phone" section my kernel version reads
3.0.8-g0d5605e-dirty
[email protected] #1
Not too sure if those are the same thing. Can i overclock my CPU with the current kernel i have or do i have to put another one on my phone?
Thanks alot for any replies!
Click to expand...
Click to collapse
Flash Glitch v14 located in the Development forum.
Please Remember to use nstools for overclocking.
Sent from my SCH-I500 using XDA App
Wow thanks for the fast reply.
Do i have to uninstall any of the other kernels I have or go back to any versions?
Or can I download glitch v14 and use odin to flash it from the version im on?
Djp2012 said:
Wow thanks for the fast reply.
Do i have to uninstall any of the other kernels I have or go back to any versions?
Or can I download glitch v14 and use odin to flash it from the version im on?
Click to expand...
Click to collapse
Flash via CWM.
Hold power button
Select 'Reboot'
then select 'Reboot Recovery'
Then flash.
No Odin needed.
That's it.
You cant uninstall a kernel, it boots the phone. You can flash different kernels though. (e.g Glitch Kernel)
Be careful when overclocking. Especially with LiveOC.
If you do not know how liveOC works, please, do not use it.
Have fun
Sent from my SCH-I500 using XDA App
Wow so i got it to work just by doing what you said. I know there is benefits for overclocking as well as some consequences if i dont do it right.
Is there anywhere i could go to read up more on how liveOC works on the fascinate? Like i said, i really want that extra edge that I can get from doing so
Also I downloaded NSTOOLS to get me started
Djp2012 said:
Wow so i got it to work just by doing what you said. I know there is benefits for overclocking as well as some consequences if i dont do it right.
Is there anywhere i could go to read up more on how liveOC works on the fascinate? Like i said, i really want that extra edge that I can get from doing so
Also I downloaded NSTOOLS to get me started
Click to expand...
Click to collapse
Here's the thread (quoted it to save you time)
Tk-Glitch said:
LiveOC and Custom Voltage guide by TkGlitch
for Glitch kernel V14
{
"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"
}
Warning!
Overclocking is dangerous and is meant only for experienced users!
1- Introduction :
The "normal" overclocking system on SGS til now was the addition of some frequency steps past the stock 1GHz step. V13 kernel was using 7 overclocked steps
to push the maximum selectable speed to 1.7GHz.
In V14, less overclocked steps are present, but you can still overclock to 1.7GHz if you want (and if your phone is able to do it), and even up to 2.25GHz as a maximum.
You will need NSTools to use LiveOC and custom Voltage features in Glitch kernel V14.
To begin with, I'll explain you some basic things you have to know.
2- Clocks :
The CPU speed is the result of a bus speed and a multiplier.
Bus speed is linked to and equal to GPU and RAM speed.
The multiplier is per step and hardcoded by the kernel developer.
It does look like that : CPU speed = bus speed x multiplier.
Here are my values in V14 :
1500 MHz = 200 x 7.5
1400 MHz = 200 x 7
1300 MHz = 200 x 6.5
1200 MHz = 200 x 6
1000 MHz = 200 x 5
800 MHz = 200 x 4
400 MHz = 200 x 2
200 MHz = 200 x 1
100 MHz = 100 x 1
LiveOC gives you the access to direct and on-the-fly bus overclocking by 1% steps (150% being the maximum available). I'll say it again : BUS overclocking !
Though, it'll overclock the bus on all the steps at the same time, for the same percentage.
We'll talk about that later.
So if I want to overclock my 1GHz step to 1.1GHz, I'll have to select 1GHz as max frequency, and push LiveOC to 110%.
My bus speed beeing overclocked by 10% will give the following :
220 x 5 (1GHz multiplier) = 1100 MHz.
If you want to go higher than 1.5GHz, it's the same :
Set 1500 MHz as maximum frequency (for example), and push LiveOC. Let's say to 110%. You will get the following :
220 x 7.5 (1.5GHz multiplier) = 1650 MHz.
Pushing it to 114% will give 1710 MHz (228MHz bus) and so on, up to 150% giving 2250 MHz running an inachievable 300MHz bus.
3- The limits :
THE MAIN LIMIT AND PHONE KILLER IS HIGH TEMPERATURE. WARM IS OK, HOT IS TOO HOT. DON'T PLAY STUPID.
Obviously, so much control over the bus speed, frozen til now to what the kernel developer set, will also give you the ability to find the limits of your chip.
The main clocking limit is generally the RAM, corrupting itself when the bus speed is too high. And since the GPU uses the RAM as well, it'll become crashy too. That's why I have decided to add some steps with a bigger multiplier, to lower the bus for a higher CPU frequency.
The bus speed limits for you will be anywhere between 240 and 270 Mhz, depending on your device potential (higher and lower exists but rare).
Average is 240 MHz.
The CPU speed limits will be anywhere between 1300 and 1800 MHz (higher and lower exists but rare as well).
Average is 1400 MHz.
With that in mind, I wouldn't go too far past 130% (giving 260MHz bus speed).
4- The sweet spot :
What you want when overclocking is to get the best balance for each part. Since the bus is linked to RAM and GPU, you obviously want it as high as possible for gaming, video playing, web browsing etc. (even more now with GPU acceleration in Android 4.0+). Though, as you know already if you've read this guide til now, all steps in V14 are using the stock 200MHz frequency.
So what to do if I want a lower CPU speed with a higher bus/GPU speed ? Simple ! Just select a lower frequency step as starting point.
Let's say we want 250 MHz bus speed, so we'll use 125% LiveOC :
Using 800MHz step, you'll get 1GHz.
Using 1GHz step, you'll get 1.250GHz.
Using 1.2GHz step, you'll get 1.500GHz.
Using 1.3GHz step, you'll get 1.625GHz.
Using 1.4GHz step, you'll get 1.750GHz.
Using 1.5GHz step, you'll get 1.875GHz.
5- The issues :
With a new overclocking system obviously comes some new problems related to it.
With the ability to fine tune the frequencies, you'll find that some frequencies are buggy somewhat, giving low performances. For example, using 115% Live OC with the 1.3GHz step will give some poor performances, when 114 and 116% won't. It could be a NSTools issue, but I think it has more to do with the hardware. It's well known that on CPUs some frequencies or even frequency ranges can be buggy, unstable, or slow. If you encounter that, try to add or remove a percent to LiveOC.
As said earlier, LiveOC will overclock the bus for all steps at the same time by the same amount of %.
Knowing that, you'll have to adapt your voltages for all the frequencies to stay stable, and this for any sensible change on LiveOC percentage.
6- Custom Voltage :
What would be LiveOC without Custom Voltages ?!
I did add leakage values to Glitch kernel features when I saw that some phones were overclocking much better with the right balance between ARM and Int voltages, depending on the phone, with very different results. The leakage value was basically that : balance between the two.
Well, as you probably know if you did read the changelogs, you have now the capacity to overvolt/undervolt both the ARM voltage (the CPU voltage you know well already), and the Int (internal) voltage. The last one is the voltage going to the GPU/memory controller, and will need to be tweaked accordingly to your phone.
As a starting point, here are the Int voltage values I was using for each leakage, adapted for V14 new frequency table :
HIGH LEAKAGE :
1500 : 1.225
1400 : 1.200
1300 : 1.175
1200 : 1.150
1000 : 1.125
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
MEDIUM LEAKAGE :
1500 : 1.200
1400 : 1.175
1300 : 1.150
1200 : 1.125
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
LOW LEAKAGE :
1500 : 1.175
1400 : 1.150
1300 : 1.125
1200 : 1.100
1000 : 1.100
800 : 1.100
400 : 1.100
200 : 1.100
100 : 1.000
Of course, using LiveOC will force you to change these voltages accordingly.
Here are some advices about this :
- Try to stay around 1.225 - 1.250V for your highest frequencies;
- Try not to ever go past 1.300V if you don't want to kill your phone quickly;
- Be VERY gentle when tweaking it as it is VERY sensitive;
- Try to follow a more or less linear curve for Int voltage on OC frequencies;
- Going below 1.000V on 100MHz step will generally kill stability with no battery gain.
This guide may change depending on my decisions related to the Glitch kernel development, or to polish / add things to it.
Thanks to Ezekeel from Nexus S section for these awesome tools.
LiveOC : http://forum.xda-developers.com/showthread.php?t=1288015
Custom Voltages : http://forum.xda-developers.com/showthread.php?t=1331610
23/01/2012 - UPDATED TO REFLECT V14-B1 CHANGES.
09/02/2012 - UPDATED TO REFLECT V14-B3 CHANGES.
Click to expand...
Click to collapse
Sent from my SCH-I500 using XDA App
Yeah the guide is highly confusing but ill attempt to decipher it lol. As of now though ill just run the liveoc at %110
And once again thanks for the help, trying to figure it out on my own was driving me nuts
Djp2012 said:
Yeah the guide is highly confusing but ill attempt to decipher it lol. As of now though ill just run the liveoc at %110
And once again thanks for the help, trying to figure it out on my own was driving me nuts
Click to expand...
Click to collapse
I use 110%, stock voltages, and the 1200 max step
Sent from my SCH-I500 using xda premium
whats the downside to just using voltage control and keeping it simple?
droidstyle said:
whats the downside to just using voltage control and keeping it simple?
Click to expand...
Click to collapse
No downside that I can tell
Terminators run on Android
The downside is that it's just utilizing extra frequency steps for CPU overclocking as opposed to being able to fine-tune BUS (CPU+GPU+RAM) speed.
droidstyle said:
whats the downside to just using voltage control and keeping it simple?
Click to expand...
Click to collapse
A bottleneck in the buss.. The old glitch v13 overclocked the buss for you. Check the op in the v13 thread. In this kernel by just overclocking cpu I'm sure your bound to not have an efficient setup as the gpu and buss and ram will be stock
Sent from my SCH-I500 using xda premium
Think of a Manure spreader flinging crap against a brick wall, you're manure is your data, the brick wall is your bottle neck.. Well your bottle neck had a 1 foot hole in it. That's your throughput. You speeding up your spreader without making that hole bigger gives you a wall o' ****.
Just because your overclocking to 1.5ghz dont Mean you'll process any more any quicker.. I can use a performance governer and oc to 1.8 GHz then lock my screen.. What does that give me? A battery sucker that is not throughputing the amount of info the step I'm on suggests i could be
Sent from my SCH-I500 using xda premium
currently 14hrs run time @ 42% battery, 2hrs screen on time. seems fairly efficient and fast idk. I was running nstools and using live oc with no issues previously, but i noticed no improvement over using voltage control. i guess ill switch back to nstools and give live oc another go.
droidstyle said:
currently 14hrs run time @ 42% battery, 2hrs screen on time. seems fairly efficient and fast idk. I was running nstools and using live oc with no issues previously, but i noticed no improvement over using voltage control. i guess ill switch back to nstools and give live oc another go.
Click to expand...
Click to collapse
To tell you the truth, i don't think any overclock will make a noticeable difference. These ics roms with the glitch kernel are so fast to begin with. But when it comes to heavy apps i know you won't see the performance of v13 just using vc. Because v13 overclocked the buss/gpu.
And i had 84% battery after 10 hours today. With at least an hour of screen on. But I'll keep track tomorrow with some screenies if you want to compare
Sent from my SCH-I500 using xda premium