yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] tbong777:
Trashing a ROM is not saying "it doesn't work for me" or has bugs for me... Thats the truth. I have claimed that about many ROMS that EVENTUALLY became very nice daily drivers and donated many $20 dollar bills to those who create the ones I supposedly" trash" as well. Sometimes the developers want to be the top dogs and they rush out incomplete ROMS. Roms get worse rather than better in their riush to update. I like the slow update. The work is always better and far less buggy.

I seriously doubt anyone will be going away because their feelings are hurt....They move on to new devices and hand off their work to new developers. , This stuff is in their blood and the donations are helpful.

They read all the threads can and HAVE "defended" themselves if necessary always claiming "is a beta" . Some comments don't need a defense. I am not the only one who has had issue with Talon. Its a beta release. We know that but when people come in here and ask which ROM or Kernel is better they expect a honest answer from personal experience. IMO Talon is not ready for my device. Others love it. Maybe I will some day as well.

Existz does not need to defend that. there are many who are loving the bleeding edge kernel. I prefer stability over performance. THIS is the ROM "at this moment that provides that for me. Maybe next month or next week it will be DGS or Icezars again,

I am not afraid of driving Developers away. When one leaves another arrives and takes over the ROM, Development is a revolving door., Few like DG have a long rack record and the confidence of the community he cultured.

Developers need not take their ROMS so seriously. Thats why I refuse to DL CM7. They take their work far too seriously for it's result. Its not the second coming.

And with that $20 to Excal for his work.....Confirmation number: 1RN83790HF7071450.
[Captivate Android Development] Bren Dekura:
Yeah. Couldn't see it in my phone. Thanks
[Captivate Android Development] sinichi21:
so im assuming that the first list is for jvh right?
[Captivate Android Development] xpakage:
So far so good on the 1.2_JVB. Much faster that 1.1!
[Captivate Android Development] tbong777:
I wish Google MAPS wasn't the top user of my battery. Has to be an app using it.
[Captivate Android Development] xcaliburinhand:
Sure is. :-)
[Captivate Android Development] sinichi21:
yay :D giggle time to fly dang thanks so much xcalibur
[Captivate Android Development] AndrewKnow:
Thank you for your work xcal.
[Captivate Android Development] eep2378:
Thank you! Just flashed build 11.
[Captivate Android Development] mrhaley30705:
Do I need to convert to rfs before flashing?
[Captivate Android Development] justmart:
Thank You Xcal! The Best kernel. Period!

Sent from Carolina, P.R.

XDA - Where SOME people don't read the OP.
[Captivate Android Development] papilliond:
Anyone been able to turn bln on?
[Captivate Android Development] mrhaley30705:
No. maybe because it's not in this kernel
[Captivate Android Development] mark1962nc:
Saw your earlier question.....did you convert back to RFS and is zip compatible with CWM3?
[Captivate Android Development] Bren Dekura:
They haven't been able to get BLN working for GB yet. I'm sure it'll be everywhere when they get it working.

Sent from my Captivate
[Captivate Android Development] Bren Dekura:
Convert back to	RFS. I believe it'll work in CWM3.

Sent from my Captivate
[Captivate Android Development] mrhaley30705:
Hadn't done anything yet. I think xcal said a couple of pages back that it was cwm3, but read back to make sure.
[Captivate Android Development] papilliond:
I looked at the variants and there was one for bln.zip and I assumed it was included in the flashable kernel.
[Captivate Android Development] Nuskul:
I need some help here guys, flashed 1.2 and went into boot loop. tried using odin to flash 1.1 back on and odin said it failed now i have a phone and computer showing. Am I bricked?
[Captivate Android Development] HaiKaiDo:
Hmmm with all this talk of bootloaders im nervous now lol.
[Captivate Android Development] Dlev7:
Ya same the bootloader thing is the one reason I dont wanna flash. This is my second captivate and I dont want to hard brick it. I doubt Odin will crash and Iwill be careful to not disconnect but Im still nervous with the bootloader situation.

Could anyone confirm if this works on the one without bootloaders? And what are the benefits and possible setbacks of flashing without a bootloader.

Also I still am wondering when flashing should we have PIT and Repartition, or NO PIT and no repartition. They give two options on the OP of the i9000 thread.
[Captivate Android Development] loserskater:
For talk about bootloaders, look HERE

It talks about JVK so I'm not sure if the same thing is true about JVB. I'm going to flash WITH bootloaders so that way there's less chance of bugs.

Also, the only things to be scared about when flashing bootloaders is

-odin hanging

-computer crashing

-tripping or hitting the usb chord out of the phone

-etc...

All of the things that were "scary" before. So if you've never had problems with odin in the past then you should be fine. The only thing now is that if any of that happens when flashing the bootloader, a jig won't work so you've got a paperweight...
[Captivate Android Development] bclark:
I got everything downloaded and set up and then realized I am really not in the mood for craziness. Thank you again xcal but ill be holding off for a later build
[Captivate Android Development] xcaliburinhand:
I haven't ever had to reparation. However, I have always used the 512 pit and samsung roms. Usually odin will pull the pit currently on your phone and use that during the flash.

Edit: typo, meant to type 512.

Sent from a cell tower.
[Captivate Android Development] loserskater:
You've asked this question 3 times now... Slow down and read...

This is taken from that thread:

Re-partition is not a must, use it only if you need to change partition sizes on the device, but in most cases you will not need to repartition at all.​

Unless you're on CM7(which is the only time I've ever had to repartition) you should be fine with no PIT
[Captivate Android Development] Dlev7:
I have the 512 PIT, so when you flashed JVB did you use the 512 PIT no repartition? And flashed that, let it boot, then flash your kernel through Odin (*Auto Reboot or no), and let it boot up and your good to go?
[Captivate Android Development] studacris:
i beleive you did get an answer ... pay attention man! :rolleyes: :D
[Captivate Android Development] LucasBrazil1984:
Thanks a lot, Xcal. This feels like the beginning of great things.

However, I'm out of my depth here, so I'm gonna hold off for a while.

Sent from my Cappy using kickass FireFly 2.9, oc/uv Onix 2.0.5 and xda premium app.
[Captivate Android Development] oxlong27:
i flashed the one with bootloaders and all is well. could someone please provide me with an odin tar of the jk4 modem or direct me to where i can find it? thanks
[Captivate Android Development] oxlong27:
u dont need to repartition just flash the pda phone and csc
[Captivate Android Development] loserskater:
Just download it from HERE then open up PHONE_XXJVK.tar.md5 in 7zip(or whichever program you like) and swap out the modem.bin files.

Nevermind... doesn't work...
[Captivate Android Development] oxlong27:
thanks man
[Captivate Android Development] Dlev7:
Just flashed everything went PERFECT!

Thanks so much to everyone that helped me and sorry to those of you who had to help me : D haha.

GREAT WORK, this is really something
[Captivate Android Development] mrhaley30705:
If there a way to verify what pit you have?
[Captivate Android Development] blue265:
This is one of those cases where having two Captivates is really handy. I have my second cappy set up with this release and kernel and will be using it a lot over the next few days to try everything out. It seems fairly snappy for a stock firmware :)

XCal, you are the man! Thanks so much for your hard work
[Captivate Android Development] oxlong27:
guys you dont have to flash a pit file. anyway my 7zip isnt letting me swap my modem bin files could someone please post the jk4 tar for me:)
[Captivate Android Development] pparavas:
any advantages over existing cm7 for the captivate? or wait for sometime to get the next build ?:confused:
[Captivate Android Development] GGXtreme:
Not to get off topic, but I heard that Google had the Samsung update pulled for some issue. Any chance that such an 'issue' could affect the Captivate when compiled from Samsung's current source?
[Captivate Android Development] momulah:
Same here 7zip says not implemented when u try to swap or delete modem.bin! I want to use jl2!!
[Captivate Android Development] gocats7:
Does this kernel have tun.ko support for VPN?
[Captivate Android Development] boog:
Only soft bricked. Maybe see if you can get it to flash the kernel again. If not, maybe something went way bad and you will have to reflash your rom.

Make sure repartition is unchecked in odin when flashing a kernel.
[Captivate Android Development] MikeyMike01:
Awesome. :)
[Captivate Android Development] boog:
The op says that voodoo lagfix is included, but I can't seem to find it. the ext4 program complains that it isn't compatible, and I don't see it in cwm.

Am I overlooking something?

Other than that it seems quite nice!
[Captivate Android Development] mrhaley30705:
And you downloaded the one with voodoo? Weird.
[Captivate Android Development] Nuskul:
when reflashing rom using odin3, do i put zip file in pda? using gr12 by the way
[Captivate Android Development] mrhaley30705:
You don't use zip files with odin. It uses tar files.
[Captivate Android Development] GGXtreme:
Does this kernel have CIFS support?
[Captivate Android Development] boog:
Yup, grabbed both I9000_reoriented_vG.1.2_JVB.tar & I9000_reoriented_vG.1.2_JVB.zip

Left the novoo alone.
[Captivate Android Development] wibi795:
wich ones are for JVH and wich ones have lagfix
[Captivate Android Development] Bren Dekura:
It's pretty self explanatory....

One has JVB on end of filename and the ones with novoo in filename don't have voodoo. Read the OP.

Sent from my Captivate
[Captivate Android Development] rockosifraldi:
From the OP, look at the file names.... :D
[Captivate Android Development] krips2003:
I too got into boot loop, but I did backup the previous kernel and was able to flash back and it boot up without any boot loop, but I now I started getting the FC for go launcher. No I'm reflashing the ROM :(
[Captivate Android Development] boog:
Seems I did overlook it and missed something. Just checked the voodoo control app and it indeed does say lagfix is active.

Must have missed it when I had to chase my kids! :D
[Captivate Android Development] boog:
Man, that sucks!

I am by no means the expert here! I'm curious if you guys are flashing with sgs kernel flasher or using cwm/odin?

I have had some odd issues using kernel flasher, enough that I don't use it.
[Captivate Android Development] arffer:
I also was confused by this. Sure, the second set says 'JVB', so one can 'assume' that the first list by process of elimination are the JVH ones.

But I don't understand the reference to 'build #11-12' and 'build #13-14'. That not only implies that there should be 4 lists, one for each build, but I also did not see any build numbers in the file names.
[Captivate Android Development] krips2003:
oops!!! seems like I got the JVH instead of JVB and I'm sure others might make the same mistake. May be the JVH and JVB should be highlighted a bit more to remove any confusion.:confused:
[Captivate Android Development] boog:
AHHHH! I didn't think of that! I bet that would cause the bootloops!

Eventually I think most rom devs will move to jvh and some of this confusion will calm down.
[Captivate Android Development] olo567:
I think it's just the two versions (lagfix and no lagfix) for each base. I'm running lagfix JVH and it's #13 in About Phone.
[Captivate Android Development] rockosifraldi:
I think that is more for his reference... but I guess he is going to make some changes to the naming convention to address this... till then I hope people read the OP properly... :D... who am I kidding...:)
[Captivate Android Development] Bren Dekura:
So can you run a JVH kernel with a JVB rom?

Sent from my Captivate
[Captivate Android Development] boog:
They found a way to modify the jvb kernel to run on jvh. And they are NOT interchangeable! Looks like boot loops will happen if you try.
[Captivate Android Development] MikeyMike01:
I was running the old 1.1 kernel on JVH without issue...
[Captivate Android Development] topiratiko:
Ive tried twice to install the zip for jvh ( not labeled) and both times got stuck @ galaxy s screen. Am i flashin wrong one???
[Captivate Android Development] boog:
Interesting. I was tempted to try, but didn't because I was afraid of the difference.

What are all of the differences then? And if the jvb will work on jvh (but not the other way around), then why the need for 2 different ones?

I have been confused about this from the start lol

I thought it was something about the intramfs? I'm still learning, and will catch on to everything (well, many things) eventually.
[Captivate Android Development] tietherope:
I'm stuck at the Galaxy S screen as well, installing JVB.
[Captivate Android Development] dizx:
Flashed JVH version with Voodoo with CWM. Everything is humming along just fine at the moment. Great job!
[Captivate Android Development] echonc:
Flashed #13 with CWM everything is good so far
[Captivate Android Development] topiratiko:
Dizx which one is jvh???

#13? How do u know? Its not numbered. IM STUMPED
[Captivate Android Development] boog:
Not the one marked JVB :D
[Captivate Android Development] gocats7:
Downloaded the following two kernels and now Im stuck on the i9000 screen.

I9000_reoriented_vG.1.2.tar md5: cc9da761c342b7f2245842dd5e87fc33

I9000_reoriented_vG.1.2.zip md5: dbeb3b7402c2be1d05dab0b618c7d64c

Just going to reflash the talon kernel until I see what the deal is. Im on Continuum V5.4.1 and I had converted the file system back to rfs before I installed this kernel.
[Captivate Android Development] topiratiko:
Ive flashed the zip not marked jvb TWICE. TWICE stuck @ galaxy s creen. Voodoo toggle says voodoo on. Im still on talon kernel. WTF
[Captivate Android Development] echonc:
Yeah one not marked jvb is 13&14.

Now if it only was a light sabor too....
[Captivate Android Development] AndrewKnow:
When I flashed jvh my phone worked great for 5 minutes then just started bootlooping. Went back to jvb w/voodoo and it is working fine.

Using GR-12 with G1.2 #12
[Captivate Android Development] dizx:
I flashed this one.
[Captivate Android Development] topiratiko:
Thats the one i flashed and it sticks on galaxy s screen and gets HOTTT...were u on talons or xcals prior? Ext4 or rfs? STUMPED tried it 5 times now
[Captivate Android Development] smully1:
Same issue for me. Went into reboot loop after it initially worked. Using GR-12. Flashed the JVB instead and it is working fine.
[Captivate Android Development] mgfjd:
I flashed the kernel with no issues... recovery, flash, erase dalvik cache.. no problems...

Thanks for this kernel.. it is making believe in Ginger again.. I was about to give up and move on... small donation coming your way soon...

Thanks..

I am using the JVH Kernel with the new continuum JVH ROM... you can not use a JVH kernel with a JVB Rom such as GR-12
[Captivate Android Development] dizx:
I was on latest Talon.

Then went back to RFS, cleared Dalvik, flashed Xcal's kernel, rebooted.
[Captivate Android Development] topiratiko:
Guna try it exactly like that. How long was it on galaxy s screen? Thank you for yur help ill click thx wen i get to comp
[Captivate Android Development] spinz:
Fantastic to see an update to this kernel... and a jvh version.. Wonderful, wonderful work Xcal

Thanks you !!
[Captivate Android Development] dizx:
I don't remember exactly how long it was on the Galaxy S screen. However, it was on Continuum's bootanimation for maybe 2 or 3 minutes because Dalvik was cleared and I have a lot of apps.

Good luck!

Edit: Don't forget to enable ext4 with the Voodoo Control app after reboot. Not necessary, but it's nice :)
[Captivate Android Development] SkitchBeatz:
awesome.. Voodoo Lagfix + Gingerbread = blazing speed. Its like a new phone.
[Captivate Android Development] topiratiko:
ive been on galaxy s screen now for 11 minutes. sound right?
[Captivate Android Development] topiratiko:
14 now 10chars
[Captivate Android Development] topiratiko:
17 now........
[Captivate Android Development] dizx:
Waaaaay too long (at least from what I remember). You went back to RFS when still on Talon and before flashing Re-Oriented, right?
[Captivate Android Development] nakedninja42:
you dont need to start a new reply for a minute to minute update...

im somewhere around 15 minutes now, flash my using ODIN
[Captivate Android Development] topiratiko:
CLEARLY...3 replies updating my status is NOT that big a deal. Calm down. 25 minutes. I DONT think its working
[Captivate Android Development] topiratiko:
followed your steps to a T....30 minutes. LOL this is TURRIBLE. You know whats freakin wierd tho is when i boot into recovery after this fiasco its no longer 3.0 but 2.5..........
[Captivate Android Development] wonner:
I was stuck on the i9000 screen after flashing JVB with Voodoo. I went into Recovery, wiped cache and Dalvik and rebooted...all is well now.
[Captivate Android Development] dizx:
Pull battery, boot into Recovery, and then do what @wonner just did --- clear cache and dalvik-cache, then reboot.
[Captivate Android Development] dizx:
Yes, it will be CWM 2.5.x.x. (green menu)
[Captivate Android Development] topiratiko:
Still nothing. Gonna have to give up on this one looks like. Thanks for your efforts dizx
[Captivate Android Development] dizx:
Bummer. I feel like were missing something.
[Captivate Android Development] tietherope:
The voodoo kernel would not work no matter what. Reinstalled the ROM and used the non voodoo version.
[Captivate Android Development] mpanary_fako:
can somebody post a mirror for JVH with voodoo or attach it? every time i click on the link it's down and i'm sure it has to do with my school's wifi network, both phone and computer

thanks
[Captivate Android Development] nakedninja42:
thats how i feel, I cant get it to work at all. clear dav before flash on CWM 3 and after on CWM 2.5, flashed multiple times... nothing.

using C5.4.1
[Captivate Android Development] topiratiko:
How likely is it that its a corrupt file?
[Captivate Android Development] nakedninja42:
i figured ODIN wouldnt flash if it was corrupt, i also tried both voodoo and novoodoo and based on MikeyMike saying he got 1.1 to work, tried that too
[Captivate Android Development] topiratiko:
im gonna do something really retarded and try to flash jvb. brb
[Captivate Android Development] topiratiko:
Odd. Does the SAME thing. Maybe its an incorrect file?
[Captivate Android Development] codeblue315:
Did the same thing and worked like a charm for me. Running Continuum 5.4.1 and WOW this kernel is fast. Thanks a ton!
[Captivate Android Development] Nickel Dime Bay:
After we flash the kernel is there something else we should do? It all went smoothe. Is there a voodoo app or something?

I get a box saying a CF Root kernel was not detected" when i try to open ext 4 and tweak apps
[Captivate Android Development] topiratiko:
well its not a bad file if everyone else is dflashin it....IDEAS anyone?
[Captivate Android Development] wonner:
Voodoo Control app

https://market.android.com/search?q=voodoo+control+app&so=1&c=apps
[Captivate Android Development] nakedninja42:
FINALLY GOT IT WORKING!!!

Unfortunetly I had to go back to stock gingerbread (used jvh since I had it) and then flash C5.4.1 again. I pulled battery and then ODIN flash the voodoo and on first boot, I heard the lovely voice!!
[Captivate Android Development] Nickel Dime Bay:
ok cool so i dont have to mess with the tweak or ext4 apps anymore. This thing is running nice.
[Captivate Android Development] mpanary_fako:
^ ^ this ^ ^ . anyone?? please?? :(
[Captivate Android Development] dizx:
Go into Voodoo Control app to set ext4, then reboot.

Don't use the ext4 app.
[Captivate Android Development] :
Im on GR12. Downloaded and installed i9000 reoriented vG1.2 JVB. I wiped cache and dalvik, and it only took about 6-7 minutes total. All went rather smoothly and it was nice to hear the sexy voodoo voice again.

GB + Voodoo is freaking awesome!
[Captivate Android Development] Nickel Dime Bay:
Is it bad that i didnt hear the voice? Everything seems ok and i downloaded voodoo control and it says im on ext4 already. Loving this kernel so far.
[Captivate Android Development] Rikusaki:
Yeah, same here. Didn't hear the voice, but it obviously did its job. I went back to RFS before the flash and now it's back to EXT 4.
[Captivate Android Development] Rikusaki:
Wow.

I installed this on my sister's phone and now all the lag is gone! This was the reason why I switched back to CM7. The lag was horrible. But now it's completely gone with Lagfix. Awesome work.

This has convinced me to come back to JVB/JVH. :)
[Captivate Android Development] dizx:
I didn't hear any voices, but all readings show ext4 is enabled and running fine.
[Captivate Android Development] rquiett:
Great work. I had no problems updating using cwm. Loving the lagfix, definitely made a big difference in how the phone performs. Everything is all around smoother. Thank you
[Captivate Android Development] eep2378:
Wow, brain overload! Lol Now where exactly can these items be changed? Is there an app/program we need or is it simply going into sys/..... and changing values? Can I use root explorer?
[Captivate Android Development] jerkysh:
Pure virtual function called. Are you calling virtual methods from a destructor?

libc-abort abort() called in pid %d

somehow we're not dead?
[Captivate Android Development] :
maybe im missing something but the kernel says "voodoo color fix" but i downloaded voodoo control app from the market and dont see any voodoo color options in it?
[Captivate Android Development] GGXtreme:
^^^ 10char
[Captivate Android Development] kamp:
I just flashed 1.2 JVH Voodoo version to Continuum v5.4.1 through ODIN.

Everything went well, and after installing Voodoo Control from market, I can see Voodoo Lagfix is enabled

However, it seems tat Ext4 is enabled only for cache, dbdata and data although when I go into Lagfix preferences, Ext4 /system is ticked.

When I open EXT4 app, it also reports that system is on rfs (other partitions are on ext4).

I tried unticking that box, restarted, tick the box and restarted the phone, but it still looks like system partition is on rfs. Is this normal?
[Captivate Android Development] jlsesler:
this kernel is buttery smooth. I did have a problem. Some time during the night it shutdown. I am running cont 5.4.1 (jvh). Anyone else se this?
[Captivate Android Development] kant5t1km3:
sorry for the noob question but which one s the JVH one?Will the home haptic work on JVH also?

EDIT: Found Out
[Captivate Android Development] tcortinag:
One says JVB, sooooo JVH will be the other :rolleyes:
[Captivate Android Development] kant5t1km3:
sorry i just woke up :o
[Captivate Android Development] glitterballs:
You can actually set these with setCPU, but I like to use Gscript because I have a few scripts I run. This way, I don't have to open setCPU and change all the knobs one by one. But you can basically copy and paste what I wrote into the other post into Gscript and run it with su. I should note that you when you're changing the sampling frequency, you need to echo something (a multiple of 40000) to the knob location (ie, echo your-sampling-frequency > /sys/devices/.../sampling_frequency).

Anyways,

But it's one of those things that if you set the sampling frequency too high, you'll have some latencies when you're using the phone. But so far, with ext4, a 400000us sampling frequency seems pretty usable, and then you can end up with CPU utilization looking something like this:

CPU at the two lowest states almost 90% of the time. :D