[Q] Caller ID Call Waiting doesn't work! - EVO 4G Q&A, Help & Troubleshooting

I have noticed since upgrading to Froyo that my caller ID is broken if I'm already on another call. It's very strange because it only shows the phone number, but after I complete both the calls and go into my call log, the phone is able to resolve the number to the contact.
I've been reading around the net and there's spotty coverage of other people having this issue but no resolution.
Is anyone else having this problem? Anyone else figure out a solution?

No problem with it here, mine has been working fine.

mine does it intermittently

Just as importantly, there seems to be no way to hang up on one call while keeping the other. You can flash between the two, and even merge them, but switching to one and then hitting end hangs up on both. As it stands, I have to let the one call sit until I decide to hang up both.my old g1 had a "switch and hang up" button that you could use to select the caller you wanted to disconnect.

pinetreehater said:
Just as importantly, there seems to be no way to hang up on one call while keeping the other. You can flash between the two, and even merge them, but switching to one and then hitting end hangs up on both. As it stands, I have to let the one call sit until I decide to hang up both.my old g1 had a "switch and hang up" button that you could use to select the caller you wanted to disconnect.
Click to expand...
Click to collapse
I haven't figured this one out either

Related

[Q] Can't answer calls sometimes! Really annoying!

Hello everybody,
Everything is fine with my Arc, except for the huge problem that sometimes I simply can't answer an incoming call! It happens like this: When a call is incoming, the phone starts ringing and vibrating as it usually does. However, the screen that is supposed to come up which shows you who is calling and where you can select to accept or reject the call is simply not showing up.
Has anybody experienced this before?
All I can do is slide to unlock the screen and then I'm looking at my home screen with the phone still ringing but no chance to get the call. There is nothing in the notification area or anywhere else where I could answer the call. All I can do is to wait until the ringing stops!! Really really bad behavior.
Furthermore, once the ringing has stopped, there is no information about the missed call in the call log. So I can't even call back the person who called me!
First time this happened I had "Plants vs Zombies" running so I figured the phone wasn't fast enough to switch to the incoming call. But it also happens when the phone is idling.
There seems to be no scheme behind all of this. Sometimes it happens twice in a row, sometimes only once a week.
I got my unbranded simlock free Arc in mid April with 2.3.2 and .181 firmware and applied Gingerbreak for root access. Later I upgraded via PC Companion to 2.3.3. and .145 firmware. But I lost root which I didn't like. So I downloaded the Generic World Firmware .181 and flashed it on the phone. Then used Gingerbreak again and made an OTA update to 2.3.3. and .145 firmware. Now I have root and the latest firmware.
All the while I used Titanium Backup to restore all my data, settings and apps as I don't want to reinstall all from scratch because it would take forever.
With this latest firmware, everything is fine, except for the call problem!
Please help me, what can I do?? I don't want to reflash and upgrade or whatever or lose all my data. I just want my phone to be able to handle calls as it should be!!
P.S.: I used Antek App Manager and frooze (not deleted!) some apps which where uncessesary and running in the background or at startup which speed up my startup time and free ram quite a bit. But I didn't frooze any crucial apps, at least I hope. Only stuff like Chinese keyboard and Let's Golf etc.
Also, if I would have frozen the call handling app or something, I wouldn't be able to accept calls in most cases, wouldn't I?
P.S.: I used Antek App Manager and frooze (not deleted!) some apps which where uncessesary and running in the background or at startup
Click to expand...
Click to collapse
Think you may have answered your own question here...
could be, but on the other hand I only frooze really stupid apps which should not affect any important functions of the phone. Also, if I frooze something important related to calls, why is it working most of the time? This is what I don't get.
Here is what I frooze (most of them just took up space in the app drawer and I don't use them), maybe it helps:
- stock browser (I use Opera)
- chinese keyboard (I'm german and don't need it)
- "Downloads"
- retaildemo
- live ware manager
- fb mediadiscovery
- dlna server
- news and weather
- postcard
- SE setup wizard
- sim toolkit
- sony ericsson sync service
- playnow
- sony ericsson support
- track id
- twitter
- let's golf
- google talk
- sony ericsson sync client wizard
so is your problem solved?
Anything related to google should be left alone news and weather should be fine to freeze or delete but would leave Talk alone, and depending what data from which FW was backed up, might also be an issue.
so I defrosted Google Talk. Anything else I should defrost?
Under "Settings" and then "Running services" I sometimes stop "Timescape Legacy Plugin" or whatever it's called because it takes up RAM. Could this also be a cause but I believe it's only for the Timescape app which I seldom use.
drsoran2 said:
Hello everybody,
Everything is fine with my Arc, except for the huge problem that sometimes I simply can't answer an incoming call! It happens like this: When a call is incoming, the phone starts ringing and vibrating as it usually does. However, the screen that is supposed to come up which shows you who is calling and where you can select to accept or reject the call is simply not showing up.
Has anybody experienced this before?
Click to expand...
Click to collapse
I have the exact same problem.
It doesn't happen often but it's really annoying either way.
I barely installed anything off the market and I don't use any sort of app killers/managers.
that's strange because I thought it could be my own fault because I played around and frooze same apps. But it's "good" to know that I'm not the only one.
Do you have any hints about when it happens or when not? Can you exclude anything?
Today, I re-enabled all the froozen apps and then frooze some of them again, according to the thread here on xda. But only apps about which I was really sure.
Don't know how I could test if the error is gone. I mean, have people calling me 100 times and hope it occurs or not doesn't really sound great.
may be there is some problem in your firmware,try some other firmware of other region.................
drsoran2 said:
that's strange because I thought it could be my own fault because I played around and frooze same apps. But it's "good" to know that I'm not the only one.
Do you have any hints about when it happens or when not? Can you exclude anything?
Click to expand...
Click to collapse
That's the weirdest part, the only thing I used that day was Whatsapp.
The incident happened about 5 hours later, I was in a car when my phone started ringing.
I tried picking it up but.. I guess you know the rest..
I was about to buy this phone but now I'm having second thoughts.
@flamez
yesterday it happened to me again. The weird thing is, that my girlfriend said she called me three times but I heard it ringing four times! She claims she didn't call me between her second and her third call! But it definetly rang but I couldn't answer it. Also my other friends say that they didn't call me at this time. Could be someone calling who I don't know at the exact time but the chance is slim I guess.
Also whenever there is such a phantom call, there's not even a hint of it inside the missing calls log. And when this happens, nobody ever leaves a message on my mailbox. Is this the same for you? Could be the person is just lazy but I don't know.
Furthermore, it happened several times to me already and never once a person asked me later why I didn't get their call. Strange, isn't it. It almost seems like that there was no one calling at all!
Now, could it be for some unknown reason that our phones just start ringing as if there is a call but in fact there isn't one at all?! You know, the phone just running crazy and triggering the ringtone? That could be the reason why the "accept call screen" doesn't show up and there's no call log because there is now call!
I know, sounds very weird. But think about it. They could be really "ghost calls".
briggs007 said:
I was about to buy this phone but now I'm having second thoughts.
Click to expand...
Click to collapse
Well, I can tell you that this a great phone and it seems me and drsoran2 are the only ones with this problem..
Guess we just had some bad luck..
drsoran2 said:
@flamez
yesterday it happened to me again. The weird thing is, that my girlfriend said she called me three times but I heard it ringing four times! She claims she didn't call me between her second and her third call! But it definetly rang but I couldn't answer it. Also my other friends say that they didn't call me at this time. Could be someone calling who I don't know at the exact time but the chance is slim I guess.
Also whenever there is such a phantom call, there's not even a hint of it inside the missing calls log. And when this happens, nobody ever leaves a message on my mailbox. Is this the same for you? Could be the person is just lazy but I don't know.
Furthermore, it happened several times to me already and never once a person asked me later why I didn't get their call. Strange, isn't it. It almost seems like that there was no one calling at all!
Now, could it be for some unknown reason that our phones just start ringing as if there is a call but in fact there isn't one at all?! You know, the phone just running crazy and triggering the ringtone? That could be the reason why the "accept call screen" doesn't show up and there's no call log because there is now call!
I know, sounds very weird. But think about it. They could be really "ghost calls".
Click to expand...
Click to collapse
No, I don't think that's it..
It's happened only twice to me over a 2-3 month period and my friends have always called me back asking why I never pick up the phone.
It really just happens about once a month to me, and I can answer the second time they call me right away without any problem.
Are you guys running task killers?
{EDIT - I remember OP saying that he'd frozen a load of stuff.. Suggest that if you're getting this a lot that you un freeze all of it and see how it goes, maybe just freeze the end user apps - like Lets Golf HD at first then build up the frozen apps slowly until you get the problem..}
im_iceman said:
Are you guys running task killers?
{EDIT - I remember OP saying that he'd frozen a load of stuff.. Suggest that if you're getting this a lot that you un freeze all of it and see how it goes, maybe just freeze the end user apps - like Lets Golf HD at first then build up the frozen apps slowly until you get the problem..}
Click to expand...
Click to collapse
No, as I said before, I'm not using any sort of task killers/app managers.
Today first time i encountered same problem. I have WhatsApp running in background. No task killer, nothing else.
Though i donno how to solve this problem. But i can surely tell how to pick up call in this case.
Just press the power key, this will take phone in locked state, but the call wont be rejected.
now click the home key and you will see the answer key, now slide it, it will slide without problem
it's good news that you found a workaround! I'll try to remember it the next time it happens.
Today, I had the problem again but this time it was different. The slider or the contact picture of the person calling didn't appear, but I could see the number of the person who is calling in the notification bar (not the name, just the number although this number and contact is stored in my contacts).
This happened the first time, all the other times the phone just rang without any hint of who is calling.
It would be nice if we were able to pinpoint a certain event which causes this odd behavior but so far I had no luck. What I'm doing differently since the last time it happened is, that I don't use task killers anymore. But still, it happened again today.
It's difficult to find out what it is when you don't know what causes it and when it will happen. For example, it happened to me today once for the first time in about a week.
in recent days, "it" happened very often to me!
Sometimes, the phone manages to at least show the number of the person calling so that I can call back. But usually it doesn't! The call just disappears into nirvana.
Do you guys remember if the error is associated with a certain amount of RAM left available? In other words, if the available RAM at the time of the incoming call is below a certain limit (which I don't know) the phone can't display the call. When it happened to me today, I had only 90MB RAM left. Maybe the phone can't free up enough RAM fast enough?!
Also the trick, which somebody mentioned a few posts above me, that when it happens you press the power button and then home and then you can slide and accept the call very rarely works!
I'm desperate and don't know what to do about it. I have just finished adjusting my phone to my needs. I linked apps with Link2SD and now have over 100 apps installed and still 215MB left on the internal memory, I have root and the .145 firmware. Everything is fine, except for this error!! It would take ages to restore it to the point where it is now, if it is complety possible at all.
I mean, if a phone can't handle calls, what good is it for?
I had a NEC e616 years ago which frooze while sending SMS or crashed after connecting a call or during a call and other "funny" things, but this was well known for this model.
But we don't have 2004 anymore and I except the Arc to work.
I could send it in on warranty, possibly. But then everything would be erased and it would take forever to get it repaired.
And I'm afraid they are going to tell me that they couldn't reproduce the error (because it happens so randomly)!
Such a nice and beautiful phone if not for this stupid error!
I'm already tempted to get rid of the phone and look for something else. But who's going to buy a phone with a bug which can't display phone calls?!!
I mean, I could reset it and flash the fimware and stuff and then hope. Maybe the error is gone. Maybe it persists and then all my data is gone and I have to start from scratch.
Or it is gone and then I have to start from scratch also!
If I should be forced to do it all over again and have all the work, then I could do it on another phone as well.
The Samsung Galaxy SII is quite ugly, to wide and big but I hope it can at least handle a call?!
Thank you for any help!!
Hmm..
If it happens rarely.. Why don't you sell it off on ebay
If asked about other mobile. I prefer sensation to sgs2. Much better phone function. In fact IMO htc is better than all other androids when it comes to phone functions.
Sent from my LT15i using XDA Premium App

[Q] Incoming call - screen disappears to wallpaper

I have gotten a major problem the latest weeks. When I get an incoming call sometimes, the screen flashes to and from the "incoming call screen" (you know with the answer button) to the wallpaper. Which means I can't answer that call. Also, if I poke around too much while I have this problem on a call, the phone just reboots.
However, I may have a suspect. I am running faux007u. I am not whining here, just wondering if that may be the cause? If so I'll just try his m version or go back to stock
The reason for me writing this instead of just re-flashing the kernel an await the problem is because it would be nice to know if anyone else have had this problem.

Difficulty answering calls

Is anyone else having a problem answering calls? On an incoming call, I can hit the green button over and over, yet it won't answer. Sometimes, I can get to the full dialer screen where I can swipe down to answer, but in my panic to answer, can't seem to get to it every time.
I've also noticed that oftentimes, pressing a contact to dial them will take up to 30 seconds or so. Just as with an incoming call, I can press it over and over, to no effect... then all of the sudden, it will start dialing.
My first sim is TMO, and the second is AT&T. I am still on 5.0.3 and have been ignoring the 5.0.4 update, since I'm worried about losing TWRP and magisk and don't feel like farting around with it right now. If I knew it would fix the problem, I might be a little more motivated to do so, but it only seems to fix an incoming call sound issue (not quite the same as what I'm experiencing... but maybe related?).
I went ahead and updated to 5.0.4, hoping it would help, but it didn't. I've noticed that if I press power to turn off the screen/mute the ringer, then turn it back on, I can get to the full dialer screen and accept/reject the call. Also, this freeze is easy to reproduce from the dialer log. If I browse for a sent/received call from earlier in the day and tap that, it won't bring up the sim card choice (TMO or ATT) until after 30 seconds or so.
If anyone has seen this issue, please chime in. I'm at my wit's end.
I have some issues with incoming calls. Sometimes it vibrates but doesn't show any incoming call only when I have missed it afterwards. I don't know what causes this behaviour and if it is related to your issue. I'll switch from OxygenOS 5.0.4 to LineageOS 15.1 soon so I didn't look into that and I'm not going to
I'm not sure, but it definitely seems to have something to do with the dialer itself. My guess is because I'm using two sims. When dialing a call, it's almost as if the box to select a sim to dial pops up behind the dialer....
Try wiping dialer cache then reboot, go to recovery and wipe cache/dalvik and see if it helps. btw, I find no difficulty in answering phone call.
lemonade747 said:
Try wiping dialer cache then reboot, go to recovery and wipe cache/dalvik and see if it helps. btw, I find no difficulty in answering phone call.
Click to expand...
Click to collapse
Pretty sure I tried that, but not since the latest update. I'll give it another shot!

anybody having issues with wifi and mobile data (T-Mobile)

I'm getting tired of it, wifi disconnects and reconnects or flat out doesn't work, mobile data flat out doesn't work most times unless I reboot the phone for either of them to work. I'm rebooting about 4-5 times a day just to get either working. I'm at my wit's end and about to get rid of this thing as soon as I can.
I generally love this phone, but I'm seeing similar issues. WiFi says connected, but I don't get any data. I thought it was my network at first, but noticed other devices working. Tested network while my phone was acting like this, and my WiFi and network were working great.
Separately, my phone sometimes won't dial out. I use Google Voice, so I'm not sure if it's the phone or Google that's not working, but it's very frustrating. The dial screen comes up, then immediately disappears. No errors or anything to indicate that it ran into problems. The dial screen just flashes. Rebooting seems to fix that. But all very frustrating. Especially when I'm trying to call someone while driving. I don't want to have to look at the screen. I want to be able to tell the phone to call and know it's going to do it. Instead, I tell it to call, it confirms it will call, then nothing.
chris.arney said:
I generally love this phone, but I'm seeing similar issues. WiFi says connected, but I don't get any data. I thought it was my network at first, but noticed other devices working. Tested network while my phone was acting like this, and my WiFi and network were working great.
Separately, my phone sometimes won't dial out. I use Google Voice, so I'm not sure if it's the phone or Google that's not working, but it's very frustrating. The dial screen comes up, then immediately disappears. No errors or anything to indicate that it ran into problems. The dial screen just flashes. Rebooting seems to fix that. But all very frustrating. Especially when I'm trying to call someone while driving. I don't want to have to look at the screen. I want to be able to tell the phone to call and know it's going to do it. Instead, I tell it to call, it confirms it will call, then nothing.
Click to expand...
Click to collapse
I'm getting the same problems and it's annoying the hell out of me I'm paying this phone off but I'm about to just ditch it buy a pocofone and just pay im this off separately or try to trade it in for a one plus 6T

Call transfer problem

Greetings!
I'm wondering if anyone has the same problem as me, and maybe someone already has a solution for it.
When there is an incoming call, my phone rings and my watch too. I take up the phone and slide to answer the call, the phone stops to ring but the watch continous to buzz, and the phone won't take the call just hangs there and shows there is a call , 5-10 seconds after I pressed the anwser on the phone, THAN it picks it up, and now I can talk.
If I slide to answer on the watch it transfers to it.
I don't why it does this...
I have an LTE version, with the same phone number as in my phone ( I have a Note 9).
sortilego said:
Greetings!
I'm wondering if anyone has the same problem as me, and maybe someone already has a solution for it.
When there is an incoming call, my phone rings and my watch too. I take up the phone and slide to answer the call, the phone stops to ring but the watch continous to buzz, and the phone won't take the call just hangs there and shows there is a call , 5-10 seconds after I pressed the anwser on the phone, THAN it picks it up, and now I can talk.
If I slide to answer on the watch it transfers to it.
I don't why it does this...
I have an LTE version, with the same phone number as in my phone ( I have a Note 9).
Click to expand...
Click to collapse
I have the same problem and I only have the 42mm BT model. It's annoying
cwb1231 said:
I have the same problem and I only have the 42mm BT model. It's annoying
Click to expand...
Click to collapse
And do you have a clue of why it does it? Or have you considered to send in to repair?
sortilego said:
And do you have a clue of why it does it? Or have you considered to send in to repair?
Click to expand...
Click to collapse
I am very careful to not answer on my watch and hope the call goes though! I have turned phone off and watch off and that seems to clear it for a bit
sortilego said:
Greetings!
I'm wondering if anyone has the same problem as me, and maybe someone already has a solution for it.
When there is an incoming call, my phone rings and my watch too. I take up the phone and slide to answer the call, the phone stops to ring but the watch continous to buzz, and the phone won't take the call just hangs there and shows there is a call , 5-10 seconds after I pressed the anwser on the phone, THAN it picks it up, and now I can talk.
If I slide to answer on the watch it transfers to it.
I don't why it does this...
I have an LTE version, with the same phone number as in my phone ( I have a Note 9).
Click to expand...
Click to collapse
carrier issue id say.
do you remember if your carrier assigned a dummy phone number to your watch? because the watch can receive and make calls with the same number that ure phone has but its basicaly like a call forward. from the description of your problem, it would seem the carried might have activated the esim and put the phone's actual number instead of an other number. When i consult my online profile from my provider and see my plan and data usage, the phone has the original phone number as supposed and the watch has a random phone number that is just a dummy one and isint really usable.

Categories

Resources