Caller ID and Outgoing call issues - Motorola Droid 3

Hey everyone,
I'm having 2 separate issues that I don't think are related, but could be. I have an unlocked Droid 3 XT862 running on Rogers (in Canada) that has been upgraded to 5.6.890.
1) Since upgrading the OS, whenever I get a call from someone that is not in my address book, the caller ID always shows up as Pay Phone. I've tried a battery pull and checked all my call settings, but to no avail. I've considered reflashing back to the stock OS, but don't want to deal with the shoddy battery life.
2) Whenever I make a call (and this has happened since day 1), it goes to the call screen, then says call ended and goes to my home screen. About 2 seconds later, it goes back to the call screen, and makes the call as expected. So it will make the call, but with a ~3 second delay.
If anyone has any insight into these problems, I'd be happy to hear it!

As a followup for anyone that's on Rogers (in Canada), the call display issue was related to a feature called 'name display'. Apparently it's incompatible with the majority of android phones, so if you're having issues with call display, try disabling it.
Sent from my XT862 using XDA App

Second update, no improvement with the 'call ended issue'. Not a big deal, but still strange. Same deal with stock OS, Liberty rom, CM7, and CM9 alpha 1 and 2.
Sent from my XT862 using XDA App

Related

Incoming call screen disappears - can't answer call!

Hi all,
Friend and I both have the Incredible S, loving it! He has a slight issue and I can't for the life of me solve it. Everything was working fine but now when he has an incoming call and the screen is off the incoming call screen flashes up briefly then disappears and device shows normal 'desktop' - you can't answer the call!
If you call his phone and the screen is active, incoming call screen pops up as expected and you can answer call.
Any ideas peeps?
Thanks
Ant
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Sliphorn said:
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Click to expand...
Click to collapse
Never worked it out, friend did factory reset in the end to fix it.
Ant
Bummer. Here's some info:
Latest Fresh EVO
Rom Manager
Rom Manager Janitor
Juice Defender Ultimate Juice
Titanium Backup Pro
Cachemate for Root
ShootMe
Adfree Android
adbwireless
Call Control (problem before this, though)
Launcher Pro
Any hints?
Having the same exact issue. This sucks... This started today for me around noon ( no calls before then), and has persisted throughout the day. Yesterday was fine.
I use Google voice for all of my calls.
The only thing I've done today that I haven't done every other day was that I installed the Gtalk app this morning. In the past, I've used Gmail directly. However, my computer was off during at least one of the phone calls I received today, so I can't imagine this could be it...
Perhaps because I installed gAlwaysIdle (an addition to Gtalk that makes you never go idle or always be idle) as well?
Does this correspond with anyone else's experience?
I'll probably just reflash my phone
<Rooted Atrix 4g running GingerBlur>
hmm this sounds like a serious firmware problem tho..
all i could suggest is flash a firmware that the most of the ppl are using, and dont got probs with...
well doing a good reboot seems to help alot these days. So disable the fastboot option en turn it off, wait a while (10 secs should be enough) en start the device again.
Also had some of the trouble like crashing things and this solved it for me. Give it a try and hope it will fix it.
Otherwise there seems to be no other way than a factory reset (go htc!)

[Q] Phone kinda reboots with incoming call

I upgraded my Captivate to gingerbread/talon/continuum yesterday.
That went fine and everything was hunky dory.
Phone was working fine the whole day today, incoming/outgoing calls, data.
I came home and installed Skype and thats when all hell broke loose.
Now the phone part is dead (kinda!). I can make calls fine but if I get a incoming call, the call gets disconnected after 1 ring and I get a msg popup (like some error) but I cant really see what the message is.
I also noticed that it disconnects me from ATT network when a call comes in and then after a little bit it reconnects.
I also verified this by going to the About->Status screen and then making a call.
It normally says ATT but for a couple of secs after call drop it says 'Unknown'.
What did I do to screw it up and how can I fix it?
Thanks
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
mommehK said:
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
Click to expand...
Click to collapse
Sorry, I should have added that to my first post.
Yes, I did uninstall Skype and reboot the phone, just incase, but no difference.
Still the same.
Update:
After playing around with various things for a couple of hrs, I finally gave up and reflashed Continuum.
Everything started working again.
Applied my Ti backed up config and loaded Netflix. Same problem. Dialer died with an incoming call.
I reflashed Continuum again and everything started working as expected.
I then applied my Ti backup, still everything working.
I am in the process of updating all my apps and then lets see if everything is still working.
The only thing that is missing for now is the Netflix app.
I will keep everyone updated if its the Netflix app causing the issue or its the Skype.
activemind: Keep us posted if you find a cause. I am on a Samsung Vibrant (3g) via TMOB but have been having the same issue today with a completely different rom (simply honey). This is actually about the 6th thread I've found in the past two days having this same issue on Galaxy S phones.
I have had this problem before and what caused it was restoring system data with titanium. Make sure you are only restoring apps.
Sent from my GT-I9000 using XDA Premium App

[Q] phone calls cause sluggishness, freezing, and crashing of phone app

I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
tigane1 said:
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
Click to expand...
Click to collapse
Try aoip its up to date and works good.
schuylkillparanormal said:
Try aoip its up to date and works good.
Click to expand...
Click to collapse
working on downloading it but the download keeps failing -_-
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Mwas. said:
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes rom and cache/dalvik. And if I forgot I went back and wiped and re-installed it.
tigane1 said:
Yes rom and cachredowvik. And if I forgot I went back and wiped and re-installed it.
Click to expand...
Click to collapse
There's nothing wrong with the link try redownloading the ROM something might of got corrupted.
I fixed it. Kind of
I did a bit more searching using some different terms and people were having trouble with the proximity sensor on their phones causing similar problems so I turned mine off and the problem corrected itself! So now I guess I just have to deal without having a functioning proximity sensor during calls, oh well, not a biggie. I appreciate the help though guys.

[Q] Annoying bugs with my active!!!

So I picked up a stock AT&T active and been using it for a month now. I love the phone but a few annoying things that it does daily on me is really starting to make me want to throw the poor phone! First the screen is way to sensitive sometimes! I try to text and it adds letters or I try to move between my home screens and it will open an app like I tapped on it, but I didn't. Or when I close out my running tasks it will act like I double tapped in that certain area and will open my mail app since it was in that touch zone. Anyhow I have played around with all the settings like "Air View" or "Motions and gestures" under the settings menu. Also the calling contact feature is really pissing me off. Say someone calls me but I miss the call, so I bring up my call log and I tap on the person that called me. It shows the phone icon and usually when you tap that, it suppose to call the person, but no stupid phone goes back to the call log list instead. I have to keep doing this like around 5 to 10 times before the dumb phone will finally decide to call the person! I am running the stock, or at least what came with it, firmware. Android version 4.3 with Baseband of I537UCUBML2. Has anyone else had these issues with this phone? Plus how can I fix this?
kcraptor82 said:
So I picked up a stock AT&T active and been using it for a month now. I love the phone but a few annoying things that it does daily on me is really starting to make me want to throw the poor phone! First the screen is way to sensitive sometimes! I try to text and it adds letters or I try to move between my home screens and it will open an app like I tapped on it, but I didn't. Or when I close out my running tasks it will act like I double tapped in that certain area and will open my mail app since it was in that touch zone. Anyhow I have played around with all the settings like "Air View" or "Motions and gestures" under the settings menu. Also the calling contact feature is really pissing me off. Say someone calls me but I miss the call, so I bring up my call log and I tap on the person that called me. It shows the phone icon and usually when you tap that, it suppose to call the person, but no stupid phone goes back to the call log list instead. I have to keep doing this like around 5 to 10 times before the dumb phone will finally decide to call the person! I am running the stock, or at least what came with it, firmware. Android version 4.3 with Baseband of I537UCUBML2. Has anyone else had these issues with this phone? Plus how can I fix this?
Click to expand...
Click to collapse
First off I'll say that ML2 had been known to be buggy. For your first problem, did you make sure Glove Mode is disabled? For your second problem I have no idea. Sorry I can't be more helpful.
If it is in fact stock, do a software update to KitKat and it should fix your stability issues. I can't because of root.

Suddenly Can't answer calls on the Nexus 6

About 2 days ago I noticed when i receive a call, it rings but the screen is black. If i hit the power button it will wake the screen but it doesn't show I'm receiving a call except for the fact I lose LTE ( I'm on Verizon). I can also double tap the screen ( have the mod) and it will wake but still nothing. Once the call is over it will show a missed call in the status bar. I'm rooted but on 5.0.1 stock. Was working fine until a few days ago. Anyone else?
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
KB112 said:
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
Click to expand...
Click to collapse
No, not using Lux. Starting to piss me off. Just shows up out of the blue and haven't really installed any new programs in a while.
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
chemguru said:
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
Click to expand...
Click to collapse
That was a great idea but still didn't work. I took the screen protector off and still the same thing. I might try a custom rom but I think it's time to sell. I love big phones and I do like this phone but it may be a tad too big for me. Might put it on Craigslist but the hicks in my area don't understand what "Nexus" is or "price is firm"...."will you take $150 for that there phone?"
alnova1 said:
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Click to expand...
Click to collapse
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
SP_Kenny said:
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
Click to expand...
Click to collapse
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
alnova1 said:
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
Click to expand...
Click to collapse
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
SP_Kenny said:
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
Click to expand...
Click to collapse
I just installed it and it seems to have fixed my problem for answering calls. Have no idea what was wrong before on the original rom. Seems to be running nicely and Verizon is working fine it seems like. Thanks for the recommendation.
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
SP_Kenny said:
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
Click to expand...
Click to collapse
I definitely will as soon as I head out and do a little testing on it.
I had this exact problem with my wife's Nexus 6 but mine was functioning fine. Turns out that under SETTINGS - SOUND & NOTIFICATION - APP NOTIFICATION she had the Goggle Dialer blocked.
Have the exact problem outlined by the original thread starter, scour a few webpages with different sort of solution.... nothing works!
My solution: Simple, just uninstall the Phone app updates, voila, all back to normal.
Hope it'll help someone.

Categories

Resources