[Kernel][CM7][July 12] Le Kernel Du Jour! Build #2 - Vibrant Android Development

DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY HARD OR SOFTWARE BASED DAMAGE. IF YOUR PHONE BRICKS, YOU LOSE IMPORTANT DATA, OR OTHERWISE INCUR LOSSES AS A RESULT OF RUNNING THIS KERNEL, ITS NOT MY FAULT.
DELETE ALL VOLTAGE CONTROL SETTINGS, AND REMOVE BOOT SETTINGS FROM CM SETTINGS AND VOLTAGE CONTROL AND DISABLE SETCPU PROFILES BEFORE FLASHING THE LATEST UPDATE. THIS GOES FOR ALL UPDATES, INCLUDING UPDATING CM.
This is a CM7 based kernel with a 1.6 Ghz overclock, Voodoo sound and color fixes, uv support, and BLN. See the changelog for all the updates and features.
Informations (THESE CHANGE ON A REGULAR BASIS):
1. Max clock is set to 1GHz on the first boot, set the max clock in CM settings or voltage control or setCPU.
2. I cannot possibly stress this enough. IF YOU EXPERIENCE BUGS WHILE ON THIS KERNEL, POST HERE. Do NOT submit bug reports to the CM team, until you have flashed back to stock CM, and can verify the bug exists there too.
3. Use Xan's UV app to undervolt.It's in that market, search "Voltage Control".
4. Want to go back to stock? First, if there's any particular reason, please let me know. I love to feedback, good or bad. Then, just flash the latest official update.
5. Sources --> https://github.com/TheEscapistxda/andoroid_kernel_samsung_aries
6. BLN is disabled by default. Please enable it by using the BLN control app from the market.
7. Its not a bug. You're not bricked. Let it boot up.
Thanks to Netarchy for his Nexus S oc code, coolhbo for setCPU, the CMSGS team for their work, Supercurio for Voodoo, raspdeep for his oc/uv patches(showed me how to create a sysfs interface for uv), Xan for the uv app, neldar for BLN, and cyanogen for his amazing rom.

CHANGELOG:
V1:
Initial release
V2:
Voodoo Sound v4 added!
v2.2
Fixed the OC bug from v2
Fixed the OC bug from (the unreleased) v2.1
Added some initial testing code for UV!
Removed v2 from the downloads
Added a stock kernel to downloads
v2.3
Added wifi sleep workaround from coolya
v2.4
Updated to be in sync with the official releases
Removed some debug code (coolya)
Added compatibility with the cpusettings in CMparts(coolya & atinm) (Only works under updates after march 04 update, as it requires code in the actual rom.)
v3.0
Added compatibility with Xan's uv app!
v3.1
Added the new wifi sleep fix
Fixed the uv bug (hopefully)
Removed v3
v3.2
updated to stay in sync with the 03122011 nightly
yas259 fixes(don't ask me about these, this driver is way over my head)
radio fixes(not ril polling)
config edits
v3.3
updated to keep in sync with the 20111303 nightly
Lots of little tweaks
-kernel hz = user hz =100
-update timings (Thanks Kang)
-enabled Tiny RCU
Removed the returntostock kernel
v3.4
Updated Voodoo sound to v5
Implemented voodoo color v2
v3.5
Updated Voodoo sound driver number to v5 (now the control app says 5)
Added 600mhz and 1.3Ghz steps
Added interactive and smartass cpu frequency governors
Some initial work on BLN (disabled)
Added frequency_voltage_table for compatibility with custom frequencies in the uv app (disabled due to bugs)
v4.0 - (BUGGY, BETA RELEASE)
Increased voltage on 600mhz and 1.3ghz steps (let me know how this affects stabilty, guys)
Implemented BLN (VERY EXPERIMENTAL AND BUGGY)
Added states table to Voltage Control app that doesn't actually do anything.
Added Atimn/eifert's fix for the bad block issue.
v4.1
Fixed the stability issue on 1300mhz (Big thanks to kang for his help)
Added in the cardock fixes from xcaliburinhand (grab the "DockSound Redirector" app from the market)
fixed the ?mv bug in voltage control
Fixed bln (thanks to neldar)
Added 1000hz version of the kernel
Did a few tweaks to smartass, it's still kinda sketchy though
Updated voodoo sound to v6
There's probably more, I just can't remember them.
v4.2
More stability tweaks on 1300mhz
-The voltage for 1300mhz is now the same as 1200mhz, so you won't be able to undervolt it as much in the app, but it seems to help with stability.
Latest bln from neldar (fixes the touchkey disabled bug, and the touchkey on during sleep bug)
Enabled the microphone presets for voodoo sound
v4.3
Added 1400, 1500, and 1600mhz steps
Updated voodoo sound v7 (very little feature changes though)
Unlocked FPS cap
Built on latest upstream code (pulls in all fixes in recovery, etc. If people are still having bad block issues, let me know)
v4.4
Disabled some debug code
Fixed the ?mv bug on 400, 200, and 100mhz steps in voltage control
Fixed up smartass
Integrated the sdcard r/w cache fix (Thanks to Existz for pointing it out)
v4.5
Upstream fixes:
-New wifi driver
-New kernel flashing method, which should help bad block people
-Dual sd card sharing
Added a time that a frequency must stay at before scaling up in smartass
- You can tweak it same way as you can tweak all the other settings, its ramp_up_rate_ns
v4.6
Upstream fixes:
- Lots of random JVB merges, code clean up, etc.
Fixed the notification bug crash on the first v4.6
v5.0[May 3]
- Extend battery polling to 15s
- Sched_autogroup patch (increases smoothness under heavy load)
- New bootlogo
- Fix setCPU crashing on screen off
-Unified HZ (256) (should increase battery life, and has no adverse effect on performance)
- Reunlock fps cap
-Switch to the Codesourcery toolchain (should result in faster/smoother code)
-Full compatibility with 2.3.4
v5.0b[May 4][First Vibrant supported/tested version]
-Fixed touchkeys for real this time
-Temporarily enabled debugging (will be disabled in the next update)
-Fixed the crazy battery stats
-Reenable smartass governor
v5.1[May 6]
-Lots of upstream gpio changes
-Camera drivers kanged from JVB (REQUIRE THE LATEST NIGHTLY TO WORK)
- -03 optimizations
- Switched to hardware based floating point calculations (seems to increase performace under certain loads)
- Dropped 1.6ghz to 1.55ghz
-set default governor to conservative
- New captivate/vibrant specific initramfs
v5.2[May 12]
-new(old) modem_ctl
-tvout stuff
-fsa switch sleep
-overvolting cap
v5.3[May 16]
-upstream initramfs/initial flash changes
-Upstream change to the way battery percentage is calculated
-Lots of little( irrelevant) upstream changes
-Actually fixed the kernel version.

NIGHTLIES/WHENEVERS
#0[May 27]
+Way too many to list. Big changes include an update to 2.6.35.13, voodoo sound v9, and a properly working ril.
#1[May 29]
+States table in voltage control kinda works now, but is herp derp.
+Disabled ext2
+Re added the 1.6Ghz step
+Upped 1.55ghz freq by a few mhz
#2[July 12]
+Up to date with everything
+GPU bus controllable via Control Freak
+Other stuff

TheEscapist said:
NOTE: I need testers, as I dont have a vibrant. There *shouldn't* be anything that breaks specifically on the vibrant, but still.
Click to expand...
Click to collapse
Miui?? Trying it neways thanks

nickmcminn60 said:
Miui?? Trying it neways thanks
Click to expand...
Click to collapse
Epic Fail! So this should work with miui tomorrow after the 2.3.4 update? Can you post a 2.3.3 version?

nickmcminn60 said:
Epic Fail! So this should work with miui tomorrow after the 2.3.4 update? Can you post a 2.3.3 version?
Click to expand...
Click to collapse
I dont have a 2.3.3 source tree right now, so no. As for miui, probably, but I'm not officially supporting miui.
Sent from my SGH-I897 using XDA Premium App

TheEscapist said:
I dont have a 2.3.3 source tree right now, so no. As for miui, probably, but I'm not officially supporting miui.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
No worries, ill just flash with miui tomorrow.

This kernel didnt boot it just went to the screen with the little computer
Went into recovery and flashed another kernel and it booted smoothly.
Sent from my SGH-T959 using XDA App

es7241 said:
This kernel didnt boot it just went to the screen with the little computer
Went into recovery and flashed another kernel and it booted smoothly.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
That's the custom boot screen. if the kernel didn't boot, you wouldn't have been able to get into recovery.
Sent from my SGH-I897 using XDA Premium App

i been running it for a day now
1.2 ghz smooth
1.3 ghz smooth
1.4 ghz starts to get choppy
1.5 ghz locks up reboots
1.6 un useable .
but its giving me good color, and operates pretty smooth at 1-1.3 ghz

brian(: said:
i been running it for a day now
1.2 ghz smooth
1.3 ghz smooth
1.4 ghz starts to get choppy
1.5 ghz locks up reboots
1.6 un useable .
but its giving me good color, and operates pretty smooth at 1-1.3 ghz
Click to expand...
Click to collapse
It sounds like you're unstable at the higher frequencies. Try playing with the voltages settings (I can't run 1.5 without undervolting), that might help.
Sent from my SGH-I897 using XDA Premium App

TheEscapist said:
It sounds like you're unstable at the higher frequencies. Try playing with the voltages settings (I can't run 1.5 without undervolting), that might help.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
what settings do you reccomend ?

brian(: said:
what settings do you reccomend ?
Click to expand...
Click to collapse
Its different for every phone. If you want something to start off with, there is lots of people who have posted theirs in my captivate thread, and there is also an overclocking/undervolting guide by shaolin in the captivate forums.
Sent from my SGH-I897 using XDA Premium App

TheEscapist said:
Its different for every phone. If you want something to start off with, there is lots of people who have posted theirs in my captivate thread, and there is also an overclocking/undervolting guide by shaolin in the captivate forums.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
ah, nonee seem to be working, i got 1.4 ghz to run tho, but im only getting 1744 in quadrant?

brian(: said:
ah, nonee seem to be working, i got 1.4 ghz to run tho, but im only getting 1744 in quadrant?
Click to expand...
Click to collapse
Because Quad scores are the be all and end all of a phone. (fyi: I pull anywhere from 1900 to 2600 at 1.55ghz).
If you're concerned, run linpack or some other cpu intensive task. If you keep getting an "Inaccurate" error in Linpack, you're probably unstable at that frequency, which could cause crashing, lag, slowness, etc.

Been running this for about 15 minutes and its running good so far, but one question how dangerous is this to the phone running at 1.5ghz as compared to 1.3ghz?
Sent from my SGH-T959 using XDA App

es7241 said:
Been running this for about 15 minutes and its running good so far, but one question how dangerous is this to the phone running at 1.5ghz as compared to 1.3ghz?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Any overclocking reduces the lifespan of a device, though typically from decades down to several years to a decade. Voltage wise, its a 100mv increase (though you can decrease it). It shouldn't be that much of a difference, and ive been at 1.5 for a while now, but obviously, there's always a chance.
Sent from my SGH-I897 using XDA Premium App

TheEscapist said:
Any overclocking reduces the lifespan of a device, though typically from decades down to several years to a decade. Voltage wise, its a 100mv increase (though you can decrease it). It shouldn't be that much of a difference, and ive been at 1.5 for a while now, but obviously, there's always a chance.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the quick reply, I have voltage for 1.5, 1.4, & 1.3ghz to -25 , and the rest stock , ill see how that goes because either way ill probably end up buying a new phone soon 8)
Sent from my SGH-T959 using XDA App

es7241 said:
Thanks for the quick reply, I have voltage for 1.5, 1.4, & 1.3ghz to -25 , and the rest stock , ill see how that goes because either way ill probably end up buying a new phone soon 8)
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Just watch you temp. Run it at 130f all the time it wont last a month.....just keep it cool.....

nickmcminn60 said:
Just watch you temp. Run it at 130f all the time it wont last a month.....just keep it cool.....
Click to expand...
Click to collapse
Not sure what that is in celcius (Canadian here), but under 45c is a good limit to aim for. Charging cuts off around there, not sure the exact value off the top of my head.
Sent from my SGH-I897 using XDA Premium App

Related

[APP][OC/UV/Governor][GPU OC][GB][21 June]Control Freak 0.5beta (NEW!!)

Control Freak, the OC/UV app for Gingerbread!
PLEASE READ THE FULL POST! !!
NEW RULE! Read the ENTIRE op, plus the last few pages BEFORE posting a question!! I don't mind sharing information and helping people, but answering the same question on every page is getting old!!
Control Freak is a re-write of xan's Voltage Control app, designed to work with Gingerbread based kernels. It has (most of) the features of my Voltage Control EX.
Beware!! This app is still in development! Any issues are being worked on, but it may not run perfectly!! Also, I, nor anyone who has helped to make this app or the kernels/roms it works with are responsible for any damages caused by use of this app or any kernels/roms supported by this app!!
Features:
Designed for use with JVx based Gingerbread kernels
Works with cm7 kernels that support OC/UV
Specifically designed around features present in existz's Talon kernel
Allows enable/disable specific states
Allows undervoltage control on a state-by-state basis
Allows limiting clock to a specific speed
Allows changing of governors
Allows control of Cpu Threshold settings - see note2 bellow.
States enabled info is found by opening each UV control.
TIS info is now shown on the main screen
TIS info for Deep Sleep
TIS percentages
Logs all major start up values as they are polled from the sysfs.
Logs all settings to be applied when Apply is selected
Logs all settings to be saved when Save As Boot is selected
Controls GPU Clock settings on compatible kernels!!
GPU O/C Capable Kernels for Captivate:
Talon 0.3.1 by eXistZ -Released to public
Le Kernel du Jour by TheEscapist - CM7, may be only available on private test versions, talk to TheEscapist for more info
Glitch Kernel by glitch - CM7, may be only available on test versions, talk to glitch for more info
Note: On Gingerbread, the conservative governor is NOT recommended! Interactive/ondemand/smartass governors are supported, and interactive is the preferred governor! Talon does not have smartass implemented yet, so smartass will not show up in the Governor dropdown on Talon.
Additional Note: As of Talon 0.2.1, interactive governor is NOT included anymore! Existz removed it in favor of the ondemand governor.
Note2: Cpu Threshold control is NOT supported on most Gingerbread kernels, since Cpu Threshold is used by conservative governor. I just added the Cpu Threshold settings, so that I can make this backwards compatible with FroYo kernels/roms.
NOTE 3:If you are experiencing issues with settings not sticking on reboot, go to the Market, download the busybox installer by stericson, and install busybox 1.17.1. Some roms, including Perception II, have a version of busybox 1.18.4 that does not have run-parts compiled into it. Without run-parts, nothing in /etc/init.d gets loaded at boot. The version of 1.17.1 included in stericson's busybox installer DOES have run-parts, so it will work.
Change log -
Control Freak 0.5b:
- Added GPU Overclocking controls! Please note that your kernel must support GPU Overclocking for this feature to work! Also note that this version has NOT been tested on kernels without GPU Overclocking, so if anyone has a kernel that does not have GPU Overclocking, test this out and let me know how it goes!!
- Fixed the states enabled command to remove the extra 0 at the end that was being added due to Deep Sleep info
Control Freak 0.4.2b:
- Fixed fc issue on kernels with higher number of states available
- Changed the icon, the new icon was designed by b_randon14
Control Freak 0.4.1b:
- Fixed save function, now the proper max frequency is written to S_volt_scheduler
- Added logging to save function
- Added logging to apply function
- Log is now cleared when it is exported, so the log starts from scratch after each export
Control Freak 0.4b:
- Added Deep Sleep TIS info.
- Added TIS percentages.
- Added logging
- NOTE: Logging DOES NOT use logcat, so there is no need to enable logcat to generate logs, or to view/export the logs.
Control Freak 0.3.5b:
- Fixed the Max Frequency issue where any changes to the Max Frequency dropdown were not being saved. Now it writes the proper value to the proper place.
- Fixed another issue with Max Frequency dropdown. If you applied a Max Frequency LESS THAN the highest state enabled, on closing and restarting CF, it would show the highest enabled state as the max frequency, regardless of current setting. Now, if you set limit to 1000MHz, it will show 1000MHz at launch, no matter how many states above that freq that are enabled.
- Fixed the SI unit prefix for frequency. Forgot that 'm' is for "milli" and 'M' is for "Mega." And I was even arrogant enough to tell someone that I was right!!! Anyway, it is fixed now. And a HUGE thank you to aalh for pointing out my mistake!
Control Freak 0.3b:
- Fixed the TIS info issue. Now each state shows it's own TIS, instead of the
the TIS for the first state.
- Moved the TIS info to the main screen, so that it is visible all the time.
Control Freak 0.2b:
- States info issue resolved
- Unsupported kernel issue resolved (Same underlying cause as the states info issue)
Control Freak 0.1b:
- Initial Release
Known Issues -
- Sometimes, gpu read out will disappear for some states at random. If you open the uv/gpu controls, it will show the read out again. Closing the controls may cause that state's readout to stay and cause other states to loose their displays at random. May have to do with a glitch in the code to hide gpu controls for non-gpu compatible kernels.
- Sometimes it will not pull states_enabled_table info. This causes the CPU Limit dropdown to be empty. As an interim solution, until I can track down why this is happening, either exit Control Freak and launch it again, or simply enable each state, and they will be added back to the dropdown.
- Occasionally will report an unsupported kernel. If you are sure your kernel IS supported, simply restart.
Sources available at https://github.com/shane87/ControlFreak
Report any issues by posting IN THIS THREAD or sending me a PM. But please, read through the thread, and check the known issues section of this post before posting an issue. If your issue is listed, quote the original issue report, and add details about your system and set up. "Me too!" comments are not helpful and will be ignored.
Issues may also be reported by sending an email to [email protected] If you use this method to report bugs/issues, please export the log from Control Freak and attach it to the email. To export Control Freak's log, launch Control Freak, press Menu > Export log. The log will be exported to /sdcard/cf.log. Please attach this file to any emails addressed to me using the above link.
NOTE: I removed CF 0.3b due to the number of bugs in that software. Granted, all of them were fairly minor bugs, and primarily affected the UI, other than the Max CPU Limit issue. But with that issue, on top of the inability to enable/disable a state since you couldnt see the checkboxes, ther wasnt a whole lot you could do with 0.3b. Anyway, 0.3.5b takes care of those problems.
I removed CF 0.4b due to the Save errors, 0.4.1b has the same functionality, and it works right!
A HUGE thank you and shoutout to b_randon14 for designing the new icon!
Keep up the good work!!
If anyone has a Samsung Intercept, or knows anyone with a Samsung Intercept, check out bROM over at sdx, a deodexed, rooted rom designed by my brother, b_randon14!
Anyone interested in contributing, drop me an email at [email protected], and I will get you added as a contributor on github!
Reserved +++
I know its still in development but with JVH out and existz already working on a JVH talon build (continuum rom has it for now), you might have to implement that too.
grkmaster said:
I know its still in development but with JVH out and existz already working on a JVH talon build (continuum rom has it for now), you might have to implement that too.
Click to expand...
Click to collapse
Yeah, I am aware of JVH, and I plan on adding JVH compatibility as soon as existz's begins to release JVH-based kernels. Actually, as long as the sysfs is still implemented the same way, there SHOULDN'T be any issues. Of course, I thought the same thing about going from FroYo to to Gingerbread, and it wasn't quite that easy. But compared to the full re-write, which has taken almost three weeks, going from JVB to JVH shouldn't be as bad.
Anyone interested in looking at the sources on github, I have committed fix that prevents the app from fc'ing at launch. As it turns out, calling the inflater function to inflate a view does NOT save that view unless you specifically tell it to! Seriously though, it was a simple issue of forgetting to add a word or two of code. It is amazing how one messed up variable, or even a missing period, can complete crash an app. Now, just to get the layout setup so that everything is visible and positioned correctly.
Hopefully, I will have a running release ready by the end of the day.
P.S. If you intend to DIVIDE by 1000, and you accidentally put SUBTRACT 1000, Java/Android won't tell you that you are an idiot. It will just cause the app to crash, lol.
Release
Control Freak is live!!
Please read the OP, especially the known issues section.
Using this app right now! Let's see how it goes! Im accutally excited cause I don't really like setcpu or voltage control
Sent from my GT-I9000 using XDA App
will this app also work with cm7 gb or just the i9000 ones
superj3211 said:
will this app also work with cm7 gb or just the i9000 ones
Click to expand...
Click to collapse
I do not know. I don't have cm7 installed, and have not tested it against cm7. If cm7 implements oc/uv in the sysfs like Talon does, it SHOULD work, but again, no guarantees.
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101
Anyone interested in designing a new icon for Control Freak? I have zero graphics design abilities, and would seriously appreciate if someone could design a nice icon. I will give a bounty of $5 US to the best design!!!
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101
Cool. Something new to play with.
sent from my cappy rocking gingerbread (CM7)
shane87 said:
Anyone interested in designing a new icon for Control Freak? I have zero graphics design abilities, and would seriously appreciate if someone could design a nice icon. I will give a bounty of $5 US to the best design!!!
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101
Click to expand...
Click to collapse
If i had any design ability Id help out but just like you they suck lol ..
Hope someone helps out since there is plenty of great graphic designers aroud here
Control Freak does not seem to pull up the states table at all under TalonDEV 0.1.7-JVH-Test_11 for Continuum, but Voltage Control EX does it most of the time.
Sent from my GT-I9100 using XDA App
rajendra82 said:
Control Freak does not seem to pull up the states table at all under TalonDEV 0.1.7-JVH-Test_11 for Continuum, but Voltage Control EX does it most of the time.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Read the OP. Control Freak does not use the States tab. If you press on the state, like you are going to change uv settings, it will show the enable/disable checkbox and the tis info.
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101
shane87 said:
Read the OP. Control Freak does not use the States tab. If you press on the state, like you are going to change uv settings, it will show the enable/disable checkbox and the tis info.
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101
Click to expand...
Click to collapse
Sorry. I missed that at first.
shane87 said:
Read the OP. Control Freak does not use the States tab. If you press on the state, like you are going to change uv settings, it will show the enable/disable checkbox and the tis info.
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101
Click to expand...
Click to collapse
I think its a great alternative way and possibly keep it that way. State tab shuoldnt be that big oa deal if we have a option like that to enable and disable a checkbox under the states
I like the states enable/disable being in there with the UV setting, but I miss being able to see tis all in one place without having to scroll. Maybe the tis could be put on the line where the mV. Is displayed? I don't much miss the tis % but I can see that's not included and it is slightly handy.
More importantly than appearance I've noticed that all states show the same time for tis. Using cpuspy I see the real results. Also I'm still having issues sometimes where opening the app no states are selected and the Max clock is empty until I check at least one state. I also sometimes have blanks for scheduler and governor.
The new voltage control lite does not seem to suffer these issues, however I have noticed an inconsistency across the board about being able to save boot settings (sometimes works,sometimes not). And yes my init.d folder is chmodded correctly.
Rom continuum 5.4.1
Kernel talon 0.1.7
iXNyNe said:
I like the states enable/disable being in there with the UV setting, but I miss being able to see tis all in one place without having to scroll. Maybe the tis could be put on the line where the mV. Is displayed? I don't much miss the tis % but I can see that's not included and it is slightly handy.
More importantly than appearance I've noticed that all states show the same time for tis. Using cpuspy I see the real results. Also I'm still having issues sometimes where opening the app no states are selected and the Max clock is empty until I check at least one state. I also sometimes have blanks for scheduler and governor.
The new voltage control lite does not seem to suffer these issues, however I have noticed an inconsistency across the board about being able to save boot settings (sometimes works,sometimes not). And yes my init.d folder is chmodded correctly.
Rom continuum 5.4.1
Kernel talon 0.1.7
Click to expand...
Click to collapse
Yeah, I am planning on adding tis info, plus an indicator for enabled/disabled status on the line with the uv, so you can see everything in one glance.
I knew that the states info still isn't getting pulled right sometimes. You said vc lite has that issue fixed? Do you know if vc lite has sources available, so I can see how it got fixed?
I didn't know that the tis was messed up. I'll take a look at it tomorrow and see if I can track it down.
And for future reference, please report issues by clicking the link in the op. I check this thread often, but I check my issue tracker on github more often, usually, lol.
Also, I am working on adding governor specific tweaks, that will be displayed in a sliding drawer like vcex's states tab.
And an enormous thanks to all who use this app and give me feedback!!
Sent from my Samsung Captivate using XDA App.
ROM: Cognition v4.3
Kernel: Onix 2.0.4, Voodoo Sound v7, Voodoo Color, lagfix
Modem: I9000 tljl3
HW Build Number: 1101
AHA
Here you are
subscribed
I will start playing with CF now
And I will think about an icon
(I did the one for Moneydance a few years back, a Linux personal Finance app))
Question
Interactive, just sits at 1.2, unlike whatever VCEX did which made it scale (or hop, depending on semantics)

[Kernel][CM7/MIUI/OMFGB] Bali-CM 2.2.2 [10/18/2011]

Introducing the new variant of Bali kernel, Bali for CM7. The main goal of this kernel is the same as other Bali kernel, balanced performance and battery life. I can't guaranteed you will get the same battery life as Bali for Froyo but you will definitely get an improve battery life over stock kernel.
Features:
- OC/UV up to 1.4GHz (Safe boot to 1GHz) [require setCPU from market]
- Voodoo Sound v10
- Voodoo Color
- Multiple CPU governor, smartass included (default: ondemand)
- Multiple IO scheduler (default: BFQ)
- LED notification support (no external app required)
- CIFS support
- Support SetCPU screen off 100/400 profile
- Dock sound redirector support [need Galaxy Dock Sound Redirector app from market]
Disclaimer:
As always, I'm not responsible with any damage cause to your phone.
Special Thanks:
- Team Whiskey - you guys are awesome.
- Alexia - for great work on the new splash image.
- Supercurio - for awesome work on Voodoo
- xcaliburinhand - for wonderful work on dock sound redirector.
- Everybody at CM dev community for their hard work on this awesome ROM.
- Everybody at #teamwhiskey for beta testing this kernel and their support.
I apologize if I miss anyone ..
Flashing Instruction:
- If you're coming from another kernel, flash "Ultimate Kernel Cleaning Script" by lippol94 first (http://www.multiupload.com/XFH1GCK4MB)
- Once that's done .. then flash Bali-CM
If you don't know how to flash then this is not for you.
Download:
Bali-CM_v2.2.2
Change Log:
Code:
- 2.2.2 [10/18/2011]
CM update
Re-enabled LED by default
- 2.2.1 [9/12/2011]
Fixed screen jitter issue
- 2.2 [9/10/2011]
Upgraded BFQ to v2
Added Smartass v2 with extra tweak
Fixed ondemand and tweaked for smoother experience
Set ondemand as default governor
Other fixes and tweaks
- 2.1 [9/1/2011]
Disabled SLQB and revert back to SLUB
Disabled LED notification for the time being
Added more UV settings
GPU tweaks
Added v(r) scheduler
Added Tiny Preempt RCU
And other tweaks and fixes
- 2.0 [8/25/2011]
Disabled ramzswap and switched to zram
Enabled zcache for better IO performance
Memory tweak, now gives you 340MB
More tweaks
- 1.2.1 [8/19/2011]
Fixed video playback issue
Fixed battery report when charging, it goes to 100% now
- 1.2 [8/18/2011]
Updated source with the latest CM patches
Added SLQB slab allocator for better memory management
Added more tweaks
- 1.1.1 [7/26/2011]
Fixed kernel instability that cause random reboot
- 1.1 [7/26/2011]
Added Voodoo color V2
Fixed UV portion to make it easier to manage
Added Voltage Control support
Added compiler tweak
- 1.0 [7/22/2011]
Initial release
A little explanation on different governors (taken from Lord ClockAn thread):
- interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
- smartass - Is an improved version of interactive governor
- ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
- conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
- performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
- powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
- userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Q and A:
My screen has green, yellow, or orange tint.
Use Voodoo Control to set color profiles (courtesy of d_phekt)
Screen RGB Multipliers:
Red = 230996000
Green = 230996000
Blue = 2704668800
Screen v1 Gamma Hack:
Red = -50
Green = -53
Blue = -44
is GPS still functional with this kernel?
gamikzone said:
is GPS still functional with this kernel?
Click to expand...
Click to collapse
Yes .. GPS still functional.
drhonk said:
Yes .. GPS still functional.
Click to expand...
Click to collapse
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
gamikzone said:
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
Click to expand...
Click to collapse
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
drhonk said:
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
Click to expand...
Click to collapse
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
gamikzone said:
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
Click to expand...
Click to collapse
Try smartass with this kernel ..
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
i think i will try this out tonight
I believe this will be ok to use with miui.
Nice animation.
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
jay661972 said:
I believe this will be ok to use with miui.
Nice animation.
Click to expand...
Click to collapse
Trying it out , any recommeneded UV settings?
Sent from my T959 using XDA App
jay661972 said:
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
It does work on miui,
Sent from my T959 using XDA App
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
would downloading SetCPU and just setting the governor to smartass improve battery life? or do you have to actually UV and all that
Really, how did you do that? I did the clean script first and flash Bali.
es7241 said:
It does work on miui,
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Okay I will try this one more time.
jay661972 said:
Okay I will try this one more time.
Click to expand...
Click to collapse
confirmed .. it works on MIUI since I just flashed MIUI with it.
jay661972 said:
after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
Same here except im flashing from trigger redux #12 and ive tried flashing from trig w/glitch and w/du jour
Sent from a cell tower to the XDA server to you.
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
drhonk said:
confirmed .. it works on MIUI since I just flashed MIUI with it.
Click to expand...
Click to collapse
jay661972 said:
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
Click to expand...
Click to collapse
So you can't flash bali on miui energy? You have to revert to stock miui?
Sent from my T959 using XDA Premium App

[KERNEL][04 APR] GLaDOS V2.11

Aperture Laboratories presents​
GLaDOS V2.11​
The latest innovation in human-smartphone interaction. Our scientist have shown in extensive tests that humans operating our kernel on their devices experience 67% more joy in life while simultaneously the likelihood of being maimed or killed by falling space debris is significantly reduced. Also preliminary human trials indicate that it might offer some protection against lethal dosages of gamma radiation and blows to the head with a rod-like object.
Features:
Based on stock Android kernel 3.0.8 IMM76D
CPUfreq governor 'lazy'
Live OC version 1
Custom Voltage version 1
Battery Life eXtender (BLX) version 1
Power saving state DEEP IDLE version 2
Touch Wake version 1
Backlight Dimmer (BLD) version 3
Backlight Notification (BLN) version 9
Brain **** Scheduler (BFS) version 0.357
SLQB memory allocator
Voodoo Color version 2
Voodoo Sound version 10
CIFS
TUN
Bigmem (+20 MB more available RAM)
USB OTG build 5
Download:
http://goo-inside.me/devs/aperture/GLaDOS-NexusS (thanks to goo-inside.me for hosting)
Always make a backup of your /efs/ directory (http://forum.xda-developers.com/showthread.php?t=1138873) before installing custom kernels or ROMs.
During installation the cache partition, Dalvik-cache and modules, init.d scripts and bootsounds from previously installed kernels are cleaned.
Source code:
https://github.com/Ezekeel/GLaDOS-nexus-s/tree/glados
Do not use profiles, they are unnecessary and only lead to instabilities.
If you experience any problems and are on a nightly or kanged ROM, try the latest stable version of that ROM first. I will not give support or answer any questions if you do not try this before reporting a problem with the kernel.
If you experience stability problems like reboots, freezes, FCs and SoDs and you did OC or UV, first try changing back to the stock settings. If this solves the problems, your OC/UV configuration is not stable. There are some indications that OC/UV settings which run fine at high battery charges might still cause problems at lower battery charges. So to be safe always check that your OC/UV configuration runs fine at low battery like 5%.
I do not offer support/help/recommendations on OC/UV. If you decide to do so and your device is unstable you are on your own. Check http://forum.xda-developers.com/showthread.php?t=1335429 for help.
If you experience the problem that the DEEP IDLE state is not properly used (according to the idle_stats), read the last section of http://forum.xda-developers.com/showpost.php?p=18299324&postcount=1.
When reporting a bug always include information about your ROM and hardware model. Also be as precise as possible when describing the problem. Just because a single person is experiencing a problem, it does not mean there actually is a problem with the kernel. I always wait until at least one other person can confirm the issue before I look into it. So if you see someone posting a bug report, do not be shy and feel free to confirm the issue or if you do not have the problem let me know that too.
When asking for a feature you would like to see implemented in GLaDOS always provide a link with information about this tweak and preferably also a link to the source code.
Aperture bootanimation courtesy of rascarlo (www.twitter.com/rascarlo)
For users unfamiliar with init.d scripts I recommend NSTools by arifhn (http://forum.xda-developers.com/showthread.php?t=1333696) for managing the various tweaks.
Changelog
GLaDOS-V2.11
Added kernel patches for Android 4.0.4 update.
Fixed bug with Touch Wake.
The kernel installer no longer modifies the ramdisk for adding init.d support.
GLaDOS-V2.10
Added USB OTG build 5 by sztupy.
Fixed small bug in Custom Voltage.
Fixed bug in Live OC.
Changed to new bootanimation by Rascarlo (many thanks!).
Changed default V1 gamma values for Voodoo Color to stock settings.
GLaDOS-V2.9
Fixed two small bugs in LiveOC.
Fixed small bug in Lazy.
Reduced display frequency back to stock settings.
GLaDOS-V2.8
Fixed a bug in LiveOC.
Fixed optimized compiler flags.
GLaDOS-V2.7
Fixed TouchWake issue of long powerkey presses causing the touch controls to be disabled without delay on next screen off.
For BLN the blink interval and blink time can now be adjusted in the sysfs interface. Also BLN is disabled by default.
For lazy the sampling rate is initialized to a default of 15000.
GLaDOS-V2.6
Fixed the problem of the CAM module being active all the time preventing DEEP IDLE from being used.
GLaDOS-V2.5
Fixed bug.
Removed several unnecessary kernel drivers and features.
Removed kernel debug and logging features.
Included logger as a module.
GLaDOS-V2.4
Fixed bugs in Live OC.
GLaDOS-V2.3
Fixed the freeze/reboot problems when changing the frequency limits.
GLaDOS-V2.2
Removed the limit of the minimum frequency to 200 when the GPU is active.
Preliminary bandaid to DEEP IDLE compensating for various bugs in ROMs.
GLaDOS-V2.1
Added Voodoo Color version 2 and Voodoo Sound version 10.
GLaDOS-V2.0
Update to Android kernel 3.0.8 for ICS 4.0.3 IML74K.
GLaDOS-V1.12
Fixed the camera problems caused by Bigmem (increases available RAM by 21MB now).
GLaDOS-V1.11
Added Bigmem option (increases RAM available for the system by 26MB).
GLaDOS-V1.10
Added DRAM scaling to Live OC.
Flash memory I/O tweaks.
Added Tiny Preemptive RCU.
Updated the optimized CRC32 algorithm.
Removed CFQ I/O scheduler.
GLaDOS-V1.9
Added OC frequency states 1.4GHz and 1.2GHz.
GLaDOS-V1.8
Fixed the problem of the touchkey backlight lighting up when touched while the screen is off.
Increased display frequency to 72Hz necessary to achieve 65fps.
GLaDOS-V1.7
Fixed the increased battery drain while in SLEEP when DEEP IDLE is enabled.
Fixed the problem on the NS4G of DEEP IDLE not being used while 4G is enabled.
GLaDOS-V1.6
Disabled most logging and debugging kernel config options.
Included logger and TUN as modules.
During installation the cache partition, Dalvik-cache and modules, init.d scripts and bootsounds from previously installed kernels are cleaned.
Removed '98touchscreen' init.d script.
Aperture bootanimation and -sound courtesy of Euphorie (http://forum.xda-developers.com/showthread.php?t=1061627).
GLaDOS-V1.5
Fixed problems with setting voltages and min/max frequency with SetCPU.
Fixed problems with the vibrator and DEEP IDLE.
Improved stability of wireless connection.
GLaDOS-V1.4
Updated to latest toolchain arm-2011.03-41
Optimized compiler flags
Added optimized RWSEM
Fixed BLD bug for i9023 of the touchkey backlights not getting re-activated on touch
Changed to advanced TCP congestion scheduler VENO
GLaDOS-V1.3
Improvements to JHash.
Improvements to CRC32.
Fix memory leak in CPUfreq stats module.
Removed PMEM. I do see any improvement regarding the available RAM, but removing unused code is never a bad idea.
GLaDOS-V1.2
Fixed 'Screen v1 gamma hack' not working for Voodoo Color.
GLaDOS-V1.1
Fixed BLN problems for i9023.
GLaDOS-V1.0
Initial release.
Oh this is going to be good.
...Thanks E
Sent from my Nexus S 4G using xda premium
oh man... downloading now
thank you so much for providing this!
Stock android uses deadline scheduler or VR?
A bit off topic, but did anyone ever toy with SIO, NOOP and CFQ on Nexus S?
Wow
Testing right know
can i flash this on my rooted stock 2.3.6? that is the latest for my country.
Ezekeel's own kernel?
Ezekeel's own kernel?!
I knew you have only provided kernel devs with MODs.
Very tempting... Will leave it a few releases before I jump from Matr1x but expecting this to be very good!
I'd be interested in seeing what people's battery life is like on this kernel compared to others, as that's the main selling point for me!
just ran a quadrant benchmark, ~1000 point increase from franco's 06 kernel on carbon c02 rom with 110 liveoc
i'm try ...
v3rk said:
just ran a quadrant benchmark, ~1000 point increase from franco's 06 kernel on carbon c02 rom with 110 liveoc
Click to expand...
Click to collapse
so its better than franco's? and does it include the latest deep idle fiX?
Finally a kernel of a master hehe
Sent from my Nexus S using xda premium
Oh em gee. Here we go!
Sent from my -=Nexus MV=- powered Nexus S c",)
--
MarkVis
After flashing no more lights in soft keys
Edit:
Solved
thegtfusion said:
so its better than franco's? and does it include the latest deep idle fiX?
Click to expand...
Click to collapse
lol
read up who made deepidle-fix. and all those other kernel-tweaks. this kernel comes from the horse's mouth so to speak, or how this is said in English.
now let's see if it's stable.
Yusei said:
After flashing no more lights in soft keys
Click to expand...
Click to collapse
Use bln app to see if it's enable.
MarkVis said:
Oh em gee. Here we go!
Sent from my -=Nexus MV=- powered Nexus S c",)
--
MarkVis
Click to expand...
Click to collapse
If i am in you, I'd have chose which kernel to include in next nexus mv release
Inviato dal mio Nexus S
report: Oh yeah this is awesome syrup, my phone loves it.
Edit : everything good on this side.
Sent from my Kush'd Google Nexus S 4G using xda premium
Ezekeel, can you put this kernel taking around 65fps in 3D graphics globe?
Btw, this rocks.

[Q&A][FAQ] HoliRaider by Bananacakes

Thread Updated: February 24th, 2012​Rom Name: HoliRaider
Developer: bananacakes
Version: 1.6 / 1.6-4G
Last Update: February 23th, 2012
Features:
Based on SKT KR 2.31.911.2 LTE
Rooted
Ultra Smooth Rosie (thanks to hamdir)
the latest Beats Audio(Thanks to RcmixTeam) & cyanogen-dsp manager
A ton of languages included
Completely De-odexed
EXT4 Optimization Complete
5X5 app drawer
XLOUD engine Powered by Sony Corporation
Advanced Power Menu
some Imported Sensation Xl audio driver
Amaze Camera V8 fully working With 3.5 Stock gallery(thanks to CdTDroiD & Baadnewz)
Imported Full Bravia engine(lib, etc, framework)
Advance Powermenu
Improved Adreno220 configuration for better quality and performance
Added Bliss Default Videoplayer
Tweaks for a smooth, faster and better performance
Improved mms(Secure sms and block list, trashcan, backup & restore, enable in sms setting)
Improved Audio(Extremely enhanced sound for Delight your music)
Improved auto-brightness values
Fixed key backlight Issue
Imported paintdriver from Bliss
Full bash shell with nano
Fixed Native Screen capture
Extended quicksettings added (flashlight, hot reboot, wireless adb)
Added BatteryBar Settings (Thanks to pvyParts)
Remove unnecessary apk
Tweak DB & more (from Warm ROMS)
And more.. more tweak for a smooth..
Updates:
v1.7
SUPER FAST & BETTER PERFORMANCE
Disabled MMS Compression
Enabled 3D Home screens with toggle in display settings
Added Drop clean caches
Tweak Threshold
Tweak Render UI with GPU
Attempting to stabilizing
More Smooth & intuitive response
Tethering hopefully fixed
Disabled Scrolling Cache (Smooter UI)
Modified Beats audio
Vdd Cpu set (For stabilizing )
echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
Net debugging hopefully fixed
Updated some drivers
heat & bootloop & battery drain hopefully fixed
And more..
Click to expand...
Click to collapse
**Notice***
I am a full time employee & student. If something is urgent please PM me and I will add it. Otherwise I will try to update this thread weekly.
Frequently Asked Questions
Q: Highest phone can be overclocked too?
A: 1.5ghz or 1.7ghz depending on your kernel. Use SetCPU to control the ranges and profiles.
Q: How do I use SetCPU?
A: First off no two phones perform exactly the same. Trust me.
Thanks DavidCampbell
The profiles I use are below in order of priority
1. Screen off 192 Max 192 Min
2. temp (greater than) > 44.9 C 864Max 192Min (important one)
3. Battery < 30% 756max 192 min
4. Battery < 60% 972max 192min
I have an extended battery and 30% and 60% are actually more like 10% and 5% its just the phone doesnt read the battery properly.
I leave the main slider at 1188000 and set on boot
oh and I use on demand for all of the options except the 30% on and the screen off one which I use powersave
Click to expand...
Click to collapse
Q: My phone doesn't wake up while sleeping when I get a phone call.
A: Flash the CRT Patch here
**placeholder**​
What's the fastest this can be overclocked to?
bangorang said:
What's the fastest this can be overclocked to?
Click to expand...
Click to collapse
some older kernals went all the way up to 1.8 but currently the two kernals are 1.7 or 1.5 ghz on this specific rom as of the 15th
bigballa said:
some older kernals went all the way up to 1.8 but currently the two kernals are 1.7 or 1.5 ghz on this specific rom as of the 15th
Click to expand...
Click to collapse
Which kernel goes up to 1.7? I flashed the one he made a thread for but it went to 1566000... or is that equivalent to 1.7? I though that was 1.5.
bangorang said:
Which kernel goes up to 1.7? I flashed the one he made a thread for but it went to 1566000... or is that equivalent to 1.7? I though that was 1.5.
Click to expand...
Click to collapse
I think those with native 1.2 are allowed up to 1.56, and those with native 1.5 has the higher limit with the kernel. Keep in mind QC only had to make sure the processor runs at 1.2 for the Vivid and not 1.5, so even though the APQ8060 is rated up to 1.5, there is no guarantee that the Vivid will run PERFECTLY at 1.5 or beyond.
I reflashed and am now able to overclock at 1.7. I used the kernel from his kernel thread. Thanks!
Sent from my HTC Raider X710e using XDA App
dizzyraider said:
I think those with native 1.2 are allowed up to 1.56, and those with native 1.5 has the higher limit with the kernel. Keep in mind QC only had to make sure the processor runs at 1.2 for the Vivid and not 1.5, so even though the APQ8060 is rated up to 1.5, there is no guarantee that the Vivid will run PERFECTLY at 1.5 or beyond.
Click to expand...
Click to collapse
This isn't logical. The only reason HTC vivid is at 1.2 is because att likely wanted it underclocked so that the skyrocket would be showcased with higher specs. The true stock clock is 1.5. Hence oc to 1.7 to 1.8 would cause no more potential damage to it than if it were the velocity which are the exact same phone.
Sent from my HTC Raider X710e using xda premium
Thankfully mine is stock at 1.5... I suggest to those overclocking you use setcpu and set profiles to force the phone to underclock at certain temperatures, this has saved my phones in the past, I've never blown a cpu.
I beleive the vivid and raider are at 1.2 to give better battery saving. I run mine at 1.18 most of the time anyway.
davidcampbell said:
Thankfully mine is stock at 1.5... I suggest to those overclocking you use setcpu and set profiles to force the phone to underclock at certain temperatures, this has saved my phones in the past, I've never blown a cpu.
I beleive the vivid and raider are at 1.2 to give better battery saving. I run mine at 1.18 most of the time anyway.
Click to expand...
Click to collapse
What CPU settings on each profile? That should definitely be a FAQ. I have setCPU and I just use inteldemand with the min at its lowest and max at the highest of 1.7
Sent from my HTC Raider X710e using XDA App
bangorang said:
What CPU settings on each profile? That should definitely be a FAQ. I have setCPU and I just use inteldemand with the min at its lowest and max at the highest of 1.7
Sent from my HTC Raider X710e using XDA App
Click to expand...
Click to collapse
If i see some good profiles written out anywhere ill add them to the FAQ if not then ill go ahead and create a base template to how i use it.
bigballa said:
If i see some good profiles written out anywhere ill add them to the FAQ if not then ill go ahead and create a base template to how i use it.
Click to expand...
Click to collapse
Ok thank you so much, I just don't wanna brick my phone for not knowing how to set my setcpu
Sent from my HTC Raider X710e using XDA App
---------- Post added at 11:28 AM ---------- Previous post was at 11:27 AM ----------
A little something you can put in this thread (just trying to help you out since you already have work and school on your hands haha).
If you have AT&T, download This and this kernel View attachment 02_15_2_flash_boot.rar. Remember to also flash the Kernel a second time after you flashed the ROM.
If you want your LTE symbol, flash the View attachment 1.6a_stabilizing_patch.zip after you've flashed your kernel for the second time
Q: How do I get my Wifi and tethering back?
A: Chances are, you only flashed the Kernel once (right before you flashed the ROM). Reflash it after the ROM is installed and it should be fixed.
The profiles I use are below in order of priority
1. Screen off 192 Max 192 Min
2. temp (greater than) > 44.9 C 864Max 192Min (important one)
3. Battery < 30% 756max 192 min
4. Battery < 60% 972max 192min
I have an extended battery and 30% and 60% are actually more like 10% and 5% its just the phone doesnt read the battery properly.
I leave the main slider at 1188000 and set on boot
oh and I use on demand for all of the options except the 30% on and the screen off one which I use powersave
Text message issue - only 80 characters per 1 text?
I flashed my Raider already over 50 times. Tested many ROMs.
I've noticed that only Holiraider by Bananacakes (all versions) has only 80 characters per 1 txt message even when Support special accent characters is OFF.
Factory ROM or any other ROM from different Developer has all the time 160 per 1 text (as it supposed to be).
Anyone knows how to get 160 characters per 1 text msg on Holiraider by Bananacakes ?
Any fix for this issue would make this ROM completly perfect
I'm sticking with HoliRaider ROM because has integrated Beats and Amaze Camera which those features are awesome and everything else works perfectly
davidcampbell said:
The profiles I use are below in order of priority
1. Screen off 192 Max 192 Min
2. temp (greater than) > 44.9 C 864Max 192Min (important one)
3. Battery < 30% 756max 192 min
4. Battery < 60% 972max 192min
I have an extended battery and 30% and 60% are actually more like 10% and 5% its just the phone doesnt read the battery properly.
I leave the main slider at 1188000 and set on boot
oh and I use on demand for all of the options except the 30% on and the screen off one which I use powersave
Click to expand...
Click to collapse
I know both HoliRaider as well as the WCX Rom has a native script that sets the cpu governor and clock speed on boot, it is recommended that you delete this if you want to run SetCPU or utilities as such. Without deleting the script, the settings might not stick as there could be conflict.
The file that should be deleted is /system/etc/init.d/15-screenstate_scaling
or
you could open the file with any text editor and change the setting according to your need
xavier_largeaux said:
I flashed my Raider already over 50 times. Tested many ROMs.
I've noticed that only Holiraider by Bananacakes (all versions) has only 80 characters per 1 txt message even when Support special accent characters is OFF.
Factory ROM or any other ROM from different Developer has all the time 160 per 1 text (as it supposed to be).
Anyone knows how to get 160 characters per 1 text msg on Holiraider by Bananacakes ?
Any fix for this issue would make this ROM completly perfect
I'm sticking with HoliRaider ROM because has integrated Beats and Amaze Camera which those features are awesome and everything else works perfectly
Click to expand...
Click to collapse
I'm not having this problem on stock SMS or even using GoSmsPro
I'm on 1.7 now.
cifs module?
Is there a CIFS module compatible with this kernel/ROM at the moment?
Since bananacakes would probably already include it, I'm guessing there's no cifs module at the moment. But, I just thought I'd check to be sure.
Thanks again!
need a mirror site for 1.7 depositfiles is down -_-
jh64dsb877r said:
Is there a CIFS module compatible with this kernel/ROM at the moment?
Since bananacakes would probably already include it, I'm guessing there's no cifs module at the moment. But, I just thought I'd check to be sure.
Thanks again!
Click to expand...
Click to collapse
not that i know of or see throughout the thread.

[KERNEL][3.10.71][KCAL] Velocity v1.1

*** Disclaimer
I am not responsible for any kind of damage to your device,
or in case it explodes, your surroundings.
Please use it at your own risk!
Click to expand...
Click to collapse
Features :
-O3, Cortex-A53, NEON, VFPv4 optimizations
Compiled from latest Linaro GCC 4.9.3 2015.02 Toolchain [Christopher83]
Upstreamed to 3.10.71 from kernel.org, from 3.10.28
Asynchronous Fsync ported from HTC Devices
Dynamic Fsync v2.0 [faux123/varunchitre15]
PowerSuspend v1.7 driver support (replaces EarlySuspend) [yank555.lu & faux123]
Android early_suspend/late_resume PM kernel driver framework has been
deprecated by Google. This new powersuspend PM kernel driver is a replacement
for it.
Conserves battery much better.
Triggered by Screen on/off.
Intelli_plug v3.9 driver [faux123]
Intelligent hotplug cpu driver with eco mode.
KCAL - Advanced color control
Disabled MMC CRC check for extra 30% boost in IO
Reduced debugging = More performance
Simple GPU Algorithm [faux123]
FIOPS, BFQ + stock I/O Schedulers
Filesystems support : NTFS, F2FS
Sysfs implementation for changing vibrator intensity [varunchitre15]
Zswap, Frontswap and znswap [faux123]
Support for kernel-mode NEON [faux123]
Increased charging current to 1.2A
Frandom - Fast Kernel Random Number Generator driver added
Added ARM NEON Crypto functions
Click to expand...
Click to collapse
Download :
Velocity v1.1 <- Mirror
Velocity v1.0 <- Mirror
Camera Fix
Changelog :
v1.1
- Added KCAL - Advanced color control (Thanks to @savoca for his great job) check this thread for more info
- Numerous fixes from android kernel_common 3.10 and 3.10.y repos.
- Enabled Conservative governor
v1.0
- Initial release
Installation :
1. Download and save the latest zip to your phone
2. Flash this zip from any custom recovery (eg. TWRP, CWM, Philz)
3. If camera doesn't work, perform steps 1 & 2 for the zip containing camera fix
Recommended Settings :
Min. CPU freq. : 400MHz (Under this might cause SOD)
GPU Governor : simple_ondemand
I/O Scheduler : FIOPS
Read-ahead size : 1536 kB
Intelliplug profiles :
* For general use : Eco Performance/Eco Conservative
* For gaming : Balanced/Disabled
Kernel apps : FauxClock, Kernel Adiutor, Trickster MOD
Credits :
@varun.chitre15
@faux123
@Christopher83
XDA:DevDB Information
Velocity Kernel, Kernel for the YU Yureka
Contributors
neomanu
Source Code: https://github.com/neomanu/android_kernel_yu_msm8916/tree/cm-11.0_exp
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v1.1
Stable Release Date: 2015-03-11
Created 2015-03-07
Last Updated 2015-03-11
Reserved
ooo new kernel...
hello bro first of all thanks for contributions towards Development of yu yureka..
Now downloading...
FEEDBACK AFTER SOME HOURS OF PLAYING....
Hey, can I flash it directly on other custom kernel
screen shots??
ankurvvvv said:
screen shots??
Click to expand...
Click to collapse
Its a kernel not a rom. What do you need screenshots of?
My bad. too excited with my new Yureka that not paying attention to anything
flashed this kernel and used it for 5 hrs.
Good BATTERY command.
i attended a con-call for 90 plus minutes and battery drained only 5%
No lag while using basic games like clash of clan or clash of lords
Issues identified
screen black out while on call, you cant control your calls like add new call or check text while you are on phone calls. but no issue in voice and reception.
while making call you cant drop call as screen goes black out.
No heating issue as far i observed.
colour reproduction is good.
seems need little fine tune can make this kernel a must install.
All the very best to develops
Regards
question
MIUI custom ROM supported???
sunilnair007 said:
flashed this kernel and used it for 5 hrs.
Good BATTERY command.
i attended a con-call for 90 plus minutes and battery drained only 5%
No lag while using basic games like clash of clan or clash of lords
Issues identified
screen black out while on call, you cant control your calls like add new call or check text while you are on phone calls. but no issue in voice and reception.
while making call you cant drop call as screen goes black out.
No heating issue as far i observed.
colour reproduction is good.
seems need little fine tune can make this kernel a must install.
All the very best to develops
Regards
Click to expand...
Click to collapse
you are talking about proximity sensor issue , is it right?
Sent from my AO5510 using XDA Free mobile app
Review after using a whole day.
1. First & best intelli_plug driver - loved the live and smooth activation and deactivation of cores acc to load. only single core runs while using light apps (whatsapp,hike,tapatalk etc) i.e. full utilization of a single core.
2. Highly customizable using the FauxClock pro app.
3. cpu temp was usually higher (50-60 degrees) than my last kernel (Tz).
4. As @sunilnair007 posted the screen goes black while call. But one thing i noticed was when i press just at the side of proxi sensor the screen wakes up Exactly same as the Yureka proximity issue but on all other kernels the proxi was working fine on my phone (stock, thunderzap)...
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
and after turning on the battery was 12% (earlier it was above 75%) and it was increasing by itself >.> battery usage graph ss --- i.imgur.com/y9QCyCz.png
and after keeping it turned off for sometime and restarting the battery got stable at 46% and started decreasing as per usage. (so got much less battery backup)
How to make best use of it.
Installed this kernel.
However, it seems very complex to make best use of it by a person like me who is not used to Custom Kernels. Before this I have used ThunderZap2, and Xcelerate, without much of tweaking. In Xcelerate for example, I found that different cores where shutting down by default. Here all the core are working by default. Obviously with this Kernel it seems I will have to do some tweaking.
I have also installed Kernel Adiutor as recommended in OP. However, information on recommended setting is too sketchy.
Would like to more detailed information as how to tweak / set this kernel to make best use of it.
tons of thanks to you bro... for kcal addition
Bro thanks a lot for adding kcal colour management to YU yureka..
Very nice bro..
One thing bro the hotplug is only working with 4 cpu of first cluster only...
I'm using kernel audiutor beta...
And please rommended any setting to run it cooller because comparing to other custom kernel it run little high temp..
Otherwise working grate.....
[KERNEL][3.10.71][KCAL] Velocity v1.1
Seems developer worked hard and results are visible.
No complaints so far testing since morning.
Need 2 days time to give a stable review.
Best wishes and please keep this spirit intact
Regards
Tarry! said:
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
Click to expand...
Click to collapse
Noticed this too. Pressing the volume buttons once/twice, when it is unresponsive, wakes it right back up.
esukhdev said:
Here all the core are working by default. Obviously with this Kernel it seems I will have to do some tweaking.
I have also installed Kernel Adiutor as recommended in OP. However, information on recommended setting is too sketchy.
Would like to more detailed information as how to tweak / set this kernel to make best use of it.
Click to expand...
Click to collapse
Firstly, I'll try to simplify the recommended settings.
Secondly, hotplugging is not enabled by default.
Enable it by going to CPU Hotplug in Kernel Adiutor and enabling Intelliplug.
DGEEEK said:
One thing bro the hotplug is only working with 4 cpu of first cluster only...
I'm using kernel audiutor beta...
And please rommended any setting to run it cooller because comparing to other custom kernel it run little high temp..
Otherwise working grate.....
Click to expand...
Click to collapse
Set the Intelliplug profile to Eco Conservative/Eco Performance to hotplug upto 7 cores.
I'm looking into the cluster problem as mentioned.
To run cooler, try reducing the max frequency.
Tarry! said:
1. First & best intelli_plug driver - loved the live and smooth activation and deactivation of cores acc to load. only single core runs while using light apps (whatsapp,hike,tapatalk etc) i.e. full utilization of a single core.
2. Highly customizable using the FauxClock pro app.
3. cpu temp was usually higher (50-60 degrees) than my last kernel (Tz).
4. As @sunilnair007 posted the screen goes black while call. But one thing i noticed was when i press just at the side of proxi sensor the screen wakes up Exactly same as the Yureka proximity issue but on all other kernels the proxi was working fine on my phone (stock, thunderzap)...
5. i didn't used the phone for an hour or so i.e. phone was in deep sleep the i tried to wake up the device by the power button several times but finally had to remove battery and put again and booted the device :c
and after turning on the battery was 12% (earlier it was above 75%) and it was increasing by itself >.> battery usage graph ss --- i.imgur.com/y9QCyCz.png
and after keeping it turned off for sometime and restarting the battery got stable at 46% and started decreasing as per usage. (so got much less battery backup)
Click to expand...
Click to collapse
Regarding point 5 , I faced same behavior in TZ as well xccelerate kernel.I don't understand the problem.the battery completely drained out and more heat on backside of the mobile.whenever if i would make any changes on IO SCHEDULER or governed faced the issue.
Sent from my AO5510 using XDA Free mobile app
androidgalaxyman said:
Regarding point 5 , I faced same behavior in TZ as well xccelerate kernel.I don't understand the problem.the battery completely drained out and more heat on backside of the mobile.whenever if i would make any changes on IO SCHEDULER or governed faced the issue.
Sent from my AO5510 using XDA Free mobile app
Click to expand...
Click to collapse
The issue is that if you set performance profile to "Power save", gov "ondemand" & min frequency lesser than 500MHz, phone sleeps to death & you have to hard reboot to get back on. Its a known bug and is present in stock kernel too. Check if settings i stated are the reason for you. Doesn't happen with "Interactive" because it never scales lower.
Sent from my AO5510 using XDA Free mobile app
@neomanu , Do I need to wipe cache and dalvik cache while flashing this kernel over any ROM. Also I have flashed a custom kernel previously and now I want to flash this, so Should I simply follow your instructions or need to wipe something.
No Need to wipe anything. To give u extra boost you can wipe dalvik cache which will rebuild cache again and its always good. no need of cache or data wipe
Is this kernel support's volte?
Sent from my AO5510 using XDA-Developers Legacy app

Categories

Resources