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
Related
hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.
thelistening said:
hi,
For starters I've had my G1 since it came out, been rooted for a while so i know what I've been doing.
Anyways.. I've checked the forums and I've seen similar problems like mine but not exactly the answers I need.
Basically my Digitizer is being unresponsive randomly and when this happens my entire phone just FC's everything. The first time i noticed this was when I would Charge my G1 using a Blackberry Charger when id text, the Screen would be unresponsive to touch on all of the screen and just lag on everything. So I would have to unplug it and re-plug it continually. Recently I switched to the new Cyan Rom (i forgot the number) and now it will just randomly be unresponsive with the touchscreen id go on apps and it will FC. Ive wiped and rebooted many times, ive switched roms multiple times as well. So I'm on my last resort and asking for help.
Any help is highly appreciated.
Click to expand...
Click to collapse
Try to upgrade to the 27.08 Radio/SPL combo. Follow all of the instructions contained within that post. It will suggest you also re-install your recovery. Do it. Once all of this is said and done, if its a software issue, it should be solved.
I had this same issue prior to the upgrade, and all is fine now. Mine didn't FC tho. If I touched the bottom of the screen, it would select something at the top. any questions or a perfect walkthrough, my direct email to my cell is in my info on the left.
<<<<<<<<<< Over there.
ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.
thelistening said:
ah! thanks! Im actually going to try this now, and hopefully i don't fail and mess up my phone even more than what it already is. and yeah the FCs are really annoying i cant really do anything like make calls, which is ridiculous. Im also having problems with the camera as well i got those really funky colours in it. and then my regular speaker for calls isnt working unless i put it on speaker, i think my G1 is telling me it wants to die. lmfao.
Click to expand...
Click to collapse
Oh crap. You have the funky color camera?! That might actually be a hardware issue. But we can certainly try this out. I have the gTalk PC app, and it's up and running now if you wanna run through this.
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.
I just recently flashed a ROM for the first time. I went with CM7 as I was looking for something close to gingerbread to improve my phone's performance. I like the way the phone is running, there is a lot less lag, but it didn't solve a problem I encountered a few days before flashing.
On the advice of a friend, I installed an app called Llama, which is a free, dumbed down Taskr wannabe. I installed it, played with it a while and decided I didn't like it, so I uninstalled it. However, since installing it, my phone no longer vibrates when it gets an alert (text, google talk, etc.). I was hoping flashing would solve this, but it hasn't.
My question is, would flashing back to stock (via Odin, or something similar) possibly solve this issue? Or, is there any type of data that the stupid Llama app left behind that I could manually delete to get my vibration notifications to work again? Thanks in advance for any advice.
Dude llama's awesome, I use it for everything. Most likely it just changed a few of your volume settings. You just need to set them back to the way you like. No flashing necessary
Sent from my ICS i897 Captivate
It was okay, just wasn't for me. I've reset all my settings and whatnot, especially considering I flashed CM7 after uninstalling Llama, but still nothing. It won't vibrate for any alerts or when I plug it in like it used to.
I've searched the note forum praying for at least one other person to have this issue, there seem to be none. I am really worried.
Sometimes, after a phone call, the 'back' and 'menu' buttons become inactive, as in they don't respond. They light up when you touch the screen, but they don't respond at all. It started happening about a month after I bought the phone. Initially I thought it was a bug from some ROM. I've done several factory resets and flashed new ROMs. The problem doesn't seem to go away. I don't know what to do.
I have to reboot every time this happens, but then it only stays till I get/make a phone call. It doesn't always happen after the first phone call. Sometimes it happens after the second, third etc. But it always happens. Please help.
Thank you for helping me.
You are not alone... happens to me every now and then. Reboot is the only option...
Sent from my GT-N7000 using XDA App
same here since i got the phone with the stock rom, have tried a few custom rom, problem still remains
sorry wrong post ignore
It is very very annoying. I wanted to know if its a hardware issue or a software issue. Rebooting every time after a couple of phone calls is simply unacceptable. If only a very few people have this problem, its probably a hardware issue.
I really want to find a solution. I've grown really fond of the phone, and I don't want to sell it.
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