invalid teleservice id and other issues

[d0x360]

When sending a text message using Google's texting app on my note 9 running Android 9 I often get the invalid teleservice error and there is also another error I get but I can't remember as it's more rare.  Regardless if results in the text failing to send.

The only way to fix it is to enter airplane mode then exit it or reboot.

I also have call issues... I'll have full 4g service (and I've never had this issue before the note 9 and more specifically the Android 9 update).  I'll be talking to someone and I can hear them crystal clear but they can't hear me.  This happens a few min into a call and seems random.  I never lose service according to the phone and I can immediately redial or receive a call again after I manually end the call where the person can't hear me.

Since I have multiple issues and they are all service related (calls, text, data) and the only fix which is temporary is a reboot I think there is something wrong with my phone's antennas.

I'd like to get this fixed considering how expensive the phone is and it should still be under it's year warranty since I bought it in Nov 2018.

If I bring the phone to a Verizon store they chances of them being able to replicate the issue are likely small unless I stay there for a couple hours or more.

If the issue is replicated what will happen?  Will I get a refurbished phone someone else had on the spot or will my phone be fixed?  I'd prefer my own phone back obviously, especially since it's in perfect condition and the last time I got a refurbished phone from a warranty issue it was all scratched up and dirty.

Thanks in advance.

[Kfelt]

Having this issue with my Note8 also, texts stop working out of the blue with no warning, then I have to shut off wifi or restart phone to try and send a message, and all my failed messages from the day come flooding in.

At first I thought this was a problem with the messaging app but have tried, Messages, Messages+ and now Google messages.  Same problem on all apps.

Updates have not improved this, Ionly started getting this error message from the google app, all other apps would just say "failed to send".  Has there been a real solution found for this?  We shouldn't be expected to restart our phones every 5 minutes to see if we have any text messages that aren't coming through.

[vzw_customer_support]

Oh no, sorry to hear that you are experiencing this issue with your Note 8, Kfelt. Texting messaging without issue is vital these days and we are on the case. Can you share the exact error message you got when getting the "teleservice" message? I do understand that other texting apps simply say "failed to send". Have you tried restarting the impacted apps? Here's how: http://spr.ly/6600EIZ4k 

RyanM_VZW

[camadella]

I have this same issue and have tried everything.  I am very phone knowledgeable - I write apps for a living.

I think this is the service - very frustrated...

[Shadowblade4]

Same exact issue and I also have a note 9. I should also mention that optimization of your phone (using Device Care) will fix it as well. 

[Shadowblade4]

One of these days, someone is going to miss an important call because of this!

[Aahenp]

My husband and I have the same issue but we have the Galaxy 8 plus.  So it isnt just the note. We are tired if missing IMPORTANT CALLS.  People act like we dont know how to operate our phones.  We have had phones from Verizon and samsung for years. We are android people and sick of issues with text and calls bot coming in. I will be sitting next to my husband and call his cell and it won't ring on his end but I can hear it ring on my phone. Its clearly a mess since the update. We clearly are figuring our next move.  No one will do anything and frankly we are tired of poor service.  

[phainlen]

I recently accepted the whole Wi-Fi calling push as well thinking "i've got nothing to lose! what a great idea!"  What I didn't know is that I would be spending the next two days trying to undo my changes and scouring the internet and blog posts for anything that would help me fix or revert back to non-Wi-Fi calling... No luck...

So, I went on a personal mission to figure it out.  I think I may have figured it out, but I'm still testing.  Bear with me while I lay the stage out... about a month ago I enabled RCS messaging through a widely distributed "hack" to google messages:
https://ww.9to5google.com/2019/10/26/enable-rcs-android-messages/
This required the download of a utility called the "Activity Launcher" and making some changes to some server settings to bypass carrier restrictions on RCS messages.
Well low-and-behold on the same day that Google announced the rollout of RCS for those who were early adopters (ie those who hacked their settings), it was the same day that the Wi-fi calling feature was rolled out too.  Coincidence?
https://ww.9to5google.com/2019/11/14/psa-manually-enabled-rcs-migrate/

Even though the article says your settings will automatically change for RCS, mine didn't.  So, instead of trying to figure out how to disable Wi-Fi calling, I decided to revert my changes made back in October for RCS and I deleted the sandbox server.  If you use the "Activity Launcher" to check the settings before you change the RCS server back, look at Advanced Calling and Wi-fi Calling. There are very few line items in these settings.  the Wi-Fi calling was only populated with one line for me which was for AT&T (att).  Hmmmm, could this be why it wasn't working?

After deleting the RCS sandbox server and a little bit of time (or syncing), if you check out the Advanced Calling and Wi-Fi calling, they are now fully populated with many different carriers and settings... and for me, this seemed to have solved the "invalid teleservice ID" error.

Check it out and report back if this fix works for you.  Again, I'm not sure if this is the reason or not, but it is all too coincidental for me to not have something to do with the error message.

[Hershel1]

Switching in/out airplane mode helps!!