yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] francous:
my 1st time flashing a kernel but i heard good things about this one.. so hopefully coming from hardcores my battery life is better and i see a big difference..
[Captivate Android Development] Mac11700:
+2

10char

Mac
[Captivate Android Development] diablo009:
Found a couple of images. I personally liked the white and black one.
[Captivate Android Development] xcaliburinhand:
Any of those images royalty free? Would rather not get into a copyright mess.
[Captivate Android Development] rraquib:
The last image seems fitting. Truly a xcal in hand.
[Captivate Android Development] diablo009:
I wouldn't recommend the 3rd one. But the other 3 I don't remember seeing any copyright labels.
[Captivate Android Development] majinzen:
I still think the idea you had of an X that starts sideways and reorients is best.
[Captivate Android Development] lrs421:
I do too. That image describes it all.
[Captivate Android Development] diablo009:
We cud have the white n dark excaliburs in a cross making a huge X
[Captivate Android Development] nfs_phone:
Voice Dial over Bluetooth and A1026 Noise Cancellation - EVER?

Been pretty frustrating to realize that no one has a fix that will enable both Voice Dialing over Bluetooth and support for the A1026 Noise Cancellation chip. I am construing this comment to mean that we'll NEVER see it with a ported kernel.

Please tell me I am wrong and that there is a way to get both features now. (Don't lie, though.)

-nfs
[Captivate Android Development] xcaliburinhand:
v2.3.3

-Captivate car/home dock support

-Audio uses dock when available (no need for the Rogers Captivate dock app)

Since all changes are dock related, if you are not using a captivate dock no need to upgrade.
[Captivate Android Development] diablo009:
thank you sir for this heads up
[Captivate Android Development] xcaliburinhand:
NEVER is a rather strong word. A1026 will come into play when AT&T finally gets around to releasing an update and Samsung publishes the source. The other option is getting a dev to devote some time to porting it from eclair.

Honestly the A1026 doesn't really interest me, so I haven't devoted any effort nor do I plan on devoting any effort to it.
[Captivate Android Development] Exostenza:
Nice to see another update... even if it doesn't do anything for me. This is my favorite kernel!
[Captivate Android Development] nfs_phone:
No one with the skills will do it for free

Too bad. The A1026 really is helpful whenever taking a call in a public place.

Yes, I get it will be around, if AT&T ever releases an update. Of course, I'm still wondering whether that update will solve the no voice dialing over bluetooth problem, too.

I guess anyone with the skills required to merge the A1026 support code into a working version of 2.2.1 (I9000 based) would not do it for free.

It just seems kind of sad to have a phone with such nice hardware, but with such poor support for it MANY months after release. By poor support, I mean that you cannot get the phone to both voice dial over bluetooth AND to support the A1026. To me, these are basic features of the phone's hardware, but there's no way to get them both working now. :mad:
[Captivate Android Development] majinzen:
You can use a ji6 or jj4 based rom and guardian bob's bluetooth app. It will allow voice dialing via bluetooth.
[Captivate Android Development] lrs421:
Can you point me to his app?
[Captivate Android Development] majinzen:
Just search the market for bluetooth launch or guardian bob. I would link you to the thread but I'm not on my computer.
[Captivate Android Development] nfs_phone:
Not really voice dial over bluetooth

Well, thanks for the Bluetooth Launch idea, but it doesn't really look like what I need (voice dial over bluetooth). According to the forum thread about Guardian Bob's app, this is what he says about it:

"Here's the thing, currently Google Voice Actions and Vlingo can't hear over the bluetooth mic. Still, this will launch the voice app, and allow you to speak through your phone's mic."

So, if your phone is in your pocket or a case, it will be useless, because your voice information isn't going through the bluetooth headset. It's being picked up by the phone's mic. It might work in the car for me, but it won't work when I'm walking my dogs.

I guess I'm just going to have to live without the A1026 till the appropriate source is released.
[Captivate Android Development] xcaliburinhand:
v2.3.4 (build #119 - 121)

-Audio uses dock when available (now via this app)

-Call audio uses dock when available

2.3.4 is only useful if you have a captivate dock. No changes otherwise.
[Captivate Android Development] loserskater:
You never cease to amaze! Thanks for all your work!
[Captivate Android Development] cisco150:
is this a rom or a ad on to a factory 2.2 or the mb of this file is less then 10mb

and how u install with clockworkmod like if flashing a custom rom
[Captivate Android Development] xcaliburinhand:
Just a kernel, should work with most roms out there. Primarily designed for i9000 roms on the captivate.

Sent from a cell tower.
[Captivate Android Development] cisco150:
ok thanks for your help
[Captivate Android Development] cardassianvol:
Thank you. This is my favorite kernel.
[Captivate Android Development] existz:
It is a good one... Xcal deserves more credit.. :)
[Captivate Android Development] xcaliburinhand:
I always appreciate any thanks I get, but in the end knowing that so many people are getting a much better user experience is satisfying enough.

On another note, it looks like 2.3.4 or 2.3.5 may end up being the final build for this kernel. At the moment I don't see any additional enhancements (other than voodoo sound v5). If the rumors are true, I will have a new kernel to work on beginning April.
[Captivate Android Development] Exostenza:
Hey xcal can we get a voodoo sound 5 update on this kernel please? Still my favorite kernel!
[Captivate Android Development] xcaliburinhand:
Went one better, voodoo sound v6.
[Captivate Android Development] Exostenza:
Thanks xcal!

Flashing now.
[Captivate Android Development] DAGr8:
awesomeness other then that any changelogs ?
[Captivate Android Development] TheYar:
Headphone logic

I don't know if this has been mentioned, but I've noticed a slight quirk with headphone logic in some of the i9000 kernels around here, so I figured I'd ask in this thread.

The bluetooth headset seems to interfere with the pause/unpause logic of the wired headset. Like, if I pause the music manually while the bluetooth headset is on, and then turn off the bluetooth headset, the music unpauses automatically and plays through the speaker. Or, if I pause the music manually while the bluetooth and wired headsets are connected, and then unlug the wired headset, the music unpauses automatically and plays through the bluetooth headset (which was crazy this morning when my podcast started up in the middle of a conference call... took a while to figure out why one of my Developers seemed to start talking about the history of the Bubonic Plague.)

I haven't quite isolated exactly what happens, and it might exist on stock for all I know right now, but it seems that some of the "auto-unpause" logic kicks in even if it wasn't proceeded by an auto-pause. I might be wrong, but I'm assuming that auto-unpause should only occur if the wired headset has just been plugged in AND if following an auto-pause due the wired headset being pulled out.

Thoughts?
[Captivate Android Development] diablo009:
Thank you once more for ur awesome work
[Captivate Android Development] xcaliburinhand:
Nothing else changed, just applied the recent voodoo sound.

Definitely odd behavior, the ROM/music player usually take care of the pause/un-pause part, so I can't provide too much insight. However, the normal logic on unplugging a wired headset is to send out an ACTION_AUDIO_BECOMING_NOISY intent. Most apps see this as a reason to pause playback.

It sounds like something is trigger the play when the audio path changes. Do you have any task launchers setup? May also be worth trying on stock to see if you can isolate the issue.
[Captivate Android Development] loserskater:
What music player are you using? Certain ones have settings that will automatically play/pause when headphones are connected/removed. So you might want to try a different one and see if it still happens. A couple off the top of my head that I know you can disable the automatic pause/play are PowerAmp, Winamp, and I think Mixzing also. I also believe that the last one you install will override all of the others.

A second option (you need root for this one) would be to install Autostarts. With that you can disable which apps are called during certain situations. For example, on my phone when "BT sink state changed" it calls PowerAmp. I dont use BT so I'm not sure if it pauses/plays but it might be something to look into.
[Captivate Android Development] TheYar:
I hadn't considered that the app would be responsible for this, but it makes sense. I've only noticed it with DoubleTwist. If the playback is paused, unplugging the wired headset will cause it to resume playing. Opposite of the intended effect.
[Captivate Android Development] loserskater:
That is pretty interesting. Try going into settings and uncheck "Headset controls" and see if it still happens, if so you might want to try a different media player.
[Captivate Android Development] TheYar:
DoubleTwist seems to be the only fully-featured music player in existence. Name me another that integrates podcasts, has a decent widget with album art, and has a lock screen widget. Not even the highest rated pay apps I've seen have all three of those simple features.
[Captivate Android Development] loserskater:
Well did you at least figure out your problem? If other media players still cause this problem then we can look at other solutions. I was just suggesting trying something else to see if it gets rid of your problem. I don't want to turn this thread into a discussion about media players, so f you would like to discuss media players with me, you can PM me otherwise lets get back to the issue at hand.
[Captivate Android Development] TheYar:
Yeah sorry, not trying to derail.

I disabled the setting in DoubleTwist that says, "Use DoubleTwist as the defaul headphone control app." That had no effect. I've also now learned that anytime I delete any file from the sdcard, it unpauses the player.
[Captivate Android Development] doctorwu:
Download links on the first page aren't working, is there a mirror?
[Captivate Android Development] loserskater:
I would like to suggest one thing with your redirect app. Add a setting to make it "silent" so the notification doesn't pop up. I've noticed it randomly pop up occasionally, like when I back out of a youtube video for instance. Just a minor annoyance.
[Captivate Android Development] sejin:
are u going to release kernel for gingerbread? :)))
[Captivate Android Development] xcaliburinhand:
Yea, I have noticed the rebroadcast issue too and have some logic in place for the next version. Turning on/off notifications may be a good option too.

Yup, once the source is available, which won't happen until an official Samsung release.
[Captivate Android Development] AReynante:
If anyone has the cwm 2.3.5 zip, it would be greatly appreciated. (With or without bln, doesn't matter. [Pref without])
[Captivate Android Development] loserskater:
Ask and you shall receive.

2.3.5 WITHOUT bln
[Captivate Android Development] AReynante:
I'd click it all 5 times for today if I could. I had been asking all day today :p Thank you very much good sir.
[Captivate Android Development] halfsoul:
What's different between that & the file in OP?
[Captivate Android Development] loserskater:
The links in the OP were down. Same exact file.
[Captivate Android Development] Radukk:
Bump

We loves you xcal, and ur upcoming ginger reorientated kernel too.
[Captivate Android Development] mcord11758:
He posted time to get to work earlier in the general thread about the source release
[Captivate Android Development] mrhaley30705:
Would that be the same one in sgs tools?
[Captivate Android Development] Dlev7:
Sorry for the noob question but now that there is source what does that specifically mean?

I know about auto-rotation and button mapping.

Besides that was does it mean to the Captivate ROM developing, or will we now get to use the Stock Gingerbread because of the source?? Which I would be very happy to use, CM7 is great and probably the best ROM ive ever flashed that being said whether you like it or not Samsung has some nice little perks and quirks in their stock ROM and Im also an addict so something new to flash is always nice : D

Thanks in advance.
[Captivate Android Development] Radukk:
AT&T tends to release update way to far late as we experienced at 4 month late froyo. We need ported i9000 ROM for up-to-date. CM7 still have several problem, and is written on Nexus S code so it is not optimized to Galaxy series yet.

Here is conclusion. Bug-free Samsung Gingerbread ROM with hardware acceleration, 720P camera recording, multiple video playback codec support (include 720p mkv), and somewhat favorable Touchwiz implant (that easily be trimmed by chefs).
[Captivate Android Development] Cezar`:
CM7 is not written on NS code. CM7 is a built from code found on Android Open Source Project website.
[Captivate Android Development] Radukk:
Sorry about that, I know CM7 written from AOSP but my word probably misleading. reason why I said so is I saw a post that CM7 for Galaxy S some hardware drivers brought from Nexus S but not sure about that.
[Captivate Android Development] xcaliburinhand:
It's coming along, I may post a beta/alpha/early release today. It is usable but still some big issues.

Home key doesn't work, orientation is proving to be a beast, recovery is a mess.
[Captivate Android Development] Dlev7:
Wow! Thats amazing thank you SO MUCH!

If you would like a tester I would love to help and give feedback any way possible.

Just tell me what I need to do coming from CM7, and all the prerequisites and I'd love to help you out.
[Captivate Android Development] tjsooley:
I will also test
[Captivate Android Development] momulah:
I will test also. I have uber amounts of down time at work. I am a welding inspector.

Also have my handy dandy notebook...scratch that...handy dandy jig on case something goes wrong!!lol

XDA presents....Captivate S4G
[Captivate Android Development] sdricke:
Battery Life

I'm hoping for some help. I flashed this kernel through CWM, over Serendipity 6.4 to activate the usb audio fix for my car dock. But my battery life is HORRID. I'm talking, 15% loss every ten minutes, not touching anything!

What the heck have I done wrong?

BTW, been fighting with this since early this morning, and went through the deleting battery stats, etc. It's always my last resort to ask in the forums, but I truly cannot figure out what is going on. Version 2.3.5
[Captivate Android Development] jswclw:
I have also flashed this kernel to Serendipity 6.4 for the same reason - usb audio through the car-dock. I used the Kernel Flasher that came with Serendipity rather than CWM. But I also am seeing increased battery use on the order of 4-5% / hour with no use.

For what its worth...I flashed the non-BLN version as I do not use that feature.
[Captivate Android Development] xcaliburinhand:
Odd, what is the top item listed in battery usage?
[Captivate Android Development] jswclw:
Top item on battery usage for me is the display. This is the case even with almost no on time.
[Captivate Android Development] sdricke:
Same for me as well. Followed by cell standby, then wifi.
[Captivate Android Development] MikeyMike01:
Once the bugs get ironed out, and this works as well as the Eclair one, then my phone will be perfect.
[Captivate Android Development] tjsooley:
I cant wate till this is out of bets.

I love the eclair kernal.
[Captivate Android Development] Cezar`:
Thanks for adding 2e recovery on the list.

I have no force closes on the i9000 ROM (running JPM) but I do experience the 2 back buttons issue. And thats kinda all.

I wanna ask, as Im not running the JPM with this kernel anymore, I installed sheep's one, does this rom have any issue with the camera? does camera and video camera work?
[Captivate Android Development] shaolin95:
Well I was able to flash back zimage and modem.bin from Cognition beta 6 and get my signal back...any ideas what I did wrong...I really want HSUPA?
[Captivate Android Development] TMC_Sherpa:
Hey guys, long time no see, did I miss anything :D

xcalibur only modified a few files (around a dozen in the build I grabbed) so those are the ones I've been spending my time diffing. Unfortunately in my quick pass most of them I labeled UGLY 'cus I need to look at them more than 10sec to figure out the changes between 2.1 and 2.2. It also looks like at least a few of the files were coded by someone else 'cus there are quite a few coder preference changes. return 0 becomes int err =0 return err and that sort of stuff so that kinda throws off the change count.

Anyway back to work.

Sherpa
[Captivate Android Development] wpb2:
I have the 2 back button issue as well. I flashed it on top of Cognition 2.2Beta5.5. I flashed the kernel first then reboot. Then I flashed the modem.bin.

Worked like a charm with HSUPA enabled, and very low latency 95ms. Voice quality is excellent as well with the JG8 modem.

For the person that was asking about the camera. I tried both the video, and stills, and can confirm both are working great.

Is it just me or does everything seem faster on this kernel? From opening the gallery app to scrolling through pictures seem way faster. Am I crazy?
[Captivate Android Development] clrana9017:
When I used the i9000 modem file, I got only the 1900 mHz band for 3G. In the end, I just found the i9000M (Bell Vibrant) modem file and used that to get 850 mHz support.
[Captivate Android Development] daraj:
gotta linky for the JG8 modem or can u upload it plz?
[Captivate Android Development] boomerod:
See the OP of this thread.
[Captivate Android Development] daraj:
I must be going blind or something I dont see th JG8 file :D
[Captivate Android Development] TMC_Sherpa:
Too many threads about this kernel

http://xdaforums.com/showthread.php?t=791366

or http://www.multiupload.com/MEVE0ZNX1Q to just grab it
[Captivate Android Development] daraj:
got it. thanks
[Captivate Android Development] arffer:
Mixing kernels?

Today I have been running Shep's ROM and this reorient kernel and the JG8 modem. Few minutes ago, I made the mistake of getting trapped in recovery mode due to the power button not working as a selector for 'reboot'.

So I ended up odining in that 2e Kernel so that I could use the power key. That all worked fine, and I was then able to select 'reboot'. Then I figured that I would now have to re-odin in this reorient kernel, since I figured it had been replaced by the 2e kernel.

But to my surprise, all of the reorient features still seemed to be working (not in an area to verify HSUPA though). Auto-rotate is fine, Mobile AP is fine, external SD is fine.

I have verified that the 2e is also still working.

Oh, and my 'Home' button is again a 'Home' button, not a 'Back' button.

It feels like I have reorient with 2e running.

'About phone' shows my kernel is 2.6.32.9 jetaek.lee@sep-11 #1
[Captivate Android Development] Pirateghost:
if you flashed 2e in, then you are not running the reorient i9000 kernel.

you can use adb to get out of recovery mode also....
[Captivate Android Development] arffer:
That's what I expected. But then should I have not 'lost' the benefits of reorient listed in the OP?
[Captivate Android Development] SetiroN:
I believe you're using a Captivate kernel arffer, you shouldn't expect anything different than having correct rotate/SD/MobileAP/button functionality. :p

HSUPA will work with an i9000 modem, voice won't.

Thanks for your efforts xcaliburinhand, I really hope you'll change your mind about adding OC/UV, I've measured a quite decent bump in battery life while undervolting. :(
[Captivate Android Development] arffer:
You nailed it! Thanks :)

Tested a voice call, and no voice. So back to the reorient kernel it is.

BTW, ditto on the UV. I have no interest in OC, but the UV added life to my battery.
[Captivate Android Development] boomerod:
Anybody have any idea if UV is what DG is using in his Cog ROMs? The best battery life I've ever experienced is on Cog 2.1.6....was just amazing.
[Captivate Android Development] Pirateghost:
there isnt a kernel to support UV yet so no
[Captivate Android Development] boomerod:
Of course...dumb question...but thanks for answering it PG.
[Captivate Android Development] rrieter:
You must have kids, or you're just a big Dora the Explorer fan.
[Captivate Android Development] alkiter:
Same problem, plus doesn't charge in car dock. Gets very hot and battery runs down.
[Captivate Android Development] majinzen:
Alright, I've been doing some reading and seem to have found a viable culprit to the battery drain issue. Seems there is some wifi bug that keeps the phone from going to sleep when you set the wifi policy to "when screen turns off". At least that's seems to be the case with me. According to Spareparts, my phone is never going to sleep (even with the screen off) and it kills my battery (5-8% per hour). Supposedly, changing the policy to "never" fixes that but I hate having wifi on all the time and scanning every 5 secs. So I have it set to "never" but then I'm using a 3rd party app to override it and turn off wifi after the screen turns off. The app I use is Green Battery but there are others that do the same thing. So far, it seems to be working. If your having major drain while idle, install Spareparts and see if your phone running time is an abnormally high %. If so I suggest this solution. It has worked for me so far.
[Captivate Android Development] Exostenza:
Any way we could get one last version with voodoo sound 8?

Pretty please.
[Captivate Android Development] jswclw:
So based on reading this, I turned WiFi off. Now it is just sipping the battery. Only used 20% of the battery over the 8 hours since I turned wifi off - that's with ligh use: 20 minutes on calls, a little twitter, some email and some web.

I'm pleased with this result, but I would like to be able to acheive it with WiFi enabled. Do you think this is a modem issue, kernel issue, or ROM issue?
[Captivate Android Development] majinzen:
From what I've read, it's a samsung issue because I found the thread in an Android Central i9000 forum. Bug doesn't happen all the time either (kinda like the 50% without signal bug). You can keep wifi enabled (never sleep) and then use a third party app (I use Green Battery) to override the policy. My battery has been alot better and Green Battery controls the wifi better than the rom did. My wifi is set to go to sleep 5 secs after the screen turns off (instead of 15min) and doesn't turn back on until I unlock the screen. That way the wifi doesn't turn on if I just want to check the time or date.
[Captivate Android Development] no clue:
Does this file work for Samsung vibrant?

Basically, xcaliburinhand's creation enable Captivate owners to try any official 9000 firmware without issue. ( THANK GOD, I have a Captivate!!! )

How about Vibrant? I don't know how they operate in that forum. lol, they don't seems to have anyone provide step by step flash i9000 firmware and needed patch on vibrant?
[Captivate Android Development] boog:
I'm guessing, never tried, don't have a vibrant (yet, but I want one.)

I would say your chances of it NOT working would be high. I wouldn't try it. This was compiled for the captivate, and there could be issues from things just not quite being right, to a brick. I would wait for the devs in the vibrant forum to give you something more specific.
[Captivate Android Development] no clue:
Thanks for advice.

Local craigislist got couple vibrant on sale...... just wondering if I should jump on it. :)
[Captivate Android Development] arahma:
I used this kernel with Froyo on vibrant device and got good results, the phone boot up normally just some FC later. Keep the good work.