Database Develop

[Q] samsung captivate wont answer calls

I have a samsung captivate. It is a early model, I got it the day they became available. The phone will not always answer an incoming call. the green answer button comes up but will not swipe. Anyone else have this problem? Will froyo cure this?

Youre gonna need to add some more info....
are you on stock 2.1?
if you did flash a custom Rom which one and which kernel/ modem are you using?
Did you do a restore with titanium? (this is where I had problems when I flashed)

captivate wont answer incoming calls Sometimes
yes complete stock, no mods whatsoever

I had a problem like this when I first got my Captivate as well. My problem was that it wouldn't swipe all the way across the screen. This got very frustrating while driving. The solution, surprisingly, was to make sure my hands weren't completely dry. Without traction on the screen my phone didn't register my fingers.
I don't know if that'll help but there are also other dialers out there on the market that you can try legitimately without rooting or flashing a different ROM (if you're trying to avoid doing those things).

I would do a flash back to stock and do a master clear to rule out any software issues. You can do this without having to root. You just wont be able to back up your apps and system config.
Sent from my SAMSUNG-SGH-I897 using XDA App

It is and always has been completly stock.

Are you rooted? I had this problem every now and then... not very often.. I figured it was due to one of the apps I was running in the background, that was sucking up all the RAM and the phone became unresponsive. I backed up my apps, and flashed stock and then restored only the ones I absolutely wanted... I am sorry, I dont remember which app it was, just know that it was a background process that was collecting some kind of stats! Hope that helps!
By the way how long ago did this start happening?

rskeeters said:
I have a samsung captivate. It is a early model, I got it the day they became available. The phone will not always answer an incoming call. the green answer button comes up but will not swipe. Anyone else have this problem? Will froyo cure this?
Click to expand...
Click to collapse
i had a similar problem even tho i had a custom rom my incoming calls didnt come in at all.i had to Reflash my rom.. idk how similar this situation is but i agree with the other guys.. try reflashing stock

phone is not rooted. I cant tell you how long it has been happening but it appears to be more frequent as of late. The one thing I can ad, when it does it, it may do it several times in a row
Thank you guys for helping the newb.. I appreciat the input!

I occasionally get the same problem on my SGS even before rooting
Sent from my GT-I9000 using Tapatalk

The time it took you to go back and forth on this forum, you could have flashed back to stock and master clear to troubleshoot. The problem isn't going to fix itself.
Sent from my SAMSUNG-SGH-I897 using XDA App

Thanks for all the HELPFUL input
I will try flashing stock

This may be a common sense answer but usually when it doesnt swipe all the way accross for me its because of to much grease ( or sweat) on my hands or on the screen like after lengthy phone calls or if my hands are dirty or something. Try cleaning the screen well, and washing your hands and such. Always fixed for me.

by swipe do you mean it doesnt move at ALL or it goes half way or you cant get it all the way to the other side to answer?

Yeah, i know that when i first turn on my phone and try swiping, nothing will happen, it will just stay green and not respond. After leaving my phone on for a couple of minutes, it usually corrects itself.

This is also a common problem for stock users wanting to use a lockscreen replacement (i.e. widgetlocker).
If you try using widgetlocker without any lagfix, you can get phone call screens you can't interact with for a few seconds.

I have had a similar issue both stock and rommed. I find a lot of time it does have something to do with friction on the screen but also if I have low signal it will happen as well. My phone will actually freeze up to the point of having to remove the battery, this same thing happened on my old Samsung Blackjack II.
Sent from my SAMSUNG-SGH-I897 using XDA App

Fixing random shut down

My wifes captivate has the random shut down issue. Already got replacement phone and it started back up after a few weeks. If I use Odin one click to restore ucjf6 (or upgrade her phone to froyo) will this end my shutdown woes? I have been under the impression that the shutdown issue was a software problem.

I can't say I've ever heard of that happening to a stock rom (I'm guessing you never flashed any custom ROMs on to it)...
At this stage, I think it'll be better off if you take it back to AT&T as you've not really done anything to it (modding/romming wise).

Its out of warranty.she has been dealing with it by using an app from the market. I was hoping that upgrade to froyo would over write the defective software. Then I got to thinking that maybe odin would do the same thing.
The app from the market works perfectly, but it kills her battery life(it's called Captivate Keep Alive from Blue Steel).

Hmm, then yeah I suggest for you to flash her phone... Possibly to a custom ROM at this stage. Stock ROMs usually have way too much bloatware.
Also, if you can please check what version of Captivate she has... It'll be underneath where her battery is.
Usually a four digit code (1006,1007,1008,etc).

Hers is 1008.

Yeap, you should be fine to use any of these ODIN files.
2.1 - http://www.megaupload.com/?d=SBSMALFJ
2.2 - http://www.megaupload.com/?d=QL6NX702
If you need instructions, just yell again
I would probably recommend the 2.2 one (if you're not going to flash any custom ROMs).
If you are thinking of custom ROMs, then I recommend going to 2.1.

Thanks for the help. I, and my wifes battery, appreciate it.

My cappy also just randomly shuts off, but i know it isn't the battery because I've switched batteries from another cappy. I also heard there were re-calls on some cappy's as well. can it also be a hardware problem?

I have installed Firefly 3.0 on my captivate every now and then when the battery gets low to like 30% it turns off and then i gotta pop the battery out and pop it back in because it randomly shuts down. It has happened in games, phone calls from friends that are in iraq, and various other things. I just reloaded fire fly onto my phone but I am not sure whats going on with it.

After trying about everything to kill this gremlin, deleting widgets, CKA, Load Monitor, etc., I went back to JF6, charged the phone fully and let it run. The problem is still here. On the very next battrery cycle after reverting to JF6, the random shutdown occurred again while running off battery with a bone stock set-up. The battery was at about 70% when the failure occurred. (It is a new battery too.)
I bot my fone last Sept, just shy of one year ago. So today I called ATT and after a short discussion with the rep, a replacement is on the way. I described the problem and advised that one by one I had un-installed all the widgets and apps that I thought might be causing problems, then mentioned resorting to the factory reset.
A few questions followed. Then I was on hold awhile. I'm really glad I reverted to JF6 and ran the stock set-up to the fail condition. It allowed me to speak to the rep with confidence, and high hopes that they would get me an exchange. When it came time to answer questions about the Settings About details, it was all right as rain.
Now the question is will the new device have the power-off Gremlin? We shall see!
Guess I'll have some fun flashing different set-ups for these next few days 'til the replacement arrives.
Then one last flash to JF6 and back this first cappy goes...
If you are experiencing this shutdown issue, get back to stock and see if it stays. If you have had your phone less than one year, and it's dying on you, you should be able to get a refurb.

[Q] Stock Dialer Gone Bad, Used Odin and Kies, Still bad! Help!

Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign

^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.

I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.

A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.

[Q] Captivate loop soft reboot???

I am a broadcast engineer and have been a Linux user for the last decade. So when Android hit it was only a matter of whose device. After a lot of research and waiting for 6 months for the initial “teething pains” to pass selected the Captivate for several reasons.
As a broadcast engineer 24/7 reliable cellular communication with data is a professional necessity not a convenience. For that reason my wife always has the same phone as I carry as a backup. If mine gets broken or unusable for any reason we switch SIMs and I am back to work. So we both received our initial “trade up” Captivates at the same time. About 25 days after receiving our phones mine started randomly shutting itself off. After three warranty replacements finally got one that stayed on. Six months later wife's was replaced due to no audio from the speaker. Later after my father past my mother merged into our family plan and choose Captivate as well.
So we have three Captivates in our family. Love the phones. Mine by my nature is loaded with “all the bells & whistles.” Lots of app, widgets and rooted. As soon as I am comfortable with my choice and feel prepared will take the plunge and try flash a custom ROM. More than likely several through ROM manager of some kind. I really like to looks of the four tap lock and other features only a custom ROM is going to get you. Besides I am a “power user,” which my wife thinks translates to “if it works, it doesn't have enough features.” My wife has a few widgets & apps as well as my mother to a lesser degree.
In the last 90 days we all three have been experiencing something that I describe as a “loop soft rebooting.” Started with my wife, she described it a “loop rebooting.” Every weekday from 10:00 to 10:20. Once I had a chance to observe I found it does not do a complete reboot. It does not show the shut down animation like a controlled shut down. Or the turn on animation like a power up after a complete shut down or OS crash. I would describe it as more like a “soft boot.” Almost like a launcher crash, but it also has to rescan the SD media. It vibrates once with the screen off or on, in use or out. then twice more, another 8 to 10 seconds another vibrator alert then the launcher appears and starts to load widgets, apps & scan media. Completely unresponsive to any key input until after the launcher reopens. The wife has never used anything but the AT&T/Samsung stock launcher. I did all the usual things. Backup, factory reset, restore. Still does it. Backup, Hard reset, restore, still doing it. Hard reset, rebuild from scratch, no restore, stayed completely vanilla, no apps or widgets at all. It still does it. Then mine started doing it. I was using ADW Launcher, switched to Launcher Pro, have even dropped down to using the original launcher since it acts like a launcher crash. No affect. Went through all the above same process with the same results. Mine does it's act between 5:00 & 5:20. About a week later my mother reported hers does the same thing between 4:00 & 4:20. Interesting side note, if we turn off the radio (airplane mode) it does NOT do it, completely stable in PDA mode. But when we turn the phone back on, it then starts the process and runs for 20 minutes and stops. I have been collecting logs off my wife and my own phone but work duties have not given me the opportunity to read through the thousands of lines of logs to find a “smoking gun.” Now in the last week we see the same activity more often and for longer periods. Because turning off the radio stops the activity there has to be a trigger from the network. It also uses lots of data during these periods. Maxed out my wife's data plan the last 3 months. We have Lookout Security installed on all three phones and it reports no Trojan's, viruses etc... Also the Hard reset should have killed anything like that. I have done hard resets three time on my wife and my own phone and rebuild from scratch now. We have left her phone completely factory fresh only adding back her contacts through Gmail. I have Titanium Backup and have tried “freezing” & unfreezing” everything I can think of. Nothing but turning off the radio seems to effect this issue.
Has anybody out there experienced anything like this???

Damn dude, can I get the cliff notes?

If you're thinking of taking the custom rom plunge, I would say to go for it. The reason I suggest this is that most custom roms will also flash a different modem, which might allow your phone to connect to the towers in a way that will prevent the hot reboots you're seeing. Just make sure to do the normal backups (Titanium backup) of stuff you want to save before flashing.

^ +1
sound74145,
yeah since ur rooted, i would suggest flashing a different modem (radio) if u don't want to flash a Dev Rom yet.
What is ur Baseband version now... i897uckb1 ?? If so try i897ucKH3.
Check the modem stickied thread. It should be attached behind the paperclip at the title of the thread.
Sent from my SAMSUNG-SGH-I897 using xda premium

hysterical

Help diagnosing freezes and random reboots

I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?

Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.

I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.

Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much

studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)

stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.

stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues