yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shane87:
Just wanted to post my thoughts on this awesome kernel! I have been running beta #5 for about 5 days now, been through 4 charge cycles. I charged yesterday until about 9pm when I went to work. Moderate use off and on all night. I have been using xda app to browse forums durring breaks over 3g, listened to some music, sent about 5 texts, made 15 minute phone call. Once I got home, I hooked up to wifi and have been on xda since. I am sitting at 42% battery, which is much better than stock 2.2. I was lucky to have 15% remaining when I got home. I have ran linpak several times, avg score is 18.5 mflops. Avg quadrant score is 1850, 1916 is the highest. Very good audio quality, no system hangs, fc's, charge death or sleeping death. Overall, I am impressed with this kernel!! The only feature I am waiting for is hpcall support. Keep up the good work existz, looking forward to updates!! Btw, my oc/uv settings are:

1400mhz -25

1300mhz -25 disabled

1200mhz -25

1120mhz -25 disabled

1000mhz -50

800mhz -50

600mhz -50

400mhz -50

200mhz -50

100mhz -50

ROM: Cognition v4.1.1

Kernel: eXistZ's KB1 #5 Voodoo Sound v4, Voodoo Color, Voodoo lagfix

Modem: I897 UCJJ4 w/ HSUPA/HSDPA enabled (according to diagnostics screen, hsupa is enabled, but based on speed tests, hsupa may not be enabled. Need to do more tests)
[Captivate Android Development] shane87:
I know that you will need to disable lagfix on k13c speedmod before flashing this kernel. I upgraded from suckerpunch #53, which is based on speedmod, and did not disable lagfix. All I can say is :eek: It hung durring install, then would only boot to recovery. I tried to disable lagfix then, and failed with errors. Had to use odin to revert to stock then flash new kernel. As for the other tweaks, I am not sure. The lagfix is only an issue because this kernel uses voodoo lagfix, which is done differently than speedmod k13c lagfix. Hope this helps!!

ROM: Cognition v4.1.1

Kernel: eXistZ's KB1 #5 Voodoo Sound v4, Voodoo Color, Voodoo lagfix

Modem: I897 UCJJ4 w/ HSUPA/HSDPA enabled
[Captivate Android Development] rajendra82:
I believe so. I don't have an i896, but in the Cognition thread there seem to be several people with i896's. If they can run Cognition 4 successfully, then you can pair this kernel and KB1 modem on an i896. Just back up the kernel and modem you have, and flash the new kernel and modem in recovery to try it for yourself. Should only take a couple of minutes, especially if you have already turned on voodoo lagfix.
[Captivate Android Development] existz:
*UPDATE*

BETA #7

-update Voodoo Sound v6
[Captivate Android Development] TheGrub:
Thanks rajendra82, i will try that for sure...

To make sure, i don't have to disable voodoo lagfix to flash this kernel ?
[Captivate Android Development] shane87:
Woohoo!! Time to charge and flash again!!

ROM: Cognition v4.1.1

Kernel: eXistZ's KB1 #5 Voodoo Sound v4, Voodoo Color, Voodoo lagfix

Modem: I897 UCJJ4 w/ HSUPA/HSDPA enabled (according to debugging screen, hsupa is enabled, but according to speed tests it may not be. will have to do more testing!!)
[Captivate Android Development] Liv33viL:
Build #7

Sweet!

Oh man, I can dig it!

I think today, I'm going to flash up to eXistZ's Build #7. The post of the new update came over just as I was reading the post.

I do have 2 concerns:

I had read Shane's prior post about disabling the lagfix...

I'm coming off the OverStock v1.1 to flash up the Build #7 as I previously stated...

1) Is it wise to disable the lagfix that was initiated with that kernel prior to flashing to this one - and - should I do so?

2) Voltage Control App: - eXistZ, I noticed VCA 3.0 in the OP. Version 3.0.1 is available. Can I use v3.0.1 or was that version specifically designed for the respective the "insane kernel" build?

Better to ask than to wind up re-flashing everything....

Thank you

Peace-
[Captivate Android Development] ConeyKiller:
An I missing something or is there not much too the sound and color controls?
[Captivate Android Development] Liv33viL:
Voodoo Audio and Video

ConeyKiller,

Do you have the Voodoo Control Application installed. V0.10 was released to the A.M. the other day.

Take a look in the settings of the application. It does have some variants for audio.

As per the video... I posted in this thread (somewhere) what Supercurio recommends to modify the video.

Peace-
[Captivate Android Development] ConeyKiller:
Ya I have that....maybe I just doing understand what the controls do.....never was good with audio lol.....and I know for the color...need to open video player, maybe I just can't tell the difference
[Captivate Android Development] Liv33viL:
Applying ear-plugs and a blindfold may induce the same results... lol

Good luck dude...

Peace-
[Captivate Android Development] cellgeek:
@existz -

Would you consider adding i897 boot screen similar to the one displayed on SpeedMod if it's not too much trouble? IMHO it really adds a nice quality visual look to the phone.
[Captivate Android Development] rajendra82:
eXistZ

Thanks for the KB1 love. The OC/UV is running super stable with the settings table I posted earlier. The only time I seem to reboot the phone is to flash your updates, ha ha.

By the way, what is that last remaining WIP "Patched ext4" supposed to do?
[Captivate Android Development] rajendra82:
You don't have disable lagfix if flashing over from another voodoo kernel.
[Captivate Android Development] antonyvijai:
Do you mind sharing the OC/UV table with me? If you can then please PM the same. I can keep it in my records. Thanks a lot. I am going to flash the beta 7 now.
[Captivate Android Development] rajendra82:
Here is what my phone can handle:

1400 MHz @ -25 mV

1300 MHz @ -50 mV (state disabled)

1200 MHz @ -75 mV

1120 MHZ @ -100 mV (state disabled)

1000 MHz @ -100 mV

800 MHz @ -75 mV

600 MHz @ -75 mV

400 MHz @ -75 mV

200 MHz @ -25 mV

100 MHz @ -25 mV

Please do not enable the states above 1000 MHz until you have done stability testing at each step as recommended by the guide. Once you know the top end, go down, and see what works at each of the lower speeds. The only speed I didn't test at was 100 MHz. It will take quite a while to do, but is worth it IMO. Once the testing is done, keep an eye on random crashes and reboots, and reduce undervolting at the frequencies where it likely happened.
[Captivate Android Development] antonyvijai:
Thanks a lot.
[Captivate Android Development] jake.corey.jacobs:
Just wanted to add eXistZ, Im running this kernel with Stock KB1 with some UC/UV'ing and its running great! Thanks for all your work!
[Captivate Android Development] antonyvijai:
looks like the same setting is working fine for my phone as wel.. i did try different combo but the phone crashed all the time..thanks for the great tip
[Captivate Android Development] Psyclotr0n:
nevermind. ir stoopidz
[Captivate Android Development] pillz424:
Any chance for a CM7 kernel?

I am on CM7, I miss your kernels.....
[Captivate Android Development] Dave the Knave:
Lol, thanks Existz. I literally flashed your beta6 8 minutes before you updated the OP with beta7.
[Captivate Android Development] antonyvijai:
can you please share your settings as well. I tried Rajendra's and it worked fine but started crashing. i tried several other set ups too but nothing seems to work. It will be helpful if you could share your settings with me. Thanks
[Captivate Android Development] antonyvijai:
it worked fine. so i applied it for boot set up. now the phone is not booting beyondnthe media scanner running point. i am stuck now..is there anyway i can clear the settings from three button combo CWM and go to stock settings?
[Captivate Android Development] Seanbest:
Going to flash this. Coming from OverStock v1.1. Gonna give this one a shot as OverStock v1.1 seems to be a bit slow on the update.
[Captivate Android Development] antonyvijai:
someone please help me...i need to have my phone working quick..need to make an urgent call...please

EDIT: I did three button combo CWM..reflashed my old cogkernel...hoping to get back and then redo the eXistz beta 7...let me see how it goes...it got my phone back...LESSON: OC/UV is not my thing :-)

When i tried to put eXistz Beta 7 back it goes through the same prob...i just ran the CWM zip file to remove the volt scheduler..so can i assume that i will be back on track to use eXistz beta 7 kernel?

EDIT: YES I AM BACK ON TRACK TO USE eXistz beta 7...OOOOOPS...NO UV/OC FOR ME...MY PHONE HATES IT!!
[Captivate Android Development] rajendra82:
Boot into recovery. Connect to computer.

Copy the voltage settings removal script file to sdcard using adb.

Use recovery to flash it, which should remove the settings and boot you into stock voltage and frequency.

Then please do the extended testing at each frequency. You need to pass 50 cpu rounds at each frequency that you enable, all the way down to 200 MHz at least.
[Captivate Android Development] antonyvijai:
Thank you. That's what I did except that I did everything from the phone. I downloaded the CWM volt scheduler remover file to the root of my phone. Then flashed it through CWM. Reflashed eXistz beta 7. Now, I am back on track. I opened the voltage controller app to make sure I am on stock settings. I am.now. Only thing I changed is the scheduler had si ..i changed that back to cfq. Everything else remains at stock frwquency. OC/UV...i dont have that patience...thanks a lot for all the help
[Captivate Android Development] Seanbest:
Can I use the SGS Kernel Flasher?

Sent from my Captivate using the XDA App
[Captivate Android Development] existz:
You can..but i recommend flashing with CWM, ive seen kernel flasher app cause weird issues (only boot to recovery mode, plus some other crazy ****)..so if you run into anything weird reflash with CWM
[Captivate Android Development] TheGrub:
allright guys, so i can confirm that this little marvalous kernel works on a I896 captivate from Rogers.

I have gone from stock+voodoo lagfix-i896 kernel from supercurio to this kernel and everything went smooth.

My question is, i havn't flashed the modem to KB1, i am still using JL1 for now.

i'm also on stock Rogers Froyo Rom.

Tested voice calls, on mic, on speaker, on car bluetooth and everything runs fine.

What would be the benifits of switching to KB1 ?

Thanks again.
[Captivate Android Development] Seanbest:
Question ... I want to try out the OC/UV feature. I saw the .zip that would reset the settings should it not boot due to a bad OC/UV. I need to keep that on the root of the SD, but does it need to be named update.zip like the others to flash with CWM? That would mean removing the kernel update.zip right? I assuming there is no way to rename it via CWM.
[Captivate Android Development] Seanbest:
Just flashed. Boot was STUPID fast.
[Captivate Android Development] Liv33viL:
Renaming the Files...

Hey SeanBest,

No need to rename the file. You can leave the file name in tact as it sits.

Just place it on the root of your SDCard /sdcard/"filename' - then reboot into recovery mode using CWM.

Volume button up/down to highlight "install from sdcard - then use the power button to select the entry.

Now search the root of your sdcard for the file you placed there and highlight it.

Select to install the file with the power button.

After install - just find your way to the reboot option at the top of the menu - select the option with the power button and you're all good to go.

HtH

Peace-
[Captivate Android Development] boog:
You can name it whatever you like (example: whatever_you_like.zip). Or even put it in a folder on the internal sd. Then browse to it from cwm>install from sd.

I have folders with roms, kernels, modems and such all stored on the internal sd. Nice to keep spare kernels just in case I mess up lol.
[Captivate Android Development] Seanbest:
So that whole rename to update.zip is out of date? Whatever lol.

So I tried copying those files to /etc/init.d/ but it's telling me that directory doesn't exist?
[Captivate Android Development] Liv33viL:
Switching Modems...

TG,

If you aren't experiencing any current issues, I would leave it be.

The marriage between the KB1 Kernel and KB1 Modem is the primary advantage.

Other than that - if it ain't broke...

Peace-
[Captivate Android Development] Liv33viL:
Menu Option in CWM

No bud, update.zip it's not out of date. (it's been updated - lol)

It's used to install update from zip from CWM.

What version of CWM are you using BTW? 2.5.1.2 or 2.5.1.3?

You should be able to see the option in your menu...

Peace-
[Captivate Android Development] Seanbest:
I saw both options. Don't know the difference. I renamed it update.zip and did install zip from sd then chose it lol. It worked though.

Still can't find /etc/init/d/ ...
[Captivate Android Development] rajendra82:
Does the JL1 modem allow HSUPA? If so, I might try flashing it myself.
[Captivate Android Development] existz:
If init.d folder is not in /etc you can just create the folder, you will need a file manager with root access like root manager (well worth the money) ..then just copy the file over..
[Captivate Android Development] TheGrub:
From what i have read, i don't think Rogers stock modem supports HSUPA.

How can i know ? try ? enable ? test ?

Thanks.
[Captivate Android Development] Seanbest:
Tried to make the init.d folder using the terminal emulator, but get cannot make directory, system is read-only. Any suggestions?
[Captivate Android Development] rajendra82:
Install app speedtest from the market, and run a test. If download speed is around 300 kbps, HSUPA is disabled, just like on AT&T with KB1. If the download speeds are 1.2 mbps or so, you do have HSUPA enabled.

I also wonder exactly what it is that makes the sound during voice calls go away when I pair a KB1 kernel and non KB1 modem on my i897, yet it works fine for you on an i896. How exactly is the audience chip interfering? I haven't tried i896 modem JL1 specifically, but other similar modems for the Bell Vibrant (JK4, JL2) didn't work for me during voice calls.

To enable HSUPA, you need to flash a modem that supports it. The two Bell modems I mentioned are supposed to.

Edit:

I had to try to see what works and not with eXistZ beta 7 KB1 kernel on my i897. So flashed several modems, used speedtest to see if HSUPA worked, and called myself to see if voice call had audio. Here are the findings:

UCKB1 - No HSUPA, Voice call worked <- As Expected

UXJL1 - No HSUPA, Voice call Worked <- This was a surprise to me, I thought i897 kernel + i896 modem = no sound in voice calls, or at least static during calls.

UGJL2 - No HSUPA, Voice call had no audio <- This was odd too, I though Bell Vibrant allowed HSUPA. Someone a few posts back used this combo and said both worked.

TLJL3 - HSUPA, Voice call had no audio <- As Expected

XXJVE - HSUPA, Voice call had no audio <- As Expected

I ran out of time tonight, but I am going to try ZNKP1 and XXJL1 tomorrow. May be one of them will allow both HSUPA and voice calls. The i896 results have me thinking it is possible.
[Captivate Android Development] rajendra82:
You need to issue a mount command in terminal emulator or adb shell after an su. I use Root Explorer to do this on the screen, so I am not sure of the exact syntax. If you install voltage control and tell it to save stock settings (if you don't want to OC/UV), the /etc/init.d folder will get created as well. but it will still be r/o.
[Captivate Android Development] existz:
grab SGS Tools, and goto apply script then mount system r/w, then use terminal emulator to do.. mkdir /etc/init.d
[Captivate Android Development] Seanbest:
Will do thanks.

Sent from my Captivate using the XDA App
[Captivate Android Development] shane87:
I'm not sure if anyone has answered your questions directly, so here you go.

1. Does overstock use voodoo lagfix or speedmod's lagfix? If it uses voodoo, you are good to go. If it uses speedmod's lagfix, you better disable it or you will crash out of flash with an error and be stuck at recovery until you use odin to reflash to stock.

2. Voltage control 3.0.1 is for insanes kernel only. The latest voltage control, 3.0.3 is up on the android market, and it does work with this kernel. Some people have had trouble finding voltage control 3.0.3 on the market. If you can't find it, get appbrain, and find it there. One more note, for whatever reason, if you try to install 3.0.3 without uninstalling 3.0 first, you will get a package unsigned error on install. I have not tried to uninstall 3.0 first, so I am not sure if that works, but I do know that when I tried to update, I got a package unsigned error. I will be trying to uninstall 3.0 and then get 3.0.3 soon. And I will be flashing beta #7 in a matter of minutes.

[EDIT]

Ok, so I can confirm that for whatever reason, if you have voltage control 3.0 installed, it will cause voltage control 3.0.3 to not install. Uninstalling voltage control 3.0 will allow voltage control 3.0.3 to install. Not sure why, but it does work.

[/EDIT]
[Captivate Android Development] Seanbest:
Dropped those 2 files in init.d, but bln still starts on boot. Had to download bln app to disable. No idea how to tell if other one is working. Thr bln file is supposed to have no extension correct? The other is .sh.

Sent from my Captivate using the XDA App
[Captivate Android Development] shane87:
Just flashed beta #7!! Super fast flash and boot!! Awesome stuff exsitz, keep up the good work!!
[Captivate Android Development] pinoymutt:
I've done a little research on the topic, but for some reason I have run into the fabled "sleep of death" where my phone off turns off randomly (I tried both #5 and the recent #7) - no overclocking (left stock), but I've noticed both times I've installed it that during the evening I'll pick up my phone and it'll be completely shut off and the only way I can get it to turn back on is to do a battery pull.

When I turn back on, the 2 times I had the issue the battery was at 35% and 57%, so I don't think it was low battery issue.

I haven't had any issues with the stock kernel or Overstock (which is what I am on now). I'd really like to use the latest Voodoo sound, but obviously having a functioning phone is a little more important. When I was on this kernel it was really nice.

As I mentioned again -- I have not touched the OC settings (preferred to keep stock).

My Cap is one of the original batches (and I have never had the random shutdown issue on any other ROM/kernel) so not sure on this one.

Anyone else have a similar issue / ideas? I know the death sleep is common when you mess with the OC/UV settings, but wasn't sure if anyone else had any ideas when I leave it bone stock.
[Captivate Android Development] existz:
If u don't have busybox installed, install it..you can get the busybox installer in the market

Once I get done with the Onix kernel ill work on adding BLN to voodoo recovery
[Captivate Android Development] TheGrub:
I am having some problems downloading apps from Market today when connected to my work wifi. Starting downlaod, paused, starting, paused... unsuccessfull.

When shutting off wifi, it works. I never had any problems with that before. Could it be the Kernel / modem ? or only Market problems ? Or Wifi at work ?

Thanks.
[Captivate Android Development] tmusall:
I too have the same market problems. Can get it to work after many attempts. Only noticed this after switching to this kernel.
[Captivate Android Development] lactardjosh:
Just updated 5 apps over wifi and it worked fine for me.
[Captivate Android Development] rajendra82:
Market over wifi working fine for me too. Plus I also got amazon appstore and angry birds rio downloaded today, over wifi.
[Captivate Android Development] shane87:
It almost sounds like it may be your work has a proxy that is messing with market downloads. I have had no trouble downloading from market on wifi. I only download from market on wifi, since I only have 2g coverage at home. You might want to check on another wifi network.
[Captivate Android Development] Liv33viL:
B7 Feedback

Some feedback... on the B7

I flashed E-B7 yesterday morning and spent hours upon hours of testing all the functionality the kernel has to offer.

First: All files (Voltage Timings, BLN Disable) were installed to the proper places and permissions were set accordingly. I currently have V.C. 3.0.1 installed and using that. (as I know 3.0.3 has been released).

The flash went smooth coming off O.S. v1.1, no lagfix issues or loop-bound boots.

First flash booted with a lock limit @ 800 Mhtz - all voltages @ 0 MV and all states except for the 1120, 1200, 1300 and 1400 states enabled.

Rigorous testing for each individual state from 100 Mhtz to 1120 Mhtz was performed with stability tests in each state for approximately 30 to 40 minutes.

Benchmarks for each state were also tested and recorded utilizing NenaMark1, Quadrant Adv, Neocore and Linpack Pro. No speed testing for network or bandwidth was performed with the B7 as of yet. Battery life - still too early to determine.

The pages of tests and numbers are very long so I will not list them.

I found 1000 Mhtz to be the most responsive and powerful frequency with what I was able to test. Numbers, screen stutter and lag became apparent immediately into the 1120 state. Voltages were calibrated then zeroed - but still there was degradation at this frequency. 1200 was a little worse and at 1300 freeze. with any voltage timing. Recycled the device 5 times from a frozen screen before calling it an evening.

My device apparently didn't like the upper band frequencies over 1000, no matter the voltage timing.

Went through 2 1/2 charging cycles to this point.

Aside for the OC/UV testing, I had no WiFi issues (as many are stating) also I noticed that GPS loads on boot and remains active until manually disabled. This was the case with every reboot, whether from a screen freeze of just a refresher reboot.

I had not had this occur prior. (Just a note)

V6 Sound quality was feasible after making slight tweaks to audio settings and levels.

The best stability tests and benchmarks that I noticed across the boards were on first boot (without OC/UV) and a lock limit @ 1000 with stock voltage timings.

I use ADW Launcher EX and noticed some slight screen lag, application loading lag. I tried the same with the stock TW Launcher - same result. Not enough to make you want to skip the phone across the floor, but noticeable. (No fugu tweaks installed or enabled).

Call quality was the same as when on OverStock v1.1 which was very good. Bluetooth headset also clear and responsive - bidirectionally.

Overall, in my opinion, for my device - B7 is pretty much a balanced, stable at stock values, and has good features for what is currently available in a feature.

Just wanted to post my experiences thus far and give others some feedback.

Looking forward to seeing what's next for this engine...

Peace-
[Captivate Android Development] ewingr:
WiFi

It would be interesting to know success of test like this:

WiFi on and attached at home; leave where it becomes detached from the home router; after gone and detached from WiFi router, turn off WiFi; When returning home turn back on and see if it hooks.

the only difference from above for what I do is that it is all automated via Tasker. That is to say, when I get in range of my cell tower, it turns on WiFi; then when I get in range of my SSID Broadcast, it hooks to my router; When I leave the reverse happens: it automatically shuts off WiFi after I get out of reach of my local Cell Tower.

The problem I experience, on this and another KB1 kernel, is it when I return a second time, wifi goes to an error state, and typically requires a reboot in order to hook to it.

While I cannot say this has never happened on the I9000 kernels I've tried, I can say it hasn't happened frequently enough for me to recognize it as a problem.
[Captivate Android Development] TheGrub:
I will try some market downloads on wifi when I get home, but I doubt they have blocked anything on the wifi at work.

I'll let you know...

Other than that, this kernel runs really good and my bluetooth seems to be better than before.

Thanks