Or is it just me?
While on a call, a incoming call renders all audio on both calls dead. Regardless if you answer, ignore or let go to VM, neither person can no longer hear any audio.
I have tried this in many different scenarios. I am using T-Mobile in the NYC area.
If anyone else is experiencing this, please respond.
UPDATE!!!!!
The "Viber" app I installed was the cause of the problem. Once I uninstalled it immediately fixed the problem.
me too.
Hi, I have the exact same problem. It is quite frustrating.
The only work around I have found so far is to go in to call settings -->additional settings and turn off call waiting. Which is also kind of annoying.
Does anyone have a more elegant solution? (like having the incoming call sound a beep instead of taking over my entire call and rendering the phone useless!)
zyoeva said:
Hi, I have the exact same problem. It is quite frustrating.
The only work around I have found so far is to go in to call settings -->additional settings and turn off call waiting. Which is also kind of annoying.
Does anyone have a more elegant solution? (like having the incoming call sound a beep instead of taking over my entire call and rendering the phone useless!)
Click to expand...
Click to collapse
hi
and Asslam o Alykum
here is same problem
i have samsung galaxy i9000 if calling via viber incoming voice is well
But out going voice is no this just for me or this is a problem in the settings,
kindly help me expert
I have a new Samsung Galaxy S6, running 5.1.1. For a week, incoming and outgoing text messages have been registering correctly in the call log. As of today, texts are no longer registering in the call log (but they appear in the message log) and no previous texts are listed. I have spent quite a bit of time looking online for an answer - no luck. I would appreciate any help.
Best and thanks,
ubi100
Go to recovery mode and wipe cache.
roydok said:
Go to recovery mode and wipe cache.
Click to expand...
Click to collapse
Thanks, but that did not work. Any other suggestions?
Try a full reset. Your problem may also be due to a rougue app. I hope this helps.
Nope, still did not work. Still not recording incoming or outgoing text messages in the call log.
Surely a 'call log' is for calls, therefore SMS messages aren't included?
EddyOS said:
Surely a 'call log' is for calls, therefore SMS messages aren't included?
Click to expand...
Click to collapse
I would agree but the oddity is that text messages were included in the call log (the log indicated that the contact was an SMS) for about a week and then they disappeared. I would like to restore that function.
Text not recorded in call log
Hello Ubi100,
I am glad I found this thread. I have owned a GS6 edge for exactly 3 days just because of this problem. I am a "veteran" user of the galaxy s line and the GS6 is the first one that does not show text messages in the call log. My GS6 edge running 5.1.1 did not show at any time sms in call log. I have also installed 3rd party apps for call log and it did not help. The GS4 and GS5 running Lolipop have no issue with this and they show text messages in call log , so I don't think that the software version is the problem. So please tell me that you found a way to fix this issue.
Thanks
Forum_user said:
Hello Ubi100,
I am glad I found this thread. I have owned a GS6 edge for exactly 3 days just because of this problem. I am a "veteran" user of the galaxy s line and the GS6 is the first one that does not show text messages in the call log. My GS6 edge running 5.1.1 did not show at any time sms in call log. I have also installed 3rd party apps for call log and it did not help. The GS4 and GS5 running Lolipop have no issue with this and they show text messages in call log , so I don't think that the software version is the problem. So please tell me that you found a way to fix this issue.
Thanks
Click to expand...
Click to collapse
Hi Forum_user,
Alas to no avail. I have spent a great deal of time online looking for the solution to this problem. I have never found anyone who has a direct answer to this exact situation. I have followed everyone's general suggestions but still no luck. No record of text messages in the call log.
The only thing that I can guess is that my phone was delivered with Lollipop 5.0.2 on it. With that version, the text messages showed in the call log. When I upgraded to Lollipop 5.1.1, the text messages disappeared from the log.
I would appreciate it if you could let me know if you find anything else out.
Thanks,
ubi100
Same problem. I think it is extremely convenient to hva both the cal and the SMS log in one list. I often answer calls with a SMS and vice versa. With a combined list as it was before I had god control whom I answered and whom not. If somebody has a solution to the problem I would be thankful.
Did anybody ever find a way to fix this? I'm dealing with the same thing on my gs6. It showed for about a week in the call log and now it doesn't. And I can't find anything online about what to do.
Yes. I too am a long time user of the galaxy series. Until the s5 the call log and message log was unified. Which does not seem to the case in s7. The new scheme is not convenient and is a feature downgrade in my view.
It's exactly the same on the S7, A royal pain & a massive step in the WRONG direction, even if they add it back in as 'activity log'
I use my S7 and miss the combined message/call log alot I stumbled in here seeking a solution. Hopefully a future upgrade will bring it back!
Hey guys!
I’m using Samsung SM-G920FD already 2 years abt. running updated Android 7.0.
Got a following problem, Whenever I’m intended to make an outgoing call trying to call a friend of mine, my phone refuses to do so. It starts the process of call but freeze on stage of dialing picture mode and no beep tone or nothing is going on afterwards, as If I or the subscriber is offline. Although, the network signal level is at high and no any indications of malfunctions by phone are being shown.
Thus, the only fix solution I found I immediately restart my phone and only then can make/receive calls.
What could be the reason of such behavior and how to fix this annoying problem.
Thanking in you advance and looking forward to hear your solutions soonest.
Regards,
kozav100
Hi all,
I'm using stock rom.
And in the last days I can't call or receive a call anymore. No tone.
Messages are working well. I receive the message that someone tried to call me. I can listen to the voice message
Internet in 4G is working well.
I think it happens since my last upgrade mid July. At the beginning it was sporadic. Sometimes to time. Now it is always.
My operator (Orange) changed my SIM but it does not resolve anything.
I wanted to install previous stock, but I read it is now impossible.
Any advice would be highly appreciated.
Thanks in advance for your kind help
--kripskroll
I have an unlocked originally-T-mobile OP9, with Android 11, and I have an issue with Google Fi that I couldn't find online references to.
Every so often, I can't make calls: the dialer starts to dial and then stops within a fraction of a second. A reboot always solves the problem, but then the problem comes back eventually. Data works fine.
Update: I can't receive calls in this state either.
I tried using the beta Google Phone dialer, and maybe even some third-party dialer, and the issue is the same.
killing the com.android.server.telecom:ui task solved the problem without a reboot, and now I have a Tasker shortcut to do that on my home page, but that's not really a viable solution given that incoming calls don't work when the issue happens.
Does someone maybe have a version of Telecom.apk from a different firmware that I could try?
A bit more experimentation: When the phone is in the bad no incoming/outgoing calls state, if I turn off mobile data, or switch it to 2G, everything works again. Then when I switch back to 5G, calls don't work (but data works). Is it a VoLTE issue?
Bump... Am I really the only person on XDA using a TMO OnePlus 9 on Google Fi? Is anybody using an international OnePlus 9 at least? I might want to change to international firmware then.
Well, I think I've solved it by installing international firmware. My guess is that the problem had to do with VoLTE support in the T-Mobile firmware.