UPDATE
I had come across what I initially thought was a bug that occurs with the phone app when not using Sense UI as the default home launcher. It even occurs when using the stock Android launcher.
As it turns out, the behavior of the Phone button on the Sense UI launcher is significantly different than that of the Phone app button found in the app drawer.
The Sense UI Phone button returns a user to an existing call, while the Phone app button starts the Phone app in a mode that allows the user to add a call (as in a 3 way or conference call).
If you are using any alternative launcher (including the stock Android launcher), please note that the only way to get back to an existing call is to use the notification bar. You can use the call notification to return to the call or end it.
Personally, I find the default behavior of the stock phone button to be unclear. I would consider it a design flaw in stock Android, but that is my opinion. Apparently, HTC feels the same way since they made the functionality of their Phone button different.
END UPDATE
It's very easy to replicate.
With the stock Android Home Launcher or a 3rd party launcher like LauncherPro or ADW.Launcher set as your default home launcher, make a phone. The call will start normally and you'll see the red End Call button.
Then press the home button and press the phone app button again to go back to the call.
When you get back to the Phone app, you'll see that the app thinks that no call is connected. Your call is still connected, but the green "Call" button is now displayed and there is no way to end the call.
Unless the other party hangs up, you are stuck in the call. The only way I've been able to end the call is to shut off the phone.
Has anyone else using the stock Android launcher, LauncherPro or ADW.Launcher experienced this problem? Can you replicate it?
Has anyone using Home++ or another third party launcher experienced this?
At first, I thought this was a problem with the 3rd party launchers, but if the phone app won't work properly, then it is a major bug on HTC's part.
Please do not post about whether or not you think users should disable Sense. That is not the issue here.
I had come across what I initially thought was a bug that occurs with the phone app when not using Sense UI as the default home launcher. It even occurs when using the stock Android launcher.
As it turns out, the behavior of the Phone button on the Sense UI launcher is significantly different than that of the Phone app button found in the app drawer.
The Sense UI Phone button returns a user to an existing call, while the Phone app button starts the Phone app in a mode that allows the user to add a call (as in a 3 way or conference call).
If you are using any alternative launcher (including the stock Android launcher), please note that the only way to get back to an existing call is to use the notification bar. You can use the call notification to return to the call or end it.
Personally, I find the default behavior of the stock phone button to be unclear. I would consider it a design flaw in stock Android, but that is my opinion. Apparently, HTC feels the same way since they made the functionality of their Phone button different.
END UPDATE
It's very easy to replicate.
With the stock Android Home Launcher or a 3rd party launcher like LauncherPro or ADW.Launcher set as your default home launcher, make a phone. The call will start normally and you'll see the red End Call button.
Then press the home button and press the phone app button again to go back to the call.
When you get back to the Phone app, you'll see that the app thinks that no call is connected. Your call is still connected, but the green "Call" button is now displayed and there is no way to end the call.
Unless the other party hangs up, you are stuck in the call. The only way I've been able to end the call is to shut off the phone.
Has anyone else using the stock Android launcher, LauncherPro or ADW.Launcher experienced this problem? Can you replicate it?
Has anyone using Home++ or another third party launcher experienced this?
At first, I thought this was a problem with the 3rd party launchers, but if the phone app won't work properly, then it is a major bug on HTC's part.
Please do not post about whether or not you think users should disable Sense. That is not the issue here.
Last edited: