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
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!
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.
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
i have a jelly bean rom on my phone and for a while it worked fine with a custom kernel. then it started to freeze as soon as i hit the lock button. so it wouldnt turn back on. it always does it now. but when i take off the kernel it works fine with the stock jb rom kernel. ive tried slim bean, cm10, helly bean and they all freeze with a custom kernel. they use the devil or sephamore kernel. both give me the same problem and i dont know what is causing it when the kernels were meant to work on these roms. some help would be much appreciated
Are you overclocking or anything? Undervolting? Live OC? Maybe your phone can't handle it.
theexel said:
Are you overclocking or anything? Undervolting? Live OC? Maybe your phone can't handle it.
Click to expand...
Click to collapse
its overclocked to 1.3 ghz with this kernel but it should be able to handle it. i used to run it at 1.6 on gingerbread and ics roms. the devil kernel ran fine with with live overclock on ics. im using sephamore on jb with live overclock of 105% and its undervolted. i dont know if this is the problem though as i used to run at higher clock speeds with undervolting and live overclock.
Try flashing the kernel, but don't overclock or undervolt.
See if it reboots/hangs.
Then try just overclocking.
Then try just undervolting.
Etc.
Just so we can narrow down the problem.
Also, is deep idle enabled?
Edit: May I ask why you overclock so high?
If it's for performance, you're much better Live OC'ing like 10% and leaving the min at 200 + the Live OC.
Heck, maybe even 20%, it'll be super snappy.
Unless you play games, then I understand.
My settings:
{
"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"
}
theexel said:
Try flashing the kernel, but don't overclock or undervolt.
See if it reboots/hangs.
Then try just overclocking.
Then try just undervolting.
Etc.
Just so we can narrow down the problem.
Also, is deep idle enabled?
Edit: May I ask why you overclock so high?
If it's for performance, you're much better Live OC'ing like 10% and leaving the min at 200 + the Live OC.
Click to expand...
Click to collapse
Yeah ill try that out and i disabled deep idle i think it still does it. if i awaken my phone periodically it wont reboot.
and i used to just because i could i usually kept the max at around 1.5 ghz. i would just use 1.6 maybe for some heavier games. but now the processor is only at 1.3 ghz and 1.46 with the devil kernel as i dont play much games anymore.
i keep my min at 200.
and when i flash the kernel do you want me to leave it alone not change the governor or scheduler? or anything of that sort?
actually i have live oc to 130% i was thinking of the devil kernel i tried earlier sorry.
How are you disabling Deep Idle?
With the Kernel app or NSTools, or?
Do it with the kernel app.
Let me try some higher settings real quick just to get an idea.
Yeah, leave it how it comes.
Ondemand is fine if you want battery life and for the ROM to be snappy.
Noop is fine, too.
Smartmassv2 seems laggy on this kernel.
theexel said:
How are you disabling Deep Idle?
With the Kernel app or NSTools, or?
Do it with the kernel app.
Let me try some higher settings real quick just to get an idea.
Yeah, leave it how it comes.
Ondemand is fine if you want battery life and for the ROM to be snappy.
Noop is fine, too.
Smartmassv2 seems laggy on this kernel.
Click to expand...
Click to collapse
i used nstools and also i have smooth profiles on and the overclock is running at 1.3 ghz yours is around 1 ish? did you set it in the kernel app to set the clock speed? my smartassV2 seema to be faster with me. I am running sio scheduler with SmartassV2.
i am going to start playing with the settings now.
may i ask what rom and kernel you had working?
Whatever Flo
What is it: Stock android kernel, JSS15J, absolutely no changes besides the overclock. No fancy features, no snake oil, no bloat, clean stock experience.
Overclock not customisable, baked right into the kernel and loaded on boot, no CPU/GPU management apps needed.
I take no responsibility or imply any warranty for the use of this kernel, use of this kernel is completely at your own risk.
If a build doesn't work for you try the lower clocked version, still not then you're out of luck and your CPU can't handle the overclock sorry. If there is enough demand I can build a lower clocked edition but I don't really see the need. Any problems or questions I will try to answer for you.
Proof is in the Source
Flash zips with TWRP/recovery of your choice
1890MHz Build + GPU OC: http://d-h.st/y0W
Vellamo metal score: ~830
GFXBench:
T-Rex 18fps
1009 Frames
Egypt 46fps
5068* Frames
1890MHz Build No GPU OC: http://d-h.st/9yr
Vellamo metal score: ~830
GFXBench:
T-Rex 16fps
889 Frames
Egypt 41fps
4653* Frames
1728MHz Build + GPU OC: http://d-h.st/95k
Vellamo metal score: ~800
1728MHz Build No GPU OC: http://d-h.st/hmZ
Vellamo metal score: ~800
* Sections of demo limited by VSync
If you like, give me a thumbs up!
Thanks and enjoy your nexus.
Change Log
Code:
Aug 4 2013:
- Added GPU OC option
Aug 3 2013:
- Added CPU Overclock builds
Very nice. Do you intend to add GPU OC as well? I think with this kernal with GPU OC it would play nicer with Clean ROM than the current Kernels. Just my opinion but Jassy kernel doesn't seem to like CR as much as Cm 10.2 so I would really like to see what stock with extra OC's does for that very nice Rom .
conan1600 said:
Very nice. Do you intend to add GPU OC as well? I think with this kernal with GPU OC it would play nicer with Clean ROM than the current Kernels. Just my opinion but Jassy kernel doesn't seem to like CR as much as Cm 10.2 so I would really like to see what stock with extra OC's does for that very nice Rom .
Click to expand...
Click to collapse
Yes I am planing on it, doing some stability and performance tests right now. Will release it when I finish that.
WhiteDawn said:
Yes I am planing on it, doing some stability and performance tests right now. Will release it when I finish that.
Click to expand...
Click to collapse
You are awesome. This is what I've always wanted in a kernel.
CPU, GPU OC and voltage control.
Thanks!
New builds up, now include GPU overclock.
Great kernel, no issues on stock ROM whatsoever. Seems like GPU scores went down a tad though, with no oc and oc versions of the 1.7ghz, looks like it went down 1k pts on 3d score in antutu.
Maybe add a little higher oc on the GPU to test out with the 1.7ghz version?
Could you confirm with me, I have the 1.7+GPU oc version and my 3d graphics score seems to be lower, I was around 7k for stock clocks.
{
"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"
}
Thanks!
Sent from my Nexus 7 using Tapatalk 4
Philaphlous said:
Great kernel, no issues on stock ROM whatsoever. Seems like GPU scores went down a tad though, with no oc and oc versions of the 1.7ghz, looks like it went down 1k pts on 3d score in antutu.
Maybe add a little higher oc on the GPU to test out with the 1.7ghz version?
Could you confirm with me, I have the 1.7+GPU oc version and my 3d graphics score seems to be lower, I was around 7k for stock clocks.
Thanks!
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thanks for the heads up, I haven't tried using antutu for my benchmarking and I ran most of my testing on the 1.8 build since I just assumed dropping the clocks down wouldn't make much of a difference. I'll look into it.
Any Chance of a JSS15Q Version?
Felnarion said:
You are awesome. This is what I've always wanted in a kernel.
CPU, GPU OC and voltage control.
Thanks!
Click to expand...
Click to collapse
Yeah that would be peachy if JSS15Q based. I was on jassy's earlier (with JSS15J) and the GPU boost was noticeable, but back on stock to fix the multitouch.
hey .
i tested the 1,7ghz+450mhz gpu kernel and its running fine .
But it would be so cool if u could make one more kernel with just GPU overclock because i think the CPU power of the n7 is fine with 1.5ghz .
but the 50mhz more in GPU frequency will be more noticable .
i hope its not to much work for you... otherwise i will be fine with running the 1,7ghz edition.
thanks
I really liked this kernel, but when I flashed it after the latest cm 10-18 nightly, it caused a corrupt display upon booting. Fortunately I had made a nandroid backup a few weeks earlier so I was able to get it working again after restoring the system partition. I'm afraid to try flashing this again..