Database Info

[Kernel] [GPL] Sense 2.6.32.21 OC/UV 1.51GHZ (CFS-Smartass-TUN)

This kernel is created specifically for sense roms It will more then likely not work in it current state on any AOSP based rom
Features
Overclocked to 1.51ghz and stable as ever (for most)
added in smartass and interactive cpu freq govs
added in TUN support
compiled v4l2 as modules
many more....
for a full list of changes check the commit log here
Quirks
Smartass wont scaled below 768mhz atm im looking into it stick with interactive for the best overall experience for now.
Source
Downloads:
Build 4​

Awesome! I'll give my feedback as to how it is working.
I did notice once a governor is selected you have to reset your Mhz or it will stay on 806 max. Also this kernel doesnt want to work with OC widget at all but works fine with SetCPU. I've always liked OC widget a little more as it uses less battery than SetCPU.
Great work so far BC your the man. Been running this bad boy and havn't had a single reboot @ 1.5ghz. Though my battery is going quick for some reason, dont know why

This'll work on the stock Sense?
^ Shift Faced

jesusice said:
This'll work on the stock Sense?
^ Shift Faced
Click to expand...
Click to collapse
yes it shall took me a bit but i found out the issue

i'm going to assume this works for stock rooted roms?

d1msum4lyfe said:
i'm going to assume this works for stock rooted roms?
Click to expand...
Click to collapse
Looks like it should, yes

Thank you very much for this. I can confirm that this is running well on stock.

cloverdale said:
Thank you very much for this. I can confirm that this is running well on stock.
Click to expand...
Click to collapse
^ Ditto
Now, coming from the Moment I've never used an OC kernel... anything I should know? Any tips?
^ Shift Faced

jesusice said:
^ Ditto
Now, coming from the Moment I've never used an OC kernel... anything I should know? Any tips?
^ Shift Faced
Click to expand...
Click to collapse
If you get random reboots, it means it's OCed a bit too high; just scale it back a bit and you'll be fine if that ever happens

Is this running at 1.5 all the time or does it throttle between ranges?
What is the default range?
Does the user have to do anything to enable or set the throttling?

zeropants said:
Is this running at 1.5 all the time or does it throttle between ranges?
What is the default range?
Does the user have to do anything to enable or set the throttling?
Click to expand...
Click to collapse
As noted above, I'm new to OC'ing but I'm pretty sure you have to set it to the ranges you want via something like SetCPU or OS Monitor. I believe default is gonna stop at 800mhz unless you scale it up.
EDIT: And thanks Impaler for the help!
^ Shift Faced

zeropants said:
Is this running at 1.5 all the time or does it throttle between ranges?
What is the default range?
Does the user have to do anything to enable or set the throttling?
Click to expand...
Click to collapse
Use SetCPU and select the Mhz/governor you want to use. Each Governor "Throttles differently"

jesusice said:
As noted above, I'm new to OC'ing but I'm pretty sure you have to set it to the ranges you want via something like SetCPU or OS Monitor. I believe default is gonna stop at 800mhz unless you scale it up.
EDIT: And thanks Impaler for the help!
^ Shift Faced
Click to expand...
Click to collapse
No problem, I'm here if you need anything else

What are some good range options?

I'm using 800 min 1.5ghz max interactive. Profiles I have setup: charging 1.5ghz performance, screen off 800 max 245 min
Bumped it up 1.1ghz min 1.5ghz max interactive, going to see how much that affects my battery life
Sent from my PG06100

Dread 7us said:
I'm using 800 min 1.5ghz max interactive. Profiles I have setup: charging 1.5ghz performance, screen off 800 max 245 min
Bumped it up 1.1ghz min 1.5ghz max interactive, going to see how much that affects my battery life
Sent from my PG06100
Click to expand...
Click to collapse
I have mine set to 768 min and 1.4GHz max interactive
Charging is 1.4 performance
screen off 245 min and 800 max interactive.
I don't want to push up around 1.5 until I'm sure this is more stable on my phone.

Dread 7us said:
I'm using 800 min 1.5ghz max interactive. Profiles I have setup: charging 1.5ghz performance, screen off 800 max 245 min
Bumped it up 1.1ghz min 1.5ghz max interactive, going to see how much that affects my battery life
Sent from my PG06100
Click to expand...
Click to collapse
there no real need to have it running at such high freqs all the time mine is set at 245 min 1.31 max usually n got no lag what so ever
the higher speeds are more for gaming and cpu intensive applications

todAY HAS been a good day for HTC EVO SHIFT 4g android development. downloading kernal now! thanks for the hard work

BC you need to set your Donation link up like Impaler. I dont have paypal and it says you have to log in. Impaler's lets you pay with just a credit card. I will send a donation if I can do it without a paypal account.

fifedogg said:
BC you need to set your Donation link up like Impaler. I dont have paypal and it says you have to log in. Impaler's lets you pay with just a credit card. I will send a donation if I can do it without a paypal account.
Click to expand...
Click to collapse
Hey, you clicked my donate link? Thanks!

[Q] Setcpu crashing at 1.9Ghz?

I try and set my sensation to 1.9 (1.89)ghz on setcpu. Right after i set it up, the phone reboots and the setting is lost. I tried different apps but nothing changes. i have a custom setcpu setting and still nothing happens. It only works when i overclock to something under 1.9. Anyone else having the same problem? Disable perflock isn't working for me. If thats the solution, how to fix it?
Running SENSEaY - XE35 v2.1.0 with Bricked 1.5 kernel.

pranker98 said:
I try and set my sensation to 1.9 (1.89)ghz on setcpu. Right after i set it up, the phone reboots and the setting is lost. I tried different apps but nothing changes. i have a custom setcpu setting and still nothing happens. It only works when i overclock to something under 1.9. Anyone else having the same problem? Disable perflock isn't working for me. If thats the solution, how to fix it?
Running SENSEaY - XE35 v2.1.0 with Bricked 1.5 kernel.
Click to expand...
Click to collapse
Sounds like you weren't aware that 1.7GHz and higher aren't considered stable freqs, 1.9GHz has a high Voltage which may cause the kernel to panic and issue a reboot. Just stick with a lower freq around the 1.2 stock speed.

pranker98 said:
I try and set my sensation to 1.9 (1.89)ghz on setcpu. Right after i set it up, the phone reboots and the setting is lost. I tried different apps but nothing changes. i have a custom setcpu setting and still nothing happens. It only works when i overclock to something under 1.9. Anyone else having the same problem? Disable perflock isn't working for me. If thats the solution, how to fix it?
Running SENSEaY - XE35 v2.1.0 with Bricked 1.5 kernel.
Click to expand...
Click to collapse
Any CPU aren't the same. It seem that your CPU can't handle that much clock speed. Speed on 1.9 and 1.782 Ghz are quite the same. (Quadrant might shows couple hundreds higher but not effect any everyday uses.)

Ace42 said:
Sounds like you weren't aware that 1.7GHz and higher aren't considered stable freqs, 1.9GHz has a high Voltage which may cause the kernel to panic and issue a reboot. Just stick with a lower freq around the 1.2 stock speed.
Click to expand...
Click to collapse
Thanks for the heads up. Where'd you hear that? i dont remember reading about it. Is there a way to make 1.9ghz work?

What benefits will 1.9GHz provide other than wearing down your battery faster?

pranker98 said:
Thanks for the heads up. Where'd you hear that? i dont remember reading about it. Is there a way to make 1.9ghz work?
Click to expand...
Click to collapse
Just looking at that voltage table and my experiences with that freq from past phones tells me so . Jumping from the low level to such a high one should cause a freeze on any device.
@LooieEng 1.9GHz may help this phone run future Android revisions smoothly, and perhaps Win8 will function on the phone too.

[Q] What Should I adjust Undervolt settings to on SetCPU that are stable

I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.

DirtyPISTOLA said:
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
Click to expand...
Click to collapse
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!

fcisco13 said:
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Alright thanks will try
Sent from my LG-P999 using Tapatalk

I've seen some general advice not to UV for anything over 1ghz speeds as well, but it may not hurt to try if you want and adjust as needed for stability.

I'm running on a -75mv at 1.5Ghz faux kernel 0.4.7..
Perfectly stable, benchmarked AnTuTu, Quadrant, and all those other good stuff.
I have not tried -100mv yet, I doubt it will be stable.

Every phone is different, but I run mine at -20 up to 1 G, and -10 for the rest.

Mine I cant undervolt shoot I have to keep my minimum frequency at 500 to be stable, course I can also run at 1.5 all day (I keep it at 1.2).
Well I guess I can't say I cant UV since I use pimp my cpu and it only gives you options in 25 increments, maybe I would be stable at like -10. But coming from my galaxy s 4g where I could UV over -150 and still be stable, that just doesnt even sound worth doing.
Edit: I just thought about it and maybe the reason I cant UV (more) is because I'm using fauxs pre UV/OC kernel, so I dont even know what stock voltage is. But comparing to my sgs4g at stock voltage I am running considerably lower voltages on the g2x.

The faux thread says it's pre uv at -50 across the board.

Beekersguy said:
The faux thread says it's pre uv at -50 across the board.
Click to expand...
Click to collapse
I been running it so long and flashed so many friends phones I can't even remember details anymore!
Sent from my LG-P999 using xda premium

why is morfic's trinity kernel the only one with gpu oc?

Any particular reason?

You can adjust it with LiveOC in nearly every other kernel.

Harbb said:
You can adjust it with LiveOC in nearly every other kernel.
Click to expand...
Click to collapse
ok, didn't know that liveoc also overclocked gpu...btw im at 110% and the phone reboots when playing, already tried to pump voltages +25 and it still reboots...should i raise them even higher?

Try a little higher. What kernel are you on now? If it still doesnt work after a fair bit of trial and error (with INT and ARM voltages), maybe it's just not meant to be.

LiveOC boost bus speed which will influence both memory clock and gpu clock?
Sent from my Nexus S using XDA

Harbb said:
Try a little higher. What kernel are you on now? If it still doesnt work after a fair bit of trial and error (with INT and ARM voltages), maybe it's just not meant to be.
Click to expand...
Click to collapse
im on oxygen rom and using franco's kernel...cant seem to get liveoc working, but what is strange is that a while back i remember using liveoc at 110% and stock voltages and it worked with no reboots

[Q] Processes Crash Like Doom...

It happens once each 3~5 day, and a nandroid backup then restore immediately solves the problem. but after a few days they go crashing again....
anybody any idea how this happens?
both CyberGR & AOKPCB have this problem on my phone, clean installed of course, but it never happens to my fella's phones (all Nexus S) running the same ROM, same kernel...
Totally confused.

cdljl2005 said:
It happens once each 3~5 day, and a nandroid backup then restore immediately solves the problem. but after a few days they go crashing again....
anybody any idea how this happens?
both CyberGR & AOKPCB have this problem on my phone, clean installed of course, but it never happens to my fella's phones (all Nexus S) running the same ROM, same kernel...
Totally confused.
Click to expand...
Click to collapse
Matr1x is undervolted. Run the kernel that comes with CyberGR or AOKPCB instead of flashing it.
It's fine that your friend Nexus S runs it, but you're not like your friend, are you? Well your Nexus S isn't like your friend Nexus S either.

cdljl2005 said:
It happens once each 3~5 day, and a nandroid backup then restore immediately solves the problem. but after a few days they go crashing again....
anybody any idea how this happens?
both CyberGR & AOKPCB have this problem on my phone, clean installed of course, but it never happens to my fella's phones (all Nexus S) running the same ROM, same kernel...
Totally confused.
Click to expand...
Click to collapse
Same thing happens to me, had to gave up Matr1x kernel because of that, despite i enjoyed it so much.

Hmm.. try v21.0 or raise voltages
Sent from my Nexus S using XDA

mathkid95 said:
Yeah that's not a kernel issue. Sorry to ruin your day
If you want, though, try v21.0 or raise voltages
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
I had voltages raised +30 across the board. It wasn't a issue with booting or nothing like that, just out of the blue all apps would crash for no reason. Rebooting wouldn't fix it, fix permissions wouldn't fix it, only way to fix it was to reflash and kernel. And it only happened with your kernel in 5 or 6 builds of AOKP, any other kernel would not give that issue, but i enjoyed Matr1x the most.
I will try v21 and if the issue happens again i'll try to capture a logcat and forward it to you.

No I understand you're not bashing my work... forgive my rudeness
Yes, try to flash v21.0 and then if that doesn't work I will look into it
Sent from my Nexus S using XDA

polobunny said:
Matr1x is undervolted. Run the kernel that comes with CyberGR or AOKPCB instead of flashing it.
It's fine that your friend Nexus S runs it, but you're not like your friend, are you? Well your Nexus S isn't like your friend Nexus S either.
Click to expand...
Click to collapse
Thanks for replying. I raised voltage long ago, the problem happens... and now I left the voltage alone as its default, the problem still happens...
as for anything different using the kernel is that I'm using BLX, setting charging limit to 80%. dunno if that would lead to the problem.
DeuXGod said:
I had voltages raised +30 across the board. It wasn't a issue with booting or nothing like that, just out of the blue all apps would crash for no reason. Rebooting wouldn't fix it, fix permissions wouldn't fix it, only way to fix it was to reflash and kernel. And it only happened with your kernel in 5 or 6 builds of AOKP, any other kernel would not give that issue, but i enjoyed Matr1x the most.
I will try v21 and if the issue happens again i'll try to capture a logcat and forward it to you.
Click to expand...
Click to collapse
Yeah my problems are exactly the same! Moreover, I noticed that the crashing processes are more or less system, or requesting root, typically android.process.acore (that's Contacts I suppose?), Google maps, and third party apps like System Tuner, Rom Manager, etc.
As for whether it is a problem with the kernel, I'm not quite sure - I had changed ROM and kernel at the same time before undergoing the problem. And it's really strange of the stability in the first few days - if it is a undervolt problem, it should be happening from the beginning, shouldn't it? Or the problem may not be caused DIRECTLY by undervolt.
but I don't reflash to solve it... nandroid backup and restore will do.
and thanks for your reply DeuXGod! I thought it was only me who get this problem.
mathkid95 said:
Hmm.. try v21.0 or raise voltages
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Will definitely try 21.0! Raising voltage doesn't seem to help, as one month ago I was using the kernel with raised voltage... the problem happened all the same.
If there's anything different in using the phone to my fellas using theirs, it's that I use BLX limiting charging up to 80%... don't know if it can cause the problem.
Anyway, I'll flash 21.0 first; if it doesn't help, I personally think one restore in each 3~5 days is also acceptable. Thanks mathkid! I'll be on matr1x.
p.s. more details about the problem are in the reply above... just FYI, hope it can help.

cdljl2005 said:
Thanks for replying. I raised voltage long ago, the problem happens... and now I left the voltage alone as its default, the problem still happens...
as for anything different using the kernel is that I'm using BLX, setting charging limit to 80%. dunno if that would lead to the problem.
Yeah my problems are exactly the same! Moreover, I noticed that the crashing processes are more or less system, or requesting root, typically android.process.acore (that's Contacts I suppose?), Google maps, and third party apps like System Tuner, Rom Manager, etc.
As for whether it is a problem with the kernel, I'm not quite sure - I had changed ROM and kernel at the same time before undergoing the problem. And it's really strange of the stability in the first few days - if it is a undervolt problem, it should be happening from the beginning, shouldn't it? Or the problem may not be caused DIRECTLY by undervolt.
but I don't reflash to solve it... nandroid backup and restore will do.
and thanks for your reply DeuXGod! I thought it was only me who get this problem.
Will definitely try 21.0! Raising voltage doesn't seem to help, as one month ago I was using the kernel with raised voltage... the problem happened all the same.
If there's anything different in using the phone to my fellas using theirs, it's that I use BLX limiting charging up to 80%... don't know if it can cause the problem.
Anyway, I'll flash 21.0 first; if it doesn't help, I personally think one restore in each 3~5 days is also acceptable. Thanks mathkid! I'll be on matr1x.
p.s. more details about the problem are in the reply above... just FYI, hope it can help.
Click to expand...
Click to collapse
Return to STOCK voltages. Stock volts aren't just 25mV across the board. This will likely sort out your issue. Have a search in the NS forums, i don't have a handy list on me.

Not looking forward for a fight, but once again, reflash the rom and don't flash another kernel this time. I'm sure you'll live without BLX 80% for a day or two.
Then if the reboots and/or crashes are gone, we can say it's the kernel or the settings and work from there. If not, then we at least eliminated a possibility.
Either way, the stock voltages are:
100MHz 950mv
200MHz 950mv
400MHz 1050mv
800MHz 1200mv
1000MHz 1250mv
Cheers.

Harbb said:
Return to STOCK voltages. Stock volts aren't just 25mV across the board. This will likely sort out your issue. Have a search in the NS forums, i don't have a handy list on me.
Click to expand...
Click to collapse
I've experienced the problem under both stock & +2mV voltage ;P
I have no developing experience though, I don't quite believe it's caused by uv.
thanks for suggestion and your search anyway, you guys are really kind!

polobunny said:
Not looking forward for a fight, but once again, reflash the rom and don't flash another kernel this time. I'm sure you'll live without BLX 80% for a day or two.
Then if the reboots and/or crashes are gone, we can say it's the kernel or the settings and work from there. If not, then we at least eliminated a possibility.
Either way, the stock voltages are:
100MHz 950mv
200MHz 950mv
400MHz 1050mv
800MHz 1200mv
1000MHz 1250mv
Cheers.
Click to expand...
Click to collapse
thanks! As I've already flashed Matr1x V21.0 before reading your post, I'm gonna give the new version a try - let's see how it will do!
In the next few days I should be flashing AOKPCB R2.1, if issue continues I would definitely do what you have posted.
Thanks again!

polobunny said:
Not looking forward for a fight, but once again, reflash the rom and don't flash another kernel this time. I'm sure you'll live without BLX 80% for a day or two.
Then if the reboots and/or crashes are gone, we can say it's the kernel or the settings and work from there. If not, then we at least eliminated a possibility.
Either way, the stock voltages are:
100MHz 950mv
200MHz 950mv
400MHz 1050mv
800MHz 1200mv
1000MHz 1250mv
Cheers.
Click to expand...
Click to collapse
Those are stock ARM voltages. Matr1x (and others, like TEUV) are also UVed with INT (GPU) voltages which can cause the same problems.
The following are stock INT voltages which you can change with NSTools:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
edit: thanks to polobunny for correcting me

Harbb said:
Those are stock ARM voltages. Matr1x (and others, like TEUV) are also UVed with INT (GPU) voltages which can cause the same problems.
The following are stock INT voltages which you can change with NSTools:
100MHz 900mV
200MHz 950mV
400MHz 1000mV
800MHz 1050mV
1000MHz 1100mV
Click to expand...
Click to collapse
You are right, but those aren't the stock INT voltages.
However, those are:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
Cheers!

Ah, stupid mistake there. Thanks polo, clearly my mind was elsewhere.

mathkid95 said:
Hmm.. try v21.0 or raise voltages
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
Matter continues in V21.0 pal...

Harbb said:
Those are stock ARM voltages. Matr1x (and others, like TEUV) are also UVed with INT (GPU) voltages which can cause the same problems.
The following are stock INT voltages which you can change with NSTools:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
edit: thanks to polobunny for correcting me
Click to expand...
Click to collapse
polobunny said:
You are right, but those aren't the stock INT voltages.
However, those are:
100MHz 1000mV
200MHz 1100mV
400MHz 1100mV
800MHz 1100mV
1000MHz 1100mV
Cheers!
Click to expand...
Click to collapse
Ah I just found that I forgot to say thanks to you guys...
Sorry for my absent of mind! And a lot of thanks!

mathkid95 said:
No I understand you're not bashing my work... forgive my rudeness
Yes, try to flash v21.0 and then if that doesn't work I will look into it
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
flashed V22 & raised voltage, still no use.
pm'ed you more details yesterday or earlier.
please tell me if logcat is needed.
cheers!

It Could Be Just A Hardware Issue ,I Had The Same Thing Happen With My Epic

MichaelCampos said:
It Could Be Just A Hardware Issue ,I Had The Same Thing Happen With My Epic
Click to expand...
Click to collapse
well this happens only when I'm on Matr1x kernel.... a great work it is though...

Same thing happens to me with Matr1x kernels, regardless of the rom (CM9 Kang, AOKP, or Kangyultra).
Everything returns to normal if I reflash just the kernel. Seems like a directory or file gets corrupted after a period of time.
Sent from my Nexus S 4G using Tapatalk 2