What started as a modification of the Community Kernel has grown into it's own beast....
As always, what you flash from me has not warranty as you have already borked your manufacturer's anyways.....
Now presenting the Choose your own Core version of Infusion Kernel. Since I couldn't deliver Dual core speeds, I thought that I would deliver 2 different cores!
Both Cores have the following....
BLN
Voodoo Sound 10
Voodoo Lagfix
TinyRCU
Insecure boot (ro.secure=0)
bfq and cfq schedulers
And now for the differences:
Core A has the standard frequencies
100
200
400
600
800
1000
1200
1400
1600
Nothing new here....
Core B however has
104
208
416
624
832
1040
1248
1456
1664
"Nani?" you say? (Nani is Japanese for what)
What I have done here is overclocked the whole CPU/GPU bus from the ground up. Thus making a more user oriented experience and preventing bouncing the GPU all over the place. It's still a beta status (since the 1664 can freeze with large amounts of playing games, but is stable for everyday use), so I would not expect as smooth as the standard 200 MHz bus, but if you feel daring, have fun!
Many thanks to:
Hardcore/Unhelpful: for the HUGE work with the SGS/Infuse processor
gtg465x: for the community kernel
supercurio: for Voodoo of course!
drowningchild/Entropy512: for the help and pushes to the kernel
You: for encouraging me and choosing my kernel!
Last but not least, the Insanity Crew:
crazynfo
gb96
Unknown #1
2sl0w
ookba
motumbo
(If you're not here yet, either the info hasn't went through yet, or I don't know who donated what.... Feel free to drop me a line. )
Previous Versons, known issues, ect.
Previous versions of the Infuse Kernel can be found here.
Known issues:
No CPU states in Core B.
Downloading now! Thanks!
----------
Working great. Loving these funky CPU clock speeds,
Sent from my SAMSUNG-SGH-I997 using XDA App
----------
TehInternetzOozer said:
Quadrant is crashing every few tests I take. When it finishes, I get always over 2300. It seems like it scores more when CPU is hot.
Click to expand...
Click to collapse
Careful with that though, I'm seriously thinking of taking the CPU/GPU from 208 to 206 due to 1664 being too close to my top speed of 1670 and freezing up 15-20 min into a graphically intensive game.... Great benches, with Nenamark 1.0 at 51 FPS (only top frequency and performance/Ondemand), but stability is key.
----------
BLN seems to be working well! Thanks!
Is there any difference between Core A and Infusion 1.8?
I tried to UV -150 and -100 across the board on core-a and got SOD both times anybody else try Uving
Sent from my Samsung Infuse with Infused 1.5.3
VinnyCh4se said:
I tried to UV -150 and -100 across the board on core-a and got SOD both times anybody else try Uving
Sent from my Samsung Infuse with Infused 1.5.3
Click to expand...
Click to collapse
too much uv on lower freqs, i dont even uv 100-200
good work on the kernel
Hmm that makes sense since I don't feel like destroying my phone I put everything back to normal and I'm gonna just wait and see
Sent from my Samsung Infuse with Infused 1.5.3
bedwa said:
What started as a modification of the Community Kernel has grown into it's own beast....
As always, what you flash from me has not warranty as you have already borked your manufacturer's anyways.....
Now presenting the Choose your own Core version of Infusion Kernel. Since I couldn't deliver Dual core speeds, I thought that I would deliver 2 different cores!
Both Cores have the following....
BLN
Voodoo Sound 10
Voodoo Lagfix
TinyRCU
Insecure boot (ro.secure=0)
bfq and cfq schedulers
And now for the differences:
Core A has the standard frequencies
100
200
400
600
800
1000
1200
1400
1600
Nothing new here....
Core B however has
104
208
416
624
832
1040
1248
1456
1664
"Nani?" you say? (Nani is Japanese for what)
What I have done here is overclocked the whole CPU/GPU bus from the ground up. Thus making a more user oriented experience and preventing bouncing the GPU all over the place. It's still a beta status (since the 1664 can freeze with large amounts of playing games, but is stable for everyday use), so I would not expect as smooth as the standard 200 MHz bus, but if you feel daring, have fun!
Many thanks to:
Hardcore/Unhelpful: for the HUGE work with the SGS/Infuse processor
gtg465x: for the community kernel
supercurio: for Voodoo of course!
drowningchild/Entropy512: for the help and pushes to the kernel
You: for encouraging me and choosing my kernel!
Last but not least, the Insanity Crew:
crazynfo
gb96
Unknown #1
2sl0w
ookba
motumbo
(If you're not here yet, either the info hasn't went through yet, or I don't know who donated what.... Feel free to drop me a line. )
Click to expand...
Click to collapse
great work
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Trying B kernel. Running great so far, Oc'd and Uv'd but not using 1664 because of too many phone freezes. I did see other people say that bln is working good but not for me. I wonder why?
Edit: bln working fine battery was really low and so phone was trying to conserve power, I think?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Nice to have BLN again.
Sent from my Infuse 4G
Got a few SOD with this one.
no UV, both on ondemand and conservative 100Mhz 1664.
Thanks for all the hard works so far!
4% overclock seems kinda useless but I tried it anyway. it needs like 100mv more to run stable so I don't think I could get more than 1.7 if I needed to. it seems stable so far.
I wonder why nobody has ever added unhelpful's gpu overclock to hardcores oc/uv meathod. with the buss overclock this could give you 231mhz. maybe 260 (if my assumtions about how it works are correct) I'm not sure if the gpu could run at 250 or 260 but it would be fun to test.
ok. I have a question about the governors. I read that deadline is the best? or no? could somone plz explain the different governors?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
I don't like bln how do you disabled it?
Sent from my Samsung Infuse with Infused 1.5.3
Related
VisionKernel v1.2
Designed for SyndicateROM Frozen 1.1.0
Disclaimer
I nor any member of INC is responsible for anything that happens to your phone when using this kernel. It has been tested on mine and a few others phones to be working, but I cannot guarantee that it will work on yours. All CPU's are different, and each one takes to overclocking in different ways. That being said, don't be surprised if your phone locks up at 1.4ghz or 1.45ghz. Just set the clock down to a lower speed and it won't do it anymore; all this means is that your phone can't handle it.
Also, 1.45ghz is set at 1.400v and 1.4ghz is set at 1.375v which is definitely above the recommended voltage for the phone. This doesn't mean it will burn up your processor as they are very robust when it comes to heat dissipation, but just keep in mind that you are pushing the processor past its designed limit.
This is my first kernel release, although I have been compiling my own custom kernels since DI18. Took me a while to get the overclocking stable, a big thanks goes to tanimn and Rodderik for helping with getting 1.3ghz stable. Also, without tanimn none of this would really be possible. He has guided me through this process a lot, and I am especially thankful to him. You the man tanimn ;-)
1.45ghz is here, I cannot guarantee that it will work even at all on your phone. This is as high as I will go, no further.
Linpack: 19.84mflops
Quadrant: 2414
Changelog
*=Thanks!
v1.0
Overclocked to 1.3ghz and 1.4ghz @ 1.375v (steps are as follows)
100mhz, 200mhz, 400mhz, 600mhz, 800mhz, 1.0ghz, 1.3ghz, 1.4ghz
Added 600mhz step for better transitions *tanimn
Voodoo Sound v6 *tanimn and supercurio
Voodoo Color (mDNIe tweaks) *supercurio
FPS cap raised to 65fps for the time being, hoping to get that number higher *Rodderik
Everything else that is contained in Twilight Zone, minus the addition of voodoo color and 1.4ghz.
v1.1
Revert the refresh rate (framerate cap) to 56fps. People having problems with video choppiness, this should fix your issue. This is only temporary; as soon as someone can figure out a proper way to raise the framerate cap I will re-implement it.
Update to Voodoo Sound driver v7
v1.2
Add 1.45ghz (It's not 100% stable, use at your own risk.)
Add 1.2ghz step
Added BFQ disk scheduler
Implemented interactive CPU governor (use at your own risk, needs tweaking)
Smartass governor (still a WIP)
Add TinyRCU courtesy of tanimn
lowmemorykiller atomic notifier fixes
UV RAM and LCD; 2.7v and 1.65v respectively
UV_mV sysfs controls as well as frequency_voltage_table for use with Voltage Control and Pimp my CPU *Rodderik
New voltage/frequency tables thanks to Rodderik!
v1.3
Battery life improvement tweaks
BFQ by default
New frequencies
More...
How-to Video:
Thanks to qbking77 for making this excellent flashing tutorial! This will show you exactly how to get the kernel running on your phone.
http://www.youtube.com/watch?v=1k7hqewGoWk
*Downloads*
v1.2
Direct:
Temporarily removed.
v1.1
Direct:
www.holylivingfuck.com/ACS/Kernals/VisionKernel_v1.1.zip
More mirrors coming soon!
v1.0
Direct:
http://k0nane.info/rom/VisionKernel_v1.0.zip
Other:
http://www.mediafire.com/?tihrnrjm6cm177u
http://www.sharebeast.com/7egv5a83g9ab
*Source*
Github
Donations are never required, but always welcome
Donators:
darkfire79
epic4GEE
jbobspants
stir fry a lot
Alright, I'm swapping the twilight zone kernal for this. Thanks for an amazing job once again.
EDIT: Damned conversion from all caps.
ONE POINT FOUR JIGGAWATTS!
ACS FTW.
Great job Thomas. I'm one of those who can't push the processor past 1.2g. Despite that I have had the privilege of testing pretty much all of the Twilight kernels courtasey of Tanimn as well as the Vision kernel. Both are great kernels, and run smooth on my Epic as long as I don't push it to the highest clock. Never had a reboot or lock up pushing my phone with these kernels. Once gain thanks Thomas, I know how much time and energy you go into this kernel and it shows!
dreamsforgotten said:
Great job Thomas. I'm one of those who can't push the processor past 1.2g. Despite that I have had the privilege of testing pretty much all of the Twilight kernels courtasey of Tanimn as well as the Vision kernel. Both are great kernels, and run smooth on my Epic as long as I don't push it to the highest clock. Never had a reboot or lock up pushing my phone with these kernels. Once gain thanks Thomas, I know how much time and energy you go into this kernel and it shows!
Click to expand...
Click to collapse
You the man dreams, much appreciated my friend thank you!
Sent from my SPH-D700 using XDA App
OMGGGGGGG
Thank you !!!!!!!!!
..... So fast that Smartbench force closes
I'll try this in a few days, assuming my phone can handle 1.3 jigga hurtz first. Sure sounds good tho, thanks, I'll report back in a few days.
How is everyone's battery doing running this kernel?
nice I just downloaded this and about to set everything up. Thanks!!
Yea buddy....
Wheres me and dreams name in big red letters for pushing you to release this
Sent from my SPH-D700 using Tapatalk
can this be flashed on eb13?
MysteryEmotionz said:
Yea buddy....
Wheres me and dreams name in big red letters for pushing you to release this
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
If Tom is smart, he'll tell you the same thing I did: ***** please.
blspyro said:
can this be flashed on eb13?
Click to expand...
Click to collapse
Yes.
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
MikeyLee said:
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
Click to expand...
Click to collapse
Long story short: Quadrant sucks. Try a better benchmark.
k0nane said:
Long story short: Quadrant sucks. Try a better benchmark.
Click to expand...
Click to collapse
Any suggestions?
MikeyLee said:
Ran a quadrant at 1.4 ghz running ViperROM Trinity
Clocked a 1765 with this kernel
Clocked a 1724 with Genocide 0.5a at 1.2 ghz. Not too much difference there. Any thoughts? Still testing battery life with this one as that's a hugs issue for me.
Click to expand...
Click to collapse
Also you will get higher scores when you get off that old ass rom with old files and source. So like 4 months ago. Smartbench is good
Sent from my SPH-D700 using XDA App
How are you suppose to test stability of oc for your phone in setcpu? I ran the stress test at 1.3ghz with no errors was there other tests to confirm stability?
Sent from my SPH-D700 using XDA App
jbadboy2007 said:
How are you suppose to test stability of oc for your phone in setcpu? I ran the stress test at 1.3ghz with no errors was there other tests to confirm stability?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Try running something CPU intensive, such as Neocore or an3dbench.
Sent from my SPH-D700 using XDA App
And its resluts will tell me its unstable or will it be laggy or fc or re boot?
Sent from my SPH-D700 using XDA App
This post has been edited because I added Mandrobench results because it utilization of both cores. Mandrobench scores were identical for both kernels. Running Mandrobench at 1500 more than once tended to overheat my phone and cause reboots and other signs of instability.
One thing is clear, if you run either Faux or Trinity kernel you must OC at least to 1100 or you take a huge hit on performance.
I ran 4 different benchmarks on every configuration of CM 10 times with the Faux and Trinity kernels. I normalized the results so that each benchmark was evenly weighted and so the numbers are better understood they were normalized so that CM with its own kernel scores 100. All other numbers are relative to that. The 4 benchmarks were Quadrant, Smartbench 2011, Linpack, and Mandrobench. The results are a bit surprising, I am attaching the spreadsheet so that anyone can check my methodology.
CM w/CM kernel 1000 MHz score 100
CM w/Faux kernel 1000 MHz score 77
CM w/Faux kernel 1100 MHz score 104
CM w/Faux kernel 1200 MHz score 114
CM w/Faux kernel 1300 MHz score 123
CM w/Faux kernel 1500 MHz score 138
CM w/Trinity kernel 1000 MHz score 85
CM w/Trinity kernel 1100 MHz score 116
CM w/Trinity kernel 1200 MHz score 124
CM w/Trinity kernel 1400 MHz score 140
CM w/Trinity kernel 1500 MHz score 147
Test for each configuration were started following a reboot with a battery charged over 60%. They were run sequentially the same way for each configuration. Each number above was the result of the averaging a total of 30 benchmarks.
Interesting note, the first couple Quadrant scores on each run were generally lower than the rest, result of caching by the phone perhaps? On certain configurations the Smartbench results fluctuated wildly producing unexpectedly low scores. Not sure what the reason for this fluctuation but it is repeatable, at least on my phone, but only on certain configurations.
This took a long time, I am sharing it because I found the results unexpected and that they might be useful to somebody. Not everyone is dumb enough to sit and run benchmarks all day. Would be interesting to know how close the numbers are ran on another phone. I am intentionally only providing the numbers and my methodology, I will leave it to someone smarter to explain them.
Add Mandrobench to the list... only app that utilizes TWO cores for its benchmarking (free too). Then we'll talk.
EtherealRemnant said:
Add Mandrobench to the list... only app that utilizes TWO cores for its benchmarking (free too). Then we'll talk.
Click to expand...
Click to collapse
I agree, Mandrobench should have been included, I didn't originally because it has disappeared from the market. I have searched my back-ups and found the apk, so I will incorporated them into the experiment later today. It is my understanding that most current apps do not take advantage of the dual core, therefore the results from benchmarks that are not optimized for dual-core have significance.
EtherealRemnant said:
Add Mandrobench to the list... only app that utilizes TWO cores for its benchmarking (free too). Then we'll talk.
Click to expand...
Click to collapse
Above not available anymore on market - maybe post the .apk.
Let me start by saying thanks! This undoubtedly took a very long time and it was nice of you to share the results with everyone. Did you use only ext3 or ext4 kernels or a combination of both?
Sent from my LG-P999 using Tapatalk
I appreciate u sharing your results. Just a quick question. was ur battery life changed a lot while u overclocked it. Also what's the difference between ext4 and 3
Sent from my LG-P999 using XDA Premium App
EtherealRemnant said:
Add Mandrobench to the list... only app that utilizes TWO cores for its benchmarking (free too). Then we'll talk.
Click to expand...
Click to collapse
Mandrobench was added to my original post. These results were identical for both kernels.
r4d14n7 said:
Let me start by saying thanks! This undoubtedly took a very long time and it was nice of you to share the results with everyone. Did you use only ext3 or ext4 kernels or a combination of both?
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Both kernels were ext4, made much easier to switch back and forth by the new version of clockwork.
Both of these are file systems and ext4 is newer and theoretically faster, probably more so on a computer where there are more read/writes to disc. I don't think any of these benchmarks test for this. Someone else may correct this as I don't know a lot about phones, I am a computer guy, and an out of date one at that.
moeahmad1995 said:
I appreciate u sharing your results. Just a quick question. was ur battery life changed a lot while u overclocked it. Also what's the difference between ext4 and 3
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
Running consecutive benchmarks can kill a battery in 2 hours.
Battery life is a subjective, I haven't thought of a way to objectively test it. I feel I get the best battery life with CM with its own kernel or Eaglesblood Froyo. Bionix appears to eat batteries.
After seeing these results, I plan to run the Trinity UV11 kernel for awhile and see to see how good the battery life is. The performance increase appears significant for only OC to 1100 and I like the idea of getting the advantages of a little OC/UV without having to run Pimp my CPU.
I have gotten a clear increase (hours more idle time) by simply turning off 4G and only toggling it on when I need it. I use Pandora a lot and it ironically runs better at 2G when I am bicycling (less drops interruptions in the streaming as I move around).
Cubeology said:
Running consecutive benchmarks can kill a battery in 2 hours.
Battery life is a subjective, I haven't thought of a way to objectively test it. I feel I get the best battery life with CM with its own kernel or Eaglesblood Froyo. Bionix appears to eat batteries.
After seeing these results, I plan to run the Trinity UV11 kernel for awhile and see to see how good the battery life is. The performance increase appears significant for only OC to 1100 and I like the idea of getting the advantages of a little OC/UV without having to run Pimp my CPU.
I have gotten a clear increase (hours more idle time) by simply turning off 4G and only toggling it on when I need it. I use Pandora a lot and it ironically runs better at 2G when I am bicycling (less drops interruptions in the streaming as I move around).
Click to expand...
Click to collapse
Really? I found that these 2 kernels gave me better battery life then the stock cm7 kernel. Also can you add antutu benchmark to the list?
maxesxp said:
Really? I found that these 2 kernels gave me better battery life then the stock cm7 kernel. Also can you add antutu benchmark to the list?
Click to expand...
Click to collapse
you are also quoting and talking about a response from 6 months ago which was beginning stages for cm7 on this phone especially kernels lol... Glad you are getting great performance and battery though.
mt3g said:
you are also quoting and talking about a response from 6 months ago which was beginning stages for cm7 on this phone especially kernels lol... Glad you are getting great performance and battery though.
Click to expand...
Click to collapse
LOL oops I need to start learning to read dates.. -.-
Sent from my LG-P999 using Tapatalk
some one should run tests again
I tested Trinity vs Faux in AnTuTu and got pretty much same results on charger,but off charger Trinity got about 50 more (6000 off charger and 6125 while charging)
I use UV kernels clocked at 1100.
Switched to Faux because Trinity has bugs like reboot hangs the phone and sometimes waking up take a while. Also boot image and animations are not that nice and boot sound with kernel doesn't even seem to be working.....
Trinity 6004-6120
Faux 5918-6124
CM Stock around 5500
kolyan said:
some one should run tests again
I tested Trinity vs Faux in AnTuTu and got pretty much same results on charger,but off charger Trinity got about 50 more (6000 off charger and 6125 while charging)
I use UV kernels clocked at 1100.
Switched to Faux because Trinity has bugs like reboot hangs the phone and sometimes waking up take a while. Also boot image and animations are not that nice and boot sound with kernel doesn't even seem to be working.....
Trinity 6004-6120
Faux 5918-6124
CM Stock around 5500
Click to expand...
Click to collapse
Why are you getting such low scores? Not OC'd maybe? I'm using Fauxs newest kernel and my Antutu score was 7566. Average scores around 7300-7600
Sent from my LG-P999 using xda premium
mike7169 said:
Why are you getting such low scores? Not OC'd maybe? I'm using Fauxs newest kernel and my Antutu score was 7566. Average scores around 7300-7600
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Faux's newest kernel is ~1.5 correct?
He's probably using the Trinity battery saving kernel clocked at 1.1 and undervolted.
I use the Trinity 1.1GHz kernel and undervolt to -200mV (for the lower ones, leave the top three at stock for stability reasons) and I score around 6100 in Antutu.
redmonke255 said:
Faux's newest kernel is ~1.5 correct?
He's probably using the Trinity battery saving kernel clocked at 1.1 and undervolted.
I use the Trinity 1.1GHz kernel and undervolt to -200mV (for the lower ones, leave the top three at stock for stability reasons) and I score around 6100 in Antutu.
Click to expand...
Click to collapse
That makes sense. I just did a benchmark @1.1ghz and I got 6007. Ya the Faux kernel max is @1.5ghz. Its undervolted too, not much, just enough to get great battery life.
Sent from my LG-P999 using xda premium
I said in post that I use UV kernels clocked at 1100mhz
I now use Trinity Kernel because Faux did not have 216Mhz option in SetCPU. I also UVed by -25 for now and set charging profile to 400+ Mhz to avoid SoD
I wonder whats the difference in battery life if you use 1100Mhz or 1500Mhz ?
kolyan said:
I said in post that I use UV kernels clocked at 1100mhz
I now use Trinity Kernel because Faux did not have 216Mhz option in SetCPU. I also UVed by -25 for now and set charging profile to 400+ Mhz to avoid SoD
I wonder whats the difference in battery life if you use 1100Mhz or 1500Mhz ?
Click to expand...
Click to collapse
It's a significant difference. I don't have any data to back it up. But I've accidentally left it on the max after a benchmark and it would be in a free fall. Especially when playing a 3D game like MC3
Sent from my LG-P999 using xda premium
I've tried using both Kernels as well as stock. Granted they both seem to run better then stock, I'm currently on Trinity with Standard Voltage, because the Under voltage versions of both Faux and trinity seemed to freeze on reboots for whatever reason. They both appear to run about the same set at 1100 which is what I've set to.
I'd like to say thank you for performing scientific and useful benchmarks!
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
EDIT:
So I was asked what kernel I'm using... I will post my ROM + KErnel! and just to let you know, my G2x has never had any problems so that may be way my G2x can get -200 on 500 and 400
And I am using faux's CM7 Kernel Version 0.2.4
Full name:
"2.6.32.41-CM7-Faux123-v0.2.4
Mod version
CyanogenMod-EagleBlood_v1.2
Im new to setcpu, good thread for me to learn a bit more from other users...
Sent from my LG-P999 using XDA App
Yes I'm trying to decide on SetCPU or PimpMyCPU so any info is appreciated
GManLynx said:
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
Click to expand...
Click to collapse
What kernal are you using?
GManLynx said:
So I have...
My G2x Is running at 1gz\.4 I don't find a need to OV it...
The UV is set at -50 at 1gz and at 800 it is -100 and at 500 and 400 at -200mv.
What are your sets? I would like to see other people's choices. I will report on my battery life later. I can't today since I have been going into recovery mode all morning.
Ps. As profiles go...
I have screen off set to 800/400. I don't like it lagging when i turn my screen on.
I can run stress test easily with my settings. No hiccups or anything.
Click to expand...
Click to collapse
How are you not getting reboot problems with 400 at -200mv? I'm using faux's froyo kernel and when I undervolt at -100mv i get rebooting problems
I replied to your comment in my main post, since other people may be interested in that and that will cause them not to scan the pages.
Bump :\ I would like input
so how is your battery life?
Bad. Something about those settings messed it up. I much prefer just using the custom rom default kernel its much better on the battery
Sent from my LG-P999 using XDA Premium App
My chip could only use faux's OC 1.2ghz, using the kernel OC 1.5 would cause my phone to boot loop. I could go stable @ faux OC 1.2 with minimum UV, getting qudrant score of atleast 3000 - 3500. Another kernel that i tried is MOrfic's, I can go stable up to 1.4 Ghz/minimum UV- quadrant of atleast 4000-4300. I believe i have what they say as the "weak chip" though running OC @ 1.4 ghz doesn't make it look weak. Thanks to the great DevS!
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
DirtyPISTOLA said:
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
Click to expand...
Click to collapse
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
fcisco13 said:
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Alright thanks will try
Sent from my LG-P999 using Tapatalk
I've seen some general advice not to UV for anything over 1ghz speeds as well, but it may not hurt to try if you want and adjust as needed for stability.
I'm running on a -75mv at 1.5Ghz faux kernel 0.4.7..
Perfectly stable, benchmarked AnTuTu, Quadrant, and all those other good stuff.
I have not tried -100mv yet, I doubt it will be stable.
Every phone is different, but I run mine at -20 up to 1 G, and -10 for the rest.
Mine I cant undervolt shoot I have to keep my minimum frequency at 500 to be stable, course I can also run at 1.5 all day (I keep it at 1.2).
Well I guess I can't say I cant UV since I use pimp my cpu and it only gives you options in 25 increments, maybe I would be stable at like -10. But coming from my galaxy s 4g where I could UV over -150 and still be stable, that just doesnt even sound worth doing.
Edit: I just thought about it and maybe the reason I cant UV (more) is because I'm using fauxs pre UV/OC kernel, so I dont even know what stock voltage is. But comparing to my sgs4g at stock voltage I am running considerably lower voltages on the g2x.
The faux thread says it's pre uv at -50 across the board.
Beekersguy said:
The faux thread says it's pre uv at -50 across the board.
Click to expand...
Click to collapse
I been running it so long and flashed so many friends phones I can't even remember details anymore!
Sent from my LG-P999 using xda premium
Hey guys I'm planning on overclocking my Samsung Galaxy S 4G. What would be the best frequencies up to 1.5GHz?
to like half flame, but why would you want to overclock? im on Valhalla Black and im undervolted and i still run ridiculously smooth
Sent from my SGH-T959V using xda premium
Johnmonkey0 said:
Hey guys I'm planning on overclocking my Samsung Galaxy S 4G. What would be the best frequencies up to 1.5GHz?
Click to expand...
Click to collapse
I have read several times that we do not have a kernel to support overclocking. If that has changed - hopefully somebody will clarify. If you mean using Tegrak Overclock - you can use it to undervolt.
dsexton posted these values in A.S. Shot v15:
dsexton702 said:
Values for super duper battery life but keeping amazing speed
Go into tegrak and put in the following:
level0 - 1000 - 1155 - 1065
level1 - 800 - 1040 - 1035
level2 - 400 - 955 - 960
level3 - 200 - 835 - 950
level4 - 100 - 825 - 930
IF THOSE VALUES CAUSE REBOOTS ADD 10-15 ON VOLTAGES FOR EVERY LEVEL
Click to expand...
Click to collapse
Hope that is more helpful.
Lumin
With tegrak paid you can OC the phone as well as UV it. I haven't in a while but the option is there with that app.
Here's an old post but pretty sure it would work with the current kernel.
http://forum.xda-developers.com/showthread.php?t=1109170
Just OC'd to 1.5 using D's values from the above post. Left the governor as ondemand. Got 4348 on quad using noop with MIUI RC3fixed. So yeah it still works. Be warned it is not stable. Phone locked up as soon as I put it to sleep. To be safe stick with 1.3 or less by choosing CPU max in tegrak. If you want to play with higher frequencies make sure Set on Boot is NOT checked. Fun to playu with but really not needed.