yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] markmunsch:
I flashed talon this morning using the kernel flasher app, worked fine. If you've already got cwm3 you should be fine, if still on xcal's kernel you may need to clear dalvik cache after flashing it with sgs kernel flasher.
[Captivate Android Development] VanThePimpMan:
I did a search and didn't see it mentioned, but on all the versions so far (B1, B2, B3, RC2) the phone would reboot during the initial phone setup if I selected connect to wifi network.
[Captivate Android Development] Cezar`:
OP updated with second installation method.

Method number 2:

​

This is applicable only if you already installed a Gingerbread release and have updated boot loaders.

Put the latest release of Continuum on your sdcard.

Reboot in Download mode

Open ODIN and uncheck "Auto reboot"

Load this kernel in PDA section

Press Start

When the message "RESET" appear disconnect the USB cable and pull out the battery

Press Vol UP + Power (that will boot your phone in recovery)

Install Continuum from sdcard, reboot and you're done.
[Captivate Android Development] Cezar`:
Return to stock using JH6 package without bootloaders then follow installation method 2
[Captivate Android Development] IDoMy0wnRacing:
Shoman,

Is PaulDiddy RMX1.0 C5 RC2 in the works?
[Captivate Android Development] Vivified:
Perception doesn't have these issues. Furthermore Continuum didn't have these issues when I had flashed this theme without porting it onto Continuum's framework. It seems rather curious...
[Captivate Android Development] VanThePimpMan:
If I just continued without selecting connect wifi it would complete the phone setup fine, and then from there I could connect to wifi without a hitch. I just thought it would be something worth mentioning, thanks for the quick reply, and awesome rom!
[Captivate Android Development] keitht:
This is not working for me. I re-flashed the kernel using ODIN and placing the file in the PDA slot and still have the same issue with Bluetooth hung on turning on. Am I doing this right?
[Captivate Android Development] Cezar`:
Power off your device and turn it on again. Dont ask...
[Captivate Android Development] Cezar`:
The about phone issue is fixed!
[Captivate Android Development] Cezar`:
This is becoming irritating.. pull out the battery and put it back, power on the phone. will take this with existz, im sure there's something somewhere in the kernel. The new bootloaders are making my head explore. I never had so many issues before with any rom that I made :mad: :mad: :mad:
[Captivate Android Development] keitht:
Sorry to report it is still not working. I powered off completely and even removed the battery. Still hung on Bluetooth "turning on". Any other ideas?
[Captivate Android Development] Nickel Dime Bay:
Take a break cezar, you deserve it bro.
[Captivate Android Development] keitht:
I hear ya. Sorry for the trouble. Thank you for all the hard work.
[Captivate Android Development] EnemyOfGlaDOS:
Forgive me, but the updated OP says updates are in post 2 and can be flashed through CWM3 only.

OK.. if I follow installation instructions for the latest update it says flash from cwm only after you have the inital package with the bootloaders. Ok. Is your initial package not the right CWM?

Are you mentioning this for people not coming from a gingerbread rom? Or do we have to flash CWM3 before flashing RC2? ...just a tad confused:p
[Captivate Android Development] VanThePimpMan:
Your's doesn't want to play nice, I had the same issue after I flashed RC2. I just went back into recovery and re-flashed it immediately after I noticed Bluetooth wouldn't turn on. I didn't do anything special either...
[Captivate Android Development] LNJ:
Initial package is Odin. Then you should Odin the latest Talon kernel which will give you the new CWM upon which you can flash RC2 which is a CWM3 zip.

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] salazar44:
for those of you who are also having issues restoring TiBu backups, i think i found a solution. use the ext4 app, reboot, and rerun the batch restores. it worked for me perfectly. no hangups!
[Captivate Android Development] bri315317:
Wonderful rom! RC2 is very stable for me. I do have a question tho.

After updating to the ext4 filesystem, the textures in the 3d benchmark of Quadrant are missing. Can anyone else verify this? And please no flames over Quadrant, i do not use it for anything other than just to see changes made, not to compare roms. :)

Thxs in advance!
[Captivate Android Development] EnemyOfGlaDOS:
I'm sorry I meant the initial .tar file to get Continuum5. That's how I initially flashed C5. I followed those instructions. Then i updated to RC1.. Since then i have tried the perception beta..FTS- .. CM7 to get me through the day:p, and now i see RC2 is available, so I'm curious whats up. If i just install like the first time and instead of flashing the RC1 update, I can flash RC2 or do I need CWM3? I'm really not sure which one came with the initial ROM.:rolleyes:
[Captivate Android Development] keitht:
Thanks, unfortunately, that did not work either for me.
[Captivate Android Development] bluerap04:
Looked fine to me.
[Captivate Android Development] SweetwaterBurns:
I downloaded quadrant to check and didn't notice anything missing. I don't run it very often, though. Did you try reinstalling to see if something might have been corrupted during the conversion?
[Captivate Android Development] bluerap04:
Didn't RC1 use CWM 2.something? Can't quite remember, but I flashed straight from it to RC2, FWIW
[Captivate Android Development] EnemyOfGlaDOS:
I have no idea, that's why I was asking. If that is the case, then maybe I'm reading the instructions wrong in post 2 but is says: if you've already installed the bootloaders (which you would have if you flashed the .tar file that came with the bootloader package) then you can just flash in cwm. But in the updated OP it says flash updates ONLY from cwm3. Hence my confusion:rolleyes:
[Captivate Android Development] sinichi21:
hmmm anyone having issue in the internal memory card i cant seem to delete stuff it says the thing is deleted but after i close the root explorer and open it its still there except if i put the thing that i want to delete in a folder and delete the folder thats the only way it can be deleted for me

EDIT: got it fix by choosing samsung kies in the usb settings
[Captivate Android Development] keitht:
Good news.. I flashed the xcal kernel and BT works fine. I am about to re-flash Talon to see if it sticks

EDIT - Confirmed: Flashing to xcal kernel to setup BT then back to Talon works. Must be a problem with Talon kernel on initial setup.
[Captivate Android Development] surfed.tk:
Yes SGS Kernel Flasher works.
[Captivate Android Development] bri315317:
RC2 will install CWM 3x. The first time installing RC2, you would already be running CWM 2x.This is true unless you had already installed the latest Talon kernel with Odin.

After you install RC2, you will be running CWM3x...
[Captivate Android Development] bri315317:
Thanks, silly me i should had done that before posting.

So how long before we have a working GB keyboard, i sure do miss it!
[Captivate Android Development] tifxalex:
Any screens of this rom??

Thanks!
[Captivate Android Development] keitht:
Same here. Looks normal except for the amazing near 1800 score! lol
[Captivate Android Development] EnemyOfGlaDOS:
hmm.. ok, thanks. I guess I'm still a little confused why he put flash updates "ONLY" from cwm3, if infact you can flash the update from cwm2.x (if thats what the initial .tar file has).. but thanks for letting me know it worked:)
[Captivate Android Development] harpo1:
Did you click on the mount R/W button at the top right before deleting?
[Captivate Android Development] Vivified:
About phone just crashed after I installed a Blackout Gingerbread Kb and had it enabled. This is not the case on Perception atm.
[Captivate Android Development] Vivified:
Continuum port is up!
[Captivate Android Development] Nickel Dime Bay:
Nice! Downloading now
[Captivate Android Development] F1reEng1neRed:
Using this with the latest Talon kernel... converted to ext4... so far so good, but now under settings, get FCs all the time when I click on about phone. Anyone else had this?
[Captivate Android Development] bri315317:
Only when i set a non stock keyboard, for example the GB keyboard, set back to samsung and the FC stops.
[Captivate Android Development] sinichi21:
anyone experiencing lag on aDw launcher?
[Captivate Android Development] Nickel Dime Bay:
Hey if i ever wanted to flash a different theme (if one is ported for RC2) then would i have to use the revert and then flash? or can i just flash on top of you're theme?
[Captivate Android Development] F1reEng1neRed:
Thanks, I figured it had to be something to do with the keyboard since it started shortly after I switched to SwiftKey.
[Captivate Android Development] Geezer000:
I'm still getting the full charge drain on RC2.... Anyone else? Woke up to a fully charged 89% this morning.
[Captivate Android Development] Nickel Dime Bay:
I dont think theres a fix for that yet, some have said it only happens a couple times and then stops. Its happened to me once but luckily ive always been around the phone when it hits 100 so i take it off right away.
[Captivate Android Development] shoman94:
Yes I'll have that one up this evening. I could only handle 2 of them last night. Only got 3 hrs of sleep last night.
[Captivate Android Development] shoman94:
I'm glad you finally did what I mentioned. Glad its working for you now. Makes me wonder why existz's kernel is so small compared to xcal's.
[Captivate Android Development] timn2bama:
Can you do KP1 on cwm3!
[Captivate Android Development] paracutin:
Same here. I woke up to a fully charged 57%! 6 hours of not being used and down to 57%! That's 10.5% per hour. Unacceptable for me. I am used to 3% - 4% per hour consumption. I can work on that and love the ROM but the full charge shut off is a deal breaker.

Are you using the kernel that come with the ROM? I'm not. I flashed Xcal's kernel. My phone seems to like them the best with Froyo based ROMs.
[Captivate Android Development] mprinceiii:
just got everything set up with RC2, excited to see how it performs today. i've had nothing but wonderful response from this ROM, except for the About Phone issue that is apparently fixed :]
[Captivate Android Development] shoman94:
That only happens on the charger. If you take out off after it his 100% you get less than 1% if your only pushing gmail.
[Captivate Android Development] Nickel Dime Bay:
Its not fixed, just switch to samsung keyboard before going to about phone.
[Captivate Android Development] kant5t1km3:
do i flash RC2 then Talon or just RC2? thannks
[Captivate Android Development] nikooe:
I'm still on Beta3 and it's awesome on Battery, I hope you guys are getting the same.

after 1d 22h, I'm still at 40%, and I've used it moderately.

I hope nothing changes with RC2.

Thanks Cezar, as always a fantastic work.

(oops while I was typing this my phone rebooted itself, I guess that get's fixed in RC2, lol)
[Captivate Android Development] mcx6:
If you are on v5 of this rom already, the OP states:

Method number 2:

This is applicable only if you already installed a Gingerbread release and have updated boot loaders.

Put the latest release of Continuum on your sdcard.

Reboot in Download mode

Open ODIN and uncheck "Auto reboot"

Load this kernel in PDA section (Talon)

Press Start

When the message "RESET" appear disconnect the USB cable and pull out the battery

Press Vol UP + Power (that will boot your phone in recovery)

Install Continuum from sdcard, reboot and you're done.

I believe that this procedure is to get CWM 3 on your phone, so you can flash RC2.
[Captivate Android Development] paracutin:
Still something that needs looked at. Most folks probably put the phone on the charger and go to bed for a few hours. Stinks to wake up to a half charged phone after six hours.

Please don't take it personally. I think the ROM is great. But if this can't be fixed soon I will have to switch ROMs until it is.

My guess is it is something in the kernel causing it. Does it happen with both kernels (Talon and Xcal)?
[Captivate Android Development] garringm:
If your already running continuum b3 you should just be able to flash RC2 over top through existing cwm, thats what I did per another users suggestion and it went without a hitch. After I flashed RC2 I went into advanced and reboot recovery before doing a reboot system, I only did this to ensure everything had changed.
[Captivate Android Development] Holmes108:
I'm trying to flash the I9000 reorient kernel to fix bluetooth. When I pick the zip from CWM, I get the error:

"Amend scripting(update-script) is no longer supported........

etc

etc

Please switch to Edify scripting to create working update zip packages.

Installation aborted"

I installed this kernel in the same way in the previous beta with no issue (although it wasn't this orange CWM).... does anyone know what's going on? Thanks.
[Captivate Android Development] nyydynasty:
i got that same error but if you flash the TAR file via odin, it works just fine.
[Captivate Android Development] Holmes108:
I'll try that, thanks.

BTW, is there a particular reason to flash back to the Talon kernel? Is there something different between the two?

And if I do flash back, I noticed in one of Cezars post, he linked to the "TalonDEV-0.1.1-Debug.tar" and in another he linked to "TalonDEV-0.1.1.tar". Does anyone know if it matters which version?

Thanks again.
[Captivate Android Development] Ptaaty:
I flashed RC2 right from B3, using the 2xx cwm with no issue. The cwm flash puts the talon kernel in.
[Captivate Android Development] richsale:
I flashed from (C5b3 no problems) to (C5RC2 no problems) this ROM is AWESOME.

I say cezar for king of Romania.
[Captivate Android Development] Holmes108:
Not sure if this was directed towards me or not, but a lot of people are noticing that if you go into the bluetooth menu and enable it, it just gets stuck on "turning on...".

A fix is to flash to the other Kernel I was discussing, and then back to Talon. (Or possibly just reflashing Talon)... I just don't know what the difference is in the Kernels. I've read the threads, but don't know how any of it affects day to day operations.
[Captivate Android Development] nyydynasty:
i think the only difference is that logcat is enabled but if I'm wrong, please someone correct me.

I flashed back to talon only because there's got to be a reason for cezar to choose that as the default kernel...otherwise, no real reason.
[Captivate Android Development] IDoMy0wnRacing:
Hey thanks, get some rest... it's well deserved.
[Captivate Android Development] bluerap04:
Bluetooth turns on perfectly fine here.
[Captivate Android Development] EnemyOfGlaDOS:
Again this leads back to my question I had last night. Why does it say install updates ONLY from CWM3... but in post 2 it says if you have original bootloaders than just install from cwm. The original bootloader file someone mentioned had cwm2.x and not cwm3... so my question still could use some clarification. Sorry about repeating ..
[Captivate Android Development] Jirv311:
I thought it was just me. I woke up to a charged 85%. To get 100%, I turned off the phone and let it charge that way.
[Captivate Android Development] grkmaster:
android-files.com doesnt seem to be working

edit: working now
[Captivate Android Development] Ptaaty:
I wasn't really directing it, just confirming that you don't need CW3 to put RC2 on. Since I don't use bluetooth, I didn't notice the bug. Since you mentioned it, I just checked and indeed, bluetooth gets stuck turning on.
[Captivate Android Development] Ptaaty:
I don't and never have had the charge drain issue. However, I am using a different USB wall charger (duet dual charger) that is compatible with ipod and Zune. I'll see if I can find the stock one and see if that causes the issue.

I know the charger I am using behaves more like a PC USB port...most don't work with Zune or certain ipods.

Those with the issue, what are you using for the power source?
[Captivate Android Development] Chargerdude70:
warning or fyi

Went from b3 to RC2...did all the wipes and clears...everything went fine....did my normal TB restore stuff...then I went and did my Android ID restore...phone rebooted and went into a bootloop....anyone else have this issue?...any clues other than don't do Android ID restore...lol
[Captivate Android Development] kaybest:
@icezar1

Thank You, this method worked perfectly from v5 BETA3 to v5 RC2.

@shoman94

This theme (GingerFIRE-BlueED_RC1_C5B3), is working perfectly on v5 RC2
[Captivate Android Development] mrhaley30705:
RC2 has cwm 3.0.0.x recovery. Xcal's kernel doesn't support that. You can use SGS Kernel Flasher from the market.
[Captivate Android Development] jokes1:
Mine charges to 100 fine
[Captivate Android Development] markmunsch:
When using the new talon kernel, it converts to CWM3, which is not backwards compatible with CWM2.x. Therefore it seems Cezar just wanted to make sure the update worked for everyone by telling you to flash the talon kernel first and then flashing RC2 in CWM3. However, it appears fine to install from CWM2, as many have done so. But once you have CWM3 you can no longer flash old .zip files, they must be CWM3, or you must swap kernels to get CWM2.x back to flash them.

Hope that makes sense
[Captivate Android Development] EnemyOfGlaDOS:
Ok thanks. Yeah that makes sense. For people like me who like to be criticle and make sure everything is where it is supposed to be, maybe post 2 could use a little update as well. Someone else may sit here asking why the directions differ from one another. Thank you :)
[Captivate Android Development] harrynghiem:
@Icezar1 your rom is wonderful. I am using RC2 but it still exist one issue. If i use another keyboard that will be installed and i go to the about phone. It is FC. Contrary to using the keyboard of rom, it's ok.
[Captivate Android Development] EnemyOfGlaDOS:
Yeah this is a known issue. Gotta use stock Sammy keyboard or swype that comes with it. Will be fixed in RC3.
[Captivate Android Development] shoman94:
You need to flash gingerfireed_rc1_c5rc2
[Captivate Android Development] bluerap04:
I still have the charger drain issue as well with RC2
[Captivate Android Development] smithisize:
Boot loop on upgrade to RC2 from initial :/ and no combo works for DL mode, and recovery is no go.

Time to make a jig! Wooooo! :D
[Captivate Android Development] markmunsch:
Ok guys, is it me being a little critical or is it THAT important to check about phone??? I mean seriously, as much as we all flash it seems we all should know what ROM, kernel, and modem we're running. That's why I don't see this FC on about phone to be a problem at all.

The only problem I still have is the charging issue, which doesn't appear to be a kernel issue but a JVB/gingerbread issue because I've had it running both xcal's and existz kernel. Other than that this ROM is solid.
[Captivate Android Development] djencode:
This shaping up to be THE rom for the Captivate! Thanks a lot Cezar!

I have yet to see the charging issue with any version of this rom I've used yet! And i've installed basically every one since beta 1 :O
[Captivate Android Development] markmunsch:
So Volume Up + power button didn't work to kick you into Recovery. My guess is this is the kernel upgrade possibly causing an issue, I had an issue when I switched from xcal's kernel to talon, booted into recovery, cleared dalvik cache, rebooted system and the phone rebooted phone. You can maybe try that
[Captivate Android Development] Adam Raines:
I had to do that this morning as well. Other than that, it seems to last fine when I charge it to 100%.

Also, what the continuous counting on the exchange email been talked about yet? After I receive an email through exchange, the amount in Notifications keeps increasing.
[Captivate Android Development] EnemyOfGlaDOS:
Well while its not super important, but there is other information in about phone other than what kernel and ROM and modem you are using. I personally like to check my battery info from time to time. Knowing the issue I would only use whatever keyboard I had to but I can see it being frustrating for some users.
[Captivate Android Development] garringm:
You may be able to use adb even though its going through a boot loop, I've had to do this many times because of minor theming mistakes I have made,

adb reboot recovery command should work just fine to put you in recovery
[Captivate Android Development] KonaZXIII:
For the charge issue I think I may have found something that "seems" to work (for me, at least).

First off, I realize this could totally be a placebo, or something that's specific to me, or even just a silly coincidence, but it can't hurt anything (correct me if I'm wrong)-

Over the last few days I've done multiple flashes of the different versions of this ROM, including the main two kernels (and several modems) that we currently have available...this is what stops the charge issue from reappearing for me.

Charge battery to full with the phone on.

Let it sit for a few extra minutes after it reaches 100%- at least 10-15 mins.

While still plugged into the charger, (and at 100% full) reboot into recovery.

After

reaching recovery, unplug the charger.

Go to advanced and select Wipe Battery Stats.

Reboot phone, plug it back in and top off the final few percent.

Again, there may be unnecessary steps, or it could all be BS- I don't know- I just know that of the handful of times this problem has appeared on various flashes of C5, I noticed doing the above steps kept me from ever taking a phone off the charger and finding a less-than-full battery. (that's a long sentence lol)

Even overnight charging is not a problem for me.
[Captivate Android Development] shoman94:
Pull the battery and put it back in then good down vol-down and power.

If that doesn't work pull battery and put back in. start odin... The hold both vol buttons and plug in usb while holding them.
[Captivate Android Development] markmunsch:
I forget that that's in there, I always just set up a shortcut to the battery use on my homescreen so I can check it from there, much easier than going through settings/about phone, battery use :)
[Captivate Android Development] surfed.tk:
This has been reported 28 times so far. Could you all please read at least the last few pages before asking a question or reporting a bug?
[Captivate Android Development] Cezar`:
Ok guys, i hopefully fixed the charging issue. As well the bluetooth issue and the about phone force closing are fixed. Im close to a final release. I ported few more languages from JVK. Swype with spanish will be included and few more surprises. By the end of next week we will have a full themed Continuum 5 similar to v4.

So stick around, you wont regret it ;)
[Captivate Android Development] harrynghiem:
You can go to navigation: setting/application/battery use to see information about battery. It is better than about phone. You should try it
[Captivate Android Development] pizz0wn3d:
You spoil us cezar, you really do.

:D

Herp derp Captivate XDA app.
[Captivate Android Development] EnemyOfGlaDOS:
Good point! That's really all I go in there for.. that and just to make sure whatever flash I just did took. But great workaround! :)
[Captivate Android Development] Cezar`:
Can someone that installed this on i9088, i896 and i9010 (i think thats the code for armani...) PM me?

Basically i need confirmation that it worked.
[Captivate Android Development] markmunsch:
Man I seriously don't know when you sleep. I think you may be more addicted to this stuff than us sitting here refreshing every 5 minutes and flashing anything you upload :D. Thanks for all the hard work Cezar, it's coming along great.
[Captivate Android Development] paracutin:
Could still be a kernel issue. Isn't existz's kernel based on xcal's?
[Captivate Android Development] pizz0wn3d:
Hey cezar, can you post the wallpaper picture that comes with rc2? I flashed mattedblues and it's nowhere to be found now. :(

Herp derp Captivate XDA app.