yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] drhonk:
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
[Vibrant Android Development] drhonk:
Change Log:

- 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
[Vibrant Android Development] gamikzone:
is GPS still functional with this kernel?
[Vibrant Android Development] drhonk:
Yes .. GPS still functional. :)
[Vibrant Android Development] gamikzone:
im about to flash this :D hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
[Vibrant Android Development] drhonk:
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.
[Vibrant Android Development] gamikzone:
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
[Vibrant Android Development] drhonk:
Try smartass with this kernel .. :)
[Vibrant Android Development] gamikzone:
i think i will try this out tonight :)
[Vibrant Android Development] jay661972:
I believe this will be ok to use with miui.

Nice animation.
[Vibrant Android Development] jay661972:
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.
[Vibrant Android Development] es7241:
Trying it out , any recommeneded UV settings?
[Vibrant Android Development] es7241:
It does work on miui,
[Vibrant Android Development] darkness122:
would downloading SetCPU and just setting the governor to smartass improve battery life? or do you have to actually UV and all that
[Vibrant Android Development] jay661972:
Really, how did you do that? I did the clean script first and flash Bali.
[Vibrant Android Development] jay661972:
Okay I will try this one more time.
[Vibrant Android Development] drhonk:
confirmed .. it works on MIUI since I just flashed MIUI with it. :)
[Vibrant Android Development] younix258:
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.
[Vibrant Android Development] jay661972:
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
[Vibrant Android Development] ChoctawT:
So you can't flash bali on miui energy? You have to revert to stock miui?
[Vibrant Android Development] drhonk:
Yes please .. PM that to me
[Vibrant Android Development] es7241:
Did you recondition and wait a couple of days?
[Vibrant Android Development] jay661972:
so far, no reboots for me and its quicker than 1.0, its just my phone, no uv (my phone dont like it) but oc to 1.3.
[Vibrant Android Development] Cesarp 24:
1.1 highly undervolted no problems. Thanks Dr.

Sent By My CM7 Monster
[Vibrant Android Development] lightninbug:
What is Voodoo Color v2? I know what Voodoo Color is...just whats new in v2?
[Vibrant Android Development] Oxirane:
Awesome work, Dr! 1.0 has been awesome, minus a few reboots (typically with Dolphin Mini and Pulse Reader) but fingers crossed that 1.1 will fix that :)

On a side note, I notice my CWM is now blue. Anyone know what kind of new features that has? :)

EDIT: And it seems I maybe should have waited on flashing that.... bootlooping now. Perhaps that blue recovery isn't a good thing :/

EDIT 2: Reflashed 1.0 without issues. Thinking maybe a bad download.... I'll try redownloading it.
[Vibrant Android Development] drhonk:
I added mirror site on OP
[Vibrant Android Development] drhonk:
If you still having that issue, try the mirror site .. maybe it's a bad upload but I will need to know if mirror site has good file before I replace the file on mediafire.
[Vibrant Android Development] darkness122:
Flashed the latest v of Bali, screen turns green before it turns off, just like before.

i wonder why this is. still have more to see as far as performance.
[Vibrant Android Development] drhonk:
Let me build one without voodoo color and post it tonight ..
[Vibrant Android Development] darkness122:
cool man, thanks. i kinda figured it had to be voodoo color since the last version didn't have it and also didn't have the color issue.

any idea of a possible fix?

thanks again!
[Vibrant Android Development] drhonk:
Does it boot at all? Also try disabling auto brightness, or whatever the name of it .. before I build it. :)

Anybody else having the same issue?
[Vibrant Android Development] Chwek13:
Tried 1.1 on miui just keeps random restarts went back 2 1.0 everything is good now tried both downloads same thing
[Vibrant Android Development] drhonk:
Do you have UV set? .. if you do .. remove on boot settings .. and try again. 1.1 is using VC compatible format that should work on both VC and SetCPU. Give it a try .. :)
[Vibrant Android Development] Goten310:
Ran the cleaning script then 1.1. It got stuck at the Bali logo. Rebooted into recovery... ran the script again and reflashed 1.1. It booted up into CM7 and I was enjoying the Voodoo color for a minute and it rebooted on me. Reverted back to version 1.
[Vibrant Android Development] JettyLife:
Hey drhonk, any reason my setcpu will not stay on its governor I set it at? It seems to default to ondemand even without a reboot. Not sure why.

Vibrant+MIUI
[Vibrant Android Development] drhonk:
Default should be conservative
[Vibrant Android Development] hussarfilms:
everything is good here.

downloaded from mediafire

cleaned kernel

installed 1.1

reconfigured setcpu to smartass [set on boot]

also have screen off 400/100

things are fine as of now.

thanks drhonk
[Vibrant Android Development] drhonk:
Nice .. but not helping this mystery reboot on some ppl .. LOL
[Vibrant Android Development] darkness122:
on MIUI energy + your last kernel, I'd occasionally get a rando reboot, but i really couldn't tell you after what/why they'd happen. all i can say is they weren't that consistent.

so far everything is okay other than the minor green screen thing. also, auto brightness is already off, and i should mention the screen goes green both turning on the screen when its off, and when it goes off too.
[Vibrant Android Development] duboi97:
Voodoo Color?!?!?!?! HELL YEAH! Here I come Bali :D
[Vibrant Android Development] drhonk:
I'm on the same ROM and doesn't have that issue but again I deleted Chain3D, well I removed a lot of the bloats. :)
[Vibrant Android Development] Cesarp 24:
Run the script and flash twice. Cm7 is buggy with that sometimes. Sometimes u have to flash things twice.

Sent By My CM7 Monster
[Vibrant Android Development] hussarfilms:
Actually i take it back.

Reboots everytime it booted up.
[Vibrant Android Development] JettyLife:
But when I set it to anything else and then close the app it ends up going back to ondemand. I guess it could be an app problem

Vibrant+MIUI
[Vibrant Android Development] darkness122:
yea i try to keep mine on smartass, but notice it going back to ondemand every once and a while, despite checking the "set on boot" setting.
[Vibrant Android Development] Cesarp 24:
Just got my first two reboots.

Sent By My CM7 Monster
[Vibrant Android Development] JettyLife:
Flashed 1.1

Voodoo color <3

Edit: just had two more reboots. Probably back to 1.0 for now.
[Vibrant Android Development] jay661972:
3 reboots and went back to 1.0 for now
[Vibrant Android Development] johnny12times:
Would someone please post Bali 1.0? (or tell me I'm an idiot if it's in the thread and I missed it.)

Thanks!
[Vibrant Android Development] vinnydakid:
1.1 causes bootloops even after wiping Davlik and Cache. Flashing back to 1.0 solves the issue immediately.
[Vibrant Android Development] betasp:
I just threw this on top of MIUI.us, my first GB flash and have had no issues other than setcpu FC'ing on me. Network detection is slow at startup, and overall MIUI lags some, but it looks great.
[Vibrant Android Development] reocej:
This has to do with your gamma settings in voodoo color. If you set the gamma too low you will get green screen. Try upping the gamma till you no longer get green screen. You can test it by turning off auto backlight and adjusting backlight all the way down till you either do/don't get green screen.
[Vibrant Android Development] drhonk:
For those of you that are experiencing random reboot or kernel instability, get the ultimate kernel cleaning script .. flash it, then reflash bali 1.1

http://xdaforums.com/showthread.php?t=1166954

See if that helps.
[Vibrant Android Development] es7241:
Was running fine on 1.0 flashed 1.1 got lots of reboots then I tryed to flash 1.0 back and it didn't boot. And yes I do use that Ultimate kernel cleaning script every time I flash, reflashing Miui and using 1.0 :D
[Vibrant Android Development] jay661972:
doc, tried the updated script cleaning and flash 1.1 and just keeps rebooting. back to 1.0 again
[Vibrant Android Development] drhonk:
I think I've found the problem, will post a fix shortly
[Vibrant Android Development] ozayas:
I also get boot loops. I flashed the cleaning script, reset my SetCPU settings and downloaded from the original and mirror location, nothing worked. I am on Miui stock. Bali 1.0 work perfect so far
[Vibrant Android Development] Cesarp 24:
I only get bootloops when my CPU is at Max for a long time.

Sent By My CM7 Monster
[Vibrant Android Development] dr150:
I'm getting several reboots even after using the Cleaner kernel.

1.1 seems to be half baked from the other reboot comments....

Going back to 1.0 works just fine though....

(...don't know how well these kernels work with CM...I got to 25% with 1 hour's worth of GPS on half bright screen and 20 minutes of goofing with settings on full bright screen.........is this about average or worse?....)
[Vibrant Android Development] drhonk:
version 1.1.1 is available for download .. I hope this will fix reboot issue for good. Give it a try and let me know .. :)
[Vibrant Android Development] mohamobo:
Thanks for the fast fix but your download link are incorrect.
[Vibrant Android Development] DynamicXL:
yup, giving me an invalid link error
[Vibrant Android Development] jay661972:
Same here, not valid URL
[Vibrant Android Development] vinnydakid:
Fixed download link from Rootzwiki until OP can be updated. http://www.mediafire.com/?r9p0vnaho1z2if1
[Vibrant Android Development] enzomtrx:
#http can be taking out of the OP to make latest link work.
[Vibrant Android Development] drhonk:
oops .. sorry about that .. link is updated.
[Vibrant Android Development] jay661972:
Use the link vinny provided and so far made it through. Using it right now. For now oc to 1.2 only and -50 alk the way uv. Hope my phone will like it.
[Vibrant Android Development] jay661972:
Thanks for the quick update.
[Vibrant Android Development] ChoctawT:
Im new to setcpu & VC ...im just looking for better battery life.. I see others talk about undervolting, how exactly do I go about doing that?
[Vibrant Android Development] ajamils:
Just flashed the latest version and so far so good. The only issue I see is that under SetCPU all voltages show up as 0mV. Is there any reason for that ?
[Vibrant Android Development] brianhaskell:
Not working with redux v 15. Is it because it's 2.3.5 not 2.3.4
[Vibrant Android Development] rom fiend:
Soooo I updated to 1.1 earlier today and everything was going great (only one reboot) and I had 60% battery left after 8 hours of moderate use which is BY FAR the best battery life I've ever gotten with cm. Problem is I got a random reboot while typing an mms message and when the phone booted back up the battery was down to 12%!! Not sure what happened but I am going to update momentarily.

Sent from my CM7 Vibrant
[Vibrant Android Development] bobbbb:
You need to calibrate your battery; upon flashing a new rom base (especially when not done so on 100%) your battery.bin stats will be messed up:cool:
[Vibrant Android Development] drhonk:
Should be easier to UV now that you don't have to know the default voltage and it's also compatible with VC now.
[Vibrant Android Development] drhonk:
Update to 1.1.1 to fix that random reboot issue
[Vibrant Android Development] drhonk:
What happen when you flash this kernel? boot loop?
[Vibrant Android Development] rom fiend:
I followed all instructions for install in the op as well as wiping battery stats.

Sent from my CM7 Vibrant
[Vibrant Android Development] brianhaskell:
Yes I keep getting bootloop. Sucks because I only use your kernals since they came out. Best battery life and smooth
[Vibrant Android Development] Cesarp 24:
Dr.honk what scheduler do you recommend?

Sent By My CM7 Monster
[Vibrant Android Development] rom fiend:
Installed 1.1.1 but was wondering if my battery actually dropped 45% in 30 seconds or if it was showing the wrong percentage all day and corrected itself after reboot.

Sent from my CM7 Vibrant
[Vibrant Android Development] drhonk:
Did you flash kernel cleaning script before you flash bali? If you didn't .. try flash kernel cleaning script first .. then bali.
[Vibrant Android Development] ruskiiwrx02:
just flashed latest version 1.1.1 on MIUI, getting a green overcast on the whole screen when it dims before the screen sleeps. Still gonna use it, but just letting you know. I'm guessing it has something to do with voodoo color....

Thanks for all your hard work!
[Vibrant Android Development] drhonk:
You will need to calibrate your battery ..
[Vibrant Android Development] rom fiend:
I clear battery stats after all flashes. I was just wondering if maybe it was displaying an incorrect number all day and corrected after reboot or if the battery actually purged 45% during the reboot?

EDIT: running 1.1.1 for about five minutes and battery percentage just jumped back to 68%. ::confused::

Sent from my CM7 Vibrant
[Vibrant Android Development] drhonk:
Use this .. https://market.android.com/details?id=com.nema.batterycalibration&feature=search_result
[Vibrant Android Development] rom fiend:
I understand what needs to be done. What I don't understand is what *actually* happened. Sorry to be a pain and thank you for your effort and time.

Sent from my CM7 Vibrant
[Vibrant Android Development] reocej:
See post #213.
[Vibrant Android Development] ozayas:
I'm still getting random boots on 1.1.1. Any way to post MD5 sum so I can make sure I'm getting a good download?
[Vibrant Android Development] viralbug:
I had done a clean flash of Trigger Redux build 15.

Flashed the kernel cleaning script and then Bali 1.1. Got stuck in a boot loop.

Flashed the kernel cleaning script and Bali 1.1 again. This time it booted fine twice, but I didn't get any network and phone rebooted randomly in a couple of minutes. After that stuck in boot loop again.

Flashed back to Bali 1.0 for now.

EDIT: Whoops. Sorry I hadn't seen the 1.1.1 update. Flashed that and it works fine. Thank you for making Bali! It's by far the most kick ass kernel, for Froyo and GB.
[Vibrant Android Development] strictlyrude27:
I'm getting GREAT UV so far with Voltage Control and Bali 1.1.1. Here are my results, then my test methodology, based on shaolin's mini overclocking guide:

f (MHz) | delta_V (mV)
-----------------------
100 | -175
200 | -125
400 | -100
800 | -50
1000 | -25

governor: smartass
scheduler: cfq

This is by far the most aggressive UV I've been able to do.

I used Moboplayer and the latest Stability Test (with root) to run my tests. I would set all frequencies for -25mV and watch a video for a couple minutes in Moboplayer. If it succeeded, step everything down another -25. Repeat until reboot, visual/audio glitch, other unexpected behavior. I then stepped the highest frequency up and tried again. If it was stable that time, I noted that as "max stable UV" for that frequency.

Once all "max stable UV" were found, I ran Stability Test with root for 15 minutes. When you use root, the app randomly sets your max CPU speed to random numbers inside your specified range. After 15 minutes of this with no errors I declared the settings stable. If the stability test failed, I would work my way back up the chain - giving more volts to the higher frequencies systematically again until I got something stable.

Once base frequencies are set, it's time to start slowly overclocking, and finding the best UV along the way the exact same way.

This might not make a whole lot of sense in words, so here's a link to the spreadsheet I made which tracks my UV progress:

http://goo.gl/RJiRC

Each column corresponds to a trial - you can see whether the test passed or failed at the top of each column, and any relevant comments to how the test failed or passed.

I hope this helps anyone be more systematic with their OC/UV. It's a whole lot better than blindly picking UV settings in the dark, I think, although it's a time consuming process.
[Vibrant Android Development] nbhnohome:
I've been testing for hours and the phone seems to be stable with these settings

100 | -200

200 | -150

400 | -125

800 | -100

CPU Governor : OnDemand or Conservative (Max Freq. : 800).

Phone is snappy with OnDemand, a bit laggy as usual on Conservative but battery life has been great so far
[Vibrant Android Development] krylon360:
it's really pointless posting your UV settings. ALL CPUS are different. Your settings might not work for mine, and mine might not work for someone elses phone. It's all just a hit or miss, the same as why some shut down just after a minor OC, and some you can OC the crap out of.
[Vibrant Android Development] Gunsmith_Cats:
I'm going to try out redux 15 w Bali 1.1.1. For the day will report back. So far so good also liking the new splash Dr honk. Thank you!
[Vibrant Android Development] ajamils:
Just to give you an update... I flashed 1.1.1 last night and after 9 hours I still have 35% battery left. Granted that I did not use my phone much but still this is the best battery life that I've gotten with Bali + MIUI combination.

Will try UV and OC to see how it holds up.
[Vibrant Android Development] Chwek13:
Can't get phone to deep sleep on 1.1.1 flashed 1.0 phone deep sleep's now
[Vibrant Android Development] alawadhi3000:
Correct, but if you look into a few user OC/UV values, you can get a general idea about what values you may get. It makes OC/UV faster to do.
[Vibrant Android Development] ursubpar:
hangs at bali logo after flashing cleaning script and bali 1.1.1.

after clearing cache and dalvik it boots but randomly reboots later.
[Vibrant Android Development] drhonk:
Need to know more detail, which ROM do you use .. etc ..
[Vibrant Android Development] ursubpar:
Redux 15. I was previously using glitch kernel

Edit: Got it running stable after a few wipes and flashes but now "no service" even after flashing a new modem
[Vibrant Android Development] drhonk:
I can't help you with modem .. :)
[Vibrant Android Development] es7241:
Make sure yoy flash the new partition modems for cm 7.1 , these roms are using a different partition than they did before .. Do alittle searching around xda to find the 7.1 modems
[Vibrant Android Development] ursubpar:
I did flash a kb5 7.1 modem but it keeps saying no service on bali.

Other kernels get signal
[Vibrant Android Development] dr150:
What settings are you guys using with SetCPU and Bali???....
[Vibrant Android Development] krntehknik303:
just downloaded this kernel.. set to smartass set on boot. hopefully my phone doesn't fry.. hahaha
[Vibrant Android Development] strictlyrude27:
Anyone else running into issues with rebooting? When I go to reboot, my phone goes through the reboot operation, then gets stuck. Kind of like a screen of death - have to hold the power button to get it to turn back on.

I thought it was my UV settings, but the same thing happens with no UV.

EDIT: Maybe it was my UV settings, but it took a couple reboot attempts to get it working again. Hm.
[Vibrant Android Development] ricky71153:
gps

I tried this yesterday with revamped 8.2 miui and could not get a lock with gps. Is there anyone else having the same problem?