Develop Bugs

Phone call abruptly disconnects and screen becomes unresponsive, help!

I've had this issue happen a few times, so I disregarded it, but just a few minutes ago it happened 3 times in a row. Here is what happens:
I'm in the middle of a phone call, and suddenly I hear a beep, and I look at the phone and the call was disconnected (I'm back on the 'Phone' screen). I then realize that the phone becomes unresponsive (the screen doesn't respond, same thing goes for the Home/Menu/Back/Search buttons).
The only thing I can do is press the top 'Off/Lock' button to shut off the screen, then press it again, and everything goes back to normal.
This happened 3 times within 5 minutes.
Is anyone else experiencing this problem? If so, any advice/solutions?
My 30-day purchase window is up in about a week, so I'd like to get this resolved before then to avoid any headaches.
Thanks in advance.

Have you loaded any apps? Modified the phone at all?
I've never seen this type of behaviour before.

Thanks for the reply. No, I haven't rooted it, or loaded custom time or anything. The only thing I've done is just download/install some Apps from the Android Market, that's it.
What do you all think I should do?

*bump*
I think I may have fixed the issue -- I had the Google Voice installed on my phone, and when I uninstalled it, I haven't had the problem since (it's been about 3 days).
Has anyone else experienced any stability issues or glitches using the Google Voice app?

My mom has been having this issue with her stock 2.1 Inc... She says the screen suddenly stops working and all that will work is the power button and volume rocker. Says it usually happens mid call.
PS. she doesn't have google voice. And google voice doesn't cause this issue on my Inc.

Yeah, it just happened to me again, and I don't have Google Voice installed, so that's not the culprit.
Is anyone else having this problem? Please let us know in this thread - I am going to swap the phone out tonight at my local Verizon store.

It happens to me frequently. Before and after I rooted. Let me know what Verizon does about it.
Sent from my Incredible.

I got the phone replaced at the Verizon store a couple of days ago, and I have yet to see the problem. However, ill keep a close eye out and will post another update in the next several days.
Sent from my ADR6300 using XDA App

com.android.phone has stopped???

Hi,
ever since having updated my unlocked Captivate Glide to ICS on Saturday, I keep getting the message "Unfortunately the process com.android.phone has stopped". Initially I thought this was just a nuisance. But at work today, I found that everytime a call came in this message pops up and on pressing the only option- "OK", the call disconnects. Further more it neither shows whose call got disconnected nor its shows missed calls. What gives?
Was wondering whether anyone knows anything regarding this before I go back to the stock gingerbread from the ROM
Ameyam

ameyam said:
Hi,
ever since having updated my unlocked Captivate Glide to ICS on Saturday, I keep getting the message "Unfortunately the process com.android.phone has stopped". Initially I thought this was just a nuisance. But at work today, I found that everytime a call came in this message pops up and on pressing the only option- "OK", the call disconnects. Further more it neither shows whose call got disconnected nor its shows missed calls. What gives?
Was wondering whether anyone knows anything regarding this before I go back to the stock gingerbread from the ROM
Ameyam
Click to expand...
Click to collapse
When this happened with our Glides we did a factory reset, which fixes the process.com.android.phone issue. Not had a problem with it since.

Same over here. No more problems after factory reset.

guillermogc said:
Same over here. No more problems after factory reset.
Click to expand...
Click to collapse
Yes, did a factory reset on Monday. Just didnt update the post after that
Ameyam

[Q] process com.android.phone not responding..

im currenty using liteROM 0.9.0 first 3 days work fine, but after i found this problem.. can anyone help me..

+1.
My phone.android repeatedly shut down in Gingerbread. Only fix i could find was upgrading to ICS.

when arldft
Hmmm.... that is weird, i´m also using LiteRom 0.9, never had that issue, first time i flashed the custom rom i did see that message a couple of times, but no big deal just reeboot and no probs. after that though i decided to install the rom from scratch, never had an issue with it since. only problem ive had is the toggle for gps sattelites and mobile connection giving me some issues, nothing a reeboot cant resolve.
my advice would be to backup all your info & apps and start from scratch. or boot to CWM and fox permissions.
hope i helped

I had similar issues with GB. I was using the latest Osimood rom. Upon receiving a call, my phone screen would go blank (the way it normally does when switching to a call) but then it would freeze. The ringtone would not ring and after a few seconds of this, the phone would go back to the last app and the network signals would be gone. After a few more seconds, the network signals would be back. The same thing would happen if I received another call. The only fix was to reboot the phone.
The annoying part was that there would be NO way for me to tell who was calling me since I would never see their name and no entry would be made in the phone log. I didn't have any success with treating that problem. While it didn't happen very often, the few times it did would be very annoying since I'd often find out several hours later that I had missed an important call.
I've just switched to Pacman rom today in the hopes that this was a rom issue and will be gone now. Let's see.

Some issues of the stock rom, is anyone else having them too?

hi guys, i got a d855 and i have some issues which i think they may be stock rom's bugs and i d like to hear your opinion. I have the latest ota V10h-EUR-XX btw.
1) Every time i restart it appears in the notification panel the "voice mate" shortcut. I remove it using the edit at far right but still it reappears every time i reboot the phone.
2) Sometimes after an unanswered call or message the screen turns on as usual but it doesnt turn off. Ofc i ve selected to shut off at 30 seconds from the settings. Even if i change the settings to like 15 seconds the screen still wont turn off unless i manually lock it. This problem fixes if i restart the phone.
3) Every time i boot my phone i get this message: "unfortunately the process com.google.process.gapps has stopped"
So is there someone else who experiences these kind of issues?

wow, these 3 bugs are new to me. haven't experienced any of those at all.
I'm on V10J global though.

You're having permissions issues.
I'd bet my left testicle that a fresh flash back to stock will fix all 3 of your issues.

+1 on the voice mate .. irritating ~

I've encountered the screen on issue - although not only did the screen stay on after a missed call, the phone also became and remained completely non-responding, no screen input registered. Had to reboot manually. It happened only once in 3 weeks though.

calls error

hi guys
kindly ask to help for a problem that I have with my note10+ SM-N976B.
Everytime when I receive a call and I answer fast, in 2-3 seconds, always the call cannot be established. The caller is not hearing me, I cannot hear him and even on the screen that is no indicator that the call is ok.
Simply is freezing the call.
Everytime I need to let the phone ring at least 10 seconds.
the phone is updated with the latest stock firmware.
could anyone have an idea how to solve it?
thanks again

I had similar before on wifi calling with dodgy wifi. so if you are using wifi calling I would try disabling it to see if it goes away.

hi thanks for answer
i dont use wifi call at all, only normal calls

no further ideas please?