yashsingh1/xdaforums huggingface dataset:
[Captivate General] jasonyump:
Well, I dont blame him. He doesnt have a captivate, so Captivate owners,

we'll probably have to get a team together to port his Vibrant CM6 for the captivate.

I for one, will take the time to accomplish the steep learning curve and step up to work on porting it.

anyone else?

It will take time, but if we have people willing to, it can get done.
[Captivate General] Mithent:
I'm hoping that it will be relatively easy to port CM6 to all the Galaxy S series devices once it's available for one of them (or at least the GSM ones) - they're all very similar and the source is available.
[Captivate General] madjsp:
So, it's safe to say that we can take this thread away since nobody is going to do a thing for the Captivate?
[Captivate General] rrrrramos:
Things will get done for the Captivate. Maybe not as quickly as the other phones, but things will get done. Noting the fact that it's also the only Galaxy S that will be out on more than one carrier (in N. America at least) it should pick up some steam soon. It sucks that the Vibrant is getting all this done right away while we sit and wait, but be patient. It hasn't even been out for a month yet!
[Captivate General] :
Vibrants CM6 port will work on the captivate perfectly fine, people need to stop thinking of the vibrant/captivate as difrent phones..there not, there exentially the same exact device with difrent model number's, just like the htc touch pro variants etc.
[Captivate General] wakeupkeo:
I also donated to HansMartin for what he is doing with JIT. If Wes is opted out we should definately edit the first post to update and get dontations going to the right people.

jasonyump, I would love to help but I don't know code, but I would donate to a group who could actually work on this. It seems too important to get back to basics on the captivate (bluez, stock music, good ol' apps2sd, etc)
[Captivate General] TimF:
I'll help in anyway I can, I have a steep curve ahead as well, the I897 is my fist android phone and I only have a rudimentary knowledge of Linux but I'm a software developer, a fast learner and I enjoy a challenge.
[Captivate General] :
Koush also said that he has never planned a port for the Captivate......only a recovery. I miss my Nexus....well I miss the overwhelming support the nexus had.
[Captivate General] sl8125:
i do remember captivate owners flashing vibrant stock rom and using the userinit fix but most of them flash back to the stock captivate after the fix was modified to work on the captivate. As long as you have the modem/phone file we should just flash CM6 when its available and then just flash the modem/phone file. Vibrant and Captivates do share hardware and software. So no worries. Just wait and be patient. One thing though, i am not sure if kernels made for Vibrant will work on Captivate. Vice versa. Someone has any idea, please confirm this.
[Captivate General] hansmrtn:
I am going to be posting a new thread called project JIT. Any one will be free to try it and comment and figure out problems. I am still working hard on Just in time compiler.

EDIT:

Project Jit is up
[Captivate General] TexUs:
Have you tried it or seen anyone use it successfully? I haven't seen enough people to draw conclusions, especially to put down someone else for saying something to the contrary.

IDK if you've seen the Vibrant forum but their development doesn't look any worse than the Captivate's does. They got a speed fix a week or so sooner but it's not like they have a functional 2.2 release or anything, really.
[Captivate General] wakeupkeo:
So does that mean it is possible to get the vibrant version of CM6 on captivate that way? What would we be lacking in doing this?

I am looking for that bluez bluetooth implementation the most, so I can get the wii controller app running. That is a big positive to do this for me. But depending on what doesn't work with that method, the cons might outweigh that pro.
[Captivate General] dalingrin:
From what I can tell it looks like we could use the CM6 from the Vibrant as long as it plays nicely with the Captivate kernel.

The Captivate can't use the Vibrant kernel. The orientation sensor is different and either the Vibrant doesn't have the A1026 voice processor or it just configured differently.(the vibrant kernel on a captivate results in microphone distortion)
[Captivate General] hansmrtn:
It should be easy to swap the kernel with the soon to be 1.2 GHz kernel and fix the voice processor
[Captivate General] dalingrin:
Agreed. I believe that there will have to be a few kernel config changes to make the phones play nice with Cyanogenmod but most if not all them can be directly ported from Vibrant to the Captivate.
[Captivate General] staticfish:
I hope the rom cooks understand that not all of us want an overclocked or increased kernel speed. I think kernel level fixes are good, but modifications not so much.

Just saying
[Captivate General] iGuitar93:
:) Good suggestion
[Captivate General] hansmrtn:
Yeah, we will probably provide an OCed kernel in a flashable zip
[Captivate General] abuthemagician:
Wish I wasn't so useless at programming... Anyone have some sources where I could get started and maybe contribute that way? Right now I am totally broke and want to contribute... I am willing to test almost anything so keep me in mind for that.
[Captivate General] Kevin187:
So after reading through this whole thread, these guys (in the OP) have all since abandoned us? What's up with that?
[Captivate General] abezapata:
IT looks like we are by ourselves in this one guys. last time this was updated was ages ago. Almost a month and no update with progress. I feel sorry for everyone who donated.
[Captivate General] THATTON:
I spoke with Wes Garner from Teamdouche and he said that the Vibrant development is well underway but they don't have anyone who is willing to dev on the Captivate. Koush created the recovery image for it but that is about as far as it went. Someone needs to step up to the plate and get involved. I don't have the time with a wife that is 8 months prego and a full time job managing multiple at&t stores it is nearly impossible for me! What I may do though is send my Captivate to Wes or one of the guys from Teamdouche- kmobs, Cyanogen, Skepterr, etc and see if they can use it to dev. I will see what I can do. As it stands right now, my Captivate is sitting in a drawer anyways because of the lack of support in the xda community... Sad really. :(
[Captivate General] fiendiish:
I don't know why the Cap is getting left behind :( It's a great phone and NEEDS this..

It seems though that once the Vibrant is done...it shouldn't be too hard to dev for the Cap. Am I right in that assumption?
[Captivate General] iGuitar93:
Haven't people put stock vibrant roms on a captivate?
[Captivate General] fiendiish:
Yeah...but results are spotty at best..
[Captivate General] Ayle:
It doesn't work properly thanks to some kernel issues.
[Captivate General] Kevin187:
Why are they only developing for the vibrant? Shouldn't the captivate be getting more attention than the vibrant (since it's on a better carrier?)
[Captivate General] iGuitar93:
Ahh. Well then a cm6 vibrant port to captivate would be possible? We would just have to fix the issues? Correct?
[Captivate General] TexUs:
I would've assumed the Captivate would have more support than the Vibrant myself, as well: much bigger carrier.

However what might hold true is the G1 and Nexus One... All the Android devs went to TMobile and switching to the Vibrant is NBD. That's my assumption anyway.

It's really really sad nobody is stepping up to support this. I understand nobody porting a Froyo release in (I mean, Samsung is doing that, who cares)... What worries me is Gingerbread.

I also feel sorry for the people that donated. Honest thing to do would've been the devs at least saying they had no intentions of working on Captivate instead of allowing people to donate for something they weren't going to work on.
[Captivate General] TGA_Gunnman:
Koush has a Captivate

Wes has a Vibrant

Secpterr has a Vibrant

Eugene373 has a Vibrant

They are trying to make a one stop build for the Galaxy S (if it is possible).

A lot of devs go with T-Mobile not because the service is bigger or smaller but because the first Android phone (G1) was on T-mobile and the Nexus One was on T-Mobile first as well.

I know T-Mobile is a lot better now that they released their HSPA+ network I get 5Mbps down right now on my Vibrant. When the HTC Vanguard comes out I hear it will hit 21Mbps down. That I would have to see to believe.
[Captivate General] LinuxNewb:
But depending on your location, T-Mobile still sucks. In New Mexico their 3g will cut in and out constantly and have horrible speeds. AT&T is slightly bottlenecked depending on the hour of use but on my old iPhone 3g I was getting download speeds of 200kb/s.
[Captivate General] TGA_Gunnman:
yeah from the middle of the country to the eastern seaboard. T-Mobile is good. the rest sucks.
[Captivate General] derek4484:
Well T-mo is just about the big cities. I debated back and forth about whether to get the vibrant of the captivate. I went with AT&T because their 3G coverage extends further outside of the cities and is in areas that t-mo doesnt even have 3G. If I wouldve known that nobody was going to dev for the captivate I'd have never gotten it. Still may consider going with the vibrant, their plans are slightly cheaper and they have faster 3G speeds.

And to the other poster who mentioned Koush has a captivate, I'm not so sure about that. He did create CWM for the captivate, but he has said he's not going to dev any roms for it, just the vibrant. Creating the CWM update.zip file for the captivate was not complicated. Just like how there was an update.zip file out to root the captivate before it was even released. It was created based on the I9000 update.zip root file, just changing some text or strings in it.
[Captivate General] derek4484:
If the vibrant rom plays nice with the captivate kernel and modem file, thats a strong possibility. Since now you can take the I9000 rom and flash it to a captivate then flash the kernel and modem file back on it, and have a good working phone.
[Captivate General] derek4484:
Like the old Eagles song.."Took the money and run" :)

I guess they just dont like AT&T or something about the Captivate drove them to the Vibrant...who knows.
[Captivate General] derek4484:
Thats how I feel. I basically know squat about linux development, but am willing to learn, and have some free time. Just a matter of getting the right resource material to learn from. But by the time I learn enough to be useful, it may be a long time away and be of no help.
[Captivate General] AJerman:
Don't worry, that won't happen. The code can mostly be shared between phones. Even if developers of CM have Vibrants or I9000s, it can be adapted to the Captivate as well.
[Captivate General] dalingrin:
When did teamdouche ever explicitly say they were making a Captivate port? As far I know no one ever did.

I think everyone should calm down until the Vibrant port is done or at least working. Then we Captivate owners can see where we stand. Chances are with the help from a few of us we can get an official captivate port much easier at that point.
[Captivate General] kakalaky:
I'm not new to Linux or development but I have no Android specific experience. I already built the kernel from Samsung and vanilla Eclair. I'm currently messing around with creating a vanilla ROM but I will look into porting CM6 for the Vibrant to the Captivate once Wes Garner releases something.
[Captivate General] E_man5112:
Very disappointing, since they have the captivate on their homepage.
[Captivate General] atinm:
Remember, T-Mobile had an installed base of Android people so the "old-hands" were on T-Mobile and they have Vibrants. But there are developers on the Captivate already (see the lag fix thread, the 1.2 Ghz overclock thread, etc). They're just not part of teamdouche but there is nothing stopping us from starting development on CM6 right behind wesgarner - we can take most of the same code as he checks in his changes for the Vibrant. The developers focused on Captivate are quickly coming up to speed on the Captivate specific stuff - just give us developers some time! :)
[Captivate General] Shammyh:
Let's be honest. The captivate is a pretty new device. It will take time for developers to come, for people to become interested, and for the whole custom ROM scene to develop.

After all, AT&T is a MUCH larger carrier than T-Mobile (not that one is better or worse than the other, just referring to subscriber base), and even though T-Mobile was the original Android carrier, I fully expect many more Captivate's than Vibrant's to be sold.

Plus, I'm still pretty content with my rooted and bloatware-cleaned stock ROM. This thing is fast and capable no matter how you look at it, and like good cheese and good wine, it will only get better with time!
[Captivate General] Mithent:
Will be interested to see how the vanilla ROM goes - I don't have much experience with Linux or Android but have wondered why no-one's built an AOSP ROM yet (even if it wasn't entirely working at first).

I'm sure that CM6 for the Vibrant will be portable to the Captivate and the I9000 without too much difficulty once it's available.
[Captivate General] golemaw:
I agree, the Captivate is basically AT&T's first decent Android phone (AT&T does not subsidize for the Nexus One unlike T-Mobile). Before that, it basically all iPhone... So I guess there are many people like myself are new to the Android scene.
[Captivate General] raid0422:
I've got an idea... let's ask Scepterr and Wes Garner if we can send them Captivates so that they would be able to develop concurrently for the Vibrant and Captivate. We could even set up some sort of 'group buy', but then again, these phones aren't too expensive as it is.

Anyway, I don't know how to contact them myself. Maybe someone has their email addresses.
[Captivate General] BoostedSR20:
If the end result was getting CM6 on the Captivate, I would donate a good bit. I would need some good proof that it was going to be done tho. At this point I would just be happy to have a fully working, optimized vanilla 2.1 ROM...

I miss Froyo, CM, and Amon_RA recovery that I had on my N1. (my gf has an N1, so I still get to play with it once in a while)
[Captivate General] TexUs:
Honestly I'm happy with the de-crapified and speed-fixed Captivate which blows every other phone out of the water.
[Captivate General] _Opiate_:
Hopefully something will come to light soon. Really I just enjoy the fact that fooling around with my Captivate is completely different than my Nexus One or Aria, with the lag fixes and Odin and all. Its like something completely new!

Plus I'm already running CM6 on my Nexus AND my Aria so I'm not in a big hurry to run it on my Captivate as well lol.
[Captivate General] madjsp:
This is why you never pay until services are done.

If they never said they were going to be developing to the captivate, this post should have never been created.
[Captivate General] ranova:
I was very sad to see that Cyanogen's news update did not include the Captivate, but did include the vibrant:

http://www.cyanogenmod.com/home/cyanogenmod-6-0-status-update

:(
[Captivate General] TexUs:
What the crap? Is this the Vibrant, perhaps?

I was happy as can be with my 2200 Quadrant score on the Captivate, CM6 is definitely needed to be ported to the Captivate if this is true and is the Vibrant!
[Captivate General] Zilch25:
He posted that to illustrate how easy it is to bug out Quadrant =P
[Captivate General] BoostedSR20:
:eek: :eek: :eek:
[Captivate General] BoostedSR20:
Yeah I remember reading a tweat from Cyan on howto do that with Quadrant.
[Captivate General] Zilch25:
"To get that result, I just mounted a tmpfs over Quadrant's data dirs. It's a good benchmark but easy to "cheat" at."

:)

Put your tongues back in your mouths guys
[Captivate General] BoostedSR20:
What is your Linpack score? I'm getting high 9's with a quad score around 1060. On my Gf's N1, with CM6 and a stock clock, gets high 30's in linpack, and a 1300ish quad score.
[Captivate General] Zilch25:
You're not going to beat 8-9mflops without an overclock or some ridiculous OS improvements. Quadrant scores of 2200 are due to the lagfix which *only* effects I/O function, not CPU power.
[Captivate General] BoostedSR20:
My high 9 score *is* with an overclock to 1.2ghz.
[Captivate General] TexUs:
8-9...

.

Characters
[Captivate General] Kevin187:
Agreed. Why was this thread ever created in the first place? Seems a little like false advertising.
[Captivate General] circa_rider:
any new news on this mod?
[Captivate General] Zilch25:
Still in development with focus on the vibrant =P Once it's out I'm sure there will be at like 10-15 new threads of people either testing the vibrant version or begging to have it ported :D
[Captivate General] hansmrtn:
Vibrant support is supposed to be available in CyanogenMod 6.1. So it may be a while
[Captivate General] ed10000:
Any status updates at all? I haven't seen anything on twitter either.
[Galaxy S I9000 General] Enarca:
Is it me or has this so called lag been blown completely out of proportion with the SGS? I used to have a HTC Hero, I tell you, it's like going from riding a snail to a rocket fuselage. That phone was so slow, a phone may I add which only a year ago was seen as the 'iPhone killer'.

Please are there any previous HTC Hero users who now own a SGS? You have to speak out!

I mean sure, I've used a HTC Desire, it's very fast. But the only difference I have noticed is that on the SGS sometimes Apps take around 3secs longer to open than they should. That's it!! I mean, why are you all complaining so much! It's just as fast as the Desire except that point.

I have now had the SGS for 2 weeks, I haven't noticed any considerable slowdown. It works great! Why are you all complaining like babies? Have you installed Crysis 2 on your SGS or something, obviously your phone would never work again if you did that. Before anybody asks, I have made no changes to my SGS. I have an unlocked SGS, still on Touchwiz, no flash, no root. I don't even use task killer for God's sake. Please would someone explain to me what the big deal is?
[Galaxy S I9000 General] Robin.B:
What you have to realise is that it's not an always persistent problem. The phone in general is extremely fast, however with earlier firmwares the phone does not free up memory effectively. 3 seconds is nothing, but I recall sometimes waiting 10-15 seconds for the Dialer to launch. And when the memory is really really clogged up, it's a complete pain even pressing the home screen button (waiting 10 seconds to go to home isn't pretty either). For a phone with so much power, do you really think this is normal?
[Galaxy S I9000 General] Enarca:
The difference must just be that I'm not a heavy app user. I still have the stock firmware the phone came with. Never had a 10 second delay with anything. Never noticed any sort of build up of lag. It works great! Do you guys install like 50 apps on your phones or something? Clearly that must be your problem.
[Galaxy S I9000 General] Tachikoma_kun:
I have never had any problems either (other than with flaky GPS).

Someone told me how to replicate the lag issue, and it boiled down to having 8-odd apps running in the background at once. I would expect the same on my multi-core 4GB RAM iMac, let alone a phone with 256MB RAM.

Not saying others are only having problems with the above situation, but it does seem like there are specific factors that cause it, which is why a lot of people have had no problems.
[Galaxy S I9000 General] Pika007:
The phone has 512mb ram.

Just that currently, HiMem is not available (will be in froyo as a default, and if we're lucky, in the JF6 firmware as well)
[Galaxy S I9000 General] Tachikoma_kun:
I know, but until we can actually use it, we are limited to 256MB (or was it 232MB?)
[Galaxy S I9000 General] djurkash:
SGS has 512MB RAM
[Galaxy S I9000 General] tameracingdriver:
+1

And although I am not a really heavy app user, I am a heavy user, and it wasn't hard to make the phone lag quite heavily at times, so I'd say no, it has not been blown out of proportion.
[Galaxy S I9000 General] eaglesteve:
+1.

More serious in some applications like mails, RSS reader. It's so slow that I don't even use my SGS for my mails, or to read news anymore.
[Galaxy S I9000 General] bookwormat:
Tachikoma_kun,

Please understand that Android does not work like the Mac OSX on an iMac, and that, if you open 8 odd apps in a row, you should _not_ have them all running in the background at once.

Android's memory management should close applications and free memory as needed. Processes will start if needed, be set to inactive as long as possible and killed if necessary. This works fine with other Android devices and obviously not with the Galaxy S.

You can read about the life cycle of Android Components at

http://developer.android.com/guide/topics/fundamentals.html

Using a task killer to free up memory might make your Galaxy S faster than not using one, but this is still a lot less efficient than it should be. In a working Android system you should use the most out of your available memory and the system should stay fast as you open and switch between applications. You should never have to think about which applications are running or not running.

Again, this works just fine with other devices. If it does not work with the Galaxy S then this is a serious flaw in the system. The flaw might be related to the slow I/O on the internal SD, or maybe there is a firmware bug besides the I/O. But it is currently not working correctly.

If you have access to 256mb memory of RAM, and you use a task killer to always keep 100MB free, then you use your device like it only had 156MB.

I also do not believe that the average customer without a technical background is able to use a task killer without shooting himself in the foot. Without knowledge about what each application and service does, and how android manages background processes, how should a normal user know what he can kill and which services he should keep running?
[Galaxy S I9000 General] quinckekorotkoffqk:
lag problem blown out of proportion. May be froyo update will satisfy the hunger of these power hungary geeks.:)
[Galaxy S I9000 General] Enarca:
I just don't get it. I've never had this problem. Emails and news update perfectly with no lag.
[Galaxy S I9000 General] eaglesteve:
Perhaps whether a person thinks it's slow or not depends on what that person was used to?
[Galaxy S I9000 General] AllGamer:
That is exactly what i was telling people.

I come from the HTC Athena, and OMG... that thing is like crawling on sand, even with its super duper 625 Mhz CPU which by then was supposed to be the state of the art.

yet everything i did was sloooooooooooooooooooooooooooooow, using the SGS was like smooth flowing water, everything is perfect in this phone out of the box.
[Galaxy S I9000 General] ksizzle9:
Im not a SGS owner but i keep noticing the reference to the desire. I did own a snapdragon device until about a week ago. (Droid Incredible). Switched to droid x. The only real reason i believe there is lag on the samsung is the touchwiz. The cpu&gpu in the SGS IS FAR SUPERIOR to that of the desire. Htc just has the most polished custom ui. If u get launcher pro id be willing to bet that lag is gonzola in a hurry. Maybe give this a try? Just trying to help my fellow androiders out. Goodluck fellas
[Galaxy S I9000 General] AllGamer:
what made you choose a Droid X vs. a SGS i9000?

the 2 phones are almost identical, except for the camera.
[Galaxy S I9000 General] penfold:
the lag is very real.

try opening Dolphin HD and then closing it again .....about 8+ seconds to do either, and that's with nothing else open.

instantaneous on the nexus with 2.2.

some apps are much slower than others, some there is no difference, but even the default samsung apps such as phonebook have a good lag when switching between tabs.
[Galaxy S I9000 General] Enarca:
I agree. I'm guessing you haven't used/owned a HTC Hero? If so, you haven't experienced the PAIN!! lol.