XT1060 on Verizon; right now on one of the later CM nightlies but I know I tried several other ROMs in the past (probably all CM based) to no avail. MMS messages sometimes send/download immediately, most of the time they take at least 30 seconds to send and received ones fail download several times. This happens regardless of mobile data settings, WiFi, 3G, LTE, Hangouts, Messaging, etc. I've yet to correlate anything with the success or failure.
I've been digging through logs and the CM sources and the issue seems to stem from initiating the mobile data connection for MMS. At this point I'm deep in the telephony stack and well out of familiar territory. I'm hoping that someone can verify that they're seeing the same issues on Verizon with non-stock ROMs and also hoping that there's someone out there more familiar with the whole telephony stack that can perhaps guide my search in more productive direction. APN settings look correct and the logs confirm that once a data connection is made the right APN is used and messages get sent/received. I've found some "unrecognized command" type errors in RIL logs during the connection setup phase, but haven't sorted out what they are yet.
I can't be of any help to you with the programming stuff but I can say I have two DE cm12 exhibiting the same bugs.
I also get a soft reboot, where I lose 4g and I have a '!' next to the signal. I don't know if they're connected.
The MMS taking forever is annoying though. I've been considering going clean to a newer nightly than I'm on now and see if it's any better.
Sent from my Nexus 7 using Tapatalk
I had the same issue on a 1060 DE running Nexus Experience (CM based) and what worked for me was to disable the stock mms application and I believe MMSService. Then installed textsecure and all worked well. I can't remember 100% if I kept MMSService disabled or not as I'm back on stock Lollipop, but some combination of the above will definitely work.
TextSecure doesn't appear to use the same channels to send SMS/MMS as the stock app. As I understand, it's more of a mobile data thing than a true SMS/MMS app, which would explain why it worked for you. I'm 100% sure the issue does not lie in the stock CM MMS app, I've traced it well outside of there and the app appears to function just fine once it gets the notification that a MMS capable network is available.
I also sometimes run in to the service indicator giving a network that is strings of numbers like "00000" or "31000". I don't know if both of these are symptoms of the same problem or something completely different.
Apologies for the mis-categorization of the thread, thanks for moving it.
It would appear that APNs do affect this. CM's apns-conf has a "Verizon" "internet" APN that's listed for MMS. Not sure what it's there for and the stock 5.1 apns-conf does not have it. Logs showed RILJ messages of SETUP_DATA_CALL attempting to access this "internet" APN instead of the "VZWAPP" APN that stock would try for. Running the stock 5.1 apns-conf and then also manually removing the "Verizon" APN in settings has allowed first connection MMS messages to download and send fine i.e. ones that result in a SETUP_DATA_CALL RILJ message. It appears that if the MMS connection is already open, however, that it fails until timeout on a RILJ message of RIL_REQUEST_ALLOW_DATA. After 5 retries, we get another SETUP_DATA_CALL message and everything works fine. I am currently running a build of CM with Motorola's 5.1 proprietary binaries though, I'll have to verify that the older ones shipped with CM do not function differently.
This may be related and not a device-specific issue but either a google play services or back-end issue. Reported here because of the mention of these appearing to be data services, not text services having issues.
VZW 1060 DE unlocked but not rooted and took the OTA to 5.1. Did not feel like I experienced any of these issues prior to the update
Now, in addition to tethering problems, having hangouts issues similar to the OP description... messages sometimes take forever to show that they sent, or to come in. I sent a photo 3 times and some text but never could tell from hangouts that I had sent them or got a reply until after I rebooted the phone.
Asus Zenpad: Same issue for hangouts, some hangouts NEVER get some messages - this is a wifi only device. On lollipop
friend's new iPhone: Same issue as OP for hangouts
friend's Droid Turbo: Same issue as OP for hangouts. Reports she leaves the hangout and comes back in to see updates
Edit: Found the LG-G3 is reporting the same issues after updating to Lollipop
http://forum.xda-developers.com/tmobile-lg-g3/general/lollipop-tethering-t3071188
This is 100% a RIL issue with this phone's chipset and vendor binaries. It may carry over to other hardware but it is certainly not a Google issue.
It appears that the libril binaries supplied with Moto's 4.4.4/5.1 do not support RIL_REQUEST_ALLOW_DATA. It looks like they support an older method, perhaps involving RIL_REQUEST_SET_DATA_SUBSCRIPTION.
FYI, i recently fastbooted back to stock 5.1, and MMS working quickly for me.
I'm able to get fully functioning normal MMS on CM 12.1 by hacking the DdsScheduler a bit. If I force it to transition to Idle after MMS releases its networkrequest, everything works fine. I'm confident this is a hacky way of doing it, but it at least narrows the issue down further.
As a side note, the whole DdsScheduler portion was added to telephony in 12. CM 11 appears to work fine, as do all stock versions, of course. As far as I can tell, this bug should affect Galaxy S3 users (probably among others?) as well. Can anyone weigh in on that? I don't have access to one with CM for testing. Anything running a Qualcomm RIL with a version less than 10 should be affected?
Related
Hello all,
I have been happily using my Moto X for many months now without any issues. I have a Verizon Dev Edition which is unlocked/rooted with TWRP installed. The only mods are a customer boot logo and animation. I have super SU installed and ADBlock. Otherwise its the stock current OTA rom.
Just yesterday I have developed a new problem. When I am connected to Wifi, I cannot send MMS messages (which is mostly pictures texts and group texts) out. I can however receive them in. When I disconnect from the Wifi (but leaving the Wifi enabled), I can then send MMS messages. I am using the stock Messaging app. I have also tried Hangouts, which has the same problem.
I have been on the internet reading through forums with people that has the same "type" of problems across different devices and networks. So far nothing I have read has fixed my issues. My APN looks to be set up correctly, but even if it wasn't, there is no ability to add/edit anything.
I just called and troubleshooted with Verizon. After numerous different things they finally sent a "network refresh" to the device. Not even this has worked. Their final solution is to do a factory reset on the device. Before I do this I was hoping someone here might know what I could try before I take the plunge.
Please help! Thanks!
Welp. I disabled Adblock Plus and it works again!
StiM_AddiCt said:
Hello all,
I have been happily using my Moto X for many months now without any issues. I have a Verizon Dev Edition which is unlocked/rooted with TWRP installed. The only mods are a customer boot logo and animation. I have super SU installed and ADBlock. Otherwise its the stock current OTA rom.
Just yesterday I have developed a new problem. When I am connected to Wifi, I cannot send MMS messages (which is mostly pictures texts and group texts) out. I can however receive them in. When I disconnect from the Wifi (but leaving the Wifi enabled), I can then send MMS messages. I am using the stock Messaging app. I have also tried Hangouts, which has the same problem.
I have been on the internet reading through forums with people that has the same "type" of problems across different devices and networks. So far nothing I have read has fixed my issues. My APN looks to be set up correctly, but even if it wasn't, there is no ability to add/edit anything.
I just called and troubleshooted with Verizon. After numerous different things they finally sent a "network refresh" to the device. Not even this has worked. Their final solution is to do a factory reset on the device. Before I do this I was hoping someone here might know what I could try before I take the plunge.
Please help! Thanks!
Click to expand...
Click to collapse
I and other people have been suffereing from the same problem, no one has found a fix. there are a few forums and someone suggested using RSD Lite to flash your phone and that wil fix it but I'm not messing with that.
I just refunded my phone. You can post about it on google plus, the motorola engineers are very responsive and way more helpful than customer service!
I have a weird issue that when my nexus 6 is connected to wifi, it can't send or receive mms messages. In the Google messaging app, it shows mms as failing to download. The second I turn off wifi though, everything goes through, both sending and receiving. My nexus 5 on lollipop had the same issue. Has anyone else on 5.0 experienced this? I couldn't find anything on the AOSP bug list. I am unencrypted, rooted and have TWRP.
RoninRyan said:
I have a weird issue that when my nexus 6 is connected to wifi, it can't send or receive mms messages. In the Google messaging app, it shows mms as failing to download. The second I turn off wifi though, everything goes through, both sending and receiving. My nexus 5 on lollipop had the same issue. Has anyone else on 5.0 experienced this? I couldn't find anything on the AOSP bug list. I am unencrypted, rooted and have TWRP.
Click to expand...
Click to collapse
That's been my experience with every device I've ever owned on both Sprint and T-mobile. Nothing out of the ordinary there
That's unfortunate. What's weird is that my nexus 5 with kitkat had it working just fine. I guess I'll just hop the wifi calling fixes it whenever that comes out.
My Nexus 6 doesn't like to send texts while on wifi. It takes a very long time for them to send but if I flip wifi off they send immediately. I haven't tried MMS but I suspect it would be a similar experience. I just leave wifi off at home now. I get LTE anyway and have unlimited data.
I had this problem at first, but seems to work fine now. Only thing different I did was change APN protocol to IPV4/IPV6 instead of IPV6. I read somewhere switching it to IPV4 solves MMS problems, but so far the combo has worked for me. Not sure if that was the issue though, worth a shot.
Now if I could fix my general signal issue, that'd be great =/
I hope this helps. It worked for me when I had the note 4 but now I'm getting a Nexus, don't have one to test this on yet but you guys can.
In short you can try setting up an APN with the MMS port as 80 because right now its probably blank.
http://forum.xda-developers.com/showthread.php?p=56544281
I'm having the same issue on Cricket with my Nexus 6. Rooted, stock 6.0. With my wifi turned ON, I can not send or receive any grouped messages. I cannot send or receive any MMS messages.
I use the stock messaging app.
There doesn't seem to be a solution. I've quadruple checked the APN. Made sure the MMS Port is set to 80, nothing has worked. I feel other solutions like Using a Different Messaging App, or remove every App are bandaids for symptoms. Not solutions for the problem.
Leejin said:
I'm having the same issue on Cricket with my Nexus 6. Rooted, stock 6.0. With my wifi turned ON, I can not send or receive any grouped messages. I cannot send or receive any MMS messages.
I use the stock messaging app.
There doesn't seem to be a solution. I've quadruple checked the APN. Made sure the MMS Port is set to 80, nothing has worked. I feel other solutions like Using a Different Messaging App, or remove every App are bandaids for symptoms. Not solutions for the problem.
Click to expand...
Click to collapse
The issu could be due to the app not switching over to data properly when needed. This could also be a radio issue among other things. Without a logcat to tell where and why it is failing everyone is just shooting in the dark.
zelendel said:
The issu could be due to the app not switching over to data properly when needed. This could also be a radio issue among other things. Without a logcat to tell where and why it is failing everyone is just shooting in the dark.
Click to expand...
Click to collapse
Okay.. What is a logcat and how do I make one?
Leejin said:
Okay.. What is a logcat and how do I make one?
Click to expand...
Click to collapse
A logcat is trouble shooting 101. Just search for how to do one and you will get a few tut. It does need root sometimes so keep that in mind.
I had major mms issues on T-Mobile. I did some searching and changed the apn. I also now use hangouts for SMS/mms, and all is well again. I could not send mms at all before with WiFi on. Make sure your apn is correct for your carrier. Mmsc was blank right out of the box on T-Mobile.
Sent from my Nexus 6 using XDA Free mobile app
zelendel said:
The issu could be due to the app not switching over to data properly when needed. This could also be a radio issue among other things. Without a logcat to tell where and why it is failing everyone is just shooting in the dark.
Click to expand...
Click to collapse
I am on T mobile and it had worked fine until 6.0.
I was on cricket and had this issue; drove me insane. I finally ported my number to Google Voice and started a new line with cricket. With GV handling all the SMS/MMS through Hangouts, I haven't had any issues, whether it be on wifi or not. Might be worth considering.
Ok, I've got something odd going on and to be honest I'm not sure if it's a T-Mobile Nexus 6 based issue or something on the other end (Oneplus One).
I have one contact in particular that can receive sms and mms messages from me with no issue but I can only receive mms messages from him. If it's a standard sms I never get it. It's really odd. Considering he can get both types from me but not the other way around makes me wonder if the issue is on my end.
I just updated to 5.1.1 and still no change. This was with a factory reset and not restoring the old data either (so nothing corrupted came from the update).
This happens regardless of what messaging program I use (Textra, stock messaging app, etc).
Anyone have any suggestions?
I would expect it to be more network than phone. Try and get a test sim from another provider in your phone.
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