Related
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Kraizk said:
Have you tried simply running the latest RUU and reverting it back to stock?
**edit** http://www.htc.com/us/support/news.aspx?p_id=629&p_name=htc-one-sprint
Click to expand...
Click to collapse
Yes, twice
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
I'm going to try this now thanks
jamesissocool said:
This is not an uncommon problem but it happens with certain HTC ones and not others. I have helped a few other people with this issue. Most likely, your current ROM is set to RUIN/SIM in Settings-> More-> Mobile Network -> Subscription settings. It needs to be set to NV. If you can't get to this setting, you need to flash a ROM that has the setting available. CM 10 based ROMs all seem to have it. If your phone does not automatically reactivate, you can flash to a stock ROM and use the handsfree activation function and that should get you back up.
Click to expand...
Click to collapse
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Kdenery said:
Okay so i just flashed a CM 11 build. and Holy S*** I have ******* service! I cant make calls, it says it's not authorized. And i don't see the option you were talking about, in mobile network, i see , Data Enables, Data Roaming, Preferred Network type, System select, (then grayed out) Access Point Names and Network operators, (then not grayed out) carrier settings. When i click carrier settings it says "Unfortunately, the process com.android.phone has stopped. and it takes me back a screen.
where do i go from here?
Click to expand...
Click to collapse
Try flashing a CM10 ROM. I've always seen the option there. The kitkat ROMs I have used do not have the option except for the Nocs GE.
Kdenery said:
Hello, everyone, I'd like to share my experience, get any help if someone can, and warn some future people.
So a few months ago i rooted and ROM swapped my HTC one. It was great, I loved it, it was fast and simple.
I tried to change the ROM on it the other day and everything went down hill form there. Basically I ended up having no service and everything else seeming to work fine. So after spending an entire day trying to fix it with BD619, i had to call my carrier today. Now i have the sprint phones, and the sprint service, but i have Credo as a carrier. God knows why. They essentially gave me nothing saying my phone must be bricked and they can't help me.
One thing they did try however was to have me put in a ##xxxxx# number, and there i saw and could edit my MDN and MSID, instead of showing my my phone number and the MSID number they both had "No" written. So he had me edit it and put it in, but when i click "commit changes" it said "commit failed" so if anyone knows anything about that or could help me there, it'd greatly appreciated.
Lesson is, even if you think you know what you are doing, and are careful, weird stuff can happen, and if you have an Odd carrier version of an already less support model of phone (the sprint version), then be EXTRA careful.
Click to expand...
Click to collapse
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
-TheEdge- said:
The only way something like this happens is one of two things.....
1. Ur a noob
2. Your a dev and your testing ril on your rom
The only way to fix this which is a cleared meid of some sort......flashing cm10.1 is the only way and aquiring service by switching to nv....once there everything is fixed just flash/restore back to your rom.
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
i'd kinda like to argue a point here as this just happened to me. i am certainly not new to flashing, starting back with the mogul and having almost every sprint smart phone since then unlocked (windows) or rooted (webos and android).
Using TWRP and previously running ecliptic 4.3 i wiped caches, system and data then installed the 4.4.2 from team d3rp and voila... no service no meid no nothing.... yes i have the latest radio on my phone.
i guess my point in this is that there's a number 3 that you didn't mention.
3. sh!t happens and it's not n00b related.
for anyone else that has this issue... flashing CM 10.1 worked for me. i didn't even have to set up anything, it just picked up signal. so i rebooted, wiped and nandroided back to 4.3 and all is well.
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Robert542 said:
Did you flash a rom that was meant for another carrier?
Sent from my SM-N900P using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I didn't... it was SuperOneK. i'm certainly not blaming the rom though. especially not when others are flashing it fine. the ONLY thing i can think of possibly happening is a bad download. I was in a rush and didn't check the md5.
I had a similar problem when flashing miui. Nothing worked. Even went back to a sense backup and nothing worked.
Commit failed as well.
Here's what I did to make it work again.
Flashed cm10. Change the network settings for CDMA. (Boom it SAID I had service..but didn't).
Rebooted a few times (probably not necessary).
Flashed a sense 4.3 ROM that was close to stock.
Update msl and all that. Commit.
For me..changed LTE/CDMA to just CDMA (no 4g in wv).
Boom it worked again. Hope this helps!
Sent from my HTCONE using xda app-developers app
any one getting opps! you need a data connection two check for updates
go two settings Wi-fi two set up a connection now
you can also visit motorola.com/systemupdates two see other update options
when i check for updates for this AM on both 3G and on wi-fi did not see that Message i have all ready reset my phone back two when i 1st got it two see if that fixed any thing but still getting the Message
so am makeing this fourm two see if any one other then me thats getting the same Message on there moto x phones when checking for OTA android updates i have the moto X XT1050
looks like its been fixs if any mods passing by and looks in two fourm they may now closed it
Yep.
phippsy84 said:
Yep.
Click to expand...
Click to collapse
so its not this me then i wounder if any one else is getting it
Snow755 said:
so its not this me then i wounder if any one else is getting it
Click to expand...
Click to collapse
I'm on Verizon too so it isn't carrier related.
phippsy84 said:
I'm on Verizon too so it isn't carrier related.
Click to expand...
Click to collapse
well am with golden state cellular
http://www.goldenstatecellular.com/
its back
opps! you need a data connection two check for updates
go two settings Wi-fi two set up a connection now
you can also visit motorola.com/systemupdates two see other update option
any one else?
I'm getting it on att in USA it just started within the last hour
Sent from my XT1058 using Tapatalk
Strange thing has happened to my beloved N6. This was a Tmob purchased device. Activated on via an existing VZ sim & been working since day 1 no prob. However, about 3 hours ago or so, its lost all its cellular data. Tried reboot, take sim in/out, etc. No luck.
Also, under Network Operators, choosing VZ and trying to register fails - Selected network (Verizon) unavailable
Anyone seeing similar behavior?
By ANY chance, did you put the TMobile SIM back in? For whatever reason, when I did that, I had to factory reset my device to get it to recognize the VZW SIM.
buddhatown said:
Strange thing has happened to my beloved N6. This was a Tmob purchased device. Activated on via an existing VZ sim & been working since day 1 no prob. However, about 3 hours ago or so, its lost all its cellular data. Tried reboot, take sim in/out, etc. No luck.
Also, under Network Operators, choosing VZ and trying to register fails - Selected network (Verizon) unavailable
Anyone seeing similar behavior?
Click to expand...
Click to collapse
anaphora68 said:
By ANY chance, did you put the TMobile SIM back in? For whatever reason, when I did that, I had to factory reset my device to get it to recognize the VZW SIM.
Click to expand...
Click to collapse
I dont think so, but there are an awful lot of sims floating around my house. Strange as it happened mid morning after I had been using data for quite some time. Then poof. No signal.
What state you live in? Indiana has had a blackout for all cell carriers since yesterday/today around knox,greene, and other counties. Bloomington, columbus.
That really, really sucks. Is it possible that Mobile Data is out in your area?
buddhatown said:
I dont think so, but there are an awful lot of sims floating around my house. Strange as it happened mid morning after I had been using data for quite some time. Then poof. No signal.
Click to expand...
Click to collapse
VZ data was ok for co-workers, so data was def good.
Ended up doing a factory reset, and all is good again. I can see a difference in my Cellular Network Screen though...
When I first got it, it was using 'Global' as the 'Preferred Network Type'. When it was busted early today, that was set to LTE with no option for Global. Also, earlier, it would let me scan for available carriers...now after the factory reset...its locked into VZ once again.
I didnt do anything, to my knowledge, to cause it to do any of this...And thats the scary part.
buddhatown said:
VZ data was ok for co-workers, so data was def good.
Ended up doing a factory reset, and all is good again. I can see a difference in my Cellular Network Screen though...
When I first got it, it was using 'Global' as the 'Preferred Network Type'. When it was busted early today, that was set to LTE with no option for Global. Also, earlier, it would let me scan for available carriers...now after the factory reset...its locked into VZ once again.
I didnt do anything, to my knowledge, to cause it to do any of this...And thats the scary part.
Click to expand...
Click to collapse
I saw a post somewhere about changing some APN settings from ipv6 to ipv4 but Verizon doesn't have these or do they?
crashercarlton said:
I saw a post somewhere about changing some APN settings from ipv6 to ipv4 but Verizon doesn't have these or do they?
Click to expand...
Click to collapse
here you go.
http://apn-settings.com/verizon-4g-lte-apn-settings-detailed-configuration-steps/
Happened to me as well. I'm unlocked and rooted on a custom ROM. It just happened to me 2 hours ago. I had to reflash the ROM to gain service again. Bought from Motorola and used on Verizon with an activated sim.
Here too. Motorola bought using an activated verizon sim. Happened a few times. Once in a well covered 4g area. That time recovered on it's own.
Last night happened again. Reboot didn't fix, but airplane mode toggled on and then off did the trick.
I had to flash my ROM again and go through activation before I was able to regain service again. Not sure what happened.
This has been happening to me since last night. The signal icon shows I have half signal, but no LTE and it has an exclamation point on the bars.
idksomuch said:
This has been happening to me since last night. The signal icon shows I have half signal, but no LTE and it has an exclamation point on the bars.
Click to expand...
Click to collapse
Are you running a cm based ROM? Some cm Roms have different RIL's and can cause this. Mine is clean stock ROM so I'm not sure why it happened.
selayan said:
Are you running a cm based ROM? Some cm Roms have different RIL's and can cause this. Mine is clean stock ROM so I'm not sure why it happened.
Click to expand...
Click to collapse
It was actually my T-Mo account. It was suspended for having an overdue bill. It was our first bill with T-Mo and they never informed me that we were not signed up for paper bills, only paperless. I just made the online payment 20 mins ago and everything is working fine for everyone on our account. I also changed our paying options to paper billing. Thanks though!
idksomuch said:
It was actually my T-Mo account. It was suspended for having an overdue bill. It was our first bill with T-Mo and they never informed me that we were not signed up for paper bills, only paperless. I just made the online payment 20 mins ago and everything is working fine for everyone on our account. I also changed our paying options to paper billing. Thanks though!
Click to expand...
Click to collapse
You guys were starting to scare me here as I haven't had any issues.
Had to post... That is an awesome screen name
Larzzzz82 said:
You guys were starting to scare me here as I haven't had any issues.
Had to post... That is an awesome screen name
Click to expand...
Click to collapse
Well with my issue I have no idea why I lost service. I notice that with any ROM you flash the cell network on version stays on global. Even stock, I had mine set to LTE which said recommend but that may have been why I lost all service and had to reflash to get it back.
Fastboot oem config carrier vzw
Sent from my Nexus 6 using XDA Free mobile app
poitee said:
Fastboot oem config carrier vzw
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
What does this do?
selayan said:
What does this do?
Click to expand...
Click to collapse
+1
According to the cyanogenmod wiki it fixes the vzw data problems.
Hello everyone,
Informations
Phone : Nexus 6
ROM : Euphoria OS 1.0 with included kernel
I have a little problem with the phone network...
I have just install the ROM (3days ago) and everything worked fine.
After the first reboot, I had a network problem: no more network (just phone)
Bluetooth is OK,Wifi also ect...
No extra apps installed.
Any idea?
Thanks
Edit : French phone/network (FreeMobile)
I am having issues over here also. My data randomly stopped working on my way down to memphis, randomly would start to work again. I tried a new rom, it slightly got better, but would cut out of data every 5 min. Kinda got it better by switching to tmo in the apn's. Now just installed sinless, and it is no longer working again.
So, same problem and no fix...? :/
Holy cow! I thought I was the only one! I mean this problem really sucks(and I have wasted a lot of my hours trying to fix it), and have been thinking of creating a thread on this problem until I saw yours.
Okay let me start with what I'm on:
N6: 64gb blue
Rom: Stock
Rooted: Yes
Any other modification: No, only think I did was unlock and do chainfire su root.
Network: VZW
I have had this phone since Dec with no issues other than random reboot every so often.
Now to the problem I had, I went out to the middle of MO for a weekend get away (on Feb 14th). The whole time I was out there it showed 1x even though I was still getting LTE speed. Didn't think much of it until we moved further into the hilly parts of MO were I lost service. Thought it was just where we were at, and thought it would come back once we got back to the hotel we were staying at. It never did. It would say "No Network found" only allow 911 calls.
Spent the next 4 days working With VZW with several trips to the store, and talking to tech support. They made sure my IMEI was not blocked on their side. We used several sim chips, they would all do the same thing, quickly connect then disconnect and go back to no service.
So I did a factory reset, still didn't help. I finally did a fastboot flash of 5.0.1 stock again, this fixed the issue. Until I used titanium backup to restore my sys setting. Then it would drop and not reconnect after the reboot. So I did fastboot flash again and it hasn't happened again since last Thurs. I just restored my app's again to make sure it wouldn't fail to connect over the weekend, and rebooted several times. No issues so far, but I called Motorola and they are RMAing me a new one, because I don't have any trust in this one anymore. They are out of 64gb ones, and they will get back to me in a week.
Questioned to anyone who has gotten a RMA from Motorola:
Are their "like new" replacements okay? I got a few from them when I had my droid x, and they were crap. So I wasn't sure if that is still the same for the N6 or not. I have a feeling its not, but just wanted to get other peoples input on that process.
Thank you for creating this thread, and for everyone's time!
Edit: Had the same issue network wouldn't work, however WIFI, Location, Bluetooth would.
Check your APNs..... make sure you are on the correct one, and that both of APN protocols say IPv4.
Sent from my Nexus 6
APN is for Internet(3G) and MMS, no?
Because we have a phone network (call & SMS) issues.
On my side, APN are OK, but still don't work...
Edit: New !
Everything works fine on :
- Paranoid Android 5 Alpha 1
- Chroma (Latest)
But not work on :
- Euphoria
- Stock ROM
Edit 2 : It works now !!
I seen that I had several issues around the APN side. I mean, I can't add APN, sometime I can. Sometimes APN reseted themselves, sometimes it was OK. Then, I had read the solution above: security tab.
I had just remove my 3rd party lockscreen (HiLocker). Restart the phone and voilà ! After the reboot, my phone ask me the pin code, and all APN are here.
I hope it can help...!
Some times I will see the APN settings, and sometimes I won't. Right now I don't. When it does show up it shows VZWINTERNET selected. There are ton of other options, but they don't work either when the problem was seen.
Is what your experiencing data going in and out? I'm on Sprint and I thought maybe it was just an issue with Sprint. I have or need to read up more on APN because it does get bothersome. I even have issues where sometimes my SMS gets hung up for minutes in sending mode before they actually send. Would be nice to have this corrected.
Sent from my Nexus 6 using Tapatalk
Casper34 said:
Check your APNs..... make sure you are on the correct one, and that both of APN protocols say IPv4.
Sent from my Nexus 6
Click to expand...
Click to collapse
This solved my problem. One of them was on IPv6.
T-Mobile Nexus 6; 32GB
Thanks!!
xjedi said:
This solved my problem. One of them was on IPv6.
T-Mobile Nexus 6; 32GB
Thanks!!
Click to expand...
Click to collapse
The thanks should go to @Circaflex though... he told me how to fix my issue and thought it could be useful here. I'm glad it was.
Sent from my Nexus 6
Casper34 said:
The thanks should go to @Circaflex though... he told me how to fix my issue and thought it could be useful here. I'm glad it was.
Sent from my Nexus 6
Click to expand...
Click to collapse
No my whole problem was that it would drop and no matter what I would do wouldn't reconnect to the network. I tried a lot of things to fix it (see above). APN would appear and then disappear from the menu. Right now its working on the network as of last Thurs. and APN options is not there.
collegencmc said:
No my whole problem was that it would drop and no matter what I would do wouldn't reconnect to the network. I tried a lot of things to fix it (see above). APN would appear and then disappear from the menu. Right now its working on the network as of last Thurs. and APN options is not there.
Click to expand...
Click to collapse
The APN option will not show for a CDMA Carrier, Sprint or VZW, in your case VZW. APNs are set by the Sim from Verizon so you shouldn't be messing with those, nor should the option show up under mobile network settings.
It was like you. Sometimes network was OK, and sometimes, it was down...
So current working theory is that it was a software issue that cause the problem. I'm just unclear as to why it happened, and how to stop it from occurring again . I do have OpenDNS enabled on the phone, could that cause the problem?
Heres my problem, I'll drop out of an LTE zone, and 3G/HSPA will come on line. Only if its on 3G I never get any data, and sometimes with HSPA too. Not until LTE comes back on line again, but then if I'm trying to stream say music 3G/HSPA wont let LTE take over again for a pretty long while.
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.