How to swap or end just one call while another call is on hold?

I have seen a very desirable user experience with this either. I have an Andoid phone with Verizon, and have experienced the following:
Initiate call
receive second call and begin conversation
press hang up to get back to first conversation

hang up disconnects both callers, but then sometimes I'll get a ring from the first caller. I assumed it was them calling back after a disconnect, but based on an article it appears it is Verizon reconnecting me to the first caller:

How to Handle Multiple Calls at Once on an Android Phone - For Dummies

Hope this helps someone.
 
I believe you are not getting the option to swap over to the other caller is because you are initiating the second call so it should only give you the option to merge but if someone calls you while you are already on a call it should allow you to swap over. As far as the issue goes with trying to hang up just one call and stay connected to the other line is a CDMA issue and the only way to do that is to ask the other person to hang up and then it will automatically connect you to the other person and it will still display both numbers on your screen but you will only be on the line with one person and it will still allow you to receive other incoming calls.

I also am encountering this issue. There is no option on the screen to reinstate the last call. It says (in the upper right hand corner of the screen, "on hold" and I've tried every thing I possibly could to resume the first call, but the only option is to hang up and call back.
 
So lets say I am on a call, and another call comes in and I take that. Or I initiate a new call while first call is still going on. What it does is that it puts the first call on hold. How do I swap back and forth between calls at this point? I saw a merge button on call screen, but no swap button.

Also, if I want to end one of these two calls, and I press the end key, it hangs up both calls. How do I hang up just one call?

So it is 2017...and this problem is still here...smh... i had a galaxy s7 with at&t and never experienced this problem. I am now with sprint and this is new and frustrating for me.... I can only swap calls..no option to merge at all and cannot disconnect either call without hanging up on everyone. For crying out loud
 
Last edited by a moderator:
I created an account just so that I could say that, 7 years later, in 2018, this is still a problem. I found this thread by googling how to disconnect from an active call while one is on hold because I am so frustrated with this issue. This is such an asinine problem to be having. Especially with new smart phones being released every year.
 
I too just created an account just to say, today marks the day before the last day of 2018 and yet this is still an issue!!! Smdh, so much for smartphones in 2019.
 
Like the above two commenters said, I only created this account to chime in on this thread. Can we all get together and write a congressperson about this? It's insane this isn't standard with all phones.
 
"Me Toooo"... (see comments above)
Just got my Galaxy S10, and the bugs start pouring. The worst part is that tech support, both from Sprint as well as Samsung, are the most incompetent people I encountered in a very long time, and totally useless. March 2019 and the Galaxy S10 is incapable of doing what it claims to be able to do. No way to swap between calls in a Multi Party call, and once you merged the calls to a conference call you can only hang up on both. The Samsung manual for my Unlocked version, as well as the one for the Sprint version are describing identical process. Ostensibly, you are supposed to be able to tap on the call that is On-Hold in order to switch between the calls, but this function is Frozen = dead, and does not work. The AT&T version (GSM network) does describe a different process - the AT&T S10 has a SWAP button besides the Merge button (while the Unlocked and Sprint phones do not have a SWAP button per the manual). The worst part is that 7 years since the inception of this thread, or whatever number of years it has been... the tech support people don't have a clue whatsoever about this problem...
Amazing... Some on this thread suggested the problem is related to the CDMA network, but I wonder if that's true.