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
Related
I have successfully overclocked the new Samsung Galaxy S II to 1.504GHz. This speed is enough to allow it to achieve really high benchmark scores like over 4000 points in Quadrant! 1.5GHz is a 25% overclock and makes this fast phone even faster and snappier in day to day usage.
Instructions:
1. You'll need the latest version of odin3 and the USB drivers for Windows. jutley's post on debranding the phone has links to both: http://forum.xda-developers.com/showthread.php?t=1064894
2. Grab the kernel. It is a tar file for odin with the overclocked kernel and a initramfs with proper modules for the kernel: http://setcpu.com/files/galaxysii_oc_v1.tar
3. Reboot the phone into download mode using ADB:
adb reboot download
4. Flash the kernel using odin3 by placing the tar file in the PDA section and pressing "Start."
5. The phone will reboot automatically.
6. Use SuperOneClick to root your phone if you haven't already. ADB should have root access with this kernel so it'll just work.
7. Grab SetCPU and try 1.504GHz.
Source code (with relevant commit for the overclock. I also enabled the interactive governor in the config): https://github.com/coolbho3k/galaxysii_oc
I haven't gone crazy on the voltages - 1.504GHz is stable at 1375mV on my device. Depending on your device, there may be even more headroom. I've gotten speeds of up to 2GHz to boot with instability (my unstable 1.8GHz Linpack run is currently in the Linpack top 10), but at very high voltages and temperatures. Leave it up to other developers to give you higher/more dangerous frequencies and voltages. If you stress the CPU a ton the phone will become hot to touch (though it does to a certain extent even at stock frequencies - there is not much thermal insulation between the processor and your hands in such a thin phone).
Current features in this kernel: Added 1.504GHz overclocking step (default frequency is still 1.2GHz for safety - use SetCPU to safely raise the frequency) and relevant modifications, 800MHz sleep death fix, interactive governor, ro.secure = 0.
The usual disclaimers apply here. Only do this if you know what you're doing. Though the long term stability/reliability of similar overclocks on other Android based ARM devices is known, this software is provided with no warranty, and I can't be held responsible if you fry your device.
Video:
A 1.504MHz overclock:
{
"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"
}
...breaks over 4000 points in Quadrant:
...and almost 60 MFLOPS in Linpack:
Since Linpack and Quadrant aren't (sufficiently?) multithreaded, you won't see that much improvement over single core Cortex A8 devices at the same clock. But these are dual core phones!
Developers: keep in mind that the Galaxy S II source currently "fixes" voltages on this revision of the Exynos to be 25mV less than what is in the table. Upon boot, the driver will actually print the real voltages at each level (look for ASV voltage_table in the kernel log) if you don't know which chipset revision a particular phone has. The overclock itself is controlled in the s5pv310_apll_pms_table.
Enjoy!
Damn .........
This is when I really wish I had a SGS2. Can't wait till it comes to American shores, great work coolbho, see you on Engadget tomorrow..
OMG already? I was wondering when this would happen. God bless you man.
Wonderful work man. Can't get Odin to download on my home rig so I'll be playing around w/ this tomorrow at the office With overclocking already here and the inevitable kernel optimizations to come, this phone is truly going to be the beast everyone suspects.
Thanks man!
..and what about undervolting?
WOW, nice work
Thanks!
Holy crap, nice work! How much hotter is it getting in the back of the phone at 1.5ghz?
Sent from my GT-I9100 using Tapatalk
Very good job here mate. It's about time somebody attempted to overclock such a sweet phone.
I will flash this with Odin tonight.
Again, great job & thanks
Not bad eh?
rovex said:
Not bad eh?
Click to expand...
Click to collapse
how you getting that score im getting just above 4000
Haha well played
coolbho3000 said:
Current features in this kernel: Added 1.504GHz overclocking step (default frequency is still 1.2GHz for safety - use SetCPU to safely raise the frequency) and relevant modifications, 800MHz sleep death fix, interactive governor, ro.secure = 0.
Click to expand...
Click to collapse
What is the 800MHz sleep death fix?
Can someone run this overclock against AnTutu Benchmark as well please ....i find this a little more stable than quadrant.
Ty
S
Sent from my GT-I9100 using XDA App
Very impressive indeed. The only question that comes to mind is if there really is a need to squeeze out higher frequencies. The CPU isn't really a bottleneck on the SGS2, is it?
MrDeacon said:
Very impressive indeed. The only question that comes to mind is if there really is a need to squeeze out higher frequencies. The CPU isn't really a bottleneck on the SGS2, is it?
Click to expand...
Click to collapse
CPU is always a bottleneck for calculations. Probably not a bottleneck in most apps though.
My install went smoothly. Quadrant showed 4144, 3892, and then 4100. Im going to try running it throughout today and see what happens. Cant wait for this to mature.
WOW.! Flashing right this second.! You people are geniouses.!
Sent from my GT-I9100 using Tapatalk
just wanted to add
oh crap.. i just realized who posted this, its Mr. Overclock himself, the creator of SetCPU... woo we have a star in our mits!
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!
Hey guys,
Ok the people who know about SetCpu and undevolting with it...
If I key in UV-values that go further than the slide-bar can take, i.e over -500mV,
does the undervolting actually go under the -500mV??
At the moment I've tried:
216mhz at -725mV [No hang when I run max and min cpu frequency at both 216Mhz]
456mhz at -650mV [No hang when I run max and min cpu frequency at both 456Mhz]
EDIT: I also ran the stress tests at said frequency settings and still no cpu hang or reboot.
I want to see if this goes further, but Im not sure if SetCpu is actually making the UV values go over -500mV.....
Cheers guys
current config: latest Blue Chronic rom, faux 2.1 kernel, carrier unlocked at&t atrix.
weaz_da_smel said:
Hey guys,
Ok the people who know about SetCpu and undevolting with it...
If I key in UV-values that go further than the slide-bar can take, i.e over -500mV,
does the undervolting actually go under the -500mV??
At the moment I've tried:
216mhz at -725mV [No hang when I run max and min cpu frequency at both 216Mhz]
456mhz at -650mV [No hang when I run max and min cpu frequency at both 456Mhz]
EDIT: I also ran the stress tests at said frequency settings and still no cpu hang or reboot.
I want to see if this goes further, but Im not sure if SetCpu is actually making the UV values go over -500mV.....
Cheers guys
current config: latest Blue Chronic rom, faux 2.1 kernel, carrier unlocked at&t atrix.
Click to expand...
Click to collapse
any jump more than 100mV between steps and it wont do the changes
The 100mV steps are the limiting factor if you use the higher frequencies which require relatively high voltage not to cause problems. What the OP might be curious about, and what I'm curious about is if I limit my phone to say 600MHz then I can set the voltage of all higher frequencies as low as I want because the phone will never use those frequencies, then I can try to find the true lower bound of the lower frequencies. The problem is I can set the lowest frequency to 0, keeping the 100mv steps, and the phone still runs fine (by limiting my phone to 216MHz), so there is some other rule in effect besides the 100mv between steps rule.
This is something that is limited by the chip itself but I guess that these rules would have to be written in the kernel, so I'm going to post over in the faux kernel thread.
Edit:
I don't have enough posts to post in the developer forum. Can someone copy the jist of my question over in the faux thread or somewhere else appropriate and with marginally high traffic? Thanks.
I have been thinking about undervolting as well and I was wondering if really does make that big of a difference like some people say? Do you really notice that it improves your batter life?
Atrix_Owner said:
I have been thinking about undervolting as well and I was wondering if really does make that big of a difference like some people say? Do you really notice that it improves your batter life?
Click to expand...
Click to collapse
The benefits of undervolting are lower power which leads to lower heat and longer battery life. I'm not sure if these power savings translate if the cpu is idle or in some type of sleep mode and the other problem is that all the other components are still using the same amount of power so the real savings might not be much if your phone is mostly idle.
But, my phone idles at 216Mhz and I have almost halved that voltage at that level so the best case scenario is that the cpu is using 1/4 the power it would normally.
I haven't done any testing but I do know there is some savings and we're all here cause we like to tweak things so you might as well undervolt cause it's pretty simple.
I would start with these levels:
1000 - 950mV
912 - 900
750 - 800
608 - 700
456 - 600
312 - 500
216 - 400
The only rule I know for undervolting is the 100mV between steps rule but I know there is some other rule at play as described in my previous post, but I don't know what it is. So really, I'm not sure if the voltages at the lower frequencies are actually being applied.
Hey thanks for the info. I don't know if I'm doing this correctly. After I undervolted, I clicked "set on boot" and rebooted my phone but I'm not sure if I did it right. For example, when you look at the "1000mhz", on the right it says "Max 1000mV" which is the default setting but shouldn't it be "925mV" because I subtracted -75mv? Look at this pic and tell me if it's like it should be.
{
"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"
}
Ya, that's right. That max voltage I think is a misnomer I think it should say default voltage really and that's just there for reference. So, when your cpu is operating at 1000Mhz it is operating at 925mV, with your current setting, it doesn't vary.
If you want to try to push for lower voltages you just want to uncheck set on boot so you avoid getting into a reboot cycle. YMMV on what kind of undervolt will be stable. I gave you my numbers because I think my phone is not as stable as others since it can't handle the 1.45Ghz overclocking kernel.
My phone isn't overclocked btw and I'm using Faux123's enhanced stock kernel 1.0ghz. I will try to push the volts even lower and see how that goes. One thing that I can say for sure is that when I play GTAIII, my phone doesn't overheat as much as it used to so this defiantly fixed the overheating issue that I was having with almost any game.
my setcpu doesnt have voltages tab.. y?
borjok536 said:
my setcpu doesnt have voltages tab.. y?
Click to expand...
Click to collapse
B/c you're not using a custom kernel.
Sent from my CM7 Atrix 4G
mebster123 said:
The 100mV steps are the limiting factor if you use the higher frequencies which require relatively high voltage not to cause problems. What the OP might be curious about, and what I'm curious about is if I limit my phone to say 600MHz then I can set the voltage of all higher frequencies as low as I want because the phone will never use those frequencies, then I can try to find the true lower bound of the lower frequencies. The problem is I can set the lowest frequency to 0, keeping the 100mv steps, and the phone still runs fine (by limiting my phone to 216MHz), so there is some other rule in effect besides the 100mv between steps rule.
This is something that is limited by the chip itself but I guess that these rules would have to be written in the kernel, so I'm going to post over in the faux kernel thread.
Edit:
I don't have enough posts to post in the developer forum. Can someone copy the jist of my question over in the faux thread or somewhere else appropriate and with marginally high traffic? Thanks.
Click to expand...
Click to collapse
What I gathered from my own experience, experimenting and looking at code is the following:
The 100 mv limit between steps seems to be more of a nvidia guideline for best chip performance. It is not an actual limit in the software, no matter the values you input, they will be applied.
What is indeed limited (and so in the code) is the lowest possible undervolt. In faux's it is 750 mv and clemsyn's (was, not sure if still is) 650 mv.
If you push any voltage past that limit, it won't be applied. Try it for yourself.
This is my first kernel build ever (not just for the Nexus 7). Just a starting point for more hacking on the Nexus 7.
Flashable zip package attached.
It should go without saying that anything you do with this package you do at your own risk.
Features
Insecure
init.d support
Overclocked to 1.5GHz
Voltage tweaks at OC clocks
BFQ scheduler
smartassv2 governor
lagfree governor
Made kernel version not suck
Notes
You should root and install busybox into /system/xbin before flashing this kernel. Don't flash this if you don't know what you're doing as I'm too lazy to include n00b instructions.
Credits
Thanks to Virtuous team for their updater-script for this device.
Source
https://github.com/zaventh/nexus7-kernel-grouper
Blog post
http://www.jeffmixon.com/custom-nexus-7-kernel-atlantis-r2-released/
Screens
{
"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"
}
Cheers...
That CPU score is sexy!
Great work! Now I definitely can't wait for my nexus to ship.
Edit: If you could try adding smartassv2. This is a popular governor that I would really enjoy on the nexus 7.
Sent from my Transformer using Tapatalk 2
this is compatible with the stock rom right? ik it has to be rooted btw
Caliyork said:
That CPU score is sexy!
Click to expand...
Click to collapse
Yes it is...
MC153 said:
Great work! Now I definitely can't wait for my nexus to ship.
Edit: If you could try adding smartassv2. This is a popular governor that I would really enjoy on the nexus 7.
Sent from my Transformer using Tapatalk 2
Click to expand...
Click to collapse
Sure. I'll be adding several custom governors to choose from.
jarjar124 said:
this is compatible with the stock rom right? ik it has to be rooted btw
Click to expand...
Click to collapse
Yes, it's compiled from stock kernel sources.
Thanks so much man. Can't wait to get my nexus so I can flash this. Hopefully before the 18th which is my birthday. I had heard though that smartass didn't work so well with more than 1 core though. Could you clarify on that.
Sent from my Rezound
evilstewie23 said:
Thanks so much man. Can't wait to get my nexus so I can flash this. Hopefully before the 18th which is my birthday. I had heard though that smartass didn't work so well with more than 1 core though. Could you clarify on that.
Sent from my Rezound
Click to expand...
Click to collapse
Smartass v1 was made for single core cpu's. Smartass v2 was made for dual core cpu's, so v2 might work better on a quad core? V2 doesn't really work all that well on my single core cpu for the phone I have.
zaventh said:
Yes it is...
Sure. I'll be adding several custom governors to choose from.
Yes, it's compiled from stock kernel sources.
Click to expand...
Click to collapse
Nice work! Can't wait to see the future of this kernel.
Sent from my Transformer using Tapatalk 2
sparksco said:
Smartass v1 was made for single core cpu's. Smartass v2 was made for dual core cpu's, so v2 might work better on a quad core? V2 doesn't really work all that well on my single core cpu for the phone I have.
Click to expand...
Click to collapse
Exactly right. I actually never really liked smartassv2 in general, but I think it is working out fairly well on the N7, actually.
This is after just a little bit of game time, some regular usage, and some sleep time. I may need to tweak some of the higher clock values so it scales up a bit more gracefully. At any rate, there will be plenty of options to play around with.
zaventh said:
Exactly right. I actually never really liked smartassv2 in general, but I think it is working out fairly well on the N7, actually.
This is after just a little bit of game time, some regular usage, and some sleep time. I may need to tweak some of the higher clock values so it scales up a bit more gracefully. At any rate, there will be plenty of options to play around with.
Click to expand...
Click to collapse
So whats the heat production and stability like at 1.5ghz? When you say 1.5ghz, is that like the htc one x where it is actually 1.4ghz but you can go to 1.5ghz when only using one core, or is it all four cores clocked at 1.5 please? Got to admit that a gpu OC would be really nice. This looks great, thanks
any chance of getting some gpu over clocks in then kernal, screw battery life give me mmmhhhzzz!
Is it possible to get scary gov on this? I think it's based on smartassv1 but not really sure. It gives me a good balance between performace and battery. Or perhaps we could make a scaryV2 lol?
Great work for a first Kernel
Is the extra battery drain worth that .2ghz of extra horsepower? Because i've heard it's a perfectly capable device @ 1.3ghz.
lhayati said:
Great work for a first Kernel
Is the extra battery drain worth that .2ghz of extra horsepower? Because i've heard it's a perfectly capable device @ 1.3ghz.
Click to expand...
Click to collapse
Thanks. Naturally, it's a matter of personal preference of course if it is "worth" it to OC any processor. OC'ing the N7 was more of a "because I can" thing than for any practical reason. The CPU is impressive as is.
The N7 is probably the fastest and most responsive mobile device I've ever seen even at stock, mostly thanks to the hardware but also due to Jelly Bean's ability to leverage this kind of raw power.
The actual battery drain between 1.3GHz -> 1.5GHz will all depend on how much time you spend at those higher clock speeds, of course.
zaventh said:
Thanks. Naturally, it's a matter of personal preference of course if it is "worth" it to OC any processor. OC'ing the N7 was more of a "because I can" thing than for any practical reason. The CPU is impressive as is.
The N7 is probably the fastest and most responsive mobile device I've ever seen even at stock, mostly thanks to the hardware but also due to Jelly Bean's ability to leverage this kind of raw power.
The actual battery drain between 1.3GHz -> 1.5GHz will all depend on how much time you spend at those higher clock speeds, of course.
Click to expand...
Click to collapse
Thank you for this kernel. I cant wait for my nexus 7
Sent From A Rotary Phone
Do we know at what speed the ram is clocked?
The transformer infinity uses DDR3 at 1600. The 300t is much lower though
Sent from my GT-I9100 using xda app-developers app
emergant said:
Do we know at what speed the ram is clocked?
The transformer infinity uses DDR3 at 1600. The 300t is much lower though
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
It's been confimred in the Q&A section that the N7 has DDR3 ram :beer:
Thanks. But DDR3-667 as in tf300 or DDR-1600 as in Tf700 or something else
I thought about putting this in QA but thought the dev might know. Sorry if that was a bad call
Sent from my GT-I9100 using xda app-developers app
Whops I meant general not Q&A
Hynix HTC2G83CFR DDR3 RAM
Hope that helps
http://forum.xda-developers.com/showthread.php?t=1748933
Smartass V2 doesn't support scaling upto 4 cores
Its useless for this device!
Share your benchmark scores with xda - Antutu / GFXBench / Vellamo Metal / Basemark OS II
Stock Rom or not will be greatly appreciated. See attached vs. other current Verizon Android Phones.
{
"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 was stock ROM, reflashed via TOT about a month after I had the phone. Rooted, all LG/Verizon disableable stuff disabled in App Manager (before rooting).
Ok so I just got done setting up Vanir AOSP 4.4.4 ROM with all my apps. I haven't customized anything other than various appearance settings - I didn't mess with SetCPU, schedulers, DPI, etc. This was just me installing all my apps and setting up the notifications etc. the way I like them. This is my first run at an AOSP ROM on the G3. Here are the results.
(NOTE: I downloaded and ran all the same benchmarks as in the list above, with a reboot between each benchmark run. I have annotated the order in which I ran the benchmarks after their respective titles.)
Antutu (first):
Vellamo Metal (fourth):
Basemark OS II (second):
GFX Bench (third):
(NOTE: The phone was scorching hot at the end of this run; throttling might explain the lower scores?)
My phone with bloat turned off and running with the interactive governor and a hack to make throttling less aggressive.
Sent from my VS985 4G using Tapatalk
tech_head said:
My phone with bloat turned off and running with the interactive governor and a hack to make throttling less aggressive.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
Dawn what is this hack you speak of?
Modifying thermal-engine-8974.conf to prevent throttling in an aggressive manner. There is a thread somewhere about it. I hacked it up self based on what I want my phone to do. As you can see from my previous post Antutu performance is right up there with the other flagships. The big reason why it still lags behind the S5 is 3d performance. Anyway I'm happy now that it doesn't throttle and I still get a days use.
Sent from my VS985 4G using Tapatalk
tech_head said:
Modifying thermal-engine-8974.conf to prevent throttling in an aggressive manner. There is a thread somewhere about it. I hacked it up self based on what I want my phone to do. As you can see from my previous post Antutu performance is right up there with the other flagships. The big reason why it still lags behind the S5 is 3d performance. Anyway I'm happy now that it doesn't throttle and I still get a days use.
Sent from my VS985 4G using Tapatalk
Click to expand...
Click to collapse
How'd you change governors if you are on the stock kernel?
Nothing in the stock kernel prevents it. I use ROM Toolbox (pro version) and you can tweak a bunch of performance parameters. LG doesn't lock the kernel down except for maximum clock speed. So you can't over clock but you can run a max 100% of the time. You will eventually hit thermal throttle, but you can do it.
Sent from my VS985 4G using Tapatalk
Here's my score with beans Rom and running skydragons kernel and no other tweaks to the kernel
sent from my stumped and bumped g3
Mine
pitbull8265 said:
View attachment 3054061
View attachment 3054062
Click to expand...
Click to collapse
Thank you, what is your current Rom / setup for these scores.
sent from my xda enhanced Android Device
[/ATTACH]
legend221 said:
Thank you, what is your current Rom / setup for these scores.
sent from my xda enhanced Android Device
Click to expand...
Click to collapse
View attachment 3054085
I did a lot of work tweaking the kernel, i/o scheduler and throttling response
Here is one using the latest Vanir Commotio Lollipop
pitbull8265 said:
[/ATTACH]
View attachment 3054085
I did a lot of work tweaking the kernel, i/o scheduler and throttling response
Click to expand...
Click to collapse
Do you mind posting details about how you have things setup?
jal3223 said:
Do you mind posting details about how you have things setup?
Click to expand...
Click to collapse
WOuld, but I am on a different setup now...
I set the governor to Interactive, read ahead buffer to 4096, cfq scheduler, Vegas Tcp Conjestion Control, max frequency 2457 minimum 300
I fine tuned the governor as well, but cant remember the settings, sorry
I am on Jasmine 4.0 running the latest Skydragon kernel. The trickster mod setup is the second pic- TCP setting is clipped off the top, its Westwood.
Broke 42k today with CM12 12/12.
In case anyone is wondering, using trickster mod the best governor is performance, not interactive, when it come to benchmarks specifically. Interactive is better for general use but performance will just always give you the optimal performance (get it) in a benchmark.
i did a benchmark with stock lil debloat and skydragon kernel , im no tech so i dont know much about these readings . im planing of switching to liquidsmooth rom
cap1tal1sm said:
Broke 42k today with CM12 12/12.
In case anyone is wondering, using trickster mod the best governor is performance, not interactive, when it come to benchmarks specifically. Interactive is better for general use but performance will just always give you the optimal performance (get it) in a benchmark.
Click to expand...
Click to collapse
Cool.. Screenshots for reference???
pitbull8265 said:
Cool.. Screenshots for reference???
Click to expand...
Click to collapse
You're just gonna have to trust me that I hit 42k xD didn't screenshot it.
I actually hit 40k with stock ROM by turning on performance governor, so it definitely helps with benchmarking.