I've had the lg g3 (verizon, rooted) for almost 4 months. The phone has worked flawlessly with my car bluetooth until the past week or so. Now it, randomly disconnects from the car. I recently added clean master and cm security to my phone, but I deleted them to see if they were the problem and I am still getting random disconnects. Any ideas? Is there some type of app I can use to monitor (log) processes during the course of the day to try and identify what is causing the disconnect? I have tried unpairing and re-pairing the phone. The first time I used the phone after the re-pairing, there was no disconnect, however, in subsequent trips, the disconnect issue reappeared. Any suggestions appreciate, thanks in advance!
Related
I have a Sprint Touch Pro2 running stock 6.5 ROM and a 2005 Acura TL. When I got the phone a few weeks ago, I was able to pair the two without problems and it persisted reliably. I was able to shut BT off and turn it back on and the pairing would take place immediately.
Four or five days ago, though, the pairing would drop periodically, forcing me to re-pair, and now, the pairing will disappear almost immediately if I'm able to get them to pair at all. Most of the time I can't get the phone to 'see' the car.
FWIW, I use my own 4-number PIN, and when the phone sees the car, I'm able to enter that PIN and pair them.
I of course was installing a lot of stuff on the phone, although nothing that one would expect might affect the BT, so I flashed back to the stock 6.5 ROM last night to see if it helped (it didn't- same prob today).
Before I take this thing back to Sprint and smash it on their counter, anyone have any ideas about settings I might not be aware of that could affect this?
Thanks in advance for any help.
PS: I'm going to be testing my old phone (Treo 800w) on the car later to see if it still pairs to eliminate the car as the problem.
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
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....
Hey guys. My watch keeps constantly disconnecting and connecting all day long. I've tried everything and still no luck. Is it a bug with the latest android wear update do you think? The app even sort of freezes when I open it sometimes where it doesn't display the watch I'm connected to and you can't do anything. Thanks for your help.
It seems to happen each time there is a notification. Ill do a test text to myself and when it comes through on my phone, instead of receiving it on my watch it starts the whole disconnect / connect process and by the time it finally connects, the notification is missed.
Thanks for your help.
Ryan.
I also have this issue. Then I reset the watch and everything runs fine for a few weeks. But then it suddenly acts up really badly. I've just done a reset after a complete malfunction, where it wouldn't even connect anymore.
EDIT: I contacted Huawei regarding this issue and they offered a waranty case as they suspect a defective BT unit.
I'm doubting. Especially if I would get a red-glow unit after a replacement, it would really be bad.
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.