[Q] Droid 3 Error: com.android.phone is not responding - Motorola Droid 3

Hey guys,
So, this problem started 2 days ago. I am receiving a call, but I cannot answer it. The screen does not respond to accept or decline the call. The phone is on 'loud' yet it is only vibrating. after a while of trying to end the call or answer it, a force close error message comes up saying: " com.android.phone " is not responding.
Please help. what can be the cause? and how can i rectify it.
Phone is not rooted. I recently installed the Mobo Task Killer. (which seems to be working fine so far...).
This is basic functionality of the phone, its kind of frustrating me to know i paid so much, yet the basic use of the phone is questionable.
Thanks in advance for anyone's assistance.

Well uninstall that moto task killer...if that doesn't fix it...and you haven't rooted..then nothing else to do but to sbf.
Sent from my DROID3 using xda premium

Related

Text msg problem!! help?

I've been having this problem for a few months now. I'm from holland and I already emailed my provider but the told me they can't help me.
So there are a few things happening:
My screen lights up but there's no message coming in. A few minutes (or hours) later I get the message that was supposed to be received at the time it lit up. Sometimes when I go to comm manager and turn the radio on and off or just soft reset the phone, I also receive the texts.
I send/receive messages when I start using the phone, like when you open a menu or something.
Sometimes I keep getting the same texts over and over again from the same person.
I've tried a few different ROMs so that can't be the problem.
Someone told me about flashing a new radio maybe that could do it?
Please help me??
Thanks!
Seems like the same problem as me
i'm also from the netherlands..
i hope someone knows a fix.

Vibration stopping?

I have vibrate enabled for the on screen keyboard and every once in awhile all phone vibration will stop in the middle of typing. It wont vibrate then for calls/messages/etc. It used to come back after I locked and unlocked it but now only if I leave it alone for a minute. This problem happened on CyanogenMod and still happens on froyo. Anyone else experience this?
-------------------------------------
Sent via the XDA Tapatalk App
Yes.. same for me.. It started with CM and also happened on froyo... now I'm back on CM and the problem is there (after 10-15 chars entered, vibration stops)
I got the same problem. Last week I sent my nexus one to htc for repair. Their stupid engineer made some scratches on my phone and hasn't found any hardware problem. Today when I was playing my phone and I think I finally found the problem. When I opened "android system info" application, the vibration suddenly gone. I uninstalled it and haven't met the vibration problem for the past 10 hours. So you guys might need to check whether you have installed this application. However, I might need another several days to finally conclude this observation.
I've never had that application installed so I don't think its that

[Q] Can't answer calls, problem appeared out of nowhere

Hey
My dad is using a Samsung Captivate which has been updated to the AT&T's gingerbread. The phone is rock stable and ran fantastically for almost 4 months, until yesterday. He has been complaining that about 7/10 incoming calls he was not "able" to answer. I tested it and found that when someone calls the phone, the incoming call screen that shows the caller's name/number/picture, accept and reject sliders, speaker options etc. does not show up and instead the phone just rings and there is no way to answer call. I restarted the phone and the problem went away, however I would like to know why this problem suddenly appeared, and are there any chances of it appearing in the future? My dad is definitely not a tech-know-how person and this captivate was a gift from me so I would really appreciate some insight on this problem.
PS: Also, could it be possible that another application with dialing capabilities could be causing this problem? We have Skype and Mobile VOIP installed, and have had it since the day he got it. Just as a precaution I cleared the defaults and made the phone+dialer the default for making calls. Been about 5 hours or so and the problem has not re-appeared, yet.
Watkins said:
I had nearly the same issue, except mine got to the point where the speaker phone didn't work either. Music played fine, phone calls stopped working. I went through a lengthy process of accidently deleting everything I had on my phone, which lead me to buy a USB Jig, install the stock ROM and it worked perfectly. I would suggest trying this before you try and physical fixes on your phone.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1427840

unfortunately the process com.android.phone has stopped

I am in a position where I'm unable to send text messages. When I try to I get the above error message or the message status keeps displaying as 'SENDING' but message never goes. I am able to make voice calls no problem. I have rebooted, force stopped the message app, all to no avail. I have been using the phone with no problems for months now and this happens out of the blue. Would really appreciate someone's help on this.
Regards
Ferg
May be it's caused due to one one of the mods installed, apps, or data corruption. Reflashing the rom should eliminate the problem.
nokiamodeln91 said:
May be it's caused due to one one of the mods installed, apps, or data corruption. Reflashing the rom should eliminate the problem.
Click to expand...
Click to collapse
Ooops bit embarrassed but posting this in case someone else makes the same mistake. But it seems the SMS I was responding to comes from a number which does not accept text messages. This was also causing other messages to be held up which explains why legit responses were slow to send. So hopefully problem is solved.
Will probably upgrade my slim bean rom next week hopefully it goes smoothly

[Q] issues after making a phone call

I'm hoping someone has experienced the same situation as I.
For some reason after making a phone call I get stuck on the screen that says the redial or message for like 30 seconds to a minute before I can make another call or back to home screen.
This Issue has happened On Rapture and Hyperdrive Tom. So that's telling me most likely an App is the cause of this issue. The weird thing is I haven't installed nor updates any apps for a couple days.(Auto update turned off in google Play. Everything was normal then out of no where this issue started.
Any help/ ideas/ fix will be appreciated and thanked
Any xposed mods that might cause this installed???
Also was this a clean install??
Which includes wiping the internal?
Flash.
Part of the Solution

Categories

Resources