I have a Samsung Tablet (android 7.0) four CCAs, all on good 5ghz wifi. Ever since the tablet was upgraded to 7.0, it's had an issue where, about half the time, once I select a device to cast to from Spotify/Pandora (either one), it disconnects the WiFi on the tablet. It will physically turn the wifi off, and it will come back on after about 20 seconds. After then it will work for a bit.
I have a LG G5 that has never had this issue. It also is running 7.0.
Could someone shed some light on what is happening when I attempt to cast? Why could it disconnect my tablet WiFi? The wifi comes from a RT-N66U, of which I've tried both old and new firmwares, but it made no difference. I've also done two factory resets on the tablet and turned off battery optimization on Spotify, pandora, and the Home app. Not sure what else to do. Finally, I've also done factory resets on all CCAs. Any input is appreciated. Thanks.
Related
I just got my Sprint GN a few weeks ago, and love using the bluetooth to connect to my car audio, but every 3rd or 4th time I get into my car I notice the bluetooth doesn't pair, so I take out my phone and look and the bluetooth icon is gray (instead of blue, indicating it has connected), I toggle the bluetooth off, and then when I try to turn the bluetooth radio back on it just sits there saying "bluetooth is turning on...". Bluetooth stops working until I reboot my phone
Does anyone have any incites into this or anyone else experiencing this?
I have the same issue. It's no solution but you can enable/disable Flightmode to get Bluetooth up and running again (but quicker then reboot).
Sent from my Galaxy Nexus using Tapatalk 2
I'll give that a try (again) next time.. I am 100% certain I had tried that, though, unfortunately.
Yeah, I tried your solution again, and it just keeps saying "bluetooth is turning on..." even after I've turned *on* airplane mode.
Need some more information to be able to help you properly >_>
Stock ROM or Custom?
Rooted/Unrooted?
Or alternatively (Because it sounds like you're running a stock Galaxy Nexus...) ave you tried unpairing, and the repairing the devices?
Hi Zach,
Completely stock & unrooted (so far)
I actually did a complete factory reset a couple days ago, and the problem has yet to resurface, so I'm crossing my fingers and hoping it's gone, but the issue was intermittent so there is no way to be completely sure it won't show up again.
If it does, I'll try your suggestion, thanks
So I just got my Note 2 this past Friday to replace my original Note. It was fantastic until yesterday.
Was playing with the cards on Google Now and the screen went black. Nothing worked until I pulled the battery and restarted. Most everything was fine after that except wifi. It keeps toggling itself on and off roughly once or twice second. It's set to stay on always so its not related to that. I can sit there and actually watch the on/off switch slide back and forth, it will do this roughly 100 times over 5 minutes and then shut off the entire phone.
Very frustrating for a new phone. any thoughts before I go exchange this?
try factory resetting it
done it, twice, still happening
Are you using the 5g wireless connection (if your router supports it)? I've had nothing but problems on recent Android versions connecting to that. It will disconnect and reconnect several times a minute. It started with my Galaxy nexus, continued with my S3, and now my Note 2.
If I connect to the standard wireless (The 2.4GHz band), everything is fine. I don't doubt it's probably my router (Netgear WNDR3400), but I hope this helps.
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Noticed the same with my 360 and Nexus 5. Both on stock latest versions.
Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.
I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?
I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.
Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.
Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.
this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.
Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.
I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....
My pixel 3 xl will connect to Android auto via USB.... Work for a few minutes then randomly disconnect. Never happened with my pixel 2.
Any suggestions??...I have tried new USB cable.... Still does same thing.
Sent from my Pixel 3 XL using Tapatalk
I have had occassional issues with Android Auto as well -
When I first got the Pixel XL I was able to connect fine via USB and even wirelessly to my Kenwood headunit - but the other day, after connecting to Android Auto, when I tried to make a phone call, Blue Tooth was not connected and I could not get it to connect. I eventualy toggled on and off Airplane Mode - and after that
it connected fine. Havn't had an issue since (knock on wood)
for your situation, have you made sure that USB Debugging i turned off? It won't work with that turned on....
Same problem here.
Never had an issue with my Pixel XL, Pixel 2 or Pixel 2 XL. Yesterday I received my new Pixel 3 XL and Android Auto keeps disconnecting. Sometimes it does last a few minutes, sometimes it does so after a few seconds. It doesn't matter if an app like Spotify or Maps is being started or if I just connect the cable. Android Auto doesn't stop on the phone but only disconnects.
As you can't deinstall Android Auto I already tried wiping cache, wiping data and deactivate. I even tried three different cables.
When I connect my work phone Pixel 2 I don't see this problem. The connection is kept as usual.
I'm getting grey hair over this.
Has anyone found a solution or workaround for this issue?
I've tried absolutely everything, even rolled back to a nano SIM after started with an eSIM.
Gonna RMA this week and cross my fingers.
I wonder if it's a hardware issue or software. Unfortunately I don't have another phone that runs pie so I can't test it. My v30 running nougat works fine. I'm kinda waiting for the next pixel update to see if it fixes it.
If you do rma your phone let us know if that fixes the issue.
Turn off adaptive battery and see if that helps you
Nope, that doesn't help. As I mentioned I have every previous Pixel and all of them work flawlessly with my head unit. All preferences are the same.
There's only one obvious difference: Android Auto is pre-installed on the 3 XL.
Unfortunately I don't know anybody with Android Auto in the car nor owning a Pixel 3 XL to check out if it's something with my head unit.
In a German forum 2 people say they have it working properly...
One of the most frustrating parts is that - for me - it sometimes it works 10 minutes. After I switched back to nano SIM yesterday on my drive home I connected, listened to great music, whatsapped my wife that it is working and boom...disconnect and from then on the known behavior started again.
Did the new rma device fix the issue?
Just send it today and because I bought from provider I've a couple of days for the new one. Used my good ol' Pixel XL today working like a charme...
I'll update when the replacement has arrived.
Experiencing same issue with Pixel 3 non-xl and 2016 Honda Accord. Android Auto disconnects anywhere from 20 minutes to just seconds after I've connected.
I've tried the following:
-Variety of brands of USB-C > A cables
-Disabling all power saving options (whole phone, specific apps)
-Setting screen to stay on when charging (solved AA disconnect issues on my LG V20)
-Re-pairing bluetooth with car
-Re-pairing AA with car
-Resetting car head unit
-Resetting phone
I've had no issues with disconnects, but I use wireless connection with Pioneer headunit.
I got my replacement today and for now the problem looks to be solved but I only sat 20 minutes in the garage messing around with it but that are 19:50 more than my last attempt with the old one.
But I already installed both Android Auto app updates that came in the last couple of days.
/me is crossing his fingers
I'll drive about one hour in the evening and hope everything stays how it is now
It's a pixel 3 software issue. Big thread in the Android Auto support forums. Google doesn't seem to be in a hurry to fix it. Said the November update should, it did not.
Anyone ever find a fix for this? I'm having the same issue, but now cannot connect at all. (Was working. Stopped the car, went into Starbucks, came out and AA won't connect.) My Pixel 2 XL works fine, but I want to sell it.
Like I said I RMAd it and it works flawlessly ever since.
Android Auto Closing Out on Pixel 3
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?
Wahoodean said:
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?
Click to expand...
Click to collapse
My phone connects fine to AA. It stays connected with the cable. Perhaps try a new cable to connect it. I'm on stock rooted.
Sent from my Pixel 3 XL
So I've got a Pixel 3 XL, completely stock and completely up to date. Unrooted.
I've got reoccurring Bluetooth issues where it won't see devices it's been paired with until I restart the phone, and then in some cases it doesn't even know it's been paired - it completely forgets the devices I've paired with (sometimes one, sometimes multiple, sometimes all!). The problem is not isolated to any particular device that I pair it with.
I've considered a factory reset to see if that helps, but wanted to see if anyone has any other recommendations before I take a chunk out of my day doing a rebuild of my device.
Any suggestions?
Thanks!
JWhipple said:
So I've got a Pixel 3 XL, completely stock and completely up to date. Unrooted.
I've got reoccurring Bluetooth issues where it won't see devices it's been paired with until I restart the phone, and then in some cases it doesn't even know it's been paired - it completely forgets the devices I've paired with (sometimes one, sometimes multiple, sometimes all!). The problem is not isolated to any particular device that I pair it with.
I've considered a factory reset to see if that helps, but wanted to see if anyone has any other recommendations before I take a chunk out of my day doing a rebuild of my device.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
I've never had this issue before, even when I was on custom ROM. My Bluetooth works fine in car, at home, and with wireless headphones.
Sent from my Pixel 3 XL
I cleared out the bluetooth cache and storage then rebooted this morning - going to see if it makes any difference. Usually it takes a day or two before a device disappears after I re-pair with the phone. Unless anyone has any other suggestions I may do a factory reset in a few days if it happens again.
Not bluetooth but I did have all my saved wifi networks wiped after a reboot a few weeks ago. Oddly, I rebooted because my phone wouldn't connect to my Fitbit via bluetooth to sync. I rebooted and the screen was black, not responding at all. If I pressed the power button it would vibrate slightly as it does when the power menu pops up, but nothing else. After trying a few button combos I got it to reboot again and everything was fine except wifi networks were all gone.