yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] tg9413:
Not sure if this has been asked but i cant digged up the answer from the previous 300 or so pages.

I followed the instruction and after I flashed the initial kernel from odin and try to boot into recovery to install teh actual zip, i keep getting a blank screen after the AT&T logo and the 4 buttons on teh bottom of the phone lit up. Retried a couple of times, and all showing the same result. Thanks in advance.
[Captivate Android Development] joeybear23:
Is there anywhere I can go to see what is in the works? Not looking for timelines, just an idea of what kinds of things are being looked at/worked on.

This is my daily driver, and it has been outstanding, but I look forward to when we are able to get as far with Gingerbread as we have with Froyo in regards to tweaking it for performance and battery life.
[Captivate Android Development] Kaik541:
issues list available in the instructions or twitter.com/cmsgsteam
[Captivate Android Development] jbcap43:
Has anyone had 55% battery life left, then did a reboot and have 77% after a simple reboot? Very odd to me!
[Captivate Android Development] zuN!:
Upstream updates?
[Captivate Android Development] Crusty_Demons:
Anyone else get an unsigned type error flashing the latest nightly update?
[Captivate Android Development] Thegodfather156:
Not here. Flash went flawlessly
[Captivate Android Development] cumanzor:
edit: disregard that, I was looking at the wrong model.
[Captivate Android Development] vvaffles:
mm im getting status 7 errors

edit: nvm fixed, i just had to boot into it once before flashing the update
[Captivate Android Development] wonsanim:
Same here,flash is a GO:cool:
[Captivate Android Development] bugity:
Ya not those exact numbers but inconsistant percentage after reboot is common in my experience.
[Captivate Android Development] nybmx:
Yeah I have those kind of inconsistencies as well. Not always but some times.

It will almost always happen though if I reboot with the phone plugged in and charging. However I remember experiencing that a few times as well on 2.2.1.
[Captivate Android Development] atinm:
There is an actual hack in the samsung kernel that was intentionally lying to userspace about battery that they took out as well with this exact comment. We haven't taken the time to figure out what the actual bug is here and fix it.
[Captivate Android Development] Aus_Azn:
Hm, I was wondering if anyone has the same peculiar thing that I do... (EDIT: Search has yielded nothing.)

Last night, when I turned my phone off for the first time since 16-Mar to flash the latest nightly, the phone began to not respond, instead showing the kernel bootup screen, then going into a reboot cycle while being basically unresponsive to the recovery mode button combo (VolUp-VolDown-Power), and the download mode command only working when I was connected to my PC. The phone does a normal bootup once I attach it to the computer, but still no dice into recovery.

Any ideas?
[Captivate Android Development] jbcap43:
Sweet thanks, not a big deal, I kind of like rebooting and have more battery!
[Captivate Android Development] slayp00n:
Guys quick question, runnning stock 2.1, or a custom 2.2, b y navigation would use the default voice I set in settings, it also said street names.

Since using CM7 I notice Nav is using its own voice selection and not reading street names.

My GMAPS is upto date.

What is going on?
[Captivate Android Development] 60hzrumble:
Did you turn the phone off while connected via USB?
[Captivate Android Development] Aus_Azn:
Maybe, but I've done it both on and off USB, not just a charging cable. It powered down through the power menu, not by just holding down the power button.

I just shut off my phone again; I'm going to try forcing download mode when I get access to my home computer. Worse comes to worst, I'll just reflash the CM7 initial kernel while its bootlooping or if I manage to jumpstart it on my PC.
[Captivate Android Development] Enhanced:
Anyone notice better battery with the new nightly?
[Captivate Android Development] stuff:
I've had times where my battery, after putting on a new kernel, said I had 5% battery life remaining. (Before the flash it had 40%)

Then just after time, about 2 hours later, the percentages jumped to around 35%. I watched it increase, and I lol'd.
[Captivate Android Development] techmik67:
Put it on your phone and see.... =)
[Captivate Android Development] peachpuff:
Its aosp meaning no touchwiz, that's the biggest feature.
[Captivate Android Development] ballz0iron:
actually 2.4 will still be called gingerbread. it is going to add support for apps written for dual core phones/tablets on single core phones
[Captivate Android Development] sold1erjjt:
Ok I know this might sound bad, but I am having FC's on the Market. It loaded the first time I flashed Gapps, and now it wont even load. I tried flashing Gapps again then clearing cache and no avail. I could use some advice, do i need to reflash the whole ROM?
[Captivate Android Development] TheEscapist:
Its a feature that Samsung broke in the official roms. Basically, the apps you download are linked to your google account, and when you use a "new" phone, it redownloads all your apps for you.

I never said it wouldn't. 2.4 is gingerbread, 3.0 is honeycomb, the next release after that(numbering wise, and disregarding in rom updates) will be ice cream.

Probably your best bet, sorry.
[Captivate Android Development] sold1erjjt:
Yeah no prob, I know it's a test ROM and its got bug. Thanks It's so fast

Oh and if you know, when they say "Wipe" that is wipe the Cache right?
[Captivate Android Development] coderunner:
I know that a known issue was have wifi sleep when the screen is off, but I just realized it has been set that way all day and I haven't had any issues.
[Captivate Android Development] seclm193:
So there possibly won't be a honeycomb version?
[Captivate Android Development] mcord11758:
I believe wipe means factory reset
[Captivate Android Development] mcord11758:
Can we curb the honeycomb talk considering this is our first taste of gingerbread ;p
[Captivate Android Development] TheEscapist:
Of course not. Honeycomb is designed for tablets. Yeah, people will hack it on phones, but cyanogen will almost certainly not support a honeycomb.
[Captivate Android Development] QuarkGluonSoup:
What do you mean? I thought all android was, by definition AOSP.
[Captivate Android Development] jhego:
Can i still use Serendipity's kitchen apps? I still like to use the Samsung calendar and clock.
[Captivate Android Development] bay_wolf:
Just reflashed it as I thought something may have went wrong when I used Titanium backup so I'm not using it this time and so far it is running solid.
[Captivate Android Development] sold1erjjt:
Oh really? hmmm yeah can anyone second this. This might be why my market was FC'ing
[Captivate Android Development] bay_wolf:
I just did both to be safe. And one more thing... the GPS is the best I've ever had on the captivate even with all the fixes. I get up to 10 sats locked in about 10-15 seconds where I couldn't get any before.
[Captivate Android Development] TheEscapist:
Probably not. The samsung apps probably rely on the two framework. For example, the Samsung messaging app doesn't work.

AOSP refers to it being stock android, with no custimizations, as opposed to sense or touchwiz. That's not entirely true, as cm has some small additions, but its the closest you see to aosp on most non nexus phones.
[Captivate Android Development] brendanmurphy:
Is auto rotate not working? I cannot get any app into landscape except the ones that are landscape only :(
[Captivate Android Development] TheEscapist:
Works here. The orientation sensors are a bit sketchy, make sure auto rotate is on, and try rebooting.
[Captivate Android Development] Aus_Azn:
Why does it feel more sluggish despite the mandated EXT4 and thus built in lagfixes?

Any explanation?
[Captivate Android Development] zas0006:
I am having an issue with the built-in blacklist. I found a bug in the tracker the other day, but it was closed. The issue is when I get a call from a blacklisted number the phone rings, but doesn't display anything. The only way to make it stop is reboot (as recorded in the original bug report) OR toggle through all available ring options in the notifications bar.

I did a logcat right after it happened from my phone so sorry if it is not exactly right. If I need to do something differently, let me know. I know I can do logcat through adb but the issue happens more during the day when the people are trying to call and I am not near a computer with adb capabilities.

Here is the logcat:

http://db.tt/kOek6sB
[Captivate Android Development] :
My data has been very crappy today, should I try a new kernal or could it be my network?

Wifi works very well by the way.

Nevermind, at&t must have had some kind of outage.
[Captivate Android Development] smeltn:
good to see an update. Flashing now.
[Captivate Android Development] cesierra:
no changes here
[Captivate Android Development] general-tso:
When is stable version going to be released

Sorry... I have n00b question. I have ATT Samsung Galaxy S froyo 2.2 and can't change ROM because of the 2f bootloader. I am thinking of reflash to 2.1 with ODIN and try CyanogenMod for Captivate because of its popularity. It's a great honor for Captivate user to finally gets CM7.

My question is: what's the benefit of having Gingerbread instead of (stock or custom ROM) Froyo? Does anybody have stable Gingerbread for Captivate?
[Captivate Android Development] heymanator:
Current nightly build 03-29-2011

I have no icons displayed in my drop down notification bar. (Example - Wifi, Auto-rotate, Silent) I have no icons whatsoever. Any else having this problem?
[Captivate Android Development] tiuk:
You can customize what buttons you want to show in cm settings, think it's under interface. One of my favorite cm features. Maybe yours got cleared somehow
[Captivate Android Development] mkoby:
You've got your android desserts mixed up.

Gingerbread = Latest available mobile phone version.

Honeycomb = Latest tablet focused release

As for what's in Gingerbread, you can look here
[Captivate Android Development] nkrick:
I believe that Google keeps track of what you remove also, so if you get items automatically restored, if you then remove them using the market, the next time you flash, it should not restore those apps again.
[Captivate Android Development] chappatti:
Is this the final gingerbread release or the beta?
[Captivate Android Development] EnemyOfGlaDOS:
It is beta.
[Captivate Android Development] Rikusaki:
First of all, don't ask for ETAs. :mad: Read the first post for known issues/bugs. From my experience, it's pretty stable and everything I need works (Huge performance improvement over 2.2.1).

Second, Gingerbread is 2.3, not 3.0 (Honeycomb, the tablet OS). :)

Third,

http://www.youtube.com/watch?v=Jx3pdWBlZ34

:D
[Captivate Android Development] TheEscapist:
*facepalm* Have you read nothing about this rom at all?
[Captivate Android Development] Enhanced:
Unfortunately, that wasn't the case for me. It installed several apps that I didn't use on my 2.2 ROM but that I did use previously a while ago. I think it may have to do with the list under "My Market Account" on the web version of the market not being updated correct (and hasn't been since the new layout was launched).

Unchecking backup and auto-restored prevented it though.
[Captivate Android Development] skatcat31:
Are there any plans to attempt to build CM7 on the official i9k 2.3.3 and then bring that over? I have a feeling it could help solve quite a few issues if done that way. JW of course, and a simple no will suffice. Looking forward to when this rom becomes a daily driver(unless I switch to an insipire of course)

EDIT: Or of course using it's kernel and drivers to fix the current problems with some reorienting?
[Captivate Android Development] DamnMersault:
CyanogenMod is compiled from source. It is not built from any other ROM. This is not winzipdevelopment.
[Captivate Android Development] s1l3nt:
question has been asked several times already would of seen it if you read
[Captivate Android Development] atinm:
Right - no source == doesn't exist as far as we're concerned . . .
[Captivate Android Development] TheEscapist:
Its an AOSP kernel, adapted from the Nexus S.

AOSP kernels and Samsung (firmware) kernels are not interchangeable. If the goal was to port AOSP to the captivate, and they were interchangeable, then yes, it would make sense to use it, at least temporarily.

However, CM, at this point, is an Android distribution, meaning that if they want to be officially supported by cyanogen, they have to play by his rules. That means a full, clean port, using only CM code. They aren't even allowed to modify anything other than the device trees and the kernel with out the mainline CM team's permission.

If you have any other questions, I'm happy to answer them, assuming they aren't easily findable on either the Q/A thread, this thread, or the CM forums thread, but I'd appreciate them being asked in the Q/A thread, or by pm.
[Captivate Android Development] TheEscapist:
Ohh, now it makes a little more sense. I thought you were one of those of those guys who though Samsung firmware == CM roms. :rolleyes:
[Captivate Android Development] skatcat31:
Oh god no... Samsung firmware is helpful in only seeing what could be changed to help on the kernel level on CM7 and possibly optimizing. Well as long as source is available.
[Captivate Android Development] Mr. Clown:
Did another cleaning to this thread.

Hoping that I don't see another report of this thread soon.
[Captivate Android Development] phat_cow:
Any reason why *#2263# doesn't work on this rom?
[Captivate Android Development] Kaik541:
this isn't a samsung ROM would be guess number one
[Captivate Android Development] h0ckey10:
Try reflashing the initial kernel.tar in Odin with reboot off and see if u can get to recovery
[Captivate Android Development] InfDaMarvel:
I noticed there is a updatefor cm7 fo the captivate. But the only update im looking for is the one where the external sd card works. Is it okay to just skip this update and use th next or should it all be updated in order?
[Captivate Android Development] Haloruler64:
They're cumulative, flash the latest and you'll be fine :)
[Captivate Android Development] EnemyOfGlaDOS:
taking a stab in the dark, but i would guess the latest update includes previous fixes .. so I would say you can skip this update and catch up on another update down the road. But maybe somebody else can confirm this..:)
[Captivate Android Development] Enhanced:
From the Q&A:
[Captivate Android Development] zaures:
could have just said yes...
[Captivate Android Development] jhernand1102:
Could have read the OP and FAQ...
[Captivate Android Development] Haloruler64:
Could have had a V8...
[Captivate Android Development] TheEscapist:
Could have had an updated sig... :p

Sorry, couldn't help my self.
[Captivate Android Development] derekedw:
After much thought I have decided to move off of CM7. As much as I love cm7, the development seems slow and severely lagging behind the cm7 RCs. Most of the bugs that get reported get turned down for various reasons and the battery life is horrid. I hope things improve at some point, but its still very beta and not moving quickly at all. And since we can't ask how things are going and eta's etc, all I can do is move to stability and monitor cm progress.
[Captivate Android Development] Haloruler64:
Well played sir, brb updating :P
[Captivate Android Development] InfDaMarvel:
So true, I assumed it was a yes anyways. Op is huge.
[Captivate Android Development] mcord11758:
Thanks for sharing
[Captivate Android Development] nybmx:
It's understandable. If you follow the logs of the devs IRC you'll see just exactly why things are so slow. Their main focus right now is merging with mainline and you can see time and time again that they're submitting things and getting rejected or having to redo some things and then waiting for approval etc. It honestly seems like a headache and I'm glad I don't have to personally deal with it. If you ever want to see the "behind the scenes" on what is going on as far as development give it a look.
[Captivate Android Development] jbcap43:
Its true, things are slow because they are waiting on bits and pieces of code! I'm pretty good with computers and everything, but I give these guys a lot of props, I've looked into building ROMs from source and all that jazz.... its not easy, and damn sure doesn't look fun... patience is a virtue! And CM7 is by far the best ROM out right now!
[Captivate Android Development] zehuali:
Will you consider to rebuild the CM7 with the newest XXJVK rom but not the nexus s rom?
[Captivate Android Development] TheEscapist:
No.

ten char.

Sent from my SGH-I897
[Captivate Android Development] heymanator:
I checked settings and my settings are fine. Still no icons in notification drop down bar
[Captivate Android Development] nybmx:
Setting>Cyanogenmod settings>Interface>Notifaction power widget (make sure this is checked)

After it is checked go down to "Widget buttons" and select the ones you want in there.
[Captivate Android Development] skatcat31:
Don't ask. Since there's no source, it's worthless. They need source to build the kernel, so right now it's still nexus S until we get a ginger kernel source.
[Captivate Android Development] puneet_champ:
any respite for the unlucky ones with dropped connections on i9000 roms? I see that the kb1 modem file still has the march 4 timestamp, so it has not been updated. Last time i used this, the voice quality was really bad. Is it still the same?
[Captivate Android Development] nybmx:
I'd reccommend an I9000 modem with this rom. Much less complaints from people who use them. I've personally always used JK4 and never had an issue.

Also as far as modems these aren't built by the CMSGS team. They are repackaged ones from Samsung. From what I understand building a modem from scratch would be near impossible without the resources some of these companies have.
[Captivate Android Development] snorkle:
Humm so i was watching tv and i had left my phone on my desk, i come back like an hour later, i take off the cover and when i realize that the phone is running really hot. At the bottom on the other side of the Menu, back , home and search, the rest was pretty cold. idk why it was so hot..i even had data turned off to save power.
[Captivate Android Development] heymanator:
I did still wont show
[Captivate Android Development] heymanator:
This is my problem. Everything is checked no icons......weird.
[Captivate Android Development] snorkle:
try rebooting?
[Captivate Android Development] heymanator:
Rebooting didn't work but reflashing the rom did problem solved.
[Captivate Android Development] rajendra82:
Thanks for the informative update atinm. I am still waiting for CM7 to mature a bit more on the SGS line, before I take a the plunge, and I am sure I am eventually going to do it.

This is a dumb question from a non developer, but what about porting binary drivers from the JVE and JVK leaks. Will that help in squashing a few more of the bugs instead of working with the non compatible Froyo drivers? Is any work being done on that front?

I am surprised how far back from being bug free and feature complete CM7 on Galaxy S is though. This is not a criticism of teamhacksung working on the port, but CM7 on a hardware as wildly different from Nexus S as the Barnes & Noble Nook Color seems to have progressed pretty far, adding things like missing bluetooth support, while we can't get the audience chip utilized on the Captivate, or have a way for modems from i9000 be used reliably on the older Captivates without losing cell tower connection after full charge. I have Froyo, Gingerbread, and Honeycomb working on my Nook Color, with obviously no sorces, leaks, or any help from Barnes & Noble. That is the kind of initiative I was hoping for on the Captivate, not waiting on Samsung. Because we know how long that takes. At some point in the near future, Samsung is going to go EOL on us, and will not port IceCream or Jellybean to Galaxy S. Is CM8 or CM9 on SGS going to be abandoned because of lack of sources from Samsung?
[Captivate Android Development] citrit:
Thanks devs for all your hard work, it truly is appreciated and thanks also for the explanation of the dev efforts.
[Captivate Android Development] atinm:
No, we cannot use the binary only stuff from Samsung that shows up in leaks. If we could, we would have. I hope people understand that binary only stuff is even worse than froyo source - it uses private interfaces to Samsung daemons and apps in user space plus we have no idea *what* it does in the interface. We cannot run the Samsung daemons and apps, and we cannot just take the binary drivers, it just doesn't work that way . . .

No source code == it doesn't exist.
[Captivate Android Development] Zilch25:
To be fair the B&N Nook Color has a lot more source available since B&N doesn't seem to feel they're exempt from GPL.

On top of that the hardware is well known enough that devs were able to get non binary source for the drivers from Texas Instruments directly =P
[Captivate Android Development] atinm:
You didn't understand my post explaining why Samsung SGS is different from all the other manufacturers and even the Nexus S . . . try reading it again . . . especially the part where I talk about where Samsung SGS is an outlier, and quite different from other manufacturers and even the Nexus S.

Nook Color is a straight up standard Android device software wise with almost all the kernel code for the device available. SGS is not. And yes, as long as Samsung keeps using proprietary interfaces and not releasing code, we will have bugs.
[Captivate Android Development] adzidek:
What's JellyBean? 2.6? I don't see whole lot of info on the web...
[Captivate Android Development] TheEscapist:
He was joking around, we don't even know what Ice Cream is really going to be called, let alone its version number. Jellybean is at least a year away.
[Captivate Android Development] comdei:
Well lets just hope a i9000 get the source code someday.

I suspect it to come very shortly after the i9000 gets gingerbread.

(i9000 seems very fast at getting on opensource.samsung)

For now you guys are doing amazingly.

Someone should explain why you can't use binarys...

I'll do it.

Layman's terms

Essentially a binary file is a compiled(put together) finished product.

It is nearly impossible to edit these. Thus it is hard to use these to make new kernels.

That is all.
[Captivate Android Development] rajendra82:
Fair enough. Since your understanding of the issues far exceeds mine, I'll take it than Nook Color was easier to run AOSP on, while it is harder on the Galaxy S.

But then, doesn't that make CM on Galaxy S pointless, in a way? Isn't the whole purpose of CM, built from AOSP, to free yourself from the control of the manufacturer and keep running the latest version long after the updates stop coming from the hardware vendor? If we can never free ourselves from Samsung, and will have to wait on them to release source before all of the hardware features will work on a given version of android, we are SOL when they stop updating. Is the situation going to change in the future in some way?
[Captivate Android Development] comdei:
Probably not, samsung really ****ed up their phones.

I don't know why I can't stop using them ^.^
[Captivate Android Development] random1204:
For some reason with the 29 update I can't change the wallpaper? Whaaaa?

PS - You guys are all awesome. Thank you. :)
[Captivate Android Development] TheEscapist:
Wall paper changing works fine here.
[Captivate Android Development] loraque:
It is because the SCREEN on the TouchSCREEN interface looks so much better. :)

Until the other LCD screens out there can compare, I will deal with the fiddly bits like GPS and whatnot.