Much to my dismay, I think device is dead, bit I was more wondering if anybody else has run into this at all. To preface I'm currently traveling in Europe, phone worked fine from the 17th of October. I have the International Data and every thing was peachy till last night when it stopped associating to the cellular network. I had been using wifi calling to home till I started getting the red wifi calling icon saying invalid sim. I started looking at settings and noticed APN settings we gone and it couldn't search for networks.
I tried restarting, puling sim, then I tried a factory wipe, ultimately culminating in the pictures attached below. I also attached a picture of the bootloader for added info.
I called into T-mobile, 5 representatives and an hour and a half later was told that the only way that I was going to get a replacement is to go return it to the store where I processed my pre-order, and that needs to be done within 14 days. I'm going to try today to see if Samsung can do anything for me, but this seems more of a hardware failure that should be covered by the manufactured warranty.
I do have JUMP but I don't feel I should have to pay the deductible for this.
:TLDR:
I've not rooted, flashed or other wise modded my phone, anybody else run into this?
numbawon said:
Much to my dismay, I think device is dead, bit I was more wondering if anybody else has run into this at all. To preface I'm currently traveling in Europe, phone worked fine from the 17th of October. I have the International Data and every thing was peachy till last night when it stopped associating to the cellular network. I had been using wifi calling to home till I started getting the red wifi calling icon saying invalid sim. I started looking at settings and noticed APN settings we gone and it couldn't search for networks.
I tried restarting, puling sim, then I tried a factory wipe, ultimately culminating in the pictures attached below. I also attached a picture of the bootloader for added info.
I called into T-mobile, 5 representatives and an hour and a half later was told that the only way that I was going to get a replacement is to go return it to the store where I processed my pre-order, and that needs to be done within 14 days. I'm going to try today to see if Samsung can do anything for me, but this seems more of a hardware failure that should be covered by the manufactured warranty.
I do have JUMP but I don't feel I should have to pay the deductible for this.
:TLDR:
I've not rooted, flashed or other wise modded my phone, anybody else run into this?
Click to expand...
Click to collapse
If you traveling I think phone needs an unlock code and a different Sim card. WiFi calling probably just updated it self and kicked you off.
NOTE 4
BACARDILIMON said:
If you traveling I think phone needs an unlock code and a different Sim card. WiFi calling probably just updated it self and kicked you off.
NOTE 4
Click to expand...
Click to collapse
You don't need a new sim to travel with. I've used my sim and carrier many times in UK and Germany with out issue, you just get to pay a premium for roaming.
If I wanted to use a local carrier and then the local rates, then I need to be unlocked and then a local carriers sim.
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.
Hello everyone.
I'm on a T-Mobile ONE plan and I've been abroad for almost 6 months now and for the past 5 months everything was working smoothly until this past month I've been getting some very annoying issues.
1) WiFi Calling no longer works and only works very rarely once every couple days for only a few hours. I keep getting the error message: ER081 - Unable to connect. This happens no matter which router i'm connected to.
I called T-Mobile about it and they said this was a known issue by Samsung. Samsung gave them a list of things to go by to try and troubleshoot the issue with a master reset being the last resort (which I cannot do). There are no timelines for if an update will be released that will fix this issue.
2) International Roaming no longer works 100% of the time. I keep getting a "No Service" notification with the message "Selected network (Vodafone) not available". (even though it shows 5 full bars). I have to constantly shutdown or pull out the battery and remove the SIM card, put it all back and turn the phone on for the network to come back again. However, this fix is very temporary as the error message comes back either after a few hours or after a few minutes (some times just 1 min!).
During the same T-Mobile call, we ran through a bunch of troubleshooting stuff but nothing was fixed and everything seems fine on their end. My SIM card was in good condition, networks are available, etc.
Are there any known solutions to fixing these issues or do I have to through in the towel and purchase a new phone?
Thank you,
Been experiencing "invalid SIM" error messages on Google Fi after the Pie update. It seems to happen when trying to connect to Sprint. I've tried removing the SIM, reactivating, factory reset. Nothing works.
Anyone else having this problem? It's happening on both my X4 A-1 and my wife's X4 A-1.
Happened to me. Thought I scratched my SIM when adding an sd card to the phone after upgrading to Pie. I contacted Fi and was sent a new SIM which hasn't fixed the issue. Factory reset and reflashing the upgrade didn't do anything.
Same here, my normal use is sprint...startup of sim is configuration of sprit dm... Get sim icon then searching in cell triangle. Signal info App data shows correct sim data for Sprint tower. After twice would access cell site but never got data connection or cell phone even though signal info app would show connected. Then fail, tried to access us cellular but complete sim failure. Removed sim returned to my "daily" Pixel working normally. I guess a push update in the future for us Fi base...have read this happening on first devices that went to Pie way back in August..... Our great android ONE .....
Different waters, same boat
I'm having the exact same issue. Wish I would have waited to take the update.
Same problem here. Restart doesn't help...tried all suggestions on the web using repair codes...only thing left to try is factory reset but have read that doesn't fix it(anybody here tried?).
Sent from my SM-T350 using Tapatalk
Google is aware of this problem and said they're working on a fix.
dgt02 said:
Google is aware of this problem and said they're working on a fix.
Click to expand...
Click to collapse
In troubleshooting I am now getting the same error using my Moto X4 Amazon prime version on 8.1. I was playing around with the various repair codes to understand how they would react compared to my wifes Moto X4 Android One 9.0. I started to get invalid sim error after repairing on Sprint. Now I get the same errors on both 8.1 and 9.0 (invalid sim switching to Sprint). Looks like the problem is a little deeper and more complex than just the Pie upgrade.
At least both still work on Tmobile (the strongest carrier locally). Anxiously awaiting a fix.
A friend at work told me today he saw the invalid sim message and he is a regular Sprint customer so I agree this seems to be a Sprint issue.
It's not just X4A1 models. Regular X4 also. However, my X4A1 was purchased from Google. Quite a disappointing intro to Fi.
I bought 3 Moto X4s for my wife & kids directly from Google Fi. Kids are on Oreo & the wife is on Pie. All 3 phones get the dreaded Invalid SIM error when switching to Sprint. Now, every now and then, I can force connect to an "Unknown Carrier" with Mobile Network Code (MNC) 310-000 (Sprint is 310-120 & T-Mobile is 310-260). When connected to MNC 310-000, I got speeds of up to 74Mbps (I triple checked that wifi was off!). I believe that Sprint is doing network upgrades & for some reason the Moto X4 phones can connect to their test network but not their live network. Anyone else have any insights?
My Fi Moto X4 is Pie same thing. I also have US Cellular in this area and I can if Forced, connect to US Cell but oddly will always revert to T-Mobile. T-Mobile is zero most of the time but will never just try the other two in my coverage area. On Sprint will sim lock, which in the end is which of course locks it up.
I have 2 Pixels (first) Nov, Dec google factory images when were released I found same thing, but a 50-50 to get Sprint to show sprint dm services and complete....registering to specific tower coverage+sim + imei? When working on Sprint would always switch to T-Mobile. Now in the good old days would never go to T-Mobile, Sprint was preferred, then US Cellular, then if found any signal T-Mobile. Jan Images work so far with NO SIM LOCK. I can on my Pixel use a radio.img from Oct 18 and will work like the past on Dec images. So........waiting for "monthly" two months later updates, I guess.
I seem to be having issues with wireless charging on my 4xl after oct update. Some posts of google seem to also say same. Phone charges wirelessly fine when off. but not very reliably when on..
https://support.google.com/fi/thread/69915042?hl=en
anyone here also seeing this?
Yep, I have had "alignment issues" with wireless charging since the last update. Annoying.
I am having the same issue with my 4XL
At first I thought is was my pixel stand but I tried a new stand and other new wireless chargers but it failed to charge on any of them - The chargers all work fine, even the original pixel stand as they charge other phones with no issues.
I spent 2 consecutive days talking with Google support trying everything that was suggested but nothing worked - They have now decided to replace my 4XL under warranty.
Just to add...
I received my replacement phone today and it is till on Android 10 and everything is working as it should.
I am hesitant to update this to 11 so will be leaving things as they are for now
mine stopped working all together after the update to october patch. google said for me to go to ubreak i fix for repair.
"A week ago I got the 10/5 security update. After the reboot I had a "No Service" cell status. After doing all the normal trouble shooting stuff, I did a factory reset. Surprisingly, I still had the "No Service" status. I also noticed that after the factory reset the device was still on the 10/5 update. I got a new sim from att and tried it on other devices and it works fine.
So I chat google support, they give me a little run around, but eventually I get an RMA device shipped to me.
A few days later I get the RMA device working as expected, things are fine. Then I get hit with the 10/5 update. I decline and decline, but eventually it rebooted and installed itself.....and again "No Service", but also this time, wifi is having issues too, connected to the network but "network has no internet". The network 100% does have internet.
So now I have 2 pixel 4 XLs with no cell connectivity and 1 with no wifi.
I've chatted google again, and they want to send me a 3rd phone, I'm all but convinced there's something broken with the security update.
Has this happened to anyone else (there are a few mentions on the pixel forums)?
Any advice for me?
info:
pixel 4 xl unlocked
att network
Android 11 build RP1A.201005.004"
https://forum.xda-developers.com/pi...ity-update-t4182401/post83805855#post83805855
Mine had to be replaced under warranty. I thought that it was the Oct update and I did update the replacement and everything was working fine. So I believe that the issue people are experiencing is hardware related and not software.. I took mine to uBreakIfix under Google warranty and that didn't work, so Google ended up sending a replacement.
lanypr said:
Mine had to be replaced under warranty. I thought that it was the Oct update and I did update the replacement and everything was working fine. So I believe that the issue people are experiencing is hardware related and not software.. I took mine to uBreakIfix under Google warranty and that didn't work, so Google ended up sending a replacement.
Click to expand...
Click to collapse
Have you checked to make sure you are indeed using the latest update?
How long ago did you update?