Android Forums at AndroidCentral.com >  HTC Android Phones >  T-Mobile HTC Amaze 4G > Wi-Fi Calling Issue

Wi-Fi Calling Issue

    Thread Author   #1  
Old 01-25-2012, 03:42 PM
 
Posts: 95
Join Date: Feb 2010
Thanked 3 Times in 2 Posts
Likes Received: 3
Activity: 5/20
Starting last night I have been experiencing issues with Wi-Fi calling. Prior to that I have not had any issues with Wi-Fi calling... I have had the Amaze about a week. What is happening now is that I am getting an error message that states "ER01 -Invalid Certificate" and I get the red Wi-Fi calling icon in my notifications drawer.

Any idea what the "Invalid Certificate" means and how can I correct it? Or, is this a T-Mobile network issue? Thanks in advance for any help.....

Additional: I just called T-Mobile and the first tier of CS said that their are no ER01 error messages listed as known issues with the Amaze. So I am calling back to get pushed to a higher level of Tech Support.

Last edited by wezra; 01-25-2012 at 05:24 PM.
  #2  
Old 03-03-2012, 11:44 AM
Member
 
Posts: 1
Join Date: Mar 2012
Thanked 0 Times in 0 Posts
Likes Received: 0
Activity: 0/20
I started having wifi issues suddenly on my Amaze 4G as well. About a week ago, I hv the blue wifi icon at the top left. BUT when I try to make a wifi call, it simply switches to wifi and about 1 second later, just goes back to the dial pad. No errors whatsoever. In the previous 30 days I had the phone, I had no issues like this. It's a intermittent issue ... does not happen all the time. But once it gets into that mode, only a restart will cure the problem temporarily.
    Thread Author   #3  
Old 03-04-2012, 10:05 AM
 
Posts: 95
Join Date: Feb 2010
Thanked 3 Times in 2 Posts
Likes Received: 3
Activity: 5/20
Wi-Fi calling isn't the best on T-Mobile. I have the Wi-Fi Booster in the house so the signal is strong in every part of the house, yet when on Wi-Fi calling I keep getting a "beep" and a message on the screen that says I am about to drop the call because I am out of range of the signal. I have a feeling this a software issue. Hopefully, when we ICS, this will clear up.