A few users have been complaining that the Pixel 6 devices (Pro and regular) have been suffering from losing the mobile data connection. The phone seems to lose the connection to 5G/4G/LTE, then the signal shows up that there is no network connection (exclamation mark with the triangle). It takes up to a few minutes until the phone catches up (you can speed up the process by switching airplane mode on and off again).
From my impression this happens esp. when switching the air tower to which the phone connects, but I might be wrong.
However, Google has promised a fix for March - issue still persists. I just received an answer from the german Google support acknowledging that this is a software issue and that this will now be fixed with the June patch. Bummer, waiting another three months.
What's quite disturbing... here on reddit a few users said that swapping out the phone with one which was manufactured more recently fixed the issue for them. Some say that only phones built within the first few weeks are affected. So this might be a combination of h/w and s/w issue.
https://www.reddit.com/r/GooglePixel/comments/tkfs5p
My rma fixed the issue. It's definitely defective hardware.
If you can post the first 2 digits of the serial number for your current model for comparison that would be interesting for me.
My launch day unit with connection issues was manufactured September 2021 and my rma unit was December 2021. I theorize the first few runs of phones had defective modems. Somewhere between September and December the issue was sorted.
The first two digits of the serial number:
First digit: year of manufacture should either be a 1 or 2 for 2021 or 2022
Second digit: 1-9 (January to September) or A-C (October - December)
Click to expand...
Click to collapse
https://www.reddit.com/r/GooglePixel/comments/tkfs5p/_/i3jo0wb
https://www.reddit.com/r/GooglePixel/comments/qhasxr
[Updated] Pixel 6 mobile network keeps dropping for some users
Some Pixel 6 users are bothered by mobile network dropping issue, while for some, Wi-Fi is automatically getting disconnected.
piunikaweb.com
Google Issue Tracker
issuetracker.google.com
https://www.reddit.com/r/GooglePixel/comments/s9g600
https://www.reddit.com/r/GooglePixel/comments/s6gvep
https://www.reddit.com/r/GooglePixel/comments/s6gvep
Why does my network keep dropping on my Pixel 6 Pro? - Google Pixel Community
My pixel 6 pro keeps dropping my TMobile connection. - Google Pixel Community
I got a day one unit and have had 0 problems with network. Are you using a physical sim or an esim
Nergal di Cuthah said:
I got a day one unit and have had 0 problems with network. Are you using a physical sim or an esim
Click to expand...
Click to collapse
Glad that everything works for you.
The statement is not that all early units suffer from this issue, but it looks like that most of the affected units are from the early production days.
I have tried both - eSim and physical SIM. Same behavior.
I had several connectivity issues before march build (had zero connection at home, couldn't get SMS/make phone calls). March build kinda fixed that, meaning at least I got SMS again and was able to make phone calls from my home office, but connection in terms of MB/s was still bad. I just updated to april and will see if that one continues to improve on top of it.
Morgrain said:
I had several connectivity issues before march build (had zero connection at home, couldn't get SMS/make phone calls). March build kinda fixed that, meaning at least I got SMS again and was able to make phone calls from my home office, but connection in terms of MB/s was still bad. I just updated to april and will see if that one continues to improve on top of it.
Click to expand...
Click to collapse
I'm already in April and it didn't get any better.
I have the feeling that things got worse with the March build, but I can't prove it in any way.
Next thing... I will try to get T-mobile to swap out my phone. I'm really sick of all the connection issues
It happened to me a couple days ago. I was outside listening to Spotify. Suddenly the data indicator started showing "E" and it wouldn't change back to 4G until I restarted the phone. Annoying.
I havent had any issue with my pixel, I wonder if this is a hardware issue...
Today someone from T-Mobile Germany customer service gave me a hint that there are a few of these lemons. So... I have initiated a replacement - really, it bothers me so much. I often use my mobile phone when I need to have information quickly or get things done quickly. My blood pressure goes up whenever I see the mobile data connection going off, which happens quite often.
Hey I got this every so often, more less recently.
I have found switching off the "automatically select network" on T-Mobile to work so far. Not sure if this is an end all, but seems to also fix not being able to call out sometimes.
I've had calls drop multiple times after the April update even after factory resetting my phone. The call will just turn off like I was never in a call in the first place. I've tried updating to the QPR beta and it's still happening. I do have a better signal with the newest modem but seriously, Google needs to fix this. In the meantime I've been forced to use my work iPhone as I can't afford to have dropped calls with clients.
Related
NEW IN THIS THREAD?
PLEASE READ THE FOLLOWING BEFORE REPLYING
PLEASE NOTE THAT THE PROBLEM HAS BEEN FIXED WITH AN OVER-THE-AIR UPDATE BY GOOGLE. IF YOU SUFFER FROM THIS PROBLEM THEN YOU SHOULD WAIT FOR THE UPDATE TO ARRIVE ON YOUR DEVICE.
Full details:
What the problem is
The device has an issue of volume acting strangely. Most often the volume mutes very quickly. Sometimes the volume starts 'jumping' between muted and loud very quickly.
This volume issue happens often during phone calls, using internet or receiving SMS text messages.
Some users are also reporting that when calling, they can hear 'radio interference' sounds.
The device is often unresponsive while the problem happens. Power button not working for the brief time has been reported.
How it happens
The problem happens while the device uses GSM 900 network, that is when the device is in 2G.
Your phone is on 2G when it uses E (Edge) and G (GPRS) connections, both data and mobile. If data is used, a small letter near signal indicator points out what you are connected to.
The problem happens while another device that is on GSM 900 is nearby and is transmitting in 2G network. This happens even if Nexus itself is not using any networks at the time (such as when radios are off and the device is in Airplane mode).
The problem is more evident when user is in low-signal area and more 2G information is transmitted.
The problem also happens in bootloader and is not the fault of Android 4.0 itself.
Please remember that the problem does not happen for all 2G networks, some 2G networks (especially outside Europe) do not use GSM 900.
How many users are affected
Every Samsung Galaxy Nexus handset seems to be affected by this problem. Majority of users however are not encountering the problem due to not using GSM 900 2G networks.
2G networks working on GSM 900 are majority of Europe, Africa, Australia, Middle East and large part of Asia.
In UK, the GSM 900 is used by O2, Vodafone, giffgaff, Tesco Mobile.
What Samsung and Google are saying
No official statements from Samsung other than asking people to send details of the problems on their customer support e-mail ([email protected]).
Samsung did post a quote on their Samsung UK Facebook wall that says 'We are aware of the volume issue and have developed a fix. We will update devices as soon as possible.' This quote is said to be originating from Google according to Samsung, Clove, androidpolice.com and The Verge.
Google employee has confirmed in an Android developer chatroom that Google is developing or has developed a software fix for the problem.
Another Google employee, Dan Morrill, shared a post by Lee Johnson on his wall and said that he is very accurate in his estimation about how software can fix this hardware flaw.
Google has replied to a customer support thread that there is a fix and it will be rolled out in the coming week. It is possible that the 'coming week' refers to week starting 5th of December.
What sellers are saying
Handtec and Clove conducted additional testing on the devices and both found the volume bug to exist on their devices.
Handtec stopped the shipments after the problem became widely known. Samsung Distribution also stopped shipments for sellers few days later, delaying shipments of the device for a week.
Clove stated that according to what they heard from Google, that a software fix is being worked upon. Clove stated that according to their sources the problem is in software and not hardware. Clove has not gotten this information from Google or Samsung directly however and refers to their inside research about information found online and their own sources.
While it was originally believed that the shipment delays are because of Samsung flashing the devices with updated software that will fix the bug, the new devices shipped on 29.11 also carry the bug according to Clove. It seems Samsung held the shipments to give Google additional testing time with the fix and held back possible refunds and replacement handsets would have gotten had the shipments not been held back.
Is it hardware or software problem?
All the tests conducted by many users so far indicate that the problem is in hardware and that the device receives signals from 2G that it should not receive due to not being protected from radio interference. This is also shown while the device runs in bootloader.
Many engineers here and in other forums and social networks say that a cheap hardware shielding would fix the problem easily, however Samsung and Google intend to fix the problem with possibly as valid means through software.
If the software fix manages to patch the problem, then it really does not matter if the problem was in software or hardware, as long as the device works properly and there are no after-effects, since some users fear that the software fix of a hardware might cause additional battery drain or unresponsiveness problems. But this is merely an opinion, we will know more once the patch is out.
The flaw is confirmed to be a hardware flaw by engineers, as well as a Google employee (referred to above). But both state that it is common for this type of hardware flaw to be patched with software and it is likely that many devices you already own have such patches in place without you knowing it.
What you can do
Wait for the update to arrive on your Galaxy Nexus. Google is slowly rolling out a fix to all handsets right now. Make sure you have internet or data connection for the update and have your phone in a charger just in case while updating.
Have it on mine
bought from Phones4u in the Trafford centre, Manchester
This looks really bad. While I am sure many people who don't have this problem won't even bother to vote in this thread, the fact that there's just one vote for someone who does not have a problem, is a surprise. I expected 50%-50% at worst.
Bought mine from O2 store in Liverpool. Problem continues even after factory reset.
Phones4u market street manchester.
I also posted the problem on Samsung UK Facebook page, those of you who have a problem should post there too so they are made aware of the problem. This might help get to the bottom of things quicker.
https://www.facebook.com/SamsungUK
Anyone reported to Google support forum?
dont have the device yet so would be hard for me to respond when google asks for logs etc. That would be the best thing to do though.
According to this video, it seriously looks like a hardware issue, so letting us know where you got the phone would be even more helpful.
Duddyroar said:
https://www.youtube.com/watch?v=B6xlZFcgPlo&feature=youtube_gdata_player
Click to expand...
Click to collapse
kristovaher said:
According to this video, it seriously looks like a hardware issue, so letting us know where you got the phone would be even more helpful.
Click to expand...
Click to collapse
Thanks for the video.... Looks like I gotta be grateful I can't get the Galaxy Nexus yet. If its sw, i expect an update soon... But something tells me, its a hw issue in a certain batch.
gogol said:
Anyone reported to Google support forum?
Click to expand...
Click to collapse
Anyone know where the Google support forum is?
I haven't noticed any problem with my phone but I have locale installed so I'm not sure if that is masking the problem.
to those trying to replicate, try turning off wifi, then disabling 3G (settings - wireless & networks - more - mobile networks - use only 2G networks). When it connects, get some data going (load a large website for example), or make a call, see if that sets it off.
it may not work 100% of the time (if it's really radio interference, there are a lot of variables) but it seems to be related.
I do have this issue. Got mine at the launch event at the Oxford Street Phones 4U.
Anyway in the other thread it looks like people are narrowing down the problem to something related to 3G or Wi-Fi signal. I think that might be the case since it had only happened to me while I am outside and not connected to Wi-Fi. (I use JuiceDefender to automatically disable Wi-Fi if it doesn't find any known spots)
I got mine from Oxford St. too. Same problem here.
Sent from my Galaxy Nexus using XDA App
had this problem yesterday with my vodafone sim.
been using it with my o2 sim today and not had the issue occur.
doubt the network would be an issue but thought i'ld just throw it in there.
yep, I have the problem too. I got mine from Phones 4 u On the lauch day in Oxford Circus. Hope this is not HW related!
I seem to have this problem intermittently. Thought it was just me doing something wrong.
Got mine from O2 over the phone.
I'm assuming it can be fixed with a software patch.
Im also having this issue. Purchased from phones4u today 19th nov 2011.
Dosnt happen all the time though. It did happen when i had my old desire next to it and was loading spotify on my desire....
What software version does everyone have? Hopefully the next (assuming 4.0.2) will fix it.
I occasionally will lose data connectivity out of no where. Half the time it happens after a soft reset. The 4G/LTE icon is still on the screen when this happens (mostly with full reception bars), and I still have access to voice.
The only "fix" I've encountered is turning airplane mode off/on three times, then powering the device off/on, repeating this process at least 3-4 times.
My sim card is provisioned correctly (obviously it works since I've had data before).
Was just wondering if anyone else is experiencing this.
vizion4 said:
I occasionally will lose data connectivity out of no where. Half the time it happens after a soft reset. The 4G/LTE icon is still on the screen when this happens (mostly with full reception bars), and I still have access to voice.
The only "fix" I've encountered is turning airplane mode off/on three times, then powering the device off/on, repeating this process at least 3-4 times.
My sim card is provisioned correctly (obviously it works since I've had data before).
Was just wondering if anyone else is experiencing this.
Click to expand...
Click to collapse
wow, of all the reviews, all the conversations with owners and testers, you are the first to mention this. Are you in an lte area? I know a higher concentration of drops appear to occur on lte areas
We'll all have to watch this one.
I think you have a bad phone. You will likely need a new phone to fix this. I know becuase this is what my 1st Droid Razr did. Does the phone get hot when this happens? does it seem slow as crap data speeds, like you can't even get a 360p youtube to load and web pages take forever. when this was happening my H+ S2 would make my RAZR look like it was on poor 3g/good 2g.
My isuse it some times droped EVERY thing or some times all data, but voice worked. A few times I fell back to 1x ( verizons 2G) and a lot of times 3g. (good day there 3g SUCKS and if any one tells you diffent take a 50 cal and .... ok you get it.)
Any way hope it gets fixed.
WPCentral has a review out (http://www.wpcentral.com/wpcentral-review-att-nokia-lumia-900) and noted the same thing. Possibly a bug: "We have seen an odd occurrence where our Wi-Fi connection can receive data but outgoing data crawls. We’re not sure why that is but haven’t seen it before on our other Windows Phones which causes us to raise an eyebrow. We’ve also had a few reports from early users noting the same behavior. Toggling the Wi-Fi on/off for a few minutes seems to do the trick but we’re a little concerned that this may an early bug."
Whats interesting is that users (like myself) who have moded their phones to re-enable the internet sharing option on devices that originally had it disabled - encounter the same issue. Leads me to believe that it could be a bug in the OS itself relating to internet sharing.
CrownSeven said:
Whats interesting is that users (like myself) who have moded their phones to re-enable the internet sharing option on devices that originally had it disabled - encounter the same issue. Leads me to believe that it could be a bug in the OS itself relating to internet sharing.
Click to expand...
Click to collapse
or, something in the modding, has led to the issue. Oh...did I say that in my outside voice...
CrownSeven said:
Whats interesting is that users (like myself) who have moded their phones to re-enable the internet sharing option on devices that originally had it disabled - encounter the same issue. Leads me to believe that it could be a bug in the OS itself relating to internet sharing.
Click to expand...
Click to collapse
How did you "mod" your Lumia?
cx1 said:
How did you "mod" your Lumia?
Click to expand...
Click to collapse
Should've been more clear, I don't have a lumia, but a Focus.
turns out to be a software issue with an update coming on 4/16. id post a link to the nokia site saying so, but i dont have enough posts, plus im sure you guys already saw it over all the tech blogs.
I have this issue as well.
me too! no data
Problem will be solved by April 16... Will need to update software...Also every lumia purchased until 21st will be given $100 credit towards attach bill.. Pretty much getting this phone for free!
Source: the verge
Sent in 3D
Boss2212 said:
Problem will be solved by April 16... Will need to update software...Also every lumia purchased until 21st will be given $100 credit towards attach bill.. Pretty much getting this phone for free!
Source: the verge
Sent in 3D
Click to expand...
Click to collapse
it's in usa right? how about buying from canada? i have the same issue.
cao0215 said:
it's in usa right? how about buying from canada? i have the same issue.
Click to expand...
Click to collapse
I don't know about canada but bill credit is given from att which is carrier in USA.. Thing is this applies to who have bought their phones under contact.
Sent in 3D
Recently AT&T users in my area (midwest) have been having "no service" problems (that last for a moment and then service is OK) and problems with their time being incorrect. Example: today my phone said 3:30am when it was 10:30am in my time zone. I googled but haven't seen any complaints about this anywhere. AT&T had me remove my battery and wait while they "disconnected" me from the network and then "reconnected" me. Since then it's OK, although I'm not sure that did anything, considering the intermittent nature of the problem. It did correct the time when I did it. I had this problem both when accessing the network normally and when accessing it through an AT&T microcell. This has been going on since March 8.
Comments?
I don't know if this matters to you but I have been having Att issues since March 8th regarding sending and receiving mms. Never had an issue before. I am in the Florida Panhandle for Spring Break and this issue has been maddening. I havent done anything to my phone or changed any settings. Anyway, take it for what it's worth
Not sure if there's a thread already for this, feel free to delete. Anyone experienced loss of mobile network connectivity when you are not using wifi anymore? You will need to restart the phone in order to get the mobile network back.
I'm not sure what actually triggers it for me, but there have been 2 or 3 times in the past 2 weeks since I got my Note where mobile data is dead and restarting my phone is the only way to fix. Not sure what's going on. Hasn't happened in several days.
s1l3ntm0use said:
I'm not sure what actually triggers it for me, but there have been 2 or 3 times in the past 2 weeks since I got my Note where mobile data is dead and restarting my phone is the only way to fix. Not sure what's going on. Hasn't happened in several days.
Click to expand...
Click to collapse
It happens all the time when im out of range from a wifi and the phone wont switch to mobile network automatically.
My wife and I have both been experiencing the same problems with our Note 7.
No solution found for us except restarting phone. It seems to happen when the following occurs: (1) temporary initial loss of mobile signal, like from being in an elevator, combined with (2) not being connected to WiFi network. Fwiw, we are on T-mobile in a major market area. Previously had Note 5's with same carrier in same area for over a year without experiencing this issue.
Same thing here and a buddy of mine same thing on tmobile. Fringe areas wreak havoc on this damn thing. Lags...loses signal..etc. my s7 had MUCH STRONGER reception in the same areas this damn thing can barely keep a signal! Smh
**UPDATE**
I got around to calling T-Mobile today, and they said that this is now listed in their system as a known issue with the device. Rep I spoke with said he didn't really have much more information other than they've gotten enough reports of signal loss with the Note 7 to have it be flagged as a known issue.
According to the rep, the only known fix at the moment is rebooting the device. Obviously this is a pain in the ass if you have to reboot the phone every time you get on an elevator and lose signal.
Given the circumstances, this at least rules out it being a network carrier issue or an Android OS issue. The rep was not sure if the problem was related to hardware or software. If its software, it something that can be corrected; but if its hardware, then there really is no solution.
My plan is to deal with it for another 3-4 weeks and see how the Note 7 recall pans out, which should also provide a bit more time for them to figure out the cause of the signal loss problem. If it seems like it's not going to be fixed, then I'm just going to trade in the phone for something different. Fwiw, I asked if they had similar reports for the S7 or S7 Edge, and they said there were no system flags for this issue on those devices.
12345123456 said:
**UPDATE**
I got around to calling T-Mobile today, and they said that this is now listed in their system as a known issue with the device. Rep I spoke with said he didn't really have much more information other than they've gotten enough reports of signal loss with the Note 7 to have it be flagged as a known issue.
According to the rep, the only known fix at the moment is rebooting the device. Obviously this is a pain in the ass if you have to reboot the phone every time you get on an elevator and lose signal.
Given the circumstances, this at least rules out it being a network carrier issue or an Android OS issue. The rep was not sure if the problem was related to hardware or software. If its software, it something that can be corrected; but if its hardware, then there really is no solution.
My plan is to deal with it for another 3-4 weeks and see how the Note 7 recall pans out, which should also provide a bit more time for them to figure out the cause of the signal loss problem. If it seems like it's not going to be fixed, then I'm just going to trade in the phone for something different. Fwiw, I asked if they had similar reports for the S7 or S7 Edge, and they said there were no system flags for this issue on those devices.
Click to expand...
Click to collapse
Same boat here. I'll swap to the s7 if it's not sorted out. Happened 2 times support work already.
Sent from my SM-N930T using Tapatalk
Just posting in case it becomes a "thing" with the Pixel 2 XL.
Last night I noticed that my stock, locked Pixel 2 XL which I had ordered as soon as available way back in October had spontaneously rebooted. I picked it up to see what happened......and it was not detecting a SIM card. It also would try to detect Wifi networks, but would never find any, then Wifi would turn off. I swapped out my SIM card with my husband's, and my SIM worked in his phone but his did not work in mine. Tried resetting network settings, didn't work, tried factory reset, didn't work, tried clean flash of latest Pie, didn't work.
Some weird stuff.....I can get into settings, but come critical info missing......like MAC address, IMEI, etc. So I think the transmitter/receiver is just dead.
Doing a warranty exchange.....Hope I get a new phone as opposed to a refurb, but we'll see.
I had gone online and noticed one post in Google Product Forums describing a similar problem on a new phone someone received, but this doesn't seem to be a pattern.....yet.
Again.....just want people to be aware. Back to my Nexus 5 for a few days.
And my replacement is shipping from Ingram Micro in Carol Stream, IL. Should be here Friday. Anyone know if this is an indication of a new phone vs. refurb?
Batteries on the two Nexus 5's I have in my possession are rather shot. Need constant charging.
Received my replacement. Manufacture date January 30, 2018. Security update version May 5, 2018. Came in flat box in Google packaging (no accessories). Hardware version 10 (same as old phone). Phone appears to be perfect, no problems (so far).