OTB 2.6.35 0704
Main Features
2.6.35 Kernel based off of work done by TeamHacksung
Overclock up to 1400 MHz
UV control via sysfs using Voltage Control app
Voodoo Sound v9 - thanks to supercurio and project-voodoo
CWM4 with options to wipe voltage settings
jhash3 table for .35 kernel
cifs.ko and tun.ko modules included - location /system/lib/modules/
BLN - does not require app to use
CONFIG_S5P_HIGH_RES_TIMERS_HZ from 256hz to 1000hz
Updated cflags
In call audio adjustments courtesy of jt1134
Readahead from 128kb to 1024kb
Kernel Hz from 256Hz to 1000Hz
Backported optical driver courtesy of jt1134
Upstream changes from teamhacksung
Disable presets for voodoo sound
Ambient light sensor fixes courtesty of jt1134
Adjusted mic levels to ED01 level
DEEP_SLEEP FIXED - new for 0704, BIG THANKS to jt1134 and happy 4th everybody.
Other misc tweaks
Frequencies and Voltages
1400Mhz @ 1450mV
1300Mhz @ 1400mV
1200Mhz @ 1350mV - should be safe overclock considering samsung left code for it in source
1000Mhz @ 1250mV - do not recommend uv more than 25 mV here, already slightly uv'ed
800Mhz @ 1200mV - do not recommend uv more than 25 mV here, wake step
400Mhz @ 1050mV
200Mhz @ 950mV
100Mhz @ 950mV - do not recommend uv more than 50 mV here, may cause songs to skip
I/O Schedulers
noop
deadline
cfq
sio - default
bfq
CPU Governors
smartass
interactive
conservative
userspace
powersave
ondemand - default
performace
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1600Mhz in testing, coming soon.
Recommended Installation Instructions
Install JT's CyanogenMod 7 (fascinatemtd) or Andmer's AOSP MIUI (fascinatemtd)
Put kernel zip on sdcard
Reboot to recovery using shutdown option or adb reboot recovery
Wipe cache, dalvik, and voltage settings (especially important when flashing BFS version)
Flash kernel zip via orange cwm
Reboot
Done
*** Do not reboot to recovery using 3 button method ***
Mini How-To
Do not use setcpu. Use voltage control from market. Test settings for at least a day before applying at boot. When testing just apply for now. Users are encouraged to share their settings. If you would like a way to keep track of how much time cpu spends in each state I recommend cpu spy from the market.
Thanks
jt1134 of course he almost single handidly got cm7 working on the Fascinate
TeamHacksung for the amazing work they have done for sgs phones
CyanogenMod Team
supercurio for all of the wonderful work on project-voodoo
adrynalyne for his roms and odin packages
enderst for allowing me to build on his machine....that is awesome and so l33t to ssh to build on a remote machine
neldar, taninm, rodderick, koush, thomasskull666, raspdeep, imnuts, khasmek, sirgatez, existz, nullghost, ssewk2x, netarchy, codeworkx, coolya, antimn, morific, nullghost, and GizmoDroid
Dank for the mirrors
All of the testers
Great people in IRC at #samsung-fascinate on FreeNode and anyone I might have missed.
*** If I missed giving you credit feel free to pm me and I will rectify as soon as possible. ***
Use this kernel at your own risk. I am not responsible for any damages to your phone. Be especially careful when overclocking.
Current Kernels
STABLE
OTB 2.6.35.7 CFS 0704
OTB 2.6.35.13 CFS 0704
Flash in orange recovery after you are already on JT's CyanogenMod 7 (fascinatemtd) TEST or AOSP MIUI (fascinatemtd). This kernel will not fix anything that is wrong with cm7, but should not break anything that is currently working either.
TESTING
OTB 2.6.35.7 CFS 0710 - 1600Mhz kernel
OTB 2.6.35.13 CFS 0710 - 1600Mhz kernel
Older Kernels
Mediafire link to mtd cm7 kernels
Misc
Voltage Control Settings Wiper Zip
My Github for source
Reserved for future use
Thanks a bunch nem, been test running this since yesterday and it flies.
Had never been able to achieve 1.4Ghz stable until now
Can this be flashed with the purple recovery
Sent from my DROIDX using XDA App
No this must be flashed in orange recovery that comes with .35 cm7. To get there go to power off choose reboot, and then choose recovery.
Or you can get there via adb
adb reboot recovery
Thats right... the rom comes with a recovery. Got all the files..bit nervous for some reason...I'm going in!
Sent from my DROIDX using XDA App
Can't find Voltage Control main App in the Market, just the unlock key app. Any idea where to get it?
vai1018 said:
Can't find Voltage Control main App in the Market, just the unlock key app. Any idea where to get it?
Click to expand...
Click to collapse
If you can't find it on market try here. http://forum.xda-developers.com/showthread.php?t=829731
nemesis2all said:
If you can't find it on market try here. http://forum.xda-developers.com/showthread.php?t=829731
Click to expand...
Click to collapse
That was just what I needed, thanks.
Sent from my SCH-I500 using XDA App
not that quadrant matters, but I managed to pull out a 2347 with the stats below
1400 -50
1000 -50
800 -50
400 -75
200 -100
100 -100
BFQ/OnDemand
18.847 Linpack..
[edit: first run did 2180 w/ 1400 @ -25 but i got a text during the test, reduced 1400 to -50 and tried again to get the number above)
Whats everyones take on the best scheduler and governor combo here?
Neuman.Tim said:
not that quadrant matters, but I managed to pull out a 2347 with the stats below
1400 -50
1000 -50
800 -50
400 -75
200 -100
100 -100
BFQ/OnDemand
18.847 Linpack..
[edit: first run did 2180 w/ 1400 @ -25 but i got a text during the test, reduced 1400 to -50 and tried again to get the number above)
Whats everyones take on the best scheduler and governor combo here?
Click to expand...
Click to collapse
I have good results with smartass and sio. 2500+ quad and about 19.8 linpack.
Neuman.Tim said:
not that quadrant matters, but I managed to pull out a 2347 with the stats below
1400 -50
1000 -50
800 -50
400 -75
200 -100
100 -100
BFQ/OnDemand
18.847 Linpack..
[edit: first run did 2180 w/ 1400 @ -25 but i got a text during the test, reduced 1400 to -50 and tried again to get the number above)
Whats everyones take on the best scheduler and governor combo here?
Click to expand...
Click to collapse
I got a 1450 and 1700 with these same stats. With sio and Smartass I got 2385.
Pulled out 2507 after switching to sip and smartass. 1400 actually got a bit unstable for a few earlier but it seems fine again with these settings.
Nemesis, what are your voltages? And has anyone else noticed that regardless of disabling a frequency it still gets used unless its over the cap?
Sent from my SCH-I500 using XDA Premium App
Neuman.Tim said:
Nemesis, what are your voltages? And has anyone else noticed that regardless of disabling a frequency it still gets used unless its over the cap?
Sent from my SCH-I500 using XDA Premium App
Click to expand...
Click to collapse
Its been that way in OTB's kernels for many versions, the freq slot states control is only 100% with conservative mode.
Ah well..no big. They are only being used about 1% lol
Sent from my SCH-I500 using XDA Premium App
i was just wondering is it possible to run this kernel without using anything like voltage control just flashing it and run it or do you need to use voltage control or something like it???
mrtonee said:
i was just wondering is it possible to run this kernel without using anything like voltage control just flashing it and run it or do you need to use voltage control or something like it???
Click to expand...
Click to collapse
You do not have to use voltage control or any other app to run this kernel.
nemesis2all said:
You do not have to use voltage control or any other app to run this kernel.
Click to expand...
Click to collapse
thank you also your doing a great job...........
Updated op. Should work on andmer's miui build as well.
wtg go nemesis, another fine release. Works like a charm on my mes with the 6/11 jt did of cm7 for us.
100 - 125
200 - 100
400 - 100
800 - 25
1000 -25
1200 - 25
sio/smartass get's me about 17.067 on my fourth or fifth linpack run. Remember guys, overclocking dangerous, especially when you push it up towards 1400, 1600. It's cool and all, but it seriously will cook your phone eventually. Just a reminder!
Have fun!
Related
33% 0C Kernel is finished and 2900+ Quadrant has been benched.
Disclaimer
As I HAVE NOT tested Uruk 0.2 I can't verify it's compatibility!
As I have not tested this on other CPU's I can not guarantee stability!
I will try to help you as much as I can if anything goes wrong, but I can't promise a fix.
Download
http://dl.dropbox.com/u/13655025/zImage
Features
5 slots {300MHz, 600MHz, 1000MHz, 1250MHz, 1330MHz}
300MHz, 600MHz, 1000MHz undervolted
1250MHz at the voltage 1000MHz was working on
1330MHz at the voltage that was said to be a very safe voltage for this cpu (droid x users have been using voltages 0.1V+ higher!)
EXT4 support and therefore support for Uruk 0.1 (and I suppose Uruk 0.2? need confirmation on that since I'm using a modified Uruk 0.1)
Usage
To use this kernel please set your SetCPU at 300-1330 (1250 if 1330 appears to be unstable for you)
The Archos stock video player seems to override SetCPU settings when using the 5th slot as the lowest cpu frequency.
The Archos stock video player will not play video when started with the frequency above the 4th slot (I think, I'm quite sure of that) it will then override the DSP frequency which will not suffice for video decoding (also speculation). I fix this by running a SetCPU 300-1330 with an ondemand governor (which seems to me, the most useful governor anyway)
Result
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This score was gained with a 1330MHz performance governor. (this is stable for me in games and other apps, only problem is the Archos media player)
Risk
This has been undervolted, overclocked and tested on MY device!
Each CPU made, although the same model is unique. There is a possibility that these clocks are far to unstable to use on your device, so please!
This may harm you CPU AND/OR BATTERY use at your own risk!
Post your results! Describe crashes as accurate as possible if there are any.
I can then release a second version that's more stable for everyone's device.
Thanks for your instructions.
Actually, I do the same as yours in my kernel except that I keep stock voltage when using 1100Mhz
{S1100M, VDD1_OPP5, 0x3c, 0x0, 0x0},
At least, we have proved that we are modifying the same file
ardatdat said:
Thanks for your instructions.
Actually, I do the same as yours in my kernel except that I keep stock voltage when using 1100Mhz
{S1100M, VDD1_OPP5, 0x3c, 0x0, 0x0},
At least, we have proved that we are modifying the same file
Click to expand...
Click to collapse
I think it should be stable at stock, the DSP is just being a ***** lol.
Have you guys identified the max voltages for these components? I would not want to have a device damaged due to overvolting. I do understand there is a risk but go over the max is typically not acceptable to any over clocking.
One other thing how are you validating stability? In otherwords what program are you using to induce load?
Tzbob said:
I think it should be stable at stock, the DSP is just being a ***** lol.
Click to expand...
Click to collapse
I'm testing stability now by running the programs that gave problems with the previous overclocking attempts, Angry Birds, stock Movie player(this one is the real *****), Linpack, Quadrant and SetCPU 'stress' test
I have not yet identified the maximum voltage as I can't seem to find a datasheet that says anything about this, I've been slowly up to 1.4V volts now to see if how warm it gets etc.
Stable 1250MHz is done, now incrementing in steps of 10MHz, I'll have a kernel release soon with undervolted and overclock slots.
UPDATE: http://code.google.com/p/milestone-overclock/wiki/KernelModule
They seem to use very high voltages O.O they say the maximum vsel is 96 as well
my 1250MHz clock is stable at vsel 64, I'm faiiiirly sure we have the same OMAP3630_1000's in our devices?
Im curious how did you overcome the DSP issue?
I still haven't really sorted the DSP issue with the Archos media player, a work-around is using a governor that allows a frequency below the last slot, I THINK
It's all speculation but it seems to work, when I have the 1250MHz as the 5th slot with my frequency on 1250MHz videos do not play. Using the same settings with the 1250MHz parameters on the 4th slot it does, the media player seems to be a very weird thing.
How is the battery performance?
I'll try this with Uruk 0.2, and let you know how it goes after some use!
Edit: After running quadrant, there doesn't seem to be any difference in score (1658)
But it is running smoothly with no noticable bugs at the moment.
Thanks Tzbob.
Can you tell us the frequency to voltage settings that you have changed? Let us find out together the max. stable frequency of archos CPU
ardatdat said:
Thanks Tzbob.
Can you tell us the frequency to voltage settings that you have changed? Let us find out together the max. stable frequency of archos CPU
Click to expand...
Click to collapse
After doing some reading on Droid forums it seems that each CPU behaves very differently, but they also succeeded in huge undervolts and OCs of 1.3GHz.
The N900, although an older version of this cpu sports an overclock on both CPU and DSP so perhaps that's something we could do? Also GPU OC is still something that could be considered but for now, this will have to do^^
/*OPP1 - 0.9875V STABLE 300*/
{S300M, VDD1_OPP1, 0x1e, 0x0, 0x0},
/*OPP2 - 1.15V STABLE 600*/
{S600M, VDD1_OPP2, 0x2b, 0x0, 0x0},
/*OPP3 - 1.3375V STABLE 1000*/
{S1000M, VDD1_OPP3, 0x38, 0x0, 0x0},
/*OPP5 - 1.375V STABLE 1250*/
{S1250M, VDD1_OPP4, 0x3c, 0x0, 0x0},
/*OPP5 - 1.4V STABLE 1330*/
{S1330M, VDD1_OPP5, 0x42, 0x0, 0x0},
Ignore the voltage in the comments as I haven't gotten around calculating them yet.
Please how do you set undervoltage cpu options? Thanks a lot
mindsurfer said:
Please how do you set undervoltage cpu options? Thanks a lot
Click to expand...
Click to collapse
The undervolted options are added into this kernel, by using it you will be using an undervolted cpu.
If you strictly want to use undervolted cpu options and refrain from any overclocks please use SetCPU from 300-1000MHz.
it is very dangerous for the tablet to increase a CPU !
cajl said:
it is very dangerous for the tablet to increase a CPU !
Click to expand...
Click to collapse
It is dangerous for any device to increase the CPU, I haven't denied, or stated something else, anywhere.
You should do this at your own risk as it may harm your CPU/Battery/Overall device.
It's dangerous to overclock anything, yet it's such a common thing to do.
yes !
mark in red this option !
but thank you fot that
Please would it be posoble to make only 300,1000,1250,1333 undervolted version? I mean specially without 600 mhz, because i think that it makes archos less fluent.. comparing to only 300/1000 original urukdroid version. Or maybe changing 600 to 800?
I'm working with sauron now to add functionality to the official Uruk kernel. We'll add more testing to it than I did with this kernel to assure good performance.
I won't bring out any more kernels as I hit the limit on this one, 1330MHz is the maximum I could get (without getting really dangerous). It's also overkill and purely for benching high scores
So, I was wondering which would be the better to run on an OC kernal, SetCpu or Voltage Control. I'm using SetCpu (cause I paid for it lol) but notice that a lot of people talk about using Voltage Control instead of the later. Is this due to options, or is it simply because it's free? Any help is appreciated, and anybody that gives me a non-flaming serious response will get a thanks lol!
Running:
Trigger v2.7.2
Tigersblood v2 OC Kernal
(all statistics may change without notice lol!)
TXLunchbox said:
So, I was wondering which would be the better to run on an OC kernal, SetCpu or Voltage Control. I'm using SetCpu (cause I paid for it lol) but notice that a lot of people talk about using Voltage Control instead of the later. Is this due to options, or is it simply because it's free? Any help is appreciated, and anybody that gives me a non-flaming serious response will get a thanks lol!
Running:
Trigger v2.7.2
Tigersblood v2 OC Kernal
(all statistics may change without notice lol!)
Click to expand...
Click to collapse
I just installed Voltage Control 1 hour ago. So far I like it better than SetCpu which I also paid for it. Voltage Control has options to lower the votage in various steps. The voltages can be lowered without needing to overclock the CPU.
Installed it after installing Tigers Blood V2 kernel. But now I want to see how my battery life is undervolted and not overclocked.
I prefer voltage control but I also have the paid set cpu from before when I didn't know about voltage. Voltage let's you uv (undervolt) your frequencies to conserve some battery life.
Trigger + Tigerblood = Winning
Well it just depends on what your trying to do, in example, if you want to set profiles and Oc, I would use Setcpu, if your trying to undervolt your clock speed, and have Oc, I would use Voltage Control. I use both because I'm trying to Overclock, and have lower voltages
Wow guys! Thanks so much! This is really helpful info.
Bambam, what settings are you using with Tigers blood and Trigger?
Sent from my SGH-T959 using XDA Premium App
TXLunchbox said:
Wow guys! Thanks so much! This is really helpful info.
Bambam, what settings are you using with Tigers blood and Trigger?
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
My settings, this might not work for your phone, every phone is different. Battery life seems great so far.
100mhz -50 = 900mv
200mhz -50 = 900mv
400mhz -50 = 1000mv
800mhz -50 = 1150mv
1000mhz -50 = 1225mv
1200mhz -25 = 1275mv
Good luck.
I personally use SetCpu for OC because i've been using it since the Nexus One and i think its just the better app b/c of ease of use
Again guys (or gals), I really appreciate all the feedback. Thanks have been given appropriately as promised. Sorry about the delay. This has been the first day that I could get to my laptop lol!
One thing I have noticed is that when SetCpu is set to "performance" the phone has difficulty pulling up the multi-tasker when long pressing the home button. This is how I get to Task Manager to clear things up before running benchmarks, so it's somewhat of a big deal to me. I'm sure there are other ways around it. I know on the stock OS that there is a Task Manager widget, but that has seemed to have disappeared with the ROMs that I've ran.
GTOJim said:
My settings, this might not work for your phone, every phone is different. Battery life seems great so far.
100mhz -50 = 900mv
200mhz -50 = 900mv
400mhz -50 = 1000mv
800mhz -50 = 1150mv
1000mhz -50 = 1225mv
1200mhz -25 = 1275mv
Good luck.
Click to expand...
Click to collapse
Thanks for the info Jim, I'm really trying out different UV settings. I'm running just the standard right now cause other settings I've tried have caused me the SOD lol!
I don't know if this applies anymore but TW used to suggest the following setting when using SetCPU.
Conservative, do not set on boot-up. Minimum clock speed of 200mhz. Some phones would not wake up using the default of 100mz minimum. As I remember they advised against setting up any profiles.
Yeah, I've known about the no profiles thing. I think I've stuck to using Voltage Control as I haven't had nearly as much issues with it.
Some of you may recall my similar thread for SetCPU...
http://forum.xda-developers.com/showthread.php?t=1321136&page=8
Well I recently switched over from SetCPU to VC and am quite happy with it... figured I'd make a thread for users to share their experiences with the app...
First a few ground rules...
You must share the following info...
Kernel, Rom, Paid of Free version of the app, Screen on time, and all your settings in the fields in the app. Also include your average battery life on a full charge and if you're on the stock battery/charger or not. *Pics are encourages and appreciated.*
my config is in my sig...
I'm also using the paid version of VC which is awesome and I have undervolted quite a bit.
*The following voltages are being tested for stability*
Noop + Ondemand
100mhz-1200mhz
1200mhz: 1200 mV
1000mhz: 1050 mV
800mhz: 950 mV
500mhz: 850 mV
200mhz: 850 mV
100mhz: 825 mV
GPU 114-267mhz
114 @ 800
267 @ 950
I average about 24hrs - 26hrs of battery pending my use with about 3hrs of screen on time.
Purpose of this thread is to exchange information on how to get a better performing and more battery efficient phone using some tweaks.
P.S. Remember all phones are different and you should NEVER expect someone else's config to work for you. The purpose in this is to get a base line for tweaking and help out users with little or no knowledge about getting good battery life and also how to make their phone faster/more efficient.
Thanks
Nice to see a similar thread for the i777 model running Entropy's kernel as well. As I always say, caring is sharing lol
Crack on mate. This kind of info makes it so much easier for new users to get started with undervolting without having too many trial and error headaches.
If anyone wants to know my settings for Siyah and VC, then click the MagicConfig link in my sig.
Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
geko95gek said:
Nice to see a similar thread for the i777 model running Entropy's kernel as well.
Crack on mate. This kind of info makes it so much easier for new users to get started with undervolting without having too many trial and error headaches.
If anyone wants to know my settings for Siyah and VC, then click the MagicConfig link in my sig.
Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
Click to expand...
Click to collapse
Thanks for the support bud. Much appreciated.
vc-
1600mhz-1425mV
1400mhz-1275mV
1200mhz-1175mV
1000mhz-1075mV
800mhz-975mV
500mhz-875mV
200mhz-850mV
Lasts more than 24 hours almoust all the time.
Najuto9tail said:
vc-
1600mhz-1425mV
1400mhz-1275mV
1200mhz-1175mV
1000mhz-1075mV
800mhz-975mV
500mhz-875mV
200mhz-850mV
Lasts more than 24 hours almoust all the time.
Click to expand...
Click to collapse
great voltages... Thanks for sharing.
Is there anything you guys are doing to test each individual frequency? Or just setting it at that frequency?
Sent from my SGH-I777 using Tapatalk
K Rich said:
Is there anything you guys are doing to test each individual frequency? Or just setting it at that frequency?
Sent from my SGH-I777 using Tapatalk
Click to expand...
Click to collapse
Well personally I set a voltage then assign my min and Max to the frequency that corresponds to the newly set voltage and then run a benchmark to see if any issues occur.
Sent from my kick ass Galaxy S II
Alucardis666 said:
Well personally I set a voltage then assign my min and Max to the frequency that corresponds to the newly set voltage and then run a benchmark to see if any issues occur.
Sent from my kick ass Galaxy S II
Click to expand...
Click to collapse
Exactly what I've been doing. If anyone has any input, please do tell.
Cpu
200mhz-850mv
500mhz-875mv
800mhz-950mv
1000Mhz-1050mv
1200mhz-1150mv
Gpu
100Mhz-800mv
267Mhz-950mV
Not getting the battery life i would like, i still drop a few percent per hour when not doing anything, but im pretty sure thats because im on 2.3.6! ive been trying to do that gpu 3 step thing i keep hearing about via scripts but it seems to mess up my voltage settings!
anyway here they are! i cant wait to see what others have!
A question: Do you use both VC and SetCPU? Won't the governor setting in VC clash with the governor settings/advance settings and profiles set in SetCPU?
Fearing that, just today morning I switched to VC Lite from SetCPU (and froze SetCPU) as I wanted scheduler control.
VC Lite settings:
Scheduler: noop
Governor: conservative
Frequencies: 200-1000
Voltages:
1600 - 1400mV
1400 - 1250mV
1200 - 1200mV
1000 - 1100mV
800 - 1000mV
500 - 900mV
200 - 850mV
---------- Post added at 10:16 PM ---------- Previous post was at 10:13 PM ----------
Alucardis666 said:
Well personally I set a voltage then assign my min and Max to the frequency that corresponds to the newly set voltage and then run a benchmark to see if any issues occur.
Sent from my kick ass Galaxy S II
Click to expand...
Click to collapse
Do you simply run something like Antutu Benchmark? Or does VC Pro have stress testing?
K Rich said:
Exactly what I've been doing. If anyone has any input, please do tell.
Click to expand...
Click to collapse
You'll find that you can run lower voltage on a forced single stepping than you can when the CPU has several steppings to choose from. For some reason the CPUs don't play well if you go to low or if it has to make to big of a jump between certain steppings.
\/icious said:
You'll find that you can run lower voltage on a forced single stepping than you can when the CPU has several steppings to choose from. For some reason the CPUs don't play well if you go to low or if it has to make to big of a jump between certain steppings.
Click to expand...
Click to collapse
running Antutu to test each step?
jazzboyrules said:
A question: Do you use both VC and SetCPU? Won't the governor setting in VC clash with the governor settings/advance settings and profiles set in SetCPU?
Fearing that, just today morning I switched to VC Lite from SetCPU (and froze SetCPU) as I wanted scheduler control.
VC Lite settings:
Scheduler: noop
Governor: conservative
Frequencies: 200-1000
Voltages:
1600 - 1400mV
1400 - 1250mV
1200 - 1200mV
1000 - 1100mV
800 - 1000mV
500 - 900mV
200 - 850mV
---------- Post added at 10:16 PM ---------- Previous post was at 10:13 PM ----------
Do you simply run something like Antutu Benchmark? Or does VC Pro have stress testing?
Click to expand...
Click to collapse
I no longer use setcpu and I do run quadranrt or antutu usually. pro version has no such stress test, but if you ask me... one should be implemented in a future update.
What amazes me is the difference a rom can make. Running Siyah 2.6.11 with the exact same VC settings (the ones in the OP of this thread) on CM7 nightly and ShoStock 1.9.1 and running Quadrant the results are about 1000-1500 points higher on cm7 nightly. From a user feel perspective they are both smooth as butter but I wonder what makes CM7 so much faster on the synthetic benchmark. Has to be a storage I/O thing or something. Battery life seems to be better for me on ShoStock though.
kennonk said:
What amazes me is the difference a rom can make. Running Siyah 2.6.11 with the exact same VC settings (the ones in the OP of this thread) on CM7 nightly and ShoStock 1.9.1 and running Quadrant the results are about 1000-1500 points higher on cm7 nightly. From a user feel perspective they are both smooth as butter but I wonder what makes CM7 so much faster on the synthetic benchmark. Has to be a storage I/O thing or something. Battery life seems to be better for me on ShoStock though.
Click to expand...
Click to collapse
Yea, I too have noticed slight variations on different roms as well.
CM7 nightly 01/24/12
I/O Scheduler : SIO
Governor : ondemand
200Mhz-1200Mhz
1200Mhz : 1200mV
1000Mhz : 1100mV
800Mhz : 1000mV
500Mhz : 900mV
200Mhz : 875mV
Phone has been on for 6hr with 1hr 5mins screen on time and I'm sitting at 80%
Got 6520 in Antutu at 1200Mhz with this setup
K Rich said:
running Antutu to test each step?
Click to expand...
Click to collapse
I used to test steps individually but again what's stable individually might not be stable with all the other steps included. I usually will quickly run through apps like mms, email, video, web, and also run a few BMs like antutu
A useful app with all the bells and whistles, with the capabilities of almost every utility app available is ROM Toolbox. I use it to edit voltage, CPU frequency, build.props, etc. Look into it if you're tired of trying hundreds of different programs for different features.
Sent from my SAMSUNG-SGH-I777 using xda premium
geko95gek said:
Nice to see a similar thread for the i777 model running Entropy's kernel as well. As I always say, caring is sharing lol
Crack on mate. This kind of info makes it so much easier for new users to get started with undervolting without having too many trial and error headaches.
If anyone wants to know my settings for Siyah and VC, then click the MagicConfig link in my sig.
Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
Click to expand...
Click to collapse
I've been using those settings with shostock rom and I have to say it has been working wonderfully
Sent from my SAMSUNG-SGH-I777 using xda premium
vc and set cpu
How do they get alone? Im afraid they might not like each other.
Please share you voltage and CPU frequency for your current setup. Hopefully this will help provide a foundation for other to find out how low we can undervolt and overclock on the new kernels coming out
Sent from my ADR6425LVW using xda app-developers app
cincyelite22 said:
Please share you voltage and CPU frequency for your current setup. Hopefully this will help provide a foundation for other to find out how low we can undervolt and overclock on the new kernels coming out
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I have DSB's kernel underclocked to 1.3 GHz, undervolted -100 mV across all freq, and lulzactive tuned for battery life. It runs smooth and the battery life is insane. :good::laugh:
Argumentation said:
I have DSB's kernel underclocked to 1.3 GHz, undervolted -100 mV across all freq, and lulzactive tuned for battery life. It runs smooth and the battery life is insane. :good::laugh:
Click to expand...
Click to collapse
if -100mV across the board causes issues the -75 should do it. can't wait for soap version. I can't go back on sense based roms now
dyetheskin said:
if -100mV across the board causes issues the -75 should do it. can't wait for soap version. I can't go back on sense based roms now
Click to expand...
Click to collapse
Yeah 100mV across the board is a little much because dsb has already undervolted a little...
Po1soNNN said:
Yeah 100mV across the board is a little much because dsb has already undervolted a little...
Click to expand...
Click to collapse
Anyone else care to share a good set of low but stable voltages for DSB's kernel? Sometimes when I do -50 mv across the board, I get lockups, and I am hoping that it is just the low frequency voltages that are going too low (192 mhz to like 762 mv might be too low).
drkow19 said:
Anyone else care to share a good set of low but stable voltages for DSB's kernel? Sometimes when I do -50 mv across the board, I get lockups, and I am hoping that it is just the low frequency voltages that are going too low (192 mhz to like 762 mv might be too low).
Click to expand...
Click to collapse
I'm undervolted 75mv across the board I think, with 725 mv at 192 MHz. I think 50-75mv is pretty standard for these phones to handle, but it will definitely vary per phone. My phone handles 1.8GHz okay, but there are plenty of others that don't. I'm sure there's similar variability in the undervolting as well.
When replying, can you fellas also include screen on time? It's hard to gauge "OMFG The battery life is so incredible!" This does'nt give me any idea as to what you really mean. Are you lasting 16 hours but only have 30min screen on time?
Sent from my ADR6425LVW using Tapatalk
Vigor 360 v1.1, dsb 2.0.0 kernel OC 1836/192, UV -50, OnDemand, SIO on Incredicontrol.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Best score to date. Usually knocks down between 7600-7700 all day long. I don't really care about battery stats because my phone stays plugged in most of my 12 hour work day. When I am unplugged seems better than before the kernel installation.
Sent from my ADR6425LVW using xda app-developers app
I am using dsb's 2.0.1 kernel, now I just started using intellidemand governor and it is super fast. I don't really care about battery life too much so I want to use a performance-minded governor. I think I undervolted around 50mV and I did get one lockup using interactivex2 so I stopped using that one (with kernel version 2.0.0). Getting good benchmark scores running ViperREZ 1.0.3 (it's still the best rom ever). Freaking Linpack personal record: single core 54 , I think (84 multi). I think I am going to keep it at 1.72 GHz and see how good battery life is, and if those cpu settings stick after a while.
drkow19 said:
I am using dsb's 2.0.1 kernel, now I just started using intellidemand governor and it is super fast. I don't really care about battery life too much so I want to use a performance-minded governor. I think I undervolted around 50mV and I did get one lockup using interactivex2 so I stopped using that one (with kernel version 2.0.0). Getting good benchmark scores running ViperREZ 1.0.3 (it's still the best rom ever). Freaking Linpack personal record: single core 54 , I think (84 multi). I think I am going to keep it at 1.72 GHz and see how good battery life is, and if those cpu settings stick after a while.
Click to expand...
Click to collapse
50mv undervolt across the board with wheatley governor
mithong said:
50mv undervolt across the board with wheatley governor
Click to expand...
Click to collapse
You must be on Rage rom? I need multi-touch to work properly, since I'm developing another game right now, so I am waiting. I even tried CM9 with the multi-touch fix, and then flashed Snuzzo's kernel (the one with wheatley) but multi-touch was still wack.
Well it's been a few days of intellidemand, 1.72 GHz, and well my voltages go from 775 to 1300 mv. I even have the screen off speed limited using System Tuner, and it always stays at the right speed. I'm getting great battery life too! I just turned off ZRam, didn't seem to help, maybe hurt my performance a bit.
-75 is a good number
Sent from my ADR6425LVW using xda app-developers app
Luczative gov with -50 voltage (testing so far good I'm gonna drop another -25 later) cubed ics kernel 2.1.0 running latest nilsp sense 4 Rom.
When I was on ViperRez I used dsb's 2.0.1 kernel under clocked to 1.3 ghz with intellidemand and under voted - 125 mV across the board and would get about 12 hours unplugged and 1 hr and a half to 2 hours screen on time and still have around 30% left
Sent from my Adrenalized Rezzy
Running at - 75 uv, but settings don't seem to stick after reboot. What app are you guys using?
Sent from my ADR6425LVW using Tapatalk 2
abby_nitewolf said:
Running at - 75 uv, but settings don't seem to stick after reboot. What app are you guys using?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I use system tuner or you could use incredicontrol. Cpu master works as well
Sent from my Adrenalized Rezzy
This Kernel is based of the latest 4.4.4 Nexus 7 Sources,
This Kernel Is Designed to give you the best battery possible while still maintaining stocks speeds
Features
Voltage Control
-O3 Optimizations
Cortex a9 optimizations
Deadline Optimizations
FSYNC
Underclock CPU LP TO 480MHz
Underclock GPU From 416-400MHz and Decrease Min From 228MHz-137MHz
New Frequancy Table
Decrease Min Undervolt To 700mv
Make 2048 MAX VM and 32 Min VM
Disable Gentle Fair Sleepers
3x Faster Sqrt
Speed Up EXT4
Linaro Makefile Optimzations
KIll Some Debugging
Enable KSM And Make It Run
Always Set Noatime
Remove PAGE_ALLOC_COSTLY_ORDER
Optimized Linaro For ARMV7-a
Decrease VDD Core Voltage -50mv
Undervolted By Default -50mv
Extremely Low Mininmum Brightness In Bootup
Min Birghtness 5 Compared to 13 Stock
PLLC 1.2Mv>1.1Mv
Display Undervolted
Disable Android Logger
GPU UV 1.2Mv-1.1Mv
1.2MV-1.1MV vdd rail
Github- UPLOADING......
Kernel Attatched
Please give results from this kernel as i haven't been able to test a great deal
might not work on your device due to aggressive undervolting and underclocking
Enjoy
Is this kernel f2fs compatible?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Works fine but can you make it run with different schedulers like interactive and ondemand. At current state 4 cores are always active rendering them useless.
And kernel don't support root and kexec-hardboot. Other than that, it seems stable.
Also the clock rate won't fall below 380mHz, just noticed.
Please f2fs support! Good job
Enviado desde mi Nexus 7 mediante Tapatalk
ok i will push out a release today or tomorrow that will fix the bugs and make the kernel F2FS compatible
anything else you guys want?
Did u was in the Xperia Play forum section? anyway seems very interesting , will try the kernel in the next release...it is possible to select only 2 cores active from trickstermod? (More battery saving and tablet is still smooth) Also more stability tests would be appreciated expecially to test the stability while using the otg since undervolt can cause reboots when using otg (i think the device can handle -50mv without issues but with -75mv it reboot while using otg so should be stable with this undervolt)
Sent from my nexus 7 using XDA Free mobile app
been waiting for this!
This is amazing... AFAIK the first battery saving kernel since Clemsyn's two years ago, which wasn't updated at all anymore after a few weeks. Going travelling in a week and since I wanted to set up my Nexus with a new ROM anyway, this comes just in time.
F2FS support would indeed be great, so it could be used with e.g. the F2FS CarbonROM builds available here.
Just one question: I know that M-Kernel overclocks the companion core to 666MHz in order to ensure that the threshold after which the regular CPU cores take over is as high as possible... so even though it might seem we'd use more power, we'll actually save power since the real cores will be utilized less often due to this. Have you considered doing this in your kernel?
Keep up the good work!:good:
UPDATE: I just saw that you created a battery saving test kernel last year where the companion core was indeed clocked up to 666MHz: http://forum.xda-developers.com/showpost.php?p=46068826&postcount=1
Any reasons why you changed that to 480MHz?
Changelog
Logger Turned Off
Remove Performance, Conservative, Powersave And UserSpace
-Os Optimizations Instead (Less To Load Up, Smaller Boot.img)
Fix 4 Core all the time glitch
Overclock CPU LP to 700MHz
Changed Frequency Table Again....
Display Undervolted More 268>220, 190>150
FSYNC Disabled By Default
Fix Lag Wake Up Screen
Tune Hotplug For Less Heat And More Battery
1 Core On Idle
Tune Interactive For Battery
Fix 2048 VM Max
Make Use Of Lower Freq <300MHz
Disable More Debugging
Underclock Host1x From 267Mhz>255MHz
F2FS Support
Remove 51MHz Freq Step
Decrease Min Undervolt To 600mv
Remove KSM uses to much CPU
3.4 LMK
+25MV Cpu (More Stability)
Benchmarks Much Higher?
Decrease GPU Min From 137MHz>27MHz
Tune GPU Freq's
Lower Default Brightness 5>3
Decrease Host1x Min 155>85
What You Guys Think
Will Have A Flashable Zip Option
And I'm going to test this kernel extensively for the this release to make sure I can get the best battery possible and iron out any possible bugs
Going to flash this tomorrow morning will let you know how the performance is
---------- Post added at 10:09 PM ---------- Previous post was at 10:08 PM ----------
Have you looked at Franco's interactive tweaks in his kernel sources?
A flashable zip pls..
Plz flashable f2fs zip
Sent from my Nexus 7 using Tapatalk 2
New Kernel Likes Low Frequency's
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looking forward to a flash able zip of this.
Sent from my Nexus 7 using Tapatalk 2
+1 really want a flashable zip!
Flashed boot image on latest Purity 4.4.4. Lost SU binary. Any apps needing root stopped working. Reflashed Purity and all is well.
tcat007 said:
Flashed boot image on latest Purity 4.4.4. Lost SU binary. Any apps needing root stopped working. Reflashed Purity and all is well.
Click to expand...
Click to collapse
nothing on my end happening like this im on pure aosp with root,
i think its due to the stock ramdisk,
will check it out
extremetempz said:
Min Birghtness 5 Compared to 13 Stock
/QUOTE]
Can you make it 4
4 is awseome at night
When's there a f2fs version I will try it out
especially when im going on a long trip
Click to expand...
Click to collapse
Looking forward for f2fs support mate!
---------- Post added at 02:13 PM ---------- Previous post was at 02:05 PM ----------
extremetempz said:
New Kernel Likes Low Frequency's
Click to expand...
Click to collapse
Pure AOSP? Rastakat? or Team EOS ? And that widget is?
Flashable zip please, thanks
jonny68 said:
Flashable zip please, thanks
Click to expand...
Click to collapse
I can make one when the f2fs version comes out