yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] speed817:
I'm stuck at the boot screen after flashign 5.2. :( Getting into recovery mode after the flash says that the "/sdcard can't mount" or something like that. I'll have to fix when I get home from work this afternoon.
[Captivate Android Development] Cezar`:
Are you sure you're stuck? The installation deletes the dalvik cache so it takes some time to create that.
[Captivate Android Development] CRAZED SOB:
Phone went black after calling

I apologize ahead of time if this has already been addressed. I am having an issue and I couldn't find the fix anywhere.

I tried flashing over Continuum 5.1 last night, and when I did it everything went smooth. I flashed over the bootloaders, and the kernel as said.

Then after flashing Continuum 5.1 everything went great! I was putting all the stuff back on the phone.

Then I tried making a phone call. As soon as I hit call, the phone went black and was completely unresponsive for about 1 minute, then came back on. The phone call still went through though.

Where did I miss up? I really like this ROM and would love to actually use it. Any help is greatly appreciated.
[Captivate Android Development] speed817:
I'll let it boot up longer when i get home. And thanks for a great rom!
[Captivate Android Development] Drew489:
Same thing happens to me every time I try to convert to ext4. I've let it sit for over an hour...then I go back into recovery mode and it says it can't mount the sdcard.

I had 5 and then 5.1 running fine but until that though...I guess I'll just run it w/o lagfix.

Wiping and reinstalling now.
[Captivate Android Development] Srikar_NBK:
Couple of issues

I have a couple of issues with 5.1

1) Galaxy Tuner app doesn't work on this ROM. I'm not sure if this app works in Froyo only.

2) The ROM seems to drain battery pretty quick. Not sure what the issue could be. :confused:
[Captivate Android Development] tbong777:
Love the GB Roms but the nightly charge is aggravating to say the least......Wake up to 85%..or less if I sleep more than 6 hours.

Has there been a work around to this I missed?. My workaround has been to replace the battery every morning with the spare I charge in a Samsung charger or shut down the phone and finish charge,

Just started happening when I switched to GR and back.

Kernel must not be the issue as it happens on both kernels. This morning Otried something different. I shut the phone down and charged while off to 100% and booted. Showed the normal 99%....

I wonder if the 100% indicators being removed is causing the drain after 100% is reached?
[Captivate Android Development] bigbyte.me:
I also faced this problem, with Gr9,Gr10 and now with Continumm 5.1. But this happens only with the first call you make, after that all the calss go smoothly as they should be.

@Icezar1 , Mate you are perfectly correct when you say you don't want to be attacked. Suggestions are always welcome but not the rants and complaints.
[Captivate Android Development] Cezar`:
I know.. is a bummer.

The indicator removal is not the cause, I had it with stock odexed JVK. I will make a test though. I will try to run the stock JVB ODEXED with i9000 kernel (like it comes from Samsung)
[Captivate Android Development] neonlazer:
Excellent job ice! Got a question or two. I so not see the flipfonts you installed, also had another found the new email app to be amazingly slow compared to gmail?
[Captivate Android Development] Chargerdude70:
Gents, comming from Mosaic1 with Talon kernel + ext4....whats the best steps to take to get 5.2 on my phone?
[Captivate Android Development] grkmaster:
1) Not made for GB. I read the author of the app hasnt been around to update it

2) It must be something you restored, cause I dont really have any major battery drains
[Captivate Android Development] Cezar`:
Galaxy tuner is not made for gingerbread. If you flashed the rom yesterday, is hard to say if there is battery drain or not as the battery did not have time to calibrate itself.
[Captivate Android Development] nyydynasty:
since you have a GB rom on your phone, you already have the bootloaders. I think you have to disable ext4 first. then put 5.1 on your phone (which is the wipe version) and flash that. Afterwards, you can flash 5.2 since its a non-wipe version. Just save your apps and data before doing anything.
[Captivate Android Development] grkmaster:
I dont think you have to disable EXT4 since this rom was mentioned in the OP i think if on EXT4 we dont need to disable. So it should count the same from other EX4 roms.
[Captivate Android Development] stangri:
Cezar,

if you have a moment, please give us the CWM-flashable TW3. TW4 is pretty and all, but I reckon it's a bit of a fight to get it working properly.

Also, I've started having DHCP time-outs with 5.1 which I haven't had with beta 1 thru to 3. Sometimes it connects, most of the times it does -- dhcp times out. Same router, same location. Dunno what to think.

I'll try flashing 5.2 when my phone is charged to see if it helps any.
[Captivate Android Development] Cezar`:
Just put the rom on sdcard, perform a factory reset from recovery and flash
[Captivate Android Development] dallasweb:
Yup, mine did the same thing, blacked out screen on on the first call, then Continuum goodness after that. Strange behavior, maybe a good note for the OM
[Captivate Android Development] Cezar`:
I didnt make any change that would affect wifi except the kernel...

and ill make the twlauncher pack in a while
[Captivate Android Development] bkeaver:
i have copied continuum 5.2 zip file to my sd card 2 times and booted into recovery and I do not see the zip???? and yes I verified that is is there. I can see mikeymikes zips
[Captivate Android Development] parnz:
which mean mattedBlues RC2.0 for Continuum v5.1 still compatible with 5.2?

thank you.
[Captivate Android Development] Cezar`:
Yes 10 char
[Captivate Android Development] betadan:
I have searched the forums and maybe i am blind, but i see the theme chooser in the screenshots for this ROM. I however cannot seem to locate it on my phone
[Captivate Android Development] grkmaster:
thats He Launcher
[Captivate Android Development] rivtre:
Agreed,have been tested just now:p
[Captivate Android Development] sremick:
What are the steps to prevent the phone from ever even doing a first boot (after installing Continuum 5.1) in an overclocked state?

I understand, and wasn't trying to be unappreciative. :) Please don't misinterpret advice and suggestions for improvements to make the ROM better and safer as lack of appreciation. There does need to be a way for users to provide feedback, even critique, without it being taken personally. ;)

It's frustrating when others are like, "Well if you don't like OC, screw you and use some other ROM!" since I never post a request or question like this unless I've already narrowed things down to the ROM I'd like to use, best of breed amongst the others. I'm posting in this thread because Continuum is so good as to be the closest to what I want... going with another ROM right now would mean facing far more things than OC that are not to my liking.

I'm not saying doing away with OC... I'm suggesting that it not be OCed initially and leave the OCing to those who wish to enable it (since it's so easy to do) while having the initial state be 1GHz to ensure best support and piece of mind for all those who do not wish to OC. That is all. Seems to me everyone wins there, and Continuum becomes appealing to the OC and non-OC crowds alike. What's so bad about that? ;)

There have been posts in this thread and other threads of situations where it does indeed appear that some people cannot safely OC on their Captivate, even to 1.2GHz. It's not uncommon for even devs to respond to some issues with "hmm you might want to try dropping to 1GHz, perhaps your particular Captivate can't handle 1.2GHz".

Anyhow the other posts were escalating needlessly and far out-of-proportion to my tone so I'm not going to escalate things further by responding. Obviously there was a misunderstanding of tone and intent.

And now that am catching up on the posts I see that as of 5.2 it's not OC by default. Thanks! :) But we can't just install 5.2 unless we have 5.1 already, correct? And 5.1 is OCed... unless there's a full-wipe version of 5.2 I'm missing (or I'm confused... which is more-likely...). Although I can probably just wait until the next full-wipe version as I see there are a few more things in the "known issues" list I'll probably want to hold out for.

Cheers...
[Captivate Android Development] Srikar_NBK:
Just updated to 5.2. All seems to be going good. Will test more and report back any issues. Thanks for all the good work Cezar
[Captivate Android Development] Cezar`:
i .. dont know what to say :)
[Captivate Android Development] grkmaster:
5.2 is a full rom but non wipe. Doing a factory reset does the wipe instead.
[Captivate Android Development] Cezar`:
@sremick, it seems that trying to not OC by default affects the CPU states.. which means the CPU will not go lower than 600 - 800 MHz. This is just preliminary analysis, not sure if it behaves the same for everyone

I might need to release another update which will, again, OC by default, until existz finds another way to keep the CPU at 1GHz but keep al states enabled.

EDIT: well.. it seems that the script created by voltage control has all states set to disabled?? ill look into this now.

EDIT 2: No, the states are fine, the phone goes to deep sleep if it has nothing to do.
[Captivate Android Development] marcopolo1:
hey thanks, it really worked ..i ahad to clear cache and factory restore, update with tibu.. thanks again

the phone seams a little slow .. after installing continuum via odin , then flash Continuum 5.1 .. do file need to install other file?
[Captivate Android Development] Srikar_NBK:
Benchmarks on 5.2

Strange issue. 5.1 scored 16.5 on Linpack and 2350 on Quadrant. 5.2 manages 10.8 and 1150 only. :confused:
[Captivate Android Development] neubauej:
While other people seem to have a charge bug that drops down to the low 90's somwhere after unplugging, I seem to have the opposite problem... Mine constantly charges. I unplug, and its at 100%. Stays there too. Since Froyo ive been used to 98% off the charger.

It isnt warm, but if it truly is charging constant, it cant be good for the bat..

Suggestions?

Also, as stated above, TW4 looks awesome, and when it works is great. But it constantly freezes and fc's. Hopefully it will become stable at some point.

Edit; It seems to be much less stable on the charger. Removing the charger makes tw4 almost useable. Much fewer fc's. Odd.

Nice work btw!

Thanks!
[Captivate Android Development] jcr81:
It's no longer overclocked...
[Captivate Android Development] Cezar`:
That shows you how big of a sh** quadrant and linpack are :) Run Linpack again though, you should have up to 14. Quadrant scores were huge in 5.1 because it had stagefright enabled by default but that broke xvid and flac playback. If you want to enable it again go to Tweaks and tap on Stagefright. As well, go to Voltage Control and set CPU to 1.2 GHz and the results will be the same as 5.1.
[Captivate Android Development] nyydynasty:
this rom is fast and smooth as it sits now. thats all that matters - lol
[Captivate Android Development] Srikar_NBK:
Appreciate the clarification. Is Stagefright framework something that was put into GB? I never heard of it in any of the Froyo ROM discussions.
[Captivate Android Development] maerlim:
If we could get a version that doesn't default to the first screen as the home screen (or can be changed), that would be great. :)

By the way, the source for TWLauncherGTG was released in hopes that it can be ported to Gingerbread. :)
[Captivate Android Development] djencode:
If you can fix it, that would be even better. The new iteration of TW4 is quite nice looking, it's just too bad it's laggy.
[Captivate Android Development] Cezar`:
You have to have in mind that TW4 was build for a 1.2GHz Dual Core processor. Not sure how much we can squeeze from it.
[Captivate Android Development] Cezar`:
it does not default to 1st screen. Do you have Tw set as default home? or you're still having the selection option when you press home?
[Captivate Android Development] Cezar`:
It has been available since 2.2. Just that no one played with it.
[Captivate Android Development] stangri:
Uhm, I know it might sound silly, but maybe you didn't scroll down far enough? Also, you're talking about 'internal' sd-card, not external one, right?

Cezar -- wifi issue *might* be router-related, but I'm at my folks and only have their only router to try. If I'm connected to wifi and then reboot the phone, upon successful reboot dhcp times out (phone is unable to obtain the IP address). I have to switch it off for like 5 minutes and switch it on again to get an IP. It is possible that the router does not reply with the IP address to the client it thinks is still connected, but it's a Linksys router, if this one does it, probably many others will do too.

Also, am I the only one who gets "Welcome to Nexus S" e-mails from google upon every successful boot up? I no longer use the TW launcher, hopefully that'll fix all the spam.
[Captivate Android Development] antonyvijai:
+1 I see your point. I like Cezar's ROM and that is why I am here. I think your feedback is valid and it helps in refining the ROM and in turn make more people appreciate Cezar. Asking us to go some place else is ridiculous. I am using continuum version 4 ever since it was out. Waiting for C5 to address some of the small issues as I am in no hurry to transition from C4 to C5. You brought up good, constructive points to the table. I.did not view that as a bad tone but I did feel bad when people respond by asking us to go and find another ROM. That's so juvenile. In fact those people do more damage to Cezar than people who come up with constructive criticisms! IMHO...please don't bash me for saying this. LOL

from Continuum V4 on matted blue theme using XDA premium app
[Captivate Android Development] richsale:
5.2 has fixed the video playback. THANkS cezar
[Captivate Android Development] p1gnone:
Loaded Continuum 5.1 just fine, BUT lost ROOT and the small update file that I have used no longer works. Any ideas or newer update.zip?...

nevermind the 5.2 came out in record time. Surely it will resolve my problem..
[Captivate Android Development] typ44q:
my quadrant score went from 1600 on 5.1 to 784 on 5.2

It seems to be getting hung up on the I/O section, could there be something wrong with my install?
[Captivate Android Development] nyydynasty:
has anyone had a problem with swype keyboard not appearing running 5.2? the keyboard looks like it is trying to appear because the screen shrinks and a white box appears where the keyboard is usually but nothing happens. Happened yesterday while I was on 5.1 so the update didnt cause this.

To fix this, all i need to do is switch the keyboard from swype to something else and back again - then it works fine. It doesnt happen often so its not a big deal but I just wanted to report this in case it has happened to others as well.
[Captivate Android Development] yahooserious:
ICEZAR SAID this about the oc:

If you want to enable it again go to Tweaks and tap on Stagefright. As well, go to Voltage Control and set CPU to 1.2 GHz and the results will be the same as 5.1.
[Captivate Android Development] bkeaver:
yeah I dont either.. its not like I have no clue what I am doing.. kind of confused
[Captivate Android Development] yahooserious:
Installed 5.2 and immediately noticed the lags from 5.1 are gone.

Tweeked setting back to OC/UV with stagefright (for now..I do need .flac in the future tho so maybe I will switch on/off)

Boot time was very speedy again! woo ho!

Thanks for the up icezar!
[Captivate Android Development] rivtre:
As long as I can feel the smoothness I don't even care sores. Just like ice said it's ****

Sent from my GT-I9100
[Captivate Android Development] typ44q:
I understand that but I have a much lower score than other people and much lower than I can ever remember seeing on my phone even before I installed 5.1 with its tweaks, that is why I was wondering if something was wrong.

I guess I should phrase it like this, what should the quadrant score be when running stock 5.2 I am not concerned with the actual score but that it might be an indication that something went wrong with the install.
[Captivate Android Development] Vivified:
Were there any changes to the framework at all?
[Captivate Android Development] pakiman47:
status bar keeps force closing

i've read through the posts and followed the instructions exactly. did all the master clears, wipe data/ cache etc. everything else is working fine (although i'm getting some disappointing results on smartbench). anyone have any idea why the status bar keeps force closing?
[Captivate Android Development] alexige:
Just curious why the model # changed to I9100? Voodoo control plus doesn't recognize that model and also why not just use I897? i know its an easy build.prop fix but still im wondering why.
[Captivate Android Development] Vivified:
yeah I had to edit it myself with root explorer to get voodoo control plus to work.
[Captivate Android Development] foxnh41b:
Cezar? Can I update 5.2 from v5rc3?

Ths
[Captivate Android Development] dracuanh:
the dark dialer number is a veryyyy nice touch, Cezar :)
[Captivate Android Development] nyydynasty:
someone correct me if I'm wrong here but I believe you can.
[Captivate Android Development] doctahjeph:
Thanks Cezar!! 5.2 fixed all my lag issues. My ram is back down to the 190s instead of 290s, and even the SGSII Email app runs so smooth. I can't wait for 5.3 and beyond.
[Captivate Android Development] harpo1:
Yes. Make sure you wipe data/factory reset in recovery.
[Captivate Android Development] LNJ:
Are you still looking for a reason not to switch to GB?

Every post you make in this thread is somewhat a rant about how you are waiting for it to address your issues!

Good luck and keep waiting cause your issues are not really issues at all!

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] Cezar`:
Does swype still work? :)
[Captivate Android Development] Cezar`:
You can try without factory reset
[Captivate Android Development] Cezar`:
there are few bugs which will not be fixed too soon. I am sorry to say that but they are out of my power. battery charge bug seems to be somewhere in the framework, if not even in the kernel or , worse, in bootloader. really tricky one.
[Captivate Android Development] ebcrew:
if we already have the bootloaders for gingerbread can we just flash this in cwm?
[Captivate Android Development] scuba_d:
only if you have cwm3 as well as bootloaders
[Captivate Android Development] ebcrew:
yep thanks
[Captivate Android Development] antonyvijai:
Hey relax man! Don't boil your blood over it. The small issues are okay for you but it does not mean it should be that way for everyone else. I know TW 4 is kind of pain in the butt also many other posts here confirm that. Even Cezar himself said he may give the old one. Anyways not here to shout and ridicule others (like you are calling my posts as rants) . UNDERSTAND I AM A BIG FAN OF.CONTINUUM / CEZAR. Try to respect others's concerns and viewpoints. I am not going to say anything else from.now on. Please try to help ppl who post some problems. Thanks

from Continuum V4 on matted blue theme using XDA premium app
[Captivate Android Development] ebcrew:
one more question do i have to flash 5.1 before 5.2?
[Captivate Android Development] antonyvijai:
Cezar : I totally understand buddy. I am not trying to criticize like others are saying here. I will make the switch soon followed by my donation.

from Continuum V4 on matted blue theme using XDA premium app
[Captivate Android Development] reflex01:
Would you mind sharing how to do this with me? I would appreciate it!
[Captivate Android Development] rockosifraldi:
Cezar, any reason for no OC and no UV ....
[Captivate Android Development] Vivified:
Using root explorer browse and open system/build.prop using the selection "open in text editor". Now go in and change all of the i9100 to i9000, or even i897.
[Captivate Android Development] surfed.tk:
He means just not default, you can OC & UV with Voltage control app after install. Some folks reported issues with default OC.
[Captivate Android Development] grkmaster:
its stock 1.0ghz .. ppl mentioned/complained/ about not wanting 1.2 with default installation. still can oc by voltage control
[Captivate Android Development] Vivified:
Nope, good thing I don't use it :P
[Captivate Android Development] rockosifraldi:
Oh cool, on to download now....
[Captivate Android Development] Cezar`:
And why do you need Voodo control plus when you have the latest voodoo implemented in the kernel..? just curios...
[Captivate Android Development] alexige:
Is broken swype the only side-effect?
[Captivate Android Development] xiaoali:
5.2 seem to have fixed my Tw launcher woes. I really like this launcher and hope you keep it.
[Captivate Android Development] ebcrew:
Im a little confused.. do u have to flash 5.1 before 5.2?
[Captivate Android Development] Cezar`:
I think you should think twice before letting your fingers type what they just did.
[Captivate Android Development] cheetablaze:
Why are you dumping the uv and oc? I'm enjoying the hell out of it.
[Captivate Android Development] Cezar`:
Yes, anyhow, you have Voodoo 8 implemented already in the kernel, dont understand why you need Voodoo control app plus.
[Captivate Android Development] jdubdieslo:
On C5RC3.zip and tried to go to 5.1 or 5.2 with or with out wipe and the phone just bootloops. I can then go back and wipe and reflash C5RC3.zip and it will boot successful. I've tried multiple downloads of both versions. I've tried while on rfs and ext4. Any help would be appreciated.
[Captivate Android Development] Cezar`:
You can activate it in VoltageControl app
[Captivate Android Development] existz:
EDIT - The man himself beat me to it :P
[Captivate Android Development] pinoymutt:
Just curious, did you change to i897 or i9000? I did hear something about if you changed to i897 it would nuke Swype, but does changing to i9000 work for both Swype and Voodoo Control Plus?

If at all possible, I'd really like them both to work (since new updates to Voodoo sound can be implement faster without having to wait for a kernel update with Plus).
[Captivate Android Development] Cezar`:
Flash talon 0.1.5 with ODIN and then try installing RC2 AFTER performing a factory reset.
[Captivate Android Development] jdubdieslo:
Thanks.
[Captivate Android Development] Vivified:
I want to be able to use whatever kernel I want and retain my voodoo sound. I paid for the app, backed it up with TiBu, so I just reload it when I flash a ROM. I'd rather use my paid app than the free one. Since I don't use swype, editing the build.prop is fine for me.
[Captivate Android Development] Vivified:
I used i9000, swype is broken.
[Captivate Android Development] Vivified:
You are tool, that is all.
[Captivate Android Development] speed817:
stuck again

So I went all the way back to JF6 and proceeded through each iteration of this rom. Everything was fine until flashed 5.2. And once again, like this morning, I'm stuck at the i9000 boot screen. It has been going for 20 minutes now. Looks like I might be the only one going through this though. Any ideas?
[Captivate Android Development] know8677:
I love the ROM and have been using it since RC1.

I'm not sure what it is, but somewhere between RC3, 5.1 and 5.2 (as well as switching to ext4) it became a lot more difficult to connect the phone to the computer to transfer files.

If Debugging is on, I don't have the opportunity to see the phone's hard drive. If I turn it off, I can see it, but the computer calls it a camera and when I move a file to it, nothing happens. I can move files using Wifi explorer, but if anyone has any suggestions, I'd really appreciate it.
[Captivate Android Development] pakiman47:
anyone know what might be causing my status bar to keep force closing? i have done all the wipes, and even did a master clear. everything else works perfectly, just the status bar specifically. using tw4 on continuum 5.1.