yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] tngal22:
Thanks! I know it is sent over 3G but I was seeing if it would kick in with the wifi on...which it didn't. Nor did it send with the wifi off; it just sat there. Hubby has no issue with Cog5b2 but I am having issues with Cog5b3. Um.....

UPDATE: I doubled checked my apn setting and I had a mistake so I fixed it and I can now send and receive mms.
[Captivate Android Development] KayvinM:
I would try clearing the main cache and dalvik cache. If that doesn't help try flashing another modem. Also double check your APN settings like you mentioned to make sure it's all in order.
[Captivate Android Development] ivebeenbit:
I had this on another ROM...clear GPS data with sgs tools and it went away.
[Captivate Android Development] dirtyballoonot:
Weird...Going into LBSTestMode via SGS Tools is FC'ing. I'm experiencing no other issues with the ROM at all aside from the GPS staying on and now this.
[Captivate Android Development] CremeFraiche:
thats because 2.3.3 uses AngryGPS not LBSTestMode *#*#1472365#*#*

AngryGPS dialer code is *#*#3214789650#*#* make sure GPS is confirmed on before entering the code then u can delete GPS data from there
[Captivate Android Development] dirtyballoonot:
Thanks...I found an app "SGS Secret Codes" before I read this. Found the culprit. It's POF (A dating site app). Turned GPS off in the app, and exited the app and it was still on, so, deleted GPS and re-launched, seems to be fine. Guess it's just poor code that leaves GPS enabled even when you exit the application.
[Captivate Android Development] DerKoch:
Thanks for the input. I did a master clear, cleared the dalvic cache, swapped kb1 in for the kf1 modem and still no luck. Btw, this was a clean install of cog 5b3 on a brand new captivate I had replace my other cappy handset which was exhibiting the same problem. Just for shiggles and gits I restored back to stock and flashed 4.5.3 and lo and behold, I can receive all calls. Something must be screwy with the 2.3.3 leaked build.
[Captivate Android Development] Hlaford:
I've been having a reoccurring issue where during a phone call the other party will just stop being able to hear me. In order to go voice back I have to either mute then unmute or go into speaker. Any ideas? I'm on beta 3
[Captivate Android Development] Cease1:
I have found that this happens after I use my bluetooth headset... something about the way it tries to play the sound through the headset... then when I stop using the headset I get no notifications. Reboot does fix though. Not a big deal, Just a minor inconvenience. :)
[Captivate Android Development] Cease1:
Lame........

Keep in touch. Like you I am headed to the SGSII very soon after it launches. :)
[Captivate Android Development] dirtyballoonot:
Ditto AS SOON as it's released!
[Captivate Android Development] wgarrido:
Same, can't wait for SGSII.
[Captivate Android Development] Cdub5:
Anyone having an issue where you're using either the camera or video and you try to exit it and you can't? Only way out is to reboot. Doesn't happen every time but about 1 out of every 5 times or so using the camera.
[Captivate Android Development] nemesishaven:
Yep, I've had the same issue, on Beta 1 and Beta 3. The camera will keep 'working' but lock out all input. Tonight I was watching a movie in MoboPlayer & the touchscreen stopped responding--movie kept playing no problem.. Strangely, the capacitative buttons + hard buttons still worked, not that they were very helpful. I had to pull the battery.
[Captivate Android Development] Cdub5:
Guess it's just another bug. Figure that's what you get with a beta. Still love this rom.
[Captivate Android Development] lapiz1618:
When will include the voodoo in the rom? The performance is poor sometime, maybe with this increases the performance and make this rom more usable ..
[Captivate Android Development] NeonMonkey:
I don't know if this is a bug for everyone, but I can't get my phone to recognize when it is plugged into a computer, it just acts like it is in a wall charger.
[Captivate Android Development] Fortune090:
You wouldn't happen to be trying to press the power button to take a picture would you? With this camera, it locks the phone, or at least the one I have does. Really missing that feature, along with the phone.apk that has the call/message screen after you end a call...
[Captivate Android Development] coferjinelong:
I have to say this is the snappiest rom I have ever tried. Great work DG.

However one thing I found is that the GPS lock is not good. Anyone can solve the problem please let me know
[Captivate Android Development] coferjinelong:
just digged through previous replies, after wiping GPS data with AngryGPS ( type *#*#1472365#*#* in phone app to get in), i got a quick lock

thanks CremeFraiche
[Captivate Android Development] CremeFraiche:
hard to say. gotta wait till the kernel source is released before DG can work his mojo on it and implement voodoo fixes. i feel no lag on this even after days of no reboots. even if voodoo is implemented i think im going to stick on rfs

try reinstall drivers, different USB port or different cable. same happened to me when i reinstalled windows and even reinstalling drivers didnt help till i installed mini kies to get the captivate drivers thru that
[Captivate Android Development] Haloruler64:
I donno man, I get prominent lag. RFS slows down over time. Especially over a week. At first it's damn near flawless, but it dies on you.
[Captivate Android Development] Dave the Knave:
That's not just this rom. I've had it happen at least once on every rom I've ever used.

Sent from my Captivate
[Captivate Android Development] leezrd:
Has anyone figured out how to get netflix to work on this rom?

SIGNATURE : Life is like a box of captivates, you never know if your gps will work
[Captivate Android Development] BrokenLegGuy:
All I had to do was run the

apk that you can find in step 1 in the op and it installed correctly. There wasn't anything to figure out.
[Captivate Android Development] leezrd:
It won't play movies just loads and goes back to screen....i even tried changing build.prop

EDIT: I will flash 5.3 then try that from scratch and see how works

Edit 2: flashing cog5.3 worked !!!

SIGNATURE : Life is like a box of captivates, you never know if your gps will work
[Captivate Android Development] darcjrt:
No HSPA on this gb release?
[Captivate Android Development] DerKoch:
if/when the source for this kernel is released by att. could be a while.
[Captivate Android Development] Haloruler64:
AT&T ROMs will not have HSPA. It's a very unlikely event to get HSPA on an AT&T ROM. For now, no. Possible in some future update? Yes, but low chances.
[Captivate Android Development] BrokenLegGuy:
Cool, as long as it works.
[Captivate Android Development] leezrd:
There is an app called ext4 and it converts rfs into ext 4...will it work in cognition? I was wondering because no voodoo lag fix and isn't that what it is basically is an ext 4 conversion?
[Captivate Android Development] CremeFraiche:
the kernel doesnt support ext4 yet so no.....wish att/samsung had a lagfix so we could get the kernel source quicker........

i apologize for that joke......wa wa waaaaaaaaaaaaaaa
[Captivate Android Development] leezrd:
Lol lol ... well kind figured that but thought a shot in the dark...yah know
[Captivate Android Development] olson.lukas:
Great work, DG!

So I'm using Cog 5b3 and I'm signed into Google Talk. If other people have a video camera, then they have the green camcorder icon show up and I can initiate a video chat with them. However, I just have the green circle saying I'm online, not a camcorder icon; so others can't initiate a video chat with me. Anyone else experiencing this or know of a fix?
[Captivate Android Development] darcjrt:
Thx. Forgot this is an att ROM.
[Captivate Android Development] cappysw10:
How do you video chat without a ffc? :confused:
[Captivate Android Development] Fallon:
I've experienced a couple of lockups on B1 & now B2. Pull the phone out & it's a bit warm. Either the phone will already have the screen on, or I will turn it on, then it stops responding to input. Depending the GPS icon will be blinking or solid depending on where I am, but touch screen, capacitive buttons, nor the power button will work. I'd have assumed it was crashed, except for that GPS icon blinking.

This has happened maybe once or twice a week to me.

Popping out the battery will get it back to normal. Although one time it looked like it rebooted on bootup. ATT boot screen > Galaxy S screen > pause > brief black screen > ATT boot screen > Galaxy S > normal puzzle lock.
[Captivate Android Development] zippox180:
The camera file I believe is hacked in such a way that it pulls the rear camera up as a source had it working on cm 7 for a little bit

Edit: the gtalk app itself I believe is hacked
[Captivate Android Development] bman221:
No idea what went wrong, that netflix app attempts to start, but just gives me a blank screen and fc's. Running cog5.3 (for a few days without any other issues) & using the apk referenced in step 1... should I flash cog5.3 again? any other suggestions?
[Captivate Android Development] tsan81:
so...GPS again....

ok....I just got a reburb through a device center last week because my GPS was unusable...that was a 1010 model, which was already a replacement from a 1008 in December...

After flashing and running Beta2 for a couple of days....I could not get a lock at all...in places that I had no problem, which was nearly everywhere I usually am. Couldn't get a lock, and if I did, it'd be gone within seconds. Absolutely unusable. Did factory resets, restores, tried the Samsung GPS restore, tried deleting data through angryGPS...nothing...

So, before taking the phone the device center, I took it back to stock 2.1...I decided to use the GPS (google nav) on the way there....about 20 miles....the gps lock and tracking was about spot on....I was like....crap...oh well...

They exchange it no questions asked....I have a 1103 model now...came with 2.2 obviously. After seeing the GPS work great right before returning, I opted to not flash....just rooted, sideloaded...etc....on stock 2.2...dealt with the sluggishness....but....GPS was great....quick locks....great tracking....seriously...

I swapped the phone last Thursday...I just decided to flash again today...I obviously did beta3 now....usual process...simple...did a factory reset, cache wipes and all before getting it to my specs....tried the GPS through Google Nav....back to crap near unusable status...

Yes I know, its beta, and by no means am I talking smack at all...this is just simply an observation....anyone experience this? Only curious because I hear about people swapping for a newer model and GPS is better than the older ones....and are getting good use out of it even when flashing to this ROM. I'm going to assume that if I flash stock 2.1 my GPS will be good again, but I don't want to since it's a bit difficult getting it to stock 2.2 (which is why I left it at 2.1 when returning the phone). I know, why would I do that....just for GPS usability I guess. and I know the custom 2.2's I've used (plenty) had pretty good GPS usability, but I am enjoying these beta's right now, and holding off to go back to i9000 ones since they were good, but still a bit buggy for me. anyway...suggestions or similar experiences here? no need to remind me that GPS in general is a fail on our phones...
[Captivate Android Development] prbassplayer:
Have you tried changing the SUPL to supl.google.com and port 7276 on angry gps? Had a similar issue and Haloruler64 told me to do that fix and it helped alot.
[Captivate Android Development] tsan81:
I haven't done this yet on this ROM, but have plenty in the past. The only reason I'm not yet is trying to see where the issue is coming from, because on stock 2.2, with the default SUPL setting and port, it was working spot on. I know changing it will help when the GPS was crap to begin with, but these two times now GPS were good and I really don't want to use a fix (a close solution) for the older units that weren't working so well so this made it better than nothing...

I'll probably change it tomorrow, but still looking for anything else. Is it a ROM issue since it seems to be happening when this ROM is flashed? and again, I know this is leaked and a beta....I know its always been said as a bunk hardware issue, but seeing and experiencing the huge improvements if not fix in stock mode just makes me curious. I flash if necessary if my GPS requirements outweigh the fun and other benefits of this ROM, but I'm not there yet... :)
[Captivate Android Development] prbassplayer:
This is a stupid question but how do i know my build number? I know im probably using one of the older builds since i got my phone late oct early nov, still curious.
[Captivate Android Development] Haloruler64:
Under your battery :)

Definitely change your SUPL settings. Your GPS will not work without the change. Mine didn't, at ALL. Changed it, and works with 5m accuracy.
[Captivate Android Development] prbassplayer:
I thought model number was 10xx or 11xx? Mine says 0168 O_o

Edit: Never mind I'm an idiot. its the smaller font 4 digit I missed lol. Its 1008
[Captivate Android Development] alanr723:
made the supl google update to AngryGPS. best GPS of all dg ROMs thus far...

Is Fenny around? I read 177 pages of this thread looking for his email.apk for this version to no avail :)
[Captivate Android Development] designgears:
Gps has always been hit and miss... Has nothing to do with the rom.
[Captivate Android Development] chibixzero:
My GPS works great with any room idle why other phones don't. I have. A 1102 one tho I had a 1007 or something like that
[Captivate Android Development] Kenn Lynch:
Beta 4 and 5, when?

Betas 4 or 5, when?

Looks like beta 3 really didn't add or fix enough of the pending issues

to be worth the reinstalation issues.

Any word on 4 or 5?

Or is this all about waiting for the source code

(which seems not to be anywhere in sight)

DG its gotten pretty boring here (no offense guys <BG>)

Please hit us up with some more of your magic!!!

Help us.. DGwankanobi you are our only hope

KJL
[Captivate Android Development] BrokenLegGuy:
I think that most of us that enjoy the Cognition brand prefer a longer wait time in exchange for stability.

I don't care if Cog 5 b4 takes a month or more as long as I get the stability. Quality takes time.
[Captivate Android Development] fooldog01:
I know there is more than can be done but the real action doesn't start until the kernel source gets released. That's what I am waiting for.
[Captivate Android Development] tsan81:
Thanks guys for the input! Thanks DG. And please don't take anything as complaining. I absolutely love the ROM! I have had no issues on b5 yet! and the battery life is amazing!
[Captivate Android Development] johnhazelwood:
Is there any way to fix the app crashing launcher issue (memory issue) or does that require a kernal change?
[Captivate Android Development] tsan81:
am i blind!!! I can't find google talk? where can I get it from?
[Captivate Android Development] BrokenLegGuy:
Did you check the Cog App Installer?
[Captivate Android Development] leezrd:
I went to sleep with battery at 43% and woke up 10 hours later (i was really tired and long day) at 41%. 1% every 5 hours is excellent imo.
[Captivate Android Development] tsan81:
Yes....not there...

when I flashed b3, after the initial install....i let it boot, then i restarted into recovery and did a factory restore/wipe....and then booted and setup the phone afterwards....I know in some other ROM in the past this caused it to delete an app or two that were included amenities...

:confused::confused::confused:
[Captivate Android Development] Haloruler64:
Dont do a factory reset. Whatever that formats, the ROM auto formats by itself. So don't do that. Talk might be in /data.
[Captivate Android Development] tsan81:
Ok, I found Talk.apk in the system/apps folder still. What do I do from here?

Update: NM....fiddled with it in Root Explorer, rebooted, and its there! Thanks
[Captivate Android Development] Haloruler64:
Market Enabler I think.

...****, sorry!
[Captivate Android Development] TriC_101:
This Rom is Great!! Just wish I could get rid of that AT&T boot screen.
[Captivate Android Development] waghoba:
And boot sound as well, few pages back DG said he will take care of it in next release.
[Captivate Android Development] YoungBloodz:
Extremely sorry if this has been posted before, but how would I go about flashing this?

I haven't really been keeping up with the whole GB rom thing since it started because I kept hearing reports that there were always unstable parts of it. Cognition was always good to me so I stayed on Cog 4 until a GB rom from DG was released, which is now! so I can't wait to try it out.
[Captivate Android Development] shak0569:
Very smooth! My battery life is great. Netflix works now. Great sound quality, Fast lock GPS, I'm as happy as a little girl!
[Captivate Android Development] nelsonw:
Seems all are pretty happy! Thanks DG for your awsome work!! but i'll wait for the final one with CMW! Thanks again!
[Captivate Android Development] xpakage:
Please ask if you have any questions about what is below.

JF6 Odin One Click to stock, master clear, unplug USB from phone, enter download mode on the phone, start the Odin One Click from this thread, plug in USB cable to computer and phone, click start button in the Odin dialog box on your computer, wait for installation. Very easy...
[Captivate Android Development] waghoba:
just put your phone on download mode and flash using attached one click ODIN..straight forward! just for info- I was running CM7 and stock 2.1 boot loaders before flashing this.
[Captivate Android Development] boog:
Any chance for a heimdall version? I already tried seeing of I could possibly rip it out of the odin exe...no dice.

I can also verify that the stock kf1 will run with the i9000 gb bootloaders, might just stick with them for now, I like the key combos.
[Captivate Android Development] Smasher816:
Just saying... DG said that this 1click includes the bootloaders so it doesn't matter where you where comming from (i believe that is what he said, posibly minus cm7 though).

I have only 1 question.

Does tv out work? This is the only thing stopping my dad from flashing a newer rom.
[Captivate Android Development] Ostate24:
Get Rom so far.....very snappy and very easy to install!
[Captivate Android Development] TriC_101:
is there a way to fix the SMS timestamp with this rom?
[Captivate Android Development] AtariBorn:
Can someone try the Engadget widget? I'm not sure if its something I've done or maybe conflicting with the LG Optimus apps I've installed, but I can't get the widget to show up.

UPDATE: Figured it out. For some reason, the widget only shows up in the widget selection when I move the app to the phone. When its installed on the SD card, no go.
[Captivate Android Development] Beny The Kid:
Get "go SMS" or similar app that has the ability to offset the timestamp.......easiest way.....
[Captivate Android Development] Dlev7:
Fantastic work DG, second I saw official Captivate GB got released I anxiously waited for a DG Cog 2.3.3 Release.

Everything is great, and only can get better from here but my question has anyone gotten TW4 to work on here?

If so please tell how.

Thanks
[Captivate Android Development] hoopas:
Excellent package DG, looking foward to updates. Working great on my end. Thanks.
[Captivate Android Development] Cdub5:
How do you flash kf1 but keep I9000 boots, since this flashes both? I like the I9000 key combo as well.
[Captivate Android Development] boog:
I flashed the stock kf1 from heimdall in linux. Everything but the bootloaders.
[Captivate Android Development] TriC_101:
Cool thanks it work.. anyone eles having the SMS time stamp issue?
[Captivate Android Development] melvinaury:
Clear the Dalvik Cache, you can clear the dalvik cache from TIBU or in Recovery.
[Captivate Android Development] RockRatt:
DG GREAT WORK as always. I do have 1 request for maybe the next update to include a few different lockscreens. I KNOW you said when it is stable but as far as I can tell Cogb5 seems REALLY STABLE as I haven't had ANY issues at all and it seems like most if not all others it is working really stable. Not asking for any ETAs, just about the ONLY thing missing as far as a complete stock type Tom for our phones. GREAT JOB again.

Sent from My 2.3.3 or 2.3.4 Captivate Test Phone depending on what Gingergurl I am testing.
[Captivate Android Development] Dave the Knave:
DG is on vacation, so there will be no updates for awhile, and even when he gets back... There probably won't be very many worthwhile updates until we get the source code, **IF** it even drops.

I never really did an update to Beta3 when I was running Beta2. To get Talk (and the updated camera), I just took the .apk's from the Beta3 zip, pushed them via ADB console to /system/app on my phone, rebooted into recovery, cleared my Dalvik cache, and rebooted the phone and VOILA, Talk and the camera app were there and updated. You can also drop the .apk's into /system/app via your favorite file manager, like Root Explorer, etc...
[Captivate Android Development] Kenn Lynch:
24/7
[Captivate Android Development] br123:
Can someone confirm if Google Talk video chat works on this ROM? So far, I have had no success initiating or receiving video chats using the back facing camera on any other ROM.
[Captivate Android Development] ratatouille:
When I unlock the screen (I use launcher pro plus) I only see the clock (upper part) and the dock (bottom part), all the rest is black, until I press the menu/home button. Any idea why?
[Captivate Android Development] RDI:
He went to Las Vegas. So all of you XDA people who are there, keep your eyes and ears open, maybe you will meet him!

Sent from my Samsung Captivate running Cognition 5b3 and KB1 modem.
[Captivate Android Development] johnhazelwood:
Has anyone cwm back to Cog 4.x? Or do I need to Odin back to stock and then upgrade to cog 4.x? The memory issue on Cog 5.x is annoying me.
[Captivate Android Development] Fortune090:
Odin back to stock first.
[Captivate Android Development] wgarrido:
But won't you loose the GB Bootloaders if you do that? Wouldn't it be better to flash without Odin so you can keep the GB bootloaders and less change of bricking.
[Captivate Android Development] johnhazelwood:
It sounded like GB bootloaders would work with 2.2, but wasn't 100% sure. I thought Odin one click included the bootloaders..maybe not.
[Captivate Android Development] prbassplayer:
I believe Cog 4.x should work on GB bootloaders. You can Odin back to 2.1 with this and you will keep 2.3 bootloaders. Also its less of a risk as well. Hope it helps.
[Captivate Android Development] johnhazelwood:
Perfect, thanks!
[Captivate Android Development] Dave the Knave:
Cog4 does work with GB bootloaders. I'm running them.
[Captivate Android Development] prbassplayer:
Thanks I hadn't tested myself. But it seems like most roms work with GB bootloaders, except Mosiac and Cyanogen? could be wrong.
[Captivate Android Development] johnhazelwood:
Argh...Screen just turned solid green while running it.

I unplugged and now when I reboot it says firmware update failed..reboot in recovery (which isn't working) :(

Ok I'm jinxing it..but I am re-odining it after the failure and it looks to be working....premature phew!

Success! (yes that was a nervous play by play)
[Captivate Android Development] Fortune090:
Fairly random, but does anyone notice the status bar that shows when you load the Browser...? Lol
[Captivate Android Development] docflower:
So Ive been reading and cant find a solution...

I have updated from stock kf1 to 5b3 and I dont have any network indicator. Any suggestions?

Thanks.

Edit... I did not have an APN set up. Wierd. Google search will yield settings if anyone needs settings.
[Captivate Android Development] prbassplayer:
Gb bootloaders error screen = a sick scare download mode from samsung. Happend to me once xD.

Sent from SGH-I897 running Cognition 5 Beta 3
[Captivate Android Development] z28james:
Mosaic V worked well for me while on captivate gb bootloaders. I cant speak to older versions.