Recently, I have seen the undervolted kernel for Nexus One which makes the battery spell longer.
Can anyone modify it for G1?
http://forum.xda-developers.com/showthread.php?t=634587
Look on the app market, dude. There are like 5 apps\widgets to do that EXACT same thing. Nothing has to be ported.
zimphishmonger said:
Look on the app market, dude. There are like 5 apps\widgets to do that EXACT same thing. Nothing has to be ported.
Click to expand...
Click to collapse
They actually don't do the exact same thing... My kernel is undervolted, not underclocked. Theres a difference. Undervolted uses less power at the same speeds, underclocked just drops the clockspeed.
interesting
This is interesting... I'd like to see this happen
EDIT: Forget it...
persiansown said:
They actually don't do the exact same thing... My kernel is undervolted, not underclocked. Theres a difference. Undervolted uses less power at the same speeds, underclocked just drops the clockspeed.
Click to expand...
Click to collapse
So you have one for cliq now or dream?
Ace42 said:
So you have one for cliq now or dream?
Click to expand...
Click to collapse
The one he linked for the Nexus is the one I made.
I don't think its possible for the G1/MT3g/CLIQ unfortunately.
persiansown said:
The one he linked for the Nexus is the one I made.
I don't think its possible for the G1/MT3g/CLIQ unfortunately.
Click to expand...
Click to collapse
In other words all 72XX lack this ability correct?
But the new Armv7 should be capable like the Droid,legend,devour,etc.
You can lower the vdd for 528MHz, but the next jump down makes it so low that the phone would immediately crash.
coolbho3000 said:
You can lower the vdd for 528MHz, but the next jump down makes it so low that the phone would immediately crash.
Click to expand...
Click to collapse
So we can lower it but not up it for the overclock?
Also, can we lower it at the lower speeds? (I have mine set up to underclock when the battery is low, when the screen is off, etc. so a lower VDD (if stable) would be great.
coolbho3000 said:
You can lower the vdd for 528MHz, but the next jump down makes it so low that the phone would immediately crash.
Click to expand...
Click to collapse
How feasible is it to underclock the phone even further than the 128 MHz?
personaly , i dont see a huge advantage to underclocking past what we got now, undervolting.... nah,
@ sleep mine atleast has virtualy no background processes.
and even on a heavy use day, cell standby shows up as my largest drain.
you want much better battery life, id say look into hacking the radio on it.
Related
I am running Cognition 4.4.8, which will not allow OC/UC. I actually just want to UC. What recommendation would you have for a kernel compatible with Cognition 4.4.8 for Captivate that would allow me to UC?
Don't you mean oc/uv? I don't think you know what you are talking about.
Yeah its UV (undervolt). Find any kernel that allows it and is working with your ROM. Maybe ask in that thread as others could be using a custom kernel for that exact reason.
Sent from my SGH-I897 using XDA Premium App
UC is a real term, maybe he meant he wants to limit his clock speed to 800mhz. What's that called if not UC?
Although undervolting and underclocking to save battery is a waste of time. The cpu doesn't use that much battery in the first place, the screen and the modem use the most power, you want the charge to last switch to the lowest brighteness and 2g, that will give way more battery than uc/uv will.
studacris said:
UC is a real term, maybe he meant he wants to limit his clock speed to 800mhz. What's that called if not UC?
Although undervolting and underclocking to save battery is a waste of time. The cpu doesn't use that much battery in the first place, the screen and the modem use the most power, you want the charge to last switch to the lowest brighteness and 2g, that will give way more battery than uc/uv will.
Click to expand...
Click to collapse
+1 on the battery topic. Even at a high OC the battery drain is not that much worse... a little yeah but not too severe.
Also good point about UC.. wasn't thinking about that at all ..underclock what!?!?
some people falsely think that the phone runs at 1ghz all the time, when in fact it downclocks itself and ramps up clockspeed when it needs it....so unless you have an app thats using 100% CPU all the time, your phone is running around 200mhz at idle.
Pirateghost said:
some people falsely think that the phone runs at 1ghz all the time, when in fact it downclocks itself and ramps up clockspeed when it needs it....so unless you have an app thats using 100% CPU all the time, your phone is running around 200mhz at idle.
Click to expand...
Click to collapse
+1 again Although there are different governors that do different things most phone at stock will idle down to 200mhz. My phone for instance idles down to 800mhz, but thats just my prefrence
Yep, I meant OC/UV. I typed too fast for my own good!
Good points
Thanks for the message on how little battery undervolting saves. That was quite helpful. I did try the discussion board for Cognition, but no one seemed to be posting on using an alternate kernel, which is why I asked for recommendations here.
I believe Cog is KB1 based, so this kernel should work: http://forum.xda-developers.com/showthread.php?t=988805
Thanks I will certainly trie eXist's kernel.
Ernesto47 said:
Thanks I will certainly trie eXist's kernel.
Click to expand...
Click to collapse
If you want the best battery life, I suggest something other than cognition. In my experience, i9000 based custom roms get better battery life.
Sent from my CM7 powered captivate
@sixstringsg I notice that you are using Cyanogenmod. I keep looking at that, but since it was still not listed as stable, I was not sure whether to try it. How are you finding the stability?
What I have here is a VERY BETA kernel built from the latest LeeDrOiD git with some ondemand tweaks to make it a bit more responsive, as well as AXI Scaling, an undervolted bottom end at 122mhz, and with a topend of 2016mhz.
Many phones may not run at the full upper-end, but vddsys is implemented as in the LeeDrOiD kernel, so you may increase or lower the VDD by 25 for 20160000mhz to attempt to get it working.
Currently working on getting a github page up with this source. I'm running it on the Unity rom at the moment without issue. 2016mhz should only be used for benchmarks, and not 24/7.
Two way call recording is also included, as well as a startup script to run at 1843mhz ondemand at startup.
Changelog:
June24-Initial Release...Working on Cleanup.
GitHub Page: https://github.com/synergydev
Will work on marking changes shortly. It should also be of note that because my GF's phone seems stable at [email protected], I changed the voltage at 2016 to 1.5 on the git just because it seems my phone likes high voltages.
I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable
LorD ClockaN said:
I've tried 2000 a long time ago on my kernel, but my dhd couldn't handle it. and it handle very very low voltages, so didn't want to release a kernel with the freq that doesn't even work on dev's DHD I've even removed 1980mhz from my kernel because there really isn't any use of that freq rather than frying your DHD
I think that BuzzBumbleBee had 2000 on his kernel once, don't remember right
Good job BTW
edit:
wht is a working voltage on 2000?
I've trid up to 1.5V and it was unstable
Click to expand...
Click to collapse
I'm using 1.525V at 2016, however my DHD could never run the 1.9986 in your kernel without a voltage bump (could undervolt all the way up to 1.8 however though). In this kernel, I needed to up the AXI clock at 2016 to even get it to run, let alone benchmark continuously. I still haven't been able to get it to scale with a minimum under 300mhz.
This is why I recommend reducing the VDD at that speed by 25 if anyone's DHD can't run it.
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).
synergye said:
In response to the first section, I only released this because I'm an enthusiast overclocker when it comes to my desktops (water chilled and vapour phase change cooled), and I wanted my clock to read the magical "2" at the beginning for bragging rights. With AXI clock scaling, we should be able to get slightly better battery life as well at the lower clocks (at least on the N1 it seems they were able to get better battery life with it).
Click to expand...
Click to collapse
+1 on that, but don't think you're more enthusiastic when talking about OC
We can argue about that the whole day
looking forward for your git!
I think 1.2G is enough..
@LorD ClockaN: if that's an sense kernel, you know what you have to do
Your 2016 MHz ASOP kernel coming soon?
with friendly greet
starbase64
You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?
Tryng with virtuous sense 3 and it makes lag the sense but for the rest is quiet good
Edit: after some time the lags disappears and all is perfect now
where source code?
u canT post kernels on XDA without source code
m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!
m-deejay said:
where source code?
u canT post kernels on XDA without source code
Click to expand...
Click to collapse
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.
tolis626 said:
He said he's working on the github page to up his source soon.So I think it's already in progress.
Good job by the way mate.Never liked the fact that kernels with the vdd interface restrict us to 1500mV!
Click to expand...
Click to collapse
Mine has voltage till 1.525 via vdd
Sent from Desire HD with CyanogenLordMod!!!
adwinp said:
What do you need it for?
Just add frequencies in multiples of 19200 to arch/arm/mach-msm/acpuclock-7x30.c
If the newly added frequency locks, add the next multiple and/or up the voltage.
No magic there.
Click to expand...
Click to collapse
really?
lol
Why do you explain to me?
m-deejay said:
really?
lol
Why do you explain to me?
Click to expand...
Click to collapse
Oohoo... Dev fight!! LOL
Sent from Desire HD with CyanogenLordMod!!!
wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??
Lizzo said:
wiped devik cache and flashed it to my honeysense rom and tha **** froze on startup lol any tips??
Click to expand...
Click to collapse
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.
Ace42 said:
Raise min freq to higher[around 1.1GHz+] to prevent voltage spikes which might be causing the freezes, try decrease the distance b/t the 2GHz and the min.
Click to expand...
Click to collapse
uuuggghhhh... how do i raise the min b4 startup?
Lizzo said:
uuuggghhhh... how do i raise the min b4 startup?
Click to expand...
Click to collapse
echo 806400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
On adb you have to change the min freq while booting up. 800 might work. Or use 1305600 [1.3GHz].
This is madness, yes i know people will post no this is sparta, but seriously, anything over 2ghz i personally wouldn't test
adwinp said:
You will find the 1.8GHz+ frequencies being only theoretical, with no increase in performance with respect to a "speed bump".
I have tested that a few months ago, going as high as 2.2GHz.
The maximum "real" performance boosts only go up to 1.5GHz (I clock my kernels to 1.497GHz).
Run a smartbench, and the results will speak for themselves.
Unless you want to fry your DHD?
Click to expand...
Click to collapse
PMSL Benchmarks mean fuk all tbh do not reflect real world peformance running at 1.8/1.9ghz stuff like Playstation emulator etc run far much smoother and with no slowdowns etc... newbs and benchmarks lol!
Just got my second G2x yesterday got it rooted and bloat ware froozen now I can't remember where I go from 1200 mah to 1500 mah. Can anyone refresh my memory
sgt_addyjp said:
Just got my second G2x yesterday got it rooted and bloat ware froozen now I can't remember where I go from 1200 mah to 1500 mah. Can anyone refresh my memory
Click to expand...
Click to collapse
1500 isn't necessary. In fact, you're risking frying your phone! 1200 is the median for most.
Common Sense is learned..........
do 1500 but when u processor will be overheat, your phone gonna restart.
thats all....I don't remember no one in my life who broke the PHONE because overclocking.
For me 1400 best...because 1500 not stable for "heavy congestion."
avetny said:
do 1500 but when u processor will be overheat, your phone gonna restart.
thats all....I don't remember no one in my life who broke the PHONE because overclocking.
Click to expand...
Click to collapse
It happens often. Why do you think is called "OVERclocking"? OEM's set specific numbers on their kernels for a reason. Besides the numbers themselves and meaningless quadrant scores, you'll probably not notice any difference between 1200 or 1400
Common Sense is learned..........
Chance Ill said:
It happens often. Why do you think is called "OVERclocking"? OEM's set specific numbers on their kernels for a reason. Besides the numbers themselves and meaningless quadrant scores, you'll probably not notice any difference between 1200 or 1400
Common Sense is learned..........
Click to expand...
Click to collapse
oh yea? play flash on 1.2Ghz and 1.4Ghz
avetny said:
oh yea? play flash on 1.2 and 1.4
Click to expand...
Click to collapse
I use flash literally everyday! No problems whatsoever and I'm using stock kernel at 1ghz
Common Sense is learned..........
Chance Ill said:
I use flash literally everyday! No problems whatsoever and I'm using stock kernel at 1ghz
Common Sense is learned..........
Click to expand...
Click to collapse
Can I use your phone for a minute
I will show ALL difference
avetny said:
Can I use your phone for a minute
I will show ALL difference
Click to expand...
Click to collapse
Lol! We can agree to disagree, but 1500 on any kernel is unstable at best!
Common Sense is learned..........
Chance Ill said:
Lol! We can agree to disagree, but 1500 is on any kernel isunstable at best!
Common Sense is learned..........
Click to expand...
Click to collapse
yes, totally agree with you!!!
Chance Ill said:
I use flash literally everyday! No problems whatsoever and I'm using stock kernel at 1ghz
Common Sense is learned..........
Click to expand...
Click to collapse
+1 on stock 1 ghz I can do anything I want without lag lol. I have oced but noticed little to no difference in anything I do. Love this phone. Benchmarks really don't mean much to me when I can't see any difference in my hand.
Sent from my G2x
Chance Ill said:
Lol! We can agree to disagree, but 1500 on any kernel is unstable at best!
Common Sense is learned..........
Click to expand...
Click to collapse
Good dialogue, but he was asking 'where' to change the settings, not if he should change the settings
alodar1 said:
Good dialogue, but he was asking 'where' to change the settings, not if he should change the settings
Click to expand...
Click to collapse
yes I had my other G2x set to 1500 and the battery life was better for me...I prolly set it to 1400 to see how things go. I had to get a new G2x because say someone set me a text msg saying "hey" i would get 200-400 of them and then one day I restarted it and it go to the point where it said LG with the blue bar under it then it would restart...why I have no clue but I would like to figure out why before I have to send it back because I have it rooted and would like to unroot it before sending it back. I also have pictures on the phone that I don't really want to lose so if anyone could help me with that that would be great also.
nobody is really going to answer his question? If you are trying to change the speed either download a program called pimp-my-cpu or setcpu. Both of those will give you full access to do what ever u please to your phones processors. Hope this helps!
there is a place in the setting that you can do it at i just don't remember where to find it at.
It was suggested to me that in order to prevent excessive battery drain and heat when using CM7 I should disable one of the cores. Has anyone done this? What negative impacts could doing this cause (if any)?
webmaster said:
It was suggested to me that in order to prevent excessive battery drain and heat when using CM7 I should disable one of the cores. Has anyone done this? What negative impacts could doing this cause (if any)?
Click to expand...
Click to collapse
If anything it would increase battery drain due to all the processing being put on one single core, what I would recommend for a decrease in battery drain is different kernels with under volting options. That's what's worked best for me.
Sent from my Sensation using xda premium
Chilled26 said:
If anything it would increase battery drain due to all the processing being put on one single core, what I would recommend for a decrease in battery drain is different kernels with under volting options. That's what's worked best for me.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
It was my perception that the older single core phones had better battery life. Do you really think it would hurt the battery?
Dual core isn't properly utilized yet so it might not be a bad idea.
Here is an example of my battery drain for today with the bricked kernel v1.4.
Sent from my Sensation using xda premium
Changing kernel and undervolting did the trick for me. Getting 20 hours moderate use.
Sent from my Sensation using xda premium
Chilled26 said:
Here is an example of my battery drain for today with the bricked kernel v1.4.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
What are your settings?
Most of the time when both cores are on the 2nd isn't doing anything, because the first core isn't even pushed enough to reach max. So, I feel 1 core is sufficient, I'm running 4.1.x w/ 1 core @800 and the battery and speed are fine. Although I see others running speeds of 1.2 and higher, but I barely notice the difference of the freqs. The S3 is so fast that the higher clocks are overkill IMO.
Ace42 said:
Most of the time when both cores are on the 2nd isn't doing anything, because the first core isn't even pushed enough to reach max. So, I feel 1 core is sufficient, I'm running 4.1.x w/ 1 core @800 and the battery and speed are fine. Although I see others running speeds of 1.2 and higher, but I barely notice the difference of the freqs. The S3 is so fast that the higher clocks are overkill IMO.
Click to expand...
Click to collapse
I suspect you see a noticeable difference in battery life then? Also, what method did you use to disable the second core?
webmaster said:
What are your settings?
Click to expand...
Click to collapse
Honestly I don't even touch the settings I just run at default.
Sent from my Sensation using xda premium
Pretty snappy
su
chmod 644 /sys/devices/system/cpu/cpu1/online
echo "0" > /sys/devices/system/cpu/cpu1/online
chmod 444 /sys/devices/system/cpu/cpu1/online
Someone in faux kernel forum was talking about doing this. Gscript app makes it easy to run script. If you dont like it just reboot and 2nd core is back on.
Sent from my Sensation using XDA Premium App
Chilled26 said:
Honestly I don't even touch the settings I just run at default.
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
I tried Faux's and it was ok, I plan on trying Bricked tomorrow. However if disabling a core gives even better results then that might be the way to go.
webmaster said:
I suspect you see a noticeable difference in battery life then? Also, what method did you use to disable the second core?
Click to expand...
Click to collapse
echo 0 > /sys/devices/system/cpu/cpu1/online
I do see a difference in battery life, which is why I prefer this setup, when we have ICS I will use both cores. But I feel cheated on Ginger so I use 1 for now, and whoever said two cores has better batt is wrong...Logically two cores use twice the voltage, that means 1 cores will save a significant amount of power. A weak dual core w/ 1 core on will have bad life, but a fast on is different.
Ace42 said:
echo 0 > /sys/devices/system/cpu/cpu1/online
Click to expand...
Click to collapse
Is that permanent or does it need to be run each time you reboot?
webmaster said:
Is that permanent or does it need to be run each time you reboot?
Click to expand...
Click to collapse
Every boot, you can make a linux script(.sh) if you want, and then use script manager. But, I'm only testing this for comparison, I can't see the speed difference w/ 1 or 2 so I just use 1. 1 @800 core feels how fast my MT4G did when OC'd @1.4Ghz.
Ace42 said:
Every boot, you can make a linux script(.sh) if you want, and then use script manager. But, I'm only testing this for comparison, I can't see the speed difference w/ 1 or 2 so I just use 1. 1 @800 core feels how fast my MT4G did when OC'd @1.4Ghz.
Click to expand...
Click to collapse
How long have you been running like that?
I run Faux kernel, Joe's RCU, undervolted -50mV and underclocked to 1Ghz, I can now easily make it through the day and I'm a moderate to heavy user. I'm pretty sure disabling the second core isn't necessary, and frankly, if you check out how little it's used, it probably wouldn't benefit that much anyhow.
Ace42 said:
echo 0 > /sys/devices/system/cpu/cpu1/online
I do see a difference in battery life, which is why I prefer this setup, when we have ICS I will use both cores. But I feel cheated on Ginger so I use 1 for now, and whoever said two cores has better batt is wrong...Logically two cores use twice the voltage, that means 1 cores will save a significant amount of power. A weak dual core w/ 1 core on will have bad life, but a fast on is different.
Click to expand...
Click to collapse
Completely false. Just because something has voltage across it doesnt mean that it is doing anything. Voltage times current equal power. Using power uses the battery.
You guys need to SERIOUSLY change the way you make decisions. Just because something SEEMS logical to you, doesnt mean it is correct. I see alot of BAD info being pushed around here.
I have CM7 and run Fauxs kernels. I FORCE both CPUs online and run at 1.56Ghz. My standby is around 30mAH...Nuff said.
Something else is messed up. Chase facts, not fiction people.
Another issue? UVing. You guys break so many rules in electrical engineering that it isnt even funny. Ive explained things so many times that I am sick of it. I wont anymore, but will let you know that you have missed some key facts.
Matt
mrg02d said:
Completely false. Just because something has voltage across it doesnt mean that it is doing anything. Voltage times current equal power. Using power uses the battery.
You guys need to SERIOUSLY change the way you make decisions. Just because something SEEMS logical to you, doesnt mean it is correct. I see alot of BAD info being pushed around here.
I have CM7 and run Fauxs kernels. I FORCE both CPUs online and run at 1.56Ghz. My standby is around 30mAH...Nuff said.
Something else is messed up. Chase facts, not fiction people.
Another issue? UVing. You guys break so many rules in electrical engineering that it isnt even funny. Ive explained things so many times that I am sick of it. I wont anymore, but will let you know that you have missed some key facts.
Matt
Click to expand...
Click to collapse
So me having better life w/ 1 core is false? Even though I've compared it w/ 2? And I don't know what your problem is but keep it to yourself, I didn't force you to respond to my post, only sharing my experiences.
webmaster said:
How long have you been running like that?
Click to expand...
Click to collapse
Almost 1 day, battery around 30 still. But I listened to music, internet, sync and played some games so my life was shorten.
Ace42 said:
So me having better life w/ 1 core is false? Even though I've compared it w/ 2? And I don't know what your problem is but keep it to yourself, I didn't force you to respond to my post, only sharing my experiences.
Almost 1 day, battery around 30 still. But I listened to music, internet, sync and played some games so my life was shorten.
Click to expand...
Click to collapse
I didnt say this. It is obvious what I said, so why would you even ask me? Just scroll up pal.
You didnt simply give an experience...You implied that your experience is LOGICAL. It may to you, but it is incorrect. Dont just throw things out there, please. It makes people with backgrounds in power and energy pissed off.
Also, my finding completely debuncts your theory. At night, while I sleep, I see 5mAH draw.
Matt
Does anyone know the ideal settings for undervolting the sensation without causing any problems?
StuartTheFish said:
Does anyone know the ideal settings for undervolting the sensation without causing any problems?
Click to expand...
Click to collapse
Not really. As faux say not all chips are created equal. I've seen up to an amazing -150 but my phone can only handle -50 stable and -75 sometimes with a reboot or two.
Sent from my HTC Sensation 4g using xda premium
Mine handles -100 just fine, but yeah,others can only go -50. Just use system tuner and hit the -12.5 till your phone freezes, then when it restarts go one less and see if it's stable. That's what I did.
Sent from my HTC Sensation 4G using XDA App
I'd also suggest keeping the Max Clock at a consistent value while you play. E.g. UV -100mV might work well at one Mhz then fail at a higher value.
Mine seemed to work consistently at about -100mV, then again I tend to UC unless I'm running CF-Bench or something
Should I only need to concentrate on the lowest and highest clock speeds it's been set to use? Or will I have to undervolt all other frequencies between the two? Not sure if it increments on usage, or simply toggles between the min and max.
If it does increment, how can I test it's stability on the other frequencies if I can't tell what frequency it was using at the time?
Just tapped the -12.5 button a few times, and it reduced all of the sliders. It's -100 now with no apparent issues as of yet.
May I ask the reason for undervolting?
masonic1032 said:
May I ask the reason for undervolting?
Click to expand...
Click to collapse
Mainly to save battery. Altho I have found that it is quite negligible. It may also help with phone heat
masondoctorjt said:
Mine handles -100 just fine, but yeah,others can only go -50. Just use system tuner and hit the -12.5 till your phone freezes, then when it restarts go one less and see if it's stable. That's what I did.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
I run faux latest version 2.7 beta and I see his scripts to undervolt and the lowest I see it too go is -75 how are you able to go lower to -100.... ???
I think it varies from phone to phone, mine too seems happy enough -100.
StuartTheFish said:
I think it varies from phone to phone, mine too seems happy enough -100.
Click to expand...
Click to collapse
Soooooo how do I undervolt below -75 that's where I am. Now
rawdawgroy said:
Soooooo how do I undervolt below -75 that's where I am. Now
Click to expand...
Click to collapse
If the phone hangs/boots below that level then with the Phone/Kernel/... that's the limit.
I created a GScript script (well a sh script) to U/V after a reboot. I didn't want it to do it automatically as you'd end up in a boot loop. Just hassle to fix. The reason for the GScript was to remove it from the various CPU controllers I'd tried, I ended up just using the CM7 one to control the CPU.
Faux has the command to do it globally (across all frequencies) or individual frequencies. TBH I never bothered with individual ones.
The bottom line is, do what you and your phone are happy with.
EDIT: meant to add you can check the actual value manually. I know the Faux one (same post as the scripts above) but if you are using a different kernel it might be in a different place.