yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] rmntruexjr:
Just wanted to say that I have been running continuum4 and was very much in love with it so I started following this thread hoping for the orientation fix. Woke up this morning and saw it was fixed so I read over the op and flashed back to stock which made me lose 3 button combo. So, I read up and got adb loaded on the laptop and learned the commands. Got the phone into dl mode with adb and again followed the op to a T. By noon I was on this rom with the latest xcal kernel and haven't looked back. The only issues I've found are minor and have already been posted. I know, no horror story or obvious questions but I just wanted to reassure that if you follow the op and can use your search bar, you can confidently have a working Continuum5 rom.

Last thing, THANK YOU DEVS for all your great work. You make my andriod worth keeping and you keep my iphone friends jealous!!!
[Captivate Android Development] kamots:
For whatever reason, it would seem that non stock keyboards are the culprit. Switch back to the android keyboard and watch the magic lol the Eagle dude figured it out a few pages back:-)
[Captivate Android Development] Endoran:
What are the "visual bugs"? I'm on B2 still and don't seem to see any...just curious. Also, can anyone get hulu to work with the user agent set to desktop?
[Captivate Android Development] kamots:
Thank you for this reply . It helped alot
[Captivate Android Development] stangri:
Since the original link is already buried within this thread and the fact I was asked about it thru PMs I decided to post this friendly reminder. If you want to get native SIP working on Captivate, you'll need to enable it by placing an xml file from the archive attached to this message: http://xdaforums.com/showpost.php?p=12818807&postcount=2 into /system/etc/permissions/. Since every beta reflash kills the native SIP support, I copied the xml file to the internal SD card and copy it to /system/etc/permissions/ with the root explorer after each flash.

Cezar, would be great if you integrated this xml file in your future ROMs.
[Captivate Android Development] Velshtein:
Hmm. Seem to have run into a speedbump. I've got ODIN open and my phone in Download Mode (as per the usual), yet ODIN isn't giving me the go ahead. Only have the standard ID 0:[COM4] appearing. Can't actually reset the phone. Opinions?

EDIT: Reverted to an old version of ODIN for a clear. Seems to be working.
[Captivate Android Development] shoman94:
GB keybvoard and swiftkey keyboards I know for sure cause this. Not sure why and Cezar is digging into it.
[Captivate Android Development] shoman94:
I'm not sure I understand.... what step are you at.... going to stock 2.1 or are you past that and have ODIN ready to flash C5 with bootloader?
[Captivate Android Development] tbong777:
Anyone else have no speaker phone...? Speaker works, but not during calls..

EDIT Nevermind Beta 3 fixed
[Captivate Android Development] RichMD:
Do you have ADB installed? If you do "ADB devices", does it show the phone as connected? Have you already updated to Gingerbread? Did your rebooting your computer < had to ask... We all miss obvious things sometimes...
[Captivate Android Development] PhillyFlyer:
Hmmmm. I use smart keyboard pro most of the time. But I've mixed n matched and still a no go. Frustrated haha.
[Captivate Android Development] RockRatt:
[/QUOTE]

GB keybvoard and swiftkey keyboards I know for sure cause this. Not sure why and Cezar is digging into it.[/QUOTE]

I am guessing it is still rom related though. I have read and kept up with this post from the beginning and have seen all of the comments. But for me using the gingerbread keyboard and going to About phone works fine. I am not at this time on Continum though. I installed as per the original instructions, then applied a rom from the I9000 forum (Juew's) then flashed Excals original kernel and now the current cwm version and do not have any issues at all.

I am following this thread to watch the development of it and may switch to it soon. I just wanted to throw my info in here in case it helps figure out WHY the gingerbread keyboard has issues with this rom and not the one I'm on currently.

Sent from My Captivated JVB Gingerbread Toy
[Captivate Android Development] jcr81:
Regarding the about phone fc's it has to do with the settings.apk file. I flashed an i9000 theme with a new settings.apk and no more fc's.
[Captivate Android Development] KonaZXIII:
I made a short speaker phone call today. Sounded/worked great with the included JP9 modem.
[Captivate Android Development] shoman94:
FYI... I just finished porting PaulDiddy-Remix theme... waiting for permission to post it.
[Captivate Android Development] mrhaley30705:
»>>bump<<«
[Captivate Android Development] b3asty:
Just in case anyone was wondering, Superpower was utilizing a good 15% of my battery since moving to GB. I uninstalled Superpower and installed Green Power. Things seem to be much more stable now with regard to battery drain. I'll go back to Superpower when the dev updates it. Love that app...
[Captivate Android Development] Dani897:
well that would certainly make it safer. i believe it does but i dont know how to open up the .exe to see what it is flashing. i dont feelike flashing my phone right now to find out either.

but there are reports that it works fine.

the issue is that some 1007and 1008 phones would need to be flashed twice once to get both bootloaders and once to bet the scondary bootloader.

also some 1010 and 1011 phones fail with the one click version. as i understand it it is not a brick situation but needs to be flashed again with another version of odin. what i dont know is if the flash is complete, do these phones fail during the flash before the bootloaders are added or do they flash then not boot all the way?

also it may be posible that the i9000 boot.bin works fine with the captivate sbl.bin there is nothing saying it wont work, just experiene saying that it doesn't work with particular combinations like a mismatch between the i897 and i9010 is proven to brick the phone.

i would try it if i had a way to restore, ill wait till adam from the andromeda team finnishes his experiments on flashing bricked phones through the usb port, or i have a connector to solder to my board for a jtag restore.

for now the best advice is to deal with the i9000 splash screen and use the gingerbread bootloaders as long as you can. flash to stock with odin3 1.3 or 1.7 full and use either the jh2 leak or the jf6 that has no bootloaders

the gingerbread bootloaders are backwards compatible, you just get a funky button combo and i9000 splash screen
[Captivate Android Development] rmntruexjr:
Haven't seen this yet, sorry if I missed it.

I was using app2sd to move apps to the internal sd like normal only instead of "move to sd" I see "move to usb storage".

I tried to move it anyway and it said it couldn't and not enough memory.

So I looked in settings/sd card and phone storage, and it also calls my internal sd "usb storage"(still has the correct size).....don't tell me I messed something up after just posting how good I did following the op lol. ......also I can still navigate and view contents on the drive...basically I just cant move installed apps to it.
[Captivate Android Development] shoman94:
I have none... in fact its better than C4 IMO
[Captivate Android Development] shoman94:
I have the same thing going on.... I never use it so I didn't notice it. Not sure but I'll bring it to Cezar's attention next time I talk to him.

EDIT: Have you tried it during installation?
[Captivate Android Development] gocats7:
How is battery life with this ROM. Im on C4 right now and its great.
[Captivate Android Development] elfie:
Don't know if somebody replied already, but you need

framework-res.apk from \system\framework

And systemui.apk from \system\apk
[Captivate Android Development] Velshtein:
Successfully installed. Only issue I have is that I have no haptic feedback for my home button. Any way to change this? (the other standard ones seem to be fine)
[Captivate Android Development] shoman94:
There hasn't been a fix developed yet for it.
[Captivate Android Development] harpo1:
It's a known issue in the OP.
[Captivate Android Development] PuffinNugz:
does this have call recording?
[Captivate Android Development] rmntruexjr:
Thanks, and no I haven't as I don't think I get the option to do so.
[Captivate Android Development] majinzen:
Not through the dialer.
[Captivate Android Development] Velshtein:
Appreciated. Stupid of me not to look. Thanks.
[Captivate Android Development] grkmaster:
ooo! this i want!!
[Captivate Android Development] mrhaley30705:
Thanks. I'm hoping its just a battery that REALLY needs calibrated.
[Captivate Android Development] PuffinNugz:
Thanks.

Has anyone tried this (from i9000 board)?

[MOD] Phone.apk with automatic call recording (v0.3)

edit: nevermind. doesn't work with GB yet.
[Captivate Android Development] grkmaster:
IM at 69% battery with light usage after 10 hours 15 minutes..
[Captivate Android Development] PhillyFlyer:
I have given up on my About Phone section. I have no idea what else to do haha. I've tried all suggestions.
[Captivate Android Development] rrambert:
How do you go about inserting the file to get SIP on your phone?
[Captivate Android Development] jferg5:
I'm running b2 with the new kernel and I've had no problems. I have wiped all cache in between flashes
[Captivate Android Development] harpo1:
Are you using the samsung or swype keyboard? If not you need to use either one. Gingerbread and swiftkey cause fcing problem.
[Captivate Android Development] jjtitus098:
Root Explorer FCs on me. Tried re-installing and still does it. Not sure what to do.

Sent from my Captivate running Continuum 5.0.
[Captivate Android Development] harpo1:
Did you uninstall first then do a clean install?
[Captivate Android Development] Holmes108:
After one day of use, I get the feeling it's slightly better than I'm used to. It's certainly no worse. I've generally used stock and cognition
[Captivate Android Development] PhillyFlyer:
Wow..i was using Smart KB Pro - took your advice and my About Phone works. Thank youuu

Captivate / Continuum
[Captivate Android Development] harpo1:
It appears for most only the stock keyboards will work at the moment. I'm sure eventually it will get worked out where 3rd party keyboards will work.
[Captivate Android Development] yourname146:
Seriously, this ROM... The battery life... WOW! I'm on ~20 hours since unplugging, and just now at 40%. Fairly heavy use, due to messing around getting everything set up. Compared to most other ROM's I've been using lately, this is about double what my battery was lasting.
[Captivate Android Development] tbong777:
YES!!!!! LOVE that theme..been using it for months.....I actually borked my GB ROm trying to install it yesterday....HAd to go back and reflash C4 and c5.
[Captivate Android Development] tbong777:
Funny...I am not having any issues with FlexT9 or Smart Keyboard Pro...

Agreed on the Batterylife..nearly double what I was getting

EDIT: Yes if you switch to anything but stock "About Phone FCs..but I can look at that then swtich back to my Swype or FlexT9 and all is well..Only have to switch to see the phone stats.
[Captivate Android Development] jjtitus098:
Yep. Tried clean install. Still can't get it to work. Seems like the only app I have problem with.

Sent from my Captivate running Continuum 5.0.
[Captivate Android Development] shoman94:
It looks sweet... I'm on it right now just waiting for an answer from him. I PM'd him a while ago so we'll see.
[Captivate Android Development] surfed.tk:
There is a fix posted in the OP of the Kernel thread: http://xdaforums.com/showthread.php?t=1042543

but i have not tried it.
[Captivate Android Development] wilsongis:
I think that is the Home fix that is already baked in.
[Captivate Android Development] shoman94:
That is to make the home button work. Not haptic feedback.
[Captivate Android Development] majinzen:
That is the fix, already incorporated into the rom, to make the Home button work. There is no fix for Home haptic feedback yet.
[Captivate Android Development] surfed.tk:
my bad... :(
[Captivate Android Development] IDoMy0wnRacing:
Apps restored by TiBu are not in alphabetical order. Is there a way to correct this?
[Captivate Android Development] elfie:
They are essentially in the order they were installed, if you install anything from market, it will go at the end.

I have not seen a workaround, except you can go to list view and they will be alphabetical in that view.

Edit: you can go ahead and manually correct the order if it bothers you too much. Menu>Edit and then you'll be able to move the icons around.
[Captivate Android Development] shoman94:
You mean in the app drawer?
[Captivate Android Development] IDoMy0wnRacing:
Yes, in the app drawer.
[Captivate Android Development] shoman94:
Yea the regular launcher is in Alphabetical or and TW Launcher is only in List view your in grid view you can edit them to the order you want. I'm using the modded ARC launcher. Regina launcher is pretty nice as well.
[Captivate Android Development] yahooserious:
Thought I would report somewhat of an anomaly.. well it was for me as I hadn't used Rom Manager to Install ROM from recovery on 5.2.

1st i went to back up my 5.2 rom that I had FRESH installed all my programs and setting into pretty much all day long with no major errors. Thru Rom Manager I confirmed CWM Samsung I9000 then chose to back up ROM without erasing ect..

Immediately I896 flashes the screen followed by samsung below that Both in bold white letters.. Then I see a glimpse of teh android man with an arrow looking like he jumped out of a box..?? Then nice chrome terminator lettering 'android' shows on the screen for a few seconds.

Phone reboots... hmm no back up then?

Headed back to ROM manager and go for the Install ROM from SD card..

%$#&$! SAME words and animation and phone reboots. Everything the same as before. (by the way I had NEVER seen this animation before.. EVER)

I loaded and ran the GB bootloader version C5.0 this morning after following the OP 'structions to a 'T' and had zero problems. When I upgraded to C5.2 those were done by USB transfer the .zips to the internal card and manually booting into recovery.

I have always had the three button fix available on this phone so I think that it is in the original 3 button club.

** Light has shined upon me this very moment and I wonder if the reason I am being denied regular ROM manager features is possibly because I am in the 3 button club.. Would the fact that i am now using the GB bootloader and not the original bootloaders the reason CWM is not working anymore? is ROM manager not programed to deal with the new Bootloader?

Gosh I hope that this does not cause me any troubles!

I will report back after i manually boot into recovery for GB (press vol up and power) and attempt to flash C3.0

I cant thank everyone here that is helping out with this ROM.. What a Class act! Best to all of you for all you have given!

Y!S
[Captivate Android Development] elfie:
I am not exactly able to figure out what you want to do and why you need ROM Manager.

I have backed up this ROM couple of times from CWM recovery (use extended power menu or Vol up+power) and go to backup and restore. I have had zero problems while backups and restores

Edit: I see you want to go to C3.0 for some reason, you can flash the zip file from CWM recovery. I would recommend "wipe data" before flashing it.
[Captivate Android Development] shoman94:
wow...lol

No need for the buttons to get into CWM. load c5 beta3 on your sdcard then hold down the power button to get the extended power menu then choose recovery... it will reboot and go right into CWM.
[Captivate Android Development] yahooserious:
I was just pointing out that using the GUI in ROM Manager FAILED to back up the C2 ROM and it also failed to load the C3 rom using the GUI. I was successful in manualy making the backup and the Flash using the Two button method without any problems whatsoever.
[Captivate Android Development] waghoba:
I dont know why but I am not able to put any apk in /system/app/ folder by nay method, I tried root explorer , terminal emulator and adb shell bu no go...I was trying to put miui music player but it says system is read only,,...I even tried adb remount but same error!!! can anyone help me how to do this? and how to mount /system as r/w?

thanks!
[Captivate Android Development] alexige:
Is the usual option of mount as r/w not available at the top on root explorer. Ive been successful in mounting as r/w no problem. Probably just overlooked it.
[Captivate Android Development] Cezar`:
Done in b4
[Captivate Android Development] Langdang02:
Can't wait for b4 ^^
[Captivate Android Development] kamots:
Ok that makes sence. I have an old school 1006 batch phone, and have never had any problems flashing with Odin. My whole deal is not so much in a hurry to get off this rom. It seems pretty good so far. But I like knowing that I can Odin one click back to stock and flash something else without thinking twice about it. I got a download jig from mobiletech video the other day, i just tested it, and it gets me into download mode so i think I am good to go. Thank you for the info:)
[Captivate Android Development] stangri:
I copied the xml file to the internal SD card and copy it to /system/etc/permissions/ with the root explorer after each flash.

Or just wait for b4, yay! Thank you Cezar!
[Captivate Android Development] waghoba:
I am getting fc's after instilling root explorer since b1. What would be the reason?
[Captivate Android Development] mcord11758:
was an app issue, try uninstall reinstall. Read changelog on market for app
[Captivate Android Development] kamots:
Alright I odin'd ( its a verb LOL) the original package in op with the bootloaders. I then flashed b2 nowipe with cwm.confirming that I can just flash b3 with clockwork like b2? I'm confused because my phone force closed on the about phone settings, and it says to flash the no bootloader version first. Then b3. What!????? Am I reading it wrong? Why would I flash nobootloader when I already flashed bootloader and b2. Confused again:( do I just flash nowipe b3 or no bootloader then b3?
[Captivate Android Development] rons_sacramental:
First flash the one without booloaders in odin (wont wipe your data) and then from CWM flash non-wipe C5Beta3.
[Captivate Android Development] nikooe:
The FC on about phone is known issue. The problem is with the keyboard. Change th keyboard in your settings and it will be fine.
[Captivate Android Development] t0ucht0ne:
Well, Shoman is going to think I'm copying him (first Continuum 4, then his blue theme, then his modem - and now Continuum 5 Beta 3 - lol! Sorry man!) - and considering three weeks ago I posted for the first time on the continuum thread as a total noob flashing to this new beta rom was pretty scary - but I followed the instructions to a "T" and everyting is working great. I didn't even have a crash on the about phone since my deafult keyboard was set to Samsung.

So far, this is great! I can't even believe I'm using the brand new spanking version of Android... blows my pumpkin.

I did the full wipe, clear, wipe again dance just like the instructions on the first page said - no hiccups at all. THANKS SO MUCH CAEZAR!

Also, this is for Shoman:

I switched to TDVJP9 modem after I saw it in your signature, but I ended up doing what you suggested and INSTALLED ALL OF THEM - lol - and in the end it seemed that TDVJP9 auto selected the best for me - and just like you had mentioned to someone else - it would swap to 850 when my signal seemed low on 1900. What I've noticed so far with Continuum 5 is that this modem is now sticking with 850 a lot longer and more frequently than my old ROM... is this just my imagination you think or are you and others noticing this?

Even right now, I'm in the same location I was before I flashed to the new rom and with my old Cv4 install with the TDVJP9 modem I'd be locked at 1900 and wouldn't see 850 until I got in my car and moved far away from the current tower into the next cell - but now without going anywhere my phone is steady at auto with 850? What would cause that from the ROM end?
[Captivate Android Development] shoman94:
I just wanted to post that I only lost 3% battery in 6 hours with wifi enabled to never sleep, auto rotate on, push gmail on, twitter set to every 15 minutes. I'm loving it.
[Captivate Android Development] shoman94:
I'm glad everything is working out for you. Thanks for the kind words. Modem wise... I'm using the same modem from c4 to c5 and it is acting exactly the same so I'm thinking for you it is more likely just coincidence.

I would agree though that this modem does like 850 and I'm thinking it doesn't scan a often once locked on a signal.
[Captivate Android Development] shoman94:
Also...fyi. I just got permission to post the port of Paul Diddy- remix theme. I'll have it up shortly.
[Captivate Android Development] t0ucht0ne:
Shoman,

I was thinking that maybe when I was installing all those modems that I messed up on one of them and forgot to do the modem dance and now my TDVJP9 is working even better then it was when I forgot to "dance" - who knows - but right now I'm just glad to see all of this reading is paying off ;-)

And grats on the epic battery life! I'm anxious to see how mine does, too! Hopefully it'll be a win like I'm reading on this thread so far :-)
[Captivate Android Development] RichMD:
I haven't tried the JP9 modem yet. I am on JVK with 850 enabled and set back to auto. Is JP9 similar that I will have to go back to JK4, lock 850, JPD, and then JP9 and then back to auto? Can I go straight from JVK auto to JP9 or straight from JK4 "locked 850" to JP9?
[Captivate Android Development] harpo1:
You can go straight to JP9 it has 850 by default.
[Captivate Android Development] shoman94:
Well the modem dance is not required for this modem but if you did it anyways....have you rebooted since you installed it? I find that after the modem dance it will remain on 850 until a reboot then auto works as it should.
[Captivate Android Development] shoman94:
Just make sure you are using TDVJP9 since there are more than one.

No "modem dance" required
[Captivate Android Development] xpakage:
Shoman- how is TDVJP9 on battery? I have been using KC1 for a while and it seems to go very easy on the battery.
[Captivate Android Development] rmntruexjr:
I saw this too. Had about the same things on and lost only 3% in 6 hours.....:)
[Captivate Android Development] jpcdeux:
Amazing battery life for me! Full day of heavy use and was still at 44% when I plugged in. So roughly 10am to 1230am

Sent via my Continuum 5 Cappy.
[Captivate Android Development] t0ucht0ne:
Shoman,

Yes, rebooted - it's not stuck at 850 - I've been watching it - it has switched to 1900 but then a few minutes later it switched to 850 again and has stayed there. Looking forward to my commute to work (I drive 150 miles round trip - lol - fail!!!) on Monday to really see how this things syncs...

Everyone:

I need CIFS/SMB support - and with the old v4 ROM I just enabled the module via recovery console - but it appears that with this v5 rom I can't even modprobe/insmod the module from a rooted terminal. Do I need to compile the module myself on a Linux machine with android libraries and a special version of GCC (sounds painful) or is there an easier way?

EDIT: Yes, there is no cifs.ko module in /lib/modules - I assume that's why I can't mount my network SMB shares... Unless there is a compiled module I can download from somewhere else I guess I'd need to compile it myself...
[Captivate Android Development] shoman94:
Well in any case I'm getting the same performance out of this modem and XXJVK <-requires the modem dance.

But I've had luck going straight to it from TDVJP9.

I'm glad it's working well for you.

xpakage- battery life is awesome for me... even better than when I was on Continuum-v4 which was already good for me.

FYI... I posted the PaulDiddy-Remix theme here: http://xdaforums.com/showthread.php?t=1046952