Related
Have an HD7 and now upgraded to mango. Trying to get the Visual Voicemail to work.
Have called T-mobile and they have enabled the feature. I got the text message that a change to my account has been made.
When I turn on Visual Voicemail in PHONE SETTING; I get the following error: OOPS!, Something happened and we couldn't set up your visual voicemail.
I have tried turning off wifi.
So; have anyone found a fit to this. Seems like many are not getting it to work and some are.
I am on the family plan with data/text/voice
Wish that Microsoft and T-Mobile had done a better job of testing in beta.
Any help/ideas would be appreciated.
just waite till your next billing cycle?
Ylinen said:
Have an HD7 and now upgraded to mango. Trying to get the Visual Voicemail to work.
Have called T-mobile and they have enabled the feature. I got the text message that a change to my account has been made.
When I turn on Visual Voicemail in PHONE SETTING; I get the following error: OOPS!, Something happened and we couldn't set up your visual voicemail.
I have tried turning off wifi.
So; have anyone found a fit to this. Seems like many are not getting it to work and some are.
I am on the family plan with data/text/voice
Wish that Microsoft and T-Mobile had done a better job of testing in beta.
Any help/ideas would be appreciated.
Click to expand...
Click to collapse
Chances are that there is no problem and that the changes made to your t-mobile account have not taken effect yet. A month ago I had the same issue. So I went to t-mobile.com and change my services to enable visual voice mail. After making the change it said that the new features would be enabled the next billing cycle. I then received an email stating that I or somebody authorized had made changes to my t-mobile account. When the new billing cycle kicked in, I received another message stating that the changes that I made were going into effect. (more or less) I was then able to use visual voicemail.
same here on a 32gb HD7 with a even more plus plan.
This is an issue for me as well. It was working on the beta but stopped when I added voice to text. I cancelled that feature in hopes that vvm would start working again but no luck. I was told to wait two hours a month ago! I just spent 45 minutes on the phone with T-MO and they told me to wait another couple hours. If that does not work than they will open a support ticket. Whatever that means. I will report back. Oh, and were not alone. http://support.t-mobile.com/message/37538
I just got a support ticket opened. well see what happens.
Here is my visual voice mail Story
So my story on visual voice mail goes like this: I was running mango beta and I had visual voice mail working just fine. I was on a old unlimited plan. I changed plans to the new 2 line unlimited plan and my visual voice mail quite working. I have spoke with the tech support line over 5 times. I have had my voice mail box removed and replaced at least five times. Still to no avail. My visual voice mail no longer works. Tech support tells me its on their end. There is no reason why it did work on beta and doesn't work on full release. In fact I had one rep pawn me off to Microsoft before the full release because she said the beta version wasn't supported by Tmobile. I have two full blown tickets in with engineering now and will post if I get anything resolved. The best people I have found so far work out of the New Mexico facility. I should have more answers by Friday.
Is your 3G data on?
Currently I'm using my T-Mobile HD7 without data.
Visual voicemail is no go.
But when I turn on 3G it works fine. (I enable Visual Voicemail as a service myself on the site.)
I haven't been charged for data yet, but I rarely use it.
Yep. 3G data with full bars of service.
Got off the phone with T-Mobile about an hour ago. Now have an open ticket over at engineering. Like you guys I'll be waiting to see what happens.
Opened my ticket as well... Fingers crossed for a quick resolution
I have the same issue.
I had Beta 2 of Mango from when it leaked until about a month after the leak, at which point I rolled back to NoDo. At that time, VVM worked perfectly. I never disabled VVM on my T-Mobile account.
Now I can't get it to work at all. I've called T-Mobile support countless times, and all they ever seem to be able to do is reset the VVM on my account.
If you guys figure out what's up, it will hopefully benefit me.
Update
Well, Spent another hour on the phone today with them and now they say there is a problem with mango. (I don't really understand how that could be because it worked fine on mango beta and wasn't until I changed my plan that I had a problem. But whatever!) I would recommend to anyone that is getting an error when trying to set up visual voicemail that you call tmobile, get to tech support and file a ticket with engineering. The more they hear it the more likely it will get to the top of the pile to be fixed. At this point I am waiting to hear back from them. My ticket started on Sep 16th.
T-Mobile is aware of the problem. I just called and they mentioned that there was a service ticket out on it.
I had activated Visual Voicemail when I had the leaked RTM. It's still working, but watch when you guys actually get it to work. The audio actually comes out of the loud speaker on the back no matter what you do..... Fun stuff.
A person provided this solution to my question on T-Mobile support. It worked for me.
try texting "Activate:dt=6" to 122 without the quotes. should say you have a voice mail and should work (make sure you have the VM soc added to you plan first)
Ylinen said:
A person provided this solution to my question on T-Mobile support. It worked for me.
try texting "Activate:dt=6" to 122 without the quotes. should say you have a voice mail and should work (make sure you have the VM soc added to you plan first)
Click to expand...
Click to collapse
Also saw this on the T-Mobile support site and it does indeed work. Question though. I'm now getting a flashing green indicator light when i have a missed call and/or voicemail. Was that always there?
Ylinen said:
A person provided this solution to my question on T-Mobile support. It worked for me.
try texting "Activate:dt=6" to 122 without the quotes. should say you have a voice mail and should work (make sure you have the VM soc added to you plan first)
Click to expand...
Click to collapse
This did work! Nice Find!
I agree that the "Activate:dt=6" trick does enable Visual Voicemail in the Phone Tile. However, with 2 bars of 2G it tells me "Can't connect to visual voicemail" [server]. Can anyone confirm they actually get visual voicemail to download with the trick?
EDIT: After leaving myself a voicemail I finally got it to download. Now I'm experiencing the same problem others have with the audio ONLY playing through the loud speaker. Does anyone have a fix for this yet?
working fine for me, but I took some extra steps since the VVM was turned on on the handset without the service being provisioned via the "my account" page. It appears that Mango enables VVM on the handset by default.
(fyi, I was in a solid 3g service area when I did this, your results may vary).
1. Disable VVM in phone settings on the handset, restart phone.
2. Enable VVM on your account page
(waited about an hour)
3. Enable VVM in phone settings on the handset, restart phone.
(waited about 15 minutes)
4. Called and left myself a VM and it showed up delivered via VVM
TLDR: Changed my phone number and now my phone (Samsung Ativ S Neo on Sprint) is not getting any kind of voicemail notifications (toast/phone tile/VVM tile/VM button in phone app/VVM app). The visual voicemail app, even after a hard reset of the device, is still listing the _old_ number under its settings page. The full details are here: community.sprint.com/baw/message/629851
How is it possible that the old number is still showing up after a hard reset when all of the provisioning steps and MSID are all programmed correctly?
Is there some registry setting somewhere that isn’t being updated after a hard reset?
Is there any way to do and even lower level reset of the device that will take it back to a pre-activated/provisioned state? If so, how do I do this?
I spent the last two hours on the phone with Sprint and they went through all of the steps they could think of, even down to changing the MSID on the phone, and they were unable to fix the problem. Any help would be greatly appreciated.
Rather ugly for a solution, but you could try using the Samsung registry editor (look for "interop unlock" on the dev&hacking forum). I forget the exact registry path of the voicemail settings but it can be found... somewhere. My native webserver app would let you browse to find it.
Also, at least on my phone, I can go to Phone -> Voicemail -> AppBar -> Settings and uncheck "Use default voicemail number", then put in a new one... not sure if that's the problem you're having or not, though.
Problem is that this is the ATIV S Neo on Sprint and therefore the visual voicemail is a separate app of theirs and not tied directly to the Phone app. The setting for the default voicemail number is in a slightly different place within the Phone app on Sprint since VVM is not integrated, but it shows the correct number there. The incorrect number is shown in the VVM app which if I'm not mistaken is intercepting the messages from the network and incorrectly processing them because it thinks it is receiving voicemails for a different phone.
I haven't tried the interop unlock yet because I'm not sure if this phone is going to have to get sent back to Sprint or not and I don't want to take a chance in having issues with support because of the change.
The main thing I want to figure out is how to do a lower level reset of the device than what Settings->About->Reset does.
interop-unlock is completely reversible, but I understand your concern. In any case, without looking at the app in question pretty closely (and chance you could post the XAP?) I doubt I'll be able to help you. Sorry.
I went through interop unlock and also have the webserver running. Just trying to figure out how to dump the XAP for the VVM app.
This is specific to Sprint as far as I understand...
Cool, thanks! I'll take a look. Can't promise I'll be quick about it - got a root-unlock to perfect, here - but I'll look into it.
The Issue with the Voicemail is NOT Windows OS. The Issue with the Voicemail is NOT HTC or SAMSUNG.
I had Called Sprint and was told to Call Samsung and Microsoft. I Called Samsung and was told to call Sprint and Microsoft. I Called Microsoft and was told to Call Sprint and Samsung.
After Long Conversations with Both Samsung and Microsoft, they Both gave me Food for Thought.
I Called AT&T, Verizon, T-Mobile, and Nokia. You ask Why make these Extra Phone Calls? What do they ALL have in Common? Windows Phone 8 Phones! No Voicemail Issues at all on ANY Windows Phone 8 Phones! Which leaves JUST ONE OBVIOUS CONCLUSION. SPRINT!
The Issue with Sprint's Voicemail is SPRINT.
Since Sprint is having a LOT More People that are getting SMARTPHONES, they WANT EVERYONE to Use their VISUAL VOICEMAIL ONLY and had changed stuff on their Servers. as soon as that was done, EVERYONE who had bought either an HTC or SAMSUNG Windows Phone 8 Phone who did NOT have Any Problems before, were ALL EFFECTED!
When Calling the Customer Service People, they have No Idea of what was the Issue and All try to help without Any End Effect that Works, EVEN SPRINTS VISUAL VOICEMAIL APP DON'T WORK!!!!
Missing a voicemail for Most People is Not Too big of an Issue, but for Some People, it Could be a Deal Breaker, a Missed Contract, a Missed Opportunity, a Life or Death Situation, or Any Other Reason that You can think of.
I have Called Many of the Sprint Customer Service People Many times and had the Issue Escalated to Advanced Tech Support a Few times and had one Advanced Tech Support Tell Me that Sprint had Changed their Servers for EVERYONE to USE SPRINT VISUAL VOICEMAIL from Now on and that there were just a Few People Effected with the Same Issue that I Was Complaining about. I was asked to hold on and then the Advanced Tech Support guy NEVER came back on the line. While Holding on, the line went dead.
I GUESS that the Advanced Tech Support guy was NEVER supposed to have told Me that and he was told to just Hang up on Me.
After waiting a few weeks before complaining again, when I called back and spoke with a Customer Service Person, they said that is a VERY KNOWN ISSUE and they have been working on it. Also, both HTC and SAMSUNG Windows Phone 8 owners are the Only ones Effected.
Knowing that you get multiple answers from multiple Customer Service People, I had called back a few times over the next 2 weeks and at varying times to make sure I get different Customer Service People, and EVERY one of them told Me the EXACT SAME thing. So it's Listed on their TELEPROMPTERS that they ALL READ OFF OF.
If this has Helped Any of you here, then RE-POST THIS ANYWHERE and EVERYWHERE!!!!!!
I have the International Note 5 (SM-N920C) with the Carrier T-Mobile in the U.S, I have had this Device for Over a year now and it always worked flawless, ever since T-Mobile started implementing changes to there System my Calls go straight to voicemail when anyone try calling me, also, when i try making out going calls it takes close to a Minute before i even here the phone start ringing on my end, its weird cause this never happened, and it not my device either, i called T-Mobile and they couldn't help me, Hence, I went on Vacation to Myrtle Beach and toke my Note 5 with me to see if it worked out there (I live in Brooklyn NY) and yes, of Course it started working Flawless again, Im writing this Post in HOPES someone can help me, I have Tried Many Custom Roms and CSC zips to No Avail, Im hoping someone out there went through what Im going through and Found a FIX, thanks in advance, Bless to everyone.. One Love, All we Have is One Life.
I'm having the same issues you're having. I recently switched over to TMobile with a SM-N920C. It takes a while to dial out and some calls are going to voicemail without even ringing. I'm in Jersey City so maybe it's something they're trying out in more congested areas.
I haven't tried any custom ROMs or kernels but I was wondering if it had something to do with Voice over LTE not being supported by the phone out of the box. Have you tried any VoLTE capable ROMs/kernels?
Hey S.G, first off, i got a Kick out your User Name, on another Note, i tried Various Custom Roms and Custom Kernels that allow me to turn on and Off VOLTE, nothing Worked, Like i mentioned in my post, i went on Vaction to South Carolina and my device worked Flawless like it should be working now, I Called T-Mobile and they couldn't help me, all i could ask is for you to also call tmobile to let them now its an issue on there end with the international devices, Now if they get enough calls from different ppl they will have no choice but to fix the issue, Ill do the same... Thanks for reaching out though. This really sucks cause i love this device.
Hi. I have exactly the same issue in NYC... Did you ever find the solution for your Note5?
About once every day or so, Android Messages won't send an SMS. If I reboot the phone, it will send. I have tried disabling wifi when it won't send, but it still won't deliver until a reboot. Verizon is my carrier. Never had problems with my Pixel 3XL. Any thoughts?
rrhutch said:
About once every day or so, Android Messages won't send an SMS. If I reboot the phone, it will send. I have tried disabling wifi when it won't send, but it still won't deliver until a reboot. Verizon is my carrier. Never had problems with my Pixel 3XL. Any thoughts?
Click to expand...
Click to collapse
Is this a new line or did you replace an old phone. I had a friend who had SMS issues and had to have a tech over the phone work things out. His phone replaced an iPhone and that had some CDMA to LTE issues in the switch.
Sent from my Pixel 4 XL using Tapatalk
Replaced a old phone. Seems to be if I have WiFi calling enabled on the phone that the problem occurs.
I'm having the same issue with Pixel 4XL when connected to Wi-Fi.
Does Verizon use the esim instead if a physical Sim card. On Sprint when I switched from my 3a to the 4 xl I had to wipe the esim information off the 3a.
My 3a was still registering as in service but no connected. It was causing issues with calling and texting. I cleared all the esim info from the 3a called Sprint and had them refresh everything in the back end and I haven't had an issue since.
I have a Verizon physical sim. The issue seems worse today. When I got home from work I was wondering why I wasn't getting any texts. I turned off wifi and was flooded with messages that I didn't receive since connecting to wifi. My wife's Pixel 3XL and daughter's Pixel 2 are not having the same issue.
I have the exact same issue and started another thread describing it. I never had this problem with the Pixel 3 XL.
Sent from my Pixel 4 XL using Tapatalk
Did you have an iPhone beforehand? If so the go to apples site and unregister from iMessage as that's the culprit.
Sent from my Pixel 4 XL using Tapatalk
Solution: https://forum.xda-developers.com/pixel-4-xl/help/advisory-verizon-users-upgraded-pixel-3-t3997613
I simply disabled "chat features" within settings of android messages and seemed to do the trick. Good luck!
Edit: Nevermind, it was working but stopped. Please let us know if anyone else has success with Verizon tech support.
Verizon customers that had Pixel 3s has the ability to use RCS through Android Messages with other Pixel 3 users. This was a legit setup, not the hack that is floating around the internet. However, Verizon does not support this with the Pixel 4 at this time.
I was running into a problem after upgrading from my Pixel 3 to 4 that if I enabled WiFi calling on my Pixel 4 it would not send text messages. After many calls with tech support to no avail, replacing my phone with a new Pixel 4 which did not solve the problem, was able to finally determine the issue was related to RCS being enabled on my account w/ Verizon. Once I mentioned to the Level 2 Tech that I thought this might be the problem, they saw where it was setup as a feature on my account in their system. They removed it and now I am able to send text messages again with WiFi calling enabled. Just a heads up for anyone that might run into this problem if they have upgraded from a Pixel 3 to a Pixel 4 on Verizon.
Why is this more desirable to disable it instead of just enabling it on the new phone??
The only way to enable it, f your on Verizon, is to use the hack. I tried the hack. It would allow me to interact with other users that had RCS enabled, but still wouldn't allow me to send SMS or MMS messages.
rrhutch said:
Verizon customers that had Pixel 3s has the ability to use RCS through Android Messages with other Pixel 3 users. This was a legit setup, not the hack that is floating around the internet. However, Verizon does not support this with the Pixel 4 at this time.
I was running into a problem after upgrading from my Pixel 3 to 4 that if I enabled WiFi calling on my Pixel 4 it would not send text messages. After many calls with tech support to no avail, replacing my phone with a new Pixel 4 which did not solve the problem, was able to finally determine the issue was related to RCS being enabled on my account w/ Verizon. Once I mentioned to the Level 2 Tech that I thought this might be the problem, they saw where it was setup as a feature on my account in their system. They removed it and now I am able to send text messages again with WiFi calling enabled. Just a heads up for anyone that might run into this problem if they have upgraded from a Pixel 3 to a Pixel 4 on Verizon.
Click to expand...
Click to collapse
Thanks for pointing this out because I was having the same issue. I was on the phone with Verizon tier 2 tech support and they claimed there is no such setting so it's hard to know which support person to believe! I simply disabled "chat features" within settings of android messages and seemed to do the trick. Thanks again!
Edit: Nevermind, it was working but stopped. Please let us know if anyone else has success with Verizon tech support.
bills742 said:
Thanks for pointing this out because I was having the same issue. I was on the phone with Verizon tier 2 tech support and they claimed there is no such setting so it's hard to know which support person to believe! I simply disabled "chat features" within settings of android messages and seemed to do the trick. Thanks again!
Edit: Nevermind, it was working but stopped. Please let us know if anyone else has success with Verizon tech support.
Click to expand...
Click to collapse
I wish I had gotten more info from the Level 2 person, but he clearly said that there was an RCS setting on my line that he had to remove. Once he did, it started working.
rrhutch said:
The only way to enable it, f your on Verizon, is to use the hack. I tried the hack. It would allow me to interact with other users that had RCS enabled, but still wouldn't allow me to send SMS or MMS messages.
Click to expand...
Click to collapse
Ah ok gotcha. I didn't recognize what you meant. I'm on Verizon with the RCS enabled and have not have any issues with sending it receiving so far. I guess it'sn like you said that it's an internal Verizon condition.