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!!!!!!
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
640k said:
i've had the call not go through as you've described, but have never had a phone not let me place "any call" afterwards. i always chalked it up to poor performance (limited RAM, too many processes, etc). My DROID3 would do it and often times when it finally did make a call, there was zero sound and I would have to reboot the phone.
Click to expand...
Click to collapse
Hmm, it doesn't seems like poor performance. I ended up every task and it still happened.
However, I noticed that when I check the "2G ONLY" option it comes back to work. Maybe it's something with the HSPA/HSPA+ connection.
it could be completely carrier dependent then. my experience has been with vzw.
Moto X "Call Ended"
I have experienced this same problem in Houston on the T-Mobile network after switching over to Android. My T-Mobile rep told me they have had towers vandalized for copper which has impacted service for them, I believe he said it was about 15 towers and 10K a pop to get things corrected. What gets me is I was on a Bold 9900 and while I had signal problems in the affected areas of town I didn't not experience the "call ended" issue. I can also call other T-Mobile phones from those same areas but not land lines so to me this seems like a possible network routing issue which I have seen before between specific carriers.
If the problem does continue I may have to switch carriers. T-Mobiles service was previously outstanding in Houston but recently had not been great after the 4G LTE upgrades. I support multiple hospitals and need service to work correctly and will work with the T-Mobile Engineers to see if I can make headway on that front. I noticed another MotoX user reporting he only had the issue when flying in to Houston for work and that everything worked for him outside of Houston. His solution was to operate in 2G mode which for me is really not an option. I have to handle a lot of tasks over the network while on calls.
Anyways I would appreciate it if others could post if they are experiencing these issues and give as many details as possible so we can try to isolate the root cause of this problem and if found to be a carrier issue we can escalate with them. Thanks
dicarli said:
First of all, I want to say that I found people with the same issue using Android everywhere and with a lot of different phones, so it's probably an Android bug rather then Moto X itself, but I wanted to leave my report.
I came from an S3, which suffered from the same problem when using Cyanogenmod. When using official Samsung ROM everything worked as it should. Now, I'm getting the same issue on my brand new Moto X.
When I try to call someone, sometimes it just doesn't call, after I press the dial button, it just hangs (without ringing) and finished the call with a "Cal ended" message. It happens randomly, and sometimes I can't call anybody for like 2/3 hours.
The simcard has been changed from the S3 (micro) to the Moto X (nano), so it's probably not it. Also, with the Samsung ROM it didn't happen.
I can still receive calls and messages, and the signal strength is fine most of the time. I just can't call.
Today I faced this problem and then I tried calling from my girlfriend smartphone (samsung ace IIx) at the same time, which is from the same carrier, calling to the same number, and it just worked fine. Mine still didn't work though.
Here is a thread on people on xda facing the same problem, but with a different phone: http://forum.xda-developers.com/showthread.php?t=2351227
Don't know what to do.
Click to expand...
Click to collapse
Call Ended Issue Resolved
Hi All,
I see this Call Ended Issue in many brands. So I assume the error is a combination of the Network along with the SimSlot.
I tried various combinations for my Moto-E mobile.
Before i post the solution i found, Let me provide a brief about the problem.
I use Vodafone network on sim1 slot and Uninor network on Sim2 slot. I started facing the call ended issue on my sim 1 vodafone network.
I inter changed the sim's and found the network working absolutely fine. This makes me to understand that the sim1 slot with the vodafone carrier has some network issue where that IMEI code has some problem.
i tried to place the vodafone sim again on the sim 1 slot and found the problem persists. So i came to that conclusion.
Hope this might help you and provide a instantaneous and temporary resolution.
Thanks,
Praveen.
Call Ended problem still going...
Hey,
I just rooted my Moto X (XT 1053), like 5 min ago, in the hope to fix this same problem. I`m no programer/developer and have nothing against rooting, I just don`t think I`m that kind of user. Anyway, about a week ago my phone started to drop my calls right after dialing. I restored factory settings, updated it and nothing worked. I took it for service and they offered to charge me 150 bucks to restore factory settings and update the software. So I was kinda forced to root and try to fix it this way. The problem is that I probably don`t understand half of what you guys say, so if there are any kind souls out there, please help me out.
To sum it up:
- No Sim Card error
- I get carrier services and can use mobile internet (3G because 4G is still too explensive here in Brazil)
- Directly drops my calls
- Won't receive calls
- Won't send or receive text messages via carrier (just over 3G or wifi)
I`ve tried another carrier's Sim Card, no go.
I`ve tried my Sim Card on another phone and it worked just dandy, so I really don`t think it`s carrier related.
I`m running Android 4.4.3, as the other updates weren`t available for my phone via Motorola. I thought maybe updating to a newer version of Android might do the trick. I just have no clue on how to do that on a rooted phone... or on a non rooted phone for that matter.
Can anyone give me any tips/pointers/etc... ?
Thanks!
I have the same issue with my moto x on Verizon. Have you been able to figure it out?
Ok everyone figured I'd come here to where the experts live. Haven't been here in awhile.
Recently my S8, wifes S8, and our sons S8+ all have the same issues.
The first issue is texts get stuck "sending". This happens with WiFi on or off, with wifi calling on or off, and I even tried changing off LTE to just 4G/3G/2G and even 2g in settings to see if that would help. I'm on the latest firmware from TMO ending in QEF, well we all are.
The other one is apps like FB and others aren't alerting but they will show the number of alerts even after they've been checked. I've reinstalled these apps and the problem persists, and then I can reboot my phone or wifes phone and all the alerts start working again for awhile and then die eventually.
The texting issue though persists and is random when it will hang and when it doesn't.
According to TMO rep at the store it's a bug in the firmware with bixpy that was pushed out, but I frankly don't buy it and figured I'd hit the guru's up here and see if you guys have any thoughts.
Thanks in advance guys and gals....
I too have had the random "texts get stuck sending" issue. I haven't had it in a while though (now that I've said that I'm sure I will).
I unfortunately don't have any suggestions.
I ended up using googles version of messages due to this. Only on stock text app do i have any problems anymore. I also noticed on the stock app that my phone would say "sending" when the other side would actually get it, but it was at random.
You don't have a cellspot repeater or router do you? Last time I had it, my device was hung and needed reboots. Just a thought.
Thanks for the feedback, yes I have a cell spot, but I also have the issue other areas of town too with no real specific place thatbit always happens.
I'm going to reverse back from the qef firmware and see if that resolves things. This has been so annoying, and it just started about two weeks ago.
Thanks again everyone.
I have had the same issue with sending texts too. I have been using the stock messenger app. I may just switch to textra.
Same issue here. A temporary fix, try turning on airplane mode and off. Works for me a times
Also happening to me on the XAA firmware (have unlocked NA variant) with the stock messaging and Google messages.
So I'll ask the question begging to be asked (at least by me): How does one disable this messaging app and use "stock messaging" app?
Thanks in advance....
rabilancia said:
So I'll ask the question begging to be asked (at least by me): How does one disable this messaging app and use "stock messaging" app?
Thanks in advance....
Click to expand...
Click to collapse
Just get a app disabler for Samsung from play store like BK Disabler.
If I were you, just download Android Messages. It's simple and fast.
However, I do not recommend disabling stock messaging, unless you don't like getting EAS (Amber/Weather/Presidential Alert)
Having the exact same issues and it's driving me crazy because I really like this phone. I don't get notifications for any of my apps but when I open them I can see the new messages. A reset seems to fix the problem but it only lasts about an hour before it starts doing the same thing. I've tried using different messaging apps but the same thing. And the fact that I don't get notifications for other apps it can't just be a text messaging issue right?
Happened to me for almost 2 months but haven't had an issue in about a week. Called t mobile, they created a ticket and said they'll be working on it. Few days after speaking to them, problem went away.
This has been happening intermitantly for me as well. It's been bad the past three days. I'm currently in coversations with T-mo's engineering team and they seem to be coming up with a bunch of dead ends. It's not a location based thing as it's been happening over a 20 mile radius in the past few days for me. Other people on T-mo network that I'm freinds with or I work with aren't having any problems. I'm wondering if just a fresh SIM card could solve it?
I have data connection although it seems a little sluggish compared to when I originally got the phone. Similar to OP I've tried all the "G's" modes, with wifi calling on, with it off, with cellular network preffered with wifi calling on and off. With Textra, with stock messaging app. I've factory reset to no avail. I've pulled and re-inserted the SIM card to no avail. This is incredibly frustrating for a flagship phone on a network where I've had no previous issues.
UPDATE: T-Mobile sent me a new SIM card and that seems to have cleared up the issues. Not sure if it just hapened to coincide with T-Mo tower fixes or anything else like that in my area but I'm back to normal operation. Anybody else experiencing this I recommend you push customer service to send you a new sim.
my husband and i are having a strange issue where we can message pictures and video clips to other people that don't have the s8, or aren't on tmobile and they'll send and receive just fine, but when we try to send to each other, the first attempt to send fails, but the second attempt goes through?
balthuszar said:
my husband and i are having a strange issue where we can message pictures and video clips to other people that don't have the s8, or aren't on tmobile and they'll send and receive just fine, but when we try to send to each other, the first attempt to send fails, but the second attempt goes through?
Click to expand...
Click to collapse
i had same problem one of you is not using stock message app, if you check it ull find pictures all there i think its new messages plus thing
"READ Tmobile acknowledge Native message app is corrupt. Don't update Says TMobile
It seems that if you read online on T-Mobile forms in other areas people are not receiving all their text messages if not 10 to 50% of them are missing people are finding this out by logging into T-Mobile digits and same messages they never got through the native messaging app after the 8.0 update.
I noticed this when I did not receive messages for a good while until I put my SIM card into a Galaxy S8 and 20 to 30 messages popped up that were pre conversation topics from the past days before after talking to T-Mobile and digits support team they are being told to replace the device one time and Advising customer to keep the Nougat software until a fix ia found or until further notice this issue seems to be tied to the Z2 only and Oreo update just wanted to throw this out there as a pre warning the alternative solution the tech told me is that you can use a different messaging app but who's to say you'll ever know if you're not getting all your messages .
It evidently seems to be affecting incoming messages alternatively at your own choice maybe Nougat could be flashed back "Not sure" but this is a real life issue for this phone . If you want to be certain and surprised login to T-Mobile digits activate it and see what messages that you have not got
Hope this information is appreciated.
Um check your wifi calling settings
Sent from my [device_name] using XDA-Developers Legacy app
androidddaaron said:
It seems that if you read online on T-Mobile forms in other areas people are not receiving all their text messages if not 10 to 50% of them are missing people are finding this out by logging into T-Mobile digits and same messages they never got through the native messaging app after the 8.0 update.
I noticed this when I did not receive messages for a good while until I put my SIM card into a Galaxy S8 and 20 to 30 messages popped up that were pre conversation topics from the past days before after talking to T-Mobile and digits support team they are being told to replace the device one time and Advising customer to keep the Nougat software until a fix ia found or until further notice this issue seems to be tied to the Z2 only and Oreo update just wanted to throw this out there as a pre warning the alternative solution the tech told me is that you can use a different messaging app but who's to say you'll ever know if you're not getting all your messages .
It evidently seems to be affecting incoming messages alternatively at your own choice maybe Nougat could be flashed back "Not sure" but this is a real life issue for this phone . If you want to be certain and surprised login to T-Mobile digits activate it and see what messages that you have not got
Hope this information is appreciated.
Click to expand...
Click to collapse
seemles said:
Um check your wifi calling settings
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
What about it ? Wether on wifi calling or not this is a message issue acknowledged and very pronounced In many ways . It's simple to see with a few trial and error tests regardless of wifi
Or LTE Data
Seeing all your messages show up on TMO digits comparing them to messages you've got or never got .....putting a SIM card in a different phone and seeing multiple messages pop up that have still been trying to push through that are tied to specific time line conversations. TMobile literally already acknowledges this it's just nobody is realizing it because they're not expecting messages that they're actually missing from people.
Feel free to test it if you would like have multiple people text you wait for it to come through not saying it affects everybody T-Mobile did tell me that they already have a ticket out for it and it's software related to this particular phone.
On top of the SMS of all things is one of the most critical uses of a phone .
Just trying to shed light on a rising issue that most would never be aware of .
Because all Android phones ship with settings set to wifi preferred wich leads to dropped calls and unsent messages after setting up a home wifi. And if you have no sim installed your obviously using wifi calling wich is most definitely not as dependable as volte.
Sent from my [device_name] using XDA-Developers Legacy app
seemles said:
Because all Android phones ship with settings set to wifi preferred wich leads to dropped calls and unsent messages after setting up a home wifi. And if you have no sim installed your obviously using wifi calling wich is most definitely not as dependable as volte.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'll look into that....but if your not on wifi calling "connected" to a wifi network you would still be using volte right ? This is happening to people conversating anywhere Mobily in a vehicle not on wifi. Messages for instance with my brother whereas I never got a reply in which I would have came through after I put my SIM in my s8.
People are seeing ungotten messages in TMobile digits.
I don't really care i was just looking out for the community here with a potential problem hindering, and T-Mobile tech support made acknowledgement about it . I highly doubt a community across United States all at once is screwing up by keeping WiFi preferred on.
You're only going to be using WiFi calling if you're connected to an actual at work under that settings menu otherwise you would be using cellular by default just like it says to choose below that
You're only going to use Wifi calling if you're connected to a WiFi network otherwise you're going to use cellular default which is the same as being on cellular by default correct me if I'm wrong
Can you post a link to the discussion? I can't find anything after searching for a while.
Sent from my [device_name] using XDA-Developers Legacy app
Z2 force sms MMS broken discussion link
http://support.t-mobile.com/thread/143284
Multiple replied posts from z2 users
How this has not made it to xda is beyond me but it is real situation
It's really not a good feeling to really not know all the messages you should be getting that you're not especially the ones that you're not expecting the scenario is playing out just like it shows in these support forums and with myself.
It's like not "Some messages are blocked in a limbo status never reaching the target device
Like myself you could stick a SIM card potentially in another phone and see stuff that pops up that was related to conversations long ago that you never got replied too.
I haven't had much of a problem with T-Mobile to T-Mobile network SMS but many other people I know that use other carriers I never got replied to until I stuck my SIM card into a different phone of mine.
It's a janky situation and if TMobile is already acknowledge this and told to replace phones one time then evidently the issue has gotten out to the people that needs to I just don't know how nobody here on XDA knows about this .
I have tried multiple text apps and nothing seems to be different I even thought about editing access point but usually that only solves MMS problems
This issue was already addressed with a fix to boot by xda. I had the issue my self. With no issues after I updated to oreo.
https://forum.xda-developers.com/z2-force/how-to/t-mobile-how-to-3rd-party-sms-apps-root-t3661703
seemles said:
This issue was already addressed with a fix to boot by xda. I had the issue my self. With no issues after I updated to oreo.
https://forum.xda-developers.com/z2-force/how-to/t-mobile-how-to-3rd-party-sms-apps-root-t3661703
Click to expand...
Click to collapse
I tried this method and it did not work, after the Oreo update I tried again but kept having issues. Decided to Force stop the CPS app and install the Google Carrier services app and this worked. Don't remember where I heard/read about Google carrier services. BTW using Googles messages app now and seem to be receiving all messages.
I discovered this a few weeks ago then installed google messages and everything works now
Missing messages FIXED
androidddaaron said:
It seems that if you read online on T-Mobile forms in other areas people are not receiving all their text messages if not 10 to 50% of them are missing people are finding this out by logging into T-Mobile digits and same messages they never got through the native messaging app after the 8.0 update.
I noticed this when I did not receive messages for a good while until I put my SIM card into a Galaxy S8 and 20 to 30 messages popped up that were pre conversation topics from the past days before after talking to T-Mobile and digits support team they are being told to replace the device one time and Advising customer to keep the Nougat software until a fix ia found or until further notice this issue seems to be tied to the Z2 only and Oreo update just wanted to throw this out there as a pre warning the alternative solution the tech told me is that you can use a different messaging app but who's to say you'll ever know if you're not getting all your messages .
It evidently seems to be affecting incoming messages alternatively at your own choice maybe Nougat could be flashed back "Not sure" but this is a real life issue for this phone . If you want to be certain and surprised login to T-Mobile digits activate it and see what messages that you have not got
Hope this information is appreciated.
Click to expand...
Click to collapse
I have already experienced this issue. It's NOT related to wifi calling at all. I tested it with wifi calling on and with it off, same results.
What worked for me to FIX it was to clear storage and clear cache on the "native" app. You won't lose messages already on the device but you should backup with Carbonite sms first to be safe. Once I wiped storage and cache for the app I started receiving messages again normally.
I found out I was missing messages by installing digits. It's all working now but I'm keeping digits temporarily just to be safe.
texasaggie1 said:
I have already experienced this issue. It's NOT related to wifi calling at all. I tested it with wifi calling on and with it off, same results.
What worked for me to FIX it was to clear storage and clear cache on the "native" app. You won't lose messages already on the device but you should backup with Carbonite sms first to be safe. Once I wiped storage and cache for the app I started receiving messages again normally.
I found out I was missing messages by installing digits. It's all working now but I'm keeping digits temporarily just to be safe.
Click to expand...
Click to collapse
Wait so your saying this is a fix wether on Oreo or nougat and digits is the whole reason why .
And the native message app just need to clear cache and data in settings app
Sent from my [device_name] using XDA-Developers Legacy app
I deleted and deactivated digits completely. After I had it completely removed from my account, I rebooted and changed to Android Messages and everything has been fine since October.
Are the issues with this phone sorted yet? I was looking to purchase the T-Mobile variant of this phone but have read about issues such as not receiving texts (huge problem), VoLTE not working with Galaxy S7s, and WiFi connection issues. If they are not fixed, can they at least be avoided by refusing the Oreo update? I would like to avoid rooting my phone just to fix a defect and would only consider using a 3rd party messaging app if it fixed the problem without introducing other problems.
I have my phone choices currently narrow down to the Z2 Force, LG G6, and Galaxy S7 (all are currently in the $400 range). I was leaning towards the Z2 since it's the most powerful, but the issues I'm reading about seem quite severe.
After a little more research I see 2 patches were released for the Z2F after the Android 8.0 update.
https://support.t-mobile.com/docs/DOC-35970
I found a Reddit thread (https://www.reddit.com/r/Moto_Z/comments/7zxcpo/tmobile_moto_z2_force_ocx271_update/) where some people mentioned it fixed the SMS notification and Galaxy S7 VoLTE issues. I didn't see anything anything discussing the Bluetooth/WiFi issues or more importanly, the SMS not being received issue (the topic of this thread). Can anyone comment if those were fixed?
cyborgLIS said:
Are the issues with this phone sorted yet? I was looking to purchase the T-Mobile variant of this phone but have read about issues such as not receiving texts (huge problem), VoLTE not working with Galaxy S7s, and WiFi connection issues. If they are not fixed, can they at least be avoided by refusing the Oreo update? I would like to avoid rooting my phone just to fix a defect and would only consider using a 3rd party messaging app if it fixed the problem without introducing other problems.
I have my phone choices currently narrow down to the Z2 Force, LG G6, and Galaxy S7 (all are currently in the $400 range). I was leaning towards the Z2 since it's the most powerful, but the issues I'm reading about seem quite severe.
Click to expand...
Click to collapse
The latest 2 Oreo updates have fixed those problems, and they didn't affect everyone.
Sent from my Moto Z (2) using XDA Labs