Database Develop

[Q] Apps Crashing, Need help

Hey guys, I've had my captivate for about 3 months and I love it. Well, I loved it until the at&t update about a month ago. I dont know if it caused the problem, but since that week or so, Ive had crashing problems with my apps. It started with the messaging app. Everything freezes, I still get haptic feedback, and then the sms fails, sometimes the phone and some games too. So I downloaded handcent and that worked for about a day without crashing, and now it wont open half the time. I have never rooted my phone, but I use launcherpro if that helps.
Does anyone know why this is happening or how I can fix it?

Have you flashed any custom roms or did you just do the at &t update? I can make some suggestions but they would require you to root your phone. Otherwise call at &t
Captivate
Cog 2.2

Why don't you just simply use the Odin one click and go back to the firmware from before the at&t update?
Sent from my Captivate

@mcord
no, i havent done much customization besides installing launcherpro. nothing that requires a computer
@miztaken
i dont know much about odin, mind telling me more?

[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

[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.

Will Flashing Back to Stock Solve My 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.

Screen Turns off and wont come back

OK, so im fairly new to this game.
I have has my I9000 for about a year, and have always sufferer from the problem of my phone 'sleeping' it can be find for days, and then randomly when i pick it up, or the phone rings, the screen wont turn on. the only way around is to pull the battery out... not good when its ringing!
i did the general factory reset, and upgraded via Kies, but I still had the same problem..
So today i downloaded and flashed the stock version of Gingerbread 2.3.6 hopeing to cure it by remving the Orange customer versions..
This obviously reset the whole thing, and even with Samsungs stock Version and zero apps, it STILL does that same...
Anyone else have this sort of problem? i have searched and found similar problems, but most indicate its on phone boot up.. so not sure if its the same.

If problem remains after flashing a new ROM via Odin, then it doesn't look like a software problem :/ Maybe you should go to service.

Its definitely a hardware problem. But you could try increasing the voltages for the lower CPU frequencies. You will need a custom kernel and then use voltage control from the market.
Sent from my GT-I9000 using xda premium