Seems like everyone has abandoned any idea of using SetCPU on a custom ROM. I'm currently running Glitterballs's 1.2 GHz OC/UV kernel, and it seems to be working perfectly. I'm going to update the op with how it works through the day. I currently have a screenoff profile set and a screenon profile set, with no issues. Feel free to try it yourself, however I wouldn't try it on any kernel besides Glitterballs's just yet until I do more testing. http://forum.xda-developers.com/showthread.php?t=505419.
I just installed SetCPU and it looks like it's working very well so far!
SetCPU crashed my phone when I put it to sleep... just use OC/UV to do your OCing.. no need to use setCPU.
YMMV, but I've been using SetCPU with every OC/UV kernel I've ever tried. I don't use any of the "profile" features, but I do use it to control the CPU speed and keep track of "time_in_state" stats and a few other things.
That includes SetiroN's kernel, Unhelpful's 2.1 kernel, and Glitterball's kernel. I even sometimes use it on non-OC kernels just to change the CPU power scheduler, like to force a specific speed.
Again, might be different for others, but in my experience, there's nothing wrong with SetCPU.
I've been breaking my head over here testing and flashing and editing ect to see what is the best balance for performance. There is something I have come across. Its the pulldown notification bar behavior in touchwiz (only touchwiz for some reason when using LP or Go they are not affected). Using stock kernel I have noticed when forcing gpu ui rendering "debug.sf.hw=1" it performs better and there is no lag in the pulldown. Flash the faux kernel and your swiping performance seems even better (prob due to OC) but the pulldown becomes laggy. It stutters. Always. Every rom every time. (Some are a little better but compare it to another and its very noticeable). This is only affected with touchwiz and only on the home screens. Open an app and pulldown behaves normal again. Then on some other roms using a stock kernel the gpu forced has the same behavior. Lag. Only there. Only touchwiz. Remove it from the build prop and voila smooth pulldown again. I know I could use another launcher but I like touchwiz compared to other launchers (its the smoothest but lacks features I know). Same result with the modded 4.5 Tw as well. Then there are other roms that perform amazing without gpu ui rendering like TPC. Its disabled in the build prop. So basically I need someone smarter than me to shed some light as to what this may be. Do we need to render the ui in gpu? Is it better? Why is only touchwiz affected? Does it use some sort of rendering that conflicts in certain cases? Is there something completely different causing this? Thanks a bunch and hope to hear what you all have to say
Basic with a Twist SGS4G KJ6 Kernel
BML, don't flash if you have partitions converted to MTD.
Use at your own risk, I take no responsibility for anything that may happen to your phone because of this kernel.
This kernel is for those who don't want to be on the very cutting edge (CM7) but rather want stability without sacrificing too many recent features. It is based mostly on Bryan's 0.0.2d commit that supposedly never had problems with silent reboots. I made some changes to the config to bring it even more to the standard Samsung VibrantPlus in terms of hardware settings, but at the same time to optimize it for speed. I will add only tried and true features to this kernel, the ones that other kernel developers have used successfully.
Special thanks to bhundven (Bryan), FBis251, TeamAcid.
Features
initramfs from TeamAcid, including CWM5, SuperSU, forced ext4, etc.
Usual CIFS, TUN. I didn't include FUSE, if anybody needs it let me know.
BLN. Use BLN Control app from market to activate.
Voodoo Sound so paid app is not needed. Voodoo Sound app from market is required. Once installed, enable Smart Amplifier, it's the best thing you can do to improve music listening experience with our phone.
jhash3 for faster hash calculations. Used widely across the kernel, especially in networking.
OC/UV support with extended frequency table. Added 600Mhz, 900Mhz, 1.1Ghz, 1.2 Ghz, 1.3 Ghz, 1.4 Ghz. Use SetCPU or Xan's Voltage Control to enable and control frequency and voltages. Tegrak can be used only with no-OC/UV version.
ondemandX and smartassV2 governors. One of these should probably be preferred over stock ondemand. Change with SetCPU or similar.
TinyRCU. More lightweight version, it fits better our single CPU system.
Swap support, although I don't recommend using it.
SIO and BFQ I/O schedulers in addition to noop, deadline, and cfq that we already have.
Install
Flash with CWM or SGS Kernel Flasher. ODIN version is available only for OC/UV kernel.
Download
CWM:
v1.1.3
v1.1.3 (no OC/UV)
v1.1.2
v1.1.2 (no OC/UV)
ODIN:
v1.1.3
v1.1.2
Notes
* OC/UV version is very conservatively undervolted to -25mV. The preset voltages are still higher than on regular I9000, which has the same CPU. I'm running additional -50mV (total -75mV) for all frequencies without issues, but you may have them, every CPU is different!
* It is recommended to create a CWM recovery file before modifying voltages. This option is available in both SetCPU and VoltageControl.
* OC-ing to 1.4 Ghz is not recommended, especially for extended periods of time.
* Voodoo ext4 conversion, or "lagfix", is enabled and forced by default. There is not way and no need to go back to RFS.
Source
www.github.com/AntonX
Changelog
1.1.3
CWM 5.0.2.8 (blue) in initramfs
Disabled a little more of Samsung debugging
1.1.2
Minor changes to initramfs voodoo extension scripts
More neutral boot logo
1.1.0
Initramfs script will not force su update
Couple of small changes
1.1rc2
Few small changes
1.1rc1
Added BFQ and SIO I/O schedulers
Switched to TinyRCU
Added Swap support
Small change to Vibetonz
1.0b5
Some changes to OC/UV
Better BLN fix
Increased write timeout for bad SDHC cards
Added ondemandX and smartassV2 governors
Renamed the title, it's becoming less and less Basic...
1.0b4
Added native OC/UV support
1.0b3
Minor BLN changes
Replaced jhash.h with jhash3 code
Updated initramfs with SuperSU 0.88
1.0b2
Added BLN, first attempt
1.0b1
Original release
Let me be the first to push you....please consider BLN lol, that would be awesome!
Could you point me to the right repository/branch?
I'm curious to see your changes and I'm probably not looking in the right place on github.
Please add BLN
bhundven said:
Could you point me to the right repository/branch?
I'm curious to see your changes and I'm probably not looking in the right place on github.
Click to expand...
Click to collapse
Well, I didn't upload anything yet. If you tell me how to control the frigging repository from Windows I'll do it right away
But seriously I want to make absolutely sure that this kernel doesn't have this nuisance of silent reboots. Because it they still present there is no need to have this kernel.
No matter what happens, if Vooodoo sound works without problems, I'll give you the code if you want it.
AntonX said:
Well, I didn't upload anything yet. If you tell me how to control the frigging repository from Windows I'll do it right away
But seriously I want to make absolutely sure that this kernel doesn't have this nuisance of silent reboots. Because it they still present there is no need to have this kernel.
No matter what happens, if Vooodoo sound works without problems, I'll give you the code if you want it.
Click to expand...
Click to collapse
I'm about to post something to my cm7 thread, so heads up.
But stock kj6 kernel (if you download it from opensource.samsung.com and apply a few of my changes to fix tfsr and add initramfs) still has the same reboot issue.
I'm gonna start comparing some of the code from the froyo kernel to see wtf is going on. I fixed a problem with rild and random reboots are back.
I'm finding that the problem is related to suspend. The reboot happens when everything quiets down.
AntonX said:
If you tell me how to control the frigging repository from Windows I'll do it right away
Click to expand...
Click to collapse
Haha, I don't even know. Don't use Windows?!?
put BLN in!!!! (i would do it myself, REALLY, i would but i don't know how)
bhundven said:
But stock kj6 kernel (if you download it from opensource.samsung.com and apply a few of my changes to fix tfsr and add initramfs) still has the same reboot issue.
Click to expand...
Click to collapse
I'm operation on the assumption that 0.0.2d never had silent reboots. Nobody ever reported having them with this version. I have never ever experienced a reboot with it myself. That's why I took it as the base.
I haven't really looked what you did right after 0.0.2d. Seems like you switched to aries config instead from vibrantplus. Any particular reason? Anyway, I reverted it back and even slightly more back. Then you did some clean up and modified bunch of code. I don't care about cleaning somebody else's code like this. Unused functions and variables will be optimized out by the compiler anyway. To get rid of annoying warnings I just used -Wno-unused switch to gcc in the Makefile.
So - hard to tell what's happened between 0.0.2d and 0.1.0 (or 0.1.1?), but something must have happened. Too many people reported it to support this.
Great initiative Anton!
Flashing it on 2 devices. I will update in 3 days.
Sent from my SGH-T959V using XDA
Anton
Just flashed. I'm fully charging up right now. I'll run it for a day to check on battery life and do some restores to make sure all that is good to go. Including voodoo is a nice touch. A already have the paid app because the headphone amp is something I can't live without but really nice for those that haven't used it to check it out. I have never had a reboot on 2d so hopefully this will maintain that tradition. Nice work.
is voodoo sound fix better than the beats audio??
m0bstr said:
is voodoo sound fix better than the beats audio??
Click to expand...
Click to collapse
Voodoo is hardware. Beats audio sodtware
Sent from my SGH-T959V using xda premium
Voodoo Sound, awesome!
Thanks man.
Sent from my SGH-T959V using XDA
I've never used voodoo sound before, but wow I was missing out..... Separation seems slightly better, clarity, just everything is awesome... And being able to adjust output gain is nice too.
Also, so far, no reboots.
Sent from my SGH-T959V using XDA
Finally a kernel w/ Voodoo Sound! I've been using the paid app for awhile but the module doesn't load on boot sometimes plus I've always wondered if there might be a difference between the app loading the module vs. the module built in to the kernel. I've gotten really use to BLN though (hint-hint)... thank you!
Sent from my SGH-T959V using xda premium
Another request for BLN. Hope we have enough voters!
Figures, as soon as I jump ship voodoo sound comes out to play...
Sent from my Galaxy Nexus using XDA
tehgyb said:
Figures, as soon as I jump ship voodoo sound comes out to play...
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
gnexus lol
so far not a single problem, touch wood...
Hey guys, I'm using the CM10 Rom right now and I was wondering if there was any ways to improve the performance of the Infuse. I checked geekbench and got a score of around the 330s. I tried the supercharger and things still seem quite slow, and often games lag and kill my battery.. Any help?
bboysamm said:
Hey guys, I'm using the CM10 Rom right now and I was wondering if there was any ways to improve the performance of the Infuse. I checked geekbench and got a score of around the 330s. I tried the supercharger and things still seem quite slow, and often games lag and kill my battery.. Any help?
Click to expand...
Click to collapse
Install Scotts custom kernel and clock it to 1600mhz. Also, clean out all the unnecessary crap to make the ROM lighter. I typically look at what's loaded in memory to see what would be good to un-install with Titanium that is not needed.
DaMeatMan said:
Install Scotts custom kernel and clock it to 1600mhz. Also, clean out all the unnecessary crap to make the ROM lighter. I typically look at what's loaded in memory to see what would be good to un-install with Titanium that is not needed.
Click to expand...
Click to collapse
I'm sorry, but I'm rather new. Where would I find this? I tried looking for it and I see no one labeled as Scott
Scott is the man who brought us cm10.
Look in the cm10 OP for the OC kernel and flash it on cwm.
Sent from my sweet & buttery Infuse
bboysamm said:
I'm sorry, but I'm rather new. Where would I find this? I tried looking for it and I see no one labeled as Scott
Click to expand...
Click to collapse
The guy who makes CM10 available for the Infuse is named Scott. He means the OC kernel 3_1. It's in the OP. To overclock, (once you have flashed the ROM), go to Settings --> System --> Performance.
Use these settings under Processor:
1. CPU Govorner: SmartassV2
2. CPU Maximum: 1600 Mhz
3 CPU Minimum: 100 Mhz
4. Checkmark "Set On Boot"
Use these settings under I/O Scheduler:
1. IO Scheduler: NOOP
2. Checkmark "Set On Boot"
Use these settings under Memory Management:
1. Checkmark "Allow Purging of Assets"
2. Checkmark "Kernel Samepage Merging"
Use these settings under Surface Improvement:
1. Select radio button labled "Fix Color Banding and Blur Effect"
Exit settings by pressing "Back" until you get to homescreen.
Reset your device.
Enjoy a fast phone.
Don't ***** about battery life if you use these settings.
Although I love Instigator's Kernel, I believe that it is time to move on from the aging kernel code.
I have started to use the stock kernel with the Paranoid Android by gs2usr, but I wanted more options to my cpu usage so I got set cpu.
Now my question is, will set cpu interfere with the performance settings originally in CM10? I have set the setcpu governor to the same gorvernor in the performance settings. The addition I have is the profile at certain battery points. Did anyone experience anything that caused the app and the CM10 settings to interfere each other causing even more waste in battery?? (like putting teo anivirus software on one computer? )
jee'sgalaxy said:
Although I love Instigator's Kernel, I believe that it is time to move on from the aging kernel code.
I have started to use the stock kernel with the Paranoid Android by gs2usr, but I wanted more options to my cpu usage so I got set cpu.
Now my question is, will set cpu interfere with the performance settings originally in CM10? I have set the setcpu governor to the same gorvernor in the performance settings. The addition I have is the profile at certain battery points. Did anyone experience anything that caused the app and the CM10 settings to interfere each other causing even more waste in battery?? (like putting teo anivirus software on one computer? )
Click to expand...
Click to collapse
Best option is to stick to the performance setting built into Cm10 because it's had all the correct paths on how to adjust the kernel properly .
I don't use set CPU anymore I now use system.tuner pro as an alternate that's it
Sent from my SAMSUNG-SGH-I727 using xda premium
crashpsycho said:
Best option is to stick to the performance setting built into Cm10 because it's had all the correct paths on how to adjust the kernel properly .
I don't use set CPU anymore I now use system.tuner pro as an alternate that's it
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
From what I've been reading the performance module in cm10/aokp is still a bit iffy, but I do agree with the system tuner pro recommendations