Develop Bugs

VZW signal issues and root.

rhinolow said:
So I went back to 4.0.1 and was getting a steady three bars on my phone
Went to 4.0.2 and am getting a steady 2 bars on 4g
Unlocked, and rooted on 4.0.2, and was getting really sporadic signal behavior, including signal loss
All these readings are from the same location in my home.
Then I went back to 4.0.1 and tested all three conditions and got the same results.
I'm no programmer so I can't say why unlocking/rooting would make a difference, but I believe it's making enough of a difference at this point that I'm going to stay stock and locked at 4.0.2 for now.
You guys that are having a lot of problems, are you unlocked or rooted?
Click to expand...
Click to collapse
Now that it's been a few days..... I want others to chime in on this report (no one answered this question in the original thread).
I was having a ton of issues, thought that VZW did something to make it slightly better (which I still believe they did), but stilll... I have issues, although not as bad as the second 12 hours of ownership.
I had made the call to tech support and was then going to return the phone.... when I got home I brought the device back to stock carrier 4.0.1 ROM floating around). Problems were almost completely gone!?! An hour later, the update came and I was worried about the upgrade screwing the radio that was acting better (not that it was perfect by any means!!). So..... after a little thought, I figured I could always go back to 4.0.1 and/or return it. I let the update do it's thing.
There seems to be zero difference between 4.0.1 and 4.0.2, when it comes to the radio.
I was still scared to do much..... I didn't install any apps while I watched the phone for a few hours. Then only Google's apps... the next day the rest of my apps (w/small exceptions, detailed below). Everything ran smoothly.... including the radio. Now it isn't nearly as good as the DX radio in my last phone, BUT..... at least I wasn't constantly with -120dbm and was able to use the phone, as a phone!
So.... I figured after another day that VZW must have fixed something.
Cool, right? Not sure..... I am stock, unlocked, and unrooted. I am afraid to root the phone..... I can't fathom how root could cause a radio issue, but am wondering how many others might have issue with and without root.
Now.... I am still seeing issues, but not nearly as bad. I'll root the phone tonight to see what happens, but would like others input.

Stock Verizon Nexus here and where I normally get full 4g I get maybe 2-3 3g bars. Most of the time I get zero signal where I at least get 3g.

http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue

droid2andyou said:
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
Click to expand...
Click to collapse
Great article. Sure as heck opened my eyes up. Thanks.

Root doesn't touch the radio. All it does it give you admin right over the phone.
-Galaxy Nexus
-Asus Transformer

player911 said:
Root doesn't touch the radio. All it does it give you admin right over the phone.
-Galaxy Nexus
-Asus Transformer
Click to expand...
Click to collapse
Exactly right it must have just been the cell towers by the ops area
I'm currently having issues now before and after root

droid2andyou said:
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
Click to expand...
Click to collapse
Just read that earlier today. Lots of great info inside.

The story continues
So, just to follow up. I did return my device for a new GNEX and have not had the same issues. I have been reluctant to root my new phone, but I still don't see any reason why the two would be related. I think I had a bad device. I think there are a substantial number of people that are getting DOA devices, but it doesn't appear to a majority. I'll report back if/when I decide to root and flash anything to my new device.
abendx said:
Now that it's been a few days..... I want others to chime in on this report (no one answered this question in the original thread).
I was having a ton of issues, thought that VZW did something to make it slightly better (which I still believe they did), but stilll... I have issues, although not as bad as the second 12 hours of ownership.
I had made the call to tech support and was then going to return the phone.... when I got home I brought the device back to stock carrier 4.0.1 ROM floating around). Problems were almost completely gone!?! An hour later, the update came and I was worried about the upgrade screwing the radio that was acting better (not that it was perfect by any means!!). So..... after a little thought, I figured I could always go back to 4.0.1 and/or return it. I let the update do it's thing.
There seems to be zero difference between 4.0.1 and 4.0.2, when it comes to the radio.
I was still scared to do much..... I didn't install any apps while I watched the phone for a few hours. Then only Google's apps... the next day the rest of my apps (w/small exceptions, detailed below). Everything ran smoothly.... including the radio. Now it isn't nearly as good as the DX radio in my last phone, BUT..... at least I wasn't constantly with -120dbm and was able to use the phone, as a phone!
So.... I figured after another day that VZW must have fixed something.
Cool, right? Not sure..... I am stock, unlocked, and unrooted. I am afraid to root the phone..... I can't fathom how root could cause a radio issue, but am wondering how many others might have issue with and without root.
Now.... I am still seeing issues, but not nearly as bad. I'll root the phone tonight to see what happens, but would like others input.
Click to expand...
Click to collapse

[Q] Galaxy Nexus Dropping Data?

So normally I run my phone on Wifi because it saves battery when i'm on my university campus all day. So last night I headed off campus and so I turned off WiFi, and it didn't want to connect to data. Just sat there (with full service) but no data connectivity. So I rebooted the phone. still no connection, turned on airplane mode and then back off, now it worked but only for about 3 minutes I had 4G with blue sync and everything, then it dropped off. I went out into a rural area and I kept having full signal but no 3G. So I thought it was the rom. I was running AOKP b25 (Team Kang) so I just updated to Milestone 4. Everything was going well in initial setup of the phone, I had 4G signal, then halfway through setup the 4G dropped off. So I turned on Wifi and got everything setup. Turned off Wifi and it hooked to 4G almost immediately. Then about 3 minutes later, it dropped again. So at this point i'm really hoping it's not my phone and it's Verizon. I've never had a single issue before (i've had the phone since December) with data not connecting like this. It just started last night, which made me think it was Verizon and maybe it had to do with the Solar Flares or something? Has anyone had a similar issue and have any idea of what I might try?

Hi
I was just about to post the same thing. I'm experiencing the same, Data and service keeps dropping, I just got the phone Wednesday and since then It's been doing it. It's very frustrating, and I'm also on Verizon.
Someone else experiencing the same? Could Verizon be the responsible here and not the phone?

And if it helps, i'm located in Norman, OK

JGeZau said:
Hi
I was just about to post the same thing. I'm experiencing the same, Data and service keeps dropping, I just got the phone Wednesday and since then It's been doing it. It's very frustrating, and I'm also on Verizon.
Someone else experiencing the same? Could Verizon be the responsible here and not the phone?
Click to expand...
Click to collapse
It's the phone, there's numerous threads about it (the Verizon version.) There's an expected software fix supposedly coming out this month sometime to fix it, that's all we know.

If it's the phone and an update will fix it, then why is it still doing it with a custom ROM? Do the custom ROMs not have the fix in place? I was under the impression that most of the things Verizon releases OTA to fix issues dont' happen in custom ROMS.

zacelliott said:
And if it helps, i'm located in Norman, OK
Click to expand...
Click to collapse
Hey, we are 4hr away from each other. I'm in Rogers AR
spencer88 said:
It's the phone, there's numerous threads about it (the Verizon version.) There's an expected software fix supposedly coming out this month sometime to fix it, that's all we know.
Click to expand...
Click to collapse
Thank you I'll start digging up in some other threads

zacelliott said:
If it's the phone and an update will fix it, then why is it still doing it with a custom ROM? Do the custom ROMs not have the fix in place? I was under the impression that most of the things Verizon releases OTA to fix issues dont' happen in custom ROMS.
Click to expand...
Click to collapse
Samsung is going to hopefully release a radio update that fixes it, which isn't found in custom rom's because it hasn't been released outside of samsung yet.

It's kinda weird though that this JUST happened last night suddenly, the signal has been flawless since I bought it so that's why I thought it was Verizon because I guess I figured if it was the phone it would have been doing it all along and not stop working all of a sudden.

It's the phone and a software update won't fix it. I've tried every radio out there, none solved the issue. I got the phone swapped over a week ago, it is still stock, and the issue hasn't returned. Theres an ongoing thread over at rootz about this.
I can't post the link but it's there. many members are reporting that replacing the device solves the issue.

this was verizon. it happened to me, went away by itself.
that being said, ive had the best handoffs using the 4.0.4 and 4.0.3 radios. try one of those, or a hybrid package.

I went to the Verizon store and they gave me a new SIM Card. Now it works!

willstilson said:
It's the phone and a software update won't fix it. I've tried every radio out there, none solved the issue. I got the phone swapped over a week ago, it is still stock, and the issue hasn't returned. Theres an ongoing thread over at rootz about this.
I can't post the link but it's there. many members are reporting that replacing the device solves the issue.
Click to expand...
Click to collapse
First of all you don't know what you're talking about. It may be a hardware issue it may be a software issue. There is no way to tell at this point. You are trying leaked radios, good job that proves nothing. If Samsung is aware of the issue and working on a new radio you haven't tried it yet. Sit back and relax until the update comes out. Then we can go from there.

SirVilhelm said:
First of all you don't know what you're talking about. It may be a hardware issue it may be a software issue. There is no way to tell at this point. You are trying leaked radios, good job that proves nothing. If Samsung is aware of the issue and working on a new radio you haven't tried it yet. Sit back and relax until the update comes out. Then we can go from there.
Click to expand...
Click to collapse
Wow dude, no need to get insulting. I was merely sharing my experience with a frustrated OP. If you want to blindly believe that there can't be anything wrong with certain devices, until the manufacturer comes out and says it, then more power to you. You are the consumer that ever manufacturer loves. Myself and many others over at Rootzwiki have found success by having our devices replaced. When I tell you that it is night and day difference, it is not a lie.
I agree with you about the leaked radios. If they don't work then it proves nothing. They are leaked and probably not finished. The reason I mentioned them in the first place is because many people tend to suggest trying them to solve signal issues. I was explaining that I have tried them and it did not work. What worked was swapping the defective phone.

No Network Signal After Flash to 4.1 on Verizon Galaxy Nexus

I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.

Rarazuh said:
I just updated to 4.1 and can't seem to get a network signal on any of the ROMs I have tried. Anyone else had this problem or found or know of a solution?
Thanks.
Click to expand...
Click to collapse
Was this an OTA uprade? If you did an manual upgrade, you should make a backup before going forward.

Are you sure you used the correct ROM? Cross-flashing between a Toro/Maguro/Toro+ will often have the phone but up but with the radios not working

did you check your apn?

I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium

mclaughlin47 said:
I just bought this phone on Thursday and the bestbuy rep had the same problem on two different phones and had to call the Verizon help desk. She managed to get it working and of course my signal went in and out as soon as I left the parking lot. I went home and immediately rooted and flashed 4.1 and had the same issue. I was on the phone with tech support and they couldn't find the problem.
I then did a quick search online and found that this is a common issue. The problem is that when updating to 4.0.4 the galaxy nexus has a hard time with the 4g connection. It then drops to 3g and then it realizes 4g is available and switches back just to start this never ending cycle. This causes a signal to be held for seconds at a time before dropping completely until it switches to the other.
The temp fix is to disable LTE and run your phone on CDMA full time. This worked for me and I have constant signal everywhere. Eventually I know a patch will arrive so I'm content with 3g for the time being.
What puzzles me is how come this doesn't happen to everyone? Its a big enough issue that I found the solution within 3min of searching for a fix but not big enough for Verizon to be aware of.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I have the same issue. it burns your battery as well by switching back and forth. I used to leave my nexus uncharged at night and the sleep mode would allow it to only lose a a few percentages but now if i leave 4g on with 50 percent battery.. Its almost alway dead when I wake up

Sad to say I have the same experience
The story told by mclaughlin47 is almost exactly what happened with me. Even rooted and running BAMF Paradigm 2.1, I still have the same problem. If anyone knows of a way to fix this, please let us know.
I can't believe Verizon isn't aware of this problem. I actually had better battery life and signal with my Thunderbolt running Vicious ROM. I may just be returning mine if I don't hear of a solution soon.
Thanks for any help, cause this is ridiculous!

I am rooted now, but even on stock ICS I was getting a problem where my radios just die. Requires a reboot to fix. But when I was seeing it, they always looked fine. You don't know they died until you try to use data or make a call.

Do you still have your imei
Sent from my SCH-I535 using Tapatalk 2

I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can

tbguy said:
I saw the same issue with ics and jb roms. Tried several radios but always dropped data and voice when using 4g. From what I've been reading, it's a hardware defect.
Mine also works great and stays connected all the time when I leave it in cdma mode. Went back to my rezound since 3g mode there at least still let's me use data while talking on the phone. I like showering in as much radiation as I can
Click to expand...
Click to collapse
Reflash the radio and the cdma radio. Samsung and Verizon Wireless both claim that hardware defects are not known issues.
Which hardware revision do you have? (looks on the label on the back should be 11.11, 11.12, or 12.0.)

i have 12.01
will try reflashing the latest radios

tbguy said:
i have 12.01
will try reflashing the latest radios
Click to expand...
Click to collapse
just to check back, did it work?

unknownzero said:
just to check back, did it work?
Click to expand...
Click to collapse
Have the same exact issue...just upgraded to a jelly bean Rom and my data drops completely and I barely have a signal, did a super wipe (radio-rom-Gnapps)...and went to my old rom of ICS and I still have the same problem...but for the most part I barely have any type of signal and calls are dropping, called Verizon and they told me something about a switch, and that there is no problem in ur area....I just called last night, I'm gonna call back today...wish there was a solution ...also tried that 3G switch I just read earlier and I still have a poor signal

Any updates? I'm having the same problem

Hi,
I'm having the same issue. I've had my Nexus for about a month now and have had nothing but horrible signal issues, while my old Droid 2 gets fantastic signal.
I'm using the latest Bugless Beast 4.1.1 with the latest radios that were released today.
People have mentioned it being a hardware defect. I'm assuming I should just go back to stock ICS and go into Verizon and exchange it for a different Nexus?

It may very well be a hardware problem, but my thought was a SIM card problem for the reason that rebooting often does not solve the problem for me. I have a passcode on my SIM card, so if my phone doesn't ask me to enter the code then I can assume it doesn't see the card. This often happens when I encounter the loss of data problem and reboot, and I usually have to remove the SIM card and fiddle with it a bit and put it back in and then it reconnects.
So I went to the Verizon store to try and swap my SIM card and they wouldn't give me a new card, saying that it's a known software issue that Samsung has already attempted to fix twice and they are working on another OTA update. I obviously made a ruckus about how I'm paying for service I can't access and I want a different device, blah, blah, blah. Basically he was incredibly unhelpful.
I've been on ICS AOKP and recently switched over the CM10 JB and that's when the problems started for me, but I switched because some type of battery issue (it lasted about 3 hours for a few days) caused my phone to reset itself and erase everything so it seemed like a good time to upgrade. So I may have unique hardware issues going on but according to vzw it is software-based. I'm not sure if this is something that can/will be addressed in a new nightly if that's the case.

PEOPLE, IT'S NOT A HARDWARE PROBLEM! IT'S SIMPLY A RADIO.IMG PROBLEM! A LOT OF PEOPLE WHO IS ON ICS, BUT FLASHED LATEST RADIO ARE SUFFERING FROM THIS!
What you can do is just flash to a older radio image. Not that hard. Will this stop the OTA? Probably, but you can either flash the latest version back or just manually flash it.
Have a good day.

I got mine the first week of Aug at Best Buy. The first one I got had all the problems described above. Radios dropping out and dropping every call I made. I returned it the next day, and the sales guy told me he was 100% sure it wasn't the phone. I asked him to exchange the phone and the card because I couldn't use a phone that couldn't make calls. He did the exchange, and the second phone was actually worse. Most of the time, I could not even make a call. So, the next day I took that one back. They gave me a third one that worked great for a week, then I started getting a no SIM card error message. The phone would reboot and work again for about 3 hours, then repeat error message. I took the card out, wiped down all the contacts with a soft cloth, and I have had no problems since. Great reception, no dropped calls. Great phone. I don't know if it is hardware or software, but I would keep returning the phone until you get one that works!
Once again, what is the point of having a phone that can't make calls.

Restoring my Redmid Note 5 (wyhyred) to factory defaults for returning to merchant

I have about 20 days left to return my RN5 to Amazon but haven't decided to do so. It seems like a solid phone but there's a poor signal quality with T-mobile towers here in the States compared to my much cheaper $30 Walmart android phone. I hear the other person fine but I'm frequently garbled on my end. I'll be trying AT&T towers within a couple of days and if I see improvement I'll be keeping the phone, if not, I'm returning it. Admittedly, my home has always been troublesome for receiving good signal strength but nothing as bad as what I've experienced with the RN5 on T-mobile towers. My question is: if my phone has been updated with OTA to MIUI 9.6.3.0, unlocked & rooted, does a simple factory reset in the MIUI 9.6.3.0 menu restore it to defaults so I can return it exactly as I received it or do I need to do something more?

JackOfOwls said:
I have about 20 days left to return my RN5 to Amazon but haven't decided to do so. It seems like a solid phone but there's a poor signal quality with T-mobile towers here in the States compared to my much cheaper $30 Walmart android phone. I hear the other person fine but I'm frequently garbled on my end. I'll be trying AT&T towers within a couple of days and if I see improvement I'll be keeping the phone, if not, I'm returning it. Admittedly, my home has always been troublesome for receiving good signal strength but nothing as bad as what I've experienced with the RN5 on T-mobile towers. My question is: if my phone has been updated with OTA to MIUI 9.6.3.0, unlocked & rooted, does a simple factory reset in the MIUI 9.6.3.0 menu restore it to defaults so I can return it exactly as I received it or do I need to do something more?
Click to expand...
Click to collapse
You need to flash miui 9.6.3.0 via fastboot.
It will remove twrp, root and stuff and restore your phone like you received it.

smog2699 said:
You need to flash miui 9.6.3.0 via fastboot.
It will remove twrp, root and stuff and restore your phone like you received it.
Click to expand...
Click to collapse
So, since I'm already on 9.6.3.0, there's no danger of bricking my device if I do this because of the anti-rollback feature? I don't think I've ever flashed from the XRN5 's Fastboot menu before.

JackOfOwls said:
So, since I'm already on 9.6.3.0, there's no danger of bricking my device if I do this because of the anti-rollback feature? I don't think I've ever flashed from the XRN5 's Fastboot menu before.
Click to expand...
Click to collapse
No, you're good to go. 9.6.3 has arb 4 and you're flashing it too. So no issues.
You can even use mi flash tool to flash it. Kinda easy than fastboot.

JackOfOwls said:
I have about 20 days left to return my RN5 to Amazon but haven't decided to do so. It seems like a solid phone but there's a poor signal quality with T-mobile towers here in the States compared to my much cheaper $30 Walmart android phone. I hear the other person fine but I'm frequently garbled on my end. I'll be trying AT&T towers within a couple of days and if I see improvement I'll be keeping the phone, if not, I'm returning it. Admittedly, my home has always been troublesome for receiving good signal strength but nothing as bad as what I've experienced with the RN5 on T-mobile towers. My question is: if my phone has been updated with OTA to MIUI 9.6.3.0, unlocked & rooted, does a simple factory reset in the MIUI 9.6.3.0 menu restore it to defaults so I can return it exactly as I received it or do I need to do something more?
Click to expand...
Click to collapse
you need latest fastboot rom or any on ARB4 and miflash.. and in miflash tick clean all lock. itll fatory reset and lock bootloader.

Wi-Fi and Bluetooth randomly won't turn on

I've had this phone for awhile now. Came from Taimen. S8+ before that..... Never had any issues until about 4 weeks ago. I thought it was the ROM I was on so I went Stock.....no good....then.....I tried Beta. Back to Stock no root/hacks. Keeps happening, intermittently. I'll come home from work, go to turn my Wi-Fi on and it won't turn on. Then I'll go to turn my Bluetooth on and it'll then just keep crashing. Sometimes it fixes with a reboot. Tonight it did not. I'm clueless. Never had an issue like this before that I couldn't fix myself. I've been on every ROM in the Forum trying to fix this last few weeks. No luck.
If at any time throughout the day I turn my Wi-Fi off I risk not being able to turn it back on. I did notice it seems to have a higher chance of working when mostly charged, but that may just be coincidence.
Any ideas?

most likely hardware issue, you're not the only one, contact pixel support.

Stock kernel? I have had the issue (no WiFi after kernel flash) with DU and EX for about the last month (worked fine before then). Have to flash my magisk_patched to revert the kernel to (in my case) Unicorn Blood.

sliding_billy said:
Stock kernel? I have had the issue (no WiFi after kernel flash) with DU and EX for about the last month (worked fine before then). Have to flash my magisk_patched to revert the kernel to (in my case) Unicorn Blood.
Click to expand...
Click to collapse
Yea. Stock kernel. I thought it was a DU issue when it started. That was the 1st thing I bailed off of to try and fix it. I remember being surprised I was having an issue with DU on my device, which I had never experienced. I bought the device, problem free, off of Swappa last year in April. I don't have any kind of Warranty protections or anything that I'm aware of.

djcrystals said:
Yea. Stock kernel. I thought it was a DU issue when it started. That was the 1st thing I bailed off of to try and fix it. I remember being surprised I was having an issue with DU on my device, which I had never experienced. I bought the device, problem free, off of Swappa last year in April. I don't have any kind of Warranty protections or anything that I'm aware of.
Click to expand...
Click to collapse
That is the only issue I have with DU, and since it is not the stock DU kernel it is hard to say where the compatibility issue lies. It started a few personal builds ago, and then before I installed another one I flashed EX even though I hadn't tried it on that build. It worked, and worked again on my next build. Then it failed on the next two, so I am just sticking with Unicorn Blood for the time being.
As for your issue, I do wonder if you don't still have some residual issues from your initial switch back to stock. After returning to stock, have you ben flashing OTA or doing flash-all? I would try a flash-all with -w intact. Change slots, and do it again. Then at least for a couple of times on and off your Wi-Fi leave the install base pretty lite to see if you have any conflicts without reinstalling a bunch of stuff. Sure sounds one of the image files (vendor or radio maybe) is bad.

sliding_billy said:
That is the only issue I have with DU, and since it is not the stock DU kernel it is hard to say where the compatibility issue lies. It started a few personal builds ago, and then before I installed another one I flashed EX even though I hadn't tried it on that build. It worked, and worked again on my next build. Then it failed on the next two, so I am just sticking with Unicorn Blood for the time being.
As for your issue, I do wonder if you don't still have some residual issues from your initial switch back to stock. After returning to stock, have you ben flashing OTA or doing flash-all? I would try a flash-all with -w intact. Change slots, and do it again. Then at least for a couple of times on and off your Wi-Fi leave the install base pretty lite to see if you have any conflicts without reinstalling a bunch of stuff. Sure sounds one of the image files (vendor or radio maybe) is bad.
Click to expand...
Click to collapse
So since DU, I've been on BETA.....clean....flashed to both slots....then to to July Stock 10, Clean both Slots.....Tried the two newest ROMs in the Forum.....now I'm on straight-up stock, clean flash-all, both slots, stock kernel.....My gut is telling me it's hardware but a part of me is in denial. My phone is still in Mint condition so it's hard for me to imagine it's broke but Uncle Google's been making some mistakes in the manufacturing of things lately so......I might be sh1t outta luck. I have unlimited data....it's the Bluetooth thing..... that's REALLY REALLY annoying.

I'd be in denial too. My last thing to check would be the Wi-Fi itself. Maybe some sort of compatibility issue with the phone of another issue. Do you have any other remembered networks that you get onto after being off Wi-Fi and returning to range? Same possibility with BT. Unfortunately, it is common with all BT connections to occasionally miss a reconnect.

sliding_billy said:
I'd be in denial too. My last thing to check would be the Wi-Fi itself. Maybe some sort of compatibility issue with the phone of another issue. Do you have any other remembered networks that you get onto after being off Wi-Fi and returning to range? Same possibility with BT. Unfortunately, it is common with all BT connections to occasionally miss a reconnect.
Click to expand...
Click to collapse
I'm doing some digging on this issue. It does appear to be a community wide issue as stated by the user a few posts up, unfortunately.
https://support.google.com/pixelphone/thread/32828289?hl=en

djcrystals said:
I'm doing some digging on this issue. It does appear to be a community wide issue as stated by the user a few posts up, unfortunately.
https://support.google.com/pixelphone/thread/32828289?hl=en
Click to expand...
Click to collapse
Good luck.

sliding_billy said:
Good luck.
Click to expand...
Click to collapse
Lololol.....damn. So WiFi and BT works when it's charge is 85% or more.....so I juts gotta keep it charged all the time. These devices have great batteries. Piece of cake.
Thanks for chiming in fellas. Appreciate it.

djcrystals said:
Lololol.....damn. So WiFi and BT works when it's charge is 85% or more.....so I juts gotta keep it charged all the time. These devices have great batteries. Piece of cake.
Thanks for chiming in fellas. Appreciate it.
Click to expand...
Click to collapse
I am at a loss for words except "glad it is repeatable."

sliding_billy said:
I am at a loss for words except "glad it is repeatable."
Click to expand...
Click to collapse
Now that is effing funny!
Sent from my Pixel 3 XL using Tapatalk