[Q] oc kernel with stock voltage - Nexus One Q&A, Help & Troubleshooting

Out of curiousity. Is there an oc kernel out there that's stock voltage, or atleast not too under voltaged?

Do you not enjoy the extra battery life? 1.275v is the stock and anything below 900-950mv seems to decrease the radios. You might want to edit the source and recompile because most people don't have a problem with the undervolting on most kernels (when done correctly).

evilkorn said:
Do you not enjoy the extra battery life? 1.275v is the stock and anything below 900-950mv seems to decrease the radios. You might want to edit the source and recompile because most people don't have a problem with the undervolting on most kernels (when done correctly).
Click to expand...
Click to collapse
Im willing to sacrifice battery life for the ability to stop dropping calls. Although Miami has hspa+ T-Mobile foot print here is spotty. I fluctuate between edge n 3g way too much. Every rooted nexus owner I know has that issue here. My brother has a stock nexus and he doesn't fluctuate as much as me...

Where can I find the stock frg kernel or frf kernel?

MoDaCo uses stock boot images I believe.

evilkorn said:
MoDaCo uses stock boot images I believe.
Click to expand...
Click to collapse
Thank-you
10 char

Related

CPU Temperature

I have setcpu installed on my Nexus One, along with the Zimage and lib files I need to overclock it. Can anyone tell me what an appropriate temperature range is for the Nexus, as would be shown in the SetCPU widget? I want to be sure I don't cause my Nexus to overheat.
Around 21-36 for me.. highest it ever got was 40.3 degrees.
crawler9 said:
I have setcpu installed on my Nexus One, along with the Zimage and lib files I need to overclock it. Can anyone tell me what an appropriate temperature range is for the Nexus, as would be shown in the SetCPU widget? I want to be sure I don't cause my Nexus to overheat.
Click to expand...
Click to collapse
rjhay22 said:
Around 21-36 for me.. highest it ever got was 40.3 degrees.
Click to expand...
Click to collapse
Is that in Celcius or Fahrenheit?
i would hope its in Celsius, or it would mean that the CPU is cold enough to freeze water
Alright thanks mines been on average about 99 degrees Fahrenheit
that's what I get when I'm charging my phone, so that's pretty high if that's what you have on standby.
crawler9 said:
Alright thanks mines been on average about 99 degrees Fahrenheit
Click to expand...
Click to collapse
Would it matter if I have a silicon case on it? And how high is dangerously high?
I have the same case, I wouldn't want it to go over 40C or bout 102 F. Thats pretty hot, I notice my phone gets sluggish and starts forceclosing too... What ROM are you running? And are you using OC-UV kernel? If not I suggest you get it.
crawler9 said:
Would it matter if I have a silicon case on it? And how high is dangerously high?
Click to expand...
Click to collapse
rjhay22 said:
I have the same case, I wouldn't want it to go over 40C or bout 102 F. Thats pretty hot, I notice my phone gets sluggish and starts forceclosing too... What ROM are you running? And are you using OC-UV kernel? If not I suggest you get it.
Click to expand...
Click to collapse
At the time I had SetCPU and was overclocked, I had Cyanogen's latest stable ROM (5.0.5.3?) installed. I was using the UV kernel. Last night I switched to Alpha r20 of MoDaCo's desire ROM for Nexus along with whatever kernel that comes packaged with.
You should be able to flash the OC-UV kernel by pershoot over Modacos desire ROM.
Battery life means more than OCing to me so here's my SetCPU profile settings if it helps.
Default setting: 998/245
Charging: 844/245
Standby: 245/245
Power<35%: 883/245
Failsafe batt > 40: 729/245
I should add that I'm charging right now, music player on, using my phone non stop and my batt temp is 95F.
crawler9 said:
At the time I had SetCPU and was overclocked, I had Cyanogen's latest stable ROM (5.0.5.3?) installed. I was using the UV kernel. Last night I switched to Alpha r20 of MoDaCo's desire ROM for Nexus along with whatever kernel that comes packaged with.
Click to expand...
Click to collapse
rjhay22 said:
You should be able to flash the OC-UV kernel by pershoot over Modacos desire ROM.
Battery life means more than OCing to me so here's my SetCPU profile settings if it helps.
Default setting: 998/245
Charging: 844/245
Standby: 245/245
Power<35%: 883/245
Failsafe batt > 40: 729/245
I should add that I'm charging right now, music player on, using my phone non stop and my batt temp is 95F.
Click to expand...
Click to collapse
Sounds like a good profile, and I think I'll try that myself and see where my temperature lies with those settings. Just curious... what are the advantages of using the OC-UV without overclocking?
Here's information on the kernel with the ROM I'm using, directly copied from the page with the ROMs.
What kernel are you using? Any other tweaks worth knowing about?
The ROM has the usual MCR tweaks (tun.ko, openvpn, busybox, dropbear etc.) and is running a custom kernel by teknologist and myself based on the stock .33 source (check the changelog below for more details). Himem is enabled. The kernel runs at standard clock speeds, uniquely only using undervolt at the lowest clock speeds.
Good question, I had an option to just undervolt it, there is a UV @stock speed kernel by Persianone too, but I opt to get the OC-UV just incase I need to show off how fast my N1 is. LOL. Better to have the option to use it when i need it.
crawler9 said:
Sounds like a good profile, and I think I'll try that myself and see where my temperature lies with those settings. Just curious... what are the advantages of using the OC-UV without overclocking?
Here's information on the kernel with the ROM I'm using, directly copied from the page with the ROMs.
What kernel are you using? Any other tweaks worth knowing about?
The ROM has the usual MCR tweaks (tun.ko, openvpn, busybox, dropbear etc.) and is running a custom kernel by teknologist and myself based on the stock .33 source (check the changelog below for more details). Himem is enabled. The kernel runs at standard clock speeds, uniquely only using undervolt at the lowest clock speeds.
Click to expand...
Click to collapse
rjhay22 said:
Good question, I had an option to just undervolt it, there is a UV @stock speed kernel by Persianone too, but I opt to get the OC-UV just incase I need to show off how fast my N1 is. LOL. Better to have the option to use it when i need it.
Click to expand...
Click to collapse
Alright thanks for all the help.
My pleasure
crawler9 said:
Alright thanks for all the help.
Click to expand...
Click to collapse

Pershoot's OC kernel, with no UV?

Hey guys
First of all, my apologies if such request has already been made. I searched for "pershoot kernel no uv" and "pershoot kernel stock voltage" and came up empty handed.
As the title says, I'm looking for a kernel similar to pershoot's, with all its tweaks except for the undervolting.
The reason for this: I love the speed, the audio boost, capacitive buttons fix, BUT I'm noticing an impact on signal strength from the radio. I remember reading a horror story from a user here who thought using and UV'ed kernel killed his radio and I'm getting nervous.
For reference I have on hand 3 nexus's. All AT&T versions, 2 of them dead stock, 1 (mine) rooted, running Rodriguezstyle's v2.3fix froyo rom with pershoot's oc uv .33.4 kernel. I'm getting anywhere from -10 to -20 db's less in my signal meter in my phone as compared to the stock ones. It sucks since my rooted one completely smokes the other two when it comes to features and speed.
I'd like to go back to stock voltage and see if my signal reception improves. I hope it hasn't caused damage to the radio.
Thank you!
Uh bump? I'm now using a rooted FRF83 stock ROM with the stock kernel and my signal reception is definitely better but I already miss pershoot's... Anybody got a suggestion? Thanks!

[Kernel]Alternative CM6/Ruby Kernel

Hey folks,
It was requested of me to make a thread regarding this. I have compiled an alternative kernel for aosp based roms. It should work with any of them.
1.0
All governors enabled, interactive patched in, conservative as default
Anticipatory scheduler vs. deadline ins stock cm6
Supports wired tethering
Latest source (may be newer than cm6?)
tun.ko support for vpn
More will be added later.
Thank you Koush, for providing me the fix for screen tearing and thanks sniffle, for helping me with making the kernel work with aosp
http://adrynalyne.us/files/kernels/cm6_ruby/
Source:
http://adrynalyne.us/files/kernels/cm6_ruby/source/
Nice job buddy! Thank you! I'll give it a shot tonight.
Sent from my ADR6300 using XDA App
oh hell yea.
maybe this will help all us aosp guys get a stable phone to use...
Just loaded it up. Will be back. To report.
Sent from my ADR6300 using XDA App
dnoyeb said:
oh hell yea.
maybe this will help all us aosp guys get a stable phone to use...
Click to expand...
Click to collapse
Thats the plan
Any plans to get undervolt and oc?
Trying now, thanks...
Is there a place I can find the Stock CM6 kernal, in case I don't like this one? Ill report back in a little bit
Its slower than the CM6 kernal. I ran a linpack of 27 and quadrant of 1277. This was both running "performance" mode, and turning set cpu to the max which was 1000. I Am going to give it a try, maybe the battery life will make up for the performance loss. If not, nandroid here I come.
bradm23 said:
Trying now, thanks...
Is there a place I can find the Stock CM6 kernal, in case I don't like this one? Ill report back in a little bit
Click to expand...
Click to collapse
ditto request backup stock cm6 kernel
I just hope it fixes my WiFi shutting off constantly.
Seems to be really solid, a bit slower than cm-6 but also took care my screen flicker and haven't found any negatives yet (1.0+ hr up time) . Looking forward to some overclock variations. Thanks for the work adrynalyne.
bradm23 said:
Its slower than the CM6 kernal. I ran a linpack of 27 and quadrant of 1277. This was both running "performance" mode, and turning set cpu to the max which was 1000. I Am going to give it a try, maybe the battery life will make up for the performance loss. If not, nandroid here I come.
Click to expand...
Click to collapse
Not sure what to tell you. The Sense version of this kernel has considerably better than that.
adrynalyne said:
Not sure what to tell you. The Sense version of this kernel has considerably better than that.
Click to expand...
Click to collapse
I wasn't complaining. I will take a slightly slower kernal thats rock solid and great battery, vs a quicker but less stable.. sorry I came off like i was complaining. I really appreciate all your hard work, thanks.
bradm23 said:
I wasn't complaining. I will take a slightly slower kernal thats rock solid and great battery, vs a quicker but less stable.. sorry I came off like i was complaining. I really appreciate all your hard work, thanks.
Click to expand...
Click to collapse
Oh I didn't take it as such.
I just don't know why
Unless the scheduler differences are doing it. Its possible.
Did you say that the top speed showed 1000 in setcpu vs. 998400?
unstable for me on 9/10 nightly wifi on and no setcpu, 3 random lockups/reboots in past 2 hrs
32.61 linpack and 1341 quadrant. Its not much slower than cm-6. @adrynalyn, do you plan on bumping up the clock speeds? Mine is showing 1000 max btw. Thanks again
I wasn't complaining. I will take a slightly slower kernal thats rock solid and great battery, vs a quicker but less stable.. sorry I came off like i was complaining. I really appreciate all your hard work, thanks.
Click to expand...
Click to collapse
Oh I didn't take it as such.
I just don't know why
Unless the scheduler differences are doing it. Its possible.
Did you say that the top speed showed 1000 in setcpu vs. 998400?
Click to expand...
Click to collapse
It shows 1k for me too
Yeah I plan on some future bumps.
THANK YOU ADRYNALYNE!!!!!!!!!! I was so pumped when you told me you did this .
adrynalyne said:
Oh I didn't take it as such.
I just don't know why
Unless the scheduler differences are doing it. Its possible.
Did you say that the top speed showed 1000 in setcpu vs. 998400?
Click to expand...
Click to collapse
1k max for me as well. 998 didn't seem to be an option.
I'm getting similar performance as I get with kernels i compiled from koush's source where i only changed cpu speeds for overclocking and udervolting. Not as fast as koush's even when i bumped it up to 1.19Ghz. Which i couldn't figure out why since i used exact same source

[Kernel] Dragon 3.6

Download link: http://goo.gl/vzEB4
FAQs: http://forum.xda-developers.com/showpost.php?p=11436660&postcount=11 (Thanks Alienz!)
Yes, the kernel is still based on the i9000 JPX source release. Hopefully we get real source soon.
Main Features:
NEAR STOCK BATTERY!!! (Thanks Morfic!)
Overclock up to 1.4Ghz.
BLN (Backlight Notifications).. A basic app is included to turn it on if you want it
Voodoo lagfix v5
Voodoo Sound v4
Many parts of the "speedmod" patch from the i9000 forum
OC is based on raspdep's OC patches, also from the i9000 forum
Various speed tweaks
CIFS/SMB and NFS support compiled in (no modules)
Tunnel support compiled in (no modules)
Changes since 3.2:
New boot logo. (Thanks Alexia!)
Added battery drain fix in standby discovered by Morfic. Should be about the same battery as stock now.
Voltages and frequency scaling have been adjusted to more quickly jump to higher frequencies and come down slower. Improves response time while you use the phone.
The Voltage Control app has the correct voltages, I recommend leaving the lower speeds alone to start with. Going too low can cause the sleep of death. That's why they are as high as they are. NOTE: The voltage control app does not control the available states they way the older ones do. That screen is useless, ignore it. Set your max and scheduler if you wish, and the voltages if you want to change them.
SetCPU.... If you want to use it, you can have it set min/max. If you set profiles, don't set the max under 800. The phone needs 800 to be available. I use a screen off profile at 100-800 just to keep the OC disabled while sleeping. No reason it should need to really crank up the speed if I'm not looking at it. SetCPU is NOT required, I'm offering this as a tip for fans of that application.
The kernel has proven stable for a number of testers so far. If you get crashes, disable any OC/UV settings and try again. I recommend you only change one setting at a time, and NOT set at boot until you have run for a while to ensure you can run stable at that voltage/speed.
Great job testing it out now. Edit: screen is a little dark but the kernel is super smooth
Sent from my SGH-T959 using XDA App
Going to test! Will post results in a couple of hours.
onix
I am considering flashing this new kernel but have a couple of questions I would like to ask first. I am currently on Bionix V 1.21 and love it. Is this kernel compatible with Bionix V 1.21? It appears that this kernel is Voodoo enabled so I presume I would not have to disable voodoo. If I decide to go back to the Kb1 with voodoo enabled which I believe is the stock kernel for Bionix V 1.21 would i just flash the kernel( is is available on TW forum?)or would I have to flash the whole rom again? I would think I would not have to but want to be sure before I leap. I would not like to have to ask for help for problems that could have been avoided by reading and asking questions. Any and all help is greatly appreciated.
Is it ok to not use set cpu? Will this kernel will oc over 1000?
ttabbal said:
Download link: http://goo.gl/vzEB4
Yes, the kernel is still based on the i9000 JPX source release. Hopefully we get real source soon.
Main Features:
Voodoo lagfix v5
Voodoo Sound v4
Many parts of the "speedmod" patch from the i9000 forum
OC is based on raspdep's OC patches, also from the i9000 forum
Various speed tweaks
CIFS/SMB and NFS support compiled in (no modules)
Tunnel support compiled in (no modules)
Changes since 3.2:
New boot logo. (Thanks Alexia!)
Added battery drain fix in standby discovered by Morfic. Should be about the same battery as stock now.
Voltages and frequency scaling have been adjusted to more quickly jump to higher frequencies and come down slower. Improves response time while you use the phone.
The Voltage Control app has the correct voltages, I recommend leaving the lower speeds alone to start with. Going too low can cause the sleep of death. That's why they are as high as they are. NOTE: The voltage control app does not control the available states they way the older ones do. That screen is useless, ignore it. Set your max and scheduler if you wish, and the voltages if you want to change them.
SetCPU.... If you want to use it, you can have it set min/max. If you set profiles, don't set the max under 800. The phone needs 800 to be available. I use a screen off profile at 100-800 just to keep the OC disabled while sleeping. No reason it should need to really crank up the speed if I'm not looking at it.
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
This kernel is much more stable for me than the dow kernel. Great work.
tenbeau said:
I am considering flashing this new kernel but have a couple of questions I would like to ask first. I am currently on Bionix V 1.21 and love it. Is this kernel compatible with Bionix V 1.21? It appears that this kernel is Voodoo enabled so I presume I would not have to disable voodoo. If I decide to go back to the Kb1 with voodoo enabled which I believe is the stock kernel for Bionix V 1.21 would i just flash the kernel( is is available on TW forum?)or would I have to flash the whole rom again? I would think I would not have to but want to be sure before I leap. I would not like to have to ask for help for problems that could have been avoided by reading and asking questions. Any and all help is greatly appreciated.
Click to expand...
Click to collapse
Im not sure if you have to disable voodoo or not .. probably not but don’t take my word for it and no you do not have to flash the whole rom again, just the kernel. Thanks for not clogging up the forums. Lol I know its hard to ask questions in the vibrant forums, (cause you'll get beaten to death with mean comments) but ask them anyway, someone will answer eventually. Ignore the whiny, ungrateful 2 year olds that somehow wandered onto this forum...
Sent from Bionix powered vibrant! If I helped, hit the thanks button!
I flashed without disabling voodoo
treyvaporizer said:
Im not sure if you have to disable voodoo or not .. probably not but don’t take my word for it and no you do not have to flash the whole rom again, just the kernel. Thanks for not clogging up the forums. Lol I know its hard to ask questions in the vibrant forums, (cause you'll get beaten to death with mean comments) but ask them anyway, someone will answer eventually. Ignore the whiny, ungrateful 2 year olds that somehow wandered onto this forum...
Sent from Bionix powered vibrant! If I helped, hit the thanks button!
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
tenbeau said:
I am considering flashing this new kernel but have a couple of questions I would like to ask first. I am currently on Bionix V 1.21 and love it. Is this kernel compatible with Bionix V 1.21? It appears that this kernel is Voodoo enabled so I presume I would not have to disable voodoo. If I decide to go back to the Kb1 with voodoo enabled which I believe is the stock kernel for Bionix V 1.21 would i just flash the kernel( is is available on TW forum?)or would I have to flash the whole rom again? I would think I would not have to but want to be sure before I leap. I would not like to have to ask for help for problems that could have been avoided by reading and asking questions. Any and all help is greatly appreciated.
Click to expand...
Click to collapse
It is compatible with Bionix 1.2.1, that's what I developed it on.
If you have the red voodoo recovery, there is no need to disable voodoo for flashing. Generally speaking, kernels can be flashed without disabling voodoo in any case.
This is what iv'e done, I've lowered my Volts on some clocks, 1000 and up, and I was wondering should/can I use setcpu for profiles?
Answers to COMMON questions:
1. Can I flash this over Voodoo or RFS (stock)
You do NOT need to disable Voodoo. Flash right over Voodoo or RFS kernels. Make sure you are not running JFS though. JFS is not supported
2. How is stability? Does it crash? Sleep of death? etc?
Stability on this is AMAZING. It will not crash unless you overclock/undervolt and your settings are unstable. If that is the case, you know its your settings.
3. Do I need SetCPU to overclock?
You do not need to use SetCPU (You can if you want to). Use the Voltage Control App to overclock.
4. How do I overclock? Can I use this without an overclock?
By default, the kernel will boot to 1.0Ghz. To OVERCLOCk to 1.4Ghz (or lower) you need to use the app that this kernel installs during the flash. The app is called "Voltage Controll" and can be found in your app drawer after the flash
5. What is the battery life?
Battery life should be close to stock now. The battery drain issue that was present in the I9000-based kernels earlier has been solved.
6. Does this support BLN (Back-light-notificaations)?
Yes. You need the BLN control app from the market to use it.
7. How do I use Voodoo sound? What is it?
Voodoo sound is a vast improvement to the sound quality of your phone. To use it, download the Voodoo Control app from the Market.
8. What ROMs is this compatible with?
This is compatible with ALL Vibrant Froyo ROMS. This means 2.2 ROMS made for the Vibrant. 2.2.1 is not yet tested but should theoretically work.
I hope this helps.
ttabbal said:
It is compatible with Bionix 1.2.1, that's what I developed it on.
If you have the red voodoo recovery, there is no need to disable voodoo for flashing. Generally speaking, kernels can be flashed without disabling voodoo in any case.
Click to expand...
Click to collapse
Thanks so much for your kind and patient and swift reply. Donation just made. I really admire yours and all of TW generosity and patience with noobs like me. I am flashing the kernel now. Thanks again for sharing your brilliant work!!!!!!!!!!!!!!!
cashyftw said:
This is what iv'e done, I've lowered my Volts on some clocks, 1000 and up, and I was wondering should/can I use setcpu for profiles?
Click to expand...
Click to collapse
You can use setcpu for profiles, just keep 800Mhz available. The phone will likely crash if you don't. I set a screen off profile of 100-800 to keep the oc disabled when I don't need it, as 800 is a lower voltage.
Hint with voltages, try to keep 1000 and higher at the SAME voltage. Changing the voltage too often can cause instability as the voltage regulator doesn't adjust as fast as we would like sometimes. OC makes this worse as you need a higher voltage to maintain a stable CPU at the higher frequency. The kernel is set to jump to 1000, then to the max set clock speed. Setting 1000 to the higher voltage gives us some extra time to stabilize the new voltage before the just into the OC speeds.
tenbeau said:
Thanks so much for your kind and patient and swift reply. Donation just made. I really admire yours and all of TW generosity and patience with noobs like me. I am flashing the kernel now. Thanks again for sharing your brilliant work!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Thanks for your kind words and the donation. I'm glad you find my work useful.
just flashed this..
and a few questions ive never used OC before..
What does VOODOO Sound really do?
I set my thing on SetCPU as 1.4ghz as max and .1 as low with conservative.
then a profile with screen off and on conservative.
will those save battery?
xriderx66 said:
just flashed this..
and a few questions ive never used OC before..
What does VOODOO Sound really do?
I set my thing on SetCPU as 1.4ghz as max and .1 as low with conservative.
then a profile with screen off and on conservative.
will those save battery?
Click to expand...
Click to collapse
SetCPU by itself will NOT overclock. You need to use the Voltage app that comes with the kernel. See my above post with the Common questions.
I'd like any of the kernels developers gave me a clue about an issue im having with all custom i9000 based kernels (eugene's and TW's). The problem is with line2 voip app which calls isn't heard in the other end when running these kernels, but in stock/voodoo it works just fine. Please any of you have an idea of what could be going wrong?
thanks.
Okay tested so far, everything is working good (undervolted to about 175 for lower clocks 100-1000 and 75 for higher clocked 1200-1400)
Don't try this, as every phone can't handle some things, i'm just stating.
EDIT: I'm seriously stupid, how do I remove the settings again? I know it's in system/ something
Edit: NEVERMIND fixed
I've never used an OC kernel, was thinking of giving it a try. If I decide its not for me is this like removing a voodoo injected kernel, disable, then flash a diff kernel then delete files?
kcp877 said:
I've never used an OC kernel, was thinking of giving it a try. If I decide its not for me is this like removing a voodoo injected kernel, disable, then flash a diff kernel then delete files?
Click to expand...
Click to collapse
Just flash other voodoo kernel on top of it no need.to.disable voodoo
Sent from my SGH-T959 using Tapatalk

Should i run an overclocked kernel or a standard one ?

I just had a long time doubt and wanted to get a clear picture, is over-clocking harmful to the device ?
Or is it just the rated capacity of the processor that is utilized while over-clocking ? I also tried an OC version of notecore before which was slower than the STD version and hence from then on i never looked for over-clocking. But now with notecore OC becoming the standard release i would like to know about the options. thanks in advance.
Akilesh said:
I just had a long time doubt and wanted to get a clear picture, is over-clocking harmful to the device ?
Or is it just the rated capacity of the processor that is utilized while over-clocking ? I also tried an OC version of notecore before which was slower than the STD version and hence from then on i never looked for over-clocking. But now with notecore OC becoming the standard release i would like to know about the options. thanks in advance.
Click to expand...
Click to collapse
What rom are you on? You definitely can handle the oc notecore, because you can ran it in your device. I think the oc slow your device compared to standard because of some of init d scripts that humpers the full potential of oc. But if you say im in cleanote rom then i dont know why, only g. lewarne can diagnose it.
jonpaslim said:
What rom are you on? You definitely can handle the oc notecore, because you can ran it in your device. I think the oc slow your device compared to standard because of some of init d scripts that humpers the full potential of oc. But if you say im in cleanote rom then i dont know why, only g. lewarne can diagnose it.
Click to expand...
Click to collapse
You may find that your Note would reboot itself randomly! It may even not be able to complete Quadrant test when you flash oc Notecore kernel for example. The CPU temperature goes over 65c. That is whay happened to mine. So, I just flashed back to the standard version. Everything is then fine.
My Note has got VoltGroup B.
No need of a overclocked kernel..a, standard kernel is fine
It realldy depends on how you will use your sgnote. I for one uses it only for internet browsing,some games and alot of sms and calls so I prefer the Standard Notecore but if you want to get more kick out of your device then you can use the OC one. But as all OC on a device may or will drain the battery alot faster.
Agreed. I use the note for just calls, text and email. So I think I'll stay with standard one. Thank you all.
Sent from my GT-N7000
To overclock or not
That depends: Like yourself, I also use the Notecore kernel. If the Note is a secondary phone and you dont actually depend on it for your day to dayaffairs, then there probably wouldn't be any harm using the overclocked version. Now , keep in mind that when you do, you are more likely to see the phone freeze up once in a while, and thus, you'll have to reboot. I once loaded the OC version of Notecore on my Note and i got very empressive results on the Quadrant benchmark app.
On the other hand; if you are like me in that you are heavily dependant on your Note for a lot of day to day stuff and having your note freeze up in the middle of a very important business call or while your using the gps to find somewhere is totally unacceptable; then I would reccomend the standard speed. For my purpose, I find that the standard Notecore kernel is considerabely fast in of itself. If i have to choose between speed and stability, I'll choose stability every time.
I've tried a number of different kernels and every one of them has made my phone freeze up....except the Notecore. The Notecore is the only custom kernel that I've never seen my Note hang on.
My two cents worth...
I keep switching between Notecore and speedmod from time to time. But I keep coming back to Notecore always when there is an update.
Sent from my GT-N7000
Gavin announced the launch of Notecore V13 for tonight (GMT)...changelog (on page 511) sounds very interesting!
Also Franco is gonna come back with a beastly kernel soon.
Sent from my GT-N7000
I do not feel any differences with an oc kernel, maybe it's just me. btw Goku's kernel worth the try

Categories

Resources