I don't use Bluetooth that often so I decided to turn it off. First I used the quick tile, but it came back on by itself an hour or two later. So I tried doing it in settings. Same thing, came back on.
Bluetooth scanning and wireless scanning are turned off.
Anyone else seeing this happen or have any ideas? Not a big deal but off should be off.
I noticed that too. I feel like there's Bluetooth scanning in the background and turns on when it is around a device it's connected to in the past. I notice when I get in my car, it's already on and connected to it.
yes it drives me crazy. It turns on after each reboot.
omvir said:
I noticed that too. I feel like there's Bluetooth scanning in the background and turns on when it is around a device it's connected to in the past. I notice when I get in my car, it's already on and connected to it.
Click to expand...
Click to collapse
I unpaired it from the car and it still does it. But it knows I am in the car because it suggests I plug it in for Android auto. So I suspect you are right, it is scanning even if turned off and turns itself back on when it sees a know device.
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
I have a really weird problem.
No matter what ROM I'm using, when I first turn my bluetooth on and connect with any device after about a minute or two the bluetooth turns itself off and if I manually turn it back on.
It's still connected to the device it was connected to and when I turn it back in it works fine but it will do this once each time I connect to any bluetooth device.
Can someone help?
I had downloaded the "auto off unpaired bluetooth" tasker profile and it had an error in it.
I've downloaded a "fixed" version and hopefully this will fix it. In any event, the phone is fine, but the tasker profile was defective.
I use bluetoothkeepalive from the Google play store. It holds the connection all the time, but I still have issues when I disconnect from my car and then reconnect again the next time..
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
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....
I get a brand new Note 4 a few days ago. The wired thing is both Wifi and Bluetooth won't reconnect automatically. For Wifi, it won't automatically reconnect to my home wifi after I get home. It won't be able to see my home wifi. I have to manually turn the airplane mode on and off to make the connection happen. For bluetooth, I have paired it with my car and Panansonics Link to Cell cordless phone. Both won't automatically reconnect. Sometimes I can reconnect manually and sometimes I have to delete the device then repair the device to make the connection happen. Anyone experiencing the same issue? Anything wrong with my phone? How I can fix it?
Thank you
Yep. Same thing here. I have to reconnect manually all of the time.
Both our note 4s auto reconnect to wifi and bluetooth.
Not exactly sure what would be interfering with its reconnecting ability but I assume standard reset procedures ,battery pull, factory reset etc.
Take it to store to have it reflashed, escalate to exchange device if necessary.
I have the issue with my car. Keeps losing connection to Bluetooth when car is shut off. Next time I turn on car it says pairing failed.
Sent from the TermiNOTEr 4!
Hello Guys!
Recently - i think after update to 5.1.1 - I've noticed that bluetooth in my 5t turns ON without me doing it. Do you know any idea what causes that?
Just to add - it's not caused by the localization method - i have turned that off for bluetooth in options that's why i can't find any other reason. Can't find any pattern - it happens when i have phone in the pocket or some time after i'll connect it to the charger, etc.
Thanks for sharking your thoughts.
Guys, is there any .log file available on our phones or any app which could tell me when BT is switching on? I can't find any pattern for that. The most common is that when i'm plugging 5t to the charger BT turns on but i don't know when. I was observing the phone for 15mins and nothing happened, i came back 40mins later and BT is ON. It's really annoying. It also turns ON without plugging phone to the charger. It's really strange. I've looked some info in the permissions but i don't see anything connected to Bluetooth there. The issue didn't stopped even after recent update.
Thanks for any help!