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?
Related
WIth five bar and over 1mbps on download test via 3G, I keep getting
"Unable to communicate with ATT server" for Software Update.
Anyone else getting the same message?
I got the same message. I don't know what to do.
Sent from my SAMSUNG-SGH-I897 using XDA App
I wasn't able to. I tried everything and finally was able to put my phone back to the stock settings. Nothing worked. Contacted AT&T and they had no idea. Finally to save myself any trouble I just contacted Amazon, who I bought the phone through, and they are sending me a new phone that should arrive tomorrow.
I spoke with business care yesterday and qouted my/same error message. Whether or not she knew what she was talking about.....who knows, but she said since it was a push I didn't need to "check for update" and that it would happen automatically. Sounded like scripted response to that particular error. I am already running leaked JH7 and noticed significant GPS improvement over stock, JH2 and JH3. Curiosity was getting best of me so I have tried twice since update was available. Very happy with phone other than hesitant "back" button since installing leaked JH7 and removing all bloatware no need to update really until Froyo 2.2
Okay so I have done nothing to my phone other than download apps from the market. I have not rooted or sideloaded or lag fixed or whatever.. wouldn't know how. I also have a brand new sim if that matters or not.
I am getting a message a few minutes after I check for updates that says "Connection Failed, Unable to connect to the AT&T servers". Any idea why this is happening? As I said, I have not done anything to the phone other than download stuff from the market.
I have done this the last 2 days and the same thing happend both times. I don't want to change the date on my phone so i waited the 24 hours. Also as a side note.. I have checked for software updates 2 other times prior to this just for giggles. Once about a week or so after I got the phone and I got a message that said no updates and than again a few weeks ago and it did the same thing it did yesterday and today.. the connection failed message.
I would just wait a couple days then try again. There looks to be nothing you can do on your side. Since the update is rolling out in stages, I bet those who can't connect aren't "allowed" to update yet.
Yesterday the update completely bricked my phone. I exchanged the phone last night and again today as both I got had alot of issues (GPS Test finds 0 satallites regardless of where I am - my first phone that bricked worked great, Can't even connect to Android Market on my new phone...).
Since last night I couldn't connect either. I just spoke with AT&T, they told me to exchange my phone against and offered to give me an $85 credit to my account for the inconvenience.
If my next phone doesn't work like my first, I might be done with the Captivate... And i love this phone.
I have the same message when I try to check for the update. When did you all buy your Captivate? I bought mine on September 3rd. I wonder if they roll the update out to the folks that bough the phone earlier this year and block the newer users.
I bought my captivate the day it came out.
I got mine 3 days before it came out and I cannot connect
I think it might be to excessive server load on the part of AT&T. It might just throw out your request if there are too many people downloading
My phone has NEVER been able to connect. Bought it launch day and while playing with it I tried to see what that function did. It didn't connect but I figured everything was fine and it would work when it needed to...until this update came out and it still wouldn't connect.
Went to the AT&T store - their solution was to replace my SIM card because that MUST be the problem. No dice. They threw up their hands and handed me the phone number to get a warranty exchange.
It was pretty funny watching them try to navigate the menus. I can't believe they sell the product and don't know a thing about it.
Much like the poster above me, when I got mine (mid-August), I attempted to update just to make sure I would have the latest software at that time. It failed to connect and when I tried 24hrs later, still couldn't. So I just gave up unworried. I haven't gotten the update yet and will give it thru tomorrow before I try again. For what it's worth, the gps has always worked fine for me.
I get the same things, no root, nothing. I have a feeling that it just hasnt been released to us yet. I could be wrong and if so its gonna really suck. I bought mine 3 weeks ago from Amazon.
Something that would confirm to me that its just that it hasnt been released is if someone who got this message magically starts working the next day, whatever. Anyone?
I'm not really sure what to believe.. Seems like many others can at least see the update from the software update menu -
some have brought their phones into at&t and gotten a new phone that does get the update manually as well.. I am well past the 30 day return and like a lot of us, have flashed other roms, etc- But this doesn't seem to be a problem with some as they are still able to get the OTA update..
I assume we just wait for the next few weeks as they push the update to everyone- but who wants to wait that long??
I understand 100% about not waiting. I keep bumping my calendar forward and trying again....Im up to some where in first part of October already.
Mine always comes up with two arrows in the upper left corner. Once, before it failed to communicate it in the top of the screen in the center it came up with a white circle with arrows inside it. In a few seconds it gave the failed to communicate.
Yea, I agree with whom said that it is prob a server rejection on the matter.. guess we will have to wait. T_T
PersonOfKnownOrigin said:
My phone has NEVER been able to connect. Bought it launch day and while playing with it I tried to see what that function did. It didn't connect but I figured everything was fine and it would work when it needed to...until this update came out and it still wouldn't connect.
Went to the AT&T store - their solution was to replace my SIM card because that MUST be the problem. No dice. They threw up their hands and handed me the phone number to get a warranty exchange.
It was pretty funny watching them try to navigate the menus. I can't believe they sell the product and don't know a thing about it.
Click to expand...
Click to collapse
Except for the ATT store thing, I've had the exact same experience. Never been able to connect, and my update clock (to ping the server) gets reset to 24h. Even though it couldn't communicate in the first place. This happened before and after root. Never thought to go to the ATT store since I got the phone online.
I wonder if it has to do with locale. A lot of the people posting "no problem" or that they got updates are not in the coastal cities with a lot of ATT server load (e.g., SF and NYC). I'm in NYC. Could that be it?
vijtable said:
I wonder if it has to do with locale. A lot of the people posting "no problem" or that they got updates are not in the coastal cities with a lot of ATT server load (e.g., SF and NYC). I'm in NYC. Could that be it?
Click to expand...
Click to collapse
I'm in Wichita, KS, by no stretch of imagination could this place be a congested area. I have had the same issue since day 1.
vijtable said:
Except for the ATT store thing, I've had the exact same experience. Never been able to connect, and my update clock (to ping the server) gets reset to 24h. Even though it couldn't communicate in the first place. This happened before and after root. Never thought to go to the ATT store since I got the phone online.
I wonder if it has to do with locale. A lot of the people posting "no problem" or that they got updates are not in the coastal cities with a lot of ATT server load (e.g., SF and NYC). I'm in NYC. Could that be it?
Click to expand...
Click to collapse
I'm also in NYC, but my SIM is still on my iphone 3GS contract. (got the phone from ebay).
and my calender is already up to...Jan 1 2011.
I give up.
Downloads to 100%, I tell it to proceed, phone reboots, returns to the launcher and I get "The update was not completed. No update is applied to your phone."
That is followed with "Connection failed. Unable to connect to AT&T server."
Now when I try to even enter the software update screen I get "No Firmware" and nothing at all happens.
I've been through this twice now, each time backup up the entire phone using ROM manager before I try to update and after it fails, restore to before the failed update attempt. Sick of trying to get the update and sick of the GPS not working.
Update FAIL. Reading the dozens of stories of all the other people with problems it makes me not even want to try any more. I don't understand how with some people it works and others it fails with what seems to be no rhyme or reason.
Maybe I should backup, completely wipe the phone then try the update. But again, I've read of people trying that with no luck. I just don't get it.
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.
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.
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
acomputerengineer said:
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
Click to expand...
Click to collapse
I had some issues after that update along with others, see here: https://forum.xda-developers.com/pixel-4-xl/help/wireless-chanrging-issues-oct-update-t4178951
I have had a replacement 4XL sent to me via Google and phone is still on version 10 and working as expected
The phone keeps asking me to install version 11 but I am holding off doing that for as long as possible.
I've been experiencing service issues as well. The last 2 weeks I've been losing sim provisioning for no apparent reason. The only way I can get service to return is via WiFi. The sim will re provision and work. This creates a huge problem for me as Im often away from WiFi while at work for 12 hours with no way to reset it.
I'm going to flash the newest factory image and see if it continues.
Current provider is Google Fi.
Yep had the exact same issue. Looked to reboot in safe mode and received only a black screen. Eventually I just reflashed the latest update and it worked again. I still have this service issue intermittently.
As of today my Pixel 2 XL is without a working camera and the last camera update October 19th has my Pixel 4 xl without a camera. As of now I will strongly have to say this may be my last Google phone.