Related
For the people that want overclocking, here is your chance. I took my standard voodoo kernel, and put in the stuff needed to overclock it. Thanks to nemesis2all and his OTB kernel from the Fascinate for the code needed to get this to work. Also, use extreme caution when using the higher clock speeds. The stock "max" voltage for the CPU is 1300mv, and 1500MHz and 1600MHz are both at 1500mv, so it's heavily over-volted at the top end. By default, the system will boot to 1000MHz and you need to set the speeds you want in Voltage Control App. I don't personally use this because I think overclocking is useless, so any bug reports need as much information as possible, or they will be dismissed and not looked into at all. If you run into an issue with the system locking up, odds are that you have undervolted to much for a given clock speed. Other than that, you're on your own. Same FAQ applies as the regular PBJ kernel, so look there until I get a chance to post it here as well.
Installation Instructions:
1. Download zip
2. Transfer to SDCard
3. Reboot into recovery, you'll need to have CWM if you don't already
4. Install zip from SDCard and select the zip you downloaded.
5. Reboot and enjoy
0808
Make logcat an option that can be turned on/off
-From root shell, run "logcat-enable" to turn logcat on, "logcat-disable" to turn it off
Make /preinstall partition swap space
Fix problem with rooting phone on boot
Fix fix_permissions in recovery
Update to recovery
0731
Fix mount USB Storage in recovery
0730
Updated CWM binary
Custom boot animation support
0709
Voodoo Sound V10
0615
Overclocking - Use Voltage Control App to adjust clocks and voltages
0602
Voodoo Sound fixed - Thanks supercurio
Removed OnDemand
Added FIFO and BFQ IO Schedulers
Added tun.ko and cifs.ko
0531
Initial release, built from source
Undervolted
Voodoo lagfix available - Thanks supercurio
Updated compiler flags
Linaro Toolchain for cross-compiling
Battery hack to allow for non-OEM Batteries - courtesy of SirGatez
init.d support
SDCard speed tweak (via init.d script)
Upstream EXT4 Patches
VFAT Patch
TCP and CFS Tweaks to help data/performance
V(R) IO Scheduler
Auto-root on boot
Maybe missing some other stuff, check Github for full changes
TODO (somewhat in order of importance):
Smooth out boot animation
NOTES:
If you are experiencing problems, I need detailed info to be able to fix it or help you out. Failure to provide detailed info will mean I'm just going to ignore your problem as user error. Details would be something such as which kernel you are flashing (filename) and steps to reproduce the issue. Also, if you used any other kernels that had the same problem or didn't have the problem.
DISCLAIMER
By downloading and using the kernels, this signifies that you have read this full post and the FAQ before reporting an issue. You also take all responsibility if your phone breaks or your warranty becomes void (which, if you're flashing this, it already is). I offer no guarantees as to anything working, though I try not to release broken stuff, it happens sometimes.
FAQ Placeholder
2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts
Undervolted and running ok so far.
Sent from my SCH-I510 using XDA App
Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
ZeppelinJ0 said:
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.
will2live said:
Go into a Terminal Emulator on the device and type Mount. 3rd or 4th row on the list should show ext4. If it does then lagfix is enabled. If you do not see Ext4 and it says rfs still then it is not enabled.
Click to expand...
Click to collapse
Well it's definitely enabled. I just must have set the CPU settings poorly because this thing is crawling right now, I can't even scroll through the app drawer!
I've been trying to CWM back to the other PBJ kernels however my phone hangs on reboot, I'm guessing because those need to be flashed with Odin.
asenduk said:
2k+ on quadrant @ 1.4ghz... Niiiiice
Thanks imnuts
Click to expand...
Click to collapse
I wish I knew what I was doing wrong.. running at 1.4 and my quadrant scores are exactly the same.... not that it really matters but still...
imnuts said:
. I don't personally use this because I think overclocking is useless.
Click to expand...
Click to collapse
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.
das7771 said:
Just curious as to why you think it's useless. I am sure you know some thing that I don't so your opinion matters to me. I love the fact that I can overclock, but if it's not needed then I might not bother. I know it did make a difference for my DX.
Click to expand...
Click to collapse
Use a program like CPUSpy that shows you the clock speed stats of your phone. >75% of the time, it will likely be in 400MHz or less, this probably approaches >90% if you say 800MHz or less, especially if you are not a heavy user. At that point, why overclock your phone? To get the overclocking stable, you need increase voltages across the board, and despite undervolting, you'll never get the same power usage as you can with a non-overclocked kernel as some of the voltage changes you can't revert. My opinion is that while overclocking can smooth some stuff out, for most day-to-day usage, it has no practical benefits and only causes more battery drain than you would otherwise have. Given how precious battery life is these days, why knowing make your battery drain faster?
it's funny you say that becuase i noticed with ludeboy's kernel that when overclocking system panel very rarely showed my phone running over the stock speed. Usually it was as you stated some where around 800mhz..I understand what your saying...Thanks for the quick response.
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Backup SD and app data b/c crashing/freezing can corrupt files.
Edit: Also keep Voltage Scheduler Remover on your phone just in case.
1600
1500
1400
1300 -0
1000 -25
800 -50
400 -75
200 -100
100 -150
"interactive" was unstable a couple kernels ago so I haven't tried it.
suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
Potentially, yes, but you may lose stability.
Awesomeness
I love it. I can deal with a slightly shortened battery life. I wanted to OC because a lot of the more intense games don't run as smooth as I would like. With OC, its all butter. Thanks!! I have mine set at 1400, and it really didn't improve my quadrant scores, but there's a noticeable decrease in lag going from one app to another.
suzook said:
So what if we run stock clock...but undervolt? Do you think we will see any batt savings?
Click to expand...
Click to collapse
You would see better battery life at stock clock speeds if you just used the standard (ie. not overclocked) kernel I built.
Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
I'm on board with not thinking it's necessary - though I can see how the tinkerers and speed demons would love it. (And all the more power to them, literally)
I don't know imnuts, I always noticed when I forced the phone into a higher overclock it always seemed quite a bit snapier.
Keep it on conservative. Interactive is buggy.
ZeppelinJ0 said:
Could you cuties advise on what sort of settings you're using for this?
I'm using the 'vr' setting with an Interactive governor at 1.1GHz and my phone is slowing to a crawl so it's hardly usable. I'm not looking for any crazy overclocking just something to keep my phone snappy whilst I keep in touch with my prostitutes and be sure they are working the proper street corners.
The weird thing is I'm not sure if Voodoo Lagfix is enabled. Voodoo control says yes, CWM says no and won't let me enable it that way, is there a way to be sure?
Spanks!
Click to expand...
Click to collapse
underscored said:
Just wondering if you're going to branch off development of PBJT w/o overclocking separately - or if this is going to be built/rolled into future releases?
Click to expand...
Click to collapse
This will remain separate from the standard kernel most likely. I will see if I can build off of this source without overclocking and have it work, though I don't know if it will. I want to keep them separate for stability and battery life reasons.
I've seen a couple of posts about this, but can't figure out how to get it to work. I installed Faux's DS OC/UV Kernel Version 0.4.3 kernel, but I can't get that OC/UV kernel to even boot. The soft keys light up, the screen turns off, and the phone just sits there.
Did a nandroid restore, and then installed Faux's DS SV Kernel Version 0.4.3 kernel. No problems with it so far, but I just wanted to know how some people can get the OC/UV kernel to work with the G2x, but others can't (aren't all these phones identical in terms of architecture, chips, etc.?)?
Just wondering if there's any improvement to battery life with this new kernel. I have SetCPU running too and have several different profiles setup.
Which ROM are you using?
Oops. Sorry. CM 7.1.0.1.
hadoob024 said:
I've seen a couple of posts about this, but can't figure out how to get it to work. I installed Faux's DS OC/UV Kernel Version 0.4.3 kernel, but I can't get that OC/UV kernel to even boot. The soft keys light up, the screen turns off, and the phone just sits there.
Did a nandroid restore, and then installed Faux's DS SV Kernel Version 0.4.3 kernel. No problems with it so far, but I just wanted to know how some people can get the OC/UV kernel to work with the G2x, but others can't (aren't all these phones identical in terms of architecture, chips, etc.?)?
Just wondering if there's any improvement to battery life with this new kernel. I have SetCPU running too and have several different profiles setup.
Click to expand...
Click to collapse
Faux has 2 kernel versions.... one that is PRE-Overclocked and PRE-Undervolted; and the other that is starts with stock speeds and voltages.
I've NEVER been able to get the pre-OC/UV'd kernels to work on any of the several phones I have went through. I get EXACTLY what you are getting now, just a black screen and unable to boot.
Download his "SV" rom. That is his kernel that starts off with stock settings. You'll get all the features and you can OC/UV manually.
Cool. Yeah, I got the SV running just fine now. Since you can't mess with the voltages with this kernel, does it still offer any better battery performance than the stock kernel?
You'll get all the features and you can OC/UV manually
Click to expand...
Click to collapse
Are you talking about adjusting these settings through SetCPU? For some reason, SetCPU works fine for changing clock speeds, but when I try and go to the "Voltages" tab in SetCPU, bam, it crashes with:
"The application SetCPU (process com.mhuang.overclocking) has stopped unexpectedly. Please try again."
hadoob024 said:
Cool. Yeah, I got the SV running just fine now. Since you can't mess with the voltages with this kernel, does it still offer any better battery performance than the stock kernel?
Are you talking about adjusting these settings through SetCPU? For some reason, SetCPU works fine for changing clock speeds, but when I try and go to the "Voltages" tab in SetCPU, bam, it crashes with:
"The application SetCPU (process com.mhuang.overclocking) has stopped unexpectedly. Please try again."
Click to expand...
Click to collapse
Make sure you delete setcpu data and cache everytime you change kernels or else you'll see that message.
Sent from my Calculator with Android.
jose makalolot said:
Make sure you delete setcpu data and cache everytime you change kernels or else you'll see that message.
Click to expand...
Click to collapse
Are you talking through Settings->Manage Applications->SetCPU?
hadoob024 said:
Are you talking through Settings->Manage Applications->SetCPU?
Click to expand...
Click to collapse
Yes.
Sent from my Calculator with Android.
jose makalolot said:
Yes.
Click to expand...
Click to collapse
OK. Just tried it. "Clear cache" was grayed out, but I did click on "Clear data" and then rebooted. I launched SetCPU. Chose the Tegra 2 chipset, selected "Set on Boot", created my Profiles, then tried Voltages, but got the same error
Any thoughts?
hadoob024 said:
OK. Just tried it. "Clear cache" was grayed out, but I did click on "Clear data" and then rebooted. I launched SetCPU. Chose the Tegra 2 chipset, selected "Set on Boot", created my Profiles, then tried Voltages, but got the same error
Any thoughts?
Click to expand...
Click to collapse
Never mind, mods please delete.
From my experience, Faux's kernel isn't playing nice with the latest stable CM release. That's why right now I'm back on stock CM kernel.
jamadio said:
From my experience, Faux's kernel isn't playing nice with the latest stable CM release. That's why right now I'm back on stock CM kernel.
Click to expand...
Click to collapse
Hmm.. Interesting. I'll keep an eye out for it. Today's my first full day with that combination of mod and kernel. Other than the weird battery charge amount readings, it seems to be stable with a better battery life than the CM kernel. Wish I could mess with the voltages too to try and eek out even more battery life. Oh well though.
Have you deleted your battery stats in CWM? When I had Faux 0.4.3 and EaglesBlood 2.4 (CM7 based) running together I had the same battery problems. I eventually went back to stock CM kernel and then I cleared the battery stats and everything normalized again.
To appropriately clear the battery stats, you have to be at 100% charge before you do it.
Let me know how it works, maybe I'll go back to 0.4.3.
jamadio said:
Have you deleted your battery stats in CWM? When I had Faux 0.4.3 and EaglesBlood 2.4 (CM7 based) running together I had the same battery problems. I eventually went back to stock CM kernel and then I cleared the battery stats and everything normalized again.
To appropriately clear the battery stats, you have to be at 100% charge before you do it.
Let me know how it works, maybe I'll go back to 0.4.3.
Click to expand...
Click to collapse
No kidding??? Nope. Hadn't heard about that. Will give that a shot late night tonight after I fully charge it when I get home. Thanks for the tip!
Any thoughts on this issue with SetCPU and not being able to access the "voltages" tab?
I went back and read over from the beginning of this thread to refresh myself. Two reasons come to mind:
1. It could be because I don't think Faux's SV kernel is optimized/set up to have it's voltages changed. On his OP, he won't even troubleshoot problems unless they're on the SV kernel. Hence, it makes sense not to give people the freedom to OC/UV it so they can't complain about problems they made for themselves.
2.It could also be SetCPU, I know other's have gone to Pimp My CPU (You can search it on XDA) because PMCPU was built from the ground up to OC and UV, but it's features outside of that are sparse. But eventually SetCPU caught up and is the No.1 for OC/UV.
Maybe giving Pimp My CPU a try wouldn't hurt, if it doesn't work than you know that the kernel won't allow it.
Cool. I guess I'll give this current combo a try and see if I even feel the need to mess with voltages. Got pretty good batter life today so far. Going to go home, charge the phone fully, wipe the battery stats and then resume testing.
I like how I can setup profiles on SetCPU. Wonder if PMCPU has something similar.
Thanks again though!
hadoob024 said:
I like how I can setup profiles on SetCPU. Wonder if PMCPU has something similar.
Thanks again though!
Click to expand...
Click to collapse
No problem. Yeah, that's what makes SetCPU so legit. I don't believe Pimp My CPU has that feature. Just establishing max, min, and their voltages. Could be wrong though.
Cool. I'll give this "clear battery stats" a shot and then might give this other app a try. So far impressed with how much battery life I have left already.
hadoob024 said:
Cool. I'll give this "clear battery stats" a shot and then might give this other app a try. So far impressed with how much battery life I have left already.
Click to expand...
Click to collapse
Any update?
I'm going to have to try later this evening or tomorrow. I forgot but when doing app updates, CW ROM Manager got updated. Anyway, I guess this update did something because when I tried rebooting into Recovery, it never did, it just rebooted normally into CM.
I finally launched CW ROM Manager, chose to "Reboot into Recovery", it then asked for su permissions (or something) and finally worked. Anyway, I rebooted like 4 or 5 times before I realized that this was the issue preventing me from rebooting into Recovery like I normally do. That put enough of a drain on the battery where I didn't want to wipe the battery stats <sigh>
And of COURSE I didn't bring my charger
Will try again this evening and post the results.
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
I've found that, in overclocking several Android devices, more often than not if you have an unstable OC, the device will either fail to boot, or will crash constantly. If it's not doing that, you're likely fine.
Um, you're not OCed yet. You need to install setcpu or cpu master and crank up the clock. Clemsyn or Blades gives you the option to OC. It doesn't just OC for you.
lol, and learn from my mistake: when overclocking, don't check the option of "set on boot" untill you have tried overclocking at the Ghz level that you want to use. Believe me, you don't want a bootloop that can only be solved by flashing or restoring from a backup.
acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
I have done extensive overclocking and undervolting.
Set your OC and voltage settings. Then use setcpu or pimpmycpu min and max to your highest OC MHz.
Then play 1 round of Dungon Defenders. If you make it through that then open the camera.
Repeat this on every MHz from top to bottom. If you are unstable at a frequency then increase your voltage slightly (like 10 - 20 mV) and try again.
If you are stable and want to get a little bit better battery do the same thing but lower the mV until dungeon defenders crashes.
Then start to increase it until you are stable.
If your tablet reboots your way low on mV
If it freezes your low on mV
If the widgets act funny, and/ or disapear every once in awhile your in the right ball park
If everything works except your camera freezes you are very close
Some kernels have more aggressive GPU timings which you can't really change so you might want to try another's kernel if you can't get stable.
Well, it seems that I can't go higher than the 1.2 GHZ. If I go any higher, I get some weird freezes and reboots.
Now I saw the post above but I dont see where I can adjust the different voltages, etc..Maybe I am not using the right program?
acdcking12345 said:
Well, it seems that I can't go higher than the 1.2 GHZ. If I go any higher, I get some weird freezes and reboots.
Now I saw the post above but I dont see where I can adjust the different voltages, etc..Maybe I am not using the right program?
Click to expand...
Click to collapse
What program are you using? Try SetCpu or Pimpmycpu
baseballfanz said:
What program are you using? Try SetCpu or Pimpmycpu
Click to expand...
Click to collapse
SetCPU is what I loaded
acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
Are you referring to this kernel?
I'm wondering because I have never heard about a "Blades 2" kernel.
EDIT: Nevermind, I figured it out. This is what Revolver Parts calls Blades' 10-01-2011 kernel.
Blades uses some aggressive GPU timings in some of his kernels. You may want to try Clemsyn 22 if you want to try and go above 1.2 GHz.
Ok, I'm running infusion A2, not OC'd, UV'd 100 across the board just fine.
My problem starts fast when I OC to 1600, it rans ok there, for the few minutes I tested it at stock voltages. The problem is when I change ANY CPU step to UV it just crashes and reboots my phone instantly. Tried it 3 times. It comes back on fine, even if I left set as boot checked (accidentally), but the settings were not saved. Haven't tried B2 yet to see it is repeatable on 1400, and don't really want to repeat it at all.
Any ideas why this is happening? On Doctorz ROM using SetCPU to OC/UV.
Thanks y'all
Try voltage control instead (free in the market) but honestly, not all Infuses can handle 1.6 ghz. In your case, you are most likely right on the line of crashing at 1.6, when you change the voltages, you cross that line.
Its well know messing with the native clock speed can AT some phones and some times cause low stability and reboots also force closes etc. I suggest you to try lower OC speeds like 1.4 Ghz ive been running my Infuse on 1.4 forever without one single problem.
Yeah, was gonna go to B2 and try 1.4, but figured I would get some suggestions first.
Had VC at first, but didn't try OC, just UV, gonna try that tomorrow.
jonrobertd - did you flash a certain kernal to OC your Infuse? Everything I've read says either the Infuse can't be OCed. I even tried using SetCPU but it kept giving me errors when I'd run it, telling me something like "no profiles loaded" or something like that.
---------- Post added at 07:31 AM ---------- Previous post was at 07:25 AM ----------
koriotto said:
...ive been running my Infuse on 1.4 forever without one single problem.
Click to expand...
Click to collapse
koriotto - how are you overclocking your Infuse? What OS are you using (Froyo, GB, etc.)?
You have to have a kernel that supports overclocking....and yes the infuse can be overclocked...I'm running it at 1.6 myself on my rom....the infusion gb kernel can be overclocked....entropy's daily driver can't...the community kernel is Froyo....if your running gingerbread rom and flash the community kernel your phone will bootloop.....read...
Sent from my SAMSUNG-SGH-I997 using xda premium
Overclock to high frequencies and lower the voltage too much and the CPU becomes unstable. Some can handle it, some can't, all cpus are different.
Sent from my SAMSUNG-SGH-I997 using XDA App
Hi, i have searched the forums, but haven't been able to find an answer, simply put i don't believe my xoom is overclocking. I have been testing it with an app called neocore, but have tried quadrant as well. It doesn't matter if i am at 1000 or 1700 Neocore always says that my xoom runs at between 34-36 fps, which is the same as when it was bonestock, quadrant is the same. No change in animation speed or results no matter what i have set the clock too. I currently have eos nightly 77 for 4g on my xoom, I was using the stock kernel that came with the rom, and recently downloaded the.3.0.5 tiamat overclock kernel, which after flashing think it was the same(I am a noob). I was originally trying to use android overclock to adjust my settings, now have completely uninstalled it and using eos's settings, no change. What am i doing wrong, or have missed?
Thanks for any help you can give me
For increased smoothness in animation, etc, I believe it is the overclocked gpu that helps as opposed to the cpu. Not all the eos kernels are overclocked. Quadrant score appears to be meaningless. Believe me, the eos kernels permit overclocking. What governor are you using? Is your setting stable?
I have it currently at interactive, after you mentioned the governer, i put it to performance and ran the neocore benchmark to see what would happen, 38.2. Well if it requires a gpu overclock that would make sense that i am not noticing a difference with the apps i am using. But raises another question,what is a overclocked cpu good for? More apps running at once? My overclock is ALLOT more stable with 77, i was previously on 74. Before it would get glitchy allot more often, and random reboots on anything above 1000. 1400 and i was having to watch the temperature, 1500 seemed to work the best, but still got random reboots (still better than what I got on honeycomb. I still get glitches here and there on 77, but still have yet to get a.random reboot.
Unrelated to my topic, thank you so much for your guide to rooting and romming, i had read a couple others and hemmed and hawed about whether to do it, even though my mouth watered about the benefits, your guide made me clap my hands together and say "let's do this"
I went back over the kernel I downloaded and flashed, it is the team tiamat overclocked gpu 3.0.5 kernel that was realeased 2/19/2012... sorry, this stuff is new to me so I am learning as i go along
Draxin said:
I went back over the kernel I downloaded and flashed, it is the team tiamat overclocked gpu 3.0.5 kernel that was realeased 2/19/2012... sorry, this stuff is new to me so I am learning as i go along
Click to expand...
Click to collapse
No problem...the EOS nightlies are on a newer kernel, but I think the lastest don't have oc gpus.