yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] viny2cool:
I might sound total noob and really stupid asking this question, but I dont understand how to apply that fix on my assonance 3.1 Rom..

Should I just download .zip file named "xcaliburinhand/I9000-Reoriented-for-I897-Froyo" and install it using recovery mode? should i do odin one click stock flash before doing this?

Sorry for stupid question...New to flashing business....
[Captivate Android Development] xcaliburinhand:
Eeek, I have a good idea of why, sit tight should have a fix tonight.

The recovery revert is due to using the new Voodoo, should be a simple fix.

-x
[Captivate Android Development] loserskater:
Is this headset fix for button control too (play/pause music) or just mic?
[Captivate Android Development] tsan81:
geez....this is exciting....waiting for the fix for the handset mic issue....can't wait to be able to use my wired headset for everything again!!!!
[Captivate Android Development] designgears:
Appears to be, I can hold the button and music comes up, which is odd because I always thought that would launch the voice commands app. Guess I will have to tweak that :)

Beta testers have reported 3rd party ones working with multiple buttons.
[Captivate Android Development] HeRmAyNe-MuNsTeR:
Awesome, this is exciting :)
[Captivate Android Development] loserskater:
Awesome news! This was the only thing stopping me from using reorient kernels.
[Captivate Android Development] tytdfn:
This was awesome news for me until I remembered that my headset broke T.T lol I never catch a break. Great Work excalibur great to see you back!! Where you been?
[Captivate Android Development] xcaliburinhand:
Here and there, spent some time in Vegas for work and a much needed vacation in Jamaica. Other than that been working on this headset headache.

I'll have to see what kind of side projects I can get my hands into now.
[Captivate Android Development] xcaliburinhand:
2.1.5 should be good to go.

Give it a whirl and let me know if I broke something else. :-)
[Captivate Android Development] designgears:
Shot me a PM when you update the github :)

Seems 2.1.5 mic is working!

So nice to have my headset back...

thank you sir!

edit---

nvm, its up :)
[Captivate Android Development] Philux:
I am using AXURA RC1 as it came after flashing with Clockwork. To use this kernel what do I need to do? (Still learning) Do I use clockwork to flash after AXURA RC1 has already been flashed?
[Captivate Android Development] hansmrtn:
Im very curios about this kernel?
[Captivate Android Development] Philux:
Can you tell me the best method to flash it on your port/Rom

Have not messed with Kernel flashing yet but itching to start. Just don't wana learn everything the hard way my first go around.

Is I9000 reoriented v2.1.5 compatible with modem on RC1
[Captivate Android Development] hansmrtn:
I really wouldnt know if it was compatible. So I will look into it, but if It is, I Would love to help :D
[Captivate Android Development] thecellx:
I tested axura and dillg disabling first lag fix of setiron... and the.phone start and infinite cicle of restarts. The fix: include the kernel on the .zip itself and it worked with both roms.

You just need to replace zimage from xcalibur into the updates folder on your rom, zip, and flash as usual.
[Captivate Android Development] techjeep:
Kernel Version....

I am crazy excited about getting to use my headset again.

This is the first time I've ever tried flashing a kernel outside of the ROM. Just to be sure, I'm showing Kernel Version 2.6.32.9 reoriented #71 in the About phone menu. Is that proper for this kernel?
[Captivate Android Development] xcaliburinhand:
Yup, #71 is correct unless you want backlight notifications which would be #72.
[Captivate Android Development] tytdfn:
I'm very curious to know what the problem was.

Also i don't know how deep your linux knowledge is but i would (humbly) suggest you either check out the CM project that aery and coolya are working on, which they have been doing a fantastic job on so far, or you could also see if you could direct the community based rom that's starting to come up.

Again just suggestions, but I'm a very big fan of your work, and I'm glad you're back. lol your reappearance made me wonder where unhelpful went. Kinda off topic but I wish the froyo source would drop so that he would show up like he said he would.
[Captivate Android Development] hansmrtn:
Good news! This kernel is going to be in A2.1!
[Captivate Android Development] tytdfn:
Sweet Just what I wanted! I loved axura but sadly it lacked the Voodoo 5 magic. Now its gonna be awesome!
[Captivate Android Development] thecellx:
???????......mmmm....what????
[Captivate Android Development] xfernand:
My favorite: Correct Headphone/Speaker logic.... :D:D:D
[Captivate Android Development] xcaliburinhand:
A little background, within the Galaxy series as with many other smartphones are banks of GPIO (General Purpose Input Output) interfaces. These are used to to interact with the other parts of the phone. A couple examples would be turning the screen on and off, turning bluetooth on and off, controlling what turns off when the phone goes to sleep, etc.

From what I can tell, every phone within the Galaxy series other than the captivate (possibly due to the A1026 chip) uses GPJ4(2) to enable mic bias on both the handset and headset microphone. Mic bias may be familiar to anyone who had an old sound blaster card with jacks on the front of their computer case. Basically mic bias provides the power needed for the mic to actually work. In the case of the captivate, GPJ4(2) is still used to control mic bias to the handset mic. However, GPJ4(4) is used to control mic bias to the headset mic. Solution is to use GPJ4(4) instead of GPJ4(2) when interacting with the headset mic.

In addition, to changing the mic bias for the headset, the interrupt used for sensing the headset button is pushed changed from 30 to 18. This could be due to the pins being different between the Captivate and I9000 phones (as mentioned by Whipon in post 560).

As a side note, the handset mic stopped working in v2.1.4 because I basically commented out the initialization of GPJ4(2) not realizing it was still used for the handset mic. Also, the reason this took so long to find is within the Eclair code the section that chooses the right GPIO for the headset makes it decision based on hardware revision. From the hardware revision that was appearing in the log it should have used GPJ4(2), so I dismissed this as a possibility. In essence I spent a lot of time looking at everything else and eventually wondered my way back. Turns out the hardware revision being used to select the correct GPIO is not the same that appears in the log.

Enjoy!
[Captivate Android Development] Mac11700:
Awesome..great work on getting this fix...

Could you tell me if there is anything in your findings that would be the cause for the constant wi-fi scanning that is occurring with the Captivate running a I9000 rom. I am unsure if it is the kernel or frame work or some other app like Flash 10.1 or even something for video chat that is causing this over the stock Eclair kernel..

Mac
[Captivate Android Development] Jay120171:
Thanks a ton for your work dude! Your kernal lets me have all kinds of fun trying out i9000 ROM's and is greatly appreciated. I am not going to pretend I know how hard it was to fix the headset issues but I do know your work is being used in a lot of ROM's and kernal mods.
[Captivate Android Development] xcaliburinhand:
Hmm, I am not sure I fully understand but the ROM usually handles the polling for new wifi networks. As far as I know the kernel just answers the call from the ROM and provides the list of networks in range.

Possibly un-checking "notify me when an open network is available" in the wifi settings will reduce how often it scans.
[Captivate Android Development] jhnstn00:
Working on version 1 fine. Thanks for heads up.

Axura CE RC1 w/ excalibur 1.2.5, i9k camera fix, Smooth as silk..
[Captivate Android Development] Mac11700:
Nope...no luck on that..

I've been looking through some different roms and their buildprop. looking for what their wifi.supplicant_scan_internal = values are in hopes of increasing the times to atleast slow things down on how often wifi is actually scanning...I know google has is =15..and I've been trying to increase this to halt some of the battery drain..Didn't know if you knew anything about it or not..that's all..

Mac
[Captivate Android Development] jgaviota:
problem with user bootanimation?

Hi xcaliburinhand,

Great job with 2.1.5, just one question about user bootanimations...

I flashed it on top of Killer23 Doc V9 and now when it starts it displays the standard animation and on top of it the animation of that rom. Is it a problem with the kernel or with my setup?

THANKS again!
[Captivate Android Development] xcaliburinhand:
In theory, that shouldn't be possible. The only thing I could think of that would cause this is the ROM somehow injecting its animation into the boot process.

Just double-checked the code and rebooted my phone, only the custom boot animation appeared.

Sorry, I can't provide any better help.
[Captivate Android Development] tytdfn:
I wonder what your reaction was when you noticed what the problem was lol. Must have been an epic facepalm :D

Oh and isn't that further proof that the software department at samsung sucks? They can even do logging right.
[Captivate Android Development] no driver:
I'm having the animation issue too. I'm running Tayutama's 1.0.2, which is based on JPM, along with your kernel and the JK3 modem. I think I've got the boot animation that you included with 2.1.3 (shiny sideways android), but after flashing 2.1.5 (BLN if it matters) this morning I've got that playing on top of the Galaxy S animation.
[Captivate Android Development] raychang:
Voodoo seemed not kicked in for 2.1.5

I tried the 2.1.5 with several methods, Odin, CWM for the new kernel or CWM for the new zip composed by the Tayutama 1.0.3 with the zImage of this 2.1.5 for a newly flashed phone from stock JF6. All of them gave the Quadrant Score of about 1000 to 1100. I noticed that Voodoo did not seemed to kick in for 2.1.5 (no voice said converting RFS to ext4).

Does anyone have similar problems?
[Captivate Android Development] xcaliburinhand:
Okay, that explains a bit more. The shiny android text is the default (i.e. no custom animation in place). I dug into the Voodoo scripts and found that if Voodoo does not see a custom bootanimation in /system/media/ it enables the standard Galaxy animation. This would give the dual animation effect you are seeing and also explain why I am not seeing it.

The voices do not appear to work on the captivate, still looking into why. If on first boot it sits at the Galaxy screen for a while, it is converting. You can also double-check by looking at the voodoo logs on your sdcard.
[Captivate Android Development] no driver:
Thanks, I'll find something fun to stick on there to get rid of that then :)

Please add something about this to the first post! I disabled voodoo to make a backup before applying 2.1.5 and when I tried to reapply voodoo it sat at the boot screen without any sound for so long that I thought something was wrong and pulled my battery. It took a while to get it back up and running again after all that. If I'd known there wouldn't be voices I would have waited for it to finish up.

All that said, I really do appreciate your work on this kernel, and I can't wait to try my headset out when I get home :)
[Captivate Android Development] zippox180:
Rocking this kernal on assonance flashed via cwm. Freaking insanely fast and smooth. Excellenent work xcal always loved your work. Keep it up. 0 issues thus far.:D
[Captivate Android Development] raychang:
xcalibur,

It did sits at the Galaxy screen for a while, but the Quadrant score is still around 1000 to 1100 after it boot up. I did another reboot after that, the Quadrant score is still the same.
[Captivate Android Development] xcaliburinhand:
Sorry to say I like a few of the other devs find quadrant scores to be useless. I'm afraid I can't help you in that respect.
[Captivate Android Development] jgaviota:
Any way to turn the shiny text into a bootanimation?

Thanks!
[Captivate Android Development] bts0uth:
xcaliburinhand, any chance the headset fix could affect handset and speakerphone volume being low? Even at max volume I have to tell people to speak up because I can't hear them.
[Captivate Android Development] ComanderTaco:
Bootanimation issue........

Im running Tay's I9000 rom and i just deleted /system/media/bootsamsung.qmg with root explorer to get rid of the double boot animations. Deleting the one i did will keep the simple android shiny one and removed the standard galaxy one.

Other that that this is a friggen sweeeeeeeeeeeeeeeeeeeeeeet setup and i will name my first born Xcalibur Tayutama (insert my last name here) in honor of you guys. The combo is the smoothest setup I have tried I F ing LOVE IT.

One thing i did whant to ask however , reading through the voodoo log i noticed an error stating " apk_cleaner cannot do its job. zip binary is missing" this anything that needs attention? or possibly something in development for a later version of voodoo?

Don't want to single anyone out but just because the quadrant score isn't bloated doesn't mean the lagfix didn't work. If you ask me (not that you would :)) quadrant scores have very little meaning and can be artaficially bloated very easily with little improvment in real world usability and smoothness of a setup. I get a score of around 1200 my current setup and I think its smoother and faster than a previous one that scored in the 1700. For your own benifit don't choose a rom and or kernal based on the quadrant scores you get with it........

Just my 2.............
[Captivate Android Development] raychang:
I have further observation on 2.1.5. It seemed to me that after flashing from 2.1.3 to 2.1.5, the UGJK3 modem hunted between 850 and 1900 band much more often. I dialed in *#0011# and can see the hunting at the same location in my home frequently where 850 band signal is much stronger. In 2.1.3, it seemed to sticked in 850 band (using the same UGJK3 modem).
[Captivate Android Development] Yuna:
Have issue with 2.1.5: i like original samsung bootup logo e.g that with sound, but seems like i have 2 logos overlaying: ANDROID logo and a samsung video... 2.15 kernel

also have VERY low FS scores in quadrant: 1100-1495... WTF?
[Captivate Android Development] xcaliburinhand:
Fix shouldn't have any effect on output, all the changes were strictly input related. I will double check to make sure nothing funky happened.

Good catch, apk_cleaner is an extension of the Voodoo lagfix. It is supposed to zipalign the TouchWiz launcher. From what I can tell supercurio switched binaries but the script that checks for the correct binary was not updated. I have a tweet out to supercurio to verify.

Got word from supercurio, appears I missed the step to compile the binary. Will be fixed in v2.1.6

-----

Voodoo 5.0.1 was released yesterday. Will roll in the new voodoo changes, include a fix for the bootanimation overlay issue, and hopefully resolve the voodoo voices issue. Time permitting, v2.1.6 will be available tonight or tomorrow night.
[Captivate Android Development] pillz424:
Im also getting the same thing. No volume on the headset. If I listen real hard I can barely hear anything, which is still more than there ever was before. Is there any way to increase the gain on the output?

Edit: its the samsung headphones that don't work. My iphone ones work great.
[Captivate Android Development] bts0uth:
I haven't tried a HEADset. I am talking about the HANDset. As in when i'm talking to someone on the phone I can hardly hear what they are saying. Speakerphone is also very low.

I have flashed a few different roms in the past two days and they all have the issue so I hope something funky happened and xcaliburhand can up the volume.
[Captivate Android Development] xcaliburinhand:
I'll do a little bit more digging but so far it doesn't look promising.

The output volume has a limit of 63, the upper limit of the output volume during a call is set at 61.
[Captivate Android Development] Stephenv1971:
I got that on Docs jp6 rom. fixed it by putting a bootanimation.zip in /system/media

My quadrant scores are lower than that, consider yourself lucky. I can't feel a difference though.
[Captivate Android Development] han.azuki:
is it possible to create newest kernel w/o voodoo? I know about /disable-lagfix folder, but i like to have a very clean rom w/o having any extra things in it. thanks!
[Captivate Android Development] MS3Zoom24:
so i noticed while the headset works correctly, the ability to use the headset jack to the cars aux port doesnt work at all like with stock eclair.
[Captivate Android Development] fatttire:
Doesn't work at all or isn't up to par? If not up to par, then how exactly?
[Captivate Android Development] lrs421:
Just loaded 2.1.6 on top of Assonance and everything works perfectly. Quadrant scores are back to normal ;) and voodoo speaks!

Awesome work.
[Captivate Android Development] rocketpower:
there is something wrong with the link of I9000_reoriented_v2.1.6_novoo.zip I download it but find MD5 is same with I9000_reoriented_v2.1.6_bln.zip you can check it
[Captivate Android Development] gtg465x:
Think you could make a version with this mem config xcaliburinhand? These are the stock values from the latest i9000 leak (JPU 2.2.1), which has 339 MB RAM available stock. HQ video recording/playback aren't working on JPU with the current mem configs you and Setiron are using. Thanks!

And jpeg should be set to 0.
[Captivate Android Development] xcaliburinhand:
Good catch, the link was pointing at the BLN version. Link has been updated.
[Captivate Android Development] xcaliburinhand:
Starting to think samsung looks at this forum and incorporates random things (such as higher memory). I'll see what I can do, there seem to be a lot of issues with building JPU compatible kernels right now.

If someone has some time, can they try v2.1.2 with JPU and see what happens. If it works well, then I know it is just a matter of adjusting the memory.

-x
[Captivate Android Development] Stephenv1971:
I'll do it.

also, did voodoo sounds disappear again? When i disable-lagfix... no voices.

Edit: going to have to try darky, rambones links are dead.

Edit: I will say, looking at my post number, I am not certain I will have good luck with this.

Edit: Yeah... 2.1.2 won't work. 2.16 doesn't work either.
[Captivate Android Development] han.azuki:
THANK YOU SO MUCH FOR NO VOODOO <3 <3 is it possible to have no voodoo in .tar format? I flash using odin.

does 2.1.6 work with jpu?
[Captivate Android Development] Athailias:
I got voodoo voices with 2.1.2 and JPU its at the galaxy S logo and then just FC's like mad after.

I flashed with odin and pulled battery and flashed kernel 2.1.2 also with odin.

Edit, I had flashed stock first :P
[Captivate Android Development] Stephenv1971:
Same here, but it picked up my old data... going to flash stock and try again.

Edit: no.. that was worse... boots... screen goes black... then the phone shakes twice every 3 minutes.
[Captivate Android Development] xcaliburinhand:
Thanks for giving it a try.

2.2.0 will work with JPU.

Enjoy.
[Captivate Android Development] arcardinal:
Will 2.2.0 still work with the JK3 roms as well, or should I stick with 2.1.6?
[Captivate Android Development] xcaliburinhand:
Should work with all Froyo based ROMs right now. I tested it on JPU and JPM.

-x
[Captivate Android Development] han.azuki:
i love YOU MAN

when i enter debug mode, the device is recognized as a cd drive, which makes it disk protected and i cannot copy files over. why did it change from usb to cd drive?
[Captivate Android Development] jgaviota:
xcal,

Can I suggest that maybe you could lend gdanko a hand?

He's working on CM6.1 and on Froyo AOSP, but has problems with I9000 kernels and modems with his intrafms.

I really don't know what I'm talking about :D but what he's working on seems interesting...

Thanks!
[Captivate Android Development] bts0uth:
same here.

external sd card shows up normally though
[Captivate Android Development] han.azuki:
do u have euro galaxy s? since captivate only has internal sd.
[Captivate Android Development] Pirateghost:
then what is that micro sd card that i have in there?
[Captivate Android Development] ArkieMD:
Not sure if this kernel installed properly. It says Kernel version 2.6.32.9 reoriented #81 under 'about phone'. Is this right?
[Captivate Android Development] sb4178:
Very good ,

i need these..
[Captivate Android Development] han.azuki:
Ahahaha..i feel dumb..i have not used micro sd since I bought this so I completely forgot. Lol my bad.
[Captivate Android Development] Dzmitry:
On jpu rom internal sd card is detected as CD DRIVE
[Captivate Android Development] beerbaronstatic:
How is performance on the 2.2.0 no voodoo kernel? anyone?
[Captivate Android Development] Stephenv1971:
So its the rom and not the kernel?
[Captivate Android Development] han.azuki:
its the rom.
[Captivate Android Development] PuffinNugz:
Anyone successfully running this on Doc's or Darkky's new rom? How is it?

Also, a noobish question here...I haven't used voodoo for awhile. Does this change all partitions to ext4 like you can with ulf? or is it just the one partition? thanks.
[Captivate Android Development] xcaliburinhand:
The USB mounting seems to be ROM related. External SD (microSD slot) mounts fine (at least for me, it is read/write), internal SD has issues.

JPM with this kernel does not have these problems.

A lot of people are experiencing this (issue shows up in the I9000 forums too). It is being looked into.
[Captivate Android Development] Stephenv1971:
I'm not convinced. In the setiron thread he said this "Known issue caused by using JPM based kernels on JPU. Nothing can be done until samsung releases updated sources."

I also checked the i9000 threads and no one is reporting the issue.
[Captivate Android Development] DAGr8:
wow , cant believe I was the first to tank this guy !!!
[Captivate Android Development] Kakashi28:
I'm new to this.....

Is there any instruction on how to upgrade this kernel onto the captivate?

Please advise..

Thanks.
[Captivate Android Development] han.azuki:
Theres several posts about cd drive and disk protected.. Not writable
[Captivate Android Development] xcaliburinhand:
Well I can tell you the root cause (no solution yet).

Prior to JPU internal SD was lun 1 and external SD lun 2.

JPU has internal SD as lun 0 and external as lun 1

Lun 0 (if it exists) is mounted as a CD-ROM. This is where the CDROM issue and why External SD has the internal SD label.

The ROM is taking care of the initial setup of LUNs.
[Captivate Android Development] xcaliburinhand:
Not exactly pretty but the USB mount issue has been fixed.

Works with both JPU and JPM.
[Captivate Android Development] illdroid:
so how did you fix it?
[Captivate Android Development] xcaliburinhand:
Edited the sections of the kernel that control the usb mass storage device. Pretty much commented out the things that made lun 0 act as a read-only cdrom.
[Captivate Android Development] illdroid:
so basically lun0 acts now like lun1 and lun2?

doesn't sound ugly to me

you are simply awesome.
[Captivate Android Development] bedwa:
Well, I see what xcal meant in it not being elegant. He forced it through by brute force, not my any other method. Thus if you would ever need the commented code for any reason, you wouldn't have it and would still be without the root cause of the problem. ;)
[Captivate Android Development] koreancanuck:
Wanted to drop in and say your kernel is awesome xcal :)
[Captivate Android Development] gtg465x:
Oops, home button breakage when flashing Doc's JPU with this kernel. Will try flashing with the stock JPU kernel and then flashing this.

edit: Nope, that didn't work either. Well this is odd considering I had home button workage with stock JPU and this kernel...

edit 2: Uhh, yeah, so I was looking for a solution and randomly tried to press the home button when I was about to start the flashing process again and it worked. Weird, but I'll take it.