Database Develop

Enable Data Roaming Setting Not Retained

Like many others, my phone has a tendency to drop 3g unless I enable Data Roaming. This has been the case with My D1 with 2.3.3.
Now that I have the Droid 3, I have the same thing. No surprise there.
HOWEVER, when I enable Data roaming on my D3 and then go into an area where the phone drops to 1x then no data, I get a notification that Data connectivity has been lost because Data Roaming is Disabled.
If I pull down the notification bar, it says I can select the bar to go to the setting. I do. Sure enough, the Data Roaming Enable box is Unchecked.
I check the box. Go to my home screen, and the notification will reappear. I can do this all day.
If I go to my home screen, ignore the notification and go to settings, battery & data manager, then data delivery, the setting is unchecked....BUT....If I access the menu this way; the setting will be retained until the phone is brought to an area where data signal does the 3g to 1x to no signal thing. Then it starts all over again.
Any suggestions? Anyone else getting this? I received my D3 over a week ago, and finally exchanged the phone for another one. That phone lagged and had random freeze issues. This phone has none of those issues, but still has the Data Roaming Enable setting not retained problem.
Wasn't this an issue with CM7 at one point? The d3 claims to be running 2.3.4, but it is hard to tell with all the Motoskin draped over it.
I have also noticed that (in my area) if I have data roaming enabled, my battery life is much improved. With it off, my battery drops like a rock.
I have contacted Moto about the issue and reported the bug; but all I am getting is the "we'll look into it" brief email. Like I'm some kind of first-time Android user who doesn't know how to use my phone.
Please tell me someone out there is having this too, or that there is a patch that Moto just hasn't released yet....
Thanks in advance everyone.

UPDATE:
2nd phone, all data connection is lost. No phone, 1x or 3g. Phone is awake, and battery settings are set to Performance (No Battery Savings).
Data manager is disabled (no stoppage of data)
When going into an area where I ALWAYS had "EXTENDED NETWORK" data available at 1x speeds prior to this phone, the phone says no data connection.
I look and my Data Roaming Enabled checkbox has been unchecked.
I check the box, click OK to agree that I may incur Roaming charges. The phone will reconnect to data at 1x or 3g depending on where I am.
If I look at the phone 5 minutes later, the checkbox is Unchecked again for allow data roaming. Sometimes less.
This only happens after the phone goes into a weak coverage area.
I have tried rebooting the phone. The setting stays retained after reboot, but is lost as soon as I go into poor coverage.
I have tried factory reset. Setting stays until I reach a poor coverage area.
Already exchanged for another phone. Same issue.
Changed phone from Global to CDMA mode and network to automatic. Setting still does not hold.
It is most strange though, that it doesn't happen until after my home network is lost. The setting will hold until then.
Without that setting checked, I cannot connect to my "Extended Network", which in my area is a no-cost option. I keep checking the box, only I can't get the setting to stick when I go to a weak coverage area.
The coverage area should not make changes to the retention of allowing of data roaming checkbox. Something is improperly referenced in the software.
Motorola's out-of-country sweat-shop customer-no-service department wants me to ship my 2nd brand new phone to them (5-7 days for them to process and receive it+whatever it takes to ship to them) and take between 14-21 days to "repair" the phone, and then take another 5-7 days to package, ship and return to me (all at my expense). Why am I sending a new phone that is defective "out of the box" to be repaired??
So I'm supposed to go without my phone for 5 WEEKS because they have a software problem??? It can be duplicated every time, and on more than one phone. They have the old one. Fix that and send out the update please!!
Am I the only one that has had this issue? Seriously, no one else?
Any help would be greatly appreciated. This is frustrating as heck. I love the phone, but this is ridiculous and makes it rather un-usable depending on where I am. I NEVER had this with my D1! Moto, what happened?
Thanks everyone. +1 if you've had the issue please.

Same Problem
I also have this same problem.
After reading other forums, I thought it may just be the Droid 3 or a Motorola problem. I ended-up turning back in my Droid 3 after Motorola said it was a Verizon problem (which really is not the case). Now, after reading your thread, it makes me wonder if this is a Android OS issue.
I really hope it is not a OS issue, I have wanting an Android phone for a long time.
At my house it always kicks off the data roaming option. I really have no idea what is causing it.
Just wanted to post so that you know your not the only one!

Thank you.
I have run a logcat and have traced the problem to Motorola's battery and data manager service. It is not the OS itself, from what I can see.
It seems that under these particular conditions, the battery and data manager service crashes. Though this should not be a major problem in and of itself, though still not right and needs fixing there too. The service promptly restarts and then loads the settings that were enabled at the time of the crash from a secure data folder. (Or it's supposed to)
The problem comes into play when these settings are loaded. Enable Data Roaming is "loaded" as No(off) any time the service loads these values after a crash of the Battery and Data Manager service.
Unfortunately, as usual, Motorola is dragging their feet at releasing the source code for the Droid 3. This may or may not help the issue, as the Battery and Data Manager service that crashes is a part of Motoblur. Meaning, they aren't going to be forthcoming with the information.
They also are being a typical OEM in their refusal to believe that they could have made a mistake when programming and that they have something to fix.
My Droid 1 has run 2.3.3, 2.3.4, and 2.3.5 and this has NEVER been an issue keeping the setting retained. This is not an issue on our INC2, which is running 2.3.4 in all the same areas that cause my D3 phone to lose the setting. I am also running an Eris with 2.3.5 and it does not have the issue. This is strictly with the D3 from what I have seen.
It's funny how Moto is blaming Verizon for an issue they say doesn't exist. If there isn't a problem, how can that be the network's fault??? The network doesn't change that setting in the phone. Software changes it. In this case, poorly written software added onto the Android OS. Too bad, the OS works fine until Moto putzed with it (Blur).
The OS is not the issue here, it seems the D3 software has two problems:
1 the Battery and Data Manager service shouldn't crash like that.
2 it should return the proper settings if it does.
If I had the chance to do it all over again (knowing what I know now), I would have said send me an INC2 as a replacement. I honestly figured it was a phone hardware problem and the new phone (under warranty) would fix it.
Honestly, I am completely disappointed with this device. That may change when root is obtained and I can get rid of the poorly written trashware that seems to plague this phone. But right now I'm most disgusted with the fact that it doesn't work right and Motorola couldn't care less, even though it's their sofware that is the problem.
I have pruchased my last Motorola product, and am not holding my breath that Motorola will either care or fix their problem. I am certain the future rooted ROMs will be able to transform this lagtastic, glitch-ridden, battery pig into the elegant piece of hardware it has the potential of becoming.
Sorry Moto, sometimes the truth hurts.
Thanks for the support that it isn't only my phone or service area.
Others please +1 as you experience it. The issue is logcat documented and now confirmed on at least 4 devices.
Sent from my DROID3 using XDA Premium App

I have this issue as well. Now that we have root, do you have any ideas on how to resolve it?

This is the response I received from Motorola. They need to get a move on with a fix for this huge goof up.
"Thank you for reaching out to Motorola.
We apologize for all the inconvenience and appreciate your patience. The Support Engineers have been made aware of the issue with the "Data Roaming" feature of the phone; and there are currently working on a possible resolution for a future update. You will need to manually change the roaming option back until fix is available. The Support Engineers have not provided an ETA on when this will be available.
If you have any additional questions or concerns please contact Customer Care at (800) 734-5870."

blkwlf said:
I have this issue as well. Now that we have root, do you have any ideas on how to resolve it?
Click to expand...
Click to collapse
The latest developer update, which is currently in soak testing, has fixed the issue for me.
No formal release date yet on the over the air (ota) version's release date, but I would expect out in the next couple of weeks as long as everyone else had the same results I had with the test update.
Update will upgrade system version from 5.5.959 to 5.6.890, and the baseband radio will be updated at that time as well as the kernel.
So there does seem to be a fix, despite the terrible customer service at Motorola. Honestly, it sucks! I had this update last week, and I'm sure somebody knew this was intended to fix the problem. Not once has Moto asked for information or applied for releasing a phone that was not ready.
Instead, we got canned bot responses and the general feeling that Moto just doesn't care now that they have our money. It is really sad.
Lets hope Google can straighten it out.
Fingers crossed. Though now that we have root, and a custom recovery possibly by week's end; I could care less about Moto. My next phone won't be Motorola...fool me once, shame on you; fool me twice, shame on me.
Sent from my rooted, de-bloated, test-updated DROID3 using xda premium

wattnxt said:
The latest developer update, which is currently in soak testing, has fixed the issue for me.
Click to expand...
Click to collapse
I have also flashed to 5.6.890, re-rooted and de-bloated. So far, the new radio has done nothing to help my issues with the data roaming becoming disabled. Have you tested the new software under the same conditions as the old?

I may have to retract my last statement... my phone did auto disable the Data Roaming once after updating, but since then it has been fine. Hopefully the update truly did fix it!
Sent from my DROID3 using XDA App

I have purposely tried to get the setting to fail. Same result for me as you saw; I got the same old warning once and have not seen it again in over a week now.
For me this was huge, as it failed 20 plus times a day at work. All I had to do was walk down one specific corridor, and by the time I got to the other end my setting would have been unchecked. So going a week with it staying retained (in global mode too by the way) is monumental proof for me it is fixed.
Now I have seen this on the D2 global twice this last week. They don't have a fix yet either, but technically this one isn't official until it's pushed ota.
Good luck all. More news as I have it.
Sent from my DROID3 using xda premium

I can't STAND this problem! Happens to me every day at work. Heck, even if I had a widget button that I could turn on the data roaming with from my desktop would be better than having to go into settings everyday
Annoying!

Baconstrip said:
I can't STAND this problem! Happens to me every day at work. Heck, even if I had a widget button that I could turn on the data roaming with from my desktop would be better than having to go into settings everyday
Annoying!
Click to expand...
Click to collapse
So... do the update. You won't regret it

blkwlf said:
So... do the update. You won't regret it
Click to expand...
Click to collapse
I was thinking about it, but I was hoping to wait until it's officially released. Taking longer than I expected

Still happening in 5.6.890
I'm also suffering this very annoying problem, and have found no solution for it.
I'm using stock XT862 5.6.890 and I need to re-enable data roaming 20 times a day. I use a carrier in Spain that has very little owned towers so it's doing national roaming very often. Every time I switch from an owned tower to a roaming tower, I get the "Data roaming is disabled" notification and need to go to "Battery & data manager" -> "Data delivery" to re-enable it.
I have searched A LOT and tried all solutions I have seen, i.e. modifying build.prop in a myriad of ways, but it still happens.
I have also tried Minimoto v1.7 which has XT862 5.7.906 but it's even worse: It still happens but that ROM has stripped out Battery & data manager so I can't even enable Data roaming. A shame because the ROM is really awesome.
Please help a poor soul! :angel:

I finally took the problem in my own hands and managed to make a small app that re-enables data roaming at the touch of a button.
I needs to be installed as a system app for it to work, but it works! :laugh:
You can get it here http://forum.xda-developers.com/showthread.php?t=2165364

Other party cant hear me on the call!

Having a strange issue with my HTC one.
History -The phone is not rooted it's on stock 4.3 with 5.5 upgraded about 2 weeks ago.
Today I have noticed that I can't be heard by the other party when I speak on the phone, I can hear him but he can't hear me.
There is not issue when I speak on the speaker, the issue is only when I use the phone without a speaker.
I have disconnected any Bluetooth devices.
I have restarted the phone, but nothing else except of that.
Any ideas what it might be?

modesty1 said:
History -The phone is not rooted it's on stock 4.3 with 5.5 upgraded about 2 weeks ago.
Click to expand...
Click to collapse
I think you need to contact HTC support or the store where you bought it. You could try a factory reset, but it's fundamentally not your problem if you haven't done any weird modifications to the phone.

fenstre said:
I think you need to contact HTC support or the store where you bought it. You could try a factory reset, but it's fundamentally not your problem if you haven't done any weird modifications to the phone.
Click to expand...
Click to collapse
The issue is that I bought the phone in another country, so I was wondering if there is a more local solution for this, and/or is it a known issue with this phone, As it happened out of the blue!

modesty1 said:
The issue is that I bought the phone in another country, so I was wondering if there is a more local solution for this, and/or is it a known issue with this phone, As it happened out of the blue!
Click to expand...
Click to collapse
Some things you can try:
- Contact HTC anyway. It's possible they'll service your phone even though it was bought in another country.
- Factory reset (this probably won't help).
- Update your firmware.
- S-Off and test as many firmwares as you can. You may want to check your version of HBOOT, and if it's an early version, S-Off before upgrading your firmware. Because the newer firmware is unreliable to S-Off.

[Q] OTA Updates Not Downloading

My girlfriend just got a Moto X from the holiday sale last week. She bought an AT&T branded devices so she could use it on Straight Talk.
It works fine on the network, but the OTA updates would just not work at ALL. Every time it wanted to update, it would ask to be on the wi-fi network, which it already was. And if we ever got a progress bar, it just said "Will Resume when on Wi-Fi" and showed a 0% progress for over an hour.
Motorola support was utterly useless, they hung up on us, TWICE, after 2+ hours of phone calls, and the third time the level two technician, who we were told could force the update, told us we could factory reset the phone to make it work.
After THAT failed, he told us we could just mail it back to Motorola and they'd install the update themselves. At that point I just used RSD Lite to flash the 4.4 stock firmware, because it was much faster than waiting two weeks for the same thing. Now I'm not sure if the OTA updates are working still, but she's been unable to download the new boot services or active notifications apps, which makes me thing there are still problems with it.
Anyone else have these issues with OTA updates? Specifically with the AT&T variant?
Anything would be helpful!

I am having the same problem on an AT&T model purchased from the holiday sale. I tried the factory reset suggestion and that didn't work. I am actually on the phone with level two support right now hoping for a solution. I will post a follow up if anything works to resolve this issue.

I updated two Moto X's to 4.4 with no problems at the beginning of the month, but I had this same issue this past weekend when my latest Moto X arrived and I tried to update it. I finally got the update to download by tethering to my other phone instead of using my home Wi-Fi. Sucked that it used my AT&T data, but at least it worked. I researched it a bit and apparently some Motorola Android phones have had this issue before. Others said it will eventually download if you just leave it, but it could take a while. Pretty sure it's an issue with Motorola's update servers because a bunch of people will report it at once and factory resetting doesn't help.

I haven't had this issue but you can always just download the OTA manually and sideload it with adb.
Sent from my Moto X

gtg465x said:
I updated two Moto X's to 4.4 with no problems at the beginning of the month, but I had this same issue this past weekend when my latest Moto X arrived and I tried to update it. I finally got the update to download by tethering to my other phone instead of using my home Wi-Fi. Sucked that it used my AT&T data, but at least it worked. I researched it a bit and apparently some Motorola Android phones have had this issue before. Others said it will eventually download if you just leave it, but it could take a while. Pretty sure it's an issue with Motorola's update servers because a bunch of people will report it at once and factory resetting doesn't help.
Click to expand...
Click to collapse
Okay, as much as it sucks, it's somewhat comforting to hear that others are having the issue as well.
Since it was new out of box, and all Moto Support wanted to do was install it at their factory, we just used RSD Lite and pushed the 4.4 factory image.
_MetalHead_ said:
I haven't had this issue but you can always just download the OTA manually and sideload it with adb.
Sent from my Moto X
Click to expand...
Click to collapse
We just wound up flashing the 4.4 Factory Image from RSD Lite in the end. Is there a good repo for OTA zips for ATT though? I found one for an earlier update listed here in XDA (the one that brought some camera fixes), but I couldn't find any other stock OTA zips that could be applied via stock recovery outside of that one.
soxfan37 said:
I am having the same problem on an AT&T model purchased from the holiday sale. I tried the factory reset suggestion and that didn't work. I am actually on the phone with level two support right now hoping for a solution. I will post a follow up if anything works to resolve this issue.
Click to expand...
Click to collapse
If support doesn't help (they were pretty sucky towards us), you can use RSD Lite to apply the factory 4.4 image to the phone without any modifications

Tmobile version not updating either
I have the Tmobile variant. Its not taking the update either. Two different ways its prompting and not working. The first is I have a notification that the update will begin when I'm on wifi. I'm on wifi and it never starts. After reboot, I check the 'about phone', --system updates. "It tells me an update is currently being downloaded. You will be notified when the download is complete."
Waiting and waiting.....

After my second call yesterday, level two escalated me to level three. They called me this morning, (they don't take incoming calls) and the rep pushed the update to my phone. It took about 10 minutes and then the update started downloading. After a reboot I was then able to download the kitkat update. So now all is well. One of the reps at level two said he tried pushing the update to me (on Monday) but it didn't work. I guess level three has more power. Anyway, it did resolve my issue.
Good luck to the rest of you with this problem and Happy Holidays to the community.

My wife took her phone to work and connected to wifi there...update came through. I'm guessing either motorola servers cleared up, or needed a different wifi...but either way, resolved.

XT 1060 Not Receiving Texts (but can send them)

Last Friday I noticed that I stopped receiving texts on my unlocked DE running stock rooted 4.4.4. Sending texts works fine. This phone has never had any problems with anything since I started using it 18 months or so ago, and out of the blue it stopped receiving texts. I have checked Verizon's side on another phone (moved sim card to old Gnex and texts are received fine) and it is definitely a problem with my phone. I have deleted all texts, wiped caches, tried Safe Mode nothing has fixed it. Seems like some odd radio problem. I have read about the 4.4.4 issues others have had, but as I mentioned, this phone has been fine on 4.4.4 since I set it up.
In any event, I am here looking for some answers or some suggestions of what else to try. I would like to keep the total wipe and restore as a last resort, as this phone is mission critical to me for work, and being too stupid to do regular backups, resetting everything back to the way it is now would be a hardship. I do have a nandroid backup from when I originally set up the phone, and was thinking of trying that. If I wipe everything though, does that wipe the SD card too? I thought a factory reset wipes the SD card, so if so I need to back it up first.
(So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...)
Thanks in advance for anything you guys can offer!
In my case, and others, this problem was solved as indicated in post #25 by qtonic (thanks to you, qtonic!). In my case, VVM was not an issue as I did not use that feature, so I can't vouch for whether or not that problem is solved. No "factory reset" was involved, nor any "upgrade" to Lollipop was necessary, so no worries there. One important note is to backup your texts if you want to restore them after you clear the data. I did that and I am back up and running with all my old texts in place. Hopefully this fix works for everyone experiencing this issue.

Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?

cnoevl21 said:
Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?
Click to expand...
Click to collapse
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?

I am dealing with the same issue. Don't want to upgrade to lolly or do i want to factory reset. I will stay tuned to this thread and hopefully get a fix.
Sent from my XT1060 using XDA Free mobile app

amajamar said:
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?
Click to expand...
Click to collapse
i just wiped cache and dalvik. then went to lollipop. it then dawned on me that i should have tried to wipe kitkat, but when u switch to LP it screws everything up so idk if you can go back to kitkat. i may try to at some point, maybe over the weekend.
right now im just running a debloated stock LP rom and i used xposed to customize.

I just added the following to my OP.
So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...
Can you guys duplicate this?

Any solutions other than factory wipe?

Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.

ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
I went up several levels of tech support at Verizon and eventually ended up getting the same story. I need a factory reset and then all will be fine. They said it was due to some voicemail interface version not being supported anymore and my phone is trying to use the old one and it's keeping the phone from provisioning and that's why texts stopped working.
I've been putting off applying the Lollipop update because I knew it was going to have undesired consequences, but I went ahead and applied it. Text work again but of course I had to re-root (Developer Edition so no sweat there) and even with root WiFi Tether for Root Users (which had been working great under KitKat) bit the dust and no longer works. Under KitKat I had to use the special version that had some added binaries to make up for pieces that were missing from the kernel and I guess those binaries don't work with the Lollipop kernel.
So I'm using the stock tether app now (with provisioning check disabled) but I hate it. You can't turn on access control lists (to "approve" users), you can't see who's connected, you can't define an inactivity timeout, blah blah blah. It sucks so bad compared to WiFi Tether for Root Users.
Oh yeah, in the process of troubleshooting they removed voicemail from my line and put it back on. So I had to set up my voicemail from scratch and lost a bunch of voicemails I'd been saving for years including one from a friend who's dead now. Not happy.
Eh, at least SMS works again.

ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
Yes, for me it was last Thursday that it was working as well. So, that being said, I take it a factory wipe is required. A couple of questions for you guys: Since I have a Developer Edition (running Xposed) too, do I have anything to worry about about doing a factory wipe? I am currently on 4.4.4, rooted, do I need to prep anything to do the factory wipe so I don't brick? Can I stay on 4.4.4 and just re-root and reinstall my apps from TiBU? I haven't messed around with anything since setting it up over a year ago, and not really thrilled with starting from scratch...
Anyway, great sleuthing MotoCache1, seems that you got to the bottom of things. At least we can be sure it was not some other app or something causing this.

I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app

mlucht said:
I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
If you're rooted edit your /system/build.prop file, add this line to the end, reboot the phone, and then use the factory hotspot tethering:
Code:
net.tethering.noprovisioning=true
More information here if you want it.

I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....

ray4jc said:
I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....
Click to expand...
Click to collapse
That's what they told me as well. They said "take it in to a Verizon store and they will back it up and do a factory reset and then restore your data".
I decided against that and instead opted to use the VZW Software Repair Assistant tool. When you use that there are 2 options - Software Repair Assistant (which is supposed to "repair" your currently installed software) and Software Upgrade Assistant (which is supposed to update your device to the latest available software for it).
I didn't particularly want to go to Lollipop so I chose the "repair" option, chose the phone, and clicked "Repair". And it "repaired" it by upgrading it to Lollipop. Lol. Maybe it's because I had previously told the phone to go ahead and try to apply the Lollipop OTA. The OTA failed to install. Not sure why - possibly due to root and/or other changes to the system partition. I was using stock recovery.
So anyway, I ended up on Lollipop even though that's not really what I wanted to do, and that did fix the problem - though, as previously bemoaned, I can't use WiFi Tether for Root Users anymore and have to use the piece of crap that's built into the OS. I guess I should be grateful that works because I'd be in a pickle if I had to do without tether.
Back to what you posted -- I don't think anybody here has yet posted that the factory reset actually fixed the problem for them. Honestly I don't understand how it would. A factory reset isn't going to suddenly make your phone start using a newer version of anything and what I was told was that the phone was using an old, no longer supported version/protocol to access voicemail and that was the root of the problem.
I suspect that if you take it into a VZW store for a "factory reset" what you're really going to get is an upgrade to Lollipop. Lol.

@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
I chatted with Motorola and did a bunch of troubleshooting with them, they suggested trying a new sim card.

ray4jc said:
@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
Click to expand...
Click to collapse
Wow. Talk about a lame answer. Nothing on the phone changed. Nothing on the phone broke. Obviously Verizon changed something on their side and rather than back out, or fix it, they want to shift the problem to the device owners.
At least you know you can probably fix it by going to Lollipop (so far that seems to have fixed everyone that has posted here) but that comes with some negatives. I'd rather still be on KitKat personally, but I put too much time into it already so I'm just going to be satisfied that it's working and try to forget how much I hate the factory tether piece of crap.

Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?

domenci said:
Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?
Click to expand...
Click to collapse
Were you rooted prior to factory reset? Did you need to re-root? Did the factory reset wipe the SD card? I want to fix this without upgrading to lollipop if possible

Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).

domenci said:
Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).
Click to expand...
Click to collapse
I did try a factory reset and it didn't work. Of course I'm running the eclipse 4.4.4 ROM not sure if that matters.
Looking in TiBU I've only got a few Verizon apps, none of them appear to be for voicemail the only thing that says voicemail is the phone 4.4.4-26 (19) app.
I'd love to stay on 4.4.4 if possible.
Otherwise I need to figure out which ROM to go to next.

Nexus 6 LTE connecting issues... strange!

My rooted Nexus 6 and my sons stock Nexus 6 are having a lot of trouble connecting to LTE on Tmobile. I have to go to APNs, reset to default and reboot every hour or so. I did no changes to my phone.
Apparently, this is happening on other networks too.
Can anyone shed light on this? Some back door google update.
tMobile says no changes on their end. Also, other carriers are having this issue, ONLY Nexus 6.
PS - apparently , this has happened before too
http://www.idigitaltimes.com/nexus-6-problems-how-fix-mobile-data-connection-failure-issue-440151

flash a different radio/modem.

Same here. Just spoke to T-MOBILE and rep said it is an issue with a lot Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Edit: change all to a lot

wolfeyes30 said:
Same here. Just spoke to T-MOBILE and rep said it is an issue with all Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Click to expand...
Click to collapse
I got the same answer.
I did flash the 5.32 and 5.34 modems. No dice.
Then I tried Developer preview 5.39. It's been working for 15 minutes, which is a long time since the issue cropped up.
What a pain!

Not sure if my issue is the same, but for the last couple days Textra fails to send a text unless I reboot. Even a reply to a just received text fails. I have tried a couple different radios but neither has helped. I am also on a T-Mobile Nexus 6 stock rooted with the August 6.0.1 security update.

JimSmith94 said:
Not sure if my issue is the same, but for the last couple days Textra fails to send a text unless I reboot. Even a reply to a just received text fails. I have tried a couple different radios but neither has helped. I am also on a T-Mobile Nexus 6 stock rooted with the August 6.0.1 security update.
Click to expand...
Click to collapse
That is probably the same issue. I can receive texts, but can't send without a reboot.
So far.. the 5.39 developer modem has kept connection for an hour. Which is good considering how intermittent it was.
What really blows is that my phone and service was perfect until this event.
Even in the mountains of the Philippines last year, my phone worked perfect.

You may try dp5 my WiFi and Mobil got a lot better, but I'm not on t mobil. Flashing only the radio is maybe not enough, if you are on stock anyway you have nothing to loose

Check out Reddit for the growing thread on this issue. Happening with Nexus 6 users on different carriers around the world. Some GPS connected apps like Pokemon Go & Lyft will bork LTE connectivity. Probably a Google play services issue. Will be using my OnePlus one today just in case.

tmicrd68 said:
Check out Reddit for the growing thread on this issue. Happening with Nexus 6 users on different carriers around the world. Some GPS connected apps like Pokemon Go & Lyft will bork LTE connectivity. Probably a Google play services issue. Will be using my OnePlus one today just in case.
Click to expand...
Click to collapse
Interesting.. I hit the speedtest app right after a reboot to check, and it immediately borked my connection several times in a row. I like your theory..

wolfeyes30 said:
Same here. Just spoke to T-MOBILE and rep said it is an issue with all Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Click to expand...
Click to collapse
its NOT an issue with all n6 users on tmobile. i have a nexus 6, since nov 2014, and have never ever had that issue on tmobile. been on tmobile since the early 2000's..

Jeff_in_LA said:
My rooted Nexus 6 and my sons stock Nexus 6 are having a lot of trouble connecting to LTE on Tmobile. I have to go to APNs, reset to default and reboot every hour or so. I did no changes to my phone.
Apparently, this is happening on other networks too.
Can anyone shed light on this? Some back door google update.
tMobile says no changes on their end. Also, other carriers are having this issue, ONLY Nexus 6.
PS - apparently , this has happened before too
http://www.idigitaltimes.com/nexus-6-problems-how-fix-mobile-data-connection-failure-issue-440151
Click to expand...
Click to collapse
wolfeyes30 said:
Same here. Just spoke to T-MOBILE and rep said it is an issue with all Nexus 6 users. They kicked me off the network and it work for a bit but I'm still losing data. She said their tech department is working with Google for a fix.
Fyi...Flash 3 other radio's and it doesn't make a difference.
Click to expand...
Click to collapse
Jeff_in_LA said:
I got the same answer.
I did flash the 5.32 and 5.34 modems. No dice.
Then I tried Developer preview 5.39. It's been working for 15 minutes, which is a long time since the issue cropped up.
What a pain!
Click to expand...
Click to collapse
JimSmith94 said:
Not sure if my issue is the same, but for the last couple days Textra fails to send a text unless I reboot. Even a reply to a just received text fails. I have tried a couple different radios but neither has helped. I am also on a T-Mobile Nexus 6 stock rooted with the August 6.0.1 security update.
Click to expand...
Click to collapse
You guys have a lot of company... > http://www.androidpolice.com/2016/08/04/some-nexus-6-owners-report-data-outages-on-t-mobile/

I'm running stock N6, not rooted; bootloader locked; on T-Mo. While on WiFi, with WiFi calling enabled, I would get out of range of WiFi and cel data would not return without full reboot. If I disable WiFi calling before leaving WiFi service, cel data flipped as normal. I tested again with manual WiFi disable and if WiFi calling was on before the cut out, cel data never flipped on.
[Edit] I did notice though that when it does flip like it's supposed to, I'm connected at 3G. LTE doesn't kick on.

simms22 said:
its NOT an issue with all n6 users on tmobile. i have a nexus 6, since nov 2014, and have never ever had that issue on tmobile. been on tmobile since the early 2000's..
Click to expand...
Click to collapse
Stated what T-Mobile told me.

Ok, I did flash the beta radio 5.39.
It might be coincidence, but my phone has a solid connection for three hours now.
Hopefully they fixed it on their end.

I am not seeing this on my N6. Still on 5.1.1 LVY48H.

toastgodsupreme said:
I am not seeing this on my N6. Still on 5.1.1 LVY48H.
Click to expand...
Click to collapse
what radio can work on 5.1
Cause i have flyme rom, but have calls issue, ian not receiving any call. The other end saids it rings but my phone does not ring at all on calls.

It seems to be affecting some people, but not others. It also doesn't seem to be related to ROM, carrier, kernel, or radio versions. There are people all over the world on different carriers having the problem.
The symptoms I see are that I can't connect to any type of cellular data. Voice and SMS seem to work though. WiFi data works fine. GPS use seems to make it more likely to fail. Speedtest.net, Pokemon Go, Ingress, and Google Maps have been used to reproduce it.
The only thing I've found that seems to help is to freeze "Google Connectivity Services" using Titanium Backup. You might also try uninstalling updates, though it will just re-install. If it is related to that, it would make sense as the rollout of updates via Play Store are staged, so people would get the update at different times. I froze it about 4 hours ago and data has been solid with GPS use, LTE and HSPA tested. I also tested switching between WiFi and Cellular without issues on Tmobile-US. That's the only SIM I have, so I can't test other services. I couldn't seem to get a data connection for more than a few minutes before, so it's a huge improvement in my case.

ttabbal said:
It seems to be affecting some people, but not others. It also doesn't seem to be related to ROM, carrier, kernel, or radio versions. There are people all over the world on different carriers having the problem.
The symptoms I see are that I can't connect to any type of cellular data. Voice and SMS seem to work though. WiFi data works fine. GPS use seems to make it more likely to fail. Speedtest.net, Pokemon Go, Ingress, and Google Maps have been used to reproduce it.
The only thing I've found that seems to help is to freeze "Google Connectivity Services" using Titanium Backup. You might also try uninstalling updates, though it will just re-install. If it is related to that, it would make sense as the rollout of updates via Play Store are staged, so people would get the update at different times. I froze it about 4 hours ago and data has been solid with GPS use, LTE and HSPA tested. I also tested switching between WiFi and Cellular without issues on Tmobile-US. That's the only SIM I have, so I can't test other services. I couldn't seem to get a data connection for more than a few minutes before, so it's a huge improvement in my case.
Click to expand...
Click to collapse
T-Mobile acknowledges the issue. The one universal is that it's with the N6, not with other phones. There are a bunch of carriers around the world that are having the problem.
When mine breaks, SMS fails. The only mobile connectivity available to me is phone calls.
The Reddit thread mentioned above has people saying that disabling Location Services works. Far from ideal over time, but if it's true, it's something. I tried that. We'll see how it goes. Freezing Google Connectivity Services is nice, if it works without introducing other problems, because it would allow us to keep using whatever connectivity we like without data breaking.
I had a Bluetooth connectivity problem a year or more ago that surfaced literally out of nowhere and on every device I tested, a little more than ten of them. This was independent of ROM, root status, device, anything. The feature in question worked on every Android device we had tried one day (and for more than a year prior) and failed on every one the next. Sounds crazy, but it's what happened. Google barely paid attention to my bug reports and ran me in circles when they did. Never got fixed.
I trust this matter will.

Both my nexus6s are doing this with heavy GPS aps, data will shut down.
Sent from my Nexus 6 using XDA-Developers mobile app

I've had GCS frozen for a long time, running 5.39 radio & it happened to me. There is definitely something occurring substantially with our devices/network be it software or hardware based. Apparently T-Mobile & Google are working on it but the fix might not come until next week. I'll probably install latest N preview when I get home.