yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] cnigro1279:
Youre not the only one. I had this problem as well until I read a post from earlier in this thread. Apparently Tiny restores some appear to the external sd card causing issues with ll and media scanning on reboots. Go into tibia and do a batch move from external sd to internal memory and that should fix your problem. Worked for me!! :-)

Sent from my couch on my phone.
[Captivate Android Development] cnigro1279:
^ meant to say tibu, not tibia or whatever stupid autocorrect thought I was saying!

Sent from my couch on my phone.
[Captivate Android Development] ctleng76:
I think what you and all the devs here are doing is allowing us to get more out of our phones than ever before. Don't let the complaints get to you. Also, please don't go out of your way to change features just because someone complains! Also accept donations as a way of saying thanks, not as a payment in return for adding features or fixing problems. Don't feel you need to pay close attention to a complaint from a donating user. If they expect something in return, then they are missing the point of donating.

Again, thanks for all you do!
[Captivate Android Development] andrewdroid:
I hope we can get pre-focusing back on the Camera Hack. Right now we can't pre-focus by holding the button. I've noticed this different behavior on all the GB roms I've tried though. It's important to be able to pre-focus when your doing photography (even with a phone!).

♫All Hail Cezar! Hail! Hail! ♫ =)
[Captivate Android Development] mrhaley30705:
You can still tap the screen, just like on stock camera.
[Captivate Android Development] andrewdroid:
Yeah but then what's the point of the hack if I'm tapping on the screen ya know? The other way gets you more stability.
[Captivate Android Development] shoman94:
But using the screen allows you to focus on exactly what you want.
[Captivate Android Development] andrewdroid:
But I still had both options with the old way, and it made it work closer to a regular camera which I liked.
[Captivate Android Development] pinoymutt:
You know I used to have this problem (even on Froyo ROMs) and then someone mentioned that if you look at the apps that are installed to your SD card (there are tons of apps on the market that make this easy) and move them all back to the phone, Launcherpro doesn't seem to lock up or crash on boot anymore (at least for me). I can't explain why it does this, but everytime I do this, it resolves the issue for me.

May want to give it a shot.

EDIT: seems like someone already replied with the same solution (guess I should read my threads from the most recent backwards :) )
[Captivate Android Development] Cezar`:
is iGo optimized for gingerbread?
[Captivate Android Development] Cezar`:
Camera pre focuses before taking the shot when you push the power button. No need to long push it. Ill look into disabling power button while camera is in use though
[Captivate Android Development] loraque:
That did the trick. Have I ever told you your're my hero? :)
[Captivate Android Development] cnigro1279:
Just paying it forward.... :-)

Glad it helped.

Sent from my couch on my phone.
[Captivate Android Development] marcopolo1:
i tried to flash the xcal kernel usin odin and it got stuked.. i almost bricked my phone, do you know witch kernel to use?
[Captivate Android Development] TheGrub:
Status

So after 2 days

Device: i896

Version 5.4.1 with Talon Kernel

LauncherPro

I get NO lag, phone is really stable, quick and smooth.

Only 2 problems i get is:

- Battery drain when plugged in and fully charged

- Device not showing up in the device list of market.android.com

Would like to know why for the Device not listed.

For the Rest, thanks a bunch to all that worked on this amazing ROM !
[Captivate Android Development] betadan:
Mine shows:

Samsung	GT-I9100	Rogers Wireless
[Captivate Android Development] Juan Bond:
The mine is a I897 and is working fine the only Only 2 problems i get is:

- Battery drain when plugged in and fully charged

- Device not showing up in the device list of market.android.com

Thanks

from my GT-I9100 using XDA Premium App
[Captivate Android Development] rivtre:
Has anybody considered making swap on cappy?

Sent from my GT-I9000
[Captivate Android Development] jlsesler:
Issue with 1000mhz setting

Reposting this here in case it has anything to do with the ROM (pretty sure it's kernel related).

There seems to be an issue with my speed at the 1000mhz setting. Look at the data below:

Linpack scores (each setting run 3 times with highest score recorded below):

1200mhz - 17.025

1000mhz - 11.525

800mhz - 11.66

400mhz - 5.97

Notice that the scores for 800 and 1000 are similar (yes, i made sure to "apply for now" when setting the speed each time). I get about a 14.5 score with Xcal's kernel (set to 1000mhz) on the same ROM. I am currently running Cont 5.4.1 (JVH) with 0.1.7 test 11 kernel, but I have seen the same results with earlier versions of the Talon kernel on JVB.

Is there something that I am missing that could be governing my cpu to the 800mhz level even though it is set at 1000mhz? Anyone else get the same results?
[Captivate Android Development] arffer:
Launcher Pro FCs

I covered this topic a day or so back, and I see that since you asked, a couple of others have posted to you my fix. But I thought it was worth it to repost the cause...

When LP starts up, it knows it has to put the icons of your apps on its various screens. But, some of your apps are on external SD, either the install from market put them there, or a TiBu restore put them there. And at the same time LP is trying to get the icons from the apps for its screens, your phone's media scanner has the external SD tied up in a scan. SO you get the FC on LP; you can either restart it or wait...

The fix is to get all your apps off of the external SD. TiBu, under its BATCH operations, has a nice tool to move all apps to internal memory. It scans every app, and skips the ones already on internal, and moves the rest.

Just remember, Market updates may move them back onto external SD, or later TiBu restores may put them back on external SD. TiBu, under preferences, has a feature to force all restores to internal memory, so that helps.
[Captivate Android Development] oscarivera17:
Sorry I dont really know, I am using an old version, so maybe that is the cause.

I am using V5.4.1, Talon 1.7 test 11, baseband version JVK, normal speed (1000), converted to ext4 and home launcher.

Every thing is smooth, no lags, bluetooth ok, gps lock fast.

Thank you for you effort in this rom.

Oscar
[Captivate Android Development] marcopolo1:
WiFi keeps turning on by itself

hey guys, definitely my WiFi keeps turning on by itself .. after turning it off, i kept watching my screen and i notice the wifi icon on the power widget turns on by itself ..

it happened many times . any ideas?
[Captivate Android Development] smackdownn:
my gps isnt working at all..i mean the main gps..and if i open gps test its force closing.can someone tell me a solution!
[Captivate Android Development] rfitts1:
is there a q&a thread for continuum? I've searched and I cant seem to find it but I have a few things i wanted to ask about flashing this over a 2.3.3 jvb.

the directions in the op seem pretty good but i'm always a little apprehensive.
[Captivate Android Development] rockosifraldi:
No Q&A thread I know off... you can ask ..what ever you need here..:)
[Captivate Android Development] greenleaf10:
I was wondering if anyone who has tried using Xcals kernel still see the battery drain when plugged in and fully charged. I have seen someone here reporting this issue is fixed in the latest Talon kernel 0.1.7 TEST 11. I am on that kernel and I still see battery drain when plugged in and fully charged. Was just wondering if people with Xcals kernel have a different experience.
[Captivate Android Development] climber1872000:
Have you installed any other navigation apps? Did you restore any data form previous ROMs or GB builds? Did you use TIBU to restore data? I would probably uncheck use wireless networks in location and security, delete GPS data, use SGS tools to make sure that you have the right geographical location (depending on the part of the world you are currently in) and uninstall and reinstall GPS test from the market. If this doesn't work I would probably perform a factory data reset form recovery. You could also try a different modem. I like KC1, it's what works best from me.
[Captivate Android Development] Juan Bond:
I tried the two lastes kernels Xcals and Talon and have the Battery drain when plugged in and fully charged
[Captivate Android Development] harpo1:
No one has fixed it yet. It's a random issue that doesn't happen all the time. I know some are looking into it but no one has come up with a fix for the captivate yet.
[Captivate Android Development] jjtitus098:
I never have the battery charging problem. I don't know what I've done. I used someones suggestion and turned auto rotate of and I never get it. But not sure if that is really what fixed it.

Sent from my Captivate running Continuum v5.4.1 and Talon kernel.
[Captivate Android Development] andrewdroid:
Thanks iCezar! Trust me, it makes shooting with the camera much better if you can do this. When I shoot normally with a regular camera, I pre-focus on my subject by holding the shutter button, and then I wait for the exact moment for my shot and release it. That's what makes it different than a simple one push.

Especially important for reducing shutter lag on a phone that's not a real camera. =)
[Captivate Android Development] rfitts1:
alright here it goes.

wanting to flash over from a 2.3.3 jvb rom. a little worried about the sentence in the op that says jvb kernels are not compatible with jvh.

So, the question is can i download continuum 5.4 (the wipe version) and get everything i need as far as a working kernel and modem included in that package?

when i reboot to recovery it says im using cwm 2.5
[Captivate Android Development] rockosifraldi:
If you are already on 2.3.3, just download 5.4.1 and you are good to go!!, you would have to flash Talon 1.7 Test 11, after you are done with 5.4.1 as I am not sure if the latest build of 5.4.1 contains test 11... or you could try xCal..your choice
[Captivate Android Development] climber1872000:
You need to flash the Talon test Kernel that is a few pages back. Flash via Odin then install 5.4 from Recovery.

Follow the directions below that Icezar1 posted in the OP.

"Flash this kernel (or any other kernel with CWM3) with ODIN in PDA section with Auto Reboot option unchecked

Pull out the battery and disconnect the cable after ODIN said "RESET"

Reboot in recovery using Volume UP + Power button

Install Continuum from sdcard."
[Captivate Android Development] rockosifraldi:
Just one more thing, if you plan to use xCal..remember to get JVH kernel from there.... :cool:
[Captivate Android Development] rfitts1:
Thanks to both of you above! Ill be flashing after work.
[Captivate Android Development] climber1872000:
Remember that you are on a JVB kernel and ROM now. It's important to follow the directions that I copied and posted from the OP.
[Captivate Android Development] TheGrub:
That's nice !

Why some have it listed and some don't ? Anyone knows ?
[Captivate Android Development] rfitts1:
i will be following them to a t. using odin 1.3 to flash the kernel posted a few pages ago then entering recovery to flash continuum. but do i use 5.4 or 5.4.1

is that the gist of it?
[Captivate Android Development] climber1872000:
Use 5.4 since it's a wipe then 5.4.1.
[Captivate Android Development] rockosifraldi:
Or you could just use 5.4.1 and do a factory reset..
[Captivate Android Development] rfitts1:
sounds great. I really appreciate it. I feel much more comfortable now.
[Captivate Android Development] tbong777:
Developers don't need defenders....this is not a contest where there are winners and losers. They do seek donations for their time and DESERVE them far more than pom poms. Many are in school and could use the bread. People who do not donate complain......and make requests. Certainly people who DO are entitled to the same. I see "donate to me" buttons on posters who offer nothing!! If people don;t complain or make requests Developers would never know what they can do better, At least PAY them for that aggravation.

I donate, without expectations, because of the time and effort spent. IF something doesn't work for me it may be ONLY me. I will mention it, you bet, If it works on another ROM I have no issue saying so on either ROM thread. Everyone has the "right" to complain, comment and back pat,.... some would call that "feedback" Claiming Talon does not work as well as Excal is not a bad thing. That is one voice. Not an Army. For a a lot of people happy with Excal that is a fact for them and vice versa. No need for defenders.

Without "complaints" I would not know which ROM is best suited for my use. If people are complaining about an Over-clocking ROMS I know it may not be for me. IF in the same sentence they name an ALTERNATIVE that is a GOOD thing, saved me some time and I thank them for that and try the alternative,

You seem the think there is some major "competition between developers. I don't see it and I would hope that is not true because then garbage will result as a product of some kind of race to be the number one Developer. I don't see that here. The complainers about those who critique are not the Developers as much as the users... I rarely read of a developer complaining about a poster making comments about another ROM in their thread.

I donate a minimum of $20 a pop, solely for their time. I have donated nearly $100 to DG since September when I used his ROMS exclusively on two phones and have not used a DG ROM on mine in ages. Money wasted? NO. I paid him for his TIME not his ROMS....... He just went in a different direction. I enjoyed his work as long as it worked for me.

I think you are confusing the fact that I support donating with "expectations of perfection" because I donate. That is simply not true. IF I use any ROM I donate to the Developer.. Period whether I end up hating it or liking it. I always donate for the TIME NOT THE ROM..... I have donated $50 to the site just for providing an environment for this. I am a huge advocate of donating to these guys for their time IF you use their work.

That does earn people the right to `comment whether negative or positive as well as keep the ROMS coming and offer alternatives to those who seek them.
[Captivate Android Development] rockosifraldi:
+1, I would have added more... but you guys have already written so much... hopefully people will read and understand..:D
[Captivate Android Development] tbong777:
I did not experience that issue with my first couple Continuum ROMs. When I tried GR it started. When I went back to Continuum it continued, Back to GR12 it stopped...back to Continuum its still good.

So I would say keep flashing different ROMS and and it will go away eventually. Did for me. Thats not saying my next flash of whatever ROM will bring it back. One thing I have found is these early GB ROMs are quirky. I left Continuum after a few incarnations because suddenly a simple reboot would wipe my apps!! Tired GR 9-12. That issue went way but I got the charging issue, Downloaded a Theme and wiped put the market so I tried Perception Beta 3, Maps was draining battery When that went wonky I came back here and so far so good. Charging is fine, Apps are sticking, Maps is not number one battery user, Rom is smooth enough without EXT4. I am not OC or UV, But things can go haywire on these ROMS is days,,,LOL

So I suggest you keep flashing ROMs and find the one that works best on your device. These are early beta ROMS not as "finsished" as Froyos. That took months though as will these.

Best advice I learned early is DO NOT "MARRY" A PARTICULAR DEVELOPER...But donate to those whose ROMS you do try and whose time you have benefited from...Try them all. And bounce around. Things change fast,
[Captivate Android Development] dallasweb:
I went from 5.3 to 5.4.1 (w/Factory Reset) with no issues, then flashed the Talon test 11 kernel. All is well.
[Captivate Android Development] MaxRabbit:
I've been following this thread loosely, but have seen enough to see a lot of people being attacked for reporting issues, even in a civil manner, that they have been having. I'm sad to see this and, hopefully, I can post my results in a welcoming environment.

Throughout all iterations I used the same apps and settings.

B3 was the best for me. I really didn't have any issues and it was blazing fast. My issues with lag began with 5.1 and lasted even until the latest 5.4.1, despite changing to ext4, OC'ing to 1.2 Ghz, etc. I removed the lagfix and voltage settings, and flashed xcaliburinhand's kernel. JVH build #13 - 14. Now my phone is quite speedy again.

I have no other issues besides immense lag with Talon. No disrespect to the hard working devs.
[Captivate Android Development] rockosifraldi:
DO NOT MARRY :D, just keep them as GF :)
[Captivate Android Development] Drew489:
+1, I don't get it. One can't even comment on a ROM anymore unless it's positive? LOL...that is odd.

So, new rules are no more comments on ROMs? Ok. Got it.
[Captivate Android Development] Jep56:
Whether a ROM is good or bad, no one has any reason to insult or diss on anyone. These people are spending their time and offering their findings/ creations on a free site. Be a little considerate, show some respect. How owuld it be if you all of a sudden had to go back to stock! Think about that nightmare.
[Captivate Android Development] flucks:
So I flashed this rom again this morning and listened to music on my drive to work. I take back everything I said. It is running flawlessly now. It must have been HeLauncher or something. I'm not sure what it was, but this rom is awesome now. Thank you!!!
[Captivate Android Development] ScottyNuttz:
You mean via BT Audio? I've noticed that this has stabilized as well. It no longer breaks up and pauses.
[Captivate Android Development] gocats7:
RC3 was great, I have read that over and over. I am on 5.4.1 and have not had near the lag that others mention. I would say mine is now basically the same as RC3 was for me. It kinda odd as you may think its apps as I have heard some mention and thats possible but if the same user has the same apps on RC3 and 5.4 and up then how can it be apps? Either way, I will say it seems variable as some its fast, some have lag and we are all running the same ROM and initially the same kernel. Im sticking with Talon as Im not having any issues plus it has the VPN support I need. Talon for me is doing great.
[Captivate Android Development] Pierce533:
I go away for a couple months and find a brand new Continuum and on 2.3.3 to boot! Man, I haven't flashed in so long! I hope I don't go premature when trying to flash this! :)
[Captivate Android Development] Time_Zone:
So as a recap for those with issues on 5.4.1:

1. For lag problems exizt suggests you should use the tweaks app to uncheck RAM: Min-free. apply changes and let it reboot.

2. If you have apps disappearing after reboot, you probably flashed using CW 2.5 instead of 3.0 in which case permissions are all messed up. Reflashing using cwm 3.0 generally fixes.

3. A quick factory reset and format of /system sometimes works wonders, you can do this from cwm. Then flash 5.4.1.

4. Sometimes going back to stock and moving back forward to 5.4.1 works. It is not clear why.

5. Try running with ALL tweaks off. I personally would try this before switching to xcaliburinhands kernel.

6. Try xcaliburinhands kernel. Some people say it flies.

7. rc3 was pretty good if you just want to wait out fixes. b3 is too for that matter. Just remember, once you are here you really can't help fix the current release if it does indeed have problems.
[Captivate Android Development] nyydynasty:
i had a little lag before but since switching to xcal's kernel, this rom is smooth as a baby's butt
[Captivate Android Development] jdv1:
This is my experience also.
[Captivate Android Development] VanThePimpMan:
I have been getting lag and messed around with tweaks apps, to no avail. I'm switching over to xcals kernel until Talon gets sorted out. I will miss my OC/UV settings for the time being.
[Captivate Android Development] shoman94:
Makes no sense to me. I have 0 lag
[Captivate Android Development] irishdude84:
Anyonne know if the wii remote works with this rom? Thanks in advance and good work!
[Captivate Android Development] mike29892:
I am getting random force closes for my email app. I searched the thead and saw a few others have this problem. Has anyone managed to get it resolved?
[Captivate Android Development] VanThePimpMan:
The lag was random for me, I really tried everything, I even slimmed down my apps to see if that was the problem, but it still was lagging. Then I tried to turn on Bluetooth and Wifi within seconds of each other and the phone locked up, so I decided to try out xcals and it is running smoothly so far. I really don't know what to say.
[Captivate Android Development] used2hvatreo:
Does it ever load? or does it just force-close every minute or so? I had that prob and I just loaded up CWM and formatted the cache and that made it work perfectly.
[Captivate Android Development] Jep56:
Dwonloaded xcal's kernel. Now I am getting the "BAZINGA" you are using an incomatible kernel" when I try to open VC. Anyone else get this? Seems to be running fine. Is this kernel just incompatible with that app? Or my phone?
[Captivate Android Development] schtuka:
That would be too drastic. I think that opinions or experience be it negative or positive should be in civilized manner.

"Hey, thanks for your effort, but I am having particular to my phone issues and I can't resolve it via re-flash/clear/or other. Soooooo.... here is what I have problem with (-) and if you get a chance please look at it."

Notice excaliburinhand attitude in his thread. "Mmmm, problem noted, can or cannot fix it, here you go new update at my leisure." No emotions, no cheap talk.

:)
[Captivate Android Development] shoman94:
weird... I just tried that too... cycling it a few times (BT and WIFI) it works fine.

Were you using the lastest builds that existz posted up in IRC last night?
[Captivate Android Development] shoman94:
That means VC is incompatible with the kernel. Xcals kernel is not an OC/UV kernel so that app does not apply.
[Captivate Android Development] schtuka:
Ecstatic about my battery life. GPS off, couple calls, emails, tapatalk, light use and 7 widgets.

Uploaded with ImageShack.us

Uploaded with ImageShack.us
[Captivate Android Development] toy028:
Xcals Kernel is not OC/UV so it wont work. If your using Talon then try rebooting and running the app or get the EX version if you dont have it already.
[Captivate Android Development] Jep56:
Thanks! I kind of thought that, but wanted to be sure! Phone flies right now! Love this ROM and kernel
[Captivate Android Development] Pierce533:
I finished loading the latest version of Cont. 5 and I am having a problem when I dial a phone number and the phone goes to connect, the screen goes black and will stay black until the other end of the connection hangs up. Once the screen comes back I can make additional calls with no problem. However, if I reboot this whole ordeal starts again.

I did a search and see a couple others have this problem, but I didn't see a solution. Can someone point me to the solution, if there is one?

Thanks.
[Captivate Android Development] rockosifraldi:
This is a proximity sensor issue... no fix yet which I know... if you wave close to the screen.. the screen should come back... may be pressing the power key.. until the fix comes thru :)
[Captivate Android Development] mrhaley30705:
@shoman,

Any idea why my notification tone won't change from default, even though it shows changed I'm sound menu?
[Captivate Android Development] keitaroguy:
Anyone else having the charge issue still I've tried battery calibration from the market and it seems to fix it. Goes to 100% drops to 98 when I unplug in the morning.
[Captivate Android Development] rockosifraldi:
so far so good, I did clear the battery stats from recovery though...;)