yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] diablo009:
I think there's a bug here.

Am on the 256 HZ version of kernel.

1. Connect to computer with debugging on

2. Turn on USB storage

<do ur work here>

3. Turn off USB storage

<wait for some time, say like a minute or two>

4. Turn on USB storage

Here, though the phone says 'usb turned on', on the computer I am unable to see my phone disks. This happened every time I tried.

Even in adb mode, it says device is offline.

I need to pull the cable out and plug it back in to see the drives on computer or for adb to recognize device as online.

Is this a bug? Is anyone else too noticing this? I am di11igaf's 3.0.2 ROM. I didn't see this behaviour earlier on the default kernel of that rom.
[Captivate Android Development] rmichl:
No 3g / Phone

Did anyone loose network after flashing? Phone reports correct kernel but In about phone,the baseband says Unknown.

Any help would be greatly appreciated
[Captivate Android Development] delugeofspam:
Sounds like a modem problem? Try flashing one from the modem thread (http://xdaforums.com/showthread.php?t=835272) and see if that doesn't fix your problem.

A bonus of this being an i9000 kernel should be compatibility with the i9000 modems. Hooray.
[Captivate Android Development] evoic:
Will require help :)

Flashed the SpeedMod K12H with HZ=500 CWM BIGMEM file using CWM.

No problems, booted right up.

45 seconds later, opened ROM Manager and clicked on "Boot into Recovery" as I was on my way to do the tweaks.

Now stuck at Galaxy S load screen for 10+ mins.

Any thoughts / suggestions here?
[Captivate Android Development] diablo009:
Looks like the kernel flash didn't go well. Onto what rom r u flashing this?
[Captivate Android Development] diablo009:
I'm not sure if rom manager supports 9000 fully yet.

I'd recommend going into recovery either using 3 button combo or extended power menu available on most 9000 roms.
[Captivate Android Development] evoic:
phone-exclamation-computer icon

This feels bad.

*Update:

Got into Odin

Sitting at:

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

...10 mins now
[Captivate Android Development] diablo009:
My data speeds on at&t network and on wifi.

Wifi speed is after I loaded the old jpa firmware.
[Captivate Android Development] existz:
If it doesn't do it within a few seconds something went wrong, if I don't enter download mode a certain way it does that to me, make sure odin is opened before u connect the phone...disconnect the phone pull battery, close and reopen odin, then enter download mode and flash again...the only way mine works is if odin is open, pull battery, connect usb and while having vol down pressed I insert the battery then it goes into download mode ..now on my last captivate it was different..I had to have vol up and down plus pwr then insert usb....so it might not work that same exact way for you

As long as you can enter download mode its not bricked, you just have to find that sweet spot for odin to catch it

Make sure you have the tar file in the pda slot

Sent from my Captivate
[Captivate Android Development] evoic:
No pda slot.

I have this screen:
[Captivate Android Development] existz:
Thats not the correct odin, that's odin one click, that will flash you back to stock ...it will wipe everything, there's another version of odin on here, u will have to search, with it you can just flash the kernel alone and you will be back to normal (in most cases)

Sent from my Captivate
[Captivate Android Development] evoic:
It's ok.

I downloaded another version of Odin, that ended up looking exactly like this version, and then the magic started happening:

<ID:0/003> Added!!

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> Sbl.bin

<ID:0/003> boot.bin

<ID:0/003> cache.rfs

<ID:0/003> factoryfs.rfs

etc.....

I'm on my way back to something I can work with, so I'll mash on it from there.

Even though I was scared, I was never reeeeally scared.

As soon as I did it, I googled and saw people getting themselves out of jams left and right so I knew there was hope.

On my way to donate to Odin devs.

>: -)

*Edit

Just thinking about it all again, I still have no idea where things went off the track.

I'm going to duplicate every step as it is all still fresh on my mind and see if the results are the same.
[Captivate Android Development] hardcore:
If you're unsure of how to flash it using Odin, check out the installation guide in my sig or the first post.
[Captivate Android Development] evoic:
I was flashing using CWM, and it went fine.

Afterwards, I attempted to use the ROM manager to reboot into Recovery to do the tweaks....and that's when things went south.
[Captivate Android Development] delugeofspam:
I'm pretty sure ROM Manager was trying to boot into the Captivate CWM Recovery when what you want to do is enter this kernel's recovery. I use Terminal Emulator and simply type "reboot recovery" (no quotes) so I don't have to hold buttons or mess with adb, or worry about app behavior.

Posted from an enslaved Captivate.
[Captivate Android Development] sublimaze:
i never use rom mgr to reboot to recovery. just hold the power button down & choose "recovery", its faster & easier

sent from my captivate | di11igaf 3.0.2 | speedmod k12h
[Captivate Android Development] pranna:
are you saying you are able save email attachments to the external SD?

I can't write anything to the external card. It seems to copy ok without any errors, but try to open any file (mp3, pdf, jpg...) it is corrupted. I can take the card out, put it in a card reader, add files to it from a computer (seems to go ok), put it back in the phone and none of the new files show up.
[Captivate Android Development] :
I have installed this kernel and I wonder: Can I install the recent OTA update (allowing stock Froyo to sideload) from Samsung while running this?
[Captivate Android Development] guika:
Is it possible to put voodoosound 9. With bass boost to inside?

Sent from my GT-I9000
[Captivate Android Development] guika:
I feel that this topic is discontinuing....

Sent from my GT-I9000
[Captivate Android Development] alexige:
If you really want to stick with froyo but want Voodoo Sound 9 get voodoo control plus from the market, its a paid app, a small donation to Supercurio who deserves every penny for all his work, voodoo plus enables new sound improvements to be implemented on your phone without needing a kernel dev to throw it in their kernel.

But why not just jump to gingerbread...
[Captivate Android Development] guika:
Because i made a much stable and fast rom in froyo. Without any problems

I checked gingerbread roms and evrywhere i read that they have issues. Thats why not i want to change.

Voodoo plus is loading the module at boot?

Sent from my GT-I9000
[Captivate Android Development] trekie86:
I'm running Mosaic by Team Phoenix and it is rock stable. Minor glitches but very minor and the new release in a few days/weeks should fix that. Continuum is also supposed to be pretty stable.
[Captivate Android Development] alexige:
Yes exactly, well atleast when you check the load sound driver and load driver at boot boxes in kernel module options inside the app.
[Captivate Android Development] JRock80:
GB Based Kernel

Hardcore.....I have loved your work in the past. Will you be releasing a GB based kernel? If I missed a post about it, I apologize in advance.
[Captivate Android Development] bgf183:
I second that.... K13e (and those that came before it) were great. Anything in the pipeline for GB?

p.s. for the guy a few posts back who was concerned about GB bugs, I'm using Continuum 5.6 with xcal's kernel and it's pretty badass. I haven't found any real bugs so far. I have had some issues with bluetooth calling on the TalonDev kernels, but xcal's seems to work quite well.
[Captivate Android Development] tbong777:
THIS ^^^^^^^

The application is well worth the small price for it..
[Captivate Android Development] trekie86:
He does have one but I believe it is for I9000 only phones at this time, not Captivate. Here is the thread, I haven't kept up on my reading so it may be Captivate ready now...not sure.

http://xdaforums.com/showthread.php?t=1044519
[Captivate Android Development] G-Bus:
I just installed this Kernel, and it works great BUT I absolutely need Bluetooth connectivity to work fine with my car. Right now I only get static. Is there a fix for this?

I've read a little through the whole thread but couldn't find anything conclusive.

Thanks for helping out!

BTW, I have installed k13e right now..
[Captivate Android Development] guika:
With a new kernel a new pairing should be done.

Delete the phone in your car and delete the car in your phone. Re pair it and it should work. I had the same problem sometimes up the solution.

Sent from my GT-I9000
[Captivate Android Development] G-Bus:
That didn't do it for me. Did it two times now and it still does it. I can't hear anything, only static.
[Captivate Android Development] reaperslay:
help please

So went to flash speedmod for my captivate not realizing i already did and and had already put CyanogenMOD 7 on my phone. Now after flashing speedmod again my phone is bricked it will not go past the galaxy s screen. Is there any way to fix this cause.
[Captivate Android Development] bryman27:
You're not bricked. You need to get into download mode and flash a CM7 compatible kernel like Le kernel du jour.
[Captivate Android Development] tygoerlitz:
Phone issues

So I started running this kernel and mostly everything is working great but.... When making phone calls people cant understand me I apparently sound very static and muffled. My phone also seems to go in and out of service almost as if the modem or radio (not sure which one) is turning off. Any help would be appreciated. Thanks guys!
[Captivate Android Development] kalex12:
You must choose modem kernel combinations. I use TLJL3 on Froyo
[Captivate Android Development] tygoerlitz:
That worked really well. Thank you so much
[Captivate Android Development] kalex12:
It's my pleasure :-)
[Captivate Android Development] trekie86:
Depending on where you are JK4 has been a very reliable modem for many as well. Go to the modem thread and just make sure you have a CWM2 compatible modem and you can try as many as you like until you find one that suites you the best.
[Captivate Android Development] dru1226:
Newbie question can I use this kernel with stock M6

Sent from a happy phone using XDA Premium App
[Captivate Android Development] bryman27:
No, this is a froyo kernel.
[Captivate Android Development] dru1226:
Got ya still new to mixing kernels

Sent from a happy phone using XDA Premium App
[Captivate Android Development] dang3r1917:
I assume this kernel is not being developed anymore? Could anyone recommend a froyo kernel that is still being developed or is better than speedmod. I've used this kernel since I started flashing and it's been great. But I've been out of touch for a while so I don't know what new stuff there is.
[Captivate Android Development] Darkuso:
Just for be sure, this kernel works in phoenix ultimate 7?
[Captivate Android Development] studacris:
yup

10char
[Captivate Android Development] mcyorian:
it works with continuum 6.1 rom??
[Captivate Android Development] existz:
No, this is a froyo kernel
[Captivate Android Development] AdamOutler:
Hi there.. I packaged Speedmod into a Heimdall One-Click

Example Image:

1. Ensure you have JAVA on your computer (Windows/Linux/Mac)

2. Download and execute i897-Speedmod-K13E-GBbootloaders-One-Click.jar from this location: http://teamkomin.com/index.php?dir=Captivate/

3. Follow any directions given and when your device is "Connected" click flash

--Optional--4. If you have problems, put your device back into Download mode, check the "Flash Bootloaders" checkbox and click flash again to reflash bootloaders and repartition.

Download Speedmod Kernel Heimdall One-Click
[Captivate Android Development] rootnik:
I've noticed that if I reboot with the usb plugged into my computer I sometimes get "no service". Can somebody try a couple times to see if they can reproduce it?

It doesn't seem to happen if I reboot on the ac adapter or unplugged.
[Captivate Android Development] existz:
@hardcore

Will you be making a k12i test version as well or are you going to skip k12i-test for captivate?

EDIT

Just flashed your i9000 k12i-test and reconverted /system with your method instead of voodoos, then reflashed back to k12h-i897 ;-p

Sent from my Captivate
[Captivate Android Development] evoic:
1. A feature that I'm

still

not used to using.

2. My New Year's resolution is to use that feature more often. :p

Thanks.
[Captivate Android Development] tysj:
I used to get this with older builds of Perception and swore it was still happening on 9.5 (but it never really bothered me since I try to keep reboots minimal). But I just rebooted with it plugged in and it still got service.
[Captivate Android Development] hardcore:
It happens very often. That's why it's noted in my installation guide:

http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-how-to-install.html

It seems to happen only when usb debugging is on. Turn usb debugging off and it should happen less (or maybe not at all).
[Captivate Android Development] ndoss:
Looking at the kernel code in this and other kernels, there aren't that many compile-time differences between the captivate and i9000 kernels. It seems like it'd be possible to make these changes run-time instead of compile-time (i.e., a kernel could be built once, then used on either a captivate or i9000).

Do you know if this has been discussed before?
[Captivate Android Development] rootnik:
Thank you for the reply.

I turned usb debugging off it still does it. This isn't a big deal at all, I just was not aware that it was a known issue. If there is anything else you want me to try I'll be glad to, otherwise I am fine rebooting without it plugged in.
[Captivate Android Development] vuoflfan:
I added this kernal to cog v23b8...everything seams fine...so far...but am getting alot of static on bluetooth when making a call,,,,BT seams to be fine on music player....anybody with suggestions?
[Captivate Android Development] existz:
Try an i9000 modem, this usually happends when mixing captivate modems with kernels built off of i9000..(this is actually an i9000 kernel w/ xcaliburinhands patch).. there's several to try.. jk3,jk4,jl2,jl3 ...etc..etc.. rule of thumb is not to mix and match.. ie. Run i9000 modem with i9000 based kernels

If your already on an i9000 modem still try a different one ...

Sent from my Captivate
[Captivate Android Development] delugeofspam:
Edit: Ignore me, my problems have nothing to do with you.
[Captivate Android Development] davwman:
Nothing else to say!

Cezars Palace, with speedmod no- lagfix, jl2 modem
[Captivate Android Development] BernaertB:
This Is The Far Best Kernal I Played Around With. I've Installed This Over The Newest Cognition Build And Didn't Even Need To Disable Voodoo Since This Kernel Is Compatible. Not Only Is This Kernel Stable And Fast But It Comes With Tweaks Inspired By Voodoo Color Fix And Advance Lag Fix Options. I've Experimented With Some Settings And I Managed To Get Over 2000 On Quadrant. Without Using OCLF Or SetCPU. If Flashed Write And Paired With A Good Modem This Definitely Unleashes The Potential Of The Captiavte.
[Captivate Android Development] ksimilie:
whats this good modem you speak of? Currently using tlgl4. getting about 1300 on quadrant.
[Captivate Android Development] BernaertB:
I'm Using ucjj4. Since I Find It Compatible With Voodoo And It Seems To Work Flawless.
[Captivate Android Development] Pirateghost:
LOL! try to call someone!

you shouldnt be mixing CAPTIVATE modems with I9000 kernels
[Captivate Android Development] delugeofspam:
The JJ4 modem worked fine for me when I flashed it but the i9000 modems are faster, so I've switched since.
[Captivate Android Development] mgfjd:
Hey, I was using speedmod 12G and I was getting ramdon fc with applications running in the background memory.

I have all the memory tweaks, and lagfix applied.

I flashed another kernel on top and I haven't had fc problems since then..

I know you are working hard for our community and I just want to help reporting my experience
[Captivate Android Development] Pirateghost:
it will work for data. but try a phone call
[Captivate Android Development] delugeofspam:
I understand what you're trying to say, guy, but the JJ4 modem really works fine using this kernel + Cognition 2.3b8. Flash it and check your voicemail if you want... it won't hurt anything but your data speeds.
[Captivate Android Development] hardcore:
Yeah it definitely bugs me. But oh well, guess we gotta live with it.
[Captivate Android Development] Pirateghost:
So what you're telling me is that all the testing that has been done and determined that you can't use i9000 kernel and captivate modem is wrong and you have somehow gotten something to work that many others could not? Congratulations, now tell me if you can actually Make a phone call where the other person can hear you.

Sent from my GT-I9010
[Captivate Android Development] delugeofspam:
OH MAH GODS UNPREDICTABLE BEHAVIOR USING CAPTIVATE! STOP THE PRESSES!

Look I'm not saying the Earth is round, I'm just saying that I've literally used the thing. It shouldn't take 3 posts to do that.

Posted from i897/Cognition 2.3b8/speedmod kernel k12h/TLJL3/LCD:210 using XDA App.
[Captivate Android Development] hardcore:
The next version will support proper conversion of /system. And maybe even smoother performance.
[Captivate Android Development] domin0311:
thanks hardcore keep it up...good work :)
[Captivate Android Development] rootnik:
I agree that he is being too hard on you. I mean, it is possible that this kernel is more compatible with captivate modems than other i9000 based kernels.

Just curious, have you tried to use bln with Cognition?
[Captivate Android Development] beerbaronstatic:
So with this kernel should you make sure you remove bootanimation.zip from /system/media?
[Captivate Android Development] hardcore:
No. If u leave it there the bootanimation will play.

But if u use anything that depends on the playlogos1 bootscript hack, that will stop working once a bootanimation is present.
[Captivate Android Development] beerbaronstatic:
I'm unfamiliar with that hack, is there any easy way to tell if the ROM I'm running is using it?
[Captivate Android Development] ThisWasATriumph:
Have an issue with this kernel. When I press the power button it takes 2-3 seconds for the screen to come on. I know this used to be a problem with some of DGs old kernels but has been fixed since. I just flashed Glitterballs kernel and theres no delay. I searched but didn't find it mentioned anywhere in this thread. Am I the only one?

edit: nevermind. still doing it. must be my rom.
[Captivate Android Development] delugeofspam:
I have not. My last phone had a Wi-Fi hardware failure for the past eight months and had a constantly blue LED, so I'm used to having no visual cues for notifications. I can give it a whirl if you want to compare notes, though.

Edit: My home keys lit up and darkened when I touched them but didn't light the screen until I hit power. Unlock screen, no strange behavior. I actually rather like this.
[Captivate Android Development] delugeofspam:
If you have the recommended tweaks enabled and want to know if they're running, open Terminal Emulator or adb shell and type

cat /proc/sys/vm/dirty_writeback_centisecs

if it returns the value 2000 you're good.

I think.
[Captivate Android Development] Bruce Inman:
Can someone please confirm this statement; "Earphone/speaker bug fixed"

On 2.1 Eclair you could use any wired headset and hear the caller on the other end.

I have flashed a few kernels but have not been able to get this to work.

Is this the bug or is it just getting sounds through the headset?

I just want to know if maybe I'm doing something wrong when flashing these.

Thanks.
[Captivate Android Development] justmart:
Yup. I have this kernel with a 2.2 rom and the earphone works in every call.
[Captivate Android Development] Bruce Inman:
Is that with the OEM headset or any headphones?
[Captivate Android Development] hardcore:
The new version K12I supports conversion of /system to ext4 as well.

Access it via CWM > SpeedMod > Lagifx > Convert SYSTEM
[Captivate Android Development] domin0311:
I flashed k12i odin version and I am getting force closes
[Captivate Android Development] sublimaze:
reflash it

sent from my captivate | di11igaf 3.0.2 | speedmod k12h
[Captivate Android Development] domin0311:
i did twice then I flashed back to k12h and still force closes... I am using docs rom from kitchen
[Captivate Android Development] hardcore:
Wiping dalvik cache is recommended after installing this version.
[Captivate Android Development] justmart:
OEM.

10char
[Captivate Android Development] crupp:
Are there any risks to do a system conversion with the new Kernel?
[Captivate Android Development] ronandi:
Hmm well I tried that and I got 500. I deleted bootanimation.zip in /system/media and I still get 500 after a reboot.

Edit: I read through hardcore's post detailing the tweaks. That line checks if the battery tweak is enabled...which I some how missed. I get the correct output now.
[Captivate Android Development] hardcore:
I don't think you'll find any conversion with no risk.

That being said, it should be quite safe. Many people have done it already using the SGS version.
[Captivate Android Development] shaolin95:
So what is the difference between this Conversion feature and other lag fixes if any? I see a lot of users mentioning this Conversion so it got me curious.

Thanks!
[Captivate Android Development] beerbaronstatic:
I'm having a lot of issues with running super user after going to K12I with system converted to ext4
[Captivate Android Development] existz:
It converts /system to ext4 also, so data,dbdata,cache and system will be ext4, similar to voodoo but hardcore has used a different method and there's different mount options than voodoo as well... and I know in his test builds it was compiled in a new way, not sure though if he kept it that way or not

Sent from my Captivate
[Captivate Android Development] shaolin95:
Interesting. I just wish there was an OCed version of this kernel to give it a shot. :-)
[Captivate Android Development] bts0uth:
Not me. I converted /system and have no issues anywhere
[Captivate Android Development] beerbaronstatic:
Did you flash this with a new ROM? or just updated with cwm? is it a 2.2 or a 2.2.1 ROM?
[Captivate Android Development] beerbaronstatic:
Since this kernel isnt OC/UV should we have any S99_freq or S99_volt scripts in our /system/etc/init.d/?
[Captivate Android Development] hardcore:
Nope and it will probably have no effect.
[Captivate Android Development] beerbaronstatic:
Awesome. I was using a SetiroN kernel, wanted to make sure before I deleted them. Any ideas why when I convert system/ to ext4 I can no longer get super user with anything? works fine if I don't convert it
[Captivate Android Development] hardcore:
Just install superuser again from CWM > SpeedMod menu if you lost it.
[Captivate Android Development] beerbaronstatic:
well it doesn't appear I've lost it, I can see su in /system/bin, and the super user icon shows up in the launcher, but nothing that requires root will even prompt me. For now I'm running with system in its normal mode with lagfix/tweaks enabled.
[Captivate Android Development] psufan5:
Decent kernel, but not nearly as good as the reoriented balls one.
[Captivate Android Development] diablo009:
Comments like this should be accompanied with proper reasons/explanation so people can know these are not baseless. Plus this would give the dev more scope to improvise on the kernel.
[Captivate Android Development] psufan5:
True. My screens dont slide as smoothly with live wallpaper on

Its generally not as snappy - possibly due to stock clock speed.