yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Liv33viL:
Raj...

Would you mind posting your comparison results between both KB1 exotics?

And perhaps a few Quadrant, Linpack and NenaMark numbers.

(1.1 and Beta2) *Edit: Beta3 - Thread was updated with Beta3 build as this post was hitting the thread.

I'm still running Supercurio's Stock KB1+Voodoo injection with my stock KB1 modem and I haven't had any glitches or issues thus far. Although I do believe I would like some better sound quality across the boards. Battery life is still fantastic and I think may be even better that the stock KB1 build. I just deodexed my device last night and hadn't really noticed too much of a performance difference / increase, but wound up gaining 33 points on my Quadrant score (From 1503 - To 1536) - consistent and that's coming off a (983) Quadrant score running completely bone stock out of the box.

I'm looking for the features as I described in one of my posts that you replied to.

I'm still in the mindset... if it ain't broke....don't fix it.

Thanx in advance Raj...

Peace-
[Captivate Android Development] c0ldburn3r:
And yet another awesome beta. Was out checking out a place I'm moving to and tried three modems all crap service. Looks like I will be buying a microcell.
[Captivate Android Development] LNJ:
You're right. OverStock 1 worked with JK4. 1.1 doesn't.

Too bad!
[Captivate Android Development] Liv33viL:
KB1-#3 Stats

Nice work Existz... keep the features comin'

Just curious...

Any reports yet on the battery draw, WiFi and GPS lock and call quality yet with version #3?

Any insight appreciated..

Thanx

Peace-
[Captivate Android Development] existz:
For battery, you need to give it a few charge cycles to be able to accurately judge..sometimes the calibration can be off after a rom/kernel flash...

Wifi works fine for me...if anyone has any problems, try rebooting your router and wipe cache/dalvik cache, worked for me ..
[Captivate Android Development] rajendra82:
Like you, I came from a slightly tweaked stock KB1 setup (rooted and bloatware removed) running a supercurio +voodoo injected kernel until yesterday. I had thought about deodexing, but had even decided against that, because I like the overall KB1 theme sans TWLauncher just fine.

Here are my benchmark scores on after putting the latest versions (OverStock v 1.1 and eXistZ beta 3) kernels through their paces:

OverStock

Quadrant - 1694-1801-1804 (for some reason they rise each time I run the benchmark)

Neocore - 64.6 FPS

Nenamark - 49.4 FPS

Linpack - 13.85

eXistZ kernel [bfq scheduler, OC 1.2 GHz, UV -75 to -100mV]

Quadrant - 1630

Neocore - 64.6 FPS

Nenamark - 49.4 FPS

Linpack - 14.18

As you can see, the scores are almost the same for both releases (which was not the case until eXistZ beta 3, which lifted the FPS cap, boosting Quadrant and Neocore). I only had benchmarked the old stock + voodoo setup using Quadrant, and got scores between 1500 to 1550). As you can see, both are a slight improvement over the stock+voodoo setup, probably not enough to make a huge real world difference. I do like the extra memory available with the rebuilt kernels. I don't have enough of a discerning eye and ear to see and hear the benefits of voodoo sound and color, but I have always believed supercurio to be a talented guy, and if he says that they are better than Samsung defaults, I trust him enough to say at least they will not be worse.

As far as installation, the OverStock version is a no brainer to move up from the setup you have. You don't need to mess around with OC/OV settings, and don't need to add any files other than the CWM flashable zip file. You can even keep the supercurio flashable kernel file on the sd card, and freely switch back and forth between the kernels without even having to disable lagfix. The eXisitZ kernel is comparatively more complicated to set up, but once you do, it can also be switched in and out of with a simple boot into CWM recovery. You don't have to remove the Voltage Control settings files, as they just get ignored if you switch over to a non-compatible kernel like OverStock. So far I have not seen any detrimental effects with regard to WiFI, call sound quality, 3G connectivity, and stability with the latest releases of either project.

I am going to stick with the eXistZ kernel for now, as I seem to have found my OC/UV settings. I can probably push it past 1.2 GHz, but would rather not. It is too early to judge battery life, but those that undervolt swear it benefits them in that department, and I can understand why. I missed the boat on OC/UV during the Eclaire phase, and once Froyo leaked, we lost access to source code, so that was no longer a choice. If you don't feel comfortable running tests on your phone for a few hours to arrive at the optimal settings, the OverStock version is a fine alternative.
[Captivate Android Development] Liv33viL:
Thanx for the quick reply Existz...

I have yet to flash KB1 #3 - I just wanted to get some feedback before flashing.

I'm still mildly stock - running a stock KB1 kernel and a stock KB1 modem configuration. I've been running Supercurios Voodoo Injected KB1 Mod without any issues whatsoever. Nothing but positives with my device as it stands.

I'm just looking to make a few specific enhancements to my device - Not overkill or a full ROM flash - just the mods and tweaks that I'm looking for. (Speed, Audio, Clarity, (Increased Up/Download speeds - which is currently pretty snappy).

Yes, I read in the thread yesterday what you posted on charging cycles.

I figured that already while needing to retrain the battery behavior, wiping battery stats and I typically clear all dalvik-cache on a major or semi major mod.

I also read that you resolved the WiFi issue previously and performed a router bounce. That cool too...

I'm curious as to the lock time to WiFi as well as the lock time for GPS (3 seconds, 10 seconds, 45 seconds, or more...)

But I still am a bit curious as the the quality of the in / outbound calls as well as the overall audio. (Yes, I also read about the audience chip as well)

Thanx for taking the time to respond Existz

Peace-
[Captivate Android Development] Liv33viL:
Raj...

Thank you very much for taking the time to respond and reply in detail.

This is exactly the information I was seeking.

I do understand.. each device will acquire its own results, even the same build and model, but the iformation you provided puts me in the area of information I needed to be.

Good luck with your new mod Raj... and continue to post your results going forward every so often... as I will do the same.

Peace-
[Captivate Android Development] rajendra82:
From a supercurio KB1 to eXistZ KB1, the GPS lock times, call quality, and WiFi lock times should not change. I would love it if the HSUPA cap would somehow go away, but it won't.
[Captivate Android Development] GGXtreme:
When you say 'WIP' next to Voodoo Color, do you mean that it's not implemented yet? Also, anyone have a good meter on battery life yet? The seemingly improved performance is great, but I'd like to know if this has any disadvantages compared to Suckerpunch (I don't OC/UV). I still keep battery life (as well as functionality and stability) a priority, followed by features like CIFS support, Voodoo Color and Sound, etc.
[Captivate Android Development] rajendra82:
No Voodoo Color in Beta 3. As to battery life, I have always been a fan of the i897 releases starting with JF6, JH2. JH3, JH7, JI6, JJ4, and now KB1. No matter how many times I tried, I can never stick with any i9000 ROM+modem. For my build 1007 they just lose tower connection from time to time, and then battery life goes to hell unless I catch it happening and reboot. When you go stock (modded the way you want) battery is the least of your concerns. As much as I would love to stick it to the man by enabling HSUPA, I live and die on WiFi everywhere I go, and eXistZ KB1 suits me just fine so far. If the battery gets low, I plug it in, and I never think about it twice. It just seems to happen a bit less often when I am closer to stock. I don't miss any calls either.
[Captivate Android Development] GGXtreme:
Hmm. I rarely use data at all (I usually keep it off and stick to wifi), so HSUPA is not a big concern for me. This sounds very promising, but I'm going to have to stick it out until Voodoo Color is implemented. I use my Captivate for watching video heavily, and the default blue-hue screen is too annoying, even in the UI.

Also, whether or not HSUPA is uncapped in this kernel sooner or later, it doesn't seem like a bad idea to have a separate version for use with I9000 modems. I don't care about data, but I care even less about the 'audience chip', as my call quality has always been fine with every ROM/modem I've used.
[Captivate Android Development] oxlong27:
Beta3 is working flawlessly for me fast stable responsive great job wifi issues gone also
[Captivate Android Development] existz:
deleted...double post
[Captivate Android Development] existz:
*UPDATE*

BETA #4

-Voodoo color: gamma 2.2 only

-Voodoo color: mDNIe color and sharpness enhancements

-darker min brightness tweak

-slightly optimized light sensor driver
[Captivate Android Development] rajendra82:
Looking good (pun intended).

P.S. - This is my first time trying voodoo color, are there any settings to adjust somewhere?
[Captivate Android Development] existz:
As far as I know there's not, before there never was but the new voodoo app has some voodoo color adjustments, but I think its only for 2.3 or nexus s...
[Captivate Android Development] rajendra82:
<strike>What is the light sensor logic in this version supposed to be? I see the darker minimum brightness being applied, but when I move outdoors in the sunlight (6 PM intensity, but still direct light), the screen never gets up to maximum brightness if automatic brightness is checked. This makes it very hard to see the screen outdoors. Is this the intended behavior?</strike>

Never mind. I am an idiot. Battery was almost dead, causing the battery saving logic to kick in. Works fine when recharging.
[Captivate Android Development] ConeyKiller:
Just flashed....seems to work great...however I'm still new...what's the apk that is listed with download and do i need to install it?
[Captivate Android Development] existz:
The Voltage Control app attatched in the OP is to overclock or undervolt, its what let's you adjust voltages and frequencies..but if you don't plan on oc/uv'ing then you don't need it.. just an option incase you want to
[Captivate Android Development] rajendra82:
Voltage Control is to setup overclocking and undervolting. You don't need to install it. Without it, everything will default to -0 mV and maximum speed will be 1 GHz. Even after installing it, the settings will stay that way until you adjust it, and tell it to apply on boot or for now.
[Captivate Android Development] ConeyKiller:
So...is it worth it? I've never overclocked anything not even a computer....more so just because of money to replace hardware lol.
[Captivate Android Development] existz:
It really depends on your use, if you don't use any apps or games that's cpu intensive, then you will never really see a difference.. The 1200 step is actually in the stock samsung source code, but not used.. most people can handle it..but its not a guarantee.. The cpu actually scales, meaning it adjust frequencies as needed, so it really doesn't spend that much time at higher voltages/frequencies..(theres a command in the OP to check how much time is spent at each frequency) it just uses them when needed (meaning it doesn't spend the whole time at a certain step, it will bounce from 100 to 600 to 200 to 1000..etc..etc) ... As for UVing, it helps with battery life and also it can actually prolong the life of your phone in theroy, less voltages=less heat=longer life.. but an unstable oc/uv can cause problems, reboots, freezes, force closes, sleep/charge death...etc.. Since all phones are different, there's really no recommended settings, some can handle more than others..there's a guide in the OP to help get started
[Captivate Android Development] ThisWasATriumph:
Has gamma 2.2 been implemented in Suckerpunch yet?
[Captivate Android Development] ConeyKiller:
Ya I was reading thru that guide..i didn't undervolt but I did check the 1400 & 1300... unchecked 100 & 600....gained about 220 on quadrant for what's that worth....my battery life seems to be great left alone...i goto sleep with full charge and wake up with nearly full charge....
[Captivate Android Development] existz:
Yep..both SP and SP-Voodoo uses gamma 2.2 only

I would keep the 100 and 600, those 2 are used frequently and will give better battery life than not using them.. even though VC says to use 5-7 states, you can use more if you do it right... the point of that is that if you have to many states selected, it can actually slow things down, giving lag.. so for example, if your OCing to 1400 ,you don't want to select 1120,1200,1300,1400.. I always try to keep a rule of thumb of a step every 200mhz..so for example, if you oc to 1400, you would want all of 100-1000 then 1200 and 1400.. having to many that's close together will make it harder for the cpu to scale down to lower frequencies, or to scale to higher ones when its needed .. but I would definitely recommend to have all of 100-1000 selected, as they are used more than anything..then adjust your higher frequencies ..I've actually set it to default that way
[Captivate Android Development] bravomail:
I'll try it tonight. UV is the best option there

As far as OC/UV goes my experience with Suckerpunch was positive. In fact, I could only overclock with undervolt. Stock voltage was unstable for me at higher frequencies.

But after experimenting I try to opt for 800MHz/-100mV as a max. Battery life is always improved.

I'll try your kernel tonight on Torch 1.5 KB Rom. Existz. Thanks for the wonderful code!
[Captivate Android Development] rajendra82:
I decided to limit the top speed to 1300 MHz for personal reasons, not actual phone limitations. When every state between 100 and 1300 MHz was enabled, my stats showed the the frequencies 1000, 1120, an 1200 MHz were all getting used a very small amount of time compared to 800 and 1300 MHz. I decided to disable 1000 and 1200 MHz, and kept 1120 MHz as the available state between 800 and 1300 MHz. Seems to still be used less than 800 and 1300 MHz, but the difference in time is not quite as drastic.
[Captivate Android Development] rajendra82:
eXistZ:

The Voltage Control app you included in the OP is version 3.0. I see version 3.0.3 in the market. Is it compatible and safe to update to?
[Captivate Android Development] existz:
Yep its fine
[Captivate Android Development] ewingr:
Used SGS Kernel Installer

and I boot to an AT&T screen, and goes no further.

Have I screwed the pooch?

[EDIT]

Maybe not. I think I just heard the Voodoo voice. I was thinking I heard that after the AT&T screen cleared.
[Captivate Android Development] rajendra82:
If this is your first voodoo kernel, it can sit quite a while (10 minutes or so) on the AT&T logo screen while converting partitions on the first boot. If truly stuck, reboot, and see if you can get into CWM recovery mode, and then reflash the kernel. If you can't do that, use the USB + volume buttons + battery trick or a jig to get into download mode, and use Odin or Heimdall to flash supercurio stock+voodoo KB1 kernel, and then get back into CWM recovery to reflash this one.
[Captivate Android Development] rajendra82:
There are actually two screens. One is on the phone (in /mnt/.lfs I think) that is shown first for a few seconds. There is a second logo screen in the kernel, which for stock and this eXistZ KB1 kernel is the same as the first logo. Other kernels like OverStock and Firebird replace that second screen with a custom logo. It's while on the second screen that the voodoo conversion happens. After the two static screens clear, the boot animation (either bootanimation.zip when present or that annoying flying bars qmg followed by the S screen called for in the playlogos script) is shown. If you cleared dalvik cache, it can sit on the boot animation for a couple of minutes as well.
[Captivate Android Development] GGXtreme:
Any chance of reimplementing the Voodoo color profiles like Suckerpunch has? A warm color profile is very crucial for my phone's blue screen, and as nice as the performance on these KB1 ROM's are, I think I may have to go back to Suckerpunch because of this, the terrible modem and the random reboot issues :(
[Captivate Android Development] existz:
That uses Hardcores color profiles, its different than voodoo color...which as of right now, im only doing 1 version of this kernel, maybe later on when I get more time, i might do a warm/cold version of this kernel..i dont know yet though.. so far having 3 kernels is a hand full (Suckerpunch, SuckerPunch-Voodoo and now KB1 Kernel) ...
[Captivate Android Development] rajendra82:
Can the 2.2 KB1 framework support FuguTweaks? Is that part of more to come? Love everything you have done so far, and just wondering.
[Captivate Android Development] existz:
Yes, you can use fugu tweaks, actually using it right now on Cog 4.1.1 with my KB1 kernel
[Captivate Android Development] rajendra82:
Cool, will try it when I am undrunk.
[Captivate Android Development] existz:
lol...thats always a good idea ;)
[Captivate Android Development] rajendra82:
WADM - Wives against drunk modding
[Captivate Android Development] boardsportsrule:
Very exciting to see this being made! Flashed for a few hours. Kb1 modem.. went to drive around, tried gps and couldn't get a lock.. enabled data, random reboot.. got to my destination and went back to previous kernel and modem....!

If there's anything I can do to provide you with more details for bug testing, let me know! Looking forward to getting proper noise cancelation!!

Thanks for your hard work!
[Captivate Android Development] ulupinar:
Any plans for setting an option for the screen darkness?

I have been using the beta 4. It seems to be pretty stable for me. Thanks for the kernel. Do you have any plans for making the lowest darkness optional like in suckerpunch kernel? The darkness setting is too dark for may phone/my taste.

Thanks
[Captivate Android Development] Liv33viL:
Impressive - Very!

Just got in a little bit ago after spending the day with my lady...

Just figured I poke my head in and see what's shakin'

Wow EXistZ ... one cannot blink around you - *Blink* another mod - *Blink* another fix - *Blink* another tweak - *Poof* another build... Fantastic!

I've been following this thread since its inception and you really put a great deal of effort into you "work" if you want to call it work - more of a passion if you ask me.

I'm not really able just yet to flash this kernel and spend the needed time tweaking the OC/UV and making all the appropriate adjustments while testing. (Time restraints - and I need a stable device when I'm out and about) - I've been building Hot Rod PCs for quite a few years now, modding and tweaking the iStuff and now just starting to get my groove on with Android and my Captivate.

Time permitting towards the end of the week (Corp Tax Time Deadline for me this Tuesday) I'd really like to take this Power House Kernel around the block a few times.

Keep up the great passion.... there appears to be much I can learn in this thread.

Thank you

Peace-
[Captivate Android Development] rajendra82:
Just chiming in to report that Fugu Tweaks is working on my stock KB1 setup.
[Captivate Android Development] ewingr:
That explains it. I have used Voodoo a lot, but have always seen a custom second screen. So I was concerned when it stayed on AT&T screen.

It is working for me, I have tweaked the UV settings. Running at 1400. My Linpack is not as fast as when I was on 2.2.1 ROM, and using Paragon kernel (over 19), this one running just under 12. I'm not sure why there would be such a difference.

But the main thing I put this kernal on for was the UV.

AutoRotate

By the way, I might point out that the reason I am trying KB1 ROM is because on all 2.2.1 ROMS I have tired, given enough time, my Auto Rotate Quites. It quits even faster if I use Screeble. But a flash back to stock always fixes it. So, I am trying to see if KB1 eliminates that problem.

So far though, I am missing a lot of the good things that the 2.2.1 ROMs were brining.
[Captivate Android Development] existz:
You will usually always get around the same linpack scores (+/-) at the same cpu speed, linpack test just the cpu, so it should be fairly similar no matter what kernel your using...that being said, your clock is not sticking, either make sure you enabled all the correct states and max clock, and/or make sure to save your settings twice, sometimes it doesnt stick...but yea, unlike Quadrant or whatever, Linpack calculates just the cpu, so you should get around the same scores at same speeds with different kernels..give or take a mflop or so, but shouldnt be a big change
[Captivate Android Development] rajendra82:
I am overclocking under this kernel to 1300 MHz, and my linpack is 18. Are you sure you are running at 1400 MHz, and still getting a linpack of 12. Recheck the time in each of the states.
[Captivate Android Development] ewingr:
@existz and rajendra82.

Is there any way to gauge what speed i am running at other than Voltage Control? According to it, I am running at 1400. But, am am experiencing a lot of freezes, and the Linpakc just now gave me 8.6, and the second time 9.2 :eek:

I just killed a bunch of tasks, and ran it twice again: 11.53, and 12 539.

Not sure what to think.
[Captivate Android Development] bravomail:
Tested b4 with KB1 Torch 1.5 - works

So I tested it.

Quadrant score is 1560 at stock 1GHz/-100mV, and score 1670 at 1.3GHz/-75mV.

Voodoo sound made a difference in the games I play.

Stayed overnight without dying.

Are there any plans to incorporate SpeedMod tweaks? Are they already in?
[Captivate Android Development] s2h2golf:
You can run Stability Test from the Market and it will tell you what speed your processor is running at. If you didn't click "Save as Boot Settings" and reboot your phone, those settings won't stick - at least they don't on my phone.
[Captivate Android Development] rajendra82:
You can use root explorer to look at /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state as text. You can also use the cat command listed in the OP to do the same in a terminal. That should tell you what states are enabled, and what time is being spent in each. I am not sure how to tell the current cpu frequency.

Edit: Found it. Use cat to output or use root explorer to look at sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq
[Captivate Android Development] existz:
Stability Test just shows bogomips, its not the same as mhz...bogomips is not a cpu speed
[Captivate Android Development] ewingr:
Hmmm....I just insntalled setCPU, and set it to 1400. Didn't make a difference.

I opened up System manager, then opened Linpack and kicked it off, and toggled back to System manager and it seems to be running at 1000 (I am assuming that Linpack in fact is continuing to run when I toggle away from it).

I am aware I need to save for reboot. But if the Voltage Control app show 1400, but it isn't using 1400, I'm not sure what to do next.

I am on V3 of Voltage Control. I tried to download 3.03 from the market, and I get an error "The backage is unsigned".
[Captivate Android Development] rajendra82:
Did you open the sliding states drawer in Voltage Control and enable the states above 1000 MHz?

In order to upgrade to Voltage Control 3.0.3, I had to uninstall 3.0 first. It still kept the settings file in /etc/init.d/