yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] GGXtreme:
Trying to compare ROM's within ROM threads is probably frowned upon around here. That said, Continuum seems closer to themed stock, with updates focused on stability and bug fixes. From there, you can theme it, swap out system apk's, etc. GR-12 has its own experience going, hand-picked by Mikey with GSII apps, no overscroll glow, etc. I'm not sure how it is on stability and the latest bugfixes (it seems to be stable enough for a lot of people to be using it), but if you like what Mikey has done with Gingerbread, flash his ROM, if not, flash Continuum. The only real way to determine if a ROM is good/better is to flash it.
[Captivate Android Development] tmng95014:
+1 10chars
[Captivate Android Development] topiratiko:
INCREDIBLY anxious for the update.
[Captivate Android Development] tmng95014:
Given time zone difference, may I suggest you go to bed and wake up finding an update :-)
[Captivate Android Development] topiratiko:
Lol ill be up fer a while watching dvr with the wifey u know ill be checkin in!
[Captivate Android Development] DON2003:
+1

been on the GR-10 (too buggy), GR-11 (most stock samsung widget doesn't work), GR-11 good and fixed some bugs,

tried Contimuum, stuck here as my daily driver as of now, IMHO the much stable ROM for Captivate at the moment,

I would like to have the MIUI lock-screen like the add-on pack for subpression, can we just flash the pack on top of continuum? or is there a way to make our lock-screen like MIUI?
[Captivate Android Development] tbong777:
U se this ROM to load GB and give it a go. You can always download other ROMS over it IF YOU DON'T ENABLE EXT4 which IMO it doesn;t need.

Dling GR12 now...

I liked beta3 of this ROM best. Today I had two battery pulls. Then the Voice Mail indicator would not go away and I don't even use ATT VM!! Reinstalled but more issues arose. I have never had success with Existz Kernals. Sucker Punch onward. I think it may be the Kernel.

Going to try GR12 and live with the battery charge issue. I will try this again sometime down the line. I like the features. But B3 version of this ROM was the best for me.
[Captivate Android Development] harpo1:
You keep posting you think it may be the kernel. Not once have you posted on his thread about it. He can't fix problems if he doesn't know about it.

Plus your on icezar1's thread so keep the conversation about continuum. If you want to talk about GRxx go to that thread.
[Captivate Android Development] tbong777:
I will speak as I please where I please....Thank You..We all speak of different ROMS in every ROM thread. I try them all and comment on them wherever and whenever. I have more than earned my right to do so. . If Icezar has an issue he will let me know....But thanks for the "advice". These ROMs are in early stages so people will bounce around and try different ROMs. Nothing bad about that as long as they donate to the Devs whose ROMS,Kernals and themes, they are using.

You want to be a moderator?.......ask first..
[Captivate Android Development] Wwebmonster:
No, 2.2.3 froyo
[Captivate Android Development] pizz0wn3d:
From ten pages back: by existz.

Herp derp Captivate XDA Premium.
[Captivate Android Development] cmfrtblynmb:
To be honest, these instructions were really terrible and confusing. I have rooted and installed many many roms before. But this time I have tried to do the stuff about bootloader, but the sad part is the instructions are not clear at all and there are tons of unnecessary stuff. To cut it short: I have bricked my phone now. I guess the problem is I have installed the bootloader cezar was talking about and at some point phone tried to boot before I could install the rom. Now all I have is stupid phone-pc connection photo with an exclamation point on it :(( I have tried to connect to pc in download mode with no chance

Do you think is there still hope? Do usb jigs create wonders?(I have ordered one). If not, what can I do? Does samsung repair it for some fee (my hopes are very low at this point, since samsung is horrible when it comes to these issues). Will I have to throw away my dear phone just like that? It has been only six months :((
[Captivate Android Development] alexige:
The directions are very easy to follow if you follow them to the letter. The USB jig should work from where your phone is stuck. Or you could go to the nearest att repair store and get it replaced. I was stuck at your point before after messing up the kernel install by not unchecking auto reboot used the jig got into download mode followed directions and all was well.
[Captivate Android Development] harpo1:
You're right I'm not a mod nor do I want to be. I also don't go around and promote other devs work on anothers thread. It's bad forum etiquette.
[Captivate Android Development] harpo1:
The instructions are well written and simple. Most people having problems using Cezars method either didn't read the directions or failed to follow them.
[Captivate Android Development] rons_sacramental:
Agreed.

I have been using icezars rom from first day and i.just blindly followed the instructions and never had any problems.

I been reading this thread from start and seen people complaining about bricked phones, blaiming the rom but i have not faced a single problem.

Folks should read it few times to understan before flashing it and ending with a bri ked phone or complaining about how confusing the instructions are.

Cezar Thanks for your time and hard work.
[Captivate Android Development] pizz0wn3d:
This. It clutters up the thread and important posts can get overlooked and buried. It's best to just keep to the topic of the thread.

Herp derp Captivate XDA Premium.
[Captivate Android Development] cmfrtblynmb:
I am not here to devalue the job cezar did. His continuum 4 was the best rom I have used and if I can de-brick my phone, I will continue using it. And If I get my phone working again, I can assure you I will contribute to him for his wonderful job

All I am saying, the part on bootloaders was hard to understand. I am sure it is clear on a lot of people's heads but there are other mortals here as well. One tiny confusion and the results are disastrous. What steps should I follow? In what order? So I went back to stock rom, but then what? I have tried to install bootloader, then the kernel given there. These instructions, especially part on bootloader could have been more dummy proof. For all the technical information given on importance of bootloaders, the instructions are like 5 lines. This is all I am saying. I am not devalueing his work, maybe I was a little bitter as someone who just bricked his phone and has 15 months on his contract. Sorry about misunderstanding, but the point I am making has some validity I belive
[Captivate Android Development] vietn95:
try pulling the battery out for 30secs then put it back in ... and hold volume down + power at the same time .. you should get back into download mode ...
[Captivate Android Development] viny2cool:
stop blaming dev for your bricked phone..it clearly says it can brick your phone...u shudnt have tried it if instructions were confusing to u...

...also if u r on phone-!-computer screen...U just soft bricked it...U can easily get it to working

15 months left on contract means u r still under warranty...call att and they replace it for u...
[Captivate Android Development] dc5ftw:
Were you even in download mod when you tried to flash the bootloader package and the kernel one? The instruction didn't say that so maybe you weren't in DL mode and that's why your phone got bricked?
[Captivate Android Development] GGXtreme:
***For those who were having issues with DIVX3***

Can you PM me a sample video? I'm trying to help narrow down this issue to ROM/kernel/other, because I've had various issues with certain video files.

I apologize for the OT post, just wanted to get the attention before the issue got buried.
[Captivate Android Development] gio22:
I've been in your position many, many times, not because I didn't follow directions, but turned out my USB cable was bad. Your phone isn't completely bricked if you can get something up on the screen and you can. You still have the ability to get to download mode.

With apologies to XDA as this is an external source, here is a link to a page I have found invaluable in situations like where you are. The link is: http://samsungcaptivate.wikia.com/wiki/Putting_the_Phone_into_Download_Mode. I have found that the best way to get to download mode is the last one in that list.

Make sure you put your phone in DL mode after you have Odin open. Anytime I put the phone in DL mode and then opened Odin, I ran into trouble. Use the Odin One-Click (NOT the one with the 3 button combo fix). Once you have the Froyo bootloaders reloaded, you can try again. You can also bypass this by loading GB bootloaders instead first, but I haven't attempted that yet. That is listed in the OP and more info can be found by searching.

Bottom line, whenever you are doing anything that messes with the bootloaders, there can be trouble. Make sure you read, read and read again before doing anything and if you are confused, don't attempt to do what you are reading. A recipe for disaster, to be sure. Do make sure your cable is ok and make sure you plug the USB cable directly into the computer (the back of the computer, not one of the USB ports in the front if you have a desktop). The front ones might not be giving the proper power the phone needs to communicate properly with your computer.

Good luck!!

EDIT: I believe your question really should be in the Q&A section, not Development. Your question really has nothing to do with the development of Continuum. Just to let you know for the future. Still, hope I was able to help in any way.
[Captivate Android Development] amwbt:
Anyone else having a problem with there music player force closing upon launch?
[Captivate Android Development] gio22:
I have, but a reboot fixed it. I also use Double Twist and had no issues with it.
[Captivate Android Development] richsale:
I use winamp and haven't had any problems
[Captivate Android Development] nyydynasty:
you dont have a bricked phone. I've had that screen many times and always recovered from it.

-unplug phone from pc

-remove battery

-plug phone back into pc

-hold volume down (not sure about this step because it depends on which bootloader you have)

-while holding volume down and usb plugged into pc, put battery back in.

it should boot right into DL mode. I've done it many times and it worked every time. If it doesnt work, then you may have to try holding both volume up and down simultaneously.
[Captivate Android Development] kant5t1km3:
if that doesnt work and u see that screen if boot up normally, i had the same problem

http://xdaforums.com/showpost.php?p=7292801&postcount=26

bookmark the page if u need it :p
[Captivate Android Development] stangri:
I'll join in -- booooo.

I've been running C5 since the first beta and always followed instructions and never had a brick (knock on wood). There's nothing unnecessary in the instructions -- it walks you thru all the terms/new stuff required to understand the actual installation steps. It is a bit more complicated than "any roms before", but it's like that with any gingerbread ROM which requires CWM3.
[Captivate Android Development] GGXtreme:
Eh...while I agree there isn't really a problem with icezar's instructions, I'm starting to think there should be a separate guide on flashing Gingerbread bootloaders. There seems to be some confusion with different guides across different ROM threads, and some things not working for some users. For example, the instructions in this thread did not work for me and several others because of our phones having messed up button combos, but the guide in the GR-12 thread did work. This isn't really a ROM-specific thing, it should be a general process for first-time Gingerbread flashers.
[Captivate Android Development] dalewest:
Cool idea... but the site hosting the actual builds is unreachable, for me at least.
[Captivate Android Development] GGXtreme:
It seems to be down right now. I've actually had success with one of the earlier hourlies (resolved lag and unresponsiveness issues I had with 0.1.5, and possibly DIVX3 playback although I haven't tested it in either build).
[Captivate Android Development] dalewest:
Would you mind posting that build?
[Captivate Android Development] neo_31591:
hey im really sorry if its been repeated already...but i just flashed from 2.2.1 to 2.3.3 by following the instructions and faced no problem....flashed to 5.2....

i keep getting the fc on the email app...i never use it.the first thing i got when i booted my cappy was the email app fc..i keep gettin it after some time....also theres a lil bit lag here an there...not soo much to bother me but then there is a little bit...

is it cause of a bad flash maybe? but i followed the exact steps and faced no probs whatsoever....

an hey theres this ext4 app in the app drawer...should i use it?

EDIT: The lag is now bothering me :eek:
[Captivate Android Development] topiratiko:
We are waiting on an update that should specifically take care of lag. Any word on it btw? Thought fer sure it would be up when i woke up lol
[Captivate Android Development] nyydynasty:
There is a "general thread" on GB bootloaders:

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

it has a complete package of everything you need and more.
[Captivate Android Development] DaUnderSheriff:
I've been running this for over a week, progressing from the RC build and I flashed 5.2 last night. I have also had the random FC and screen freeze issues with the Phone and horrendous lag, regardless of the settings (stagefright and so forth).

After flashing 5.2 last night, I noticed that nearly all of the lag went away and that the whole UI was much more responsive, less choppy and a lot faster in transitioning from app to app and screen to screen.

After a Titanium B/U of all apps, I did a factory reset and then flashed 5.2 from CWM.
[Captivate Android Development] maxpower1985:
Go into Application settings and delete data related to email apps.. that works for me
[Captivate Android Development] Jep56:
This had to be the EASIEST download I've ever done! I don't understand the problems!

I watched the video on Mobile Tech Videos first.

I backed up all with Tit BU

I put my phone to stock (Odin 1 click)

Used Odin 1.7 for the bootloaders. Only my phone did not bott into recovery, it booted all the wat up.

Turned off phone, used the 2 button method into recovery.

Flashed the kernel.

Flashed the ROM

Bodda-bing! I'm rollin'

Ran Tit BU and I've had no problems.

I un-install the email, I use Gmail and Enhanced Email only

I turn off message nitifications and use GoSMS Pro exclusively

I use Power Amp for music

Love the ROM, excellent work!
[Captivate Android Development] Jep56:
I did do the factory reset before 5.2, and ran "Missing APPS & data" for Tit BU, not system data
[Captivate Android Development] topiratiko:
Welcome jep56 ;) you will notice some ocassional lag but theres an update commin to address that.
[Captivate Android Development] papashex:
I see many problem reports, here's a success story for encouragement.

Everything works in my 5.2!

I just did alot of cleaning to get there. I have been checking out all the new GB roms, so I have functioning boot loaders. I started with a GR-12 base & talon 1.5.

From there I restarted in recovery.

In recovery I cleared dalvik cache and performed factory reset (in recovery), then flashed 5.1.

Restarted unit and allowed all media scanning to complete.

From there I restarted in recovery.

In recovery I cleared dalvik cache and performed factory reset (in recovery), then flashed 5.2.

Restarted unit and allowed all media scanning to complete.

Shutdown unit, then entered download mode.

Flashed Talon 1.5 via odin.

Restarted unit and allowed all media scanning to complete.

I have not encountered a single app FC or audio / video corruption / lag issue that I see reported here. It may seem excessive but it's like updating pc bios roms - always start and end with defaults for best results.

I even dropped in the sgsII camera app and it functions without issue. Take a few minutes up front to save hours down the road.

I'm on hardware 1006 FWIW.
[Captivate Android Development] mrhaley30705:
Could you post a download for the cam app? Might like to try that out.Thanks
[Captivate Android Development] Jep56:
Same here. I have found that allowing all media scanning to complete seems to save headaches. I have a 32gb external drive, that takes awhile to scan but once it's done, it's smooth sailing.

I also leave it our until everything is loaded, shut off, re-insert it, reboot, complete scanning, then run Tit BU, reboot again. Somewhat tedious, but seems to payoff in the end.

I have had little lag, and no other problems.
[Captivate Android Development] ScottyNuttz:
I hope THIS gets incorporated into this ROM :)
[Captivate Android Development] Jep56:
Thanks, I believe icezar1 is from the Czech republic (per MTV's) so I'm sure his schedule is a little different.
[Captivate Android Development] pinoymutt:
Hopefully Samsung addressed the driver issues causing that nasty little charging bug and can eventually be incorporated into Cezar's ROM. :D

It'll probably take at least a week for DEVs to get a hold of the latest code, dissect it and figure out what's usable.

(Plus, not sure if they would need the Source Code for driver issues like the charging bug, but Samsung has been pretty quick on releasing those lately)...

AND I have a feeling this thread is going to get a whole lot more interesting in the coming days!!! :)
[Captivate Android Development] MaxRabbit:
Awesome! 10char
[Captivate Android Development] dalewest:
+1

But hasn't this thread been interesting enough for you over the past few days? :p
[Captivate Android Development] topiratiko:
The lag between screens in comparison to my buddys vibrant makes me sad.
[Captivate Android Development] koreancanuck:
You can flash talon 0.1.4 which seems to remove a lot of the lag on 5.2 or flash another gb rom or froyo until icezar comes with the update :-) rc3 was pretty good too
[Captivate Android Development] tbong777:
Anyone have a "bug" where there are "problems loading widgets" after reboot?

Happens on all launchers.

Edit" Oops its worse than that.....all TiBu backed up reinstalled installed apps are gone after wiping battery and voltage stats and rebooting. THAT'S why widgets aren't loaded. The apps are gone.
[Captivate Android Development] loraque:
Do a factory reset from Recovery. This happened to me using Doc's beta kitchen.
[Captivate Android Development] topiratiko:
Ill fire up odin when i get home and flash Talon 1.4 i dont have to disable ext4 do I?
[Captivate Android Development] neo_31591:
i deleted the email app using tibu hopefully the next update fixes it....

Maybe the dev could incorporate the Call Recording feature aswell? keepin my fingers crossed...

love the ROM! Thanks to the dev!
[Captivate Android Development] topiratiko:
So if i flash the kernel now that i already have gb do i leave auto reboot checked or uncheck it? I would think its safe to autoreboot since gb is already on?!?
[Captivate Android Development] cnigro1279:
Personally I would uncheck reboot and reboot to recovery to do a Dalvik Cache clear first. Always a good idea after a Kernel flash.....

Reverting back to Talon 1.4 was a night and day difference on my phone, although it may be different with yours.
[Captivate Android Development] topiratiko:
Good idea thanx
[Captivate Android Development] rockosifraldi:
You do not have to disable Ext4... just wipe dalvik
[Captivate Android Development] Jep56:
New to GB roms, so if this is a stupid question, oh well.

I can flash back to Talon 1.4 w/o reflashing the ROM correct? Just like flashing over a Froyo kernel, but I'd be using Odin in lieu of CWM
[Captivate Android Development] hiepgia:
Great battery :D
[Captivate Android Development] rockosifraldi:
That is correct, how ever if you are already on Talon, there is CWM Manager already installed on your cappy and it has the option of Flashing Kernel...if you so desire
[Captivate Android Development] cnigro1279:
Yes

Fire up Odin and flash just the kernel .tar in pda slot. Uncheck reboot option. After flash is complete, reboot to recovery and wipe dalvik cache. Should be good to go. First boot may take awhile as Dalvik is rebuilt. Just like Froyo Kernel flash using Odin.. :)
[Captivate Android Development] Jep56:
Cool beans....thanks
[Captivate Android Development] Cezar`:
5.3 is up, sorry for delay

5/6/2011 - v5.3 - Download | Mirror md5: 1E05275EFF20371295612F9D80590ADA

*

non-wipe

release , however, emails and email account will be wiped *

* davik cache is wiped, initial boot will take a while *

* flash over v5.2. If you come from an earlier release, it is recommended that you perform a factory reset *

* no need to disable lagfix *

* preferably flash with power cable unplugged *

* if you're running a gingerbread ROM, you do not need to update bootloaders! (because you have them already...)*

* if you're caught in a boot loop, reboot in recovery and just install the rom again *

Replaced Email app with Email from Continuum4 (2.2.1)

Removed Email widget, SevenEngine (needed to run Email from SGS2) and Digital clock (cute but stupid)

-----------------these changes removed the lag, mainly removing SevenEngine.apk and Email.apk--------------------

Added FuguMod 0.2

Added Mod Version and Full kernel name and build date to Settings - About Phone

Added "link voice call volume with notification volume" option in Settings - Sounds - Volume
[Captivate Android Development] rockosifraldi:
Hurrray!! I am sure this fixes the lag... not that I can be of any help for Dev... what was the issue... we have been running crazy since yesterday to identify the issue..
[Captivate Android Development] MastaBetta:
There is no need to apologize. Take your time, you deserve it.
[Captivate Android Development] dallasweb:
Trying to flash Talon 1.4 kernal

Opened Odin(as administrator)

PDA point to 1.4

Connect cappy to usb in download mode

click start...now hung at zImage

Odin msg:

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> zImage

hung for awhile, with a pink/purple screen, what to do now!!!

TIA
[Captivate Android Development] markmunsch:
Downloading now, just opened xda app and saw title was updated :).
[Captivate Android Development] Vivified:
You changed Settings.apk so the themes need to be redone. Any framework changes as well, just want to double-check
[Captivate Android Development] XorZone:
Thank you!

Now it is time to go with JVH ;)
[Captivate Android Development] xpakage:
Full Wipe

I would like to do a full wipe since I am coming from another ROM. Since I have the GB bootloaders installed, can I add the kernel (Talon 1.5) with Odin (reboot and repartition unchecked), then use CWM3 and flash 5.3? Or do I need to install 5.1 and then install 5.3?

Thanks.
[Captivate Android Development] Cezar`:
Take out cable and battery, put battery back, boot in download with Power + Vol Down, flash kernel again.
[Captivate Android Development] topiratiko:
Had BIG TIME issues trying to use kernel flash embedded in cwm. Best to just run update now lol
[Captivate Android Development] Cezar`:
Install Talon, factory reset from recovery and then install the rom
[Captivate Android Development] Cezar`:
No framework changes
[Captivate Android Development] Vivified:
Thanks for the quick reply bud, I'll update the 2 I'm maintaining so far with the new System.apk.
[Captivate Android Development] mrhaley30705:
Existz just posted that Continuum user not use some of the latest hourly updates for Talon. Causing boot loops and not playing well. Check his thread for more info.
[Captivate Android Development] tbong777:
Dammm and here I was ready to go back to Froyo for awhile......OK lets give it a go...

Any idea when "call recording" might be implemented?
[Captivate Android Development] Storm T:
Thank You!!