Hey fellow SGS3 users.
Several kernels have undervoltage capabilities for the Galaxy S III.
With this poll I'm trying to get a statistical handle on what the lowest possible voltages are on an average S3 device.
I am currently running at -100mV on all levels and I'm wondering if some people have already spent time testing the limits of the UV that is stable for their device. I haven't tried anymore that -100mV but since I have been running stable on that setting for more than a day, I am considering to decrease the voltage even further.
So if you're using a flat UV on all frequencies, fill in the poll and add any info you think may be relevant. If you use a specific voltage for each frequency, vote for custom and post your values (and maybe how you reached/tested them)
So for me:
Max Freq: 1.4Ghz
Min Freq: 100
Undervolt: Flat -100mV
Kernel: SiyahKernel S3-1.2.6
Edit: Seems stock voltages are not necessarily fixed on the SGS3 so take these with 2 grains of salt.
Stock Voltages in Siyah (in mV):
1400Mhz - 1287.5
1300Mhz - 1250
1200Mhz - 1187.5
1100Mhz - 1137.5
1000Mhz - 1087.5
900Mhz - 1037.5
800Mhz - 987.5
700Mhz - 975
600Mhz - 962.5
500Mhz - 937.5
400Mhz - 925
300Mhz - 900
200Mhz - 900
100Mhz - 900
These ones work for me:
1400Mhz : 1100 mV
1300MHz : 1050 mV
1200MHz : 1000 mV
1100MHz : 975 mV
1000MHz : 925 mV
900MHz : 900 mV
800MHz : 875 mV
700MHz : 850 mV
600MHz : 825 mV
500MHz : 800 mV
400MHz : 775 mV
300MHz : 775 mV
200MHz : 750 mV
Max Freq: 1200
Min Freq: 100
Undervolt: -100mV
Kernel: S3-1.2.6
the limit in ExTweaks is -100, i have Voltage Control Extreme but im not comfortable going any further for now
my uv values are in my sig, though -25mv from the one in my sig worked its not that stable .
Right now I'm running stable with:
1400: 1287500 > 1187500 = -100mV
1300: 1250000 > 1137500 = -112.5mV
1200: 1187500 > 1112500 = -75mV
1100: 1137500 > 1075000 = -62.5mV
1000: 1087500 > 987500 = -100mV
900: 1037500 > 937500 = -100mV
800: 987500 > 900000 = -87.5mV
700: 975000 > 837500 = -137.5mV
600: 962500 > 825000 = -137.5mV
500: 937500 > 812500 = -125mV
400: 925000 > 750000 = -175mV
300: 900000 >737500 = -162.5mV
200: 900000 > 687500 = -212.5mV
Although I might still be able to get one or two steps out of the upper middle frequencies, I spent several hours testing trying to find my voltages and it is annoying and tedious work, and I stopped at the above values. My chip is being attributed ASV5, so middle ground in terms of quality of the chip.
I tried to do -50 on all steps using ExTweaks and Siyah Kernel.. and my headset speaker stops working Works fine stock, but as soon as I reboot after a UV I have no headset speaker :/
AndreiLux said:
Although I might still be able to get one or two steps out of the upper middle frequencies, I spent several hours testing trying to find my voltages and it is annoying and tedious work, and I stopped at the above values. My chip is being attributed ASV5, so middle ground in terms of quality of the chip.
Click to expand...
Click to collapse
How did you find your chip number and how do you know about its quality? Cheers!
Fruktsallad said:
How did you find your chip number and how do you know about its quality? Cheers!
Click to expand...
Click to collapse
A stupid and simple way to do it is to check your default voltages and compare them to the ASV table.
Fruktsallad said:
How did you find your chip number and how do you know about its quality? Cheers!
Click to expand...
Click to collapse
I'm curious about that as well.
I find Kevin's values to be completely stable so far. I'm impressed with the UV potential on the SGS3. On the SGS2 I rarely managed to take 100mV off the stock voltage while Kevin's values are significantly lower than 100mV off the stock.
I'll put the stock voltages in the OP to make comparison easier.
AndreiLux said:
Right now I'm running stable with:
1400: 1287500 > 1187500 = -100mV
1300: 1250000 > 1137500 = -112.5mV
1200: 1187500 > 1112500 = -75mV
1100: 1137500 > 1075000 = -62.5mV
1000: 1087500 > 987500 = -100mV
900: 1037500 > 937500 = -100mV
800: 987500 > 900000 = -87.5mV
700: 975000 > 837500 = -137.5mV
600: 962500 > 825000 = -137.5mV
500: 937500 > 812500 = -125mV
400: 925000 > 750000 = -175mV
300: 900000 >737500 = -162.5mV
200: 900000 > 687500 = -212.5mV
Click to expand...
Click to collapse
This was a good starting point to get rid of my -100 blanket UV, but using that as a firm base.
1704: 1275mV
1600: 1225mV
1500: 1175mV
1400: 1150mV
1300: 1125mV
1200: 1050mV
1100: 1000mV
1000: 950mV
0900: 925mV
0800: 875mV
0700: 837mV
0600: 825mV
0500: 812mV
0400: 750mV
0300: 750mV
0200: 750mV
0100: 750mV
Seems stable so far. Its always those bottom 3 which I have as a screen off profile that worries me. I can ascertain the other frequencies by using the device, but these 3, the only real test is whether it falls over when Idle.
Are any of today's kernels using AXI does anyone know? Not seen it mentioned in any of the threads.
I am at:
GHZ mV
1.4 = 1100
1.3 = 1050
1.2 = 1000
1.1 = 975
1.0 = 925
0.9 = 900
0.8 = 875
0.7 = 850
0.6 = 825
0.5 = 800
0.4 = 775
0.3 = 775
0.2 = 750
I can't believe how far the s3 can under volt. I haven't had any problems with these voltages all day. I haven't and don't dare go any lower
Currently running these frequencies and everything is perfectly stable, no a single lockup or crash so far.
Basically dropped all the frequencies by 100 mV then pushed 200mhz down as far as i dared as i figure undervolting is most useful for extending standby time.
From other peoples settings it looks like I can lower most of these a lot more without any problems.
Freq - mV
1500 - 1200
1400 - 1150
1300 - 1137
1200 - 1100
1100 - 1050
1000 - 1000
900 - 950
800 - 900
700 - 875
600 - 862
500 - 850
400 - 850
300 - 825
200 - 720
GHZ mV
1.4 = 1100
1.3 = 1050
1.2 = 1000
1.1 = 975
1.0 = 925
0.9 = 900
0.8 = 875
0.7 = 838
0.6 = 825
0.5 = 813
0.4 = 750
0.3 = 738
0.2 = 675
AndreiLux said:
I spent several hours testing trying to find my voltages and it is annoying and tedious work, and I stopped at the above values. My chip is being attributed ASV5, so middle ground in terms of quality of the chip.
Click to expand...
Click to collapse
How did you work out your setup?
Seems that my UV is not stable and I had 2-3 SOD.
This is what I did: undervolted the cpu step, then kept stuck the cpu on that step and tried for a while.
I did this for every passage, and tested untill the phone freezed.
So for exemple, I started from 900 mv, then went down 875-850 etc. If my phone dies on 825, I setup 850, or the previous valid voltage step.
I did this for every cpu step, from 1400 to 200, but when I stopped keeping the cpu stuck on a single step and let it go between 200 and 1400, I started to have loads of reboots etc.
Any hints? Since I've just spent like 2 hours of my life for nothing
TMaLuST said:
I did this for every cpu step, from 1400 to 200, but when I stopped keeping the cpu stuck on a single step and let it go between 200 and 1400, I started to have loads of reboots etc.
Any hints? Since I've just spent like 2 hours of my life for nothing
Click to expand...
Click to collapse
I went through this same procedure and the same thing happened. Unstable as hell, wasted hours of time...
I ended up just using extweaks to undervolt all clocks to -50mv by default and that seems to save me a decent amount of power.
Also set sleep clock to 100mhz. Saves even more during sleep.
Getting runs of 30 hours with moderate useage, browsing texting calling photos etc.
Sent from my GT-I9300 using xda premium
I think the higher steps don't all undervolt quite as well as lower ones. To get 1.6 stable on mine needs quite a lot of juice and then it heats up a bit and benchmark scores drop so I guess there's some thermal throttling. I'll just keep it at 100-1400MHz 725-1200mv.
What app/program are you guys using to undervolt this? you wouldn't happen to be using setcpu right? This seems much more advanced than what setcpu offers?
Enigmani said:
What app/program are you guys using to undervolt this? you wouldn't happen to be using setcpu right? This seems much more advanced than what setcpu offers?
Click to expand...
Click to collapse
I use setCPU. All we are doing is setting a voltage for each clock frequency. Set CPU has a voltages tab.
doi its fine
rootSU said:
I use setCPU. All we are doing is setting a voltage for each clock frequency. Set CPU has a voltages tab.
Click to expand...
Click to collapse
thanks for the reply and screenshot, what version are you using of setcpu? i don't seem to have the voltages tab there.. My only tabs are: Main|Profiles|Governor|Info|About.
maybe i'll see if I can update my version maybe...
Related
I am currently running CM7 with the Bali kernel. I just recently installed setCPU and wanted to know what the best settings are for having decent battery life without taking away to much from performance. I'm pretty new to OC/UV so any pointers would be greatly appreciated.
anybody? any help would be great? I've been trying to search for settings but havent gotten to far.
Conservative is great 1000-100 an 4 speed On demand
Sent from my SGH-T959 using XDA Premium App
Here is my settings on Voltage Control for Glitch. That may help you out a bit. Have you tried looking in the Bali thread to see if anyone posted any stable results?
1300: 1400mv -0mv = 1400
1200: 1350mv -0mv = 1350
1000: 1250mv -25mv = 1225
800: 1200mv -50mv = 1150
400: 1050mv -75mv = 975
200: 950mv -75mv = 875
100: 950mv -100mv = 850
Been Undervolting on the Glitch Kernel, and trying different things. What I have set my UV to is just slightly too low I guess, because it keeps restarting..
Have never really Uv'd before and having troubles finding the Lowest possible..
These are my Settings ;
1500mhz - 0 = 1500mv
1440mhz - 25 = 1450mv
1400mhz - 25 = 1425mv
1300mhz - 25 = 1375mv
1200mhz - 25 = 1325mv
1000mhz - 50 = 1200mv
800mhz - 50 = 1150mv
400mhz - 50 = 1000mv
200mhz - 75 = 875mv
100mhz - 125 = 825mv
Any of this Look wrong?
Any Suggestions?
I dont belive you should UVing the OC... just makes sense that anything over 1ghz should stay with factory voltage settings. Could be part of the problem your having?
xplred said:
I dont belive you should UVing the OC... just makes sense that anything over 1ghz should stay with factory voltage settings. Could be part of the problem your having?
Click to expand...
Click to collapse
dragonmodz has undervolted the OC on his kernel i think so shouldnt matter but might do for some phones
Try 100mhz at 875 and if that doesn't work try 1225 on 1000mhz
Sent from my SGH-T959 using XDA App
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.
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