yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] xcaliburinhand:
I plan on devoting some time tonight to recovery, since the lack of it is starting to get annoying. Should be less than an hour of work.

In addition, I will throw together an update.zip with the correct melfas_touchkey.kl

-x
[Captivate Android Development] neptronix:
Thanks Xcal. Do you have IRC channel?
[Captivate Android Development] gudduseon:
thanks home key is working
[Captivate Android Development] xcaliburinhand:
I don't have a specific channel, I usually pop into a few different ones on freenode in the evening.
[Captivate Android Development] kevinjmoore:
base perception ii beta 3 gb rom...any takers on this issue?
[Captivate Android Development] bruzski:
hi all,

I have the reoriented vG.1.2 kernel with GR-12 gingerbread running on my GT-I9010 armani phone and have successfully change the startup bootlogo inside the (param.lfs) but can someone help my change the i9000 logo what resides inside the kernel to something more suitable? :)

thx
[Captivate Android Development] loserskater:
You would need to build the kernel from source.

@Xcal, the link to your github has an extra "http://%20" in front of it. Thought you might want to know
[Captivate Android Development] BoldFace:
I'm also curious on how to do this. All my attempts have failed.
[Captivate Android Development] nakedninja42:
Download the Voodoo App from the market, you can disable it there the easiest. Another method is placing a txt file named disable-lagfix I think in the voodoo folder found on the SD Card. Someone will confirm the file but using the app is the easiest method.
[Captivate Android Development] BoldFace:
Is this only available with the paid version of the app? There is no option in the free version.
[Captivate Android Development] nakedninja42:
I have the paid app but installed the free version to verify. The Voodoo Lagfix options are in both programs. You need to have a kernel installed that supports Voodoo. Which kernel version did you grab from the OP?
[Captivate Android Development] studacris:
Yes the file method is correct. make a file (or folder doesn't matter) in the voodoo folder on the sdcard... Name it disable-lagfix. Actually all the app does is make that file for you :)

You can do it with the free version of the app... Are you sure you have the voodoo version of the kernel?
[Captivate Android Development] topiratiko:
Theres also voodoo toggle reboot app on marked. A doll with pins works too

Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.
[Captivate Android Development] nakedninja42:
Am I suppose to stick the needle in the head or heart, can't figure out where the lagfix is?!? ... or is it the feet?
[Captivate Android Development] BoldFace:
I'm pretty sure, the app says that the ext4 lagfix is active, however I can't revert to rfs. I've tried creating a "disable-lagfix" folder in the voodoo folder and all that happens is the folder is removed, but lagfix remains lol.
[Captivate Android Development] studacris:
Been there...uninstall the app rehash the voodoo kernel...then either place the file or install the app again and try that.

If that doesn't work flash back to stock gingerbread and proceed from there.
[Captivate Android Development] bruzski:
are the reorient kernel sources available somewhere ? :( can someone point me out to them or possibly help me with adding a logo file inside the kernel
[Captivate Android Development] studacris:
umm idk have you looked in the op, or below this sentence? :p

GIT
[Captivate Android Development] bruzski:
yup i'm looking inside the sources but cannot seem to find the logo files... lol :o

edit:

me thinks I found it, is it called initlogo.rle ??
[Captivate Android Development] existz:
The kernel boot image is actually a .h (C Header file), its located...

drivers/video/samsung/logo_rgb24_wvga_portrait.h

I have a repo on my github (Samsung Logo) that will help you convert a png to .h
[Captivate Android Development] Exostenza:
Damn. I really want to get the JV5 modem on, but all I can find is a CWM3 file for it. Any ETA on the new version of this kernel?
[Captivate Android Development] xcaliburinhand:
No eta, an eta tends to be a curse. BTW, cwm 2* supports cwm 3 scripts.

Sent from a cell tower.
[Captivate Android Development] Exostenza:
Oh sweet, thanks.

Also

really

looking forward to the next release!
[Captivate Android Development] bruzski:
thx a million :p hopefully i will not brick my phone, lol
[Captivate Android Development] loserskater:
A common misconception is how you "brick" your phone. Flashing kernels won't brick your device. As long as you can get into download mode from the phone being off, you can always use Odin to flash another kernel, or worse case scenario go back to stock.
[Captivate Android Development] jerkysh:
would it be possible to integrate the voodoo color fix in a future release?
[Captivate Android Development] ahkahkahk:
thanxxxxxxxxxxxxxxx man

it works fine with the jvpjv6 ginger rom (the arabic rom)
[Captivate Android Development] loserskater:
It's in the current release now. Read the "Whats included" section in the OP.
[Captivate Android Development] bruzski:
hiya existz,

I successfully saved a logo to a mylogo.h file (gimp), but i'm can't find a correct win32 version of g++ so i am unable to change the it to logo_rgb24_wvga_portrait.h :(
[Captivate Android Development] shane87:
Hey, I think you posted to the wrong thread. This is xcal's thread, not existz's. Also, you can't compile the kernel, or any android kernel for that matter, on a windows machine. You uave to use linux, ubuntu is preffered. So I don't think you will be able to change the boot logo without using a linux machine, since the logo is compiled into the kernel. (Anyone who knows I am wrong, feel free to jump in and correct me)

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Android Development] existz:
He's actually compiling from Xcals source, so probably good to post here. I was just helping him out with converting a boot image for it.. But yea, you can compile a kernel on windows, sztupy had a vm compiler around here some where, but I don't know if it will do what's needed for converting png to .h
[Captivate Android Development] shane87:
Ahh, I see! Well, I was basing the not able to compile on windows on the fact that the aosp says only linux should be used for compilation. I guess that's what I get for listening to os developers. I should have learned from listening to microsoft, lol.

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Android Development] bruzski:
I will hunt down sztupy's compiler otherwise it's getting to much OT

@existz, thx for helping me out! :)

edit:

think this is the thread!

http://xdaforums.com/showthread.php?t=1022407
[Captivate Android Development] MikeyMike01:
There are three things that will brick your phone:

Corrupt bootloaders

Mismatched bootloaders

Hitting it with a hammer

Everything else is at least JIG-able.
[Captivate Android Development] studacris:
also severe water damage and

a JIG-able situation with a busted usb port :)
[Captivate Android Development] 4-2ndtwin:
^ This will also cause a brick....:D http://www.youtube.com/watch?v=mcr2uWkJkzI&feature=player_detailpage

Sorry, couldn't resist.
[Captivate Android Development] andrewdroid:
I think this kernel should be updated with CWM 3, because as it stands with 2.5, you cannot flash Continuum directly using this kernel, otherwise your apps will delete on reboot.

However, it works very well with Continuum *after* you flash that rom.
[Captivate Android Development] Exostenza:
He said CWM3 is coming in the next release. We all just have to wait and be patient even though we do not want to.
[Captivate Android Development] andrewdroid:
Oh good, so it's on the agenda then.
[Captivate Android Development] nbarsotti:
XXJVP 2.3.4 compatibility?

I would love to try out the new 2.3.4 leak, found here, http://xdaforums.com/showthread.php?t=948790

Can anyone confirm if the xcal kernel will work or not?
[Captivate Android Development] zelendel:
It was just posted that it will most likely not work as it is a different Linux kernel version
[Captivate Android Development] xcaliburinhand:
That's what I thought of after reading "hitting it with a hammer".
[Captivate Android Development] xcaliburinhand:
What version are they using for 2.3.4, I thought it was still 2.6.35?

I haven't seen a diff of the new initramfs yet, but if they didn't do any major changes there is a good possibility this will work with 2.3.4.

-x
[Captivate Android Development] nbarsotti:
Since there is no source for i9000 2.3.4 is there any hope of building a reoriented kernel?

(You beat me with your reply)

Sent from my SGH-I897
[Captivate Android Development] zelendel:
To be honest I have not looked deep yet. I know that any kernel for the captivate that you try to flash to it get a too big error with CWM and odin.
[Captivate Android Development] kant5t1km3:
i love that commercial!!!
[Captivate Android Development] know8677:
OK. Don't blast me here because I know there's an answer to this question but I can't find it.

I just went to Mosaic 3. I want BLN to work. I believe flashed the correct kernel for this:

"vG.x.x_novoo.tar = standard kernel, installed with ODIN, includes BLN, no voodoo lagfix"

BLN control says I don't have the correct kernal mod installed.

I've seen something about a services.jar previously, the OP doesn't mention it anymore. Plus, I wouldn't know what to do with that anyway.

Any help?
[Captivate Android Development] topiratiko:
Shoes can also prove deadly. See infuze commercial.

Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.
[Captivate Android Development] blutruck:
If you're using Mosaic 3 you can download this and install through CWM. I've done it that way and BLN works fine. This will install the kernal that has lagfix enabled.
[Captivate Android Development] know8677:
Thanks. I'll give that a try.
[Captivate Android Development] existz:
You are correct, the source we have now will work with 2.3.4, I haven't looked at the initramfs diff yet either, but I did use the stock jvp initramfs on my kernel and it does work.. so initramfs changes is all that's needed .
[Captivate Android Development] majinzen:
Well... JVH with bln doesn't work with JVP unfortunately. Tried all day to no avail. Have had to use darky's kernel for now. Hope we get a JVP soon but, obviously, at your convenience is soon enough for me.
[Captivate Android Development] no clue:
+1.

Unfortunately, I only trust xcaliburinhand!!!!

So I will wait till your magic patch before upgrading to 2.3.4.
[Captivate Android Development] xcaliburinhand:
G.1.3 is up.

I'll start looking at 2.3.4 support.
[Captivate Android Development] Barbarian:
Nice, thanks. :D
[Captivate Android Development] sfernandez:
Will 1.3 work with JV9?
[Captivate Android Development] zelendel:
Thanks again for all your hard work. Looking forward to you 2.3.4 version

Sent from the Bat Cave
[Captivate Android Development] xcaliburinhand:
Yup, G.1.3 will work with anything G.1.2 worked with.
[Captivate Android Development] tbong777:
WOW Maybe have to go back to a GB ROM after all.....Had nothing but issues with Talon. your Kernels have always been super stable
[Captivate Android Development] geokilla:
As much as I like Talon, Xcal's kernel just feels more refined and smoother for some reason despite not having as many features and as much RAM as Talon.
[Captivate Android Development] ChanceM:
if you want the additional ram you can try the kernel in the Serendipity VII thread. Its based off Xcals with a few additional mods. Xcal didnt mean to hijack your thread just offing a solution. I will remove this post if you wish.

ChanceM
[Captivate Android Development] jerkysh:
will it work on JVP or JVO?:)
[Captivate Android Development] xcaliburinhand:
Working on a JVP (GB 2.3.4) kernel. So far it looks good, haven't run it through all the tests yet.

One thing that does need to be fixed is the boot animation service, it is not being killed properly. Should be a relatively simple fix.

-x
[Captivate Android Development] trekie86:
Zel, does that mean that Mosaic V may be 2.3.4 based?
[Captivate Android Development] xcaliburinhand:
Honestly, Samsung is to thank for the smoothness of the kernel. I try to leave the kernel as close to the stock I9000 kernel as possible.

Post can stay, no complaints from my side.
[Captivate Android Development] tbong777:
Put Continuum on the wife's phone... ( she is the new beta tester for marginal ROMS) Don't care for Talon. I seriously don;t think these devices need all that OC/UV PC related stuff. Which kernel will work with JV0 if any? I am taking a break from the GB ROMs for now. Can't find one that runs as well as Froyo yet.
[Captivate Android Development] jlsesler:
Is there a change log for 1.3? I looked around and don't see it.
[Captivate Android Development] singlebeam:
right under the dl links for v1.3
[Captivate Android Development] nbarsotti:
Car dock charging? feature request

Hello Xcal, I am not sure if my change request needs to happen in the kernel or in the ROM, but I thought I was ask here first. I am currently running stock JVP and the Dark Core kernel, but what I’m about to explain also am happened with stock versions of JVB, JVH, and JVO while using your kernels. When the Captivate is connected to the Samsung car dock the battery will show "Charging" when looking at the status, but when the Captivate is connected directly to the wall AC charger, car DC charger, or to a computer the battery status will show "Charging (AC)" or "Charging (USB)". Also when looking at the Battery Use graph, the time spend connected to the Samsung Car dock does not show as time spent charging in the bottom section of the screen.

The problem this creates is that when a ROM or a app is supposed to keep the screen on while charging it does not because the Samsung Car dock is not a recognized charging state. Can you make the kernel recognize the Samsung car dock as "Charging (AC)" rather than just an undefined "Charging" state? If this is a ROM issue and not kernel related please let me know. Thank you.
[Captivate Android Development] jlsesler:
Wow. Thanks. Don't know how i missed that :p
[Captivate Android Development] white00gt:
Hey x-cal thanks for your hard work, just flashed your new Kernal with Serendipity 7, with Chance's version i had an issue with wi-fi toggle and now with your new version wi-fi has same error but forces system re-boot

Just a heads up!
[Captivate Android Development] olo567:
Any of the JVH kernels (including the new 1.3 here) will work for JVO.
[Captivate Android Development] jgaviota:
Thanks xcal for the new version and for the upcoming JVP!!!

One question, over at the i9000 forums [Ramad] advises to flash both bml7 and bml8. What is your take on this?
[Captivate Android Development] loraque:
He knows about this one. Xcal is the one that hacked car dock support into 2.2, so we bugged him about this one too. In addition to what you note, the battery stats are always incorrect as well, since the stats think the phone is still discharging when in the car dock, even though the rest of the phone knows it is charging. It does the same thing in CM, so not limited to Samsung ROMs.

As a work-around to the screen timeout issue, I use tasker (not free) to change the display timeout to an hour when connected to the BT in my car, and it sets it back to 1 minute when it leaves the dock. Nothing else works that I have seen.

Xcal mentioned he MIGHT be able to do something about it in the kernel or with his dock-redirect app. But then, there are a great many sources changes coming about, and I would be hesitant to put valuable dev hours on anything when the source is changing every other day ;).
[Captivate Android Development] zelendel:
It does.

Sent from the Bat Cave
[Captivate Android Development] jo7878:
can i ask does update-home_button_fix.zip work with jvp yet.many thank.
[Captivate Android Development] nbarsotti:
I am using the currently available download on JVP and I am not having any issues.
[Captivate Android Development] xcaliburinhand:
Wi-fi reboot issue normally occurs when the ROM is based on JVB and the kernel is based on JVH. I'm guessing Serendipity is based on JVB if you are running into these issues.
[Captivate Android Development] xcaliburinhand:
JVP kernel for those who are bored and looking to flash.
[Captivate Android Development] electroau:
Xcal...as a bluetooth user, something I have noticed, the different modems have different mic gain settings in the audio engineering menu. I have many people complain of sounding muffled on the newer modems and tracked it down to the higher mic gain settings. Jk4 is clear and had less gain. I have lowered the gain on the newer modems, and it works until I cycle the power, then it loses its change and returns to the higher default values.

Is this something that can be fixed?
[Captivate Android Development] existz:
Theres actually another wifi reboot issue, if you toggle wifi on/off a few times it will reboot, it seems that for some it can happen just enabling/disabling it once, others it might take awhile, but it does happen.. Quite a few of use verified the same problem on stock roms and stock kernels, it seems the issue is there with every kernel. For some users it doesnt happen that often, but if you toggle it on/off enough times it will reboot, once it does, then its very easy to reproduce, and then starts to happen every other time or so..seems some kernels are easier than others to trigger, but like i said, its even there on stock kernel/rom (verified on jvh, jvo, and jvp stock roms and kernels)
[Captivate Android Development] tkjeeper:
So xcal, I'm confused, which kernel is optimum to run with the latest mosaic IV? It's jv9, I've run 1.3 and now 2.0, does it matter? I don't see much difference btw the two. What's your recommendation?

Sent from the frozen tundra known as Canada.
[Captivate Android Development] RichMD:
vG 1.3 no-voodoo running smoooooth on Continuum 5.6

Great job - thanks!:D

I've never tested it but do you think there is any noticeable difference for battery life when using a lagfix such as voodoo or not? It is so smooth without voodoo I don't see a reason to enable it and I've seen some people say RFS is better for battery life than EXT4.
[Captivate Android Development] geokilla:
I'm confused too. Also wondering if there's any difference between JVP and JVH kernel.
[Captivate Android Development] tkjeeper:
Yeah, and what about jv9

Sent from the frozen tundra known as Canada.
[Captivate Android Development] geokilla:
There isn't a JV9 kernel. I just realized that JVP = Android 2.3.4. JVH is sitll Android 2.3.3.
[Captivate Android Development] tkjeeper:
So if M IV is jv9 based framework, what do we use?

Sent from the frozen tundra known as Canada.
[Captivate Android Development] nakedninja42:
You can use 1.2 or 1.3. Difference is 1.2 has CWM 2.5 and 1.3 has CWM 3.
[Captivate Android Development] crusecontrl:
I'm using 2.0 without any issues and im on MIV
[Captivate Android Development] tkjeeper:
Me too, so far.

Sent from the frozen tundra known as Canada.
[Captivate Android Development] F1reEng1neRed:
Would really like to give this a try...

For the JVP kernels are we supposed to do anything with the initrd_files?

Also, does the home button fix still need to be applied?

Thanks.
[Captivate Android Development] pinoymutt:
Hi Xcal, with JVP 2.0 BLN, I am getting a blank screen when trying to boot (currently on Simply 2.2). I remember Talon and Dark Core having similar issues because there was an issue with custom boot animations on JVP kernels.

Anyone else experience this?

EDIT: It appears after the first boot, the screen will go blank for several minutes after the Android boot animation comes on. Subsequent boots do not have this delay. I saw this referenced in the Apex thread as well.

So just a note if you flash the JVP version and your screen goes blank for a while -- just let it sit and it seems to work.
[Captivate Android Development] climber1872000:
I am now having issues with my phone waking up from deep sleep. I will swype my thumb to unlock the sgsII lock screen and the screen will become completely unresponsive for 3-5 seconds. I flashed back to the latest dark kernel and could not recreate the issue. Besides the above issue, I found the JVP kernel version to be very quick and responsive.
[Captivate Android Development] arffer:
As Xcal mentioned, the new JVP kernel does not yet support boot animations.

So, where you watched an extended looping of the boot animations with non-JVP kernels while the davlik cache was built, with this JVP kernel with no boot animation you instead get an extended black screen while the davlik cache is built.
[Captivate Android Development] nakedninja42:
That's weird, I am using the Android Particle boot animation from Docs kitchen with JVP kernel
[Captivate Android Development] no clue:
THANKS AGAIN to xcaliburinhand's new vG.2.0,

it works perfectly with official 2.3.4 JVP ROM!!!!

1. Odin flash Official JVP

2. odin flash vG 2.0

3. Install buttom_fix zip

Working perfectly~

I am not a fan of custom ROM, and xcaliburinhand's magic just happen to be really easy for me to try every i9000 at will. :)

Why there isn't any similar magic patch at Vibrant forum?
[Captivate Android Development] pinoymutt:
Thanks, that's what I eventually figured out, since it did eventually load, but if I hadn't read it in another forum I may have just given up and went back to DC or Talon, so I figured I'd bring it up as maybe a possibly note for the OP so that folks that have never seen that behavior don't prematurely give up :D
[Captivate Android Development] xcaliburinhand:
I believe Samsung modified the init sequence slightly from past builds. In the past when the phone was ready, init would kill the boot animation service. Samsung's boot animation now seems to be do some check and killing itself, so I believe they dropped the kill from the init process. (I have no proof on any of this, just basing it off of what I am seeing)

In the past I could just call the AOSP boot animation binary instead of Samsung's. However, with the change the AOSP boot animation binary will just keep running. So the phone would be ready in the background but the animation would be holding the foreground.

To resolve this, I have a script that runs instead of the animation. It starts the animation binary, sleeps for 15 seconds, then kills the animation binary. Under normal boot, this should look normal. However, since the first boot after installing new kernel/rom builds the dalvik cache, the boot process takes longer than 15 seconds. This causes the blank screen as the animation has stopped but the phone is not ready for the user yet.
[Captivate Android Development] white00gt:
Serendipity is based off of JVH, not sure why it did it- started to work today just getting same issue I had with Chance M's kernal it gives me a wi-fi error
[Captivate Android Development] MikeyMike01:
xcaliburinhand is awesome, and you can't have him.

Sent from my Infuse 4G
[Captivate Android Development] :
what do I need to do with initrd_files
[Captivate Android Development] majinzen:
With the new 1.3 kernel my android os is going nuts. Battery use 20% and draining like crazy. Anyone else have this problem? Any suggestions?
[Captivate Android Development] xcaliburinhand:
Nothing, unless you are building your own kernel.

Have you used Google Maps or Google Music lately? Whatever background processes they spawn tend to chew through battery even after the app is closed.