yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] paracutin:
Would it be possible to get the charging issue fix sooner? I know, I should be more patient. Heck, I'll be the guinea pig for the fix. PM me if you are interested. Overnight charging is a big deal for me.

GREAT ROM!
[Captivate Android Development] Cezar`:
https://picasaweb.google.com/ionut.cezar/AndWalls#
[Captivate Android Development] -Perp-:
PMed

Works on i896.
[Captivate Android Development] djencode:
pm sent. i'm using i896 rogers captivate.
[Captivate Android Development] Cezar`:
well

it could be... im hoping is not one of those issues like wifi enabling on froyo...
[Captivate Android Development] Cezar`:
ok, anyone on armani and i9088?
[Captivate Android Development] pizz0wn3d:
Thanks :D

Herp derp Captivate XDA app.
[Captivate Android Development] RN_ReFlux:
Must say, as a convert from firefly/supernova/phoenix, you, icezar, are da man!

Sent from my super phone!
[Captivate Android Development] kaybest:
Thanks, Link please.
[Captivate Android Development] garringm:
I cannot confirm or deny this problem As I did not have this problem, I experienced one issue last night but I was still on b3, I momentarily opened maps up by mistake, and when checking my usage in about phone later that night maps was eating up my battery, it acted as though it was in continual use in the background, while looking in the stats for maps it was giving me a stay awake time of over 30 minutes and continually counting and wouldn't quit. I finally experienced my first charge issue when I woke up this morning but not real worried I am on RC2 with a full charge now will see how things run over the next day or so.

iCEZAR1 YOU ARE THE MAN (or robot)

one last thing I noticed in b3 that you had dropped in the build.prop the ril hacks for hsxpa and another one, I tried these on C4 and never really seen any benefit to it this is why I never mentioned before. I did try these for ****s and giggles on b3 but don't know that they really help out either I was just more or less playing around. There is another one I would like to figure out but it looks to be motorola specific it was a mod for the prox switch to take out some delay. but oh well no big deal. But I think I read don't quote me but those ril.hs*** settings were already at optimal in the carrier settings on the galaxy s phones. I was over on the inspire threads looking and they are actually benefiting from those changes to bring their network speeds up to par with the captivate on ATT network

These are copied form a post in the droid x threads thats why I don't think they worked but you never know until you try

To make the phone ring faster when dialing out, I changed

ro.telephony.call_ring.delay=3000

to

ro.telephony.call_ring.delay=1000

Now the phone rings pretty much instantly when dialing out.

To enable better scrolling speed through lists, I changed

windowsmgr.max_events_per_sec=55

to

windowsmgr.max_events_per_sec=60

Scrolling through the app drawer and contacts and any lists really is now smoother
[Captivate Android Development] dcarter:
Ok, three issue/questions most likely related to my own ineptitude:

1. Keep the lights on doesn't work for me since I installed the RC2- Do I need to clear something or reinstall the whole bugger fresh?

2. When installing the whole thing fresh, clearing everything possible-master,dalvac,stats, cache, etc...., is there a way to back-up and restore my current homescreen layout (icons, widgets,etc.)?

Thanks,

dcarter
[Captivate Android Development] elfie:
1. I am not too sure, but why put it in first place, a few lights go off, conserves the battery. Every drop counts ;)

2. In 2.2/2.2.1 SGS tools had that feature where you could back up your homescreen, I am not sure it works in 2.3.3

3. There was no third issue ;)
[Captivate Android Development] Holmes108:
Keep the Lights on is my absolute most missed app right now (in fact it's the only issue I have with the ROM right now). I HATE having the lights go off. I never noticed an increased drain in battery.

I cannot wait for the app to be usable again, and I'm sure it will eventually.
[Captivate Android Development] wilsongis:
Thanks. 850 is a hassle in my area
[Captivate Android Development] LNJ:
Wasn't that the first beta before xcal implemented recovery?

Sent from my GT-I9000
[Captivate Android Development] mrhaley30705:
Still there on beta2. But it added CWM. Be patient. Xcal has only been on this out dropped.
[Captivate Android Development] shoman94:
This is on beta2
[Captivate Android Development] shoman94:
Are you saying you don't want 850?

Because KC1 is also.
[Captivate Android Development] louvass:
Soft Brick

I also got locked without a 3 button recovery. Hold down volume and power get to downloading mode, bring up odin plug in USB and odin will see it and u can flash back to stock rom. Hope this helps
[Captivate Android Development] rsunny:
n00b question

Take that question back. A fellow xda-er helped out.
[Captivate Android Development] shaolin95:
Means you better know what you are doing before you brick your phone. ;)
[Captivate Android Development] elfie:
^ ^

LOL !!!
[Captivate Android Development] mrhaley30705:
I know. I'm running juwe 4.1(only temporary), I had to flash kernel with odin. I'm hoping xcal drops either b3, or rc1 soon. I'm really missing auto landscape.
[Captivate Android Development] mrhaley30705:
Agreed. All in favor?
[Captivate Android Development] wilsongis:
I need to have 850 enabled. I have used the instructions (yours, i believe) to enable on modems that naturally did not have it turned on by default. I was not sure if i needed extra steps
[Captivate Android Development] elfie:
Bootloaders are like BIOS for your PC, it loads first and then tells the PC what files to load.

GB ideally requires an updated bootloader, but flashing bootloaders is a little tricky and if something goes wrong you can permanently damage your phone. Chances of that happening is slim, but there is a possibility that it can happen and only samsung will be able to save you after that.

So there are 2 versions, one with bootloader and one without it. Generally the first flash of GB requires a bootloader update, and subsequent flashes don't. Some people don't flash the bootloaders at all, but then their recovery and initial graphics are screwed up.
[Captivate Android Development] elfie:
+1

Agreed, but thought the guy should atleast know.
[Captivate Android Development] rsunny:
Thanks mate.
[Captivate Android Development] elfie:
You are welcome. Just so that you know there is an easier way to say thanks on xda ;)
[Captivate Android Development] astrocrep:
Just wanted to say thanks... got it working... it's awesome!!
[Captivate Android Development] shoman94:
Alright cool.... yea it is mine...lol

Anyways... modem has been working great so I got problem recommending this in lieu of JVK since the flashing method to enable wouldn't be fun to do with ODIN and I have no idea if that method would even work with ODIN.

BTW... thanks for keeping SGSTools going!
[Captivate Android Development] elfie:
Has anybody tried SGStools on this ROM, I really like the 5 button launcher and wondering if it will work on GB ?
[Captivate Android Development] PeteSeiler2010:
Running nice and smooth, Thanks!
[Captivate Android Development] dcarter:
Oh yeah-the third was extra special:

3. Could the lights on issue be kernel related, and would I need to convert my file system back to RFS from EXT4 to try xcal's G.1.1?

Thanks again,

dcarter
[Captivate Android Development] djencode:
Lol, I haven't followed an operating system release this closely since Windows 7 ha!
[Captivate Android Development] Holmes108:
I've tried both, neither currently work with the lights.
[Captivate Android Development] longr6:
We are not worthy!
[Captivate Android Development] PuffinNugz:
Both kernels? My lights stay on using xcal's latest.
[Captivate Android Development] bluerap04:
How do you see which one you have
[Captivate Android Development] Holmes108:
Edit: You just blew my mind.... you're right. I just went back and it's fine. Not sure how I missed that. Too many flashing combinations this week.

Thanks!
[Captivate Android Development] brisknfade:
About the charging issue, im curious to know if people who are experiencing it are using to charge as well.

I've noticed that I get the charging issue on an ac wall charger and not a USB charger. Here's the thing though, while using sparepart's battery info the battery status says charging while the power plug status says unplugged. Hook it up to my USB power source and it instantly recognizes it as connected and charging by usb. In froyo it would correctly recognize that it's connected to the ac charger with no issue.

Perhaps when using an ac charger the phone just doesn't realize its plugged in yet still charges, so once it hits 100% it gets all screwy and doesn't really accept more charge or something.

Thought something was up when my time on battery in battery use menu was not resetting after coming off the charger.
[Captivate Android Development] jgaviota:
Thanks for the rom, we are all loving it, your work is amazing!

My only two complaints with JVB is the sudden stop when scrolling fast in the browser, it doesn't allow fast scrolling to the bottom of the page. Also, is there a way to change the id? I bought some gameloft games while on continuum4 and now they are not detected as legal copies :( And then companies complain about piracy...

So if anyone know how to fix these two things...

THANKS!
[Captivate Android Development] brandonb81:
Just flashed it RC5... Pretty pretty awesome so far. Excited about finally being able to use Gingerbread.

The samsung keyboard sucks though! Any confirmed way of getting the Gingerbread keyboard in here? Or any other decent replacement? Thanks

Edit: Because of the known issues list indicating GB keyboards wouldn't work, I was concerned about recovering the gingerbread keyboard with titanium, but I downloaded the APK here: http://xdaforums.com/showpost.php?p=9854871&postcount=1 and so far it seems to work as expected, so I'm not sure what that's all about.
[Captivate Android Development] Holmes108:
Embrace the Swype! I can never go back to a regular keyboard.
[Captivate Android Development] brandonb81:
Lol. Swype is fine. I like it enough, have used it extensively when I first got the phone but I just prefer the regular keyboard for some odd reason. Got it working anyway though, so go figure.
[Captivate Android Development] EnemyOfGlaDOS:
:eek:how'd you get ahold of RC5!!! ... jk:D

..sorry, i had to:p
[Captivate Android Development] Ptaaty:
Hopefully some people respond to help isolate the problem. My charger tricks the phone into thinking it is a normal USB connection, it shows up with the USB indicator in the notifications.

I have never had the charge issue people are experiencing (on B3 and RC2), and had only one "charge death" issue on another rom/kernel combo back on 2.2, while others had them all the time.

Something is likely different between a straight AC charging and "USB" charging where it fakes the connection (or is actually in a PC). That is a difference with my duet charger, it fakes the connection which is the only way to get a Zune 80GB to charge.
[Captivate Android Development] bluerap04:
I can confirm that the charger issue does indeed happen with my wall charger.
[Captivate Android Development] nakedninja42:
Great observation... only thing is, I had the charge issue with my dock, plugged into the wall and USB to computer. Last night I changed to perception II andthis morning was the first 100% charge I had since before b1 (ran stock JVB for a few days).

Edit: wonder if it has to do with talon and the USB dock support. For those who have the issue still, what kernel are you running?
[Captivate Android Development] sharksman:
^^^ THIS!

You simply don't need/want anything else once you get used to it.
[Captivate Android Development] xxsxx:
I have the charge issue on both the wall charger and my usb connection. No deal breaker, just got to watch for when I get close to 100% then unplug.

//edit: Have had the issue on both kernels.
[Captivate Android Development] brisknfade:
I was seeing the issue in all the xcaliburinhand kernal's as well as the talon kernels.

I just tried Perception as well as just stock JVB and they both failed to recognize they were connected to the wall charger while somehow still charging the battery. I'm not quite sure if that's the main culprit now though seeing as you say it still does acts up on USB power.
[Captivate Android Development] KonaZXIII:
(Sorry to quote myself, this thread moves pretty quick)

Any chance someone/anyone could confirm, or refute this if time permits? I don't mind being told I'm wrong, but if I'm even part right there's a possible temporary workaround in there for the charge issue.

Just throwing it out there and seeing what sticks.
[Captivate Android Development] garringm:
I have the charge problem on USB as well, I was going to post the exact same thing until I checked it this last time. On another hand I installed Crysis Sensation from i9000 with TW4 and the FC on about phone with other keyboards is fixed I don't know what changes to settings or framework-res that may be different from what icezar has done though so it may break something else that cezar fixed
[Captivate Android Development] nakedninja42:
I want to make sure I make it clear that in every case of plugging in the phone via USB (wall charger, computer, or dock) it did charge and tells me that I am charging, the problem I have is that when it tells me that I am charged 100%, unplug it and im at 82% or 92% or 96%, I plug back it and then it tells me I am at 100% so I unplugged and it lied. I powered off my phone when it hit zero once and let it charge (powered off) until it told me 100% and turned it on, it was at 92%.

This was on B1 - RC1
[Captivate Android Development] tmng95014:
+1 I am still on RC1 and not experiencing any issue.
[Captivate Android Development] tmng95014:
Thanks icezar! I am quite happy with RC1. Did not experienced any of the problem people have seen. I will continue on RC1 until you come out with the final version.
[Captivate Android Development] dallasweb:
Thanks for the spot on instructions. I made the jump from andromedia3 to Continuum5 RC2 this afternoon. So far running smooth as butter. GPS locked quickly and was geocaching 10 minutes after the flash....sweet

On the charger now to see if I have the same charging issues as stated earlier. But, I had similar problem on andromedia3, if I took it off the charger right when it displayed 'Charged'. the percentage would indicate something like ~92%, however if I left it on the charger for 30-60 minutes longer it would display 100%.

Thanks for the fine smell of freshly baked gingerbread!
[Captivate Android Development] killinjoke:
just got done flasing rc2. took longer than rc1, is that normal?
[Captivate Android Development] phlunkie:
Sorry for the possibly dumb question:

I want to verify that those with the 3 button issue should not do this? Or is it "safe" to odin one click back to stock, and then flash the 3 button update? Then run through the directions. (I did search, but maybe not with the correct terminology)
[Captivate Android Development] tmng95014:
I am on RC1 and never experiencing any charging problem. I left my phone on charge last night via wall charger. This morning it was 100%.

May I suggest the following procedure to reset the battery stats.

http://www.samsungcaptivateforum.co...g/?PHPSESSID=1a0e223675e649c8a7cf03118b6e2e3e

This worked for me when I was on Paragon ROM.

P.S. Wifi was on during this charging time.
[Captivate Android Development] mbc663:
Getting ready to make the jump, curious about the same thing
[Captivate Android Development] CremeFraiche:
it mentions in the OP that u can safely flash back to 2.1 with oneclick with bootloader and not one with 3 button fix then after that u can safely flash the 3buttonfix for it
[Captivate Android Development] nakedninja42:
The steps listed is essentially what I did. The weird part is when I charged to 100% while powered off, I deleted the battery stats before booting up into the ROM (I did it in CWM and not in root explorer) and when the phone finished booting, I was at 92%. That day I drained the battery to shut down and plugged in and turned on the phone while I slept. The next morning it was at 82%.

I just did my first drain cycle on perception II and charging now. When I woke up this morning and took it off the dock, it was the first time it was 100% since when I was on stock. I'll report back if it happened again when I take it off the dock later.
[Captivate Android Development] phlunkie:
I saw that in the "unsafe" part. Maybe a better question would be "has anyone here with the 3 button issue flashed over without issues?"
[Captivate Android Development] harpo1:
I did with no problem. Followed the directions in the OP and all went well.
[Captivate Android Development] LNJ:
Seems like it is a JVB ting in general and not just isolated to Continuum.

Cezar tested with just stock JVB and had the same issue.
[Captivate Android Development] mrhaley30705:
Its amazing what happens when we follow directions.
[Captivate Android Development] mrhaley30705:
Im running Juwe's at the moment, awaiting the resolve of the charging issue, and I haven't had any issue charging with it. I actually unplugged my phone this morning and it had 99%.
[Captivate Android Development] phlunkie:
@harpo1 - Thank you.
[Captivate Android Development] LNJ:
I've only had the issue the firt couple of times during Beta1 and not since.

So it is very random.
[Captivate Android Development] paracutin:
It is not a calibration issue. It appears that when the phone reaches 100% the charging stops but does not restart as the battery falls below 100%. I plugged my phone in last night at 67%. When I woke up six ours later the display said 100%. I unplugged it and it dropped to 57%. This tells me that after reaching 100% the phone basically acted as if it were unplugged for five hours or so.
[Captivate Android Development] keitht:
From 100 > 57% in 6 hours sounds like it was sucking the juice out instead of actually charging. But I had the same issue last night (first night on the new ROM).
[Captivate Android Development] gocats7:
Which version of Continuum are you using?
[Captivate Android Development] paracutin:
I agree. I am hoping it improves. I am used to 3% - 4% per hour. 7% + would make me look at going back to Froyo.
[Captivate Android Development] paracutin:
Started on B3. Flashed RC2 last night. Hoping the charging issue gets fixed ASAP and the battery consumption settles down.

I think Cesar said end of next week before we get the fix. I hope not.
[Captivate Android Development] gocats7:
I never had that type of battery drain on B3, today is my first time on RC2 so we will see. On B3, I could get 4hrs of screen time and about 15-30 min of calls before it died. It was as good or better than any battery life I ever had. Lucky of the draw I guess. Today, on RC2 1hr display, 48 min voice calls and Im at 52% so not quite as good today but...battery stats and such have to settle out.

Could someone post a CWM3 version of the original kernel in B3 just as a backup?
[Captivate Android Development] spencertp81:
My battery life has been decent so far, no noticeable difference between my 2.2.1 ROMS that I was running and Continuum V.5 RC2. I was on CM7 for a while and the battery life was atrocious.
[Captivate Android Development] paracutin:
I was considering going back to stock and starting over just to see if the charging issue would go away and battery life would be any better.

I have had crappy battery life with other ROMs but usually only if they had OC kernels (weather I over clocked or not).
[Captivate Android Development] tmng95014:
+1

My battery life is comparable to me previous ROM, Paragon, which I used for 2+ months). I was running for 2 days normal use before charging last night and this morning i was 100% charged. my Wifi was on during the charging. Don't know if this is a variable.

I am on RC1 updated from Paragon ROM.
[Captivate Android Development] mrhaley30705:
You can use SGS Kernel Flasher. it will flash zip and tar files.

I also started a thread about converting files to CWM 3.

http://xdaforums.com/showthread.php?t=1053523
[Captivate Android Development] antonyvijai:
In CM7 thread, the CM7 users say they get awesome battery life with the latest nightly build! Strange!

from Continuum V4 on Crysis using XDA premium app
[Captivate Android Development] grkmaster:
icezar, i saw you mentioned you made a few fixes today.. does that mean your releasing a update today? cause im going to flash RC2 since i stayed on b3 the past few days. Still debating to do it. The zip is on my phone waiting for me to flash lol
[Captivate Android Development] tbong777:
Still on B3....No issues with batterylife (actually better) and charging in the AM is 100%..

I think I will use B3 as my Daily Driver until things settle. Having no issues with it at all and I really like the PaulDiddy Remix theme.
[Captivate Android Development] spencertp81:
Huh, I haven't tried the newest nightly build yet, but I'm completely satisfied with Continuum V.5 right now, so I'll probably stay with this for a while. Also, does anyone know how I can get this donate button off of my profile? I accidentally put it there when I first opened my account and I'm not a dev, so I'd like to take it off.
[Captivate Android Development] Time_Zone:
I couldn't find a way to do it. Had to create a new profile.
[Captivate Android Development] OBatRFan:
Has anyone found a TW that has an alphabetical app drawer? That's my only complaint. I have it in my mind that GTG won't work. Is this correct?
[Captivate Android Development] mrcpu:
Preach it brotha! I'm having a great time with this rom, first time in 2 days Ii haven't had SD, BT works, call quality seems OK, everything is just humming along.

but Finding apps with the current method is a PITA.
[Captivate Android Development] tmng95014:
+1

I am on RC1. Went there from Paragon ROM. I have been very happy and do not plan to flash anything else for a while.
[Captivate Android Development] mbc663:
I just did this and my phone isnt turning on what so ever after flashing the 3 button fix in the odin post! help!!!!!
[Captivate Android Development] jgaviota:
What worked on my Galaxy Tab is to clear data for TW launcher, the app list is generated again in alphabetical order. I have not tested it on C5 couse here I use LP+

I now have 4 JVB pet peeves:

1) Browser lack of fast and long kinetic scrolling

2) No way to change Android id to make my legal games work

3) Lack of Wireless AP

4) Annoying jumps in brightness

Does anyone have fixes for these?

And THANKS again Cezar for your awesome work!
[Captivate Android Development] jgaviota:
what and from where did you flash? Did you FIRST do the Oneclick and THEN the 3 button fix? Where you trying to go back to 2.1?

if your phone is not giving any sign of turning on then most probably you have a brick.

I know couse I bricked mine a loooong time ago mixing bootloaders.

The only solution is taking it to a repair center :(

Edit: Read the first part of the OP in this thread for an explanation on bootloaders and the boot process

http://xdaforums.com/showthread.php?t=1049294
[Captivate Android Development] LNJ:
Are you referring to the Mobile AP?

If so it's there in tethering in Settings.

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] gocats7:
If for #3 your referring to wireless tethering Im using it right now on RC2. Otherwise all I can do is confirm #4.
[Captivate Android Development] skeepon:
when i try to install an app from the market website, my phone doesnt show up on the list of phones to install to. anyone else having this problem?
[Captivate Android Development] tietherope:
Mine shows as the I9000, just like the XDA app is showing it.
[Captivate Android Development] mrhaley30705:
Did you flash the regular, non 3 button fix version first?
[Captivate Android Development] sinichi21:
Happened to me once I just reflash stock 2.3 and from there change the android id then flash continum