yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] michael.seltzer:
I have download mode right now but I have a build 1008. Will i lose download mode?

Sorry if thats a support question.
[Captivate Android Development] wvumaniac79:
Flashed this, for about 10 minutes before going back to my normal. I cant wait for a stable build!
[Captivate Android Development] delugeofspam:
I'm excitedly watching. Too new a Captivate owner to feel like flashing this yet.

If I end up using a stable release I intend to donate to it. Looks like a lot of hard work is going into this.
[Captivate Android Development] used2hvatreo:
Can some people not access download mode using the method where you remove the battery, putt batt back in, hold vol +/- at same time and plug in usb?

I'm gonna go do some reading but I thought this was a hardware dl mode trigger that was universal for captivates, similar to using the hardware jig.
[Captivate Android Development] sqweeto:
That's so funny, I posted that method a while back on xda and still use it every time using Odin. Glad to see people are using it to solve their problems.:)
[Captivate Android Development] aleadam:
Supposedly not, but I read some posts of people having problems with it. I have a 1007, so I wouldn't know.

Ask Michael ;)
[Captivate Android Development] xtremekilla09:
Flashed it about six hours ago and has been running smoothly.

I dont use 3G and I don't use my cell phone camera that much either. So, for me this 2.3 ROM is amazing. I love it.

Thanks DG - u are the best.

EDIT: Oh and that screen off animation is awesome. I am sitting here just turning my screen off and on. LOL
[Captivate Android Development] darvo:
I never had to pull battery but holding both volume buttons and just plugging usb always worked for me.
[Captivate Android Development] JamieD81:
maybe this can be used as a base now?

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

just a thought.
[Captivate Android Development] designgears:
Its the same, everyone is working together on the gingerbread port to all galaxy s phones. Cyanogenmod are putting their usual theme and such into it.
[Captivate Android Development] JamieD81:
ahh didnt think it was due to the thought a dev phone would get alot more support then our phones, my bad :P

keep up the good work will try each version that comes out!
[Captivate Android Development] lowlymarine:
It's not just you, I did a reset to JF6 -> Assonance 5.2 (Setirion 1.4.7 with ext4 /data, so I know that's right) -> this, and I just get sent back to into FroYo on reboot, like nothing had flashed. Tried a couple times.

Edit #1: CWM is complaining that it can't format "SDEXT," which I assume is the external SD card. I'm going to backup and install my MicroSD (perhaps wise that I hadn't yet, since it was where all my backups were!) and see if that fixes it.

Edit #2: Tracked it down to an issue with apps2sd(?), but I wasn't able to get it fixed. Started the whole process over (JF6, master clear, etc.) and used COgnition as a base and everything went straight through, no problems.

Well, I had lots of other, non-phone-related problems in there, but that's not anyone here's fault. :p
[Captivate Android Development] nbs11:
I am having the exact same issue as you. Let me know if you can fix it. I have tried 3 times and nothing. If I can't find a fix I am planning on just flashing cognition to do this, but I don't have a windows computer to use for ODIN atm.
[Captivate Android Development] g1ddy:
Is this a CWM flashable vs Odin flashable version of the kernel found in the other thread?

If I decide to go back do I just have to reflash a custom kernel with CWM?

Thanks.

P.S. Awesome work you guys!!!
[Captivate Android Development] JamieD81:
im back on ginger clone v5 with xcaliburinhand's kernel for now, but my orientation isnt working at all, just stays vertical, setting is selecting to auto rotate and nothing.

edit: reflashed gingerclone and seems to have fixed it.
[Captivate Android Development] flashman2002:
Once you are runnIng gb you have no access to recovery so going back would be done using odin or heimdal.

This is my captivate. There are many like it buy this one is mine.
[Captivate Android Development] King Shady:
guys if i am running assonance 5.2 can i just flash this right over? thanks :)
[Captivate Android Development] RockRatt:
To keep with DGs request I am not asking or saying any bug issues here but would like to hear others thoughts and such on my post in Q and A section. I have been using version 3 for about. 5 hours now andamlooking forward to GingerBread now. Great work DG and any other collaborators.
[Captivate Android Development] Dani897:
yes if that uses voodoo 5

the whole flash to stock thing is a precaution not a rule. this particular rom needs to flash from froyo with voodoo 5 or ulf with appropriate settings and cant flash from stock. as a precaution you might want to clear data/cache/dalvik cache in advance but i dont think it's at all necessary.
[Captivate Android Development] techmik67:
FANTASTIC quote!!
[Captivate Android Development] g1ddy:
same thing here. I tried getting the zImage file from the zip and flashing it using Neldar's kernel flasher and it wouldn't boot. Reverted back to perception with Sentiron's kernel for now =(
[Captivate Android Development] designgears:
build-4 is live!
[Captivate Android Development] TheEscapist:
Flashed this, but it booted into my froyo build. Should I have wiped my

Ginger bread install out of /data first?
[Captivate Android Development] mcord11758:
May be a dumb question but I am on docs port which is 2.2.1, with xcal kernel. Its it safe to flash this our do I need to boot up a 2.2 rom?
[Captivate Android Development] jdbeitz:
Hey dg, does this fix the random reboots in standby?

Sent from outerspace
[Captivate Android Development] designgears:
Read the OP

2.2.1 is fine.
[Captivate Android Development] jdbeitz:
Oops :) haha. Thats when you just ignore me!

Sent from outerspace
[Captivate Android Development] ColonyDude:
So where is the support or bug reporting thread? Can you put it in the OP (I sure hope I did not miss it). I still don't see my external SD card.
[Captivate Android Development] TheEscapist:
There isn't one.
[Captivate Android Development] Khaos-Rage:
You could post it in the i9000 dev forum that's were the post is. But if you take a look at the Commit History on github the latest commit is
[Captivate Android Development] designgears:
Coolya or codeworkx is working on that, not me.
[Captivate Android Development] h8rift:
I have nothing against DesignGears, please note that.

DG will not be fixing anything on this port/ROM. You need to understand that this entire Gingerbread port are headed by supercurio and codeworkx. They are laying the groundwork for the i9000. xcaliburinhand's fantastic (I can't stress enough how important his work is to our community!! Thanks man!) kernel work is the ONLY reason we are able to "share the love" for GB with the i9000 users.

The fixes are still needing to be made in the mainline...meaning that the i9000 has the same problems. Once supercurio and codeworkx fix those issues on the i9000, you will see that they are "fixed" for our version.

DG is ONLY making the delivery system better and faster. Please don't pester DG with "hoping he'll fix the GPS" or "hoping he'll fix the camera"....because he's not working on it! If he is, then he's working with supercurio or codeworkx. All three of these folks are not shy to post where they are at on their twitter pages. I highly recommend watching their posts on twitter, which will keep people from asking for ETAs :).

Thanks DG for packaging this all up for the Captivate users who are not so ADB-inclined.

I'll echo DG when i say this is NOT a support thread. As a matter of fact, there is zero support for this build, because its not done yet!

You can't expect a home-builder to be answer questions about "is the house truly level", "is this a good neighborhood to build a home in" and then expect him to finish his work in a timely manner.

Just think. Every question you ask to devs, even if they don't answer, holds up progress for a few minutes. Keep that in mind when you ask a question. "Is it really that important? Did they mention that they KNOW this problem exists? Did they even ask me to report bugs to them?" If not. Then write it down on a notepad at your house...and wait until its built. If its fixed then AWESOME! :). If not, then bring it to their attention. Also..."built" = "Final"...not "BETA" or "ALPHA"...

K. I'm getting off the soapbox now. Just been watching this for FAR too long and i'm getting sick of this. I've been wanting to start dev'ing...and the lack of understanding of this community is what is keeping me from doing it.

EDIT: KingShady....I apologize in advance if this seems to point at you directly. This is not the case. You are just well-wishing :). Just laying this out to spear-head further questions to DG and other devs.

</soapbox>

Thanks,

-h8
[Captivate Android Development] MikeyMike01:
Bravo.
[Captivate Android Development] designgears:
Added CyanogenMod 7 Alpha 2, their system folder in my installer.

I think they added a wallpaper, launcher and boot animation... Everything else is the same.
[Captivate Android Development] leets4uc3:
couldnt get it to boot after an hours work :'(
[Captivate Android Development] donharden2002:
I've been running build 4 for about 5 hrs now with not many issues. I started by loading perception 9.5 and then gb over that. The only thing i really miss is my phone not going into landscape mode. Great job to all who have their hands in this. Forgot one other issue, YouTube not playing videos just sound.
[Captivate Android Development] cruiserbax:
This question is to other members who have used this zip method to install GB. I have flashed every build using this method but nothing happens it just boots into my normal ROM like it did nothing. It says complete install from SD Card and all and all my partitions are ext4 but just flashes zip then when rebooted it goes right into froyo without any changes? If someone knows what I did wrong and would like to help please PM me if you don't want this in this thread, then I will edit this out of my post.
[Captivate Android Development] KCutrer1:
At cruiserbax: you also need to flash the gingerbread reoriented kernel through either CWM or odin. Once you do it'll boot gingerbread. Then you can use odin to flash a froyo kernel and it'll boot froyo
[Captivate Android Development] cruiserbax:
Thanks, works as per OP now.
[Captivate Android Development] connexion2005:
+1 Never saw this in the main thread. I should have read the whole thing but ya know. Hopefully I can put together a jig and get her in dl mode.
[Captivate Android Development] used2hvatreo:
does the "pull battery, putt batt back in, hold both vol buttons and plug in usb" method not jump you back into dl mode?
[Captivate Android Development] MikeyMike01:
If it did before, it will after.
[Captivate Android Development] used2hvatreo:
Yeah thats what I figured, making the jig is good and all, but I just figured out I never needed one to begin with. trying to help people learn from my silly mistakes and save them some work.
[Captivate Android Development] g1ddy:
So with each subsequent version is it a kernel change or a /Data change?

i.e. do I always have to reflash/untar the Data partition or is it just the kernel that needs to be reflashed?
[Captivate Android Development] hypermann7:
So to install cm7 do you need the voodoo prerequisite like you do for just the gingerbread build?
[Captivate Android Development] KCutrer1:
Yes you do. Since CM7 is based on Gingerbread, it behaves in the same way.
[Captivate Android Development] donharden2002:
Well I have found that the beta version of swype works well with this build so far. I just signed up for the beta testing and have it going now for those that must have swype. If I run into any issues I'll make sure to post them.
[Captivate Android Development] ademejia:
does anybody have the 3 button combo working mine is not working with this gingerbread rom,when shoud i hold and release the button?
[Captivate Android Development] scrizz:
well mine works, but I have found the jig to be faster to use(especially if the phone is off.

;)

:D
[Captivate Android Development] used2hvatreo:
yeah i would have to agree with you on that one. i def traveled away from home and left my jig. I then immediately "bricked" the phone with no hardware jig in sight. but normally i just turn the phone off and plug that sucker in and flash back to stock that way.
[Captivate Android Development] RockRatt:
Mine has always worked for me (3button to recovery) until I have been using the Tech Demo rom. I used it for almost 2 days and like it but I go back to work the rest of the week and needed something a little more reliable for tbe week. So I tried and tried but could not get into recovery mode. I twice had to use odin1 click and start all over. I am back on Perc.9.5 and realized my 3 button recovery was still not working. I COULD HOLD DOWN THE TWO VOLUME BUTTOMS AND CONNECT TO USB AND ODIN NO PROBLEM. But recovery was a *****. I had to go to stock fj6, cog 2.3b ( only odin rom i had on my pc), then use rom manager to go to recovery mode and put cog 2.3b6 on, then it would allow me to put Perc.9.5 back on. Like I said today was a *****. So I just read about the 3button fix DG posted and applied it. Now my 3button recovery is working again. So give that a try. For now on I may use the ji6 odin from what I read when needing to go back to stock. Sounds like odin fj6 can wipe out your 3button even if it has always worked for you. Just hoping this helps others.

Sent from MY Perception 9.5 on XDA App
[Captivate Android Development] bames:
had same problem with v6 rom. had never had any problem getting into recovery or download mode prior to it.

I know your wanting to get to recovery but if all else fails and you just want to revert back and flash back to stock to have a working base again...i was finally able to get into DL mode after tinkering using the following variation.

1. Remove Battery from phone.

2. Plug phone into pc via USB (without battery inserted)

3. Hold vol + / - at same time

4. While continuing to hold vol. + / - insert battery

I normally used a 3-button or 2 button plus usb combo to enter DL mode but when they failed (including pulling and re-inserting battery, then holding vol +/-, and plugging in usb while doing so). i the above worked variation and it entered DL mode almost immediately upon the battery contact points hitting.
[Captivate Android Development] TheEscapist:
The one click can break your 3 button, cause it overwrites your sbl.bin. There is a one click with it fixed though.
[Captivate Android Development] silverslotcar:
this is true only for batch 1008s (but not every 1008 just quite a bit of them)

search "3 button fix" thread by DesignGears
[Captivate Android Development] keredini:
Strange, I'm running Docs ROM with ULF all EXT4 enabled. I rebooted into recovery, installed the Tech Demo Download Build-4 ZIP from OP, that installed fine. I rebooted, then got into download mode to flash the 2.3 kernel file 'nsonsgs.tar'. Once I flashed this, I got stuck in a boot loop where only the AT&T screen would show. I flashed a 2.2 kernel 'setiron_v1.4.3_1280.tar' and got back to my original setup as expected. I then realized I need a different 2.3 kernel, so I flashed 'I9020_reoriented_alpha_1223.tar' and got the same thing (boot loop on AT&T screen). Did I screw something up in the process of setting up 2.3, or is there a different 2.3 kernel i need to flash?
[Captivate Android Development] designgears:
Why did you flash another kernel over the kernel that got flashed with the zip?
[Captivate Android Development] xtremekilla09:
Friendly suggestion: Flash back to stock -> Master clear -> Flash Cognition -> Then Flash 2.3

very simple and it works.
[Captivate Android Development] keredini:
I didn't realize the kernel was in the ZIP, i thought the ZIP was just a friendly way of not having to utilize ADB for creating the new gingerbread directory and dumping everything in it. When I flashed the ZIP i booted straight back into 2.2, and I see from reading other posts that you can essentially run 2.2 and 2.3 side by side by just swapping out kernels, so i thought i needed to flash a 2.3 kernel.
[Captivate Android Development] biggem001:
hell when i flash it, the kernel doesn't even go in?? and thats installing the GB zip from latest perception build. then i install just kernel and i get the same as you. ATT logo flash, black, flash, black.
[Captivate Android Development] cruiserbax:
I also flashed the latest zip from here and just booted back into 2.2 then was told to flash the 2.3 reoriented kernel to boot 2.3 then flash back a 2.2 kernel to boot back to 2.2 I did this and it worked as described without any boot issues (2.3 bugs all as per OP)
[Captivate Android Development] vinny.1967:
hi guys, I noticed after install cm-7 alpha 2 there is no market app and no google acct sign in is that what it's suppose to be or i did something wrong???
[Captivate Android Development] ankitb4u:
All I had to do is configure APN.

Now WiFi shows error everytime I turn it on. weird. Quite Unsure I remember fixing it on nexus s
[Captivate Android Development] designgears:
there is sooo much that needs to be done with the rom, most anything you can report is probably in the list already. Any minor stuff is just not important right now.

Support is impossible, the rom reacts differently for everyone it seems.
[Captivate Android Development] cesierra:
This info is for the devs working on the Gingerbread port.

http://android.modaco.com/content/g...ingerbread-internet-calling-sip-without-wifi/
[Captivate Android Development] Captainkrtek:
Locking and Cleaning :cool:

EDIT: Done, please listen to OP and dont feel you have to post any time something pops into your head. XDA is about group development not "Hey this works great thx <3 bye" If you want to thank them use the thank you button. And as per OP's request do not ask for support here.

Reopened
[Captivate Android Development] urisma:
CyanogenMod doesn't come with the proprietary google apps as per licensing mumbo jumbo. IIRC (I'm not running 2.3 on my captivate, only have read about it) you can't access CWM from 2.3 to flash the gapps update.zip, and the apps can't be applied through the builtin apk installer inside android. I think the only thing to do is merge the cyanogenmod update.zip with the gapps update.zip and reconfigure the updater scripts for the resulting update.zip then sign it and flash it as your 2.3 ROM. The gapps updater-script looks really simple, so it shouldn't take more than a couple changes to the cyanogenmod updater-script (actually, it -might- be possible to just merge the system folder into the CM update.zip gingerbread/system folder. Don't quote me on that). Actually, I think that might work, as both do a simple overwrite of the /system partition, and have no conflicting files (which would make sense). The gapps has a update-binary file, which I have no idea what it does, but other than that it could work. I may look into it later.
[Captivate Android Development] CNKirby:
Just copy the apks from the /system/app folder in this zip into the /data/gingerbread/system/app folder of your phone using Root Explorer (or something similar) on your Froyo ROM. Then swap kernels to boot back into CM 7. I copied all of the apks over (you could pick and choose, ie. no setup). Had the Google setup pop up upon boot. I was already having network issues with this build though, so I didn't get to complete the setup. Just wanted to test this out.

Hope it helps someone.

GAPPS MEGAUPLOAD LINK: http://www.megaupload.com/?d=0P4YJSWW
[Captivate Android Development] leezrd:
flash player

i know this is stupid question but is this same adobe flash player from 2.2 just carried over. if new one can i back it up with titanium and then reinstall over froyo flash player (i know it is still 10.1 but mabey tweeked) if i flash back (cognition of course)
[Captivate Android Development] chrisharmful:
I actually had to download Flash, it wasn't included on the Nexus S.
[Captivate Android Development] geokhentix:
To anyone who is facing the reboot problem when the screen locks, it seems that downloading Superpower and letting it run at stock settings has prevented it from rebooting for about 5 hours for me somehow, plenty of manual locks and auto locks later, still kickin'.

I know this isn't a support thread, but it's a problem plaguing us all and it's a pretty easy fix, just thought I'd share it! ;)

EDIT: Killed both active and cached processes for Superpower, locked screen, died. Turned superpower back on, no longer rebooting once again.

EDIT 2: Upon further testing;

I'm pretty sure to say Superpower prevents the rebooting for me perfectly, if it does for others too, perhaps if we check out how Superpower handles things when the screen is locked, we can solve this mysterious rebooting problem, or at least get a little bit more information on it.
[Captivate Android Development] TheEscapist:
If this works for me, I will love you for ever. :p
[Captivate Android Development] ademejia:
is superpower a app?
[Captivate Android Development] Dlev7:
Superpower is an app in the app store which I have used and its extremely useful I am going to try the lock settings right now if they work as someone already said I will love you long time my friend.

But I have a question I am using this with Perception but I really want to move over to Darkys latest ROM but I just wanted to make sure that, Darkys' will still work with the gingerbread port?

Thanks
[Captivate Android Development] geokhentix:
Upon further inspection and testing, it's very picky, so i'll detail it a bit more.

Superpower will likely cause a soft crash while installing sidekick on first boot; ignore it.

After that, enable WiFi and set the Sleep Policy to Never (Menu > Settings > Wireless & Network > WiFi Settings > Menu / Advanced > WiFi Sleep Policy > Never), and make sure you aren't connected to any networks.

Open superpower, and click on Screen State. The only boxes i have checked are Auto Wi-Fi Disable, and Auto Bluetooth Disable.

For me, WiFi has to be on, and sleep policy has to be set to Never. If i turn WiFi off or change the sleep policy to anything else, it will crash.

Hope it works!
[Captivate Android Development] TheEscapist:
I'll try it, but I won't have a chance until Sunday.
[Captivate Android Development] r_3:
I do not have external sd card access with this. Am I missing something?
[Captivate Android Development] ademejia:
gingerbread or any aosp rom does not support external sd cards unless hacked, cyanogenmod nightly would be your best bet.
[Captivate Android Development] TheEscapist:
It's not supported. Possibly, you could pull a vold.fstab out of a working rom, but I don't know of that would work.
[Captivate Android Development] geokhentix:
Just an update on the Superpower thing. For over 24 hours now with Superpower enabled I did face one crash, but I figured it out and thought I'd post it just in case the superpower thing works for anyone else, seeing as how this ROM is temperamental.

When the battery crossed below Superpower's Low Battery Threshold (30%), phone crashed on first lock. If WiFi is entirely disabled, I will crash on screen lock / time out. When Superpower kicks into low battery mode, it kills wifi entirely, which will cause the rebooting.

Set Superuser's Low Battery Threshold to 0% to disable it and I've suffered 0 reboots yet again. It's stable enough to use as a daily driver, at least for me since I don't use the Camera or GPS on the Captivate much ever.
[Captivate Android Development] designgears:
Yes, you misses reading the OP and title... this is experimental, unstable, and no where near being ready for daily use.
[Captivate Android Development] zas0006:
Point me in the right direction if I am missing something but does kernel level access to the external sd card (from the op) mean that it is available for us users/testers or available for the rom makers (DG, etc) to try to make it available. By the way, I love that we are heading towards GB goodness one step at a time.